View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009798 | Kali Linux | Kali Package Bug | public | 2026-07-25 22:13 | 2026-07-31 22:36 |
| Reporter | Bend_ami | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0009798: [Oneplus 6 - enchilada / SDM845] Nethunter pro: image shipped with firmware bugs | ||||
| Description | I'm coming from standard Oxygen OS 11. Adjusting the firmware position on the main file system doesn't resolve BUT... SUGGESTED SOLUTION: | ||||
|
Check this anomaly if you want to know more about fajita problems |
|
|
Hi, I have a similar issue on my OnePlus 6T (codename fajita). I’ve tried different ROMs. First I installed Kali Nethunter on top of Android, but Kali refused to start on the latest LineageOS 22.2 with Android 15, so I had to roll back to an archived build lineage-22.2-20260505 (LineageOS doesn’t keep older builds, I had to download it from SourceForge). Only that version worked. However, I didn’t like Kali Nethunter over Android because systemd wasn’t functional, preventing me from using it as a full Linux system. So I decided to try Kali Nethunter Pro — a full Linux system with systemd. Installation went fine, but right after boot I encountered the exact same issues described by the reporter “Bend_ami”. I tried all the same fixes he mentioned, but unfortunately none helped. I’m disappointed that the OnePlus 6T is on the supported devices list for Kali Nethunter Pro yet I can’t use the device properly due to non-working internal Wi-Fi. USB Wi-Fi adapters work, but it’s not always convenient. Unable to find a fix, I tried other ROMs. First Droidian and Ubuntu Touch, but they never boot after installation — the phone gets stuck at the bootloader unlocked warning screen and won’t go further no matter how many reboots or slot switches I try. To my surprise, the official Mobian image installed without issues, and after boot camera, Bluetooth, and internal Wi-Fi all worked. This raises a question: if Kali Nethunter is based on Mobian, why is this problem solved in Mobian but still present in Kali Nethunter Pro? I then tried installing Kali tools on Mobian, but there I discovered that the internal Wi-Fi, although working, cannot be switched to monitor mode. Even after sudo airmon-ng check kill, it refuses to enter monitor mode and shows a warning that some software is blocking the adapter. Currently my device is still running Kali Nethunter Pro. I’m following the bug tracker hoping the developers will release a fix. As a hint, Mobian doesn’t have the firmware/ADSP issue, but it does have the monitor mode problem. Also, for reference, on the regular Kali Nethunter over Android, the internal Wi-Fi worked perfectly, wifite and airmon-ng functioned fine, and the adapter could enter and exit monitor mode without issues. Thanks for your attention, I really hope the developers resolve this because I lack the expertise to fix it myself. I’ve tried all the same methods as Bend_ami. |
|
|
I took a risk and tested Wi-Fi functionality in the weekly build kali-nethunterpro-2026.W30-rolling-sdm845.tar.xz as suggested by g0tmi1k, even though I had previously been running the stable version kali-nethunterpro-2026.2-sdm845.tar.xz. To my disappointment, the issue remains unresolved in the weekly build. I installed the weekly image, performed all the same procedures as before, updated packages via an external USB Wi-Fi adapter, rebooted the system, and even tried running droid-juicer — all to no avail. The problem persists. It's unfortunate that I had to wipe my stable installation just to test this, and I feel like I wasted my time. I sincerely ask that this issue be given proper attention. I purchased the OnePlus 6T specifically to run Kali NetHunter on it. This device was recommended by many as one of the best alternatives to the PinePhone for Kali purposes — even an AI chat assistant suggested it. However, I am currently unable to fully use Kali on this device, and I'm sharing my experience here in the hope that developers will prioritize a fix and include it in a future stable release. |
|