android-backup-processor Activity
Android adb backup extractor and packer
Brought to you by:
dragomerlin
Activity for android-backup-processor
No more activities
-
dragomerlin modified a comment on discussion General Discussion
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all in good faith), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that:...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all in good faith), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that:...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all in good faith), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that:...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all in good faith), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that:...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all in good faith), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that:...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all in good faith), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that:...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup/savestate of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. Adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably all), but as time went on, it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. adb backups are actually partial backups with the strongest boundaries. The adb backup was intended initially to backup only user apps and data (probably al), but as time went on it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want...
-
adb backups are nowhere near a ISO/raw/dd/1:1/clone/mirror/backup of an android phone. Only very few apps and its data gets actually backed up. adb backups are actually partial backups. The adb backup was intended initially to backup only user apps and data (probably al), but as time went on it got neglected, because Google didn't have the courage to fully remove it but didn't want people to use it either. You see, there are reasons for that: App developers don't want people randomly backing up stuff...
-
Courtney Alan White posted a comment on discussion General Discussion
Hi, I did a simple console command in adb app control to create a backup.ab file that I THOUGHT had my full phone contents, from pictures to app data and everything When I finally got this tool to work, I was presented with a measly selection of a few random app data's, nowhere close to my full library. I thought this was gonna take like an iso image of my phone, a complete replica of the internal file structure What I got doesnt seem to be the case. Can you guys verify that I either did something...
-
Since you are extracting you must provide tar name: java -jar abp.jar -debug unpack viewer.ab viewer.tar Then you can view or extract tar with any app, is similar to zip or rar.
-
Conrad Braam modified a comment on discussion General Discussion
step 1: adb backup -f viewer.ab -noapk com.realvnc.viewer.android this creates a nice 1.2Mb file called viewer.ab , all good step 2: java -jar "<path to="" binary="">\abp.jar" -debug unpack .\viewer.ab <some file="" name=""> now that last parameter is terribly confusing do I need to know what fiels to pull out of the backup, how do i list the backup contents? No commandline documentation nearthe top of any of the readme files.</some></path> $> java -jar abp.jar info .\viewer.ab android-backup-processor...
-
step 1: adb backup -f viewer.ab -noapk com.realvnc.viewer.android this creates a nice 1.2Mb file called viewer.ab , all good step 2: java -jar "<path to="" binary="">\abp.jar" -debug unpack .\viewer.ab <some file="" name=""> now that last parameter is terribly confusing do I need to know what fiels to pull out of the backup, how do i list the backup contents? No commandline documentation nearthe top of any of the readme files.</some></path>
-
the documentation says to replace abe with abp , but since .ab files get emitted by the backup tool, not TAR files, which abp wants. The new abp tool will not ingest these.ab files, so this tool looks like it's just undocumented in a way that cannot serve it's purpose. Are there alternative updated tools that dont require large downloads and other setting up for simple scripted .ab extractions?
-
the documentation says to replace abe with abp , but since .ab files get emitted by the backup tool, not TART files, which abp wants. The new abp tool will not ingest these.ab files, so this tool looks like it's just undocumented in a way that cannot serve it's purpose. Are there alternative updated tools that dont require large downloads and other setting up for simple scripted .ab extractions?
-
Ashish Kumar posted a comment on discussion General Discussion
DSC_0006.JPG is the encryped file and i used 123 for unpack file name and yes these files are from the folder ".semc-fullbackup". By the way its unpack successfully thanks :)
-
If you could give me a hint, is the file DSC_0006.JPG 123.jpg which is encrypted in adb backup format, or are the files inside the folder ".semc-fullbackup"?
-
OMG!! After posting last comment I accidently try password "1234" and its works. :) Now i can restore any file from the folder ".semc-fullbackup" Thanks you so much for this tool. AKPaharia
-
@dragomerlin Thanks for the reply. OK. i create this backup in 2015 with my sony Xpera M2 Dual (D2302) (android kitkat) via backup & restore app. But i don't have that device anymore. However i have that backup & restore apk file (com.sonyericsson.vendor.backuprestore) BUT it doesn't work in todays androids phone might be due to changing android version or it works only in sony phones. I download the tool (android-backup-tookit-20221220.zip) and after extracting run for files located in ".semc-fullbackup"...
-
@dragomerlin Thanks for the reply. OK. i create this backup in 2015 with my sony Xpera M2 Dual (D2302) (android kitkat) via backup & restore app. But i don't have that device anymore. However i have that backup & restore apk file (com.sonyericsson.vendor.backuprestore) BUT it doesn't work in todays androids phone might be due to changing android version or it works only in sony phones. I download the tool (android-backup-tookit-20221220.zip) and after extracting run for files located in ".semc-fullbackup"...
-
Sony backup & restore app which you used already should be able to restore the same ".semc-fullbackup" to your phone. Did you try this already? At which exact step are you having issues and which steps did you follow?
-
@dragomerlin @geekguy22 Hi, First of all thanks for this tool. I also have ".semc-fullbackup" in my windows PC which was created by sony backup & restore app. Now I want to unpack/restore the files but i don't know how to use this tool to restore files. and i have windows PC. Can you provide installation guide and commands guide to use this program in windows? Thanks in advance Ashish.
-
android-backup-processor released /android-backup-tookit-20221220.zip
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
android-backup-extractor updated /android-backup-tookit-20210530.zip
-
-
-
-
-
-
-
-
-
-
Brian Fenton posted a comment on discussion General Discussion
Thanks for the reply! That's a real pity. Yes, you're right, my phone was rooted. Maybe I'll check prices of second hand phones.
-
abe does not work with TWRP backups. Plus if you could make such backup your phone is rooted., so you can buy used (second hand) same phone and restore backup there.
-
Hi! thanks for this tool, I'm really hoping it can help me. My phone died unexpectedly and unfortunately the only back up I have is one I took a month ago. I've got some very important data on that backup which I would love to retrieve. I created the backup a month ago with this command: adb backup -f 20210305.bak --twrp Today, I renamed the backup to 20210305.ab and then tried your tool to unpack this as follows: java -jar abe.jar unpack 20210305.ab 20210305.tar This gave the following output: Invlaid...
-
The command is meant to be run on Linux or Windows with Cygwin, anyway the file you have is not adb backup, looks like cwm (ClockWorkmod) backup, so try commands listed on xda: [Q] unpack userdata.backup from cwm on windows
-
av_admin posted a comment on discussion General Discussion
Happy new Year
-
Hi dragomerlin, Thank you for reply I am using win 7 and I was creat this backup in Recovery mode of my phone TP Link Neffos 5Max This photo from WinHex I should use this command in CMD of my windows ? or should run into the Linux ? Thanks
-
Ok, first you must check if your .backup file is actually adb backup file. for example with this command: od --format=c --read-bytes=15 userdata_20191225_135459.backup You can open the file with any hexadecimal viewer also. It should display something like: 0000000 A N D R O I D B A C K U P \n 0000017 If it's adb backup, we will check later on more things.
-
Ok, first you must check if your .backup file is actually adb backup file. for example with this command: od --format=c --read-bytes=15 userdata_20191225_135459.backup It should display something like: 0000000 A N D R O I D B A C K U P \n 0000017 If it's adb backup, we will check later on more things.
-
Ok, first you must check if your .backup file is actually adb backup file. for example with this command: od --format=c --read-bytes=15 userdata_20191225_135459.backup It should display something like: 0000000 A N D R O I D B A C K U P \n 0000017
-
Ok, first you must check if your .backup file is actually adb backup file. for example with this command: od --format=c --read-bytes=17 userdata_20191225_135459.backup It should display something like: 0000000 A N D R O I D B A C K U P \n 5 0000020 \n 0000021
-
Hi I google it for my files " userdata_20191225_135459.backup" and I found this topics and tools I was downloaded but I couldent found how to use it Please help me Thank you.
-
Probably it is a problem with your device. Try this https://downloads.sourceforge.net/project/adbextractor/android-backup-tookit-20180521.zip?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fadbextractor%2F&ts=1563772281&use_mirror=datapacket Click on Try to download anyway.
-
Probably it is a problem with your device. Try this https://downloads.sourceforge.net/project/adbextractor/android-backup-tookit-20180521.zip?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fadbextractor%2F&ts=1563772281&use_mirror=datapacket
-
David Crawley posted a comment on discussion General Discussion
Hi, the software wont download or from any of the mirrors, is there an alternaate way to get the software please.
-
TWRP makes a raw backup of the ext4 filesystem, which has nothing to do with the real "adb backup" which is a tar filesystem. If you want to restore the TWRP backup you need to root the destination device, you can't use adb restore because Google's adb doesn't allow direct modification of the filesystem.
-
alecxs posted a comment on discussion General Discussion
screen was broken so the only option left was backup from adb: https://twrp.me/faq/openrecoveryscript.html adb backup --twrp compress data twrp produces his own backup.ab, which is just a normal data.ext4.win with a 1536 bytes header: 00000000 54 57 52 50 00 00 00 00 74 77 73 74 72 65 61 6d |TWRP....twstream| 00000010 68 65 61 64 65 72 00 00 01 00 00 00 00 00 00 00 |header..........| 00000020 03 00 00 00 00 00 00 00 3b cd 25 5d 00 00 00 00 |........;.%]....| 00000030 00 00 00 00 00 00 00 00 00 00...
-
killuaDK posted a comment on discussion General Discussion
oki Thank you Drago i sry i late
-
Hi again, looks like the backup is corrupt. You can try sending your backup to the pigz developer in case he can help you, I can't help you anymore since it's not abe problem... https://github.com/madler/pigz/issues/44
-
Hey Drago sorry for the late well the import python take alote of time and space from disk so it get terminated by signal SIGKILL (Forced quit) #pigz -dz < ../backup.zlib > ./backup.tar pigz: skipping: <stdin>: corrupted -- incomplete deflate data extract the tar with 7zx i get this list of file and folder Apps (like the old one exactly 584Mega no contact or image ) AndroidManifest.xml assets backup.tar classes.dex META-INF res resources.arsc
-
You can try again with pigz using a pipe: pigz -dz < backup.zlib > backup.tar
-
Since pigz failed try it with python to see if it throws some error: cat backup.zlib | python -c "import zlib,sys;sys.stdout.write(zlib.decompress(sys.stdin.read()))" > backup.tar
-
it's not Huawei it's samsung s7 edge and i using a mac couldn't find any contacts folder and no shared folder either just apps folder that contains some apps data ~#tail -c +25 /Volumes/no/nt/backup.ab | openssl zlib -d > /Volumes/no/nt/backup+25.tar give no error tail -c +25 backup.ab > backup.zlib >> no error just a backup.zlib pigz -d -z backup.zlib >> pigz: skipping: /Volumes/no/backup.zlib does not have compressed suffix thank you Drago
-
If it's a pure android usually contacts will be stored in com.android.providers.contacts, however since it's a Huawei you need to find which app stores the contacts. For pictures, there should be the shared folder at the same level as apps. Did openssl zlib throw any error when decompressing? Try also unpigz to decompress the file: tail -c +25 backup.ab > backup.zlib pigz -d -z backup.zlib https://unix.stackexchange.com/questions/22834/how-to-uncompress-zlib-data-in-unix/312411#312411
-
Thank time for your time Drago First command give me : root@Macbook /V/n/tab2# java -jar ../nt/android-backup-tookit/abe.jar -debug info /Volumes/no/nt/backup.ab android-backup-extractor v20180521 Strong AES encryption allowed "/Volumes/no/nt/backup.ab" size is 6520843187 bytes Magic: ANDROID BACKUP Version: 5 Compressed: 1 Algorithm: none Second Command give me a Apps folder with size of 584Mb (backup.ab is 6G ) contain com.* (different apps ) but no data (i wish i can just bakcup my contact and...
-
Ok it looks like the archive is damaged. Probably it's compressed but not encrypted. You can find out with: java -jar abe.jar -debug info backup.ab After that, try using openssl to extract the tar (you need Linux, Cygwin or macOS): tail -c +25 backup.ab | openssl zlib -d > backup.tar
-
Hey Drago adb-split-no-extraction.sh give same error : android-backup-splitter/adb-split-no-extraction.sh ../backup.ab Extracting ab archive... Exception in thread "main" java.lang.reflect.InvocationTargetException at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)...
-
Ok probably the backup is damaged. Try splitting the backup into individual apps, with "adb-split-no-extraction.sh" It will create an .ab file for each app, then try to restore individually those that you want your data back. If it doesn't work we can try something else.
-
oki Dude ^__^ the faillure happen when i do restore i did a bachkup month ago with samsung s7 edge (SM-G935F) with no password after erasing data with twrp and installed magisk (for root) i did want to restore i lanche #adb restore backup.ab >> click restore in the device >> start restore after finish nothing seem to be restored except some SMS without contact name just numbers i did try your adb extractor it show me that message : Exception in thread "main" java.lang.reflect.InvocationTargetException...
-
Dude, first of all, I need more information. 1) Do you still have the device of origin, I mean, can you make again the adb backup, or you don't have the device anymore? 2) The failure happens when performing a backup or restore?
-
Hey Drago thank you for reply i don't have that kind of app .. what i did is to execute #adb logcat >> file.txt and i did a quick search of <<e backupmanagerservice="">> and find this error : . E BackupManagerService: Unknown tar entity type: 32 E BackupManagerService: Parse error in header: Unknown entity type 32 I hexdump : 0000 00 61 70 70 73 2f 63 6f 6d 2e 72 6f 6f 6b 69 65 I hexdump : 0010 73 74 75 64 69 6f 2e 70 65 72 66 65 63 74 76 69 I hexdump : 0020 65 77 65 72 2f 72 2f 73 68 61 64 65 72...
-
Uninstall the app com.lightelements.photoeventplanner before making the backup adb uninstall -k com.lightelements.photoeventplanner
-
yea the error i posted is from je abe.jar from your android-backup-extractor-20180521-bin i didn't use the one from github
-
Use abe.jar inside "http://android-backup-tookit-20180521.zip\android-backup-tookit\android-backup-extractor\android-backup-extractor-20180521-bin\abe.jar" The version you are using is the Nelenkov version compiled directly from his github, but mine has more features.
-
Hey thank for the reply i didn't get you witch version you mean !!! i already have downloaded the << android-backup-tookit-20180521.zip >> give me i link
-
-
Download my version it is compatible with version 5
