Related
Hi!
I just want to vent my anger
Has anybody noticed that there are a minimum of four "parties" that work on an android kernel tree?
First there is the android open source project.
Then there is the CodeArora project.
There is also a kernel tree at Cyanogenmod.
And last but not least we have the "manufacturer" kernel tree.
AOSP has got a common tree and an individual tree for each architecture- just like Cyanogenmod.
CodeAurora has got multiple(!) trees for a single architecture.
The manufacturer seems to use some of CodeAurora's trees in the majority of cases.
Ah- I forgot the "original" linux kernel tree
This way we never get the most efficient and most stable kernel.
Just my two cents
you're right, but not only the kernel is used. LG takes code from codeaurora project - have seen this in code from the frameworks base tree^^
but on the other side: better they use community code as own code that didn't works perfect
WTF? LG really takes his sources from CodeAurora?!?!?
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
sarfaraz1989 said:
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
Click to expand...
Click to collapse
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
andy572 said:
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
Click to expand...
Click to collapse
That is exactly the problem!
I cannot really judge which patch from which tree is good- because I have not the time to read through Qualcomm's manuals (if they are public at all) and the kernel source.
If they would concentrate on one tree everything would be fine (ok- if you look at the "chaos commits" in the git repositories you become sick )
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
sarfaraz1989 said:
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
Click to expand...
Click to collapse
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
ciolnadu said:
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
Click to expand...
Click to collapse
yes, it's marketing strategy and its ok - but why should i buy me a new device, when my is doing a good job?
andy572 said:
but why should i buy me a new device, when my is doing a good job?
Click to expand...
Click to collapse
+1 agreed 100% with andy.
andy572 said:
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
Click to expand...
Click to collapse
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
rivett said:
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
Click to expand...
Click to collapse
code isn't moved but deleted.
Has anybody found out the CodeAurora git commit on which LG's V10r is based on?
Just rambling here. In order to get ICS ported to the Venue, we need compatible kernel drivers. It appears, from what I can find on the 'net, that Qualcomm isn't releasing drivers for the QSD8250 for ICS. Looking around XDA, I see the HTC Desire (GSM), also based on the '8250, has a working ICS beta found here: http://forum.xda-developers.com/showthread.php?t=1403113. This appears to use a Tiamat kernel, http://tiamat-dev.com/tiamat_bravo/. Using the AOSP 4.0.x repository, the Dell info from http://opensource.dell.com/releases/venue/v4.06/ and the Tiamat kernel, is it possible to pull together an ICS port? I wish I had more experience with this type of stuff...
Dell used the CAF 8260 GB sources when building 4xx roms, they simply backported whatever they need to from their already working 3xx codebase for whatever was needed (i assume)
CAF itself dropped support for 8x50 in their GB codebases, but the 8x60 is close enough it didnt really matter ultimately.
Much of the drivers arnt even in the kernel, they're in the android userland which is Apache and not gpl, hence the driver issue.
Which ever method you (presumedly do) to get the kernel booting under ICS doesnt really matter, but the more difficult/time-consuming methods will ultimately be more useful for porting to newer kern versions.
Don't forget the Nexus One and, IIRC, the HD2 also use the 8250
I would think this would help too: http://www.xda-developers.com/android/qualcomm-releases-adreno-2xx-gpu-binaries-for-ics/
Too bad the development work is well outside my capabilities. Maybe our Korean friends are working on it though.
Guys.!!! Dell venue n dell streak 5got same rom n environment hardware too just diffrence is venue is Hdpi n dell streak is Mdpi .so why do nt we join hands n make ics work for dell or on other hand u can take advantage of our dell streak 5 formus there r few good roms like longhorn 2.8 with Hdpi support for dell Venue and Dcs 1.1.which supports both hdpi n mdpi just need to edit build.prop n may be kernel....whish u all safe cooking ...n Friends in need friend indeed ..
Max
Sent from my Dell Streak using xda premium
Sent from my Dell Streak using xda premium
Folks, I can see that Qualcomm released Adreno 200 drivers for ICS several months ago (Mar) (https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources).
Information in the above page also says that, the drivers has been tested on CAF M8960AAAAANLYA1030. As I noticed, whenever we get the source code from Code Aurora, there is also a kernel directory included. Do you think that we can start from that kernel to port ICS to Venue?
chacona said:
Folks, I can see that Qualcomm released Adreno 200 drivers for ICS several months ago (Mar) (https://developer.qualcomm.com/mobi...phics-optimization-adreno/tools-and-resources).
Information in the above page also says that, the drivers has been tested on CAF M8960AAAAANLYA1030. As I noticed, whenever we get the source code from Code Aurora, there is also a kernel directory included. Do you think that we can start from that kernel to port ICS to Venue?
Click to expand...
Click to collapse
Yes we can,
But I aint that good into dev
This mobile has what it requires to run ICS
The kernel itself ultimately doesnt matter, as long as it has the right code changes merged in.
The current S5 ICS kernel's lineage is:
S5/405 (dell) -> Phoenix kernel/GB (n0p) -> Phoenix/cm7.2 (hPa) ?-> Phoenix/cm9 (hPa) -> Phoenix/AOSP (kibuuka)
Only the final step involved merging in any changes to make it work with ics, ultimately it's based mostly on the phoenix GB kernel which itself is based on the S5's 405 kernel
S5 405 = S5 408 = V 406 = V 408, they're all the same kernel (with ifdefs/configs for the S5/V).
I'd imagine getting a V kernel to boot ICS period is 85% of the work as the S5's froyo/GB kernels can directly boot V froyo/gb roms, and the reverse would likely hold.
The kernel 405/6/7/8 from Dell can be built successfully, however there are known issues such as after charging, we won't be able to boot the kernel up. I do not have a Streak, so I wonder whether those issues are fixed well in Phoenix kernel Manii? Can you show me how to get the source for the latest phoenix kernel that you're using with your Streak AOSP? Maybe I will try to build with Venue myself to see how things work!
phoenix kernel/ICS - Github
It's currently in the process of being merged back in.
You could try diffing S5 405 with V 406 and seeing what's changed in the source, they're nearly identical, but I dont expect them to be bit identical
TheManii said:
phoenix kernel/ICS - Github
It's currently in the process of being merged back in.
You could try diffing S5 405 with V 406 and seeing what's changed in the source, they're nearly identical, but I dont expect them to be bit identical
Click to expand...
Click to collapse
Sounds interesting, that's exactly what I did in my custom overclocked kernel. However, I will be able to save some time by using their kernel directly. In fact, I think that 405/407 kernel is not very different from 406 since my build for 405 also ran on DV too.
I will try with their "master"/experimental14 branch kernel first (to CM 7.2.0). Thanks for your information!
chacona said:
I will try with their "master"/experimental14 branch kernel first (to CM 7.2.0). Thanks for your information!
Click to expand...
Click to collapse
Will be waste of time as only streak-specific file is board-qsd8x50_austin.c, other changes are device-independent.
Changes that essential to run ics with hwa:
kgsl3.8 - kernel-side drivers are in drivers/video/msm - direct drop in instead of one that's shipped with stock 405 kernel
include/linux/msm-kgsl.h - to make kgsl3.8 build
(not really)*streak-specific*changes to arch/arm/mach-msm/board-qsd8x50_austin.c - changes in hardware init routines needful for kgsl3.8 (updated data structures, powerrail). In short - do a diff for board-qsd8x50_austin.c between Phoenix and ics branches to find out what's changed - to be honest - changes are generic for qualcomm devices, so direct copy/paste of changes into your device's board file will do the job
Other patches that were applied to ics branch are optional (cpu governors, io schedulers, netfilter specific changes (these are only needed if you need ics' mobile data usage collecting/limits features)) or affect streak-specific drivers only (and are not ics-specific).
So, in short - update your device's board file and use ics branch - that would be enough.
kibuuka said:
So, in short - update your device's board file and use ics branch - that would be enough.
Click to expand...
Click to collapse
Do you think I can start with the stock kernel, download the ICS tree including the kernel, then do the diff/merge between device's board file from ICS kernel to Dell kernel? After that, the original Dell kernel is patched with new stuffs for ICS, and can be used with ICS ROM?
i can also provide you with all patches made for streak against aosp source tree for shortening your mileage and instructions for a quickstart (my streak is broken at the moment, so i've suspended my development activities and got spare time for that)
please mention kernel for streak's ics is being built separately at the moment (i've got plans incorporating it in aosp build process, but it will take some time)
when i've messed with streak kernel making it ics-friendly i've realised that most of stuff can be made cross-compatible between two devices.
It's 95% the kernel, the only thing left is to turn off the rotation patch and swap out the BCM4325 for BCM4239 drivers.
On stock 3/4xx i can directly load venue roms on my S5 and only wifi is broken. (with a S5 kernel) Everything else works.
TheManii said:
It's 95% the kernel, the only thing left is to turn off the rotation patch and swap out the BCM4325 for BCM4239 drivers.
Click to expand...
Click to collapse
rotation is triggerable through kernel configuration menu. check.
as of wifi - is there any known-to-be-trustable list of hardware components for venue?
The V is just an S5 without the hdmi and whatever provides usb hosting.
The only other notable change is the wifi chip.
All the other sensors are compatable, and so is the modem+ril.
(I was able to get 3g working, but not wifi due to the chip being different)
I dont think anyone has done a (good quality) teardown on the V though.
Most I can offer is to pull details android gives back while it's on.
I'm guessing that's how CM7.2 was ported, since hPa didnt actually own a V,
he just took his S5 build, and flicked a few switches.
(it helped a lot that CM7.2 doesnt need any kernel changes to boot, it's just the stock 408 one with a modded ramdisk)
He only had access to a V for like a day or so.
kibuuka said:
i can also provide you with all patches made for streak against aosp source tree for shortening your mileage and instructions for a quickstart (my streak is broken at the moment, so i've suspended my development activities and got spare time for that)
please mention kernel for streak's ics is being built separately at the moment (i've got plans incorporating it in aosp build process, but it will take some time)
when i've messed with streak kernel making it ics-friendly i've realised that most of stuff can be made cross-compatible between two devices.
Click to expand...
Click to collapse
Hi Kibuuka, that sounds good, could you please share?
One more thing I would like to ask is, the stock kernels 405/407 and 406 have issues regarding power (sometime I can see the issue that after charging, screen goes black and we can only quit that situation by removing the battery). How did you address it? (I notice that your kernel works well on my CM7, without that issue - or is just simply because it has not happened yet?)
n0p did enormous amount of work addressing sleep of death issue (which, i believe is one you refer to), so dsc kernels (opposed to stock ones) are free of this bug. Ask him for details (i wasn't involved to dsc development at the point he managed to fix it) as he's best source of information on SoD issue fix you could find
As of aosp patchset - will upload it during weekends.
For whatever it's worth, as soon as we get a working ICS level kernel, I plan on porting TWRP and CWM-touch.
Those require ICS kernels (or rather it's a great deal more difficult to make them run on GB kernels) and I cant port them until then.
I've already gotten TWRP and CWM-touch working on the S7, and plan on porting TWRP to the S10 now.
Edit: come to think of it, I actually have TWRP running on a 5xx kernel (which is HC), i'll try simply porting and seeing what happens
Guys,
I have a CM802 Android 2.2 tablet that I would like to support external USB devices. My problem right now is that the default ROM doesn't seem to have USB host drivers, and I have no idea where to look. Can you guys point me in the right direction?
Thanks!
I don't know your hardware, but your android version should have no support for both usb host mode and USB otg. If you upgrade and hardware is ready, maybe. But very likely you'll need the kernel USB modules sources and a dev to compile them especially for that build. That's why on my se xperia x10 such feature is still missing ...
The hardware has support for it, and I don't care what version of Android I end up with, as long as there's support. I also don't mind installing them myself, but would like some direction as to where to find the modules.
have you tried going to the manufactures website?
Wrycu said:
The hardware has support for it, and I don't care what version of Android I end up with, as long as there's support. I also don't mind installing them myself, but would like some direction as to where to find the modules.
Click to expand...
Click to collapse
You will need to compile a proper kernel with support for it. There have been a few on the site that have done it for a few devices but it is not an overly popular mod
Well, I have just seen a site where they sell the android 2.3 version of the same device which seems to have the USB otg support. In any case, the first step must be one upgrading at least to android 2.3...
lucaoldb said:
Well, I have just seen a site where they sell the android 2.3 version of the same device which seems to have the USB otg support. In any case, the first step must be one upgrading at least to android 2.3...
Click to expand...
Click to collapse
the kernel would have been made to support it on that device. After building 2.3 from android source code I can say that it is not there by default.
Thanks, I agree that is not supported by default but maybe they had actually patched a kernel with those modules, though such kind of sites are not very reliable...
zelendel said:
the kernel would have been made to support it on that device. After building 2.3 from android source code I can say that it is not there by default.
Click to expand...
Click to collapse
Can you guys link me to the modules or whatever? Again, I'm perfectly willing to build the kernel from source myself, as long as I can have a little direction.
Any help? Links, information, tutorials.. whatever you can give me would be awesome, Internet <3.
Oh, and sorry for the double post.
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.
Instructions on installing Kali NetHunter for the LG K20 Plus. (MP260)
This is a modified LineageOS 14.1 arm64 Kernel modified for use with the Nethunter although its should work for any ROM.
I am going to assume that your device is rooted and has TWRP installed. Also since this is an arm64 kernel, you will most likely need to have a custom ROM installed. I am using AICP "aicp_lv517_n-12.1-UNOFFICIAL-20180216". You can download it from this thread https://forum.xda-developers.com/note-4/snapdragon-dev/rom-aicp-12-1-t3592312.
Once you have that done, Make sure you download the nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170211-0304.zip and then download the kernel I compiled from my github.
https://github.com/robnew/NetHunter_K20plus_Kernel
Flash them both from TWRP and you should be good to go.
THE KERNEL
The NetHunter kernel for the LG K20 Plus is based on the LineageOS 14.1 [LV517] kernel sources.
•SELinux enforcing, switches to permissive when requested by NetHunter app
•Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
•FIOPS IO scheduler as default IO scheduler, SIO available
•DriveDroid compatibility
•USB HID Gadget keyboard & mouse support (HID Attacks, Duckhunter HID Attacks)
•mac80211 packet injection support
•Additional drivers built in for the full Kali NetHunter experience
•Data partition encryption optional (may not be supported by custom kernels - encrypt at your own risk)
•Kernel module support, insert your own modules! (modprobe available in Kali chroot)
•CIFS, NFS available through included kernel modules
Enjoy.
Hello
Hey I am pretty root savvy but just got a phone able to have nethunter kernal I mainly want it for hid keyboard but I can figure out what build to download I can't find any that say lv517 they say Shamu and hammerhead etc. So I was wondering if you could help me find the kernal or a hid kernal I am using the LG mp260 I am on lineage 15.1 I have twrp. I downloaded master zip at GitHub but when I tried flashing it said md5 checksum error if I am leaving out any info I apologize any help would be greatly appreciated
---------- Post added at 11:41 AM ---------- Previous post was at 11:31 AM ----------
Sorry 14.1 I ment 7.1.2 is my version my model is LG k20 plus lineage version 14.1 lv517 20180114 (weird that's my bday lol) hope to here back
Bigjohnvancil said:
Hey I am pretty root savvy but just got a phone able to have nethunter kernal I mainly want it for hid keyboard but I can figure out what build to download I can't find any that say lv517 they say Shamu and hammerhead etc. So I was wondering if you could help me find the kernal or a hid kernal I am using the LG mp260 I am on lineage 15.1 I have twrp. I downloaded master zip at GitHub but when I tried flashing it said md5 checksum error if I am leaving out any info I apologize any help would be greatly appreciated
---------- Post added at 11:41 AM ---------- Previous post was at 11:31 AM ----------
Sorry 14.1 I ment 7.1.2 is my version my model is LG k20 plus lineage version 14.1 lv517 20180114 (weird that's my bday lol) hope to here back
Click to expand...
Click to collapse
Make sure you download the nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170211-0304.zip from the Nethunter Repository and then download the kernel I compiled from my github. github.com/robnew/NetHunter_K20plus_arm64_Kernel. Flash them both from TWRP and you should be good to go. Make sure you are running 64bit Rom. Good luck. Let me know if you have any issues.
Awesome work. I will have to give it a try.
Hey this kernel does not support postgresql in nethunter there is an error about memory segmentation fault. Is there a way to fix this?
Colt5775 said:
Hey this kernel does not support postgresql in nethunter there is an error about memory segmentation fault. Is there a way to fix this?
Click to expand...
Click to collapse
Postgresql works fine for me. I am running it as the back end for MetaSploit. What Rom are you running?
buggy kernel
I've managed to get nethunter pretty much all set up but it seemed like every time I flashed the kernel I would be stuck in a boot loop. anyone got anything on this?
64Bit
Make sure your using a 64bit ROM like RR or AICP. There are both 32 and 64 versions of these. I have uploaded a newer kernel to GITHUB with support for more wifi cards. Let me know if this helps you. Also what is the model number you are using?
robnew said:
make sure your using a 64bit rom like rr or aicp. There are both 32 and 64 versions of these. I have uploaded a newer kernel to github with support for more wifi cards. Let me know if this helps you. Also what is the model number you are using?
Click to expand...
Click to collapse
lg k20 tp260
64 bit pbrp , 64 bit lineageos 15.1
I just tried out the Unofficial LineageOS 15 and the Kernel is not working for me either. I know it works fine on all the 7.1 ROMS. I will work on a new kernel designed for Android 8.1. Not really sure what is different yet.
robnew said:
I just tried out the Unofficial LineageOS 15 and the Kernel is not working for me either. I know it works fine on all the 7.1 ROMS. I will work on a new kernel designed for Android 8.1. Not really sure what is different yet.
Click to expand...
Click to collapse
Thank you I look forward to trying it out asap
Wich zip file from GitHub do we download?
robnew said:
I just tried out the Unofficial LineageOS 15 and the Kernel is not working for me either. I know it works fine on all the 7.1 ROMS. I will work on a new kernel designed for Android 8.1. Not really sure what is different yet.
Click to expand...
Click to collapse
Base it on my 9.0 kernel on github
Thanks for the work I'm going to try noe
Hi thanks for continuous hard appreciated work.
Question did you get this working with the lineage Os 15.1 ROM the kernel part I mean?
Last question is the ROM you have posted here better than lineage one I'm using for this phone like in options or speed ,mods ,etc..
Please everyone do not take anything in wrong terms. All of everyone's work done I respect and appreciate and thank them all including XDA
USB storage device not mounting with this kernel... No devices detected. I've tried stickmount and still the same thing... Can anyone please help? I've already ordered the WiFi adapter and I hope its going to work...
GXDA3 said:
USB storage device not mounting with this kernel... No devices detected. I've tried stickmount and still the same thing... Can anyone please help? I've already ordered the WiFi adapter and I hope its going to work...
Click to expand...
Click to collapse
Does this kernel not support native usb otg? I can't get it to read my usb flash drive with an otg cable it wont even read it... no option to mount?
llib01 said:
Hi thanks for continuous hard appreciated work.
Question did you get this working with the lineage Os 15.1 ROM the kernel part I mean?
Last question is the ROM you have posted here better than lineage one I'm using for this phone like in options or speed ,mods ,etc..
Please everyone do not take anything in wrong terms. All of everyone's work done I respect and appreciate and thank them all including XDA
Click to expand...
Click to collapse
The kernel is a modified lineageOS 14.1 kernel. The only difference is that mine supports the nethunter tools like HID attacks and external USB WiFi cards.
No rtl88xxau kernel modules
robnew said:
Instructions on installing Kali NetHunter for the LG K20 Plus. (MP260)
This is a modified LineageOS 14.1 arm64 Kernel modified for use with the Nethunter although its should work for any ROM.
I am going to assume that your device is rooted and has TWRP installed. Also since this is an arm64 kernel, you will most likely need to have a custom ROM installed. I am using AICP "aicp_lv517_n-12.1-UNOFFICIAL-20180216". You can download it from this thread https://forum.xda-developers.com/note-4/snapdragon-dev/rom-aicp-12-1-t3592312.
Once you have that done, Make sure you download the nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170211-0304.zip and then download the kernel I compiled from my github.
https://github.com/robnew/NetHunter_K20plus_Kernel
Flash them both from TWRP and you should be good to go.
THE KERNEL
The NetHunter kernel for the LG K20 Plus is based on the LineageOS 14.1 [LV517] kernel sources.
•SELinux enforcing, switches to permissive when requested by NetHunter app
•Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
•FIOPS IO scheduler as default IO scheduler, SIO available
•DriveDroid compatibility
•USB HID Gadget keyboard & mouse support (HID Attacks, Duckhunter HID Attacks)
•mac80211 packet injection support
•Additional drivers built in for the full Kali NetHunter experience
•Data partition encryption optional (may not be supported by custom kernels - encrypt at your own risk)
•Kernel module support, insert your own modules! (modprobe available in Kali chroot)
•CIFS, NFS available through included kernel modules
Enjoy.
Click to expand...
Click to collapse
I have used all the methods and yours was the last method and I am telling you it does not work for the rtl88xxau. I am trying to have this build within the kernel and I have done anything so far but not successful. The modules you have compiled are the ralink which you describe. I am having trouble building a kernel. I am trying to build a kernel with the drivers or rtl88xxau available but I am getting stuck at some point. Can you please tell me what version of linux os have you used to compile the kernel. I am trying to compile the kernel for the cm 14.1 with the rtl88xxau. thank you.
Small world.
robnew said:
Instructions on installing Kali NetHunter for the LG K20 Plus. (MP260)
This is a modified LineageOS 14.1 arm64 Kernel modified for use with the Nethunter although its should work for any ROM.
I am going to assume that your device is rooted and has TWRP installed. Also since this is an arm64 kernel, you will most likely need to have a custom ROM installed. I am using AICP "aicp_lv517_n-12.1-UNOFFICIAL-20180216". You can download it from this thread https://forum.xda-developers.com/note-4/snapdragon-dev/rom-aicp-12-1-t3592312.
Once you have that done, Make sure you download the nethunter-generic-arm64-kalifs-full-rolling-3.15.4-20170211-0304.zip and then download the kernel I compiled from my github.
https://github.com/robnew/NetHunter_K20plus_Kernel
Flash them both from TWRP and you should be good to go.
THE KERNEL
The NetHunter kernel for the LG K20 Plus is based on the LineageOS 14.1 [LV517] kernel sources.
•SELinux enforcing, switches to permissive when requested by NetHunter app
•Enabled USB (OTG) Atheros, Ralink, and Realtek WiFi drivers
•FIOPS IO scheduler as default IO scheduler, SIO available
•DriveDroid compatibility
•USB HID Gadget keyboard & mouse support (HID Attacks, Duckhunter HID Attacks)
•mac80211 packet injection support
•Additional drivers built in for the full Kali NetHunter experience
•Data partition encryption optional (may not be supported by custom kernels - encrypt at your own risk)
•Kernel module support, insert your own modules! (modprobe available in Kali chroot)
•CIFS, NFS available through included kernel modules
Enjoy.
Click to expand...
Click to collapse
Thanks so much for this. I was trying to figure out if I was gonna need to get to learn how to build a kernel, or if I was gonna need to try and edit one? I dunno what I'm doing, and even though I like the process of reversing that, I'm just a little tight on time right, now.