• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Google One backup fails after rooting

Search This thread

puterboy

Member
Jun 24, 2012
41
21
I rooted my Pixel 5a using Magisk and it no longer successfully backs up to Google cloud/Google One.
To be specific:, when I run "Back up Now" from Settings, it runs for a bit and then returns "Pixel 5a: No data backed up" (or if I run backup from the Google One app itself "Pixel 5a: some data not backed up")

Under backup details it says:
  • Apps No data backed up
  • Photos & videos: Synced with Google Photos
  • SMS & MMS messages: No data backed up (though it does seem to backup messages if I run backup from Google One app itself)
  • Call history: No data backed up
  • Device settings: No data backed up
  • Google account data: Synced with Contacts, Calendar, and more
So it seems like the phone is still syncing photos/video and my account data as normal but nothing is being backed up unique to the device.

Note that:
  • Backup worked properly before rooting and everything else works fine after rooting
  • I am short but not out of storage on Google cloud (>1GB left)
  • Under Magisk, I pass the full SafetyNet

I tried clearing backups and re-installing Google One -- all to no avail.

Any thoughts on how to fix or troubleshoot?
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,680
5,230
Vancouver
Google Pixel 2 XL
Google Pixel 5
Dude! Sorry, I meant to reply yesterday when I got home after I saw this post on the train after work. You can fix this. You can force a backup with adb. After you force the backup it should do it automatically after.

In adb enter:
adb shell
bmgr run
bmgr backupnow --all


Sometimes you'll get an error/fail. If this happens enter:
bmgr backupnow appdata

It won't actually backup anything and is over in one or two seconds. When it's done, enter again:
bmgr backupnow --all

And all of your stuff should start backing up. Like I said earlier, once you do this auto backups should start working again.

Good luck!
 
  • Like
Reactions: galaxys

puterboy

Member
Jun 24, 2012
41
21
I tried the above and it returned 'Success', however I still have the same problem.

Specifically,
  1. The Backup detail screen under settings is unchanged
    • Apps No data backed up
    • Photos & videos: Synced with Google Photos
    • SMS & MMS messages: No data backed up (though it does seem to backup messages if I run backup from Google One app itself)
    • Call history: No data backed up
    • Device settings: No data backed up
    • Google account data: Synced with Contacts, Calendar, and more
  2. Google drive backups still shows that only MMS was backed up
    So that whatever was backed up manually via 'adb' doesn't seem to be showing up in Google drive as a backup

Not sure this is relevant, but when running 'bmgr backuppnow --all', I got a lot of messages of form:
Package xxx.xxx.xxx. with result: Transport rejected package because it wasn't able to process it at the time
Indeed this occurred for almost all the packages

(By comparison, I tried the same 'bmgr' commands on my old Samsung S8+ and I got very few packages with transport errors and lots of 'successes'. The backup also took much longer and the progress seemed to indicate significant amounts of data being backed up...)

But bottom line is that I can't seemingly manually or automatically backup the phone
 
Last edited:

puterboy

Member
Jun 24, 2012
41
21
The logcat shows the following errors corresponding to the transport, for example:

09-22 21:22:20.539 1557 11541 I PFTBT : Initiating full-data transport backup of com.android.theme.icon_pack.rounded.themepicker token: 2040284044
09-22 21:22:20.554 1557 11541 I PFTBT : Transport rejected backup of com.android.theme.icon_pack.rounded.themepicker, skipping
09-22 21:22:20.554 1557 11541 I PFTBT : Unbinding agent in com.android.theme.icon_pack.rounded.themepicker
09-22 21:22:20.554 1557 11541 W ActivityManager: Unbinding backup agent with no active backup
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,680
5,230
Vancouver
Google Pixel 2 XL
Google Pixel 5
The logcat shows the following errors corresponding to the transport, for example:

09-22 21:22:20.539 1557 11541 I PFTBT : Initiating full-data transport backup of com.android.theme.icon_pack.rounded.themepicker token: 2040284044
09-22 21:22:20.554 1557 11541 I PFTBT : Transport rejected backup of com.android.theme.icon_pack.rounded.themepicker, skipping
09-22 21:22:20.554 1557 11541 I PFTBT : Unbinding agent in com.android.theme.icon_pack.rounded.themepicker
09-22 21:22:20.554 1557 11541 W ActivityManager: Unbinding backup agent with no active backup
That doesn't matter. There's several things that have that output, but it makes no difference. What gets backed up successfully is everything that an automatic backup would do. The only difference is now you're seeing the output, but when is was auto before you didn't.

