Develop Bugs

Oh Boy...Huge Error...Help Requested

Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.

fisheric1 said:
Okay. I've search around and haven't found anything yet.
I recently got a new evo and rooted with the Unrevoked 3.0 beta RC2 yesterday. All was going well until I tried to upgrade to the CM 6.1.2 this morning. Google apps wasn't installed so I flashed the zip which put me in to a boot loop with Clockwork.
It was giving me an error when I tried to restore the backup. I tried to flash pc36img.zip and now whenever I go into recovery I am in RA-evo-v1.8 which I am unfamiliar with. I've tried installing other ROMs via this recovery but the prcess is aborted each time.
Any help would be more than appreciated. I am literally stuck.
Click to expand...
Click to collapse
Need any and all information about your phone. I also notice that you are new. The dev section isnt for Q/A there is an entire section dedicated to solving these issues. Please remember that next time. Keeps things cleaner. So please gather anything you can about your phone. Method, Hboot, Version, Radio, Anything that can help anyone here identify something.

Do you have the rom in the root of the usb card? If so try full data wipe and installing the room see if it boots up.

Thanks for the quick reply. Will remember. Desperation has gotten the better of me. I will move over to Q/A if you prefer.
HBOOT-2.10 0001
RADIO - 2.15
Initially rooted via Unrevoked 3 beta RC2 yesterday.

if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)

T3hPWN said:
if your able to boot up into a rom download Rom manager and select flash clockworkMod recovery or flash alternate recovery thats prob gonna be the easiest fastest fix (considering it works)
Click to expand...
Click to collapse
I agree with this method... the best way to determine the recovery to use would be to go into the terminal and type
Code:
cat /proc/mtd
if you see "400000" then you need to get the clockwork v3.0.0.2 that supports this phone partion layout. If you see "20000" then you should get amon_ra 1,8 from here:
http://forum.xda-developers.com/showthread.php?t=705026
The information I gathered was from this post:
http://forum.xda-developers.com/showthread.php?t=894331
Making sure you have the correct recovery is the first step. Once that is done create a nandroid and save it somewhere to ensure that the wimax partition is saved.

You have to flash the modified version of Amon_ra found in Zikronix thread. You can find my thread that points to it or just search for hboot 2.10 and follow the instructions in that rooting thread. It seems you're already rooted so just flashing the recovery is probably all you will need.

