Database Users

How to make angler build

I am trying to build an image for angler. Looking for make files to build the image for angler (Nexus 6P) Where can i find the vendor/make files to build the image.
How do I see the angler option when I do lunch?

Do a quick search on Github, it should have everything you need.

Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.

debby_8 said:
Thanks for the reply. I looked at the git hub. But I saw so may files. Not sure, which files I need to make the build.
Click to expand...
Click to collapse
Trying to build the kernel myself, would also appreciate some info. Samsung always at least always includes some help file to specify the toolchain needed etc.

to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?

mehmehmen said:
to build angler you need all the device files from android_devie_huawei_angler im fairly sure. Iv gotten my new handset and been working with a guy whos helped me to get a booting port of Omni Rom up and running other than that im not sure exactly how to help.
if your trying to build a image you surely know what files you need to use?
Click to expand...
Click to collapse
Well in my case, at this point I just want to build the kernel. It's really too bad that XDA doesnt accept posts like this on their 'development' forum. On this general FAQ forum I dont think it reaches the right audience and hence no reponse from anybody yet, to this fairly simple question. I wish XDA would support developers a bit more and would allow development questions on the development forum.

I understand what you mean, although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading. I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Im currently working on the angler with a couple of guys and we have a booting fully operational OmniRom port in testing stages now, which may end up to me then posting that as a full [ROM] thread and trying to offer support on the device for that rom. The guy that built the rom himself is very good and has helped me understand a lot, with the right attitude and willingness to learn I am sure you would be welcome in the IRC channel where I personally would be happy to try and help you get your head round some things, as the next goal for me regarding the 6p in terms of our project is going to be kernel based compiling as i want to try and get a really robust kernel built now we have a seemingly stable feature full rom built and booting.
Feel free to message me if this sounds like it may be of some help
Regards
Meh

mehmehmen said:
although the development forums used to get INUNDATED with questions similar to these which would usually be able to be remedied with a bit of googling and a decent amount of reading.
Click to expand...
Click to collapse
That happens on any forum.
I think you would find if you were to go to the actual angler kernel threads and be very concise and polite in asking for any help that someone would actually be happy to help at least a little bit.
Click to expand...
Click to collapse
Sure but that would be going off topic on someone's thread.
You have to remember on the dev forums most people are kind of in the know of what they want to do and roughly how to do it hence why they prefer posts to remain within the realms of people contributing to thread projects and giving test feedback as opposed to asking for help on seperate (although maybe related) issues.
Click to expand...
Click to collapse
Everybody has questions, regardless of their level. I was the maintainer for Cyanogenmod Note 4, so if the above would be true, I wouldnt be here I'm sure I can figure out myself how to get the Angler kernel compiling but it would save me, and others who will try the same in the future, quite a bit of trouble if someone who had done it would just post the used toolchain etc.
Anyway you used a lot of words without helping at all. That's exactly my point, when posting on a general forum you can expect these kind of replies. That's why I'd love to see a true development forum here on XDA, not just a 'developer' forum where people just support their projects. Giving support to a project, has not much to do with development.
Nah, I could have expected this. I'll figure it out myself. Thanks but no thanks.
*EDIT* I guess this will work, using toolchain 4.6 like they recommend, it's probably the latest anyway (?)
https://source.android.com/source/building-kernels.html
They dont mention Angler, but I'll try this anyway, I think it might work. And I'll let people know if it worked or not, so someone in the future who reads this thread will know how too. Although I kinda doubt a developer will search the general FAQ forum here ...

Might wanna try asking that on a kernel development thread in Dev section - kernel developers are usually friendly to people willing to rightfully use (and maybe improve) their work. They should be at least give you a vision on how go get the basic Angler kernel up and running.
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]

Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.

