How to save my device from OTA failure?
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- embedded-iot, security
Research direction
Start with the reported OTA update flow and the idf.py serial connection failure for the LILYGO T-Display-S3. Determine whether secure boot permits recovery after this failure and document a verified recovery path, with success defined as restoring a bootable device.
Written by the indexing model from the issue text.
Description
Device: LILYGO T-Display-S3
Background
I purchased the device and flash the Jade latest firmware with secure boot enabled.
Everything works but I forgot to disable the DEBUG log output which could cause the Sparrow wallet failed to unlock the device.
So I try to do the OTA update with the DEBUG log disabled firmware.
The OTA result shows successful on both the device screen and my computer's terminal.
Problem
After I reboot the device, it became this:
Is it possible to save my device?
I tried to flash the firmware again by using idf.py tools but it failed due to
Connecting......................................
/dev/cu.usbmodem101 failed to connect: Failed to connect to ESP32-S3: No serial data received.
I think it's caused by the secure boot.
So can I save the device on my own? Or I have to send it to the manufacturer to rewrite the chip?
- Dominant language
- C
- Stars
- 502
- Forks
- 132
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Blockstream/Jade
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Blockstream/Jade#329 · 4 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Blockstream/Jade#315 · 3 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Blockstream/Jade#345 · 4 comments ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Blockstream/Jade#344 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Blockstream/Jade#340 · 2 comments ·
Maintainers usually reply within 2 days
All issues in Blockstream/Jade
Similar issues
-
Discover carries headerEdges that nothing reads since #1914 moved E0507/E0517 to the compiler graphOpentech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
2个显示的问题Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
coolsnowwolf/lede#14209 ·
-
Status: Opened
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 3 days