Running qFlipper 1.2.1 on windows 10, qFlipper crashed while updating my Flipper Zero from Version: 0.56.1 commit: d21e5bd5 radio: 1.13.0 to Version: 0.69.1 commit: 3ab17e59 radio: 1.13.3.
After this flipper zero was off and did not seem likely to respond.
On restarting qFlipper, it suggested 'repair' in the place where it normally proposes to update, I did that, it worked (it seemed to take longer than the original update when I first received my flipper zero.)
The entier procedure (flash/crash/repair flash) was repeated with my other flipper zero, etc.
Based on reading the logs, it seems like the coprocessor firmware might be an issue, therefore this might be connected to this issue in some way.
But "flash failed, Flipper Zero doesn't respond until repair-flashed" feels like a sad but not unexpected outcome when flashing anything.
"qFlipper terminated unexpectedly mid-update" feels like a failure to catch (and possibly log) an exception. So I'm reporting it, as a seperate bug, and just in case these log files are helpful.
Expected behavior
Normal device flashing experience, or on failure, the app to stay open and explain what went wrong.
Actual behavior
App window closes, one log file seems a little corrupted 3 lines before the end, etc
Additional troubleshooting
On the second try it ran a full repair without crashing.
On the second device, entire interaction was repeated, except that the log doesn't seem to have gotten corrupted, or not the same way, (is this a threading issue?)
Describe the bug What were you trying to do?
Running qFlipper
1.2.1on windows 10, qFlipper crashed while updating my Flipper Zero fromVersion: 0.56.1 commit: d21e5bd5 radio: 1.13.0toVersion: 0.69.1 commit: 3ab17e59 radio: 1.13.3.After this flipper zero was off and did not seem likely to respond.
On restarting qFlipper, it suggested 'repair' in the place where it normally proposes to update, I did that, it worked (it seemed to take longer than the original update when I first received my flipper zero.)
The entier procedure (flash/crash/repair flash) was repeated with my other flipper zero, etc.
Based on reading the logs, it seems like the coprocessor firmware might be an issue, therefore this might be connected to this issue in some way.
But "flash failed, Flipper Zero doesn't respond until repair-flashed" feels like a sad but not unexpected outcome when flashing anything. "qFlipper terminated unexpectedly mid-update" feels like a failure to catch (and possibly log) an exception. So I'm reporting it, as a seperate bug, and just in case these log files are helpful.
qFlipper-20221024-235602.txt (crash) qFlipper-20221024-235645.txt (successful repair) qFlipper-20221025-061453.txt (crash) qFlipper-20221025-061341.txt (successful repair)
Expected behavior Normal device flashing experience, or on failure, the app to stay open and explain what went wrong.
Actual behavior App window closes, one log file seems a little corrupted 3 lines before the end, etc
Additional troubleshooting