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] Can't restore /data after 4.3 update

Hello!
I'm in a bit of panic. Since Google pushes their stuff over OTA and my custom rom PAC somehow didn't deal with that correctly, it caused to use all my data, so I wanted to give stock 4.3 a try.
Rebooted into CWM, made a backup of my current ROM, free unused backup data, did a factory reset like always and flashed the 4.3 image. Wasn't happy at all with stock 4.3 so I wanted to go back. To my horror, restoring that image failed. Error while restoring /data!. I tried booting up anyway, maybe only a few settings were lost, but it started like the first time I flashed the ROM with the gapps log-in thing and all my apps are gone.
I tried getting back in CWM, manually restored /data, but that didn't work either. It starts restoring /data but then halfway through it stops with the error.
Previous backups (AOKP/CM/PAC) didn't restore /data either.
Installing Nandroid Manager to restore individual apps to a fresh ROM fails too. It sees all apps but it can't restore anything at all.
I have come to the discovery that apps won't even install. Apps manually extracted from the backups are 0kb and I can't seem to install some apps from the Play Store either. Unknown error code during application install: "-24"
Does 4.3 change anything about where the /data partition is? Or what happened?
What's the problem and can I even restore the data? Or do I have to start over?

RainbowSwag said:
Hello!
I'm in a bit of panic. Since Google pushes their stuff over OTA and my custom rom PAC somehow didn't deal with that correctly, it caused to use all my data, so I wanted to give stock 4.3 a try.
Rebooted into CWM, made a backup of my current ROM, free unused backup data, did a factory reset like always and flashed the 4.3 image. Wasn't happy at all with stock 4.3 so I wanted to go back. To my horror, restoring that image failed. Error while restoring /data!. I tried booting up anyway, maybe only a few settings were lost, but it started like the first time I flashed the ROM with the gapps log-in thing and all my apps are gone.
I tried getting back in CWM, manually restored /data, but that didn't work either. It starts restoring /data but then halfway through it stops with the error.
Previous backups (AOKP/CM/PAC) didn't restore /data either.
Installing Nandroid Manager to restore individual apps to a fresh ROM fails too. It sees all apps but it can't restore anything at all.
I have come to the discovery that apps won't even install. Apps manually extracted from the backups are 0kb and I can't seem to install some apps from the Play Store either. Unknown error code during application install: "-24"
Does 4.3 change anything about where the /data partition is? Or what happened?
What's the problem and can I even restore the data? Or do I have to start over?
Click to expand...
Click to collapse
have the same story with galaxy note 2..

Flash backwards first
not an expert here, but isnt the general protocol to try to flash back to the same version of the os first (i.e 4.2.2), and then try the CWM restore?
Are you able to try to track down the same os version you had before?

Have the same issue with my i717
nimbin2k said:
not an expert here, but isnt the general protocol to try to flash back to the same version of the os first (i.e 4.2.2), and then try the CWM restore?
Are you able to try to track down the same os version you had before?
Click to expand...
Click to collapse
I flashed back to 4.2.2 and then tried restore, but no luck. It gave me the same error (Error while restoring /data).

[Q] HTC One M8 - Bootloop PLEASE HELP

