ER605 V2 firmware update to 2.1.0 is work not correctly
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ATENTIONE:
Today an update version 2.1.0 was released for the ER605 V2, which can be installed directly via the controller.
PLEASE DO NOT UPDATE
The update put my ER605 V2 in an endless loop disconnected-adoption-configuration-connected-disconnected.
When connected, all WAN + LAN ports are shown as disabled and the WAN connections as dropped.
Even after hours and through several hardware resets, this behavior does not change.
I can use the internet only with my replacement devise ER605 V2 with the old firmware version 2.0.1, now.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @Phuripat and other community members,
The support team has noticed this issue, and I have released the Solution Post in here.
If you are still having issue after referring to this Solution post and troubleshooting, or if your WAN Connection Type is not PPPOE and still have the same issues with the latest firmware, the engineer may need to collect some detailed information exactly when the issue occurs to figure out the issue.
If you are willing to try further troubleshooting with our engineer via email directly, please feel free to let me know and I'd help to escalate your case.
Best Regards!
- Copy Link
- Report Inappropriate Content
Jup, amazing fail - again. Firmware 2.1.0 is already no longer available on the website. OTA-Update is still available.
The problem can be "fixed" as follows:
Reset the ER605 via Hardware-Button since the Firmware-Downgrade via controller won't work due to adopt-loop. Log in directly to the router, the IP address is now 192.168.0.1. Depending on the configuration, you may need to connect directly to the router via cable and set your ip address manually. Make a Firmware Downgrade to 2.0.1, just download it from https://www.tp-link.com/de/support/download/er605/#Firmware
After that you should be able to adopt the router again. Your settings won't be lost as they are stored on the Omada controller.
I hope this helps a little.
- Copy Link
- Report Inappropriate Content
I already know this way of resetting and have already done it afterwards.
Since I have a second ER605 V2, I swapped it first to keep the downtime of the entire network as short as possible.
Nevertheless, thank you very much for your help.
- Copy Link
- Report Inappropriate Content
@Phuripat I have ER605 v.2 with OC200 running latest version ( 5.7.6 ? ) and the upgrade from ER605 v.2 firmware 2.0.1 to 2.1.0 went smoothly and I have none of the problems mentioned here. So it could be an issue but it seems it affects only some users.
- Copy Link
- Report Inappropriate Content
Thanks for the tip the update broke my wifi. I was rebooting everything and factory resetting the APs but that didn't work. Downgrading to V2.01 fixed it.
- Copy Link
- Report Inappropriate Content
It seems that the update actually runs cleanly and works smoothly for some users. I'll just rule out that the switches and EAPs don't further affect the update. Since I have a second ER605 V2 with firmware 2.0.1, I would like to update it manually to firmware 2.1.0 in stand-alone operation. Is the update available for free download?
- Copy Link
- Report Inappropriate Content
I also had the same looping issue after upgrading my ER605 V2 from 2.0.2beta to 2.1.0.
I managed to downgrade the firmware after adopting it to a temporary Omada Controller v5.8.4 on windows.
- Copy Link
- Report Inappropriate Content
@Adandu May I know where you got a beta version of 2.0.2 from?
Where can I get this version?
If you try to downgrade the router during operation (after the error has been discovered), you usually get an "https" error message.
So here is the easiest way and quickest way to downgrade the router to the old version and thus minimize network downtime:
- remove the router from the Omada controller
- then reset the router via hardware reset
- connect a PC or notebook directly to a LAN port of the router
- select the IP 192.168.0.1 via the browser
- the web login of the router should now open, in which the creation of a user and password is required (restart the router if necessary)
- then the previous firmware can be installed manually.
- Copy Link
- Report Inappropriate Content
@Phuripat check https://community.tp-link.com/en/business/forum/topic/581548
- Copy Link
- Report Inappropriate Content
OK thanks.
I see that the beta only works with the 5.5 controller and not the 5.6 though. I'm already using the 5.7.6 controller
I will now set up a test environment for further testing and let it run for a longer period of time for further tests.
- Copy Link
- Report Inappropriate Content
I'm using the 2.0.2 20220727 beta form this post and it is working with Linux Controler V 5.7.x without any problems.
https://community.tp-link.com/en/business/forum/topic/522628
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 4960
Replies: 21
Voters 1
