Backup & Restore Official Firmware of Sonoff WiFi Smart Switches

Contents:

Controlling Sonoff Smart Switches without internet over Local Area Network is hot topic for Sonoff enthusiasts. After loading any custom firmware to Sonoff, you cannot go back to the official firmware but now you can!!. Just backup your official firmware by following the instructions below and you can restore it later if you want. So Let’s get started..

Hardware Requirements:

Software Requirements:

Step-by-Step Procedure:

Step A:

Download and install Python 2.x or 3.x from https://www.python.org/downloads. Download Esptool from https://github.com/espressif/esptool/releases. Extract the contents of esptool compressed file to C:\. All the contents of esptool should be under  c:\esptool.

Step B:

  • Open Command Prompt (Start > Run > cmd) and navigate to esptool folder.
  • Install the esptool by issuing the command below.
It takes few seconds to upload firmware and output will be shown as follows.

Step C:

Now We are just one step behind to download / upload any firmware to our Sonoff Smart Switch. Connect FTDI to Sonoff Smart Switch (For detailed information about each Sonoff Switch, visit Sonoff Smart Switch LAN Control without Internet) and start Sonoff device in programming mode. Now find the port under Control Panel > System > Device Manager > Ports at which Sonoff device is connected.

Determine the Flash Size:

  • Change COM5 to your own Port.
  • Wait few seconds and it outputs the flash size as shown in picture below Detected flash size: 4MB.

Backup / Download Official Firmware:

1MB Flash:

4MB Flash:

  • Change COM5 to your own Port.
  • Change flash size parameter  0x100000  for 1MB and  0x400000  for 4MB flash.
  • Wait a minute and firmware binary file will be downloaded and saved in to  c:\esptool

It takes few seconds to upload firmware and output will be shown as follows.

Official Sonoff Firmware Binary Files:

Step D:

Erase Flash Memory:

Erase the custom firmware from flash memory before uploading any new firmware.

  • Change COM5 to your own Port.

It takes few seconds to erase firmware and output will be shown as follows.

Upload Official / Third Party Firmware:

Determine the flash size as discussed in Determine the Flash Size section. Copy the official / any third party firmware binary file to  c:\esptool folder if it is not already there and upload it by issuing the command below.

1MB Flash:

4MB Flash:

  • Change COM5 to your own Port.
  • Change flash size parameter  -fs 1MB  for 1MB and  -fs 4MB  for 4MB flash.
  • Change sonoff.bin to the name of your firmware file inside  c:\esptool folder.

It takes few seconds to upload firmware and output will be shown as follows.

Troubleshooting:

  • Choosing Wrong COM Port will cause the following error.

  • If following output is shown, Sonoff is not correctly connected to FTDI, Check wire configuration or terminals.

  • After restoring the official firmware, if led does not blink, It means you have problem with backup image
    • either backup image is corrupt – Check 3.3v power supply during backup
    • Chose wrong flash size during backup – See Determine the Flash Size Section

 

34
Leave a Reply

avatar
13 Comment threads
21 Thread replies
2 Followers
 
Most reacted comment
Hottest comment thread
16 Comment authors
mcgyver83AhmedcarozoynarizotaVickyMalikSerg k Recent comment authors
  Subscribe  
newest oldest most voted
Notify of
Serg k
Guest
Serg k

I need Official Sonoff Firmware for Sonoff rf BRIDGE

redlyon
Guest
redlyon

Does anyone have the original sonoff T1 US 2C firmware?
Thanks

D. Mora
Guest
D. Mora

The only problem I saw running this directions is that the ID flashed in the device is the one coming in the .bin file, which belongs to a real device, so it means that once flashed, the device will have a duplicated id, and when registered into eWelink cloud it will dump the real one, or even worst, all the people downloading this file will be deleting the registry of the device from each one.

So, How to generate a unique Device ID to edit with hex in the bin?

carozoynarizota
Member
carozoynarizota

D.Mora you are right, but both the Device ID and the MAC-ADDRESS are found as seen on eWelink on the HEX file. So you can edit the file before uploading to your new device. With that you can have any ESP module running at least Sonoff Basic and RF as if they were originals.

vickeymalikpc
Member
vickeymalikpc

carozoynarizota, Is it possible on non rooted phones? And what is the procedure?

carozoynarizota
Guest
carozoynarizota

vickeymalikpc I´ve done everything through my desktop PC, procedure explained here to flash Sonoff devices is the same for every ESP8266 you come across. Once the right FW version flashed on your device it is supposed to work according to what is it in there. For example if you pick an ESP-01 and flash that device with Sonoff Basic R2 FW, then you can make it go up on ewelink in your phone (that can be downloaded from play store). D.Mora points here that you will be replicating the ID found on you FW file, then my answer that it… Read more »

D. Mora
Guest
D. Mora

Yes, it can be modified, the problem is that the Device ID is linked to a unique API key, so if you modify the device ID to any random number (or even the original one), it will register to the eWelink cloud, but it will never achieve the connection to work without the correspondent API Key. The only way to restore a Sonoff device to its original with this firmware, can happen if you know your original, Device ID (or anyone not used) and it’s API key; the MAC is not problem as it is not related to the firmware,… Read more »

Ahmed
Guest
Ahmed

So these files are useless!!

mcgyver83
Guest
mcgyver83

How can I get the Device ID if I already flashed the tasmota and I want to come back to original?

carozoynarizota
Guest
carozoynarizota

Did you flash it inmedately before testing your device with the original FW in the ewelink APP? If registered may be you can get the original ID from there. If not you can edit the files shared here to give them a different ID to see if the ewelink app recognises your device.

carozoynarizota
Guest
carozoynarizota

Good point, they might be doing some kind of verification through their servers. But at least we know that the IDs are not linked to device type (as I was able to run a Basic like an RF module). Did you tried to change the device ID to see if it is rejected by the ewelink platform?

carozoynarizota
Member
carozoynarizota

Hi, I was doing some tests with Sonoff Basic and RF. Downloading their FW and then uploading the files to a different device, also to an ESP-07 stand alone module. This way I was able to make a Sonoff Basic or an ESP-07 run as a Sonoff RF on Ewelink. I tried the same with the RF image shared here and it runs OK, but if I upload the TH10/16 images nothing happens. I power the device, put GPIO to GND for a few seconds but the ITEAD Wifi doesn´t appear. Any clue?

Vlad
Guest
Vlad

Great write up, thanks!

I have one residual question. Is it possible to write the official firmware, read from a 1M flash onto a 4M flash?

The reason I ask is that I have swapped the flash chips (from 1M with 4M flash) on most of my Sonoff basic’s. I would like to restore the original firmware onto the 4M flash chips.

LD Taylor
Guest
LD Taylor

I have two SONOFF basic switches both loaded with custom firmware. Using your backup/restore processes, I backed up factory firmware and restored to these two switches. The backup, erase, then restore worked perfectly. However, when I powered up both restored switches, nothing, no lights. What am I missing here. Does backup/restore only work with the same switch? Thanks for your guidance.

Stan
Guest
Stan

I have same issue with sonoff POW after succesfull backup/restore it is dead no light. The flash size is correct 4MB Source POW: C:\esptool-2.6>esptool.py –port COM3 flash_id esptool.py v2.6 Serial port COM3 Connecting…. Detecting chip type… ESP8266 Chip is ESP8266EX Features: WiFi MAC: 5c:cf:7f:92:2d:34 Uploading stub… Running stub… Stub running… Manufacturer: e0 Device: 4016 Detected flash size: 4MB Hard resetting via RTS pin… C:\esptool-2.6>esptool.py –port COM3 read_flash 0x00000 0x400000 image4M.bin esptool.py v2.6 Serial port COM3 Connecting…. Detecting chip type… ESP8266 Chip is ESP8266EX Features: WiFi MAC: 5c:cf:7f:92:2d:34 Uploading stub… Running stub… Stub running… 4194304 (100 %) 4194304 (100 %) Read… Read more »

Smax
Guest
Smax

For Martin do you need press button to your sonoff pow and connect power for programming and read.
This is error cpu not in programming mode.9

Smax
Guest
Smax

Programmatiin working. I change firmware ok . Test espurna and espeasy work. Revert original with new flash not work . Old flash is burned..
I have double backup. One 1mb and one 4mb. Memory flash is 4mbyte this is Pow sonoff.
Tedted ftdi and board ch340

Martin Hardoy
Guest
Martin Hardoy

If you keep getting this:
esptool.py v2.3.1
Connecting…….._____….._____….._____….._____….._____….._____….._____….._____….._____….._____

A fatal error occurred: Failed to connect to Espressif device: Timed out waiting for packet header

Try to disconnect the esp from the PC and start Sonoff device in programming mode again

letroll
Guest
letroll

push the button when plugging ftdi usb cable and release it after 2 seconds

Smax
Guest
Smax

??? Dear not have solution? Change spiffs? Or other ? Have all file for upload? Only Boot ?
Pls help

Smax
Guest
Smax

I have dump for my original sonoff pow i have dumped 1mb and 4mb . My fflash type original is 25q32. I have burned original switch in the sonoff pow. And have replaced with 4.5V power supply. And have changed many time to original and espurna.Working fine for 60 day. If reprogramming flash a this day not work. Error md5. A this time have replaced flash with qh32bhig brand xmd, recovered by old lolin board. New test with new flash i have uploaded espurna and work fine. Router ap and work fine. If reinstall original sonoff pow firmware not work.… Read more »

Smax
Guest
Smax

Hello dear i have bakup but not working? I have replaced new flash , uploaded my backup and not work. I have error boot @1000 or boot @81000
Help for backup?
Oter firmware working fine.

zweistein
Guest
zweistein

Hi,
Great article. Thanks for it.
But I have a problem in reading flash:
“A fatal error occured: Corrupt data, expected 0x1000 bytes but received 0xffd bytes”
Do you have any idea about this error?

Thanks