Go Back   Android Forums > Android Phones > HTC Droid Incredible 2 > Incredible 2 - All Things Root

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree22Likes

test: Reply
 
LinkBack Thread Tools
Old July 29th, 2012, 04:27 PM   #1 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default [guide] How to manually downgrade firmware build 6.01.605.05 and newer

please note: taco root does not work in build 6.04.605.07. if you are on that build or newer,please follow the directions in post #2 to unlock and root using htcdev,then downgrade to s off.

this first post is a guide to manually temp root and downgrade build number 6.01.605.05 for the incredible 2(Vivo_W).

it will downgrade the inc 2 to build number 2.18.605.3,so that revolutionary can be run to achieve s-off.

this not my work,i am just trying to simplify it into a more understandable process. its intended to help new rooters get a basic understanding of adb,fstboot,and doing things in a cmd window. it is intended to take the mystery out of setting up the sdk,as the whole thing is not needed for most folks.

credits:
-jcase for taco root and the universal misc-version
-prototype7 for this guide on xda
-condemned soul for hookin me up with a 605.5 ruu
-sele and the crew in the "rescue squad" on the thunderbolt forum for what i like to call the "mini-adb" concept.

1)download this file
miniadb_inc2
md5: miniadb_inc2.zip 173e70b48de6ba663866c2e334187aad

2)install drivers
-use these,from Revolutionary: htc drivers

3)prepair to downgrade
-unzip,or extract the contents of miniadb_inc2.zip. some versions of windows you may need a utility such as "7zip" to do this.

-move the unzipped miniadb_inc2 folder to the root of your C drive

-open a CMD window. on windows 7,click the start bubble,type "command" or "cmd" in the search box. this should open a small black window. it may be same or similar for other windows versions.

-enable usb debugging in settings/apps/development. disable fastboot in settings/power. plug in your phone,and select charge only mode.

*make sure your phone is charged to 100% before starting the donwgrade process. it will reboot several times. it must then flash factory firmware,and you dont want it do die in the middle of the flash.

-now type in the cmd window,at the prompt: cd c:\miniadb_inc2

-provided that you unzipped the file,placed it correctly on the root of your PCs C drive,and didnt change the name,this should change your prompt to c:\miniadb_inc2>


4)downgrade with adb
*from this point forward,all commands will be in bold you can copy,then paste them into the cmd window,one at a time. blue are just additional info/comments,and should not be copy/pasted

md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip should return cea499f51b40055ffd118960e1e73255. if youh ave trouble here,search the pasted line for spaces that shouldnt be there.

md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip should return ea6b98be48210d7797e62362f49ff751

md5sums tacoroot.sh should return 6ec06d776feb212d8b2a55817eddf76d

md5sums misc_version should return 050f55d34ddbcc860efa5982491437de

adb devices should return your phones serial number. indicating drivers are working,and youre connected.

adb push tacoroot.sh /data/local/

adb shell chmod 755 /data/local/tacoroot.sh

adb shell /data/local/tacoroot.sh --setup

your phone will reboot,eventually ending up on the stock recovery screen,with a picture of a phone,red ! and triangle. press vol up and power. this should bring up some writing(menu options for stock recovery). dont select any of these options. hold vol up,vol down,and power until the phone reboots.

once your fully booted:


adb shell /data/local/tacoroot.sh --root

at this point your phone will become confused and unstable. it will reboot. maybe a couple of times.it may hang. it may start boot looping(what my phone did),or it may do other strange things as well. let the phone boot as far as its going to.

if it gets so far,and starts bootlooping,thats ok,continue on:


adb push misc_version /data/local/tmp/misc_version

adb shell chmod 777 /data/local/tmp/misc_version

adb shell /data/local/tmp/misc_version -s 2.18.605.3

adb shell /data/local/tacoroot.sh --undo

at this point,your phone will reboot again. this time,it should boot fully back into the OS,and once again be stable. as soon as it does:

adb reboot bootloader

fastboot devices again,this should output your serial number,indicating youre connected and drivers are working

fastboot getvar mainver it should output 2.18.605.3 if it does,then procede. if not,something above was not entered correctly,and the downgrade will not flash. reboot your phone using the command fastboot reboot and start again at step 4.

if you did get 2.18.605.3 then continue:


fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip (as above, if youh ave trouble here,search the pasted line for spaces that shouldnt be there)

this part will take some time,so please be patient,its not hung. it will check the file,send it,then start writing. do not under any circumstance interupt the phone while the writing is flashing in the comd window,indicating partitions are being written to.

once you get OKAY and finished. total time: xxx.xxxs then:


fastboot reboot-bootloader

this will take your phone out of RUU mode,and back to fastboot. note that you now have hboot .97

fastboot reboot will boot you fully into the revolutionary-able 2.18.605.3 firmware.

download and run Revolutionary

you can have revolutionary install a recovery,or install one manually after s-off is achieved. included in miniadb_inc2 download is the 0312 radio,wich you will need to flash if you start experincing bootloops.

if you need to flash the 0312 radio:
put the phone in fastboot mode(select fastboot from hboot menu),open a cmd window,change to miniadb_inc2 directory, then enter:

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)

fastboot reboot-bootloader (make sure your baseband changed)

fastboot reboot


i personally reccomend amon_ra recovery. you can find it here: [Recovery] Amon Ra Style Recovery for Incredible 2 vivow - xda-developers

here is what the commands and responses will look like in your cmd window. red are my inputs,blue are simply additional comments:

Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>cd c:\miniadb_inc2

c:\miniadb_inc2>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.
09.01.0622_NV_VZW1.92_release_199487_si.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc2\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255

c:\miniadb_inc2>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc2\]
1.09.01.0312_vivow_Radio_PG32IMG.zip           ea6b98be48210d7797e62362f49ff751

c:\miniadb_inc2>md5sums tacoroot.sh

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc2\]
tacoroot.sh                                    6ec06d776feb212d8b2a55817eddf76d

c:\miniadb_inc2>md5sums misc_version

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename                              MD5 sum
-------------------------------------------------------------------------------
[c:\miniadb_inc2\]
misc_version                                   050f55d34ddbcc860efa5982491437de

c:\miniadb_inc2>adb devices
List of devices attached
HTxxxxxxxxxx    device


c:\miniadb_inc2>adb push tacoroot.sh /data/local/
297 KB/s (2129 bytes in 0.007s)

c:\miniadb_inc2>adb shell chmod 755 /data/local/tacoroot.sh

c:\miniadb_inc2>adb shell /data/local/tacoroot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory

phone will reboot to stock recovery. press vol up and power to get stock recovery menu. press vol down,vol up,power to reboot

c:\miniadb_inc2>adb shell /data/local/tacoroot.sh --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.

phone will be unstable,and my reboot or bootloop. do not panic,its normal

c:\miniadb_inc2>adb push misc_version /data/local/tmp/misc_version
2542 KB/s (367096 bytes in 0.141s)

c:\miniadb_inc2>adb shell chmod 777 /data/local/tmp/misc_version

c:\miniadb_inc2>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...

c:\miniadb_inc2>adb shell /data/local/tacoroot.sh --undo
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by

both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Root removed, rebooting

allow phone to fully boot

c:\miniadb_inc2>adb reboot bootloader

c:\miniadb_inc2>fastboot devices
HTxxxxxxxxxx    fastboot

c:\miniadb_inc2>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s

c:\miniadb_inc2>fastboot erase cache
               erasing 'cache'... OKAY [  0.114s]
finished. total time: 0.114s

c:\miniadb_inc2>fastboot oem rebootRUU
                              ... OKAY [  0.213s]
finished. total time: 0.213s

c:\miniadb_inc2>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605
.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
     sending 'zip' (292817 KB)... OKAY [ 48.709s]
                 writing 'zip'... INFOzip header checking...
INFOshift signature_size for header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,31
INFO[RUU]UZ,boot,73
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,22
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,63
INFO[RUU]UZ,recovery,84
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,13
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,42
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,56
INFO[RUU]UZ,system,61
INFO[RUU]UZ,system,65
INFO[RUU]WP,system,0
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,13
INFO[RUU]WP,system,16
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,30
INFO[RUU]WP,system,33
INFO[RUU]WP,system,39
INFO[RUU]WP,system,42
INFO[RUU]WP,system,47
INFO[RUU]WP,system,50
INFO[RUU]WP,system,55
INFO[RUU]WP,system,59
INFO[RUU]WP,system,65
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,67
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,73
INFO[RUU]UZ,system,77
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,98
INFO[RUU]WP,system,65
INFO[RUU]WP,system,67
INFO[RUU]WP,system,70
INFO[RUU]WP,system,73
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,85
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO[RUU]WP,tp,0
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,7
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,21
INFO[RUU]UZ,radio,27
INFO[RUU]UZ,radio,34
INFO[RUU]UZ,radio,42
INFO[RUU]UZ,radio,48
INFO[RUU]UZ,radio,55
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,76
INFO[RUU]UZ,radio,83
INFO[RUU]UZ,radio,90
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,5
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,33
INFO[RUU]WP,radio,42
INFO[RUU]WP,radio,100
OKAY [160.164s]
finished. total time: 208.874s

c:\miniadb_inc2>fastboot reboot-bootloader
                     rebooting into bootloader... OKAY [  0.160s]
finished. total time: 0.156s

c:\miniadb_inc2>fastboot reboot
                     rebooting...
finished. total time: 0.161s
serenityy likes this.

__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
donate to my device fund
scotty85 is online now  
Last edited by scotty85; August 5th, 2013 at 08:03 PM.
Reply With Quote
The Following 18 Users Say Thank You to scotty85 For This Useful Post:
4MUSKRAT (September 22nd, 2012), bberryhill0 (July 29th, 2012), cdrom511 (July 31st, 2012), cheesiepoof (July 30th, 2012), Chindu (January 3rd, 2013), HpTouchMePad (August 15th, 2012), jenx117 (September 3rd, 2012), jntdroid (August 27th, 2012), KaHOnas (August 6th, 2012), kirkers (October 9th, 2012), little york (August 30th, 2012), magdelaine (September 6th, 2012), NiceGuyJon (November 12th, 2012), pantallica7420 (November 1st, 2012), serenityy (August 1st, 2012), speedster63 (March 27th, 2014), thedon81 (July 14th, 2013), weaverinva (August 14th, 2013)
sponsored links
Old July 29th, 2012, 04:50 PM   #2 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default method 2: use htcdev instead of taco root

reported working!

this method should work for any future builds,as long as we continue to have unlock support,even if taco root and other exploits fail. it may at some point even warrant its own thread.



download miniadb_inc2 from above

1)unlock with hctdev,install recovery,flash root files
[guide] unlock with htcdev

2)downgrade with adb
*from this point forward,all commands will be in bold you can copy,then paste them into the cmd window,one at a time. blue are just additional info/comments,and should not be copy/pasted

md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip should return cea499f51b40055ffd118960e1e73255. if youh ave trouble here,search the pasted line for spaces that shouldnt be there.

md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip should return ea6b98be48210d7797e62362f49ff751

md5sums misc_version should return 050f55d34ddbcc860efa5982491437de

adb devices should return your phones serial number. indicating drivers are working,and youre connected.

adb push misc_version /data/local/tmp/misc_version

adb shell should change your prompt to a #if not,have your phone awake and watch the screen to grant superuser permissions when you enter su

chmod 777 /data/local/tmp/misc_version *have your phone awake and be watching it,incase superuser needs you to grant permission

/data/local/tmp/misc_version -s 2.18.605.3

exit exit again if your promt changes to a $

adb reboot bootloader

fastboot devices again,this should output your serial number,indicating youre connected and drivers are working

fastboot getvar mainver it should output 2.18.605.3 if it does,then procede. if not,something above was not entered correctly,and the downgrade will not flash. reboot your phone using the command fastboot reboot and start again at step 2.

if you did get 2.18.605.3 then continue:


fastboot oem lock *may casue a security warning if youre on a cusom rom,or extrememly modded stock rom. if it does,dont panic,this is normal. in a worse case if the ruu wont flash,you can simply re-unlock with your original unlock token. relocking the bootloader may cause your phone to reboot. if it does,simply let it reboot,renable usb debug,disable fastboot,and adb reboot bootloaderback to fastboot. then procede

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip (as above, if youh ave trouble here,search the pasted line for spaces that shouldnt be there)

this part will take some time,so please be patient,its not hung. it will check the file,send it,then start writing. do not under any circumstance interupt the phone while the writing is flashing in the comd window,indicating partitions are being written to.

once you get OKAY and finished. total time: xxx.xxxs then:


fastboot reboot-bootloader

this will take your phone out of RUU mode,and back to fastboot. note that you now have hboot .97

fastboot reboot will boot you fully into the revolutionary-able 2.18.605.3 firmware.

download and run Revolutionary

you can have revolutionary install a recovery,or install one manually after s-off is achieved. included in miniadb_inc2 download is the 0312 radio,wich you will need to flash if you start experincing bootloops.

if you need to flash the 0312 radio:
putt the phone in fastboot mode(select fastboot from hboot menu),open a cmd window,change to miniadb_inc2 directory then enter:

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)

fastboot reboot-bootloader (make sure your baseband changed)

fastboot reboot



i personally reccomend amon_ra recovery. you can find it here: [Recovery] Amon Ra Style Recovery for Incredible 2 vivow - xda-developers
scotty85 is online now  
Last edited by scotty85; December 19th, 2012 at 05:48 AM.
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
ViljarKuusk (September 28th, 2013)
Old July 29th, 2012, 04:50 PM   #3 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

uno mas
scotty85 is online now  
Reply With Quote
Old July 29th, 2012, 05:28 PM   #4 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

Do you have to make sure you are running the cmd window as admin?
__________________
My Eris apps
bberryhill0 is online now  
Reply With Quote
Old July 29th, 2012, 06:06 PM   #5 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by bberryhill0 View Post
Do you have to make sure you are running the cmd window as admin?
i have never done that,in anything i do with adb/fastboot.
scotty85 is online now  
Reply With Quote
Old July 29th, 2012, 08:40 PM   #6 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

Do you always run as admin? It's something that gets mentioned a lot in the root threads. You have to right-click somewhere and choose Run as Admin for the cmd window if you are running as a regular user.
bberryhill0 is online now  
Reply With Quote
Old July 30th, 2012, 04:18 AM   #7 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by bberryhill0 View Post
Do you always run as admin? It's something that gets mentioned a lot in the root threads. You have to right-click somewhere and choose Run as Admin for the cmd window if you are running as a regular user.
a root tool,or a .exe file i will run as admin,unless the directions specifically say not to.

but a cmd window,i have never run as admin.
scotty85 is online now  
Reply With Quote
Old July 30th, 2012, 10:07 PM   #8 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Thank you scotty85!! I now have the 2.18 firmware and will proceed to Revolutionary.

I ran into one hiccup: When I flashed 2.18 firmware I got an error message stating:

error: cannot load 'Ruu_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_R a'

due to the command line not wanting to read the entire file name. I shortened the file name and loaded it without issue. Note it takes about 6 minutes to load.

This post saved me an incredible amount of time, and saved my Verizon phone. (a carrier I'm seriously considering ditching!)
cheesiepoof is offline  
Last edited by cheesiepoof; July 30th, 2012 at 10:37 PM. Reason: problem fixed
Reply With Quote
The Following User Says Thank You to cheesiepoof For This Useful Post:
scotty85 (July 31st, 2012)
Old July 31st, 2012, 12:00 AM   #9 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

Score! Good job Scotty.
bberryhill0 is online now  
Reply With Quote
The Following 2 Users Say Thank You to bberryhill0 For This Useful Post:
HpTouchMePad (August 15th, 2012), scotty85 (July 31st, 2012)
Old July 31st, 2012, 06:18 AM   #10 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by cheesiepoof View Post
Thank you scotty85!! I now have the 2.18 firmware and will proceed to Revolutionary.

I ran into one hiccup: When I flashed 2.18 firmware I got an error message stating:

error: cannot load 'Ruu_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_R a'

due to the command line not wanting to read the entire file name. I shortened the file name and loaded it without issue. Note it takes about 6 minutes to load.

This post saved me an incredible amount of time, and saved my Verizon phone. (a carrier I'm seriously considering ditching!)
sorry about the wierd space issue. im not sure how to avoid that,in retrospect i could have just changed the name of the RUU.maybe i will do that and re-upload later. there is no space when i pasted it into the reply box,but for some reason when it posts the thread publicly it is there ive tried making the writing smaller,and a couple thigns to make that line one long line,with no spaces.

until i can change it, other folks can avoid the error without shortening simply by backspacing back,and deleting the space between Ra and dio

at any rate,glad the guide was useful

edit:
out of curiosity,what did you experince on taco root? my phone bootlooped while i was entering the next commands,lol. did you experience the same,or something different?
scotty85 is online now  
Last edited by scotty85; July 31st, 2012 at 06:25 AM.
Reply With Quote
sponsored links
Old July 31st, 2012, 02:14 PM   #11 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 2 Times in 1 Post
Thumbs up

Thx so much worked great!
I dunno what I did wrong the first time but I had to run twice
Anyway 2nd time no hiccups

Update: my phone won't stay on (Help? please?) I dont have/ cant find the .0312 radio file, plus anyway how am I supposed to flash it if my phone is stuck in bootloop?
Update 2: All is good Thanks
cdrom511 is offline  
Last edited by cdrom511; July 31st, 2012 at 05:08 PM.
Reply With Quote
The Following 2 Users Say Thank You to cdrom511 For This Useful Post:
HpTouchMePad (August 15th, 2012), KaHOnas (August 6th, 2012)
Old July 31st, 2012, 04:37 PM   #12 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by cdrom511 View Post
Thx so much worked great!
I dunno what I did wrong the first time but I had to run twice
Anyway 2nd time no hiccups
it may have something to do with the exploit. i had to run it twice as well in theory,the "setup" portion gets it ready,but maybe with this software version there is a lil something different?

i figured i just goofed something up the first time,but now that youve mentioned it,im curious to see if others have to run it twice as well.

Quote:
Originally Posted by cdrom511 View Post
Update: my phone won't stay on (Help? please?) I dont have/ cant find the .0312 radio file, plus anyway how am I supposed to flash it if my phone is stuck in bootloop?
the 0312 radio is included in the miniadb_inc2 download. its a zip file called 1.09.01.0312_vivow_Radio_PG32IMG. flashing shoulnt be an issue,as your phone wont be bootlooping in fastboot/hboot. you can flash it in hboot as a PG32IMG,or you can flash it with fastboot commands like above,by putting the phone in fastboot mode(select fastboot from hboot menu) then enter:

fastboot erase cache

fastboot oem rebootRUU

fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)

fastboot reboot-bootloader (make sure your baseband changed)

fastboot reboot



maybe i should have put this in the original instructions?

i assume the prollem comes from having revolutionary hboot with a certain newer radio? i dint have any bootloop issues,but im clip s-offed,so im on the stock .98 hboot. ill have to research this boot loop thing since my inc 2 isnt my daily driver now...
scotty85 is online now  
Last edited by scotty85; August 6th, 2012 at 05:06 AM.
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
KaHOnas (August 6th, 2012)
Old July 31st, 2012, 08:00 PM   #13 (permalink)
New Member
 
serenityy's Avatar
 
Join Date: Jul 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Hi. I'm new here.
fastboot does not detect my device. It shows absolutely nothing. However, adb works fine, it shows device. How do I fix this problem?
serenityy is offline  
Reply With Quote
Old July 31st, 2012, 08:56 PM   #14 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by serenityy View Post
Hi. I'm new here.
fastboot does not detect my device. It shows absolutely nothing. However, adb works fine, it shows device. How do I fix this problem?
make sure that you have your phone in fastboot,not hboot.(adb reboot bootloader should boot you to fastboot. powering the phone on via vol down/power takes you to hboot)

try reinstalling the drivers(use the ones linked here,if you havent allready)

temorarily disable htc sync,and any other program that can comunicate with the phone.

if none of that works,you can try installing the drivers manually by extracting the driver file,then open device manager. place the phone in fastboot,plug it in,and when it pops up,right click and manually update drivers,directing the wizard to the extracted driver folder.

last and not least,make sure you are entering fastboot devices(not adb devices). sorry if that seems like common sense,its actually a pretty common error.
scotty85 is online now  
Reply With Quote
Old August 1st, 2012, 08:28 AM   #15 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by cdrom511 View Post
Update 2: All is good Thanks
did you flash the radio from the download? or did you have to find it elsewhere? sorry i was late getting you directions

at any rate,im glad youre back up and running.
scotty85 is online now  
Reply With Quote
Old August 1st, 2012, 07:22 PM   #16 (permalink)
New Member
 
serenityy's Avatar
 
Join Date: Jul 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by scotty85 View Post
make sure that you have your phone in fastboot,not hboot.(adb reboot bootloader should boot you to fastboot. powering the phone on via vol down/power takes you to hboot)

try reinstalling the drivers(use the ones linked here,if you havent allready)

temorarily disable htc sync,and any other program that can comunicate with the phone.

if none of that works,you can try installing the drivers manually by extracting the driver file,then open device manager. place the phone in fastboot,plug it in,and when it pops up,right click and manually update drivers,directing the wizard to the extracted driver folder.

last and not least,make sure you are entering fastboot devices(not adb devices). sorry if that seems like common sense,its actually a pretty common error.
I reinstalled the drivers and I still have the same problem. I have my phone in fastboot...

Android ADB Interface disappears in fastboot. I think that's the problem...


This one is not in fastboot.
serenityy is offline  
Reply With Quote
Old August 1st, 2012, 08:20 PM   #17 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

do you have the fastboot utility in the windows\system32 folder? AdbWinApi.dll?

try changing to the miniadb_inc2 directory and try again.
scotty85 is online now  
Reply With Quote
Old August 1st, 2012, 08:39 PM   #18 (permalink)
New Member
 
serenityy's Avatar
 
Join Date: Jul 2012
Posts: 3
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by scotty85 View Post
do you have the fastboot utility in the windows\system32 folder? AdbWinApi.dll?

try changing to the miniadb_inc2 directory and try again.
I changed the directory to the miniadb_inc2 and still the same thing....
serenityy is offline  
Reply With Quote
Old August 1st, 2012, 08:58 PM   #19 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

my only suggestion at this point,is to try a different PC. sounds like something on your pc is interering with fastboot.

the times i have seen things like this(where everything looks 100% correct and it still doesnt work) more often than not,users are able to get it to work on a "virgin" computer that has never had phone stuff installed on it.
scotty85 is online now  
Reply With Quote
Old August 6th, 2012, 01:08 AM   #20 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 11
 
Device(s):
Carrier: Not Provided

Thanks: 5
Thanked 4 Times in 4 Posts
Default

Quote:
Originally Posted by scotty85 View Post
...fastboot reboot bootloader (make sure your baseband changed)...
Just a minor syntax error I noticed, for those of you who are flashing the radio .

fastboot reboot-bootloader

Don't forget to put a hyphen between reboot and bootloader. This took me a second to figure out.

Thanks a bunch, Scotty! This thread has been fantastic!
KaHOnas is offline  
Last edited by KaHOnas; August 6th, 2012 at 01:10 AM. Reason: cleaning it up
Reply With Quote
The Following User Says Thank You to KaHOnas For This Useful Post:
scotty85 (August 6th, 2012)
sponsored links
Old August 9th, 2012, 08:21 AM   #21 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 8
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 2 Posts
Default

I used HTC Devtool to unlock my bootloader not knowing that it wouldn't give me s-off now that I have done so am I stuck? Can I still use your guide to get s-off?
cjoc is offline  
Reply With Quote
Old August 9th, 2012, 09:58 AM   #22 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Yes,you can still use it. You can even flash root.files since you're unlocked,and not have to fool with taco root.

I.can give some more specific instructions later if you need them.
scotty85 is online now  
Reply With Quote
Old August 9th, 2012, 11:47 PM   #23 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

To get s-off you have to relock first.
bberryhill0 is online now  
Reply With Quote
Old August 10th, 2012, 12:19 AM   #24 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 12
Thanked 1 Time in 1 Post
Default

hey guys just got a inc2 with this FW , i have read the taco method and this ( other guide too ) I was just wondering if there is any benefit to rooting now before ICS update is released ? ( basically is it gonna have to be rooted all over again after the update and if so any benefit to rooting now ) I would hate to do this only to have to do it all over again in a few weeks when ICS comes out . what do you guys think ? fyi thanks for the guides
HpTouchMePad is offline  
Reply With Quote
Old August 10th, 2012, 08:21 AM   #25 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by HpTouchMePad View Post
hey guys just got a inc2 with this FW , i have read the taco method and this ( other guide too ) I was just wondering if there is any benefit to rooting now before ICS update is released ? ( basically is it gonna have to be rooted all over again after the update and if so any benefit to rooting now ) I would hate to do this only to have to do it all over again in a few weeks when ICS comes out . what do you guys think ? fyi thanks for the guides
it is always better to root sooner than later.when you are s-off,things will be easy i the future,where if you stay s-on,exploits will be broken,and the processes may be more complex(or nonexistant )

even if inc2 gets factory ICS wich includes a new bootloader,youll easily be able to install an upgraded hboot since youre allready s-off.

IMO dont wait.
scotty85 is online now  
Reply With Quote
Old August 10th, 2012, 09:39 AM   #26 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by scotty85 View Post
Yes,you can still use it. You can even flash root.files since you're unlocked,and not have to fool with taco root.

I.can give some more specific instructions later if you need them.
htcdev directions added in post 2. if i can get an s-on volunteer to verify it works,that would be awsome
scotty85 is online now  
Reply With Quote
Old August 10th, 2012, 12:03 PM   #27 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Hi, I got to the fastboot devices step, but nothing showed up in the cmd prompt. It brought my phone to a different screen and I had the option of rebooting, rebooting the bootloader etc. So I rebooted the phone, went to fastboot getvar mainver and now it has just been sitting at < waiting for device >

What should I do from here? I don't want to screw my phone up. Is there a way to start fresh or if I just stop the process will my phone be messed up?
iiichrisiii is offline  
Reply With Quote
Old August 10th, 2012, 12:41 PM   #28 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by iiichrisiii View Post
Hi, I got to the fastboot devices step, but nothing showed up in the cmd prompt. It brought my phone to a different screen and I had the option of rebooting, rebooting the bootloader etc. So I rebooted the phone, went to fastboot getvar mainver and now it has just been sitting at < waiting for device >

What should I do from here? I don't want to screw my phone up. Is there a way to start fresh or if I just stop the process will my phone be messed up?
the screen you are describing is fastboot. the prior command(adb reboot bootloader) is the one that takes you there. from your description,it sounds like you entered fastboot devices prior to the phone actually being in fastboot(it sometimes takes a minute or 2). the next command failed and hung at 'waiting for device' becasue you rebooted back to the OS,but it needed to be entered in the fastboot screen as well,as do all the commands after it.

you can either:
1)start again at the adb reboot bootloader command,amd this time wait for fastboot to load before you enter the next commands.
or
2)manually put your phone in fastboot by booting to hboot,then select fastboot from the hboot menu. pick up the commands at fastboot devices

