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.
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.
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.
when i try to restore my nandroid it says error flashing boot image please help
That happened to me once. I think the actual file was corrupt because I was able to restore from a different nandroid. Do you have any others saved that you can try?
I don't remember that exact error message (I actually think it might have been different), but a very similar (or identical) error can occur of on backup/restore you have a low battery, low disk space or have renamed the directories.
What recovery are you using?
Do you have other backupsyou can try?
Are you trying to restore a clockwork backup with ra, or an ra backup with clockwork?
Sent from my blah blah blah blah
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
rcbarr said:
Once you get through this (best option, use one of the other Nandroid backups if you have them), download and install Titanium Backup, I trust it more than Nandroid's backup. Heck use both before you install ROMS and make any major changes. Just a thought...
Click to expand...
Click to collapse
Wait, what?
It's not like you have a choice to do one or the other, nand and titanium do totally different things. You should always do a nand backup before flashing anything, regardless if you use tb...unless I misunderstood what you're saying...
Sent from my blah blah blah blah
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
DaKlown said:
I am having this same problem. i switched from the regular sense rom to CM 6 rs2. i can load cm6 backups all day long but my sense rom gives me an error when i try to load it saying "clockwork mod error while flashing boot image!". Both nandroid backups were made with clockworkmod. I had to downgrade my version of hboot to install cm6. I am wondering if i need to upgrade it again to load my original sense rom or am i wrong in thinking this?
Click to expand...
Click to collapse
OP didn't give as much detail as you - good example of how details help.
You can only restore backups you made with the same version of hrboot. You can't restore a .79 backup while running .76 (which I'm pretty sure is what you downgraded to in order to load cm6).
Now I need to find flashable zips of both hboots so I can switch between cm6 and sense. I so miss my 4g lol. Thanks for your help!
I upgraded hboot to .79 and still got the same error. Funny thing is that my cm6 loaded fine and my hboot is still reading .79 anyone have any clue as to why sense wont load and why cm6 loaded on a different hboot?
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
potna said:
i was able to achieve my objective and then some. now i can restore to a cm6 or a oem rom in a matter of maybe 5 or ten minutes.
maybe it wasn't directly the way i wanted to do it but i think it was similar enough that it worked without me understanding what i was doing therefore keeping me out of the mix which is why it probably worked.
what ui did was i found a ruu.exe for 3.29, i downloaded it and ran it
once it was done i ran unrevoked to get root again and the boot loader installed, i think the .97 boot loader was key here, but i dont know.
then i booted to recovery and did a nandbackup
then i did a nand recovery to my older backups of cm6-success
then i did a nand recovery of a older oem 3.29 sense rom- success
im sure that i rambled on here and i never really knew what i was doing but i was able to do what i set out to do and then some. if only we could dual boot roms.....
Click to expand...
Click to collapse
You are doing exactly what I am trying to do, and ran into the same trouble.
Seems like having to run unrevoked again is unnecessary. There must be a way to switch the boot loader without it ? Did you ever find a quicker way?
I feel pretty comfortable messing with this stuff, even though I am new to the EVO. That said, I really do not want to brick it doing something stupid. Messing with these boot loaders does scare me a bit.
potna said:
did you ever get this figured out? i am in the exact same boat.
i rooted with unrevoked 3.21, this went well
i backed up oem sense in recovery via nandroid, this worked, i wiped and restored from this backup just to test, again the restore worked just fine.
later i tried to flash cm6 but all arrows pointing towards not having the right hboot. i dont remmeber what i had but i needed to got to eng boot .76.2000, which i finaly got figured out and was able to flash to cm6.
at this point cm6 loads and runs juts fine, i decided to boot to recovery and do a backup via nandroid, infact i did two of these back ups. i wiped my phone and did a restore just to test these back ups.
heres my problem: just for the fun of it i thought i would try to use the first nadroid back up to restore (that had stock sense installed at the time) and it wont flash. it says something about:
"Checking MD5 sums…
Erasing boot before restore…
Restoring boot image…
Error while flashing boot image!"
i thought i found a fix: i need to "Switch .76 with .79", this still did not allow me to restore from my oem sense backup, i get the exact same error.
i found another potential fix pertaining to going back to .93.
i feel like i dont know enough about what i am doing and im abit scared to try this as i dont see much info on this method.
basicaly i'd lile to be able to go back and forth between stock and custom for a while and also i'd like to be able to use nandroid backups to quickly do this.
am i approaching my problem correctly pertaining to the hboot thing? and can i just drop the .76,.79, 93. images in and out of the pc36image.zip file that i will place on root on my sd card with out anything else in this zip and expect it to just work?
Click to expand...
Click to collapse
I'm having the same problem, but I don't have the luxury of either Sense or Cyanogen working--I'm just permanently stuck inside the ClockworkMod Recovery and can't get back to a nandroid restore point I've verified in the past as working.
Is there something I can do to remove the pc36img.zip file? How?!
I have amon_ra and I ran into this issue a while back too. You most likely got this error due to your battery level being too low. Turn your phone off, charge the battery for a while and try again.
http://forum.xda-developers.com/showthread.php?t=705026&highlight=%5Brecovery%5D
Near the top of his post it states your battery must be atleast 30%, in red text.
Sent from my HTC Evo 4g
i have searched all over this forum and google and i havent been able to find anyone having a similar problem with recent versions of clockwork.
Im having problems with restoring my nandroid backups, i have been playing with different roms and kernels lately and have had a few times that i have been stuck in boot loops, so i go to do a nandroid restore from clockwork and all my backups will freeze at checking MD5 sum.
After the first time this happened i reinstalled a rom from sd card and started over, everything seemed to be fine. I made a backup from clockwork and then restored it as a test, it worked fine. Then i got stuck in a boot loop again, and suddenly all my backups were freezing at checking MD5 sum again.
I am running the latest vesrion of clockwork and rom manager, both backups i make with rom manager and from clockwork are affected by this issue.
Any help is much appreciated.
How long have you let it try to check? I've had one take over ten minutes.
Sent from my Incredible using XDA App
I let one go for 30 mins, most the time i get restless after about 5, but the few times it has worked it works in a couple seconds.
How much free space is on the SD card?
If it's near full, that will impact backups and performance of CWM.
CWM seems to get wonky when it doesn't have all the room it needs to fully stretch it's legs.
Assuming the card is formatted FAT32.
One of the things that might be causing it is a flakey SDcard. They are making so many of them and many are counterfeit/relabeled that we don't really know what we are buying.
If the card is dropping sectors on the write when you do the backup it will never pass md5. Also if the phone is having trouble reading the image because of borderline bad sectors it will take forever but might still pass.
These things can barely keep up with a normal users phone use. Then we come along. And just slam them with alot of small writes installing apks to SD and Ti back-ups then larger writes with Roms and Nandroids. This could also be a sign that the controller chip is not able to keep up with it. And we know some of the hardware/drivers in this phone are funny. (cough..bluetooth)..
And SDcards really hate battery pulls. I have lost data on 2 8gb SanDisk cards that way.
Treat them like floppies. Don't trust them with anything. Ever.
i've heard of people having issues with the latest CWM and backups. try pushing an older version and try
I've used 3 versions of clockworkmod recovery so far, and have done 1 recovery from each version, many backups from each version. Here's what I've noticed about md5sum:
Version 2.5.0.5 - Normal ~5 minutes for full backup. ~5 minutes for md5sum.
Version 2.5.1.2 - Normal ~5 minutes full backup . ~8 minutes for md5sum.
Version 2.5.1.8 - Normal ~5 minutes full backup. ~30 seconds or less for md5sum.
Note: all work with SLCD which I have.
By the way, since 2.5.1.8 isn't on the official image downloads site, I got that from the thread about multitouch testing in the dev forum here. It is the second link in that thread.
Good luck -
Before I went to sleep last night I decided to backup my phone via recovery. After it backed up I rebooted and I had no service and a service called com.phone or something like that would force close every 5 seconds. I went back into recovery and reflashed CM7 and it bootlooped. I went back into recovery and restored a backup from the day before and it worked flawlessly. I hadn't changed any type of settings, I had just installed the new Swiftkey Beta and Robot Unicorn Attack between the 2 backups. Through trial and error and many reboots into recovery I found out that it is the data portion of the backup that was causing the problems. Does anyone know why this happened? I am a little nervous about doing another backup for fear of not being able to use my phone.
CM7 Stable
Incredikernal (latest)
hboot .92
3.0.0.8 recovery
I suspect the backup had nothing to do with it. I'd bet you would have had the same problems after a simple reboot.
As far as I know, a nandroid backup simply reads from the phone and writes to the SD. I don't see how it could have changed anything on the phone itself.
That's what I thought. I can't remember if I had recently rebooted at that point but after getting the phone working through a restore of the previous backup I tried one last time and restored the backup that had caused the problem and the problem persisted.
How much free space do you have on data/data?
Sent from my ADR6300 using XDA App