I have an old HTC One M7, and have found the LineageOS 14.1 ROM that works on it, and a 15.1 that doesn't. I thought I'd like to have a crack at making a LineageOS 16 builld for it. There's one unofficial one for the M8 for 16.0 and the system/build.prop file contents of the M8 16.0 ROM zip and the M7 14.1 ROM zip would indicate that they are very similar hardware wise. However, it complains that the M7 is not one of it's target devices if I try to install the 16.0 ROM with TWRP. Haven't worked out how to fool it or modify it to be recognised for the M7 (due mostly to my ignorance).
All of the build guides I have are for the cm-14.1 target, not lineage-16.0 target (I guess that's why it's not officially supported any more ).
First question, is this even possible to do, or am I barking up the wrong tree?
I follow the build guides for the M7 and M8 builds but using the lineage-16.0 target and get stuck after the build/envsetup.sh step as breakfast doesn't exist, and I guess in the 16.0 build tree, the M7 hardware is not defined.
Are their better guides for this type of thing available?
Regards
Braedon
Related
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
flamingspartan3 said:
Hi everyone,
I'm currently working on building Lineage OS 13, which is unsupported on the Nexus 7 2013. My device has WiFi issues with 14.1 and none of the Marshmallow ROMs incorporate a fix for the Krack vulnerability. Since this fix is already part of the cm-13.0 branch, I've been trying to build it but running into the following error when I run "breakfast flo".
Code:
build/core/product_config.mk:257: *** No matches for product "lineage_flo". Stop.
Device flo not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
I have already incorporated the Muppet's proprietary blobs for Flo but don't know how to deal with this error. I have experience with the Linux command line and programming using Java but am new to ROM-building.
Click to expand...
Click to collapse
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
flex1911 said:
You will need to apply device tree rebrand like it's done in 14.1: https://github.com/LineageOS/android_device_asus_flo/commit/e596a332b44ea40769fc516c451728b1cd58eb2b
Click to expand...
Click to collapse
Thanks for the help! I was able to get it to work by running 'lunch cm_flo-userdebug' and then mka.
Are you sure the Krack fix isn't already in 14.1:
https://www.lineageos.org/Changelog-15/
KRACK Wi-Fi vulnerability has been fixed in both LineageOS 14.1 and 13.0
Click to expand...
Click to collapse
Why official LineageOS community don't build ROM for OnePlus 5T ?
It is some thing wrong on OnePlus 5T hardware driver ?
Until the unofficial builds have everything worked out it will not go official. Second they are only building Oreo builds at the moment, and there are no Official LOS 15 builds at all at the moment. So if you want an official Lineage build, someone needs to start building a 14.1 build for dumpling. Which honestly in my opinion would be a good thing, as many features are still missing for 15.1.
So:
1. There are no official builds for LOS 15.1 yet for any device.
2. The unofficial builds are not bug free, so they would not meet official build standards yet.
You have to wait. Give it time.
You can watch developers' progress on 15.1 for the OP5T here:
https://github.com/LineageOS/android_device_oneplus_dumpling
But notice, the last commit was 6 days ago, and compared to the OP5, it has a long way to go:
https://github.com/LineageOS/android_device_oneplus_cheeseburger
THIS THREAD CLOSED
--------------------------
Hi friends,
Because lineageOS stop supporting xiaomi devices this month, so I decided to build LOS 16 ROM for sagit myself.
I have some experience of using linux, but that is my first time to build an Android rom.
I follow the official guide to build. https://wiki.lineageos.org/devices/sagit/build And I got the freshable zip rom "successfully".
However, after I install it via the lastest TWRP, it stuck on the boot MI logo and can not enter the system.
I ask one oneplus developer, he told me some xiaomi device need specific clang version, but he can not give me a solution. I come here and hope someone can give me some propose.
-----------------------------
UPDATE, I found los group ready the re-support xiaomi device. https://github.com/LineageOS/hudson/commit/9e0206569670a2566562e000b9f1e3492eacca83
But I still hope get some answer just for study.
-----------------------------
UPDATE II
I found the reason that I use a wrong branch of VT repo. I use another VT repo in gitlab when the github repo was closed because of DMCA. And the default branch of the gitlab one is not LOS16. My bad. Sorry to bother everyone.
Thread closed!
-LTT
Hi!
I have been looking some time for a Lineage 16.0 device tree to build Lineage 16.0 to this phone and as I forked the 17.1 repo made by whatawurst I started to change it accordingly and the reason for it is that I intend to build libhybris with Lineage 16.0 as a base since there's no hybris-17.1....... YET (It's coming though).... to it so that I may boot Sailfish OS as well.
I had to change the standard local manifest and make my own repos for obvious reasons.
Now here's the fun part.
I extracted the blobs from the phone and put them in my vendor repo and synced without a problem.
I then ran source build/envsetup.sh && lunch lineage_beyond2lte-userdebug and it worked OK.
As I started to build Lineage I got an error about a missing ril file and YES I suspect that it's missing a lot more files as well.
I have no clue why ./extract-files.sh in /android/lineage/device/samsung/beyond2lte looked for files that aren't in the stock vendor directory.
I guess it differs from Lineage version to another.
I also know that Lineage 16.0 won't boot on a Q bootloader, but I don't intend to boot Lineage after it's built.
I'd appreciate if someone here would be kind enough to help me fix any missing files so that Lineage 16.0 will build.
When I can confirm that it builds I'll start to try: https://github.com/mer-hybris/hybris-patches/tree/hybris-16.0
Here's my device tree for Lineage 16.0: https://github.com/Umeaboy/android_device_samsung_beyond2lte
Hi. I want to try to build lineage os 17/18 for my old phone. I have env and I already build package for other phone. For Nexus 4 there and only some old lineage os 15 builds. How to prepare lineage os 18 based on lineage os 15? Is it possible or maybe it needs to be done from scratch. Is there any instruction how to do this?
Porting a ROM means there's a similar device with a working LineageOS on it. Which means it's already built, and only small modifications to make it stable for you.
Porting doesn't work the way you described. You can't build Android 12 on top of Android 8, every new major Android update, Google releases a new source code.
Then, manufacturers/developers modify it to their sweets. What you want to do is to build LineageOS 18/17 for an unsupported device. There's a lot of guides online about it. The context matters.
Can you share some links about building lineage os for unsupported devices? Will it help somehow when there are some old versions builds?