Database Users

CyanogenMod 7.0 for eLocity ?

Check this out !
Anyone in relation with those guys ? How could we get out tablet to support it ?
Pretty amazing !
Link here : http://www.engadget.com/2011/04/11/cyanogenmod-7-0-is-now-final-ready-for-your-consumption/
I know Dexter is the eLocity king atm, but it must be tirering to be a one man army !

Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...

5[Strogino] said:
Again and again and again...
Without kernel source we unable to do custom ROMs. Only modifications over stock.
Not a development topic...
Click to expand...
Click to collapse
maybe I should put my old signature back on? lol

the Synergy Bluetooth implementation is nowhere close to standard implementation, so although we might get a CM6/7 on this tablet, even without 2.6.36.3 kernel maybe, we still need more coding done to support the BT implemention otherwise the port will be without Bluetooth support..
I got, as example, the FolioMod ported easily, but Bluetooth did not work, same with the Blur port.. and since our kernel has no real loopdevice or devicemapper support and modules needs to be specifically compiled with the revisions used in our kernel, the "move2sd" function is also missing here, and other nice function as optimized filesystems using loopdevice for faster database updates etc..
it will be hard! , and the drivers without any source, makes its practically impossible to do a kernel based on nvidia's git tree alone..

Moved to proper forum

Kernel available??
Mr. Clown said:
Moved to proper forum
Click to expand...
Click to collapse
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5

ming_a said:
See on http://www.elocitynow.com/downloads/open-source.tar
and chacksum http://www.elocitynow.com/downloads/.checksum.md5
Click to expand...
Click to collapse
Yep. Did you find it here:
http://www.elocitynow.com/developers.shtml
Billy

[KERNEL]Nexus 7 Compiled from Kernel.org Source

Hi All!
I have been trying to compile a Kernel for Android from Kernel.org Source. Avidly awaiting a Nexus 7 I got straight to work. I have created a zImage. I have been trying to document the process but rather than type it again I have been doing it here. If someone with a Nexus 7 wants to give this a go I would be very much grateful. This is an ongoing process. I have included the file and necessary instructions here...
It looks like I cant post external URL's .... YET! If you want to post here or PM Me I will send you the links.
If someone could test this for me it would be greatly appreciated.
Thanks

I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)

Bogdacutu said:
I'd like to help. How do you intend to test the kernel though? (since I'm not sure if it would work in Android, but of course you're probably more experienced than me)
Click to expand...
Click to collapse
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.

JamesSawyer said:
Basically people flash it and then test it. People can provide their own benchmarks if they want. Against their previous Kernel versions etc. I have a sort of active thread on the Neowin Forums about this but I cant post links yet on XDA. I also got my VPS setup today to build and host the files.
Click to expand...
Click to collapse
Okay then, I can do that. I assume you can PM links?

You might be able to state the URL address in your post for your kernel. I'd test it and I guess others may also.

Hi All,
I have someone from Neowin who is going to post the links for me.
At the moment my guide and files are all disjointed I am trying to organize it better.

Great idea! I'll look around your thread @neowin.
What supposedly differences are there from the native android kernel and one compiled using the code from kernel.org?

Personally I just like playing with Bleeding Edge code. You would get all the latest features from source as well as bug fixes most end users wouldn't see. Performance is to be determined, Battery life and CPU performance etc. Its also quite a little Niche that I like been a part of if it all works and comes off.

The kernel you're compiling most likely won't work if you don't even have the machine definitions nor the drivers for your nexus (seeing that you have taken the source directly from kernel.org)
The best of testing a new version would be to backport it but doing so takes an incredible amount of time and considerable skills.
Envoyé de mon Nexus 7 en utilisant Tapatalk

I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.

