-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
request support for bcmdhd4389 #572
Comments
i second this, would be awesome to have support for those phones |
i can provide any logs or info that you need as well. heres a link to the firmware. every thing needed will be in the system/vendor folder of the magisk modules repo here https://github.com/Biohazardousrom/nh-magisk-wifi-firmware-gs101-gs201/tree/master/system/vendor and here is a link to the xda page explaining wifi sniffer and how to use it https://forum.xda-developers.com/t/get-bcm4389-into-monitor-mode-for-wifi-sniffing.4525011/ |
I already started adding |
thank you for getting back to me. just to let you know that the fw_bcmdhd_monitor.bin firmware already has monitor mode built in and through radiotap0, but the caveat is that as of right now we have to use the wifi_sniffer binary to bring up radiotap0. also i pulled the firmware from a precompiled vendor image used to build android 14 beta. from what ive found it should work with any device that uses the 4389 bcm chipset note that bcm4389 uses radiotap0 instead of wlan0 |
thanks, I am aware of the monitor and manufacturer builds that come in addition to the default firmware |
Any updates on this? |
Not in a position to drop a request, but would really love to see nexmon coming to bcmdhd4389 :) |
Hi there
i would request support for the bcmdhd4389 broadcom chip and firmware. Atm we have firmware with wifi monitor mode but would like to use nexmon on the tensor boards including pixel 6/pro, pixel 6a and pixel 7/pro. Also as it stands the app fc's after trying to grant root permission on pixel 6 and pixel
thank you
The text was updated successfully, but these errors were encountered: