Develop Bugs

[Q] Error: run ' nandroid-mobile.sh restore ' via adb!

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.

[Q] Problem with Nandroid

Hello I really need some help.
I have been a little skeptical about nandroid backups so I decided to try and make a backup and restore from it immediatly after. The restoring went well until I booted the phone and all hell broke loose (sorry for drama). Most apps kept FCing and then the phone started rebooting.
Does anyone know why this is happening?
I tried doing a restore from nandroid before but it complained about md5 something so that's why I decided to test now if it would give the same error. But I just got a worse problem from it.

did you do a full wipe before restoring? also did you have enough room on your sd card? if you run out of space recovery dosent tell you... just finishes the backup.

It can also be caused by bad blocks in your SD, have you had any SD issues before, SD unmounting by itself etc?

No I did not do a full wipe before, I didn't know that it was needed. It actually sounds logical that you need a full wipe that was stupid of me.
The SD card is fine haven't had any issues with it. I will try again with full wipe.
If you get an md5 mismatch error is that backup completely unusable?

ynischa said:
No I did not do a full wipe before, I didn't know that it was needed. It actually sounds logical that you need a full wipe that was stupid of me.
The SD card is fine haven't had any issues with it. I will try again with full wipe.
If you get an md5 mismatch error is that backup completely unusable?
Click to expand...
Click to collapse
Are you using the same version of CWM? I have read problems with later versions of CWM. And md5 mismatch would certainly cause problems as far as i know...

Backup problems with DInc 2 and CMR

I have s-off and am permanently rooted. I am able to flash and run such roms as CM7.1 and RMK Gingersense from the original .zip file without a problem. However I have been unable to restore a single backup made with ClockworkMod Recovery.
For example, once I flash Gingersense I am unable to restore a backup to CM7.1. If I flash CM7.1 I am unable to restore a backup to Gingersense. In fact, I can't even successfully restore a previous backup of the same rom. I have reloaded CMR several times.
Every time I try to restore a backup, when I reboot I freeze on the white HTC screen. I have tried wiping everything before restoring, but that doesn't help.
It's a pain not being able to play with new roms and variations without being able to painlessly restore from a backup.
Any ideas?

bsteenson said:
I have s-off and am permanently rooted. I am able to flash and run such roms as CM7.1 and RMK Gingersense from the original .zip file without a problem. However I have been unable to restore a single backup made with ClockworkMod Recovery.
For example, once I flash Gingersense I am unable to restore a backup to CM7.1. If I flash CM7.1 I am unable to restore a backup to Gingersense. In fact, I can't even successfully restore a previous backup of the same rom. I have reloaded CMR several times.
Every time I try to restore a backup, when I reboot I freeze on the white HTC screen. I have tried wiping everything before restoring, but that doesn't help.
It's a pain not being able to play with new roms and variations without being able to painlessly restore from a backup.
Any ideas?
Click to expand...
Click to collapse
Here are a couple of thoughts.
1 - Is your SD Card full? I had been flashing ROMs and doing back ups a lot recently. As I flashed a ROM to give it a try, I noticed that my back up went very quick. I thought nothing of it, but when I restored that back up, it did not work and caused problems. Looking into things, their was not enough room on the SD Card for the back up to complete all partitions, so it did what it could and finished. You may have several back ups that are incomplete.
2 - You are not waiting long enough for the phone to boot. I have had my phone stuck on the HTC screen for a minute or more before it finally starts the boot animation. If the HTC animation keeps starting over, you have a boot loop, but if it is just on the screen, it may just be taking longer to boot.
I hope this helps.

I had some similar issues at one point. I would try deleting the entire clockwork folder from your SD card and let it recreate when you go back into cwr. That's what worked for me. I believe it was due to some older files that were left behind from prior versions of cwr.
Sent from my ADR6350

Sounds like the same problem I had. Which was a bad SD card format. You can try to format your SD card via Windows and start all over. One thing to note is when you hook your phone up to your computer and mount it that you must use the safely remove device icon in the system tray. This will cause many problems for you if you don't. Trust me, I learned the hard way!

Thanks for suggestions, but I don't think we've got it yet.
Plenty of room for backups (more than 7 GB) on SD card. Have looked at backup files and am pretty sure they are complete. Backups take the usual amount of time, but I notice the failed restores go more quickly than full new installs.
Always use safely disconnect to disconnect from computer (rarely mount to computer anyway - files are usually sent to phone through Dropbox).
Suppose I can reformat SD card, but what a hassle to copy/paste everything back on.
Will try deleting CMR folder, but don't think there could be vestiges from previous versions since this is the first/only version installed since root.
Any other ideas from the incredibly bright and helpful people on this forum?

Have you tried reflashing recovery?
Sent from my Droid Incredible 2

ruvort said:
Have you tried reflashing recovery?
Sent from my Droid Incredible 2
Click to expand...
Click to collapse
Yeah, even tried using an earlier version. No joy.

bsteenson said:
Suppose I can reformat SD card, but what a hassle to copy/paste everything back on.
Any other ideas from the incredibly bright and helpful people on this forum?
Click to expand...
Click to collapse
This is your best solution. If it doesn't work then you might have a bad SD card. It is a hassle to format the card but if you want it to work then it's the best solution.

Just a follow-up for anyone who lands on this thread because they have a similar problem.
Following the advice of spizzo03, I completely deleted ClockworkMod Recovery -- the app, the paid license app and the folder on the SD card. I then reinstalled just the free app of CMR from the Market.
Testing by trying to restore one of my backups ... IT NOW WORKS. Goes through the entire restore process -- system, data, cache, etc. -- whereas before it used to stop while restoring system.
Thanks to all who offered suggestions.

bsteenson said:
Just a follow-up for anyone who lands on this thread because they have a similar problem.
Following the advice of spizzo03, I completely deleted ClockworkMod Recovery -- the app, the paid license app and the folder on the SD card. I then reinstalled just the free app of CMR from the Market.
Testing by trying to restore one of my backups ... IT NOW WORKS. Goes through the entire restore process -- system, data, cache, etc. -- whereas before it used to stop while restoring system.
Thanks to all who offered suggestions.
Click to expand...
Click to collapse
Another one here. I was having issues as well restoring backups and simply wiping the sdcard's clockworkmod folder was enough for me.

Can't restore backup and network problems

dud3me said:
Phone reboots every time I turn on mobile data. Had this issue after using 3gturbocharger but got 2g working after that. Then I chose the network from settings and now it's rebooting every time I turn mobile data on. I think I'm on 3g atm and I'm on nightly 236. Will try a fresh install and see if it helps!
Click to expand...
Click to collapse
dud3me said:
Ok so did that and it's still rebooting every time i try to turn it on -.-
Click to expand...
Click to collapse
dud3me said:
I don't think it was about the script cause I "unsuperduperturbo charged it" the problem started when I chose network again. I took the same carrier that I was on atm (don't remember the reason why I did that).
Also when trying to restore a backup I get "error while restoring sdcard/android/.secure" or something like that.
Click to expand...
Click to collapse
When I try to restore back up I get this "error while restoring sdcard/android/.secure" or something like that. I'm on cwm 5.0.2.0 and you can see the reason why I need to restore from the quotes.

Happened to me a few times, even on some backups I know previously worked. I just put it down to unpredictable software and start again. If there's things you need from the backup try advanced restore in clockwork recovery or app extractor from the market, a free app which lets you pull apps and data from nandroid .imgs.
Sent from my HTC Wildfire using xda premium

Ok so figured the backup problem but the mobile network still isn't working

Do a fresh install (Remember to format /system in mounts and storage, just doing wipe data / factory reset is not sufficient). Then, reflash the radio and try again.

3xeno said:
Do a fresh install (Remember to format /system in mounts and storage, just doing wipe data / factory reset is not sufficient). Then, reflash the radio and try again.
Click to expand...
Click to collapse
That should disable all the scripts? Cause I tried that and then restored nandroid but I'm not sure If I was running the script when I made the nandroid. And how can I reflash the radio because when you start cm7 for the first time It has data on so it just reboots before you can turn it off and I can't flash cm7 and radio with same cwm so should I do a fresh install of cm7 and then fastboot flash cwm 2.5 and flash the radio?

Keep this zip file on your sdcard, its the same as ROM Manager (ie Temp 2.5.0.7). Flash in your existing Clockworkmod 3/4/5 after fresh installing CM7 to get temporary 2.5.0.7 and then flash the radio. You need not boot into the ROM to do this.
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
I don't know whether it will solve all your issues or not, but I think its worth to try it. (Again, remember to format everything under the Mounts and Storage Menu, especially /system)

Actually the 3g is now working on senseonfire I guess the reboot was just a coincidence. I'm gona go back to cm7 now and I'll fast the new radio just to be sure.
Edit: Seems to be working fine

Error restoring .secure
HI
As opposed to other items, "android_secure" is stored on the SD card instead of internal flash. So, your "error while restoring sdcard/android/.secure" is likely to happen if your sd card is full. (it happened to me for that reason !!)
I would suggest to mount the sdcard from usb - you can do it from the recovery menu - then try to free enough space for this restoration. Or maybe also try repairing the sdcard filesystem.

jjacinto said:
HI
As opposed to other items, "android_secure" is stored on the SD card instead of internal flash. So, your "error while restoring sdcard/android/.secure" is likely to happen if your sd card is full. (it happened to me for that reason !!)
I would suggest to mount the sdcard from usb - you can do it from the recovery menu - then try to free enough space for this restoration. Or maybe also try repairing the sdcard filesystem.
Click to expand...
Click to collapse
Wow......... Talk about waking the dead lol.
Sent from my Nexus 4

Well I had this issue and couldn't find any solution on the forums... But I ended up on this similar thread and had to resolve it by myself, so I thought this little contribution might help someone else in the future.
slymobi said:
Wow......... Talk about waking the dead lol.
Sent from my Nexus 4
Click to expand...
Click to collapse

Does anybody have a Odin-able copy of SM-T800 LRX22G.T800XXU1BOE2?

Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?

¿GotJazz? said:
Apparently, TWRP v2.8.6.2 compressed images to external SD cards are damaged, and it wiped my Recovery Mode and part of my previous Stock OS LRX22G.T800XXU1BOE2 installation.
I was able to Odin a Canadian copy of T800XXU1BOCC_T800XAC1BOC4_XAC, but it isn't working properly on my SM-T800.
Can somebody please point me to a US LRX22G.T800XXU1BOE2?
Thanks,
¿GJ?
Click to expand...
Click to collapse
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/

Ramer said:
Always check sammobile.com
http://www.sammobile.com/firmwares/download/47566/T800XXU1BOE2_T800XAR1BOC5_XAR/
Click to expand...
Click to collapse
Thanks, @Ramer - I checked Sammobile earlier this morning, and it wasn't there. They must have posted it later today.
I can't get to it right now, tho, their website may be having issues. I'll try later.

What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.

ashyx said:
What do you mean the backup was damaged, what failed and which partition?
You can reflash recovery then just restore system. No need to do a full restore.
Click to expand...
Click to collapse
Unfortunately. @ashyx - I'm not sure exactly where now. The recovery failure was almost instant (within the first 5 to 10 steps), and I remember that the error occurred right after a progress comment about EXT4. I lost the capability to boot up, and I lost the capability to get into Recovery Mode. My only option was to stay stuck in Download Mode, and hope that my battery didn't die before I was able to get a Odin image re-installed.
It was nerve-wracking.
I wasn't sure if the tablet would be charging while in Download Mode, and there was no way (that I knew of) to get out of Download Mode. I thought there was a high probability that I was about to permanently lose my brand-new tablet.
I paid for a subscription to Sammobile to get an older image installed until someone was able to get me the more recent stock image.
I'm too nervous to try and restore the image again without need, but I will definitely do it if you want me to. I understand the urgency to make sure that TWRP makes good images 100% of the time, and I am reluctant to do anything future to my tablet if I can't make a reliable back-up.
¿GJ?

Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.

