It probably has a cfe that prevents flashing of any third party firmware. Just like the rt-ac3100 and rt-ac88u. _________________ I am far from a guru, I'm barely a novice.
Posted: Mon Jul 31, 2017 4:20 Post subject: Which Kong file to tftp - bin or trx?
I've been fighting with this router most of the day today. I've used recovery mode to get back to the stock firmware a few times, I've tried using the stock firmware's update process to load BS's 29739 build, got the reboot loop, tried using tftp to install Kong's build, still reboot looping.
By the way, which Kong firmware am I supposed to load using tftp - the bin file, or the trx file?
Currently, I'm back to stock firmware. The only thing I haven't tried is the serial cable method mentioned in this thread, mainly because I don't have a computer with a serial port anymore, so while I understand how to connect the serial cable in the router, I have no idea how I could connect the other end.
I'm quite close to boxing this thing back up and returning it to Fry's.
Posted: Mon Jul 31, 2017 13:17 Post subject: It worked!
So, the last thing that I attempted was using the recovery tool to load r31722. It seemed to still be in a reboot loop, but I unplugged it for like 5 minutes, then plugged it back in and let it sit overnight. This morning, I was able to bring up the web interface of dd-wrt. I then did a firmware upgrade to Kong's latest build, DD-WRT v3.0-r32805M (7/24/17). It seems that waiting was key.
I am also completely stuck in a bootloop attempted fixes:
- 30-30-30
- reset 10s hold
- left it running overnight
- attempted to clear nvram
- attempted to ping(destination unreachable on 192.168.1.x subnet)
- Attempted to tftp even without ping
- attempted asus firmware recovery
What i did: went to the asus website and attempted to flash via the web interface, showed success however obviously wasn't successful.
I am also completely stuck in a bootloop attempted fixes:
- 30-30-30
- reset 10s hold
- left it running overnight
- attempted to clear nvram
- attempted to ping(destination unreachable on 192.168.1.x subnet)
- Attempted to tftp even without ping
- attempted asus firmware recovery
What i did: went to the asus website and attempted to flash via the web interface, showed success however obviously wasn't successful.
build used was kong's latest test
Based on my experience, I would try turning it off for at least 5 minutes, then turn it back on, and leave it on.
Your case is different from mine though - yours is not responding to pings at all, which is indicative a more serious problem. Mine would at least respond to pings for a little while during each boot loop - I was getting a response that had TTL=100, which is what you look for to do the tftp. If yours is not responding to pings ever, then you may have to consider the JTAG or serial cable options. Check the Peacock thread about bricked routers.
From the webif I installed Brainslayers firmware. The device rebooted. It took about a minute to reboot.
Just like last time, the lan ports did not appear to work or have dhcp. So I logged in to the router wirelessly ssid:ddwrt open. I was prompted to change the default password which I did. I then proceeded to install Kongs firmware from the webif.
OK... Apologies in advance but I'm trying to be sure I understand before I start. I have several routers with DD-WRT but this my first attempt with RT-AC5300. The thing is brand new and I've NOT updated the stock firmware.
3. Through the stock firmware update page in the web interface, install the .trx
4. Reboot and log into the new webif either by hardwire connection (if available) or wireless connection to open dd-wrt ssid and then install the Kong .bin
5. Reboot and the world is good with new AC3500 in DD-WRT goodness.
You are in the right direction. I would also download the asus recovery tool. I found that if you need to flash the router from recovery mode, this tool does the trick. I have done 3 ac5300's and just recently an ac3200
I would definitely make sure you have a way to connect via wifi. All 3 of my ac5300's I was not able to connect to via lan until I got kongs fw on the router. _________________ Please Fix The Following Bugs:
EOIP Settings not applied automatically after FW upgrade or reboot. http://svn.dd-wrt.com/ticket/4061
The port 80 forwarding bug with out reapplying settings appears to have been fixxed.
You are in the right direction. I would also download the asus recovery tool. I found that if you need to flash the router from recovery mode, this tool does the trick. I have done 3 ac5300's and just recently an ac3200
I would definitely make sure you have a way to connect via wifi. All 3 of my ac5300's I was not able to connect to via lan until I got kongs fw on the router.
Done. I have the recovery tool downloaded. I also downloaded the ASUS FW 3.0.0.4.380.3341, just in case. I assume this is an OK version to load if I get into trouble? This is the version you mentioned in your post. The FW on my unit out of the box appears to be quite ancient. In fact, my current version doesn't even appear on the ASUS support site for download. I'm only asking as there was some mention on this site about a FW update that interfered with the ability to push DD-WRT onto the unit.
Do you happen to know the latest ASUS FW that is safe to use without blocking my path to a non-stock FW?
Once on DD-WRT, what is the best build number for this unit? Or is the development towards a stable/well performing build still ongoing?
Lastly, if I get in trouble and need to go the route of rescue utility, best to flash back to ASUS FW or load the DD-WRT .trx?
Anyway, thanks to the guys supporting DD-WRT on this router and to DUN4CHEAP for taking the time to read and respond.
On the ac3200 I put the dd-wrt.trx on it in recovery mode. I am running the newest betas without any issue. _________________ Please Fix The Following Bugs:
EOIP Settings not applied automatically after FW upgrade or reboot. http://svn.dd-wrt.com/ticket/4061
The port 80 forwarding bug with out reapplying settings appears to have been fixxed.
By the way, be sure to post your results when you are done.
Thanks, _________________ Please Fix The Following Bugs:
EOIP Settings not applied automatically after FW upgrade or reboot. http://svn.dd-wrt.com/ticket/4061
The port 80 forwarding bug with out reapplying settings appears to have been fixxed.
By the way, be sure to post your results when you are done.
Thanks,
Not good... loaded the ddwrt.trx via Asus webif and router never came back. I managed to get it into recovery mode but Asus recovery tool won't connect to force an Asus or ddwrt.try.
I put the IP of the PC into non-DHCP and assigned 192.168.1.10 but when I say upload the tool searches for a bit and then the router power light stops the slow flash and the tool times out at 30-sec saying 'router is not in recovery mode'
Any ideas? Pretty sad as this didn't seem that hard.
Turn it off. Hold the reset button it while turning it on. When the power led starts flashing, go to 192.168.1.1 in your browser and use the mini cfe to upload the asus firmware.
If it has a newer cfe, you may not be able to load dd-wrt onto it. _________________ I am far from a guru, I'm barely a novice.
Malachi is spot on, but i had better luck with the asus tool. Start it, start the upload firmware and do the reset that malachi posted. _________________ Please Fix The Following Bugs:
EOIP Settings not applied automatically after FW upgrade or reboot. http://svn.dd-wrt.com/ticket/4061
The port 80 forwarding bug with out reapplying settings appears to have been fixxed.
I managed to get it into recovery mode but Asus recovery tool won't connect to force an Asus or ddwrt.try.