Develop Bugs

Desire won't boot into recovery or OS, Bootload & Fastboot works

I don't know what I did wrong. After downloading a moddet statusbar vor Oxygen 0.2 I wanted to reboot into recovery and it took me very long. It freezed. After pulling the battery and setting it back in and pushing the power button my desire vibrated in 3 short intervals.
Since that I can't boot into the os or into recovery. Only thing that is working is the bootloader and the fastboot.
First thing I tryed is to flash (with fastboot) a new recovery but nothing changed. still it freezes at the splash screen.
I also downloaded official o2 rom from their homepage. But I think they want me to run the .exe while in android. A error comes up and tells me that it can't find a phone.
official htc roms don't work too. one told me that I'm not allowed to install this particular rom and an other official rom keeps exiting with error code: 170 telling me that the usb connection couldn't be established or something like this.
is there something else I can try?
I googled and searched the board. Tryed to boot into recovery without microSD card too but still no success.
help

Unpack the Rom and get the image out of the file...
Rename it to pb99img.zip dump only that on the root of your sdcard and boot into hboot .
T i d y .

Or just look on shiped roms for an 02 pb99img.zip and download then rename
T i d y .

Thank you so much. I already tryed this with 3 different pb99img images and had always the same error (CID). One of them was a o2 uk rom. So I gave up on trying it this way. But I didn't know that it could be extracted from every rom.
Now I think every thing is working again. Thank you.

Oh well ... I destroyed it again. Like I said I was able to install official o2 rom and everything was working again. After that I wanted to root it with unrevoked 3.21 but it freezed at "waiting for reboot". So I had to pull the battery once again.
But now I can't even enter bootloader. Only a screen pops up with htc in the middle and with four ! in every corner of the display.
Tryed to install official o2 rom again. It can find it and starts installing but at the end of the installation it stops with an error:
error [110]: error while opening data. Tryed it 3 times but always the same.

This might work for you
WAIT, BEFORE YOU START, CREATE A GOLDCARD. IT IS VERY NECESSARY. THINGS WILL GO WRONG IF YOU DONT.
EDIT: YOU MUST BE ABLE TO BOOT GO TO THE BOOTLOADER MENU.
Firstly, download this file. http://dl.dropbox.com/u/13240777/Desire Downgrade.ZIP
Extract the files.
Run the win-down.bat file.
Follow on screen instructions.
After the process is completed, Head to the root of your SD card and check if there is a file named P99***IMG (FORGOT THE EXACT NAME BUT IT SHOULD BE SOMETHING LIKE THIS) there should be one.
Secondly, disconnect your phone and turn it off.
After that boot up your phone while pressing the volume down button and the power button.
The bootloader should be checking for files after awhile and once it found the file that is supposed to be in the root of your sd card, press the volume up button (NOT EXACTLY SURE, SHOULD BE THE ONE THAT SAYS YES AND CONTINUE)
It should be writing files to your phone. and replaces everything. E.G: HBOOT, RECOVERY,RADIO and such.
It should be writing files successfully and then it would ask you to reboot. Continue with the reboot and you should be having your Desire back to stock. Perfect.
PLEASE KEEP IN MIND THAT THERE ARE RISKS INVOLVED LIKE FAILURE OF WRITING TO THE HBOOT. PLEASE REMEMBER TO FOLLOW INSTRUCTIONS. MAINLY, DO NOT BLAME ME FOR ANYTHING THAT GOES WRONG.
FINALLY, YOU SHOULD BE READING EVERYTHING UP TO HERE AND THAT YOU MUST HAVE A GOLDCARD (A GOLD SD CARD)
Hope this helps you and please ask if you have further questions. PM me if the questions cannot be answered here. Good Luck

You have to have a working Goldcard and be able to access HBOOT to do the above

Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.