I haven't used unrevoked, and I know there are several versions. But I have seen others who have used unrevoked and couldn't flash anything bc evidently the method they used to root didn't install the flash_image file on their phone.
I know that installing flash_image fixed being able to flash for some people who rooted with unrevoked.
This issue came up and I was able to help some people, if you check near the end of fastRX8 thread. But I was only able help point the right direction, they figured out the rest of the way. The OP there has the flash_image file and tells you what terminal commands to install it.
I don't know how for you to check if you gave it or not, as I can see mine on sd card cuz I put it there when I rooted.
Beyond this suggestion, lithid can probably help much better than I.
But def post your hardware version, root method, and hboot version (you see that when you go into bootloader and read the top line.
Sent from my PC36100 using XDA App

Wow, sorry, theres been several posts since I started tying. Looks like these guys got it for ya
Sent from my PC36100 using XDA App

Was there a resolution for your problem? If so please post so anyone searching in the future can resolve there problem quickly.

you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.

dkdude36 said:
you should flash the pc36img.zip located at the bottom of zikronix's root thread. good luck. just put it on the root of ur sdcard named as pc36img.zip and boot into bootloader. accept the update, and say no to the reboot. then pick recovery, and flash a rom. you need to stay with this recovery if it works for you.
Click to expand...
Click to collapse
You mean the modified amon ra recovery image?

exactly...

dkdude36 said:
exactly...
Click to expand...
Click to collapse
Ya it worked for someone else in the Amon_Ra Clockwork thread here is the link.
zikronix said:
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to.
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
Click to expand...
Click to collapse
OP flash the PC36IMG in the bootloader to load this new recovery, then you can go into your new recovery and flash a new rom.

i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?

defjef123 said:
i just rooted my evo with the unrevoked beta.hboot 2.02 it installed clockwork and through that i switchted to the aman ra after that i did a nand backup, powered off my phone and when i turned it back on it was stuck in the bootloader loop. the only thing that eventually worked was installing the sprintlovers pc36img. that got my phone working again. just tried to nand backup again and the same thing happened. does this mean that i need to flash that broken recovery?
Click to expand...
Click to collapse
Were you restoring a backup or did you stuck on loop on a new rom flash?

i wasnt even trying to flash a rom yet. i was doing the very first nand backup so i could check some roms out. after the backup was complete it gave the option to power off so i did and when i turned my phone back on it was in the bootloader loop. so i went back to recovery, wiped everything, restored nand and i said it restored but when i rebooted it was back in the bootloader loop.so i just search around trying to get help but couldnt find much so i put sprintlovers since it boots up right when you turn your phone on. now it wouldnt even nand backup it said some error and was in the bootloader loop again so i just reinstalled sprintlovers, again

Try downloading an actual rom in zip format (not sprintlovers pc36img) and see if you can flash a new rom fresh. Make sure to wipe everything.
Try using Caulkings format all zip in recovery to wipe your caches.
http://www.mediafire.com/file/ikylelx99c49133/Calkulin's_FORMAT_ALL.zip

put in on my sd card turned my phone off to go into recovery and now my phone wont even turn on

it came on now. gonna try to wipe and flash that rom

Q: "Validation error: Backup CID is missing" Unrevoked issue

hboot 2.02
hardware 003
Software 3.30
I tried on 2 pcs without luck. Ihave double checked everything but no luck after numerous tries. I have rooted 2 other phones so this isnt my first root. Anyone else been able to get around this issue?
hmmm I booted into hboot and it says S-Off (although its not off) but there is no recovery.

Looks like im up!! My s was off so I manually backed uped my RSA keys just to be safe and proceeded to flash Amon_RA recovery PC36IMG.zip and then I flashed superuser zip and that got me where I needed to go.

bizdady said:
Looks like im up!! My s was off so I manually backed uped my RSA keys just to be safe and proceeded to flash Amon_RA recovery PC36IMG.zip and then I flashed superuser zip and that got me where I needed to go.
Click to expand...
Click to collapse
hey..
even iam experiencing same problem..
but i really could not get what you did to make it work.. lol
it would be of great help if you can help me with it.
hboot 0.93

So your s-off now when you boot into boot loader?
I just flashed the recovery and got back up manually with superuser and busy box. You can download superuser from the market or flash a zip as for busy box I installed through Titanium Backup.
I used this method to get my recovery fixed.
http://forum.xda-developers.com/showthread.php?t=829045
zikronix said:
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
==========================================
FIX BROKEN RECOVERY
This is really only needed if you rooted with one of the previos guides version 6 or lower or if you installed a different recovery like I told you not to. It installs amon_ra 2.2.1
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
================================================
Click to expand...
Click to collapse

is unrevoked CID issue fixed
Hi..could you fix this issue, I wish know how fix it but I only found really old post without solutions...thanks!!!........

[Q] HELP!my evo doesnt Start fully!

i flash CM7 savage rom and gapps and all seems normaly running a great rom but when i turn it off for a bit and then i turn it on...my evo doesnt start fully and its stuck on boot doesnt even let go to the recovery it restarts all over again ...i tried to clear the data or restart the bootloader...and the battery is charge so its not it ...can some one help me with this or any advice what i should do .... ????

Pulling the battery, waiting a couple minutes, and then holding vol+down and power doesn't allow you to access your bootloader?

yes it does but then i try recovery and it doesent work tho.. :/ and i already put the battery out its benn 24 hours like this...

I'm not entirely sure, then. I'm rather new myself, so I'm not too knowledgeable yet. Hopefully someone else with more knowledge will chime in soon.
DirtyShroomz should be perusing these forums right about now... anytime, buddy.

What kernel are you using...had similar problem with sense ROM due to a flashed kernel that didn't play well with custom ROM. You can try to reflash your recovery if you can find a flashable zip of it or a PC36100.IMG of it. Put on root of sdcard and flash PC36100.IMG through bootloader or flash zip through recovery. What does your recovery do when you access it...it wont let you reflash the ROM or what

ianmb said:
What kernel are you using...had similar problem with sense ROM due to a flashed kernel that didn't play well with custom ROM. You can try to reflash your recovery if you can find a flashable zip of it or a PC36100.IMG of it. Put on root of sdcard and flash PC36100.IMG through bootloader or flash zip through recovery. What does your recovery do when you access it...it wont let you reflash the ROM or what
Click to expand...
Click to collapse
PC36100.IMG? Don't you mean PC36IMG.zip?
jhonbra said:
yes it does but then i try recovery and it doesent work tho.. :/ and i already put the battery out its benn 24 hours like this...
Click to expand...
Click to collapse
Are you using Clockwork or Amon RA?

am using Clockwork tho

it only lets me go to the bootloader but doesent let me use the recovey it takes me back to the bootloader :/

jhonbra said:
i flash CM7 savage rom and gapps and all seems normaly running a great rom but when i turn it off for a bit and then i turn it on...my evo doesnt start fully and its stuck on boot doesnt even let go to the recovery it restarts all over again ...i tried to clear the data or restart the bootloader...and the battery is charge so its not it ...can some one help me with this or any advice what i should do .... ????
Click to expand...
Click to collapse
jhonbra said:
yes it does but then i try recovery and it doesent work tho.. :/ and i already put the battery out its benn 24 hours like this...
Click to expand...
Click to collapse
Please be a little more specific. When you say 'but then i try recovery, and it doesnt work tho', what doe you mean? Does it hang at the white 'htc evo 4g' screen (splash screen) or does it give you a black screen with a red triangle? When you get to the bootloader, it still shows that you are indeed S-off, correct? What happens when you pull the battery, and try to boot normally? Do you have any success? If so, download ROM manager from the market, and use that to reflash whichever recovery you were using, either clockwork or amon ra ( i suggest amon ra) If you are unable to boot into the rom at all, and you're unable to access your recovery, then the first thing to try is reflashing your recovery, using the bootloader. To do that, download the PC36IMG that I'll attatch. That is Amon Ra recovery, version 2.3. Download the zip file, make 100% sure that it's named exactly PC36IMG (capitals matter), and put it on the main directory of your sd card ( you'll need to either use an sd card adapter, and put it right into your computer, or put the sd card in a different phone to transfer the file) You may be able to access the sd card using hboot usb, I don't recall at the moment. Either way, get the file on your sd card somehow. Make sure it's named right, and not in any folders. Then put the sd card back in your phone, and boot into the bootloader. The bootloader should then scan and find the PC36IMG file, and ask you if you want to update. Select volume up to say yes. Once it's done flashing, from the bootloader, select 'recovery'. You should now boot into Amon Ra recovery. From that point, I'd suggest doing a complete wipe (data/factory reset, cache, dalvik cache), and then flashing Calkulin's Format all.zip (i'll attatch it) Once you're done wiping, then reflash the ROM and Gapps. Reboot your device, and you should boot into the ROM. Good luck.
EDIT: I just saw that you were using clockwork before. I don't have a PC36IMG of clockwork, so just use Amon Ra for now. It's a better recovery, but if you must go back to clockwork, once you're phone's back up and running, you can easily use ROM manager to select 'flash clockworkmod recovery' , and that'll get you back on clockwork. just please be sure not to attempt to restore a clockwork backup using Amon Ra. That's a no no. You need to use clockwork to restore a backup that was made by clockwork. Just so ya know.

