Skip to content
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

How to save my device from OTA failure? #216

Open
qdwang opened this issue Feb 12, 2025 · 2 comments
Open

How to save my device from OTA failure? #216

qdwang opened this issue Feb 12, 2025 · 2 comments

Comments

@qdwang
Copy link

qdwang commented Feb 12, 2025

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:

Image

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?

@JamieDriver
Copy link
Collaborator

Once you enable 'secure boot' you can no longer flash the device. (That's partly what the 'secure' is about - no-one can take your hw and flash nefarious fw onto it).

@qdwang
Copy link
Author

qdwang commented Feb 14, 2025

@JamieDriver
Thanks for the reply. I managed to recover my device by doing the OTA again with the previous firmware.

It seems the only way to recover is

  1. The OTA update functionality still works despite the device's issues.
  2. You have a backup of the previous firmware bin file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants