Develop Bugs

Recovery affected by rom?

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

[Q] HELP frozen bootscreen / bootloader

Hey,
I was wondering if anyone could help me out with this issue I have. I have a rooted Evo, with my latest ROM being Fresh Evo 4.0.0.4 Beta by flipzmode. I was having some issues with the rom, so I was attempting to reflash the rom, however its beta 3 (one update older) version, first. I went through ROM Manager and did a complete backup, then chose install from SD Card and checked the boxes for Wipe Dalvik cache and the other check for wipe cache / data (i forget exactly what it says). ROM manager took over from there, rebooting into recovery and installing the rom, atleast as i thought it as doing. Once it was said and done, I now am at my problem area. It will not boot past the white htc EVO 4G screen. I've given it anywhere from 20-40 minutes to load. I've tried pulling the battery as well. I've even attempted to get into recovery by going into my hboot bootloader. However there, i have ANOTHER problem...I can't pick any of the available options. Its as if my volume buttons just don't work. When I have my SD card loaded and I go into hboot, it does some kinda search which yields five results of No Image Found! it then returns to the main menu where again, I can't scroll up or down the list. It says s-off so I assume that means I'm still rooted. I'm not an expert by any means, and overall I'd say I'm a noob to this stuff, but I am trying to figure it all out. If anyone can help me out with what to do to get my phone running again, I'd appreciate it greatly.
Thanks!

Hmmmm, that's odd. You can try putting a PC36IMG of the RUU on the root of your SD card. If you used unrevoked, you'll stay s-off, so all you'll need to do is reflash recovery to flash a rom or restore from a backup. However, you need to use your volume buttons to agree to the flash in the bootloader. In the odd case that it just won't navigate the menu, but the volume buttons are fine, it may still receive the confirmation from the button that you want to flash the PC36IMG.
If that's the case , download this file: http://goo-inside.me/supersonic/sto...15.00.11.19_NV_1.90_release_161482_signed.zip and rename it to PC36IMG, don't add a zip to the end because it's already there. Put it on the root of your SD card and boot into the bootloader, when it asks you to update, *try* to agree with the volume up button. If it works, hopefully that'll fix your problem.
It's not the greatest fix, and the chance of it working isn't all that high, but it's all I've got.
Oh, and obviously your volume buttons are fine if you can get into the bootloader, unless a button is stuck.
(from... Evo/MIUI/Tapatalk)

And don't use ROM Manager.....

Thanks plainjane,
Just a couple more quick details before I try to do what you said, I'm not sure which root method was used for me. My cousin did it for me and with my phone mia, I have no way to find out. Does that effect anything? Also, i'm pretty sure i've used ClockWorkMod recovery, as i remember flashing it through ROM manager a few days ago. I've realized that the volume buttons do work, but only when to accept the update for the pc36img..I read about that before so I tried putting one that I believe was for ClockWorkMod recovery on my sd card, but I wasnt sure if that was the right pc36img file i need. So I can replace that with the one you have linked me with. Will running that cause any problems with the addtional details? I just don't want to end up permanently bricking my phone, so I'd rather cover all my bases.
Thanks again!

I would do 2 things: 1 flash a new recovery, specifically amon_RA and then I would flash a rooted ODEXED stock rom.
Click on the word "amon_RA" above and download the PC36IMG.zip file and place it on the root of your SD card (not in any folder). Make sure there is NO OTHER FILE with that same name on the root of your card. Turn off your device and then boot it to the bootloader screen. After a pause, the file should be autodetected and you should be prompted to install. follow the easy instructions to install. Afterwards, you should be able to go into recovery and flash a rom. Download the rooted stock rom by clicking on "rooted ODEXED stock rom" above. Afterwards, put it on your SD card and flash it from recovery. Once you've successfully flashed a rom and if you're set on re-using ClockWorkMod recovery, you can always download the ROM Manager app and have it install ClockWorkMod recovery for you, but I recommend you stay with amon_RA.

!
plainjane said:
If that's the case , download this file and rename it to PC36IMG, don't add a zip to the end because it's already there. Put it on the root of your SD card and boot into the bootloader, when it asks you to update, *try* to agree with the volume up button. If it works, hopefully that'll fix your problem.
Click to expand...
Click to collapse
Thank you, thank you, thank you plainjane! I decided to just go for it and try your method, it took care of my phone not being able to boot-up. I'm now at what seems like a stock rom.
dougjamal said:
I would do 2 things: 1 flash a new recovery, specifically amon_RA and then I would flash a rooted ODEXED stock rom.
Click to expand...
Click to collapse
Thanks for your suggestion dougjamal, I actually attempted your method first, but I still wasn't able to select the recovery option from the hboot bootloader main screen after running the PC36IMG, so I couldnt flash the rom.
So, I still have a couple of the same problems. I still can't choose the recovery option from the bootloader menu, I've tried multiple times to use a PC36IMG for ClockWorkMod recovery and Amon_ra. Also, while using the actual phone, my power button seems to not work. It doesnt turn of the screen, nor does longpressing it allow me to shut off the phone. If it helps to diagnose the problem, since i'm pretty sure up until today my power button still worked, whenever I pull my battery and put it back in, the phone boots automatically without me pressing the power button. Anyone have any suggestions?
Otherwise, is there anyway for me to just go back to complete stock again and attempt rooting the phone again, and starting completely from scratch?
Thanks again for everyone's help!

Boot into the bootloader screen and see if you're still rooted (S-OFF). If it displays S-ON then you will not be able to make changes to your device.
posting & replying via the XDA Premium app.

