Has anyone made a Nethunter Kernel? - ASUS ROG Phone II Questions & Answers

Has anyone made a Nethunter Kernel for the ROG Phone 2? I've done some searching but haven't found one yet...
I know you can pretty much install the Nethunter system on top of any rooted device/ROM, but without a kernel built specifically for the device you won't have Monitor Mode, Packet Injection, HID Mode, Bluetooth RFCOMM, etc...
I've tried looking through the Nethunter documentation for porting the kernel to a new device, but it's all way over my head since I've never don't any custom kernel work. I'm sure for someone who's done custom kernels before it would be a piece of cake, as the documentation seems pretty extensive.

Related

q for the devs.

i run linux at home but am by no means an expert, i was wondering if anyone has ever tried to incorperate dkms into android. it would be great to be able to change drivers in a kernel that is already on your phone. like voodoo sound. with new versions coming out all the time some kernel builders get the updates out faster than others, some kernels may work better on one phone or another but not include newest drivers supercurio is putting out.
would it be possible to make something like dkms compatable with android?
and if not where can i find information about compiling my own kernels for android?
DKMS is generally used for things like VGA drivers.. tried and true technologies... Legacy stuff... In the mobile world, the hardware of today is not used tomorrow. There are Kernel Modules (KO) files, but they are not DKMS. DKMS is used more for generic building. KO files load slower then standard kernel files.
When building for a mobile platform you always want the latest, greatest kernel, all manditory functions included, all options made as modules, and all others excluded. DKMS is used when you reuse the same hardware or functions over and over again. DKMS is basically for legacy use. You build something once and never have to build it again.
I dont' think it will make it's way onto phones until it's practical.

Budding dev needs some help

Hello all. I've recently been trying to get into Android development, more specifically Kernel development. I've played around with some kitchens and looked at the GB kernel sources from Samsung and tweaked it around.
Previously I previously learned Java to a point where I can put basic lines down and also more advanced stuff but with a bit of help here and there.
I have one question though, what would be the recommended path for creating an ICS Kernel. My plan is to start of with something "stock" and build up but I'm not quite sure what to consider stock seeing as the S1 never got ICS officially. Would I have to use CM9's Kernel sources and if so where do I acquire them.
I also have a good understanding of Ubuntu and its terminal and have a functional idea of what I'm doing there.

[Kernel] Shield Portable Kernel Development [Incl. Guide]

Welcome to the first custom kernel for the KitKat Shield.​
This thread is for the development and building of the Shield Portable kernel.
This is not intended to download a build, post issues, and return when fixed.
Kernel Source:
https://github.com/StarKissed/starkissed-kernel-roth
Kernel Downloads:
https://goo.im/devs/playground/shieldroth
The kernel can be built using the commands below or the included script.
Code:
make tegra11_android_defconfig -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make tegra114-roth.dtb -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
make -j$CPU_JOB_NUM ARCH=arm CROSS_COMPILE=$TOOLCHAIN_PREFIX
App & Donations:
StarKissed [SKU] on Google Play allows you to configure many of the options provided by this kernel. Issues or comments about the app can be posted at the XDA StarKissed app thread
Donations are not being collected through the forum. If you would like to donate, you may do so through StarKissed [SKU] on Google Play by using the donate options located in the top right (the green dollar bill guy).
[Kernel] Shield Kernel Development
The included ramdisk is for update 98. If you are on 72, this will most likely result in a bootloop. Using the 72 ramdisk will not work with this kernel, as the source is specific to "OTA 5" according to the Nvidia gitweb.
I recently updated the source and changed a few commands that may explain why current source resulted in non-working builds. I will be testing builds soon and then begin modifying the kernel once the core build is verified working.
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
rylen said:
Nice, I hope there will also be an overclocked kernel for 4.4. I know it's silly but I miss the 4.3 overclocked kernel.
Click to expand...
Click to collapse
All the code is there, it just loops. I'm not sure what's going on with it. The shield tablet version works.
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
bakageta said:
Quick question. Any chance you could update the usb ethernet drivers in this? Specifically, I'm suffering from this bug on an ASIX 88772 on the official kernel, and it seems their driver is rather out of date. Thanks, and keep up the good work!
Click to expand...
Click to collapse
Won't do much good until it boots
True enough, just thought I'd bring it up since it's a fairly easy fix. In the meantime, I threw together a stock kernel with an updated driver to get by. I had one problem after another with the latest official driver, but the good folks at LKML had already put some work in on v4.1.0 several years ago. Using drivers/net/usb/asix.c and usbnet.c from the 3.4.106 source built without problems.
Beginning to think I may have to settle for building against the full source on this one. It boots fine when doing that, but not built alone. The shield tablet builds fine alone, so there's no explanation for it.
you are going to make a new build of your kernel? if you need help with the tests i can help.
YamazakiRobert said:
you are going to make a new build of your kernel? if you need help with the tests i can help.
Click to expand...
Click to collapse
Things are a bit crazy, but once I can get all of the changes fixed up and it'll build clean, I'm going to try to run it over night.
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
bakageta said:
Slightly off-topic, but I'll ask you since you're the only other person I know building a shield kernel. I built nvidia's kernel, changing only the two drivers associated with my ethernet, but for some reason console mode has stopped working now. Have you ran into a similar problem? Plugging HDMI in pops up the selector, but clicking on console mode doesn't do anything - it just stays on the selector screen.
Click to expand...
Click to collapse
It shouldn't be related. You may need to check the proprietary drivers. I believe HDMI is one.
Didn't bother to find out what the problem was, it just stuck around because I was doing dirty builds as I tested. Once I got a few other tweaks and had some time, I did a clean build and it resolved itself. Did you manage to get your kernel booting when building it by itself? I'm sure I'm doing something wrong there too, but I've been grudgingly building the entire device, since that at least works reliably.
What is so special about this kernel compared to stock ? goodjob already btw, you're one of the few who actually have a kernel
It's really sad how not much development is going on, it's such a good device there is only like 1 release at the original section :/

