This is my first time to restore a nandroid backup i recently made. The load bar isnt animated any longer and its sitting on:
"restoring data...
[email protected]"
the first time i pulled the battery after about 5 minutes and rebooted into what appeared to be a partial restore, but the home button didnt work and i powered down before it finished synching my settings. Im on my second attempt, sitting at the same place and its been close to 10 minutes, is this normal or should i just try pulling the battery again and reflashing the rom altogether? I wiped the first time even though my searching said it wasnt necessary, no wipe the second time. here are my unhelpful search results:
http://www.google.com/search?source...s+nandroid+restore+take+on+nexus+one?&qscrl=1
http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=did+my+nandroid+restore+freeze?&qscrl=1
Doesn't sound too good i'm afraid & I am of little help either as I too am new to Android ROM flashing - but rather, as a help to others, can you state what type & version of recovery you are using (ClockWorkMod / amon_ra), what Nexus you have (AMOLED / SLCD), whether you have the phone connected over USB when backing up / restoring, android version backed up, what charge level you had etc.
I believe all of these elements can affect your results in one way or another.
e.g, I believe for SLCD, you require amon_ra v1.8.0.1 & some people have reported issues if performing the operations while connected to USB.
Good luck & let us know how you get on.
Steve.
thanks, i ended up just reflashing the rom because restore kept freezing. I remember usb was not plugged in during backup, it may have been during the first restore, i dont recall, but it was definitely not plugged in the second time. Im just glad no serious damage was done though, i guess i just wont do nandroid anymore ill stick with the rom manager backup method. Im using clockwork recovery
AndroidPerson said:
thanks, i ended up just reflashing the rom because restore kept freezing. I remember usb was not plugged in during backup, it may have been during the first restore, i dont recall, but it was definitely not plugged in the second time. Im just glad no serious damage was done though, i guess i just wont do nandroid anymore ill stick with the rom manager backup method. Im using clockwork recovery
Click to expand...
Click to collapse
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
cmstlist said:
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
Click to expand...
Click to collapse
thanks im going to remember this, the more things i have to try when something goes bad, the better
cmstlist said:
The backup/restore function in Clockwork is the same as what you get in ROM Manager.
I had a restore freeze on me too, during the data segment. Same thing happened twice. Here's what I did to fix it:
1) Booted into Clockwork
2) Wiped cache and data
3) Went into the nandroid menu, "Advanced" restore
4) Restored the data partition *only* - this succeeded where other restores had failed
5) Restored each remaining partition individually as well, also from the Advanced menu
6) Booted up and everything was fine
Click to expand...
Click to collapse
I've run into a similar hangup before running Clockwork, and fixed it pretty much the same way you did. I've since gone back to Amon's recovery, as its nandroid functions seem to be more reliable.
Related
Hi all,
I just installed ClockworkMod Recover using ROM Manager on my G1, replacing Amon_RA. Immediately before replacing, I did a Nandroid backup using Amon_RA. No problems, lots of dots and then it returned. After I installed ClockworkMod, I tried creating another Nandroid backup, first from the recovery screen and then from the ROM Manager app. Both times the backup hung on the message "Backing up .android_secure..." and required a battery pull to get back. The last time I let it go for over an hour before giving up. I'm running CM6 stable, if that matters.
Any idea? I'm about to put Amon_RA back on, so I can get good Nandroid backups again.
I know this is an old post but I am getting the same thing. Going to continue researching.
hmmm last time i had an issue kinda like this it was the recovery... need to re flash it somehow.. maybe the sd ext has something to do with it also...? im not sure but i would try to re flash recovery or maybe switch back to amon-ra if all else fails can always re-root
Mine took over 20 minutes today. Just when I was about to pull the battery, it moved on. Probably down the amount of stuff you have on your phone I guess.
I'm running a 32GB card stuffed with apps
havent used clockworkmod in a long time, i stick with amonra -- but if i remember right with clockwork isnt there an option to have a status bar so you can see how things are moving along? maybe not...
So tonight I was close to a freak out. I made a Nandroid backup of my CM 6.1.1 system. And then I restored a backup of an old 2.2 stock rom. After that I did a wipe / factory reset thing since I wanted to play with plane untweaked and new stock rom. When I got bord of it I booted into recovery mode via "power + volume down" and tried to restore the CM Rom which it refused to do. One point showed up and then it aborted and said something about "something wrong, nandroid restore doesn't work" - cant remember the exact words. So I thought "**** maybe the backup is corrupt". So I tried another one. Which didn't work either. So I actually ended up trying every single of my 22-ish backups. None of them worked. So instead of having a heart failure I just went to bed and told myself I would deal with it today. So today I wanted to boot into recovery mode so instead of dealing with my broken power button I installed 1-click universal androot and quick boot. I soft rooted the phone (obviously stock roms are not known for its rootedness) and rebooted into recovery mode where my restoration attempt succeeded like it always does. So now I'm curious why it worked today. And I must admit it sounds obvious. But it has to have something to do with the fact that I rooted my phone. So is that true? Can recovery managers only write the images of a nandroid backup when the phone is rooted. I thought the fact that there is a recovery image that is capable of backing up and restoring a system has all necessary rights through its bare existence? Just curious... =)
arminsoyka said:
So tonight I was close to a freak out. I made a Nandroid backup of my CM 6.1.1 system. And then I restored a backup of an old 2.2 stock rom. After that I did a wipe / factory reset thing since I wanted to play with plane untweaked and new stock rom. When I got bord of it I booted into recovery mode via "power + volume down" and tried to restore the CM Rom which it refused to do. One point showed up and then it aborted and said something about "something wrong, nandroid restore doesn't work" - cant remember the exact words. So I thought "**** maybe the backup is corrupt". So I tried another one. Which didn't work either. So I actually ended up trying every single of my 22-ish backups. None of them worked. So instead of having a heart failure I just went to bed and told myself I would deal with it today. So today I wanted to boot into recovery mode so instead of dealing with my broken power button I installed 1-click universal androot and quick boot. I soft rooted the phone (obviously stock roms are not known for its rootedness) and rebooted into recovery mode where my restoration attempt succeeded like it always does. So now I'm curious why it worked today. And I must admit it sounds obvious. But it has to have something to do with the fact that I rooted my phone. So is that true? Can recovery managers only write the images of a nandroid backup when the phone is rooted. I thought the fact that there is a recovery image that is capable of backing up and restoring a system has all necessary rights through its bare existence? Just curious... =)
Click to expand...
Click to collapse
1) Paragraphs...look it up
2) When you reloaded your stock rom you lost custom recovery. That's why you couldn't re-flash your cm backup.
Hi All,
Suddenly my phone gets stuck during booting at the S logo and it vibrates sometimes similar to FC-ing.
I have the feeling that some process keeps crasing in an infinite loop.
I havent touched the ROM for at least a month.
It was upgraded to JPY via KIES with reg hacking and it has worked fine until today.
Yesterday before going to sleep I shut it down and when this morning I turned it on it could not get past the logo it just vibrates and front leds are lit.
Battery is fully charged, screen showing fully green battery when charging.
I can enter both Recovery and Dowload modes, nothing unusual is displayed there.
Battery out-in did not help.
No lagfix, phone was rooted with modified kernel (chainfire afair) more than 1 month ago.
No problems like this whatsoever.
Last successful boot was yesterday evening, no signs of any problem.
I have not done factory reset yet as my last Titanium Backup was quite a long ago.
Questions:
- is there any kind of "safe mode" boot like in windows?
- I can not access its internal SD card from PC (USB), is there a trick to make the pc recognize it?
- any other suggestion before FR?
It is International Galaxy S, JPY, unbranded
Thanks in advance!
if you have CWM recovery then i think there is an option to mount the sd card so its visible on your pc,
another thing. there is a safe mode i accidentally entered it a few months ago, what you need to do is boot up the phone and whilst it is booting press the left key (menu) until the keys light turns off, (or keep pressing the menu key) and then the phone should come up in safe mode..
i havent tried it with a boot loop and i dont know if anyone else has so it may not work..
and finally if you do have CWM you can do a nandroid backup thru that, then do a factory reset and re-apply the nandroid backup.
Unfortunately I do not have CWM.
I tried safe mode the way you wrote but it did not work for me, neither worked the other Menu + Home + Power combination mentioned elsewhere, probably the problem comes earlier than that.
Is there a chance to install CWM in this limited mode of my phone?
the problem is that int sd does not seem accessible.
does update.zip work only from internal sd?
im afraid so yes its not possible to do it from the external sd unless you have a steam kernel.
looks like your only option would be to do a factory reset in recover or re-flash through odin.. but you will lose your data..
your best bet is to just write down as many apps as you can remember you had, and maybe re download them after the flash 1 by one.
but all the stuff on your internal sd card WILL STAY INTACT. e.g pictures music movies ect
EDIT::: you can now access the market on-line so perhaps you check that to see if your apps show on there before you do the reset... I've not checked it out yet...
My market on web looks good so that should not be a problem.
I was just told that I could have CWM by flashing a kernel that contains it.
If that is true I can do what you said earlier: do a nandroid backup + FR + restore
I except this to save my Angry Brids achievements that are in not on the int sd card but only in the app data.
Does this make sense?
jasahu said:
My market on web looks good so that should not be a problem.
I was just told that I could have CWM by flashing a kernel that contains it.
If that is true I can do what you said earlier: do a nandroid backup + FR + restore
I except this to save my Angry Brids achievements that are in not on the int sd card but only in the app data.
Does this make sense?
Click to expand...
Click to collapse
Replying to myself: It made sense.
I flashed a SpeedMod kernel to have CWM
- tried booting, but no success (as expected)
and then from CWM
- I mounted USB storage to back up SD card
- did Nandroid backup as well to make backup of the rest
Then Factory Reset -> phone could boot again
tried to only 'Restore data' from nandroid backup -> failed to boot
ok, FR again and get back the most from my 1 month old titanium backup
My is guess that some program with root rights corrupted something which made me unable to boot
What I learned -> backup frequently !
Now what remained is to get back my Angry Birds progress from nandroid backup
Thanks for help!
I have a rooted HTC Hero (Sprint) and during preparations for upgrading to CM7 I ran into issues with ROM Manager.
First, I backed up everything (apps and data) via two different methods. I cleared davlik cache, and then performed a CWM Flash Recovery backup. Once that completed successfully, I sought out to apply the CM7 ROM. I selected it from the GUI menu, rather than rebooting into the Flash Recovery. I selected to backup everything and then wipe the data/cache. During the process, the phone hung (white HTC screen for over 10 minutes). I could reboot successfully after this, and selecting "Recovery" didn't work either. I figured my phone was bricked. But miraculously, it managed to finally recover.
The recovered ROM was a fresh clean slate. So, I installed ROM Manager and Titanium backup again. However, when I tried to reboot to the CWM Flash Recovery, or even try entering the CWM CUI menu from power up (by holding the HOME key), the phone hangs. Something is seriously screwed up with ROM Manager. I'd like to wipe it completely clean and start over, but everything I've tried results in a phone that hangs. I'm now thinking I should use a different program for managing the ROMs... but, being familiar with ROM Manager and seeing other people use it successfully, I feel determined to make it work. Any suggestions?
I would just flash an RUU and start from scratch.
https://docs.google.com/file/d/0B9lyYjZr_O3gZnJrRVFqRmh4eVU/edit
I was able to recover.
What I didn't realize is that the first boot can take upwards of 20-30 minutes. I pulled the battery after around 15 minutes, thinking my phone had hung.
Anyway, when I selected "Recovery" again I left the phone alone and eventually I got a stock ROM again. Whew!
While ClockworkMod is fine for 2.1, when you're on 2.3 there's no question that TWRP is the way to go. I've flashed it to my phone (did "flash_image recovery [recoveryfilename.img]") from the terminal window and it's working great, far more extensive than ClockworkMod.
I was running Resurrection remix 6.
Flashed the latest kernel 5.08.
Flashed rom to Havoc OS.
Flashed gapps.
Decided it wasn’t good enough, so went back into twrp, wiped and restored my nandroid backup.
It goes through. At the very end it seems to have finished. The phone then turns off. After 10 or so seconds, the phone turns back on but only the white notification LED is on.
I pressed and held the power button, then turned it on again but it doesn’t see the operating system.
So I try to wipe again but now it’s saying it can’t mount the system.
I do the formatting to FAT, then back to ex4 and restore the backup again. However, it’s done the same thing again.
Any ideas on going forward or back?
Well, I was able to reinstall the new ROM again but it's not that great a rom.
I guess I could download the old rom and start a fresh? I have a Titanium Backup so I guess it won't be too bad.
But any ideas as to what may have happened with this would be greatly appreciated.
anotherxdauser said:
I guess I could download the old rom and start a fresh? I have a Titanium Backup so I guess it won't be too bad.
Click to expand...
Click to collapse
Probably need to flash the old ROM again, yes. As you said, it won't be that bad, since you have TB.
The nandroid probably just didn't backup properly. It's happened to me occasionally. Why it corrupted the storage, is a bit harder to answer.