rustyjay said:
Use googles 4.9 aarch64 toolchain for kernel to start off. Any questions feel free to hit me up, better on hangouts though as I forget about XDA sometimes ha. Pm me for email.
Click to expand...
Click to collapse
Thanks mate ! That's what I was looking for, will try that one.
---------- Post added at 03:23 AM ---------- Previous post was at 03:03 AM ----------
Ok and it's building !
Steps I took:
1) Download angler kernel here: https://android.googlesource.com/kernel/msm/+/android-msm-angler-3.10-marshmallow-dr
2) Download toolchain with: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9
3) add the toolchain to the path, in my case: export PATH=~/android/toolchains/aarch64-linux-android-4.9/bin:$PATH
4) go to the unpacked kernel dir
5) export ARCH=arm64
6) export SUBARCH=arm64
7) export CROSS_COMPILE=aarch64-linux-android-
8) make angler_defconfig
9) make
Thanks again @rustyjay for the toolchain info !
---------- Post added at 03:32 AM ---------- Previous post was at 03:23 AM ----------
AndyYan said:
As for me... I build CM, everything on the CM wiki is mostly enough for me.
Click to expand...
Click to collapse
As much as I love CM (I was maintainer for the Note 4), I don't particularly see the point of running it on a Nexus device. I just want some kernel tweaks (for example that damn fuel gauge is giving me wakelocks), so I think l wont jump onto CM. But who knows ...
---------- Post added at 03:46 AM ---------- Previous post was at 03:32 AM ----------
Build completed So I guess I just insert the resulting Image.gz-dtb into the boot.img (with android image kitchen for example), right ? Will try tomorrow, but I think that should work. off to bed now ...

Yeah what it basically does when I build aosp, don't know too much about kitchen.

rustyjay said:
Yeah what it basically does when I build aosp, don't know too much about kitchen.
Click to expand...
Click to collapse
Ok I used android image kitchen to replace the Zimage, flashed it and ... it boots
Cool, so that's easy. Now for the next part: building the whole rom ! Any idea on how to do that ? Or where to even download the code ? Is there even a whole ROM to build, including the blobs etc ? I think i saw google releasing a device tree but not the whole ROM, right ? I must say I havent really googled myself this, will look into this today myself too.
*EDIT* yeah here's the device tree: https://android.googlesource.com/device/huawei/angler/ but I dont think it's the whole ROM, going to download it now ...
*EDIT2* No this definitely isnt the whole ROM,not even the device tree There's not a lot in there !?!
*EDIT3* Info here: https://source.android.com/source/running.html
*EDIT4* So as per the link above, it turns out that most drivers are blobs ! Hmm that's a bit disappointing. You buy a Nexus because supposedly it's 'open source', turns out most of it is not.... Anyway so it seems it's just a matter of compiling the sourcecode that IS there and then adding the blobs.
*EDIT5* So this section explains the whole process of setting up the environment, downloading, syncing and building: https://source.android.com/source/requirements.html looks very similar to the CM install/build process indeed !

To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.

rustyjay said:
To me its easier than cm but aosp is what I do the most. And to build for aosp you'll need angler device tree and vendor blobs. Ive been using the huawei vendor from pure nexus github.
Aosp out of the box is really unfinished though to me so it takes some work with cherry picks to get everything slick.
Click to expand...
Click to collapse
Thanks for all your info, much appreciated. Currently syncing to AOSP like explained on that page I linked, will take a few hours I guess.
BTW, what are you exactly building this for ? Just some tweaks ? I saw this kernel wakelock qpnp_fg myself, I just disabled CONFIG_QPNP_FG=y in the defconfig, the wakelock is gone but like I expected, the battery gauge doesnt work anymore neither, lol. Will need to look into it for a real fix I guess.
Also I'm planning to make an option to default MTP as USB connection. It's just plain crazy Google left that out in 6.0 !

I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.

rustyjay said:
I've been building for myself for like 2 years now, kernels I just started really messing with about 6 months ago. I just had a hard time finding a ROM with stuff I like and not a million other mods added to it. Now its just hard for me to stay on stock or a ROM I didn't cook up.
Click to expand...
Click to collapse
It's my first Nexus and am just loving it already. I mean, getting CM to run on a Samsung device is of course fun, but it's also just SO much work. I dont think I could do it all over again on another non AOSP device.
Now on nexus, just syncing directly from google and building it, what a breeze this is !

Oh yeah if your into building, nexus is really the only way to go. My first nexus was the ns in '10 and have had a nexus phone ever since

OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.

rustyjay said:
OK, so I don't know anyone else with a 6p but want a second opinion on my rom/kernel so far. I do not want to start and maintain a thread, why I'm posting this here.
https://drive.google.com/file/d/0B_f86wvdx8LKUm12NHpxSVBhVEk/view
Its not a kitchen sink rom, if there's interest I'll make a changelog with the proper credits to people and probably upload builds to my drive.
Click to expand...
Click to collapse
What are your main changes ?
Anyway I just finished building the ROM myself. It ends up with system.img, userdata.img, recover.img, ramdisk.img, ramdisk-recover.img. I'd probably just flash boot.img and system.img, right ? That userdata.img, what is that exactly anyway ? If I flash that I'll lose my user partition=installed apps, I guess ?
BTW I didnt pull any blobs so I guess it wont run anyway. I guess I first need to extract the blobs ? Does the AOSP build process include the blobs automatically ?
Thanks !

Test build

Hello everyone.
http://download.jgcaap.xyz/files/bullhead/cm-13.0/
Would like to request if possible if someone could test this build
This build is based on CM device tree kernel and blobs, which shouldn't cause any issues on flashing.
As a test, please remember i'm not responsible to any damage which might occurr.
The worst thing might happen is not booting.
This rom is like flashing a CM nightly.
I'm interested on expanding my work between diferent devices. So please let me know how it goes.
Please list the bugs.
F2FS is compatible with this device?
source https://github.com/CyanogenMod/android_kernel_lge_bullhead
Thank you

jgcaap said:
Hello everyone.
http://download.jgcaap.xyz/files/bullhead/cm-13.0/
Would like to request if possible if someone could test this build
This build is based on CM device tree kernel and blobs, which shouldn't cause any issues on flashing.
As a test, please remember i'm not responsible to any damage which might occurr.
The worst thing might happen is not booting.
This rom is like flashing a CM nightly.
I'm interested on expanding my work between diferent devices. So please let me know how it goes.
Please list the bugs.
F2FS is compatible with this device?
Thank you
Click to expand...
Click to collapse
Please add a direct link to kernel source used as required by XDA and GPLv2...thanks. And thanks for your contribution.

KennyG123 said:
Please add a direct link to kernel source used as required by XDA and GPLv2...thanks. And thanks for your contribution.
Click to expand...
Click to collapse
It's stock from CM. I'll open a new post under development thread if everything goes well on tests and add all source links there. Is it ok? thanks

jgcaap said:
It's stock from CM. I'll open a new post under development thread if everything goes well on tests and add all source links there. Is it ok? thanks
Click to expand...
Click to collapse
The only thing considered stock is direct from the manufacturer, LG or Google. CM is not a stock OS, therefore if you are distributing the binary (boot.img) in your link then you must post a link to the kernel source compiled to make it. Otherwise you need to remove the boot.img and let people get their own kernel.
Thanks

KennyG123 said:
The only thing considered stock is direct from the manufacturer, LG or Google. CM is not a stock OS, therefore if you are distributing the binary (boot.img) in your link then you must post a link to the kernel source compiled to make it. Otherwise you need to remove the boot.img and let people get their own kernel.
Thanks
Click to expand...
Click to collapse
done Thanks for clarifying.

Hello @jgcaap
i will test and report back
thanks for supporting 5x and 6p (i have both)
edit: i'm using F2FS and un-encrypted. I've had to change the kernel to jolla's, to make it boot. It does not boot on stock kernel.
everything else seems to be working fine.

