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

[scotty1223]

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.

just a couple of things- the "warnings" you saw were normal hboot activity. when you enter hboot,it will always check the sd card for the various files that you see in the green writing. this is nothing to worry about,the phone is not missing any files,and they are not errors or warnings.

the red ! and triangle are simply the stock recovery. as you have discovered,running a full signed ruu will overwrite all partitions that it contains. the stock recovery is accessed by holding vol up and power until you see a menu,at wich point you could have rebooted without the battery pull.

you could not unlock via htcdev at this point in your adventure,as running the froyo ruu as s-off overwrote the 1.02 htcdev compatible hboot with the older .92 version. not a big deal,as with s-off there are many ways you could have skinned the cat,such as installing a recovery as a PB31IMG file,then flashing a rom,or slashing root files. you could also have re-run the GB ruu,and done the same. s-off will always remain,and you can always install recovery as a PB31IMG. you defaintely were not "stuck" in froyo!

as far as your adb commands,you may have not enabled usb debugging,you may have needed a simple unplug and replug,or you may have been in fastboot,where adb will not work. adb is only for use in the booted android operating system.

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.

i assume the directions you found were these(wich i found with a search for EVOrootWiki): http://noobgui.de/wiki/index.php?title=Incredible_Froyo_Downgrade

i assume since you were on froyo,you simply ran the custom ruu. the difference between that and what you had backed up,are that it is an older version: 4.06.605.3. the newest is 4.08.605.15. maybe there is a difference somewhere between those 2 versions that is helping your wifi connectivity. it is also containing its matching radio,not the newest(newest is 2.15.10.12.20).

the hboot it contains is pretty slick- it is basically the 1.02 hboot,patched to think it is unlocked,without having to actually unlock via htcdev. defaintely neat if you had never unlocked via htcdev and needed the fastboot boot and fastboot flash commands,but since you have an unlock token,i dont know if youre getting ay advantage to running that over the 1.07. the hboot only boots the OS,it has nothing to do with your wifi connectivity issue.

i dont really maintain this guide like i do the original. there are links to the 1.07 hboot and the 2.15.10.12.20 baseband in the OP of the guide on AF if anyone wants to upgrade to them. ill try and update the OP here to match it in the next ocupld days.

glad you got everything sorted... holler if you have any other questions about your adventure

 

[TKHouse]

I know it's been said a few times, but thanks so much for this.

Worked like a charm on my DINC

 

[kirkers]

Hey, Scotty, what a response! You ALMOST are speaking in a different language from mine, but I am doing my best to translate... :laugh:

