Can't restore NANDROID backup on Nexus 7 - Android Q&A, Help & Troubleshooting

Hi, all.
I've been reading and searching, but haven't found any info related to my problem.
Prior to upgrading to 4.2.1, I made a NANDROID backup of my Nexus 7 (4.1.2) using mskip's toolkit. The restoration method copies the backup folder to the device (/sdcard/clockworkmod/backup/), then boots it into custom recovery. At first I was using TWRP 2, but I think I need to be using CWM, so I flashed CWM Touch. I actually went through the motions again of copying the backup over to the Nexus 7, but CWM Touch doesn't see the backup folder. It returns two messages when attempting to Restore:
1. Couldn't open directory
2. No files found
Same with Advanced Restore.
The folder containing the NANDROID backup and all parent folders are readable/writable/NOT Hidden, according to ES File Explorer, but I wonder about ownership.
I'm rooted with SuperSU 0.99.
Anyone have any suggestions about how to make CWM Touch, TWRP 2 or some manual method recognize and restore a NANDROID backup?
I know I could just flash stock 4.1.2 and start from scratch (I have apps + data backed up), and if it comes to it, I'll do that, but while I have some time, I thought I'd make this a learning experience.
Thanks.

ThurstonX said:
...
Click to expand...
Click to collapse
Same problem here, any solutions?

xXSturmiXx said:
Same problem here, any solutions?
Click to expand...
Click to collapse
I posted this a few minutes ago. It may be TL;DR, but it's got all the gory details.
I'm not sure exactly what's going on, but in essence, you can use adb to push the NANDROID backup folder to /data/media/clockworkmod/backup/, then boot into recovery and CWM will see it.
The weird thing is, after I restored the 4.1.2 factory ROM, rooted, flashed CWM Touch, and then ran a backup from within CWM to create /data/media/clockworkmod/backup/ ... /sdcard/clockworkmod/backup/ was also created. I guess it's a symlink...? Haven't explored that yet, but I seriously doubt the backup data is being duplicated.
Anyway, after pushing my original backup folder to /data/media/clockworkmod/backup/, it's also listed under /sdcard/clockworkmod/backup/ That's why I say symlink.
I was able to restore while still running 4.2.1, but /sdcard/0 still had all apps and data there, which is why I decided to just go back to stock 4.1.2 before restoring my 4.1.2 NANDROID backup. Maybe I did something wrong, but I don't think so.
So yeah, the new CWM Touch Recovery is backward compatible. My 4.1.2 backup did NOT use CWM, so no "blobs" and all that. Good news there.
I suppose if you're restoring a 4.2.x backup over a custom ROM based on 4.2.x, but CWM can't see the backup folder under /sdcard/clockworkmod/backup/ just push it to /data/media/clockworkmod/backup/ and you should be good to go.
Anyone know if a 4.1.2 NANDROID backup can/should be restored over a 4.2..x install? Is the /sdcard/0 problem really a problem. NANDROID doesn't back up /sdcard, correct? I'm guessing it does not.

Boot into recovery w/your tablet plugged into your computer
Code:
adb devices
adb remount
abd pull ./where/your/backup/is/located
adb push ./yourbackup /where/it/needs/tobe
or if you have a jacked rom and cant do anything, you can do what I did
Code:
adb devices
adb remount
adb push ./newrom /sdcard
adb reboot recovery
then wipe and flash your new rom

Related

Problems restoring old nandroids

