I've been running stock rooted MD4 with TWRP 2.5.0 and have done backup and restore several times just to try out new roms. Yesterday I decided to try Hyperdrive, did another backup, and gave it a shot. I decided it was much more than I needed so changed back to stock. I have a total of 3 backups, 2 of which I know are good because I've used them before. Now when I do restore I get "failed" on data restore. I've done the triple wipe of everything and even downgraded TWRP to 2.4.1 to no avail. I can get data to restore by restoring everything else, rebooting, then going back to recovery and restoring data. I'm open to suggestions guys. Am I missing something? Help would be very much appreciated.....
Sent from my SPH-L710 using XDA
I've had this same exact issue...the only way I fixed it was with what you found too, or by flashing the rom, booting up and then back into recovery and restoring data
I honestly have no idea why it does this, everything I've read said that this was an issue on older recovery versions when restoring files bigger than 2 GB,.but that's since been fixed.
BTW: CWM had this issue to for me
Related
I am getting this error when ever I try to do a nand restore : Error: run ' nandroid-mobile.sh restore ' via adb!
I am running amon ra 1.8, I have the latest sprint lovers installed running 3.70, new radios, pri 1.90. Hboot 79. I've succesfully backed up and restored nands in the past but now I get this error. I've tried to backup and then immediately try to restore the backup and I get the same error so its not a corrupt backup. I have more than 6gb available on my sd card and am fully charged. I've looked in other threads and haven't found an answer. Any help is appreciated since I'm flying without a net when I flash if I can't restore my nand.
Run the command from adb shell, and it'll tell you what's wrong. Duh.
In other words, do what it tells you to do. Is it really so hard to follow instructions?
Hey man had the same problem. I was on miui and I went back to sense to update profile and flashed the new radio combo so I made a nandroid of miui first and then when I tried to restore that same back up I got the same error that you got. I'm not positive but I think that it has something to do with flashing the new radio and then switching to aosp rom. I ended up having to reflash miui and then every thing went back to working normally.
Sent from my PC36100 using XDA App
nandroid won't work if battery is low, I think if it's less than 30% charged, might want to try charging it before restoring to see if it helps...
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Nefariouss said:
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Click to expand...
Click to collapse
I had the same problem and what nefariouss is saying might work. Also, once i wiped several times and then completely turned the phone off and booted back into recovery and then it would restore. Another time i reflashed the rom that i was trying to restore and once it booted i went back to recovery, wiped all and then it would restore. Hope that helps. Just keep messing with it. I know its a pain but eventually it will restore.
Sent from my PC36100 using XDA App
if your sd card didnt partion properly this will happen.
save everything on your sd.
reboot into recovery
repartition sd card.
read that a few people running clockwork recovery have this issue frequently.
Delete Spaces!
If you are trying to flash a file in recovery that has spaces in it, it will not flash and will give you that error. so 'Fresh Evo.zip' won't work, but FreshEvo.zip will work.
FML, ignore this post please. I was a bit stupid.
Sorry for bumping, I have the same problem on my Optimus One p500
Sorry for bumping but I'm really worried about my phone. I have the same problem on my Optimus One and I've tried stuff mentioned above with NO success. Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
antiother said:
.... Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
Click to expand...
Click to collapse
Download and flash this. It is a rooted stock rom (Froyo) that has NOT been deodexed. In other words, it is THE stock HTC sense rom (3.70) that will allow you to maintain root privileges. While in recovery, wipe EVERYTHING in the wipe menu EXCEPT the SD card BEFORE flashing.
posting & replying via the XDA Premium app.
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
wampuscat said:
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
Click to expand...
Click to collapse
Same thing happened to me after I updated Amon Ra recovery after doing a nandroid backup. Desire wouldn't boot and got stuck on white screen. Tried to do the backup using ADB but each time I got to the last step it failed. So I tried clearing Dalvik cache etc and finally wiped my card using recovery. After a couple of attempts, I was able to restore the last nandroid backup. Big relief.
i need help!!! i have the same problem of the whole error run nandroid-mobile.sh.. via adb. ive scoured the internet and havent solved my problem. i tried doing the cmd prompt thing and i found the latest backup, put into the cmd prompt but this is what i got.
error: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411/nandroid.md5 not found,
nnot verify backup data
/ # /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sbin/sh: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411: Permission denied
/ #
and i rebooted and have no idea what to do. someone help. i have the nandroid backup saved to my computer as well in case something like this would happen, and if i could restore, things would be fine!!! i dont understand this, i created a nanroid backup and its not corrupt but i can restore it! wth, im lost and confused and i have lots of data on that nandroid backup. someone please help. i partitioned my sd card and lost everything so all i have is the nandroid backup and my original rom, Cyangon MOD 7 is running right now bc i lost all my data, so im at the beginning. PLEASE HELP!
Delete spaces
I was facing similar problem but thanks to @hecklbrg, It did the trick. Cheers.
This isn't like some of the other nandroid fail threads i've encountered.
I had a full nandroid backup of my tmobile g2 (eng hboot) and I lost that device. I got an exact replacement, rooted it (no eng hboot), installed rom manager only and flashed clockwork. I then copied my nandroid backup to the clockwork/backups directory and did a restore.
The phone booted successfully with cyanogen 7 nightly 22 flashed but the only problem is that it seems to have done a fresh install...as in there are no apps, no data, just cyanogen 7 nightly 22. It appears it didn't restore anything except the rom itself. Any ideas? thanks in advance.
ps. ive done multiple data wipes, and tried 2 different nandroid backup files on the new phone.
Did you have darktremors a2sd installed on the old ROM? CWM3 seems to have an issue for some with seeing the sd-ext partition and won't back it up. So when you select 'restore' in CWM it *successfully* completes the nandroid restore correct, no errors? It would be odd for it to give you a 'restore complete' message if it ran into any errors.
pretty sure I don't have a2sd installed on the old rom. first time i'm hearing of it. I don't recall getting any errors after restoring the backup but I will try again and double check. I also have much older backups that I can try to restore and see if those go through
Well I think this needs more attention if it's really not restoring the nandroids fully. Seems like it's restoring the system.img and whatnot just not the data.img. Maybe try it with ADB and see if it works. I've never had to do it that way but I know it can be done, you may have to run it in a shell.
I tried restoring a nandroid backup from February, which I believe was backed up with an older version of clockwork, and it was completely successful. This tells me that either the new clockwork is not backing up correctly or it's getting corrupted.
I then tried restoring 3 different backups and they did not give me any errors but failed to restore my data. hmmm
Hi
I seem to be having a strange problem making a backup with CWM. Everytime i try to make a backup itll go through all the steps successfully but when backing up /data it'll say error while backing up data. Im running stock 4.0.4 and i never had a problem backing stuff up in the past, this is the first time i've had an issue. My CWM version is 6.0.12 and i also had the same problem on the older 5.something
Any advice would be greatly appreciated thanks
Sent from my SGH-I747M using Tapatalk 2
Sounds like either your cwm or ROM is corrupt. I'd reinstall cwm with ROM manager. If that doesn't work try wiping data/factory reset (will delete all your apps)
I have a Samsung Galaxy Note 2(AT&T). I have it rooted w/CWM recovery. I recently flashed Jedi X12 rom to it following the directions to the tee. It installed perfectly and all was going well. I then tried run TiBu to put all apps with data back and system files. This cause several issues most of which were pop up boxes telling me various processes were failing. Tried to run the backup again and the problems persisted. So I restore to my CWM .zip image from before the whole process and it all is fine and where it should be. I then went back through the Jedi X install process and when it is all wiped, flashed, clear chached, it just hangs on the first black and white Samsung Galaxy Note 2 page. I let it sit for an hour hoping it would eventually boot, but no luck. So i restored to backup zip(CWM) again and the phone is fine. I repeated this process half a dozen times trying clearing different things, but nothing has gotten the rom to boot. It says all went fine in install.
*It worked the first time, got messed up by a TiBu, and hasnt worked since
*tried reflashing and restoring several time
*re-dl'ed the rom zip again and copied to phone incase file was corrupt
*In between every restore and rom flash I
-Wipe data ( factory data reset)
-Wipe system (Format system (in mounts/storage) if on CWM)
-Flash ROM
-Wipe cache/Dalvik
-Boot system and DO NOT TOUCH FOR 10 MIN
-After the 10 min, reboot phone
*All restoring/flashing was done through the CWM recovery.
I assume I have to clear/wipe/format/flash some other location to fix this. But Im going nuts trying to figure out where. Any help would be much appreciated. Thanks for your time.
Use Odin to get back to stock/unbrick. and NEVER restore system data using Titanium Backup
mrevankyle said:
Use Odin to get back to stock/unbrick. and NEVER restore system data using Titanium Backup
Click to expand...
Click to collapse
Thanks. I'm going to try app2zip the next time i get it to work. The phone works fine after i do a restore in clockwork mod, but I should still flash back to stock in odin again,, and start over? The recovery doesnt do that for me? Sorry if these are dumb questions, just getting into the android stuff, but have years exp. modding iphones.
if the phone is working fine, then no, you dont have to go back to stock; just NEVER EVER restore system files in TB, and you will be fine
Also, if you are going to be flashing alot of roms, you might want to switch to TWRP recovery, insted of CWM, as most folks have far fewer problems flashing when TWRP is their recovery..
wase4711 said:
if the phone is working fine, then no, you dont have to go back to stock; just NEVER EVER restore system files in TB, and you will be fine
Also, if you are going to be flashing alot of roms, you might want to switch to TWRP recovery, insted of CWM, as most folks have far fewer problems flashing when TWRP is their recovery..
Click to expand...
Click to collapse
Thanks all good info. Definitely learned the hard way about TB. Ill check TWPP out.
wase4711 said:
if the phone is working fine, then no, you dont have to go back to stock; just NEVER EVER restore system files in TB, and you will be fine
Also, if you are going to be flashing alot of roms, you might want to switch to TWRP recovery, insted of CWM, as most folks have far fewer problems flashing when TWRP is their recovery..
Click to expand...
Click to collapse
+1 on this...
I do a complete backup in TWRP...data and all saved to my external SD before doing any changes to my phone...and have not had 1 issue restoring it completely. FWIW...I make a complete back up every week regardless..then delete the previous one..and have everything available to me when it is restored all apps & data....TWRP makes it very easy to do this..and you can name & date your backups any way you choose to..I've found doing it any other way..causes more headaches than needed..and in less than 5 minutes I can be back up and running with all my apps & data with no problems in case I downloaded something that was causing an issue or changed something that caused issues. It's no different than using any desktop computer...you just need to get in the habit of doing it on a regular basis.
Mac
So, I've been using TWRP since I purchased this device. I did a TWRP backup today as usual since I wanted to flash back to TouchWiz to update my PRL. I did so, then went to restore my backup. Only part of the backup restored. Now, no matter what I do in TWRP, I get the same error:
E error opening 'data/data/com.newegg.app/share (there's more text here but it's truncated by the recovery)
E error: Not a directory
This happens when I try to wipe (any option), flash a ROM, create a backup, restore a backup, etc. I've updated from TWRP 2.5 to 2.6.3, still to no avail. I don't believe it's a recovery issue. Recoveries don't just stop working, especially after using Odin to write a new recovery partition.
My ROM is screwed up. It boots, but no apps open. The hardware keys don't work (except home).
Any ideas or suggestions? I don't really want to switch to CWM but will if absolutely necessary.
Thanks!
I would suggest doing an ODIN back to Stock. Make sure everything is working correctly. Then Root the Device again.
I did something similar. I used a flash to stock and reset counter .zip that worked. It still threw that newegg error, but once I rebooted, reinstalled twrp, rooted, flashed Slim 4.3 Stable 2 and did another nandroid, the weird error is now gone. So glad I didn't ruin my phone! Thanks!
Your welcome. Happy you got the issue resolved .
TEAM MiK
MikROMs Since 3/13/11