Posted: Mon Aug 05, 2019 7:20 Post subject: Netgear EX6200 - bricked?
Hi everyone - this is my first DD-WRT router flash try and despite my best efforts to read through all the information available at least three times i think i might have missed quite a few things as my try ended with a non-functioning router.
First some hardware/software information.
OS: Windows 10 Version 10.0.17134 Build 17134
Internet: Wireless connected to local network for access while flashed router to the Ethernet port on the PC
Router: Netgear EX6200 - no identifying marks on it or serial numbers (not purchased by myself so no receipt or etc to find details). Identified it by design. Looking at the board it looks like all the other EX6200 boards I've seen around the net. Also, the GUI identified itself as such.
Netgear firmware version:
- initial: V220.127.116.11_1.1.109
- before flash: EX6200-V18.104.22.168_1.1.70.chk
Steps I took:
- Checked https://wiki.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear for the build version and install guides
- As there was no install guide for EX6200, but it accepted the same build as R6300/AC1450 i used that one https://wiki.dd-wrt.com/wiki/index.php/Netgear_R6300v2#Netgear_AC1450
- Followed all the steps from the beginning (reset, setup, etc) up to uploading new flash file.
- Got an error that Firmware upgrade failed. Please check your file.
- From https://www.myopenrouter.com/forum/how-update-ex6200 i found that downgrading the firmware version should solve it.
- After the proper reset and setup the new firmware accepted the the DD-WRT build and started the setup process.
- After the setup process finished on screen the in-page frame said it cannot reload
- Following the instructions i left the router alone for 10 minutes and then trying to access it via a separate TAB i could not get the GUI
- Tried doing the recommended reset, but no response
- The Router is not getting a subnet, blank gateway, etc
At this point i realized something went wrong (doh) and looking through the forum and following the numerous troubleshooting topics (specifically peacock's among others) I did the following:
- Tried the hard reset / 30-30-30 3x times but to no avail
- connecting the router via cable i get "Unidentified network" and the gateway is blank and no information on the subnet
- connected the router to another laptop not connected to the internet in any way and had no contact with this router
- assigned manual TCP/IP settings (192.168.1.10/255.255.255.0/192.168.1.1 and 22.214.171.124 and blank)
- ping -t 192.168.1.1 gets either "Request timed out" or "Host Unreachable"
- tried the same ping and accessing via browser the gateway while pressing the reset button and powering up the router and still no TTL response
- connected the router to my main router but it's not seen on the network map. Connecting my PC to the broken router gets the same Unidentified network and no Gateway Info to access the GUI - the IP assigned to the PC is in the 169.254.155.x range - but blank trying IP for GUI gets me nothing
- tried power cycling by leaving the router unpowered for ten minutes
- might not be explicit but did follow Note6 from Peacock Thread
At this point I think i have exhausted all possibilities, but i wanted to check with the community and see if in desperation i might have missed something
The device seems to recognize the J252 connection as the port leds all light up and stay lit - which is different to regular status (constant light on power, yellow on 2 and 5ghz as well as the transmit led, while the port led is lit green for whichever ethernet is in).
If anyone has any idea i would appreciate the support
Those are pages/topics that I've used to either prepare for the flash or troubleshoot it afterwards.
Unfortunately my problem right now is that I'm not getting any response from the device even with a serial cable so loading a standard flash to recover the device doesn't seem possible. (like i mentioned i'm hoping it's the TTL cable or i'm doing something wrong, but i haven't been able to find what that might be).
I read somewhere else that you can get some response if you don't connect the ground - just tried that and once i get the Rx and Tx right Putty just gets a mumble of squares filled with dots like "▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒"
Joined: 08 May 2018 Posts: 2691 Location: Texas, USA
Posted: Thu Aug 08, 2019 5:24 Post subject:
That is usually a sign of bad / reversed connection or no ground ... I've never seen where you didn't need the ground connected. So, you may be more than just reversed. GND-GND, TX-RX, RX-TX. Does your serial to usb cable have markings to tell you which wire is which? Also, if you short TX and RX on the serial-usb cable, minicom or PuTTY should echo the output of what you type, to test if the cable adapter is bad, but since it worked on another device, then it shouldn't be. BUT, hopefully, the EX6200 isn't fried somehow...
Joined: 08 May 2018 Posts: 2691 Location: Texas, USA
Posted: Thu Aug 08, 2019 5:56 Post subject:
Did you try changing which ground lead you used? Not that it *should* matter, but, the order, as best I can tell, should be, from right to left, the right being where the black heatsink is, tx, rx, gnd. So, your rx wire from the usb adapter shoud go to the far right pin, tx to the next pin, and one of the grounds to the next pin, if that makes sense. If that doesn't work, then the usb adapter card is labeled different than what I have seen.
And the board in yours has "U12H269T01", so obviously there is more than one board number for the EX6200, or, it is actually another model, perhaps... BUT, other devices have been known to have more than one board number, so tough call.
I would test the pins with a multimeter to see which one is the +3.3V, though!!