Develop Bugs

nandroid Restore +++Hours+++

Can someone please tell me how long a nandroid restore can take as a maximum?
I am running a nandroid restore as I type.
From CM6 RC1 with snap kernel
To Nandroid back up of Fresh 3.1.0.1.
It's been going for 2+ hours, the dots are still progressing but this seems like its taking longer than it should.
Question: Is this amount of time a sign that something is severely wrong?
How can I correct the issue? What will a battery pull do to my device?
Update: Battery pull did the job and my phone isn't bricked.

Shouldn't take that long.. I've done dozens of restores and most it took was 10 minutes or so.
Pull the battery and try again.. might be a r/w issue with the card.. You should still be able to get to recovery.

did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.

yep, 10 minutes is the longest I've ever had one go. Also, fwiw, it always seems to finish somewhere around the fifth line of dots..

fachadick said:
did you do the backup with clockwork, and trying to restore with RA, or the other way around? I heard that can cause issues.
Click to expand...
Click to collapse
Nope, all done with Amon. Still not sure what the issue was. Resolved, I just flashed the rom again instead.

[Q] Any idea what just happened? (bricked for a few minutes?)

This evening I was playing around with my Evo and got thinking, "I really like how everything is running right now! I've been running SteelH I.2 ROM stable for a few weeks, launcherpro, all my homescreens setup... perfect! I should take a backup."
I reboot into recovery, take a nandroid backup, then go to reboot the phone. Backup completed without any errors, but the phone would not restart. It sat at the white HTC and would not budge. I removed the battery several times and rebooted, but nothing. I could still get into recovery, so I wiped data, cache, dalvik and attempted to reboot. Again, nothing... just sat at the HTC screen. At this point I was thinking, "great... gonna have a long night ahead of me troubleshooting this one." I restored the backup I had just taken about 30 minutes earlier, but wasn't very confident that it would help at all... reboot, and after a few seconds, my boot screen starts loading!
So, here is what I am wondering.... I had not done any "hacking" since the last reboot... just installed/uninstalled a few apps from the market. What could have caused my phone to react like this? Also, if it wouldn't reboot in the first place, why did restoring the backup work? I had just taken the backup a few minutes earlier....
thanks!

Well, that certainly is unique. I've had problems doing nandroid back-ups (recovering from and creating them) before but it always booted just fine no matter what happened. Maybe there was a small software error that was fixed when you recovered.
Either way, I wouldn't worry about it. Recovering a nandroid back-up = problem got deleted.
That's why I tell everyone to nandroid before doing anything

[Q] Help (Boot Related)

Okay, so I researched my issue and didn't really find an answer. I'm not sure it is even the same issue, let me explain.
I rooted my phone using unrevoked, the latest one. I haven't flashed any roms or anything. I just deleted some bloatware and use wireless tether and shootme...etc....
The other while I was surfing the net on my laptop, I lost the signal. I went to my room and saw my phone rebooting. I didn't think too much of it until I realized it kept repeating after the 4g screen. I instinctively removed the battery and let it cool down. I replaced the battery and the same thing still happened. I wouldn't boot past the 4g screen.
I made a nandroid backup about a month ago and decided to just backup once again. I backed it up and restored the backup from a month ago. It worked fine. Now I tried to restore the most recent one and it wouldn't work at all. The same repetition of the boot screen, I believe it is called boot loop. I don't know.
My question is how would I be able to restore that most recent back up and why isn't it working? What could've possibly occurred to cause this malfunction?
I also read somewhere that battstatpro could be the culprit?
Cliffnotes:
Rooted phone a month ago
Did a nandroid backup & titanium backup (same day)
Phone stopped working while using wireless tether
Stuck in bootloop?
How do I fix it?
Thank you

wutitizshorty said:
Okay, so I researched my issue and didn't really find an answer. I'm not sure it is even the same issue, let me explain.
I rooted my phone using unrevoked, the latest one. I haven't flashed any roms or anything. I just deleted some bloatware and use wireless tether and shootme...etc....
The other while I was surfing the net on my laptop, I lost the signal. I went to my room and saw my phone rebooting. I didn't think too much of it until I realized it kept repeating after the 4g screen. I instinctively removed the battery and let it cool down. I replaced the battery and the same thing still happened. I wouldn't boot past the 4g screen.
I made a nandroid backup about a month ago and decided to just backup once again. I backed it up and restored the backup from a month ago. It worked fine. Now I tried to restore the most recent one and it wouldn't work at all. The same repetition of the boot screen, I believe it is called boot loop. I don't know.
My question is how would I be able to restore that most recent back up and why isn't it working? What could've possibly occurred to cause this malfunction?
I also read somewhere that battstatpro could be the culprit?
Cliffnotes:
Rooted phone a month ago
Did a nandroid backup & titanium backup (same day)
Phone stopped working while using wireless tether
Stuck in bootloop?
How do I fix it?
Thank you
Click to expand...
Click to collapse
Well I can't say for sure what caused the phone to initially wack out and go into a bootloop, but I'll tell you why the nandroid backup didn't work. The reason you can restore you're original backup, from a month ago when you rooted, is because you created that backup when your device was operating correctly. Since this most recent backup was created when you're phone wouldn't even boot to begin with, it will not work. The backup takes an exact copy of your entire system the way that it is when you make that backup. Since your phone was inoperable at the time of the backup, whatever it is that is broken was also copied to that backup, thus the reason it wont work. A nandroid restore will only be as good as your phone was when you created that backup.