help with gamepad support and loading xpad.ko

Hi all,
I have a rooted sm-t810 running stock marshmallow kernel 3.10.9.8374498 and I have been trying for a long time to add support for my xbox 360 wireless dongle and controllers.
I read a lot online about it and it seems that I need to load a specific module (xpad.ko) that is not available by default in my kernel.
However I have no idea where to find one that is compiled and compatible with my kernel and I have absolutely zero experience with compiling the kernel and/or the module from source, I wouldn't know where to begin or what to do about it.
From what I understand I should download the source of my kernel in a linux desktop, compile the module in it, copy the compiled module to my decide and run insmod it, but again, I have zero experience in all this.
Could somebody help me by giving me the compiled xpad.ko for my kernel?
If not, could you tell me step by step what should I do it to do it myself assuming im a total ignorant in kernels,modules, their compilation, the specifics about android, and everything around it ?(before yesterday I didn'teven ever rooted my tablet )
Thank you in advance if anybody is willing to help!
Cheers,
Mastro

Compiling a kernel with usb-hid support for lenovo k3 note

Hi Everyone !
I am a noob here and in the android kernel space too .
I have seen this USB-HID project here : https://github.com/pelya/android-keyboard-gadget and seen many kernels for the same, however there isn't any for lenovo k3 note and in general for any mediatek devices ( not sure about this one though ).
Coming to the point, I won't be asking this question if I knew exactly what to do here.
Although the github mentions how to compile custom kernel and I did see a few videos on how to create a custom kernel ( which were pretty good to say the least ).
However I don't understand which kernel source to choose and all that cause , in the github repo it gives an example for nexus device and then say that "change them for your device accordingly.".
So, for my lenovo k3 note what all do I have to change "accordingly" ?
Like in the first line it mentions
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8
and then
Code:
git clone https://android.googlesource.com/kernel/tegra.git
So , how does it change for my device ?
I know that my device has octacore ARM processor, so arm thing should remain the same , right ?
What about the tegra thing, googling it finds me that its the nvidia processor but mine is mediatek, so that should change "accordingly" , but then again change to what ?
Sorry, for asking such noobish questions, I know there are great people out here with way better expertise than a noob like me and so am here.
I don't fear experimenting on my phone.
I did somewhat got stuck in a boot loop a few days back and got to use SP flasher to get it runninng again, I installed AOSP extended on my k3 device alongwith twrp.
I was trying to install nethunter and although it got installed but it's hid device wasn't showing up ( perhaps that needed the correct kernel to get it working ).
Thanks guys/gals.
Aniket
P.S. I am not someone who wants to get the work done from you guys, I am ready to get my hands dirty. Just guide me, how to proceed with that and I will comply :angel:
I'm in the same boat but with aLenovo P2

Categories

Resources