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?
Related
Hi guys
I just changed my color of everything in recovery mode. My phone has been trying to start up for 40 minutes! I don't know what to do. Can I remove the battery and try to turn it on again? I just want it to startup.
Thanks
i guess you are stuck in a bootloop. you should have made a backup, did you?
I'm not really sure what a backup is? I have titanium, and clockwork I believe on my phone. I have changed the os a few times. Please explain to me what a backup is
Backup (Nandroid) is a part of clockworkmod recovery.
usually before you flash anything that changes the system files, you should make a backup (takes less than 5 minutes). just in case something goes wrong with the file you flashed, so you can revert back to how the phone was before the backup.
are you stuck at the splash screen or bootanimation?
I just removed the battery, and I put it back in and it's doing it again... I hope it starts up.
You are the fifth person I saw having this problem today. Something is not right here...
I am guessing chrome beta is causing this. I didn't get a chance to do factory restore yet as I want to backup my data files first when I get home.
But someone said data wipe and factory restore do not help...
http://forum.xda-developers.com/showpost.php?p=22320729&postcount=2
tigersgt said:
You are the fifth person I saw having this problem today. Something is not right here...
I am guessing chrome beta is causing this. I didn't get a chance to do factory restore yet as I want to backup my data files first when I get home.
But someone said data wipe and factory restore do not help...
http://forum.xda-developers.com/showpost.php?p=22320729&postcount=2
Click to expand...
Click to collapse
i highly doubt that Chrome for Android is the source of the problem.
kkl1993 said:
i highly doubt that Chrome for Android is the source of the problem.
Click to expand...
Click to collapse
I am on stock rom without root. There wasn't any issue before and installing chrome was the only thing I did yesterday.
By changing the color what do you mean? Flashed a theme?
http://forum.xda-developers.com/showthread.php?t=1485568
I did the red sensation
Biomera said:
http://forum.xda-developers.com/showthread.php?t=1485568
I did the red sensation
Click to expand...
Click to collapse
which process did you use to root your phone?
So basically something from that theme didn't install correctly and is not allowing your phone to boot.
When making any changes to anything it is always wise to make a nandroid backup. If you made a nandroid you could restore that and you would be fine.
Since you didn't you have 2 options.
Option 1) Flash the current rom you were running with just a dalvik cache wipe and hope that it boots back up. If it does not you will have to do option 2.
Option 2) Wipe both data and cache and then flash a rom. You will lose all of your data but, you will then have a working phone.
I installed the chrome earlier today, a few hours later i got stuck in reboot loop. I use adb pull to get a copy of important data.
factory reset doesnt work. when i try to flash an earlier image of my phone, it fails at restoring 'data'
i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks
antn said:
i bought the phone rooted already. its running aokp milestone 5 and franco.kernal milestone 3. i restarted the phone the other day and i got the android is upgrading..optimizing applications #of#. after it finished it would crash and reboot and ill get the android is upgrading message again and it would crash and reboot and repeat the whole process. i tried wiping the data through cwm and it would do the same. i tried restoring the backup and it would do that same. can anyone help me with this problem? im stuck with a blackberry until i can fix my phone. i already tried searching. thanks
Click to expand...
Click to collapse
wipe and reflash the rom. or wipe and try another rom and kernel. every time you wipe, you want to reflash.
yea i already tried doing that and it would do the same thing.
I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.
I'd rather flash the takju build via fastboot using efrants step by step instructions. If I were to buy a used phone I'd want to do all the rooting and flashing as if it were a new device.
- Google
kvirus11 said:
I would try going into recovery and load a restore point first, hopefully there IS one.
I had this happen a few times to me while over flashing and restoring fixed the problem.
Click to expand...
Click to collapse
restore point? lmao! theres no such thing. you can restore a nandroid backup, but i doubt the previous owner would leave it in your sd storage considering all his/her personalinformation/data would be contained in it.
i got it to work now. i was able to learn and unroot the phone through the guide. at first i thought it wouldnt work cause i couldnt access the phone to put it in debugging mode but i guess it was already on and i did the whole unrooting process and flash stock image with no problems. thanks guys
Hi everyone,
I recently upgraded my cwm from 6.0.1.2 non touch to 6.0.2.3 touch with Odin and when doing a backup it takes a really long time and eventually fails about halfway through backing up /data. I thought maybe the recovery got corrupt or something so I used rom manager to upgrade to 6.0.3.1 non touch and tried again. This time it took longer to backup /system and while backing up data the phone rebooted. I've been running CM10.1 nightlies for quite some time now and kt kernel with no issues, and I always backup before flashing but I need to fix this before i flash anymore nightlies. Anyone else have this issue before? I've been wanting to clean wipe/install my phone for a while now but I just don't have the time right now.
My phone is a d2can on Bell. I know that's relatively irrelevant information but doesn't hurt to mention.
Also I installed the same 6.0.2.3 touch on a GS3 that I just got for my girlfriend and it backs up fine.
Also apparently in attempting these backups it somehow messed up some of my settings. I had a sign in error for gmail which went away as soon as I hit sync now in the Google account, although I had to sign back in to Facebook. It also changed a bunch of my sound settings... Imagine my surprise as I get a Whatsapp message and an Opeth song starts blaring (and also doesn't stop upon checking the message...) lol.
I back up my apps and settings with Titanium Backup so I can easily restore everything when I have a chance to do a clean wipe and install, but how do I fully wipe/reinstall the recovery to fix this backup issue? Maybe I just have to hit the factory reset button in the recovery?
Lessaj said:
Also apparently in attempting these backups it somehow messed up some of my settings. I had a sign in error for gmail which went away as soon as I hit sync now in the Google account, although I had to sign back in to Facebook. It also changed a bunch of my sound settings... Imagine my surprise as I get a Whatsapp message and an Opeth song starts blaring (and also doesn't stop upon checking the message...) lol.
I back up my apps and settings with Titanium Backup so I can easily restore everything when I have a chance to do a clean wipe and install, but how do I fully wipe/reinstall the recovery to fix this backup issue? Maybe I just have to hit the factory reset button in the recovery?
Click to expand...
Click to collapse
I would download Goo Manager and flash TWRP, forget CWM. If you hit factory reset then you are going to have to go through the clean install process. If I were you I'd flash TWRP and then clean install whatever your into. It'll take maybe 30 minutes to get the rom setup the way you want it and you'll have the piece of mint that everything was cleanly wiped and you have a fresh start.
I guess I can try TWRP. I don't really get why everyone rags on CWM, it works just fine. I was using 6.0.1.2 for about 7 months without a hitch, this is the first problem.
If I did a clean wipe I'd still backup my pictures and my apps from TiBu and restore everything after wiping, it would just take a while. I don't have an external SD so it's all on the internal. I might have some time tonight to try it out.
Lessaj said:
I guess I can try TWRP. I don't really get why everyone rags on CWM, it works just fine. I was using 6.0.1.2 for about 7 months without a hitch, this is the first problem.
If I did a clean wipe I'd still backup my pictures and my apps from TiBu and restore everything after wiping, it would just take a while. I don't have an external SD so it's all on the internal. I might have some time tonight to try it out.
Click to expand...
Click to collapse
I would copy your pictures (or any other irreplaceable files) to a computer for safe keeping just in case it hits the fan. Apps are whatever, but you can't retake pictures so I'd back them up somehow; computer, dropbox, etc.
Same Issues on a SG3
I also recently upgraded and have been having the same issues. It doesn't seem to matter whether I enter recovery through or use Rom Manager to enter into in recovery. Each time the back up fails. I had just switch back after having TWRP issues where it back up would not fail but when they were to be use in recovery I would get a message before restarting stating I didn't actually back up the OS. ( I realize it might not be reliant info but I've learn a little to much is better than not at all)
I've noticed it will fail and restart only when I try to back up to my SD card. Yesterday it was giving me trouble by mounting and unmounting repeatedly. I thought I had fixed all the problems after I did a diskcheck and had my computer scan and fix all found errors.
If anyone can link me to a previous version of CWM or help with this back up issue you'll have the OP's and my appreciation.
Thanks in advance.
---------- Post added at 03:36 PM ---------- Previous post was at 03:00 PM ----------
Are you backing up to an SD card or the phone it's self?
Lessaj said:
Hi everyone,
I recently upgraded my cwm from 6.0.1.2 non touch to 6.0.2.3 touch with Odin and when doing a backup it takes a really long time and eventually fails about halfway through backing up /data. I thought maybe the recovery got corrupt or something so I used rom manager to upgrade to 6.0.3.1 non touch and tried again. This time it took longer to backup /system and while backing up data the phone rebooted. I've been running CM10.1 nightlies for quite some time now and kt kernel with no issues, and I always backup before flashing but I need to fix this before i flash anymore nightlies. Anyone else have this issue before? I've been wanting to clean wipe/install my phone for a while now but I just don't have the time right now.
My phone is a d2can on Bell. I know that's relatively irrelevant information but doesn't hurt to mention.
Also I installed the same 6.0.2.3 touch on a GS3 that I just got for my girlfriend and it backs up fine.
Click to expand...
Click to collapse
Icon000 said:
Are you backing up to an SD card or the phone it's self?
Click to expand...
Click to collapse
I'm backing up to the phone itself, I do not have an SD card.
Lessaj said:
I'm backing up to the phone itself, I do not have an SD card.
Click to expand...
Click to collapse
So was your problem fixed by switching to TWRP?
I know when I had tried using TWRP, the issue I was having after back ups, was it would ask me if I was sure I wanted to leave since it said I didn;t install a OS.
Does that help you to find a solution?
post-mortem said:
So was your problem fixed by switching to TWRP?
Click to expand...
Click to collapse
post-mortem said:
So was your problem fixed by switching to TWRP?
Click to expand...
Click to collapse
Yes.
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
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!