ashyx said:
Maybe your backup somehow got corrupted.
Which partitions were you actually trying to restore? For future reference if you made a backup of recovery don't restore it. Only restore it if you want to revert to a different version.
Also don't worry about bricking your device. As long as you still get download mode you will always be able to recover. I soft brick my tablet on a daily basis lol.
The only thing you need to flash to get into a bootable state is recovery. From recovery you can usually solve most issues. Even if your battery had died you would have been able to charge it and then power it back on. Also the tablet does charge in recovery mode.
Twrp can be a funny so and so sometimes. You just get the one time when it doesn't t behave as you expect. 99% of the time though its pretty solid.
I always find its good practise to restore a backup immediately after making it to ensure its sound. You don't want to wait until its too late to find out its corrupt.
Click to expand...
Click to collapse
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.

¿GotJazz? said:
Thanks, @ashyx - Good advice on the partition recovery steps. Normally, I have automatically accepted the three defaults, and swiped. I will not do that anymore.
I have found TWRP to be very reliable in the past: If it's working fine, I always get a good backup. If it's failing on something, I always get a bad backup image, or always can't restore. I haven't had a random corruption yet. There was a problem I saw with TWRP and my Samsung GS3 a few years back where it would corrupt compressed archives, but uncompressed archives were fine. Maybe this is a replay on that problem.
I will backup my current CM12.1 image uncompressed, and then try just restoring my system & data partitions from the previous backup, and let you know what happens.
Click to expand...
Click to collapse
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.

ashyx said:
I can assure you compressed backups should work fine. I have done it countless times. Probably just a one off for whatever reason, could be a failing sd card. You may find the backup is fine and will be ok to restore. I wouldn't be afraid to try again. When a backup fails to restore you usually only get an error message not a sudden crash and reboot.
Try making a compressed test backup by just backing up the cache partition then restore.
Click to expand...
Click to collapse
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255​
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.

¿GotJazz? said:
Well, as a point of reference, I just tried to restore system & data from my older (apparently corrupted) image.
I saw:
...
Wiping System...
Formatting System using make_ext4s function.
Restoring System...
E:extractTarFork() process ended with ERROR=255​
I will follow your suggestion, and try writing a compressed Cache backup to see what happens.
Click to expand...
Click to collapse
Is this backup also encrypted. I have seen that error with encrypted backups in the official twrp. However this was fixed with an update pushed to the twrp repo which I have incorporated into the latest build.
Does your version of Twrp show your model number at the top?

ashyx said:
Is this backup also encrypted?
Click to expand...
Click to collapse
Yes.
ashyx said:
Does your version of Twrp show your model number at the top?
Click to expand...
Click to collapse
No, it just shows Team Win Recovery Project v2.8.6.2. It doesn't show any Samsung model numbers (If that is what you are asking).
I installed it using your All-In-One Root/Recovery tool.

Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633

ashyx said:
Ok I think you're actually running an earlier build. I have updated builds below.
Install one of the f2s versions from the link below.
http://forum.xda-developers.com/gal...p-2-8-6-1-unofficial-sm-t800-805-807-t3074633
Click to expand...
Click to collapse
Thanks, @ashyx! I'll download the SM-T800 F2FS version right now.
BTW, I've been really interested in installing F2FS. One thing I have been worried about, though, is that once I go down the F2FS path, it may be easy to really mess things up. For example, if I update a ROM, I would always need to use a F2FS ROM, or I might lose all my data - is that right?

Normally you would only format the data and cache partition to f2fs. There isn't much point formatting system to f2fs.
Also f2fs requires a special kernel. Myself and Tkkg1994(Iron Rom) have been working together to get this working properly. Still testing.
We are almost there.
Once formatted to f2fs you would need to reformat back to ext4 and flash a kernel to return back to normal. You could then flash your backup.