matthiasseemoo
commented
5 years ago In few cases, the Wi-Fi chips stops its operation even after reinstalling the backup, but it was always possible to make it work again after a complete system reinstall.
You can simply add new ioctls by modidying the ioctl.c file.
Am Fr., 28. Dez. 2018, 16:31 hat dakami notifications@github.com geschrieben:
Everything appears to build fine on Bionic but the resulting firmware doesn't appear to work. I managed to build under a Docker Xenial environment, after hitting a fair number of missing dependencies (build-essential, file, vim, bison, flex, maybe one or two others). It's a bear getting adb working from inside a container, but ultimately copying fw*bin to /vendor/firmware via the host worked.
The failed image does something wonky too. wlan0 stays down even after backup restoration and power cycle. Need to return to a full backup.
Could use slightly less opaque ioctl syntax :)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/seemoo-lab/mobisys2018_nexmon_channel_state_information_extractor/issues/17, or mute the thread https://github.com/notifications/unsubscribe-auth/ALP_7gKjQ1Tz4Kg7rzPvK8V8FPT25Cp_ks5u9jlqgaJpZM4Zj9pk .
dakami
Everything appears to build fine on Bionic but the resulting firmware doesn't appear to work. I managed to build under a Docker Xenial environment, after hitting a fair number of missing dependencies (build-essential, file, vim, bison, flex, maybe one or two others). It's a bear getting adb working from inside a container, but ultimately copying fw*bin to /vendor/firmware via the host worked.
The failed image does something wonky too. wlan0 stays down even after backup restoration and power cycle. Need to return to a full backup.
Could use slightly less opaque ioctl syntax :)