I just wanted to give you all a heads up that in my quest to fix up twrp/make custom ROMs, I've finally achieved a victory today after a couple weeks of effort. I have successfully compiled the N200 kernel from source. In the near future expect at least one custom kernel (likely to be caf upstreamed), and as of right now I am working on Lineage-18.1 bringup to start with then quickly move onto Android 12 custom ROMs long live the Nord n200!!
On a side note I could use some testers
Nord N200 Testers
Nord N200 Testers
A group for discussing N200 custom software testing. All off topic discussion has been moved to this group: https://t.me/+1qZHIItf9R80MTYx Check pinned messages for important messages and shared/confirmed working files.
t.me
Weird question but is it possible to add a wifi option to not broadcast ssid? Or is that not a kernel thing..
Also I can test but not until the end of next week
cass89 said:
Weird question but is it possible to add a wifi option to not broadcast ssid? Or is that not a kernel thing..
Also I can test but not until the end of next week
Click to expand...
Click to collapse
I'm not a kernel guru, It was luck that I got this kernel to compile lol.
But on a plus note, I did shim TWRP and managed to get it to mount the super.img so we will be able to flash gapps packages and magisk modules n stuff. I think I'm close to getting userdata decrypted as well
that group is very friendly and helpful, working towards development of this device
BTW, im Castiel in the TG
Related
I have the idea for an unified build from quite some time, but only now I'm trying to bring it to life.
Looking at LineageOS github and gerrit you can see that other devices (klte, m8) have the same stupid amount of variants, but they have merged them into one device repo.. So why can't this happen for the Note4?
Following their steps I've created an unified android_device_samsung_trlte (that includes SM-N910F/trltexx, SM-N910G/trltedt, SM-N910T/trltetmo, SM-N910W8/trltecan, SM-N910P/trltespr, SM-N910R4/trlteusc and SM-N910V/trltevzw), this proprietary_vendor_samsung and added this commit to the android_device_samsung_trlte-common that I'm currently using.
For now I'm able to use those repos to build a LineageOS-14.1 build that boots up, but w/o sim and camera being recognized.. For what I've tested (on trltexx) wifi and (strangely) bluetooth are working. Something is probably wrong with specific device blobs not being recognized/used properly.
It needs some work but I think this is a good base to start with.
trltexx/trltedt blobs are from here;
trltetmo/trltecan blobs are from here;
trltespr/trlteusc blobs are from here;
trltevzw is using trltespr blobs for now (there are no guaranteed working blobs repos for it at the moment, the only (WIP) way is to establish which are needed and extract them from hsbadr's builds).
The kernel is the same that I'm using for the not unified builds (android_kernel_samsung_trlte), at the moment testing if the klte's way of using the international variant defconfig works for us too.. other options are to add something like this commit to remove the need of a variant defconfig or merge the different defconfigs into one and use that instead.
Source:
unified_android_device_samsung_trlte
unified_android_device_samsung_trlte-common
unified_proprietary_vendor_samsung
android_kernel_samsung_trlte
I was going to share this anyway, but I'm sharing it now (even if there are still major problems) because I have a very limited free time where I can work on it, so, maybe, someone of you will join/fork/clone this project and help me out, finalizing it earlier and better (the support of experienced developers is needed and much appreciated).
I'm now going to mention the SeniorMembers/RecognizedContributors/RecognizedDevelopers that, maybe, have interest in this project.
@fattire @hsbadr @SaintZ93 @SferaDev @TheBr0ken @ZION959
If you get it to work, @_mone, I'll switch my daily builds to this unified one.
On a related matter, there seems to be a typo in the name of one of your repos: unified_andorid_device_samsung_trlte.
Let me also add @lilferraro to the list of devs, as I use his device tree to build for trltespr.
I built this and it boots, with the same issues you have (no SIM detected, camera is busted). Took a bunch of of logs. Getprop shows ro.build.fingerprint is trltetmo (which is right), ro.bootimage.build.fingerprint is trlte. Wifi and bluetooth are working. Mediaserver/libcameraservice service crashes repeatedly. I agree with you that having a unified tree for the entire Note 4 line is the way to go. I tried manually copying the blobs from /system/blobs/tmo/ to /system/lib and /system/vendor/lib but it didn't help.
what proprietary blobs did you use for sprint?
All device trees for the note 4 pie builds are up at
GitHub.com/tripLr-dev
User forum at Telegram
https://t.me/triplr_dev_users
Thanks to @_mone
And @ripee
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
tigerpro357 said:
I will do a test build of my Ubuntu Touch port using this unified repo and report back if anyone is interested. My port still needs a couple things to work but the stuff that works now should be enough to give me a good idea if it will work or not.
Click to expand...
Click to collapse
Let us know what you need
Source code
GitHub.com/triplr-dev
Contact me on telegram t.me/telegram to get you in touch with testers and developers. .
I am EXTREMELY interested in a touch port.
Thanks
Also GitHub.com/underscoremone for all the older stuff
I actually have my work on github already, I am also on telegram in the ubports groups, and if you would like to help my repo is probably the best place to start (unless you prefer duplicating work) I only have sensors and the stylus left for hardware (both of which I have been trying to get working) the stylus is an issue on the ubports side but I dont understand the code enough for mir. I haven't had a chance to test the unified repo yet, but I will once I have a few minutes to actually do it.
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
tripLr said:
I wonder how it work to create xda threads for Ubuntu touch, since they seem to have their own forums.
I think adding Ubuntu touch to xda would be an additional resource for users and developers.
Click to expand...
Click to collapse
I agree, as all I really see on xda as far as Ubuntu Touch goes is prebuilt downloads which is good for letting people try it, but when I started I initially looked into xda but found no help. I do hope to see that change in the future though
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
doubledragon5 said:
Nice to see someone actually wanting to still develop for this device.. I love this Note4 still.
Click to expand...
Click to collapse
Same here
We have several developers for note 4 snapdragon and exynos
T.me/triplr_dev_users
See you there
Roms
Tiny.cc/triplr
Tiny.cc/ripee
And many links in XDA for ROM threads
Post comments in XDA, and bug reports and logs in telegram
Android 10 in progress
Thanks @_mone
The lineage-17.1 thread is up!
[ROM][UNOFFICIAL][10] LineageOS 17.1 [tblte][trlte][trlteduos]
If you don't mind not having a working fingerprint sensor, or audio through the headphone jack, then Q is stable enough for daily use. As always when coming from an older rom version, it is highly recommended not to waste your time dirty flashing and just clean flash.
Q is still a work in progress, so I will still be releasing Pie builds, though maybe not as often. As in years past, once the Q bugs have been fixed up to the current Pie level, I will post about when my last Pie build will be. I will upload it to the Downloads tab located at the top of each page of this thread, and link it in the OP.
This is unofficial lineageos 16 for Motorola Clark. It is only compatible with nougat firmware - you must have the nougat bootloader and modem flashed on your device.
Tons of thanks to hashbang for all of his work
Kernel Source-
https://github.com/randomblame/android_kernel_motorola_msm8992
Device tree-
https://github.com/randomblame/android_device_motorola_clark
Current status of rom-
Daily Driver
Broken-
Camera post processing- rotation is not accounted for in hal with latest round of hacks credit to AgathosAnthropos for fixing image capture by disabling the calls to pp, hold device in landscape for photos
Tethering - it works but device will soft reboot when tethering stops
Dual sim variants are NOT supported! I do not have the hardware to test and fix at this time - bugreports appreciated
Working - everything else?
Try it yourself (Requires Nougat Firmware and as always wipe data+cache)
Latest Releases:
1/12/2020 https://www.androidfilehost.com/?fid=4349826312261700035
8/1/2019 https://www.androidfilehost.com/?fid=6006931924117928331
Don't forget to grab a compatible version of gapps for 9.0
https://opengapps.org
Once again this rom REQUIRES that the stock nougat firmware was properly flashed to work correctly... It will check before installation that you have the correct modem version installed.
*If your radio does not work you may have the wrong modem
*If you can not switch lockscreen to pin or pattern you may have the wrong modem.
*Modem flashes fail quietly sometimes please make sure you have properly flashed it before reporting issues.
Great! [emoji6]
Enviado desde mi Nexus 5X mediante Tapatalk
I'll be happy to test once there is a working rom
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Can't wait to see more from this
We wait impatiently.
Spent a couple more hours going through init narrowing it down failure happens just before zygote startsI currently have my pure propped up in charging position so I can work more on it it's had a hard life
Thank You so much
randomblame said:
I've been updating op, it seems to just be getting shorter as I fix things. The rom now compiles with default manifest only needs device tree and kernel source now. something is failing quietly and preventing boot. I'm just working the problem slowly getting it sorted out.
Click to expand...
Click to collapse
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Moto X Pure XT1575 said:
I have been searching and search for lineage OS roms for my XT1575 but the bootloader is Ax052 which is not supported by 14.1 Lineage. I Hope you find a fix for this.
Click to expand...
Click to collapse
Hi, I have the Lineague 14.2 installed. What I did to eliminate the bootloader check was to edit the uptader-script
Fixing error caused by missing taskstats kernel feature
Hi randomblame,
A quick review please, could you tell us the intended purpose of your project.
Meaning like I'm thinking it's for a "Moto X Pure 2015 (clark)" device isn't it?
Would that be for everyone on this XT1575 device which has upgraded to a stock Nougat kernel and modem?
Or could/would others benefit from it as well with your research here - other moto's?
Any and all answers - thoughts are welcome in understanding the project...
Thanks for the lady power on XDA,
RIF
This device can have a new future. Think about it !
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
randomblame said:
I will look into bootloader incompatibility once I get it running seems like it shouldn't be a big deal. I'm also toying with the idea of a new kernel 3.18 seems like low hanging fruit considering Motorola was kind enough to give us good searchable git history on GitHub of both kernels and the 3.18 source for the Moto z seems to have most of the msm8992 support still. My next step is going to be a new device tree starting as bare bones as possible and populating it properly to figure out this issue. I'll throw up a PayPal link again later a less broken device would be helpful USB port is bad and this is probably the fourth screen I've installed on it but touch only works when it feels like it lol
Click to expand...
Click to collapse
I'm trying to follow along with your posts best as is possible for me - but, so sorry I and as well many others are lame to understand the under-the-hood workings of Android.
Are you saying in such a way that the Moto Pure XT1575, will maybe and with your research efforts move forward to a true PIE OS possibly?
Maybe I'm reading to much into your words.
But, as I follow your posts, you'll advance us Pure device owners beyond the Nougat kernel - or at least try too?
Or yet with your efforts will this yield something like HashBang did for the XT1575 device when a Nougat OS wasn't even a thought of possibility from Motorola for us.
Back then, HashBang had worked the Nougat OS on the Marshmallow kernel and modem - I'm very green to all of this - but that's what I understood.
Still that's good none the less if that will come here from you with PIE on Nougat internals...
Beings Motorola support is dead for our device for anything future of an OS update - not to mention security patches.
If you would spell it out better as any interested XT1575 owners now could grasp the concept here in your efforts - create a buzz for a greater community following. More MXP owners to jump on board as gained support from well wishers.
Is it to early yet for that? Is there a fear that someone could steal it out from under you? Unexpected negativity, or is it just the way you wish to present this to us for the present.
I'm still going to watch and support this project with high hopes no matter what may come in the end...
Could you benefit knowledge from a LineageOS 16 for Moto Z. download?
https://www.cyanogenmods.org/forums/topic/download-moto-z-lineage-os-16-android-9/
For people like me,
Device Tree = https://source.android.com/devices/architecture/dto
and on XDA
https://forum.xda-developers.com/android/software/guide-how-to-make-device-tree-phone-t3698419
As for any active developers still left for the XT1575 a big thank you to you all, seems to me like a daunting task to crawl inside of android moreless understand things once your there...
Kernels are only loosly linked to Android versions, Google maintains the Android-common kernel repos which are usually quite far behind mainline Linux, and caf who maintains Qualcomm specific kernels are further behind in general. Literallyany feature required by Android can be backported to an old kernel I'm sure 2.6.27 could run pie but it would need so many patches it would be an unrecognizable mess. It will become progressively more of a nuisance as time goes on to keep patching up 3.10 Pie "requires" 4.4 for new devices but only needs kernel features from 3.18 which I've backported to 3.10. with each new version of Android more assumptions are made about how modern the devices kernel is and what features it has so moving to a newer kernel would be nice and like I said 3.18 seems doable but it will still be quite a bit of work.
Thank you @randomblame I was able to grasp most of that...
Maybe it's too early but, how does Googles Android security patches figure into this - if they are possible to bring us forth from Oct 2017?
Remembering I'm a laymen to the nuts and bolts of android.
I understand your post #16 - Super !
Security patch version is irrelevant when you are building from the latest source
Obnoxiously after a few builds the dedicated 250gb SSD is full and I have to make clean which takes ages, I nooped every thing but the basics didn't include telephony or wifi, ril, audio, Bluetooth GPS nfc etc and left it to build overnight will test after work trying to narrow down the problem
Surface flinger is the culprit
I have the device laying around and getting no use. Will sure donate some $$$. Seeing a los16 with all working hardware would be great.
Only got a couple hours to work on it this weekend, there is an issue where /system/vendor is not symlinked to /vendor early enough and calls for things in /vendor fail thus the issue, since we don't have a physical /vendor partition it can not be mounted immediately via the kernel. Tis annoying. I can change the calls to /system/vendor or maybe make it symlinked earlier when I get a chance
As you all V20 owners know, there's only one kernel available for Rooted Stock Oreo ROM and it is MK2000. However it's a good kernel and its developer has put a great effort on it but unfortunately it doesn't function properly on H990DS variant. Some problems like intensive lags and battery draining are two major examples.
If you remember we had a good DOTS kernel in nougat. If someone could fork it for Oreo it would be great as well.
Anyways, here's what we need:
[*]Stock kernel based on H990ds Oreo sources (20a or 20b)
[*]Dirty Santa fixes applied (You can read about this in H990* root thread under TECHNICAL DISCUSSION section)
[*]RCTD, Triton and whatever related removed
[*]"ForceEncryption" and "dm(avb)verity" removed
[*]KCAL, EXFAT and USB Quick Charge support
[*]More CPU governors (We will talk about this in the group)
[*]Overclocked
[*]Make the project Open Source
If you think you can do something, PM me! I'll send you additional information required.
Also I'll give you a link for a Telegram group where you can share what you have and it can be tested out.
Anyone interested in testing potential builds, also contact me for the Telegram link.
The current list of supporters:
----------------------------------------------------
$15 -- @Daved+
$15 -- @mikekote666
$5 -- @Chucknorris1975
$10 -- @aygross1929
$5 -- Uditha
$5 -- @rivaldo21
$5 -- @giriraj121
$5 -- Taufik Kusuma
$15 -- @tapir1505
$10 -- @albaniax
$10 -- @henrylar
$10 -- @DrugsBunny
$10 -- @lefffen1
$5 -- @bronze_eye
$5 -- @Blissv
$20 -- @Qron
$20 -- @NoName!
----------------------------------------------------
Total: $170
Due to some problems I can't manage this thread soon enough, so please contact @Daved+ for more information.
He will also collect the bounties and release the kernel when ready. Stay tuned!!!
Last update: 2020-3-26 /// 16:16 (GMT +3:30)
After the H990DS variant, we can ask for the other variants if people support it!
So we are looking for money to pay a dev to make a good H990DS kernel (And after that for more models). This is important! Thanks for your collaboration.
Good work creating the thread.
Hope more people jump in
Thanks for pushing this, let's get some more life outta this phone and make rooted oreo usable.
Commenting as a reminder to add to donation list
how do I financially support?
henrylar said:
how do I financially support?
Click to expand...
Click to collapse
Please write the amount of your donation, you can transfer the money when the stable release of the kernel will be ready.
10$
10$
$10
reza_xdv said:
We want the kernel to populate custom NTCODE (Being able to change ntcode for region changes)
Click to expand...
Click to collapse
Hey there
What exactly does this mean? Aren't you able to change the NT-code as it is?
I've actually been wanting to change the region of one of my G5's, but simply changing the code did not do the trick.
I used the hidden menu method btw, where you can also change mac address IIRC.
I also fiddled with the two partitions; cust and OP. Doesn't seem to be it either. Probably something needed to be edited in misc partition or something as well.
And BTW, I'm not offering to make this new stock kernel. Though I did just now re-upload the v2.2 kernel, here:https://www.androidfilehost.com/?w=files&flid=297449
With some fixes and stuff. Not saying it's gonna fix 990ds problems, but at least it's out there for V20 users to be aware.
askermk2000 said:
Hey there
What exactly does this mean? Aren't you able to change the NT-code as it is?
I've actually been wanting to change the region of one of my G5's, but simply changing the code did not do the trick.
I used the hidden menu method btw, where you can also change mac address IIRC.
I also fiddled with the two partitions; cust and OP. Doesn't seem to be it either. Probably something needed to be edited in misc partition or something as well.
And BTW, I'm not offering to make this new stock kernel. Though I did just now re-upload the v2.2 kernel, here:https://www.androidfilehost.com/?w=files&flid=297449
With some fixes and stuff. Not saying it's gonna fix 990ds problems, but at least it's out there for V20 users to be aware.
Click to expand...
Click to collapse
Hey,
the AutoMID option in h990ds hidden menu doesn't allow to modify anything. OP partition in v20 is a complete waste of space and full of junk stuff. We have edited the ntcode in misc by hex editor and have addressed the custom ntcode in cust to use the desired path, but the phone reads the ntcode from the modem as we can still see the factory ntcode in the hidden menu (SVC, Version Info). If we populate the custom ntcode at the kernel level (smem) maybe we can overcome this obstacle. Read this post: https://forum.xda-developers.com/v20/how-to/bounty-thread-lg-v20-root-h990ds-t3493062/post72323004
And thanks for the Re-uploaded kernel. It's more stable than the previous stable 2.2 build.
Personally I was using 2.2 beta 26 as it was working better than other builds, but I can confirm that the new re-uploaded build is slightly better than beta 26. Benchmarks: Antutu -> 2.2 beta 26 (156K) --- 2.2 Stable Re-uploaded (161K)
We would greatly appreciate if you could help us to fix some issues regarding the development of the stock kernel as you know how to deal with the dirty santa stuff. (We've found out that it's causing more issues than expected) If you're willing to guide us and tell us the steps I can send you the Telegram kernel development group link.
A noob question - to update the kernel, I just need to flash it followed by magisk, right?
henrylar said:
A noob question - to update the kernel, I just need to flash it followed by magisk, right?
Click to expand...
Click to collapse
If you're upgrading the current kernel just dirty flashing the new version over the old version followed by magisk is enough.
But if wanna flash a different kernel, you should first flash a clean bootimage then flash the custom kernel followed by magisk.
Question- how much do we need to raise to make this happen?
Additionally, can we specify that this not be specific to a single variant? You might get more donors.
(btw there's already enough bounty to send a dev a used unit to experiment with too! LOL)
Dishe said:
Question- how much do we need to raise to make this happen?
Additionally, can we specify that this not be specific to a single variant? You might get more donors.
(btw there's already enough bounty to send a dev a used unit to experiment with too! LOL)
Click to expand...
Click to collapse
We need to get something working first, then we will open the game to the other variants but we need help raising money to get this done, so if you care about a new kernel for your v20 please help us with the money now.
We have about $130 now. But it isn't enough for an expert dev to make this happen.
Currently we are dealing with touchscreen issue. LG sources are trash and a real dev knows how to deal with them.
i95swervin said:
Curious is anyone on a h990 has tried alpha kernel from my rom project. If you have let me know what was working and what wasnt.
Also why not mk2k kernel ? The dev has done a lot of work for this device.
Click to expand...
Click to collapse
No we haven't tried that kernel. Kindly send me the boot image so I can test it.
About the mk kernel. It's the only kernel available for us, but we have some problems with it like general lagging, apps getting killed and memory problems. And these problems are more severe for h990ds variant.
I the end, if you can help us with kernel development (building or just helping to fix few issues), I can send you the group link.
UPDATE:
I flashed the h910 stock kernel inside the AO rom.
It has static screen issue. However I fixed it by covering the proximity sensor for some seconds. (However this trick won't work on h990ds kernels.)
Sims do not being read.
The UI was smoother comparing to MK kernel but it started lagging after a few minutes.
I can tell stuff were crashing in the background.
Hi Guys,
I am ready to become beta tester for this kernel. I have this device with root and its H990DS India version. I know bit about android and give you crash reports. Please post me link of telegram. I have already replaced its thermal paste to make it cooler and this mod really worked as now device lot better than earlier hot pot condition. Even with mk2000 kernel (great respect for developer) its standby battery sucks. I have Lenovo Z2 plus which also does have same Qc 820 and poor software but due to developer efforts now it is smooth as butter. Hope this kernel solves most of the problems and I am ready to dive into depths of kernel development to save this last of its kind removable battery super phone. Kudos to all developers.
I m also ready to become a tester
Count me in. I'll donate $20.
Hello, So, I used to own a OnePlus 5t and I made the jump to Nord 2 because my 5t was not working.
Honestly, the stock rom is a complete disappointment. I can't use half of the apps without giving them permissions to location, contacts, phone, etc.
I mean why does camera need my location? The sad part is it won't work without it which is complete BS. Same goes for gestures and other features. like Why do these apps needs contact and phone access? I disabled most of the apps from adb and I am using Gcam for camera.
Sorry for the rant. Anyways, does anyone have any idea by when can we expect to have a custom rom for this phone?
There is some problem with kernel and oneplus just don't care about it. I think thats main problem right now. You can try GSI but there are some bugs.
USB make device panic on OnePlus Nord 2 5G OSS kernel · Issue #2 · OnePlusOSS/android_kernel_oneplus_mt6893
Hello, I noticied that USB were making kernel panic with the current source code released by OnePlus, it would be really usefull if that's fixed soon. Also, I request for MediaTek kernel modules an...
github.com
Until Oneplus don't release the full firmware it'll be difficult.
I've contacted the support though, and they say it will be published "soon"
Is this because its harder to make a custom rom for a mediatek soc? (or because mediatek wont release the firmware?)
8vasa8 said:
There is some problem with kernel and oneplus just don't care about it. I think thats main problem right now. You can try GSI but there are some bugs.
USB make device panic on OnePlus Nord 2 5G OSS kernel · Issue #2 · OnePlusOSS/android_kernel_oneplus_mt6893
Hello, I noticied that USB were making kernel panic with the current source code released by OnePlus, it would be really usefull if that's fixed soon. Also, I request for MediaTek kernel modules an...
github.com
Click to expand...
Click to collapse
Elixir Rom is there for OnePlus Nord 2
"Just flash a GSI and be done with it bro" comments will be ignored.
The BE2028 is the T-mobile variant of the Nord N10 5G and before I do any thing on this phone, I want to be sure of a few things.
I want to be able to get back to EDL mode should something go wrong and I want to be able to use a good boot.img and if there are any decent boot.img file(s) for this phone.
I realize that this isn't a very popular phone and I plan on compiling a few custom roms for this phone which i'm in the process now. But is anyone else working on the BE2028 variant of this phone? When I fan thru this forum, mostly what I see is the other variants and not much is spent on the BE2028 so that's where I'd like to help and if anyone else would like to help would be great and if you want we can stay in contact on Discord or telegram or whatever.
If anyone has any experience with this phone, please let me know.
Also, is there a good way to make clean backups of the partition tables, partitions and data as well as ny hard linked code if something goes squirrely like IMEI lost or whatever. I believe once I get a good custom rom built for this phone it can be a very nice budget phone.
I'd also like to remove the tmobile branding from the rom as well which is why I want to get a good feel for this. I've built custom roms for my Xiaomi and Samsung Note 2 but I feel this is going to require a bunch more work than just building a ROM out.
OnePlus Nord N10
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
I've written to OnePlus support in regards to debranding this phone and if there is an official way of putting a global OS on here instead of a TMobile only, since I own the phone, I want to use my phone.