Hello Everyone!
When I was restoring one of my OrangeFox 10.1_1_stable backups, My device went-off almost in the middle of the backup. I somehow managed to bring it alive. But when I restored my backup with TWRP 3.2.3-1 recovery, it was restored perfectly, and the system booted.
I had posted my problem in detail here http://forum.xda-developers.com/showpost.php?p=83046045&postcount=667
I want to know whether the recovery had bugs OR I made the error of restoring the wrong partitions?
And I have one more query too -
In official TWRP, I always made backup of every partition EXCEPT RECOVERY AND FIRMWARE, and never ever had even a single problem in backup or restore.
But in Orangefox, I saw some partitions, which were not in TWRP. The backup in which I faced problem had all partitions EXCEPT RECOVERY AND INTERNAL STORAGE (i couldnt find FIRMWARE in Orangefox, and INTERNAL STORAGE in TWRP).
So, why the two recoveries show different partitions.
And most importantly, which partitions should be backed up, that can be restored safely to get my device in previous state exctly?
So here is some additional detail.
I have one-one backup - one from my TWRP 3.2.3-1, and the other from the OrangeFox 10.1-1-stable on my PC. On viewing the files of the backups, I found the following -
Common files in both the Backups -
aboot.emmc.win
aboot.emmc.win.sha2
boot.emmc.win
boot.emmc.win.sha2
cache.ext4.win
cache.ext4.win.sha2
cache.info
cmnlib.emmc.win
data.ext4.win000
data.ext4.win000.sha2
data.ext4.win001
data.ext4.win001.sha2
data.info
devcfg.emmc.win
efs1.emmc.win
efs1.emmc.win.sha2
efs2.emmc.win
efsc.emmc.win
efsg.emmc.win
keymaster.emmc.win
persist.ext4.win
persist.ext4.win.sha2
persist.info
recovery.log
rpm.emmc.win
system.ext4.win
system.ext4.win.sha2
system.info
tz.emmc.win
vendor.ext4.win
vendor.ext4.win.sha2
vendor.info
Files present in OrangeFox backup but not in the TWRP Backup) -
cmnlib.emmc.win.sha2
devcfg.emmc.win.sha2
dsp.emmc.win
dsp.emmc.win.sha2
efs2.emmc.win.sha2
efsc.emmc.win.sha2
efsg.emmc.win.sha2
keymaster.emmc.win.sha2
modem.emmc.win
modem.emmc.win.sha2
persist_image.emmc.win
persist_image.emmc.win.sha2
rpm.emmc.win.sha2
sec.emmc.win
sec.emmc.win.sha2
splash.emmc.win
splash.emmc.win.sha2
system_image.emmc.win
system_image.emmc.win.sha2
tz.emmc.win.sha2
vendor_image.emmc.win
vendor_image.emmc.win.sha2
Files in TWRP backup that are not in OrangeFox backup -
data.ext4.win002
data.ext4.win002.sha2
data.ext4.win003
data.ext4.win003.sha2
Viewing these... can someone find out which restoring which partition from orangefox caused problem for me?
Related
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.
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?
Hi
1. How can I backup the efs partition with TWRP v2.7.1.0 that is already installed on my xt1022?
If I boot to TWRP recovery, touch the backup icon, so I get only the possibility to backup:
[x]System
[x]Data
Cache
[x]Boot
But I don't get the choice for efs, like there is one I saw on pictures (hyperlinks are not allowed for new xda users) an older TWRP version then mine for an other smartphone.
2. How can I backup the efs partition with an dd linux command - in an root adb (root already activated)?
3. How can I then restore this efs partition in case of an efs disaster?
Thanks in advance!
Use this: https://play.google.com/store/apps/details?id=ma.wanam.partitions
It automatically highlights appropriate partitions. Restore functionality is also available.
When I was installed ZCX TWRP. That time i was Nandrodroid backuped my all system, data, efc all file.
After restored time my Nandrodroid backup file are come successfully but not flashed now.
Showed this error #unmount storage
Why showed this error? How to solve them? And what the TWRP are help to restored my Nandrodroid backup file.
NB: sorry my bad English
Nazmul.i404 said:
When I was installed ZCX TWRP. That time i was Nandrodroid backuped my all system, data, efc all file.
After restored time my Nandrodroid backup file are come successfully but not flashed now.
Showed this error #unmount storage
Why showed this error? How to solve them? And what the TWRP are help to restored my Nandrodroid backup file.
NB: sorry my bad English
Click to expand...
Click to collapse
Most of the times, Backup made from unofficial recovery isnt compatible with other recoveries. so u have to restore it using same recovery.
i personally dont like zcx as it has given me several times encryption decryption data corruption. might be it was my mistake but on the run i use alka recovery. its good its just u have to enter name of backup manually as it doesnt show correct time.
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.