hopefully that should get you thru the rest of it.
scotty85 is online now  
Last edited by scotty85; August 10th, 2012 at 12:58 PM.
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
bberryhill0 (August 10th, 2012)
Old August 10th, 2012, 02:14 PM   #29 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by scotty85 View Post
the screen you are describing is fastboot. the prior command(adb reboot bootloader) is the one that takes you there. from your description,it sounds like you entered fastboot devices prior to the phone actually being in fastboot(it sometimes takes a minute or 2). the next command failed and hung at 'waiting for device' becasue you rebooted back to the OS,but it needed to be entered in the fastboot screen as well,as do all the commands after it.

you can either:
1)start again at the adb reboot bootloader command,amd this time wait for fastboot to load before you enter the next commands.
or
2)manually put your phone in fastboot by booting to hboot,then select fastboot from the hboot menu. pick up the commands at fastboot devices

hopefully that should get you thru the rest of it.

Got through it with no problems! Thank you sir.
iiichrisiii is offline  
Reply With Quote
The Following User Says Thank You to iiichrisiii For This Useful Post:
scotty85 (August 10th, 2012)
Old August 10th, 2012, 06:38 PM   #30 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

awsome sauce
bberryhill0 likes this.
scotty85 is online now  
Reply With Quote
sponsored links
Old August 10th, 2012, 07:19 PM   #31 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Thanks your the man have failed in everything with tacoroot and been unlocked this whole time decided to try your 2nd post and let me tell you worked like butter i made an account just to thank you bro! youve made one more person a happy man lol
bberryhill0 and scotty85 like this.
Goon2Gods is offline  
Reply With Quote
The Following User Says Thank You to Goon2Gods For This Useful Post:
scotty85 (August 10th, 2012)
Old August 10th, 2012, 09:17 PM   #32 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by Goon2Gods View Post
Thanks your the man have failed in everything with tacoroot and been unlocked this whole time decided to try your 2nd post and let me tell you worked like butter i made an account just to thank you bro! youve made one more person a happy man lol
excellent! i will go about adding a lil more detail to it. thanks for reporting and glad it worked for ya
scotty85 is online now  
Reply With Quote
Old August 10th, 2012, 10:21 PM   #33 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

