We need build instructions in order for people to more easily make custom roms. Currently most roms here only provide a repo or two, hardly describing the build process if anything. Not sure if those repos contain all the sources/blobs you need either.
It's not that hard to build and you can always go on th cheap and hire a cloud vps for a few hours, so don't bother with local building unless you have the powerful hardware.
Anyhow, so far what I know is that some people just replace the kernel and firmware, it seems this is called repacking.
Others are building Lineage from source as per their instructions, which are not descriptive when you're porting to a new device.
We need concrete and concise information about how it's done.
Lineage wiki is pretty accurate and if someone ask here I can try to solve his doubt.
I am not the best developer but I know the basics xD
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
randxor said:
Can you describe the basic workflow?
Which repos to check out, what build scripts are there, how to combine them. Basically a short tutorial on stuff. Also how come you're using 821 kernel from zl1, i know 820 and 821 are alike, but when do you patch the kernel to work for 820, i read that you need some config changes and a different gpu blob.
I am a developer myself, but not an android rom one. Things look really fragmented and chaotic. Besides Lineage wiki, I haven't found anything that resembles docs. I really want to contribute on this and have the hardware to build, just need some info on where to begin.
Thanks for taking your time to reply.
Click to expand...
Click to collapse
Thats thanks to codeworkx code. Basically you compile a rom for zl1 and works for zl0.
My workflow is
repo init/sync the rom
Fix libhidl and libbfquio if needed (Dont know why they fix an error creating a bigger one tho)
Take the device tree, vendor and kernel
Adapt the device tree for the rom (Like in cosmic where config is in root not in config folder, boardconfig...)
And just brunch or make or lunch depends on rom xD
Edit: Forgot u need like 200 frameworks/av commits to make zoom work https://github.com/mosimchah/frameworks_av/commits/o8.1 all the january 15th and this one http://gerrit.aicp-rom.com/#/c/54436/
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
randxor said:
You init the Lineage repos?
What are those libhidl and libfquio about, and how do you fix them?
Vendor is the firmware blobs?
Kernel is obvious
What is a device tree? And how it relates to the kernel?
How did you adapt it to the device?
Different devices have different partion layouts I assume. How do you make the zl1 rom work for both zl0 and zl1? Earlier people were reporting bricks because of flashing roms for zl1 on zl0
Click to expand...
Click to collapse
Yout init the rom source you want to compile
You dont need to adapt anything codeworkx already did it for us we just compile zl1 roms with his device tree (Los one) or any of the forked ones (Like Aicp which I recommend).
Libhidl and libbfquio depends on the rom you are building. Libhidl is solved by reverting this changes https://github.com/PixelExperience/system_libhidl/commit/607e961b85eea8969503d8ff8437c014f04f0ca2 and libbfquio by taking this http://gerrit.aicp-rom.com/#/c/56488/
You dont adapt device tree to device you adapt it to the rom you are compiling see how other devs do it in their github (Every rom is different for example in cosmic you rename lineage/aicp.mk to cos.mk and change where to import things)
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
Start by picking up a rom you want to compile that has 8.1 source working and better if a msm8996 device is there (zuk z2, oneplus 3...)
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
randxor said:
Thanks for the info. Will experiment a bit when I have free time. Planning on making an in-depth guide if I succeed and clarify the concepts.
Btw I see that everyone is using kernel 3.18.20, why can't we get a newer kernel? If we have the sources for it and the blobs? Is the reason being that the drivers are not in the mainline kernel so they need to be ported to a newer kernel?
Click to expand...
Click to collapse
Np
Not sure dont know much about android kernels
I would like to develop a custom ROM for my device. I read some guides and obtained some basic knowledge, but still don't know how to start. So I would like to ask some questions to test my knowledge and expand them.
My device: Wiko View
My Android version (actually installed): 7.1.2 almost pure Android (just some third-party apps)
Desired Android version: AOSP 9.0 (maybe?)
So as far as I know I need these things:
AOSP Source Code (9.0)
Kernel
Vendor (tree or blobs?)
Device tree
So for the AOSP: I can get it from the repo hosted by Google. How should it look once downloaded?
For the kernel: should I use that from my actual ROM, or the most recent one? And how to include it in my ROM before compiling?
For the Vendor: As far as I read, with project treble I shouldn't edit this. But since I'm not developing a treble ROM, I'm in troubles, right? In older ROMs (before Oreo and Treble), they're stored in /system/vendor. Is just that folder or are there more? Do I need to update something? Where do I need to put this folder?
For the device tree: I read some guides that explains how to extract it from ROM (only from 5.0 and up, since mine is 7.1 no problems, I hope). Is this right or are there other ways? Or do I need to write it myself?
I'm going to thanks anyone in advance. I know there are plenty of questions, but I hope this thread will be a place for begginer (like me) to know more about compiling from source a ROM. Have a great day!
Hi!
i am new to the treble-enabled stuff, this is the first phone i own that is treble capable and i have a few questions. I think they can apply to other NOBS, so here i go hoping some nice guy will help me understand:
Background: i have the redmi 5plus (global) which i have unlocked (after painful 720h) and i have flashed Pixel Experience 8.1 rom, but i like to experiment and it seems most of interesting roms are on treble.
1. By default, "vince" is not treble enabled. (treble check app says so)
2. "vince" seems to be an "A only" device, not A/B device,
Main Question: Now, what should i do to try (safely) some GSI roms (like here XDA LOS 16 GSI)?
Sub-Question 1: I must most likely flash some other things first, i guess... like a vendor or a treble image? Where do i find it?
Sub-Question 2: I have installed TRWP recovery, is it treble enabled or should i ALSO find a treble enabled recovery?
If i got it all wrong, please i would be happy to stand corrected!
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Xyzko said:
Hi.
Well, yeah, you need to install another vendor, as far as I know, OrangeFox is the treble enabled recovery.
Someone already explained this in this post.
Have fun. :fingers-crossed:
Click to expand...
Click to collapse
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
gardiol said:
Thank you! Sometimes hard to find the right threads...
Installed orangefox, cool recovery!
One last question... how does kernel works with treble? Do i need treble enabled kernels if i want to change the kernel? Are they provided with the treble-enabled rom already or i get to keep the existing kernel? Is the kernel on a dedicated partition separated from the GSI and the Vendor? (i am starting to understand this, maybe)?
Click to expand...
Click to collapse
Months ago it started to appear some projects about android 9.0 before of Google revealed it as android Pie, then at this time devices with treble support also can support GSIs from these projects according two specific conditions: the processor (first qualcomm, then exynos, kirin and mtk were supported) and kind of partition system A-A/B.
At this first times was needed to flash a vendor treble supported rom to add treble support and flash over it a GSI 9.0. without the need to flash other kernel.
In this forum there are a lot of GSIs that eventually could work in our device but it could be many bugs https://forum.xda-developers.com/project-treble/trebleenabled-device-development.
Now is not needed to complicate the job flashing a vendor, then a GSI and maybe a custom treblized kernel so started to appear first developments of roms running 9.0 and these roms will work as exactly did it any rom 7.1 or 8.1, in the future they could be include treble support.
This is the short story.
Is there a custom kernel patched for Nethunter available for the v30?
A moderate browsing suggests that there isn't one already available. How difficult would it be to do this on my own? Im decent on a command line, I've got the time to teach myself how it is done, and Im not too afraid of borking my phone.
Are there guides, kitchens, or the like for doing this? Is there anyone who can point me in the right direction, and doesn't mind the occasional question or two (I don't really want someone to do it for me- I'd like to learn a skill I can use in the future as well)?
Thanks.
This is leading nowhere
First you guys asking for kali nethunter "custom kernel" need to clarify what Nethunter even is (the differences from e.g. a LineageOS 15.1 or dot os 2.6 Android Oreo custom ROM build) and what it would require to get it running in the V30
Also: why changes or features are needed from the kernel side
otherwise it's like turning in circles and the dog chasing its tail ...
zacharias.maladroit said:
This is leading nowhere
First you guys asking for kali nethunter "custom kernel" need to clarify what Nethunter even is (the differences from e.g. a LineageOS 15.1 or dot os 2.6 Android Oreo custom ROM build) and what it would require to get it running in the V30
Also: why changes or features are needed from the kernel side
otherwise it's like turning in circles and the dog chasing its tail ...
Click to expand...
Click to collapse
being flippant certainly will get you the answers you are looking for.
furthermore your reading ability is a bit sub-par, to be honest. I asked for a couple pointers on how to begin going about patching a kernel, myself.. Just pointers, or someone willing to let me bounce a couple questions off them. Being a **** is pointless here. I literally cannot tell you what is needed to get it up and running. Im starting at square one, chief.
Nethunter is Linux that runs in a chroot on top of android. It'll run as-is with a unmodified kernel, but to be able to put an external wifi adapter into monitor mode, you need a kernel patched to allow this.
If you don't have something constructive to offer, maybe next time g-g-go kick rocks dude. It takes soooo much *less* time to just not respond, than it does to fire off some half-assed reply because your reading context sucks eggs.
elijah420 said:
[snip]
Nethunter is Linux that runs in a chroot on top of android. It'll run as-is with a unmodified kernel, but to be able to put an external wifi adapter into monitor mode, you need a kernel patched to allow this.
[snap]
Click to expand...
Click to collapse
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
zacharias.maladroit said:
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
Click to expand...
Click to collapse
no problem. I understand. tone doesn't carry well via text sometimes, so things can get muddled.
I have a couple wifi adapters that support monitor mode. One uses the ath9k driver, and the other uses the rtl8812 driver. I had intended to use one of them (I use them currently with Kali in vbox on my desktop/laptop, so they are known good/working), whichever works best. one is a 11ac, the other 11n.
Does the stock kernel need recompiling with built in support for the wifi adapter/s? Is this the desired end result- a recompiled kernel with support for my particular wifi adapter?
Im going thru the links you posted, currently.
zacharias.maladroit said:
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
Click to expand...
Click to collapse
Im willing to learn how to do this, first. Are there some decent up to date guides that I can follow? Is there a subforum here for this, that I can follow/subscribe to for this?
elijah420 said:
no problem. I understand. tone doesn't carry well via text sometimes, so things can get muddled.
I have a couple wifi adapters that support monitor mode. One uses the ath9k driver, and the other uses the rtl8812 driver. I had intended to use one of them (I use them currently with Kali in vbox on my desktop/laptop, so they are known good/working), whichever works best. one is a 11ac, the other 11n.
Does the stock kernel need recompiling with built in support for the wifi adapter/s? Is this the desired end result- a recompiled kernel with support for my particular wifi adapter?
Im going thru the links you posted, currently.
Click to expand...
Click to collapse
thanks for understanding, agreed - solely text can be pretty prone for misunderstandings
yeah, that's the gist of it
however from the looks of it e.g. SYSVIPC is deprecated and not sure if relay fs (config_relay) is really needed, also options below CONFIG_QCA_CLD_WLAN probably don't need changes at all (might break the wifi of the phone itself)
also CONFIG_USB_G_ANDROID isn't selected in the new config and the f_hid.o and usb_f_hid.o might clash/broken with the patched up state without that config entry being selected
besides that the other config changes might be okay ( OP5_elementalx_kali_defconfig.diff )
elijah420 said:
Im willing to learn how to do this, first. Are there some decent up to date guides that I can follow? Is there a subforum here for this, that I can follow/subscribe to for this?
Click to expand...
Click to collapse
dotfiles that include needed mkbootimg and unpack_bootimg
copy over to ~/bin/
build_lunar.sh
lines out the steps to build a kernel as standalone
Sample steps for lineageos:
https://wiki.lineageos.org/devices/cheeseburger/build
steps are valid until "Download the source code" (including repo sync)
needed git repos for "joan" (V30) have lge in their name:
https://github.com/SGCMarkus?tab=repositories
mostly up to "Updated on May 27" (from the top = newest)
the repos below shouldn't be needed
Those need to be added to .repo/local/manifest.xml (or so, hope that is correct path & file name)
in xml syntax
XDA Y U NO MERGE POSTS ?
edit:
steps for current LineageOS 16.0 related source are:
Code:
export USE_CCACHE=1
export CACHE_DIR=~/.ccache
export KBUILD_BUILD_USER=zacharias.maladroit
export KBUILD_BUILD_HOST=BuildHost
export ARCH=arm64
export CROSS_COMPILE=aarch64-linux-gnu-
export PATH=~/android/toolchains/gcc-arm-8.2-2018.08-x86_64-aarch64-linux-gnu/bin/:$PATH
fakeroot make lineageos_h930_defconfig
fakeroot make -j8
Code:
mkbootimg --kernel arch/arm64/boot/Image.gz-dtb --ramdisk ~/android/final_files/ramdisks_V30_8.0/boot_lineage-16.0_20181118_h930_unpack_b/ramdisk --second /dev/null --cmdline "androidboot.hardware=joan user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 sched_enable_hmp=1 sched_enable_power_aware=1 service_locator.enable=1 rcupdate.rcu_expedited=1 swiotlb=2048 androidboot.configfs=true androidboot.usbcontroller=a800000.dwc3 androidboot.selinux=permissive buildvariant=userdebug" --base 0x00000000 --kernel_offset 0x00008000 --ramdisk_offset 0x02200000 --second_offset 0x00f00000 --os_version 9.0.0 --os_patch_level 2018-11 --tags_offset 0x00000100 --board "" --pagesize 4096 --out ~/android/final_files/ramdisks_V30_8.0/test/H930_lineageOS-16.0_18.11.2018/boot
ramdisk from "stock" (LineageOS default) kernel was extracted via unpack_bootimg , mkbootimg is used to re-assemble the kernel
both are from dotfiles: https://github.com/luca020400/dotfiles/tree/master/bin
zacharias.maladroit said:
dotfiles that include needed mkbootimg and unpack_bootimg
copy over to ~/bin/
build_lunar.sh
lines out the steps to build a kernel as standalone
Sample steps for lineageos:
https://wiki.lineageos.org/devices/cheeseburger/build
steps are valid until "Download the source code" (including repo sync)
needed git repos for "joan" (V30) have lge in their name:
https://github.com/SGCMarkus?tab=repositories
mostly up to "Updated on May 27" (from the top = newest)
the repos below shouldn't be needed
Click to expand...
Click to collapse
thanks for the starting place. I've got plenty to chew on now for the time being.
elijah420 said:
being flippant certainly will get you the answers you are looking for.
furthermore your reading ability is a bit sub-par, to be honest. I asked for a couple pointers on how to begin going about patching a kernel, myself.. Just pointers, or someone willing to let me bounce a couple questions off them. Being a **** is pointless here. I literally cannot tell you what is needed to get it up and running. Im starting at square one, chief.
Click to expand...
Click to collapse
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
ChazzMatt said:
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
Click to expand...
Click to collapse
idk, that's a bit extreme
XDA is/was made for developers and thus it's supposed to be fun (if you remember the previous threads where devs were scared off by people with a salient arrogant attitude)
however in this discussion it just seemed that we both might have taken things a bit too personal - so it's fine.
Also - I might not be the only custom kernel dev anymore - jollaman999 is working on a great custom kernel (each custom kernel is unique with its own goals)
not sure if he's ready to release it already though or if it's for personal use.
There are also other devs or users working on the V30 which might not have released their stuff (or are not willing to release it [again] for whatever reason - such as tattedup, etc. )
zacharias.maladroit said:
idk, that's a bit extreme
XDA is/was made for developers and thus it's supposed to be fun (if you remember the previous threads where devs were scared off by people with a salient arrogant attitude)
however in this discussion it just seemed that we both might have taken things a bit too personal - so it's fine.
Also - I might not be the only custom kernel dev anymore - jollaman999 is working on a great custom kernel (each custom kernel is unique with its own goals)
not sure if he's ready to release it already though or if it's for personal use.
There are also other devs or users working on the V30 which might not have released their stuff (or are not willing to release it [again] for whatever reason - such as tattedup, etc. )
Click to expand...
Click to collapse
Well, I wasn't saying you were arrogant. I was saying even if you seemed that way (you didn't seem that way to me, you seemed to be asking legitimate questions about how much detailed information he could handle), still why would he call the person names like "****" or other offenses -- who just might be extremely important resource?
It's all straightened out now, I was reading from beginning of thread.
ChazzMatt said:
You're replying to a V30 custom kernel developer. The ONLY custom kernel developer for V30, right now. He can be as (seemingly) flippant as he wants, as he has the information you need. He doesn't know yet how much you know or if you can handle full detailed information. Insulting him would not be the best strategy...
I see you two have worked it out. I was starting from the beginning of the thread.
Click to expand...
Click to collapse
I understand *exactly* who I was conversing with. I also understand the questions I asked. He/she can certainly be as flippant as they want. It's within their rights to be. Likewise, I can tell him/her to pound sand. To be perfectly blunt, it doesn't bother me.
He is a great dev. I've used his stuff on my v20. Doesn't change the fact that he made some incorrect assumptions and acted on them. Dont attempt to chide me for someone else's goof. It's not correct, and you aren't contributing anything relevant to the actual question. Besides, it was obviously put to bed well before you decided you have to chuck in your two pennies.
elijah420 said:
Besides, it was obviously put to bed well before you decided you have to chuck in your two pennies.
Click to expand...
Click to collapse
As I've said at least twice. So you're not adding anything either. Or you can't read.
Sent via open market LG US998 V30/V30+
zacharias.maladroit said:
lol - sorry for the venting - there was lots of built-up anger at all the folks who just ask ask ask and don't do research on their own (probably not even knowing what kali is),
even with a custom kernel we won't get far thus more is needed - OP5 folks might have just what we need (as a good basis)
that's exactly what I needed (sorry my ranty post was kinda like venting anger and getting a reasonable answer to not lose faith in humanity, XDA isn't what it used to be)
pie_I_6_WIP9_11
the last 2 commits are what to be added to the kernel.
I've looked around but haven't found anything related to qcacld (our wifi driver) that would indicate it supports packet injection (perhaps need to look more) in any case thus OTG and usb-powered WiFi adapters would be needed
OP5 elementalx kali defconfig is the diff for OP5 elementalx kernel to get kali wifi drivers
with e.g. lunar kernel base other changes would be needed
When using Markus' kernel base (lineage-15.1 vanilla) - it probably would be easier for you to get there quickly: lineage-15.1
https://medium.com/@ruvoteka/how-to...-android-device-universal-method-32e58660d084
is a somewhat better explanation on how to install kali (non-func on our device currently)
https://forum.xda-developers.com/oneplus-5/development/burgerhunter-t3638810
should offer lots of valuable groundwork and git repos to work with
A good "training" would be to attempt to build a custom ROM (e.g. lineageOS 15.1) and a standalone kernel (either for LG stock or lineage-15.1) and see if both are able to boot
Click to expand...
Click to collapse
The last two including
"sched/core: Allow __sched_setscheduler() in interrupts when PI is not..."?
I've never built a kernel but I'd like to have the option of mobile pentesting. If you find yourself with the time and inclination I'd be interested. I'm still learning Java, struggling with recursion, so custom kernels is probably out of my reach.
tooandrew said:
The last two including
"sched/core: Allow __sched_setscheduler() in interrupts when PI is not..."?
I've never built a kernel but I'd like to have the option of mobile pentesting. If you find yourself with the time and inclination I'd be interested. I'm still learning Java, struggling with recursion, so custom kernels is probably out of my reach.
Click to expand...
Click to collapse
nope - I moved the commits to a dedicated branch:
pie_I_6_WIP9_11_kali
so it's
HID patch
Wireless packet injection & selinux patch
the related wifi drivers from the kernel diff need to selected though - since specific wireless adapters are needed which support packet injection functionality
Hi,
Is there a working kernel source that builds and runs fine on nikel ?I know we need correct kernel modules for fingerprint sensor and camera and such but I don't need those features, I only want a kernel source that builds and boot on the device with working screen and touch.
So does anyone have a source ?
Regards
Hi,
To be honest I just need a kernel where I can load my modules, all the precompiled kernels that I found are compiled without CONFIG_MODULES and an embedded device tree.
so if there is a compiled kernel with
CONFIG_MODULES
CONFIG_MODULE_UNLOAD
CONFIG_MODULE_FORCE_LOAD
CONFIG_MODULE_FORCE_UNLOAD
I can live with that.
Any tip is much appreciated.
Regards
This question is to be asked to Xiaomi. Then you will get the best answer
CMKdaGreatest said:
This question is to be asked to Xiaomi. Then you will get the best answer
Click to expand...
Click to collapse
There are already multiple issues opened on Xiaomi's github account with no response, that's why third party communities like xda-developers exist.
Regards