[KERNELSOURCE] MT6755 Sony XA DUAL Discussion: Is it possible to port?

Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie

vsrookie said:
Hi out there!
Today i've looked another time for kernel sources of our loved (and hated) phone.
The only full source i've found was this one on the Sony Website:
http://developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-33-2-a-2-37-and-33-2-b-2-37/
I don't have the time nor the knowledge of kerneldevelopment to check this out.
My question is:
Is it possible to port this Sony kernel, to have a working p9000 kernel, with the goal to have let's say DirtyUnicorn running?
greetings
vsrookie
Click to expand...
Click to collapse
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.

Jonny said:
Kernel and ROM are 2 different things. We could get DU working on stock kernel, but we need valid device and vendor trees. Sometimes you can make them yourself, other times the manufacturers provide them.
Click to expand...
Click to collapse
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app

vsrookie said:
Ok. But an android system need functions from the kernel, don't they?
What do you exactly mean with device tree and vendor tree? The drivers for the components? If it is so, then can't we "just take them" and integrate in the kernel source?
greetings
vsrookie
Ps: Basically i need to read sonething about Android development. [emoji12]
Sent from my P9000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Vendor tree example >>> https://github.com/omnirom/android_vendor_omni
Device tree example >>> https://github.com/omnirom/android_device_sony_kitakami-common
The Android system does use functions from the kernel but its not really "aware" of doing so, you can run custom ROM's like DU, Omni etc from stock kernels most of the time without any issues.

So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.

Boristruyens said:
So basically: When/If Elephone decides to release CM13, it's still possible they won't give us the vendor/device tree? So that's basically a byebye to porting roms?
Sorry, I'm a nub too.
Click to expand...
Click to collapse
Tbh that is a massive probability, making device and vendor trees is not non-trivial and is a lot of work. For instance the HTC 10 still doesn't have a stable CM build, and there are some hard hitters in the AOSP dev world that own that device. I'll have a look and see what I can do but I'm an app developer and an apk editor (i.e. Java and Smali are more my languages than C/C++) more than a source builder so I might not be able to do much.

Can i use it for making recovery for moto m

The P9000 has a kernel on github anyway ...

3.10.33 kernel from Nvidia Shield ported to Mi Pad

Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2...nhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2...FhQTHJIa2xVems

reserved

Artemka2008 said:
Hello from Moscow, Russia. I can't write in Firmware section, so I write here.
I'm and my teammate(Dblm) ported 3.10.33 kernel from Nvidia Shield. TWRP works fine with this kernel. But android don't work cuz our graphical blobs are very very old. So may be somebody can find necessary blobs and run android.
zImage: https://drive.google.com/open?id=0B2ALf4H-2aBrZnhPdlJkWkdYQjg
TWRP recovery with this kernel: https://drive.google.com/open?id=0B2ALf4H-2aBrZFhQTHJIa2xVems
Click to expand...
Click to collapse
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).

drakonizer said:
Thanks a lot for posting this. It would be more helpful if you could post your source code for the port and the source (the original shield kernel).
Click to expand...
Click to collapse
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)

Artemka2008 said:
At the moment my teammate does not want to publish the source code.
CPU fixed in this build(all 4 cores work)
Click to expand...
Click to collapse
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.

drakonizer said:
I really appreciate your work. Don't get me wrong. But Linux is licensed under GPL. The law requires you to open source your work, and so does XDA. This is why we didn't have a Mi Pad forum till now. To avoid problems and to prevent XDA from banning you or closing this thread, I suggest you either publish your source or remove the link.
None of the devs can help you if you don't release the source code. Please co operate with the open source community.
Thanks for understanding.
Click to expand...
Click to collapse
ok, I will delete this thread.

Artemka2008 said:
ok, I will delete this thread.
Click to expand...
Click to collapse
You don't have to delete the thread. It can be used for discussions. You can upload your kernel whenever you feel its appropriate to release your source code.
On a more helpful note: I can't say much without seeing the source code, but if you have ported the kernel drivers as well from shield, you can try using the blobs from Shield itself. You'll probably need to use blobs that match the version of the kernel you are trying to port.

