seemoo-lab / nexmon

The C-based Firmware Patching Framework for Broadcom/Cypress WiFi Chips that enables Monitor Mode, Frame Injection and much more
GNU General Public License v3.0
2.45k stars 455 forks source link

Can't restore firmware 6p #240

Open S1CAR1US opened 6 years ago

S1CAR1US commented 6 years ago

The documentation on using the app is scarce. I read that using the app is the easy way to get monitor mode working with a 6p. I install the app, follow the prompts to install the tools. Then firmware, make a backup, install nexmon firmware, WiFi stops working and can no longer turn it on at all. Go to firmware section in the nexmon app to restore firmware using the backup I made, and now it tells me that the device I have is not supported... I have a 6p and just a minute ago it was supported. I have had to re flash Nexus image and nethunter twice now because of this. How do I fix without starting over every time?

matthiasseemoo commented 6 years ago

Manually make a backup of the firmware file and restore it when something fails. The app can now be considered depricated as we did not update it for quite a while. If you have a firmware version in your android rom that is supported by nexmon, compile your own firmware from the repository and install it.

On Fri, Jul 20, 2018 at 7:32 PM, S1CAR1US notifications@github.com wrote:

The documentation on using the app is scarce. I read that using the app is the easy way to get monitor mode working with a 6p. I install the app, follow the prompts to install the tools. Then firmware, make a backup, install nexmon firmware, WiFi stops working and can no longer turn it on at all. Go to firmware section in the nexmon app to restore firmware using the backup I made, and now it tells me that the device I have is not supported... I have a 6p and just a minute ago it was supported. I have had to re flash Nexus image and nethunter twice now because of this. How do I fix without starting over every time?

— 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/nexmon/issues/240, or mute the thread https://github.com/notifications/unsubscribe-auth/ALP_7m1iJ6AkGSuqnmPhYjFKp0PDmhVmks5uIhQ4gaJpZM4VYku8 .

-- Matthias Schulz Secure Mobile Networking Lab - SEEMOO

Email: matthias.schulz@seemoo.tu-darmstadt.de Web: http://www.seemoo.de/mschulz Phone (new): +49 6151 16-25478 Fax: +49 6151 16-25471

Department of Computer Science Center for Advanced Security Research Darmstadt Technische Universität Darmstadt Mornewegstr. 32 (Office 4.2.10, Building S4/14) D-64293 Darmstadt, Germany

S1CAR1US commented 6 years ago

That's a pretty cheap cop-out, the info on your own page refers the app. Now your telling me as if I should have known. At least offer some direction as to how to go about restoring the correct fw

matthiasseemoo commented 6 years ago

This should be the location of the firmware file: /vendor/firmware/fw_bcmdhd.bin Where exactly do we refer to the app on the webpage?

In any case, you use nexmon on your own risk: Our software may damage your hardware and may void your hardware’s warranty! You use our tools at your own risk and responsibility! If you don't like these terms, don't use nexmon!

On Fri, Jul 20, 2018 at 8:23 PM, S1CAR1US notifications@github.com wrote:

That's a pretty cheap cop-out, the info on your own page refers the app. Now your telling me as if I should have known. At least offer some direction as to how to go about restoring the correct fw

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/seemoo-lab/nexmon/issues/240#issuecomment-406686958, or mute the thread https://github.com/notifications/unsubscribe-auth/ALP_7jcJefnAtkLq1L0blevGerc6JMrPks5uIiANgaJpZM4VYku8 .

-- Matthias Schulz Secure Mobile Networking Lab - SEEMOO

Email: matthias.schulz@seemoo.tu-darmstadt.de Web: http://www.seemoo.de/mschulz Phone (new): +49 6151 16-25478 Fax: +49 6151 16-25471

Department of Computer Science Center for Advanced Security Research Darmstadt Technische Universität Darmstadt Mornewegstr. 32 (Office 4.2.10, Building S4/14) D-64293 Darmstadt, Germany