Flipper Zero dead during firmware update

Sad short story.
I just got my Flipper Zero.
I connect it to my MacBook Pro to update the firmware.
I follow the procedure but the Recovery Boot Mode times out. (look at the logs)
“Flipper Zero” dead.
P.S. I have tried this procedure with no success.
Any advice?
Thank you.

1108 [APP] qFlipper version 1.1.0 commit 73c2ac6a 2022-06-03T19:50:17
1108 [APP] OS info: macOS 10.16 10.16 21.6.0
1122 [REG] Detected new device: VID_0x483:PID_0x5740
1552 [RPC] Starting RPC session…
1675 [RPC] RPC session started successfully.
1676 [RPC] (1) System Device Info START
1766 [RPC] (1) System Device Info SUCCESS
1767 [RPC] (2) Storage Info @/ext START
1820 [RPC] (2) Storage Info @/ext SUCCESS
1820 [RPC] (3) System Get DateTime START
1870 [DBG] Flipper time skew is -7093484 milliseconds
1874 [RPC] (3) System Get DateTime SUCCESS
1874 [RPC] (4) System Set DateTime START
1925 [RPC] (4) System Set DateTime SUCCESS
1925 [RPC] Stopping RPC session…
1930 [RPC] Attempting to unload protobuf plugin…
1930 [RPC] Unloaded protobuf plugin.
1930 [RPC] RPC session stopped successfully.
1930 [REG] Registering the device
1930 [DEV] Version: 0.43.1 commit: a4267626 radio: 1.12.1
1930 [BKD] Current device changed to “Ospiold”
2040 [RPC] Starting RPC session…
2160 [RPC] RPC session started successfully.
2161 [RPC] (1) Gui Start SreenStream START
2220 [RPC] (1) Gui Start SreenStream SUCCESS
4406 [UPD] Fetched update information from https://update.flipperzero.one/firmware/directory.json
4707 [UPD] Fetched update information from https://update.flipperzero.one/qFlipper/directory.json
49280 [RPC] (2) Gui Start VirtualDisplay START
49335 [RPC] (2) Gui Start VirtualDisplay SUCCESS
49455 [UPD] Fetched update information from https://update.flipperzero.one/firmware/directory.json
49576 [DEV] Legacy Update @Ospiold START
50021 [ZIP] Uncompressing file with size of 164992 bytes…
50022 [ZIP] Uncompression finished : No Error
50192 [ZIP] Uncompressing file with size of 34949 bytes…
50193 [ZIP] Uncompression finished : No Error
50372 [UTL] Start Recovery Mode @Ospiold START
50373 [RPC] (3) System Reboot START
50373 [RPC] (3) System Reboot SUCCESS
50572 [RPC] Serial connection was lost.
50572 [RPC] Stopping RPC session…
50572 [RPC] Attempting to unload protobuf plugin…
50572 [RPC] Unloaded protobuf plugin.
50573 [RPC] RPC session stopped successfully.
50606 [REG] Device went offline: VID_0x483:PID_0x5740
51507 [REG] Detected new device: VID_0x483:PID_0xdf11
51534 [DBG] Device reported transfer size: 1024
51534 [DBG] Bytes uploaded: 32 100%
51534 [DBG] Upload has finished.
51535 [REG] Device went back online
51651 [UTL] Start Recovery Mode @Ospiold SUCCESS
51663 [RCY] Set Recovery boot mode @Ospiold START
51664 [DBG] Device is not idle, resetting…
51691 [DBG] Device reported transfer size: 1024
51691 [DBG] Bytes uploaded: 128 100%
51691 [DBG] Upload has finished.
51691 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
51692 [DBG] Device is not idle, resetting…
51717 [DBG] Device reported transfer size: 1024
54125 [DBG] Failed to perform control transfer: LIBUSB_ERROR_NO_DEVICE
54125 [DBG] Unable to get device status
54125 [DBG] An error has occured during download phase
54125 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
54125 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
54125 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
54125 [REG] Device went offline: VID_0x483:PID_0xdf11
84206 [RCY] Set Recovery boot mode @Ospiold ERROR: Failed to set Recovery mode: operation timeout
84207 [DEV] Legacy Update @Ospiold ERROR: Failed to set Recovery mode: operation timeout
84207 [BKD] Current operation finished with error: “Failed to set Recovery mode: operation timeout”
99723 [BKD] Finalized current operation
99723 [REG] Removed offline device: Ospiold

UPDATE
After many attempts I managed to get into DFU mode.
Now I have this error

log.txt (21.6 KB)

Are you connecting directly to the flipper? Using any hubs or adapters may cause this error

Yes, I’m using an hub.
So now I need to find a USB-C to USB-C cable to test…
However I tried a dozen time to enter DFU mode with no luck.

Yes, you need a C-C cable. Usually the charging cable that comes with your MacBook works for that

You nailed it @Astra
Thank you!
:+1:

1 Like