Develop Bugs

Desire stuck in fastboot RUU mode

First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr

After "a lot" of research you still haven't looked at my guide, well done.

Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.

Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.

Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr

New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr

I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.

bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please

[Q] Is it possible to Recover my DInc?

I hope someone in this community is able to help. I've already been scouring Google this morning for people with a similar issue and haven't been successful in getting my phone to come back so I suspect there may be a hardware issue.
Here's a summary of the problem:
My phone shutdown this morning while I was listening to a podcast. It got stuck in a boot loop at the splash screen, constantly rebooting itself. A battery pull would not solve the problem. I was able to get it into HBOOT (version 0.92) but when I tried going into recovery from there, It got stuck on the splash screen (no looping). Before all this I had been running Nils Business Gingersense for quite a while and things were working fine, in case anyone needs that detail.
After failing to boot to recovery, here are some of the things I have tried to fix this issue:
1. Factory reset in HBOOT
2. Flashed RUU 2.2 and then tried RUU 2.3.4 through HBOOT. Though neither of these would get the phone to come up, the splash screen reboots stopped and the phone just freezes in splash screen now (over 30 minutes with no change).
3. Tried to reflash CWM 5.0.2.0 through Fastboot. Although the phone is recognized by 'fastboot device', it says 'remote: not allowed' when try to flash the .IMG file.
4. Tried to flash an older CWM recovery from when I originally rooted my phone --same 'not allowed' error
5. Ran the official RUU for Froyo on my PC and it looked promising but I never got past the splash screen afterward a reboot.
6. I don't know a ton about ADB but ADB does not recognize my device even though Fastboot does.
At this point I'm not sure what else to try. It seems promising that I can get into HBOOT and that Fastboot will recognize my phone but what can I do with that now?
Thanks for any ideas you might have.

Have you tried flashing cwm thru hboot as a PB31IMG.zip? http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip. If that dosent work you could try to update hboot to 1.02 and htcdev unlock it. This will allow extended fastboot commands. You can do this on the htcdev website. Or you could downgrade hboot to the 0.77 engineering bootloader http://dinc.does-it.net/Hboots/ENG_Hboot_0.77/PB31IMG.zip which basicly does the same thing, and might be a better option than upgrading. You are s-off right?

Yes, I still have S-OFF. I did try flashing several recoveries through hboot and they all acted like they updated fine but I wasn't able to boot into any of them because I kept getting frozen at the white screen after choosing recovery from hboot. I will try another hboot and see if that makes any difference. Thanks.

Cmlusco, I tried the CWM version you posted with hboot .92 and .77 but had no luck. I also tried walking through the hboot upgrade steps on the htcdev site but I couldn't get the RUU exe to find my phone. This is odd because an older RUU found the phone just fine earlier today.

[Q] boot loop after downgrading to hboot 0.97

I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.

kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
try typing this (in fastboot menu)
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip (name of zip)

kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Did you check the md5 for the radio? Did you rename it to EXACTLY PG32IMG.ZIP? if using windows, make sure there's no extra .zip at the end. What did hboot say when it "checked" the file?
Give me some more info. We'll get you going.
Sent from my vivow using xda app-developers app

having the same issue
Ok so I'm a complete noob at this. I ran everything and it seemed fine up until i went to run revolutionary. Rev kept waiting for the device I let it sit for ten minutes. then I had the bright idea to program my phone with my number, thinking that might help. it then rebooted and started bootlooping. It's been constantly looping since. Please help.

*similar* issue
kioji86 said:
I downgraded my hboot to 0.97 in the hopes that I would be able to get S-OFF with revolutionary. I used tacoroot to gain root access, misctool to modify the misc_version so I can downgrade, and flashed the 2.3.3 Gingerbread RUU through hboot. Everything seemed fine so I went to use revolutionary to get S-OFF. After gaining root access my device was rebooted into fastboot where i got an error and revolutionary terminated. Now my phone gets stuck in boot loop. It gets to slide to unlock screen, but reboots seconds later. A factory reset temporarily solves the boot loop problem and the phone doesn't automatically reboot, but once I power down or reboot the phone the boot loop problem returns.
While looking through the forums I noticed that in several threads about boot loops members suggested updating the radio. So I tried flashing the .0312 radio. First I tried through hboot. It checks the zip like normal, but never provides me with the option to install or not. Next I tried through fastboot, but I get this: sending 'radio' <13225 KB>... FAILED <command write failed <Unknown error>>
I'm not sure if I'm doing something wrong or not. If it is indeed the radio that is the issue what am I doing wrong and if it's not does anyone have any ideas as to what wrong and how I can go about fixing it? Any and all help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
I downgraded to 2.3.3 using the tacoroot method. Everything was acting fine after the reboot and I was about to run Revolutionary, but I got a bright idea to confirm I had gained a .97hboot so I shut the phone off and went into the bootloader screen. Yup I have .97hboot. Restarted phone. Boots normally but as others mention it restarts its self after a couple seconds on the lock screen. Hoping this isn't a permanent brick.

