Tasmota: Bricked device?

[kalety]

Upgrading via OTA (5.1.6) one of my sonoffs, the screen says 'this device resseting (or something) in few seconds', but were several minutes and then I closed the web page... I'd try to reflash it but I can´t put it in flashing mode, don't respond..

Bricked device? (like title ;))

[kruebsam]

Have you tried disconnecting it from the mains and reconnecting it? I noticed similar behaviour once in a while after upgrading. However, flashing it the hard way (with direct connection to the board) should bring it back to life.

[kalety]

Thanks kruebsam for your help!, I tried everithing, the problem is that the led no flashing nor blinking, anything... Whe you say "hard way", you want say the normal flash through FTDI?

[davidelang]

Yes, unless the chip itself is fried, you can flash it via the serial port. the
'ground gpio0 and flash' is not something that can be changed by the software
you load on it.

[jaysuk]

Or try resetting the board using the button. See the wiki for the correct
amount of presses.

On 13 Jun 2017 09:12, "David Lang" [e-mail] wrote:

Yes, unless the chip itself is fried, you can flash it via the serial
port. the
'ground gpio0 and flash' is not something that can be changed by the
software
you load on it.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arendst/Sonoff-Tasmota/issues/514#issuecomment-308041188,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACdJBkL550tKAQKgNOq52b2jAYdJUbeZks5sDkR1gaJpZM4N1NK6
.

[guillier]

Something similar happened to me and I thought I would have to replace the chip but didn't have to in the end.

With https://github.com/espressif/esptool can you run successfully?

esptool.py --chip esp8266 --port /dev/ttyUSB0 flash_id
and/or
esptool.py --chip esp8266 --port /dev/ttyUSB0 erase_flash

You'll probably have to press (and keep pressed) the button before applying the FTDI power, took me a few tries before it worked. Then I reprogrammed the chip using platformio (again pressing the button at boot).

Good luck!

[kalety]

Thanks, I've tried everyhing, and no success... Only 5€ / $ I've loss...

Enviado desde mi iPhone

El 14 jun 2017, a las 16:30, François GUILLIER [e-mail] escribió:

Something similar happened to me and I thought I would have to replace the chip but didn't have to in the end.

With https://github.com/espressif/esptool can you run successfully?

esptool.py --chip esp8266 --port /dev/ttyUSB0 flash_id
and/or
esptool.py --chip esp8266 --port /dev/ttyUSB0 erase_flash

You'll probably have to press (and keep pressed) the button before applying the FTDI power, took me a few tries before it worked. Then I reprogrammed the chip using platformio (again pressing the button at boot).

Good luck!

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[jetema]

The last chance is to replace the flash memory ( U6 on the picture ), it is not quite difficult, look this video
https://www.youtube.com/watch?v=8mz5sCAvDAY&t=616s

I have revived some sonoff that had flash blocked/fault

[davidelang]

if the esp8266 is still functioning, you should be able to get it into
programming mode and flash it again. If it's not, changing the flash won't help
you.

if it's retaining 'bad' settings, then you need to change CFGHOLDER or flash
with all zeros.

These are pretty simple devices, and the flashing mechanism is built in to the
chip, not something that can be changed in software. So the only way to 'brick'
it is to damage the chip (say by applying 5v to it)
k

[MesserMike]

i also think i have the device bricked, BUT I coincidentally found a loose solder joint of an smd component...

The primary or life side was ok, but on the secondary side (3,3 volt side) was a loose solder joint...
iCheck the lines with an messuremeter and find it.
i use 250 degre on my solderingstation and put the solder short on every single solderside of the items...
after this work the pow works pobably again... :)

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem.