View Single Post
Old 03-09-2022, 07:10 PM   #3
downeaster59
Wizard
downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.downeaster59 ought to be getting tired of karma fortunes by now.
 
downeaster59's Avatar
 
Posts: 1,251
Karma: 2957301
Join Date: Apr 2014
Location: Rochester, NY
Device: Boox Go 10.3, Kobo Libra 2
Quote:
Originally Posted by Renate View Post
If you decrypt the update and unzip you can see if any part of it is an incremental update (instead of a full update) which might be a conflict if you modified something. If any of the "patch" files (vs. "new" files) are not zero, then it's incremental. Or you can look at META-INF\com\google\android\updater-script to see if it says things like:
Code:
ui_print("Patching system image unconditionally...");
The most proactive way to investigate this would be to take it to recovery and manually install from there over ADB. That way you get the real log.
It must be an incremental update. Its size is 187 MB. That seems too small for a full update, even if it is compressed. It's possible that my device being rooted is itself the issue. I haven't made any other modifications beyond root itself. Still, it'll be worth following up on your suggestions. Thanks.
downeaster59 is offline   Reply With Quote