Develop Bugs

Personal Build Playground Moto G5 Plus

I'm creating this thread to post personal builds to those that want to try them. Just an FYI I'm choosing this approach instead opening numerous unoffical build threads because 1)I'm unsure how much time I'll be able to invest 2) I'm too much of a flashaholic to stay with one rom long enough to properly support it 3) I'm not a dev, I'm just someone with a linux laptop that enjoys putting pieces together. Also If anyone would like to share their builds or assist with others that want to learn to compile. (JUST PLEASE DO EVERYONE A FAVOR AND MAKE SURE THE ROM BOOTS FIRST AND ARE NOT GOING BRICK DEVICES ALONG WITH SOURCES)(BUGS are expected this is a newbie.....as in Me thread)
Note:
I used SuperSU for root on this rom with no problems what so ever, Mileage may very with those that use Magisk.
Maintaining of rom may be here nor there depending on if I grow tired of the rom and decide to go to bigger and better things or if time allows, so please don't expect or request updates......I'm doing this just to share my personal builds and hopefully spark interest with others.
OREO BUILD ......CARDINAL-AOSP
rom: https://github.com/Cardinal-AOSP
more info:https://plus.google.com/communities/110928715574226998482
Launcher used in screenshot: https://www.androidheadlines.com/20...ixel-2s-pixel-launcher-with-new-features.html
Missing gallery app, use simple gallery or one your choose from playstore.
bugs....same as anyother oreo rom at the moment as this is built one top lineage and vache device tree and HAL's
download: https://drive.google.com/file/d/0B2AnAjPZx9hjYnBrZEJmdFBSWVE/view?usp=sharing
MD5: 36f091041cf70dd03ce8e7c4b37c4397
XPERIENCE 12.0 OREO!!
rom: https://github.com/XPerience-AOSP-Lollipop
website: http://thexperienceproject.com/
download: https://drive.google.com/file/d/0B2AnAjPZx9hjckNWQllFQjZ2Q3c/view?usp=sharing
md5sum: b7bbf632b76deb74d35336bf47466f77 xperience-12.0.0-20171015-HOMECASE-potter.zip
Bugs bluetooth app may FC on initial boot but once in the rom it seems to be working fine
Thanks and Happy Flashing.......or sharing which ever you choose.
PS yeah I know I need to make this OP a little more easy to find builds and I'll get to that shortly
Source:
Device: https://github.com/boulzordev/android_device_motorola_potter
Vendor: https://github.com/boulzordev/android_vendor_motorola_potter
Kernel: https://github.com/boulzordev/android_kernel_motorola_msm8953
Rom: https://github.com/CypherOS
Here is my Device Folder for those that want to download and tinker https://drive.google.com/drive/folders/0B2AnAjPZx9hjeVVzVWNrajV6MTg?usp=sharing
Very handing DYI that I've used back with I was building roms for my LG phone https://forum.xda-developers.com/showthread.php?t=2223690
older nougat builds:
-CypherOS 4.1.2 release
-Camera fixes thanks and cherry picked from gregor160300 along with his version of CMActions that are better suited for aosp based roms.
Rom: https://drive.google.com/file/d/0B2AnAjPZx9hjdUwwR0pHdzZoU1k/view?usp=sharing
MD5:93a5e9a1435051f18b799dd794898a1b
SlimRoms Build 1.11
synced to give us the up to date slim since our beloved potter has been dropped from official status.
https://drive.google.com/file/d/0B2AnAjPZx9hjb1RhaTdkODlzclE/view?usp=sharing
md5sum: 01eec677fc705ef5432cda7597c0aebf

Working like a charm

NEW UPDATE! 9/25 this is a new upload any previous update is now obsolete and will probably be my last build for the nougat version of this rom as I'm looking at other build possibilities

Thanks alot. Will flash ROM and let you know.

SlimRoms build 1.11
new SlimRoms build is up:good:

I Feel like playing
feeling the urge to pull out some more hair and scream a few more swear words at my computer:silly:

Oppps I slipped
just a teaser of things to come for those that check this thread

tuxattack80 said:
just a teaser of things to come for those that check this thread
Click to expand...
Click to collapse
Awesome :good: But why don't you create a thread in the Rom section? BTW What Linux distro are you running?

McKellen said:
Awesome :good: But why don't you create a thread in the Rom section? BTW What Linux distro are you running?
Click to expand...
Click to collapse
I'm running Ubuntu mate 16.04 at the moment but I hop distros from arch to fedora. And that kind of answers your other question, I'm to A.D.D to stick with one rom for long and I open a thread I'm committing to that rom. This is more or less a hobby for me and when get a chance I'll build but it doesn't happen very much between the kids and the girlfriend lol.

Is that cardinal 8.0

syrkles said:
Is that cardinal 8.0
Click to expand...
Click to collapse
Yep

Xperience 12.0 oreo!!
New build up in OP, ENJOY!

Hey thanks for sharing I'll test one out this weekend .

Cardinal Update is in the oven
Had a ittle bitty stump in the build but don't worry I made it up to you all by adding a couple of additional features
PS....why is it so quite in here?? Feels like I'm talking to myself.........this is a discussion/build form lol! crickets!!crickets!! crickets!! Believe me all I don't mind a little off topic as long as you keep it clean and nice and android focused. Just don't blow up the thread with screenshots or links
Soooooo........thinking about a rebase to another linux distro soon...any input on with one? Thinking Fedora because it's also a great distro for building on but I do miss Solus and Arch

Hi!! I'm that guy from g+ remember me?? The one asking for the cypher os build? Well I've come to ask again, sorry if that sounded a little rude.
No, but my DUDEE! I think cypher 5.0 sources are up already. Can you make a build? Please? I don't if you take request like this but at least I tried.
Also that cardinal build is ? supper smooth, just one thing fingerprint gesture didn't work either. I hope you fix that in the update. Thank you for all this ROMs that no one are building, just you

RonaldRND said:
Hi!! I'm that guy from g+ remember me? The one asking for the cypher os build? Well I've come to ask again, sorry if that sounded a little rude.
No, but my DUDEE! I think cypher 5.0 sources are up already. Can you make a build? Please? I don't if you take request like this but at least I tried.
Also that cardinal build is supper smooth, just one thing fingerprint gesture didn't work either. I hope you fix that in the update. Thank you for all this ROMs that no one are building, just you
Click to expand...
Click to collapse
delete

RonaldRND said:
Hi!! I'm that guy from g+ remember me? The one asking for the cypher os build? Well I've come to ask again, sorry if that sounded a little rude.
No, but my DUDEE! I think cypher 5.0 sources are up already. Can you make a build? Please? I don't if you take request like this but at least I tried.
Also that cardinal build is supper smooth, just one thing fingerprint gesture didn't work either. I hope you fix that in the update. Thank you for all this ROMs that no one are building, just you
Click to expand...
Click to collapse
Thanks for the feed back, I'll look into the fingerprint thing again soon but probably wont be in this build as its already building after being up all night trying to wrap my head around a feature that due to sleep will have to wait lol. I'll see if I cant get a cypher build out soon as well:good:

Cardinal AOSP Update 10/19
Alright peps, sorry for the long delay....but the build is ready. Not exactly what I want to upload because I was wanting to add a certain feature but with sleep deprivation kicking in I was forced to put it on the back burner and do a clean build. So with that said I'm going to get some rest and I will update the OP with changes and so on tomorrow...HAPPY FLASHING :cyclops::silly::victory:
download : https://drive.google.com/file/d/0B2AnAjPZx9hjbV93M2N1Q0pJcEk/view?usp=sharing
md5sum: f7c99b93e53163e4533e55e66b687be8
Quick observation snapdragon camera force closes, so you footej or whatever alternate camera app you like, will revert back to camera2 in next build

tuxattack80 said:
Cardinal Update is in the oven
Had a ittle bitty stump in the build but don't worry I made it up to you all by adding a couple of additional features
PS....why is it so quite in here?? Feels like I'm talking to myself.........this is a discussion/build form lol! crickets!!crickets!! crickets!! Believe me all I don't mind a little off topic as long as you keep it clean and nice and android focused. Just don't blow up the thread with screenshots or links
Soooooo........thinking about a rebase to another linux distro soon...any input on with one? Thinking Fedora because it's also a great distro for building on but I do miss Solus and Arch
Click to expand...
Click to collapse
Arch

Thanks going to try this but you should move your thread to Moto G5+ Development Section. I think no one checks ROMs on Discussion section.
Edit - Your Drive Link is not working - https://goo.gl/7yBr7e

No Official Lineage OS 15.1 for MARLIN :( Because of no Developer...

I just chatted with someone at Lineage OS and they are looking for a Developer for Marlin for Lineage 15.1. He is stating there will be no Official Builds because they have any Devs with the device and i told him i would help find someone who would like to take over Lineage OS for Marlin. If your interested, this person is asking for your gerit username i'm guessing to see your work. Please let me know if your interested in taking over Official Lineage OS builds for Marlin at your earliest conveinence or you can contact Lineage OS yourself from the information below on how to become a Developer...
Thanks in advance,
TJ
From Lineage OS Website :
For developers
Contribute!
To contribute, you’ll need to be able to produce builds for your device. Pick your device from our list of supported devices to get started.
Once you’re successfully running your own build, you can begin to make your changes. All the apps included in LineageOS can be found in packages/apps, and core parts of the system can be found in frameworks/base.
Once you’ve finished making your change, simply follow our guide on submitting to Gerrit.
Submit your port!
If you unofficially maintain a device, and think it’s good enough to go live, follow our instructions on submitting a port. One of our developer relations staff will reach out to you, and we’ll work to get the ball rolling on official builds for your device.
Thanks again!
*edit*
If this developement stops, so will the few custom ROMs we have being they are LOS based so if there are any free and no tied up at the moment, or wants to take on another project, PLEASE do this for the Pixel XL Custom ROM Community! Not only I would gladly appreciate your hard work but so will many others in the community. I will even donate $$$ if thats what it takes for the build and for at least weekly updates.

Invisiblek is a dev who already has unofficial builds up and running
https://forum.xda-developers.com/member.php?u=2385005

spamfilter247 said:
https://forum.xda-developers.com/member.php?u=2385005
Click to expand...
Click to collapse
Yea I contacted him via PM and let him know the situation with Official Builds are that they are looking for an Official Builder.

I hope you all understand the work it entitles to take on a rom project.. you really shouldn't ask people to take over someone else's work unless this dev asks themselves...

60smusic said:
I hope you all understand the work it entitles to take on a rom project.. you really shouldn't ask people to take over someone else's work unless this dev asks themselves...
Click to expand...
Click to collapse
I was informed by a Lineage OS Developer that there will be NO MARLIN Official Lineage OS Builds going out any time soon, it happens that they dont even have a Dev for our Device and i;m guessing they dont have our device either... I am just putting it out there, and there may or may not be someone qualified with the time to do it. But if we get official Builds, we'll get alot more Custom ROMs...

[HomeBrews] Pixel 2: LineageOS/CarbonROM/DirtyUnicorns

Dirty Unicorns is a project that started out with no name. It was a project that was first based off AOKP back in the early days of Jelly Bean. In the early days it was just a one man show on one device, the EVO 3D. Since then, many others have joined the project and it has grown exponentially.
We have seen a lot of talent contribute to this project of ours. Big or small, the focus was always on contributing to the community. That is ultimately why we do what we do. After Jelly Bean, we decided to move to a new base, OmniROM. While AOKP was fun, OmniROM proved to be even more exciting base because it challenged us to see what we could do with a project that had different goals in mind. We learned a lot and again, gain contributors. With Lollipop, we moved to an AOSP base with a lot of patches from CAF to make our older devices function as they should. We grew even more and learned a whole lot more.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Pre-Disclaimer:
THIS IS AN UNOFFICIAL BUILD. The intent is to showcase what is coming up soon. I have been working hard on getting Walleye on a level I consider DD ready, especially from a security side of things.
Please keep any problems with those builds in this thread, I don't accept any bug reports for any other builds other than my HomeBrews.
Disclaimer:
While I make every effort to test these builds as much as possible, I am not responsible for anything that may happen to your device. I ask that you do your part to know your device and know how to recover from problems before you flash or post that you broke your phone!
Support:
I spend an astonishing amount of time developing this device. I can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Ask a question in this forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
Notice:
This build includes GApps for now. We're still working on ways to not prebundle it.
Before you flash, make sure you're on the latest 8.1 stock builds (and bootloader), then flash the ROM in TWRP.
Instructions :
Boot to TWRP
Format Data (If you didn't type YES, you did it wrong!)
adb sideload homebrews.zip
reboot system
(to gain root you must first boot homebrewsROM. Then reboot and to TWRP and install Magisk 1 6.0)
See below
Reporting Bugs:
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
What is your--
Build Date:
Did you--
wipe:
all data?
install gapps when you weren't suppose to?
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
WARNING: These are my personal testing builds. They include unmerged, work-in-progress stuff such as SuperUser, Privacy Guard, Google Play services etc. DO NOT FLASH 3RD PARTY GAPPS PACKAGES!
If you see a warning about vendor partition mismatch, you can ignore that in most cases, but before reporting issues you should be on the right version (without the warning).
### RELEASES ###
https://drive.google.com/drive/folders/1NY1j-eH9demisz5Y05jeIPGXipENo5yK?usp=sharing
XDAevDB Information
LineageOS, ROM for the Google Pixel 2
CarbonROM, ROM for the Google Pixel 2
DirtyUnicorns, ROM for the Google Pixel 2
Contributors
Source Code: http://github.com/LineageOS
Source Code: http://github.com/CarbonROM
Source Code: http://github.com/DirtyUnicorns
Source Code: http://github.com/TresReinosDeLeche
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
### DONATE ###
paypal.me/JacobStermer
Created 2018-02-2
Last Updated 2018-03-Today

reserved

Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.

I for one am happy to see it.

iluvamk said:
I for one am happy to see it.
Click to expand...
Click to collapse
Me to ? do we need to flash twrp after the ROM like on pixel 1?

GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.

Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse

Archangel said:
Holy crap do my lying eyes deceive me or is there a rom for the Pixel 2 LOL,,,thanks brother for letting me know about this. Now who is going to be the guinea pig and flash it LOL
Click to expand...
Click to collapse
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?

Let us know how it goes brother.
jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse

jasonsamms666 said:
I'll flash it I just need more clear instructions. Likes wipes and do I need to flash twrp?
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.
right now i am getting FC on Camera APP, X Google, Ok Google, and T Google something. My computer just crashed building the potential fix.

Ryche666 said:
boot to twrp.
wipe all data
adb push lineageos
reboot to bootloader
boot to twrp
adb push magisk
reboot to system.
right now i am getting FC on Camera APP, X Google, Ok Google, and T mobile something. My computer just crashed building the potential fix.
Click to expand...
Click to collapse
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy

jasonsamms666 said:
glad i did a backup. i just tried to install it normally and it didn't boot. i got ballsy
Click to expand...
Click to collapse
Sorry, i got super anxious myself when i finally got playstore, phone, and text messaging working.
Thus the piss poor thread that i copy and pasted from taimen's lineage.

GohanBurner said:
Is there really no mainstream support for this device? Everything that comes out, no disrespect, is moonshine lol.
Click to expand...
Click to collapse
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.

Ryche666 said:
I heard they are working on taimen first then our phone. For the most part it is all their that it seems. ****ty part is they cannot make it official until they find out why you cannot flash gapps.
So the work around is make it unofficial and build gapps inside.
Click to expand...
Click to collapse
FWIW this is what's been done with the Essential Phone.

razrlover said:
Don't devices that are not officially supported need someone to start the process and possible become a maintainer? I could be mistaken. I myself think moonshine is pretty cool and would love to know how to make it.
Click to expand...
Click to collapse
I was the same way. A **** ton of reading and a lot of PMing. It is pretty simple when you get the hang of it. This early in the game you get to see the codes that attract you to certain roms or kernels.
Right now i just need to make sure it is stable before i work on the kernel or choose what rom i am gonna stick with.

NadavCE said:
FWIW this is what's been done with the Essential Phone.
Click to expand...
Click to collapse
That's what i heard. If i knew that last weekend we would have had that much sooner.

Awesome, glad to see some work

Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666

Chronzy said:
Sideloading it worked. Totally clean install- formatted data (as in typed "yes") and pushed the files like described.
*Wouldn't pick up my 5ghz wireless network during setup, but connected once I was in the os.
LTE seems fine, the screenshot is par for what I get around here. Still setting up and testing, but looking good so far!
Thanks @Ryche666
Click to expand...
Click to collapse
Can you share the complete steps and details on how you flashed it? Thank you!

infamousvincci said:
Can you share the complete steps and details on how you flashed it? Thank you!
Click to expand...
Click to collapse
boot to twrp.
wipe all data
adb sideload lineageos
reboot system.
After first boot then you can flash Magisk for root.

ROM ❯ PIXEL 3a ❯ UNOFFICIAL ❯ ProtonAOSP 11

ProtonAOSP • Pixel 3a
Android 11 ROM​
ProtonAOSP is a minimal custom Android 11 ROM focused on UI/UX and performance, with a touch of privacy.
Instead of customization it is focused on more smoother experience.
Installation
1. Unlock Bootloader
2. fastboot flash boot boot.img
3. Reboot to factory and factory reset
4. adb sideload rom.zip
5. Reboot​Note:- Rom already comes with gapps included so no need to flash them
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Download Here​Known issues
No eSIM support(I plan to add in next build)
Join the Telegram group for support
Kernel source code
ROM source code
This is just a side project, I may or may not maintain it in future.
A huge thanks to @kdrag0n for the amazing rom and the work done on this rom.

Reserved

I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.

96carboard said:
I was just thinking how much I'd love to see this for the 3a.
Couple of things though;
1) Where's the device tree source and vendor blobs?
2) Its unfortunate that you baked in the google crap, one of the great things about custom builds is to get rid of that.
Click to expand...
Click to collapse
1. Soon I'll push source
2. I do have microg build for sargo as it is my main device, but not for bonito, so I did not post here on xda, if you want it join the support link group in the thread. Regarding google crap, for some users flashing gapps externally had less fluid experience so I did it.

