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

Root [how to]unlock,install recovery,and root with htcdev

scotty85

Extreme Android User
Jul 25, 2010
11,131
7,412
this is a device specific-thread to help you unlock,install a recovery,and root your HTC thunderbolt(mecha). this guide originated for the htc rezound, thus some of the names and references. however, all files and info are specially for the Thunderbolt.

first and foremost,htcdev is a PITA. it has limitations if you are a "hardcore" rom flasher/rooter/romer. while it may be fine for the folks that want to be completely stock and have root acces to delete some bloatware,and run root required apps,s-off is better,and worth the extra efforts to achieve,IMO.

for those of us that want complete freedom to mod our devices,htcdev is still a valuable,and a solid,reliable means of adding root acces for other exploits.

and now,on with the info!

the basic steps will be:
1)unlock with htcdev
2)temporarily or permanently flash a recovery
3)flash root files

before you start,go ahead and download these files:
-mini-adb.zip: mini-adb.zip
-Amon_RA 3.06 recovery for mecha: http://www.mediafire.com/?601tnkdzefq2e33
-superuser files: for GB or ICS,use the latest superSU from this thread on xda (the download link is where is says: CWM installable ZIP: CWM-SuperSU-v0.xx.zip )
-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.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.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 may want to rename it to "miniadb_mecha" since youll be putting some device specific files in here. (directions from here forward will assume this folder to be named "mini-adb_vigor",as an example)
-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 mini-adb_vigor directory. type the following at the prompt in your cmd window:

cd c:\mini-adb_vigor

your command promt should change to "c:mini-adb_vigor>" provided you: 1)unzipped the miniadb zip 2)put the folder on your c drive 3)entered the name of the folder correctly ("mini-adb_vigor" in this case)

-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 your device from the "select your device bar"(or "other supported devices" if its not listed) and click the green "begin unlock bootloader" button underneath.
-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

*check your hboot screen. if you allready have an htc compatible hboot, then skip ahead to the next step,you dont need this.if you have a pink **locked** at the top of the hboot screen,then it is compatible with htcdev. if you dont have a compatible hboot,then 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 hboot to the htcdev unlock compatible version.

-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 :p )
-save the unlock_code.bin that htc sends you directly to your mini-adb folder(if your PC automatically downloads somewhere else,no biggie. just move the unlock code to mini-adb folder)
-click the link in your email to get the rest of the unlock instructions
-step 12 is where them magic happens :D 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

as you can see,once the adb files are put in one place to download,its not hard to use,and the commands are pretty simple. below is what you will see in your command window,the red are my inputs.

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

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]


c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot oem get_identifier_token[/COLOR]
                              ... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO2ADC7C0C0F1BAF92074BAE9B0035CB6A
INFO021839BFA7465CD0788664688DCCFDEA
INFO33A2FD2C96C7308DD3C57A517DBA8E14
INFO8048F98A9FEA06B8F2AD05D4D3497CFE
INFO6FCCC1DC4E31E0C6F54CEA18D9A80C82
INFO27C33E209D472E6C11753E9D7BCBCE6D
INFO90D9F226E827B6C26165A029B6F7DFF2
INFO63E382B4C82F9F6D866C01B9823ED1BC
INFO0EEFA859327E6B5AC4C24533C9DFA7AF
INFODBD70D55E4666B4B41828B76FFBD010C
INFO1B916E350EFF199EA5B096FF3337FE19
INFO40E6CA9E7F1DD5B33D8D4780DD775289
INFO953404686AEC4C3CB6F1BBB9DC69BA13
INFO8738C00DAFF280ECF02D0C7A66E13855
INFO1D756616732FF47915EAD551A6933E08
INFO10C541C7RD02C14991E83CC49FCA4B92
INFO<<<<< Identifier Token End >>>>>
OKAY [  0.069s]
finished. total time: 0.070s

c:mini-adb_vigor>[COLOR="red"]fastboot flash unlocktoken Unlock_code.bin[/COLOR]
  sending 'unlocktoken' (0 KB)... OKAY [  0.143s]
         writing 'unlocktoken'... INFOunlock token check successfully
OKAY [  0.011s]
finished. total time: 0.156s

c:mini-adb_vigor>

2)flash a recovery
if you want to run stock,do not permanently install your recovery. keeping the stock recovery on the phone will ensure that you recieve OTAs without a hitch,wich i know is important to alot of users. YES,the OTA will break root. its no big deal. one good thing about htcdev is that you will always be able to reroot after,simply by following steps 2 and 3 again to launch recovery,flash superser.

once youve either skipped past all the setup,or have re-set up and are ready to root,chose either of the following options to either permantly or termporarily install a recovery:

1)temporary recovery:
-move the recovery image file you downloaded above and place it into the mini-adb folder.(note: this an .img file,not a .zip file. youll need to extract the recovery download to get the image inside)
-put the superuser zip file onto your phones sd card
-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 mini-adb directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

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

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)

-boot to bootloader:

adb reboot bootloader

-check for connectivity:

fastboot devices

-should return serial number
-temporarily launch your recovery to phone memory:

fastboot boot <recoveryname>.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

in your command window you will see(red are my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="Red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.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:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot boot recovery-ra-vigor-3.14-gnm.img[/COLOR]
        downloading 'boot.img'... OKAY [  1.518s]
                       booting... OKAY [  0.005s]
finished. total time: 1.523s
2)permanently install your recovery
-move the image file you downloaded above and place it into the mini-adb folder.
-put the superuser zip file onto your phones sd card
-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 mini-adb directory:

cd c:\mini-adb_vigor

-make sure youre connected by typing:

adb devices

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

md5sums <recoveryname>.img

**make sure the resulting md5 matches the one that is listed for the image that you downloaded. ** (if no md5 is listed,post in the thread,i can download and compare my md5 to yours.this is not as good as getting an md5 from the one who linked the file,but its better than nothing)

-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 <recoveryname>.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. amon ra is now permanently on your phone when you need it. be aware that you can no longer accept OTAs,unless you reinstall the stock recovery at some point before the next OTAs are pushed.
-to get to recovery,push the power button to select hboot. once in hboot wait for the green writing to flash and disapear,then select recovery.

*note that you can still launch recovery by using the command from scenario 1 above.
-youll then see the HTC splash screen,then your recovery.

and the code(again,red my inputs):
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:UsersScott>[COLOR="red"]cd c:\mini-adb_vigor[/COLOR]

c:mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx    device


c:mini-adb_vigor>[COLOR="red"]md5sums recovery-ra-vigor-3.14-gnm.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:mini-adb_vigor]
recovery-ra-vigor-3.14-gnm.img                 915d5e3cb662076f36f3d6e54759e951

c:mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]

c:mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx    fastboot

c:mini-adb_vigor>[COLOR="red"]fastboot flash recovery recovery-ra-vigor-3.14-gnm.img[/COLOR]
  sending 'recovery' (7074 KB)... OKAY [  1.659s]
            writing 'recovery'... OKAY [  5.179s]
finished. total time: 6.840s
3)flash superuser root files*
there is not much to explain with this one. if booted to recovery from above,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 :D

if youre considering leaving htcdev unlock,read the following post to learn some of the pitfalls.

s-off is better,and worth whatever extra efforts to achieve. see this thread to downgrade ICS to GB software build 2.11.605.5,so you can s-off via revolutionary: http://androidforums.com/thunderbolt-all-things-root/689221-how-downgrade-root-ics.html

*hope it helps,holler if you have questions :)

donate to my device fund :)
 
after typing this out more times than i can count,i have decided to make up a thread for it. hopefully this will end some of the confusion about fastboot booting recovery,why its better,and what you have to do if you opt not to take advantage of its benefits.

if you have not rooted yet, consider using the guide above,as ive tried to eliminate some of the confusion from htcdev's page,and using it will give you some basic knowledge and tools that you will use in happily modding your s-on device. youll also potentially have an understanding of fastboot booting your recovery into phone memory,as it is the same thing as what the guide instructions are for a "temporary recovery".


most folks that have come from other devices are used to the following sequence of events:
1)root phone
2)install a custom recovery(generally clockwork mod,or Amon_Ra)
3)booting to that recovery to make and restore backups,flash roms,etc. since the root method generally gave access to all the phones different memory partitions,many of wich are modifiable via the custom recovery.

even worse,are folks who have come from different devices and used an app called "rom manager" to manipulate things from within the booted operating system. i am not a fan of rom manager period,even on phones that it works on.

unfortunately,the above is a recipe for disaster on any s-on,high end htc device.

to begin,
a few words about htcdev
htcdev is htc's answer to the publics cry for unlocked bootloaders,and the ability to modify and install custom operating systems on their htc devices.

basically,you send information to htc,and they provide an unlock token that is reusable,but unique to your device. this changes the locked lettering at the top of your hboot screen to unlocked,and gives you access to the /boot,/system,and /recovery partitions only of your phone. it is not s-off by any means,and there are still alot of checks being done by the phone,wich lead to disadvantages. most notably,you cannot change any other partitions. hboot,radios,and splash screens are protected and off limits. you also cannot roll backwards in software build numbers and firmware if you flash a leaked rom and dont like it.

there are a couple of advantages.

1)unlike the underground exploits used in the past,htcdev will always work. you dont need to worry about unrooting and not being able to root again. if you need to relock your bootloader and flash factory firmware,you will always be able to re-unlock with your original unlock token.

this makes it convenient for users that only want root access so that they can run a few root apps(titanium backup,wifi tether) and delete some bloatware. the folks that like to run stock,and recieve OTA updates can easily do so by keeping the STOCK recovery on the phone.

as long as the stock recovery is in place,you are not in danger of an OTA messing up your phone.

MT4GS user: but,wait! wont accepting an OTA break my root?!
scotty: yes,but thats not a big deal. after the OTA has finished,you can quite easily relaunch your temporary recovery,and re-flash your root files,just as you did when you first rooted. re-rooting is easily accomplished,and therefore nothing to be concerned with.

2)the other big advantage of an htcdev unlocked s-on bootloader,is that since the bootloader is protecting itself,and the radios,it is nearly impossible to hard-brick(i.e.,unrecoverable) device with software flashes. any damaged to the phones filesystem are almost always fixed by RELOCKING the bootloader,and running an RUU(factory signed software package)

modding your s-on,unlocked device
first and foremost,remember this:

**an htcdev unlocked phone CANNOT write to the /boot partition FROM its /recovery partition.**


what this means is that,unlike your s-off evo 4g,thunderbolt,inc 1,or just about any other htc device you may have messed with,the rom that you flash from a recovery that is permantly installed on your phone cannot install the boot image. since the boot image houses the kernel, the roms kernel is not being installed along with the rest of the rom.

this means that if your rom requires a different kernel than what is on your phone,it will not boot. it will hang indefinately at the splash screen.

there are a couple options to work around this handicap with s-on phones:

1)use juopunut bear's tool to s-off your phone. :eek: doing this makes your phone and recovery act like you are used to(recovery can[/ write to /boot) but does not come without consequence. see this post for more info: *link coming soon

2)flash the kernel manually. it can be done with the command fastboot flash boot or it can be done by placing the boot image inside a PH98IMG file and flashing it in hboot.

PH98IMG flashing is a PITA on an s-on phone,in my honest opinion. the information on the "android info" text document inside the file must contain the correct info or the phone will not let the file flash. this leads to much aggravation,confusion,and an overall very bad rom flashing experience ;)

therefore,the better way to flash kernels,IF you want to do it manually,is to use the fastboot flash boot command. more info on that here: http://androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html#post3933400

and now the best for last:
3) fastboot boot your recovery into phone memory

this involves,basically,placing your recovery image inside the folder that contains adb and fastboot,booting the phone to fastboot,and the launching recovery into phone memory by entering the command:
fastboot boot recoveryname.img

do not confuse this with the fastboot flash command.

fastboot boot is taking an image,and booting it right up on the phone.

fastboot flash is permantly installing an image into the phones filesystem.

*if you use fastboot boot to launch your recovery into phone memory,then recovery CAN write to the boot partition,making rom flashing on your s-on device just like rom flashing on an s-off device.

i.e.,launching recovery from fastboot lets the rom install the kernel,and requires no seperate kernel flashing. this means that when you are following a rom developers install instructions,you can follow the set for s-off devices.

why does this work?!

well,an oversimplified explanation is this:
-fastboot is part of the bootloader,wich can write to the /boot partition
-launching recovery from bootloader,makes the recoverys operations work thru the bootloader.
-hence,launched recovery can write boot image. hooray! :smokingsomb:

all the above applies to bakcups as well. you canot restore a backup from the permenent recovery if it contains a different kernel. just like flashing a rom. all the above info in this post applies to restoring a rom as well.

last and not least,
some more detailed instructions

if you rooted with my guide,then you have seen this before. its basically the directions to "temporarily flash recovery"

