Thanks, I had done that before with a different ROM from @ronnz98
But maybe for someone else: Just extract boot.IMG from a different ROM place it on the device, when in TWRP via MTP, choose install IMG in TWRP and choose boot as target.
It’s pretty simple and you can always install a full ROM again, if something doesn’t work out!
The one thing I really enjoy on the hardware side is the sound and now – coming from Android 5 – I get to install all the apps I like.
Being able to choose grid size and accent color, makes me very happy, too!!!
Rotating app launcher and log in screen, yeah that is nice, too!!
Calendar app with all calendars from my nextcloud and murena look pretty good, too!
Video playback with any of my apps for local media, as well as newpipe, work flawless in HD.
Drawbacks, no opengapps… in my case, only a not so well working KiwiBrowser so far.
Battery life is good, started at 55% 10h ago and it’s down to 38% now.
Browser seem to cause the highest load, but still okay.
So, this is a useful daily driver for media and casual browsing.
In another post someone asked what vbmeta was, it got me thinking… @ronnz98 & @piero as its Verified Boot Metadata, is it maybe because of something in there, which stops it from booting, maybe? Any ideas, deeper knowledge?
I see no mentions of Verified Boot Meta Data on the TWRP download website or instructions in the lineageos build thread on XDA forum.
But i found :
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting
you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it’s likely because you didn’t follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Tanks @Piero
I did all of the above MUSTs on three T550, before trying @ronnz98 versions of /e and none of them booted. On two T550s I tried LOS and both booted right away…
Q18. Will this rom ever become official?
A18. Never. I don’t want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standard
what about /e/ standard ? that are based on lineageOS standard
In addition to the sources, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.
Yes, I find it’s just always a pity, if somebody figured it out and the knowledge on bits and piece gets lost. Wouldn’t it be great, if @ronnz98 could just piece together a working /e build…