Hi all, got a lot to do phone-wise and would appreciate tips on the best way to go.
Currently I have an unrooted locked bootloader kitkat N5. It has a ton of problems (GPS bad, camera bad, wifi doesn't turn on, wifi doesn't save passwords properly, etc) and I'm RMA-ing it when I get back to the 'states in about 2 weeks. Given that I'll need to backup my app info for the RMA, I've been researching adb backup & got it working.
1. On locked phones, adb backup doesn't backup google authenticator, nor... what else? Better to know ahead of time.
Given that I can't get on wifi currently, and that I'll have to migrate to L anyway, I figure I might as well do the following procedure:
A. Unlink google authenticators (& save any other unbackupable things from Q1)
B. Empty all SD card files (quicker backups)
C. Backup again in a few formats to be safe, (consider doing specific packages), 'best' code: "adb backup -f backupDATE.ab -apk -noshared -all -system"
D. Unlock bootloader
E. Root
F. Allow standard startup to run (back to fresh kitkat)
G. adb Restore from backups = back to 'normal' on kitkat
H. Flash L
I. Backup again in a few formats to be safe, (consider doing specific packages)
J. (when in states with new handset) Start phone after L is available for OTA. Assumedly it'll start in kitkat then I'll have to OK the OTA. Result: new handset, locked, with factory OTA L, basic personal settings from google backup.
K. Unlock bootloader
L. Root
M. Allow standard startup to run (back to fresh L)
N. adb Restore from stage "I" backups (above) = back to 'normal' on L. Result: new handset, unlocked & rooted, with L & all my saved app data.
2. Does the above process sound like the best way to go about things, given my situation? If not, what would you do differently?
Thanks. I know this sounds super unique, but I figure anyone currently needing to RMA (TONS of people) is in the same boat.
Cheers!
dez
Currently I have an unrooted locked bootloader kitkat N5. It has a ton of problems (GPS bad, camera bad, wifi doesn't turn on, wifi doesn't save passwords properly, etc) and I'm RMA-ing it when I get back to the 'states in about 2 weeks. Given that I'll need to backup my app info for the RMA, I've been researching adb backup & got it working.
1. On locked phones, adb backup doesn't backup google authenticator, nor... what else? Better to know ahead of time.
Given that I can't get on wifi currently, and that I'll have to migrate to L anyway, I figure I might as well do the following procedure:
A. Unlink google authenticators (& save any other unbackupable things from Q1)
B. Empty all SD card files (quicker backups)
C. Backup again in a few formats to be safe, (consider doing specific packages), 'best' code: "adb backup -f backupDATE.ab -apk -noshared -all -system"
D. Unlock bootloader
E. Root
F. Allow standard startup to run (back to fresh kitkat)
G. adb Restore from backups = back to 'normal' on kitkat
H. Flash L
I. Backup again in a few formats to be safe, (consider doing specific packages)
J. (when in states with new handset) Start phone after L is available for OTA. Assumedly it'll start in kitkat then I'll have to OK the OTA. Result: new handset, locked, with factory OTA L, basic personal settings from google backup.
K. Unlock bootloader
L. Root
M. Allow standard startup to run (back to fresh L)
N. adb Restore from stage "I" backups (above) = back to 'normal' on L. Result: new handset, unlocked & rooted, with L & all my saved app data.
2. Does the above process sound like the best way to go about things, given my situation? If not, what would you do differently?
Thanks. I know this sounds super unique, but I figure anyone currently needing to RMA (TONS of people) is in the same boat.
Cheers!
dez