for those that have rooted via other means,you can modify these directions to fit whatever folder you have adb/fastboot in,or you just use these directions:

download these files:
-mini-adb.zip: mini-adb.zip
-twrp for htc amaze(ruby) http://techerrata.com/file/twrp2/ruby/openrecovery-twrp-2.3.3.0-ruby.img

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 (i recomand revolutionary drivers)

1)prepair ADB
-unzip your mini-adb.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. rename it to "mini-adb_shooter" since youll be putting some 3vo(shooter) specific files in here. you actually can call it whatver you want,but directions from here forward will assume this folder to be named "mini-adb_shooter"
-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 mini-adb_vigor directory. type the following at the prompt in your cmd window:

cd c:\mini-adb_shooter


2)launch a temporary recovery:
-move the image file from your downloaded zip file, and place it into the mini-adb_shooter folder.

-type in your cmd window,or copy/paste the commands that are in bold

-check the md5 of your recovery image:

md5sums <recoveryname>.img

i.e.,if youre using an image named recovery-clockwork-5.0.2.7-doubleshot,then your command will be:
md5sums openrecovery-twrp-2.3.3.0-ruby.img

**make sure the resulting md5 matches any available listed md5 sums. **
(md5 openrecovery-twrp-2.3.3.0-ruby.img 7054c5123f094c191dd7af00873e8749)

-enable usb debugging on your phone and plug it in,charge only mode.

-check for connectivity:

adb devices

-it should reply with your serial number. if so,then:

adb reboot bootloader

-this will boot your phone into "fastboot" wich is a white screen with coloered letters.

-check for connectivity:

fastboot devices

-should return serial number

-temporarily launch your recovery to phone memory:

fastboot boot <recoveryname>.img

again,if youre using an image named as above:
fastboot boot recovery-clockwork-5.0.2.7-doubleshot.img

-youll see a (really fast) green status bar on the top right as your PC sends the recovery to your phone. youll then see the HTC splash screen,then your recovery.

now that youre recovery is running,you have lots of options. you can mount usb storage to move things on and off the sd card if you need to.

note that once recovery is running,you can unplug from the PC if you want to flash your rom from the couch,ktichen table,or wherever :)

you can now restore a backup,or flash a rom.

last and not least,a couple notes:
-to paste into the cmd window,you must right click/paste. you cannot control/v
-to copy from the cmd window,right click. click mark. highlight everything to copy in white. now hit enter,or right click again.

holler if you have more questions :)
 
  • Like
Reactions: landscapeman
Upvote 0
I managed to obtain root, however there were a few hiccups in the guide.

First, there was NO mention of the fact that I would lose ALL my personal data until the end of the HTCdev process. This was a very crappy situation to come to lol. Granted I should have backed up my stuff, but I have done roots on 4 other phones, as well as rooting my Thunderbolt pre-ics without losing any personal data prior to this so I wasn't expecting it.

The Amon Recovery you listed does not have an MD5 checksum with it and when I found another listing for the same file, the MD5 didn't match. I used the linked file anyways, but a solid listing for the MD5 file would be great so that things move more smoothly. The temporary PG05IMG file that it lists (PG05IMGrecovery-ra-mecha-3.06-gnm.zip), the one I downloaded had a MD5 of ccd64cadf2b98e8f446e79d5a5c3d1a8, and has worked for me.

Thanks for the guide, despite the hiccups I was able to obtain root and everything appears to be running smoothly.

Thanks again,

[MisterHighway]
 
  • Like
Reactions: scotty85
Upvote 0
I managed to obtain root, however there were a few hiccups in the guide.

First, there was NO mention of the fact that I would lose ALL my personal data until the end of the HTCdev process. This was a very crappy situation to come to lol. Granted I should have backed up my stuff, but I have done roots on 4 other phones, as well as rooting my Thunderbolt pre-ics without losing any personal data prior to this so I wasn't expecting it.

sorry about your data,i guess you missed this part of the guide:
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

The Amon Recovery you listed does not have an MD5 checksum with it and when I found another listing for the same file, the MD5 didn't match. I used the linked file anyways, but a solid listing for the MD5 file would be great so that things move more smoothly. The temporary PG05IMG file that it lists (PG05IMGrecovery-ra-mecha-3.06-gnm.zip), the one I downloaded had a MD5 of ccd64cadf2b98e8f446e79d5a5c3d1a8, and has worked for me.