ok first i flash CM7 savege rom! then i flash the gapps for the cm7 then everything was alright but then i just turn it off and turn it in again and the bootanimation come in stays there doesent go on and restars it self so i pull the battery off and put the bootloader so i can tried recovery but it Doesent let me in to the recovery ...nothing appears it just send me back to the bootloader again ...and YEs it still shows that you are indeed S-off...and no red triangle it just restarts again .. :/ but thanks for the help i gonna try to see if teh PC36IMG file like ur said and try to put it on the Sd card

jhonbra said:
ok first i flash CM7 savege rom! then i flash the gapps for the cm7 then everything was alright but then i just turn it off and turn it in again and the bootanimation come in stays there doesent go on and restars it self so i pull the battery off and put the bootloader so i can tried recovery but it Doesent let me in to the recovery ...nothing appears it just send me back to the bootloader again ...and YEs it still shows that you are indeed S-off...and no red triangle it just restarts again .. :/ but thanks for the help i gonna try to see if teh PC36IMG file like ur said and try to put it on the Sd card
Click to expand...
Click to collapse
Okay, thanks for clearing that up, I got the situation now. Yes, flashing the PC36IMG, following my previous instructions will give you a recovery back. Once you get recovery back, you'll be able to wipe everything and flash the rom again, starting over. Recovery is all you need man!

dude tahnk youuu veryyy muchhh mann that works like a charm now can enter to the recovery so i can flash my restore my files thanks man!

