-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on firmware install: resources.tar operation timeout #40
Comments
yup, problem on OFW. if you want to make yourself heard on the matter, here flipperdevices/flipperzero-firmware#3452 |
read the update below |
This comment was marked as duplicate.
This comment was marked as duplicate.
@feldlef read what i said to the other person, right above your comment. follow those instructions. |
Not sure if it was just a fluke, or what, but I was having this issue. I tried twice, with failures. Before my third attempt, I increased my screen lock timeout from 2 minutes to 10 minutes, on a hunch, and it worked. I didn't test it scientifically, so it may have been a coincidence. Figured I'd mention it anyway. |
had the same error resolution:
next attempt went smoothly |
Update: OFW has now rectified the issue, and all CFWs either have the new proper fix to this issue (Momentum, Unleashed, probably RM soon enough) or the old USB CDC revert patch (XFW). OFW is still affected by this bug in 0.102.3, but is fixed in dev branch and will be fixed from next OFW release. If you are affected by this issue: select "development" channel in qflipper / phone app, and update to latest OFW dev; then, update to Momentum / whatever FW you want. |
Fix released in OFW 0.103.1, if necessary update to OFW if you have issues installing Momentum or any other CFW. After that, CFW updates should be fine and not affected by this bug. |
Describe the bug.
On a fresh 32gb SD card with stock flipper zero firmware, latest release (downloaded today), on Windows 11
Reproduction
Install using Qflipper on windows 11, select Zip file downloaded from Github
Logs
The text was updated successfully, but these errors were encountered: