Develop Bugs

Black Screen of Death - Failed hboot Downgrade

I know at least 2 other people have had this happen so I wanted to make a central thread to troubleshoot and maybe fix it. Chime in with what you've tried and (hopefully) what worked.
After a failed attempt at downgrading my hboot, I'm stuck with no picture on the screen. I can only access my phone in fastboot and the official RUU .exe. When I try to run the exe, I can get as far as the phone rebooting into bootloader but then it just times out. In fastboot I have tried to flash a new hboot or boot image but get "failed image error" or somethng.
Any other ideas/solutions?

Did you try flashing a recovery through fastboot? There is a link to amon ra's thread in my sig that has directions on it
Sent from my PC36100 using XDA App

I had the same problem this weekend.
http://forum.xda-developers.com/showthread.php?t=839155
Apparently nobody knows what to do because I didn't get it fixed.
EDIT
That being said, today I gave up and took it to Sprint, said HTC told me to use a program to restore it to factory defaults (I was very vague about the RUU, tried to sound as unknowledgeable as possible), and it stopped midway (which is sort of the truth). The guy at Sprint tried to restore it using their program, but it wasn't working. He asked if it was rooted, I played dumb, and I'm getting a new one sent to me through the warranty for free.

If your NAND is locked again (S-ON) you will only be able to flash an update signed by HTC.
I'm assuming you had the 2.02 hBoot? If so place this on your SD card, rename it to PC36IMG.zip and then put it back in your phone. Hold vol down and boot into your bootloader like normal, and after a full minute push vol down. If all goes well it will flash everything the RUU would normally.
3.30.651.2_PC36IMG.zip

xHausx said:
If your NAND is locked again (S-ON) you will only be able to flash an update signed by HTC.
I'm assuming you had the 2.02 hBoot? If so place this on your SD card, rename it to PC36IMG.zip and then put it back in your phone. Hold vol down and boot into your bootloader like normal, and after a full minute push vol down. If all goes well it will flash everything the RUU would normally.
3.30.651.2_PC36IMG.zip
Click to expand...
Click to collapse
he wasnt getting into the bootloader...I had a phone that did this...I was able to recover using unrevokeds hboot drivers and the 3.30 ruu on a 32bit windoes 7box

Most likely bricked EVO 4g

I have officialy given up on repairing my phone. Looks like it's not possible to fix this thing. Just spent the better part of 3 pays (4hours of sleep a night) trying to get my phone fixed. My sister bought this EVO through some work deal and gave me it on Christmas. I rooted it that night, and bricked it 30mins later, because of the newer partition scheme it is currently impossible to get this phone back working...
This is what I have now. A EVO 4G that boots normally to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
A Vol Down + Power Boot boots to this screen. ftp://eto.homeip.net/shared/IMAG0004.jpg
I can also navigate to this screen. ftp://eto.homeip.net/shared/IMAG0005.jpg
Because of the S-OFF it is obvious to those in the know that I rooted my phone.
I'm just wondering if you guys think this scenaro will work.
_________________________________________________________________
Walk into a Sprint Repair Store, tell them my sister just bought the phone new (about a week ago) and gave it to me as a X-Mas gift. I chose to do the latest OTA-Update, and after it stopped booting and only went to this screen. ftp://eto.homeip.net/shared/IMAG0003.jpg
Where I'd have to pull the battery to turn it off.
They will probably try VolDown+Power and might comment on S-OFF (which I will say I don't know what that is).
Hope they give me a new/refurbished EVO for free or less then $50.
===============================
Questions
* Should I go to a Sprint Store I've never been to? (There are stores within 20miles of me) (Closest knows I root phones, then other I've been into a bunch of times and may have given up on me)
* Should I get the receipt from my sister, who I don't want to tell I rooted/bricked phone
* Also please give me suggestions of anything that will help
BTW
* Am well within 30days of buying phone, though I'm not sure if my sister bought it through Sprint or not (Think she did though)
* I have pin/name/number on account and can easily activate a different phone they give me.
* Would rather not tell my sister or even get the receipt from her room to keep her from suspecting anything, but can if need be
Thanks for your suggestions, wanted to get this done by the end of the week before I head back down to San Luis Obispo for college. (Where there are fewer Sprint Stores to spam)

The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.

http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.

LaloHigh said:
http://forum.xda-developers.com/showthread.php?t=884060
Pick which ever one you like and put it on the root of the sdcard. I couldnt tell you because if you didnt record what software you started with niether could I.
Click to expand...
Click to collapse
What do you mean record what software I started with? I had 2.02, now have 0.76 (But my screen says 2.10). I've tried both the exe and the PC36IMG.zip that you've linked.
Using .exe gives me a Error 170 (Not recognizing my phone is plugged in)
Putting PC36IMG.zip on sd and using hboot gives me Failed-PU, Partition Update Fail! for every category but Radio_V2. BTW I'm supposed to use the first two files from that link
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36*****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.11.19
Mar 30 2010,11:24:04

Greenfieldan said:
The Good news: If you're screen is turning on (using ANY method) you're Evo isn't bricked.
The Bad news: I don't know what you did. I would suggest trying the unroot method and seeing if you can get yourself out of this pickle that way. My first rooitng experience everything went horribly array, and I ended up just accepting an OTA to get out of it.
Click to expand...
Click to collapse
Well what I did was messup the way it sees my partition. I have a nwer partition scheme i believe but the 0.76 software thinks I have the older partition settup.
If you mean unroot method from this post http://forum.xda-developers.com/showthread.php?t=829045 the one I rooted with then I can't do it cause I have no recovery. I can't get to it cause bad partition settup.

I know I can run fastboot erase commands, do you guys think I should run
Code:
fastboot erase boot
to create an unbootable system. One that doesn't even have the screen turn on?
*Which if any partition can I delete in order to never have the phone even turn the screen on?
Here's the choices (wimax, misc, recovery, boot, system, cache, userdata)

if your getting error 170, the RUU can't communicate with the phone.\
Can you get Hboot USb on? IF so, the RUU may run with it.
Drivers installed on computer?
Otherwise, you mave have blown out USB port, like I did.
Try putting the RUU, rom.zip (rename rom.zip to PC36IMG.zip) to your sd card, and see if that saves your a$$.
If that don't work, better run it over with a car or something and take it back.

The good news is you are still in your 30 day warranty. The solution I would suggest is try to flash the bootloader back to hboot 2.10. I would find a pc36 with 2.10 and flash away. Maybe even fastboot erase every partition except boot and hboot first. Don't do radio or wimax either or it will brick your radio and wimax. Then flash a full pc36. Other than that, manually brick. I would erase hboot and boot to brick.
Good luck

If you erase boot.img, it will still go to hboot. Erase the touchpanel image. That way they cant see it. By the time your phone gets to its repair destination, "they" wont be looking for that type of thing. They will just repartition. Also, it wont let you erase hboot

What error are you seeing when you select recovery from the bootloader menu?
The RUU that you tried, what version was it? You MUST use the 3.70.651.1 RUU because your phone thinks you are on hboot 2.10. Do not try an older RUU.
--------------------------------
Try the following
1) Download File PC36IMG_Recovery.zip and Rename to PC36IMG.zip.
copy to the root of your SDCard and power off phone
2) Power your phone back on into the boot loader by holding power and vol-down until your presented with a white screen. It will read the pc36img.zip and as you if you want to flash. Say yes. Then it will ask if you want to reboot, VOL+UP for yes.
3) If your rom gets tossed in the process. Reboot your phone into bootloader select recovery, and reflash your rom....DONE
4) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1
-----------------------------------------------
If that does not work then try the following:
1) Download the img file for the modified Amon_Ra Recovery
2) Put evo-test.img on the root of your sdcard
3) Put the phone in fastboot mode
4) fastboot boot evo-test.img
5) Once in recovery, flash HBoot 2.10 zip
6) Now try RUU 3.70.651.1

Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks

josh4trunks said:
Update
thanks to some help I have gotten farther on this issue. Can get past USB Erro 170. Now get to Error 171 when trying to flash image. When i run RUU.exe it tries flashes then reboots into stuck image of 3 androids skating. Which I alwasy need to battery pull to fix. Heres the log
ftp://eto.homeip.net/shared/RUU_101228T160722.log
__________________________________________
So how could I remove touchpanel img? thanks
Click to expand...
Click to collapse
But if you can't flash a RUU.exe, then you can probably flash a zip file of a ROM.
This can or be or is not correct, I am just curious how this well happened to you.

nope tried flashing ROM through hboot, fastboot... Tried 'fastboot erase boot' didn't do anything. I'm gonna update the OP on the current situation, giving up...

Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.

i think he said multiple times that he was totally screwed and his partitions were messed up so he either needs a total memory reflash or god's private java code

illogos said:
Are you able to use the bootloader to flash only the custom recovery amon RA zip? If you can get into custom recovery you will be fine. Once in recovery you can flash hboot radio etc 1 at a time with a reboot in between each flash. After that you can flash a custom rom and be happy.
Click to expand...
Click to collapse
Can't flash through bootloader. Get Fail-PU
Which is a Partition Update Error

Continuous Boot loop, Cant load Recovery, NEED HELP!

