[HOW tO] unlock,downgrade,and achieve s-off with htcDev

[scotty1223]

disclaimer: this threads original home is here. im not in this forum much,so minimal support will be offered. in other words,help each other out. your welcome to jump over to the original thread and post if i dont answer specific questions within a couple days. i do honestly hope it will help some folks out over here,as well.

if your incredible has run out of factory warranty,and you cant get temp root any other way,then this could be for you,as no finicky root tools are used,just htc's own unlock.

first a couple words about htcdev:
-it does technically void "all or parts of your warranty." please be well aware of this.
-htcdev only unlocks boot,recovery and system. it is NOT a full unlock,or s-off,by any means.
-it does NOT allow the boot partition to be written from recovery. kernels must be flashed as PB31IMG files,or using the "fastboot flash" command. i.e.,flashing roms and restoring nandroids is much more of a PITA
-due to being s-on,you cannot change radios,hboots,or go backwards in firmware versions.

in short- s-off is way better. nuff said. on to the info.

this is a guide to unlock,root,downgrade,and s-off using htcdev

first,some credits:
-first and foremost,the good folks at htc for listening to customers and implementing their unlock program,even for older devices
*alpharev and unrevoked for all they for the root community
-iowabowtech for point me in the direction of this thread that i collected the misc image,and parts of the guide. also for his support answering questions.
-sele and the crew in the "rescue squad" on the thunderbolt forum for what i like to call the "mini-adb" concept.
-whomever origianlly came up with the images and guide linked above. if i can figure out who this was,ill add you in later.
-zamkat for testing the forever patch with the 1.02 htcdev hboot in this thread

the basic steps will be:
1)unlock with htcdev
2)flash recovery
3)flash superuser root files.
4)rewrite the misc image with adb and downgrade to froyo
5)re-unlock htcdev hboot
6)re-flash recovery
7)re-flash superuser root files and flash unrevoked's "forever" s-off patch



before you start,go ahead and download these files:
-miniadb_inc miniadb_inc.zip
md5: 7c5211686a20b558ccd660c782f82e2b
-PB31IMG for froyo: PB31IMG.zip
md5: 31bb1611a0fa8197d447c0438426717e
-superuser files: superuser 3.07 (found on revolutionary public wiki)
-forever patch unrevoked-forever from public:forever [RootWiki]
-go to HTCdev - Unlock Bootloader and register an account


1)unlock with htcdev
first thing you need is drivers for adb to see your phone. if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary

most guides simply say "follow the directions to unlock with htcdev" but im gonna go thru it with ya the mini-adb-inc.zip file is all the files that htcdev is telling you to download and put into a folder,so allready this should be a lil easier

1)prepair ADB
-unzip your mini-adb-inc.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C\ drive on your PC(sorry, you mac guys will need to develop this for yourself,i dont have a mac). root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you actually can call it whatver you want,but directions from here forward will assume this folder to be named "miniadb_inc"
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_inc directory. type the following at the prompt in your cmd window:

cd c:\miniadb_inc

your command promt should change to "c:\miniadb_inc>" provided you: 1)unzipped the miniadb_inc zip 2)put the folder on your c drive 3)didnt change the name

-now make sure usb debugging is checked in settings/apps/development,and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices

if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

2)unlock using htcdev
-go to HTCdev - Unlock Bootloader and sign in to your account. chose "htc droid incredible" from the "select your device bar" and click the green "begin unlock bootloader" button underneath. note the "*" wich means you will need to update your hboot in order to unlock.
-click yes to procede,then read the warnings before checking the boxes and clicking yes to continue,as they are basically explaining that your warranty is now void,and any repairs that your phone needs that may have been a result of unlocking your bootloader and messing with your phones operating system may no longer be covered under mfgr warranty
-download the RUU for the new hboot. right click it,and run as administrator. plug in your phone when prompted to. it will ugrade your .92 hboot to the htcdev unlock 1.02.0000 hboot.
-steps 1-4 are describing how to get your phone into bootloader mode and connect it to your PC,wich we have done above. ignore these steps and simply type in your cmd window:

adb reboot bootloader

