[KERNEL] [DEV ABOOT ONLY] [UNOFFICIAL] Boeffla-Kernel [KLTEVZW] [4/30/2016] - Verizon Galaxy S 5 Android Development

Note: I am not in any way a developer of the Boeffla-Kernel. I asked the developer, @Lord Boeffla, if it would be OK to post a modified version of his kernel on this forum. He agreed but indicated that he will not be providing support for his kernel on the SM-G900V and, as per his FAQ, he is not willing to take on any new Samsung models. Please do not ask him for help or request that he officially support the Verizon model.
Disclaimer: Install this kernel at your own risk. Neither I nor the kernel developers take any responsibility for any damage done by flashing or running this kernel and no support can be offered.
Requirements
A developer aboot
Custom recovery (I use TWRP)
Either a Samsung Stock Lollipop or CM13 based ROM
Root (to run the Boeffla-Config app)
Optional: FlashFire
Please make a full nandroid backup before flashing anything. If you're already using a custom kernel, use the Cleaner Script below. If you're using stock Samsung, make sure it is the latest version of Lollipop. Use custom recovery or FlashFire to flash. Afterwards, install the latest Boeffla-Config app.
Downloads
If coming from a different custom kernel, use this cleaner script before flashing the kernel:
Boeffla_Cleaner_Script_SM-G900V_V1.zip
For Samsung Stock Lollipop based ROMs:
boeffla-kernel-1.0-test-Samsung-g900v.recovery.zip
For Cyanogenmod 13 based ROMs:
boeffla-kernel-1.0-test-CM13.0-g900v.recovery.zip
For Resurrection Remix ROMs:
As of late komarov27 has been supporting a Resurrection Remix Boeffla Kernel compatible with the kltevzw in the comments section of the main S5 Resurrection Remix thread ( here for instance). Please see the thread for the latest version.
Regardless of which Boeffla kernel you flashed, install the latest Boeffla-Config app for tweaking goodness:
Boeffla-Config
Known problems
Some custom CM13 ROMS may produce stalls or boot-loops during bootup with the Boeffla Kernel, especially after cleaning the cache and/or Art/Dalvik cache. The ResurrectionRemix version of the Boeffla Kernel may fix the problem but not every CM13 ROM should be expected to work. Always make a full nandroid backup ahead of time.
Be careful with xposed as some have reported issues with modules that alter kernel options.
The original Boeffla Kernel thread for Samsung stock can be found here.
The original Boeffla Kernel thread for CM can be found here.
The official Boeffla Kernel site can be found here.
A special thanks to @Lord Boeffla for the kernel.

Reserved...

Cleaned cache and dalvik with RR and Boeffla and dont bootlooped... And i am using xposed, not notice nothing wrong...
Nsane457 said:
The original Samsung Boeffla Kernel thread can be found here.
Click to expand...
Click to collapse
Maybe this link are more accurate?
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062078

TioCareca said:
Cleaned cache and dalvik with RR and Boeffla and dont bootlooped... And i am using exposed, not notice nothing wrong...
Click to expand...
Click to collapse
Good to know. It always stalls for me on boot with RR if I wipe the dalvik cache. I expect many people won't have any trouble with xposed but it is still not advised.
TioCareca said:
Maybe this link are more accurate?
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062078
Click to expand...
Click to collapse
The link I gave was for the Samsung stock version but I've added this one for the CM version. Thanks.

Yes i see your point, the warnings are made...
The xposed problems are caused by modules that change kernel options, not xposed itself so is pretty safe to use with the right modules...
Maybe this for the stock version? Your link is for S3....
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062073

TioCareca said:
Yes i see your point, the warnings are made...
The xposed problems are caused by modules that change kernel options, not xposed itself so is pretty safe to use with the right modules...
Click to expand...
Click to collapse
OK. I'll adjust the warning.
TioCareca said:
Maybe this for the stock version? Your link is for S3....
http://forum.xda-developers.com/gal...ernel-boeffla-kernel-1-0-beta1-23-03-t3062073
Click to expand...
Click to collapse
Yes. Sorry about that. The link is updated.

No problem... Just trying to help... I will make some experiments with the kernel source code...

TioCareca said:
No problem... Just trying to help... I will make some experiments with the kernel source code...
Click to expand...
Click to collapse
That would be fine. :good: I have some experience with cross-compiling but none with Android. Sadly, the script used for building the Boeffla Kernel apparently didn't work with python3, gcc-5.*, or the version of perl I was using. I just got tired of installing different versions of my libraries and adjusting defaults.

I just updated the thread with a patched version of Boeffla-Kernel that works with ResurrectionRemix ROM, thanks to @j1gga84. It finally fixes the bootloop/stall problem I've been having.
Link to original post

