Repository navigation
device-lynx 0.2.2: accept devinfo 3.11 for boot-success - #436
Conversation
41f26c2 to
b10d9a0
Compare
|
Thank you for this, and for writing up the 3.11 unit so clearly. A phone whose bootloader is a release behind is exactly the case our boot-success refusal was built for, and I'm glad it refused rather than guessed. I'd like to get 3.11 supported, but not quite this way yet:
Smaller things: the comment above the new table still says 3.15 is the only layout; the new comment says 3.15 came from "the Android 17 bootloader used by the published lynx notes", which the notes don't say (3.15 was first checked on the 7 Pro); a |
|
Thanks for the careful review, and for the 3.11 write concern. Agreed on all points.
I will bump the version only when you say which number is free. The phone is currently back on stock Android, so the table and smoke report need one Arch reflash after the patch is review-shaped. Assisted-by: DeepSeek |
b10d9a0 to
9861bd8
Compare
|
Revised as requested:
Still to add from your list: the 3.11 eight-byte table, the record of the earlier write, the comment fixes, ools/phone-smoke, and the NOTES line that both slots carry lynx-15.2. Those need the one Arch reflash; I will do them before asking for another review. Assisted-by: DeepSeek |
|
Thank you for turning this around so quickly, and for keeping the shared table behind a build-time switch as I asked. It's the right shape. I also appreciate that you didn't write
Smaller things: NOTES is newest first, so the 11-06 section belongs at the top, and the 10-30 "Fix:" bullet still describes the shared table. The title still says 0.2.2. I'll set the version and title at merge, since #98 and #438 also bump device-lynx. #98 is closest to ready, and #438 waits for the kernel side. Thanks again. The package tests pass here, the 3.14 refusal test is a good addition, and |
3f08df9 to
0d45ab5
Compare
|
Rebased onto current main (71b47a6) and followed your smaller shape exactly:
On the bytes: you were right that the table was not same-state. I marked it provisional in NOTES.md - the Linux bytes and bootloader getvar were read in separate cycles, the retry byte disagrees, and slot A's flags differ. I have not claimed 3.11 is validated; a same-moment table still needs one Arch run. #436 is mergeable/clean now. Assisted-by: DeepSeek |
|
Thank you for the rework. The shared source now has exactly the shape we discussed, and I reproduced your check: cheetah's That honesty is also why I can't merge it yet:
Smaller: NOTES is newest first, so the 11-06 section belongs at the top. If you like, copy the same source change into the Pixel 6 Pro package's |
Android 15 lynx units report
devinfo3.11, whileomamobile-device-lynx0.2.0 only accepted 3.15. On this unitomamobile-boot-successrefused to write, so slot B stayed unmarked and burned its retries.The A/B slot bytes are at the same offsets in both layouts. This adds a verified-layout table for 3.11 and 3.15, keeps the write refusal for anything else, and covers the 3.11 one-byte plan plus an unverified 3.14 rejection in the lynx package test.
main.device/lynx/NOTES.mdrecords the unit evidence; the matrix row notes 3.11 support from 0.2.2.7.3.0-rc6-omamobile-push1-gfbbcac19d8ea, GT9895 touch works, slot B's earlier marking is not recorded.Package tests pass, including
ok - bootctl accepts devinfo 3.11andok - bootctl refuses an unverified devinfo layout.Assisted-by: DeepSeek