Hello everyone !
I have a little problem with my HTC Desire since two days. I used the tool Alpharev to get S-OFF and flashed with the file 'bravo_alphaspl-cm7.img'. Since then, he gets stuck on the splash screen.
I followed many tutorials, tried with different ROM (including CM7 InsertCoin), made a Goldcard (he was branded), formatted and formatted again the SD card, created ext4 partition, flashed with the others hboot proposed by Alpharev ... but nothing helped.
With some ROM, it starts, but remains finally locked before I could do anything ...
I thought return back to the original ROM and remove the root, but I'm afraid it still doesn't work and no longer be able to do anything.
Does someone have an idea to help me? It's really becoming annoying
(Sorry for the english mistakes, but I'm far from a perfect bilingual. )
I think the first thing to try would be to return your hboot to stock bravo via the alpharev process.
Then retry flashing rom of choice.
If that doesn't work, try to restore your last backup after returning to stock bravo hboot.
I returned back to stock bravo. With the Nandroid back-up it makes a bootloop and with another ROM, it gets stuck too: (
I finally tried to return to the original ROM. Now when I turn it on (in recovery or not), it displays a black screen with a white 'HTC' and a point exlcamation in every corner of the screen. If I plug the USB port and I unplugged it, it goes into recovery, but with only one option: 'RUU' and I can't do anything ...
It was not the best idea of the week
I guess nobody is able to help me this time ?
It finally started installing the "RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00.32U_5.09.00.20_release_140022_signed" !
Thank you for those who have read my problem and sought a solution! : D
Related
Hey all,
I decided to root my HTC Desire today, via unrevoked3; everything went alright.
I later installed ClockworkMod Recovery, and flashed the ClockworkMod recovery image. I tried to make a backup from inside the ClockworkMod Recovery app (ROM Manager). The phone reset, loaded the ClockworkMod recovery image, but then failed backing up, complaining about "failed signature verification". (I should mention at this point that my phone could still boot up.)
I searched the forums a bit, and someone suggested to just select backup/restore from within recovery mode. I did so, and the backup completed.
After that, the phone reset... but now, it sits at the white HTC screen and won't go any further. Every 30 seconds or so, the screen goes black for a bit, then the white HTC screen comes back (phone restarts, I assume). Also, I should mention that I can still get into the bootloader & recovery mode (Clockwork), if that helps.
I wouldn't mind reimaging my phone via one of the Desire RUU packages, as I was planning to upgrade my rom/radio anyways...
Anyone have any suggestions? I'm rather new to the android community, so help a newbie out!
Thanks in advance.
If I were you I would first try to clear data/restore to factory settings from recovery.
Failing that I would restore the backup you made.
If that didn't work just flash a custom rom (clear data again).
If all of that still fails flash the RUU.
Hey, thanks for the info & reply.
I ended up doing a factory wipe, and flashing a custom rom (MoDaCo)
Everything seems to be working order... thanks again!
I have a question / issue somewhat related to this. I have the USCC version of the HTC Desire. I have it rooted via unrevoked forever. I created a goldcard following the guide on modaco. I placed the rom I was trying to flash over to on the root of the SD card (leeDrOiD in this case). The rom flashes over successfully, but it will never boot up. It stallsl at the white HTC screen. It will never go past this. I did a wipe before hand as well. I have hboot 0.98.0000. That's the only thing I can think of that is different from the other forums I've seen. My radio is 2.05.10.06.29. I have tried several other roms as well. I can easily flash back to a backup I made of the stock rom, but I really want to use a custom one to get to 2.2. Any help is greatly appreciated.
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
Hey mates,
would be cool if you could help me to understand the connection between recovery and flashed rom...
This is why I'm asking: I rooted my desire a couple of weeks ago (by applying the unrevoked method). Since then I flashed a couple of custom roms. I wasnt very happy because the most roms caused my mobile phone to crash. I thought it was because a broken sd card therefore i bought a new one today. Sometimes when my phone crashed I wasnt even able to enter recovery anymore. And sometimes it did just nothing... I couldnt even enter hboot (it just didnt boot - like it was briked - only the charging led was on when i plugged the charger in). In this case I had to remove the battery a couple of times or plug in the charger. Usually I needed to do this many times. This is btw. why I'm fed up with custom roms but maybe its just my mistake. And now finally my question:
Why can I enter recovery sometimes and sometimes not? Does this depend on the rom? Why do I have to remove the battery etc. to make it run?
I know flashed back to the rom I of which I created a backup after root. But it seems that my phone is more unstable since then (even if its just my rooted stock rom)
Thank you for your answers...
What rom are you on? Maybe your recovery is a bit messed, have you tried reflashing it? Btw, s-on right?
If your not able to get to your hboot then there is something wrong with your phone. It will most likely be able to do with your hardware. You can use an ruu to restore everything back to factory default. You could then root again and see if that will help. But it does look like to be a hardware/corruption issue.
Swyped...
Your Desire maybe being one of the new PVT4 new nand would might cause this. I know that the latest version of unrevoked and Clockwork recovery can't be used to root the PVT4 new nand. I had that problem and the fix for me was to use an earlier version of unrevoked and flash Amon Ra recovery instead. There's a thread around the forums regarding this. Check first if your Desire is of the new PVT4 model. Can't post the link but there's a thread that explains how you can check if your Desire is PVT4 new nand. Would post the link but can't yet, but a quick search should take you to it.
hey guys, thank you very much for your fast answers. The desire is s-on. I'll try an official ruu. If I'm brave enough I'll root again . The strange thing is that I can enter recovery but not always. A hardware issue would be awful. I'll let you know how it went. I hope it is ok to just use ruu to update a rooted rom. It flashes a new recovey too, doesnt it?
Ok, i tried to use ruu to unroot my device. It told me that my bootloader was not compatible and canceled flashing. But it also broke my rom. I couldnt boot the system anymore and i couldnt boot into recovery. I dowloaded a ruu image (with my radio) to flash it via hboot. Everything seemed to go fine but after the first restart i'm stucking with an update sign (i guess its the recovery menu) - a mobile with green arrowrs. I think its frozen. Do i need to do anything else?
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Lovebongo said:
Hey, just to keep you up to date. I successfully unrooted my device by flashing a stock ruu. Now its booting (but not always) but it often freezes after a few minutes after the boot progress. I guess I'm going to send it back.
Thank you all for your help anyway.
Click to expand...
Click to collapse
Yeah best to send it back, it sounds more like a fault with the device
I had a few problems with my HTC Desire he won't start after I did an update of Insertcoin (I did this update, like every other update).
So I thought that I had to re-root my phone.. Bad idea I think.
Now my sd-card is formatted so I don't have my gold-card anymore
and I can't boot my phone.
When I boot it, in the top right and left corner and bottem left and right corner there is the debugging logo (so the triangle with the '!') and in the middle of the screen HTC logo.
EDIT: I also cannot go to the bootloader or fastboot I can only see the screen above nothing else.
EDIT2: I tried and original RUU but I don't know which one I had to use..
I don't know what to do, so please help me!
Sounds like you've flashed the wrong RUU. This happened to me, I've got a Vodafone Desire, flashing the newest HTC Europe RUU restored my HBOOT but still didn't boot (so you could try that I guess), so I used fastboot to flash recovery and then a new ROM. Good luck to you.
Oh yeah also, if you've installed a custom HBOOT and then tried to use a RUU it may be the cause of the problem since it wouldn't have been able to flash the system partition. Although it doesn't appear as to be working, I tried to flash the stock HBOOT through fastboot when my phone was like that, and after the RUU finished installing I did have the stock alpharev one and not my cm7 one.. Just something that might come in useful.
I've tried this solution here but it doesn't work for me.
Yes, it's working again.
This is the solution.
I downloaded this RUU and install it and now it works
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!