Thanks Scotty. It's really cool to have a root thread that works here.
scotty85 likes this.
bberryhill0 is online now  
Reply With Quote
The Following User Says Thank You to bberryhill0 For This Useful Post:
scotty85 (August 11th, 2012)
Old August 11th, 2012, 05:51 AM   #34 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by bberryhill0 View Post
Thanks Scotty. It's really cool to have a root thread that works here.
youre quite welcome. im glad its helpful
scotty85 is online now  
Reply With Quote
Old August 11th, 2012, 10:54 PM   #35 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default Unable to read

when I go to use this command: md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip

I get an error saying "Unable to read file/directory RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip"

any solutions?
skullabyss is offline  
Reply With Quote
Old August 11th, 2012, 11:30 PM   #36 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by skullabyss View Post
when I go to use this command: md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip

I get an error saying "Unable to read file/directory RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip& quot;

any solutions?

You prolly have a space between Ra and dio. Delete the space,or Rename the file to something short and simple in the miniadb folder,and change the command accordingly
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
bberryhill0 (August 12th, 2012)
Old August 13th, 2012, 05:10 PM   #37 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Quote:
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip (as above, if youh ave trouble here,search the pasted line for spaces that shouldnt be there)

this part will take some time,so please be patient,its not hung. it will check the file,send it,then start writing. do not under any circumstance interupt the phone while the writing is flashing in the comd window,indicating partitions are being written to.
I'm stuck on this part. I did it and now all I see is a silver htc and the cmd prompt window saying sending 'zip' <292817 KB>... _ and the underscore is flashing. It's been like this for an hour and I don't know what's going on...does it really take that long to flash the zip over? Or did I mess up?
wolfdroid2012 is offline  
Reply With Quote
Old August 13th, 2012, 05:43 PM   #38 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by wolfdroid2012 View Post
I'm stuck on this part. I did it and now all I see is a silver htc and the cmd prompt window saying sending 'zip' <292817 KB>... _ and the underscore is flashing. It's been like this for an hour and I don't know what's going on...does it really take that long to flash the zip over? Or did I mess up?
as long as its 'sending' youre ok to unplug it. once it starts spitting out stuff(look in the codebox in the OP to see what it looks like),definatley do NOT interupt it.

