Hello
I own a Samsung Note 4 SM-910A. It is unlocked, (but unfortunately bootlocked because of ATT policy), unrooted and used internationally by me both at home and internationally using a variety of SIMs.
I backed up my device using adb and successfully created a backup file xxx.ab of about 3.2GB
I then updated the android baseband to ..DOI4 from ..DOI3 (the goal is to get to MM).
I wanted to make sure the backup would restore before going all the way up the update list. So i tried to restore my data.
I now find that adb will not restore my data. The only clues I have... The message in the DOS command window on my PC: “Now unlock your device and confirm the restore operation”
And a message on the phone stating that the restore has started then finished after a few seconds.
“Restore starting... Restore ending...”
Questions:
1. Is there a log file that I can read that might give me a clue as to why adb has failed? If the answer is logcat – how do I find actual failure messages in this vast logfile?
2. Are backups from different basebands, but on the same phone compatible?
Any help appreciated.
Related
G'day/Good Morning/Hello/Hi,
I own a Sony Ericsson Xperia Pro (MK16i) and I am running CyanogenMod9 (20130721), rooted and bootloader unlocked. I have been trying to back up the apps and app data so that I can transfer them to my new phone (Motorola Moto G with Android 4.4.2, unrooted and bootloader locked), but whatever I try doesn't work.
With adb backup, it prompts me to confirm the backup operation on my phone, but nothing appears and I end up with a 0 byte backup file. Tried it on a few computers. Works with my new phone.
With Carbon/Helium, it complains that I have a desktop backup password, but I've never set one, and I can't seem to set one. No matter what I type, I get "failure setting backup password".
With google's servers, I can't find a place to check that it is backed up, nor figure out how to restore to my new phone. It may be backed up, but I can't find out where. In google's dashboard, I only see three apps' data backed up, and they're all system apps (wallpaper, settings, market).
With CWM-based recovery, it took a while and seemed to backup to my SD card, but I can't find where it put anything.
I would prefer to use Carbon/Helium, so if someone could tell me what file or db I can access to clear/reset the desktop backup password, that will hopefully push me in the right direction.
Hope you'll help me.
Thank You
http://forum.xda-developers.com/showpost.php?p=38583034&postcount=3 looks like i should just give up now
I used to use TitaniumBackup to transfer apps and data from one Android phone to another when both devices are rooted. Recently I got a phone which currently does not have root access, so TitaniumBackup would not be useful. Most apps are not an issue, but I have trouble transferring a few apps and their data.
I was thinking to use adb to backup each app+data separately on the old phone (and then to restore it in the new phone), and tried the following command on the old (and rooted) phone:
adb backup -f <appname>.ab -apk <app_package_name>
but I got the following message:
Now unlock your device and confirm the backup operation.
The strange thing is that there is nothing there for me to accept when I unlock the phone or when I keep the phone unlocked.
Also when backing up all apps via "adb backup -apk -shared -all -f all.ab", I still get the same message: Now unlock your device and confirm the backup operation. And this happens on two computers I have tried so far. Very weird.
I just tried another phone, and had no problem with the adb backup command (I did see the confirmation request on the phone). So the problem seems to be with this particular phone (LG G2 with root).
Any suggestions as to how to handle the transfer? Any better alternatives to transfer a few apps+data from one phone to another?
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.
IMy phone is connected to a Amazfit Verge smartwatch.
When I have an incoming call the ringtone is interrupted, when I power down the smartwatch the ringtone rings without interruption..
To see what's going on I want to reset my phone and just connect to the smartwatch to see if it works then.
If the reset does not work I want to go back to my previous setup asap.
I've rooted my previous phones and I was using twrp at that time, then it was easy to do a full system nandroid backup.
But I do not want to root or unlock my S9+ since this is irreversible.
I've been looking for a way to achieve this backup.
I can find a lot of programs but they all do need root or at least unlock.
It seems even adb backup ( but it will be deprecated) needs unlock.
I tried it and it says to unlock, even without that it takes a backup but it is only 160 kb in size.
If I need to unlock it will trip knock on the phone and wipe the device, that's just what I want to prevent
And I do not even know if adb takes a full system backup.
I found one method that seems interesting
Boot into twrp or cwm from a bootable SD card
But it says it is only applicable to a B&N Nook Color, is there another way to get this working on a S9+ or is there another way to achieve my goal?
Try Samsung Smart Switch.
Ok, but Samsung Smart Switch is only for a data backup. I need a full backup so I can restore my phone from that backup and all is done at once.
BUMP
if anyone can help
I want to move my app data(app logins from old phone(rooted) to new samsung phone(stock) without modifying it.
I have used ADB to backup data and apps on all of my devices for a couple of years. It is very reliable and the backups for individual app can be restored across devices without issue. It is preferable to using Titanium Backup, especially since that program is no longer reliable since the inception of A12. It is especially handy when the device is not rooted. But until recently, it always worked whether the device is rooted or unrooted. Today, while preparing to install the latest A12 update on my T870, I attempted do a backup of my favorite game, it would go through the motions and create the backup file. However, I knew immediately that the file was not correct because it was only 1K in size. The same game on my phone creates a 500 Mb file. My tablet was rooted using the Magisk/boot.img method but that hasn't made a difference in the past on any device. I wasn't overly concerned because I tested restoring the phone version of the backup to my tablet and it worked just fine. I went ahead and did a clean install of the latest A12 update, debloated my tablet and restored my backups via. ADB. everything is copacetic. The only difference is I did not root my tablet this time. I suspect if I do I will have the same issue. Not a big deal since rooting holds much less importance for me than it once did.
Command used to backup - adb backup -apk com.crossword.bible.cookies.find.english -f com.crossword.bible.cookies.find.english.adb
Restore command - adb restore com.crossword.bible.cookies.find.english.adb
Same commands used in both the successful and unsuccessful backups.
Thoughts anybody?