I'm running Fresh 3.3.0.1 on an EVO and when I do a factory reset and clear all cache then try to install any ROM from a zip, my phone goes into a constant boot loop. I've downloaded the Fresh ROM twice thinking it was corrupt, I've used Clockwork and RA but neither works. The only way to get the phone running again is to restore the Nandroid backup. I'm afraid when a newer version of Fresh comes out, or I want to flash a different ROM I won't be able to. This problem did not used to happen, and I've installed so many programs I wouldn't know where to start eliminating. Can someone shed any light on my problem. I would love some suggestions please.
Related
i recently updated to froyo for evo 4g but as i noticed it started reboot frequently.... i tried clearing everything and still as it loads back up it still does it i tried eferything and this thing just keeps restarting... i tried restoring my old nand backup still .... i searched everywhere and still no solution.... please i need help desperatly!!!!!
what rom are you using? did you change kernals? do you overclock?
I am assumign you are rooted since you said you restored an old nandroid.
did you do a full wipe before upgrading if you did which recovery did you use?
If you used clockwork recovery you may try using Amon RA and wipe with ti and reflash.
i was told to wipe dev. cache and wipe factory reset and take the battery out put it back in 15 secs or 30 and it should work...did the trick for a while but once im getting all my setting how i want it with my contacts and my apps downloading.... it starts the problem all over... SMH....
i used nandriod to recover...when all other failed i was told to use clear storage....so now everytime i turn my phone on i have 2.2 but it restarts the phone for no reason...how do i use amon ra and wipe with ti? i think i havent tried that....and im using build 3.36.651.6 (Rooted) Odexed rom....
i really need some help with this anybody got a related post with a solution or a fix for this my phone still turning off and on...
Flash the eng-PC36IMG zip in bootloader, then restore.
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.
I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.
Any idea's?
I'm entirely stumped.
Start over
Nand recovery then root again. Find a stable rom. There are tons that float to the top of the forum. I'm on Damage Control 3.5, works great.
Tried to Nand, It error's out and won't restore.
Like I said, DC 3.5 is what gave me the trouble to begin with, at least thats when my troubles started.
My phones gone completely unstable..and at the moment, unusable.
Also, be patient. After a flash, it may take a while for it to load. You seem overly anxious, by your post. I've flashed 30x and probably only bootlooped twice and those were Fresh's 3rd to last rom.
I let it sit there for 10 minutes saying fresh 1000x over a couple times, pretty sure I'm not being impatient.
battery is now dead.
Full wipe
Are you wiping everything? Dalvik wipe, user data wipe, cache wipe? Can you get back to recovery? How did you root?
Yes I can get into recovery, yes I'm wiping everything.
I used Simpleroot to get Root.
Rerun
I would try to re-run the second button in simple root to unlock nand. It doesn't hurt to re-run. You really shouldn't have a problem recovering nand if that process worked the first time. If you can't get that to run, you might want to adb it, but since you simplerooted your phone, you might have to read up on that. Once you take care of nandroid, you are good to go.
Nand is giving me an error that backup cannot be found <even tho I most definitely did Nand backup my stable setup> so IDK what fixing nand would do even if it is broken if it cant find the restore files. erm..
End of the Road
I suggest you do a forum search for more opinions/solutions. You are not the only one on here that has been through this. I did a quick search and found a handful of threads with this exact same topic.
Alanmw86 said:
Hey guys, was running the latest fresh when I decided to wipe via clockwork and try out DC, DC gave me bootloop at 4G screen, so I wiped via clockwork and tried again, same result.
I picked up the Amon Ra recovery and wiped and tried flashing via that, same result, tried again, same result so I figured I'd wipe it and flash back to Fresh, well now I've wiped using Amon Ra and tried to flash Fresh and I'm bootlooping as well.
Any idea's?
I'm entirely stumped.
Click to expand...
Click to collapse
How did you install a different recovery if your stuck in a boot loop? As for your problem, i had a bootloop before on freshz's older rom, and some of the solutions i had read werent working, i ended up booting into recovery, and rewiping without doing a reinstall of the rom, and it solved my problem, also have read that pulling the battery has gotten some people out of there loops. Hope this helps
I pulled the battery booted into recovery and wiped the rom, flash an alternate, booted up, changed to Amon and started over, was the one time I was able to get it to boot threw, after that same results.. I couldn't explain how it managed to boot up just one time either.
I just managed to nearly brick my buddy's Droid X, and I just wanted to see if there was an easier way to do what I had to go through.
Going from Liberty 2.0 to DarkSlide, did a nandroid backup, wiped data, cache, dalvik, the usual... But, darkslide didn't install right for some reason, and it hung on the bootlogo. After waiting 15 minutes, I finally pulled the battery, expecting Clockwork to come up, and I could restore. Instead, I had the normal recovery, with the four options to wipe data, wipe cache, install update.zip, or reboot.
Now, besides the point that I just had to sieve through several update.zip's, including a bad md5 sum or two, running RSD Lite and loading a stock Rom and re-rooting. This was my first time ever going through all this crazy process... I'm just wondering:
If a ROM goes wrong in installing, is there a way to avoid all the insanity I just went through, or am I running the risk of going through all that every time I flash a new ROM?
Haha same here. I almost bricked my phone but o was able to restore it with the original RUU to downgrade and reset to factory settings. By doing that I just had a spare sd card to format and re-rooted. Once that was done ROM Manager did the rest with restoring my last backed up working ROM on my original sd card.
Its hard to come by one click rooting tools.
Sent from my HTC Inspire 4G
XDA Developers Premium App
homescrub said:
I almost bricked my phone but o was able to restore it with the original RUU to downgrade and reset to factory settings. By doing that I just had a spare sd card to format and re-rooted.
Click to expand...
Click to collapse
How would I go about that?
hmm If you would flash Clockwork into recovery section of you phone and not using Rom Manager to boot into update.zip (ClockWork), you woudln't have such problems
Everytime I do a update and it fails it still boots into the Bootloader and my beloved ClockWork Mod v3 with the ability to flash another CustomRom with works.
Greetins
About a month ago I decided I wanted to try out Synergy ROM for my EVO, so I went for God Mode and everything has been running fine...until now. I had installed a kernel earlier this week for underclocking and such, but decided today that I didn't really use it as much as I though so I decided to reflash the HTC stock 4.24. I just did that about 10 minutes ago, I made a backup in case something went wrong and I backed up all my apps/texts as well. It flashed, rebooted...then it got stuck in a boot loop. So I pulled the battery and booted up into the bootloader to go into recovery...when I found every time I hit recovery it would just restart to the bootloader. So I'm not really sure if there is anyway to restore my backup or any other way to boot into recovery. Am I just screwed? Or can I use ADB to boot into recovery/restore my backup? This is sort of my first question post so...If you need any more information just ask.
Thanks,
Suprgamr232
If your phone is still going into bootloops. Connect your phone to your computer and go to adb and type in adb reboot recovery. There you can revert back into a nandroid backup. Hope this helps
Not to be rude, but you didn't read the entire post did you? I can't access my recovery and AFAIK adb doesn't work while it's in a bootloop. Also, I don't think adb recognizes my device when it's in the bootloader either.
Hey im just trying to help, Maybe some how you lost your recovery? Maybe try reflashing your recovery from the bootloader, make sure it named pc36img.zip. See if you can access your recovery after that. What recovery are you using btw, clockworkmod or amon ra? and did you wipe your cache and dalvik cache files through recovery before you flashed your kernel?
If you can access your recovery after reflashing it, Try wiping those in recovery and rebooting, see if it boots into your rom. If not and you still get a boot loop but you can access recovery do a full wipe and reflash your rom or try restoring a nandroid
Not gonna argue with you, so I'll let it slide...I'm using clockworkmod and I did wipe my cache and dalvik cache. ATM I haven't been able to get a hold of a new recovery img for some reason...can never get it to download 100%, will try it soon hopefully.
There's no need to argue Ive heard that clockworkmod doesnt always completely wipe the cache and dalvik maybe try using amon ra this time around http://forum.xda-developers.com/showthread.php?t=705026
Cant hurt to try it. hope you can get it working for ya, gl
Still stuck in the bootloop. I tried restoring but that didn't help. I tried reinstalling the ROM and the kernel I used before and no change, I don't really want to wipe my phone and try it but...I guess it might turn out that way. Before I do though I was wondering if there is anything else I should try?
suprgamr232 said:
Still stuck in the bootloop. I tried restoring but that didn't help. I tried reinstalling the ROM and the kernel I used before and no change, I don't really want to wipe my phone and try it but...I guess it might turn out that way. Before I do though I was wondering if there is anything else I should try?
Click to expand...
Click to collapse
You're gona have to do a full wipe [ factory/data, cache, and dalvik ] , reflash your rom, kernel, ect. Once you sign in, boot, ect, you can use titanium backup to restore your apps and data, NOT system settings.
Alrighty then. Did that and everything seems to be working fine...A little disappointed but as long as I have my phone! Thanks for your help!
suprgamr232 said:
Alrighty then. Did that and everything seems to be working fine...A little disappointed but as long as I have my phone! Thanks for your help!
Click to expand...
Click to collapse
Glad its working again.
Hello,
I was flashing the latest version of AOKP using TWRP, and the update failed. I verified the MD5 hash before attempting the flash, but figured I'd the file had gotten corrupt somehow. So I went to reboot my phone, and it hung on the boot loader screen. I Pulled the battery and tired again, but same result. So I booted back into TWRP, restored from the backup I took just prior to attempting the flash, and upon booting my phone went directly to the Setup Wizard. I rebooted, tried the restore again, but same result. I went through the wizard, and confirmed my phone had factory reset (Note, I didn't manually wipe anything).
Does anyone know what might cause this, and if I have any way to restore the backup I have? I was going from AOKP JB Builld 3 to 4, so I didn't take a Titanium Backup first. I've been using CWM since I got my GNex in January and have never had an issue (I've switched ROMs several times, and done many backup.restores with CWM. So i'd like to think I know what I'm doing ). This is the first time I've tried out TWRP, and everything seemed to go smoothly (Except for the failed flash).
Any help would be greatly appreciated. I've been searching around and haven't found anyone else reporting this.
Not sure why it factory reset but if you still have cwm back ups flash cwm and restore one of those. Factory reset isn't a bad thing though staying fresh is the best way to start a new ROM. I don't recommend restoring anything.
Sent from my Galaxy Nexus using xda premium