id uplug it,you may have to pull the battery and manually place the phone back into fastboot to get it recognized again by fastboot devices

sounds like something else is running. make sure you disable htc sync,pda net,easytether,and any other program capable of interacting with the phone.

you did get a matching md5 for the RUU at that step,correct?
scotty85 is online now  
Reply With Quote
Old August 13th, 2012, 05:49 PM   #39 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Correct. Everything worked up until the point where it's sending the zip file. Should I restart the cmd prompt window too?
wolfdroid2012 is offline  
Reply With Quote
Old August 13th, 2012, 05:51 PM   #40 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

I just unplugged the phone and it said FAILED <data transfer failure <too many links>

On the phone it's on the fastboot screen that says

***LOCKED***
Vivo_W XB SHIP S-ON RL
HBOOT-0.98.0000
RADIO-1.09.01.0312
eMMC-boot
Jul 18 2011, 12:39:36
RUU
wolfdroid2012 is offline  
Reply With Quote
sponsored links
Old August 13th, 2012, 06:03 PM   #41 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

yup... the phone is still ruu mode. plug it back in,and it should go back to the black/silver htc screen.

do:
fastboot devices

then
fastboot reboot-bootloader
then
fastboot reboot
if you need to be able to use/boot the phone
scotty85 is online now  
Reply With Quote
Old August 13th, 2012, 06:09 PM   #42 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

Does that mean that the tacoroot worked? Or do I have to manually install that zip onto the sd card and then unzip them via bootloader? Or can I just go straight to revolutionary now to finish the root?
wolfdroid2012 is offline  
Reply With Quote
Old August 13th, 2012, 06:16 PM   #43 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Talking

I am stuck at the same thing
sending 'zip' <292817 KB>

