summaryrefslogtreecommitdiffstats
path: root/adbbu (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Fix compatibility across the boardEthan Yonker2016-08-261-6/+3
| | | | Change-Id: I6376920775ddabb4d4af505fffd86e404403a64a
* Update to 7.0Ethan Yonker2016-08-241-1/+1
| | | | Change-Id: I621cc47352f7ac552d9602485825ae3a6f9ae516
* adbbu: fix include path, now builds again in Omni 4.4that2016-08-051-2/+2
| | | | Change-Id: Idee80db34a0685abb4bec50383dcbc4911c1a341
* ADB: Add adb backup for TWRP.bigbiff2016-08-016-0/+1258
Functionality for client side to backup tar and image streams over adbd to the client under backup.ab. Using adb backup on the client side you can backup the partitions TWRP knows about. On the client side you can do the following: adb backup -f <filename> --twrp <options> where options are --compress: compress data system: backup system cache: backup cache data: backup data boot: backup boot etc for each partition. You can string multiple options, i.e. adb backup -f <filename> --twrp --compress cache system data adb backup in TWRP will take any option corresponding to TWRP fstab partitions, e.g. efs boot as well. If you do not specify the filename with the -f option, adb will backup your data to a filename backup.ab on the client. You can then rename the file and encrypt it with desktop tools. If you don't want to use command line arguments: adb backup --twrp will bring up the gui and allow you to choose partitions from the backup page. To restore the backup use the following convention: adb restore <filename> Structures are used to store metadata in binary inside of the file itself. If the metadata structure is modified, update the adb version so that it will invalidate older backups and not cause issues on restore. When restoring, we currently do not support picking specific partitions. It's all or nothing. Change-Id: Idb92c37fc9801dc8d89ed2a4570e9d12e76facf8