it may take several seconds,but this command should boot your phone into the "fastboot" screen wich is white with a bunch of colored writing. once this happens,make sure your phone is still being seen in fastboot. type:

fastboot devices

again,this should return your phones serial number.

-click the green procede to step 5 bubble.
-steps 5-7 are telling you how to find the files and utilities inside your mini-adb folder. you have them,so ignore steps 5-7.
-click the green procede to step 8 bubble.
-heres where steps are important,steps 8-10 are telling you how to get your unlock token,and send it to htc. its phone specific(so they prolly know your serial number,meid,etc) so no,you cant use your buddys unlock token and not have htc know that youve unlocked your bootloader. copy this line either from below,or from step 8,and paste it into the prompt in your cmd window. you have to right click to paste in cmd,you cannot control/v :

fastboot oem get_identifier_token

-after yuo hit enter,you will get a bunch of letters that are your identifier token. not much i can say,other than follow the directions in steps 9 and 10 to copy and submit your identifier token to HTC. make sure you get the characters as shown in the pic,with no extra lines or letters. note that you can also hit the "enter" key on your PC to copy,as well as right clicking.
-click the green submit button. wait patiently for an email containing your unlock code. (dont worry,it should come pretty fast )
-save the unlock_code.bin that htc sends you directly to your miniadb_inc folder
folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to miniadb_inc)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where the magic happens copy from below,or from htc dev:

fastboot flash unlocktoken Unlock_code.bin

-youll see the purdy screen pictured in step 13. use the vol rocker to chose "yes unlock bootloader" and select it with the power button. your phone will reboot,performaing a factory data reset in the process. your data is gone,sorry this boot may take a bit longer than they normally do,dont freak out this is normal .

*special note: do NOT remove unlock_code.bin from miniadb_inc. we will use it again to reunlock in froyo

2)flash recovery
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your miniadb_inc directory:

cd c:\miniadb_inc

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums recovery-clockwork-5.0.2.0-inc.img

**make sure the resulting md5 matches: ea382ca5809cb872d0582aa22741d592


-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-permanently flash your recovery to phones recovery partition:

fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. you now have clockwork recovery installed on your phone.

fastboot reboot

-your phone will reboot

3)flash superuser root files*
there is not much to explain with this one.

*note that the menu options are navigated,and selected with the optic tracpad(NOT the power button)

1)place superuser 3.07 onto the root of your sd card.
2)enter recovery via the hboot menu(power off,power on while holding vol down. once in hboot,wait for green writing to flash,then select recovery with power button and vol rocker)
3)use the recovery menu on your phone to:
-make a backup of your stock,unrooted rom. completely optional,but a very good idea,IMO.
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-reboot

*congratulations,youre rooted at this point,you could enjoy root with htcdev. however,i strongly reccomend to continue with the downgrade. again,htcdev is a PITA,s-off is way better

4)rewrite the misc image with adb and downgrade to froyo
-make sure your phone is charged to 100% before starting.
-take the froyo PB31IMG,and place it into your miniadb_inc folder
-open a cmd window,as above

-make sure phone is plugged in and usb debugging checked on,in charge only mode

-at the promt in your command window:

cd c:\miniadb_inc this should change your command promt to "miniadb_inc",indicating youre using that directory.
adb devices this should output your phones serial number,indicating its recognized

md5sums mtd0.img it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839

md5sums flash_image again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a

md5sums PB31IMG.zip this is a big file,and will take a couple minutes to check,so be patient- its prolly not hung. it should output 31bb1611a0fa8197d447c0438426717e

*those numbers must match exactly. if they do then you can procede.


adb push flash_image /data/local/
adb push mtd0.img /sdcard/

adb shell your prompt should change to a #. if it changes to a $,then type su note your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.

cd /data/local
chmod 0755 /data/local/flash_image

cd /data/local
./flash_image misc /sdcard/mtd0.img

you can now downgrade back to 2.2,so you can flash the "unrevoked forever patch" in recovery to regain s-off

exit to get out of your adb shell,and back to the "mini-adb_inc" prompt

adb reboot bootloader this will boot your phone to "fastboot"

