mirror of
https://github.com/safijari/openpuck.git
synced 2026-11-04 06:34:45 +00:00
[GH-ISSUE #282] Web UI updater soft bricks MDBT50Q-CX dongles, possibly requiring a SWD to recover #127
Labels
No labels
pull-request
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
safijari/openpuck#127
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ase1590 on GitHub (Sep 9, 2026).
Original GitHub issue: https://github.com/safijari/openpuck/issues/282
With the new support for the MDBT50Q-CX in https://github.com/safijari/openpuck/pull/137 this now puts users of this device at risk of soft-bricking the device for use with OpenPuck. As this device requires hex files to be flashed manually and does not support U2F files, loading the U2F files from the web updater causes a soft brick, in which the device when re-flashed with the openpuck firmware no longer appears for the Web UI to find and may not be even loading openpuck properly.
Two users, myself included and one user on the bottom of the comments on pull 137, have made this mistake with the Web UI updater.
There are also multiple reddit accounts of this happening as well:
https://www.reddit.com/r/SteamController/comments/1uyfn04/openpuck_alternative_device_raytac_installation/p6mddye/
My advice:
My suspicion is that the bootloader or some other part of the device is modified in such a way that it no longer can run Openpuck.
I suspect this is correctable via purchasing a segger J-link to wipe and re-flash the device, but I am not familiar enough with NRF development to be able to know if this would fix it or not.
For clarification: the devices can still be opened in in NRF Connect in DFU mode, but OpenPuck ceases to work on them after making the web updater mistake.
@ase1590 commented on GitHub (Sep 9, 2026):
attempting to run the openpuck factory reset firmware does not seem to fix this issue either.
@ase1590 commented on GitHub (Sep 13, 2026):
I stood up a VM and attempted the new build and deploy instructions that were added for Raytac devices, and that seems to unbreak the device for OpenPuck
https://github.com/safijari/openpuck/blob/main/docs/BUILD_AND_DEPLOY.md#4a-raytac-mdbt50q-cx-40
Steps 1-3 need to be followed, then 4a for the raytac specific item.
I think in order to close this issue: we need to alert raytac users to NOT use the web UI for updating, and hand them off to those instructions if they do accidentally update via web ui.
@spider-enigma commented on GitHub (Sep 18, 2026):
Can I get exact instructions to unbrick it? I accidentally used the web-ui to update it and i cant flash it from nrf connect and get it to boot, it flashes but it wont boot normally
Im at the 4a part of it and getting No rule to make target 'provision-raytac-softdevice'. Stop. and most of the stuff is making input all of my derectories and names manully in the guide and I'm failing badly