Open craftyguy opened 8 years ago
Wow, after a TON of troubleshooting, I managed to figure out that these two packages were disabled. I did not disable them. Are there any conditions where oandbackup would disable them?
package:com.android.terminal
package:android
When I re-enabled them (by spamming adb on bootup before it reset), I was able to boot successfully.
to be honest it's not quite easy to imagine what could have gone wrong here. oab only disables packages when asked explicitly and when restoring on a multi-user setup. i'm sorry to give you a useless answer but i'm thinking that some of the programs called by oab maybe triggered a system bug. i don't know about the backup manager service, oab never touches that part of android. if you can reproduce this issue on different (nightly) versions of your rom then i'll make you an apk which tries to do some persistent logging.
I've not been able to reproduce it, but then again I've not been able to reproduce the crash that resulted in my phone resetting. I don't know if the two (phone crash + two important apps being disabled) are related or not, and this may go unsolved, but thought I would mention this to you just in case. I'll report back if I make any progress in reproducing it.
I had a similar issue, but I accidentally restored some system apps .apk files included.
After installing this app and attempting to do a backup of user apps, the device immediately rebooted and has been unable to boot. It seems that oandbackup has done something to the Backup Manager Service (see logcat output below). If I remove oandbackup (using pm over adb), the Backup Manager Service complains about oandbackup not being installed.
The device is a MotoX 2014 (victara) running CyanogenMod 13 (nightly from 9/06).
Logcat when oandbackup has been removed: