I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
I've discovered the log function under Advanced of CWM. This is what the log is ending with:
tar: can't remove old file data/system/packages.xml: Operation not permitted
#92997temp.dumpefs1.binefs2.binefs3.binS30edt_perms.logzipalign.log.cid.info.psm.info.mac.infoentropy.datbatterystats.binuiderrors.txtusage-20120304usage-20120305usage-20120229usage-20120301usage-20120302usage-20120303packages.xmlError while restoring /data!
Click to expand...
Click to collapse
I Googled around, and came up with this:
http://forum.xda-developers.com/showthread.php?t=1461658
Again, the Galaxy Nexus, with the same problem being this data/system/packages.xml file, and the same solution being Fastboot.
What the heck is going on? Is it possible for us to use Fastboot on our T989's?
manekineko said:
I'm using regular Clockworkmod 5.0.2.6 (not touch, which I've never tried).
I made a bunch of Nandroid backups of my phone. In the past I've restored to some of them and they worked. However, now, whenever I try restoring any of them from CWM, including the ones that worked before, it restores for a while and then it fails stating:
"Error while restoring /data!"
I searched on Google, and the only references I've found to this problem are from Galaxy Nexus owners. For them, just reflashing stock over Fastboot fixes it, so I reflashed stock 2.3.5 over Odin, but the problem remains.
I've also tried doing wipe data/factory reset from inside CWM and that didn't help.
Has anyone seen this before or have any ideas on how to fix this?!
Click to expand...
Click to collapse
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
manekineko said:
Fixed it, just as you were typing up your response. (Thanks for the tip nonetheless!)
I just ran Darkside Super Wipe on my phone, and after that my restore proceeded perfectly.
I wonder if that's really the key. I don't suppose your favorite ROM is Darkside Digital Warfare, which has Darkside Super Wipe built-in?
Click to expand...
Click to collapse
Of course it is lol.
»»DARKSIDE««
Thanks for the fix, same thing happened to me. I had the Optimus T before this so I whent flash happy 12 hours after I unboxed this beautiful phone. I've only had this phone a week, you saved my life lol.
this is just now happening to me, this threat is old but very help full lol
Hey all,
not trying to rehash a "solved" thread but Im having this issue and then some.
First, I tried Darksides wipe script and tried to restore the boot and install a new rom, then install the backup, all to no avail. I tried everything. When you get this error, it seems (at least from my experience) that your only hope is to restore from the stock 4.02 google image and then restore from the nandroid. This first happened to me when my phone dropped and off the couch and the battery came out. It seemed to have corrupted the sdcard, or, at least that was my guess.
However, upon redoing everything to stock and restoring the nandroid (even upgrading to the latest ver of clockworkmod recovery), the problem comes back. Im worried about permeneant damage, possibly, but it makes no sense that I would be able to revert to stock and have it working fine. When I reverted and restored from my nandroid, everything worked flawlessly. Then, today, I turned off my phone (which is a rarity, if ever) and it wouldnt boot back up a few minutes later. Bootlooop and the dreaded "error while restoring data!" message. Im going to revert to stock again and start completely from zip, no nandroid. Its possible that the nandroid is corrupted I suppose but i dont believe it would let me restore it than. Any ideas? Could this be from me leaving my phone on practically all the time, without ever turning it off? or the battery coming out while in use? (which makes sense in theory but I've done a battery pull countless times and never had a problem like this). Would there be a way I could determine, for sure if its a hardware problem? Verizon Nexus (hardware ver 9 I believe) now running JB Sourcery 2.0 (from team sourcery...an AWESOME rom, so I dont believe it to be that.)
Cheers!
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
Wow thanks so much for this! Just happened to me on my note 2 and after doing some googling I came across this post and it worked perfectly, first try. thanks again!
i had this problem now.. my hearth stopped to work.. but this guide helped me ! thanx ! so it is working in year 2014 too
raycaster3 said:
You're not alone my friend and I know how to fix it, albiet temporarily, although I haven't actually had the issue in quite some time.
Do a full wipe and clean install of your favourite rom. Once it boots and you let it settle for a few minutes reboot recovery and restore your backup. I have done this method about 12-15 times. The error restoring was accompanied by the inability to reboot my phone at all without having a complete meltdown of every app force closing. It was after the first "bad reboot" I had that I got the error while trying to restore a backup. Hopefully you don't have o go through that. It sucked big time to say the least. Hope this helps
»»DARKSIDE««
Click to expand...
Click to collapse
plz help me :crying: i am new to this here is my situation i hav a galaxy s4 i9500 i rooted my device 2 days ago and i backed up during the back up it showed no .android_secure found. skipping backup of applications on external storage andalso root error fix . i google it and found its not a big deal so i factory formatted it but when it restored it and restored it all the applications started showing error msg so i formatted sd card and replaced backup folder and tried to back up it showed md5 mismatch so i editted nanroid.md5 with notepad++ and tried to reboot again now its showing recovery data error . what to do?
Ok, so i have backed up, restored, MANY times, I just went from 4.2.2 to 4.3 ROM, and now it says failed when I try to restore it back to 4.2.2. I have done this a few times over the last couple of days, not it is giving me the failed error. What can I do?
I have plenty of room on my SD card as well. I also do a full wipe before I try to restore.
Disregard, after the 4th time it worked fine.......
I was on ND8 and attempted to flash the CM 11 nightly after backing up. It failed with error 7. I wasn't thinking and just hit restore (even though I didn't need to). Whenever I restore it, the apps keeps crashing over and over again and I can't even open anything. I get messages saying this and this crashed. I need to restore because I have contacts on that nandroid that i'll never be able to restore. I have tried clearing the dalvik and it didn't seem to work. Advice?
Edit: By the way, I have an older backup and they both do the same thing. I've flashed many many ROMs and have never had an issue like this. UGH.
Hopefully somebody knows how I can make the restore work. I'm literally freaking out.
galaxyman635 said:
I was on ND8 and attempted to flash the CM 11 nightly after backing up. It failed with error 7. I wasn't thinking and just hit restore (even though I didn't need to). Whenever I restore it, the apps keeps crashing over and over again and I can't even open anything. I get messages saying this and this crashed. I need to restore because I have contacts on that nandroid that i'll never be able to restore. I have tried clearing the dalvik and it didn't seem to work. Advice?
Edit: By the way, I have an older backup and they both do the same thing. I've flashed many many ROMs and have never had an issue like this. UGH.
Hopefully somebody knows how I can make the restore work. I'm literally freaking out.
Click to expand...
Click to collapse
Try doing a full wipe (Data,System,Cache,Dalvik) and then restore it. That should fix it. It sounds like you never wiped the system and the two roms are going at it. Best of luck!
To cut to the chase…
My G5 (XT1671 32GB) has no IMEI. The one smart(?) thing I did before starting to screw around was make a backup with TWRP - 2 backups actually, one stock, the other AtomicOS. When I try to restore the backup I get an "unable to locate partition by backup name" message for these partitions: efs1, efs2, logo, oem. I gather the efs partitons are the ones that correspond to IMEI and other modem related things.
Is there any way to bring these partitions back? I've reinstalled the stock ROM (a few times now) and that doesn't seem to restore them (however when I try restoring I always get an error message on this line "fastboot flash partition gpt.bin"
Is restoring even going to fix the IMEI? From what I've read those backups are supposed to be an exact clone of the device - sort of like using Macrium to make an image of your PC (btw the backups include everything, whether it was needed or not ~6-7GB in size)
Cheers
Once you've flashed an oreo rom, imei will always be 0 when reverting to stock.
You could try this though: https://www.youtube.com/watch?v=XmKg84IXEbo
Going back to stock isn't the issue with the IMEI, it's whether you can turn off auto-update fast enough no to let an OTA update through (at least that's what screwed me)
I did run through the video you linked before hand. Kinda worked. Got 3G back, but when I tried the steps to restore 4G I just lost my IMEI again.
Still doesn't answer why I kept getting the missing partition message in TWRP. I do have full backups so you'd think restoring my efs would be the answer.
Turns out that was the answer… I have no idea what exactly happened but after trying the steps in that video again I decided to restore my AtomicOS backup (prefer it to Pixel Experience) for WIFI usage if nothing else. I got the same missing partitions message and this time somewhere during the restore process TWRP crashed/rebooted (could only boot as far as the bootloader menu). When I booted back into recovery to try and restore again I finally had all the options to restore my efs/logo/etc.. So I restored everything available (minus "system image") and am back to a fully functional AtomicOS.
I'm thinking I could also restore my stock backup now without problem now since I made it way before I ever tried any 64bit/Oreo roms. But ATM I don't want to tempt fate. Besides probably better to wait until Moto/Lenovo officially launches their Oreo update before considering stock again
I've been trying to install one of the android 10 lineages on my wife's phone.
It keeps on bootlooping and by now I have tried so many combinations of twrp and restores, wipes, different roms and restoring the backup of an android 9 lineage.
The phone keeps bootlooping, sometimes in the "your bootloader is unlocked" message and sometimes in the lineage startup movie.
It even seems to bootloop in the twrp startup screen, but maybe it is just slow and my impatience is getting too high.
I've tried two different twrp versions as one gave an error in restoring a backup (I think the newest one gave the error).
Could it be that a backup made in the older twrp cannot be restored with the newer twrp?
I'm running out of options and may need to go back to stock, which is not the easiest path to take.
Oh, the phone was rooted when I made the backup, if that makes a difference...
Any thoughts?
If you backed up all partitions, then restore all of them and follow the steps to install...
Note: Before you restore the partition, make sure to wipe it, it ensures that nothing goes wrong...