I am using the newest amon recovery. Everytime i try to restore a nandroid i save it gives me bootloops. I normally wipe everything twice and flash caulks format all zip. Is there something im doing wrong?
Sent from my PC36100 using XDA App
i would love to have this answer also...was getting the same thing happening to me, sumtimes bootloop off a hot restart...various roms, mysn, mik, virus, miui, didnt really matter which i was coming from or going too...
have since unrooted my phone and rerooted it just to see if sumthing was off...so far so good...would still like to have answers as to why though.
amon ra 2.3
latest radios
oo3 hardware
3.70
hboot .76 eng boot
Same here i rerooted and then reooted back and i still get the same result. Wonder if i am supposed flash the rom, then restore? On my hero i never had issues.
Amon ra 2.3
004 hw
Newest everything
Myns rls5
Ziggy nwest
Sent from my PC36100 using XDA App
Is your usb plugged in while either backing up or restoring? Have you tried loading a different version of amon?
U need to flash a kernel, nandroid dont save that
Sent from my SGH-T959 using XDA App
so your are saying flash the kernal first then restore nandroid restore?
Okay I just tried what you said and I still got bootloops. And my USB is never plugged in when i do a nandroid.
Something in the backup is giving you bootloops. Try completely wiping, the flashing a new rom.
You can review the recovery log too.
Sent from my PC36100 using XDA App
DEFINITIONOFREAL said:
U need to flash a kernel, nandroid dont save that
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes it does. Likely the issue is that a wipe is not being performed before restoring the data in the nandroid.
Sent from my PC36100 using Tapatalk
Garbage in, garbage out.
If your device was unstable when you backed it up, it will continue to be so after you restore.
Try a different Sd card. If your device continues to be unholy, revert back to a stock based rom or even RUU. If your issues persist, you likely have a hardware fault.
Basic troubleshooting 101...
Nandroids dont replace the kernel, do the nand then flash the kernel
Sent from my SGH-T959 using XDA App
i really need sum help...have posted here once before on this issue...i just flashed mik4.5 last nite...made a backup this am...flashed sum mods and made another nand backup this afternoon...needed a text message off the first nand backup so i wiped everything and started the nand restore...installed just fine and started to boot up just fine untill the boot animation stopped...then it started bootlooping...wth man...i have had my evo since it came out and been using amon ra since i started this adventure we call rooting...never have i had so many things go wrong with nand restore or backups...9 out of 10 backups i have made since 1.8 has become obsolete has not worked...please help...ty
Man I'm having bootloops all the time now ever since i updated the new combo radios and flashed myn RLS5. On sense with rls5 my phone reboots a lot kinda and with AOSP roms like MIUI my phone reboots like every 24 hours and goes on a bootloop. I can't figure out what's going on. Tried messaging some devs but they don't answer me
Did u run Calkulins Format All.zip?
Sent from my PC36100 using XDA App
LuvThyMetal said:
Man I'm having bootloops all the time now ever since i updated the new combo radios and flashed myn RLS5. On sense with rls5 my phone reboots a lot kinda and with AOSP roms like MIUI my phone reboots like every 24 hours and goes on a bootloop. I can't figure out what's going on. Tried messaging some devs but they don't answer me
Click to expand...
Click to collapse
When you switched roms, did you do a format data/calkulin's format all? doing either or should fix your bootlooping problem.
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
marcusva79 said:
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Same here bro. I've tried 3 different roms this weekend thinking it was just miui causing the problem but I actually got bootloops on all of them . This is weird
Sent from my PC36100 using XDA App
"Wipe everything", is that a factory restore/reset?
Cause that's what I do (factory reset).
Then the nand restore............
marcusva79 said:
I always use caulkins format all. Still get bootloops. Wipe everything, still get bootloops. I dont know what to somwtumes except star all over from scratch.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Are you flashing kernels over that?
Related
I am unable to flash any roms except cm6 ( I can also flash any nightlies. )
This is driving me crazy. I have tried to flash fresh 3.2 to no avail. I have also tried to install the new virus rom. I attempted to install the rooted version off the newest ota with the same results.
After each attempt the result is the same. It will just hang on the HTC evo 4g screen.
I have downloaded the roms a few times each to ensure they were completed correctly.
I have pulled the battery and waited.
I have deleted all data / dalvik / Cache several times in a row.
I have attempted to flash using a different version (earlier) of clockwork with the same results.
I even attempted to flash with RA recovery. Same results.
I am completely lost as to why I can only flash cm6 roms
Please let me know any suggestions.
Sent from my PC36100 using XDA App
From what I have read...................
You need to restore a 2.1 or a 2.2 rom you have, boot to that, then you can flash to a 2.2 rom.
You can't go from CM directly to another rom.
I am on 2.2
Sent from my PC36100 using XDA App
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Bielinsk said:
An HTC rom.
CM is not a typical ROM.
Restore your original backup, and try from there. If you don't have one, you may need to RUU
Click to expand...
Click to collapse
Ok, so basically I am going to unroot - reroot?
I just flashed from cm6 straight to baked snack directly with no problems. Not really helpful but you shouldnt need to flash to a stock rooted rom first. Note sometimes you have to wait a good 5 minutes for the htc screen to go away. Probably took about 5 when I moved from cm6 to snack.
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Defpdp said:
I just tried again, attempted to go to fresh. I let it sit for 10 minutes with no results.
Click to expand...
Click to collapse
I unrooted- rerooted with the same results, I cannot flash ANY roms other than Cm6 it seems, this is very frustrating..
Anyone else have any ideas at all??
Thanks!
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
crimeslunk said:
Try flashing a new recovery. If you're using the newest amon go back to the last one or vice versa. Or even move over to clockwork. But I would ask about that I know clockwork doesn't play well with cm6. This could get you in trouble but I guess you always go back to amon.
Click to expand...
Click to collapse
Nothing worked, tried going to different recoveries/versions. Nothing.
Anybody? Any advice?
if you flashed cm6 and have it working... its my understandung that you cqn not just go and flash a different rom. there is a process that needs to be followed.
but i have never and never will use cm6 so i could easily be talking from my rear.
Sent from my PC36100 using XDA App
I flash from cm6 to rooted stock rom when I need to update prl and stuff.
After you flash wipe dalvik and cache again I had that problem when flashing snap.
Im not sure if these don't help. Maybe you can send a tweet to cyanogen himself to get it resolved. If fix pst your findings
Sent from my PC36100 using XDA App
Re root and see what happens
Sent from my PC36100 using XDA App
Also check your kernel, you shouldnt have to flash anything but the rom you want when switching from cm6
Driving me crazy. Phone wont hang up!!! It reads 0.00 with green phone symbol. It stays like that for over a min then hangs up. Any ideas? I running cm7 nightys.?
Sent from my PC36100 using XDA Premium App
1st step, did you do anything before this happened? 2nd step, reflash the rom, remembering to wipe everything first.
sitlet said:
1st step, did you do anything before this happened? 2nd step, reflash the rom, remembering to wipe everything first.
Click to expand...
Click to collapse
No dident change any thing, it started doing this on the stable version of cm7 and it started acting up also with text messages not going through,so I flashed the nightys and its still giving hang up problems
Sent from my PC36100 using XDA Premium App
Did you wipe everything first? Did you flash a new kernal?
fierceeagle2003 said:
No dident change any thing, it started doing this on the stable version of cm7 and it started acting up also with text messages not going through,so I flashed the nightys and its still giving hang up problems
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
definitely a weird 'one-off' issue with your cell. But as everyone has already said, wipe and wipe everything. Use VRwipe or something similar and I HIGHLY recommend Amon RA Recovery as apposed to Clockwork recovery (in my opinion) as I have had zero issues after using RA.
Hope that helps
I searched but couldn't find this particular problem; any help would be greatly appreciated.
Over the last few days I've downloaded midnight 5.5 and the new Urban fury (each three times; 2 times from different computers and once from the phone) and everything I flash just hangs at the Samsung boot screen. I've odin'ed back to EC05 and tried, always wiped everything 3x....nothing is working.
I can restore a previous backup just fine but that's all that works. I'm on the EC05 modem but also tried with the EF02 and EF10 (?)...the update from 02 anyway. I'm using the purple nurple for recovery.
Any ideas because I'm fresh out. Thanks!
Sent from my SPH-D700 using XDA App
Did you odin to stock EC05 or just the modem?
Sent from my SPH-D700 using XDA App
I guess that part wasn't clear; I odin'ed the whole ROM and it switched me back to the EC05 modem in the process.
Sent from my SPH-D700 using XDA App
Aren't those EXT4 ROMs? You need to run the EXT4 conversion script first. CWM 3.1.0.1 does not convert for you like the older clockworks.
That's a good point. I'm not sure how that works but before the odin ordeal I was on EXT4 and tried wiping and flashing. After odin'ing I suppose it would switch back to RFS but how then does that handle my CWM restore as it was EXT4 when it was backed up? Does the restore change the file system as well?
Sent from my SPH-D700 using XDA App
Just to cover all of my bases I downloaded and flashed the RFS2EXT4.ZIP. I assume that it worked, at least it backed up and flashed to "complete" but after wiping and attempting to flash Midnight again it is still hanging at the Samsung screen..
Sent from my SPH-D700 using XDA App
anderson620 said:
Just to cover all of my bases I downloaded and flashed the RFS2EXT4.ZIP. I assume that it worked, at least it backed up and flashed to "complete" but after wiping and attempting to flash Midnight again it is still hanging at the Samsung screen..
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Restore your system to a working condition with no FCs, run the RFS2EXT4, don't wipe, flash Midnight. The problem with restoring a nand from EXT4 onto an RFS is the new CWM restores the kernel as well which would be EXT4 only. So anytime you need to restore from a Nand, choose advanced restore and restore data.
I tried re-flashing after getting back to a stable backup but still had no luck. I then downloaded Frankenstein ECO5OCE directly to the phone, wiped 3x and flashed it and it booted up with no problems. I'm still not sure what the problem was with the other two. It's hard to believe that all 6 were bad downloads. I think you're probably on to something with the file system train of thought.
Either way, I'll give this ROM a try for a while. Thanks for all your help.
per the 5.5 thread - Bonsai recovery works best with the 5.5 Midnight fixed. CW wasn't working so great for lots of people.
Thanks for pointing out the problems others were having. I actually was able to flash Frankenstein fine and SRF 1.2 fine today. At least I know that my phone's not jacked; I'll try Midnight again shortly I'm sure. I've always had good luck with Rob's ROMs. Thanks again everyone for the help.
Sent from my SPH-D700 using XDA App
I have been trying to hook a buddy of mine up with a new rom for his Evo, basically make it exactly like mine with the newest Fresh Rom. I rooted his phone with Revolutionary and it all went just fine, the phone is now rooted with Superuser successfully installed. I put the Fresh zip on his SD card, wiped everything as you are supposed to, and then flashed the zip. It flashes fine and boots up, loads to the lockscreen and setup, but then reboots and does the whole process again, basically a bootloop. I have tried various roms and kernels, wiped over and over again, redownloaded the file, etc., but nothing seems to work. Am I missing something?! I never had this issue installing this rom on my phone. Any help would be appreciated!
try using a different recovery
Something other than RA? What do you suggest? CWM is crap isn't it?
Sent from my PC36100 using XDA App
Give newer versions on CWM its work just fine for me. I never had a problem.
Sloth
I am skeptical that a different recovery will fix the problem, but I will give it a try and report back. Is there anything else anyone can come up with?
I had a really weird issue where I couldn't flash any of the Gingerbread roms a while back, and had flashed goodness knows how many since I bought my evo on launch day and rooted it day one when it was available.
Trying different recovery versions might help, but if it doesn't, I'd suggest to unroot it and start all over. Find a post in the dev section on unrooting, go back to the stock sprint rom, and start over.
I did that, and was then able to flash all gingerbread roms and get them to not bootloop.
I'm not the only one that was having the problem, but NO devs could/would help figure it out. Not even flipz. Give it a shot.
Thanks for the info, I will try to Recovery thing first and then do a full wipe out and start over from a stock rom. The weird thing about it is that this is the first time this phone has been rooted and the first attempt at flashing roms.
Just curious, how many times does it reboot?? Over and over and over, or are you pulling the battery after the first or send time?
Over and over
Sent from my PC36100 using XDA App
Try recovery and fast boot from there.
Sloth
I changed recoveries to clock work, and it did not make a difference. I continued to get the same boot loop as before with RA. I just wiped out the entire system, and went into the boot loader to unroot back to stock. I will report back my results once I am done
Sent from my PC36100 using XDA App
Either change you clockworkmod or try something else. Dam man that sucks.
Sent from my PC36100 using XDA App
SLB9884 said:
Either change you clockworkmod or try something else. Dam man that sucks.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Changing up the recovery did nothing to fix my problem. I unrooted his phone, regained s-on, flashed a stock rom and am starting over. I will report back my results.
Well damnit anyway, starting all over from scratch did nothing as well. Still get the same damn bootloop. WTF!?!? Anyone else have any other ideas?
I've read every post and I can't think of anything that would help. You think it's a software issue, like inside the phone itself might be bad?
Sent from my PC36100 using XDA App
Is this something that could be discovered on a logcat? I have never done one or know how they work, but would anyone be willing to diagnose the problem if I am able to get a logcat?
Damn that sucks. What your status. Did you fix the bootloop?
Sent from my PC36100 using XDA App
Still no fix discovered, any help on this would be greatly appreciated
Sent from my PC36100 using XDA App
What's interesting, is that this is the exact same boot loop problem I was having on my Evo when trying to flash any sense 3.0 rom.
Sent from my PC36100 using XDA App
Have you tried using / flashing any of the zips that are prepackaged " wipes " ?
Have you tried using TWRP recovery ?
I never had any problems while using RA but had numerous failed flashes with Clockwork.
TWRP has been stellar so far ... no failed flashes yet.
I'm sorry if this has been covered anywhere, but I searched and couldn't find it.
Here is my dilemma: Anytime I want to flash a new ROM on my phone now (Evo4G) and do the factory reset or even flash a format/wipe my files all stay intact. It doesn't matter what ROM I flash, when it boots into the system all my old files and settings are still there. What am I missing here?
Tried wiping sdext? Flashables won't wipe that and it's where dta2sd moves (and finds) settings, files, etc. What recovery are you using?
Kerr is that after you you setup up the new rom? What rom are u currently using?
Sent from my PC36100 using xda premium
I'm using Clockwork 5.0.2.2
I know clockworkmod has been having some issues lately. Have you tried amon RA recovery?
Sent from my PC36100 using xda premium
I have tried wiping before and after. I have never run into this before and it has me stumped to say the least! lol I'm currently trying out The Express B1.1.
(I must be overlooking something)
marcusva79 said:
I know clockworkmod has been having some issues lately. Have you tried amon RA recovery?
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
+1 2 EVOs, different hardware, a million ROMs and the ONLY time Amon has screwed up on me is when I've told it to...
I'm going to give it a shot now. Thanks!
Worked like a charm! Looks like I will be sticking to amon RA from now on. Thanks for all the help guys!