jhonbra said:
dude tahnk youuu veryyy muchhh mann that works like a charm now can enter to the recovery so i can flash my restore my files thanks man!
Click to expand...
Click to collapse
You're very welcome! I'm glad it worked. Now that you have recovery back, you'll be good to go. Just make sure to do full wipes before flashing roms, and I suggest sticking with Amon Ra instead of clockwork. Once you get the system running again, make a nandroid backup using Amon Ra, and make sure to check the 'wimax' box, to backup your RSA keys (you dont need to backup wimax every time, just be sure to keep a good backup around of it). Then you'll have a solid backup using Amon, because as I said before, as long as you stay with Amon Ra, your previous clockwork backups are useless.

I have a similar issue. EVO bootloops twice and then gets stuck at 4G and stays there. I am able to boot into bootloader. It has
HBOOT 2.02 S-ON.
RADIO-2.15.00.09.01
So far I have tried....
Fastboot USB
RUU 3.30
RUU 3.70
Took the sdcard out and put PC36IMG.ZIP for 3.30 and 3.70. HBOT scans it with the blue bar and does the "checking the zip" and then back to bootloader. Does not give me an option to update. Any suggestions? I need help.

soulassasin187 said:
I have a similar issue. EVO bootloops twice and then gets stuck at 4G and stays there. I am able to boot into bootloader. It has
HBOOT 2.02 S-ON.
RADIO-2.15.00.09.01
So far I have tried....
Fastboot USB
RUU 3.30
RUU 3.70
Took the sdcard out and put PC36IMG.ZIP for 3.30 and 3.70. HBOT scans it with the blue bar and does the "checking the zip" and then back to bootloader. Does not give me an option to update. Any suggestions? I need help.
Click to expand...
Click to collapse
Sorry, I didn't see your question before I went to bed last night. So you are trying to flash back to stock? That's your goal. I see you're already S on. So both of the RUU's that you tried failed on you? What happened when you tried to run the RUU, did it give you an error or what? Do you have HTC Sync installed? You only tried putting one PC36IMG on your sd card at a time right? From the way you described it, it kind of looks like you loaded both on the sd card at the same time, but I'm not sure if you can even do that. Anyways, I'd try downloading the PC36IMG from a different source, confirming that you have a good download, and trying again. THe bootloader should scan and ask you to update. The only time I've seen where it doesn't is if the PC36IMG is named incorrectly, if it's in a folder, if the file is corrupt, or if your sd card is corrupt. If you can't get the PC36IMG to work, I'd suggest formatting your sd card (back it up first) then loading just the PC36IMG on there, and try again. Good luck.

Thanks for seeing the question. Tried pretty much everything. I just want it to work thats all. Its never been rooted. Now I tried the RUU for 3.29, 3.30 and 3.70 and they all give me Error 132 Signarure Error. I ran the RUU by putting EVO in Fastboot. I tried formatting the SDCARD and individually putting the PC36IMG. It does loading with the blue bar on the side, then "checking the PC36IMG" and back to HBOOT. Never gives me an option to "volume up" to update. I have done the PC36IMG files on another EVO and they worked fine before. I have tried 2 different SDcards. I got the RUU from shippedroms and also from here on xda. I got all PC36IMG from here. Don't know what else to do.
k2buckley said:
Sorry, I didn't see your question before I went to bed last night. So you are trying to flash back to stock? That's your goal. I see you're already S on. So both of the RUU's that you tried failed on you? What happened when you tried to run the RUU, did it give you an error or what? Do you have HTC Sync installed? You only tried putting one PC36IMG on your sd card at a time right? From the way you described it, it kind of looks like you loaded both on the sd card at the same time, but I'm not sure if you can even do that. Anyways, I'd try downloading the PC36IMG from a different source, confirming that you have a good download, and trying again. THe bootloader should scan and ask you to update. The only time I've seen where it doesn't is if the PC36IMG is named incorrectly, if it's in a folder, if the file is corrupt, or if your sd card is corrupt. If you can't get the PC36IMG to work, I'd suggest formatting your sd card (back it up first) then loading just the PC36IMG on there, and try again. Good luck.
Click to expand...
Click to collapse

