Example project for extracting channel state information of up to 80 MHz wide 802.11ac Wi-Fi transmissions using the BCM4339 Wi-Fi chip of Nexus 5 smartphones.
Other
98
stars
39
forks
source link
Error "__nex_driver_io" on Nexus 5 when activate monitor with root #12
I am trying to implement CSI extractor on Nexus 5 with firmware version 6.0.1(M4B30Z, Dec 2016).
After smooth compiling and installing, when I was using nexutil to activate monitor mode, wired things happened:
1) When I ran "nexutil -m1" at the first time, no error shows up, normal Wi-Fi connection got disabled, which should be correct since wlan0 is set to be monitor mode.
2) However, after this first try, nexutil always came with the problem:
root@hammerhead:/ # nexutil -m0__nex_driver_io: errorroot@hammerhead:/ # nexutil -m1__nex_driver_io: errorroot@hammerhead:/ # nexutil -m__nex_driver_io: errormonitor: 0
I am sure about commanding with root, I can found the existence of "libfakeioctl.so" under "/system/lib/" and "nexutil" under "/system/bin/", and I think the firmware is running because the first time "nexutil -m0" succeed. Is there any other possible cause?
FYI, even though the installation of utilities with running "make install" under "/nexmon/utilities/" is smooth, I noticed some unnormal stuff:
make[1]: Entering directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio_make[1]: *** No rule to make target 'install'. Stop._make[1]: Leaving directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio
The "No rule to make target install" and "No such file or directory" problem also happen to some other utilities, such as "libnexio" and "wireshark".
Do you think the unnormal stuff has something to do with the "__nex_driver_io" error?
Hi everyone,
I am trying to implement CSI extractor on Nexus 5 with firmware version 6.0.1(M4B30Z, Dec 2016).
After smooth compiling and installing, when I was using nexutil to activate monitor mode, wired things happened: 1) When I ran "nexutil -m1" at the first time, no error shows up, normal Wi-Fi connection got disabled, which should be correct since wlan0 is set to be monitor mode. 2) However, after this first try, nexutil always came with the problem:
root@hammerhead:/ # nexutil -m0__nex_driver_io: errorroot@hammerhead:/ # nexutil -m1__nex_driver_io: errorroot@hammerhead:/ # nexutil -m__nex_driver_io: errormonitor: 0I am sure about commanding with root, I can found the existence of "libfakeioctl.so" under "/system/lib/" and "nexutil" under "/system/bin/", and I think the firmware is running because the first time "nexutil -m0" succeed. Is there any other possible cause?FYI, even though the installation of utilities with running "make install" under "/nexmon/utilities/" is smooth, I noticed some unnormal stuff:
make[1]: Entering directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio_make[1]: *** No rule to make target 'install'. Stop._make[1]: Leaving directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexioand
make[1]: Entering directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libfakeioctlcd ../libnexio && makemake[2]: Entering directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio~/BCM-CSI-TOOL/android-ndk-r11c/ndk-build NDK_APPLICATION_MK=pwd/Application.mkNDK_APP_OUT=. TARGET_PLATFORM=android-21make[3]: Entering directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio'make[3]: Leaving directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio'make[2]: Leaving directory '/home/ptoh/BCM-CSI-TOOL/nexmon/utilities/libnexio'adb shell 'su -c "mount -o rw,remount /system"'adb push libs/armeabi/libfakeioctl.so /sdcard/284 KB/s (13640 bytes in 0.046s)adb shell 'su -c "cp /sdcard/libfakeioctl.so /system/lib/libfakeioctl.so"'adb push libs/arm64-v8a/libfakeioctl.so /sdcard/209 KB/s (9760 bytes in 0.045s)adb shell 'su -c "cp /sdcard/libfakeioctl.so /system/lib64/libfakeioctl.so"'_cp: /system/lib64/libfakeioctl.so: No such file or directory_make[1]: Leaving directory '/home/yanbo/BCM-CSI-TOOL/nexmon/utilities/libfakeioctl'The "No rule to make target install" and "No such file or directory" problem also happen to some other utilities, such as "libnexio" and "wireshark". Do you think the unnormal stuff has something to do with the "__nex_driver_io" error?
Thanks a lot for any suggestions.