I am currently using AR Recovery on my evo. Everything was working fine until two weeks ago when I got major random reboots. I have since fixed the reboots, but one problem remains. After one use of the recovery I am no longer able to get back to it. If I attempt the various means, ie reboot recovery from adb, from cyanogen reboot, from ROM manager and from the bootloader, my phone continuously boots the splash screen in a loop. When this happens I have tried to reinstall the recovery by;
-fastboot
-adb
-ROM Manager
-terminal emulator
These all have given me mixed results as the problem happens after only a single use. One odd thing to note is that one time any reboot recovery command would take me to fatboot, even via the bootloader.
HTC EVO 002
Cyanogen 6.1 stable
Baseband 2.15.00.09.01
Stock kernel
Sorry for the amount of info to take in, but I really need the help. Thanks
Related
Been installing custom roms for a while now.
Whenever i try to install a new rom ( tried several ones, next sense, leedroid , defrost) i get stuck on the first white boot screen with the green htc screen.
Iv used full wipe, cache, wiped sd partition, formatted sd card, different sd card.
I can install an older version of next sense rom, but that is about all i can do.
im on bootloader v0.8, used the latest version of clockwork mod ( have tried with several versions) iv tried booting with the sd card out.
iv tried so many different times with different variations but none have been successful other than the nextsense v4.0 that i can boot to, or an nandroid back up of nextsense v4.0.
Any help?
I had the same this morning after fixing a recovery boot problem (re-pushing the reboot file to the system/bin/ directory on the device).
I resolved the hanging white screen problem by rebooting (via volume down + power button) into recovery with Clockwork Mod (v2.5.0.7 for Desire) and manually reflashed (N.B. without wipe!) the already installed ROM (I had upgraded to Nextsense 6.0 earlier that morning without difficulty, so reflashed that version).
Maybe this helps, but sounds like you may have already passed this station...
Good luck!
After that my Desire booted up normally.
Edit: Bootloader is v0.75
Can you get any response from running
#adb logcat
??
If it sits there saying "waiting for decice" for ages then yeah, something isn't right (possibly a bad flash of boot parition), but if you get anything, even a bootloop of sorts, the output may help narrow down whats going on!
I'm stuck here too. After I flash a custom ROM it just sits there after booting for the first time. I've tried so many ROMs, but I haven't even gotten to see a single one, yet!
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
A clean flash of cm 6.1.2 should not give you any issues. Are you using a custom kernel?
ald3n3 said:
I charge my phone overnight everynight. There are times when i wake up in the morning my phone is just stuck on the splash screen. What could be the problem?
-I'm Running on CM6.1.1
-I have a customize splash screen and boot animation
-I used unrevoked root and unrevoked s-off
-I noticed that the random reboot happened when wifi is on (noticed this twice, not sure about the other times)
-And this started to happen (from what i remember) when i tried to flash something over my recovery (toast or something like that, i can't remember i was just following a tutorial for me to able to put a new splash screen. It was for fast reboot to work) then i got stuck on a loop in bootloader. Then i flashed CM6.1.1 to get an image.
Help please?
Click to expand...
Click to collapse
Random reboots are usually always caused by a custom kernel that your phone does not like.. I could be wrong but that is my experience anyway...
i had the same exact thing except i actually had 6.1.2 clean with no custom stuff. the only thing custom would be the galaxy s theme i put on it.
i would be trying to go to sleep and i would feel my phone vibrate and then i noticed its rebooting, the rebooting is pretty frequent.
i wiped and restored my original backup and installed all the new stuff (radio/wimax/etc.., except hboot)
right now im gonna install a clean 6.1.2 and see how it goes
No custom kernel. Maybe i just need to manually flash cm6 so i can wipe data 3 or 4 times. I kinda don't trust the rom manager and clockwork work recovery method i feel like it doesnt really wipe everything clean before installing.
Sent from my PC36100 using XDA App
How do you un-install a custom ROM
I installed a custom ROM and now (a month or two later) I'm getting reboot after reboot. How do I get rid of the custom ROM?
Also, what does it mean when the phone reboots, then vibrates 5 times and locks up?
To get rid of the custom rom just do wipe through recovery...
And the the locking up? I have no clue why that is... sorry
Sent from my PC36100 using XDA App
Hi, guys.
Have a problem with my Evo 4G.
It's S-OFF, rooted, and have custom recovery (made my unrevoked). There was also MIUI (different versions) as a firmware for more than a year.
Few days ago while laying on the table Evo just became rebooting in a cycle. After battery remove nothing changed. Just showing HTC Evo logo and then vibrate one time and reboot to the same logo and so on.
I've tried to wipe the phone from a recovery, phone just halted until battery remove. Evo just lied for about a week, than i tried to do wipe once more and that worked and after reboot everything was working, but in a few days reboots came over again.
But now i can't even enter the recovery mode. I choose "Recovery" in bootloader and getting Logo + vibrate again and again.
Is that a death for my Evo or i can try some methods to revive it?
PS: there were no programs installations prior to reboots happen. Phone just lied on the table for a few hours or at night.
Updated hboot to the latest 2.18. unlocked it.
Flashed clockworkmod with bootloader (PC36IMG method), also amon ra with "fastboot recovery". With no luck. Can't enter the recovery.
Tried installing RUU, everything fine... except it doesn't boot anyway...
Any other way to try?
I've tried:
1) Remove battery then insert and wait until it charges, then try to power on.
2) Update hboot and re-root it (it was S-OFF, but still made lock off)
3) Re-write recovery, tried clockworkmod and amon ra with hboot update and with fastboot
4) installed RUU (and it passed without any troubles)
5) "Clear storage" from hboot
what else can i try to revive my Evo ?
While I haven't seen this in awhile, you can do a search and see that this isn't a totally rare experience. It's possible you have the same issue other phones have had with bad partitions (Not on the SDCard). If so, it's basically a brick
HipKat said:
While I haven't seen this in awhile, you can do a search and see that this isn't a totally rare experience. It's possible you have the same issue other phones have had with bad partitions (Not on the SDCard). If so, it's basically a brick
Click to expand...
Click to collapse
Yeah, it does sound a lot like the infamous bootloop of death.
You may not have any options. Unless you want to send it to me. I doubt I can do anything with it, but I'm always willing to try.
----------------------
Current Device: HTC EVO 4G LTE | ROM: Viper4G 1.0.0 | Kernel: 3.0.8-AwesomeSauce1.2
I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
ViaraiX said:
I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
Click to expand...
Click to collapse
try to reflash stock kernel, maybe it will be ok again, in worst case you'll have to wipe
Today I received my GT-N7105 back from the repairers after having the screen replaced, or maybe the whole phone replaced as for some reason my phone was un-rooted! God knows why they would have to do that to replace the screen.
So I've just rooted again and installed ROM Manager and attempted to flash CWM recovery, according to the app it went fine, but when trying to boot to recovery using the ROM Manager app and the volume up + home + power method I'm met with the stock recovery.
I have tried using Odin to install CWM recovery but the device freezes on the boot screen every time I try, and freezes there when I take the battery out and attempt to boot the phone again. So I have to root again just to get the device to turn on.
Its been years since I flashed a custom recovery so tried following a couple guides, but no luck.
I want to flash CyanogenMod to the device but cant do this without CWM (I've never attempted to use TWRP, better the devil you know!)
I have noticed Knox has appeared on my device, but I have not activated it as I hear this causes issues with rooting, and the reason I think this is a different device altogether is the flash counter was at 0 when first rooted this one, but I must have pushed this p to at least 15 before it went in for the repair.
Am I missing something? Please don't make me have to use the bloated to the heavens stock Android!
Thanks in advance and will be thanking any help.