soulassasin187 said:
Thanks for seeing the question. Tried pretty much everything. I just want it to work thats all. Its never been rooted. Now I tried the RUU for 3.29, 3.30 and 3.70 and they all give me Error 132 Signarure Error. I ran the RUU by putting EVO in Fastboot. I tried formatting the SDCARD and individually putting the PC36IMG. It does loading with the blue bar on the side, then "checking the PC36IMG" and back to HBOOT. Never gives me an option to "volume up" to update. I have done the PC36IMG files on another EVO and they worked fine before. I have tried 2 different SDcards. I got the RUU from shippedroms and also from here on xda. I got all PC36IMG from here. Don't know what else to do.
Click to expand...
Click to collapse
So, you've never been rooted before? Everything was just working fine, and then suddenly it won't boot up? Just hangs at the 4g screen? Is that accurate? Were any changes made to your phone before this happened? Any unusual apps you added, changes you made, anything noteable at all? Or just 100% random out of the blue?
So you ran the RUU with the Evo in fastboot, what happened? Did the RUU appear to run successfully, or does it error out? Any info on what happens when you attempt the RUU would be great. Did you try downloading a PC36IMG or RUU from this thread yet? I have never had a problem with one from here. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu. Do you know what software version, radio version, and hboot version you currently had on your phone before it started acting up? Was it the most recent OTA, 3.70 software?
There is annother way to try to flash the PC36IMG using fastboot commands, which I've never done, so don't know the instructions off the top of my head. I'll post back when I find how to do that.
Are you sure you're not getting a bad download of the RUU's and PC36IMG? It's odd that your bootloader scans it, but doesn't ask you to update. That could be due to a corrupted file (bad download) Do you have a good internet connection when you're downloading the files?

The phone was never rooted. I bought it from someone. Practically brand new. No damage at all. I downloaded every single RUU and PC36IMG file from the link you mentioned but same thing happens. RUU ERRORS 132 and PC36IMG files scan and check out but no choice to press volume up for update. Hboot is2.02, radio is 2.15, s-on and the software version when I run the RUU says 3.30. I am stuck at this point. I can only get the phone to recognize fastboot. Help.....
k2buckley said:
So, you've never been rooted before? Everything was just working fine, and then suddenly it won't boot up? Just hangs at the 4g screen? Is that accurate? Were any changes made to your phone before this happened? Any unusual apps you added, changes you made, anything noteable at all? Or just 100% random out of the blue?
So you ran the RUU with the Evo in fastboot, what happened? Did the RUU appear to run successfully, or does it error out? Any info on what happens when you attempt the RUU would be great. Did you try downloading a PC36IMG or RUU from this thread yet? I have never had a problem with one from here. http://forum.xda-developers.com/showthread.php?t=884060&highlight=hboot-0.97+ruu. Do you know what software version, radio version, and hboot version you currently had on your phone before it started acting up? Was it the most recent OTA, 3.70 software?
There is annother way to try to flash the PC36IMG using fastboot commands, which I've never done, so don't know the instructions off the top of my head. I'll post back when I find how to do that.
Are you sure you're not getting a bad download of the RUU's and PC36IMG? It's odd that your bootloader scans it, but doesn't ask you to update. That could be due to a corrupted file (bad download) Do you have a good internet connection when you're downloading the files?
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

need Recovery for HBoot 93 SLCD

Hi,
I have a TELUS HTC Desire that was already rooted when I got it.
It has HBOOT 0.93
I didn't know that my phone was SLCD so when I used ROM Manager to flash recovery, it messed up my recovery.
If I go into hboot, and press down arrow to boot into recovery, I get the black screen with the little phone and the red triangle with the exclamation mark.
I was desperate enough to try the ClockworkMod Recovery for the HBOOT 0.83 (ClockworkMod Recovery v2.5.0.1 SLCD)
from hxxp://forum.xda-developers.com/showthread.php?t=748618
flashed that on with UnrEVOked but didn't work. Recovery is still messed up.
I googled and searched for a week to find something for HBOOT 0.93 but I never find anything. Everything is for 82, 83 and 92. There are other people who asked about 0.93 in other threads but there are never answers to them.
Does anyone know of a proper ClockwordMod recovery img or ANY recovery img I can flash for my HBOOT 0.93
My phone is already android 2.2 but i would really like to flash to LeeDroid
Should I reflash my phone with the RUU to get rid of any dmg done? The only thing i'm afraid of is that my phone will be unrooted because of the RUU reflash and I can't find a way to root it.
If it's not possible to use UnrEVOked or Rom Manager to install LeeDroid because of HBOOT 0.93, I'm willing to manually do it.
But will the LeeDroid flash properly onto my phone if it's HBoot 0.93?
Does the flashboot thing when i boot into the HBOOT work for installing custom ROMS if I can't get into recovery? I noticed it will load images...but not sure exactly what the fastboot thing is suppose to do.
Thanks!!