fastboot getvar mainver this will tell you if you have successfully re-written your misc image. if you see anything other than 1.22.605.2,then start over at step 4,and try again.

fastboot oem lock relocks your bootloader. you only need to enter the command and relock if your hboot is still unlocked when you get to this point. mine was allready relocked when i got to fastboot,so i did NOT need this step. again,if you are allready relocked then you can skip this command.i left the command in place just in case it works differently for others.

fastboot erase cache

fastboot oem rebootRUU this will put your phone in RUU mode

fastboot flash zip PB31IMG.zip this should flash your downgrade zip file

-when the phone finished flashing the downgrade:

fastboot reboot

*when your phone reboots,you should be in froyo

5)re-unlock htcdev hboot
-open a cmd window
-once again,enable usb debugging,plug in your phone

adb devices check conectivity

adb reboot bootloader boot to fastboot

fastboot devices check connectivity

fastboot flash unlocktoken Unlock_code.bin re-unlock

like the first time,on your phone select yes to unlock.your phone will reboot.

6)re-flash recovery
-enable usb debugging once again,as above. open a cmd window,if its not still open from unlocking.
-if you had to re-open a cmd window,dont forget to change back to your miniadb_inc directory:

cd c:\miniadb_inc

-make sure youre connected by typing:

adb devices

-should return serial number
-check the md5 of your recovery image:

md5sums recovery-clockwork-5.0.2.0-inc.img

**make sure the resulting md5 matches: ea382ca5809cb872d0582aa22741d592

-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-permanently flash your recovery to phones recovery partition:

fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone,then a (really,really fast) red bar as it flashes it. you now have clockwork recovery installed on your phone.

fastboot reboot

-your phone will reboot

7)re-flash superuser root files and flash unrevoked's "forever" patch*
there is not much to explain with this one,either.
1)place superuser 3.07(if its not still there from the first time),and unrevokeds "forever" patch onto the root of your sd card
2)enter recovery via the hboot menu(power off,power on while holding vol down. once in hboot,wait for green writing to flash,then select recovery with power button and vol rocker)
3)use the recovery menu on your phone to:
-wipe cache
-wipe dalvik cache
-install zip from sd card(chose your superuser file)
-install zip from sd card(chose your forever file)
-reboot

*congratulations,youre rooted. again. and hopefully now s-off as well. reboot,then go to hboot and verify that you are now S-OFF!


and heres what youll see in your cmd window. note that i did the whole process at one sitting,so i only had to change to the miniadb_inc directory once. red are my inputs,blue are additional comments:

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

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

c:\miniadb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT117HJ00242    device


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

c:\miniadb_inc>[COLOR="red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\miniadb_inc>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
                              ... INFO
INFO< Please cut following message >
INFO>
INFO65200481FCA29CD35BEC7DC337DCFA23
INFO71D74C4990C5E0CB5C6782517CFA050A
INFO99ABE5367E9EC9F5ACC1CE72B9A6A727
INFOA30412634D313494698CDFC7299A1F10
INFO8AB672DAB3DD89CA4CCFBB9201B4299F
INFO75043A2C4C5E311A30BF3DA18F103E73
INFOEEDA6977212E64D26B91A9C8D7895AFB
INFOD8AD398966EC1603F9AE177467FCE9CD
INFO4072F0702930148BC22923CBCF3C8925
INFO41B9FD1E6D913668186769E1ABBE877A
INFODD7DABBFB847F79F19665B0EDC6E7C67
INFO9E4426907F319A4E402E10625249A382
INFO325C48A94E2DFFB5F95734AA0BF32D9D
INFOADC2B232D8907982F2BC66DE75B73970
INFO6756674C42BE065E0A5B9FEF5C887E27
INFO5F6EFC9F42D1F543328893E3EC71C7B5
INFO>
OKAY [  0.065s]
finished. total time: 0.066s

[COLOR="blue"]*submit token to htc. move unlock_code.bin to miniadb_inc folder.[/COLOR]

c:\miniadb_inc>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.014s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.008s]
finished. total time: 0.022s

