Older OS X

Firmware update / qFlipper
#1

I just got my FlipperZero today and went to update the device to latest.

I’m running: OS Version: Mac OS X 10.13.6 (17G14042)
Which turns out to be a little bit of a problem, as once it finishes writing the co-processor blocks, qFlipper crashes:
Termination Reason: DYLD, [0x4] Symbol missing

Dyld Error Message:
Symbol not found: ____chkstk_darwin
Referenced from: /Applications/qFlipper.app/Contents/MacOS/…/Frameworks/libusb-1.0.0.dylib (which was built for Mac OS X 11.0)
Expected in: /usr/lib/libSystem.B.dylib

This left a somewhat bricked FlipperZero, I could restart qFlipper, but it failed again at the same location.

I built a new libusb (from NetBSD pkgsrc) and had qFlipper use that instead:
$ cd /Applications/qFlipper.app/Contents/Frameworks/
$ mv libusb-1.0.0.dylib libusb-1.0.0.dylib-
$ ln -s /usr/pkg/lib/libusb-1.0.0.dylib libusb-1.0.0.dylib

This executed the update, but left me with the following:

  • the display on the FlipperZero was complaining about a missing database.
  • qFlipper complained about an interrupted operation with the connection to the device lost.
    Log:
    [APP] qFlipper version 1.0.1 commit beb47b7f 2022-04-06T06:16:06
    [APP] OS info: macOS High Sierra (10.13) 10.13 17.7.0
    [DEV] Full Repair @Ong0rg START
    [RCY] Set Recovery boot mode @Ong0rg START
    [RCY] Set Recovery boot mode @Ong0rg SUCCESS
    [RCY] Co-Processor Firmware Download @Ong0rg START
    [RCY] Co-Processor Firmware Download @Ong0rg SUCCESS
    [RCY] Firmware Download @Ong0rg START
    [RCY] Firmware Download @Ong0rg SUCCESS
    [RCY] Correct Option Bytes @Ong0rg START
    [RPC] Starting RPC session…
    [RCY] Correct Option Bytes @Ong0rg ERROR: Failed to write corrected option bytes: Operation timeout
    [DEV] Full Repair @Ong0rg ERROR: Failed to write corrected option bytes: Operation timeout
    [RPC] Failed to start RPC session: Failed to begin CLI session: Device is not responding

At this point the FlipperZero is unbricked. But was complaining about “No SD card or database found. Some app function may be reduced.” when pressing Left. (It’s there, and I was able to reformat it.)

Did qFlipper finish “enough”, or am I going to have to keep poking at things to get this fully working?

(The other systems of mine are only a Windows 7 box, running Steam mostly, and a bunch of NetBSD 9.x systems.)

#2

@gsurkov

#3

I also had a problem with the desktop software crashing during a firmware update.

Flipper’s Full log & Apple’s Crash Log attached.

I hope these help diagnose the issue at all.

Flipper’s Full log:

Blockquote
1495 [APP] qFlipper version 1.0.2 commit 9284d92a 2022-04-27T11:52:33
1495 [APP] OS info: macOS High Sierra (10.13) 10.13 17.7.0
1580 [REG] Detected new device: VID_0x483:PID_0xdf11
2064 [DBG] Device reported transfer size: 1024
2064 [DBG] Bytes uploaded: 32 100%
2064 [DBG] Upload has finished.
2066 [REG] Registering the device
2066 [BKD] Current device changed to “Hiscline”
2075 [UPD] Fetched update information from ///Doesn’t allow URLS///
20174 [DEV] Full Repair [name of device not allowed] START
20676 [ZIP] Uncompressing file with size of 165029 bytes…
20678 [ZIP] Uncompression finished : No Error
20873 [ZIP] Uncompressing file with size of 31196 bytes…
20875 [ZIP] Uncompression finished : No Error
21126 [RCY] Set Recovery boot mode [name of device] START
21129 [DBG] Device is not idle, resetting…
21157 [DBG] Device reported transfer size: 1024
21158 [DBG] Bytes uploaded: 128 100%
21158 [DBG] Upload has finished.
21159 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
21160 [DBG] Device is not idle, resetting…
21187 [DBG] Device reported transfer size: 1024
22482 [DBG] Failed to perform control transfer: LIBUSB_ERROR_NO_DEVICE
22483 [DBG] Unable to get device status
22483 [DBG] An error has occured during download phase
22483 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
22483 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
22483 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
22485 [REG] Device went offline: VID_0x483:PID_0xdf11
22491 [REG] Detected new device: VID_0x483:PID_0xdf11
22521 [DBG] Device reported transfer size: 1024
22522 [DBG] Bytes uploaded: 32 100%
22522 [DBG] Upload has finished.
22523 [REG] Device went back online
22714 [RCY] Set Recovery boot mode [name not allowed] SUCCESS
22714 [RCY] Co-Processor Firmware Download [name not allowed] START
22716 [DBG] Device is not idle, resetting…
22745 [DBG] Device reported transfer size: 1024
22745 [DBG] Bytes uploaded: 2 100%
22745 [DBG] Upload has finished.
22746 [DBG] FUS appears NOT to be running: Error occured, Not running.
22746 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
22747 [DBG] Device is not idle, resetting…
22776 [DBG] Device reported transfer size: 1024
24072 [DBG] Failed to perform control transfer: LIBUSB_ERROR_NO_DEVICE
24072 [DBG] Bytes uploaded: 0 0%
24073 [DBG] End of transmission.
24073 [DBG] Upload has finished.
24073 [DBG] Failed to read FUS status
24073 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
24073 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
24073 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
24074 [REG] Device went offline: VID_0x483:PID_0xdf11
24080 [REG] Detected new device: VID_0x483:PID_0xdf11
24110 [DBG] Device reported transfer size: 1024
24111 [DBG] Bytes uploaded: 32 100%
24111 [DBG] Upload has finished.
24112 [REG] Device went back online
24296 [DBG] Device is not idle, resetting…
25067 [REG] Device went offline: VID_0x483:PID_0xdf11
25258 [REG] Detected new device: VID_0x483:PID_0xdf11
25287 [DBG] Device reported transfer size: 1024
25288 [DBG] Bytes uploaded: 32 100%
25288 [DBG] Upload has finished.
25288 [REG] Device went back online
25478 [DBG] Getting Co-Processor (Wireless) status…
25480 [DBG] Device is not idle, resetting…
25508 [DBG] Device reported transfer size: 1024
25509 [DBG] Bytes uploaded: 2 100%
25509 [DBG] Upload has finished.
25510 [DBG] Current FUS state: Idle, No error.
25510 [DBG] Attempting to flash CO-PROCESSOR firmware image…
25513 [DBG] Device is not idle, resetting…
25545 [DBG] Device reported transfer size: 1024
25546 [DBG] Bytes uploaded: 128 100%
25546 [DBG] Upload has finished.
25546 [DBG] SFSA value is 0xf4
25547 [DBG] Target address for co-processor firmware image is 0x80d7000
25547 [DBG] Device is not idle, resetting…
25597 [DBG] Erasing memory: 0%
25646 [DBG] Erasing memory: 3%
25695 [DBG] Erasing memory: 7%
25745 [DBG] Erasing memory: 10%
…continues…
26811 [DBG] Erasing memory: 85%
26861 [DBG] Erasing memory: 88%
26914 [DBG] Erasing memory: 92%
26967 [DBG] Erasing memory: 96%
27017 [DBG] Erasing memory: 99%
27018 [DBG] Erase done.
27019 [DBG] Device is not idle, resetting…
27048 [DBG] Device reported transfer size: 1024
27093 [DBG] Bytes downloaded: 1024 0%
27133 [DBG] Bytes downloaded: 2048 1%
27176 [DBG] Bytes downloaded: 3072 2%
27217 [DBG] Bytes downloaded: 4096 3%
27256 [DBG] Bytes downloaded: 5120 4%
27301 [DBG] Bytes downloaded: 6144 5%
…continues…
31585 [DBG] Bytes downloaded: 110592 96%
31668 [DBG] Bytes downloaded: 112640 97%
31709 [DBG] Bytes downloaded: 113664 98%
31752 [DBG] Bytes downloaded: 114688 99%
31785 [DBG] Bytes downloaded: 115084 100%
31785 [DBG] Download has finished.
31786 [DBG] Sending FW_UPGRADE command…
31789 [DBG] Device is not idle, resetting…
32858 [REG] Device went offline: VID_0x483:PID_0xdf11
32941 [DBG] Getting Co-Processor (Wireless) status…
32942 [DBG] Failed to get FUS status. The device is offline at the moment.
33062 [REG] Detected new device: VID_0x483:PID_0xdf11
33093 [DBG] Device reported transfer size: 1024
33094 [DBG] Bytes uploaded: 32 100%
33094 [DBG] Upload has finished.
33095 [REG] Device went back online
33289 [DBG] Getting Co-Processor (Wireless) status…
33310 [DBG] Device is not idle, resetting…
33339 [DBG] Device reported transfer size: 1024
33467 [DBG] Bytes uploaded: 2 100%
33467 [DBG] Upload has finished.
33468 [DBG] Current FUS state: Firmware upgrade ongoing, No error.
33958 [DBG] Getting Co-Processor (Wireless) status…
33983 [DBG] Device is not idle, resetting…
34015 [DBG] Device reported transfer size: 1024
34081 [DBG] Bytes uploaded: 2 100%
34081 [DBG] Upload has finished.
34082 [DBG] Current FUS state: Firmware upgrade ongoing, No error.
34958 [DBG] Getting Co-Processor (Wireless) status…
34974 [DBG] Device is not idle, resetting…
35058 [DBG] Device reported transfer size: 1024
35156 [DBG] Bytes uploaded: 2 100%
35156 [DBG] Upload has finished.
35157 [DBG] Current FUS state: Firmware upgrade ongoing, No error.
35957 [DBG] Getting Co-Processor (Wireless) status…
35979 [DBG] Device is not idle, resetting…
36010 [DBG] Device reported transfer size: 1024
36077 [DBG] Bytes uploaded: 2 100%
36077 [DBG] Upload has finished.
36078 [DBG] Current FUS state: Firmware upgrade ongoing, No error.
36957 [DBG] Getting Co-Processor (Wireless) status…
36970 [DBG] Device is not idle, resetting…
37022 [DBG] Device reported transfer size: 1024
37152 [DBG] Bytes uploaded: 2 100%
37152 [DBG] Upload has finished.
37153 [DBG] Current FUS state: Firmware upgrade ongoing, No error.
37957 [DBG] Getting Co-Processor (Wireless) status…
37961 [DBG] Device is not idle, resetting…
38013 [DBG] Device reported transfer size: 1024
38016 [DBG] Bytes uploaded: 2 100%
38016 [DBG] Upload has finished.
38017 [DBG] Current FUS state: Firmware upgrade ongoing, No error.
38157 [REG] Device went offline: VID_0x483:PID_0xdf11
38359 [REG] Detected new device: VID_0x483:PID_0xdf11
38388 [DBG] Device reported transfer size: 1024
38389 [DBG] Bytes uploaded: 32 100%
38389 [DBG] Upload has finished.
38390 [REG] Device went back online
38619 [DBG] Getting Co-Processor (Wireless) status…
38621 [DBG] Device is not idle, resetting…
38648 [DBG] Device reported transfer size: 1024
38649 [DBG] Bytes uploaded: 2 100%
38649 [DBG] Upload has finished.
38649 [DBG] Current FUS state: Error occured, Not running.
38651 [DBG] Device is not idle, resetting…
38679 [DBG] Device reported transfer size: 1024
38679 [DBG] Bytes uploaded: 4 100%
38679 [DBG] Upload has finished.
38679 [DBG] Reading 56 bytes from address 0x20030024
38680 [DBG] Device is not idle, resetting…
38708 [DBG] Device reported transfer size: 1024
38708 [DBG] Bytes uploaded: 56 100%
38708 [DBG] Upload has finished.
38709 [DBG] FUS version: 1.2.0
38709 [DBG] Wireless Stack version: 1.13.3
38709 [RCY] Co-Processor Firmware Download [name not allowed] SUCCESS
38709 [RCY] Firmware Download [name]START
40743 [DBG] Device is not idle, resetting…
40794 [DBG] Erasing memory: 0%
40894 [DBG] Erasing memory: 1%
40992 [DBG] Erasing memory: 2%
41042 [DBG] Erasing memory: 3%
41142 [DBG] Erasing memory: 4%
41244 [DBG] Erasing memory: 5%
…continues…
48830 [DBG] Erasing memory: 96%
48930 [DBG] Erasing memory: 97%
48978 [DBG] Erasing memory: 98%
49079 [DBG] Erasing memory: 99%
49131 [DBG] Erase done.
49132 [DBG] Device is not idle, resetting…
49161 [DBG] Device reported transfer size: 1024
49202 [DBG] Bytes downloaded: 1024 0%
49455 [DBG] Bytes downloaded: 7168 1%
49747 [DBG] Bytes downloaded: 14336 2%
49989 [DBG] Bytes downloaded: 20480 3%
50282 [DBG] Bytes downloaded: 27648 4%
…continues…
76565 [DBG] Bytes downloaded: 674816 99%
76811 [DBG] Bytes downloaded: 680704 100%
76811 [DBG] Download has finished.
76812 [RCY] Firmware Download [device not allowed by forum] SUCCESS
76812 [RCY] Correct Option Bytes [device not allowed by forum] START
76817 [DBG] Device is not idle, resetting…
76846 [DBG] Device reported transfer size: 1024
76847 [DBG] Bytes uploaded: 128 100%
76847 [DBG] Upload has finished.
76847 [DBG] Option Bytes mismatch @nBOOT0: this: 0x0, other: 0x1
76847 [DBG] Option Bytes mismatch @nSWBOOT0: this: 0x0, other: 0x1
76847 [DBG] Writing corrected Option Bytes…
76847 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
76849 [DBG] Device is not idle, resetting…
76875 [DBG] Device reported transfer size: 1024
78169 [DBG] Failed to perform control transfer: LIBUSB_ERROR_NO_DEVICE
78169 [DBG] Unable to get device status
78169 [DBG] An error has occured during download phase
78169 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
78169 [DBG] vvv ATTENTION: Ignore errors below until matching closing message. vvv
78169 [DBG] ^^^ ATTENTION: Ignore errors above until matching opening message. ^^^
78170 [REG] Device went offline: VID_0x483:PID_0xdf11
78175 [REG] Detected new device: VID_0x483:PID_0x5740
80126 [REG] Device initialization failed: Failed to find a suitable serial port
108460 [RCY] Correct Option Bytes [device not allowed by forum] ERROR: Failed to write corrected option bytes: Operation timeout
108460 [DEV] Full Repair [device not allowed by forum] ERROR: Failed to write corrected option bytes: Operation timeout
108461 [BKD] Current operation finished with error: “Failed to write corrected option bytes: Operation timeout”
605447 [UPD] Fetched update information from ///Doesn’t allow hyperlinks///
Blockquote