JamesSawyer said:
I have used the Prebuilt ToolChain from git and also the defconfig to build the kernel from Google. I have created a boot.img this should make it easier. I am just waiting a Nexus 7 myself to test this anyway.
Click to expand...
Click to collapse
You need to have proper board files, proper drivers (device-specific ones) and tons more. I don't think it will work without those. Then chances are it's not going to compile properly; it will throw tons of errors. After you get it to compile, you have to get it to boot. After you get it to boot, you have to get it fully-functional (not necessary if this is a test kernel). So unless you have gone through it all, I don't think it'll work.
BUT I may be wrong.

It compiles no problem, That's what I am wanting people to test :good:

JamesSawyer said:
It compiles no problem, That's what I am wanting people to test :good:
Click to expand...
Click to collapse
Ready to test! Check that neowin thread, but all the links I've tried lead to 404

vrutkovs said:
Ready to test! Check that neowin thread, but all the links I've tried lead to 404
Click to expand...
Click to collapse
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.

JamesSawyer said:
Hi!
Well I have not been on this for a few days however I set up a quick and dirty VPS. Looks like the process fell over. I have restarted it and published any files people might find useful on here.
http://svm24652.vps.tagadab.com:8000/
All actual builds are in the build folder.
Click to expand...
Click to collapse
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha

poondog said:
wow you are building 3.13 kernel?! Impressive if it boots
I have a patched 3.4.76 AOSP kernel in my repo thats all hahaha
Click to expand...
Click to collapse
I am trying to ha! :highfive:

Do you have your 3.4 Kernel? Do you have notes how you built it?
Edit: Updated to include 3.13rc8

I have done some more merging from latest Mainline and Flo Kernel from Google. Its building as we speak. Time to head to Tesco.
Hopefully what I have done will get rid of a compile time error I was having.
Has anyone got the ones I made previous to boot. I have my Nexus 7 on the way as of today so I will be testing it on my own sooooon!! :good:

http://linux.jamessawyer.co.uk:8000/
A bit more easy to remember. There are some test builds and experimental stuff on there too. I might do requests if anyone wants me to make a build for their device let me know. Rather than the Nexus 7 2013. I only did that because thats the device I am getting

The link is down

LG uploaded V500 kitkat kernel source today!

https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=lgv500
Is where you can get it (start your downloading now...)
the strange thing is they appear to have two uploads for kitkat...
Sent from my LG-V500 using XDA Premium HD app

Yay! What does it mean for the simple user? Better roms?
Sent from my iPhone using Tapatalk

All I really want is gamma correction and maybe overclocking and U/V.

This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M

muiriddin said:
This means that anyone interested in building a replacement kernel for the LG stock 4.4.2 release has a blueprint to start from. I know of two kernels that have been released for 4.2.2 stock, this release means that we may see updates of these projects to 4.4.2.
I may try and restart my own efforts in this area as well depending upon time and what kind of problems I find in the 4.4.2 US release.
M
Click to expand...
Click to collapse
The first and most obvious is the gamma set at 2.05 roughly. If you set it to 2.2 - 2.3, that would already be a big plus.

The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk

id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Good to hear that someone else contacted them as well. I have been impressed with their open source group responding as quickly as they did. They definitely respond better than several other companies when facing these requests!

:good::good: I would pay anybody to incorporate or activate the OTG+Charging in this Kernel. :good::good: :fingers-crossed:

id10terror said:
The source uploaded by LG didn't include the kernel source so I contacted their open source division and they've now uploaded a proper kernel source. I'm travelling for work now, but will take a look at it when I get back home next week and get something compiled.
G Pad(V500)_Android_KitKat_LGV500_v20b_Kernel
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.

LBJM said:
When if get the chance can you compare the 18a kernel to the 20b one? I like the settings the 18a kernel, the lower brightness levels are setup in a way that makes it great for night time. I have the 18a kernel running on the 20b build but after the screen is locked it and turned back on it changes to levels of the 20b kernel, but retains the gamma level. I could attach a flashable zip with the 18a kernel if you need it.
Click to expand...
Click to collapse
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think