so does that mean that there is a chance for cm12+?

Jahhhhhhh said:
so does that mean that there is a chance for cm12+?
Click to expand...
Click to collapse
Without camera and sound now. I tried to run Android 5.1.1 with our kernel. But I can't find working graphical blobs. I need help with it.
This is my last logcat https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?

Palm Trees said:
This is going nowhere until you share the source code with the community as per GPL. How long does your teammate want to drag the process? Release the source code today and start getting feedback from other devs - what's the hold up?
Click to expand...
Click to collapse
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.

Artemka2008 said:
God, the source code will not help here. You just need to pick up the blobs to run android. With the kernel of today there are no problems.
Click to expand...
Click to collapse
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.

drakonizer said:
Blobs are heavily linked to the kernel drivers. Without even knowing what kernel you have used as a source for the port (the one for Shield), how can we randomly test blobs and somehow magically fix this? I really don't want to piss you guys off, but the reason why you can do the work you do is because the Linux kernel is open source. And it's stayed that way because people have followed the GPL (with only a few exceptions like Xiaomi). I do not understand why you don't want to release the source code. Nobody is trying or will try to steal your work and claim credits. In the end we all want the same thing - stable Android 5/6/7 on the Mi Pad. Let other people help too.
Click to expand...
Click to collapse
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.

Palm Trees said:
That's my point exactly. Have you tried asking in the Nvidia Shield xda thread: http://forum.xda-developers.com/shield-tablet/development. There's plenty of development going on, you might be able to get some tips and tricks.
Click to expand...
Click to collapse
Not the point. The shield developers will not be able to help us. Things will become very easy if this shield kernel port works. We will probably be able to use the newer blobs meant for the Shield, which makes development very easy, if this becomes bootable/stable. I really hope the OP manages to get it working. We either need newer blobs from Xiaomi or we need to write wrappers to use the current kitkat blobs (not easy, since Nvidia documentation is nowhere near as detailed as say, Qualcomm) or we need to get this port working well, which would enable us to use most of the blobs from the Shield (provided Xiaomi hasn't gone out of their way to screw with their blobs). The first two ways are practically impossible, which leads me to rest all my hope on this port. Unfortunately without the source code, we will just have to be silent spectators, waiting for some news.

Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks

rocky869 said:
Here's my effort for asking sheild developer- http://forum.xda-developers.com/shield-tablet/help/help-support-xiaomi-mipad-custom-rom-t3512695
I also posted a xiaomi forum link where Sheild Lollipop kernel is accessible for developers. It's available in Xiaomi forum.
Here's the link - http://en.miui.com/thread-439620-1-1.html
I have just shared the information available. Not taking any credit away from developer from 4pda.ru.
Thanks
Click to expand...
Click to collapse
I asked LuckyMeAgain to publish on the official website, so it's the same thing. I am ArtemkaVZM on 4pda and arttt on en.miui.com MiuiSmokeRom dev team.

Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia

Harrynowl said:
Presumably the easiest way is to go through TheMuppets repo and testing them at different points in time by checking commit history.
https://github.com/TheMuppets/proprietary_vendor_nvidia
Click to expand...
Click to collapse
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U

Artemka2008 said:
I think that we have to make a new build. Current builds are useless for us now. I mean available android 5 roms.
This is my last logcat with 5.1.1 Vartom's SlimRom: https://drive.google.com/open?id=0B2ALf4H-2aBrX3dCRkthR21wM1U
Click to expand...
Click to collapse
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?

drakonizer said:
looks like hwcomposer is the broken blob. Have you tried using the hwcomposer.tegra.so from a Sheild ROM to boot it?
Click to expand...
Click to collapse
All the necessary blobs were taken from Shield. More no such files, which could be replaced.

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