So, I will break up your reply into parts and see if I can respond with something that makes sense to me (and you too, I hope -- at least that is the goal! :fingers-crossed:

just a couple of things- the "warnings" you saw were normal hboot activity. when you enter hboot, it will always check the sd card for the various files that you see in the green writing. this is nothing to worry about, the phone is not missing any files, and they are not errors or warnings.

I get that CWM Recovery checks for pre-cooked zip install files (PB31IMG.zip in the case of the HTC Droid Incredible, aka DINC). Usually the text flies by so fast I cannot even read what it says. The difference here was that I deliberately renamed to PB31IMG.zip the Froyo ROM you use for downgrading in your DINC rooting guide. Not only could I read the writing on the wall, so to speak, but they were clearly warnings about "wrong image" and "no image". Recovery then proceeded to load the file and asked me politely if I wanted to install to boot, system, etc. Since I had carefully wiped all those directories prior to trying this install, I figured my only answer could be “yes.” Only in hindsight did that not look like a good idea, but you have lots more to say about that further on, and I will get there. Just let me plod along slowly at this point...

the red ! and triangle are simply the stock recovery. as you have discovered, running a full signed ruu will overwrite all partitions that it contains. the stock recovery is accessed by holding vol up and power until you see a menu, at which point you could have rebooted without the battery pull.

So what you are saying is, this was fine. The problem did not arise at this stage. It is standard procedure to do what I did to force recovery to install any ROM, Radio, kernel, or bootloader (HBOOT) that I want. Please confirm or correct me!

This is the VERY FIRST I have read anywhere about a “stock recovery” and the use of the volume-UP rocker key. I tried to do this just now with my rooted CWM Recovery installed, thinking that maybe the stock recovery was still lurking somewhere in the DINC. All I got was three quick vibrations. Then when I tried the usual volume-DOWN key, the normal S-OFF HBOOT popped up. So does that mean when I was in unrooted Froyo, tried to boot into CWM Recovery with the DOWN-volume+power keys and got the red triangle, I could I have rebooted, accessed the stock recovery with the UP-volume+power keys, and it would have installed any PB31IMG.zip file it found, because of security being S-OFF? Could I instead have chosen to restore the nandroid backup to get me back to where I was before I flashed the Froyo RUU? Or would it have simply allowed me to start the DINC normally, without my being able to alter anything?

You could not unlock via htcdev at this point in your adventure, as running the froyo ruu as s-off overwrote the 1.02 htcdev compatible hboot with the older .92 version. not a big deal, as with s-off there are many ways you could have skinned the cat, such as installing a recovery as a PB31IMG file, then flashing a rom, or slashing root files. you could also have re-run the GB ruu, and done the same. s-off will always remain, and you can always install recovery as a PB31IMG. you definitely were not "stuck" in froyo!

Well, that’s good hearing Scotty! I only THOUGHT I was under the kosh, as opposed to being REALLY stuck. :silly: The key difference was that the Froyo ROM from your guide was a full ROM Update Utility (RUU) file, complete with ROM, radio, kernel and HBOOT bootloader. When I ran what I thought was “just a ROM” it actually replaced everything. Since security was S-OFF, everything came charging through the gates, so to speak. Right?

The downgrading of HBOOT back to 0.92 was what stopped me from locking or unlocking using the “adb oem” commands, in conjunction with the unlock code BIN file HTC sent me? That accounts for all the ERROR responses I received?

Did HBOOT 0.92 also stop me from reflashing CWM recovery 5.0.2.0 effectively? I renamed it PB31IMG.zip, and got it back just once before the red triangle scenario reasserted itself and flashing with ADB produced nothing but ERROR statements. (I now know the red triangle is the stock recovery, requiring the UP volume + power keys to boot properly)

Since nearly all my ADB and fastboot commands were met with ERROR statements, is this because I was back in HBOOT 0.92 with a stock recovery that is unresponsive to ADB and fastboot, other than to report the device serial #? If that is not the case, then I still can’t see why I got all those ERROR statements. I can’t reproduce the scenario right now, and I’m not sure I even want to try! But I’m eager to read and learn from you …

Going back for a moment to HBOOT’s polite inquiry near the beginning of my walkabout, could I have said “yes” to some of the items listed and “no” to others? If so, what should I have done at that point to prevent overwriting of HBOOT and CWM Recovery?

And lastly, what is “slashing root files” all about? It sounds positively bloody!

as far as your adb commands, you may have not enabled usb debugging, you may have needed a simple unplug and replug, or you may have been in fastboot, where adb will not work. adb is only for use in the booted android operating system.

Now I’m worried again, Scotty! I am just competent enough to be certain that USB debugging was turned on. Also, I tried this several times at different moments of the day, so the USB cable was therefore definitely unplugged and replugged into the PC and DINC. I also am aware of the difference between fastboot and ADB. I always use the “devices” argument to check to see if the DINC’s serial# appears, which proves I am in the right programme. I am pretty confident about these parts, although feel free to say a quiet word at this point to set me straight.

i assume the directions you found were these(which i found with a search for EVOrootWiki): http://noobgui.de/wiki/index.php?title=Incredible_Froyo_Downgrade

Correct!

i assume since you were on froyo, you simply ran the custom ruu. the difference between that and what you had backed up, are that it is an older version: 4.06.605.3. the newest is 4.08.605.15. maybe there is a difference somewhere between those 2 versions that is helping your wifi connectivity. it is also containing its matching radio, not the newest(newest is 2.15.10.12.20).

Again, correct. I have the older ROM build 4.06.605.3 with the older radio running right now on the DINC. It makes sense that the radio is matched to this build, and it is very true that my WiFi connectivity and reception are excellent, at least based on my past experience with a MOTO DROID A855 for the past 6 months in the exact same locations.

the hboot it contains is pretty slick- it is basically the 1.02 hboot, patched to think it is unlocked,without having to actually unlock via htcdev. definitely neat if you had never unlocked via htcdev and needed the fastboot boot and fastboot flash commands, but since you have an unlock token, i don’t know if you’re getting any advantage to running that over the 1.07. the hboot only boots the OS, it has nothing to do with your wifi connectivity issue.

Are there any REAL advantages to my having the latest radio and HBOOT? Should I bother to try to flash them? Can I do this without losing my programmes, contacts, SMS, calendar, gmail account settings, etc and having to set them all back up using Titanium Backup (plus some old-fashioned elbow grease for the settings)?

Once I get things the way I like them, should I run “unrevoked S-ON” to keep HBOOT from being overwritten? What effect does “S-ON” have on flashing new RUUs (all-in-one packages), ROMs, radios, kernels, recoveries, and/or bootloaders?

I am still uncertain about how to proceed with installing any sort of custom ROM. I know enough to make a nandroid backup using CWM recovery. (I normally use ROM Manager from within the DINC as a friendlier front-end, but I know my way around CWM direct thanks to your guide.) I am still unclear if the backup is like a cloned disk image would be in the PC world, or if it just preserves certain things but not others.

If a nandroid is a clone, then I would say I must reinstall apps and settings for each custom ROM I install.

If a nandroid is just apps and settings, then I should restore it AFTER installing an RUU or a ROM.

Which one is true?

there are links to the 1.07 hboot and the 2.15.10.12.20 baseband in the OP of the guide on AF if anyone wants to upgrade to them. I’ll try and update the OP here to match it in the next couple days.

What about installing these sorts of things -- radios, kernels, recoveries and HBOOT bootloaders? Can some or all of these be swapped in and out without disturbing the ROM, apps and settings?

I don’t QUITE have a firm grip on this yet, but with a little more instruction from you, Scotty, I’m confident that I’m just one or two steps away! (BTW, does “OP” stand for original post, and “AF” stand for Android Forums?)

glad you got everything sorted... holler if you have any other questions about your adventure

Would it be easier for you if I cross-posted somewhere else? (I am a member of Android Forums as well – in fact, I first got hold of your guide on that site.)

Cheers!

 

[scotty1223]

Hey, Scotty, what a response! You ALMOST are speaking in a different language from mine, but I am doing my best to translate... :laugh:

So, I will break up your reply into parts and see if I can respond with something that makes sense to me (and you too, I hope -- at least that is the goal! :fingers-crossed:



I get that CWM Recovery checks for pre-cooked zip install files (PB31IMG.zip in the case of the HTC Droid Incredible, aka DINC). Usually the text flies by so fast I cannot even read what it says. The difference here was that I deliberately renamed to PB31IMG.zip the Froyo ROM you use for downgrading in your DINC rooting guide. Not only could I read the writing on the wall, so to speak, but they were clearly warnings about "wrong image" and "no image". Recovery then proceeded to load the file and asked me politely if I wanted to install to boot, system, etc. Since I had carefully wiped all those directories prior to trying this install, I figured my only answer could be “yes.” Only in hindsight did that not look like a good idea, but you have lots more to say about that further on, and I will get there. Just let me plod along slowly at this point...
this mode is not clockwork recovery,it is hboot. again,it isNOT a warning,it is checking your sd card for those files(PB31IMG,PB31DIAG,etc.) the "no image or wrong image" is simply stating that that particular file is not on the sd card. hboot will perform the check for those file every time you boot to it. in your particular situation it simply stopped when it found one of the files it looks for. it doe not mean files are missing,and it is perfectly normal behavior.


So what you are saying is, this was fine. The problem did not arise at this stage. It is standard procedure to do what I did to force recovery to install any ROM, Radio, kernel, or bootloader (HBOOT) that I want. Please confirm or correct me!
correct

This is the VERY FIRST I have read anywhere about a “stock recovery” and the use of the volume-UP rocker key. I tried to do this just now with my rooted CWM Recovery installed, thinking that maybe the stock recovery was still lurking somewhere in the DINC. All I got was three quick vibrations. Then when I tried the usual volume-DOWN key, the normal S-OFF HBOOT popped up. So does that mean when I was in unrooted Froyo, tried to boot into CWM Recovery with the DOWN-volume+power keys and got the red triangle, I could I have rebooted, accessed the stock recovery with the UP-volume+power keys, and it would have installed any PB31IMG.zip file it found, because of security being S-OFF? Could I instead have chosen to restore the nandroid backup to get me back to where I was before I flashed the Froyo RUU? Or would it have simply allowed me to start the DINC normally, without my being able to alter anything?
you are misunderstanding slightly. the stock recovery is now gone,as you have clockwork installed. holding bol up and pwoer from powered off pute the phone in some sort of qualcom diagnostic mode. what i meant was that when you booted to the screen with the red ! and triangle,you did not have to pull the battery. you coul have,at that point, held vol up and power,and you would have gotten a menu.

even with s-off,the stock recovery will not install roms or PB31IMG files. it will only install htcs specially prepared OTA files. the only thing it was good for,was a less abrasive way of getting the phone to reboot



Well, that’s good hearing Scotty! I only THOUGHT I was under the kosh, as opposed to being REALLY stuck. :silly: The key difference was that the Froyo ROM from your guide was a full ROM Update Utility (RUU) file, complete with ROM, radio, kernel and HBOOT bootloader. When I ran what I thought was “just a ROM” it actually replaced everything. Since security was S-OFF, everything came charging through the gates, so to speak. Right?
correct. since security was off,you could install older software/firmware,and the full ruu replaced all partitions.

The downgrading of HBOOT back to 0.92 was what stopped me from locking or unlocking using the “adb oem” commands, in conjunction with the unlock code BIN file HTC sent me? That accounts for all the ERROR responses I received?
no,and yes. the .92 hboot had nothing to do with the adb commands. adb will work fine in froyo if usb debug was enabled. i know youre sure you had it on,but if you had tried unlpug/replug,different ports,etc. its likely you left it off. unfortunately we cannot trouble shoot that now. just rest assured it was a fixable situation,nad nothing to do with root,the downgrade,or the .92 hboot.

what the .92 hboot DID prevent was youre being able to fastboot flash unlocktoken Unlock_code.bin to re-unlock,as the .92 hboot is not htcdev compatible. on any hboot,you can "fastboot oem ?" with the phone in fastboot,and it will list all the available oem commnads. with .92,youll see the unlock command and get ideitifier token commads are not present.

again,not that it mattered much. you can install recovery as a PB31IMG,so you can live without the fastboot flash and fastboot boot that the unlocked hboot provides.

Did HBOOT 0.92 also stop me from reflashing CWM recovery 5.0.2.0 effectively? I renamed it PB31IMG.zip, and got it back just once before the red triangle scenario reasserted itself and flashing with ADB produced nothing but ERROR statements. (I now know the red triangle is the stock recovery, requiring the UP volume + power keys to boot properly)
you cannot install recovery with adb. you need to use fastboot or hboot to install recovery.(well,techenically thats not true,but the way we are discussing currently,it is true)

.92 will let you install clockwork as a PB31IMG when you are s-off. it will NOT let you fastboot flash recovery recoveryname.img

Since nearly all my ADB and fastboot commands were met with ERROR statements, is this because I was back in HBOOT 0.92 with a stock recovery that is unresponsive to ADB and fastboot, other than to report the device serial #? If that is not the case, then I still can’t see why I got all those ERROR statements. I can’t reproduce the scenario right now, and I’m not sure I even want to try! But I’m eager to read and learn from you …
really,you would need to list the particular errors in order for me to explain them. i still get the impression you are confused when you are using adb,and when you are using fastboot.
-.92 will let you install PB31IMG
-.92 will NOT let you use fastboot flash or fastboot boot
-.92 is not part of the equation when using adb,within the booted OS. after the OS is loaded,the bootloader is not used. some commands may fail if one does not have root access,however. but thats still nothing to do with s-on or s-off,or the hboot version.

Going back for a moment to HBOOT’s polite inquiry near the beginning of my walkabout, could I have said “yes” to some of the items listed and “no” to others? If so, what should I have done at that point to prevent overwriting of HBOOT and CWM Recovery?
no. you cannot answer anything,they are not questions,they are statements. hboot is telling you that it did not find PB31DIAG,etc. when it did find one of the files(PB31IMG.zip) it stopped,loaded the file did no security checks since it was s-off,then asked you if youd like to update.

the only way to prevent the overwrite of hboot and CW would be to select no for the entire update.

And lastly, what is “slashing root files” all about? It sounds positively bloody!
umm,that was a typo. should have been "flashing"

Are there any REAL advantages to my having the latest radio and HBOOT? Should I bother to try to flash them? Can I do this without losing my programmes, contacts, SMS, calendar, gmail account settings, etc and having to set them all back up using Titanium Backup (plus some old-fashioned elbow grease for the settings)?
i for one always like to run the newest firmware. even if the differences are not percieveable,i feel that if improvements had not been made,there would not be new versions. that decision is a personal one for you. you can stay where youre at if your happy with your current performance.

yes,you can change firmware or recovery in hboot,and it will not affect any settings or data in your rom.

Once I get things the way I like them, should I run “unrevoked S-ON” to keep HBOOT from being overwritten? What effect does “S-ON” have on flashing new RUUs (all-in-one packages), ROMs, radios, kernels, recoveries, and/or bootloaders?
i would NOT do that. IMO it would be unwise. s-on will not prevent hboot from being overwritten, it will just re introduce all the security checks that hboot does,wich is not to your advantage.

only reason to ever s-on,would be tu turn the phone in to vzw for a warranty excahange.

I am still uncertain about how to proceed with installing any sort of custom ROM. I know enough to make a nandroid backup using CWM recovery. (I normally use ROM Manager from within the DINC as a friendlier front-end, but I know my way around CWM direct thanks to your guide.) I am still unclear if the backup is like a cloned disk image would be in the PC world, or if it just preserves certain things but not others.
a nandroid is an exact image of your phone when you make it.

If a nandroid is a clone, then I would say I must reinstall apps and settings for each custom ROM I install. <- true

If a nandroid is just apps and settings, then I should restore it AFTER installing an RUU or a ROM.

Which one is true?
top one is true. thats about all ill have to say about it,as there is TONS of info on various forums about rom flashing,backing up and restoring. how to flash roms is a bit out of the scope of this guide and thread.


What about installing these sorts of things -- radios, kernels, recoveries and HBOOT bootloaders? Can some or all of these be swapped in and out without disturbing the ROM, apps and settings?
yes

I don’t QUITE have a firm grip on this yet, but with a little more instruction from you, Scotty, I’m confident that I’m just one or two steps away! (BTW, does “OP” stand for original post, and “AF” stand for Android Forums?)
you got it



Would it be easier for you if I cross-posted somewhere else? (I am a member of Android Forums as well – in fact, I first got hold of your guide on that site.)
im active in several forums on AF,and have somewat limited computer time with work and daily life. your questions will liely get answered a lil quicker over there. i get email notifications to replys to this topic,xda is one of the last stops i make,if i dont run out of time
Cheers!

hope that helps. i did try and update the OP here to match the one on AF,but got an error message it was too long so i guess the guide here will stay as is.

 

[tlipur]

this is freaking money it worked. took me a while since i had jellybean on here already, it wouldn't worked, installed another rom and bingo was able to follow guide to a t

Thanks!!!!!!!!!!!!

 

[scotty1223]

this is freaking money it worked. took me a while since i had jellybean on here already, it wouldn't worked, installed another rom and bingo was able to follow guide to a t

Thanks!!!!!!!!!!!!

awsome! glad it was helpful

 

[kirkers]

Thanks Scotty! I was away doing some other things for awhile, but upon returning to read your long detailed reply, I now believe I am much better prepared to tackle further modding. You are indeed the chief tutor on my "ROMan Education". Thanks for all your efforts, and I will have a look in at the Android Forums (AF) for your updated Original Post (OP) guide.

Cheers!

 

[funkpod]

hey, anyone develop a Mac version yet? just got a "new" Incredible and I'd like to try this. i have a Galaxy s3, but I want to use this to play around with, etc.

 

[Astrokid248]

scotty1223, you just gave my phone a brand new life. I couldn't root it at all after trying four or five different methods. It turns out my issues were from installing ClockworkRecovery. Your instructions work perfectly, and it never occurred to me to use the adb to push the installation through. The best part about this guide is that I actually understand just what I did as I went through the steps. Massive kudos.

 

[funkpod]

So... i'm stuck.

I am trying to do this on a Mac (insert joke here), and i finally am confident enough translating the Code and typing the code into Terminal, using the Mac version of the commands, and not using the miniadb_inc, but the Mac Version of the Android SDK.

However, I get stuck at the HTCDEV part, about unlocking my bootloader.

it's asking me to download a new RUU in order to unlock

"Verizon WWE 4.08.605.2 PB3120000"

however, the RUU it's asking for is .exe, which means my mac can't run it.

any suggestions?

i just want to root, my phone is still

software number
4.08.605.2

baseband version
2.15.10.07.07

build number
4.08.605.2 CL 185897 release-keys

and it keeps asking me to update to this one...

4.08.605.15

http://www.htc.com/us/support/htc-droid-incredible-verizon/software-updates

I believe that is the update that breaks this method, right?

So i can probably still use 3.22 unrevoked and root, and use titanium backup to freeze the ota from happening, right?


in which case if i don't get a windows computer or a mac way to use htcdev right away, i can root the old way and then do this method to get s-off after i get access to windows?

 

[cmlusco]

So... i'm stuck.

I am trying to do this on a Mac (insert joke here), and i finally am confident enough translating the Code and typing the code into Terminal, using the Mac version of the commands, and not using the miniadb_inc, but the Mac Version of the Android SDK.

However, I get stuck at the HTCDEV part, about unlocking my bootloader.

it's asking me to download a new RUU in order to unlock

"Verizon WWE4.08.605.2PB3120000"

however, the RUU it's asking for is .exe, which means my mac can't run it.

any suggestions?

i just want to root, my phone is still

software number
4.08.605.2

baseband version
2.15.10.07.07

build number
4.08.605.2 CL 185897 release-keys

and it keeps asking me to update to this one...

4.08.605.15

http://www.htc.com/us/support/htc-droid-incredible-verizon/software-updates

I believe that is the update that breaks this method, right?

So i can probably still use 3.22 unrevoked and root, and use titanium backup to freeze the ota from happening, right?


in which case if i don't get a windows computer or a mac way to use htcdev right away, i can root the old way and then do this method to get s-off after i get access to windows?

You can skip the ruu part of the htcdev site, as you should already have the 1.02 bootloader which is already unlockable. If you dont have the 1.02 hboot, then you will need to do this ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip thru hboot to get it.

Just finish the htcdev site skippimg the ruu. Once unlocked fastboot flash cwm and then flash su thru recovery and you will be rooted. From there you can fastboot flash the misc partition, and then do the froyo ruu thru hboot (PB31IMG.zip). Then flash cwm again and then flash the unrevoked forever patch thru recovery. Then you will be rooted, s-off and ready to flash anythimg you want.

 

[funkpod]

You can skip the ruu part of the htcdev site, as you should already have the 1.02 bootloader which is already unlockable. If you dont have the 1.02 hboot, then you will need to do this ruu http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip thru hboot to get it.

Just finish the htcdev site skippimg the ruu. Once unlocked fastboot flash cwm and then flash su thru recovery and you will be rooted. From there you can fastboot flash the misc partition, and then do the froyo ruu thru hboot (PB31IMG.zip). Then flash cwm again and then flash the unrevoked forever patch thru recovery. Then you will be rooted, s-off and ready to flash anythimg you want.

okay, i am on .92, so i would need to do that hboot stuff... how do i do it? or is that what htcdev take me through?

 

[cmlusco]

okay, i am on .92, so i would need to do that hboot stuff... how do i do it? or is that what htcdev take me through?

Download the PB31IMG.zip file i posted earlier and put it on your sdcard in no folders. Pull the battery, reinsert, and hold vol down and power till a white screen appears, hboot. Hboot should find the file after a few secs, and prompt you to press vol up to install it. Then continue with the htcdev site instructions skipping only the ruu part.

 

[imattxc]

I have stock 1.07 hboot? How do I update that?

---------- Post added at 01:32 PM ---------- Previous post was at 01:21 PM ----------

Download the PB31IMG.zip file i posted earlier and put it on your sdcard in no folders. Pull the battery, reinsert, and hold vol down and power till a white screen appears, hboot. Hboot should find the file after a few secs, and prompt you to press vol up to install it. Then continue with the htcdev site instructions skipping only the ruu part.

I have stock 1.07 hboot? How do I update that?

HBOOT 1.07
radio 2.15.10.12.20
touch panel atmelc03-16ac

I have been following this guide [cant post link]
but it doesnt give much info on updating the hboot. I downloaded the RUU updater but it doesnt detect my phone.

Sorry for the reply, but it said my message didnt send.

 

[musical_chairs]

I have stock 1.07 hboot? How do I update that?

1.07 is the latest hboot, you are already up to date on that. You should be able to proceed with unlocking your bootloader via htcdev.

 

[imattxc]

1.07 is the latest hboot, you are already up to date on that. You should be able to proceed with unlocking your bootloader via htcdev.

I was able to. im now on stock ginger rooted s-on. im about to downgrade to froyo for s-off

 

[paul1701]

cwm appears to be locked

Removed post - found answer in other forum - trackball controls CWM selections on Dinc.

 

[scotty1223]

no,you do not need zergrush for this guide. i wish i had used amon recovery in the guide... clockwork casues so much confusion.

you are using power to try and select menu options,but power takes you back a menu,it does not select. pressing power on the main menu takes you to.... then hat.

use the optic track pad thingy to manuver and select menu options and you should be able to complete step 2

 

[funkpod]

HEY! IT WORKED!

AWESOME, THANKS!

and i did it on a MAC! most of it, anyways. I was having trouble getting myself onto the correct ROM, RUU, 4.08.605.2.

i needed to do that on windows. other than that, i got it all done on my mac, with the help of "./" before every command, the android sdk, and you guys! and my good friend who is a programmer.

I have included the whole Terminal session, in case it is helpful to someone. and there are a LOT of weird mistakes in it, but the gist is there...

Teacher107MBP6-20-2012:~ teacher$ md5 /Users/teacher/Desktop/ROOT/PB31IMG\ \(1\).zip 

MD5 (/Users/teacher/Desktop/ROOT/PB31IMG (1).zip) = 25ec451e08cd98c9495971bcb37e6582
Teacher107MBP6-20-2012:~ teacher$ 
Teacher107MBP6-20-2012:~ teacher$ md5 /Volumes/INCREDIBLE2/PB31IMG.zip 
MD5 (/Volumes/INCREDIBLE2/PB31IMG.zip) = 25ec451e08cd98c9495971bcb37e6582
Teacher107MBP6-20-2012:~ teacher$ cd /Users/teacher/android-sdk-macosx
Teacher107MBP6-20-2012:android-sdk-macosx teacher$ fastboot oem get_identifier_token
-bash: fastboot: command not found
Teacher107MBP6-20-2012:android-sdk-macosx teacher$ ./ fastboot oem get_identifier_token
Teacher107MBP6-20-2012:android-sdk-macosx teacher$ ls
SDK Readme.txt	platform-tools	temp
add-ons		platforms	tools
Teacher107MBP6-20-2012:android-sdk-macosx teacher$ cd /tools
-bash: cd: /tools: No such file or directory
Teacher107MBP6-20-2012:android-sdk-macosx teacher$ cd tools
Teacher107MBP6-20-2012:tools teacher$ ls
Jet			emulator		monkeyrunner
NOTICE.txt		emulator-arm		proguard
adb_has_moved.txt	emulator-x86		source.properties
android			etc1tool		sqlite3
ant			hierarchyviewer		support
apkbuilder		hprof-conv		systrace
apps			lib			templates
ddms			lint			traceview
dmtracedump		mksdcard		zipalign
draw9patch		monitor
Teacher107MBP6-20-2012:tools teacher$ cd
Teacher107MBP6-20-2012:~ teacher$ cd /Desktop/ROOT
-bash: cd: /Desktop/ROOT: No such file or directory
Teacher107MBP6-20-2012:~ teacher$ s
-bash: s: command not found
Teacher107MBP6-20-2012:~ teacher$ ls
Backupdocs-lite.app	Movies			android-sdk-macosx
Desktop			Music			drop.app
Documents		Pictures		miniadb_inc
Downloads		Public			run shirt back 2012.svg
Google Drive		Samsung
Library			Sites
Teacher107MBP6-20-2012:~ teacher$ cd Desktop/ROOT
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
-bash: ./fastboot: No such file or directory
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
< waiting for device >
...
(bootloader) [ERR] Command error !!!
OKAY [  0.008s]
finished. total time: 0.008s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [  0.007s]
finished. total time: 0.007s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [  0.007s]
finished. total time: 0.007s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [  0.008s]
finished. total time: 0.008s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
FAILED (status malformed (1 bytes))
finished. total time: 0.001s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot-mac oem get_identifier_token
... FAILED (status malformed (1 bytes))
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot-mac oem get_identifier_token
... INFO[ERR] Command error !!!
OKAY
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [  0.007s]
finished. total time: 0.007s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
(bootloader)    
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 4AEEDE8F5B17934521842903424C1DF7
(bootloader) EB83AB9F85C83D4B3506FE0E32D33F50
(bootloader) DE0C387857FE1584434E59370A7F1228
(bootloader) 39216967E2C5455FE3169F24580C1309
(bootloader) A787E47E66495AD401736DEF147013B1
(bootloader) 15646BEF0DE7A62ED7922E1B8F102989
(bootloader) 9A00BA1E7F82D5F36DEE61C0844ED1DF
(bootloader) B5B31A21801137EC1A1B90BA1DAB651F
(bootloader) 01B3AA6BF05EE1E42FD6991D6C09C7AB
(bootloader) DF17FE8DAA9FAA2B86A685A000C4BE94
(bootloader) 44260BBFF88F3F02F80A75C8422CF90A
(bootloader) 196AF903E474B68AD216F945663A28F8
(bootloader) E5EB7FBDC9AC9180FD1E14EC9BDFC94E
(bootloader) 72B2377F9AED7E3401713D5D253F58DC
(bootloader) 1F83E0A41C1AA74C06F259A1B2FE21A1
(bootloader) 594C04F62810A81FB13A7339A236FBC7
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [  0.068s]
finished. total time: 0.068s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [  0.014s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [  0.006s]
finished. total time: 0.021s
Teacher107MBP6-20-2012:ROOT teacher$ md5 /Users/teacher/Desktop/ROOT/recovery-clockwork-5.0.2.0-inc.img 
MD5 (/Users/teacher/Desktop/ROOT/recovery-clockwork-5.0.2.0-inc.img) = ea382ca5809cb872d0582aa22741d592
Teacher107MBP6-20-2012:ROOT teacher$ .adb devices
-bash: .adb: command not found
Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot
usage: fastboot [ <option> ] <command>

commands:
  update <filename>                        reflash device from update.zip
  flashall                                 flash boot + recovery + system
  flash <partition> [ <filename> ]         write a file to a flash partition
  erase <partition>                        erase a flash partition
  format <partition>                       format a flash partition 
  getvar <variable>                        display a bootloader variable
  boot <kernel> [ <ramdisk> ]              download and boot kernel
  flash:raw boot <kernel> [ <ramdisk> ]    create bootimage and flash it
  devices                                  list all connected devices
  continue                                 continue with autoboot
  reboot                                   reboot device normally
  reboot-bootloader                        reboot device into bootloader
  help                                     show this help message

options:
  -w                                       erase userdata and cache
  -s <serial number>                       specify device serial number
  -p <product>                             specify product name
  -c <cmdline>                             override kernel commandline
  -i <vendor id>                           specify a custom USB vendor id
  -b <base_addr>                           specify a custom kernel base address
  -n <page size>                           specify the nand page size. default: 2048
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem get_identifier_token
...
(bootloader)    
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 9428F4494B41C06E32BB6AE499110C03
(bootloader) 973D44CD26E92FE13F64DDC66BD6D1B2
(bootloader) 3A00F180C91E4B8E8B62F075B2A75A46
(bootloader) 56D417A08C041207E0156C4BCB9B600B
(bootloader) 888A9E5A83197A11F20C55ADD48A9781
(bootloader) F7ED1690D18A5EFAF77D59FE54E4D0B6
(bootloader) 3381A6588E5474E5C869D0420ACAE8DD
(bootloader) D6130C1DDCFEE517FB5BF28B8B9CF1B0
(bootloader) 81FF93D07225ACE83DEC9FAC27A156C7
(bootloader) 9B13A7C3FDF71219C6326EF0C55F9C58
(bootloader) 36B12E69ED38D97FC55C956AF12FE177
(bootloader) AB4DA4B60B60716DBA4AB5DC6D34739B
(bootloader) 8C9A2E95C2D85C8769C34FC3BEF3C409
(bootloader) E249FA2B846AC67BA0BCE1AF64E24998
(bootloader) 6E28580B6F883693EA2F436B3A6326F0
(bootloader) 3DCE3F9F38AA61D99BB50B83802737B0
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [  0.061s]
finished. total time: 0.061s
Teacher107MBP6-20-2012:ROOT teacher$ ./adb reboot bootloader
error: device not found
Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 
HT0C2HJ02350	device

Teacher107MBP6-20-2012:ROOT teacher$ ./md5sums recovery-clockwork-5.0.2.0-inc.img
-bash: ./md5sums: No such file or directory
Teacher107MBP6-20-2012:ROOT teacher$ ./adb reboot bootloader
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot devices
HT0C2HJ02350	fastboot
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
OKAY [  0.436s]
writing 'recovery'...
OKAY [  0.983s]
finished. total time: 1.418s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot reboot
rebooting...

finished. total time: 0.095s
Teacher107MBP6-20-2012:ROOT teacher$ md5 /Users/teacher/Desktop/ROOT/PB31IMG\ \(2\).zip 
MD5 (/Users/teacher/Desktop/ROOT/PB31IMG (2).zip) = 25ec451e08cd98c9495971bcb37e6582
Teacher107MBP6-20-2012:ROOT teacher$ md5 /Users/teacher/Desktop/ROOT/PB31IMG\ \(2\).zip 
MD5 (/Users/teacher/Desktop/ROOT/PB31IMG (2).zip) = 31bb1611a0fa8197d447c0438426717e
Teacher107MBP6-20-2012:ROOT teacher$ md5 /Users/teacher/Desktop/ROOT/PB31IMG.zip 
MD5 (/Users/teacher/Desktop/ROOT/PB31IMG.zip) = 31bb1611a0fa8197d447c0438426717e
Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 
HT0C2HJ02350	device

Teacher107MBP6-20-2012:ROOT teacher$ ./md5sums mtd0.img
-bash: ./md5sums: No such file or directory
Teacher107MBP6-20-2012:ROOT teacher$ md5 mtd0.img
md5: mtd0.img: No such file or directory
Teacher107MBP6-20-2012:ROOT teacher$ md5 /Users/teacher/Desktop/ROOT/PB31IMG.zip 
MD5 (/Users/teacher/Desktop/ROOT/PB31IMG.zip) = 31bb1611a0fa8197d447c0438426717e
Teacher107MBP6-20-2012:ROOT teacher$ md5 flash_image
md5: flash_image: No such file or directory
Teacher107MBP6-20-2012:ROOT teacher$ md5 mtd0.img
MD5 (mtd0.img) = 34307be744275f1db1dd16af04c37839
Teacher107MBP6-20-2012:ROOT teacher$ md5 flash_image
MD5 (flash_image) = 0098a7dd6600b55fac34fc6645be5d7a
Teacher107MBP6-20-2012:ROOT teacher$ ./adb push flash_image /data/local/
1364 KB/s (76044 bytes in 0.054s)
Teacher107MBP6-20-2012:ROOT teacher$ ./adb push mtd0.img /sdcard/
891 KB/s (655360 bytes in 0.718s)
Teacher107MBP6-20-2012:ROOT teacher$ ./adb shell
$ ./su
./su: not found
$ su
# cd /data/local
# ./chmod 0755 /data/local/flash_image
./chmod: not found
# chmod 0755 /data/local/flash_image
# cd /data/local
# ./flash_image misc /sdcard/mtd0.img
# exit
$ exit
Teacher107MBP6-20-2012:ROOT teacher$ ./adb reboot bootloader
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot getvar mainver
mainver: 1.22.605.2
finished. total time: 0.001s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [  0.005s]
finished. total time: 0.005s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot erase cache
erasing 'cache'...
OKAY [  0.840s]
finished. total time: 0.840s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot oem rebootRUU
...
OKAY [  0.092s]
finished. total time: 0.095s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot flash zip PB31IMG.zip
sending 'zip' (176625 KB)...
OKAY [ 25.561s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,100
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,32
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,51
(bootloader) [RUU]UZ,radio,60
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,78
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,97
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,7
(bootloader) [RUU]WP,radio,16
(bootloader) [RUU]WP,radio,21
(bootloader) [RUU]WP,radio,26
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,40
(bootloader) [RUU]WP,radio,45
(bootloader) [RUU]WP,radio,50
(bootloader) [RUU]WP,radio,100
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,43
(bootloader) [RUU]UZ,boot,83
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,42
(bootloader) [RUU]WP,boot,85
(bootloader) [RUU]WP,boot,100
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,20
(bootloader) [RUU]UZ,recovery,43
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,20
(bootloader) [RUU]WP,recovery,40
(bootloader) [RUU]WP,recovery,60
(bootloader) [RUU]WP,recovery,80
(bootloader) [RUU]WP,recovery,100
(bootloader) start image[system] unzipping & flushing...
(bootloader) [RUU]UZ,system,0
(bootloader) [RUU]UZ,system,6
(bootloader) [RUU]UZ,system,12
(bootloader) [RUU]UZ,system,19
(bootloader) [RUU]UZ,system,25
(bootloader) [RUU]UZ,system,32
(bootloader) [RUU]UZ,system,39
(bootloader) [RUU]UZ,system,45
(bootloader) [RUU]UZ,system,51
(bootloader) [RUU]UZ,system,58
(bootloader) [RUU]UZ,system,64
(bootloader) [RUU]UZ,system,71
(bootloader) [RUU]UZ,system,78
(bootloader) [RUU]UZ,system,84
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]WP,system,0
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,89
(bootloader) [RUU]UZ,system,90
(bootloader) [RUU]UZ,system,91
(bootloader) [RUU]UZ,system,92
(bootloader) [RUU]UZ,system,93
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,94
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,96
(bootloader) [RUU]UZ,system,97
(bootloader) [RUU]UZ,system,98
(bootloader) [RUU]UZ,system,99
(bootloader) [RUU]UZ,system,100
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,89
(bootloader) [RUU]WP,system,90
(bootloader) [RUU]WP,system,91
(bootloader) [RUU]WP,system,92
(bootloader) [RUU]WP,system,93
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,94
(bootloader) [RUU]WP,system,95
(bootloader) [RUU]WP,system,96
(bootloader) [RUU]WP,system,97
(bootloader) [RUU]WP,system,98
(bootloader) [RUU]WP,system,99
(bootloader) [RUU]WP,system,100
(bootloader) start image[sp1] unzipping & flushing...
(bootloader) [RUU]UZ,sp1,0
(bootloader) [RUU]UZ,sp1,100
(bootloader) [RUU]WP,sp1,0
(bootloader) [RUU]WP,sp1,100
OKAY [149.945s]
finished. total time: 175.507s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot reboot
rebooting...

finished. total time: 0.090s
Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 
HT0C2HJ02350	offline

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 

Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 
HT0C2HJ02350	device

Teacher107MBP6-20-2012:ROOT teacher$ ./adb reboot bootloader
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot devices
HT0C2HJ02350	fastboot
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [  0.014s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [  0.007s]
finished. total time: 0.021s
Teacher107MBP6-20-2012:ROOT teacher$ ./adb devices
List of devices attached 
HT0C2HJ02350	device

Teacher107MBP6-20-2012:ROOT teacher$ md5 recovery-clockwork-5.0.2.0-inc.img
MD5 (recovery-clockwork-5.0.2.0-inc.img) = ea382ca5809cb872d0582aa22741d592
Teacher107MBP6-20-2012:ROOT teacher$ ./adb reboot bootloader
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot devices
HT0C2HJ02350	fastboot
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)...
OKAY [  0.459s]
writing 'recovery'...
OKAY [  0.921s]
finished. total time: 1.380s
Teacher107MBP6-20-2012:ROOT teacher$ ./fastboot reboot
rebooting...

finished. total time: 0.091s
Teacher107MBP6-20-2012:ROOT teacher$

 

[musical_chairs]

I've done this complete guide on Linux too. The only part that kind of requires Windows is applying the RUU to update HBOOT. I 'ran' the RUU with Wine, and while that was never going to actually apply the update, it did extract the files enough for me to grab the PB31IMG.zip, copy it to my sdcard, and flash it from the bootloader. Many thanks to scotty1223 for the guides, my first Android root job was following one of your older guides for the dinc on another forum. Guys like you are invaluable!

Edit: For non-Windows users, it's easier to update HBOOT by downloading the PB31IMG.zip from here, rather than downloading the RUU from HTCdev.
http://dinc.does-it.net/Hboots/Hboot_1.07/