This is the edit to make modules work in the new kernel you must make the edit in the config.gz, tgen recompile the kernel with the new config
ACTIVATING MODULE LOADING SUPPORT IN THE KERNEL
Module loading support is previously disabled in the kernel, if we want to load modules in the kernel we have to enable it:
edit .config file and set: CONFIG_MODULES=y
We have the new ics, but no overclock or webtop without dock, and some other issues that tge older roms have. And its not because the new leaksare locked. Someone is just lazy or ignorant. So here it goes
You will need alot of free space 100GB or more of free space NO JOKE.
First go here: http://source.android.com/source/initializing.html
You may want androids kernel or cyanogens
androids kernel: http://android.git.kernel.org/
$git clone git://android.git.kernel.org/kernel/common
We check which branch we have downloaded: $git branch it shows * android-2.6.27, not the one we are searching for:
To list all remote available branches: $git branch -r
This is only refernce the kernel number for the bionic is up to 3.0 so when you git branch-r choose one for the bionic
$git checkout --track -b android-goldfish-2.6.29 origin/android-goldfish-2.6.29 $git branch
Cyanogens Follow all steps and restart computer then go here: http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
After you have installed everything you are ready to create a complete distro from scratch.
Now go to adb and pull your working config.
adb pull /proc/config.gz
$gunzip config.gz # uncompressit. $cp config .config # renameitinto.config
Now you can edit .config file the way it suits you the most.
But really all we want is the modules for overclock and symsearch to be compiled for our new kernel
CROSS_COMPILE environment variable stores the path to the arm cross compiling toolchain. I use the one which comes with android source code.
$ARCH=arm CROSS_COMPILE=/path/to/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make
Executing make will build the kernel.
Last lines will show:
Kernel: arch/arm/boot/Image is ready Kernel: arch/arm/boot/zImage is ready
So we have obtained Image and zImage kernel binary files.
ACTIVATING MODULE LOADING SUPPORT IN THE KERNEL
Module loading support is previously disabled in the kernel, if we want to load modules in the kernel we have to enable it:
edit .config file and set: CONFIG_MODULES=y
$ ARCH=arm CROSS_COMPILE=/path/to/mydroid/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make
I am asked about some options when executing make. I ask yes for module related options.
After compiling I see several modules have been built.
MODPOST 6 modules CC drivers/video/fb_sys_fops.mod.o LD [M] drivers/video/fb_sys_fops.ko CC drivers/video/syscopyarea.mod.o LD [M] drivers/video/syscopyarea.ko CC drivers/video/sysfillrect.mod.o LD [M] drivers/video/sysfillrect.ko CC drivers/video/sysimgblt.mod.o L drivers/video/sysimgblt.ko CC drivers/video/vfb.mod.o LD [M] drivers/video/vfb.ko
Ok so now we have a kernel that supports modules, but we still need the overclock.so or opptimizer.so compiled for this kernel. This is wete I stop because I dont have any of those modules and this was merely for information really. To get someone to compile our kernel for modular support.
I'm not even sure how Motorola phone devs even get the option to recompile the kernels seeing as how the locked bootloader doesn't let us modify the stock kernel in any way.
If/when we get Kexec, I could see this being an option, however.
It is easy to compile the kernel and edit it and even put it to the motorola droid.
There is actualy 2 ways not just 1.
1. first use follow steps compile kernel and apply it to a boot.img using an android-kitchen.( google android-kitchen) Once you allpy it to a boot.img we can flash in recovery or use an rsd lite and flash using the .xml just replace the boot.img with the modified kernel boot.img. The boot.img for the .875 is 8.3 megs as is the .902 boot.img.
2. use any kernel updater from kuash in recovery wich will replace the current zImage with the new kernel compiled in the steps you just followed.(google android any kernel updater)
So Like I said why hasnt anyone compiled a new kernel.
The Motorola Droid has an unlocked bootloader. The Droid Bionic does not. That is why kernel development barely ever happens on Moto devices.
Feel free to try to flash unsigned images to your Bionic. Let us know how that goes.
I'm a developer of China, and my mobile type is XT1079(MOTO G 2014), I tyied to compile a linux kernel to replace the origin kernel, and I used the project provided by Motorala in github(https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-LXB22.46-28).And[/url] I edit the config file based on the "furnace" kernel config.
After I finishing compiling and replacing my kernel. I found the wifi doesn't work, there is a wifi.ko will be loaded, so I downloaded the opensource drvier(https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-wlan-prima/tree/MMI-LXB22.46-28[/url]), and compiled it.
But it doesn't work, I can get the same info from the kmsg log with the origin wlan.ko, but in wifi configure page it will be blocked and show no AP.
Also, the size of wlan.ko I compiled is 40MB, but the origin wlan.ko file is only 4MB
I don't know how to fix this problem, could you give me some advices?
I doubt that there are something wrong in my kernel config file
Hello! So I've been trying to Kexec-Hardboot another custom kernel. I'm using Agni Kernel which has Kexec-Hardboot implemented. I patched the guest kernel to copy atags to be able to make it a guest kernel. Everytime I try to execute the guest kernel, the phone turns off for about 30 seconds and then boots to the ptevious kernel.
kexec --load-hardboot zImage --initrd=ramdisk --mem-min=0x44000000 --command-line=" androidboot.selinux=permissive buildvariant=userdebug"
kexec -e
Tried different --mem-min values but still the same. Tried cat'ing /proc/cmdline for --command-line. I even Tried recompiling Agni and enabling ram_console and copy atags. Still the same. If anyone could please help me here. Thanks
EDIT: Managed to implement kexec on TWRP but still the same. last_kmsg shows no trace of kexec
Post it in Q&A section not here
Sorry I didn't know there was a discussion section for this. I can't move this thread.
I found out that recent versions of the mainline linux kernel can boot on our motorola razr-i without any additional patches. Most of the hardware doesn't work. Only usb and emmc drivers are working. Maybe I or someone else can try if I get some more hardware working. To this post, I attached the kernel config file I used in my builds and the initramfs init script which I used for debugging. So if somebody wants to see the 4.18 kernel running he can use this files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WITH GREAT POWER COMES GREAT RESPONSIBILITY............
Please use kernel responsibly and respect the rights of others including and especially privacy!
The mad clown is back with another Kernel for all of the Kali-linux-nethunter users wanting the portability of kali-nethunter for their Pixel 7 and pixel 7 pro devices codenamed cheetah and panther collectively pantah
hahahahahahahahahahahahahahahahahahaha
Warning your warranty is now void. Do this at your own risk. The mad clown is in no way responsible for the chaos, worldwide disease, nuclear destruction, laughing fish, costumed caped crusaders or damage caused to your device by performing the steps involved.
hahahahahahahahahahahahahahahahahahaha
kernel features::
Code:
--Merged latest android kernel source Linux 5.15.149 QPR2
--Make TEO-Cpuidle util-aware (improves latency, performance and decreases energy consumption for certain workloads, more information here)
--Scheduler improvements for RT (realtime) tasks
--Boeffla's wakelock blocker
--Enabled power efficient workingqueues on various drivers
--mm: vmstat: use power efficient workingqueues tree wide
--Fsync on/off support
--Multi-gen LRU driver
--DAMON driver
--Disabled lots of debug spam
--Added bbr2 tcp drivers and enabled full options
--Lazy RCU should grant extra battery savings
--Enable support for TTL spoofing
--Full USB gadget support
--update several drivers to use power efficient workingqueues (for example wlan driver)
--f2fs: reduce timeout for uncongestion
--f2fs: Demote GC thread to idle scheduler class
--f2fs: set ioprio of GC kthread to idle
--tcp: enable advanced tcp, give user more options for tcp alorithm
--Force usb fastcharge
--Some hardening and security from graphene
--Errata work arounds
--DNS resolver support
--Checkpoint restore
--Suspend skip sync
--Security Yama
--uci functions including
-sweep2sleep
-cleanslate battery feature
-more
--Tri cluster kernel api =big, little, prime
plus all the commits needed to run kali-linux on your device and more. see my commits on github for more info
prerequisites:: vbmeta must have disabled verity and verification.
To do this pull a vbmeta.img from stock image zip or from a custom rom zip. back up your device as you will need to factory data reset your device after doing so
connect your device to your pc and open a terminal window and run
Code:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification
fastboot -w
Works on any Android 13 sec patch
Flash using FKM (preferred)
Source ::
GitHub - Biohazardousrom/Mad-Kali-MaxHunter-Pantah at QPR2
Contribute to Biohazardousrom/Mad-Kali-MaxHunter-Pantah development by creating an account on GitHub.
github.com
release ::
349.83 MB folder on MEGA
15 files
mega.nz
For one on one support join us on Telegram at
gs101 and gs201 development/support
Pixel 6/pro & 7/pro discussion group for general support and development
t.me
Special Thanks to
@acuicultor
@Freak07
I dont know what google did to the build system but
BUILD_CONFIG=private/gs-google/build.config.cloudripper
no longer works. it gets all the way past lto on the vmlinux and fatals making the gki modules at edgetpu/jainero complaining about it not being a git repo. i removed .git folder and stil it failed
i tried different build commands but the only one that would finish was
BUILD_CONFIG=build.config build/build.sh
but upon further inspection i noticed in the .config only gs101 configs were enabled and none of the gs201 configs.
Im hoping one of the seniors has a clue as to what im doing wrong and how to get the kernel to boot both p6 and p7 devices
as it stands i ended up moving my gs-google kernel source to a qpr1 build system and everything built fine using the cloudripper config.
wifi monitor mode can be enabled using wifi sniffer and special firmware thats included in the android 14 developers previews.
we pulled whats needed from the vendor image and i created a magisk module for you to flash with the firmware binaries and .rc files.
i have included the zip in this post but you can get it from my github as well
GitHub - Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201: This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter.
This Magisk module adds the required firmware for external wireless adapters to be used with NetHunter. - GitHub - Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201: This Magisk module adds the r...
github.com
For more info on wifi sniffer and how to use it follow this link
Getting the BCM4389 in Pixel 6 into monitor mode for tcpdump/Wireshark WIFI sniffing
A little side project to debug a WIFI 6E TP-Link mesh network in my house, went from "This sounds easy!" to "This is impossible!" to "It can...
chrisf4.blogspot.com
im trying to get sweep to sleep to compile and ive run the commits in entirety and it still errors for implicit declarations.
im attaching the log in a zip (since i cant attach .txt files) with the errors if anyone knows to fix this please let me know
Does this support external wifi adapters? I have the kernel and magisk wifi module installed. My wifi adapter chipset is RTL8812BU . lsusb lists it's info but in the driver section says driver=(none)
i think i know whats going on. some kali linux programs and android apks as well look to the /proc/config.gz for the proper configs in order to use them
the problem is that when you make all of the kernel configs needed by kali in order to use everything it creates a system warning at every boot due to a frameworks trigger that also checks /proc/config.gz
if the trigger checks it and it sees that it doesnt match you get the warning.
to fix this we use a commit that packages the original defconfig as the /proc/config.gz
see this commit::
kernel: Use the stock config for /proc/config.gz · Biohazardousrom/[email protected]
Userspace reads /proc/config.gz and spits out an error message after boot finishes when it doesn't like the kernel's configuration. In order to preserve our freedom to customize the kernel ...
github.com
What i can do is make two different kernels. keep the current kernel as is for those that want the kali flex and dont need all the functionality and recompile the kernel with that commit reverted for the power users that need it.
But be warned every time you reboot you will get a system warning. it wont effect anything its just annoying
Duhjoker said:
i think i know whats going on. some kali linux programs and android apks as well look to the /proc/config.gz for the proper configs in order to use them
the problem is that when you make all of the kernel configs needed by kali in order to use everything it creates a system warning at every boot due to a frameworks trigger that also checks /proc/config.gz
if the trigger checks it and it sees that it doesnt match you get the warning.
to fix this we use a commit that packages the original defconfig as the /proc/config.gz
see this commit::
kernel: Use the stock config for /proc/config.gz · Biohazardousrom/[email protected]
Userspace reads /proc/config.gz and spits out an error message after boot finishes when it doesn't like the kernel's configuration. In order to preserve our freedom to customize the kernel ...
github.com
What i can do is make two different kernels. keep the current kernel as is for those that want the kali flex and dont need all the functionality and recompile the kernel with that commit reverted for the power users that need it.
But be warned every time you reboot you will get a system warning. it wont effect anything its just annoying
Click to expand...
Click to collapse
Brilliant idea! That would be wonderful.
Change log: 03/27/23
v1.1
removed non working uci functions
added some tcp optimisations
some other optimisations see branch qpr2-0327
Change log: 03/27/23
v1.1 full
same as above
removed the commit to hide the actual /proc/config.gz
if you use the full version you will receive a system warning at boot. this is an expected annoyance and non harmful but will give you full function of the kernel and all available drivers
if you try an adapter and it still doesnt work check my defconfig at the bottom for your drivers and see if its already configged if not let me know and ill look for the missing drivers.
make sure you have the proper firmware installed for your adapters chipset. this can be done using apt in kali linux or by installing the magisk module from previous post
Mad-Kali-MaxHunter-Pantah/arch/arm64/configs/gki_defconfig at QPR2-0327 · Biohazardousrom/Mad-Kali-MaxHunter-Pantah
Contribute to Biohazardousrom/Mad-Kali-MaxHunter-Pantah development by creating an account on GitHub.
github.com
the kernel folder will have a special folder called kali-full-config and the zip will have full in its name
i also updated the link in op. just navigate to correct folder
Thank you for your work. I will try sometime today.
The kernel flashes successfully. I did not seem to get a warning message. The adapter does not work still sadly. I init and synced QPR1 build system and cloned your repo in to gs-google source. looked up the driver by device ID (https://linux-hardware.org/?id=usb:2001-331c) and it seems the driver is in your source. I ran the BUILD_CONFIG=private/gs-google/build.config.cloudripper build/build.sh command.
It seems to build fine. I'm just not sure what to look for in the /out to make an AnyKernel.
This is my first time lol.
look in the android-kernel/out/android13-gs-pixel-5.10/dist directory
there you will find the
boot.img
dtbo.img
vendor_dlkm.img
vendor_kernel_boot.img
are you sure you flashed the right .zip it should have full in its name
also do you have the adapters firmware installed
Duhjoker said:
look in the android-kernel/out/android13-gs-pixel-5.10/dist directory
there you will find the
boot.img
dtbo.img
vendor_dlkm.img
vendor_kernel_boot.img
are you sure you flashed the right .zip it should have full in its name
also do you have the adapters firmware installed
Click to expand...
Click to collapse
my output was different lol. i'll have to look into it more.
Anyway.. I did not get that error. I flashed the "Mad-Kali-MaxHunter-pantah-tm-qpr2-v1.1-full.zip". I also flashed the magisk firmware module on your github that inlcudes support for "RTL8821/12* (AE/AU/BU)" in the readme. # usb-devices still says there isn't a driver. weird. i guess i'll try to figure out how to get a driver for it.
-I will add that I have StagOS-cheetah-13.0-OFFICIAL-GApps-20230224-2018-update ROM
Thanks for your help.
i updated the nh wireless firmware. i got down to finding the vendor.img for A14 development build using the master android branch.
looked like it was missing some firmware blobs for gs201 and i added all the fw_bcmhd files so hopefully this will help with wifi_sniffer
This is how i get wifi_sniffer to work. first download and install the nethunter firmware magisk module. check permissions of the binaries.
next reboot your device and disable wifi and data. This must be done in order to restart the wlan in monitor mode
now open terminal emulator and either type or copy and paste the commands below
in su shell
Code:
su
# Set bandwidth to 160 MHz for sniffing on 2.4 GHz
Code:
setprop persist.vendor.wifi.sniffer.bandwidth 160
# Set 2.4GHz band
Code:
setprop persist.vendor.wifi.sniffer.freq 2412
# start wifi sniffer
Code:
wifi_sniffer start
#tcp dump to .pcap file
Code:
tcpdump -i radiotap0 type mgt subtype beacon -w /data/beacon-capture.pcap
Wifi_sniffer is only if you have AOSP, right? Or does it work on other ROMs?
should work on any rom. im currently on aicp and it works
Thank you for building a Cheetah Nethunter Kernel
I was able to get it running on stock rom.
Change log: 4-11-23
version bump to v1.2
merge gs-google/refs/tags/android-13.0.0.70
Fixed CVE-2022-4696 :
UPSTREAM: io_uring: add missing item types for splice request
see commits for branch QPR2-0411 for more info
Change log : Mad-Kali-MaxHunter-full
same as above but i changed the version from full to EX, honestly because it sounds better
@Duhjoker
Hey man, why don't you cross-post this in the P7P forum if you're building for Cheetah and Panther?? I just wandered in here, the P7 forum just for the heck of it. I doubt many other guys do the same thing and like me, didn't know this kernel even existed