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

[vlsi99]

When I select "backup and recovery" with CWR , it takes me back to the previous screen like there is nothing to restore.

thanks

 

[scotty85]

When I select "backup and recovery" with CWR , it takes me back to the previous screen like there is nothing to restore.

thanks

are you selecting with the correct button? im admittedly fuzzy on inc 2 stuff too i personally use amon recovery when i can. you might give it a shot. altho,you will need cw to restore your backup if thats what you used to make it.

also make sure the whole folder is in your cwm/backup folder on your sd card. if just the images are there,the phone wont see them.

sorry for the delayed response,been a busy weekend

 

[ViljarKuusk]

As a new member here I apologize if I'm not doing something right, but I really want to thank you Scotty85 for this guide... After about 20 hours I have finally achieved s-off with revolutionary and have superuser rights to my Dinc2. What would us Noobs do without guys like Scotty85! LOL Thanks again, and keep up the good work!

 

[scotty85]

awsome! glad it was helpful :smokingsomb:

 

[fifthlake]

I created an account for the sole purpose of thanking Scotty. I have had the DIC2 for a while now and since I am up for an upgrade with big red I decided to start experimenting. I followed the steps in post 2 and everything worked perfectly except I did get into bootloop. I flashed the radio and now all is good.

Thanks a lot Scotty. You da man!

 

[GeneticEntity]

Ok, so I picked up a 2.3.4 DINC2 today, with 6.04.605.0710RD. I've spent all day trying to figure out how to get it downgraded and rooted but eventually I settled on this guide. Nothing else was working, however I think I finally noticed my problem: the phone isn't working with adb. I'm just getting this:

C:\miniadb_inc2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

And that's it. It doesn't list devices. The phone is also not showing up under Device Manager. USB Debugging is on, it's in Charge Only, fastboot is off. It's almost like it's not connected to my computer... I don't *THINK* it's the cord, though, as it will charge it, but I could be wrong. Not sure if we have another to use, I'll check. But, overall, the problem is this phone isn't showing up on my computer no matter what I do and hence I can't get the thing rooted. I don't know what to do. Can anyone help?

Oh, and I am running XP, but, so far everything I've seen for 7 works the same way here, so, I don't think that's an issue.

 

[bberryhill0]

Can your computer see the phone if you mount it as a storage device?

 

[GeneticEntity]

No. It doesn't seem to matter what I set it as.

 

[bberryhill0]

Sounds like a driver issue.

 

[scotty85]

Ok, so I picked up a 2.3.4 DINC2 today, with 6.04.605.0710RD. I've spent all day trying to figure out how to get it downgraded and rooted but eventually I settled on this guide. Nothing else was working, however I think I finally noticed my problem: the phone isn't working with adb. I'm just getting this:

C:\miniadb_inc2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached

And that's it. It doesn't list devices. The phone is also not showing up under Device Manager. USB Debugging is on, it's in Charge Only, fastboot is off. It's almost like it's not connected to my computer... I don't *THINK* it's the cord, though, as it will charge it, but I could be wrong. Not sure if we have another to use, I'll check. But, overall, the problem is this phone isn't showing up on my computer no matter what I do and hence I can't get the thing rooted. I don't know what to do. Can anyone help?

Oh, and I am running XP, but, so far everything I've seen for 7 works the same way here, so, I don't think that's an issue.

does indeed sound like a driver issue. definately dont take your usb cable for granted- ive learned the hard way not all are created equal

here are some basic driver troubleshooting steps:

Spoiler

troubleshooting connectivity issues:
*make sure you have changed to your adb/fastboot directory!
*make sure usb debugging is enabled(checkmarked) to use adb in the OS
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot(not hboot!),enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.

 

[scotty85]

Any luck?

 

[mauryoung10]

Hi I followed your instructions to the T and all went throught without errors however when i check the HBOOT version im still seeing .98

Can i get some assistance please?

 

[scotty85]

Hi I followed your instructions to the T and all went throught without errors however when i check the HBOOT version im still seeing .98

Can i get some assistance please?

sure,but were going to need more info

you will need to try the process again,and make note of any errors,and paste a copy of your cmd window here- the entire process. something went wrong somewhere but theres unfortunately no way to know exactly what or where witout seeing it.

 

[mauryoung10]

sure,but were going to need more info

you will need to try the process again,and make note of any errors,and paste a copy of your cmd window here- the entire process. something went wrong somewhere but theres unfortunately no way to know exactly what or where witout seeing it.

Ok will try it now that im at work and let you know. Does it matter if it's 64 bit windows?

Other thing when I boot by holding the volume down and power button I see "unlocked" highlighted in pink will that be a factor in this method?

 

[mauryoung10]

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

C:\Windows\system32>cd c:\miniadb_inc2

c:\miniadb_inc2>md5sumsRUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.0
9.01.0622_NV_VZW1.92_release_199487_si.zip
'md5sumsRUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZ
W1.92_release_199487_si.zip' is not recognized as an internal or external comman
d,
operable program or batch file.

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 - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
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 - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
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 - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
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 - PC-Tools.Net: Tools and utilities for Windows, Unix/Linux, DOS
Type md5sums -h for help

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

c:\miniadb_inc2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT16WMA09286 device


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

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

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.

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

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

c:\miniadb_inc2>adb reboot bootloader

c:\miniadb_inc2>fastboot devices
HT16WMA09286 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.113s]
finished. total time: 0.113s

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

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.644s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 54.436s

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.704s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 54.384s

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

c:\miniadb_inc2>fastboot reboot
rebooting...
finished. total time: 0.229s

c:\miniadb_inc2>


This is the entire process that I just did but still the same result. could you please assist?

 

[bberryhill0]

The last two zips didn't flash but I don't know what causes that.

 

[mauryoung10]

The last two zips didn't flash but I don't know what causes that.

I'm clueless as to what to do now. Was really looking forward to getting this done

 

[bberryhill0]

Scotty will know. My guess is that you didn't start in the right state.

 

[mauryoung10]

Scotty will know. My guess is that you didn't start in the right state.

when I boot by holding the volume down and power button I see "unlocked" highlighted in pink will that be a factor in this method?

 

[bberryhill0]

Just guessing again but you may be able to just run the last two flash commands to finish the process because you are already unlocked.

 

[mauryoung10]

Ok I'm happy to report that (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) aspect ran and did all it should got the "OKAY" I was looking for...

I never relocked the bootloader before I went ahead with the instructions. I have now done so and waiting to run revolutionary and then flash the radio..

I was able to instal revolutionary recovery on my phone without a problem.

 

[scotty85]

Ok I'm happy to report that (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) aspect ran and did all it should got the "OKAY" I was looking for...

I never relocked the bootloader before I went ahead with the instructions. I have now done so and waiting to run revolutionary and then flash the radio..

I was able to instal revolutionary recovery on my phone without a problem.

Looks like you have gotten yourself sorted. As you've found error 99 is the "bootloader unlocked" error. Holler if you have further questions

 

[mauryoung10]

when I initially finished flashing the cm 7 rom and doing the regular setup, I came up on a section that says it was activating my phone so it was making a call but the thing is I'm not on verizon network im on another network so it was like I was waiting forever for that call to actually activate the phone. I cancelled and moved along but there was a message saying I wouldn't be able to connect to a service to make calls etc and opted to ignore it. Now there no signal and when I search or select global still no signal bars. can u assist me please?

 

[scotty85]

when I initially finished flashing the cm 7 rom and doing the regular setup, I came up on a section that says it was activating my phone so it was making a call but the thing is I'm not on verizon network im on another network so it was like I was waiting forever for that call to actually activate the phone. I cancelled and moved along but there was a message saying I wouldn't be able to connect to a service to make calls etc and opted to ignore it. Now there no signal and when I search or select global still no signal bars. can u assist me please?

What network are you on? This process should not have interfered with the flash to a.different cdma network. If this is how your using it,you may need to.contact that carrier.

If you're using it on a gsm network,i believe the issue is simply that cm7 is not set up to work that way. Try a stockish rom and see if things work again

 

[mauryoung10]

What network are you on? This process should not have interfered with the flash to a.different cdma network. If this is how your using it,you may need to.contact that carrier.

If you're using it on a gsm network,i believe the issue is simply that cm7 is not set up to work that way. Try a stockish rom and see if things work again

I think thats the problem im using a gsm carrier. what other rom would you suggest that works well and is stockish?