Thank you. Is there anyway where I would be able to pull any information off that backup or fix that backup or at least get it to boot?

wutitizshorty said:
Thank you. Is there anyway where I would be able to pull any information off that backup or fix that backup or at least get it to boot?
Click to expand...
Click to collapse
Your welcome. I've never tried accessing any info or data from nandroid backup before, but I found this thread on how to do it. I've never tried it, so can't confirm nor deny if it works, but it looks like you're answer may be in this thread here: http://forum.xda-developers.com/showthread.php?t=890508

Thanks...I'll check it out

Stuck at boot splash after creating backup

I'm on an EVO 4G running Fresh 3.5.0.1 with Netarchy Toastmod 4.3.4 cfs havs-less no sbc. I'm currently using ClockworkMod recovery 2.6.0.1.
Last weekend, I wanted to try Synergy with GodMode. I don't know if it wasn't in the thread when I read it (I see the thread's been updated since my attempt), or if I just missed it, but either way, I was unaware that I couldn't install the GodMode ROM with ClockworkMod.
So I did a Nandroid backup and attempted install (I'll admit, I initially forgot to wipe data/davlik/cache). It seemed to install fine, but then couldn't make it past the boot splash. So I figured I'd cut my losses and just restore my backup. After restoring, it once again got stuck at the bootsplash (never had this issue in the past). And when I say stuck, I mean I let it sit at the boot splash screen for 5-10 minutes, pulled the battery, repeated (including wiping everything), and it could never get past it. To get the phone working again, I had to restore to a much earlier Gingerbread Deck backup that I had made while fooling around with that ROM, then I was able to restore the most recent backup without issue.
Fast forward to this evening. I figured I'd try again, but now I know I need Amon_RA's recovery. So my plan was to do another Nandroid backup, install Amon_RA, and try Synergy with GodMode. I never made it past the first step... after creating the backup (no changes were made, just the backup created), the phone wouldn't progress past the boot splash. I had to go to an earlier restore point (last weekend's) to get the phone to work. Tried restoring today's backup after getting it to work on the old backup, no luck.
Thinking perhaps the attempted GodMode install messed something up, I did a fresh install of Fresh 3.5.0.1 (pun semi-intended), fresh install of my kernel, and then tried restoring the most recent backup. Once again, couldn't get past the boot splash.
I feel like something is seriously wrong, and I don't feel comfortable going into recovery to make any changes until I have some insight into what the issue is.
To make matters worse, I rely on 4G tethering for internet, and have no landline, so if the phone is bricked while trying to resolve this issue, I'll have no resources to get help.
Any help is GREATLY appreciated. I've searched, but it seems that the problems everyone has that are like this occur immediately after changes are made and are remedied by wiping data/davlik/cache. I made no changes this evening, and wiped everything multiple times in my many attempts.
Edit: Almost forgot, some things did stand out as I was trying to get it to work.
While whiping Davlik, I was given the line:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
While restoring today's backup:
sd-ext.img not found. Skipping restore of /sd-ext/.

There was a nandroid restore issue using a previous version of twrp that was remedied by restoring nandroid and then flashing the rom over top of the nandroid. Maybe try that
Sent From My Pocket

Ok I had the same problem. I wiped everything three times also wiped dilvak (might have spelled wrong) cache, and wiped battery stats. Then flashed it. It took forever also close to 15 mins. This is what I did I hope it helps.

Just a followup: I decided I could do without restoring to that specific backup (tried restoring it after wiping data a few more times, but oh well). I only installed a couple apps and changed a couple other things since the last backup that worked, so I installed Amon_Ra since it seems to be the consensus that it's a better recovery and made a backup with that... rebooted just fine afterwards.

Restoring backups with TWRP...

I've been curious about a few things. For one, is there a "proper" way to restore a backup from TWRP? Should you do a wipe first before you restore, or does that not matter? Let me give an example of an issue I ran into. I have a (Verizon) Galaxy Nexus, and I've mostly stuck to AOKP, but a while back, I wanted to try out a different ROM. This was back when TWRP was on version 2.4.x.x, so maybe it was just an issue with that. But anyway, I made a backup in TWRP, did my wipe, then flashed the new ROM to play around with. I played with the new ROM a little, but ultimately decided I didn't like it. So I went back into TWRP, wiped again, then used the restore function to go back to the backup I made. When my phone rebooted, though, I was dismayed to find that lots of stuff did not restore properly, and I had to waste a bunch of time fixing things that didn't restore. I was under the impression that when you restore, it just returns exactly the way you left everything before you wiped it out?
Also, I'm doing something similar now, on 2.6.0.0 of TWRP. I wanted to try a new ROM, so I made a backup, wiped, flashed the new ROM, played around with it, and decided to restore my previous backup. The backup file was about 7GB. My phone seems to be "stuck", though, in the recovery process. The bar is all the way at the end (the little slanted lines are still moving), and it's been stuck at "Restoring data..." for about 10-15 minutes, now. Is this normal? I don't remember it taking this long before, although I've only ever restored a backup a handful of times. Should I just leave it alone, or should I pull the battery, or what? I don't want to screw anything up, but I kinda need to have my phone working within the next five or so hours...