Nsane457 said:
I just updated the thread with a patched version of Boeffla-Kernel that works with ResurrectionRemix ROM, thanks to @j1gga84. It finally fixes the bootloop/stall problem I've been having.
Link to original post
Click to expand...
Click to collapse
If BETA20 was RR fix what did BETA21 change?

Does this kernel support CPU oc?
Sent from my SM-G900V using XDA-Developers mobile app

jordash25 said:
If BETA20 was RR fix what did BETA21 change?
Click to expand...
Click to collapse
From here:
CM13.0 -- Version 3.0-beta21
12.04.2016
Update: Updated with latest official CM kernel commits as of 12.04.16, 8am CET
Update: Ramdisk of official CM13.0 build of 12.04.16
Click to expand...
Click to collapse

thrgk said:
Does this kernel support CPU oc?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes. Overclocking and underclocking. See here for config info.

Beoffla Kernel for Ressurection Remix ROM updated to boeffla-kernel-3.0-beta22-RR-kltevzw.zip.

Nsane457 said:
If coming from a different custom kernel, use this cleaner script before flashing the kernel:
Boeffla_Cleaner_Script_SM-G900V_V1.zip
For Samsung Stock Lollipop based ROMs:
Stable: boeffla-kernel-1.4-Samsung-g900v.recovery.zip
Click to expand...
Click to collapse
Hi there! thanks for the port, it looks amazing!
Quick question. I have installed the two files I quoted, and everything looks like is working fine (System, Xposed, etc). However, when I open the Terminal it tells me this:
Code:
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "/system/bin/sh"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "getprop"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "id"; caused by library "libNimsWrap.so" not found
[email protected]:/ $
I tried googling it and couldn't find a solution, but I know for sure it is the custom Kernel because I tried troubleshooting it and it only shows up with the custom Kernel (not even related to Xposed). Does this happen to you too?
Thanks again!

rauleeros said:
Hi there! thanks for the port, it looks amazing!
Quick question. I have installed the two files I quoted, and everything looks like is working fine (System, Xposed, etc). However, when I open the Terminal it tells me this:
Code:
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "/system/bin/sh"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "getprop"; caused by library "libNimsWrap.so" not found
WARNING: linker: could not load library "libNimsWrap.so" from LD_PRELOAD for "id"; caused by library "libNimsWrap.so" not found
[email protected]:/ $
I tried googling it and couldn't find a solution, but I know for sure it is the custom Kernel because I tried troubleshooting it and it only shows up with the custom Kernel (not even related to Xposed). Does this happen to you too?
Thanks again!
Click to expand...
Click to collapse
It mentions your issue on this thread.
I'll try to install and troubleshoot it tonight.

Nsane457 said:
It mentions your issue on this thread.
I'll try to install and troubleshoot it tonight.
Click to expand...
Click to collapse
You are amazing!
P.S. I followed what the said: move the libs that it asks for (libNimsWrap.so & then libcnefeatureconfig.so) to the /system/lib/ folder and change the permissions. Open the terminal.... And gone!

rauleeros said:
You are amazing!
P.S. I followed what the said: move the libs that it asks for (libNimsWrap.so & then libcnefeatureconfig.so) to the /system/lib/ folder and change the permissions. Open the terminal.... And gone!
Click to expand...
Click to collapse
Yeah. It seems to be caused by a line in the "init.environ.rc" script in the boot ramdisk. I'll look into fixing it later. For now the workaround is fine and either way it should be harmless.

Bootlooped on 5.0 AllianceRom Xposed. Don't have much information to give you besides it doesn't work. Unlocked the retail bootloader.

Dashaquavius said:
Bootlooped on 5.0 AllianceRom Xposed. Don't have much information to give you besides it doesn't work. Unlocked the retail bootloader.
Click to expand...
Click to collapse
Its for 6.0 roms only...

Related

[KERNEL][COΙ4 v1.05][5.1.1][TW] talexop - Note4 N910C Permissive