Don't worry, the commands I suggested you use will backup everything that a regular G backup would do.

It's often more comprehensive.
When I'm flashing something that could possibly go wrong (including system updates ~ sometimes something happens and I have to wipe afterwards) I KNOW that using that command will backup everything that it can. Some days sms won't backup on automatic backup, sometimes call logs..,.etc
 
Last edited:

puterboy

Member
Jun 24, 2012
41
21
OK I *partially* solved the problem.
The clue for me was the logging line (found elsewhere in the log):
not performing kv backup "Encryption key has not synced"

Then in the following xda post (https://forum.xda-developers.com/t/guide-google-backup-waiting-to-backup.3895101/post-81931589), I saw the following:

""Starting in Android Pie, devices can take advantage of a new capability where backed-up application data can only be decrypted by a key that is randomly generated at the client. This decryption key is encrypted using the user's lockscreen PIN/pattern/passcode, which isn’t known by Google. Then, this passcode-protected key material is encrypted to a Titan security chip on our datacenter floor. The Titan chip is configured to only release the backup decryption key when presented with a correct claim derived from the user's passcode."

And elsewhere in the thread, people suggested turning off password encryption...

So I removed the login/lock screen password and backups proceeded successfully (both from 'adb/bmgr' and after reboot from 'Settings->Backup' on the phone itself)

UNFORTUNATELY, restoring the login/lock screen password caused the backups to fail again with the same errors as before...

So it appears the problem seems to be with the encryption key not being synced when I have a security password enabled.
 

puterboy

Member
Jun 24, 2012
41
21
Even more annoying, turning login/lock screen password back on seems to delete the previous backup done without protection, leaving me with no Google cloud backup at all.
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,680
5,230
Vancouver
Google Pixel 2 XL
Google Pixel 5
Even more annoying, turning login/lock screen password back on seems to delete the previous backup done without protection, leaving me with no Google cloud backup at all.
Did you check in Google Drive > backups? It should be still listed there. Changing someone on your phone shouldn't affect what stored on the cloud. If you wipe, during setup you should still get the option to restore your latest backup
 

puterboy

Member
Jun 24, 2012
41
21
Did you check in Google Drive > backups? It should be still listed there. Changing someone on your phone shouldn't affect what stored on the cloud. If you wipe, during setup you should still get the option to restore your latest backup
After adding back security, it does seem to get completely wiped from Google Drive. Indeed, under backup, it says "Your Device is not backed up" -- though backups from my other devices are there untouched.

So adding back security seems to reset/wipe any old backup created without security...
 

puterboy

Member
Jun 24, 2012
41
21
Not sure this is helpful, but found this in the 'logcat' when doing a "Backup Now" operation from the phone:

09-23 21:20:59.303 3191 14292 E Backup : [BackUpNowOperation] Waiting for key to sync timed out​
09-23 21:20:59.303 3191 14292 E Backup : java.util.concurrent.TimeoutException: Waited 45000 milliseconds (plus 156618 nanoseconds delay) for [email protected][status=PENDING]​
09-23 21:20:59.303 3191 14292 E Backup : at ccrq.get:)[email protected]@21.33.14 (150400-395723304):38)​
09-23 21:20:59.303 3191 14292 E Backup : at qhc.d:)[email protected]@21.33.14 (150400-395723304):1)​
09-23 21:20:59.303 3191 14292 E Backup : at qhc.f:)[email protected]@21.33.14 (150400-395723304):6)​
09-23 21:20:59.303 3191 14292 E Backup : at adhi.run:)[email protected]@21.33.14 (150400-395723304):17)​
09-23 21:20:59.303 3191 14292 E Backup : at bxdu.run:)[email protected]@21.33.14 (150400-395723304):2)​
09-23 21:20:59.303 3191 14292 E Backup : at uwo.c:)[email protected]@21.33.14 (150400-395723304):6)​
09-23 21:20:59.303 3191 14292 E Backup : at uwo.run:)[email protected]@21.33.14 (150400-395723304):7)​
09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)​
09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)​
09-23 21:20:59.303 3191 14292 E Backup : at vcm.run:)[email protected]@21.33.14 (150400-395723304):0)​
09-23 21:20:59.303 3191 14292 E Backup : at java.lang.Thread.run(Thread.java:923)​
09-23 21:20:59.325 3191 14292 I Backup : [BackUpNowOperation] Backup done for all packages, result code: 29011​
Again, suggesting that there is some issue with syncing the encryption key corresponding to the security passcode.
 

xunholyx

