All AOSP Android 14 builds after 1-29 fail to boot

[AnonVendetta]

So, it's just like the title says. From the earliest A14 builds all the way up to 1-29-2024, I can boot the gsis successfully. But on all AOSP builds produced after that date, starting from 1-30, the bootloader screen just bootloops back to itself infinitely. The Android logo doesn't have a chance to appear, so I don't think adb logs are possible. I can manually get into TWRP with a button combo while USB plugged into my laptop, but if I don't do that then it's just a neverending bootloop back to bootloader screem.

Device: Galaxy Tab S7 Plus, SM-T976N, recently flashed with the latest stock A13 firmware (Samsung has already stated that this model lineup won't get stock A14, just A13 security patch firmwares until the end of its' update lifespan).

I have TWRP, Magisk Delta is in my boot.img. and I changed offset 123 in my stock vbmeta.img to 03. I doubt this is a vbmeta issue, since I can boot all A13 AOSP gsis, and A14 AOSP gsis up until 1-29.

I can replicate the same behavior on a Note 20 Ultra, also flashed with latest A13 stock firmware, but I don't want to submit logs for that device. It's currently running LOS20 and I'm very happy with it, so I'm keeping that gsi long term.

@phhusson: Is there any logs I can get from TWRP that might help? I understand I can't be helped without logs, but as of right now i'm not sure what to send. Thanks.

Edit: just thought I'd note this, but I tried lots of other A14 gsis. So far the only one that actually manages to boot into Android is the official Google GSI. With Project Elixir I can get as far as the gsi's PE boot logo, but it stalls there and won't go further. With all other A14 gsis they just immediately reboot into recovery after a few seconds on Samsung unlocked bootloader screen. Something must have changed between the 1-29 and 1-30 builds that is behind the boot fails.

I've checked /sys/fs/pstore in TWRP, the directory is empty. I did find last_kmesg files in /proc, but I'm not sure if they're for the TWRP's kernel, or the one that the ROM uses to boot. That's all I have, so I'm attaching them. My logs are for the 1-30 and 2-26 builds. of course no log is needed for 1-29 build, since it boots. I also find it interesting that the data partition remains largely unpopulated, which indicates that Android never got a chance to fully load. There are a few directories in it, but only the ones that were already there when I wiped data/cache in TWRP, as i always do when flashing a new ROM.

logs.zip

[phhusson]

From twrp your can grab logs from /sys/fs/pstore after trying/failing to boot gsi. Ideally with the phone as cold at possible, so maybe put it in a fridge for 10 minutes before booting gsi. The cutoff date your gave could be enough for me to debug. Though I'm unavailable for a week, and will have forgotten your ticket then

Le dimanche 17 mars 2024 à 08:19, AnonVendetta @.***> a écrit :

 So, it's just like the title says. From the earliest A14 builds all  the way up to 1-29-2024, I can boot the gsis successfully. But on  all AOSP builds produced after that date, starting from 1-30, the  bootloader screen just kicks me back into TWRP. The Android logo  doesn't have a chance to appear, so I don't think adb logs are  possible.    Device: Galaxy Tab S7 Plus, SM-T976N, recently flashed with the  latest stock A13 firmware (Samsung has already stated that this  model lineup won't get stock A14, just A13 security patch firmwares  until the end of its' update lifespan).    I have TWRP, Magisk Delta is in my boot.img. and I changed offset  123 in my stock vbmeta.img to 03. I doubt this is a vbmeta issue,  since I can boot all A13 AOSP gsis, and A14 AOSP gsis up until 1-29.    I can replicate the same behavior on a Note 20 Ultra, also flashed  with latest A13 stock firmware, but I don't want to submit logs for  that device. It's currently running LOS20 and I'm very happy with  it, so I'm keeping that gsi long term.   @. [https://github.com/phhusson]: Is there any logs I can get  from TWRP that might help? I understand I can't be helped without  logs, but as of right now i'm not sure what to send. Thanks.    —  Reply to this email directly, view it on GitHub  [https://github.com/TrebleDroid/treble_experimentations/issues/108],  or unsubscribe  [https://github.com/notifications/unsubscribe-auth/AAAA4OQ4IVKMWNGZHD3IRJ3YYU7Y7AVCNFSM6AAAAABEZ7L4TSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGE4TANJSGAZTMNA].  You are receiving this because you were mentioned.Message ID: @.>

[AnonVendetta]

@phhusson: I've tried several times to find a log file in /sys/fs/pstore, via the fridge method, but always nothing every time. I put it in a sealed bag to keep moisture from getting in, seemed cool when i took it out. Are there logs in other locations I can look for? I don't know if you can glean info from the last_kmesg logs I've already submitted. They may be for twrp's kernel and not the kernel the gsis boot with. I can't know for sure.

[phhusson]

Try to run mount -t pstore none /sys/fs/pstore in your TWRP after starting. Did it say nothing or did it give an error? If it said nothing, that means your TWRP didn't do it for you and you need to catch logs again but before going in /sys/fs/pstore you must run that command

[AnonVendetta]

@phhusson: After reflashing the non booting gsi, the error i'm getting from that command is: mount: 'none' -> /sys/fs/pstore': Device or resource busy

It would seem that my TWRP is automounting, which explains that error. I checked the output of the mount command, without any parameters, pstore is indeed mounting to /sys/fs/pstore.

Regardless of whether i use that command or not, it's empty.