Nethunter Kernel (Immensity Kernel) - Redmi K20 Pro / Xiaomi Mi 9T Pro ROMs, Kernels, Re

*ONLY FOR AOSP (Verified working on Evolution X)
This is my first Nethunter Kernel build. Based on UtsavTheGreat's Immensity Kernel this port provides all the benefits of the original Kernel with the added Nethunter functionality.
What's tested and working:
• Internal wifi monitor mode (Use the provided custom command in Nethunter app)
• Hid support (In the USB Arsenal section of the Nethunter app select hid USB function, disable adb and then click set USB function)
• External adapter support (TP-LINK TL-WN722N Tested, you may need to manually copy your WiFi card's firmware in "/vendor/firmware" from the provided zip. Also it appears as Wlan2 instead of Wlan1 if that matters)
Installation:
*Assuming you already have Magisk (and the BusyBox Magisk module), Nethunter store, Nethunter app, Kali chroot and Nethunter terminal installed.*
1) Flash the Nethunter_final.zip
2) Enjoy
Big thanks to the creator of Immensity Kernel
Source: https://github.com/Moto-John/kernel_xiaomi_raphael

Changelog:
•5/8/20 -> Fixed HID bug

Was waiting for someone to make this! Thanks!
Did you think about adding the drivedroid patch too?
Sent from my K20 Pro using XDA Labs

dr460nf1r3 said:
Was waiting for someone to make this! Thanks!
Did you think about adding the drivedroid patch too?
Click to expand...
Click to collapse
I think you can do the same thing from the USB Arsenal section in the Nethunter App
Edit: No, wait. You are right. Will try to fix it
Edit 2: Figured out it works fine as it is. Just booted an iso from it

moto-john said:
I think you can do the same thing from the USB Arsenal section in the Nethunter App
Edit: No, wait. You are right. Will try to fix it
Edit 2: Figured out it works fine as it is. Just booted an iso from it
Click to expand...
Click to collapse
Crazy. Thats pretty much all I wanted since this way the phone can replace usb sticks
Sent from my K20 Pro using XDA Labs

moto-john said:
*ONLY FOR AOSP (Verified working on Evolution X)
This is my first Nethunter Kernel build. Based on UtsavTheGreat's Immensity Kernel this port provides all the benefits of the original Kernel with the added Nethunter functionality.
What's tested and working:
• Internal wifi monitor mode (Use the provided custom command in Nethunter app)
• Hid support (In the USB Arsenal section of the Nethunter app select hid USB function, disable adb and then click set USB function)
• External adapter support (TP-LINK TL-WN722N Tested, you may need to manually copy your WiFi card's firmware in "/vendor/firmware" from the provided zip. Also it appears as Wlan2 instead of Wlan1 if that matters)
Installation:
*Assuming you already have Magisk (and the BusyBox Magisk module), Nethunter store, Nethunter app, Kali chroot and Nethunter terminal installed.*
1) Flash the Nethunter_final.zip
2) Enjoy
Big thanks to the creator of Immensity Kernel
Source: https://github.com/Moto-John/kernel_xiaomi_raphael
Click to expand...
Click to collapse
Sir plz help how to add specific WiFi card firmware plz provide full tutorial

Ralink RT5370 WiFi chipeset ... support...?

Is injection mode also work with internal wifi adaptor?

[email protected] said:
Is injection mode also work with internal wifi adaptor?
Click to expand...
Click to collapse
Unfortunately no. Only monitor mode is supported. If you want injection you have to use am external wifi adapter

swapnilj210f said:
Ralink RT5370 WiFi chipeset ... support...?
Click to expand...
Click to collapse
Have you checked if it's recognised without a specific driver first?

Can miui12 be used?

DKarls said:
Can miui12 be used?
Click to expand...
Click to collapse
It's for AOSP only, so probably no

moto-john said:
It's for AOSP only, so probably no
Click to expand...
Click to collapse
I am on latest Evolution X (https://forum.xda-developers.com/k20-pro/development/rom-evolution-x-elle-t4179163), Magisk 21.1, Busybox 1.31.1, have nethunter store, app and terminal installed and chroot is working. Installed it with:
https://forum.xda-developers.com/k20-pro/how-to/guide-how-to-install-kali-nethunter-t3998623
I flashed your kernel via twrp. But unfortunately HID is not working. I dont know what i should do anymore. Maybe you could help.
Thanks for all your work so far
EDIT: Could it fix with a fresh reboot, great work my friend
---------- Post added at 02:15 AM ---------- Previous post was at 01:42 AM ----------
moto-john said:
I think you can do the same thing from the USB Arsenal section in the Nethunter App
Edit: No, wait. You are right. Will try to fix it
Edit 2: Figured out it works fine as it is. Just booted an iso from it
Click to expand...
Click to collapse
which iso did you test? ive tryed it with a kali linux live system and it didnt work.

moto-john said:
*ONLY FOR AOSP (Verified working on Evolution X)
This is my first Nethunter Kernel build. Based on UtsavTheGreat's Immensity Kernel this port provides all the benefits of the original Kernel with the added Nethunter functionality.
What's tested and working:
• Internal wifi monitor mode (Use the provided custom command in Nethunter app)
• Hid support (In the USB Arsenal section of the Nethunter app select hid USB function, disable adb and then click set USB function)
• External adapter support (TP-LINK TL-WN722N Tested, you may need to manually copy your WiFi card's firmware in "/vendor/firmware" from the provided zip. Also it appears as Wlan2 instead of Wlan1 if that matters)
Installation:
*Assuming you already have Magisk (and the BusyBox Magisk module), Nethunter store, Nethunter app, Kali chroot and Nethunter terminal installed.*
1) Flash the Nethunter_final.zip
2) Enjoy
Big thanks to the creator of Immensity Kernel
Source: https://github.com/Moto-John/kernel_xiaomi_raphael
Click to expand...
Click to collapse
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware

chikko80 said:
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware
Click to expand...
Click to collapse
You just have to copy the whole ath9k_htc folder in /vendor/firmware. Then it should recognize the firmware

chikko80 said:
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware
Click to expand...
Click to collapse
Just realized you just couldn't find the vendor folder, If you use the miX file manager you should see it under the root section
https://streamable.com/lixw7d

moto-john said:
Just realized you just couldn't find the vendor folder, If you use the miX file manager you should see it under the root section
https://streamable.com/lixw7d
Click to expand...
Click to collapse
Yeah i could fix it meanwhile thank you
Everthing except drivedroid works like expected now ! do you have any advice? i tried different linux distros as well as different modis in drivedroid. I also tried the build-in image mounter of nethunter. I could not get it to work. You said u could boot. With which settings and distro did you tried it?
greetings chikko

chikko80 said:
Yeah i could fix it meanwhile thank you
Everthing except drivedroid works like expected now ! do you have any advice? i tried different linux distros as well as different modis in drivedroid. I also tried the build-in image mounter of nethunter. I could not get it to work. You said u could boot. With which settings and distro did you tried it?
greetings chikko
Click to expand...
Click to collapse
It definitely is a bit finicky. What I tested was linux mint and the built-in mounter. It definitely didn't want to work at first but after some plugging, unplugging and a few reboots which are seemingly unrelated it then worked pretty consistently every time I tried it

moto-john said:
You just have to copy the whole ath9k_htc folder in /vendor/firmware. Then it should recognize the firmware
Click to expand...
Click to collapse
Where can I find such firmware folder for rtl8812au ? Thanks in advance...

chikko80 said:
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware
Click to expand...
Click to collapse
Any idea where I could get such firmware folder for rtl8812au?

Related

CifsManager works on SGS Galaxy 3 (CIFS module compiled successfull for Android 2.1)