Thanks for the guide, despite the hiccups I was able to obtain root and everything appears to be running smoothly.

Thanks again,

[MisterHighway]

sorry for the confusion on the md5s. the one i had on the pc,and the one i downloaded to check,have an md5 of:
PG05IMGrecovery-ra-mecha-3.06-gnm.zip b9a6ed032e5feb113e92979051b4b7ed

the differences can be simply a a different android info text document. if even one byte is off,it will throw out a whole new sum.

the important thing,is that the image inside,wich should be the same no matter that the md5 of the zip is,is:
recovery-ra-mecha-3.06-gnm.img ccd64cadf2b98e8f446e79d5a5c3d1a8

ill get the OP updated so there will be less confusion in the future :)
 
  • Like
Reactions: MisterHighway
Upvote 0
My phone is wanting to do an OTA update and I used this rooting process to root my phone. Can I use the other guides you've posted such as using the process listed as:

"Putting current stock firmware and s-on back onto the phone

after getting the bootloader back to the original s-off,engineering 1.04.2000 hboot download these 2 files:
1)PG05IMG_no_hboot_2.11.605.19
mirror: https://rapidshare.com/files/271867813/PG05IMG_no_hboot_2.11.605.19.zip
md5: 334909756073760b3d7316e51a4ce837
2)*link removed PG05IMG_hboot_ONLY_2.11.605.19.zip
mirror:PG05IMG_hboot_ONLY_2.11.605.19.zip
md5: d26b3253358407d459c654e6729a39ca

rename PG05IMG_no_hboot_2.11.605.19.zip to "PG05IMG",move to your sd card,and flash in hboot."

And flashing just the first file? Will that allow me to do my OTA update and then re-root my phone? I ask because this rooting process did not use S-Off as far as I know. I worry my phone will get stuck in the update loop and since I use it as my alarm clock as well as it being a literal lifeline for me at work, I cant afford for it to do that.

Thanks for your help!

[MisterHighway]
 
Upvote 0
If your phone is wanting to ota to ICS,then no,you cannot ota with the revolutionary hboot in place. Users have had issues since the ota is unable to replace the revolutionary hboot with the new 1.08.0000

Your best option is to flash an ICS rom in recovery,then update the radios thru hboot. This will get you to the same state as unrootng,ota,rerooting.

If you want to stay on GB, use tibu or equivalent to freeze or delete the "updater" file.

Hope that helps :)
 
  • Like
Reactions: MisterHighway
Upvote 0
After reading your other post agwin,if you are only htcdev unlocked,you will need to relock the bootloader,then run a full signed ruu. The ones in the sticky are for s off use only.

After the phone otas,you can re-unlock the new hboot and reroot using this same guide.

Sorry fr the short answers,I'm at work ATM :)

Hopefully that helped more than the prior post :)
 
  • Like
Reactions: MisterHighway
Upvote 0
I'm already in ICS, this OTA update just popped up last night. I used the above guide and rooted with HTCdev with ICS already in place. I personally use root for removing some minor bloatware as well as using my phone as a hotspot. Is it possible to do as I described and flash the stock, update my OTA stuff, and then root in the same fashion that I did?

Thanks for your rapid response.
 
Upvote 0
I typed my response while yours was coming through :) where might I find a signed RUU and can I re-lock my bootloader via the HTCdev site like I used to lock it?

Unfortunately,there is not one for ICS. For now,just freeze the updated file. You can wait fr the ota to be baked Into a rom,or well need to come up with a different solution.
 
  • Like
Reactions: MisterHighway
Upvote 0
Doing some good ol' Google research has pointed me to Titanium Backup Pro for a good app to freeze the updater. Any other suggestions or is that a good plan of action?

Do you have a nandroid that is unmolested? If so,boot recovery and restore it. If your stock recovery is in place,you can then allow the update.

If not,then freezing updater is a good plan fr now.

If you select recvery frm hboot,youll get a triangle and ! If its stock
 
  • Like
Reactions: MisterHighway
Upvote 0
Root/superuser, that is it besides using this guide and "disabling" some bloatware via applications setting. Originally I did this:

Wiped GB and reverted back to stock. Did OTA updates all the way to ICS. Rooted using your guide and HTCdev and installed the SuperUser software you provided. That's it for customization that requires root. Nothing else besides disabling bloatware which I can do without root as far as I know.
 
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