I don't know what I am doing wrong. I've never rooted a phone. The HTC Sync and other programs that you mentioned are those on my phone or computer? How do I stop those?
Thanks for the help
Travo85 is offline  
Reply With Quote
Old August 13th, 2012, 06:18 PM   #44 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by wolfdroid2012 View Post
Does that mean that the tacoroot worked? Or do I have to manually install that zip onto the sd card and then unzip them via bootloader? Or can I just go straight to revolutionary now to finish the root?
if the answer to the fastboot getvar mainver command was 2.18.605.3,then taco root and the adb commands worked. unfortunately,youre only halfway there,you do need to flash the downgrade to be on revolutionary-able firmware.

if you cannot figure out what is running on your PC and confusing the phone,then you certianly can rename the downgrade .zip to PG32IMG and let your phone flash it from your sd card in hboot.

once that downgrade finishes,reboot the phone,then check hboot and make sure you have the .97 hboot
scotty85 is online now  
Reply With Quote
Old August 13th, 2012, 06:46 PM   #45 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

I will give that a try and report back! Thanks!

Quote:
if you cannot figure out what is running on your PC and confusing the phone,then you certianly can rename the downgrade .zip to PG32IMG and let your phone flash it from your sd card in hboot.
When you say this, do I rename RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip to PG32IMG and move it to the SD card, then reboot? Should it automatically update?

And what about the 1.09.01.0312_vivow_Radio_PG32IMG.zip file?

Thank you so much again for answering all these questions.
wolfdroid2012 is offline  
Last edited by wolfdroid2012; August 13th, 2012 at 06:49 PM.
Reply With Quote
Old August 13th, 2012, 07:41 PM   #46 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by wolfdroid2012 View Post
I will give that a try and report back! Thanks!



When you say this, do I rename RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip to PG32IMG and move it to the SD card, then reboot? Should it automatically update?

And what about the 1.09.01.0312_vivow_Radio_PG32IMG.zip file?

Thank you so much again for answering all these questions.
yes,rename "RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_R a dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip" to PG32IMG and place it on the root of your sd. boot to hboot,it should find the file and ask you to update. tell it yes

im still a lil unlcear what situations require the 0312 radio. all i know for sure,is that you need to run revolutionary,then if you start experiencing reboots,then install the radio. you can install it in hboot from the sd as well,if you need to.

just remember,always remove PG32IMG from your sd card immediately after flashing and rebooting. its presense will keep you from entering recovery thru hboot in case of an emergency
scotty85 is online now  
Reply With Quote
The Following User Says Thank You to scotty85 For This Useful Post:
wolfdroid2012 (August 13th, 2012)
Old August 13th, 2012, 08:46 PM   #47 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

The .0312 radio is required to run Sense ROMs. This is only true if you downgrade from the 6.*** firmware. CM ROMs will run with the older radios.
bberryhill0 is online now  
Reply With Quote
The Following User Says Thank You to bberryhill0 For This Useful Post:
scotty85 (August 14th, 2012)
Old August 13th, 2012, 10:31 PM   #48 (permalink)
New Member
 
Join Date: Aug 2012
Posts: 6
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 1 Time in 1 Post
Default

It worked! Everything worked out. After changing the files to PGIMG32 and updating it via hboot (for both of the files) I was able to use revolutionary and then install superuser. Thank you so much!
wolfdroid2012 is offline  
Reply With Quote
The Following User Says Thank You to wolfdroid2012 For This Useful Post:
scotty85 (August 14th, 2012)
Old August 13th, 2012, 10:51 PM   #49 (permalink)
Senior Member
 
bberryhill0's Avatar
 
Join Date: Jan 2010
Location: Rhinelander, WI> Wayzata, MN>Sisters, OR
Posts: 2,338
 
Device(s): Q9c, Eris xtrROM 4.6.5, Droid Concepts 11, Incredible 2 EclipticSense
Carrier: Not Provided

Thanks: 777
Thanked 338 Times in 301 Posts
Default

Scotty is totally awesome.
bberryhill0 is online now  
Reply With Quote
The Following User Says Thank You to bberryhill0 For This Useful Post:
scotty85 (August 14th, 2012)
Old August 14th, 2012, 05:04 AM   #50 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,647
 
Device(s):
Carrier: Not Provided

Thanks: 7,181
Thanked 6,785 Times in 4,267 Posts
Default

Quote:
Originally Posted by bberryhill0 View Post
The .0312 radio is required to run Sense ROMs. This is only true if you downgrade from the 6.*** firmware. CM ROMs will run with the older radios.
cool,thanks for the info. for some reason i thot it was a lil more complicated than that

Quote:
Originally Posted by wolfdroid2012 View Post
It worked! Everything worked out. After changing the files to PGIMG32 and updating it via hboot (for both of the files) I was able to use revolutionary and then install superuser. Thank you so much!
awsome! glad it worked for you
scotty85 is online now  
Reply With Quote
Reply


Go Back   Android Forums > Android Phones > HTC Droid Incredible 2 > Incredible 2 - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 08:15 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.