[GUIDE] Google Backup - Waiting to backup

Search This thread

haoquan

New member
Dec 26, 2020
2
1
London
www.linkedin.com
I have got Mi 8 running lineage OS 17.1, got transport error too. This is how I resolve the problem:

  1. Make sure your phone screen is on and unlocked.
  2. You can do this either in root or non root mode.
  3. run "adb shell" to get a cli prompt, or a terminal or ssh to it if you have Termux set up.
  4. run "bmgr run" to begin the process.
  5. run "bmgr list transports" to identify your current transport. In my case, it is "com.google.android.gms/.backup.BackupTransportService"
    For example: -
    dipper:/ # bmgr list transports
    com.android.localtransport/.LocalTransport
    com.stevesoltys.seedvault.transport.ConfigurableBackupTransport
    com.google.android.gms/.backup.migrate.service.D2dTransport
    * com.google.android.gms/.backup.BackupTransportService
  6. If the transport is not "com.google.android.gms/.backup.BackupTransportService", you can set it by running "bmgr transport -c com.google.android.gms/.backup.BackupTransportService" and run "bmgr list transports" again to confirm. The selected transport is with * prefix.
  7. run "bmgr init com.google.android.gms/.backup.BackupTransportService" to re-initialise the transport.
  8. Run "bmgr backupnow --all", and good luck.
 

sheva7

New member
Feb 3, 2021
2
0
I finally got to make it work without that many manipulation, I had to install all standard apps from Google like Message and Phone that wasn't installed on my Xiaomi.
 

Soupifier

New member
Jul 20, 2021
1
0
This worked for me, had the same problem even tried with Google one, ADB and all that stuff.

Never tried to remove my lockscreen since too lazy fixing again.

Install Google dialer, Google messages and Google contacts, make them standard.

Try to backup now, turn off wifi. Works for me.

I can't believe this worked but it did. I tried Google One but it kept saying couldn't back up. Tried adding multiple google accounts but that didn't work. Removing screen lock PIN does work but only if I keep it off and it also deletes all my fingerprints which of course is very annoying to redo everytime. Couldn't be bothered to try ADB.

Strange thing is I already had all three apps installed but Google Dialer is now called Phone by Google. Before I realized this I searched for Google Dialer and it showed me Phone by Google and I saw there was an update for it even though in my Play Apps it says I have no updates. I updated it and checked the other two apps to make sure they were updated. I also went into Contacts, settings, and noticed under Edit Contacts - "Default account for new contacts" was blank. I clicked it and my gmail address was already stored as an option so I used that. Then I checked Backup settings and now the blue button is back. Did a backup, verified it on Google Drive. I restarted my phone to make sure the blue button was still available. Yep looks like it's fixed.

I didn't need to turn off wifi. Backup worked fine with it on. I don't know why this worked but it did. Maybe it was the unlisted Phone by Google update or the Contacts option. Anyways thx for the solution!
 

Zalext

Senior Member
Dec 23, 2008
119
17
Xiaomi Redmi Note 7 Pro
Hello, time to time, many users are facing problem with greyed Backup now button in Google Backup. So here's the solution.


ADB solution

What you need
  1. Device specific drivers
  2. ADB
  3. USB Debugging turned on

Procedure
  1. Connect the phone to the PC
  2. Open Command prompt - CMD
  3. Type in console
    Code:
    adb shell
    bmgr run
    bmgr backupnow --all


Thank you



It works on a RedMi Note 7 Pro | CN Version | EU Rom



Thank you!
 

blackpager

New member
Jan 5, 2020
2
0
Turned out that it was the Universal SafetyNet Fix magisk module for me. I just left it de-activated for now...
 

Zalext

Senior Member
Dec 23, 2008
119
17
Xiaomi Redmi Note 7 Pro

puterboy

Senior Member
Jun 24, 2012
60
26
With "bmgr backupnow --all" I am getting "Transport rejected package because it wasn't able to process it at the time" for almost all packages.
Also tried Google One, the backup button is enabled, but it fails every time with "failed to backup - try again later" error.

When disabling the screen lock PIN, the backup works, but re-enabling the PIN and fingerprint brings back the problem.

Any ideas? I am on Xiaomi Mi A1 with latest Lineage 17.1.
I am having the same exact problem on my (rooted) pixel 5a.
Any solutions?
 

Anduril97

New member
Hello, time to time, many users are facing problem with greyed Backup now button in Google Backup. So here's the solution.

How it looks
OkjnlVM.png


ADB solution

What you need
  1. Device specific drivers
  2. ADB
  3. USB Debugging turned on

Procedure
  1. Connect the phone to the PC
  2. Open Command prompt - CMD
  3. Type in console
    Code:
    adb shell
    bmgr run
    bmgr backupnow --all
  4. If error "Backup finished with result: Backup Cancelled" pops up, type in console
    Code:
    bmgr backupnow appdata
    and then
    Code:
    bmgr backupnow --all
  5. When it's finished reboot your phone, Backup now button should be blue and functional

Terminal Emulator solution

What you need
  1. Root
  2. Terminal Emulator

Procedure
  1. Open Terminal Emulator
  2. Type
    Code:
    su
    bmgr backupnow --all
  3. Reboot phone
Backup doesn't work after deleting data/data/com.google.android.gms

There's a new problem after deleting mentioned folder to get GPay working. Unfortunately this breaks Backup. I captured the issue, backup transport path is disabled, you need to reenable it.

Procedure is same but this time, type in console
Code:
bmgr transport com.google.android.gms/.backup.BackupTransportService

Now repeat previous steps.

If I helped, consider buying me a coffee or just hit Thanks button. I appreciate any kind of feedback.
Years later, they changed it to Google One backup and this fix still somehow worked for me, thanks!
 

saifssj6

Senior Member
Apr 5, 2013
74
3
I have got Mi 8 running lineage OS 17.1, got transport error too. This is how I resolve the problem:

  1. Make sure your phone screen is on and unlocked.
  2. You can do this either in root or non root mode.
  3. run "adb shell" to get a cli prompt, or a terminal or ssh to it if you have Termux set up.
  4. run "bmgr run" to begin the process.
  5. run "bmgr list transports" to identify your current transport. In my case, it is "com.google.android.gms/.backup.BackupTransportService"
    For example: -
    dipper:/ # bmgr list transports
    com.android.localtransport/.LocalTransport
    com.stevesoltys.seedvault.transport.ConfigurableBackupTransport
    com.google.android.gms/.backup.migrate.service.D2dTransport
    * com.google.android.gms/.backup.BackupTransportService
  6. If the transport is not "com.google.android.gms/.backup.BackupTransportService", you can set it by running "bmgr transport -c com.google.android.gms/.backup.BackupTransportService" and run "bmgr list transports" again to confirm. The selected transport is with * prefix.
  7. run "bmgr init com.google.android.gms/.backup.BackupTransportService" to re-initialise the transport.
  8. Run "bmgr backupnow --all", and good luck.
Hi I hope someone can help me with this, on step 7, I am getting "Initialization result: -1000", can someone help me how to proceed from here?
 

greenyellow

New member
Jan 27, 2022
1
1
Same problem with a Moto G6 (android 9). The problem was in the SDcard system file. It was preventing GServices to backup. 1-Removed SDcard safely; 2-Cleaned Gdrive, Gplaystore, Gplayservices and GOne data. 3-Restarted Android. Then backup was possible using GOne. The backup button was still gray in the Configuration menu, but it was possible to backup using GOne. Removing the security settings (PIN and fingerprints) also made the Backup button in the Config section active (blue). After that, tried the initial commands using ADB and they finally worked.
 
Last edited:
  • Like
Reactions: kaem84

jonny68

Senior Member
Mar 27, 2010
5,747
601
Dublin
I'm having the same issue with the Xiaomi 12 Pro , don't particularly want to try the ADB method and i tried the rest and not working, any other ideas?
 

jows

