0009780: [NetHunter Pro 2026.2/SDM845 / fajita] Wi-Fi non-functional- modem, ADSP, pd-mapper, and firmware-path issues in shipped image - Kali Linux Bug Tracker

ID	Project	Category	View Status	Date Submitted	Last Update

0009780	Kali Linux	Kali Package Bug	public	2026-07-10 21:11	2026-08-15 10:39

Reporter	pyankulov	Assigned To
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	new	Resolution	open

Summary	0009780: [NetHunter Pro 2026.2/SDM845 / fajita] Wi-Fi non-functional- modem, ADSP, pd-mapper, and firmware-path issues in shipped image
Description	Device: OnePlus 6T (fajita), SDM845 Image: kali-nethunterpro-2026.2-sdm845 (Phosh), kernel 6.12.92-sdm845-nh Prior OS: LineageOS 22.2 (OxygenOS 11 firmware base, MPSS.AT.4.0.c2.15) Summary: Out of the box, internal Wi-Fi (WCN3990 / ath10k_snoc) is non-functional — wlan0 never appears, Wi-Fi is greyed out in Phosh. Root cause is a chain of missing/misplaced firmware and broken PD-mapper descriptors in the shipped rootfs. Cellular/modem is also dead out of the box for the same underlying reason. Issues found (in dependency order): Firmware path mismatch. The DTB requests co-processor firmware from qcom/sdm845/oneplus6/ (e.g. mba.mbn, adsp.mbn, cdsp.mbn, venus.mbn, a630_zap.mbn), but the shipped rootfs places these files in qcom/sdm845/ (one level up). Result: Direct firmware load ... failed with error -2 for every remoteproc at boot. The oneplus6/ subdirectory does not exist in the image. Modem firmware not device-matched. Even after placing mba.mbn/modem.mbn at the correct path, the shipped generic modem firmware fails PBL authentication: qcom-q6v5-mss 4080000.remoteproc: PBL returned unexpected status -284557301 → Boot failed: -22. The modem only boots when using firmware extracted from the device's own modem partition (MPSS.AT.4.0.c2.15, OxygenOS 11). Suggests the shipped modem firmware is either absent, generic, or version-mismatched against the device's secure-boot trust root. Modem firmware ships split, loader wants merged. The device modem/ADSP firmware is .mdt + .bNN segments; the mainline loader expects a single squashed .mbn. Required manual pil-squasher merge. Worth documenting or handling in-image. ADSP does not auto-boot (remoteproc0 stays offline), so its servreg node is never published — which pd-mapper needs. Had to manually echo start > /sys/class/remoteproc/remoteproc0/state. pd-mapper: "no pd maps available". Two causes: (a) the .jsn PD descriptors in qcom/sdm845/ are symlinks to wrong SoCs (adspr.jsn → ../qcm2290/, cdspr.jsn → ../qcs615/, modemuw.jsn → ../qcm2290/); (b) pd-mapper searches /lib/firmware/updates/qcom/sdm845/oneplus6/ (confirmed via strace openat), where no .jsn files are shipped. Fixed by placing the device's own .jsn descriptors (from the modem partition) into that path. ath10k probe-order race. ath10k_snoc probes at ~13s (boot), but modem comes up ~19s and ADSP/pd-mapper later. ath10k stalls silently after Adding to iommu group 10 and never retries. Runtime modprobe -r/reload and driver unbind/bind do not re-trigger a working probe (no dmesg output on reload) — appears to only probe successfully at boot. No working ordering is shipped to guarantee modem+ADSP+pd-mapper are up before ath10k probes. 7.Bluetooth crnv21.bin path. Initramfs reports missing qca/oneplus6/crnv21.bin; the file exists elsewhere in the tree and must be copied to that path for BT to initialise cleanly. 8.Minor: venus.mbn (video codec) and slpi.mbn (sensor DSP) also fail -2 on the oneplus6/ path; USB Ethernet r8152 works despite an rtl8153a-4.fw load-fail warning. Net: with (1) correct firmware paths, (2) device-extracted + squashed modem/ADSP firmware, (3) correct .jsn descriptors in the updates/.../oneplus6/ path, cellular and the full servreg/pd-mapper chain come up — but ath10k still won't complete its probe at runtime due to the boot-ordering issue (6), which remains unresolved. Suggest the image ship: correct oneplus6/ firmware paths, a documented/automated way to source device modem firmware, correct per-SoC .jsn descriptors, ADSP auto-boot, and ath10k load ordering after pd-mapper.

Bend_ami 2026-07-19 23:34 reporter ~0021892 Last edited: 2026-07-20 11:02	I can confirm (I have an enchilada, and coming from a pure Oxygen OS android 11) that this bug is reproducible. I tried to fix the misplacement of the .mbn (wich is the main problem, that makes the wifi not functional) files but symbolic link haven't solved the problem. But ALL the usb problems are resolved, and the usb port is working fine not having any kind of problem with recognition, or alimentation. And is finally set on "host".

020197 2026-07-30 14:36 reporter ~0021908	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.

g0tmi1k 2026-07-31 18:57 administrator ~0021914	Can you try the weekly build, and see if that's an issue? https://artifacts.kali.org/images-nethunterpro/kali-weekly/ The Build-script recently got updated

020197 2026-07-31 22:26 reporter ~0021915	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.

Sh1n1gam1 2026-08-15 10:16 reporter ~0021931	Just like my pal 020197, I've purchased a Oneplus 6 (enchilada) specifically to run Kali Nethunter pro with the full access and was really disappointed to know about this bug just now. We appreciate the work of the developers, and we kindly ask for their attention to fix the issue if they have the time to spare. Thanks in advance.

Anymene 2026-08-15 10:39 reporter ~0021932	Guys, is this a universal issue? I don't find it having enough attention since the release of the 2026.2 image, not just from developers but also no from users. Should I try and install it myself to see if it works?

Date Modified	Username	Field	Change
2026-07-10 21:11	pyankulov	New Issue
2026-07-19 23:34	Bend_ami	Note Added: 0021892
2026-07-20 11:02	Bend_ami	Note Edited: 0021892
2026-07-30 14:36	020197	Note Added: 0021908
2026-07-31 18:57	g0tmi1k	Note Added: 0021914
2026-07-31 22:26	020197	Note Added: 0021915
2026-08-15 10:16	Sh1n1gam1	Note Added: 0021931
2026-08-15 10:39	Anymene	Note Added: 0021932