What is CIFS module ?
It is needed to mount SAMBA/CIFS filesystems (windows directories share over network)
Requirements:
- Naos or Teos phone ROOTED
- Android 2.1 (Eclair)
- CifsManager (with root access, available on market)
- Cifs module compiled successfull (cifs.ko, you can download it below)
Follow these steps:
1. Put cifs.ko on your phone on your sdcard (or better on "/lib/modules")
2. Open CifsManager.
3. Go to "Settings..." then tick "Load via insmod", configure "Path to cifs.ko" to where you put cifs.ko file on your phone and close "Settings..."
4. Finally go to "Add New Share..." and enter your information.
Note: Share Path -> Carefull to put an IP not a dns name (invalid argument error) and it is case sensitive.
Now you can browse your share docs with an explorer app.
Very useful to play video, music without download the file (seeking works).
Removed : Module compiled for kernel 2.6.32 (Froyo)... I am workin on it.
psyckotic said:
- Naos or Teos phone ROOTED
Click to expand...
Click to collapse
What does that mean?
Nice... How have you build the module ?
psyckotic said:
What is CIFS module ?
It is needed to mount SAMBA/CIFS filesystems (windows directories share over network)
Requirements:
- Naos or Teos phone ROOTED
- Tested only on firmware [I5800XXJH1]
- CifsManager (with root access, available on market)
- Cifs module compiled successfull (cifs.ko, you can download it below)
Follow these steps:
1. Put cifs.ko on your phone on your sdcard (or better on "/lib/modules")
2. Open CifsManager.
3. Go to "Settings..." then tick "Load via insmod", configure "Path to cifs.ko" to where you put cifs.ko file on your phone and close "Settings..."
4. Finally go to "Add New Share..." and enter your information.
Note: Share Path -> Carefull to put an IP not a dns name (invalid argument error) and it is case sensitive.
Now you can browse your share docs with an explorer app.
Very useful to play video, music without download the file (seeking works).
Click to expand...
Click to collapse
plz provide detail instruction in comp and phone
I will create a new thread to explain that.
I am workin on optimize that module and try to compile other modules.
I have test the module on a Naos phone (GT-5801) with firmware [I5800XXJH1] with root access.
I don't want to test other firmware.
But i think it works with all firmware with kernel 2.6.29 (without extraversion added).
Also works with XXJK1 (Kernel 2.6.29 #2).
For all those asking what this is all about: just have a look into the description of CIFSManager.
psyckotic said:
I will create a new thread to explain that.
I am workin on optimize that module and try to compile other modules.
I have test the module on a Naos phone (GT-5801) with firmware [I5800XXJH1] with root access.
I don't want to test other firmware.
But i think it works with all firmware with kernel 2.6.29 (without extraversion added).
Click to expand...
Click to collapse
Mh.. I think there might be a way to boot a Froyo firmware with 2.6.29 kernel no ? Since the SDK emulator use a 2.6.29 kernel..
psyckotic said:
I will create a new thread to explain that.
I am workin on optimize that module and try to compile other modules.
I have test the module on a Naos phone (GT-5801) with firmware [I5800XXJH1] with root access.
I don't want to test other firmware.
But i think it works with all firmware with kernel 2.6.29 (without extraversion added).
Click to expand...
Click to collapse
hey willing to try on froyo but need tute for that cas cant get a thing do we need usb or wifi will work plz give a detailed tutorial
I think it is possible to compile it for kernel 2.6.32 because it depends only from kernel source and arch-type cpu (armv6l for sgs galaxy 3)
psyckotic said:
I think it is possible to compile it for kernel 2.6.32 because it depends only from kernel source and arch-type cpu (armv6l for sgs galaxy 3)
Click to expand...
Click to collapse
If you compile i am willing to test...
psyckotic said:
I think it is possible to compile it for kernel 2.6.32 because it depends only from kernel source and arch-type cpu (armv6l for sgs galaxy 3)
Click to expand...
Click to collapse
AFAIK Samsung didn't publish (yet) the kernel sources which belong to the leaked firmwares (you cannot use a stock kernel as it is a derived (patched) version).
dude we need a guide for this
psyckotic said:
What is CIFS module ?
It is needed to mount SAMBA/CIFS filesystems (windows directories share over network)
Requirements:
- Naos or Teos phone ROOTED
- Tested only on firmware [I5800XXJH1]
- CifsManager (with root access, available on market)
- Cifs module compiled successfull (cifs.ko, you can download it below)
Follow these steps:
1. Put cifs.ko on your phone on your sdcard (or better on "/lib/modules")
2. Open CifsManager.
3. Go to "Settings..." then tick "Load via insmod", configure "Path to cifs.ko" to where you put cifs.ko file on your phone and close "Settings..."
4. Finally go to "Add New Share..." and enter your information.
Note: Share Path -> Carefull to put an IP not a dns name (invalid argument error) and it is case sensitive.
Now you can browse your share docs with an explorer app.
Very useful to play video, music without download the file (seeking works).
UPDATE: Module stripped: Size 270ko instead of 3Mo
Click to expand...
Click to collapse
divinesahil said:
dude we need a guide for this
Click to expand...
Click to collapse
indeed! This would be nice! As i found out by now you need to download the cross compiler and kernel sources from samsung open source:
opensource.samsung.com and search for i5800!
let's hope that they publish the sources for 2.6.32 soon!
mizch said:
AFAIK Samsung didn't publish (yet) the kernel sources which belong to the leaked firmwares (you cannot use a stock kernel as it is a derived (patched) version).
Click to expand...
Click to collapse
I don't their sources for this module.
This module works in software mode not in hardware.
I only need to know the cpu used in the phone...
I compiled it with the original kernel sources.
dabubu said:
indeed! This would be nice! As i found out by now you need to download the cross compiler and kernel sources from samsung open source:
opensource.samsung.com and search for i5800!
let's hope that they publish the sources for 2.6.32 soon!
Click to expand...
Click to collapse
Let's try the module compiled for 2.6.32 kernel (Froyo)
PS: How can i change the thread title (pm me)
got pm... ;-)
do you compile against aosp sources or where you got 2.2 kernel sources from?
FadeFx said:
got pm... ;-)
do you compile against aosp sources or where you got 2.2 kernel sources from?
Click to expand...
Click to collapse
Like i said before i don't need all the kernel sources for this module. I only need cpu information because there aren't many differences between kernel 2.6.29 and 2.6.32
But it needs to be tested... i don't try it on froyo.
Google has modified the Linux kernel in some regions and in not necessarily compatible ways, e.g. in terms of power saving techniques. So a stock kernel's module may work, but it is not guaranteed in all situations. However, I see no adverse effects from your cifs.ko.
But as long as Samsung sources are available (as they are for Eclair on opensource.samsung.com), I would always prefer their kernel sources. They come with a compiler and all the needed tools which guarantee full binary compatibility.
On the other side -- your module is working, so it's probably unnecessary to bother. Thank you for your time to build a module I now use on a daily basis to mount my Linux/Samba home server.
I'm getting a "no such device" error with froyo! But it never worked for me so i don't know if it is the module or my fault somewhere else.
"mount: Invalid Agrument" error. Pls help!!!!
- My phone firmware DDJG6 kernel 2.6.29 #2
- rooted
- copied cifs.ko to /sdcard/cifs/cifs.ko (change to insmod and edit path to /sdcard/cifs/cifs.ko) as well. My cifs manager version: 1.4.1 by F3d0r @ XDA 2010
@ my PC ip 192.168.0.226 (windows 7) share full read/write (everyone) folder name: test and this folder only content 01 mp3 file, so my share path must be:
192.168.0.226/test
mount point: /sdcard/cifs/test (cifsmanager automatically generate folders)
save => mount => error "mount: Invalid agrument"
Pls help.
TIA
P/S: using es file explorer i still can browse inside 192.168.0.226 but offcourse audio and video must be download to the phone NO direct playing!!!!! CIFS is the only and the best solution.