I compiled a kernel using the source provided by LG, but for some reason, it doesn't boot.
I keep getting this error:
Code:
Secure booting error
Cause: boot certification verify
I noticed that the resulting "boot.emmc.win" is a lot smaller than the original boot.emmc.win (~10 MB compared to 24MB)
Another interesting thing is that if I uncompress the original 24 MB boot.emmc.win using the command "unmkbootimg -i boot.emmc.win", I get two files: kernel (7.5 MB) and ramdisk.cpio.gz (2.6 MB). If I rebuild the boot.emmc.win using these exact two files, I get an 11MB boot.emmc.win, but this one DOES boot.
It probably has something to do with the locked bootloader and the loki exploit.
Can anyone help me get to the bottom of this? I really want to solve the gamma issue.

Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.

Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk

ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Canadoc said:
Can you look at the 18 Rom kernel and see what has changed?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Panel is very close to correct gamma when using default linear qlut, instead of MSM_MIPI_LGIT_VIDEO_WUXGA_PT_PANEL qlut.

I would definitely take a look at the 50018A kernel if someone can provide the source. I wasn't able to find it.

gin_silver said:
Hi, I am quite a newbie. Just wondering what is the use of the kernels? Can we just flash it on custom roms like the kitkats ones done by _infected. AOKP or the Cynogenmod for the GPAD? The AOKP and the Cynogen are smooth but few features like Autorotate doesn't work and there is no gamma correction i think
Click to expand...
Click to collapse
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.

LBJM said:
The kernel is what drives the Rom. Without the kernel sources improvements to a device are hard to make. It's AOSP ( Android Open Source Project) not AOKP.
Click to expand...
Click to collapse
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996

gin_silver said:
Thanks. Hopefully we will have some great modified kernels for the kitkat version
Btw i was referring to AOKP (K for Kang) in this thread http://forum.xda-developers.com/showthread.php?t=2710996
Click to expand...
Click to collapse
Good to know.

20d source released
I do not know if anyone will find this of use, but they have now posted the 20d kernel source (and some other stuff).
https://www.lg.com/global/support/opensource/opensourceList?types=ALL&search=v500

ruxandy said:
Well, as I suspected, it was because of the locked bootloader, but using the loki_tool, I was able to bypass the bootloader check.
So I now have a working, self-compiled 4.4.2 kernel (using the eabi-4.7) , based on LG's kernel source.
Unfortunatelly, gamma is still the same (about 2 - 2.1). Need to figure out how to modify it.
If someone can and wants to help, I'd greatly appreciate it.
Click to expand...
Click to collapse
Hello ruxandy,
Can you explain in few words how did you manage to push the kernel to your v500?
Here is my story:
I downloaded the V500 Lollipop kernel because I wanted to compile .ko loadable modules and drivers to support RTL2832U DVB USB dongle. I successfully compiled those modules, rooted the tabled and tried to insmod them. But it failed because the modules did not find some kernel APIs.
Then I decided to build the kernel with built-in those drivers and I did it successfully, the problem now is what to do with zImage. I read there are two roads the one building own KDZ file seems very complicated and not sure if really possible. The other seems to be to extract the boot.emmc.win file using TWRP. So I downgraded the V500 bootloader from LT to KK and installed TWRT using this http://forum.xda-developers.com/lg-g-pad-83/help/v500-how-to-install-twrp-stock-lp-t3165846 but after reboot got the secure boot error you did.
So again - how to use self built zImage and is this possible for KitKat only, since installing TWRP with Lollipop does not seem possible so far?

[HELP] Porting G2's L to G1 [KERNEL]

