Related
Hey guys, ive read every solution to Error: run ' nandroid-mobile.sh restore ' via adb! hero, eris etc whatever phone that has this problem and no solutions work. ive run the restore through adb and restores just fine. but that is a pain in the ass. i wanna restore via recovery. sometimes ill be running a rom and need to switch to run gps or 4g etc. ive partitioned the sd card. ive made a new restore of current rom and flashed a different rom and restored and works just fine. but what about all of my other nandroid back ups i put them back on and get that error. even my original before i started rom flashing. should i unroot and flash it to stock etc and start fresh? sorry if its just ramblings and not really questions but dont now what to ask. i just want my backups to work. ps have over 7 gb free and battery is full and plugged in when tring to restore. ive flashed restores with alot less
crzy619 said:
Hey guys, ive read every solution to Error: run ' nandroid-mobile.sh restore ' via adb! hero, eris etc whatever phone that has this problem and no solutions work. ive run the restore through adb and restores just fine. but that is a pain in the ass. i wanna restore via recovery. sometimes ill be running a rom and need to switch to run gps or 4g etc. ive partitioned the sd card. ive made a new restore of current rom and flashed a different rom and restored and works just fine. but what about all of my other nandroid back ups i put them back on and get that error. even my original before i started rom flashing. should i unroot and flash it to stock etc and start fresh? sorry if its just ramblings and not really questions but dont now what to ask. i just want my backups to work. ps have over 7 gb free and battery is full and plugged in when tring to restore. ive flashed restores with alot less
Click to expand...
Click to collapse
I usually got that issue when one of two things happened. The nandroid backup I did was corrupted, or never backed up right. Or two, when I changes the name, and added spaces or certain symbols it borked it.
If you haven't changed it, it may just not have nandroid backedup correctly. If you are able to restore via ADB then do so and renandroid.
Did you use illegal characters in your file name? Did you try to restore a clockwork backup with amon ra or vice versa?
ive only used amon ra from the very beginning. i will try clock just cuz i can. and nope all the backups ive tried are original names. i have renamed some in the past and they have restored fine before. but ones im trying are original. i cant even flash the first nandroid i made and ive gone to that one bunch times?! idk cuz this randomly started happening.
crzy619 said:
ive only used amon ra from the very beginning. i will try clock just cuz i can. and nope all the backups ive tried are original names. i have renamed some in the past and they have restored fine before. but ones im trying are original. i cant even flash the first nandroid i made and ive gone to that one bunch times?! idk cuz this randomly started happening.
Click to expand...
Click to collapse
Did you make any changes to system files? The files may be corrupted.
crzy619 said:
ive only used amon ra from the very beginning. i will try clock just cuz i can. and nope all the backups ive tried are original names. i have renamed some in the past and they have restored fine before. but ones im trying are original. i cant even flash the first nandroid i made and ive gone to that one bunch times?! idk cuz this randomly started happening.
Click to expand...
Click to collapse
what version of Amon-Ra are you using? If your not using 2.3 go flash it immediately and try again.
I know that I have seen this question asked before but I can't find the post. I broke my evo (let's call it #1) and I am trying to restore evo#1 CWM backup onto evo #2 the new phone that I just got. I have put the sdcard from evo#1 with its latest backup into evo#2 and have booted into recovery.
I remember seeing that you can't do a full restore but rather to use Advance Restore but I don't remember which components to restore and which not. I think that I restore all but WIMAX bacause WIMAX is different for each phone.
Anyone know ??
ChadH42 said:
I know that I have seen this question asked before but I can't find the post. I broke my evo (let's call it #1) and I am trying to restore evo#1 CWM backup onto evo #2 the new phone that I just got. I have put the sdcard from evo#1 with its latest backup into evo#2 and have booted into recovery.
I remember seeing that you can't do a full restore but rather to use Advance Restore but I don't remember which components to restore and which not. I think that I restore all but WIMAX bacause WIMAX is different for each phone.
Anyone know ??
Click to expand...
Click to collapse
Generally, I don't believe it's recommended to restore a backup from one phone to another. However, I've seen reports that it it can be done. As you assumed, you are correct by NOT restoring the wimax. If you were to do that, it would restore the RSA keys of your old phone, overwriting your NEW RSA keys. You don't want to do that. So remove the wimax.img from your nandroid backup before you restore.
Also, I'm not positive on this, but I do believe that if your old backup was made on a certain hboot version, that you need to be on the same hboot version when restoring that backup. (lets say you when you created the backup, your hboot version was 2.10, then when you restore your backup, be sure the hboot version on the new phone is also 2.10). The reason I believe taht to be true, is because I had always had hboot .93 on my phone, and all backups I had ever made were when I was running .93 hboot. I then downgraded to the ENG .76 hboot, (to use fastboot), and I tried to restore a backup that had been created when I was on .93 hboot, and it did not go well. After the backup restored and I rebooted, it booted straight to fastboot, and that was the only place I could get. None of my old backups would restore. I then switched back to hboot .93, and my backups restore perfectly fine. So that is what led me to my conclusion. Good luck with your quest. ( i personally recommend just starting fresh, and not restoring an old backup, just to be safe)
k2buckley got you covered, but restoring a backup from an old phone to a new one WILL cause you problems, and the easiest way to avoid it is to not do it.
The best you can do is backup your apps via titanium backup and your launcher settings, transfer those folders to your new phone. When restoring the apps, do only app and data, NOT system settings.
Thank you both for the reply. Based upon your feedback I decided to do a clean install of everything.
You're welcome; just trying to make it smooth as possible.
I have done a quick search on this but didn't come up with anything that refers to my specific problem.
I did two backups tonight.. one before I went back to stock w/root and one about ten minutes ago once I got back to almost where I was before going back to stock.
Neither one of them are showing up in the menu on CWM recovery?!? I did a Titanium Backup as well as the nandroid bu so I was at least able to get my data back but I really wanted to restore the first backup I made this evening before I had issues and had to restore an older backup... what I'm wondering is where are the backups? I looked in the clockworkmod/backup folder on the sd card and nothing from tonight shows up.. just my previous bu I made before flashing a ROM. Any help?
No ideas huh?
I just did two Nandroids in Rouges custom recovery based on CWM. It's CWM based so I assume this is going to be the same.
OK! Now I would assume they would/should end up the clockworkmod folder but my phone keeps putting them in /emmc/emmc/bmmc/*
I went into that folder, found the two I just did and moved them over to clockworkmod/backup/* and my recovery instantly saw them and I was able to restore to them.
Not sure why this is the way it is, maybe someone else can shed some light?
Like the previous poster mentioned, sometimes different versions/builds of CWM store their backups in different directories. When backups don't show up, usually the backups are all there, just CWM isn't looking for them there.
You may have gotten different versions of CWM inadvertently by installing a ROM that included a kernel with a different version/build of CWM.
If you manually move the backup directory to the place where your current CWM is expecting them, they'll be seen again.
Hi all,
So I've been on paranoid android for the past few months, and I had to revert back to stock for work reasons tonight; it's been a while since I've done my routine backups.
Having made my standard nandroid backup and restored to stock via ODIN, I was horrified to discover that none of my stored nandroid backups would work, running into system/data restore errors every time. I've just read that clockworkmod uses a new process that keeps each individual backups small but requires the presence of a .blob file of sorts, which must have gotten erased when I flashed stock. I checked the size of my nandroid backups and sure enough, they were only around 20 megs; it looks like my internal memory was wiped clean.
My questions are: is everything pretty much gone? And if so, WTF is the point of nandroids if they're no longer self-contained backups? If the devs indeed made changes that led to this, it reeks of inconsiderateness, if not just plain ineptitude.
I apologize in advance if I'm venting or missed something obvious, but I've been at this for a while now and exhaustion is just turning into frustration.
Thanks for your feedback/help.
Blob backups are incremental. Tar backups are full.
When CWM 6 was released, the devs made blob the default backup format. Later versions changed it back to tar.
You can manually change this setting through the CWM options.
As far as your backups being hosed, its tough to say without having the device in front of me. Are you attempting to restore with the same version that created the backup?
For what it's worth, I mirror your opinion about incremental backups being a terrible idea.
Aerowinder said:
Blob backups are incremental. Tar backups are full.
When CWM 6 was released, the devs made blob the default backup format. Later versions changed it back to tar.
You can manually change this setting through the CWM options.
As far as your backups being hosed, its tough to say without having the device in front of me. Are you attempting to restore with the same version that created the backup?
For what it's worth, I mirror your opinion about incremental backups being a terrible idea.
Click to expand...
Click to collapse
Thanks; I did try multiple recovery versions including older ones, but the internal memory was wiped since I formatted system so I'm pretty sure everything's gone. Clockwork has been such a useful tool but I really have to wonder what they were thinking when they did this, ugh.
C'est la vie
HTC One V [CDMA], Virgin Mobile US, original (pre-OTA) radio version, TWRP recovery
Has anyone else experienced flakiness with Nandroid backups on this phone? All of them that I've done with major OS changes—even after factory reset—have failed to produce a working restore even though they were taken from a working state.
I'm also unable to get back my previously-working CM 10.1 ROM even though I followed the exact same procedures (with the same files) that I used to get it working before.
This has been happening since my first failed Nandroid restore trying to go back from CM 10.1 to the HTC Sense Nandroid backup I made before attempting CM 10.1 in the first place. I thought this was due to the Sense Nandroid having been made under the OTA-upgraded radio version (I had to use the stock rom.zip from the RUU to get CM 10.1 working at all), but now I'm not so sure. I get the HTC logo and angry red legal text indefinitely now with those setups.
I can't even get back to the Nandroid I made of the stock HTC Sense ROM right after I restored from the RUU's rom.zip.
Anyone have any idea what I'm doing wrong? Or is this model really just that much of a pain?
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
riggerman0421 said:
Are you flashing the correct kernel in fastboot after completing the restore? The recovery is not able to flash a kernel, that still needs to be done through fastboot, even with a nandroid restore.
Click to expand...
Click to collapse
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
mynewshiny said:
That's the boot.img, right? I did try flashing that after the restore didn't work the first time. No joy.
EDIT: Actually, that explains why some of my restores have failed, but not all of them.
EDIT 2: Mystery solved. I think. The Nandroid backup I took yesterday evening must be broken somehow. I noticed a few minutes ago that TWRP wasn't actually telling me that it finished restoring the backup—it was just taking me back to the home screen. I switched to CWM Recovery to grab a backup I took yesterday Morning, and that one worked.
So now I'm just left extremely disconcerted that I can't be certain my backups are reliable.
Click to expand...
Click to collapse
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
mynewshiny said:
I originally thought this was just an isolated incident, but it seems to be recurring. Several of the Nandroid backups I've made more recently, both within TWRP Recovery and via the Online Nandroid Backup app, seem to produce this result. (Fortunately, I have a known good backup that I've been able to use reliably.)
Is there a way to validate a Nandroid backup other than trying to restore from it? I don't mean comparing a hash (which is what I find using Google), but rather making sure that the original, uncorrupted file is valid for use as a backup.
As a side note, every backup I've done with CWM Recovery has been reliable, so my fallback plan is to switch to CWM. I just find TWRP easier to navigate.
Click to expand...
Click to collapse
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
so as a conclusion, nandroid backup won't restore boot image? and the option in cwm advance restore>restore boot is useless? Me also always got stuck using nandroid restore
Ken-Shi_Kun said:
I've played with recovery files before (se my signature) when cwm wasn't working well.
Basicly if you want to know that the backup is correct, you can only compare the hash codes (nandroid.md5) which is practically useless, because hases are made only for the .img files, so the OS itself is not protected like this, which is somehow ok, because the files are compressed to a .tar file, which also means it has it's own validation algorithms itself. So you can validate it if you can decompress the file (don't ask that how it could be done under windows) without errors, it should be allright.
I personnaly can say only this: use CWM 6. i-don't-know-which version (which is online now). There is a possibility for cache not mounting, and of course a backup to not be full, but as you can see from my signature, it can be "bypassed" so the OS will be backed up, and because we don't have S-OFF, it doesn't really matters. All of my backups from CWM is working (have at least 10 gigs at the time, from stock to EV).
Click to expand...
Click to collapse
sellersj27 said:
I always use android file verifier by scary Allen (free market download). It has saved me many times!
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Confirmed that comparing file hashes isn't helpful for this purpose—I just downloaded scaryalienware's AFV as suggested and ran it against several of my Nandroid backups. It said all of them succeeded, including at least one of which I know will not restore successfully. However, of interest is the fact that it took about half as much time to scan the known "bad" one, and further analysis shows that it's about half the size of the others. I'll have to make some more backups via the various mechanisms to confirm that the size is an indicator; it may be simply that I had fewer apps installed when making those backups.
Too bad there isn't some kind of Nandroid Restore Simulator. But even if there was, this phone probably wouldn't have enough memory to use it. Checking Nandroid backups in a VM would be awesome though!