Hi everyone,
I've been running ARHD on my HTC One M8 (S-ON) for the past few days. Recently I decided to get S-OFF using the firewater method.
In step one, I downloaded the OTA 3.0.7-3.0.8 Insertcoin ROM onto my device, instead of the full ROM. Without knowing this, I proceeded to make a nandroid backup from TWRP, then did an Ådvanced Wipe, checking Dalvik Cache, System, Cache, and Data. I then realised I had the wrong Insertcoin ROM file. So with the realisation that I had to download the correct one and transfer it onto my M8, I downloaded the correct one on my Mac and did a restore of the TWRP backup that I had done previously (this was because HTC Sync Manager had to recognise my device, and it couldn't do that whilst it was in TWRP).
I restored, and rebooted the system. It looked like everything had gone smoothly, except after ~20 seconds, my M8 entered into a bootloop, where it would show the white HTC screen with the red letters "This build is for development purposes only...". Sometimes it starts up as normal, but always after a few moments it restarts again into the bootloop.
Any ideas/suggestions? Help would be greatly appreciated!

rkdku said:
Hi everyone,
I've been running ARHD on my HTC One M8 (S-ON) for the past few days. Recently I decided to get S-OFF using the firewater method.
In step one, I downloaded the OTA 3.0.7-3.0.8 Insertcoin ROM onto my device, instead of the full ROM. Without knowing this, I proceeded to make a nandroid backup from TWRP, then did an Ådvanced Wipe, checking Dalvik Cache, System, Cache, and Data. I then realised I had the wrong Insertcoin ROM file. So with the realisation that I had to download the correct one and transfer it onto my M8, I downloaded the correct one on my Mac and did a restore of the TWRP backup that I had done previously (this was because HTC Sync Manager had to recognise my device, and it couldn't do that whilst it was in TWRP).
I restored, and rebooted the system. It looked like everything had gone smoothly, except after ~20 seconds, my M8 entered into a bootloop, where it would show the white HTC screen with the red letters "This build is for development purposes only...". Sometimes it starts up as normal, but always after a few moments it restarts again into the bootloop.
Any ideas/suggestions? Help would be greatly appreciated!
Click to expand...
Click to collapse
Hi!
What version of TWRP have you installed? Did you checked the compression options when you did your nandroid backup?
I ask about the compression because I have read some people having problems with compressed nandroid backups.
If you have TWRP 2.7.1.0, just try again to wipe the same partitions like you did before, and then restore your nandroid backup. But depending on the TWRP version you have installed, wiping data partition could also wipe the sdcard partition (internal storage, not external sdcard).
Some apps store information in that partition, if one of them is having troubles trying to get information, it could lead to a bootloop.
Here you have also nandroid backups for different versions if there is no way to recover your one: http://forum.xda-developers.com/showthread.php?t=2701376
Now that you are s-off, be careful about what you flash to your M8, specially firmwares, because now nothing prevents you to do brick your phone.
Read twice what you downloaded before flashing. Check also if the TWRP version you have matches your device, I think there are different TWRP builds available for different carriers like verizon, international, etc.
Good luck & cheers!
---------- Post added at 08:50 PM ---------- Previous post was at 08:47 PM ----------
You could also install ARHD again and select wipe everything from the installer (clean install), that should work. But you will have to reconfigure everything again...

ducted said:
Hi!
What version of TWRP have you installed? Did you checked the compression options when you did your nandroid backup?
I ask about the compression because I have read some people having problems with compressed nandroid backups.
If you have TWRP 2.7.1.0, just try again to wipe the same partitions like you did before, and then restore your nandroid backup. But depending on the TWRP version you have installed, wiping data partition could also wipe the sdcard partition (internal storage, not external sdcard).
Some apps store information in that partition, if one of them is having troubles trying to get information, it could lead to a bootloop.
Here you have also nandroid backups for different versions if there is no way to recover your one: http://forum.xda-developers.com/showthread.php?t=2701376
Now that you are s-off, be careful about what you flash to your M8, specially firmwares, because now nothing prevents you to do brick your phone.
Read twice what you downloaded before flashing. Check also if the TWRP version you have matches your device, I think there are different TWRP builds available for different carriers like verizon, international, etc.
Good luck & cheers!
---------- Post added at 08:50 PM ---------- Previous post was at 08:47 PM ----------
You could also install ARHD again and select wipe everything from the installer (clean install), that should work. But you will have to reconfigure everything again...
Click to expand...
Click to collapse
Hey, thanks for the reply.
So I got things working again, by adb sideloading the v1.94 SuperSU.zip to my internal storage and flashing it through TWRP. That seemed to get rid of the bootlooping issue. It also meant that I had to reinstall SuperSU on my device (it wasn't there when it booted). Going into SuperSU, it told me that binaries needed to be updated. The installation finished, and I rebooted my device... but then the bootloops started again.
Right now I've re-flashed the SuperSU.zip so I have things working again, it's just that I can't update my SuperSU binary because of the bootloop issue.
Oh and also, I never managed to get S-OFF in the end - I got the ***** device patched by HTC, you are out of luck ***** message ... seems like I downloaded an OTA or something.

You can get s-off by using sunshine which costs around 20/25$ because of the licence...but it's worth it..
It will s-off your phone without problems as long as you are on stock Rom and stock kernel

Stuck on boot after re-installing stock recovery

Hi, when I got the phone I rooted it by installing TWP recovery, it was all working fine after that until an OTA update popped up, after some research I learned that in order to install OTA updates you need to install stock recovery. Firstly, not knowing entirely what I was doing I installed the stock recovery for the wrong software version. The phone booted however and I tried to install the OTA update, upon restarting I was met with the "red triangle" error screen. I restarted the phone and it booted up fine.
Then having found the correct stock recovery (4.16.401.10) I installed it and ran the update again. It seemed to be going fine with the loading bars moving along nicely when it got stuck on the HTC bootup logo. From here I restarted it and now the phone turns on, shows the htc logo, then gets stuck on a black screen,
Please help, Thanks.

http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508

ckpv5 said:
http://forum.xda-developers.com/htc-one-m8/help/boot-loop-problem-t3194508
Click to expand...
Click to collapse
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.

DarwinW said:
Hi, thanks for that, I guess I should have searched around harder. One question though, you mention that there is a way to restore just system to keep your data, I don't wanna loose all of my data so I'd like to do that, I'm just not sure how to apply that to your guide, what is it that I have to do differently to keep my data?
Thanks.
Click to expand...
Click to collapse
2 options :
1.
In step 8, select dalvik cache, cache, system but don't select data
In step 9, tick only boot & system and don't tick data
or
2.
Make a nandroid backup of your current ROM
Do all the steps, once completed the OTA reinstall TWRP and restore only data from your earlier made nandroid backup

Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!

DarwinW said:
Thank you so much, you're amazing. Just creating a backup now. So once I've flashed the stock rom and the TWRP recovery to restore my data, if I then install the stock recovery again, should it all work fine? or does changing the recovery at any point stop OTA updates working?
The reason I rooted my phone to start with was to use titanium backup to restore apps from a previous phone, so if I can get the phone all stock just with my data, then I don't really need root.
Thanks!
Click to expand...
Click to collapse
That's almost same as option 1 above. You need stock recovery for OTA to work.
Most important is the system part must be stock with nothing changed.
Personally, I always do option 2 to make sure OTA is successfully done .. then restore data.
One thing to note ... you don't need to relock bootloader doing all these process.

Also, now that I've created the backup (stored to the phones storage), how do I transfer that to my PC, since the phone doesn't boot, the computer doesn't recognize the storage.
Thanks.

In TWRP you have option to enable MTP then both your internal storage and microSD can be opened on PC
Make sure to use TWRP 2.8.4.0 or newer or latest. I'm still on TWRP 2.8.6.0

It seems I'm on an older version of twrp (2.7.0.2), I made the backup using this version. If I update to a newer version now will the restore work properly?
Thanks.

Usually yes we can restore a backup made with older TWRP version but I'm not so sure about 2.7.0.2 as that is the buggiest TWRP among all versions but very popular because it is included in one very old and not updated toolkit.
Why don't install latest/newer TWRP then redo the backup then transfer to PC.

I'm having trouble viewing files on my pc, I select "mount" from the main twrp menu, it then shows a screen to select which partitions to mount, I tick them, then nothing happens. There's no button to actually start the mount.

I did mentioned enable MTP function ... see below on the right side you should see Disable MTP or Enable MTP (beside Mount USB Storage) .. not those partitions to mount (but in the same screen)

I think you were right about that version being buggy. Those buttons on the bottom were missing. Just installed the latest twrp and I can mount now as the buttons to mount are showing up. Hopefully all will be fine now
Thanks.

Hi, I'm following the guide now and when I try to wipe the phone it doesn't work, I get:
Wipe Complete
Failed
"Unable to mount /cache
failed to wipe dalvik"
This error repeats a few times.
Thanks.
EDIT** scratch that, sorted it

Horray! Everything has now worked out and my phone is back to it's old self with the update, thank you so much ckpv5! you're the best.

Failed Boot after Flashing SuperSU

I finally got around to rooting my 5x this last weekend. I flashed the latest version of the SuperSU update zip. After flashing I used the SafetyNet Helper to check if my phone successfully jumps through all of Google's hoops. I failed the test, so I went back to recovery and restored my boot partition from my nandroid backup, which I created immediately after flashing and booting to TWRP. When I tried rebooting system I got a message my software was corrupt and phone got stuck on boot screen (Google logo with annoying padlock to indicate bootloader is unlocked). Went back to TWRP and tried restoring both boot and system but it was still getting stuck on the boot screen. So I downloaded the factory images, flashed everything but userdata, and phone was working again.
After some digging I found that I failed to read the fine print for the newer versions of SuperSU, stating that if you want the systemless install you have to write a couple of settings to a file in /data that the installer checks. Did this and root worked and passed the SafetyNet checks and I was happy. Then I installed AdAway and flashed systemless hosts and I'm even happier. But I'm still wondering why it was saying my software was corrupted, even after I restored my nandroid backup. Any ideas?

jgummeson said:
I finally got around to rooting my 5x this last weekend. I flashed the latest version of the SuperSU update zip. After flashing I used the SafetyNet Helper to check if my phone successfully jumps through all of Google's hoops. I failed the test, so I went back to recovery and restored my boot partition from my nandroid backup, which I created immediately after flashing and booting to TWRP. When I tried rebooting system I got a message my software was corrupt and phone got stuck on boot screen (Google logo with annoying padlock to indicate bootloader is unlocked). Went back to TWRP and tried restoring both boot and system but it was still getting stuck on the boot screen. So I downloaded the factory images, flashed everything but userdata, and phone was working again.
After some digging I found that I failed to read the fine print for the newer versions of SuperSU, stating that if you want the systemless install you have to write a couple of settings to a file in /data that the installer checks. Did this and root worked and passed the SafetyNet checks and I was happy. Then I installed AdAway and flashed systemless hosts and I'm even happier. But I'm still wondering why it was saying my software was corrupted, even after I restored my nandroid backup. Any ideas?
Click to expand...
Click to collapse
In general, phones get messed up after flashing backups or changing through multiple ROMs. The backups like nandroid backup are primarily meant for immediate resolution and a full fresh install is always recommended for any device (be it a desktop, laptop or any mobile device). Its always better to find the best suited ROM as per your needs and stick with it rather than messing up by flashing different zips through TWRP. Cheers :good:

ultraquantum said:
In general, phones get messed up after flashing backups or changing through multiple ROMs. The backups like nandroid backup are primarily meant for immediate resolution and a full fresh install is always recommended for any device (be it a desktop, laptop or any mobile device). Its always better to find the best suited ROM as per your needs and stick with it rather than messing up by flashing different zips through TWRP. Cheers :good:
Click to expand...
Click to collapse
Right. Nandroid can quickly get you out of the most common sticky situations by restoring the most commonly messed with partitions (system, boot, data). There are a bunch of other partitions that can mess things up. The only things flashed though were TWRP and SuperSU (non-systemless by mistake). I'm just trying to understand what might've gone wrong. Something outside of system/boot must have been modified and broke the boot, only after restoring the boot partition. Think I figured it out though - I looked at the update script for SuperSU and it looks like it could be messing with the vendor partition (at least for non-systemless installs). When I flashed back the stock boot image a change in the vendor partition must have tripped dm-verity, which the SuperSU installer had disabled when it updated the boot image.