Yo peeps,
Code:
[COLOR="Red"]For people who say I will wait for official update STAY OUT![/COLOR]
So i was trying to port the G2's Lollipop update to G1. Many of you may think itz quite useless, well i just decided to try because i am a big dev here to compile AOSP or CM12 roms without a proper device tree. So while we wait for Official Update or until CM/AOSP becomes stable i thought maybe i could try porting. So i managed to get the system and boot.img made a zip and now the problem seems with the kernel. I get a fall through to fastboot mode when i use their kernel and when i use ours it gets stuck on bootlogo. Both the kernels are of 3.4.42 and i am not good at kernels like the way i am at kang so if someone could help me with the kernel part maybe we can get L earlier.
This thread is for only people who can encourage and try helping! Others please excuse.
I unpacked both the boot.img made a zip of it and uploaded so that it would be easier for people to help. I dont mind testing it numerous times. Willing to listen and try anything and everything that can make it boot. So here are the kernels.
Hope to find help!
 @VictoriousShooter
 @rr46000
 @S0bes
 @yajnab​

I think it is impossible without kernel source... This way you can play with Ramdisk only. Moto g2 has little bit different hw..

only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.

AgentChaos said:
only difference is screen size and camera, the processor, graphics chip, ram, battery and sensors are the same. so it is possible to port g2 update to g1.
Click to expand...
Click to collapse
The ROM itself-yes
Kernel-no.

I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...

S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken

Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?

Justice™ said:
Try using a CWM flashable version of the G2 rom along with the CM12 kernel? You might be able to get some kind of result from it?
Click to expand...
Click to collapse
cm kernels wouldnt work on stock roms bro.. tried it.
fabus said:
I have flashed ZTE warp cm10 on ZTE v9a with kernel built by myself and it was also working... But with warp kernel there was no chance to boot v9 device up.
I think with flashing g2 lollipop over g1 shouldn't brake your phone permanently, unless you are not flashing modern etc. (just flashing system and kernel). But I cannot promise nothing will be broken
Click to expand...
Click to collapse
S0bes said:
I know almost nothing about kernels and all related with it things and even do not know why I was mentioned by OP
But I have a question. Can we just flash firmware from G2? Can it brick our device completely in a worse way?
Why am I saying such a bool****? Read first line in that post again
Never the less I remember guys who flashed android 2.3 on samsung galaxy gio from galaxy ace and phone booted and even hadn't critical bugs...
Click to expand...
Click to collapse
@S0bes i thought you may know something so kinda tagged u bro btw i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.

yeshwanthvshenoy said:
i tried flashing g2's stock firmware image it doesnt brick or anything but since they have a different kernel it still goes to fall through to fastboot mode even on g2's stock roms. the main difference is that 5.0 uses ART and ours DALVIK and hence i believe that what the issue.
Click to expand...
Click to collapse
I do not believe so. Neither Android 4.4.4 Moto G LTE nor, Moto G (2014) Kernels (or ROMs) boot on Moto G (2013.)

@yeshwanthvshenoy I know you stated you are a big dev, but since you are, you already know kernels can't be ported from an image. You need the source code. Unless you have a magical way of changing code without needing to decompile.
Still... if you are having fin making zips, go ahead, don't let my words discourage you. But... this is a dead end.

Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]

reversegear said:
Agreed with @fermasia
if porting kernel without source was such an easy task by this time we had so many kernels
Only way is directly flash 2nd gen kernels to try our luck if some things work
All the best [emoji4]
Click to expand...
Click to collapse
I dont think there will be any luck since G 2014 has a different MSM board and that has to do with the result you will get. So if you manually flash XT1064 firmware on an XT1032 just expect a beautiful soft brick in the best of the cases... Just wait for official OTA, there are just days left for it!!! Next week we will se some news.

for this you need a new kernel for G1, which we dont have. (and even if we had it then we had the ROM too)
you will have to use the old kernel with the new ROM. which will obviously create tons of error.
have you tried CM12 kernel with the ROM?

For the kernel, try following and check if there is some progress.
Decompile both the kernels with dsixdia kitchen. You will get ramdisk and Zimage for each kernel. Try following combination.
4.4.4 Zimage (G1) + 5.0 Ramdisk (G2) + Modules (G1)
If no, try using init.rc of G1 and give another try.

I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...

Somcom3X said:
I'm not planning on helping you do this, but the g2 and g1 use the same kernel. You only have to enable certain things in the defconfigs...
Click to expand...
Click to collapse
They are using the kernel source, but even kernel source for g2 hasn't been released so far...

fabus said:
They are using the kernel source, but even kernel source for g2 hasn't been released so far...
Click to expand...
Click to collapse
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.

Good luck on the kernel. Though I highly suspect that Motorola will give us Lollipop on the Moto G before anyone is able to come up with a working port.

Somcom3X said:
You don't really need it, decompile the boot.img and replace the zimage inside with a compiled one.
I don't recommend doing this. Porting in this case is pointless.
By the way, kernel source was released a while ago.
Click to expand...
Click to collapse
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.

Get the basic source of the G1. Match the changes made to G2 for the L. Best to getthe old G1 kernel source and modify the things needed for the L. Test and Go.
Unless its creating changes in filesystem its good to play with.
---------- Post added at 03:13 PM ---------- Previous post was at 03:13 PM ----------
yeshwanthvshenoy said:
thanks for the info and help all of u are extending i know maybe this may not work out but itz just a try. and @Somcom3X can u please a little more of the above statements u said about changing defconfigs and few other stuff. Should i use G2's zimage and G1's ramdisk or any file that u think would make it boot? Can u specify the file name if so.
Click to expand...
Click to collapse
G2 device board name differs. It will be just foolish and waste of time

Question Build Nothing OS source code?

Hello.
I want to compile and flash a custom fork of the Nothing OS. My issue is that I have never compiled and built an android OS before. I have built other OSes before for other devices but that was with instructions. I'd like to understand how I can build the Nothing OS and how I might find out that in the future for other android forks.
I know I need the source code from here and I know I need the devicetree from here. But I do not know how.
Thank you!

snakehater said:
Hello.
I want to compile and flash a custom fork of the Nothing OS. My issue is that I have never compiled and built an android OS before. I have built other OSes before for other devices but that was with instructions. I'd like to understand how I can build the Nothing OS and how I might find out that in the future for other android forks.
I know I need the source code from here and I know I need the devicetree from here. But I do not know how.
Thank you!
Click to expand...
Click to collapse
You can't build a closed source rom like NothingOS, they only provided device tree and kernel sources for custom rom development and custom kernel building.

acuicultor said:
You can't build a closed source rom like NothingOS, they only provided device tree and kernel sources for custom rom development and custom kernel building.
Click to expand...
Click to collapse
Alright, but, if I were to compile and flash the kernel sources, what would be missing from the system that is proprietary? Would I even have a UI or would it only be the core kernel?

You answered your question, if you build the kernel source you'll get only the kernel which doesn't have any ui itself, you still missing everything from the rom.
snakehater said:
Alright, but, if I were to compile and flash the kernel sources, what would be missing from the system that is proprietary? Would I even have a UI or would it only be the core kernel?
Click to expand...
Click to collapse

acuicultor said:
You answered your question, if you build the kernel source you'll get only the kernel which doesn't have any ui itself, you still missing everything from the rom.
Click to expand...
Click to collapse
Alright, so basically, this is only a fork from the original android repo, with changes so it runs on the nothing phone, and nothing more?

The kernel just allows the operating system to talk to the hardware so you still need an operating system. Your best bet is to grab a custom ROM if you really want to build from scratch or you can create a magisk mod that customizes the stock ROM.

snakehater said:
Hello.
I want to compile and flash a custom fork of the Nothing OS. My issue is that I have never compiled and built an android OS before. I have built other OSes before for other devices but that was with instructions. I'd like to understand how I can build the Nothing OS and how I might find out that in the future for other android forks.
I know I need the source code from here and I know I need the devicetree from here. But I do not know how.
Thank you!
Click to expand...
Click to collapse
Gotta have it working on the OnePlus Nord N200 and I'd be interested