Router stuck after Omada disconnect, no bootloader access, login required over console
The router was previously managed by an Omada Software Controller.
After removing the controller, I accessed the router via HTTP and performed a factory reset from the GUI.
After reboot:
No DHCP is provided
Web GUI is not accessible
Device does not respond on default IPs (192.168.0.1 or 192.168.0.10)
Only serial console is accessible
Current behavior
On boot, console shows:
Jump to BL
Username:
Device asks for login, but:
admin/admin → not working
admin/(empty) → not working
root/(empty) → not working
root/admin → not working
tplink/tplink → not working
SYS LED blinks during boot, then stabilizes
LAN/WAN port gets link only during normal boot (not during reset/recovery attempts)
What I have already tried
1. Hardware reset
Held RESET for 15–20 seconds during boot
Also tried extended reset (~45 seconds)
No change
2. Emergency Mode (official procedure)
Set PC to:
IP: 192.168.0.20 / 255.255.255.0
Connected via LAN
Held RESET while powering on
Tried accessing:
http://192.168.0.10
Result:
No response
No ping replies
Port does not come up in this mode
3. Serial console
Connected via UART (115200 8N1)
Full boot visible
No option to interrupt bootloader
No U-Boot prompt or recovery menu available
4. Network checks
Tried multiple ports
Verified link status
No ICMP response during recovery attempts
Current conclusion
Bootloader seems to be alive (BootROM → BL → system)
System partially boots (login prompt appears)
Network services are not initialized
Recovery (Emergency Mode) does not start
No working credentials for CLI access
Questions
Is there any hidden or alternative recovery method (TFTP, special key combo, etc.) for this model?
Is it possible that the device is stuck in “Managed by Controller” state and blocking standalone access?
Is there any default CLI credential specific to Omada-managed gateways in this state?
Can firmware be forced via serial/bootloader in this model?
Is this a known issue after factory reset on adopted devices?
At this point I’m trying to determine if there is any way to recover it without hardware flashing or RMA.
Any help would be appreciated.
