• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

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?

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

Could you help me out with your second post step 2 install recovery. How do I go about doing that. Do I use fastboot?
 
Upvote 0
I keep getting to a snag on step 4

with
"c:\miniadb_inc2>adb push misc_version /data/local/tmp/misc_version
1707 KB/s (367096 bytes in 0.210s)

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...
Error opening input file."
 
Upvote 0
I keep getting to a snag on step 4

with
"c:\miniadb_inc2>adb push misc_version /data/local/tmp/misc_version
1707 KB/s (367096 bytes in 0.210s)

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...
Error opening input file."

i got that error as well the first time. make sure you run thru it twice in a row. if thAT doesnt make it click,try a reboot and then run it again
 
Upvote 0
I did try it again

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

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

c:\miniadb_inc2>md5sums RUU.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.zip 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>
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
List of devices attached
HT1BLMA01292 device


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

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...
Error opening input file.

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...
Error opening input file.

c:\miniadb_inc2>reboot
'reboot' is not recognized as an internal or external command,
operable program or batch file.

c:\miniadb_inc2>adb reboot bootloader

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...
Error opening input file.

c:\miniadb_inc2>md5sums RUU.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.zip 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 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
List of devices attached
HT1BLMA01292 device


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

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...
Error opening input file.

c:\miniadb_inc2>"

and still got the error
 
Upvote 0
how about this i have root, super user installed, i'm trying to follow the second post, step 4, bc I used htcdev unlock tool, and just want to put ics on my phone and make it work better and I'm stuck here
ok,how bout this:

type
adb shell

then if you get a $

su

have your phone awake and be watching for a superuser pop up
 
Upvote 0
slightly modified step 4:

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

wake up your phone and watch for superuser popups during the next step

adb shell if you get a "$",then enter: SU this should get yuo a "#"

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

/data/local/tmp/misc_version -s 2.18.605.3

exit ( exit again,if you are taken back to a "$" prompt)'

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 oem lock *may casue a security warning if youre on a cusom rom,or extrememly modded stock rom. if it does,dotn panic,this is normal. in a worse case if the ruu wont flash,yo can simply re-unlock with your original unlock token

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

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
 
Upvote 0
Is it suppose to say the failure thing here?
Also thank you for all your help with this, its really annoying but I'm sure you can figure it out,
Patching and backing up misc partition...
# exit
exit
$ exit
exit

c:\Android>adb reboot bootloader

c:\Android>
c:\Android>fastboot devices

c:\Android>
c:\Android>fastboot devices
HT1BLMA01292 fastboot

c:\Android>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.000s

c:\Android>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.530s



so i mixed up a step, but now its working, idk how that happened but thank you very very much buddy

so from there, so i go to step 5? I installed the revolutionary recovery.
 
Upvote 0
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.



i will expand a little more upon this later,but for now:

download miniadb_inc2 from above

1)unlock with hctdev
2)install recovery
3)flash superuser root files( http://www.androidfilehost.com/main/-Support_Files-/superuser/Superuser-3.0.7-efgh-signed.zip ) in recovery

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 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 chmod 777 /data/local/tmp/misc_version *have your phone awake and be watching it,incase superuser needs you to grand adb access

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

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 oem lock *may casue a security warning if youre on a cusom rom,or extrememly modded stock rom. if it does,dotn panic,this is normal. in a worse case if the ruu wont flash,yo can simply re-unlock with your original unlock token

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

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


Hi there thanks for all your info , so is this the suggested method over the 1st post ? or should i wait for you to post more details.


thank you
 
Upvote 0
Is it suppose to say the failure thing here?
Also thank you for all your help with this, its really annoying but I'm sure you can figure it out,
Patching and backing up misc partition...
# exit
exit
$ exit
exit

c:\Android>adb reboot bootloader

c:\Android>
c:\Android>fastboot devices

c:\Android>
c:\Android>fastboot devices
HT1BLMA01292 fastboot

c:\Android>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.000s

c:\Android>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Unknown error))
finished. total time: 0.530s



so i mixed up a step, but now its working, idk how that happened but thank you very very much buddy

so from there, so i go to step 5? I installed the revolutionary recovery.

yes,you get that error when relocking.

no where to go from here,youre done :)

once youre s-off,you can install the 0312 radio and flash roms,or you can run an RUU to get back to the latest GB build. its up to you :)

Hi there thanks for all your info , so is this the suggested method over the 1st post ? or should i wait for you to post more details.


thank you
its up to you. if you have not allready unlocked thru htcdev,id prolly just use the first post directions and use taco root. it may be slightly less time consuming than htcdev unlocking.

the details i was going to add were simply making the first 3 steps more "noob friendly". you can certainly procede using htcdevs directions if you wish. ill try and work on it some more in the next few days :)
 
Upvote 0
While doing this step:

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

I got this. There is a FAILED (remote: not allowed).


C:\Users\Dad\Desktop\miniadb_inc2>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VE
RIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 50.840s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 90.106s
 
Upvote 0
You are in fastboot,correct? Not hboot?

A copy of your cmd window may prove helpful :)

In fastboot here is a copy of the command window

C:\Users\Dad\Desktop\miniadb_inc2>adb devices
List of devices attached
HT1BMMA07631 device


C:\Users\Dad\Desktop\miniadb_inc2>adb push misc_version /data/local/tmp/misc_ver
sion
1532 KB/s (367096 bytes in 0.234s)

C:\Users\Dad\Desktop\miniadb_inc2>adb shell
$ SU
SU
SU: permission denied
$ su
su
# chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/misc_version
# /data/local/tmp/misc_version -s 2.18.605.3
/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...
# exit
exit
$ exit
exit

C:\Users\Dad\Desktop\miniadb_inc2>adb reboot bootloader

C:\Users\Dad\Desktop\miniadb_inc2>fastboot devices
HT1BMMA07631 fastboot

C:\Users\Dad\Desktop\miniadb_inc2>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: -0.000s

C:\Users\Dad\Desktop\miniadb_inc2>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.437s

C:\Users\Dad\Desktop\miniadb_inc2>fastboot erase chashe
erasing 'chashe'... FAILED (remote: not allowed)
finished. total time: -0.000s

C:\Users\Dad\Desktop\miniadb_inc2>fastboot erase cache
erasing 'cache'... OKAY [ 0.187s]
finished. total time: 0.187s

C:\Users\Dad\Desktop\miniadb_inc2>fastboot oem rebootRUU
... OKAY [ 0.172s]
finished. total time: 0.172s

C:\Users\Dad\Desktop\miniadb_inc2>fastboot devices
HT1BMMA07631 fastboot

C:\Users\Dad\Desktop\miniadb_inc2>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.156s]
finished. total time: 0.156s

C:\Users\Dad\Desktop\miniadb_inc2>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VE
RIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 50.840s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 90.106s
 
  • Like
Reactions: scotty85
Upvote 0
OK thank you scotty i got my phone rooted of 1st post , everything went without error , with the exception of the reboot loop where I had to put in hboot and flash the radio , got that done and phone seems fine . YEA

Now what do i do next , like can i upgrade sw thru verizon to GB 2.3.4 and it will still be rooted ? do i need to install anything else while on 2.3.3

thank you so much for this guide ! :)
 
Upvote 0
Now what do i do next , like can i upgrade sw thru verizon to GB 2.3.4 and it will still be rooted ? do i need to install anything else while on 2.3.3

thank you so much for this guide ! :)

From this point on you don't want to install anything from Verizon. Look in the All Things Root sticky for a list of ROMs you can install. GingerBangSense is a good place to start. I'm running Ecliptic.
 
  • Like
Reactions: HpTouchMePad
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones