Obsolete
Status Update
No update yet.
Comments
pa...@gmail.com
I just found out that my device's ADB version is 1.0.31.
So 1.0.32+ broke backwards compatibility.
So 1.0.32+ broke backwards compatibility.
th...@gmail.com
Saw the same problem happen with version 1.0.36 on MacOSX
Can't backup anything, neither a single app nor using options.
Apparently some people have had success escaping or quoting the parameters, but that does not seems to work here
Can't backup anything, neither a single app nor using options.
Apparently some people have had success escaping or quoting the parameters, but that does not seems to work here
ha...@gmail.com
I can confirm that this is a problem on Mac OS El Capitan 10.11.6 with ADB Version 1.0.36.
I tried command "adb backup -apk-all -f <filename>" and it said "Now unlock your device and confirm the backup operation..." and nothing happened. My Nexus 6P did not prompt me for password. Note - Password for desktop backup is set in Developer Options
I tried command "adb backup -apk-all -f <filename>" and it said "Now unlock your device and confirm the backup operation..." and nothing happened. My Nexus 6P did not prompt me for password. Note - Password for desktop backup is set in Developer Options
ah...@gmail.com
the same problem happen with ver 1.0.32 up to 1.0.36 on Linux
do...@gmail.com
Same for 1.0.32 on Windows.
fl...@gmail.com
Hi,
I had the same issue not being able to backup a single app with my phone updated from Android 5 to Android 6 (both CM based). Then I found out this:
- adb 1.0.31 silently fails with Android 6 (at least on Linux). adb 1.0.36 seems compatible with android 6. I have no Android 7, but you see the idea of testing recent adb versions.
- adb syntax has changed and nobody documented it so far... Well, not the syntax of the 'adb backup' command by itself, but what Android expects from adb has changed. What worked for me (and I checked my phone's logs to get this) is:
adb backup -f <path to your backup file> ['<flag>']* <name of the package>
So, for example: adb backup -f test.ab '-apk' '-nosystem' 'air.Anodyne.humble.ab'
Notice the mandatory single quotes _on each flag_.
Good luck.
I had the same issue not being able to backup a single app with my phone updated from Android 5 to Android 6 (both CM based). Then I found out this:
- adb 1.0.31 silently fails with Android 6 (at least on Linux). adb 1.0.36 seems compatible with android 6. I have no Android 7, but you see the idea of testing recent adb versions.
- adb syntax has changed and nobody documented it so far... Well, not the syntax of the 'adb backup' command by itself, but what Android expects from adb has changed. What worked for me (and I checked my phone's logs to get this) is:
adb backup -f <path to your backup file> ['<flag>']* <name of the package>
So, for example: adb backup -f test.ab '-apk' '-nosystem' 'air.Anodyne.humble.ab'
Notice the mandatory single quotes _on each flag_.
Good luck.
pa...@gmail.com
I, too, have this problem. Windows 10, Nougat on a LG K20 VS501 Rev 1.0.
Cannot backup anything!
Cannot backup anything!
al...@google.com
Thank you for reporting this, we've decided to deprecate adb backup and restore, but I hope this won't discourage you from reporting other issues in the future.
ma...@gmail.com
But... How will I backup and restore my applications in the future? This was an incredibly useful tool!
za...@gmail.com
hi my friends
Description
Kevinoid's answer is seems to highlight the problem (
Device: Galaxy S4 @ 4.4.2
Platform Tools: 24 rc2
adb version
Android Debug Bridge version 1.0.35
adb backup
Now unlock your device and confirm the backup operation...
Unlocked device and tapped button, here's the log:
04-27 14:12:32.240 819-1586/? V/BackupManagerService: Requesting full backup: apks=false obb=false shared=false all=false pkgs=[Ljava.lang.String;@42bee810
04-27 14:12:32.240 819-1586/? I/BackupManagerService: Beginning full backup...
04-27 14:12:32.240 819-1586/? D/BackupManagerService: Starting backup confirmation UI, token=1139628272
04-27 14:12:32.240 819-1586/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1362 com.android.server.BackupManagerService.startConfirmationUi:5708 com.android.server.BackupManagerService.fullBackup:5600 android.app.backup.IBackupManager$Stub.onTransact:190 android.os.Binder.execTransact:404
04-27 14:12:32.240 819-1586/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startActivity:1374 android.app.ContextImpl.startActivity:1363 com.android.server.BackupManagerService.startConfirmationUi:5708 com.android.server.BackupManagerService.fullBackup:5600 android.app.backup.IBackupManager$Stub.onTransact:190
04-27 14:12:32.330 819-1586/? D/BackupManagerService: Waiting for full backup completion...
04-27 14:12:34.232 819-1527/? D/BackupManagerService: acknowledgeFullBackupOrRestore : token=1139628272 allow=true
04-27 14:12:34.232 819-1527/? D/BackupManagerService: Sending conf message with verb 2
04-27 14:12:34.242 819-24384/? I/BackupManagerService: --- Performing full-dataset backup ---
04-27 14:12:34.242 819-24384/? I/BackupManagerService: Initiating bind of OBB service on com.android.server.BackupManagerService$FullBackupObbConnection@453e1d40
04-27 14:12:34.272 819-24384/? W/ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1894 com.android.server.BackupManagerService$FullBackupObbConnection.establish:2602 com.android.server.BackupManagerService$PerformFullBackupTask.run:2805 java.lang.Thread.run:841 <bottom of call stack>
04-27 14:12:34.282 819-819/? I/BackupManagerService: OBB service connection com.android.internal.backup.IObbBackupService$Stub$Proxy@45256d50 connected on com.android.server.BackupManagerService$FullBackupObbConnection@453e1d40
04-27 14:12:34.282 819-24384/? W/BackupManagerService: Unknown package '
04-27 14:12:34.312 819-1586/? D/BackupManagerService: Full backup processing complete.
04-27 14:12:34.332 819-24384/? D/BackupManagerService: Full backup pass complete.
Notice the
Unknown package '
and this is just the simplest possible way of calling.
adb backup -apk
Unknown package '-apk' 'net.twisterrob.inventory.debug', skipping
Please do something about this in the N update, it's been a year since that commit possibly causing this issue.