HBOOT 0.93 is not the problem, neither is your SLCD. Use fastboot to flash your recovery, I suggest use either AmonRa 2.0.1 or CWM 2.5.1.8.
CWM from ROM Manager isn't the best recovery for your HBoot as I think it flashes 2.5.0.7 which is no good on your HBoot.
You can't flash a ROM from fastboot, you need recovery. Once you've done that, LeeDrOiD will work fine on your setup, but I would suggest you study up a lot more before proceeding, for one thing, it's easy to find a lot of info on HBoot 0.93 on this forum, secondly, get to know fastboot etc as you needs to know this for when things go wrong with cheat/easy methods like ROM Manager.
Take your time, be confident you know what you are doing it before you do it, you don't want to brick your phone.

Both of you need to know quite a bit more, but especially the OP...
But no he can of course not flash an unsigned recovery from fastboot without being s-off, and from the sound of the first post I'm confident he's not.
ghalalb is right though when he states that this has nothing to do with your bootloader version or slcd, and i really can't imagine how you can get the simple instructions on here wrong, but please simply use unrevoked via usb. It comes preloaded with a perfectly fine recovery for you, and also i believe you should really reconsider the decision to hack your phone with this little knowledge on the subject.
Also 2.5.0.7 vs 2.5.1.8 has nothing to do with hboot versions.. Both will work fine if flashed correctly, but the problem with just making rom manager flash the recovery is, that it is not quite up to date, so it does not actually flash anything. It just downloads an update.zip file, which loads the recovery when flashed. This fixed the problem of not being able to flash a custom recovery back before unrevoked came around. And to correct you on another thing you got wrong, yes you can actually flash a zip file containing something like a rom from fastboot if you are s-off. It will probably just not work exactly the same way, as the recoveries does.

That's interesting that you say hboot version and slcd has nothing to do with the ClockworkMod when other threads are very specific about which clockworkmod version you should use depending on your hboot and if your phone is slcd or not.
Also last time I did an update to the phone, it just used the fastboot. Didn't go into recovery.
I followed the exact instructions for unrevoked but an error occurrs when it tries to unroot...All I wanted to do was flash the recovery and not unroot the phone since it's already unrooted. So probably that's why it was having problems. But the recovery was still messed up after unrevoked did it's work.
I wonder if part of the problem is because I'm using a test image and not the actual production image for the phone. Which is probably another reason why the phone was already unrooted.
I'll try to reflash my phone using the RUU for a production image and try Unrevoked again just so everything is clean from the start

Trust me it doesn't matter. The only problem was on slcd phones back when they first came out, where cwm didn't contain the drivers for the new screen.
That is why it says it's for 0.83, as back then 0.83 was equal to slcd and all amoled models had come with 0.75 or 0.80. But now after the newer updates everyone is on 0.93 or so, and all newer cwm recoveries will work for both amoled and slcd. So no there is not a specific recovery for every bootloader, and there is no way a flash from rom manager messed your recovery up, as it never flashes anything.
And i think you might need to slow down and think about what you are doing? Because you talk about unrooting with unrevoked, and unrevoked will probably try to root your phone If you use unrevoked correctly you will have it working fine.
Also you say last time you updatet it, it used fastboot? updatet it officially? As then there is a reason you have the stock recovery. But try using the ruu and then go back to rooting using unrevoked or just keep it stock, as it might not be a good idea trying something without knowing what it does.
edit: and the screen you get with the phone in a triangle with an exclamation mark doesn't mean anything is wrong. It's just the stock htc recovery... If you press vol-up+power(or vol-down+power i don't remember) when you see this screen, you get a simple menu, which lets you flash update.zip and erase data.

mortenmhp said:
edit: and the screen you get with the phone in a triangle with an exclamation mark doesn't mean anything is wrong. It's just the stock htc recovery... If you press vol-up+power(or vol-down+power i don't remember) when you see this screen, you get a simple menu, which lets you flash update.zip and erase data.
Click to expand...
Click to collapse
Thanks for your response I thought that the triangle screen was bad since I tried the volume stuff and I couldn't get to the screen.
But if that's the stock htc recovery, then that means the clockworkmod recovery wasn't flashed properly?
I will try the keys again when i get to the recovery state later.
Actually I was having problems with UnrEVOked because my phone was ALREADY rooted. So it was trying to do something that was already done which is probably why it failed. I only needed unrevoked to flash the recovery...I didn't need it to do anything else but the recovery.
What I have on my phone right now is not the official load. It has test keys and crap in it....
Anyways, I'll see if I can get into the recovery menu properly before doing the RUU flash to have a clean start.

Ok Unrevoked should work fine anyway though. It just flashes a recovery and the su binary plus the superuser app. So if you are rooted it will just overwrite them. Your problem is far more likely to be a driver problem.
I rooted the old way as well(the one only allowing test keys signed roms) and then i used fake flash from rom manager until alpharev s-off came along, and now i just flash everything but roms from fastboot, it's far easier.

driver problem?
I followed the unrevoked instructions and my computer recognizes the phone while it's in bootloader
i can also adb shell into it when it's just normally powered on etc
oh and to answer previous question, yes i updated to 2.2 using fastboot
i put IMG99.zip onto my sdcard
powered on while holding the volume down for fastboot
it went and found the image on my sd card and grabbed it...and asked if I wanted to update...and viola...2.2
my phone was...2.0 or 2.1 when i first got it i think...i forgot what it was before 2.2
that's why i asked if anyone just stuck a custom rom into their SD card and tried using fastboot before....seems like everyone these days use things like rom manager, unrevoked etc >_<
I would think that the fastboot would find the zip file and can unzip and load it just like how it did the testkey one i did before....but i thought i would ask before i tried....maybe i should wait next week until i'm at home and have sd card readers in case anything goes wrong so i can recover the phone easier lol

There is a reason why people don't do that.. When you flash that way via fastboot, it only allow zip files signed by HTC, if you are s-on, and those write everything on the system to stock, which means you lose root and custom/modified recovery.
You could potentially do it that way if you were s-off, but the bootloader flashing utility does not allow as sophisticated commands as the custom recovery does, so everything in the original roms is actually packed in .img files for every partition.

All good advice.
I offered mine as my Desire would not accept CWM 2.5.0.7 (to this day it doesn't), and it would only accept CWM 2.5.1.8 or AmonRa 2.0.1. (as they work on PVT4 with a 40000 page) As for unrevoked, the only version that works for my Desire is 3.2.1, the latest (which I think is 3.3.2) doesn't work on my Desire.
It seems the longer these phones are around, the more individualised rooting and recovery has become, so advice should maybe always come with a word of caution.
***this is what worked for my device***
TinyAggie, I hope you are getting there!

Yep new page size will require the modified cwm for it, but it still has nothing to do with hboot version. However the other recoveries should flash ok as well, they just won't work well for installing roms(gave some error), which he hasn't come to yet

ghalalb said:
All good advice.
I offered mine as my Desire would not accept CWM 2.5.0.7 (to this day it doesn't), and it would only accept CWM 2.5.1.8 or AmonRa 2.0.1. (as they work on PVT4 with a 40000 page) As for unrevoked, the only version that works for my Desire is 3.2.1, the latest (which I think is 3.3.2) doesn't work on my Desire.
It seems the longer these phones are around, the more individualised rooting and recovery has become, so advice should maybe always come with a word of caution.
***this is what worked for my device***
TinyAggie, I hope you are getting there!
Click to expand...
Click to collapse
I found the same thing that only unrevoked 3.2 would work with my device.
I finally managed to flash the custom rom and is what i did to make it all work >_< Maybe it'll help someone else
I started with a fresh official load by flashing the RUU.
Then I used unrevoked that you can download from their website
I still got an error. CID missing. I go searching for it and it seems like a common enough error that the unrevoked team had addressed it
Because of the error, it was not able to unroot and flash recovery properly. The only thing it did was s-off.
So 2 ways to get root/recovery on your phone
1. Manually....find a PB99IMG.ZIP file that has root in it and flash that, then you can either use rom manager to flash the recovery or do it manually as well.
I created my own PB99IMG.zip with the recovery image of clockworkmod for desire using the android info .txt file I had in my other PB99IMG that contained the root access. Put the PB99IMG.zip into your SD card, go to Flash boot and let it do it's magic.
2. Easier way, get unrevoked 3.2 ... There was a warning for using it. Apparently you should only use the 3.2 version if you get the CID error.
But with unrevoked 3.2 it will give you superuser and the recovery image without you doing anything so it's easier.
So after I finally got Root, I backed up my sd card onto my comp.
Then I partitioned my SD card using ROM manager.
Once that was done, i flashed into recovery to do a backup.
After that I tried using ROM manager to flash leedroid...
it looked ok but it never managed to get past the splash screen after 20mins so I pulled the battery and rebooted
Same problem so I decided to flash manually.
Went into recovery and cleared everything then flashed the rom from SD.
Now I'm on leedroid
So far it looks exactly the same as the stock rom. It has everything I need so I'm happy.
I hope this helps anyone with similar problems.
Sometimes you just can't take the easy way out and have to do things manually

[NEED HELP] Hopefully not bricked HTC Incredible with wrong ROM

Guys, please help!! Yesterday I was so hungry for some ice cream sandwich, that I accidentally tried to flash a rom for HTC Incredible S onto my HTC Incredible! Only after the install failed (used Rom Manager, and when it rebooted, it was saying something about missing pb31img.nmh or some weird extension like that) did i realize what i have done. However my phone was pretty much functional at that point. I tried booting into hboot and doing recovery, but whenever i selected any of the hboot options (clear storage, recovery, factory reset), it would just reboot back into hboot. But at this point i was still able to boot into my phone. I tried backing up from saved images using Rom Manager, but when it rebooted, it always gave the pb31img message. Then it just froze. When i pulled the battery and plugged it back in, the phone just got stuck at the HTC Incredible white screen and would not boot. I've been searching the forums long and hard, but it seems all solutions assume i need to be able to boot into the phone, or to be able to simply use hboot to recover. None of these seem to be viable options for me at the moment. Please help with any suggestions as I wanted to wait for the Tegra 3 phones to come out before upgrading!!

fastboot and adb require phone to be able to boot. my phone does not boot into anything besides hboot. and even in hboot, none of the functions work. i was able to format my sd card and copy an img of the proper rom on there, and when i go to hboot->fastboot, it says "loading pb31img.zip" and shows the blue status bar, then says parsing "pb31img.zip" but that takes a second and then it just goes back to the hboot screen without installing anything!! does this mean i'm totally SOL now?

You can use fastboot to flash a stock image. You do not need to be able to boot to use fastboot,fastboot is thru hboot.
http://android-dls.com/wiki/index.php?title=Fastboot#Fastboot_Commands
However if you can get into hboot (the screen with the PB31IMG.zip message), then you can just do an ruu thru hboot. It sounds like your missing or have a corrupt boot image. You need to download the PB31IMG.zip ruu file from here (http://pvillecomp.com/?page_id=22), place it on your sdcard in no folders and then reboot thr phone. Hboot will find the file and prompt you to press vol up to update. Once thats done press vol up to reboot. Your phone should boot now. You will have to reroot if you want.

cmlusco said:
You can use fastboot to flash a stock image. You do not need to be able to boot to use fastboot,fastboot is thru hboot.
However if you can get into hboot (the screen with the PB31IMG.zip message), then you can just do an ruu thru hboot. It sounds like your missing or have a corrupt boot image. You need to download the PB31IMG.zip ruu file from here , place it on your sdcard in no folders and then reboot thr phone. Hboot will find the file and prompt you to press vol up to update. Once thats done press vol up to reboot. Your phone should boot now. You will have to reroot if you want.
Click to expand...
Click to collapse
OMG!!! Thank you soooo much! I can't give you enough thanks, you have no idea! I don't know why this one worked and lots of other cwm img files and rom img files didn't though! And i tried using the fastboot command through the terminal from the computer to flash this same RUU file, but it was giving me problems. But when i put it on the sd card, it worked right away. Now i have a phone to wait out for the Tegra 3!

Glad i could help.

Everything I have read so far says NOT to do any of that through a ROM manager. Could that be why his attempts to install a stock recovery failed?

This really helped me in my situation. I think I had an old version of clockworkmod on my Incredible and it wouldn't let me flash things correctly so it got me stuck in a bootloop but than I flashed the Froyo RUU PB31IMG.zip in hboot and it got my phone working again. Now time to re-root. (I chose Froyo because if you want to re-root with gingerbread you have to downgrade to Froyo which is a hassle)

Your device can not really be bricked. Impossible if you know what you are doing . Revert back to old rom after booting into recovery or choose a simpler from.
Sent from my HTC Incredible S

emaninthenation said:
Now time to re-root. (I chose Froyo because if you want to re-root with gingerbread you have to downgrade to Froyo which is a hassle)
Click to expand...
Click to collapse
If you are s-off it does not matter whether you use the froyo or gingerbread ruu. That is the whole point of getting s-off, so that if an ota or anything else for that matter replaces the custom recovery with the stock recovery, you will still be s-off allowing you to flash the custom recovery right back without having to do all that unrevoked stuff again.