Apple Crash Report:

Blockquote
Process: qFlipper [14752]
Path: /Applications/qFlipper.app/Contents/MacOS/qFlipper
Identifier: test.qFlipper
Version: 0
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: qFlipper [14752]
User ID: 502
Date/Time: 2022-05-15 21:02:54.706 -0400
OS Version: Mac OS X 10.13.6 (17G14042)
Report Version: 12
Time Awake Since Boot: 80000 seconds
Time Since Wake: 550 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: [forum thinks this is a link?]
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x4] Symbol missing
Dyld Error Message:
Symbol not found: ____chkstk_darwin
Referenced from: /Applications/qFlipper.app/Contents/MacOS/…/Frameworks/libusb-1.0.0.dylib (which was built for Mac OS X 11.0)
Expected in: /usr/lib/libSystem.B.dylib
Thread 0 Crashed:: Dispatch queue: [forum thinks this is a link?]
0 dyld 0x0000000112a41256 __abort_with_payload + 10
1 dyld 0x0000000112a40bc8 abort_with_payload_wrapper_internal + 89
2 dyld 0x0000000112a40bf5 abort_with_payload + 9
3 dyld 0x0000000112a14482 dyld::halt(char const*) + 354
4 dyld 0x0000000112a145a9 dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 170
5 libdyld.dylib 0x00007fff5de15292 dyld_stub_binder + 282
6 ??? 0x000000010b8d1258 0 + 4488761944
7 libusb-1.0.0.dylib 0x000000010b8c4205 0x10b8b9000 + 45573
[forum thinks all of these are links?]
CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000002000209 rbx: 0x0000000000000004 rcx: 0x00007ffee44d27f8 rdx: 0x00007ffee44d2c70
rdi: 0x0000000000000006 rsi: 0x0000000000000004 rbp: 0x00007ffee44d2850 rsp: 0x00007ffee44d27f8
r8: 0x00007ffee44d2870 r9: 0x0000000000000000 r10: 0x000000000000008c r11: 0x0000000000000246
r12: 0x000000000000008c r13: 0x00007ffee44d2c70 r14: 0x0000000000000006 r15: 0x0000000000000000
rip: 0x0000000112a41256 rfl: 0x0000000000000246 cr2: 0x0000000112a91fe0
Logical CPU: 0
Error Code: 0x02000209
Trap Number: 133
Binary Images:
0x10b72a000 - 0x10b84afff +test.qFlipper (0) <1CE19C47-FA32-3D5E-B5C1-2527F5308E8D> /Applications/qFlipper.app/Contents/MacOS/qFlipper
[ …Very Long dump that is over character limit… ]
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 128K 2
Activity Tracing 256K 2
CG backing stores 2712K 4
CoreGraphics 8K 2
CoreImage 8K 3
CoreUI image file 280K 4
IOKit 7940K 2
JS JIT generated code 268K 25
JS VM register file 6400K 6
Kernel Alloc Once 8K 2
MALLOC 165.0M 90
MALLOC guard page 48K 12
Memory Tag 242 12K 2
OpenGL GLSL 256K 4
STACK GUARD 56.1M 15
Stack 22.1M 15
VM_ALLOCATE 14.9M 51
WebAssembly memory 4096K 2
__DATA 26.5M 308
__DATA_CONST 16K 2
__FONT_DATA 4K 2
__GLSLBUILTINS 2588K 2
__LINKEDIT 202.8M 90
__TEXT 208.5M 307
__UNICODE 560K 2
mapped file 300.7M 203
shared memory 704K 16
=========== ======= =======
TOTAL 1.0G 1148
Model: MacBookAir4,1, BootROM 135.0.0.0.0, 2 processors, Intel Core i5, 1.6 GHz, 4 GB, SMC 1.74f4
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353737334448302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE9), Broadcom BCM43xx 1.0 (5.106.98.102.30)
Bluetooth: Version 6.0.7f22, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM128C, 121.33 GB
USB Device: USB 2.0 Bus
USB Device: FaceTime Camera (Built-in)
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: DFU in FS Mode
Thunderbolt Bus: MacBook Air, Apple Inc., 8.1