I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?

96carboard said:
I hope soon will be very soon, since I'm only interested in building myself anyway.
Have you spoken to @kdrag0n about adding in your source and making this "official"?
Click to expand...
Click to collapse
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.

FoxA said:
Device source
Vendor Source
Note:- I have few extra proprietary stuff added in vendor for Google Fi and stuff to work for users out the box which lineage does not have added in their vendor, so if you really want less vendor blob use lineage vendor. It will work without any issue, I think kdrag0n also uses them.
Regarding official builds, I don't have the same infrastructure as him(reason why I only posted gapps build here, it takes lot of time to maintain both gapps and non gapps build) nor the time to maintain it officially. as said in thread, this is my side project which I thought to share it with community. If things work well in future and I feel like doing it official, I may ask kdrag0n. Also idk if he is accepting new device as he is maintaining all the official devices alone by himself.
Click to expand...
Click to collapse
Thank you very much. I'll give that a go

Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
sorry, I don't have the device anymore.

The link download is not working, please update it

cichy63 said:
Hi, just checking if there is any development planned for this one? Looks to be interesting ROM for daily use.
Click to expand...
Click to collapse
Here's a current source.
I don't know if it's trusted, or who the maintainer of this unofficial build is though. Just found it via telegram.
ProtonAOSP - Browse /ProtonAOSP at SourceForge.net
sourceforge.net

