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
[ASUS Zenfone 5 (2018)] Unable to boot v300.f/g #1553
Comments
After some difficulty in building kernel, I finally enabled pstore and got some ramoops - see if it's of any use? |
I attach here for the reference the logs of a device that succeeds to boot a-only (Moto E5, vndk 26, arm32) What I see as difference is:
so add a |
@phhusson I don't have an AOSP workspace though, and according to others' reports, only AOSP boots on A-only so far. Can I modify this on-device myself, or get a test build from you? |
Yes that's it, booted! It lags compared to Q, but that's not the concern here. |
Device: ASUS Zenfone 5 (2018)
Treble status: Yes, non-SaR A-only, native
Stock Android version: 8 (VNDK 26) or 9 (VNDK 28)
Neither versions of stock base would boot v300.f/g. Stock 8 base does a splash loop, while 9 base reboots after splash into the bootloader.
In both cases, after rebooting into TWRP to check, pstore and last_kmsg are absent.
Tried changing fstab to use EXT4 data (ASUS likes F2FS), no change.
Android 10 GSIs boot normally.
The text was updated successfully, but these errors were encountered: