“Built it, flashed it, bootlooped.” WAIT NO????

Context

Well, I like to thinker with shit, and recently I’ve come more used to AI Tools and how good they actually became at coding.

So I said, why not extend the previusly extend life of an Android Device by vibecoding the shit out of previous incomplete projects of a Motorola SM6150 kernel and make it work?

In the past we had a bunch of bootloops, kernel problems, incomplete API surfaces, almost bricking the device 6x times in a row. And much more (read past devlogs)

Faster Bootloops

Well, in Software Engineering the anwser always may be WAY more simple than it looks. In the case of the “flash” of the Motorola Logo (fast bootloop), it had something to do with in how the OTA package messes with the partition table. In those cases the anwser was just to do flash the Stock Partition table of the device (fastboot flash partition), and it would just boot.

This happened WAY too many times, so in the (spoiler: end of the post) that was just randomly fixed.

Boot stall?

After way too many back and forths with GPT, a new OpenCode config (abusing the heck out of GPT-5.6-Luna in Max Reasoning as a subagent) we had a phone that didn’t bootloop! (YAH!)

But… It didn’t do anything. We were only meet with a Motorola Logo for a LONG time. (I called it Boot Stuck but GPT said its actually called a Stall, like the thing with manual transmition cars)

LineageOS Boot Animation?

Like the past chapter, with a bunch of back and forths (and 14 tries) I was meet with three dots circling (and that felt REALLYY GOOD).
After a litle more it was the LineageOS Logo Animation, then the dots again, then it repeated… Looking through GPT logs, it was actually the GPU driver that was kinda broken, it fixed it!

WAIT, “WELCOME TO LINEAGEOS!” WTF!!!!!

In the TRY number 18, didn’t need to flash the partition table once more (that was strange), animation logo, LineageOS logo and, the “Welcome to LineageOS!” text.

I was astonished, the first step to having the phone, Android 16 and almost brand new.

The thing is… Touch of the screen didn’t work… So we need to work on that. Plus all the commits and changes.