I had my phone replaced recently, and I rooted it and tried to put my old nandroid back on but it won't restore from Amon Ra, I have to use ADB and run the shell script. I thought maybe because I switched phones but any nandroids I run now still require me to go into ADB to restore them.
Any ideas what could have caused that?
Stonent said:
I had my phone replaced recently, and I rooted it and tried to put my old nandroid back on but it won't restore from Amon Ra, I have to use ADB and run the shell script. I thought maybe because I switched phones but any nandroids I run now still require me to go into ADB to restore them.
Any ideas what could have caused that?
Click to expand...
Click to collapse
The answer you seek can be found in the recovery log file /cache/recovery/log
Run the Nandroid restore from the menu, and then have a look at the end of that file
bftb0
When I got a new phone what I did was:
a) Copy the contents of the nandroid folder (not the folder iwth the #s/letters, the .iso files and stuff inside it)
b) delete that folder
c) create a nandroid backup
d) delete that backup
e) put the contents from step a) into the new nandroid folder.
Solved it.
Thanks all. I've got some things to try now.
I had problems flashing old nand backups because of having a different kernal.

[Q] Problems restoring data (corrupt Nandroid backup?)

I wanna start by saying that I have been searching and I can't find a similar post...forgive me if I was simply unsuccessful :/
So here's what happened.
Me - "Hey! I've got a rooted phone, but no custom ROM? I think I'll download one!"
I performed a Nandroid backup.
Flashed Macnut 14.
"Awesome, it works. Now I'm gonna restore my data."
I tried doing an advanced Nandroid restore, but it hung at "dalvik-cache".
I then tried doing a full Nandroid retore, but it still hung at "dalvik-cahe".
I then flashed Stock JK6 and repeated steps 5 and 6 with the same results.
I then downloaded and compiled unyaffs in order to get files out of the Nandroid .img files.
I tried "adb install" for apps and "adb push" for both data and apps. I've been getting error messages for both approaches (not syntax errors, but things like "permission denied," "not enough space," etc.), both while the phone is booted and when it's in recovery.
I've also tried moving the files to my SD card and then using "adb shell" to move them to their appropriate folders, but that didn't work either.
Besides these errors, I also had a very hard time figuring out where to put certain things.
So that's what happened...you guys are my final hope. I'm trying to figure out a foolproof way to restore (in order of priority):
Application data (settings, high scores in games, etc.).
Applications themselves (.apk files, preferably not overwriting newer versions of things like GMail, Youtube, etc. included in Stock JK6).
Text messages.
Phone settings.
I've learned my lesson...next time, I should use Titanium Backup.
Thanks,
Gerard
Personally I would:
1. ODIN to JK6
2. Root and use the modified 3e recovery
3. Install ROM Manager from the market and flash CWM Recovery
4. Then attempt to Nandroid restore
If you're not comfortable with the above Step 2 you can:
1. ODIN to JFD and root
2. Install ROM Manager from the market and flash CWM Recovery
3. CWM Flash JK6
4. Attempt to Nandroid restore
You went from eclair to froyo and when you restored your backup, CWR does not restore the kernel.
Try flashing the stock 2.1 kernel and then restoring your backup.
And yes, titanium backup & SMS Backup+ are your friends.
hmm... re-read... it's odd that a restore started and didnt finish. Most people get hung at the vibrant screen when they do not restore the kernel.
Sounds like you nandroid is corrupt, and if that is the case I'm afraid that I do not know the answer you seek.
Yeah, I don't think that a Nandroid backup is gonna do the job...I just tried again after ODIN.
Any other ideas?
EDIT: I was finally able to push all my applications back...However, I'm having trouble pushing the contents of "data/data/" and "datadata/". I keep getting errors like:
failed to copy 'data/com.android.browser/app_appcache/ApplicationCache.db' to 'datadata/com.android.browser/app_appcache/ApplicationCache.db': No such file or directory
Click to expand...
Click to collapse
How can I evade this error? :/
You have to flash a kernel as well cause nandroid won't replace that
Sent from my GT-I9000 using XDA App
Are you trying to adb from linux or windows? If you are on linux try this:
1) sudo adb kill-server
2) sudo adb devices
3) now push your apps
Also I found out the hard way, do not restore apps or system data from nandroid backup, I always had a corrupted system with a lot of force closes. Always use Titanium Backup and SMS Backup.
Hope this helps
brnbock said:
Are you trying to adb from linux or windows? If you are on linux try this:
1) sudo adb kill-server
2) sudo adb devices
3) now push your apps
Also I found out the hard way, do not restore apps or system data from nandroid backup, I always had a corrupted system with a lot of force closes. Always use Titanium Backup and SMS Backup.
Hope this helps
Click to expand...
Click to collapse
I'm actually on a Mac. I tried your method but I still got the same results...is Mac close enough to Linux (since it's Unix), or do you think I should attempt it on Linux as well?
DEFINITIONOFREAL said:
You have to flash a kernel as well cause nandroid won't replace that
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I don't mean to sound like a douche...but isn't that what s15274n was saying?
ya try it on linux, Mac is BSD based but I'm not sure how permissions are set. BSD is close to linux but there are some major diff and some commands are diff.
So far, for me Nandroid on the Vibrant has been completely useless. I don't even bother any more.
I use Titanium to back up my apps and my SMS messages, and it only takes a couple minutes to re-do the settings once I install a new ROM.
This is way different than my experience with the G1, where I could easily restore a Nandroid backup if I didn't like a new ROM install. On the Vibrant it's easier to just Odin back to a stock ROM and redo all my settings using TB.
brnbock said:
ya try it on linux, Mac is BSD based but I'm not sure how permissions are set. BSD is close to linux but there are some major diff and some commands are diff.
Click to expand...
Click to collapse
Yeah...tried this too after downloading and setting up everything on my Linux box (java, Android SDK, etc.). Same error as I got on my Mac
I think I'll take like one more suggestion from the community before I finally give up and start my phone from scratch...It's been like 3 days since I lost all my data, ugh.