STOCK KERNEL FOR NOTE 4 910C (Exynos)
WORKS WITH 5.1.1 TW!!​
Code:
*** Disclaimer
This is a stock kernel. Please be aware that it is for 910C Exynos only.
I can not guarantee that it will work for other devices.
Use it at you own risk. If anything goes wrong I take no responsibility.
Introduction
This kernel is build from stock samsung C0H4 sources I wanted to keep it as stock as possible for people like me that are satisfied with the stock kernel, do not want OC, UV.
The Kernel is SElinux Permissive.
Click to expand...
Click to collapse
Description
This is the stock samsung kernel source, but changed the SELinux policy from enforcing to permissive. In the settings app, it still shows as "Permissive". Removed the restrictions from kernel source regarding rooting etc.
Click to expand...
Click to collapse
Install ALL IN ONE
If you have installed the stock firmware and you want a ROOT, BUSYBOX, INIT.D, Remove Knox, WIFI FIX Then DOWNLOAD ALL IN ONE
*******
-Install Twrp (Info - Download Latest)
-Reboot to Recover
-Flash ALL IN ONE throught TWRP which roots, installs busybox, removes Knox files, adds init.d support, and wifi fix
-Clear Darvik/Cache throught TWRP
*******
Click to expand...
Click to collapse
Install Just The Kernel
If you want to Install JUST the kernel which allows rooting to 5.1.1 download below "just kernel" version file and follow the steps below
-install Twrp. (Info - Download Latest)
-Reboot to Recover
-flash kernel
-flash SU zip file from getting root access (http://download.chainfire.eu/559/CF-Root/CF-Auto-Root-trelte-treltexx-smn910c.zip More info Here
-boot system and remove with titanium backup anything that has to do with Knox and security log.... (OR Use this to remove knox * thanks to agentdeep for pointing out)
-Change /system/build.prop ro.securestorage.support=false to fix wifi passwords...
Click to expand...
Click to collapse
Downloads
-ALL IN ONE Version 1.05 COJ5 RAMDISK * New Kernel 1.1 & More AGGRESIVE Ram fixes included (Thanks to @AndroidWars)
-ALL IN ONE Version 1.05 COJ5 RAMDISK * New Kernel 1.1 & SOFT version RAM settings same as v1.04
-Just Kernel Version 1.1 COJ5 Ramdisk
-ALL IN ONE Version 1.05 * New Kernel 1.1 & More AGGRESIVE Ram fixes included (Thanks to @AndroidWars)
-ALL IN ONE Version 1.05 * New Kernel 1.1 & SOFT version RAM settings same as v1.04
Just Kernel Version 1.1
OLDER Versions
-ALL IN ONE Version 1.04 * Updated ramdisk to COI4& more Ram fixes included
-ALL IN ONE Version 1.03 * Fixed Knox removal & Ram fixes included
-ALL IN ONE Version 1.01 - Mirror
-Just Kernel Version 1.0
Click to expand...
Click to collapse
Donate
Keep me motivated Click HERE
Click to expand...
Click to collapse
Sources
Kernel Sources
Click to expand...
Click to collapse
Thanks To/Credits
Code:
* Samsung
* Google
* wanam
* not-i
* All of you that support me thought the thread!
Trying... Will let you know! Thanks!
Trying now.. will update
Thanks
BRAVO........... worked flawlessly..... No hiccups... Thank you so much...... NEXT mission 'heading towards xposed' lol
Thank you very much talexop !!!!!!!!!!!!!!!!
trying this right away!
I hope you are back in building kernells for n910c as you did for galaxy s4
If this is successful, please post all knox related files that needs to be remove. Thanx!
hiimimtayaz said:
BRAVO........... worked flawlessly..... No hiccups... Thank you so much...... NEXT mission 'heading towards xposed' lol
Click to expand...
Click to collapse
+1
Good job OP!
Finally. ..
Trying
Thanks
Use this to remove knox http://forum.xda-developers.com/attachment.php?attachmentid=3038378&d=1417202593
Thanks!
thank you @talexop the only thing that has been changed was done to convert it to permissive kernel? Does the rest of the features remain stock as per the source code?
IT WORKS! THANK YOU SO MUCH
it's just there are few problems i am getting could you please help me solve them?
2-i cant install anything from Google Play
3-notifications comes back when dismmissed
i did clean install ,wipred cache dalcik and cache
working charm, thanks bro
This is strange ! This kernel is @not-i 's kernel for sweet ROM ! nothing new !
APCOtech said:
This is strange ! This kernel is @not-i 's kernel for sweet ROM ! nothing new !
Click to expand...
Click to collapse
Did you even test it?
I think the OP used not-i updater script only but he should be appreciated for his work for the new kernel coz root is working 100%
wireless lost setting after reboot, anyone having similar issue ?
Safar_Ibrahim said:
wireless lost setting after reboot, anyone having similar issue ?
Click to expand...
Click to collapse
+1 .... @talexop please advise...
agentdeep said:
Did you even test it?
I think the OP used not-i updater script only but he should be appreciated for his work for the new kernel coz root is working 100%
Click to expand...
Click to collapse
Yes I tested it and I just finished removing knox stuff , It is working fine .
I just mentioned what I got in TWRP that this is sweet ROM kernel !
BAYmustafa96 said:
IT WORKS! THANK YOU SO MUCH
2-i cant install anything from Google Play
Click to expand...
Click to collapse
No problem
APCOtech said:
Yes I tested it and I just finished removing knox stuff , It is working fine .
I just mentioned what I got in TWRP that this is sweet ROM kernel !
Click to expand...
Click to collapse
I don't want to argue with you, I did not even see any post from not-i that he has a new kernel.
As I said earlier, maybe the OP used not-i updater script and put the new boot.img (his new work) inside the zip... that is why we are seeing not-i when we install it!
Unless the OP and not-i is the same person.

[ROM] [DEV ABOOT] [UNOFFICIAL] VanirAOSP m6 [KLTEVZW] [Weekly-ish]

-- Begin copy-pasta template from one of my other unofficial build threads... please let me know if I miss updating something --
Note: I don't run this ROM personally, I really just built it. It shouldn't, but it may eat your cat.
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your
phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: When/how often are these built?
A: Less often than my CM13.0 build, but at least every week. Unlike my CM13.0 build, I don't use this ROM so I won't be doing a "does it boot" check before uploading. Please tell the entire thread if one day's build doesn't work properly.
Q: Why did you do this ROM next instead of ______?
A: #1, it was easy. Vanir doesn't require me to make a new branch to change file names and text lines in the makefiles from "cm" to XXXX. #2, Vanir holds a special place to me for having device trees that worked for our S5 at least through Lollipop -- they allowed me to make my own CM builds. #3, I used it back in the day and they seemed pretty tight.
Q: Can I get help with something?
A: I have a full-time job and travel a lot. I'll try to jump in and answer some questions, but there is a lot of info out there for you to learn on your own. Aside from you having a vzw-variant, most of the details are standard KLTE.
Click to expand...
Click to collapse
Recovery:
The standard KLTE TWRP 3.1.0-0 should mostly work, but MTP doesn't work for any klte* variant using it.
I prefer KToonsez's 2.8.6-based Recovery. It's older, but MTP works.
There are Unofficial 3.*.0-* recoveries available by @jcadduono. I find that these don't support decryption properly, which I find to be mandatory.
Like many other devices, the .zip files can be flashed in a recovery. The .tar.md5 files can be flashed in ODIN. The .img files can be flashed using Flashify, a TWRP recovery. You can even get an .img file from a .zip or .tar.md5 if you just open it up.
If you use adopted storage then things get odd. The latest recovery by @jcadduono MAY support adopted storage if you don't encrypt userdata (I personally know that TWRP handles adopted storage for jflte and d2), but I do use encryption so I don't use that recovery. It may be that you only see /data/media/0 -- if so, I find that using Flashify for each nightly is the most straightforward way to update, but you could always manually copy to /data/media/0 before rebooting to recovery. This is a standard Marshmallow and TWRP thing.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. Please note that some have reported that you cannot flash these after the aboot unlock; If you cannot flash the PB1 modem/non-hlos it shouldn't cause any big problems.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
Various Vanir threads recommend SlimGapps, OpenGapps, or a Gapps packaged by DHO (the Vanir main developer). If you use OpenGapps, make sure to use an 6.0 version for ARM architecture. Like with all Gapps selections, they're all pretty much the same with the differences being which apps are packaged and what versions are packaged.
OpenGapps
SlimGapps
DHO's Gapps. These are a little bit older.
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
I'll build at least once per week, at least until the RR team picks up the torch. Once the build is complete, I upload it to my AFH account.
VanirAOSP m6 KLTEVZW weekly-ish
Click to expand...
Click to collapse
Does/Doesn't Work:
Everyone that gives it a shot needs to let the thread know.
Click to expand...
Click to collapse
Thanks:
Everyone on the Vanir and CM teams. This is 99% of their stuff with just a couple tweaks to make it build, (hopefully) boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r22 (prior to 20160406 build)
Android Version: 6.0.1_r24 (20160406-present build)
I forgot something. I know I did. I'll try to update this post sometime.
More things...
Source
In order of importance:
VanirAOSP github: https://github.com/VanirAOSP
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse
Man, you're awesome. Glad to have someone like you to port all these rims. ***roms oh my god
Thanks for turning me in a flashing junkie again... Lol, great work... Now just miss PacMan rom, Dirty Unicorns and AOKP...
Running smooth with Vanir..
Thanks haggertk!!
Thanks again! I love how smooth and stable it is. Not too much mod bullcrap, and I get my WiFi on notifications.
Sent from my SM-G900V using XDA-Developers mobile app
Runs smooth, what happenned to this thread?
Is this ROM still supported? Anyone know what's going on with it?
MortimerR said:
Is this ROM still supported? Anyone know what's going on with it?
Click to expand...
Click to collapse
Check here..
http://forum.xda-developers.com/showthread.php?t=3355159
Sent from my SM-G900V using Tapatalk

[MM 6.0] [Nougat 7.0] Kali Nethunter for Nexus 5x/bullhead [INSTALL] [UPDATE 09/28]

Updated as of 09/28/2016
Rebuilt Kali Nethunter Installers from Sept. 28th source code pull.
Update - 10/03
Reuploaded ALL zips and Relinked in Post, So all links should now be working.
Since the current version of Kali Nethunter (3.0) doesn't currently have an official build for the Nexus 5x (bullhead), I decided to do a build for it.
I created packages for Android 6.x (Marshmallow) and for Android 7 (Nougat). One has the full-chroot and one has the minimal-chroot.
I'll be creating updated builds once a week, both complete install zips and update zips.
I have installed and tested the marshmallow-kalifs-full version running Blissrom and CM13, but I have not had a chance to test the nougat versions yet.
If you have any issues, or questions post it and I'll try and get back to you asap.
The offical Kali Nethunter webpage is located here: https://www.kali.org/kali-linux-nethunter/
Kali Nethunter Source: https://github.com/offensive-security/kali-nethunter
Marshmallow builds
-- Full --
nethunter-bullhead-marshmallow-kalifs-full-20160928.zip (AndroidFileHost) (771.7mb)
Code:
md5: a7334c498a098e808ddce428d22f62d1
-- Minimal --
nethunter-bullhead-marshmallow-kalifs-minimal-20160928.zip (AndroidFileHost) (195.2mb)
Code:
md5: 49e82dfdd937c0623d5554d51cef076b
Nougat builds
-- Full --
nethunter-bullhead-nougat-kalifs-full-20160928.zip (AndroidFileHost) (771.7mb)
Code:
md5: a7334c498a098e808ddce428d22f62d1
-- Minimal --
nethunter-bullhead-nougat-kalifs-minimal-20160928.zip (AndroidFileHost) (195.3mb)
Code:
md5: e45062dad1da603fa546aa09b101dc7f
Uninstaller
nethunter-uninstaller-20160901.zip (AndroidFileHost) (1kb)
(mirror)
Code:
md5: 8df3e20510084db7cab0e8ee670c7331
Delete
What is the difference between a full and a minimal package? Will the minimal package install over my existing ROM ? I'm using official Nougat, systemless root.
I am also little bit confused between the minimal and full packages. Can anyone explain what's the basic difference in both of them?
Installed the full package on stock nougat. Works fine, had to install the app separately and the nh-terminal too.
What exactly is functionality of this on 5X? Do I need seperate dongle to do penetration, etc. ?
I think you will always need a separate dongle for penetration ?
Sent from my Nexus 5X using XDA-Developers mobile app
What is the difference between a full and a minimal package?
Click to expand...
Click to collapse
The Minimal kalifs/chroot is basically the barebones Kali OS without any of the extra software pre-installed, which is better if you want to pick and choose which meta-packages to install.
And of course the Full kalifs/chroot is the normal Kali OS with all the default software/tools installed.
Will the minimal package install over my existing ROM ? I'm using official Nougat, systemless root.
Click to expand...
Click to collapse
None of the Kali Installs overwrites any rom. It is install alongside whatever ROM you are running.
I have tested the Full Nougat Nethunter and it worked just as well as the Marshmallow build, so I don't foresee you having any problems..
What exactly is functionality of this on 5X? Do I need seperate dongle to do penetration, etc. ?
Click to expand...
Click to collapse
It all depends on what you are trying to pen test... It would be better to have a dongle but it isn't an absolute must. Before I had a dongle, When I had my Nexus 5 I used to tether it to my laptop or tablet and use the wifi adaptor on that device as my second Network Interface.. I'm not sure if that will work on the 5x but it's an option.
You can still do a decent amount of Wireless Pen Tests/Exploits with the onboard network adapter but you may end up using Cellular Data if you are attempting certain MiTM attacks or HostAPd ... I know for sure if you want to use the Kali-Linux Evil Wireless Access Point you will need a dongle, but I have heard that you can use Cellular Data with it by tweaking the config file.
Can you please build nougat version with full Chroot for hammerhead? (there are already 3 nougat Roms and a couple of nougat kernels for hammerhead)
nihad15 said:
Can you please build nougat version with full Chroot for hammerhead? (there are already 3 nougat Roms and a couple of nougat kernels for hammerhead)
Click to expand...
Click to collapse
Yeah, I'll compile it now.. I'll post a link to the zip soon as its done
Shiestie said:
Yeah, I'll compile it now.. I'll post a link to the zip soon as its done
Click to expand...
Click to collapse
Thanks
Sorry, if this may sound stupid. Is this consider as a multirom flashing? If it's suppose to run side by side with my existing cm13 rom. Do i need to be running the stock cm kernel?
Eugene729 said:
Sorry, if this may sound stupid. Is this consider as a multirom flashing? If it's suppose to run side by side with my existing cm13 rom. Do i need to be running the stock cm kernel?
Click to expand...
Click to collapse
Edit: Was I drunk or something I answered a completely different question.
The primary should have Cm13 with the Multirom mod (forgot it's name but you can install it through the Multirom app)
the secondary ROM's kernel will be overwritten by Kali's kernel.
combined with preceeding post.
Eugene729 said:
Sorry, if this may sound stupid. Is this consider as a multirom flashing? If it's suppose to run side by side with my existing cm13 rom. Do i need to be running the stock cm kernel?
Click to expand...
Click to collapse
It's more like the xposed framework.. It installs a couple pen testing apps, as well as the Nethunter App and a chroot filesystem so you can actually run the Kali Linux OS via the VNC App or through the Terminal if you don't want to use a GUI. But you don't really need to VNC into the OS, the Nethunter app has most of the stuff you'd want in it, BeeF-XSS, Metasploit, SSH, MITMf, Apache2, etc...
as for the kernel... I actually built all the zips with a working kernel in them.. I'm not sure if the cm13 stock kernel will work with nethunter, but a lot of other kernels do, when I had a nexus 5 I used ElementalX kernel with nethunter... If you'd like a nethunter install zip without a kernel built in, just let me know and I'll build one without..
nihad15 said:
Can you please build nougat version with full Chroot for hammerhead? (there are already 3 nougat Roms and a couple of nougat kernels for hammerhead)
Click to expand...
Click to collapse
Alright, so good news and bad... I was able to build nethunter for hammerhead running nougat.. BUT, they do not currently have a nougat kernal for hammerhead in the repo. So I'm going to have to compile one from the original Nougat kernel for hammerhead from Google... I started syncing the source so I'll hopefully have a working kernel for it by tomorrow evening.. If there are any third-party nougat kernels for hammerhead like franco, elementalx, etc... they should work just fine until I build one specifically for Nethunter for hammerhead nougat.
nethunter-hammerhead-nougat-no-kernel-kalifs-full-20160904.zip
Shiestie said:
they do not currently have a nougat kernal for hammerhead in the repo. So I'm going to have to compile one from the original Nougat kernel for hammerhead from Google... I started syncing the source so I'll hopefully have a working kernel for it by tomorrow evening.. If there are any third-party nougat kernels for hammerhead like franco, elementalx, etc... they should work just fine until I build one specifically for Nethunter for hammerhead nougat.
nethunter-hammerhead-nougat-no-kernel-kalifs-full-20160904.zip
Click to expand...
Click to collapse
Google didn't release (nor kali) a kernel for hammerhead-nougat.
and don't I need kali kernel to be able to use the wifi dongle?
(Oh btw thanks for the zip)
nihad15 said:
Google didn't release (nor kali) a kernel for hammerhead-nougat.
and don't I need kali kernel to be able to use the wifi dongle?
(Oh btw thanks for the zip)
Click to expand...
Click to collapse
The kernel is compiled into the nougat firmware updates, I'll pull it from source n build it with what's needed to run nethunter, without a kernel chroot nor kexec would work so pretty much none of kali will work..
Shiestie said:
The kernel is compiled into the nougat firmware updates, I'll pull it from source n build it with what's needed to run nethunter, without a kernel chroot nor kexec would work so pretty much none of kali will work..
Click to expand...
Click to collapse
Well, Good luck then.
monitor mode
can i use monitor mode or injection with this??
moonjy1120 said:
can i use monitor mode or injection with this??
Click to expand...
Click to collapse
on external cards: yes
internal card: no

[KERNEL][HAVOC-OS-2.2 - 2.4]Coconut Kernel with Nethunter Support[HolyDragon Source]

Coconut Kernel for HAVOC OS - With Nethunter Support
Code:
***I'm not responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
This kernel is tested on HAVOC OS 2.2 - 2.4 PIE. This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
The kernel should also work on every ROM that Holydragon kernel supports.
Requirements
Oxygen OS 5.0.8 firmware is required. The wifi adapter wont work on older firmwares. Those who are using Havoc OS would most probably be on 5.0.8 firmware so this is just a remainder for others and/or anyone who have trouble making this work.
How to install
Make sure that you are rooted with magisk/supersu/any superuser
Download kernel from attachment and flash in TWRP Recovery
Reboot and download any terminal app like Termux
Plugin the USB Wifi card and open Termux
Type the command su
Then type ifconfig wlan1 up
This is how you can test whether it works or not
The kernel works fine with Nethunter as well as other chroot applications like Linux Deploy.
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Credits
@HolyAngel for HolyDragon Kernel Source
Source
https://gitlab.com/HolyAngel/OP3
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Victroid said:
Thanks sir, this weekend, I test and i say you if I have a problem, but surely not, at this moment it is the kernel that I have but without the controller. I want to learn to compile the kernel on my own so that, in case HolyAngel updates the kernel, it dosn't depend on your work.
Click to expand...
Click to collapse
https://forum.xda-developers.com/an...erence-how-to-compile-android-kernel-t3627297
Follow the tutorial above for kernel building.
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.?
DoN LoUhI said:
@fredrickz
Any future build for stock oos pie like your Oreo one, it was perfect man thank you for your efforts regard to the community.
Click to expand...
Click to collapse
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
fredrickz said:
Stock oos pie source isn't available yet man. I can build pie version from holydragon sources. I'll compile one when stock sources arw available too.
Click to expand...
Click to collapse
Fair enough, thank YOU:laugh::good:
You explicitly mention this:
This is built from HolyDragon Source with added nethunter support/USB Wifi Adapter Drivers and monitor mode/packet injection
Click to expand...
Click to collapse
And the kernel source points to:
https://gitlab.com/HolyAngel/OP3
Click to expand...
Click to collapse
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Note:- This kernel does not need any module to be inserted as all wifi drivers are compiled inline. So no need to insmod/modprobe
Click to expand...
Click to collapse
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
anupritaisno1 said:
You explicitly mention this:
And the kernel source points to:
This can only mean 2 things:
1) you've merely taken holydragon kernel source and renamed it as your own or
2) you're actually breaking the GPL here by not releasing your changes
So which one is it?
And this leaves me no doubt that the second is very likely the case:
Click to expand...
Click to collapse
I dont want to break any gpl.. the thing is that all my changes are local. Im not used to github. This kernel and all others i posted werr just for my own use. I have been using @ZaneZam kernel for oneplus3. But the Oreo kernel wasnt working fine. Thats the reason i tried to compile one my own. I shared it with a friend of mine some time ago and he insisted that i should post it so that others may also benefit. The kernel i posted doesn't have tonnes of feature list because i mostly stick to stock. I just added the wifi drivers and was using them. My friend asked me to add support for DriveDroid and i just did that. I don't know much about git and didnt have time to learn.
If this is against the rules then maybe ill post the source later. Im currently out of town.
for now if you want to know what changes i did,
1. Prepare the kernel for standalone build (except holydragon kernel)
2. Added just the wifi drivers mentioned in the nethunter wiki. I didnt add support for usb Bluetooth or sdr.
3. Added support for DriveDroid from official post in xda making changes to adapt the code to 3.18 kernel.
4. Added a fancy name to the kernel.
5. Published it.
DoN LoUhI said:
@Fredricks
It would be more than appreciated if you could add support for HID brother. Thanks:crying:
Click to expand...
Click to collapse
Im out of town bro. Ill add it when i reach home.
fredrickz said:
Im out of town bro. Ill add it when i reach home.
Click to expand...
Click to collapse
Very thankful, have a good time..:good:

[KERNEL][NETHUNTER] Coconut-Kernel (Lineage 18.1 - Nethunter Support)(Oneplus 3/3T)

Coconut Kernel for LineageOS 18.1 - With Nethunter Support
Code:
***I wont be responsible for any problems that might occur flashing this kernel or what you do with the kernel support***
​
Just flash the kernel from recovery for supported ROMs.
You can use this kernel for Nethunter functions and other chroot applications like Linux Deploy.
HID and DriveDroid patches are also included.
Note:- The USB Wifi adapter firmware collection is also included with the zip and will be automatically installed. No need to use additional magisk module for installing firmwares.
Source
https://github.com/xpz3/android_kernel_oneplus_msm8996-2
hi, does it work with PE A11? thanks
mohawahba said:
hi, does it work with PE A11?
Click to expand...
Click to collapse
This is compiled from los 18.1 kernel source with modifications for nethunter. I don't use custom rom much, so i don't know about specific features that a custom rom like pe have. If the android version is same, it should work, but if the rom has any special feature that's dependent on the kernel it may or may not work. You can try flashing and see. If it doesn't work, just go back to the old kernel.
Hi!
So i have some problems with getting my wifi-adapter working, can u help me?
So i have Lineageos 18.1 installed om my op3t, latest nt from kali website and your kernel. Using a RTL8811AU, i can see it with lsusb and i cant find any errors in dmesg. I have tried to change otg adapter and i have tried with y-cable. But still no luck... Is there anything else i can try?
thx for help.
jobsdonn said:
Hi!
So i have some problems with getting my wifi-adapter working, can u help me?
So i have Lineageos 18.1 installed om my op3t, latest nt from kali website and your kernel. Using a RTL8811AU, i can see it with lsusb and i cant find any errors in dmesg. I have tried to change otg adapter and i have tried with y-cable. But still no luck... Is there anything else i can try?
thx for help.
Click to expand...
Click to collapse
Whats the issue you're facing?
@fredrickz
Thank you for this kernel
Just a question:
which nethunter version do I have to install?
On the kali.org page are nethunter releases for pie and ten. But not for eleven - this kernel is for eleven.
Do I install a eleven Custom ROM and then the nethunter PIE version and then this nethunter kernel?
fredrickz said:
Whats the issue you're facing?
Click to expand...
Click to collapse
I have the same problem with TP-LINK TL-WN722N (RTL8188EUS) - it looks nice in lsusb, no problems are reported in dmesg, but no wlan1 device ... Do i miss something?
nadastry said:
@fredrickz
Thank you for this kernel
Just a question:
which nethunter version do I have to install?
On the kali.org page are nethunter releases for pie and ten. But not for eleven - this kernel is for eleven.
Do I install a eleven Custom ROM and then the nethunter PIE version and then this nethunter kernel?
Click to expand...
Click to collapse
Flash generic arm64 installer, then this kernel
Which toolchain do you use to build your kernel?
HI
I have flashed your kernel,but when I try to use rucky,it Pop-up ”kernel not supported!“
How can I fix it?
jlock. said:
HI
I have flashed your kernel,but when I try to use rucky,it Pop-up ”kernel not supported!“
How can I fix it?View attachment 5895271
Click to expand...
Click to collapse
fixed the problem,just need to flesh agian
Any solution with missing wlan1 adapter? HID also doesnt work. OnePlus3T + LineageOS 18.1 + NetHunter Lite ARM64 + Kernel
lemongrass1717 said:
Any solution with missing wlan1 adapter? HID also doesnt work. OnePlus3T + LineageOS 18.1 + NetHunter Lite ARM64 + Kernel
Click to expand...
Click to collapse
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
XDrz said:
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
Click to expand...
Click to collapse
Official nethunter requires android 10, last official oxygenOs is android 9 but the only available lineageOs for op3t is 18.1 on android 11. Probably Im doing something wrong but I still couldn't make wifi adapter work
XDrz said:
wow! still active people here! are you chinese? i'm planing to rebirth my old op3. does this kernel wifi driver have problem? maybe you can try offical nethunter for op3
Click to expand...
Click to collapse
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
lemongrass1717 said:
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
Click to expand...
Click to collapse
KernelSu is a new root solution for android kernel, there shows some docs about kernel source compilation and module integration. I've tried several times, not so hard but so messy,lots of trivial details(such as adding lost source, changing argvs for compiler.....) you should search for solutions and solve.
Building Kernels | Android Open Source Project
source.android.com
How to build KernelSU? | KernelSU
A kernel-based root solution for Android GKI devices.
kernelsu.org
lemongrass1717 said:
Seems missing build-in driver is a culprit of non working adapter. Is there an actual guide how to compile kernel from source? I could try to add driver to kernel and recompile it.
Click to expand...
Click to collapse
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
yesimxev said:
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
Click to expand...
Click to collapse
Followed you guide:
1. Downloaded kernel source
2. Patched it with https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch
3. Getting Error on compile
I also tried to add this drivers manualy to kernel https://github.com/aircrack-ng/rtl8188eus and run compile. Seems it compiled OK but on TWRP I get Unsupported Device Error
yesimxev said:
Here's my guide.
Since this kernel is already a NetHunter patched, I recommend clone this post's source, so you don't need to start from scratch. If it's kernel 3.x, I usually have to nuke the rtl8xxxu folder and apply this: https://gitlab.com/kalilinux/nethun...d-rtl8xxxu-with-rtl8188eus-drivers-3.18.patch, because the patch from 4.x (adds only rtl8188eus) is for a newer base driver.
You can also add rtl88xxau if you're there, and if you want: https://gitlab.com/kalilinux/nethun...add-rtl88xxau-5.6.4.2-drivers-3.18-h990.patch or https://gitlab.com/kalilinux/nethun...3.10/add-rtl88xxau-5.6.4.2-drivers-3.10.patch
Click to expand...
Click to collapse
Nevermind. I fixed it and re-compiled the kernel. Seems it fixed problem with adapter visiibility. Thanks again for the awesome guide.
lemongrass1717 said:
Nevermind. I fixed it and re-compiled the kernel. Seems it fixed problem with adapter visiibility. Thanks again for the awesome guide.
Click to expand...
Click to collapse
Awesome! I mean if you want to use the same kernel, and just adding some patches, clone the already existing NH kernel source. Nice

Categories

Resources