Conversation

holy fucking shit, android (aosp) actually has useful working backups that don't require you to upload everything to google servers and which you can manually trigger and have it work they're just incredibly well hidden h/t

@DanielMicay

for giving me the right direction

181

Catherine

@whitequark

Sep 12, 2020

to prepare: $ bmgr transport com.android.localtransport/.LocalTransport $ bmgr enable true to backup: $ bmgr backupnow --all host$ adb root; adb pull /data/data/com.android.localtransport/files/1

Catherine

@whitequark

Sep 12, 2020

to restore: host$ adb root; adb push 1 /data/data/com.android.localtransport/files/ $ bmgr restore 1 [package...]

Catherine

@whitequark

Sep 12, 2020

note: this is mostly useful as a replacement for `adb backup`/`adb restore` that doesn't require blood sacrifices to restore half of your data instead of none of your data it doesn't work remotely and AFAIU requires a userdebug build

Daniel Micay

@DanielMicay

Replying to

@whitequark

I don't think it requires a userdebug build, since it's part of the functionality required by the CTS and the CTS only fully passes with a user build.

12:04 PM · Sep 12, 2020Twitter Web App

Replying to

oh. uh, how does CTS pull out the data?

Replying to

CTS largely operates via adb. There's a whole lot of functionality available in `adb shell` that's largely to support the CTS. So, CTS has access as `adb shell` and as the many apps it installs, including device managers, accessibility services, etc. that it authorizes.

Show replies

Replying to

and

As far as I know, it exists so that the CTS can test the backup service implementation, so every Android device is required to have a working implementation of it that's certified to work as part of their CTS certification.