[Q] Extracting CWM6 Backups

Hello, while I was using my phone it rebooted and aparrently someting from my /data got corupted disabling my Rom from booting ever again.
So I created a nandroid via CWM6, installed a new rom and I'm now scratching my head on how to extract certain apps from that backup. Using CWM5 I could do this via the use of Titanium Backup, but now it's more complex than that CWM6 nandroids are unreadable from anything that exists out there. The only app which could analyze the backup correctly was the latest beta of "app extractor" but even that could not extract the apks *with* their data.
Basically my apps' data is precious and I wish to restore it at all costs, I have a nandroid of them, but the format is so unspeakably complex that it is basically useless. So the other "solution" was restore the nandroid and pull the whole /data partition in my PC via ADB, but I'm not sure what I can do with it.
So as it stands I now have two copies of my apps, one in a nandroid format another as it was pulled from the phone but I'm not sure how I can go on and restore them in a new rom. As I have found out CWM6 was quite a downgrade for/to those who backup/recover frequently, it's sad that I have found about it in such a disastrous way

(Rooted and CM11) Have I got everything ready in case I ever screw my phone up?

Hi guys,
Only recently did I recover my phone from a soft brick and since then; learning and living everything XDA and Android I decided to flash CyanogenMod on my phone. Loving it! Aside from the terrible Trebuchet launcher. I since downloaded all my apps and the like, flashed Philz recovery. Anyway, the following is everything I have backed up on my computer and all the files I have. Have I forgotten anything?
I am asking if you can actually read this and make sense of what I'm asking, do I have everything in case I end up screwing my phone I have everything needed? The user Darke5tShad0w was extremely helpful and he drilled it in my to backup the efs file for my S3 but I am unsure if I actually have backed that up, however there is an actual efs backup on my phone's internal memory in a folder named clockwork mod, I'm unsure though if I do in fact have a backup of the efs.
Phone - Samsung Galaxy S3 (GT-i9300)
CyanogenMod 11
Philz Touch 6.48.4
On computer / Backups
cminstaller
# S3
clockworkmod
backup
.efs_backup
(bunch of folders and disc image files – all the same really)
.recovery_version
Odin
Odin3
Stock Backup
Backup
clockworkmod
backup
2014-09-20.01.15.48_JSS15J.I9300XXUGMK6
philz-touch_6.sav
Stock Recovery
International-GT-i9300-StockRecovery.tar
Stock ROM
I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md 5
SS_DL.dll
philz_touch_6.48.4-i9300 (zip)
TitainumBackup
update.zip
Sorry, I know it's difficult to read but I've tried to get all the information across and attempted to make it readible. Italics are folders while bold is like the root folder containing what I need.
Reason for all the stock files is in ever the case I need to restore to my last rendition of TouchWhiz, install Touchwhizz and reinstall the stock recovery.
Would it be worth doing a nandroid backup of my current CyanogenMod settings and what have you? Would the process be the same? In case I ever softbrick, wouldn't just using the Installer be enough.
JJKirby said:
Sorry, I know it's difficult to read but I've tried to get all the information across and attempted to make it readible. Italics are folders while bold is like the root folder containing what I need.
Reason for all the stock files is in ever the case I need to restore to my last rendition of TouchWhiz, install Touchwhizz and reinstall the stock recovery.
Would it be worth doing a nandroid backup of my current CyanogenMod settings and what have you? Would the process be the same? In case I ever softbrick, wouldn't just using the Installer be enough.
Click to expand...
Click to collapse
Hello again.
If you did it all through philz like was said in the other thread and it didn't fail when you did it you should be sorted.
If you want to make doubly sure another app like ktool to create another efs backup.
Remember to keep a copy on your computer or somewhere else.
And yes it would be a good idea to do a nandroid backup now you have cm up and running.

