[GUIDE][PROJECT CROISSANT] Installing official Chrome OS on any device (PC/PC-like) - Chromebooks

{
"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"
}
CHROME OS ON ANY DEVICE
About Project Croissant (formerly known as Ć̸h̷̢̡r̢͝o̡҉ḿ̴̢̧e̷͜҉f̡͝y͝͞͡͡)
This project is aimed at making Chrome OS (the official releases by google) available for any non-chromebook devices (ATM The device must be able to boot from live USB, this excludes most Android-only devices);
The steps can also be followed on a chromebook, to install an image with android and linux support.
The script uses an official Chrome OS image, while it uses the Kernel and GRUB bootloader from another Chromium OS distribution (EX: ArnoldTheBat builds).
This project has an official GitHub/Wiki page, a Telegram group, a Twitter page and is the result of many ideas and contributions.
Please fill this survey to let us know whether Chromefy works (or doesn't) on your device
Required files
An official Chrome OS recovery image (downloads on the right; RECOMMENDED: eve (best) or pyro are the most complete images [must be from the same chipset vendor (Ex: Intel, ARM or RockChip); If eve/pyro doesn't work, try an image from a device with a similiar chipset as your own]
Another Chrome OS recovery image from a TPM 1.2 device (EX: caroline or kip) or the swtpm.tar file (swtpm TPM2 emulator needs VTPM proxy support in kernel) (this step is only needed if using an image from TPM2 device to fix a login issue, which is most likely the case for newer ones)
An image from a Chromium OS distribution (EX: ArnoldTheBat builds).
The Chromefy installation script.
Installation guide (Partition method)
For method 1 (bootable USB image generation) check this video guide:
Method 2-B (chromium OS root partition conversion) described below:
Other methods described in the official GitHub/Wiki page.
This procedure will install Chrome OS on top of a Chromium OS kernel, you will thus need to install a Chromium OS distribution on your device first;
RECOMMENDED: ArnoldTheBat builds
NOTE: CloudReady builds are not yet supported due to a different partitioning scheme and incompatible kernel
If you consider this guide too generic, try reading a more comprehensive guide
Flash the selected Chromium OS build on a live USB, boot into the live USB and install it on your HDD/SSD by typing the following command on the shell
Code:
sudo /usr/sbin/chromeos-install --dst [COLOR=Blue]YOURDRIVE[/COLOR] [COLOR=DeepSkyBlue](Ex: /dev/sda)[/COLOR]
now make sure the your chromium HDD/SSD installation is working before proceeding.
Resize the third partition of your sdX drive (EX: sda3 inside sda) from its current size to atleast 4GB; I suggest using Gparted live USB to resize it; you can either downsize sdX1 (data partition) or delete the sdX5 partition (we won't need it) to get more unallocated space.
Boot from your live USB again, make sure you have your Chrome OS images available and run the installation script with the following command
Code:
sudo bash /path/to/chromefy.sh [COLOR="blue"]YOURSYSTEMPARTITION[/COLOR][COLOR="DeepSkyBlue"](EX: /dev/sda3)[/COLOR] /path/to/chosenchromeosbuild.bin /path/to/carolinebuild.bin_OR_swtpm.tar
Don't leave live USB yet, make a powerwash (manually) by typing
Code:
sudo mkfs.ext4 [COLOR="Blue"]YOURDATAPARTITION[/COLOR][COLOR="DeepSkyBlue"](Ex: /dev/sda1)[/COLOR]
You can now reboot and enjoy your new "chromebook"
Images supporting swtpm TPM2 emulator
ArnoldTheBat's latest special build (v72) now supports VTPM proxy
FydeOS V6 (or newer) now supports VTPM proxy
ArnoldTheCat v3 (custom)
EmydeOS v3 (custom)
CloudRadish v3 (custom)
FAQ
Can I dualboot with Windows/Linux?
Yes, but it's a little more complicated
Will this ever work on CloudReady?
We don't know, nor we have any ETAs. There's currently a repartitioned image (still not working with chromefy)
My motion sensors do not work, how do I rotate the screen?
Laptop mode/keyboard connected: press ctrl+shift+f3
Tablet mode: use this app by Andrew Whaley (source) (check out his blog)
Linux apps (crostini) are not working at all, how do i fix it?
Go check if you have enabled all virtualization related option in your BIOS (Ex: "Intel Virtualization", "VT-x", "VT-e" etc...) (you should)
Do automatic updates work? How to update?
Not at the moment, and it's unlikely we find a workaround; you can update by ONLY repeating step 3 (without step 4).
ChromiumOS works on live USB but not HDD, what to do?
Did you remove the USB before rebooting the fist time? If you did NOT, you might need to reinstall it. If you did, try using fix_grub.sh
Some apps (ex: Netflix) do not show up in the Play Store, how do I fix it?
Read next answer
SafetyNet check fails, why?
For SafetyNet not to break you need two things, leave selinux on enforcing when chromefying (only working on Pie, otherwise will break android container) and disable "cros_debug" in the grub launcher to boot without developer mode (Custom images [ex: CloudRadish] have custom boot entries for this)
ChromeOS flags are not showing up, why?
Try opening the chrome://flags page in incognito mode.
Alternatives
FydeOS
Fyde OS is a Chromium OS based operating system that comes with Android apps; if you don't want to bother with the hassle of running the chromefy script and just want an OS that works out of the box, this might be for you.
...Also the developers are awesome
ArnoldTheBat
Does not come with Android apps (yet), but he's awesome too, so there's that
Credits
allanin for all of his ideas on Arnoldthebat discussion, most part of the code is from him
TCU14 for upgrading, and the MultiBoot guide
Dnim Ecaep from the Telegram Group for the shell command to change the SELINUX to permissive
Diogo from the Telegram Group for the corrections on the firmware migration
Danii from the Telegram Group for the work on the TPM bypass method and TPM2 emulation method
sublinhado for writing down the steps needed for the TPM bypass method
alesimula for the installation script
Giedrius Tamošiūnas (liolka) for the custom chromium kernels
++ some poor unlisted guys

Amazing. Just confirming whether Google play store work in this?

Awesome work!
Does it work with FydeOS builds?

Forever Alone said:
Amazing. Just confirming whether Google play store work in this?
Click to expand...
Click to collapse
coolloser said:
Awesome work!
Does it work with FydeOS builds?
Click to expand...
Click to collapse
Play Store (and crostini) works.
And yes, you can install it over FydeOS;
Some users report Arnold kernel working better for them, for others it's Fyde, so just test both to find the best one for your device

alesimula said:
Play Store (and crostini) works.
And yes, you can install it over FydeOS;
Some users report Arnold kernel working better for them, for others it's Fyde, so just test both to find the best one for your device
Click to expand...
Click to collapse
Tried it with Arnold special build on my AMD-450 with Radeon GPU and got a bootloop. I wasn't surprised because I don't think that there are any chromebooks with AMD chipset yet! The procedure was pretty painless though, thanks for all your hard work.

coolloser said:
Tried it with Arnold special build on my AMD-450 with Radeon GPU and got a bootloop. I wasn't surprised because I don't think that there are any chromebooks with AMD chipset yet! The procedure was pretty painless though, thanks for all your hard work.
Click to expand...
Click to collapse
Just make sure you didn't accidentally use the ARM build

This is something I have offered for well over 3 years...... http://zzsethzz.blogspot.com/2015/09/install-chromium-upgrade-it-to-chrome.html
Does this not suffer from the same hardware support issues due to the fact that ChromeOS has very limited hardware support naively?

zZSETHZz said:
This is something I have offered for well over 3 years...... http://zzsethzz.blogspot.com/2015/09/install-chromium-upgrade-it-to-chrome.html
Does this not suffer from the same hardware support issues due to the fact that ChromeOS has very limited hardware support naively?
Click to expand...
Click to collapse
Tried that some time ago and never worked for me as well as this method, also this one let's you have Crostini with the new recovery images that have tpm protection.

DiogoSilva48 said:
Tried that some time ago and never worked for me as well as this method, also this one let's you have Crostini with the new recovery images that have tpm protection.
Click to expand...
Click to collapse
That is simply a hardware based issue and not selecting the right build. I admit my project needs more work but even the github page tells you to use a build close to your own hardware. Also the TPM is bypassed and not a functioning part of the OS in this regard the same as mine, from a quick look anyway.
All this does is the exact same as my script but you have to download a lot of other crap too, my script does it all for you. This seems a rather long method to get the exact same thing.
Mine also doesn't require any messing with partitions, even between upgrading to newer versions.

zZSETHZz said:
That is simply a hardware based issue and not selecting the right build. I admit my project needs more work but even the github page tells you to use a build close to your own hardware. Also the TPM is bypassed and not a functioning part of the OS in this regard the same as mine, from a quick look anyway.
All this does is the exact same as my script but you have to download a lot of other crap too, my script does it all for you. This seems a rather long method to get the exact same thing.
Mine also doesn't require any messing with partitions, even between upgrading to newer versions.
Click to expand...
Click to collapse
Not build problem since I have an Ivy Bridge system and I'm using eve (pixelbook) recovery image and works perfectly, and maybe it's not your script fault, I don't remember it to be honest, I used it once 2 or more months ago. But another guy also has a script that downloads the image automatically. But I'm telling you to please join our telegram group, it's better if we work all together. I apologise if I somehow offended you.

DiogoSilva48 said:
Not build problem since I have an Ivy Bridge system and I'm using eve (pixelbook) recovery image and works perfectly, and maybe it's not your script fault, I don't remember it to be honest, I used it once 2 or more months ago. But another guy also has a script that downloads the image automatically. But I'm telling you to please join our telegram group, it's better if we work all together. I apologise if I somehow offended you.
Click to expand...
Click to collapse
Oh no you haven't offended me at all! Don't want you to think you have lol, I'm just joining telegram now as I've not used it before however it won't send me a verification message which is rather annoying. I was intended on seeing if its something that could be worked on together.

zZSETHZz said:
Oh no you haven't offended me at all! Don't want you to think you have lol, I'm just joining telegram now as I've not used it before however it won't send me a verification message which is rather annoying. I was intended on seeing if its something that could be worked on together.
Click to expand...
Click to collapse
Alright, thanks, I will be waiting for you there ? good luck, if you need anything related to telegram or anything pm me.

zZSETHZz said:
That is simply a hardware based issue and not selecting the right build. I admit my project needs more work but even the github page tells you to use a build close to your own hardware. Also the TPM is bypassed and not a functioning part of the OS in this regard the same as mine, from a quick look anyway.
All this does is the exact same as my script but you have to download a lot of other crap too, my script does it all for you. This seems a rather long method to get the exact same thing.
Mine also doesn't require any messing with partitions, even between upgrading to newer versions.
Click to expand...
Click to collapse
Your script, if I recall, uses the kernel from the downloaded chrome OS build, that's why you had to pick a version from a device with a similiar processor.
This not only limits the number of builds you can install, but, by extension, the features you can have, and the conpatible devices, and many drivers (bluetooth and stuff) may not work
This method copies the kernel from chromiumOS (as well as kernel modules and certificates)

Hi, I'm wondering if this can be installed in my 2016 Pixel C tablet, as it has an ARM processor and it was rumored to be designed to use Chrome OS.
Anyone can help me?

Is it multi-bootable with windows 10??
Sent from my OnePlus 5 using XDA Labs

@srmahunt said:
Is it multi-bootable with windows 10??
Sent from my OnePlus 5 using XDA Labs
Click to expand...
Click to collapse
Check this for multiboot:
https://docs.google.com/document/d/1uBU4IObDI8IFhSjeCMvKw46O4vKCnfeZTGF7Jx8Brno/edit?usp=sharing

Verdera11 said:
Hi, I'm wondering if this can be installed in my 2016 Pixel C tablet, as it has an ARM processor and it was rumored to be designed to use Chrome OS.
Anyone can help me?
Click to expand...
Click to collapse
ATM you can't do this on Android tablets (unless they have a BIOS and live USB booting, which is not your case)

Will this method give Android and Linux app support to devices that Google hasn't enabled that for? I have an Acer C720p that's been an awesome Chromebook, and I use Ubuntu on it as well using crouton. I suspect it would run Android just as well, but so far the ability hasn't been unlocked officially.

Nice

Snowflake6 said:
Will this method give Android and Linux app support to devices that Google hasn't enabled that for? I have an Acer C720p that's been an awesome Chromebook, and I use Ubuntu on it as well using crouton. I suspect it would run Android just as well, but so far the ability hasn't been unlocked officially.
Click to expand...
Click to collapse
Yes (but in case you have a BayTrail device, still no linux)

Related

[ABANDONED] AndroPlusKernel v43

***ABANDONED***
I am sorry but I stopped supporting this kernel because I don't have much time recently.
{
"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"
}
This is first custom kernel for Xperia Z4 Tablet SGP712/SGP771.
Download
Download from official website
How to root
See my blog post:
https://androplus.org/Entry/626/
I won't create kernel for device which I don't own.
If you want me to create, please give me the device.
Donate:
PayPal
XDA:DevDB Information
AndroPlusKernel for Z4 Tablet, Kernel for the Sony Xperia Z4 Tablet
Contributors
AndroPlus, Tommy-Geenexus, DHGE, dl12345, andip71, nilezon
Source Code: https://github.com/AndroPlus-org/android_kernel_sony_msm8994
Kernel Special Features:
Version Information
Status: Testing
Created 2015-08-02
Last Updated 2017-05-04
Features and changelog
I won't answer questions or requests for older version (e.g. "Please update kernel for old firmware!")
Moved to here
SONY has a 28.0.A.7.31 under "Android Downloads"
Have not found a changelog yet.
DHGE said:
SONY has a 28.0.A.7.31 under "Android Downloads"
Have not found a changelog yet.
A device tree is in the attachment.
Click to expand...
Click to collapse
Oh I meant set of files such as "android_device_sony_karin" or "android_device_sony_msm8994-common". (you can see some device tree for other devices on cyanogenmod's Github)
This is also called device tree.
@AndroPlus:
Hello, I'm seriously considering to buy this device but first I want to make sure (before buying a new tablet) that (a) it supports root (which obviously you were able to do) and (b) to support linux running on the device's framebuffer.
Since running linux on my 10 inch + tablets has become a 2nd nature to me (tablets make some of the best netbooks, being so light and battery-efficient compared to regular netbook) may I venture a suggestion?
Can you try enabling the config_VT on the kernel's option (i.e. the Virtual Terminal feature)? I know some devices to be unbootable after enabling that feature, others do boot. I mean I would be happy to try it myself, but for that I would need to buy the device first, and I much prefer to have a confirmation first.
So yeah great work there (creating the first custom kernel et al). Enabling a single feature would -at worse- cause a boot loop, so I'd guess it would be an easy experiment to do (in case of bootloop you just reflash a "proper" version of the kernel).
Thanks.
Code:
# Character devices
#
CONFIG_TTY=y
# [COLOR="Red"]CONFIG_VT is not set[/COLOR]
CONFIG_UNIX98_PTYS=y
# CONFIG_DEVPTS_MULTIPLE_INSTANCES is not set
# CONFIG_LEGACY_PTYS is not set
# CONFIG_SERIAL_NONSTANDARD is not set
# CONFIG_NOZOMI is not set
# CONFIG_N_GSM is not set
# CONFIG_N_SMUX is not set
# CONFIG_TRACE_SINK is not set
CONFIG_DEVMEM=y
CONFIG_DEVKMEM=y
I do not have the time ATM to test VT.
When I have the itch to work in terminal mode I either use adb from my Debian box or the app "Terminal Emulator".
What would VT give us more?
I'd like (as a challenge, not too useful) to port Perl 5.22 to the device and some tools...
But that should be possible with my above mentioned terminals at hand.
I have disabled SONY's RIC and that prevents the bootloops when fiddling with the configuration.
No guaranty for CONFIG_VT though.
Next thing I will try (not this week I suppose): work with the latest ..31 version from SONY and try to enable SELinux again. AndroPlus used my sources and with "his" kernel SELinux is disabled - necessary for me in rooting in the first attempt but I'd like to have SELinux again (stagefright etc.)
Virtual Terminal gives us the chance to output whatever image "we wish" directly to Android's framebuffer.
To make a longer story short, it lets us run Linux on a chroot environment almost natively.
The alternative to that would be running a whole X-server on top of Android or -worse- establish a VNC connection to the chroot environment. In both occasions running a (Desktop) linux distro would be a pain both for every-day use purposes but also kill the battery.
So -yeah- enabling the VT feature lets us -basically- turn our android tablet into a linux tablet with a press of a button (a script that starts the chroot environment and outputs to android's framebuffer) and then back to android through a second script.
I find the concept of Android/Linux netbooks/tablet very appealing as unlike Surface pro it lasts a longer (battery wise), it's half the weight and much better for tablet purposes.
Anyway testing VT would be a godsend (just see whether it boots at least). If it does boot I will buy the tablet in a heartbeat, and probably even write a guide of how to turn it into a full featured Linux machine with the press of a button (without having to dual boot)
I'll try to build config_VT enabled kernel.
For ric problem, maybe this commit works, so I'll try this.
https://github.com/fxpdev/android_k...mmit/a1223a90286f3a59eadb82c709c8d3c427e7bb78https://github.com/fxpdev/android_k...mmit/a1223a90286f3a59eadb82c709c8d3c427e7bb78
maybe this commit works
Click to expand...
Click to collapse
This is straight disabling RIC.
Fine but when I went this route my device bootlooped. I suppose because RIC-calls are hardcoded into SONY's init binary and we do not have the source for that.
So my "solution" was just to patch the calls to RIC and give OK on every call.
When AOSP sources will be available we have a modifiable init and you get your device tree.
@Stevethegreat
It booted successfully after adding CONFIG_VT and patch to arch/arm64/kernel/setup.c.
https://github.com/AndroPlus-org/an...mmit/18db9f30bc60bdb5ec0e91826e1ebba313b762a0
How do I check if it really works?
AndroPlus said:
@Stevethegreat
It booted successfully after adding CONFIG_VT and patch to arch/arm64/kernel/setup.c.
https://github.com/AndroPlus-org/an...mmit/18db9f30bc60bdb5ec0e91826e1ebba313b762a0
How do I check if it really works?
Click to expand...
Click to collapse
Wow those are great news. Thanks!
A quick way to check if it worked is to open Terminal emulator. Then navigate to dev/graphics and make a mental note of the different fb files that exist in that folder (for example fb0, fb1, etc)
When you do that you simply type "su" (to gain super user access) and lastly:
cat /dev/urandom > /dev/graphics/fb0
If all goes well you should get a flashing screen or even a solid screen with urandom's gibberish on top of the screen (a screen fillled with characters). You should *not* get "static" (non specific image) or an error code, really. After trying fb0 , please try the rest of FBx that you found in /dev/graphics. At least one should work as above (generally fb0 does).
Once again thanks man, much appreciated. If all goes well, I'm buying this tablet
I built a new kernel from the 28.0.A.31 sources with SELinux enabled (Yeah!! :laugh.
On a second run I set CONFIG_VT=y.
cat /dev/urandom > /dev/graphics/fb0
Click to expand...
Click to collapse
gives:
tmp-mksh: ... No space left on device
attempting to write on fb2 (three framebuffers 0-2) gives No such device
So no sport here ...
Hmmm pity :/.
Hope you ran the command as a super user.
Also maybee trying it w SeLinux in permissive may give different result.
Still I may buy the tablet annyway. As long as it boots with VT on I may find a way to make it work once I have it in hand...
yes I used the root account
I really like the tablet:
http://forum.xda-developers.com/showpost.php?p=62033395&postcount=17
Was fortunate to get it for 465 EUR, otherwise I'd have used my Tablet Z longer.
DHGE said:
yes I used the root account
I really like the tablet:
http://forum.xda-developers.com/showpost.php?p=62033395&postcount=17
Was fortunate to get it for 465 EUR, otherwise I'd have used my Tablet Z longer.
Click to expand...
Click to collapse
Since I'm very much interested, where did you find it (selling it) at 465 Euros? Everywhere I look is close to 600 Euros (shipping included) and that's kind of too much.
edit: sorry for the off-topic, I just remembered that this thread is about the OP's kernel, not our discussion (still PM me the answer if you wish, thanks).
I use this way to disable RIC:
CONFIG_SECURITY_SONY_RIC=n
I did diff command to check what files are changed in 28.0.A.7.31 and... no diff
Well I uploaded v2, now kernel has some new features such as KCAL and CPUQuiet.
I could build TWRP from source but it didn't boot, so I need to brush up my dirty device tree...
I compile a dtbtool from this git: https://github.com/scotthartbti/android_device_common_qcom.git
and use this command: dtbtool --force-v2 -o dt.img -s 2048 -p scripts/dtc/ arch/arm/boot/dts/
thus I have made a dt.img for my xperia z4
I tried to build TWRP and build succeeded, but didn't boot
here's last_log
kitakami device tree
https://github.com/AndroPlus-org/android_device_sony_karin
I could build and boot Cyanogen Recovery (useless...):
Download
If someone want to try useless recovery, enter into fastboot mode and type
Code:
fastboot flash recovery cmr.img
then reboot and hit power key when LED turn on.
[UPDATE]
OK, TWRP now boots!
...but no touch input:crying:
Build from official source didn't boot at all, and this multi-language fork boots.
Recap please
I've been following this thread intrigued for about a month, as long as I've had the tablet. I see that people have been successful in getting their tablets rooted and even gotten TWRP to work on some of them.
What I'm interested is getting simple instructions on how to get root access and of course TWRP would be a big plus since I'm using it on my phone

Thoughts on Oreo...

So, since the Pixel and newer Nexus devices are now getting their Oreo updates, I think it's time that we, the developers who still own Nexus 6's, to look into porting Oreo to this device. I am looking into the source code as we speak for feasibility. If anything, I will probably do like I have done with most of my devices in the past, forge the path and create a guide, and let everyone else do the creative stuff. I just happen to like stock Android.
There is already one dev who got Oreo to boot on the Xiaomi Mi 3, runs on SD800 (32bit)
konradit said:
There is already one dev who got Oreo to boot on the Xiaomi Mi 3, runs on SD800 (32bit)
Click to expand...
Click to collapse
Looking promising,fingers crossed
Sent from my Nexus 6 using Tapatalk
There ARE people working on Android O port, even back when it was still in developer preview status. You'll see releases whenever they are ready, I'd give it a few weeks or months.
I won't argue if you're a developer or not, I'm sure you are. But you are not a "recognized developer". Your title is member
Dopamin3 said:
There ARE people working on Android O port, even back when it was still in developer preview status. You'll see releases whenever they are ready, I'd give it a few weeks or months.
I won't argue if you're a developer or not, I'm sure you are. But you are not a "recognized developer". Your title is member
Click to expand...
Click to collapse
Getting it to build is easy. Ive already done as much but without updated binaries (which I havent seen for any device) it wont boot. There are likely some kernel changes needed as well though I havent dug to much into that yet. Then there is the whole GApps for Oreo issue. I would say we are definitely a week or so away from anything working.
Things are in the works and if gapps don't work for 32 bit.. I suggest you gentlemen familiarize yourself with microG
I built it from developer preview 2 a couple months ago. Booted and everything, but nothing as far as any of the radios worked. I had to modify franco kernel to get it there, but it did work..
I tried re-building it after the stable source dropped and can't seem to get passed this error:
frameworks/native/include/gui/IGraphicBufferProducer.h:35:10: fatal error: 'hidl/HybridInterface.h' file not found
The file is there and where it should be... So I'm kinda scratching my head as to where the switch is that causes it not to pick up that location.
{
"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"
}
So the development for Xiaomi Mi3/Mi4 has gone online: https://forum.xda-developers.com/xiaomi-mi-3/development/8-0-aosp-t3662028
The source code is not available yet but is on it's way. Maybe there might be hints on what's needed for us to make stuff work on the shamu once the source is online(?). I'm aware they are completely different devices but the architecture are closer as they both are 32bit rather than the newer devices running 64bit.
I was able to get a build to complete but it doesn't boot. I don't have the time today to go over it, but if anyone has some free time, feel free to take a look at the logcat and see if anything jumps out immediately.
boot.log
kkozma said:
I was able to get a build to complete but it doesn't boot. I don't have the time today to go over it, but if anyone has some free time, feel free to take a look at the logcat and see if anything jumps out immediately.
boot.log
Click to expand...
Click to collapse
@followmsi build had a similar issue yesterday on the Nexus 7 2013 forums. I tested the build and it would not get to the boot animation and would restart to the bootloader after about a minute. After returning to TWRP the data partition was either corrupted or unreadable. OP said that it was probably the fact of missing SDcardFS support in the recovery/kernel.
https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067/page60
the struggle continues.
wavedashdoc said:
@followmsi build had a similar issue yesterday on the Nexus 7 2013 forums. I tested the build and it would not get to the boot animation and would restart to the bootloader after about a minute. After returning to TWRP the data partition was either corrupted or unreadable. OP said that it was probably the fact of missing SDcardFS support in the recovery/kernel.
https://forum.xda-developers.com/nexus-7-2013/development/rom-t3569067/page60
the struggle continues.
Click to expand...
Click to collapse
He is wrong. The sdcardfs is a file system for sdcard enabled devices. Nothing to do with the nexus 6. It was even removed in most other builds for the device. The only people that added it were people that didn't understand what they were doing.
wrongway213 said:
Things are in the works and if gapps don't work for 32 bit.. I suggest you gentlemen familiarize yourself with microG
Click to expand...
Click to collapse
Late reply here.
I have tried MicroG before - on a custom Galaxy S4 ROM - and I like MicroG about as much as I like Xposed. If MicroG is required I won't be upgrading.
wrongway213 said:
Things are in the works and if gapps don't work for 32 bit.. I suggest you gentlemen familiarize yourself with microG
Click to expand...
Click to collapse
People are not gonna do that. Microg is known for causing its own issues.
Strephon Alkhalikoi said:
Late reply here.
I have tried MicroG before - on a custom Galaxy S4 ROM - and I like MicroG about as much as I like Xposed. If MicroG is required I won't be upgrading.
Click to expand...
Click to collapse
zelendel said:
People are not gonna do that. Microg is known for causing its own issues.
Click to expand...
Click to collapse
It's been confirmed that gapps for arm are working since I posted that, so it's a moot point now, thankfully.
zelendel said:
He is wrong. The sdcardfs is a file system for sdcard enabled devices. Nothing to do with the nexus 6. It was even removed in most other builds for the device. The only people that added it were people that didn't understand what they were doing.
Click to expand...
Click to collapse
Oh mate, you're so wrong. SDcardFS is a virtual FS for emulating /sdcard/ (/storage/emulated/0) and EVERY android device has it. It's just a replacement for vFAT (virtual FAT). One of the most important fixes is that the file timestaps won't get corrupted anymore (this bug existed in android for years).
Lawstorant said:
Oh mate, you're so wrong. SDcardFS is a virtual FS for emulating /sdcard/ (/storage/emulated/0) and EVERY android device has it. It's just a replacement for vFAT (virtual FAT). One of the most important fixes is that the file timestaps won't get corrupted anymore (this bug existed in android for years).
Click to expand...
Click to collapse
vfat is a real filesystem for block devices. Think of it as being in between FAT and FAT32. What it adds over FAT is a virtual file NAMING convention in order to exceed the standard "8.3" filename format that FAT was stuck with. vfat is also the NAME of the linux implementation of FAT (FAT12, FAT16), VFAT, and FAT32.
What you are thinking of as being present on "EVERY" android device, is this; https://android.googlesource.com/pl...197870433386fb809d34b58b30fc0/sdcard/sdcard.c
You should pay attention to the README section of it starting at line 32.
When Android devices used to have an actual sdcard, it was formatted using vfat (the linux implementation of FAT32), with a mount point of /sdcard.
When they stopped including real sdcards, they started emulating sdcards using that FUSE simulated vfat I linked to above.
Now what sdcardfs is, is (a) a replacement for the FUSE filesystem I linked to above, and (b) a replacement for FUSE itself. Think of it as a scaled back and simplified FUSE+sdcard.c. The problem with FUSE is that it is too complex and with too high of an overhead. It causes performance degradation. And I'm not talking about the general userspace degradation that you would get with, for example, NTFS-3g compared to a native implementation, but rather the sdcard.c adds some problems because it is actually *abusing* FUSE. FUSE isn't designed or intended to wrap one filesystem with a simulation of a different one. FUSE is intended to actually implement a filesystem proper. What that means is that the kernel performs certain filesystem operations on the FUSE filesystem, which calls back to essentially perform the same operations on the base filesystem (ext4). Double the operations. Also double the caching, which is horrendous because it means that you are storing the same cached file in RAM twice. That is the kind of thing that sdcardfs is intended to solve.
Now personally, I completely disagree with this approach. Sdcardfs (as with FUSE+sdcard.c) is a backwards compatibility layer that really should be removed altogether. Instead, access controls to the data really should be by way of ACLs. Yes, this will break some very old software, but its the right way to move forward.
kkozma said:
I was able to get a build to complete but it doesn't boot. I don't have the time today to go over it, but if anyone has some free time, feel free to take a look at the logcat and see if anything jumps out immediately.
boot.log
Click to expand...
Click to collapse
Well, the first thing that stands out is this;
03-13 02:38:08.029 0 263 W VendorServiceManager: failed to open binder driver /dev/vndbinder
Indeed, the factory kernel does not have any such driver. This is probably something related to "Project Treble", which is supposed to make it simpler to update the android platform while leaving the *vendor* platform unchanged. Sounds like this driver will have to be added to the kernel.
https://android-developers.googleblog.com/2017/07/shut-hal-up.html
There is also this, which happens immediately before the SIGABRT for surfaceflinger:
03-13 02:38:09.975 298 298 F Gralloc2: gralloc-mapper must be in passthrough mode
Code:
Mapper::Mapper()
{
mMapper = IMapper::getService();
if (mMapper == nullptr || mMapper->isRemote()) {
LOG_ALWAYS_FATAL("gralloc-mapper must be in passthrough mode");
}
}
That gralloc issue could be a consequence of the vndbinder issue.
Hmm... https://github.com/SiXROM/platform_device_moto_shamu/commit/86ebb7db1b0a23c4d0a09568a6414d3b9f140596
Note that their changes to the BoardConfig.mk are bogus, none actually apply to this hardware. But the additional PRODUCT_PACKAGES are possibly meaningful.
Might try a build using these three projects;
<project path="device/moto/shamu" name="platform_device_moto_shamu" groups="device,shamu,broadcom_pdk,generic_fs,pdk" remote="sixoreo" revision="oreo" />
<project path="kernel/moto/shamu" name="platform_kernel_moto_shamu" groups="device,shamu,broadcom_pdk,generic_fs,pdk" remote="sixoreo" revision="oreo" />
<project path="vendor/moto" name="platform_proprietary_vendor_moto" remote="sixoreo" revision="oreo" />
sixrom has also made a whole lot of other changes, but I suspect that they are more related to customizations rather than actual device functionality.
I had seen the vndbinder thing the other day and added it to the kernel I'm using. I actually had it booting yesterday, but managed to hose it up trying to fix bluetooth and then ended up losing my boardconfig.mk and device.mk so I have to start over on those two.
I actually tried building with that sixrom repo and it wouldn't boot at all. I suspect it's because it's based on Lineage whereas mine is straight from AOSP.
Getting ready to play around with it some more, hopefully I can get back to a booting rom again!
kkozma said:
I had seen the vndbinder thing the other day and added it to the kernel I'm using. I actually had it booting yesterday, but managed to hose it up trying to fix bluetooth and then ended up losing my boardconfig.mk and device.mk so I have to start over on those two.
I actually tried building with that sixrom repo and it wouldn't boot at all. I suspect it's because it's based on Lineage whereas mine is straight from AOSP.
Getting ready to play around with it some more, hopefully I can get back to a booting rom again!
Click to expand...
Click to collapse
How do you lose your make files? Did you forget to commit them to your git?
Commit often, ESPECIALLY when you have things (anything) working.
Then if you bugger it up, just roll it back, of git diff it to see what you changed.
I don't see any evidence of sixrom being based on anything besides aosp (certainly not lineage/cm)
Take a peek at their manifest, there's a few frameworks that they've messed with, a bunch of applications, but its mostly AOSP;
https://github.com/SiXROM/manifest/blob/oreo/default.xml
Yeah, that was a real derpasaurus moment for me there, but I'm back to a bootable situation.
- Bluetooth is still broken
- No Cellular Radio
- WiFi connects but causes a reboot immediately
- Not able to view anything on the SD Card & Camera asks for an SD card to be inserted. Oddly enough I am able to play the music that's on my sdcard.
I'll get everything pushed up to my github later so if anyone else wants to tinker with it...
They probably haven't pushed the working updates to device to get to where they. As I said, I built directly from their repo and it didn't work at all.
Edit: my github is https://github.com/vwmofo
if you want to put together a local manifest and pull it down, feel free.

[UPDATED][ROM OVERLAY][OnePlus One][Pie]Kali Nethunter[2020.1][22 Feb][Unofficial]

​
A Project By​
Code:
[FONT=Garamond][COLOR=Red][B][SIZE=4][CENTER]*** Disclaimer***[/CENTER][/SIZE][/B][/COLOR][/FONT]
[CENTER][FONT=System]The warranty of this device has ended ages ago but still, [B]please[/B] read this disclaimer.
This thing will break your device [B]HARD[/B] and possibly [B]HURT[/B] you if you don't follow instructions properly.
I [B][URL="https://en.wikipedia.org/wiki/Brick_(electronics)"][COLOR=Red]HARD BRICK[/COLOR][/URL][/B] my device 4 times before getting it right.
So please, if you follow these instructions, it [URL="https://en.wiktionary.org/wiki/should"][B]SHOULD[/B][COLOR=Gray][SIZE=1](3)[/SIZE][/COLOR][/URL] be safe for you to flash it without worries
since I have solved almost all of the problems that occur.
BUT nevertheless [B]myself, [URL="https://forum.xda-developers.com/member.php?u=6857433"]FiveO[/URL], [URL="https://www.kali.org/"]Kali Linux[/URL], [URL="https://www.offensive-security.com/"]Offensive Security[/URL], [URL="https://forum.xda-developers.com"]XDA[/URL][/B] and its staff, members and crew
and/or any of the [B]developers credited[/B] on this [B][URL="https://www.kali.org/kali-linux-nethunter/"]project[/URL][/B] will [B][COLOR=red][URL="https://dictionary.cambridge.org/dictionary/english/never"]NEVER[/URL][/COLOR][/B] be held responsible.
The tools provided in this thread are to be used in a legal context only.
Thank you.[/FONT][/CENTER]
PLEASE DO NOT QUOTE THE ENTIRE THREAD​Introduction
The Kali NetHunter is an Android penetration testing platform targeted towards Nexus and OnePlus devices built on top of Kali Linux, which includes some special and unique features.
Of course, you have all the usual Kali tools in NetHunter as well as the ability to get a full VNC session from your phone to a graphical Kali chroot, however the strength of NetHunter does not end there. We've incorporated some amazing features into the NetHunter OS which are both powerful and unique. From pre-programmed HID Keyboard (Teensy) attacks, to BadUSB, Man In The Middle attacks, to one-click MANA Evil Access Point setups, access to the Offensive Security Exploit(1) Database(2)...
And yes, NetHunter natively supports wireless 802.11info frame(1) injection(2) with a variety of supported USB NICs.​
Click to expand...
Click to collapse
NetHunter Editions
NetHunter can be installed on every Android device under the sun using one of the following editions:
{
"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"
}
The following table illustrates the differences in functionality:
The NetHunter-App specific chapters are only applicable to the NetHunter & NetHunter Lite editions.
The Kernel specific chapters are only applicable to the NetHunter edition.
Click to expand...
Click to collapse
Images
NetHunter Apps
NetHunter Companion Apps
Nethunter Kex
Kex Docs
Nethunter Store
Nethunter Store F-Droid and others repo add-on
Nethunter Terminal
Click to expand...
Click to collapse
NetHunter and NetHunter Lite ROM compatibility test result on Android PIE
[ROM][9.0][BACON][OFFICIAL]Syberia Project
syberia_bacon-v2.6-20190622-1327-OFFICIAL = Pending
syberia_bacon-v2.9-20190921-0756-OFFICIAL = Pending
[ROM][9.0][OFFICIAL][bacon] LineageOS 16.0 for OnePlus One
lineage-16.0-20190620-nightly-bacon-signed = Success
lineage-16.0-20190701-nightly-bacon-signed = Success
lineage-16.0-20191130-nightly-bacon-signed = Failed
[ROM][9][Pie][Bacon][UNOFFICIAL] crDroid 5.5 (6/16/2019)
crDroidAndroid-9.0-20190616-bacon-v5.5 = Pending
[ROM][9.0.0][PIE] ViperOS 6.1 [BACON][UNOFFICIAL]
Viper-bacon-20190219-v6.1-UNOFFICIAL = Pending
[ROM][9.0.0][WEEKLIES] CarbonROM | cr-7.0 [bacon]
CARBON-CR-7.0-OPAL-RELEASE-bacon-20191120-0302 = Pending
[ROM] [OFFICIAL] [AOSP] Arrow OS [Pie] [9.0.0_r44] | Bacon [2019-07-21]
Arrow-v9.0-bacon-OFFICIAL-20190613 = Pending
Arrow-v9.0-bacon-OFFICIAL-20191016 = Pending
[ROM][9.0][OFFICIAL]Superior OS Nemesis[Bacon][16-09-2019]
SuperiorOS-Nemesis-bacon-OFFICIAL-20190630-0838 = Failed
SuperiorOS-Nemesis-bacon-OFFICIAL-20191012-0637 = Failed
Will do 2nd test for SuperiorOS
[ROM]-[bacon]-[OFFICIAL]-Havoc-OS-[9.0.0]
Havoc-OS-v2.6-20190626-bacon-Official = Success
Havoc-OS-v2.9-20190912-bacon-Official = Success
[ROM][9.0.0_r37] POSP v2.3 - bacon [OFFICIAL][WEEKLIES]
potato_bacon-9-20190719.Baked-v2.3.WEEKLY = Pending
[ROM][LineageOS][Android 9.0.0r40][OMS]TugaPower™ 19.0
TugaPowerP21_OP1 = Failed
TugaPowerP22_OP1 = Failed
TugaPowerP23_OP1 = Failed
Result on TWRP
twrp-3.3.1-0-bacon = Nethunter Flashable
TWRP 3.3.1-K1 = Nethunter Unflashable
Unofficial TWRP 3.2.1-1 by TugaPower = Nethunter Flashable(Stable)
Click to expand...
Click to collapse
SELinux Issues
SELinux will effect HID Interface functionality as well as SafetyNet, please download SELinux mod changer to solve this problem.
Click to expand...
Click to collapse
Download
NetHunter
Nethunter 2020.1 Stable
NetHunter Lite
Nethunter Lite 2020.1 Stable
Gapps
MindTheGapps
F-Droid Store
F-Droid
Click to expand...
Click to collapse
NetHunter Rootless Editions
Maximum flexibility with no commitment
Usage
Note: The command nethunter can be abbreviated to nh.
Tip: If you run kex in the background (&) without having set a password, bring it back to the foreground first when prompted to enter the password, i.e. via fg <job id> - you can later send it to the background again via Ctrl + z and bg <job id>
To use KeX, start the KeX client, enter your password and click connect
Tip: For a better viewing experience, enter a custom resolution under “Advanced Settings” in the KeX Client
Tips
Run apt update && apt full-upgrade first thing after installation. If you have plenty of storage space available you might want to run apt install kali-linux-full as well.
Firefox won’t work on unrooted devices. Just replace it with Chromium via: apt remove firefox-esr apt install chromium Next: ~ Find the “Chromium Web Browser” item in the application menu ~ right click and select “Edit Application” ~ Change the “Command” to /usr/bin/chromium --no-sandbox %U
All of the penetration testing tools should work but some might have restrictions, e.g. metasploit works but doesn’t have database support. If you discover any tools that don’t work, please post it in our forums.
Some utilities like “top” won’t run on unrooted phones.
Non-root users still have root access in the chroot. That’s a proot thing. Just be aware of that.
Galaxy phone’s may prevent non-root users from using sudo. Just use “su -c” instead.
Perform regular backups of your rootfs by stopping all nethunter sessions and typing the following in a termux session: tar -cJf kali-arm64.tar.xz kali-arm64 && mv kali-arm64.tar.xz storage/downloads That will put the backup in your Android download folder. Note: on older devices, change “arm64” to “armhf”
Please join us in our forums to exchange tips and ideas and be part of a community that strives to make NetHunter even better.
Click to expand...
Click to collapse
Instructions
NetHunter & NetHunter Lite
Skip this step if device already rooted
Preparation
Backup everything including internal storage.
Download Bacon Root Toolkit
Unlock bootloader and root(+flash custom recovery) your device.
Reboot to recovery
Flash TWRP use TugaPower
Reboot back to recovery and continue with flashing instruction
Flashing
Please make sure batteries are above 90%
Backup everything including internal storage,
Erase everything, Advance Wipe tick on cache, dalvik, system, data and internal storage, after that Format Data type YES.
(you can proceed without wiping internal storage but it can cause unknown problem)
Reboot back to TWRP
Flash ROMs
(Please choose ROM that already tested if possible)
Flash Magisk 20.3
Flash Gapps
(Please use MindTheGappps version instead of OpenGapps since it's has BusyBox pre install that could cause problems after flashing)
Reboot System and proceed with the start-up, after start-up completed, enable developer’s mode.
Reboot back to TWRP and flash Nethunter 2020.1
Reboot back to system.
NetHunter Rootless
Android Device (Stock unmodified device, no root or custom recovery required)
Installation
Install the NetHunter-Store app from https://store.nethunter.com
From the NetHunter Store, install Termux, NetHunter-KeX client, and Hacker’s keyboard
Note: The button “install” may not change to “installed” in the store client after installation - just ignore it. Starting termux for the first time may seem stuck while displaying “installing” on some devices - just hit enter.
Open Termux and type:
Code:
[LIST=1]
[*]termux-setup-storage pkg
[*]install wget
[*]wget -O install-nethunter-termux https://offs.ec/2MceZWr
[*]chmod +x install-nethunter-termux
[*]./install-nethunter-termux
[/LIST]
Happy Hunting​
Click to expand...
Click to collapse
Post Installation Setup
Open the NetHunter App and start the Kali Chroot Manager.
Install the Hacker Keyboard from the NetHunter Store using the NetHunter Store app.
Install any other apps from the NetHunter app store as required.
Configure Kali Services, such as SSH.
Set up custom commands.
Initialize the Exploit Database.
Click to expand...
Click to collapse
Frequently Asked Questions
Q - Documentation and Attack Descriptions
A- Attack descriptions as well as some documentation to get you started with the installation and setup of Kali NetHunter can be found at Nethunter Wiki
Q - Is Kali NetHunter an Android ROM?
A- Kali Linux NetHunter is not a ROM but is meant to be installed over an existing stock factory image of Android. It can also be installed over some Cyanogenmod based ROMs depending on device support. It is heavily based on using custom kernels and only supports a select number of devices. We're relying on you, the community, to port your devices for the full Kali NetHunter experience.
Q - Does NetHunter support Marshmallow, or Nexus 9 devices?
A - Yes, check our wiki for more information on supported devices and ROMs wiki
Q - What kind of attacks does NetHunter support?
A - Our wiki has a list of included attack tools wiki
Q - NetHunter is awesome! How do I install it?
A - Follow the instructions on the Installation wiki
Q - What is the best wireless card for NetHunter?
A - A list of supported devices and chipsets wiki
Click to expand...
Click to collapse
Thanks To/Credits/Source Code
Code:
[FONT="Franklin Gothic Medium"]# [URL="https://www.gsmarena.com/oneplus_one-6327.php"]OnePlusOne[/URL]
[oneplus1]
author = "[URL="https://twitter.com/_binkybear?lang=en"]binkybear[/URL] & [URL="https://twitter.com/yesimxev/with_replies"]yesimxev[/URL]" for the [URL="https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-devices/tree/master/pie/oneplus1"]zImage-dtb and Module[/URL]
version = "2.2"
devicenames = bacon A0001 one OnePlus
block = /dev/block/platform/msm_sdcc.1/by-name/boot
[URL="https://forum.xda-developers.com/member.php?u=4544860"]osm0sis [/URL]for the [URL="https://github.com/osm0sis/AnyKernel3/"]AnyKernel3 Ramdisk Mod Script [/URL]Customized for NetHunter
[URL="https://forum.xda-developers.com/member.php?u=5672995"]jcadduono [/URL]for the [URL="https://github.com/jcadduono/lazyflasher"]lazyflasher[/URL]
[URL="https://twitter.com/re4sonkernel?lang=en"]re4son [/URL]for the [URL="https://gitlab.com/kalilinux/nethunter/apps/kali-nethunter-app"]Nethunter App[/URL], [URL="https://www.kali.org/docs/nethunter/"]Documentation[/URL] and [URL="https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project/-/tree/master/nethunter-rootless"]NetHunter Rootless[/URL]
[URL="https://www.kali.org/"]Kali Linux[/URL] for the [URL="https://gitlab.com/kalilinux/nethunter/build-scripts/kali-nethunter-project"]Nethunter Project[/URL]
[URL="https://lineageos.org/"]LineageOS[/URL] for the [URL="https://github.com/LineageOS/android_kernel_oppo_msm8974"]Kernel Source Code[/URL]
[URL="https://forum.xda-developers.com/member.php?u=4841620"]Timmmmaaahh[/URL] for Proofreading[/FONT]
​
Hello XDA Members,
This is Official Nethunter 2019.4 Originally for OnePlus One Android Marshmallow that i port with Android PIE Boot-Patcher.
It's a stable build if you flash with a suitable ROM, so please check the Test Results before flashing,
The ROM compatibility test is still ongoing, and i will update it regularly.
Nethunter 2019 has some issue with Older Devices on latest ROM build, For example on Lineage 16, Nethunter will not work after July build, it will cause boot loop or error on Lineage newer build,
but this problem is not the same with all ROM,
example Havoc-OS work with Nethunter 2019 without any issues, even with September build.
I still finding a way to fix this issues, and i intend to solve this before i release Nethunter 2020.1 next year.
That all update i have for now.
Thank You for participating, have a great day.
Sent from my OnePlus One using XDA Labs
Heck yeah, nice to see seething like this finally ported to pie
Glad to see you finally releasing! Looking forward to testing it on my sweet old Bacon (when I ever find some time, lol)!
wow really nice, any idea why Kex only show blue screen with pointer? now menu or something else? sorry its been a year since lastime im try kali net hunter/
ender1324 said:
Heck yeah, nice to see seething like this finally ported to pie
Click to expand...
Click to collapse
Thanks, I'm happy to see you like it.
Timmmmaaahh said:
Glad to see you finally releasing! Looking forward to testing it on my sweet old Bacon (when I ever find some time, lol)!
Click to expand...
Click to collapse
Thank you Timmy and thanks for all the help too, hope you do find some time to try it:good:.
xsetiadi said:
wow really nice, any idea why Kex only show blue screen with pointer? now menu or something else? sorry its been a year since lastime im try kali net hunter/
Click to expand...
Click to collapse
If this what you meant(refer attachment) then it's the new Kali Desktop Xfce user interface.
Not like that. There's no start menu. Only blank screen with pointer like this
Installation tips.
Hello FairuzOnn and thank you very much for your hard work, it is appreciated.
I like the way your post is written, it's easy to read.
I am preparing my OPO for Nethunter install over a new ROM (lineage-16.0-20190701-nightly-bacon-signed) and I have a question for you. You mentionned at point #2:
"Erase everything, Advance Wipe tick on cache, dalvik, system, data and internal storage, after that Format Data type YES".
That means there will nothing left on the OPO except TWRP. So my understanding is that I should use adb sideload to install the ROM.ZIP from my computer. If not, can you tell me more about this?
Normally, I download the ROM to my OPO and then flash it with TWRP but I think it's better to "clean" the phone and start fresh.
Can you run EDXposed and Multirom? If not, I'll backup after the ROM/Nethunter install before I install those.
Again, thank you very much.
xsetiadi said:
Not like that. There's no start menu. Only blank screen with pointer like this
Click to expand...
Click to collapse
Hi xsetiadi sorry for the very late reply.
Try update chroot
on nethunter terminal
Code:
apt-get update
apt-get dist-upgrade
That should solve the problem.
2643625 said:
Hello FairuzOnn and thank you very much for your hard work, it is appreciated.
I like the way your post is written, it's easy to read.
I am preparing my OPO for Nethunter install over a new ROM (lineage-16.0-20190701-nightly-bacon-signed) and I have a question for you. You mentionned at point #2:
"Erase everything, Advance Wipe tick on cache, dalvik, system, data and internal storage, after that Format Data type YES".
That means there will nothing left on the OPO except TWRP. So my understanding is that I should use adb sideload to install the ROM.ZIP from my computer. If not, can you tell me more about this?
Normally, I download the ROM to my OPO and then flash it with TWRP but I think it's better to "clean" the phone and start fresh.
Can you run EDXposed and Multirom? If not, I'll backup after the ROM/Nethunter install before I install those.
Again, thank you very much.
Click to expand...
Click to collapse
Hello
Thank you for the compliment
You can use adb sideload or adb push, but the best way to flash ROM is by using USB Pendrive or USB OTG.
By the way I recommend using Havoc ROM, it's currently the most stable for nethunter.
You can use EDXposed but it will break safety net,
As for Multirom, I'm still working on it, the current build i made for android pie has lot of issues and can cause hard brick.
I will update you if Multirom android pie build stable to use.
This looks so impressive. Wish I were smart enough to find use for it lol
Hi! How to fix? I'm using I am using TWRP from the developer Kutep0v. (TWRP 3.2.1-K2).
thoiloidainhan said:
This looks so impressive. Wish I were smart enough to find use for it lol
Click to expand...
Click to collapse
Hi thoiloidainhan,
You can visit offensive security to learn about ethical hacking, please try it if you got the time.
Бахрам Байрамза said:
Hi! How to fix? I'm using I am using TWRP from the developer Kutep0v. (TWRP 3.2.1-K2).
Click to expand...
Click to collapse
Hello Бахрам Байрамза,
You can solve this problem, by using stock TWRP or Unofficial TWRP 3.2.1-1 by TugaPower.
For some reason all KutepOv TWRP not compatible to flash NetHunter.
HAPPY HUNTING
FairuzOnn said:
Hi thoiloidainhan,
You can visit offensive security to learn about ethical hacking, please try it if you got the time.
Hello Бахрам Байрамза,
You can solve this problem, by using stock TWRP or Unofficial TWRP 3.2.1-1 by TugaPower.
For some reason all KutepOv TWRP not compatible to flash NetHunter.
HAPPY HUNTING
Click to expand...
Click to collapse
Thanks!
Бахрам Байрамза said:
Thanks!
Click to expand...
Click to collapse
Your Welcome:good:
Hi there, thanks for all your hard work. I'm about to install but which base rom would you recommend as some time has passed.
amd-dude said:
Hi there, thanks for all your hard work. I'm about to install but which base rom would you recommend as some time has passed.
Click to expand...
Click to collapse
Hi sorry for the late reply,
Right now I recommend HACOV ROM,
anyway I currently compile new update, version 2020.1,
I'm planing to finish it and upload it the latest by tomorrow,
batter wait for this update.
FairuzOnn said:
Hi sorry for the late reply,
Right now I recommend HACOV ROM,
anyway I currently compile new update, version 2020.1,
I'm planing to finish it and upload it the latest by tomorrow,
batter wait for this update.
Click to expand...
Click to collapse
Will do, I'll download all the other files in the meantime.
FairuzOnn, wondering if you completed the new version yet?
nickkilla said:
FairuzOnn, wondering if you completed the new version yet?
Click to expand...
Click to collapse
Hi sorry for the late reply, i Have finish most of it, got some problem with NetHunter App I'm working on it, I'm really sorry for the delay. I'm at Gaylord California right now, i have to attend a conference here, i think i will post the new update in 2 or 3 days time.
Sent from my OnePlus One using XDA Labs
FairuzOnn said:
Hi sorry for the late reply, i Have finish most of it, got some problem with NetHunter App I'm working on it, I'm really sorry for the delay. I'm at Gaylord California right now, i have to attend a conference here, i think i will post the new update in 2 or 3 days time.
Sent from my OnePlus One using XDA Labs
Click to expand...
Click to collapse
No worries. Thanks for the update.

Development MARS_SOMs - Stock - VoLTE, VoWifi, Carrier Video Calls

MARS SOM
{
"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"
}
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 13 Stock Xperia FW
Magisk Init.d Injector
Download:
Sign in - Google Accounts
Bugs:
Report them if You found one!
Donations:
paypal.me/miustone​
Reserved <3
Nice work. I'm glad to already see some custom ROMs (well, in that case, SOM).
However, this is the first time I encounter a SOM, is it just a Magisk module that can be turned on and off at will, switching between stock and Mars? Or shouldn't I do that?
Miustone said:
Welcome to MARS SOM
The first so called SOM
Systemless-On-Memory
SOM - The right naming for a new age of Android ROMs
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into two Zip Files...
Features:
Full Camera API2 Support
Full Pixel User Interface
Full Darkmode Support
Ported Pixel Apps
Ported Pixel Features
Enabled various Android Features
Enhanced Security Support
Enhanced Display 4K HDR Support
Enhanced Audio Output
Enhanced Audio Input
Enhanced Display Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Beta or Canary Channel
Android 11
A way to extract and create Zip Files
(For GitHub Zips)
Downloads:
Miustone - Overview
Founder of Dev Ice Software Technologies. Miustone has 10 repositories available. Follow their code on GitHub.
github.com
Note: Zips from GitHub can't be flashed ootb.
GitHub?!:
Extract the 2 Downloaded Zips and repack everything inside of the second "MARS_SOM_XXX" Folders to Zips
Flash these Zips with Magisk and enjoy <3
Bugs:
QuickSwitch is needed for the Pixel Launcher
Donations:
paypal.me/miustone​
Click to expand...
Click to collapse
Could you please tell me where can I obtain more information about this "Mars Som" and more details instruction to install it. Thanks for your reply.
Thanks for Your Interest! I'm reconstructing the SOMs on GitHub and the ReadMe's there will be updated soon with more Infos! For now, just Check My (Discontinued) MARS-SOM Repo on GitHub...
BR
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
tonysunshine said:
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
Click to expand...
Click to collapse
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Miustone said:
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Click to expand...
Click to collapse
Hi what do you mean by use them separated? Like install/activate the base module, reboot, then do the system module?
Yep, it could be one of them or both which causes the Bootloops. I updated the Base so it might be that... The System should cause less Problems at the end... @tonysunshine
I also got a bootloop after installing the zips. I tried following the instructions on your github and was able to do the device simulation with the props config module, but can't follow the next step "Download and extract the NgaResources.apk to /MARS_SOM_SYSTEM/system/product/app/NgaResources" as there's no NgaResources.apk file anywhere on the github that I can find. Could it be this missing file that's causing issues?
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
akkk44 said:
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
Click to expand...
Click to collapse
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Miustone said:
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
akkk44 said:
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
Click to expand...
Click to collapse
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Miustone said:
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Click to expand...
Click to collapse
Understood! I will test the module out sometime……
akkk44 said:
Understood! I will test the module out sometime……
Click to expand...
Click to collapse
Great! Thanks in advance!
Miustone said:
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
tardis_42 said:
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
View attachment 5445471
Click to expand...
Click to collapse
Thanks for pointing out. I'm uploading the latest Version to this Google Drive Directory rn! Sorry for the Trouble...
Updated the Thread, MARS_SOMs and GitHub<3
HUGE UPDATES INCOMING!
MARS will be available over GitHub Releases so You can easily Download ready-to-use Zips of MARS for Magisk. Also included are now OTA Updates for MARS over Magisk and the focus Changed to GSIs again. Use PHH AOSP 12 or PIXEL EXPIERENCE 12 by Ponces to unleash Your Xperias

General [Kernel][Kali-NetHunter]Pixel 6/Pixel 6Pro Oriole/Raven[Kernel][Kali-NetHunter]

{
"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.
Disclaimer::
Please use this Kernel in accordance with local law and with the privacy of yourself and others in mind. Not responsible for any charges you might accrue, bail money or fines if you choose to use it for unlawful reasons
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.
The mad tech clown is back with another Kernel for all of the Kali-linux-nethunter users wanting the portability of kali-nethunter for their Pixel 6 and 6Pro devices codenamed Oriole and Raven .
I now bring you the
Mad-Kali-Maxhunter kernel for raviole
Some of the features include:
-power efficient workqueues
-fsync switch
-boeffla wake lock blocker
-force usb fastcharge
-mm: oom_kill: Reduce some verbose logging
-cpufreq: add cleanslate battery optimizer feature
-/dev/tmp and /dev/tmp/ mount
-full bluetooth support
-Wifi injection
-dvb / sdr support
Plus:
-Everything neeeded to use kali properly on your device plus some systemd stuff
-dns resolver support
-full usb/otg support
See source commits for more
This is not a super fancy pot luck kernel with every allowable feature. This is tuned out quite effeciently and ive found that adding certain features or too many causes heat to rise and we all know thats not good with this device.
Source
GitHub - Biohazardousrom/android_kernel_google_raviole
Contribute to Biohazardousrom/android_kernel_google_raviole development by creating an account on GitHub.
github.com
Download
16.68 GB folder on MEGA
74 files and 20 subfolders
mega.nz
How to Flash:
pre-requisites:
Franco Kernel Manager & root
Download zip to the internal storage of your device.
Open FKM and tap 3 line menu and choose flasher.
Choose manual flash and navigate to the zip file, select it and choose reboot after flash.
Enjoy
For more support
gs101 and gs201 development/support
Pixel 6/pro & 7/pro discussion group for general support and development
t.me
Thanks to
acuicultor
freak07
tbalden
arter97
andip71
for all your development
reserved
Some notes to help you get the Kali-nethunter system set up on your device.
1. Please install the Kali-nethunter magisk modules. These will have the firmwares needed to use the various USB dongles for wifi/bluetooth.
2. Visit this site to download and install the Kali-nethunter store https://store.nethunter.com/en/
3. After installing the store app let it update and then install these 3 apps
-Kali-nethunter installer updater and interface (aka kali-nethunter gui)
-Kali-nethunter terminal
-Kali-nethunter bvnc and kex manager
once installed open the kali gui app and ok any permissions it asks for. it will then force close.
Note:: Since android 12 the gui quit asking for several permissions needed for running scripts in the terminal so you will need to download the attached file kadb.sh to your pc then connect your device to the pc and open a command prompt and run
./kadb.sh
this will grant the missing permissions and allow the gui to open again without it force closing. script was written for linuxed based pc's. if you use windows just open it up and copy and paste the comnands one by one.
or if you have another rooted device you can connect the two via otg and run from the extra rooted device
4. open the gui app once more and navigate to install and start chroot. if you have your own just add the location to the given box when you choose install. for everyone else let the app download it and install from the Kali repository.
Note:: this will take some time please do not exit the app while in the process of downloading or installing
5. to make it easier to enter the kali nethunter terminal app create a custom comnand in the gui. it can be anuthing ls, apt-get update just what ever. then save it to kali and use it when ever you want to use the terminal
Note:: If you want to use the Kex manager/vnc you will need the root password to run programs as root. That password is toor.
Also you can activate wlan0 and wlan1 without a usb dongle. But for some reason it wont allow use of bluetooth without a dongle. i never could find a rhyme or reason for this but i have found when using bluetooth on my pc that kali would not use the built in bluetooth either and i would have to use a dongle. this is probably by design for stealth reasons but dont quote me.
I have found dual wifi and bluetooth adapters in the past and they work simultaneously
This is great! Will it be possible for you to share the kernel build instructions here? I cloned you repo into private/gs-google and ran BUILD_KERNEL=1 ./build_slider.sh -j$(nproc) after that. I do see the kernel files in out/mixed/dist. I flashed them, and it gave me boot loops.
It would be awesome if you could share some build instructions as well.
you can find more info on building kernels here....
Building Kernels | Android Open Source Project
source.android.com
but the steps i took were to initialize and sync the repo listed in the link above. then from there i made my cherry picks. next i went to /arch/arm64/configs and edited the gki_defconfig to match the needed configs i needed for kali linux. after that i ran build/build.sh.
it will error after that because the abi_symbol_allowlist in /android/abi_gki_aarch64_generic file will need updated with the new symbols now compiled in the newly customized kernel.
then after you have corrected all the errors and its built a kernel you will have 4 items to flash..
boot.img
dtbo.img
vendor_boot.img
vendor_dlkm.img
dtbo and boot are flashed in fastboot while vendor_boot and vendor_dlkm are flashed in fastbootd.
but the easiest way to flash is by making an anykernel.zip
also need to point out that some custom roms will not allow you to flash custom kernels so i would hop on tg and ask the maintainer if that rom permits flashing kernels else your gonna have a hard time
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
evansfromza said:
thanks for the build @Duhjoker. I managed to flash it on a Pixel 6 and install NetHunter but wifi monitoring mode doesn't work. This is the output from `airmon --debug`
View attachment 5705665
Click to expand...
Click to collapse
i am aware of the problem and im looking into it. to be honest i never could get airmon-ng to work on any android.
im thinking monitor mode may need to be enabled first through /sys/ like qualcomm but i could be wrong. this is my first exynos kernel and im having to relearn stuff.
gahndii said:
Hey Duhjoker! Thanks for your work on this! Its a dream come true! I just have one question. Is there any chance we will see a pixel 6a version of this kernel with wifi injection? Or is this a pipedream?
Click to expand...
Click to collapse
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
ok so i dont know whats up with android 13 kernel source but so far none of the builds are booting. ive been at it since release and no go.
but be assured i am working on stuff
Duhjoker said:
I can but i dont own a pixel 6a. The build would have to completely blind but if your willing to test i can try. i did the same for the pixel 3 so it shouldnt be a problem but read next post to see whats up on the current state of building
Click to expand...
Click to collapse
Though I wouldn't mind testing something like that, however would not consider myself a reliable tester. I'm more of a tinkerer honestly. I haven't flashed a rom in 4-5 years haha I gave up years ago on a kernel with wifi packet injection drivers baked in. (for a model I owned) I would not be able to give you solid reliable feedback but id happily try it out for fun. From what ive been reading looks like im staying on Android 12 for a bit longer.
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
acuicultor said:
The ramdisk provided by Google for A13 is the issue, you must extract it from vendor_boot and replace it inside prebuilts folder, thanks to freak07 for the solution.
Here's the commit from him.
Click to expand...
Click to collapse
Thank you so much for that. it was driving me crazy and couldnt understand what the problem was.
so now we have kali coming for a13 in a couple days
ok guys Mad-Kali-MaxHunter-Raviole-T for android 13 is now live and linked in op.
I have been researching the wifi monitor mode and packet injection properties on the wlan and heres the state of the driver from my google searches
The bcm4389 wifi 6e client set of chips was announced in 2020 by broadcom and can be found in the Samsung galaxy s21 and google pixel 6, 6pro and 6a models along with some xiaome phones.
For us that means that the drivers and firmware are so new that theres been very little development for it. i myself was only able to find a bluetooth patch that im sure has already been picked up by the google source kernel devs.
from what i can tell of the other drivers by looking at the nexmon github page and further reading the previous wlan modules needed patched firmware to enable airmon-ng.
im still doing research into how to fix this but if anyone has any clues please speak up.
but for now if you should be able to get by using a usb wifi dongle.
Hi, @Duhjoker I was able to install everything successfuly but it seems like the kernel is missing some features not directly related to Kali but that would be nice to add.
HID attack support from Rucky, and ISO usb host from DriveDroid.
I'm using a Pixel 6 Pro on A13
Thanks for your work
Unfortunately, usb wifi dongles aren't working even if they're supported, even after installing their firmwares. Something's wrong with the kernel.
I have good news. Seems google did the hard work for us on hacking the firmware for monitor mode and it looks like we can now use monitor mode to catch packets "NATIVELY".
please read here for the details.
Get BCM4389 into monitor mode for WIFI sniffing
Hey all, I was trying to watch beacon frames transmitted by my access point, but had no capable hardware in my house to sniff it. Or did I? Turns out, Pixel 6 / Pixel 6 Pro can do it. Here's my howto...
forum.xda-developers.com
i havent tested this fully yet but a friend in my tg chat helped me snag the binaries rc files and best of all the firmware.
i dont currently have a magisk module yet but with root copy the vendor folder in the zip to /data/adb/modules pick any module for example
/data/adb/modules/busybox-ndk/system
reboot and enjoy
edit: you made need to chmod the binaries after placing them
deleted
tried that, it doesn't work.
also, wifi dongles are recognized by lsusb but not mounted (airmon-ng only shows phy0 - internal wlan interfaces)

Categories

Resources