dougjamal said:
Boot into the bootloader screen and see if you're still rooted (S-OFF). If it displays S-ON then you will not be able to make changes to your device.
Click to expand...
Click to collapse
Yes, it still says S-OFF. I don't understand why I can't scroll through the menu nor turn off my screen though. Even when it times out, I can't turn the display back on. I have to plug in a charger.

[Q] Phone possibly bricked but it might be saveable!

Hi,
My first phone was rooted and I rooted my second too so I am confident rooting them however my second phone which had been rooted for a while had a space issue on SD card so I cleared out a few things which unfourtunatley included all the backup files ....
It worked fine afterwards but didnt let me change rom (using rom manager) so I just left it in working order for a few months until I wanted to reflash a new rom (as I am sure most people do every few months)
When it didnt let me, I tried to unroot and root options using superoneclick and unrevoked3 however, unrevoked 3 just stayed on "running root" and superoneclick got so far and crashed. When I go into the bootloader, it says something about some filed missing (think might be some nbh files).
At the moment, when normally turning the phone on, it stays on the screen with the pink circle, the first boot screen.
I have tried updating it using the RUU but it takes a long time and then says "use the correct rom for your device" which I am, this method just boots my phone and goes to a htc logo.
I can also get into the bootloader but when I apply update.zip, it says it has failed and something about files not existing/step 7 failure.
The thing is, I can get to fast boot and I am sure there is a way via ADB to force a new image (such as a cyanogen recovery image) on to the device.
Can anyone tell me how to push an image to the phone without using the RUU (as this didnt work for me)??
Maybe my phone is just bricked
Thank you very much!!

It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)

Thanks but I do not have another Desire...

Any card reader

yeah, I got a card reader laying around somewhere, if not ill go get one in Tesco, what where you thinking?

bortak said:
It. Is. Not. Bricked.
You can only push files onto the phone through fastboot if you are S-OFF (are you?)
Have you tried to enter recovery? boot into Bootloader (vol down + power) and then select recovery. Does it work?
no?
Then you need a goldcard. Make one with your working Desire, stick it in your misbehaving one, and then run the latest WWE RUU (link on my guide, check #resources)
Click to expand...
Click to collapse
Hi Bortak, I am having similair problems with my phone sticking on the pink circle screen. I cant seem to load a recovery file from Bootloader. Will I need to make a Gold Card, my phone is s-off.
thanks mate

if phone is S-OFF go to my guide, look at advanced boot problems S-OFF.

SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!

Mugube said:
SOLVED WOOHOO!
Thank you to all who helped but I managed to fix it my own way.
For anyone still having trouble...
I still had the cyanogen mod bootloader soo all I did was download the latest cyanogen mod rom and apply it (you can mount sd card from cm bootloader) and after a hairy minute, it finally booted up!
Click to expand...
Click to collapse
#facepalm#
Translation: I flashed another ROM because my other one didn't boot.

[Q] HTC Desire GSM stuck in "fastboot"

Hello forum!
Yesterday when I found out that the new CWM Recovery Touch had been announced I just had to try it. Since I didnt wanna spend $ 2 for it, I was going to flash it in just as ive done with CM 7.1 and GAPPS. When i was going to enter the Recovery Mode via HBOOT (Power button and Volume up) I chose "Recovery" by pressing volume down and power. This resulted in a .5 second AlphaRev splashscreen flash and I didnt enter Recovery, I was stuck in Fastboot. Ive read many threads becuse I wanted the new feature, but that didnt resolve in any success. Im S-OFFd and im using the newest CWM Recovery (5.0.2.0) FYI. Ive tried to Hardreset, turn off and take out the battery and put it back in (and even use my charger during the HBOOT process) but no luck so far. This is why im turning to you guys becuse im kinda new to this things. I hope maybe someone have some experiance in this kind of errors and might help me, becuse I dont know what to do. Thank you in advance.
/ Kaoukan
Edit: Watched some videos, am I able to use the Unrevoked 3 tool again (since i rooted and flashed cwm at first with it) to "reflash" the recovery so it could work? Or am I going to brick my phone?

Check bortak's troubleshooting guide.
Sent from Sandvold's ICS using Transparent XDA App

Fix
Ive got this all fixed now, it seems that the CWM 5.x was still a beta and it messed up my recovery, a simple downgrade back to 2.5.0.7 made some magic and set my device back into recovery on demand.

Also have this problem on v5.006.
I'm trying to downgrade now.

[ATT] Probably bricked my device

So the old ROM I was on (a super outdated Android Revolution) needed to be updated because my battery was draining a lot and I figured I would update everything. Apparently I flashed a bad or wrong version of TWRP, so I can't get into recovery. It just sits there trying to get into recovery but it keeps failing. Then I tried using MultiRom recovery and installing that through the app in the play store. Now my phone won't go into recovery and just boot loops. I can get into the HBOOT menu but I can't get into recovery or boot the device at all. Does anyone have any ideas to get a working recovery or working ROM? I already backed up my pictures and videos and stuff, but I forgot to transfer my titaniumbackup files I've been trying to look around and see how to fix it but I don't want to do something that will cause more damage than I've already done. I did all this to update my firmware so that I can use the newer ROMs. Anyway if anyone has any ideas I'm all ears.
Thanks in advance.

You didn't mention whether or not you are S-off and/or bootloader unlocked.
Since you already have a custom ROM, you must have unlocked your bootloader at some point, so if it is STILL unlocked, just reflash the correct recovery from fastboot. If it is not, unlock it with HTCdev first, then reflash the correct recovery.
Alternately, if you just want the phone fixed, you can always re-run the AT&T RUU - though that will trash any files you have on the phone.

Yeah that's what I did yesterday thanks for the response!