Develop Bugs

Nandroid and bootloops.

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?

[Q] Cant flash sense anymore or make a nandroid backup

Hi I recently flashed evo-decks 1.2 stable after I did that I had errors with any nandroids and I can't flash any sense or aosp ones either. I'm stuck and and stumped as to what my course of action should please any ideas would be fantastic thank you.

Well first, do you have a current working rom at the moment?

What he ^ said.
Sent from my PC36100 using XDA Premium App

yes I do its the evo decks 1.2z the one I found to be more of a stable version

[email protected] said:
yes I do its the evo decks 1.2z the one I found to be more of a stable version
Click to expand...
Click to collapse
Well backup the rom; make sure you have at least 500mb free space. Do a full wipe [factory/data, cache, dalvik cache], flash the new rom. Make sure you have more space, because the sense 2.1/3.0 can be big in backup size.

What happens when you try to flash another Rom?
Sent from my PC36100 using XDA Premium App

I get stuck at the HTC evo 4g screen just stays white and wont boot I have wiped it numerous times and I get the same result never happend until I flashed the 1.2 stable I also did flash the vipermod and Google apps as well as available memory mod I found I had used that multiple times before as well

Wipe everything 3x, use Virus's CR super wipe after you manually wipe everything. Factory wipe, cache and delvik cache. That should clear everything out. Then flash a Rom. It sounds like something isn't getting wiped.
Sent from my PC36100 using XDA Premium App

Well it says report to the recovery log to see what went wrong its preventing me from even Making a backup at all it says depot to recovery log to see what went wrong seems more serious no?

So because somethings not wiping properly that will give me an error telling me to view the recovery log and then prevent me from flashing different builds and making a nandroid backup I don't seem to see a link for the superwipe under virus I tried searching and i could not locate it is it on his website?

[email protected] said:
So because somethings not wiping properly that will give me an error telling me to view the recovery log and then prevent me from flashing different builds and making a nandroid backup I don't seem to see a link for the superwipe under virus I tried searching and i could not locate it is it on his website?
Click to expand...
Click to collapse
here you go.
http://bit.ly/jEjuoN

If I were you, I'd backup my SD Card, format it, repartition it, if you're using partitions, and then copy the essentials back over. Specifically, you're nandroid folder, then reflash your Recovery, which hopefully, is Amon Ra.
Then either try to reflash one of your nandroids, although if it was me, I'd just copy the ROM you want first, and then try to flash that, and it if goes well, try a nandroid you have saved.
I've had this happen twice and both times, reflashing recovery did the trick

Alright ill try thanks alot everyone I appreaciate your help ill get back to you guys hopefully with good news

Well so there's no way I could just wipe it with recovery and flash it over cause apparently I'm not the only one with this issue and somebody said it has to do with partitions of my SD card I'm trying to look into it deeper.
Sent from my PC36100 using XDA App

[email protected] said:
Well so there's no way I could just wipe it with recovery and flash it over cause apparently I'm not the only one with this issue and somebody said it has to do with partitions of my SD card I'm trying to look into it deeper.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You don't have to partition it; first reflash your recovery via PC36IMG image, then copy your sdcard to a pc, format it, then copy the files back over, try to restore a backup, or reflash the rom.

[Q] Restoring from CWM 3.1.0.1 not working

I created a backup using CWM 3.1.0.1 (from rooted EC05). I then flashed one of the new roms, and today wanted to go back, so i booted into 3.1.0.1 and did the restore (from cw). Now the phone boots up to the Samsung screen and sits there. What am I doing wrong? Sorry if this has already been asked, I did a search but couldn't find this particular issue. Thanks for any and all help.

both backups were made using 3.1.0.1? and were both made in 3finger recovery? and when you restored you were in 3 finger recovery, not reboot recovery?

chris41g said:
both backups were made using 3.1.0.1? and were both made in 3finger recovery? and when you restored you were in 3 finger recovery, not reboot recovery?
Click to expand...
Click to collapse
I only did 1 backup, not sure what you mean by 3 finger recovery? I booted in CWM (purple) and did the back-up. I then put on the "Bamboozle" rom (and yes, I wiped everything 3x like qb shows in the vid) then installed the rom. I ran it for the past week (loved the rom, but it was eating my battery really bad) so wanted to try a different rom. I thought the easiest way to start was to restore the backup I made, so I booted back into cwm and selected Backup/Restore, Restore, Yes and it ran and said it restored fine. I reboot, but all I get to now is the Samsung screen, no further.

libracolo said:
I only did 1 backup, not sure what you mean by 3 finger recovery? I booted in CWM (purple) and did the back-up. I then put on the "Bamboozle" rom (and yes, I wiped everything 3x like qb shows in the vid) then installed the rom. I ran it for the past week (loved the rom, but it was eating my battery really bad) so wanted to try a different rom. I thought the easiest way to start was to restore the backup I made, so I booted back into cwm and selected Backup/Restore, Restore, Yes and it ran and said it restored fine. I reboot, but all I get to now is the Samsung screen, no further.
Click to expand...
Click to collapse
Let me just say, I think I f'ked my phone up. So I gave up trying to restore, just odin'd back to stock (ec 05). Which I then re-rooted and re-installed CWM 3.1.0.1 (I have titanium backups as well). However, now the phone runs really, really slow and when I try to restore apps from titanium it just sits there (in batch mode). Sorry, for being a noob; hey, if nothing else, maybe I'm making someone smile at my dumb a$$. But now, if I can be even more stupid, is there a way to just "reset" the phone, by that I mean put it back to a "true stock" form so I can start over? And then, can I just delete these backups, and roms from the sd card (just hookup to laptop and delete from the sd-card)? I think maybe it'd be easier to just start from scratch again...thanks for the help, I try to keep up with the forums, but so many posts....

What he means by 3 finger is the ONLY way to get into recovery for proper operation. With power off press and hold camera, volume down, and power. Holding all 3 until you see the recovery menu. If you use any other method such as ROM Manager or Quick Boot you will more than likely screw up your phone. Neither application is recommended for recovery operations.
Sent from my SPH-D700 using XDA App

I believe clockwork does not backup the kernel. You may need to install a kernel.
Just a thought...

libracolo said:
I created a backup using CWM 3.1.0.1 (from rooted EC05). I then flashed one of the new roms, and today wanted to go back, so i booted into 3.1.0.1 and did the restore (from cw). Now the phone boots up to the Samsung screen and sits there. What am I doing wrong? Sorry if this has already been asked, I did a search but couldn't find this particular issue. Thanks for any and all help.
Click to expand...
Click to collapse
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App

crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Thanks, that must have been it. I was on Bamboozle, which is based on Gingerbread.

libracolo said:
Thanks, that must have been it. I was on Bamboozle, which is based on Gingerbread.
Click to expand...
Click to collapse
Wait, did you wipe data/system,cache, and Dalvik Cache then restore your nandroid? I have a SRF 1.2, an Urban Regeneration, and a CM7 nandroid. As long as I wipe everything then restore I have no problems. I have bounced between all three today with no issues
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
Wait, did you wipe data/system,cache, and Dalvik Cache then restore your nandroid? I have a SRF 1.2, an Urban Regeneration, and a CM7 nandroid. As long as I wipe everything then restore I have no problems. I have bounced between all three today with no issues
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah, the issue was I was running bamboozle (GB leaked rom), so once I odin'd back to EC05, I was able to run the restore without problem. I am now running SRF 1.2 (awesome rom btw) and I was able to restore when trying to install that rom (and the genocide kernel). Thanks for all the helpful answers.

crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
I would have thought the same thing. However, I simply restored my SFR 1.2 nandroid right over the gingerbread rom. With a few glitches smoothed out I am running fine again with no Odin involved.
Sent from a secret underground bunker

mjben said:
I would have thought the same thing. However, I simply restored my SFR 1.2 nandroid right over the gingerbread rom. With a few glitches smoothed out I am running fine again with no Odin involved.
Sent from a secret underground bunker
Click to expand...
Click to collapse
Yeah, I have gotten the dreaded Google Services Framework FC's a couple of times but for the most part I can wipe everything and restore a Froyo setup even when on a Gingerbread ROM. The purp recovery is good like that.
Sent from my SPH-D700 using XDA Premium App

JohnCorleone said:
Yeah, I have gotten the dreaded Google Services Framework FC's a couple of times but for the most part I can wipe everything and restore a Froyo setup even when on a Gingerbread ROM. The purp recovery is good like that.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Thanks for the info. I will have to remember that and try it out in the future.

crawrj said:
Thanks for the info. I will have to remember that and try it out in the future.
Click to expand...
Click to collapse
Hey, no problem crawrj. It definately comes in handy with all of the testing I do for sure.
Sent from my SPH-D700 using XDA Premium App

When restoring across different OS versions it is handy to do a Restore>Advanced Restore Data from the Nand backup. There may be the occasional FC if the data format has changed but that usually can be fixed by clearing data of the offending app, especially for Google sevice framework.

kennyglass123 said:
When restoring across different OS versions it is handy to do a Restore>Advanced Restore Data from the Nand backup. There may be the occasional FC if the data format has changed but that usually can be fixed by clearing data of the offending app, especially for Google sevice framework.
Click to expand...
Click to collapse
Kenny - I did try that as well. I tried everything, I did the "Restore" option like 4 separate times, I wiped data, cache, dalvik cache 3 x, even did the Advanced option and went down the list. None of that helped. Now it may be that I just didn't wait long enough, but I figured 4-6 minutes of the "Samsung" screen meant it had stopped responding (I see that all that time in MS apps). I finally odin'd back to stock ec05, re-rooted (and updated back to cwm 3.1.0.1), then I ran the restore (not advanced), and it worked like a charm. Thanks for all the suggestions on this.

libracolo said:
Kenny - I did try that as well. I tried everything, I did the "Restore" option like 4 separate times, I wiped data, cache, dalvik cache 3 x, even did the Advanced option and went down the list. None of that helped. Now it may be that I just didn't wait long enough, but I figured 4-6 minutes of the "Samsung" screen meant it had stopped responding (I see that all that time in MS apps). I finally odin'd back to stock ec05, re-rooted (and updated back to cwm 3.1.0.1), then I ran the restore (not advanced), and it worked like a charm. Thanks for all the suggestions on this.
Click to expand...
Click to collapse
Sometimes our phones can be so finicky. Glad you got it working. Usually when Dalvik is rebuilding it takes awhile at the S screen, so you are correct that 4-6 minutes at Samsung is a cry for help from your phone.

crawrj said:
If you backed up on ec05 and installed a gingerbread rom you need to odin back to ec05 and then do the restore. It won't work if you are on different os versions. At least it never has for me.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Not true. I always go from froyo to gingerbread with backups. What he Did wrong was not wipe when he tried to restore his back up that's why he got stuck on the Sammy screen. Also if he tried to restore a rfs froyo rom it could've gotten stuck there also since bammbozle was ext4.
Sent from my SPH-D700 using XDA Premium App

Esteway.619 said:
Not true. I always go from froyo to gingerbread with backups. What he Did wrong was not wipe when he tried to restore his back up that's why he got stuck on the Sammy screen. Also if he tried to restore a rfs froyo rom it could've gotten stuck there also since bammbozle was ext4.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You can restore from EXT4 to RFS with advanced restore data nand. He said he tried all of this and still got stuck. But I think you are correct and the first restore attempt borked everything. From there a reflash then advanced restore data should have worked.

kennyglass123 said:
You can restore from EXT4 to RFS with advanced restore data nand. He said he tried all of this and still got stuck. But I think you are correct and the first restore attempt borked everything. From there a reflash then advanced restore data should have worked.
Click to expand...
Click to collapse
So if I understand what you guys said, I should have wiped first (before the initial restore), which I didn't do. When the first restore didn't work, then I did the wipe x3, but it sounds like by that point it was already too late. So should you always wipe before restoring? I only ask, because once I got everything back to a good place I flashed the sfr 1.2. The first attempt caused the phone to boot up with that annoying "Android" screen, so I just booted into CWM and restored. That time I just restored (no wipes, no advanced) and it restored fine. I then re-flashed and all was good. So it seems like you don't always have to wipe x3 before restoring? Thanks btw, all good info for future ref.

[Q] Cleared data prior to nandroid.

I did some searching and I wasn't able to find the answer I was looking for, so here goes.
Last night I rooted my GB Evo with the new Revolutionary method. I got all excited to put my MikG ROM back on the device using AmonRa, and without thinking I cleared cache, delvic-cache, and then data ... THEN I did my Nandroid backup.
If I ever decide to restore back to my backup, is this going to cause problems? What exactly is lost when you choose to clear data?
Thanks for your help.

That will clear all your settings definitely and apps I think.
Clearing data I mean .
Clearing cache and dalvik cache will do nothing I do that before backing up to save memory.
Sent from my PC36100 using XDA App

You pretty much only backed up the system and wimax.

i dont think it will boot up if you restore. try it and tell us your results you can always go back into recovery and flash a new rom

Make another backup and don't wipe data I only keep backups that I want to go back to and incase something goes wrong .
As long as you have your apps backed up you can always flash a stock rooted ROM and restore your apps.
Sent from my PC36100 using XDA App

restoring backup

I am a currently running swagged out stock but would like to see decks ics ROM, would backing up sos and restoring to it after checking out the ics ROM be fine? will i have to wipe anything between the two ROMs?
Sent from my HTC EVO 4G using Tapatalk

Just do a back up via recovery. Then flash your new from. Afterwards restore via recovery and you will be fine
Sent from my PC36100 using XDA App

Yes, backing up your rom, trying a new one, and flashing back is perfectly fine, everyone here does it.
Just remember to wipe everything BEFORE flashing (restoring). Restoring a backup is just like flashing a new rom, you need to wipe before flashing.

I never wipe when restoring a backup. It's just an image.

sitlet said:
Yes, backing up your rom, trying a new one, and flashing back is perfectly fine, everyone here does it.
Just remember to wipe everything BEFORE flashing (restoring). Restoring a backup is just like flashing a new rom, you need to wipe before flashing.
Click to expand...
Click to collapse
+1
Always the safe way to avoid problems.
Sent from my SHOOTER juiced EVO using XDA Premium.

HipKat said:
I never wipe when restoring a backup. It's just an image.
Click to expand...
Click to collapse
+1
Also, just an FYI - backups WON'T work (or maybe worse than just that) if you repartition between bking up and restoring.
It's only Flashahol, try a sip...