I have the same problem but I have a wrt1200AC. Can you tell me how you unbricked it? TFTP does not work either. Router wired and wireless works but I cannot do anything in the gui.
Posted: Mon Jul 01, 2019 19:07 Post subject: Got it working!
I was inpatient but the turning it off and on several times instructions that Justanotherbrokenrouter gave worked for me eventually. I was not sure it would on my wrt1200AC. Thanks!
Glad you got it to go, told you just keep at it, took me a bit to get mine flipped from that as well, Just keep at it people it will flip patitions..... _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Well, I didn't know that the build is broken, so I've updated my WRT32x. Now the router is performing well, but the web interface looks like isn't loading properly.
What are my options now? Should I wait for the next build and try to upgrade?
I've also tried to revert to an older firmware, but nothing happens when I hit the "Upgrade" button. _________________ Linksys WRT32X - DD-WRT v3.0-r50551 std (10/19/22)
Linksys EA6300 - DD-WRT v3.0-r40167 (backup router if something goes wrong with the main one)
Manually switch the router from primary to alternate partition or vice versa [backup] partition:
Power off router with power switch.
Turn power back on and Power LED will light.
As soon as all LEDs turn off (~2s), power off router with power switch
Turn power back on and Power LED will light.
As soon as all LEDs turn off (~2s), power off router with power switch
Turn power back on and Power LED will light.
As soon as all LEDs turn off (~2s), power off router with power switch
Turn power back on and allow router to fully boot.
It should now be booted to the alternate firmware partition
T-z3P wrote:
Well, I didn't know that the build is broken, so I've updated my WRT32x. Now the router is performing well, but the web interface looks like isn't loading properly.
What are my options now? Should I wait for the next build and try to upgrade?
I've also tried to revert to an older firmware, but nothing happens when I hit the "Upgrade" button.
_________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Manually switch the router from primary to alternate partition or vice versa [backup] partition:
Power off router with power switch.
Turn power back on and Power LED will light.
As soon as all LEDs turn off (~2s), power off router with power switch
Turn power back on and Power LED will light.
As soon as all LEDs turn off (~2s), power off router with power switch
Turn power back on and Power LED will light.
As soon as all LEDs turn off (~2s), power off router with power switch
Turn power back on and allow router to fully boot.
It should now be booted to the alternate firmware partition
Thank you for the answer, I've already read the solution you provided in a previous post, but I want to keep the main partition intact. That would be my last resort, if nothing else works. I've also forgot to mention that I can access SSH on the affected router. Is there a way to push an older version from terminal? _________________ Linksys WRT32X - DD-WRT v3.0-r50551 std (10/19/22)
Linksys EA6300 - DD-WRT v3.0-r40167 (backup router if something goes wrong with the main one)
Ok, so I've managed to return the router into a working state. I will detail the steps below:
1. SSH into router
2. cd /tmp
3. Download firmware with wget ftp://ftp.dd-wrt.com/betas/2019/06-27-2019-r40134/linksys-wrt32x/ddwrt-linksys-wrt32x-webflash.bin
4. Check what partition is in use with ubootenv get boot_part (on the 3rd line it will return 1 or 2) and change it if needed with ubootenv set boot_part 1 or 2 (mine was already set to 1, as the default firmware is still on partition 2)
5. Flash firmware with write ddwrt-linksys-wrt32x-webflash.bin linux (if your partition is set to 2, use linux2)
6. Wait to complete and then reboot
PS: The above instructions were followed on WRT32x. I'm not sure if it will work on other routers.
PS2: If you are not able to SSH into router, you can get a USB to TTL cable and follow the steps in this video https://www.youtube.com/watch?v=PZYXKAkuJ5w _________________ Linksys WRT32X - DD-WRT v3.0-r50551 std (10/19/22)
Linksys EA6300 - DD-WRT v3.0-r40167 (backup router if something goes wrong with the main one)
So far, on R40134, I've not experienced any of the issues that others have described with these latest builds. Then again, my setup is very straightforward: no VPN, WiFi on each interface, and a virtual WiFi for guests.
My escape plan, should I need one, is:
Flash to R36154 that worked quite well (including the automatic reboot), letting it reset.
After reboot, restore from the settings file I'd previously saved from that release.
I blew away the stock firmware quite some time ago, so I'm okay with overwriting the opposite partition.
Does this all make sense? Thanks! _________________ Router: Linksys WRT1900ACSv2
Modem: Verizon Fios DD-WRT v3.0-r44048 std (08/02/20)
ISP: Verizon Fios
NAS: ReadyNas314
Joined: 04 Aug 2012 Posts: 612 Location: behind the screen
Posted: Wed Jul 03, 2019 19:37 Post subject:
Be carefull with these builds, u should know how to recover if you want to test these images. _________________ WRT3200ACM openwrt 18.06.5
WRT3200ACM dd-wrt r41791
WRT54GL dd-wrt r21676
i agree, unless your checking the forums first looking for any mishaps, make sure you can use a usb to ttl serial cable to recover and already have the other necessary tools already in place to recover the firmware. _________________ Downloads:
ftp site: ftp://ftp.dd-wrt.com/betas/2021 SVN Timeline:
https://svn.dd-wrt.com/timeline Commands: Misc: sleep 10;stopservice nas;stopservice wlconf;startservice wlconf;startservice nas
samba: { sleep 30; stopservice samba3; startservice samba3; } &
WRT1900ACv1: WIFI: 2.4ghz: NG-mixed, 20mhz channel width, channel follows AP, WPA2-CCMP-128.
WIFI: 5ghz: AC/N mixed, 40mhz channel width, channel 100+upper, WPA2-CCMP-128.
Misc Info: WPA2 Personal: "CCMP-128 (AES)" Static IP's VIA Mac+Host, SFE Enabled, No Rebind, Strict, no-resolv. NOTE: this is now just a wireless access point so to speak but all settings still apply to what ever wireless person connects.
Dr. Frankenstein: [Holds up hand] Ah. Good. Uh... would you mind telling me... whose brain... I did put in?
Igor: And you won't be angry?
Dr. Frankenstein: I will not be angry.
Igor: [Shrugs] Abby...someone.
Dr. Frankenstein: Abby someone? Abby who?
Igor: Abby Normal.
Dr. Frankenstein: [takes a deep breath] Abby Normal?
Igor: I'm almost sure that was the name. [He and Dr. Frankenstein laugh]
Dr. Frankenstein: Are you saying... [Stands] that I put an abnormal brain... [Puts hand on Igor's hump] into a 7 and a half foot long... 54- inch wide... [Grabs Igor by throat] GORILLA?!?!?! [Strangling Igor] IS THAT WHAT YOU'RE TELLING ME!?!
Posted: Thu Oct 31, 2019 21:07 Post subject: R40167....I need some review and assistance please!!!
A few months ago I had updated 2 of my WRT1900AC routers with this bad build (R40167). Upon doing some research I found data that walked me thru re-flashing to a baseline linksys build with hope of another re-flash to a good DDWRT build for my routers.
Upon removing the shell to my router, I inserted the the TTL Serial cables to the router as follows
(L>R) Black #1, White #2 & Green #4)
Red- Don't Use
Black-Ground
White-RX
Green-TX
Step 1- I went to https://www.linksys.com/us/support-article?articleNum=148550 to obtain an .img file for flashing my router back to a stock firmware. Upon download, I changed the name and placed it in a newly created FTP folder on the root of the C:drive.
Step 2 – Plugged the TTL USB into Laptop & plugged Cat5 cable into port 1 of router as was as Cat5 cable into laptop NIC card (while router is power off).
Step 3 – Changed laptop IPv4 properties to the following
IP address: 192.168.1.2
Subnet mask: 255.255.255.0
Default Gate: 192.168.1.1
Step 4 – Opened TFTPd application on laptop and modified settings for directory of .img file and set the server interface.
Step 5 – Verified Comm port and set Putty accordingly.
Set speed to 115200 and modified Serial line
Step 6 - Turn on router and hit the space bar on keyboard to stop auto-boot when it prompts in Putty terminal.
Step 7 – Within Putty terminal, type in separately the following command followed by hitting the return key. This will set the IP address of the the client, server, name of the img file and tell Putty to reformat both partitions on the router.
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.2
setenv firmwareName linksys.img
run update_both_images
this should be the end result
Step 8 – Put iPV4 back to DHCP config
Step 9 – in Putty type the word reset and hit enter. The router will reboot. When it comes back Putty should say something about Linksys.
In my case after multiple attemps to flash, I get a Wrong Image Format for bootm command, ERROR: can’t get kernel image!
Here is a copy of all text within my putty shell. Does anyone see what went wrong with the flash? Also, within the terminal there is a reference to Filename “blk-mamba.128mb.img”. What is that referencing?
setenv ipaddr 192.168.1.1
setenv serverip 192.168.1.2
setenv firmwareName linksys.img
run update_both_images
*******************************
reset
***************************************
egiga0 [PRIME], egiga1
modify Phy Status
Saving Environment to NAND...
Erasing Nand...
Writing to Nand... done
#### auto_recovery:2 ####
auto_recovery_check changes bootcmd: run altnandboot
Hit any key to stop autoboot: 0
Marvell>> setenv ipaddr 192.168.1.1
Marvell>> setenv serverip 192.168.1.2
Marvell>> setenv firmwareName linksys.img
Marvell>> run update_both_images
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'blk-mamba.128mb.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
NAND erase: device 0 offset 0xa00000, size 0x4000000
Erasing at 0x49e0000 -- 100% complete.
OK
NAND write: device 0 offset 0xa00000, size 0x1e00000
31457280 bytes written: OK
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'blk-mamba.128mb.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
NAND erase: device 0 offset 0x3200000, size 0x4000000
Erasing at 0x71e0000 -- 100% complete.
OK
NAND: Spansion 1Gb(ID=F101) 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000007ea0000
#### auto_recovery ####
[u_env] get auto_recovery == yes
[u_env] get auto_recovery == yes
[u_env] get boot_part == 2
[u_env] get boot_part_ready == 3
auto_recovery enabled:1, boot_part:2, boot_part_ready:3
PEX 0.0(0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Root Complex Interface, Detected Link X1, GEN 1.1
PEX 0.2(2): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.3(3): Detected No Link.
PEX 1.0(4): Detected No Link.
PEX 1.1(5): Detected No Link.
PEX 1.2(6): Detected No Link.
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:
mvEthE6171SwitchBasicInit finished
Net: mvSysNetaInit enter
set port 0 to rgmii enter
set port 1 to rgmii enter
egiga0 [PRIME], egiga1
modify Phy Status
auto_recovery_check changes bootcmd: run altnandboot
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x3200000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>>