Brick after adding Reboot Schedule (firmware bug)
Warning: Do NOT add a Reboot Schedule for 1st day of every month at 00h 01m because the ER605 will become a brick after reboot.
Bug in firmware
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
KenoUno wrote
@Clive_A Please, do not try, it Will brick your device.
Add a Schedule Reboot for every month on 1st day and 00h 01m
Click ENABLE
Click OK
Then manually reboot your ER605. IT WILL NOT BOOT.
First ER605 with 2.2.6
Second ER605 with 2.2.5
Both lost in action, jejeje
What does the port LED look like?
System LED?
Bricked does not mean it is dead. You can use firmware recovery mode to recover it.
How to use the Emergency Mode to recover the firmware for Omada Gateways
As you reported this, we gotta do a local test with the same firmware and hardware. No worries about us.
- Copy Link
- Report Inappropriate Content
@Clive_A I already tryed. I did put into emergency mode, loaded the firmware with the same result: Only POWER led on after reboot
- Copy Link
- Report Inappropriate Content
KenoUno wrote
@Clive_A I already tryed. I did put into emergency mode, loaded the firmware with the same result: Only POWER led on after reboot
The firmware recovery mode got a separate cache on the storage, which cannot be deleted or modified without root privileges. That's reserved for the firmware recovery.
So, it is either that you missed or did not perform it correctly. The recovery mode can fail to recover for certain users. In my experience with the proper steps, I never failed a time in recovery mode.
The firmware determines the hardware interface. I don't think it would completely ruin the system. The test team will need some time to confirm this behavior.
- Copy Link
- Report Inappropriate Content
@Clive_A Sorry for My poor English. Recovery Mode runs perfect. Open the web page where You browse and upload the firmware. It says everything works fine but after reboot, no BOOT at all.
- Copy Link
- Report Inappropriate Content
KenoUno wrote
@Clive_A Sorry for My poor English. Recovery Mode runs perfect. Open the web page where You browse and upload the firmware. It says everything works fine but after reboot, no BOOT at all.
We confirmed that the device enters the reboot loop.
As the system has not been syncing with the NTP, it is on default time, which should be 2018, January 1st, and it will enter the reboot loop before the NTP(proper time) is synced.
Dev recommends you try reset or recovery mode. That should fix it.
- Copy Link
- Report Inappropriate Content
@Clive_A I tried reset (long press reset button) and recovery (emergency) mode for firmware reload... None of that helps, the er605 does not boot whatever i do
- Copy Link
- Report Inappropriate Content
KenoUno wrote
@Clive_A I tried reset (long press reset button) and recovery (emergency) mode for firmware reload... None of that helps, the er605 does not boot whatever i do
Keep pressing the reset button until the power LED is blinking. That's what you need to do to fix this.
Recovery mode does not erase the settings. So, this requires a reset anyway.
Unplug the power supply -> wait for 30 seconds, the power indicator light is on -> long press the reset button until the power indicator light flashes and then release it
- Copy Link
- Report Inappropriate Content
@Clive_A Thanks for your time, i don't want to sound with a bad attitude but i did try that already. I did perform the reset to factory defaults sometimes before (forgotten password, etc)... It was my first try this time too, it did not work. Believe me, i know how to do it, i did it... It didn't work.
Sorry if that sounds Bad, My English is very límited but believe me, i'm very familiar with those procedures and none of them fix the er605
- Copy Link
- Report Inappropriate Content
KenoUno wrote
@Clive_A Thanks for your time, i don't want to sound with a bad attitude but i did try that already. I did perform the reset to factory defaults sometimes before (forgotten password, etc)... It was my first try this time too, it did not work. Believe me, i know how to do it, i did it... It didn't work.
Sorry if that sounds Bad, My English is very límited but believe me, i'm very familiar with those procedures and none of them fix the er605
Dev mentioned that they reset it in this way. They tested this method.
Unplug the power supply -> wait for 30 seconds, the power indicator light is on -> long-press the reset button until the power indicator light flashes and then release it
If this does not work for you, you can consider the RMA.
This issue is reported, and they will come up with a plan to address this in the future firmware update.
For anyone else who read this post, DO NOT TRY IT.
If you happen to face the same issue, try the steps above.
- Copy Link
- Report Inappropriate Content
@Clive_A Sorry, i had to begin with that... The first ER605 was send to RMA under report TL-01692 (TPLINK LATAM). The second er605, the brand new delivered today to me, failed in the RMA location in front of the guys there. The two persons there, awesome guys, try everything too. Tomorrow i will receive another one. Obvously, i will not config the Scheduled Reboot. I posted because none of us, included the RMA guys, could fix it and think it could be a good idea post the warning.
The team at TPLINK LATAM told me that they are going to set a lab to test if the bug affects a router under Omada Controler, if it happens in other similar models and another bunch of test to inform to TPLINK with all data. Meanwhile, they will send me a new one with the promise not to configure that Scheduled Reboot. Hope this helps.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 758
Replies: 21
Voters 0
No one has voted for it yet.