Ok, I'll try to keep this simple and informative.
I have been rooted with unrEVOked for months. Last night I flashed CyanogenMod 7 RC2. (I've posted this there too on their forums) Today my Evo crashed while using the app QR Droid, and now goes into a boot loop after the "htc EVO 4g" white screen. It loads that screen, then goes black, reboots and does this cycle until I pull the battery.
I can get into hboot. (v 2.10.001, Clockworkmod), S-OFF, updated radio last night when I actually could before I flashed CM7 RC2 to 2.15.00.11.19.
Here is where the problem deepens, and is very similar to this thread; Bricked Evo, and cant factory wipe. Help please
When I try to select Recovery, the boot-loop starts over; so i actually cant get into recovery and flash anything from the sd card it also does not give me any triangle bull**** or whatever, just starts the boot loop.
I have a card reader for my micro sd card; I took everything off of it and put an RUU on it, renamed it PC36IMG.zip, got into hboot, tried to update it and it failed, goes back to the boot loop. I believe the ruu was outdated.
Can someone link me to the most recent recovery image? I should use to get back to stock? I think that is my problem, the ruu is out of date.
Or any other input would be greatly appreciated.
Thanks
I tried this recovery image to know effect, when i reboot after applying update it goes back into loop; CANT POST LINK YET!

mhport2 said:
Ok, I'll try to keep this simple and informative.
I have been rooted with unrEVOked for months. Last night I flashed CyanogenMod 7 RC2. (I've posted this there too on their forums) Today my Evo crashed while using the app QR Droid, and now goes into a boot loop after the "htc EVO 4g" white screen. It loads that screen, then goes black, reboots and does this cycle until I pull the battery.
I can get into hboot. (v 2.10.001, Clockworkmod), S-OFF, updated radio last night when I actually could before I flashed CM7 RC2 to 2.15.00.11.19.
Here is where the problem deepens, and is very similar to this thread; Bricked Evo, and cant factory wipe. Help please
When I try to select Recovery, the boot-loop starts over; so i actually cant get into recovery and flash anything from the sd card it also does not give me any triangle bull**** or whatever, just starts the boot loop.
I have a card reader for my micro sd card; I took everything off of it and put an RUU on it, renamed it PC36IMG.zip, got into hboot, tried to update it and it failed, goes back to the boot loop. I believe the ruu was outdated.
Can someone link me to the most recent recovery image? I should use to get back to stock? I think that is my problem, the ruu is out of date.
Or any other input would be greatly appreciated.
Thanks
I tried this recovery image to know effect, when i reboot after applying update it goes back into loop; CANT POST LINK YET!
Click to expand...
Click to collapse
I attatched a PC36IMG of Amon Ra recovery version 2.3. You can try flashing that from the bootloader. I will also provide a link to the most recent RUU's and PC36IMG's. This link actually has all of them, old and new. Hope you're able to recover the phone dude. Good luck.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu

thanks, I have clockworkmod from when i unrevoked and had it updated via the CM7 rom manger last night, does that matter?
I tried that img you attached, it did not work, Im not exactly sure how to use the RUU's could someone explain what else I should do?

mhport2 said:
thanks, I have clockworkmod from when i unrevoked and had it updated via the CM7 rom manger last night, does that matter?
Click to expand...
Click to collapse
should'nt make any difference at all. I'm not sure how your initial problem happened, but you are not the first I've seen this happen to. Most that I've seen were recent, and were running CM7. Not sure what's up with that, but if you search the q and a section, you'll find a few similar threads. Very strange. I hope you ge it working again.

Happened to me and a few others a week or 2 ago. There was no fix that we found. Pc36img wont work, ruu won't work. U won't be able to do anything to get s-off to s-on either (in my experience.) Even tho u can get to bootloader, if its like what happened to me and a few others, ur bricked. I got mine warranty replaced (but they're still gonna charge me $125 for returning an unrecoverable phone) another guy threw his out his car window and they charged him $100 to replace his "lost" phone. Those are the only options I know of.
Sent from my PC36100 using XDA App

[Q] Help with soft birck

The incredible will go into hboot but the recovery, factory reset, clear storage all send it into a boot loop. It is S-off and should have cwm (the root was done by unrevoked) but I cant get it into recovery mode to fix the problem. the up vol + power will cause it to vibrate 3 times but the screen stays black.
I am use to samsung phones where I can just odin it back to stock but have little experience with Htc. Any help on reverting it back to stock or just help me get into recovery so i can flash a custom rom would be great. thanks
btw
hboot is .92
Radio 2.15.00.07.28

If you are s-off I would first try reflashing cwm thru hboot as a PB31IMG.zip
Here is the CWM 5.0.2.0 PB31IMG.zip
http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip
Just place it on the root of your sd and then boot into hboot (hold vol down and power) it should find the file and prompt you to press vol up to install. If that works then install the su binary found below thru recovery.
http://dinc.does-it.net/SuperUser/SuperUser_3.0.7.zip

thanks for the quick reply after updating with the PB3 file it still wont go into recovery mode, just the boot loop. any other ideas?

I would say your next step would be to do an ruu of froyo 2.2 wich you can fiNd here http://dinc.does-it.net/Stock_Images/3.26.605.1/PB31IMG.zip and if that dosent work I would try an ruu exe with your pc.

Thanks for your quick response, this phone is wack! I ran the ruu exe from my pc it did its thing and successfully updated the Rom but to my surprise when it rebooted it was stuck in a boot loop!

I had a similar problem a few days ago, and the only solution I found was to update CWM through RomManager. I'm thinking that the problem may have been caused by RomManager in the first place, which is why this is the only method that worked for getting CWM working.

You could try flashing an older version of cwm like 3.0.0.8 thru hboot. Mabey cwm 5 is whats causing your troubles. Or try flashing amon ra recovery.
Cwm 3.0.0.8
http://dinc.does-it.net/Recoveries/CWM_3.0.0.8/PB31IMG.zip
Amon_ra 3.02
http://dinc.does-it.net/Recoveries/AmonRA_3.02/PB31IMG.zip

I flashed both recovery's, also an ruu of a stock rom, and I also tried doing an ruu exe through the computer. all of them succeeded but in every case I am still stuck in a boot loop and cant get the phone to boot up

jordonlm1 said:
I flashed both recovery's, also an ruu of a stock rom, and I also tried doing an ruu exe through the computer. all of them succeeded but in every case I am still stuck in a boot loop and cant get the phone to boot up
Click to expand...
Click to collapse
Can you get into recovery yet or are the hboot options still not working?
Mabey your hboot got corrupted somehow you can try reflashing it.
hboot 0.92
http://dinc.does-it.net/Hboots/Hboot_0.92/PB31IMG.zip
Then try flashing a recovery again and see if you can get into it.

None of the hboot options work. I have flashed all the files you have given me. and I have done the ruu exe of both froyo and gingerbread. they all say they have completed successfully but nothing has fixed the problem. Still cant get into recovery and it wont but up at all. Im not sure what else it could be

Im not sure then if none of those options work im at a loss of what else you could do. Mabey someone with more experince can chime in with some other options. Have you tried reformating your sdcard or using a different one? Thats the only other thing I can think of.

jordonlm1 said:
None of the hboot options work. I have flashed all the files you have given me. and I have done the ruu exe of both froyo and gingerbread. they all say they have completed successfully but nothing has fixed the problem. Still cant get into recovery and it wont but up at all. Im not sure what else it could be
Click to expand...
Click to collapse
When you say "flashing" are you literally flashing these .zip files in CWM or are you renaming these files to PB31IMG.zip and installing thru HBOOT? There is a difference between the two.

Marcismo55 said:
When you say "flashing" are you literally flashing these .zip files in CWM or are you renaming these files to PB31IMG.zip and installing thru HBOOT? There is a difference between the two.
Click to expand...
Click to collapse
He cant get into recovery thats one of the issues.

ya i guess not flashing just running the PB31 file in hboot. I think im done working with it though. Im doing it for some guy who tried flashing it from verizon to another carrier but it didnt work and it only goes into hboot now. but thanks for all your help especially cmlusco. I'm still open for ideas but It's not going to my priority anymore. I learned a lot about htc phones if anything

cmlusco said:
He cant get into recovery thats one of the issues.
Click to expand...
Click to collapse
So the OP is S Off and can't flash the PB CWM file in HBOOT? Ccould be a bad file too. Make are you are checking md 5s
Sent from my Droid Incredible HD using Tapatalk

He can flash any PB31IMG file sucessfully but the phone will not boot and selecting any of the options in hboot leads him to a splash bootloop, and requires a battery pull. It's all above.

Marcismo55 said:
So the OP is S Off and can't flash the PB CWM file in HBOOT? Ccould be a bad file too. Make are you are checking md 5s
Ya it is s -off
I have flashed the pb CWM file no luck and also the other recovery (cant remember the name)
I also tried flashing th pb hboot file no luck
I flashed the pb ruu froyo no luck and also gb no luck
i then tried doing it through my computer using stock froyo exe and also a gb one with no luck (In every case the phone said it was "successful" in updating the roms and/or the recoverys)
But nothing ever changes it will only boot into hboot but nothing works in the hboot everything just sends it into a boot loop on the white htc screen
Click to expand...
Click to collapse

jordonlm1 said:
ya i guess not flashing just running the PB31 file in hboot. I think im done working with it though. Im doing it for some guy who tried flashing it from verizon to another carrier but it didnt work and it only goes into hboot now. but thanks for all your help especially cmlusco. I'm still open for ideas but It's not going to my priority anymore. I learned a lot about htc phones if anything
Click to expand...
Click to collapse
Thats probably the issue it was attempted to be switched to another carrier wich is a fairly complicated process. He may have changed some settings below rom level that cant be fixed by flashing an ruu. Im not sure if there is a fix with qpst or not but if there is I have no clue how to do it.

Been seeing some odd issues lately. I had a problem, and it would just go to a black screen and vibrate five times.
If the USB was plugged in to my PC, it would boot and operate fine, as soon as I unplugged it, it would crash again.
Check this out, it may be related.
http://forum.xda-developers.com/showthread.php?t=695243

I've been having almost this exact problem and have been working on it since 5:30 last night. As my phone is also my modem, I am currently at the library on wifi... FML.
The only difference is that I did not try to switch carriers, I was just using my phone normally and then yesterday morning I had a bunch of FCs, and yesterday evenings began the boot loops when I unlocked to make a phone call, again, FML.
The timing is very bad, only about two weeks till my new-every-two. Please help, I need my phone and don't really have the money to spare for a new one.
Thanks in advance.
Your pal,
-H

[Q][NOOB] Please help me unbrick my PRIMOC

First post here, please excuse my ignorance. This is a Virgin Mobile HTC One V. I never rooted a phone before, and was just trying to do a basic rooting, and somehow got into trouble. I would like to return the phone to stock and start over.
Right now the phone boots itself into bootloader, and shows me this:
Relocked
Security warning
PRIMOC PVT SHIP S-ON RL
HBOOT-1.57.0000
RADIO-1.00.00.0928
eMMC-boot
Jun 18 2012, 10:22:43
I am able to do this: fastboot getvar cid. The response is this: cid: SPCS_002.
I am also able to do this: fastboot devices. The response is this: FA2AKX405758 fastboot.
I have attempted to use this RUU:
RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed.exe
It gives me error 170, USB connection error (even though I have installed the HTC drivers). I relocked the phone in an attempt to get that RUU to work, but it didn't help. I also tried to extract the rom.zip from the RUU.exe (by finding it in a temp folder, as described on another XDA thread), but the rom.zip acts corrupt. Various zip programs refuse to open it.
Before relocking the phone (in an attempt to get the RUU to work) I tried this:
fastboot flash boot boot.img
I did that with various boot.img files I found via threads here. This just created various problems. One result was that I was in a bootloop. Another result was that I booted to the screen that said "this build is for development purposes only do not distribute outside of htc without written permission." And it would hang there.
Now my condition is that I boot directly to bootloader.
Starting from the beginning: I unlocked the phone using the unlock bootloader procedure at htcdev. No problem. Then I figured I should do a backup right away, so I installed CM Recovery. Right away I knew I had a problem because it did not run correctly. It would present a menu. Then I would select "backup and restore." It would present a splash screen (with the hat) and just hang there. When I pressed power, it would return to the menu. That's when I started trying various other things.
I never got as far as doing anything with superboot or superuser, which is what I thought I was going to do after doing the backup.
I have read a zillion threads here, and tried various things from those threads, but I'm afraid that without specific help I'm just going to make it worse. I'm pulling my hair out, so I hope someone here can help me while I still have a few left. Thanks!

OK, I have made some progress but I'm still pretty stuck.
I have been able to solve two problems I had before. Before when I ran the RUU, it gave me a USB error. And I could not extract recovery.img from the RUU. I solved both those problems by moving to a different PC.
So now I can run the RUU, and it gives me a bunch of progress messages I didn't see before, but at the end it tells me this:
"Error 155, unknown error. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
So then I tried the procedure described here:
http://forum.xda-developers.com/showpost.php?p=27301573
I unlocked the phone again, and I did this:
fastboot flash recovery recovery_signed.img
I did that using the img file I extracted from the RUU. Then I relocked the bootloader, and I ran the RUU again. But it gave me the exact same error (155).
What should I try next? I notice that the RUU also contains these img files:
system.img
radio.img
boot_signed.img
Should I try flashing those?
Any ideas would be greatly appreciated!
Edit: One more thing. When I ran the RUU, at the end the phone said this:
RUU
Hboot version is older!
Update Fail!

OK, the next thing I tried is the method described here:
http://forum.xda-developers.com/showthread.php?t=1674226
I extracted rom.zip from the RUU, and I renamed it PK76IMG.zip, and I put it on the sdcard, and then I rebooted the phone. The phone found that file and tried to install it, but in the end it gave me the same error message: "Hboot Version is older." On that same screen I see that my current Hboot is 1.57.0000. I guess the RUU contains an older Hboot?
Anyway, that's the same error I get when I run the RUU as an exe.
I notice a couple of people in that thread reported the same problem (Hboot is older), but it's not clear how or if they got around this.
Any ideas?

OK, so here's the next stage in this saga.
Looking around, it seems that there is no RUU for this phone, because I have Hboot 1.57.0000 and radio 1.00.00.0928. I have noticed that people with those specs cannot find a RUU that works, but they have been able to get the phone working with RhythmicRom. I see that discussed here:
http://forum.xda-developers.com/showthread.php?t=2147407
So what I'm trying to do now is install RhythmicRom, but I'm having trouble doing that, I guess because I don't have CM Recovery installed, so the standard recovery is running instead.
I have placed RhythmicRom_v1.4.zip on my sdcard. I am able to boot into bootloader, and I have done factory reset. In the bootloader, I can select Recovery and I see a screen that indicates the phone is looking for something (green circle containing green arrow pointing down, and with a progress bar at the bottom, and an icon of an sdcard). But I guess it doesn't find what it's looking for, and then I see the screen with the red triangle/exclamation mark.
I'm thinking that maybe it will work if on the sdcard I rename RhythmicRom_v1.4.zip to whatever the phone is looking for. Maybe I should rename it to PK76IMG.zip? Just a guess.
Many thanks in advance.

OK, that sort of almost worked. On the sdcard, I renamed RhythmicRom_v1.4.zip to PK76IMG.zip. I booted into bootloader, and it looked like the phone found that file, and loaded it. Then I did this:
fastboot flash boot boot.img
With the boot.img that was inside RhythmicRom_v1.4.zip. Then I rebooted. Now the phone gets to the red animated Virgin Mobile splash screen with the annoying audio. That seems like a good sign, since I haven't seen that in a while. But instead of continuing to boot, then I see the white HTC screen that says "this build is for development purposes only do not distribute outside of htc without written permission." And then it continues to loop between those two screens, so I am stuck in a bootloop. Although I found I was able to interrupt it and get back to the bootloader.
Not sure what to try next. Any suggestions?

Wow, I can't believe you haven't had a single reply.
Ok. First of all.... Use TeamWinRecoveryProject
( TWRP ) as your recovery img
So easy to use
Use fastboot the flash
fastboot flash recovery recovery.img
Then boot into your new touch screen recovery
Now click wipe
Cashe,Dalvick,Factory Reset, System
In that order. It makes sure every thing is wiped thoroughly.
Now navigate to where the Rom is you would like to use and flash it in recovery.
After It's flashed click the wipe cashe/dalvick
Then click home,reboot,bootloader.
Once in bootloader, flash the kernel/bootimg
fastboot flash boot boot.img
After the boot.img is finished,
fastboot reboot
Victory and enjoy the awesomeness of custom ROMs!

P.S. don't forget to unlock your bootloader again. First and foremost
fastboot flash unlocktoken Unlock_code.bin

Russell, thank you for your response. After 24 hours with over 100 views and zero replies, I figured that meant that I had already done the proper steps, and there wasn't some obvious solution I was missing. Although I can see now that I should have tried TWRP. It couldn't have made things worse, and maybe it would have worked better for me than CM Recovery (which seemed to fail as soon as I installed it).
Another key thing was when I figured out that there is no RUU for my specs (because there was an OTA that installed a newer hboot and radio). I like the idea of trying different custom ROMs, but I don't like the idea of never being able to go back to stock, since I would expect that all the custom ROMs have some quirks that I might find unacceptable. But I notice that you have the same hboot and radio, and I assume you have a backup of your stock ROM, so maybe you could have helped me with that.
Anyway, at literally the exact moment that you were posting your comment, I was standing at the UPS counter handing them the phone. If the phone had been working, we would have heard it buzzing inside the box as your email came in! The phone is heading to the HTC repair facility in Houston. They told me they would unbrick it for me for less than $35. I haven't seen anyone else report this, so maybe I was misled and it's too good to be true? We'll see. I don't like being without the phone for a week, but $35 seems like a cheap price to clean up the mess I made.
Anyway, thanks again for speaking up.

Check out the CDMA development thread
Whenever you get your phone back.....
Good luck

I see the thread you're talking about. I just did the download (might as well have it handy). Thank you.

Hope it helped or helps in some way
:beer:
---------- Post added at 02:40 AM ---------- Previous post was at 02:35 AM ----------
I gave you a thanks for first download

Similar problem
Hi,
I had a similar problem. Following this thread I have successfully "unbricked" my phone. My main concern though is activating my phone on VM, which I'm unable to do as I can't go back to stock. I bought the phone as is from craigslist. Any suggestions?
Edit: Internet seems to work though. No go on phone calls or texts, when trying to call this is what I get(Audio):"Account couldn't be verified"

Visit the HTC one v CDMA thread I have a stock rooted Rom there for the taking

Yes, here's the link to that thread:
http://forum.xda-developers.com/showthread.php?t=2321904
It would be interesting to hear if your rom works for cellphoneman.