Nice one. It's really handy to be able to revive old, unsupported devices like the Pixel 3a, which is a perfectly usable phone and can be picked up for next to nothing.
Some of us don't care about de-googling our phones and really just want to extend their lifespan with security updates, so having gapps baked in to ProtonOASP is really nice. Especially when we're just trying to help out our non-technical friends get a bit more life out of their old phones. A consistent, familiar user experience is all they really want.
I was wondering though: Does your build (or any build of ProtonOASP) come with verified-boot signatures so that the device's bootloader can be locked down after the ROM is installed, or is CalyxOS the only option for this?
Unfortunately, Calyx are very puritanical when it comes to de-googling, and microG is just a terrible substitute for interacting with Google services. I tried it on the Pixel 3a, and it doesn't even sync the contact list from your Google account. My non-technical friend was not impressed.

GrapheneOS still has builds up for 3a, however new builds were terminated as of February. While it doesn't ship with gCrap preinstalled, installation is trivial as they've built a compatibility layer to make it work correctly (and much MUCH more securely) as user-installed software, which you can install from the program "Apps".

Building LineageOS 18.1 for device that only supports 19.1

I desperately need to get my work profile working on my new OnePlus Nord N200 5G (dre), and I've just discovered that it is apparently impossible to create a new work profile on LineageOS 19.1. It seems, however, that a work profile set up on 18.1 will continue to work after a dirty flash to 19.1. Thus, I'm hoping that I can install 18.1 on my device, setup of the work profile, and immediately dirty flash 19.1. I won't really need a fully functional build of 18.1; just something that will boot up and allow me to create the work profile before I dirty-flash 19.1.
In order to do this, I need to build LineageOS 18.1 for this device. Unfortunately, only 19.1 has ever been supported.
I have a build environment that is currently building 19.1, just as a test. I also have the most recent Android 11 vendor firmware, from which I should be able to extract any required proprietary files.
I'm really missing 2 things:
The list of proprietary files that I should extract from the vendor's firmware. (I have the 19.1 list, but I assume that it won't work.)
What other files do I need to create/edit to add the device to the 18.1 build tree.
Is there a guide somewhere that walks through the process?

