[ABANDONED] AndroPlusKernel v43 - Xperia Z4 Tablet Android Development

***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

Related

[SOURCES][DEVONLY] CyanogenMod 11.0

Hi,
I've started to investigate what is needed to build CyanogenMod 11 for the slte. I need to understand what we need to compile for exynos5430. There are extra repositories available. If anbody knows how to port a ROM or knows C/C++ and want to work together, feel free to contact me! Reading and understanding strace output is essential.
I will post my progress in this thread.
TODO
# RIL
Add WB (wide band) support to audio ril and add missing mixer values to mixer_paths.xml (WORK IN PROGRESS)
Test usb and wifi tethering.
Fix VoIP calls
# WIFI
Try to find a better solution for getting wifi working. Currently it is a hack in the wifi nl80211 driver. We should check if the kernel can indicate that the p2p device can't be set into station mode.
Revisit macloader and network patches to set nvram path. Maybe only the macloader should set the path. (WAITING FOR REVIEW)
# Media
Fix video decoding
Fix video recording
# CMHW (Samsung specific hardware configuration)
Add BOARD_HARDWARE_CLASS += hardware/samsung/cmhw in BoardConfig.mk
VibratorHW.java is wrong, copy to device tree and modify it? Check other devices how to fix it.
# MMS
Create overlay/packages/apps/Mms/res/xml/mms_config.xml
# Audio
Revisit sound recording, capture volume to low?
Check if CM DPS Manager is working.
Do we need voicefx in audio_effects.conf
# USB OTG
Fix attaching usb sticks and disks with CM. Need to look what CM expects and then fix init.rc
# MTP
MTP doesn't work, it uses not the standard mtp gadget driver.
Debug MTP server and driver to find out what is going wrong ...
mtpg_read() fails with a dev error and returns EIO ...
# NFC
Get NFC working (low priority) (maybe remove it, needs to much battery)
# DRM
Try to fix mobicore
If you know how to write C code or Java code, please pick an item and send patches. The java task is to reverse engineer the MTP server code. Use JAD for this. The rest is C/C++ code. You should know how to use strace and gdb.
-- modpunk
Package Complete: /home/asn/workspace/projects/cyanogenmod/system/out/target/product/slte/cm-11-20141109-UNOFFICIAL-slte.zip
My USB OTG cable should arrive tomorrow, then I can do a backup of the stock ROM and see if CM will boot. The slte SoC looks similar to the the manta SoC. At least they have the same GPU. Maybe it works with the 4250 sources ...
It doesn't look good. The hardware is much more different from exynos5420 than thought. I'm not sure if a port is possible without deeper insight into the SoC.
You said, you tried it with the mantas kernel? Thats google nexus 10 with a Exynos 5250?
I think, the google note 3 or google note 10.1 2014 might be better choices to start with - they use the Exynos 5420, form what i see it looks like 5430 is a advanced version of it using the 20nm process.
Both are octacores where every core is accessible.
- there seems to be a cyanogenmod repository holding 5420 kernel code...
on Samsung OSRC there seems to be source code for the Alpha available - but i can't download it, and can't make a login - i can't make a password that is accepted by that page... weird.
DThought said:
You said, you tried it with the mantas kernel? Thats google nexus 10 with a Exynos 5250?
Click to expand...
Click to collapse
No, I didn't. I tried it with the manta hardware support which is a exynos5420 chip. I fixed the Kernel sources for the slte and it is working just fine.
DThought said:
I think, the google note 3 or google note 10.1 2014 might be better choices to start with - they use the Exynos 5420, form what i see it looks like 5430 is a advanced version of it using the 20nm process.
Click to expand...
Click to collapse
The gpu seems to be differnt too. I've looked at the sources and the kernel interfaces they access are different too.[/QUOTE]
I have that kernel running already. I have to dive deeper. Maybe just the HDMI support is different and we don't need that.
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G850F
Two painfully slow download links, haven't had much experience with Samsung source before, is there a difference between the two variants listed for download that i'm missing before I start to download one ? I note one has SEA in the title of the file and the other doesn't.
You need the KK version. At least the source is cleaner However it needs a bunch of bugfixes that it even compiles! You can find my kernel tree (with fixes) here:
http://git.cryptomilk.org/projects/android/android_kernel_samsung_slte.git/log/?h=cm-11.0
This kernel is running on the recovery and I'm working on the exynos5 sources to prepare them for this kernel. I'm currently trying to fix hwcomposer so it works with decon-fb.
modpunk said:
It doesn't look good. The hardware is much more different from exynos5420 than thought. I'm not sure if a port is possible without deeper insight into the SoC.
Click to expand...
Click to collapse
Well, two days later the world looks different ...
{
"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"
}
modpunk said:
Well, two days later the world looks different ...
Click to expand...
Click to collapse
congratulations man :victory:
as i've said earlier, i'm glad to have a dev like you on our device
modpunk said:
Well, two days later the world looks different ...
Click to expand...
Click to collapse
Dude. Awesome. Tell me there's some way I can donate to show my appreciation? Can't wait to try it out man. Keep it up!
tnicko said:
Dude. Awesome. Tell me there's some way I can donate to show my appreciation? Can't wait to try it out man. Keep it up!
Click to expand...
Click to collapse
Thanks, the question is if I will get it fully working. It is still a long way to go. However there is a donation button on the left I guess ...
modpunk said:
Well, two days later the world looks different ...
Click to expand...
Click to collapse
you are the man m8,nice job
as neofral said, nice to have you hire
ps .if you lake tester I`m hire...also your kernal will work only with Cyan or with TW
Awesome dude !
Downloading sources at 9kb/sec so should be done sometime this year !!
Sent from my SM-G850F
Congratulations from France !
Are you on FreeNode ?
Is there a channel we can hang in and collaborate in ?
DangerMUK said:
Are you on FreeNode ?
Is there a channel we can hang in and collaborate in ?
Click to expand...
Click to collapse
Yes, I am. I do not get Wifi working and I don't know what is going wrong. I suspect it is a kernel issue cause I don't get any messages in the kernel ring buffer. No work till next week ....
Could you post us some experimental build, i'm sure all of us would appreciate it?
What for? The only thing which works is that it boots. Everything else is broken so what I will get is a load of bug reports which tells me nothing works.
The sources are available. If you want to help with development, feel free to build it yourself
I will try publish the changes to the exynos5 tree soon.
I still do not understand how Android sends the START command to the wifi driver to give it power and load the firmware and start it up. If someone could shed some light on this it would be really helpful!
modpunk said:
I still do not understand how Android sends the START command to the wifi driver to give it power and load the firmware and start it up. If someone could shed some light on this it would be really helpful!
Click to expand...
Click to collapse
can you look at this page and see if you get your answer?
http://blog.linuxconsulting.ro/2010/04/porting-wifi-drivers-to-android.html
edit: also this one is interesting http://boundarydevices.com/android-wlan-the-rest-of-the-story/
and this:
Wifi module initialization:
To in SystemServer start will generate an instance of ConnectivityService, ConnectivityService the constructor creates WifiService the WifiStateTracker will create WifiMonitor receiving from the underlying event, WifiService, and WifiMonitor is the core of the whole module. WifiService is responsible for starting off wpa_supplicant itself which is a bit more tricky, to start off WifiMonitor monitor thread and the command to the wpa_supplicant WifiMonitor is responsible to receive event notifications from wpa_supplicant.
WiFi module to start:
WirelessSettings the initialization configuration by WifiEnabler Wifi button
When the user presses the WiFi button Android will call WifiEnabler of the onPreferenceChange, and then the call WifiManager by WifiEnabler setWifiEnabled interface functions, AIDL actual call is the WifiService setWifiEnabled function the WifiService then send itself an MESSAGE_ENABLE_WIFI message in the message code to enable real work: First, load the WiFi kernel module (the module position hard-coded "/ system / lib / modules / wlan.ko"), and then start wpa_supplicant (hard-coded configuration file "/ data / misc / wifi / wpa_supplicant.conf "), then WifiStateTracker to start monitor thread WifiMonitor.
from here: http://www.programmershare.com/3736477/

Kali NetHunter For HybridRom Concept EditioN

{
"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"
}
IF YOU DON'T KNOW WHAT IS NETHUNTER OR KALI(BACKTRACK) LINUX YOU DON'T NEED IT.
DISCLAIMER: I, ASSUME NO RESPONSIBILITY FOR ANY ILLEGAL ACTIONS AND/OR DAMAGE PERFORMED OR CAUSED BY INDIVIDUALS WHO USE IT FOR PURPOSES WHICH IT IS NOT INTENDED TO BE USED.
DESCRIPTION:
The Kali NetHunter is an Android ROM overlay that includes a robust Mobile Penetration Testing Platform. The overlay includes a custom kernel, a Kali Linux chroot, and an accompanying Android application, which allows for easier interaction with various security tools and attacks. Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, Evil AP MANA attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page. NetHunter is an open-source project developed by Offensive Security and the community.
More info
Kali NetHunter Application
Home Screen - General information panel, network interfaces and HID device status.
Kali Chroot Manager - For managing chroot metapackage installations.
Check App Update - For checking Kali NetHunter Android App updates.
Kali Services - Start / stop various chrooted services. Enable or disable them at boot time.
Custom Commands - Add your own custom commands and functions to the launcher.
MAC Changer - Change your Wi-Fi MAC address (only on certain devices)
VNC Manager - Set up an instant VNC session with your Kali chroot.
HID Attacks - Various HID attacks, Teensy style.
DuckHunter HID - Rubber Ducky style HID attacks
BadUSB MITM Attack - Nuff said.
MANA Wireless Toolkit - Setup a malicious Access Point at the click of a button.
MITM Framework - Inject binary backdoors into downloaded executables on the fly.
NMap Scan - Quick Nmap scanner interface.
Metasploit Payload Generator - Generating Metasploit payloads on the fly.
Searchsploit - Easy searching for exploits in the Exploit-DB
3rd Party Android Applications (WIP)
NetHunter Terminal Application
DriveDroid
USB Keyboard
Shodan
Router Keygen
cSploit
BUGS
The same as on original Nexus 5 version
REQUIREMENTS
Latest HybridRom Concept Edition + Advanced Kernel v2 from this thread. Don't install anything else.
Hands growing from a right place
External WiFi Adapter for Monitor Mode
INSTALLATION
Make sure you've read the requirements
Boot in TWRP
Install what you need with aroma installer.
Wait until process is finished (will take some time to extract packages)
DOWNLOAD
Kernel Sources
XDA:DevDB Information
Kali NetHunter Togari, ROM for the Sony Xperia Z Ultra
Contributors
Uncle Lucifer
Source Code: https://github.com/offensive-security/kali-nethunter
ROM OS Version: 5.1.x Lollipop
Version Information
Status: Testing
Created 2016-03-11
Last Updated 2016-03-11
Reserved
Reserved
Most of the things will work out of the box.while some of the scripts requires modifications, like changing patch and etc.
Unless you don't want to change storage patches, don't upgrade SuperSU binary.
I just figured out that it's somehow breaks symlinks, which can break a lot of scripts.
Also. when you install it, don't pick supersu, may cause a bootloop.
Seems like something is broken in the new supersu update.
Also I did a kernel update.
It includes updates for modules necessary for external wifi and usb attacks support.
I hope that they will soon add our device officially.
I got cannot boot and red LED flashing after flash "Kali NetHunter For HybridRom Concept EditioN" on "HybridRom Concept EditioN V2.0 ". Any step or version wrong? I need to restore factory image now(downloading).
pckeung said:
I got cannot boot and red LED flashing after flash "Kali NetHunter For HybridRom Concept EditioN" on "HybridRom Concept EditioN V2.0 ". Any step or version wrong? I need to restore factory image now(downloading).
Click to expand...
Click to collapse
It may happen if you didn't have advanced kernel v2.
You don't need flash whole rom again.
Just flash boot.img from concept with hotboot and you will have recovery.
Uncle Lucifer said:
It may happen if you didn't have advanced kernel v2.
You don't need flash whole rom again.
Just flash boot.img from concept with hotboot and you will have recovery.
Click to expand...
Click to collapse
oh Thank! I can restart the flashing process now.
Dear developers, can you build your kernel for Samsung Galaxy Tab 3.8.0 SM T311? (Cyanogenmod 13)?
Finally , the nethunter installed into my z Ultra successfully. But it restart when i enable monitor mode with my USB wifi. This problem has not appear in my nexus 5. I already flashed the "kernel update". I will try other USB wifi.
*i have school project about this topic. Thanks for help.
pckeung said:
Finally , the nethunter installed into my z Ultra successfully. But it restart when i enable monitor mode with my USB wifi. This problem has not appear in my nexus 5. I already flashed the "kernel update". I will try other USB wifi.
*i have school project about this topic. Thanks for help.
Click to expand...
Click to collapse
LOL, I was writing an extended essay back in school about wireless packets injection.
I was using nokia n900.
I've got a TP-Link WN721N and monitor mode works fine.
Didn't have any networks around with WEP encryption, so idk about injection.
Phone may reboot, but only if I disconnect external wifi.
And yeah, I enabled drivers, which were avaliable in my sources, so if your adapter is too old, then it might be missing.
Good luck with your project.
Feel free to write,if you need anything.
i find my tp-link lsusb command dut i cant start wlan0 bacause when i type ifconfig its not find my tp-link tl-wdn3200, i use xperia x ultra c6833.anythink what i can do about that?
shadow8 said:
i find my tp-link lsusb command dut i cant start wlan0 bacause when i type ifconfig its not find my tp-link tl-wdn3200, i use xperia x ultra c6833.anythink what i can do about that?
Click to expand...
Click to collapse
Wlan0 is your internal adapter.
Try
Code:
ifconfig wlan1 down
iwconfig wlan1 mode monitor
ifconfig wlan1 up
wlan card not found
Uncle Lucifer said:
Wlan0 is your internal adapter.
Try
Code:
ifconfig wlan1 down
iwconfig wlan1 mode monitor
ifconfig wlan1 up
Click to expand...
Click to collapse
when i type ifconfig wlan1 down i get wlan1 error while getting interface flags: no such device
and iwconfig wlan1 mode monitor i get Error for wireless request "set mode" (8B06) :
shadow8 said:
when i type ifconfig wlan1 down i get wlan1 error while getting interface flags: no such device
and iwconfig wlan1 mode monitor i get Error for wireless request "set mode" (8B06) :
Click to expand...
Click to collapse
Not all wlan adapters are supported, I think you should go to official wiki page and find if your model is supported.
wlan adapter not find
Uncle Lucifer said:
Not all wlan adapters are supported, I think you should go to official wiki page and find if your model is supported.
Click to expand...
Click to collapse
its supported because i already use that with kali my pc.i read its mayby kernel bug and some people download and instal somekind other version because they have samekind broplem.but i want to keep this1.and thx fast reply hopefully i get this work.ps i build y cable also and that giving power tp-link but no luck that1
shadow8 said:
its supported because i already use that with kali my pc.i read its mayby kernel bug and some people download and instal somekind other version because they have samekind broplem.but i want to keep this1.and thx fast reply hopefully i get this work.ps i build y cable also and that giving power tp-link but no luck that1
Click to expand...
Click to collapse
If it works on kali on pc, it doesn't mean that it's going to work on mobile.
It's not bug, just means that it simply does not have drivers for the specific device
Thx.i need,To check if i find drivers.afterall its not many wlan adapters what support monitor Mode.so i am so happy if some1 can say what wlan adapter support Xperia z ultra.and ofg thats need monitor Mode
Its bossible To add More attack software inside romm? Mayby somekind Phone and Bluetooth attack
please create one for xperia sp
electro_nik said:
please create one for xperia sp
Click to expand...
Click to collapse
Instructions are available on the official website.
Compiling it,not harder if is not easier than using it.

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

{
"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)

[ROM][F5121][WIP] Ubuntu Touch for Sony Xperia X

{
"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"
}
A Mobile Version of the Ubuntu Operating System
Ubuntu Touch is made and maintained by the UBports Community. A group of volunteers and passionate people across the world. With Ubuntu Touch we offer a truly unique mobile experience - an alternative to the current most popular operating systems on the market. We believe that everyone is free to use, study, share and improve all software created by the foundation without restrictions. Whenever possible, everything is distributed under free and open source licenses endorsed by the Free Software Foundation, the Open Source Initiative.
For more information check out the UBports website.
Known issues:
Recording video doesn't work
Changing volume in-call doesn't work
Contribute:
As not everything is working fully yet helping hands are welcome!
Follow the project management issue over at the Halium GitHub page:
https://github.com/Halium/projectmanagement/issues/98
Instructions (tested on Ubuntu 18.04):
First make sure to wipe /system & /data from within TWRP. The partitions must be ext4.
Make sure to upgrade your device to the latest stock Android 8.0 before continuing: https://developer.sony.com/develop/open-devices/get-started/flash-tool/
Download and install the UBports installer: https://github.com/ubports/ubports-installer/releases
OEM unlock your device: https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
Boot your device into fastboot mode by shutting it down and keeping the Volume Up button pressed while plugging in a USB cable between your phone and PC. The LED should be on and blue.
Flash the OEM binaries from: https://developer.sony.com/file/download/software-binaries-for-aosp-nougat-android-7-1-kernel-4-4-loire/ using:
Code:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
Run the UBports installer and follow the on-screen instructions
Reserved for future use
wtf bro i never expected to see ubuntu touch on any device again great news and good work! keep it up!
Too bad my device broke......gotta fix fast lol
I've updated download links and the instructions to enable call functionality. Testers welcome!
Ready for tests! Just need to install Ubuntu with current manual
Have I need to flash stock rom with android 7 or just flash binaries on stock android 8?
New tests to be done, we've recently gotten video decoding to work and I enabled basic camera support.
OP has been updated with the link to the newest images.
Feel free to post issues here if you are not feeling well with GitHub.
Regarding stock ROM or not:
Any system image should work, you can even wipe system as it's not used.
As long as the ODM partition is flashed everything should be good.
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
samijam said:
I'm trying this for the 2nd time and both times I can't get any audio in calls. I ran the commands in the first post. Any tips on what else to try? I'd really like to try this, test some more and help out, but it's the only phone I've got right now.
Click to expand...
Click to collapse
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
beidl said:
Did you run the commands through ssh or via the Terminal app? Mind doing a "select all" and copy-paste the output to some paste service?
EDIT: Also, did you reboot after issuing the commands?
Click to expand...
Click to collapse
Sorry for the late reply. I got it to work now. My problem was using an outdated system.img and boot.img. (oops, sorry, my bad!) I had downloaded the newer versions, but had them in the wrong directory. Once I deleted the old and installed the correct versions, I was able to get audio in calls and had the basic camera functionality.
---------- Post added at 16:43 ---------- Previous post was at 16:37 ----------
matiz098 said:
Thanks for the work on this.
I need a little bit more explanation on how to install this. I gave it a try, but I end up in getting a white boot screen with the sony logo. Installing SailfishOS with the flash.sh script works perfectly.
Questions:
- When do you need to use twrp? When running adb?
- Running the halium install script only works when booted into twrp. Is this correct?
- Do you need to manually boot into fastboot mode (volume up, blue led)?
- The sailfish installation uses oem for android 6, here 7 is used. Can this make the difference?
Thanks for any support.
Click to expand...
Click to collapse
boot into fastboot and flash the oem:
fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_5.7_r1_v08_loire.img
then boot into twrp recovery and wipe /system and /data
while in twrp, run the halium-install.sh script (because the computer needs to connect to phone in adb mode, which twrp provides)
following from there, as you see in the first post, you will run "adb reboot bootloader" (but I think I did have to do it manually) which should put you back into fastboot mode where you'll "fastboot flash boot halium-boot.img"
then you should be able to reboot into ubuntu. The first boot takes a little longer.
Are there any screenshots available?
Fajormein said:
Are there any screenshots available?
Click to expand...
Click to collapse
No but you can find some videos on YouTube, just search for "Ubuntu Touch 2019".
The videos might feature different phones but it's the same on the Xperia X.
Is there any way to install it using a windows pc?
Fardin Rehman said:
Is there any way to install it using a windows pc?
Click to expand...
Click to collapse
Not currently.
please make a porting for kugo (x compact) sir
rizky_zulfikar said:
please make a porting for kugo (x compact) sir
Click to expand...
Click to collapse
Someone else is working on that already, but this port is only for the Xperia X (F5121).
In other news:
Installation instructions have been updated, the Xperia X port is now available from the UBports community channel!
Can you make port for XA 2 (H3113)
As I get the question very often: To support the F5122 variant of the Xperia X (or other devices in general) for Ubuntu Touch I need donations to buy the device.
Use the "Donate To Me" button on XDA or head over to https://fredl.me/donate/ for info on how to do so.
In other news: The Xperia X F5121 has gained support for the official UBports installer. You can now flash the device using a fancy GUI.
I hit 2 problems. For some reason neither Emma nor flashtool wants to flash stock rom correctly. Tried to flash ubuntu through stock 8.0 custom rom, phone reboots and black screen. Also there is was an error with something that the file couldn't be sent to the phone
Click to expand...
Click to collapse
Ok, so I did install the stock rom through EMMA fine. I did enable the usb debugging, installed twrp, wiped system & data, made sure they are EXT4. Rebooted to fastboot, installed SW binaries. Opened UBports Installer & proceeded with instructions. I got this error
Code:
Error: systemimage: Error: Error: {"error":{"killed":false,"code":1,"signal":null,"cmd":"C:\\Users\\domin\\AppData\\Local\\Temp\\1Uo4H80AYPnCivmpnC8M9LLWxLb\\resources\\app.asar.unpacked\\platform-tools\\win\\adb -P 5037 shell mount -a"},"stdout":"","stderr":"mount: mounting /dev/block/bootdevice/by-name/userdata on /data failed: Invalid argument"}
Any solutions, did I miss something? I gonna retry without the twrp step, as I am pretty sure the partition format will be EXT4

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