Posted: Sun Sep 15, 2024 18:19 Post subject: [SOLVED] WRT1900AC with r58381 - won't install
Hello,
I decided to recycle my old WRT1900AC to a wireless repeater bridge and while at it, flash it with DDWRT. Here's the steps I made:
1- Reinit the router with factory default
2- Charge the factory-ro-ddwrt.bin - it works but it stayed in Linksys webUI (?)
3- Charge the lastest ddwrt-linksys-wrt1900ac-webflash.bin
4- Now I can't access the webUI anymore (192.168.1.1)
5- When I ping the router, I got PING: transmit-failed. General failure.
6- The power led is flashing
At this point, I guess I made an error. I tried reset button for 30 secs to no avail. Before doing a 30/30/30, I think it's best that I ask here for help first, perhaps all it's not lost yet.
I guess Murphy was looking at me, I should have stayed outside on the sun
Thanks for your help!
Last edited by MercadorHG on Sun Sep 15, 2024 19:53; edited 2 times in total
After you flashed factory2ddwrt and it came back with a Linksys WebUI, that should have been your first clue that something went wrong. Then flashing the webupgrade didn't do you any favors either.
This appears to be a dual partition router. You can try to force boot it from the other partition by toggling the power switch 3 times every 3 seconds or so. On the forth attempt, it should boot from the alternate partition.
Other than that, I'd guess it's time to open it up and get a serial port connected to it.
Another handy link:
https://openwrt.org/toh/linksys/wrt_ac_series#reset _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r58662
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk - r58662
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r58662
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r58662
- Linksys MR7350: Testing r58662
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 39, 9 RPis (2,3,4,5), 20 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
I was able to get Linksys back with the power on/power off three times.
I reread everything in English (I followed a French guide that might be outdated), I will try again factory-to-ddwrt. What should happens at that time, reloading to DDWRT webUI I guess?
I tried only "factory-to-ddwrt.bin" and after the flash was done, I was get back to Linksys WebUI so obviously, there's something amiss. I won't resend the other bin file this time though.
Not too sure what I do wrong.
When I push the factory2ddrwt, it told me that's not a recognized file (obviously, it's not a Linksys file) but it allow me to upgrade nonetheless.
Then webupgrade to current release. This has been discussed numerous times in the forum (web search would've probably revealed). Guess I still need to revisit the Wiki and give it some attention _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Then webupgrade to current release. This has been discussed numerous times in the forum (web search would've probably revealed). Guess I still need to revisit the Wiki and give it some attention
I used the 2018 file and now I got the "Redémarrage du routeur" but it doesn't refresh after 5+ minutes. So I guess it's now fine to click "Ok" and it would go DDWRT webUI. I'll cross my fingers.
This doesn't work, I have to reset to go back to default 2018 release of DDWRT. Should I indicate this in the build thread? Or perhaps my other partition is messed up and I can't upgrade to the new version. Or I shouldn't opt in for Reset after flashing.
Joined: 08 May 2018 Posts: 15233 Location: Texas, USA
Posted: Sun Sep 15, 2024 22:12 Post subject:
You'll have to boot into DD-WRT and figure out which boot partition you are on and then upgrade via CLI, then. It should flash via webUI. SSH/Telnet into the router and:
Code:
ubootenv get boot_part
If 1, then:
Code:
cd /tmp
wget http://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2024/09-13-2024-r58381/linksys-wrt1900ac/ddwrt-linksys-wrt1900ac-webflash.bin
write ddwrt-linksys-wrt1900ac-webflash.bin linux2
If 2, then:
Code:
cd /tmp
wget http://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2024/09-13-2024-r58381/linksys-wrt1900ac/ddwrt-linksys-wrt1900ac-webflash.bin
write ddwrt-linksys-wrt1900ac-webflash.bin linux
Joined: 30 May 2017 Posts: 588 Location: Rural Manitoba
Posted: Mon Sep 16, 2024 3:39 Post subject:
I noticed the problems you have getting and glad that the fine people here helped you out. I am not sure if you managed to setup WDS but I assure you that it does work extremely well. You can see by my profile that I use it extensively and have been for a few years. The only catch is that both routers in a wds configuration must be of the same breed (i.e. Marvel). Also I use the 5ghz for my WDS links and do not try to repeat the 5ghz. Only the 2.4ghz is used on the slave. I have tried to repeat the 5ghz and although I did get it working as long as I use channel 100, even at that is was shaky. One thing of note is that the 5ghz masters (I use two) do not negate any 5ghz devices as they connect as if it were just a regular AP. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) -r58785
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r56941 Spare
WRT1900Ac V1 5Ghz -r58785 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station -r58785
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS -r58785 WDS Station
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP ----r58785
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Unfortunately, my "recent" router is an Asus RT86-Pro so I don't know which kind of chipset there's in. However, I have an old WRT54G on DDWRT, it could be enough to broadcast 2.4ghz, I'll try that route next weekend.
kernel-panic69: thank you! It seems running fine now, it's just not up-to-date. I guess when I try to update with the webflash, it tries to update a messed up partition so I should try to push back Linksys default stock software to the other partition, I read it's round-robin so I don't have to decide which one is which.