Froyo (2.2) for HUAWEI U8120 [based on AOSP] (under development)

Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.
v.1 initial build
How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
for the future
thnx for the gifts up to it tomorrow
A question about camera problem, only video or all features?
bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.
Ρε πατριδα αξιζει η rom ή οχι;
tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!
Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks
calibration fixed at this repo?
larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?
Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM
I think yes

Wont connect to USB

Hey,
I connected external WiFI adapter to my Xperia Z3, and it doesn't work. Any idea how to make device recognise/connect to the adapter?....
By my understanding of that Android is technicaly based on Linux kernel, you would need a kernel module for taht WiFi dongle or kernel that Supports it (Driver compiled in kernel)...
Why external WiFi?
I want to use reaver, Z3's WiFi doesn't support monitor mode.....
And is this even possible with rooted phone, while keeping locked bootloader?...
David47 said:
I want to use reaver, Z3's WiFi doesn't support monitor mode.....
And is this even possible with rooted phone, while keeping locked bootloader?...
Click to expand...
Click to collapse
In theory yes. You would need kernel module driver compiled for that kernel you are running. Drivers in Linux can be compiled in the kernel or provided as module. So grab source code compile as module and insert module (insmod) from terminal...
Sent from my D6603 using xda Forum
Sony Xperia Z3 NetHunter Kernel monitor mode
ondrejvaroscak said:
In theory yes. You would need kernel module driver compiled for that kernel you are running. Drivers in Linux can be compiled in the kernel or provided as module. So grab source code compile as module and insert module (insmod) from terminal...
Sent from my D6603 using xda Forum
Click to expand...
Click to collapse
Helo Friends
I have the latest KaliLinux + Nethunter installed on Sony Xperia Z3 RooT / Boot unlocked MM 6.0.1 - 23.5.A.1.291 ((Kernel: 3.4.0-perf-gc14c2d5)) according to this instruction:
http://www.hackcave.net/2017/05/install-kali-nethunter-on-any-android-device.html
everything works terminal, SSH, VNC, etc., but the network card
TP-LINK TL-WN722N does not want to wake up: (((
in the Kali Terminal, the "lsusb" command shows the adapter connected to the OTG cable with power supply:
Bus 001 Device 003: ID 0cf3: 9271 Atheros Comuni ..... AR9271
, but the green light on the usb wi-fi card does not shine
Here I have a question: does my kernel support the modules needed to support external wifi ???
what's the kernel under my system ???
My English is Google Translator I wrote matter-of-fact .............
Thank you very much for any advice

[ROM] [ 6.0 ] NetHunter - Jiayu S3 [MT6752]

Hi guys.
I have been working on a project to port NetHunter to Jiayu S3 (advanced for me , MT6752 platform) , working okay so far.
The rom contains two parts: Patched Kernel & NetHunter Files.
Kernel is modified and patched based on LoliTeam's project on Github.
mac80211 patched with script provided by Offensive-Security , HID manually patched regarding "Kernel-3.10-Nexus9.patch". Not exactly the same yet similar.
Additional Package of NetHunter is built under construction of [email protected]
Tested on
CM13 UNOFFICIAL for JIAYU S3a MT6752 (recommend)
AICP 6.0 UNOFFICIAL for JIAYU S3a MT6752
( Should work on JIAYU S3 basic too I guess. Never tried )
Progress:
OTG: Fix the 5V Power Supply for OTG so we can mount more than a USBdisk , like Mouse/Keyboard/JoyStick/WirelessAdapter , all avaliable now.
DuckHunter HID attack: working. Tho simple HID attack item didnt work , no idea why.
BadUSB MITM: RNDIS enabled. Capable to redirect the traffic of the computer you connected through your phone. (DHCPD on phone required, do it manually)
WiFi MITM: built-in wireless adapter does not support Monitor Mode so built-in Nethunter WiFi MITM does not work either. But we can do it manually , with a external USB via an OTG cable
Kali Chroot: Working
USBkeyboard(as HID device): Working
cSploit: Working
Shodan: Working
OpenVPN for Android: Working
VNC: Working
MSF: Working
RF Analyzer: Working
SDR softwares: Working
Not working:
aircrack-ng toolkit: seldom working. But can be replaced by manually command.
War Driving: not working normally , because aircrack-ng. Not planning a fix.
Router Keygen: Only support built-in adapter. Giving it up.
Problems:
Battery Power is consumed faster.
Easier to heat up.
I think they are bearable.
Installation Instructions:
To manually install , there is a long way to go.
Download ManuallyFlashImage.zip and unzip.
1. get a SP_FlashTool with a stock 5.1.1 RC5 firmware.
I have done most of the job.
Replace recovery.img with a TWRP one.
Modify scatter.txt to enlarge the partition of boot , recovery and system (I enlarged them * 2 , * 2, * 1.5)
You just need to select "download only" to "Format all and Download"
2.Get the roms ready in sdcard. I got [ cm13 , opengapps-mini , supersu , nethunter, xposed-framework ]
Vol-Up + Power
Vol-Up to select recovery and Vol-Down to confirm.
Wipe everything EXCEPT micro sdcard.
Install the roms in order.
CM13 - reboot to system - reboot to recovery - opengapps-mini - supersu - xposed - nethunter .
Screenshots (AICP)
Credits:
M.A.D.
DKingCN
LoliTeam
Offensive-Security
Download Link:
ManuallyFlashImage.zip
Keep track or commit:
@ https://github.com/offensive-security/kali-nethunter
@ https://github.com/DKingCN/nethunter-devices
@ https://github.com/DKingCN/android_kernel_jiayu_s3_h560
@ https://github.com/DKingCN/android-keyboard-gadget
i like that otg feature where you can plug in more than one. i hope that can be implemented in nougat too.
first time i hear about this nethunter, is that some kinda like linuxdeploy? where you can launch a desktop distros?
ak0ztik said:
i like that otg feature where you can plug in more than one. i hope that can be implemented in nougat too.
first time i hear about this nethunter, is that some kinda like linuxdeploy? where you can launch a desktop distros?
Click to expand...
Click to collapse
OTG might be avaliable on nougat , too.
I havent seen the source code of 7.0 kernel so I cant say for sure but most likely there should be OTG configuration.
Nethunter is a professional security package for android where you can do penetration test.
check NetHunter
Simplely it can be seen as Kali Linux on android.
And yes , local VNC server is avaiable so you can access local chroot kali desktop. Seems like gnome2.
I'm missing something
So you used kernel repo, that is a clone from mad repo, yet where's the credits?
Call me a jackass but this is the exactly reason why there's no much development on this devices.
Ever since M.A.D. released their GPL (and more non-GPL repos like device &vendor trees)
People had been using ( and good) and making kernels & semi-compiled cm builds forgetting the ones that had the heavy work on making those trees & releasing repos to the public ( that was an huge headache )...
Well done
As the project itself , looks cool
superdragonpt said:
I'm missing something
So you used kernel repo, that is a clone from mad repo, yet where's the credits?
Call me a jackass but this is the exactly reason why there's no much development on this devices.
Ever since M.A.D. released their GPL (and more non-GPL repos like device &vendor trees)
People had been using ( and good) and making kernels & semi-compiled cm builds forgetting the ones that had the heavy work on making those trees & releasing repos to the public ( that was an huge headache )...
Well done
As the project itself , looks cool
Click to expand...
Click to collapse
I forked the kernel from LoliTeam where the project can be found no link between MAD.
I am not a historian but I checked the commits and decide that MAD should be the origin of the copy of kernel so the credit is added.
Can be used kali linux from framebuffer in this project ?
(Request) help
Using magisk we can install universal full kali net hunter on miui or any other custom android rom
Which works almost perfectly
But
to do advanced stuff like wifi related stuff we need a external adapter i already has a fully supported wifi adapter
But the problem is to use a external adapter through otg we need a kernel which support wireless adapter, adapter driver built in
(Like most of the official device oneplus nexus lg samsung has "Any kernel" its a kernel available for nexus devices fully supports nethunter has wifi adapter driver built in)
Even the net hunter detects the adapter (cheked using "lsusb" command, it shows apater name chipset) but we cant do anything on off nothing because of that kernel compablity
So is there any kernel has this type of functionility available for note 5 pro whyred
If answer is no
Then im requesting Devs to make or port one
Since there is both stock and nethunter kernel source available in internet
So it will be not that difficult to port
(even previous year note 4 note 3 has a ported kernel which fully functional with net hunter)
So why not for our star
So plz its an request
A rom for net hunter will be great but
A kernel which support wireless adapter and other functionality is enough
Thanks in advance
[email protected] said:
Using magisk we can install universal full kali net hunter on miui or any other custom android rom
Which works almost perfectly
But
to do advanced stuff like wifi related stuff we need a external adapter i already has a fully supported wifi adapter
But the problem is to use a external adapter through otg we need a kernel which support wireless adapter, adapter driver built in
(Like most of the official device oneplus nexus lg samsung has "Any kernel" its a kernel available for nexus devices fully supports nethunter has wifi adapter driver built in)
Even the net hunter detects the adapter (cheked using "lsusb" command, it shows apater name chipset) but we cant do anything on off nothing because of that kernel compablity
So is there any kernel has this type of functionility available for note 5 pro whyred
If answer is no
Then im requesting Devs to make or port one
Since there is both stock and nethunter kernel source available in internet
So it will be not that difficult to port
(even previous year note 4 note 3 has a ported kernel which fully functional with net hunter)
So why not for our star
So plz its an request
A rom for net hunter will be great but
A kernel which support wireless adapter and other functionality is enough
Thanks in advance
Click to expand...
Click to collapse
Android kernel is device-specific. You cant flash one kernel to another device.

[ROM] [Unofficial] [Stable] GrapheneOS 10 Pre-Rooted

**** Disclaimer: I'm not responsible if you destroy your device. Use at your own risk!!! ****
GrapheneOS is an open source privacy and security focused mobile OS with Android app compatibility. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. Currently it is based on AOSP.
Link: (Mod Edit: Link removed)
Important information:
1. This ROM does NOT include Gapps or Google Play Service and hasn't Signature Spoofing Support. If you rely on the mentioned things this Rom isn't for you.
2. I take the official releases, modify the install script and include a pre-patched Magisk boot image. I'm not in contact with the GrapheneOS dev which is the reason why i mark this ROM as Unofficial.
3. Due of point two: Please don't ask questions on the official channels as reddit. Leave comments etc here on this thread.
4. You need a unlocked bootloader to flash this rom and must have adb+fastboot installed on your computer. If this is not the case download it from here: https://developer.android.com/studio/releases/platform-tools
I plan to make unofficial releases when new official builds are available.
Features:
AOSP 10
Built-in Firewall
Built-in local backup function (it's not working on all Apps; some doesn't support it)
Improved MAC Randomization
Hardened Kernel
Expanded Permissions (sensors)
Force calls to 4G only
Bugs
- Receiving text over verizon sim doesn't work reliable. Thx @wolfu11 for reporting.
Download: (Mod Edit: Link removed)
Installation:
Notice 1: The First-time installation will wipe your data. Backup first (i recommend this too when you follow the update instructions to be safe)
Notice 2: I recommend to have the newest stock firmware before the First-time installation
First-time installation:
1. Download the zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all_first_install.bat for Windows or flash-all_first_install.sh for Linux
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Install the Magisk Manager App
10. Be happy with a rooted GrapheneOS
Update:
Notice: I assume that fastboot+adb is still installed on your computer.
1. Download the newest zip from the linked download page and unzip it on your computer
2. Copy the following files into the plattform-tools folder:
-> coral zip
-> bootloader img
-> radio img
-> flash-all.bat for Windows or flash-all.sh for Linux
If your computer asks you to overwrite the current files in the plattform-tools folder, confirm it.
3. Boot your phone into fastboot mode and verify that the phone is recognized from your computer
4. In Terminal (Linux) or Powershell (Windows): Run the appropriate script
5. Start the system once. This need a few more time than the first installation cause the data partition remains. Be patient.
6. Install the Magisk Manager App
7. Be happy with a rooted GrapheneOS
Sources:
https://github.com/GrapheneOS
https://grapheneos.org/releases
https://github.com/GrapheneOS/kernel_google_coral
https://github.com/GrapheneOS/device_google_coral-kernel
All Credits go to:
- The GrapheneOS team
- wolfu11 for reporting the verizon bug and testing the windows scripts
- and topjohnwu for his amazing Magisk
Created: 09.08.2020
Based on: Android 10
Updated: 21.08.2020
Current Version: 2020.08.07.01
Changelog from 09.08.2020
New Release: 2020.08.03.22
SHA3-512 Hash for Complete zip:
Code:
773c67b8571927c6f884a98ee67a10f96c3a759e34f925f7a8aaab7c19a4ca6b1ff53bb6dc500b4fe7c306b73853189a1c559889df6d9b4f2e8a90258d3d26c9
SHA3-512 Hash for Unpatched boot.img:
Code:
9b584f6941d37f60a7ed17ec4108b7bf484c3cbf1b63f2be6af1e59f452ed1d06e1b64704785d6ca3b38a3c09c8f29657f88c757bda993df509ef001d9842f00
Changes:
full 2020-08-01 security patch level
full 2020-08-05 security patch level
rebased onto QQ3A.200805.001 release
fix secondary stack hardening when a non-page-size multiple stack size is specified
fix picking up previous build date when doing incremental builds
Vanadium: update Chromium base to 84.0.4147.89
Vanadium: update Chromium base to 84.0.4147.105
Vanadium: update Chromium base to 84.0.4147.111
Vanadium: remove Chromium logo in chrome://version
kernel (Pixel 4, Pixel 4 XL): read-only data expansion
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. I patched the boot.img which come with GrapheneOS in the zip with Magisk and then replaced the original GrapheneOS boot.img in the zip with the patched version.
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
dhacke said:
Changelog from 11.08.2020:
Updated the OP with some more informations
Rewrite the instruction cause i believe that they were not fully correct.
Reupload the 2020.08.03.22 unofficial release with new structure. It isn't needed anymore to flash Magisk separately from the zip. I replaced the stock boot.img in the zip with the pre-patched one.
Click to expand...
Click to collapse
Just a heads up - you really aren't meant to pre-patch a boot image for Coral/Flame, as you are only meant to patch the boot image from your own individual device, as per the man topjohnwu himself
See: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
Can you supply the unpatched boot img?
Thank you
wolfu11 said:
Can you supply the unpatched boot img?
Thank you
Click to expand...
Click to collapse
Done. Look here: (Mod Edit: Link removed)
I added an SHA3-512 Hash for file checking,too (see changelog from 11.08.2020).
Changelog from 15.08.2020
New Release: 2020.08.07.01
SHA3-512 Hash for Complete zip:
Code:
f3a2b088e0ec503296d5a2527a3766951cb2a3ccd1955ced14d304222e76ed3f341dd9d84b6e186a534eddac335065b756c1fdc89d0f1db3985314424e7f9eea
SHA3-512 Hash for unpatched boot image:
Code:
11abb901511ce8e39911bc951be4b1a349158c5d8389e74766942159c0f83aa9730ed39d8c8ae6c3cc66be559e3c165b5d4f35e0962d20a7be0b1532673a0287
Changes:
SELinux policy: fix executing apk libraries as executables for third party applications
Installation Notices:
From 2020.08.03.22 => No wipe needed. Just take the update scripts and let the right one running (see OP).
From Stock Rom => Use the install_first scripts. Be aware: This will wipe your data
Apart from that i recommend to make a backup first always (to be safe).
Wireguard Kernel integration
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
[email protected] said:
Hi, great work!! It was exactly what I was looking for, GrapheneOS with root. Are you able to integrate wireguard into the kernel?
Click to expand...
Click to collapse
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
dhacke said:
Hi Cryptt33,
first thx for your praise.
Regarding wireguard integration:
You should be able to use Wireguard independently from the kernel if i understand the description from the wireguard f-droid app right (https://f-droid.org/en/packages/com.wireguard.android/).
Then Wireguard runs in a userspace version. Apart from that i have found a xda thread already regarding wireguard integration. I guess i will at least try it and mayby i will be successful with the help of the thread. But i can't give a eta. I built roms from sources in the past but i until now i didn't try to modify them before the compiling step.
Best regards
dhacke
Click to expand...
Click to collapse
Just need to add this to local_manifest for WG support
If unfamiliar with local_manifest, it's located in /.repo/local_manifests/ - it'll be the only file in that dir, often it's called room service.xml but it could be something like graphene_manifest.xml. Either way, it'll be the only file there and it'll be an XML - add those lines above to it and sync and you should have WireGuard support.
<remote name="zx2c4" fetch=https://git.zx2c4.com/>
<project remote="zx2c4" name="android_kernel_wireguard" path="kernel/wireguard" revision="master" sync-s="true" />
dhacke said:
Hi good evening to all,
Can somebody try to install this Rom with the updated instructions? I think they should work now (at least on Linux) but i would appreciate a confirmation to be safe.
Click to expand...
Click to collapse
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
wolfu11 said:
I've tried this several time with a windows computer with no luck the shell opens briefly with red writing on the top and closes.
i must be doing something wrong but can't put my finger on it..... i run windows ltsb but i don't have any issues up and downgrading my p4 xl on it i am running the latest platform tools but get this message:
C:\Users\Wolf's laptop\Desktop\platform-tools_r30.0.4-windows\platform-tools>flash-all_first_install
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:10
+ $version=fastboot --version; try { $verNum = $version[0].substring(17 ...
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
fastboot too old; please download the latest version at https............
Click to expand...
Click to collapse
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
dhacke said:
Hi wolfu11,
i know this message in similar way on Linux. To fix it on linux i need to run all fastboot commands and scripts with './' before.
So for example:
./fastboot devices instead of fastboot devices or ./flash-all.sh instead of flash-all.sh.
I done this in the scripts for linux already cause i know it is needed there but didn't thought that it is needed on windows, too.
So please go into the script and make this before all fastboot commands:
./
Save it and execute it in the plattform-tools folder with ./ again in the shell. Hopefully it runs then.
If this fixes your issue, i will update the windows scripts.
Click to expand...
Click to collapse
I will try it when I get home today thank you
wolfu11 said:
I will try it when I get home today thank you
Click to expand...
Click to collapse
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
wolfu11 said:
that didn't work either i downloaded the latest platform tools so im at a loss about the fastboot issue.
I'm going keep trying
Update: I was able to get the official Graphene to work via putting the image into a working stock update platform tools folder and renaming it to the stock image. it wouldn't work per instruction on the website very strange.
Click to expand...
Click to collapse
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
wolfu11 said:
Well it was worth a shot texts don't work on verizon so i guess i'll just give up.
thank you
Click to expand...
Click to collapse
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
dhacke said:
Hi wolfu11,
i tested the bat script (more precisely flash-all.bat) with './' on my dedicated gaming machine with win 10 2004 education, too. First i got the same problem as you: It didn't run whether i made './' before all fastboot commands in the scripts.
Then i removed all the './' before all fastboot command except at this line:
Code:
$version= fastboot --version; ^
So the line looks now:
Code:
$version=./fastboot --version; ^
And hurray the script worked without problems on my machine (see attached screenshots).
Only as reminder: The bat scripts are from the 2020.08.07.01 unofficial release so you need the radio, bootloader and image files from that release.
i attached the new scripts with my mentioned modification, too. Xda doesn't allow bat files so i made them into a zip file. Please test once more. Thx in advance.
Click to expand...
Click to collapse
That script worked thanks
wolfu11 said:
That script worked thanks
Click to expand...
Click to collapse
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
dhacke said:
Yeah finally. I'm happy to read that. Then i will update the OP & scripts in the next days and take you on the credit section. Thx very much for your windows testing.
Now the next on the to-do list is the building of this rom from source and adding Wireguard support into the kernel
Click to expand...
Click to collapse
No problem i'm happy to test. unfortunately the still is an issue with texting on verizon which is what i use this phone on. the texts send but receiving them is not reliable. I tested on an att sim and it didn't have an issue so it's something on verizon's end.

Categories

Resources