How to recover data from "adb backup --twrp" archive? Been through hell and back

How to recover data from "adb backup --twrp" archive? Been through hell and back
I have two backups I made using "adb backup --twrp" while my OnePlus one phone was in TWRP recovery 3.2.1-0 running LineageOS with a recent build (don't know exactly which one, but it was from Feb/March 2018). Each of the backups are about 6.0GB so they appear to be complete backups. I am trying to recover one app and its data (Signal/Textsecure) but the rest would be nice too. The backup files have .ab extensions. I am fairly android savvy and have been working on this for days, your help is VERY MUCH APPRECIATED! I have access to Windows and Linux.
I have tried the following:
-"adb restore filename.ab" while in TWRP recovery. It appears to restore (progress bar goes, it reports success, etc), but no apps are restored. I have tried this both with totally wiped partitions/system/data and with a fresh install of LineageOS. As far as I can tell, nothing happens. When doing a restore after a full wipe and trying to restart, TWRP warns that no OS is installed.
-Restoring using the restore menu in TWRP. Immediately upon clicking on the backup, the phone restarts and TWRP opens again. Not sure what's going on there.
-Opening the backups in Titanium Backup, Nandroid manager, and a few other apps. None of them worked. Titanium backup crashes instantly in recover from ADB, doesn't recognize the backups in nandroid recovery mode.
-Opening the .ab files in an archive manager, all of which report it isn't a valid tar archive. One time I was able to get a list of directories, and things looked pretty right, so I know at least some of the data should be there. Running variants of this command with different skip values, none of which produces a valid tar file dd if=file.ab bs=512 skip=1 of=test.tar
Questions:
- Is there a way to extract data from these backups in Linux or Windows outside of Android? From what I read, TWRP adds some stuff in the headers which makes them invalid tar files, and that doing "adb backup --twrp" is different from a regular TWRP backup.
- Why is TWRP crashing? Is there a log I can look at for this and how? Maybe i can find a way to diagnose it that way.
- Where does Signal store message data? I have a flat-file backup that may have this information depending on where it's stored.
- Can I somehow convert these backups to a different format that might be better-tolerated by TWRP or other apps?
- Any good utilities for reading a corrupted tar file? I think all this utility would need to do is skip through the junk at the start.

Categories

Resources