Member
Aug 24, 2022
9
3
I'm having the same issue with the Xiaomi 12 Pro , don't particularly want to try the ADB method and i tried the rest and not working, any other ideas?
This worked on my Xiaomi 11T Pro. Credit goes to a previous message somewhere in this post 💙

Try setting your Screen Lock (under Settings --> Security) to "None".

Go back to Settings --> Google --> Backup

After backing up, you can go back and re-institute your security setting.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 106
    Hello, time to time, many users are facing problem with greyed Backup now button in Google Backup. So here's the solution.

    How it looks
    OkjnlVM.png


    ADB solution

    What you need
    1. Device specific drivers
    2. ADB
    3. USB Debugging turned on

    Procedure
    1. Connect the phone to the PC
    2. Open Command prompt - CMD
    3. Type in console
      Code:
      adb shell
      bmgr run
      bmgr backupnow --all
    4. If error "Backup finished with result: Backup Cancelled" pops up, type in console
      Code:
      bmgr backupnow appdata
      and then
      Code:
      bmgr backupnow --all
    5. When it's finished reboot your phone, Backup now button should be blue and functional

    Terminal Emulator solution

    What you need
    1. Root
    2. Terminal Emulator

    Procedure
    1. Open Terminal Emulator
    2. Type
      Code:
      su
      bmgr backupnow --all
    3. Reboot phone
    Backup doesn't work after deleting data/data/com.google.android.gms

    There's a new problem after deleting mentioned folder to get GPay working. Unfortunately this breaks Backup. I captured the issue, backup transport path is disabled, you need to reenable it.

    Procedure is same but this time, type in console
    Code:
    bmgr transport com.google.android.gms/.backup.BackupTransportService

    Now repeat previous steps.

    If I helped, consider buying me a coffee or just hit Thanks button. I appreciate any kind of feedback.
    8
    For this backup bug, I found a easier solution by adding a second email....just add another account to save that backup and the Backup Now is live again...than you can remove the second email once the primary email backup is working now....

    Enviado do meu POCOPHONE F1 através do Tapatalk
    6
    Try setting your Screen Lock (under Settings --> Security & Location) to "None".

    Go back to Google --> Backup, and see if the blue button isn't lit up for you.

    After backing up, you can go back and re-institute your security setting.
    3
    @Dexer125 Thank you very much for this helpful thread!
    Both the "remove PIN" and "adb/terminal" approach work for me, in general. However, there are two strange or interesting observations that I made in this context.

    First: After removing the PIN and hitting "back up now" the backup runs fine. Afterwards, I set up the PIN again and the backup status in settings returned to "Waiting to back up..." as if there was never any backup. I checked in Google Drive and the backup was there with the correct time stamp. For some reason I went back to Google Drive one or two hours later and now Google Drive was no longer showing the time of the last backup, but also "Waiting to back up...". It looks like the backup had been automatically deleted. Using the adb-approach the backup menu in settings does still show "Waiting to back up..." afterwards, but at least this way the backup does not get auto-deleted in Google Drive.

    Second: After an adb-triggered backup I factory reset my device due to changing ROM. During the initial setup process this backup was not recognized. The setup wizard was claiming there is no backup in the cloud, although it was visible in Google Drive. That was actually pretty annoying.

    Do you have any thoughts on this?
    The presence of a backup in Drive is not sufficient for having a usable backup. I've found that it can take days after doing a full backup for it to become a usable one.

    How to tell if the backup is usable? Run this command:
    Code:
     adb shell bmgr list sets
    The command lists the tokens of all usable backups. If it reports "no restore sets" then it's not usable.

    You can find the token of the current backup by running:
    Code:
    adb shell dumpsys backup
    and looking for the line containing "Current:"
    When it's usable the token is listed by the "list sets" command above.

    Sent from my OnePlus 3T using XDA Labs
    2
    Hi guys. I try this method but on my Mi9 not working.
    ADB command says transport error.
    Disabling pin code and FP do the Google backup now blue but after one minute it says try later and nothing happens.