i switched to twrp recovery (v2.6.3.0) recently. i usually do backups while the phone is still switched 'on' - i.e., without booting into recovery - by either of the following methods:
----------(i) using online nandroid backup app (v4.2.1)
----------(ii) executing the appropriate command after installing onandroid script (v9.20)
these backups are created in /sdcard/TWRP/BACKUPS/0000000000000000/. but, backups done from within recovery are created in /sdcard/TWRP/BACKUPS/Micromax_A116/.
'restore' from within recovery detects backups located in /sdcard/TWRP/BACKUPS/Micromax_A116/, but not /sdcard/TWRP/BACKUPS/0000000000000000/.
since i wanna be able to restore my backups with ease, rather than having to first move the backup from the former location to the latter location, i'd like help regarding the following:
----------=> saving the backups created by "online nandroid backup app" or "onandroid script" directly in /sdcard/TWRP/BACKUPS/Micromax_A116/
----------=> getting twrp recovery to detect backups in /sdcard/TWRP/BACKUPS/0000000000000000/
i'm a bit . somebody please help. thanks.
Related
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
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
When I try to recover my apps using Titanium Backup's "Extract from Nandroid" feature, it says "Could not find any data in this TWRP backup"
The files in my TWRP backup folder are
data.ext4.win000
data.ext4.win001
data.ext4.win002
md5 for the above
recover.log
Any help would be appreciated
Yup, same problem here. Im on a Galaxy Nexus running XenonHD and TWRP.
I've tried unpacking them on my pc, so i could use an emulator and run my phone through there.
That kinda works, and using Titanium Backup, it seems to extract it without an error. But afterwards, the app is very glitchy.
Im guessing Titanium Backup doesnt really do well on TWRP as i had no problems using clockworkmod.
I'm experiencing the same problem running Marshmallow trying to restore apps from a TWRP backup (Galaxy S4). At first, Titanium backup just refused to even see the backup files (although it accepts the containing folder as a backup location). Once it finally and magically accepted to see the backups it now tells me that it cant find any data in them...
Has anyone solved this yet?
I've been using onandroid to make CWM backups of my device for a while now.
It does work really well and I want to take the time to congratulate onandroid developer, congratulations Ameer!
Anyway, I recently got a TWRP image that supports my device and was very pleased with it as it has neat features compared to CWM (which is still awesome and flawless). So, I flashed TWRP recovery image and the next thing I did was create a typical TWRP backup with onandroid (v9.51).
Now, the thing is that I cannot properly restore the backup from TWRP. The system/kernel/recovery images seem to be recovered correctly because the system boots fine after a complete wipe, but the data is just not there. Instead I'm greeted with the typical brand new Android OS language selection, bla, bla. Everything is missing.
In an attempt to understand why I also backed-up my tablet's system and data partitions with TWRP (from recovery), this is what I ended up with both method:
TWRP
=====
system.ext4.win (508 MB)
data.ext4.win000 (1.47 GB)
data.ext4.win001 (805 MB)
Onandroid v9.51
=============
system.ext4.win (507 MB)
data.ext4.win000 (1.02 GB)
data.ext4.win001 (1.16 GB)
data.ext4.win002 (30.0 MB)
TWRPs backed-up data partition is correctly restored while onandroid isn't. Also, the contents of those archives are totally different. TWRP creates a data.ext4.winXXX structure with AndroidManifest.xml, resources.arsc file, res and META-INF folder, etc... while onandroid structure is the raw folder/file structure from the partition. I also need to mention that onandroid doesn't log any error during the process which takes around 10 minutes.
Is this normal? Am I doing something wrong?
I also tried using onandroid through Online Android Backup and I had the exact same result/problem.
PS: FYI my data partition is >2GB
Thanks for the help.
I am having the same problem. Restoring from onandroid backup restores everything but the data for me. I have tried multiple different ways to restore the data but no luck.
Teleshot said:
I am having the same problem. Restoring from onandroid backup restores everything but the data for me. I have tried multiple different ways to restore the data but no luck.
Click to expand...
Click to collapse
Sorry about this but... FINALLY!
I thought nobody else had this damn problem.
I concluded onandroid is the problem because the backups do not follow the norm in comparison to the ones made by TWRP recovery.
I'm not sure if TWRP backups were officially made differently in previous versions. This is the single thing keeping me from using TWRP as a whole.
I even posted this issue on onandroid Github but so far I had no reply from the developer. Fortunately I have a choice between TWRP and CWM, unfortunately not everyone has both compatible custom recovery roms.
I have the same problem with a CWM based recovery. Everything is restoring fine but when It comes to the data it stops with an error
DirkStorck said:
I have the same problem with a CWM based recovery. Everything is restoring fine but when It comes to the data it stops with an error
Click to expand...
Click to collapse
That is a very different issue and I don't get errors restoring TWRP backups, it just doesn't restore the data.
Anyway, what error(s) do you get while restoring your CWM backup?
Is your data partition over 2GB?
What CWM backup method do you use (default, split, incremental)?
What is your CWM rom version?
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.