[COLOR="Blue"]*select yes to unlock on phone screen.phone will reboot,doing a factory data reset.[/COLOR]

c:\miniadb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT117HJ00242    device

c:\miniadb_inc>[COLOR="red"]md5sums recovery-clockwork-5.0.2.0-inc.img[/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_inc\]
recovery-clockwork-5.0.2.0-inc.img             ea382ca5809cb872d0582aa22741d592

c:\miniadb_inc>a[COLOR="red"]db reboot bootloader[/COLOR]

c:\miniadb_inc>[COLOR="red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\miniadb_inc>[COLOR="Red"]fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img[/COLOR]
  sending 'recovery' (3064 KB)... OKAY [  0.422s]
            writing 'recovery'... OKAY [  0.976s]
finished. total time: 1.399s

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

[COLOR="blue"]*phone reboots*[/COLOR]

c:\miniadb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT117HJ00242    device


c:\miniadb_inc>[COLOR="red"]md5sums mtd0.img[/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_inc\]
mtd0.img                                       34307be744275f1db1dd16af04c37839

c:\miniadb_inc>[COLOR="red"]md5sums flash_image[/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_inc\]
flash_image                                    0098a7dd6600b55fac34fc6645be5d7a

c:\miniadb_inc>[COLOR="red"]md5sums PB31IMG.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_inc\]
PB31IMG.zip                               100% 31bb1611a0fa8197d447c0438426717e

c:\miniadb_inc>[COLOR="red"]adb push flash_image /data/local/[/COLOR]
1428 KB/s (76044 bytes in 0.052s)

c:\miniadb_inc>[COLOR="red"]adb push mtd0.img /sdcard/[/COLOR]
1120 KB/s (655360 bytes in 0.571s)

c:\miniadb_inc>[COLOR="red"]adb shell[/COLOR]
$ [COLOR="red"]su[/COLOR]
su
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]chmod 0755 /data/local/flash_image[/COLOR]
chmod 0755 /data/local/flash_image
# [COLOR="red"]cd /data/local[/COLOR]
cd /data/local
# [COLOR="red"]./flash_image misc /sdcard/mtd0.img[/COLOR]
./flash_image misc /sdcard/mtd0.img
# [COLOR="red"]exit[/COLOR]
exit
$ [COLOR="red"]exit[/COLOR]
exit

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

c:\miniadb_inc>[COLOR="red"]fastboot getvar mainver[/COLOR]
mainver: 1.22.605.2 [COLOR="Blue"][COLOR="red"]fastboot erase cache[/COLOR]
               erasing 'cache'... OKAY [  0.753s]
finished. total time: 0.754s

c:\miniadb_inc>[COLOR="Red"]fastboot oem rebootRUU[/COLOR]
                              ... OKAY [  0.100s]
finished. total time: 0.100s

c:\miniadb_inc>[COLOR="red"]fastboot flash zip PB31IMG.zip[/COLOR]
     sending 'zip' (176625 KB)... OKAY [ 25.609s]
                 writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,9
INFO[RUU]UZ,radio,18
INFO[RUU]UZ,radio,23
INFO[RUU]UZ,radio,32
INFO[RUU]UZ,radio,41
INFO[RUU]UZ,radio,46
INFO[RUU]UZ,radio,51
INFO[RUU]UZ,radio,60
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,78
INFO[RUU]UZ,radio,87
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,7
INFO[RUU]WP,radio,16
INFO[RUU]WP,radio,21
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,35
INFO[RUU]WP,radio,40
INFO[RUU]WP,radio,45
INFO[RUU]WP,radio,50
INFO[RUU]WP,radio,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,43
INFO[RUU]UZ,boot,83
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,42
INFO[RUU]WP,boot,85
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,20
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,73
INFO[RUU]UZ,recovery,99
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,20
INFO[RUU]WP,recovery,40
INFO[RUU]WP,recovery,60
INFO[RUU]WP,recovery,80
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,6
INFO[RUU]UZ,system,12
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,32
INFO[RUU]UZ,system,39
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,51
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,64
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,78
INFO[RUU]UZ,system,84
INFO[RUU]UZ,system,89
INFO[RUU]WP,system,0
INFO[RUU]WP,system,89
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,90
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,92
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,97
INFO[RUU]UZ,system,98
INFO[RUU]UZ,system,99
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,89
INFO[RUU]WP,system,89
INFO[RUU]WP,system,90
INFO[RUU]WP,system,91
INFO[RUU]WP,system,92
INFO[RUU]WP,system,93
INFO[RUU]WP,system,94
INFO[RUU]WP,system,94
INFO[RUU]WP,system,95
INFO[RUU]WP,system,96
INFO[RUU]WP,system,97
INFO[RUU]WP,system,98
INFO[RUU]WP,system,99
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
OKAY [152.900s]
finished. total time: 178.510s

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