Ah, @ipilcher I was hoping someone smarter than me would answer your question. It would do so much for all the Android forks, and Android in general. I've asked the same question to several devs on IRC and they all basically say "no, no easy way to explain it...". My kingdom for a guide that doesn't involve the School of Hard Knocks all the way through.
So in full disclosure, as of today, I haven't managed to build a ROM on an unsupported phone- but I have done full builds from source with LOS and Calyx (with bootloader relocking on the latter) using existing projects.
But... I would assume from others that have gotten the AOSP "Generic Stock Images" to run on various random phones that there isn't really that much you /need/ for what you want to do; you don't need a functioning modem, fingerprint sensor, camera, GPS, notification LED, battery management, etc.
From what I understand, if your vendor follows android specs, all that would be in one of the vendor partitions anyway. From the builds I've done (mostly Motorola and OnePlus devices) the proprietary files (in "stock" LOS) are sourced from a few different places, possibly from generic chipset support (the same tree is used for multiple devices by a manufacturer and/or chipset). One LOS 18.1 build had a whole bunch of (proprietary) files in it that weren't even in the stock rom image! If you are sourcing from stock firmware (OTA off OP site or one of the MSM images here) I'd assume that half the partition is spyware or manufacturer test/calibration tools, and the other half are the drivers you want for a fully functional phone- which, luckily, it seems you can fall short of without failure, so you can probably be pretty lax about picking.
The bootloader chain seems to have a lot of drama between Android 11, 12, and 13 (requiring flashing other partitions outside of the normal system ones)- I've never had a N200 to play with to know if it is high drama, too.
Hey, at least you're using a OnePlus with QC chipset, so EDL can bail you out of pretty much anything you do wrong. I hard-bricked a $500 Pixel and learned how absolutely hideous Google support is- never buying one of those again.
Hope that helps.

SomeRandomGuy said:
Ah, @ipilcher I was hoping someone smarter than me would answer your question. It would do so much for all the Android forks, and Android in general. I've asked the same question to several devs on IRC and they all basically say "no, no easy way to explain it...". My kingdom for a guide that doesn't involve the School of Hard Knocks all the way through.
So in full disclosure, as of today, I haven't managed to build a ROM on an unsupported phone- but I have done full builds from source with LOS and Calyx (with bootloader relocking on the latter) using existing projects.
But... I would assume from others that have gotten the AOSP "Generic Stock Images" to run on various random phones that there isn't really that much you /need/ for what you want to do; you don't need a functioning modem, fingerprint sensor, camera, GPS, notification LED, battery management, etc.
From what I understand, if your vendor follows android specs, all that would be in one of the vendor partitions anyway. From the builds I've done (mostly Motorola and OnePlus devices) the proprietary files (in "stock" LOS) are sourced from a few different places, possibly from generic chipset support (the same tree is used for multiple devices by a manufacturer and/or chipset). One LOS 18.1 build had a whole bunch of (proprietary) files in it that weren't even in the stock rom image! If you are sourcing from stock firmware (OTA off OP site or one of the MSM images here) I'd assume that half the partition is spyware or manufacturer test/calibration tools, and the other half are the drivers you want for a fully functional phone- which, luckily, it seems you can fall short of without failure, so you can probably be pretty lax about picking.
The bootloader chain seems to have a lot of drama between Android 11, 12, and 13 (requiring flashing other partitions outside of the normal system ones)- I've never had a N200 to play with to know if it is high drama, too.
Hey, at least you're using a OnePlus with QC chipset, so EDL can bail you out of pretty much anything you do wrong. I hard-bricked a $500 Pixel and learned how absolutely hideous Google support is- never buying one of those again.
Hope that helps.
Click to expand...
Click to collapse
I just wanted to close this out and thank you for your response.
Fortunately, the issue that was driving me to try to build 18.1 for this device (https://gitlab.com/LineageOS/issues/android/-/issues/4983) has been diagnosed, and I was able to work around it.
Of course, I just realized that my wife's new Moto G 5G is an XT2213-3, not an XT2113-3, so maybe I'll revisit this subject some day.

Welllp... at the risk of being accused of insufficent RTFMing, I did stumble across this article the other day that nicely outlined a few things that I didn't know:
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
NOTE: THIS GUIDE WILL WORK ANY ANDROID DEVICE BUT HAS FEW EXTRA PRE-SUGGESTED LINKS FOR GALAXY ACE PLUS USERS. Special Thanks to - dsixda for his awesome kitchen. Please Hit Thanks button for him. inspired by isidromxz's thread. Please kindly...
forum.xda-developers.com
It isn't exactly "build your own device tree on top of AOSP" which I think is what you wanted and I certainly still do... but it might help someone else who finds /this/ thread with the same question. It also ends with the wonderful quote "This thread is 10 yo. Leave it alone. things have changed" - which is pretty solid advice IMHO.
Ah well, if it wasn't a challenge, there would be no reward, eh?