Peikko said:
Nevermind.
I send it to o2. Since I was able to install the official RUU once I think they will take care of it.
What happend is:
For some reason I wasn't able to boot my phone. Recovery wasn't working too. Only thing that was working was Bootloader and Fastboot.
Just to sum up what I tryed:
Installing new recovery didn't help. I was able to install official o2 RUU and everything was working. But I lost my root. I think it had HBoot 0.930001
So I wanted to root it again with unrevoked 3.21
It started well and rebootet one or two times. But at the thirt reboot attempt it juft freezed and nothing was happening. I don't know what I did wrong?
is unrevoked 3.21 really able to root a phone with hboot 0.930001?
As I said ... if faild and after that I couldn't even enter Bootloader or Fastboot.
So I send it to o2 and hope they fix it.
But now I am really scared to root it again. If it fails again ... what will they think if I send it after 3 days again to them.
Click to expand...
Click to collapse
Well lad you had USB brick, easy to fix.There is a thread on this thing.

I am having similar problem described.
Currently I can get into Fastboot, and have tried reflashing recovery but still boot loop.
What should I do now?

please help my desire break
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.

Hi,
I have the same problem and getting pretty desperate now.
Only FASTBOOT and BOOTLOADER works.
I have clockwork recovery installed but it wont boot into recovery. It just gets stuck on the white boot screen.
I can't copy PB99IMG.zip or any other zip file because I can't access the phone through usb. I tried:
adb push PBIMG99.zip /
error: device not found
Is my phone useless now? As good as a brick?

try pack it in some tolietpaper put it in to the freezer fore 5 min an try again

jalal.arkat said:
my desire wont work into recovery and os only work in fastboot and hboot.
i am root desire and install custom rom arabic after flash not boot up,usb work into only charge, but not work lcd
i am install recovery clock work mod slcd on recovery clockwork mod 2.5.0.7 and break recovery.
now not work os and recovery.
please help me please.
BRAVO PVT3 SHIP S-ON
Hboot-0.93.0001
TOUCH PANEL-SYNT0101
RADIO-5.09.05.30-2
Aug 10 2010,17:52:52
please help me.
Click to expand...
Click to collapse
janielsen's idea seems crazy but give it a try..
put it in the freezer for few minutes then take it out
and then try to get into recovery mode..
you'll be able to do that
if you see a triangle with ! mark at the center that means it's a serious hardware issue and we can't do anything about that you have to send it to htc service center

Ha, funnily enough I did try the freezer thing but that didn't work either. What did work was booting into fast boot, connecting the usb and flashing with an official RUU in windows.
The phone is still stuffed!!!
It now has an official htc rom, no root, no mods, nothing... just stock!
But whenever it has to do a bit more processing like viewing a complex web page with flash, playing a game, downloading from the market it resets itself. Why?
I am starting to think it's a hardware problem but I need confirmation. I tried different roms but I get the same result. Has anyone has the same experience???

well i have sent my phone in fore repare the trick whit the freezer is only so u can unroot it so they cant see that it has bien rooted
the problem is that the cpu is getting to hot

Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.

yes u have warrenty because htc can see by the imei when the garanty is running out
they will replace the mainboard

FreshNClean said:
Hey janielsen,
I had a feeling it was a hardware problem, because it only resets when it's doing a lot of processing.
But what can they do? Replace the CPU? Did they say how much it costs?
I bought my phone second hand so I don't have warranty.
Click to expand...
Click to collapse
i thit also buy my second hand an didtn have the warrantypapper
but they said that i still have the 2 year warrenty so my is in fore repair
i shut get it back this week

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

[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] stuck on logo, please suggest

i just completely got lost here in incredible forums
have one phone here and it stock on htcincredible logo, phone goes to hboot ( it is S-ON, HBOOT-0.92.0000, radio 2.15.10.07.07) , recovery and stuff, but i cant find a stock firmware, some topics have broken links
tried this one PB31IMG_3.26.605.1_RUU.zip, but it says "Main Version is older! Update Fail!" i believe this file is too old
what is the solution? which firmware should i flash to recover it
thanks

vladvertigo said:
i just completely got lost here in incredible forums
have one phone here and it stock on htcincredible logo, phone goes to hboot ( it is S-ON, HBOOT-0.92.0000, radio 2.15.10.07.07) , recovery and stuff, but i cant find a stock firmware, some topics have broken links
tried this one PB31IMG_3.26.605.1_RUU.zip, but it says "Main Version is older! Update Fail!" i believe this file is too old
what is the solution? which firmware should i flash to recover it
thanks
Click to expand...
Click to collapse
Try this PB31IMG.zip
http://www.mediafire.com/?1ovb6959r9qyg6w

flashed with no errors, but still stuck on htc incredible logo,
tried to do factory reset getting this result (see pic)

vladvertigo said:
flashed with no errors, but still stuck on htc incredible logo,
tried to do factory reset getting this result (see pic)
Click to expand...
Click to collapse
It seems like you might have a bad SD card. Do you have any spare SDs lying around that you could try out? by the way have you been trying to flash these updates through recovery, because they are designed to be flashed in hboot. I thought you were using hboot to flash based on the language used but from the picture you loaded it looks like stock recovery if I am correct. If you have been trying to flash these files through recovery try again using hboot but I suspect you were doing it right the first time. If that is the case, I would do like I suggested above and try using an alternate sd card. I can't promise that will fix the problem but based on the fact that recovery is unable to mount /sdcard it seems like it is a hardware problem.

no, i flashed trough hboot and device did not boot
after that i tried to do hardreset in recovery
i will try another card, i have 64gb on me right now, dont know if it will work :laugh:

vladvertigo said:
no, i flashed trough hboot and device did not boot
after that i tried to do hardreset in recovery
i will try another card, i have 64gb on me right now, dont know if it will work :laugh:
Click to expand...
Click to collapse
Okay, Let me know how it goes!

Have you tried reflashing recovery? Or flashing to stock or amon ra recovery and then back to cwm.

now what...lol
nschiwy said:
Try this PB31IMG.zip
http://www.mediafire.com/?1ovb6959r9qyg6w
Click to expand...
Click to collapse
I had the same problem...flashed PM31IMg file in hboot and it went all the way though the set up steps ..when it finished asked to reboot i said yes and then it didnt boot,,,pulled battery started phone goes to HTC splash vibrate then goes black...nothing else...Anyone with any ideals on what ,where i can go with this...lol...thanks

ufish2 said:
I had the same problem...flashed PM31IMg file in hboot and it went all the way though the set up steps ..when it finished asked to reboot i said yes and then it didnt boot,,,pulled battery started phone goes to HTC splash vibrate then goes black...nothing else...Anyone with any ideals on what ,where i can go with this...lol...thanks
Click to expand...
Click to collapse
If you can still get to hboot, try doing another ruu. http://pvillecomp.com/?page_id=22

[SOLVED] Bootloop with no access to recovery (S-OFF)

SOLVED. THE PHONE IS BROKEN AKA HARDWARE FAILURE
Hi,
My old Desire had been sitting in my desk for about a year since i bought myself a Galaxy S2. Today, I decided to try it out. Charged the battery first and then tried to boot it. Well, I got stuck in the splash screen. The phone had been working normally the last time i used it (maybe 6 months ago?) so i thought it was weird. Then I tried to boot it into recovery, and got again stuck in the splash screen. HBOOT came up normally but after pressing the recovery button the phone just made the boot vibration multiple times and then was stuck in the splash screen.
What I have:
- Alpharev S-OFF HBOOT: bravo_alphaspl-oxygenr2.img
- Oxygen rom (don't remember the version but i have the zip on my computer): update-oxygen-2.1.6-signed.zip
- My current HBOOT screen shows the following:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
- AFAIK the phone is the older AMOLED version (if that matters)
- I have a working ADB
- I dont have a goldcard
What I did after noticing the problem:
1. Read the sticky which told me to reflash my recovery.
2. Flashed the CWM 2.5.0.7 recovery via Android flasher. The program said it was successful but my phone was in a bootloop again without access to recovery.
3. Flashed the Amon Ra recovery via Android flasher. The program again said it was successful but the bootloop persisted.
4. Flashed both of the recoveries (one at time of course) via the adb fastboot command. Again, it was supposed to be successful, but the phone STILL was in the bootloop.
I thought the sticky explained my situation perfectly but apparently this is not the case
I have also a RUU lying around:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
But I was hesitant to use it as I have the custom Alpharev HBOOT which might cause problems.
So what should I do now? I appreciate all advice.

Re: Bootloop with no access to recovery (S-OFF)
In my sig you'll find a thread with how to install 4ext recovery through pb99img. Check it out.

I DL'd the PB99IMG.zip file for the recovery and put it on my SD by moving the SD to my other phone and connecting it to my PC.
However, when the HBOOT searches for the PB99IMG.zip, it only says "No Image!".

Re: Bootloop with no access to recovery (S-OFF)
Are you sure you didn't put it in any folder?
Then, again in my sig, you'll find a partitioning guide. The first part of the guide will help you install a recovery. Try it.

Yes, I put it right in the root of the sd card.
The partitioning thread in your sig has a few methods of installing the recovery. But i have already tried them and for some reason they fail. I have now tried the Android flasher method, the ADB + Fastboot method and the PB99IMG.zip method. I have no clue why these should fail like i have described.
EDIT: Looks like I cannot run the RUU either. It says it failed to detect the device. What on earth could be going on when EVERY possible way of reinstalling the recovery fails? I was starting to think that maybe there was something wrong with my USB connection/drivers or ADB so I made a test and flashed another alpharev HBOOT (their bravo stock one: bravo_alphaspl.img) and the flashing procedure worked. So at least my ADB is working. Still no idea why the PB99IMG.zip just won't work... looks like my phone defies all these guides available here.

Update:
I downloaded the 2.3 GB RUU from the sticky topic. Suprisingly enough I could run it, it detected my device and went throught the whole RUU process without a single error. I booted the phone - and was again stuck in a bootloop. Went to HBOOT, chose recovery (the RUU should have flashed the stock recovery) but no, I could not get into the recovery. Instead the phone was again stuck in a bootloop. So I still cannot get into the recovery. The only thing that changed was the splash screen I was stuck on... (I had a custom splash, now it's the stock one)
I then formatted my SD, put the 4ext recovery PB99IMG.zip there and booted into HBOOT. This time It found the PB99IMG.zip. It asked if I wanted to update, I pressed yes and it went through it without any error. When it asked if i wanted to reboot, i pressed no, navigated into recovery and pressed the power button. This should have taken me to the 4ext recovery i just flashed successfully. And guess what? Bootloop again...
So after all this, I still do not have access to the recovery. I just get the bootloop every time. I've whacked around with android phones (mostly Galaxy S2 though) quite a lot but this far have never seen such a persistent problem which just evades all (for other people) working attempts to fix it. The procedures work exactly as described and give me no errors, but in the end the issue still persists: I cannot access the recovery because of the bootloop.
I was starting to wonder if it could be hardware failure causing this? Just a wild guess but the phone has been sitting in my desk for almost a year... I didn't change anything in the software. The only thing that comes to my mind is that the memory where the recovery and rom are stored is somehow corrupt. This would explain why I cannot get into the recovery even though i have reflashed it successfully multiple times. I also can change my HBOOT and splash screen.
Does anyone have any ideas left?

Re: Bootloop with no access to recovery (S-OFF)
Are you s-on now?

Yep,
At the moment i'm S-ON with the 2.3 RUU from your sig. Bootloader is 1.02.0001. I flashed the RUU from the PB99IMG. No errors. Still cannot get to recovery.
I then opened the phone and removed the mainboard but i could not see any damage at all. No burns, marks of water damage etc.

Re: Bootloop with no access to recovery (S-OFF)
As weird as it sounds, try putting the phone in the freezer without the battery for 10 minutes, then try to boot.

You are pretty good, man.
CASE CLOSED
Explanation: after putting the phone into the freezer for some time, I tried to boot. It booted normally to the ROM. Wifi worked, I could use internet, setup my settings etc. After 10 minutes the phone rebooted into a bootloop. This proves that the problem always was a hardware one, and this is why any software fixes couldn't solve the issue. Because i don't have a freezer in my pocket I can safely say the phone is broken and I can throw it away.
Thank you!