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.
Related
Last night I power cycled my phone and put it on my charger. When I woke up this morning and looked at my phone there were a ton of force close screens. I have no phone (cannot make calls) and not data.
I power cycled the phone over and over and have been searching the net all day but cannot get it to work. The only thing that I had done prior to the initial power cycle was a few updates from the market, so I uninstalled those apps, but it appears that was not the problem.
I have root access and was running gumbo's rom (now MaDoCo...thought that would help) and I really don't wanna do a factory reset. Is there anything I can do?
Factory reset is most likely gonna be your only option. If you dont wanna do that, do you still have the .zip for your rom on your mem card? If so, why not just reflash the zip? Might take care of the issue without having to do a hard reset. I am assumingm, though, that if you are rooted you would have created a nandroid backup? Why not just restore?
Tried reflashing the rom and that didn't work. Gonna do a Factory reset now. Lets see
tried factory reset and now i'm stuck on boot screen
Did you ever make a Nandroid backup?? I would suggest you run the Sprint RUU and bring your phone back to Stock, reroot, install recovery, and then a custom ROM. That looks like your best option.
But, just for the hell of it -- take out of your battery and then insert it back in and reboot, see if that does anything.
What kind of factory reset did you do? Wipe from recovery, go through setting, the home>back>power one, or what? And are you stuck at the HTC screen? That happened to me once, but it was because I flashed a GSM rom my first try. Boot into recovery, wipe the phone, and if that doenst do it, I agree with pseodo, time to RUU.
Well I tried resetting from the recovery and wiping, but it will not boot up. Then I tried the RUU, but it wont get past the boot screen in order for me to to connect it to the USB. I tried connecting the USB through recovery and although I can access my SD card via my PC, going through the steps for the RUU says its not connected.
I took my phone over to sprint and although they know I have a custom rom on there (which voided my warranty), they are still gonna give me a brand new one and send mine back through manufacture warranty. It'll be in on Tuesday. Luckily for me I have an online back up through by MyBackUpPro, so I should be good on restoring settings, apps, contacts and all other important stuff. (Minus Root and Custom Rom )
Thanks for all the suggestions, I appreciate it.
I flashed a new set of icons last week and had a bunch of force closes, restored a nandroid and everything was fine.
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.
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...
i had network problems (3g stopped working, don't know why), and had an old version of doc's. so i figured i'd install the new version after a wipe, see if that'd fix it.
just to be safe, i went in recovery (clockwork) and restored an earlier backup. it worked, but still no internet. upon remembering that this was the backup i made just after installing docs, i went back to my previous backup, stock rom, i think 2.1.
this is where stuff went wrong. i hadn't disabled the lagfix (forgot which one, i remember i had ext4 as filesystem), and now, no matter what i do, my phone won't go past the boot screen. big lettering galaxy s, smaller gt-i9000 and at the bottom samsung, you know the one.
i tried everything i could imagine. wipe data/factory reset, wipe cache partition, re-restore to the oldest backup. only then did i remember the lagfix and remove it. retried all of those, still no dice.
i can get into recovery mode, both clockwork and 2e, and i can get into download mode.
when i connect my phone to my pc, it doesn't notice. when selecting mount in clockwork, it mounts, and shows the two drives in my computer, but when i try to open one of the drives, i get nothing.
i installed docs rom a while back, and have wiped my pc since then, so i have no files from that. i have installed the android sdk, but don't know how to use it, let alone how to use it with a phone that doesn't show.
all i want is to get back to stock, for now. try again from there.
can i? or have i ruined my phone?
edit:
wow... take about relief.
i used odin to flash xxjpu, 2.2.1, and it seems to have worked!
in case anyone else is stuck on a boot screen, download mode with odin means you're safe.
anyone with more sense than i showed in my stupidity, sorry for adding another semi useless topic.
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.