Related
Hi all
For the last few weeks I have been trying to fix my HTC Desire back to some sort of working state. After awhile, I managed to get back to stock (from CM7), but soon realised I had the USB brick and SD Card issue. For info I used the stock HTC 2.3 Gingerbread RUU and used Alpharev PB99IMG_downgrade.zip for HBOOT (I was using Alpharev S-OFF with CM7).
So, I followed this guide, http://android.modaco.com/topic/309939-usb-brickrickrolledb0rked-fixed/ and managed to mount the SD Card. However, I could not get the update.zip file to apply because I was no longer rooted.
So I followed the guide linked in the USB brick article, http://android.modaco.com/topic/307...ide-now-with-hboot-080-and-os-to-121-support/ and soon realised that I did not have the HBOOT version required. Either 0.75 and below, or, 0.80 and below. I have 1.02.0001.
Not a problem, I thought. I will follow this guide to downgrade, http://forum.xda-developers.com/showthread.php?t=768256 as it specifically says that "...the downgrade does not depend on any version of HBOOT" which is what I need. However, first step is to get a working Goldcard. This is where I start to get into trouble and I'm already losing track of what I'm doing, but I soldier on...
How do I create a Goldcard? I followed this guide, http://android.modaco.com/topic/305672-creating-a-goldcard/ and got stuck at running the ADB command as because my USB is broken, Windows 7 (x64) refuses to see the Phone. Luckily, my father has the same phone, so I put my SD Card into his Desire and managed to create a Goldcard (he is running CM7 on his Desire too).
So Goldcard in hand, I go back to the downgrade guide and then spot my next issue. I can't get Windows to see the phone to use ADB commands and I also can't get Windows to see the phone when it is booted up (the charge light won't even come on now), meaning I can't run the downloaded application.
Not to be outdone I went back to the Rooting Guide and tried both of the downloads with the "step1-windows.bat" command just in case they did work, but both give an error, which on searching, is to do with the HBOOT version being incompatible.
I tried putting on the PB99IMG_downgrade.zip file from Alpharev again, then re-running the HTC 2.3 Gingerbread stock RRU and taking the ROM.zip folder and re-loading it on to the phone, but it hasn't changed the HBOOT version. So my cry for help is.... how can I downgrade HBOOT without using ADB commands or having to have Windows detect my phone? I'm basically stuck with Fastboot and my SD Card.
Even though my phone looks stock, I can't call people as it disconnects straight away, the USB is broken and the battery drains stupidly quickly.
Thanks for any help!
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
bortak said:
now this IS a sticky situation.. well done on what you've done so far by the way.
On my guide there's a section on how to temproot and flash recovery without USB connection, then flash a recovery that restores usb functionality, but it's only been tested on 2.2 and S-OFF... could be worth a try though
Click to expand...
Click to collapse
Hi bortak,
Thanks for the reply. It is a bit of a strange situation I agree. I've been putting off signing up and posting for help as I feel quite dumb for breaking my own phone, but I have to admit defeat on this one.
I saw your reply also in this similar topic, http://forum.xda-developers.com/showthread.php?t=1290391, so I will definitely try your suggestion and report back.
Appreciate you taking the time to post.
Thanks.
USB Brick on official GB 2.3.3 and HBoot 1.02
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
dexterm1 said:
I still have the same problem and tried to get temp. root with the "rageagainstthecage" and terminal emulator method:
http://forum.xda-developers.com/showthread.php?t=691639&page=73
But I had no luck. There is no way to write the Misc patition... I´d like to downgrade (to Froyo), but without USB it seems to be impossible. Alpharev did not work. Revolutionary needs USB !USB brick with official Gingerbread, S-ON and HBoot 1.02 seems to be a dead end so far....
Click to expand...
Click to collapse
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
bortak said:
well this sucks, it's also strange how there is so many people at once with exactly same problem as well!
you could call HTC and ask if they'd fix it for you, and say that this happened after you did the update.
Click to expand...
Click to collapse
I´ll have a try
just fixed my desire 1 hour ago and it works.
look at this http://forum.xda-developers.com/showthread.php?t=1296916
What I did:
I was able to connect my pc and phone through wi-fi and adb worked (adb connect phones-IP-address ) and then pushed, chmod'd 755 and executed zergrush. Gained root via cmd with adb shell in windows and after that I just pushed flash_image and mtd0.img to phone and ran it like you supposed to in the guides (chmod 755 and execute). Rebooted and voila! USB connection is working and now my phone signal isn't dropping anymore - phone fixed!
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
dexterm1 said:
I fixed my unrootet Phone (official GB 2.3.3, HBoot 1.02, S-ON, USB Brick)!!!!
I wifi connected with adb and got temp root with zergRush!
Then from cmd in adb shell I flashed the misc with mtd0.img!
Rebooting and everything was fine ))
Many thanks to all of you!!!
Click to expand...
Click to collapse
Hi, pls. tell us how did you managed to connect your unrooted phone over wifi with adb? I get only "unable to connect to ... ip ..."
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
exocetdj said:
You may now want to install 4ext touch recovery now u have sorted it. This has a USB unbrick feature and will save a lot of time should this happen again
Click to expand...
Click to collapse
I can not install anything without root, and i can't root 2.3.3 software.
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
exocetdj said:
try this,
http://theunlockr.com/2010/09/20/how-to-root-the-htc-desire-unrevoked-method/
mine was 2.3.3 after the manual update but now rooted
Click to expand...
Click to collapse
Ignore this, you can't root 2.3.3 with unrevoked
r5_alpine said:
I can not install anything without root, and i can't root 2.3.3 software.
Click to expand...
Click to collapse
Use revolutionary instead
http://theunlockr.com/2011/08/02/ho...android-phone-using-the-revolutionary-method/
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
eddiehk6 said:
Ignore this, you can't root 2.3.3 with unrevoked
Use revolutionary instead
Instructions are all there, read them several times
Sent from my HTC Desire using XDA
Click to expand...
Click to collapse
I can't do both of this, because my phone is not recognized by PC in any way, i must root it without PC.
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
matus.karahuta said:
If you have 2.3 connect to same wifi as your pc and adb connect to your phone's IP. Then run zergrush and you will have temproot over adb from your pc. Then you can flash your mtd0.img and your brick will be resolved
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
r5_alpine said:
I have tried this too, but i get unable to connect error. And on phone i can't enable adb over wifi without root. I have tried almost everything what i found, and im still on the same step.
Click to expand...
Click to collapse
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
matus.karahuta said:
Are you on 2.3 from htcdev? Because that version has adb over wifi enabled by default as it is a dev version. Are you S-on?
Click to expand...
Click to collapse
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
r5_alpine said:
Yes i have flashed it via bootloader from sd card, hoping to resolve the problem, but it become worse. With previous firmware there was no problem temp rooting, now it seems impossible. And yes i am S-ON.
Click to expand...
Click to collapse
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
matus.karahuta said:
Have you tried running RUU while connected with fastboot? Have you tried flashing anything while in fastboot? I am just throwing suggestions at the wall, anything might work or brick...
Click to expand...
Click to collapse
The phone is not seen by pc in any statement, not in bootloader, or fastboot, or recovery. I need to either downgrade to 2.29 rom version, or to root it in some way.
I'm on Android 2.3.4 and trying to unlock bootloader and get s-off, etc.
I can't get my computer to recognize my phone for long enough to run the RUU from HTCdev. HTC Sync will recognize my phone if I put it into sync mode on my phone, but when I start the RUU it disconnects.
any way to do the HTCdev method on Ubuntu? I have a system that I have Ubuntu on but I am not a pro with it either.
i am new but i've gotten the custom rom fever now since I got my nook tablet but this is frustrating me.
Suggestions?
I did it with Arch, and I'd bet you could do it with Ubuntu. Try http://www.droidforums.net/forum/ht...bootloader-through-htc-dev-linux-edition.html
I know it says Rezound, but it'll work (as long as you choose HTC Droid Incredible instead of Rezound).
Thanks. I'll try this tonight when I get home.
I am in desperate need of unrooting my phone now, but due to it being almost 2 years that I've owned this phone I can't remember how I rooted it in the beginning. Any way to figure this out?
Need to know your Hboot version and radio, and also is the phone S-ON or S-OFF (power off, then volume down and power buttons simultaeously).
HBOOT-2.18.0001
RADIO-2.15.00.12.19
Phone is S-OFF
Thanks for your help.
On a side note, my phone is in an infinite boot loop that only loads to the white evo screen, I can't flash custom recoveries, roms, or RUU. I think the problem is the fact that it says LOCKED in the pink label at the top of my bootloader. I tried using the command fastboot oem lock and it says it's already locked and doesn't unlock it or anything of the sort. If you know any way to aid my problem I thank you for the help.
Most infinite bootloops are never fixed, however;
The best advice that I can give you right now is to download these two files.
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
http://goo.im/stock/supersonic/ruu/...15.00.12.19_NV_2.33_release_234563_signed.exe
Connect your phone to your computer, then boot into your bootloader and click on FASTBOOT. The phone should be in FASTBOOT USB. Install the HTCDrivers exe file to your computer. Then try to run the RUU file with the phone still in FASTBOOT USB.
If that doesn't work, then the phone may already be permanently bricked. Interestingly, the phone was rooted nearly 2 years ago, but you have the latest everything. I hope you did not do that with OTA updates.
Thanks shortyydoggg, unfortunately I've tried that method with those exact files already and had no such luck. My last resort is that if I can change the LOCKED pink label to RELOCKED or UNLOCKED, I'll be able to flash through the bootloader again, and temporarily use my phone once more until i can get the EVO LTE. Also, there is basically no way to tell now which root method I used?
Yea, Unlocking the bootloader was going to be my other suggestion after trying the RUU. It's not much else you can do after that.
Sent from my PC36100 using xda premium
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
djs415 said:
Ya the RUU unfortunately goes through successfully but then the phone restarts again. I can't help but feel this is all because my bootloader says LOCKED. The problem now is fastboot oem lock command doesn't work for me, and says the phone is locked and doesn't change the label to RELOCKED or anything else like it should? Do you know why this command isn't unlocking my bootloader or any other commands or ways to do this?
Click to expand...
Click to collapse
That's the wrong command. You need to go to the htcdev site (www.htcdev.com), register, and unlock the bootloader. Since you're already S-OFF, have you tried running a PC36IMG file for a custom RECOVERY. You might not need to be unlocked to do that.
I'm almost positive I tried to flash a custom recovery through the bootloader and it didn't work... however, you were right and my bootloader is now unlocked so THANK YOU! Will post back after flashing the recovery you attached.
To answer your previous question about which root method you used, unrevoked-forever was used at some point to S-OFF the phone, since you are on Hboot 2.18 and still S-OFF and not on the old Engineering S-OFF Hboot. Whether the phone was rooted with Unrevoked, Toast Method 2, Simple Root or AutoRoot, there is no exact way to tell right now, but it can be guesstimated that it might have been Unrevoked.
Now for the confusion if you dare to read:
AutoRoot is Toast Method 1, unrevoked-forever, and a custom ROM inside a program, and Simple Root is Toast Method 1 and a custom ROM inside a program along with the engineering S-OFF bootloader. Unrevoked is uh, Unrevoked and Unrevoked forever inside a program. Toast method 2 is just a custom ROM flashed along with the same S-OFF bootloader as SimpleRoot. If you used Toast Method 2, then you did everything AutoRoot did in order to S-OFF the phone. You just needed unrevoked-forever to keep it S-OFF for any other and your bootloader. Toast Method 1 alone does not S-OFF the phone. If you used SimpleRoot, which does not use unrevoked-forever, you needed unrevoked-forever at some point again to keep the phone S-OFF on any other Hboot (your 2.18). So again, you would have done everything AutoRoot did.
So that brings it down to AutoRoot and Unrevoked, since everything else you did is the same thing that AutoRoot does. Since you rooted nearly 2 years ago, and Unrevoked-forever is inside AutoRoot, AutoRoot has to be newer than unrevoked-forever to contain it inside its program. Also Unrevoked is newer than AutoRoot and already contained Unrevoked-forever. So the likely-hood that you used Unrevoked is very great, but not for sure. It is also the easier method and the one that nearly everyone else used at that time.
Somehow, still no luck. Flashed that file you linked and it goes through successfully, asks to reboot and then back to white screen boot loop. How can this be possible at this point, with the bootloader unlocked it goes through with the process but the actual writing of the data seems to fail. Trying the RUU one last time now that it is unlocked, but if this doesn't work I'm stumped.
I thought the whole beauty of the the bootloader, and more importantly being able to reach it, was that it meant your phone couldn't be bricked. Last try, will report back.
Bootloader unlocked, RUU flashed this time through PC. Nothing, and completely out of ideas here.
Shortydoggs been doing a lot of help around here for similar situations. There have been cases (maybe a dozen I've seen) where people get into a situation like yours where bootloader is accessible , but that is about it. And from what I've read, in those cases, when the phone tries to boot, it does 4 or 5 short vibrates before going back to bootloader.
Your situation is also strange in that, you rooted 2yrs ago, but don't have S-off, a locked bootloader. Hboot 2.18, which is the latest but is unlockable thru HTC dev, but no S-off available for it yet. And your radios are latest, too (mostly irrelevant).
First there was toasts root for baseband 1.37 (which downgraded you to 1.17 with eng hboot to get s-off before bringing you back up to 1.37). Then there was simple root by jiqqaman, which worked for people who took the baseband 1.47 OTA. Then when froyo came out, anyone who took that OTA (baseband 3.25, or 3.26, I forget) had to wait for unrevoked to be developed. I think hboot at that point was 2.08 and 2.10. Unrevoked forever worked on that, and gave you S-off.
I know none of that info helps you necessarily. It's just puzzling how you rooted 2yrs ago, bit have the latest hboot with S-on. Maybe you didn't finish toasts part 2 S-off guide, then sometime recently updated your radio and hboot? No. You need S-off to flash radio. Were you recently on a stock rooted ROM and took an OTA (is that even possible) when you were still S-on (from not finishing toasts guide)?
Sorry, I know it's not a lot of help. Just trying to figure out how things could not match up so much, and if that's how you ended up in this situation (that could be helpful info for others). I hope you don't have the bootloop of death and can get it sorted. Between shortydogg and captain throwback, I HAVE seen some phones saved.
sent from 2yr old Evo on ICS
Yea, I'm not going to waste your time any further. There's not much else to do.
Ya unfortunately I'm quite confused myself... however, if this information helps you at all... For starters, I have S-OFF and until recently (2 weeks or so since my phone started acting up like this) I was running a ROM perfectly fine until one day it restarted into this never ending boot loop. I'm not sure how my HBOOT is the most up to date, seeing as I was always very careful not to do something stupid like change my HBOOT for no reason. The interesting thing is that I had never seen that pink label before on my bootloader saying unlocked or locked OOW until the problem started occuring 2 weeks ago.
Also something I'm realizing... are you telling me that the HBOOT I have does not have S-OFF yet, and therefore you can't flash roms or custom recoveries... but my bootloader still says I am S-OFF. So the problem is I am S-OFF for the most recent HBOOT which can't be changed to S-OFF yet? Could downgrading hboots work?
He did not realize that you were S-OFF. Your phone is set to stay S-OFF regardless of what Hboot you have or how that Hboot usually comes.
Also, your phone appears to have a hardware, and not software issue, so, changing Hboots, might not hurt to try, but may not help much. In case I'm wrong, do not try anything below Hboot 2.10. Here is one for 2.16.
What rom were you running up until the time the bootloops started happening? This sounds alot like the cyanogen mod bootloop of death which no one has ever fixed I believe.
I believe I was using some version of SOS or a sense rom, but I'm leaning more towards SOS.
Just tried using that HBOOT thought it's still not working. Would going to the engineering hboot make any difference?
What could be the hardware problem causing this?
I see that shortydogg is in here taking good care of you .
The bottom line is, if you can't flash/get into recovery from HBOOT, you're probably in an unrecoverable situation.
It's unclear after my review of the thread, but you have tried flashing a recovery through HBOOT using a PC36IMG.zip file, right? And then after flashing, you choose not to reboot, but to boot into Recovery?
If you can get into recovery, then we can resolve your issue (if in fact it is software related).
If the problem is bad NAND blocks on your recovery or boot partitions, then there's nothing that can be done.
Also, the watermark on your bootloader (LOCKED, UNLOCKED, etc) has nothing to do with your issue. That's just connected to the version you were running. As long as you're S-OFF, that's irrelevant.
Incrediblec XD ship S-On
Hboot-0.92.0000
microp-0417
touch panel-atmelc03_16ac
Radio-2.15.10.07.07
Jul 23 2010, 18:06:51
Hello, first thank you for an amazing and current forum, I'd been researching my issue for a while, but most things are dated around 2010. I've experience rooting and ROMing a Droid X with multiple ROMS, but I use the original Incredible as my main phone because I still love it. Well, I originally rooted my Inc with Unrevoked3 I believe. I left the ROM as stock up until a couple months ago when I put CM7.2.0 on it.
About a week ago, the phone would always have working mobile data. Yet, if I received or tried to make a call, I couldn't and then I would lose texting ability. Then, a couple days ago, I was using the Inc for wifi tethering when suddenly it went into an Incredible bootloop. I tried booting to the cyanogen recovery, but it will quickly loop out of it as well.
I went to pvillecomp.com/ and downloaded all the stock Inc software. I individually renamed files to PB31IMG.zip and tried to have HBoot pick up on them. Hboot will see the files, but then do nothing. Except, the originally ROM will get checked and come back and say that the current version is older and can't be flashed.
I've always tried the RUU software for hboot and the original ROM. I either get a usb error or a low battery error even if the battery is charged. Granted, I'm trying the RUU from the phone's bootloader screen.
Does anyone have some support they could throw this way? I use my phone for internet and everything. Thank you all.
-Nevin
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
did you flash any radios? Flashing radios always ends up bad.
NevinInc said:
BUMP*
Has anyone any ideas? I've since ordered a replacement phone, but would really like a workaround in case something would happen again or even to fix the old one. Thanx all.
-Nevin
Click to expand...
Click to collapse
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
123421342 said:
S-off, flash TWRP (because CWM sucks) and flash a new rom. This should fix everything. Flashing a radio DOES not screw everything unless you do not know what to flash, in that case you should not be flashing radios.
Click to expand...
Click to collapse
Btw, no I didn't flash the radio. That was the only thing I didn't attempt to flash. Yet, when attempting to flash anything else, nothing worked. Still wondering about getting S-off before using TWRP, but hopeful to still get it working. Thank you again.
NevinInc said:
I'm looking into the TWRP stuff right now since I've only experience with CWM. My only concern is that I still have S-on. How can I get S-off on my phone when I've only access to the bootloader? Sorry if this is a bit off a noob post, I've simply not the experience with the incredible to know. Thank you so much.
-Nevin
Click to expand...
Click to collapse
BUMP/UPDATE:
Yes, I'm still at it trying to get my Dinc out of it's bootloop and up/running. It's difficult at this point to say what all I've tried. At one point I wanted to use htcdev.com to ensure the bootloader was unlocked/etc. I've had much trouble trying to get fastboot to work correctly on my pc. I've seem to get stuck on "waiting for device" which appears to be a driver error.
I gave up on that and started focusing on the RUU process. I've tried to install the entire Gingerbread 605.3 file. I fixed the error usb 170 by updated or changing htc sync software. Now I'm left with error 140 bootloader error.
I've also updated hboot using the ruu process for version 605.2. This worked on my pc and got me partially excited. Now my hboot shows up as "Locked" now at the top. I also downloaded a different Stock.img file. Hboot detected this and begun the install process. Everything came up as complete and upon reboot went right back into the white screen/incredible bootloop.
So since posting before I've updated htc sync on my pc and have officially relocked my bootloader. I don't mind RUU'ing things to stock, but now gotta get past the Error 140. Any ideas?
So I'm not sure how many are looking at this or have had ideas, but I was able to use htcdev to unlock the bootloader.
Before unlocking the bootloader I was able to RUU to image .15. After this is when I unlocked the booloader. The RUU said it was complete, but I still only bootloop on the incredible white screen. Now, some of the pb31img.zip files I've come across don't even try to install. This includes signed and unsigned .15 img files. Currently these are the new settings to the phone:
Bootloader: unlocked, s-on
hboot 1.07.0000
radio - 2.15.10.12.20
Image version: 4.08.605.15
The last option I can think of is to try using fastboot, but won't that essentially do the same thing? If you think fastboot is the way to go, can u link me or give me some basics on using it. Obviously I used it for unlocking the bootloader so it can't be that complicated.
Are there any other ideas or should I give up on my Dinc? Looking forward to hear what you think. Thanx.
-Nevin
somebody recommended you install TWRP and install a stable Jellybean ROM. Did you try that?
Hi all. I recently broke out my old HTC Droid Incredible to set it up as a gaming device. However, it really can't do a whole lot with the VZW bloatware and being an old phone. Figured I would root it to fix that. However, I can't even get HTC Sync to read the phone. Is it too old to do anything with? Any help is greatly appreciated.
Madnapali said:
Hi all. I recently broke out my old HTC Droid Incredible to set it up as a gaming device. However, it really can't do a whole lot with the VZW bloatware and being an old phone. Figured I would root it to fix that. However, I can't even get HTC Sync to read the phone. Is it too old to do anything with? Any help is greatly appreciated.
Click to expand...
Click to collapse
You should still be able to root it. You don't need HTC sync, you just need a new enough bootloader (HBOOT) to be able to unlock the bootloader, and you need to be able to communicate with HBOOT via fastboot commands.
Did you try following one of these guides?
http://forum.xda-developers.com/showthread.php?t=1506258
http://forum.xda-developers.com/showthread.php?t=1600904
You don't need to bother with s-off, just unlock the bootloader and flash the recovery. From there, you can do anything you want with the phone.
I couldnt get fastboot commands to do anything, either. I'll give it another shot but really have no confidence it will work. Thanks for the links.
I figured out that HBoot didn't update when I did this last. Even if the image is the same. Problem is, the HTC RUU stops being able to read the phone once it gets to the bootloader, so I can't even update it. Any ideas?