Root [guide] How to manually downgrade firmware build 6.01.605.05 and newer

[scotty85]

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_Radio_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_Radio_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:

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

C:\Users\Scott>[COLOR="Red"]cd c:\miniadb_inc2[/COLOR]

c:\miniadb_inc2>[COLOR="red"]md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.
09.01.0622_NV_VZW1.92_release_199487_si.zip[/COLOR]

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>[COLOR="red"]md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip[/COLOR]

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>[COLOR="red"]md5sums tacoroot.sh[/COLOR]

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>[COLOR="red"]md5sums misc_version[/COLOR]

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>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:\miniadb_inc2>[COLOR="red"]adb push tacoroot.sh /data/local/[/COLOR]
297 KB/s (2129 bytes in 0.007s)

c:\miniadb_inc2>[COLOR="red"]adb shell chmod 755 /data/local/tacoroot.sh[/COLOR]

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tacoroot.sh --setup[/COLOR]
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

[COLOR="Blue"]phone will reboot to stock recovery. press vol up and power to get stock recovery menu. press vol down,vol up,power to reboot[/COLOR]

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tacoroot.sh --root[/COLOR]
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.

[COLOR="blue"]phone will be unstable,and my reboot or bootloop. do not panic,its normal[/COLOR]

c:\miniadb_inc2>[COLOR="red"]adb push misc_version /data/local/tmp/misc_version[/COLOR]
2542 KB/s (367096 bytes in 0.141s)

c:\miniadb_inc2>[COLOR="red"]adb shell chmod 777 /data/local/tmp/misc_version[/COLOR]

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

c:\miniadb_inc2>[COLOR="red"]adb shell /data/local/tacoroot.sh --undo[/COLOR]
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

[COLOR="blue"]allow phone to fully boot[/COLOR]

c:\miniadb_inc2>[COLOR="red"]adb reboot bootloader[/COLOR]

c:\miniadb_inc2>[COLOR="Red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:\miniadb_inc2>[COLOR="red"]fastboot getvar mainver[/COLOR]
mainver: 2.18.605.3
finished. total time: 0.001s

c:\miniadb_inc2>[COLOR="red"]fastboot erase cache[/COLOR]
               erasing 'cache'... OKAY [  0.114s]
finished. total time: 0.114s

c:\miniadb_inc2>[COLOR="red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.213s]
finished. total time: 0.213s

c:\miniadb_inc2>[COLOR="red"]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[/COLOR]
     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>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
                     rebooting into bootloader... OKAY [  0.160s]
finished. total time: 0.156s

c:\miniadb_inc2>[COLOR="red"]fastboot reboot[/COLOR]
                     rebooting...
finished. total time: 0.161s

 

[scotty85]

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
http://androidforums.com/incredible-2-all-things-root/617779-guide-unlock-htcdev.html#post4958403

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_Radio_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_Radio_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]

uno mas

 

[bberryhill0]

Do you have to make sure you are running the cmd window as admin?

 

[scotty85]

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.

 

[bberryhill0]

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.

 

[scotty85]

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.

 

[cheesiepoof]

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_Ra'

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!)

 

[bberryhill0]

Score! Good job Scotty.

 

[scotty85]

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_Ra'

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 :smokingsomb:

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?

 

[cdrom511]

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

 

[scotty85]

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.

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...

 

[serenityy]

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?

 

[scotty85]

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]

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. :smokingsomb:

 

[serenityy]

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.

 

[scotty85]

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

try changing to the miniadb_inc2 directory and try again.

 

[serenityy]

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....

 

[scotty85]

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.

 

[KaHOnas]

...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!

 

[cjoc]

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?

 

[scotty85]

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.

 

[bberryhill0]

To get s-off you have to relock first.

 

[HpTouchMePad]

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

 

[scotty85]

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.