device cannot be correctly detected again after the firmware is flashed about sweyntooth_bluetooth_low_energy_attacks HOT 7 CLOSED

Hi, @f0rm2l1n it is not common that you cannot put the dongle on programming mode again, as the DFU is locked by Nordic and cannot be removed even if flashing SweynTooth firmware.
Can you confirm what happens when you press the small reset button while the dongle is plugged in?
Please find below such button which is supposed to put the dongle in programming mode again with a blinking red led:

from sweyntooth_bluetooth_low_energy_attacks.

@f0rm2l1n no worries, I've just updated the documentation so this is better clarified: https://github.com/Matheus-Garbelini/sweyntooth_bluetooth_low_energy_attacks#getting-started-installation

from sweyntooth_bluetooth_low_energy_attacks.

Hi @f0rm2l1n if you put the dongle in programming mode (reset the dongle while it is plugged to USB), do you get to see the red LED blinking? You can only flash a new firmware if the dongle is already on programming mode (DFU mode). Let me know if this helps.

from sweyntooth_bluetooth_low_energy_attacks.

@Matheus-Garbelini Thanks for your reply!
Oops, this may sound quite weird as the dongle of mine never blink red (only yellow for now)
Every time I plug it into my laptop the yellow LED starts blinking and no matter how I press the button, nothing changes.

some pictures are shown below

Should I buy other cables for flushing the firmware? Or maybe I just bought a bad one which is not support programming mode?
P.S. I try many different methods of pressing this damn button :(. No idea which one is correct...

from sweyntooth_bluetooth_low_energy_attacks.

@Matheus-Garbelini
I am such an idiot T.T I just keep pressing the SW button
Thanks for your answer, it really helps a green hand out~~

from sweyntooth_bluetooth_low_energy_attacks.

@Matheus-Garbelini
In addition, one more question, If I choose to flash the firmware though "connector", which options below I should choose

The command line just drives me crazy sometimes :)

from sweyntooth_bluetooth_low_energy_attacks.

for s140_nrf52_6.1.1_softdevice.hex you should write a custom SoftDevice ID: 0xB6

from sweyntooth_bluetooth_low_energy_attacks.