-
Notifications
You must be signed in to change notification settings - Fork 659
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[A/B] Boot doesn't set current slot as bootable after successful boot #55
Comments
To workaround this issue, I added "PRODUCT_PACKAGES += bootctl" to device_phh_treble/generate.sh |
I don't get such a problem on Razer Phone, that's a bit weird. Something as simple as on property:sys.boot_completed=1 bootctl mark-boot-successful in an init.rc should be enough I guess, but I want to check the behaviour on an A-only device first |
Tested on a Google Pixel (arm64, A/B):
I put that into The bootloader successfully marked the slot as bootable. Before first boot:
After first boot:
|
There I commited: |
Fetched, and tested on a Google Pixel XL (A/B): it works. |
Update OP6T Overlay
On A/B partition devices, system must mark current slot as "bootable" after successful boot.
Otherwise bootloader counts down slot-retry-count and it reboots in bootloader recovery mode when slot-retry-count became 0.
https://source.android.com/devices/tech/ota/ab/ab_implement
Currently slot is not marked as bootable even if the device boots successfully.
I tested on Sharp AQUOS S2 SS2 (arm64).
The text was updated successfully, but these errors were encountered: