RE700x dont start after firmware update

RE700x dont start after firmware update

14 Reply
Re:RE700x dont start after firmware update
a week ago

Hello,

 

I'm having the same issue with my RE700X repeater (hardware version 1.0). It keeps trying to boot indefinitely.

When plugged in: the power led is on, then every 30 seconds, all leds are lighting briefly blue for 1 second, then the wifi led is lighting briefly red for 1 second and turns off.

 

What has been done: upgrade from RE700X(EU)_V1_1.1.4 Build 20230509 to RE700X(EU)_V1_1.2.10 Build 2025062 firmware.

Firmware upgrade result: successful.

Done from: Tether App

 

Seems the firmware is corrupted and the repeater is no more able to boot correctly.

 

Before you ask: yes I tried on several different electric plugs, yes I tried to reset the repeater several times.

Could you please help by providing a solution to fix it? How can I reinstall or downgrade the firmware to recover the repeater?

 

Thanks in advance for your support.

 

 

  0  
  0  
#12
Options
Re:RE700x dont start after firmware update
Thursday

  @alkiris 

Sorry, but at this point, the repeater is dead. There's no way to flash another firmware version, except by soldering wires to the PCB, and even then you need to know where and how to solder those wires.

  0  
  0  
#13
Options
Re:RE700x dont start after firmware update
Thursday - last edited Thursday

  @Tim584 

 

Thank you I appreciate your reply, but I would also please request an answer from a TP-Link support representative.

If the repeater is effectively out of order while I upgraded the firmware from Tether App (so just the way it should be done as per TP-link recommendations), I need someone from TP-Link tell me how this is just possible and what kind of support we can expect from them.

  0  
  0  
#14
Options
Re:RE700x dont start after firmware update
Friday

Hello @alkiris ,

 

Firmware upgrades are intended to improve performance, but sometimes unexpected behavior may occur during or after the upgrade process. It looks like you've already tried some solutions, but they haven't improved.

 

Please contact local support for further assistance.

  0  
  0  
#15
Options