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.
Related
I flashed DC 3.5 yesterday on top of my 3.2.3, and it was working flawlessly. However, I realized that some of my apps didn't like the upgrade, so I was planning on restoring my nandroid of my 3.2.3 installation, backing them up with TB and then restoring. I began the restore process and it has been running for over 1.5 hours so far. This seems excessive but I don't want to just pull the battery out if this could be normal.
I haven't changed from the default SD card that came with my EVO, so I know that it isn't the fastest card. Some advice would be appreciated.
Edit: I gave up waiting, pulled the battery, and restored my froyo backup. This restored in about 3-4 minutes, so that tells me there was something wrong with my 3.2.3 backup. That's obnoxious
Try restoring one more time...if it doesn't work then restore froyo again
I have similar problem, I am trying to do a nandroid restore. It's been going for two 1.5 hours.
I was on CM6 RC1 with Snap V7.b kernel.
Trying to nandroid restore fresh 3.1.0.1.
The restore process has completely filled my screen with the dots it's been going for SOOOOOOOOO long. What should I do?
If I pull the battery will it toast the phone? phone is unresponsive to button pushes but the dots are still going. PLEASE HELP
TF1984 said:
I have similar problem, I am trying to do a nandroid restore. It's been going for two 1.5 hours.
I was on CM6 RC1 with Snap V7.b kernel.
Trying to nandroid restore fresh 3.1.0.1.
The restore process has completely filled my screen with the dots it's been going for SOOOOOOOOO long. What should I do?
If I pull the battery will it toast the phone? phone is unresponsive to button pushes but the dots are still going. PLEASE HELP
Click to expand...
Click to collapse
You should be fine pulling the battery. If you've been running this for 1.5 hours as you say, I'm sure you wasted a significant amount of juice. just leave the phone off and charge it for an hour and then boot up into recovery and try again.
If it happens once more, either select a different nandroid or flash a new rom again.
I NAND backed up my fresh Rom so I could get the PRI 1.40 update, and after the update I tried to restore back and when I click on my restore file I get the error something like " run nandroid-mobile.sh restore via adb"
I've backed up and restore plenty of roms, but for some reason this is the first error like this I've gotten.
I've been using and currently am using Amon RA 1.7 recovery.
I wiped/factory reset twice, data twice, and dalvic twice. Tried several times and even tried retoring another ROM from a few days ago and getting the same error.
I tried the command in adb, but that just doesn't seem right, I don't get a list of all my backup points, it just says "using a G1 keyboard, enter a directory name or substring and then <cr> to find matches or to accept defaults."
any help would be appreciated. Thanks!
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
davebu said:
first thing i would do is try a different recovery, RA 1.8 or clockwork. also, make sure that the md5 isnt corrupted. otherwise i would have no idea, i probably would just titanium my apps back and manually reset all my settings.
Click to expand...
Click to collapse
I could do that, and I would, but I'd like to figure out the root cause of the problem so as not to have to do it in the future. I'd like to know I can Nand backup and Nand restore if and when I need to.
If I flash RA 1.8, i assume all my restore points show up the same?
Thanks
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
astro004 said:
I've run into that problem for two different reason:
1. First, I had renamed my NAND backup files. I think if you place decimals within the file name (I.e "8.31.2010") it will give you that error
2. If you do not have a sufficient battery level it will not allow you to do a restore
Click to expand...
Click to collapse
I didn't rename the files, so that can't be it, but I just barely thought of the battery thing about 2 minutes ago. I actually got this error a couple days ago at night and gave up trying, the next morning (after charging the phone all night) I tried again, and it worked right off the bat.
I never thought it was because of the battery, but I do recall reading to make sure you have plenty battery left when flashing roms. I never knew that it was because it wouldn't physically let you flash. I thought it was more so your phone doesn't run out of juice while flashing.
I guess I'll try in the morning with a full battery and post back. I think I'm currently at 20% or so.
Thanks for the feedback.
Prob with new RA update. I had a problem with my update of RA when restoring a Nand backup from previous RA. It just ran for about ten minutes without completion and had to pull the battery and thankfully I have a pc36img of clockwork 2.5. I had to load that through bootloader and load an old clockwork backup to get my phone working again. Thank god for Titanium Backup. It restored my apps and data.
Anyone know what the deal is with the dots filling up the page during the restore. Has anyone made a backup with the update and proved it to be working?
squick said:
Prob with new RA update. I had a problem with my update of RA when restoring a Nand backup from previous RA. It just ran for about ten minutes without completion and had to pull the battery and thankfully I have a pc36img of clockwork 2.5. I had to load that through bootloader and load an old clockwork backup to get my phone working again. Thank god for Titanium Backup. It restored my apps and data.
Anyone know what the deal is with the dots filling up the page during the restore. Has anyone made a backup with the update and proved it to be working?
Click to expand...
Click to collapse
I saw quite a few people with your issue but also many that had it working fine. Did you update to 2.1 or 2.2? seems to be less of what you experienced with 2.2 thus far.
I updated from 1.8 to 2.1 and all of my nand backups work. They take eternity, but they do work.
Maybe you pulled the battery too soon? I've literally done a recovery and went to the gas station to get smokes and gotten back without it being done yet.
squick said:
Prob with new RA update. I had a problem with my update of RA when restoring a Nand backup from previous RA. It just ran for about ten minutes without completion and had to pull the battery and thankfully I have a pc36img of clockwork 2.5. I had to load that through bootloader and load an old clockwork backup to get my phone working again. Thank god for Titanium Backup. It restored my apps and data.
Anyone know what the deal is with the dots filling up the page during the restore. Has anyone made a backup with the update and proved it to be working?
Click to expand...
Click to collapse
How big is the backup? Use some file manager app to pull up the details on the backups folder inside nandroid folder.
2.1.1 - Estimate 5 minutes per 100MB. It's slow. 2.2 beta is a little faster, but still slow. Restores are taking approximately 50% longer than backups it seems. I think it has to do with the fact that it uses a new kernel. The same kernel used in clockwork 2.6 and 3, which is also slow.
You could always revert to RA 1.8 though.
Long story short:
Amon_RA 2.x uses a new kernel which is a bit slower.
2.1.1 has the minimum CPU speed set kind of low, so it doesn't speed up all the time.
2.2 has the minimum and maximum CPU speed at the same (not sure what the actual frequency is) but it's a bit faster than 2.1.1.
illogos said:
How big is the backup? Use some file manager app to pull up the details on the backups folder inside nandroid folder.
2.1.1 - Estimate 5 minutes per 100MB. It's slow. 2.2 beta is a little faster, but still slow. Restores are taking approximately 50% longer than backups it seems. I think it has to do with the fact that it uses a new kernel. The same kernel used in clockwork 2.6 and 3, which is also slow.
You could always revert to RA 1.8 though.
Click to expand...
Click to collapse
How do I get 2.2. Rom manager is only saying 2.1
Look in the AR Recovery thread, or you can pull it from here:
http://goo-inside.me/amon_ra/supersonic/
Note that 2.2 is in beta.
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
I'm having an issue with a nandroid restore with this recovery. It has been on the performing restore screen for quite some time now... enough to completely fill the screen with dots (greater then 20 minutes). All I did was perform a backup of my previous rom, upgraded ext3 to ext4 partition, wiped everything, flashed nitrous rom, didn't like it and wiped things again and performed restore and now I seem to be stuck here. Is it safe to pull the battery and just reflash my rom? Or should I let the device go longer on the restore? Never had this on prevous recovery (3.07). Did I do something wrong? Thanks.
wow i cant say i've EVER seen that happen lol i would have just done a battery pull and try it again? and or maybe just downgrade to 2.3 or something and then try and re upgrade? just a suggestion since i cant say i've ran across this personally but maybe someone else has
ben.nesheim said:
wow i cant say i've EVER seen that happen lol i would have just done a battery pull and try it again? and or maybe just downgrade to 2.3 or something and then try and re upgrade? just a suggestion since i cant say i've ran across this personally but maybe someone else has
Click to expand...
Click to collapse
Battery pull didn't harm anything thankfully. Ended up reflashing and just resetting the sd partition to ext3. Can mod mark solved? tia.