zombolt said:
Hoping this isn't a permanent brick.
Click to expand...
Click to collapse
Doubtful that it's bricked. Have you tried flashing a custom rom?
Sent from my Incredible 2 using xda app-developers app

[Q] Stuck HTC Boot screen

Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?

TheHeffNerr said:
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
Click to expand...
Click to collapse
Not exactly sure because I didn't use the HTC DevUnlucky/Unlock, but you can try to S-Off with this: http://forum.xda-developers.com/showpost.php?p=28290187&postcount=2 and see if you can flash a custom rom after gaining S-Off. If you have tried that you will have to wait on someone with a little more experience can help you.

ThePhantom97 said:
Not exactly sure because I didn't use the HTC DevUnlucky/Unlock, but you can try to S-Off with this: http://forum.xda-developers.com/showpost.php?p=28290187&postcount=2 and see if you can flash a custom rom after gaining S-Off. If you have tried that you will have to wait on someone with a little more experience can help you.
Click to expand...
Click to collapse
Oops forgot to put that in there. I've tried the revo s-off but as far as I know the device needs to boot into android to take it. It just sits there waiting for device when I run it. And that needs HBOOT 97 and I'm unable to downgrade
TACOROOT needs ADB and I can't connect with ADB

TheHeffNerr said:
Oops forgot to put that in there. I've tried the revo s-off but as far as I know the device needs to boot into android to take it. It just sits there waiting for device when I run it. And that needs HBOOT 97 and I'm unable to downgrade
TACOROOT needs ADB and I can't connect with ADB
Click to expand...
Click to collapse
Ah, sorry m8, you will have to wait on one of the other more knowledgeable guys jump on to give better advise.

All good, thanks for giving it a shot. If it would lock again stock RUU might work... but no this device hates me lol.

ThePhantom97 said:
Ah, sorry m8, you will have to wait on one of the other more knowledgeable guys jump on to give better advise.
Click to expand...
Click to collapse
Any ideas?

I'm no expert but try re downloading the ruu with the hboot 97 and try it again if you haven't already maybe it was a bad download. I remember when I downgraded mine I tried 3 different files before I got it to work. If you can't find any other ruu flies I'll look on my PC tomorrow and see if I still have the one I got to work and if you're transferring the file to the sd card from a PC leave off the
.zip or it will name it .zip.zip
Sent from my Incredible 2 using xda app-developers app

I think because I can't relock the boot loader it won't let me flash a RUU. But if you could upload the one you got to work that would be amazing none that I find work even with redownloading them
ps I hate that spider....

If the person is htc dev unlock they need to flash a kernal via fastboot for the phone to boot. That's more than likely the reason they are bootlooping. There is a thread in android development about how to flash via htc dev unlock. I would have them read that and proceed.

TheHeffNerr said:
Friend sent me his phone after trying to update to CM and it's getting stuck on the HTC White boot screen. Not sure if it is rooted or not, but was in the processes of rooting when it broke.
Phone is:
HTCDev unlocked
S-On
HBOOT-0.98.0000
RAIDO-1.09.01.0312
Phone will not:
Boot into recovery - HTC White screen
Boot normally - HTC White screen
Update with stock RUU - Bar on the right side fills up and goes back to normal bootloader screen.
Update new recovery - States it takes it but gets stuck on HTC white screen.
ADB Will not show device with "adb devices"
"fastboot oem lock" "FAILED (status read failed (Unknown error)) - "fastboot devices" does find device.
Factory reset - locks up bootloader.
"fastboot clear cache" runs for 30+ minutes phone is unresponsive.
That is about the only information I have any one got any ideas besides use it for a personal safety device and throw it at people?
Click to expand...
Click to collapse
go to bootloader and flash your kernel (stock kernel/custom kernel )
you can get it from your rom.zip
the command would be
fastboot flash boot boot.img
hehehehe i answered after 3 years ! im sure youve solved the problem !

[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.