#4

Hi @graeioume,
If you look through that crash dump, it’s the issue I first tackled with the bad compilation of libusb. Hopefully we’ll hear some response about how an OS X 11 version of a library got bundled in with a OS X 10 distribution.
There does seem to be additional issues past that, causing issues.

1 Like
#5

qFlipper is based on Qt5 which does not support old macOS. We have no plans to add support for old versions of macOS and Windows, because this will require to complete rework of qFlipper.

#6

Maybe it could be documented what versions of things are actually supported?
“OS X 11 on Intel only”?

It seems like a bunch of people are burning time trying to get things working that have no hope, when that time could have been better spent improving things. (ie on the /update page and the Readme.md )

That said, I did get qFlipper to function on OS X 10.13, with the libusb replacement. It did update the firmware. There still continues to be some errors that I was hoping for some clarification on.

#7

I think you have lots of pain using 20 years old macOS. What browser do you use for example?
The only thing I can recommend you is to fork qFlipper and build it for old macOS. We can not help you here.

In feature version we will add a error banner to prevent running qFlipper on old macOS.

1 Like
#8

The hardware is 11 years old. OS X 10.13 first released in 2017. 10.13.6 in 2018, with the last major build in November of 2020.

Browsers:
Brave 1.37.116
Firefox 100.0
Chrome 101.0.4951.64
Though the first two want me to restart for the update. :wink:

1 Like
#9

I was able to get my Flipper flashed after the first failure, fortunately. It may have been a USB contact issue?

Either way, I also have the same comment: the hardware on my computer may be 11 years old, but it still runs OS X 10.13.6 just fine with no flagrant errors or slow-downs.

And Qt5 absolutely supports OS X 10.13 .
https://doc.qt.io/qt-5/supported-platforms.html

I think there is some confusion about how old our computers are.

#10

ran into this same issue. running 10.13.6 on a 2014 MBP. I followed @cyber’s instructions to link in another libusb build. The one I used was installed via homebrew. My exact steps were:

brew install libusb
cd /Applications/qFlipper.app/Contents/Frameworks/
mv libusb-1.0.0.dylib libusb-1.0.0.dylib_
ln -s /usr/local/Cellar/libusb/1.0.26/lib/libusb-1.0.0.dylib libusb-1.0.0.dylib

I was able to run the firmware update to 0.58.1 without any errors.

thanks @cyber and @graeioume for investigating!

#11

Father of flippers seems to be an elitest. Terrible representation for what I expect that you hope to be a successful company. You should probably hire a PR firm to help with your customer interaction because you don’t seem to know how to talk to people. Reminds me of a lot of my CS classmates in college.

1 Like