I am unable to create a full phone backup file of my Realme 2 Pro (model RMX1801) through the ADB. The phone runs stock ColorOS 7 (Android 10). The device is not rooted and I do not want to root it. Doing that would delete my data. Also, my device hasn't had any screen-lock protection days before I ran the very first command (which is several hours amounting to few days before the original-revision of this post) and remaining wholly unchanged to the best of my knowledge till the timestamp of latest-revision.
Here's what I've tried. I launched Command prompt (cmd.exe) and ran:
C:\Users\Dell> OneDrive\Desktop\adb.exe
C:\Users\Dell> adb devices
List of devices attached
86b3470 device
At this point I started to take backup. I have tried a couple of things and I'm categorizing them now.
Attempts when I entered no backup-encryption key whatsoever
C:\Users\Dell>adb backup -all -f -nosystem C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup -all -f -nosystem -shared C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
Both of the commands showed on the UI that backup was taking place. But none of them created the backup file in my PC.
Attempts when I entered a backup-encryption key
C:\Users\Dell>adb backup -all -f -nosystem C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup -all -f -nosystem -shared C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
No change, whatsoever.
I also changed the destination path from OneDrive/Documents to OneDrive/Desktop and repeated all the above commands. That did not work either.
Attempts with double-quotes
C:\Users\Dell>adb backup "-f -all -nosystem C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab"
C:\Users\Dell>adb backup "-f -all -nosystem -shared C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab"
Did not work.
Changed double quotes position
C:\Users\Dell>adb backup "-f -all -nosystem" C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup "-f -all -shared -nosystem" C:\Users\Dell\OneDrive\Documents\RMX1801backup.ab
C:\Users\Dell>adb backup -f "-all -nosystem -shared" C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab
C:\Users\Dell>adb backup -f "-all -nosystem -shared" C:\Users\Dell\OneDrive\Desktop\RMX1801backup.ab
Here's what happened in the case of double-quoted commands: All of the ones ending the double-quotes before the backup file's path appeared to have started the backup process but it did not create the backup file either. The duration of the backup process in the UI was also incredibly shorter, aka literally instantaneous, in these attempts.
As asked in the comments, the versions of adb are produced below:
C:\Users\Dell>adb version
Android Debug Bridge version 1.0.41
Version 33.0.3-8952118
Installed as C:\Users\Dell\OneDrive\Desktop\platform-tools\adb.exe
C:\Users\Dell>adb shell adbd --version
* daemon not running; starting now at tcp:5037
* daemon started successfully
/system/bin/sh: adbd: inaccessible or not found
C:\Users\Dell>adb devices
List of devices attached
86b3470 device
C:\Users\Dell>adb shell
RMX1801:/ $ adbd --version
/system/bin/sh: adbd: inaccessible or not found
127|RMX1801:/ $
here are the [hitherto] unsolicited screencaps/screengrabs/screenshots:
adb backup
command your phone display has to be on and the phone has to be unlocked, otherwise you won't recognize the screen that is shown where you have to enter the backup password. Anyway for checking if backup works correctly useadb shell
and then execute the backup commands locally on the phone using thebu
command instead ofadb backup
. This way you will get all [error] messagesbu
outputs. See also android.stackexchange.com/q/231235/2241adb shell
part) in the original-post/"question". It has been added belatedly since I felt it was too concise enough, that it may end-up prolly giving wrong idea of my experience; especially for the target-audiences.adb shell
sub didn't return with an error — in fact, it didn't even execute the "Full Backup" [G]UI on my phone, no matter variables.adb logcat
in a second cmd window. I once had a device where the manufacturer pushed a ROM with a defectbu
version thusadb backup
wasn't functional at all. I could see it onadb logcat
where the stack trace of the error always appeared after executing anadb backup
command.