[COLOR="blue"]*phone reboots*[/COLOR]

c:\miniadb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT117HJ00242    device

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

c:\miniadb_inc>[COLOR="red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\miniadb_inc>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.014s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.005s]
finished. total time: 0.021s

[COLOR="Blue"]*select yes to unlock on phone screen.phone will reboot,doing a factory data reset.[/COLOR]

c:\miniadb_inc>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HT117HJ00242    device

c:\miniadb_inc>[COLOR="red"]md5sums recovery-clockwork-5.0.2.0-inc.img[/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_inc\]
recovery-clockwork-5.0.2.0-inc.img             ea382ca5809cb872d0582aa22741d592

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

c:\miniadb_inc>[COLOR="red"]fastboot devices[/COLOR]
HT117HJ00242    fastboot

c:\miniadb_inc>[COLOR="red"]fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img[/COLOR]
  sending 'recovery' (3064 KB)... OKAY [  0.423s]
            writing 'recovery'... OKAY [  0.915s]
finished. total time: 1.340s

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

[COLOR="blue"]*phone reboots*[/COLOR]

just so you know it does work

 

[SlimSnoopOS]

Appreciate the thread Scotty1223! Between this thread, Cmlusco's thread on bootloader unlocking also, and your thread on rooting GB 2.3.4, I'm sure this community will continue to help others.

 

[scotty1223]

btt,so folks can have a look at this thread again,as i have declared my other thread outdated. more and more folks seem to be having issues with unrevoked.

this method has proven itself to be reliable,and thus far,predictable.

 

[pcmedics911]

Scotty...Excellent instructions. This took an inc from s-on to s-off and from locked to unlocked.

Follow it to the letter and you will be grateful to have your labor pay off.

Thank you

 

[zachf714]

Could I brick doing this....If so how bad.. is it fixable

 

[cmlusco]

Could I brick doing this....If so how bad.. is it fixable

You can potentially brick your phone any time you flash anything, especially radios. There is no kind of bricked, your either bricked or your not. If truly bricked, you cant boot or access hboot or recovery. If thats the case, there is no fix and yore phone is a "brick".

 

[imtoomuch]

I gave in and installed HTC Sync. That helped me finally get the boot unlocker past the USB connection error. It started the unlock process then lost connection. It looks like the phone connects to the computer but it doesn't stay connected. Any ideas?

Sent from my Galaxy Nexus using Tapatalk 2

 

[zachf714]

You can potentially brick your phone any time you flash anything, especially radios. There is no kind of bricked, your either bricked or your not. If truly bricked, you cant boot or access hboot or recovery. If thats the case, there is no fix and yore phone is a "brick".

Thank You

 

[dunderhead]

Thank you for this, was incredibly helpful and well written. :laugh::good:

 

[spiffmandave]

Works perfect!

This was easy to use and worked like a charm! Thank you scotty1223!

 

[Masoono]

worked

This is kickass, finally got my friend's incredible s-offed.
Thanks!

 

[us27inks]

Yes, I am a complete noob, and this is my first post at xda. I hope my question isn't merely the result of not knowing how to properly use the search function.

I got a replacement for my waterlogged Dinc today, and attempted to root it. No luck until I found this thread. Everything went well until I went to install SU root files. The phone consistently hangs when I select any function in the recovery menu. I went back to adb to see if I needed to reinstall clockwork, but now when I type "adb devices" or "fastboot devices" it returns no devices.

Anyone know a workaround for this?

 

[cmlusco]

Yes, I am a complete noob, and this is my first post at xda. I hope my question isn't merely the result of not knowing how to properly use the search function.

I got a replacement for my waterlogged Dinc today, and attempted to root it. No luck until I found this thread. Everything went well until I went to install SU root files. The phone consistently hangs when I select any function in the recovery menu. I went back to adb to see if I needed to reinstall clockwork, but now when I type "adb devices" or "fastboot devices" it returns no devices.

Anyone know a workaround for this?

You say it hangs, are you using the track ball to select items in recovery?

Do you have usb debugging on? Try restarting the phone and pc.

 

[us27inks]

You say it hangs, are you using the track ball to select items in recovery?

Do you have usb debugging on? Try restarting the phone and pc.

I'm not using the track ball, just the volume and power buttons. USB debugging is on, and the phone and pc have been restarted multiple times. The battery must be removed to get into the recovery menu, but that should be normal (I think).

I selected reboot from the recovery menu and left it for an hour or so. It has made it past the clockwork logo and is now at the "eyeball". Perhaps if I leave it long enough I can get SU installed. Something is not playing nice though.

*** UPDATE *** Just because you asked if I was using the track ball, I tried it with the track ball instead of the buttons. Seems to be working. We'll see in a minute.

 

[cmlusco]

I'm not using the track ball, just the volume and power buttons. USB debugging is on, and the phone and pc have been restarted multiple times. The battery must be removed to get into the recovery menu, but that should be normal (I think).

I selected reboot from the recovery menu and left it for an hour or so. It has made it past the clockwork logo and is now at the "eyeball". Perhaps if I leave it long enough I can get SU installed. Something is not playing nice though.

*** UPDATE *** Just because you asked if I was using the track ball, I tried it with the track ball instead of the buttons. Seems to be working. We'll see in a minute.

You press the trackball to select items, vol up and down to navigate, and the power button to go back.

 

[us27inks]

You press the trackball to select items, vol up and down to navigate, and the power button to go back.

It's working. Thank you very much. I would have figured out what I was doing wrong if it had gone back instead of hanging at the clockwork logo.

Anyway, got my old rom installed, and I'm restoring all my apps. I'm just really glad I did a full backup the day before it got wet.:good:

 

[zachf714]

Can I do the process while on a custom ROM and do I have to reactivate the phone after the process

Sent from my ADR6300 using xda app-developers app

 

[cmlusco]

Can I do the process while on a custom ROM and do I have to reactivate the phone after the process

Sent from my ADR6300 using xda app-developers app

Well the process requires you to do a couple ruu's that will make you stock. It dosent matter if you start the process while on a custom rom.

I cant remember if you have to reactivate, but im pretty sure the only time you have to reactivate is if you do a factory reset from hboot, which this proccess does not do. But i could be wrong, so dont take it as a for sure thing.

 

[zachf714]

Well the process requires you to do a couple ruu's that will make you stock. It dosent matter if you start the process while on a custom rom.

I cant remember if you have to reactivate, but im pretty sure the only time you have to reactivate is if you do a factory reset from hboot, which this proccess does not do. But i could be wrong, so dont take it as a for sure thing.

OK thank you

Sent from my ADR6300 using xda app-developers app

 

[kirkers]

Biggest risks for me came AFTER success

I totally relied on Scotty's guide, and it delivered everything it promised. Nevertheless, I found my way into some very heavy going shortly thereafter.

Perhaps the story of my "near-Droid-death" experience will help others be safer. I still am not absolutely sure I know what happened. I am definitely happy to still have a properly rooted Droid Incredible (DINC) and at least have a chance of making some further mods, if I can work up the courage to risk it.

Why am I sounding like the cowardly lion from the Wizard of Oz? Keep reading and you may get a better idea...

It all started in the middle of the successful downgrade & re-upgrade process Scotty provides in his guide. The one thing that was disappointing about my DINC was WiFi reception. I had expected a significant positive bump up from my venerable MOTO DROID (the original), but that had not happened. If anything, the DINC was a bit behind the DROID in performance. This seemed odd, given how much users raved about the DINC’s many fine features. I did not recall reading a single criticism of WiFi, or anything else for that matter – except somewhat disappointing battery life. (My solution to that is easy: get some cheap batteries and a stand-alone charger on eBay or wherever, and keep those little wafers charged up and handy on your person!)

Then, suddenly , everything changed for the better after the downgrade to Android 2.2 Froyo happened. WiFi connectivity became very easy, and dropouts virtually disappeared even with only fair signal strength (-75 to -80 dB). I was thrilled of course, and gave all the credit to the rooting process. I fully expected to retain the WiFi up-tick when I reached our final destination of a rooted stock Gingerbread (GB) 2.3.4. Only …. It didn’t work out that way. Instead, the DINC’s WiFi sank back down to pre-root levels. Something about the two flavours of Android seemed to be causing this. It deserved extended investigation.

What I found out here at XDA and elsewhere is that GB implemented a tougher minimum value for the Received Signal Strength Indicator (RSSI) . The intention seemed to be to offer users a good WiFi experience whenever they actually managed to connect without many annoying dropouts. In practice, this made connectivity much more difficult and at times impossible, even in situations where connectivity should have been reasonably good and definitely easy to access – like on a home network, for example. I could stand right next to the router or access point, and the DINC with GB simply would not lock on to the signal. During the Froyo downgrade, the exact same hardware in precisely the same wireless environment experienced no such problems.

What I concluded from this was that Froyo was where I belonged – at least until something just as good in the WiFi department showed up amongst the custom ROMs, radios and/or kernels. So I set my sights on installing the Froyo ROM Scotty had us all use in his guide.

Only in hindsight do I realize that this ROM was not rooted, because Scotty had us re-unlock and re-root once it was installed. Noob (or simply boob!) that I was, I missed this key bit. So on I went, wiping off everything except my sdcard and internal storage, renaming the Froyo ROM to the default “PB31IMG.zip” so that HBOOT would automatically try to install it, and rebooting into HBOOT.

HBOOT gave me all sorts of warnings (“wrong image”… “not an image”), but I had read on another site (not XDA, mind you) that this sort of thing could happen, and that if HBOOT went ahead and parsed the file and offered to install it, it was okay to go ahead. So, I charged ahead…

What I ended up with was Froyo without root. Titanium Backup and ROM Manager confirmed that quickly enough, since they were the first two apps I installed from the Market/Play Store. Booting into the ClockWorkMod (CWM) recovery produced a red triangle and exclamation point on-screen, and a frozen device that could only be thawed with a battery pull. All the commands worth trying from a PC using ADB over a USB cable to the DINC were rejected. Now I was no longer authorized. Even the procedure to re-run device unlock via ADB OEM produced fatal errors.

I thought my brief time rooting the DINC was over, and that I would have to get used to a phone without proper Titanium backups and other amenities – assuming nothing further went wrong and the DINC would never need me to use CWM recovery for anything.. Just as I was about to give up my not-so-flash flashing career, along came the perfect website to save me. Sorry, it was not XDA – at least not this time! It was the EVOrootWiki in Europe. Lucky for me I was stuck in Froyo, because the “Incredible Froyo Downgrade Kit” and instructions I downloaded completely rescued me and my DINC. At the end of the day, I was rooted into GB 2.3.4, and this time WiFi remained at the high level found in Froyo. Why this is so remains a mystery to me, but the ROM was definitely up to date in most ways with regard to radio, kernel, HBOOT (the engineering version) and such -- although it was basically all stock HDC/Verizon. Something about it set it apart from what I had used for such a brief time after finishing Scotty’s guide.

So the lesson of this fable is that dangers continue to lie in wait for unsuspecting noobs who possess that most dangerous commodity: a little bit of knowledge. Now, if my analysis is in any way incorrect, incomplete, or otherwise misguided, I do hope Scotty or other XDA seniors will step in on this thread and explain the dos and don’ts of what is at bottom a tricky and less than stable situation.

If you have made it this far, thanks for reading through a long post! :good:

Cheers all!