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.
Related
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...
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.
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Mitzu' said:
Well, i wanted to change my rom, CM 7.2, with DjangoManouche 1.2 and used the rom below..i backed up, and when i started flashing, it said that"this is not a ROM"..i..kind of panicked and after a minute, when i seen "nothing moves" i removed the battery. When i tried to start the phone, it only shows the LG logo..but does not boot(i waited for just 1-2 minutes..). I hope someone could help me.
xdafileserver.nl/Files/LG/Optimus%202x%20(P990)/ROMS/DjangoManouche%20ROM/1.2/1.2ROMS/DjangoManouche1.2WipeEXT3Stock.zip
Click to expand...
Click to collapse
I recall reading something about using NVFlash to force the stock rom on and allowing to recover from a bricking.
I'll defer to someone with experience in fixing bricked phones though.
Thank you...now..it wont even start, even when i plug-in the charger..it had pretty low battery..i am pretty ducked..
You have to reflash it with KDZ recovery method. Look up google and you'll get it working. I did this the first time too (what a bad joke to say "this is not a ROM")...
I'm sure you can still enter Cwm if you hold down volume- while pressing power button until it the Cwm menu appears.
Sent from my Optimus 2X using xda premium
First of all, don't worry, O2X is pretty unbrickable...at least in the level you're messing with it!
If you have recovery installed, you should be able to reboot into recovery : press and hold vol down button, then power button until you see blue halo of LG. before that, download another ROM and put it in your external SDcard. Flash that ROM.
You can also download and flash the original firmware of LG by using smartflash. You can find those in ANDROID DEVELOPMENT section!
Also check KDZ recovery!!
Thank you..it worked with recovery mode..i had back-ups. I got a bit scared because when i pressed vol_dwn+ shut down button..after i release the 2nd button, it turned off...but i menaged to make it. Again, thank you for help.
====================
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Mitzu' said:
well, today i tried again to install a new rom(temasek's cm7 last build)..but i couldn't..after it is installed it get's into boot and stays like that..i tried to AOKP and it worked..my backup also worked...i just can't get it, why these roms won't work?
Click to expand...
Click to collapse
The common mistake for new people is that they restore entire nandroid backup after flashing ROM. CWM doesn't have option to backup DATA only, so you have to restore DATA from nandroid backup using Titanium Backup etc.
Try this:
1. Restore into fully functioning ROM(+data) if you don't have already
2. Reboot to recovery
3. Format /system
4. Flash new ROM
5. Clear cache and dalvik cache
6. Check if phone successfully boots
7. Flash Gapps if needed.
8. DO NOT DO ANY RESTORES AFTER STEP 1!!
9. If it doesn't work out, try another ROM. There may be some error with the file!!
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Apoplectic1 said:
I'm trying to restore a backup on my phone, and it's stalled at 27% for the last 30 minutes and wont move. Is there a way to reboot the recovery and try to wipe and reflash a ROM or something?
Click to expand...
Click to collapse
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
mikeprius said:
TWRP sometimes does that. It gets really hot too. What I do is just use the hardware keys and manually reboot into recovery. If I were you just wipe the whole phone and attempt to restore again. You shouldn't have any issues the second time around.
Click to expand...
Click to collapse
Wiping and then restoring didn't work, stalled in the same place. Wiping, reflashing the ROM and then restoring did for whatever reason.
Thanks for tip!