Recognized Contributor
Dec 3, 2012
7,680
5,230
Vancouver
Google Pixel 2 XL
Google Pixel 5
Not sure this is helpful, but found this in the 'logcat' when doing a "Backup Now" operation from the phone:

09-23 21:20:59.303 3191 14292 E Backup : [BackUpNowOperation] Waiting for key to sync timed out

09-23 21:20:59.303 3191 14292 E Backup : java.util.concurrent.TimeoutException: Waited 45000 milliseconds (plus 156618 nanoseconds delay) for [email protected][status=PENDING]​
09-23 21:20:59.303 3191 14292 E Backup : at ccrq.get:)[email protected]@21.33.14 (150400-395723304):38)​
09-23 21:20:59.303 3191 14292 E Backup : at qhc.d:)[email protected]@21.33.14 (150400-395723304):1)​
09-23 21:20:59.303 3191 14292 E Backup : at qhc.f:)[email protected]@21.33.14 (150400-395723304):6)​
09-23 21:20:59.303 3191 14292 E Backup : at adhi.run:)[email protected]@21.33.14 (150400-395723304):17)​
09-23 21:20:59.303 3191 14292 E Backup : at bxdu.run:)[email protected]@21.33.14 (150400-395723304):2)​
09-23 21:20:59.303 3191 14292 E Backup : at uwo.c:)[email protected]@21.33.14 (150400-395723304):6)​
09-23 21:20:59.303 3191 14292 E Backup : at uwo.run:)[email protected]@21.33.14 (150400-395723304):7)​
09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)​
09-23 21:20:59.303 3191 14292 E Backup : at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)​
09-23 21:20:59.303 3191 14292 E Backup : at vcm.run:)[email protected]@21.33.14 (150400-395723304):0)​
09-23 21:20:59.303 3191 14292 E Backup : at java.lang.Thread.run(Thread.java:923)​
09-23 21:20:59.325 3191 14292 I Backup : [BackUpNowOperation] Backup done for all packages, result code: 29011​
Again, suggesting that there is some issue with syncing the encryption key corresponding to the security passcode.
I'm really not sure. I use this to force backups even when I have a recent one on my Pixel 5 and 2xl. I've had to use it in the past on both when backups didn't start automatically. I actually used this for beta 12/5 when I was visiting my dad for his birthday.
(I had problems with getting fastboot to work on his PC and ended having to wipe when I got home a couple of days later to re-root)
 

puterboy

Member
Jun 24, 2012
41
21
I ended up just 'factory resetting' my phone and starting from scratch -- first rooting, then restoring apps, then adjusting settings, then using the Magisk SafetyNet-fix.... each step-by-step, testing backup after each change...

And to my relief, it works and continued to work at each step...

Somehow, something must have gotten "wacked" in my previous setup and was not able to be reset (despite clearing caches and data stores on Google Play Services, Google Play Store, Google One, Google Pay, etc). But a full factory reset did solve it.

Unfortunately, while Swiftbackup restored my apps and most of their settings, I had to manually redo all the Android settings since there was (obvoiusly) no Android backup that I could use to restore them... this took hours...

But in any case, it works and perhaps this thread will be useful to others should they encounter this problem...
 
  • Like
Reactions: xunholyx

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Dude! Sorry, I meant to reply yesterday when I got home after I saw this post on the train after work. You can fix this. You can force a backup with adb. After you force the backup it should do it automatically after.

    In adb enter:
    adb shell
    bmgr run
    bmgr backupnow --all


    Sometimes you'll get an error/fail. If this happens enter:
    bmgr backupnow appdata

    It won't actually backup anything and is over in one or two seconds. When it's done, enter again:
    bmgr backupnow --all

    And all of your stuff should start backing up. Like I said earlier, once you do this auto backups should start working again.

    Good luck!
    1
    I ended up just 'factory resetting' my phone and starting from scratch -- first rooting, then restoring apps, then adjusting settings, then using the Magisk SafetyNet-fix.... each step-by-step, testing backup after each change...

    And to my relief, it works and continued to work at each step...

    Somehow, something must have gotten "wacked" in my previous setup and was not able to be reset (despite clearing caches and data stores on Google Play Services, Google Play Store, Google One, Google Pay, etc). But a full factory reset did solve it.

    Unfortunately, while Swiftbackup restored my apps and most of their settings, I had to manually redo all the Android settings since there was (obvoiusly) no Android backup that I could use to restore them... this took hours...

    But in any case, it works and perhaps this thread will be useful to others should they encounter this problem...