Posted: Mon Nov 18, 2024 6:52 Post subject: RESOLVED - Unable to install 58627 on WRT1900AC v1
I have a WRT1900AC v1 with Linksys OEM F/W (Ver 1.1.10.187766) on partition #1 and I am trying to install r58627 onto Partition two. So far what I am running into is the Linksys OEM F/W is the only firmware that will correctly install on partition 1. The only versions of DD-WRT that I can install on partition #2 from the GUI is r53633 or earlier using the factory-to-ddwrt.bin files which are smaller than the webflash version. I am not able to successfully upgrade from the GUI using any webflash version of ddwrt.
Note - Yes I can flash & boot the OEM F/W on both partitions without any issues.
So I popped open the case and used the serial recovery to flash the firmware.
I soon discovered that I can flash anything I want to Partition #1, but the only firmware that will successfully boot and configure itself is the OEM F/W. Regardless of the ddwrt build the kernel will load but it fails to configure three times then switches partitions.
I have attached three log files captured from the serial console.
1 - factory-to-ddwrt-r53633.bin flashed to partition #1
2 - factory-to-ddwrt-r58627.bin flashed to partition #1
3 - Successful flash & boot of factory-to-ddwrt-r58627.bin flashed to partition #2
Joined: 30 May 2017 Posts: 602 Location: Rural Manitoba
Posted: Mon Nov 18, 2024 12:25 Post subject:
It sounds like you are having the problem which is well documented where when upgrading a WRT1900 from stock firmware. You must do it in two stages, this has been documented many times on the forum, first upgrade factory to DD-WRT with an old release (ie. r35898) then upgrade to whatever release you desire. As you can see from profile I run multiple WRT1900's and at the most current version. I am sure if you follow the multiple upgrade steps you will not have any problems. _________________ Starlink & DSL ->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) -r63200
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm -r63200 WDS-5Ghz Client
WRT3200acm-r61465 Spare
WRT3200acm-r62170 Spare
WRT1900Ac V1 5Ghz -r62540 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 -r62540 WDS Station
WRT1900AC SPARE r60942
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP- - -r62540 2.4Ghz AP Ch1 HT20 Mixed
I have four of these devices, two of them have the same issue, and the other two do not. I am not changing anything on the second two until I pinpoint what corrupted the first two.
Yes, I have been using the process quoted below to upgrade since R33555.
Quote:
Trick to Upgrade DD-WRT Firmware without losing current configuration or the need to return to Stock Firmware:
Using Telnet/SSH and the ubootenv set boot_part command (described below) it is possible to upgrade to a newer version of DD-WRT without the need to manually switch back to Stock Firmware Partition. All previously configured settings will remain intact.
1. Use the ubootenv get boot_part command to learn the current Partition in use.
2. Use the ubootenv set boot_part (1 or 2 – the opposite number returned in Step 1) command.
3. DO NOT REBOOT
4. In DD-WRT GUI – Administration Tab – Firmware Upgrade Sub Tab: Upload the new ’dd-wrt webflash.bin’ file for your Router & Hardware Version. MAKE SURE THAT NO RESET IS SELECTED.
5. After Firmware Upgrade is finished the Router will automatically reboot.
*You should now have the new DD-WRT upgrade on the current Partition and OEM Firmware will still be intact on opposite partition.
The preceding was provided by an unknown author on this Forum. Whomever you are, thank you! Also, thank you to @myersw for saving & providing a copy and to @gainestr for testing.
Thankfully it is nowhere near as convoluted as the peacock thread; however, it's quite simple to execute.
The first-time flash portion of the cliff notes instructs you to install the crippled version of DD-WRT using factory-to-ddwrt.bin file.(No USB, VPN, NAS, AdBlocking, or SpeedChecker, etc.) Then use the compact version to upgrade to the complete version you desire. Even an alcoholic logger(aka My brother-in-law) could figure that out.
The above process used to work in the GUI, CLI via SSH or telnet.
First of all these devices are suppose to flash firmware in round-robin style. You install to the opposite partition, if it fails it falls back to the partition you started from. For some reason these two devices no longer funtion this way. WHY?
I found a thread on another site discussing how the parent company of Link-sys modified the last version of the OEM F/W to resrict partition #1 to OEM F/W only.
Basically you should not allow the OEM firmware to update itself to version 1.1.10.187766 (FW_WRT1900AC_1.1.10.187766_prod.img)
I tried resetting the u-boot environment with:
Code:
env default -f
saveenv
reset
No change. It seems they modified the bootloader itself.
Maybe I should be asking a different question?
How do I extract the original bootloader/nand environment of another WRT1900ACv1 then restore it to the two corrupted devices?
Joined: 08 May 2018 Posts: 16697 Location: Texas, USA
Posted: Thu Nov 21, 2024 4:27 Post subject:
All you should have to do is flash the factory-to-ddwrt.bin from the last 2017 / first 2018 build and then upgrade to a current release (twice if you want to keep them on the same or one behind current) and go from there. Reset required after flashing a current release due to NVRAM variable name changes, etc. I haven't noticed the round-robin flashing being broken on Marvell, at least not on my 3200. /shrug _________________ "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... RSS feed for DD-WRT releases (2025) RSS feed for DD-WRT releases (2024) RSS feed for DD-WRT releases (2023)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
That's the whole problem I was having. I could not flash anything onto partition #1 other than the OEM F/W version 1.1.8.161917, even from the bootloader. Once that version was booted I could flash the abbreviated/crippled factory-to-ddwrt versions, r53133 or earlier from the OEM GUI.
Note: OEM F/W Version 1.1.8.161917 was the release version & included on the cd-rom that came with the new device.
Now I was trying to use the method describe in the cliff notes to retain the current config by changing the boot_part then flashing over the top of partition #2. However, every time I did this both partitions would get wiped out. Forcing me to use the serial recovery. Using the bootloader I could flash ANY factory-to-ddwrt version onto alt_image I choose without issue. You could not use the GUI or CLI to upgrade the partition without corrupting both. I could not upgrade any version without using the serial recovery which is not exactly a convenient method. That was the problem I wanted to correct.
What I found was the latest version of the OEM F/W, version 1.1.10.187766, has been modified to include an updated bootloader that deliberately interferes with third party firmware installation. I didn't bother to research the exact mechanism. I just wanted it gone.
I found the bootloader in the unaffected devices was different. I got some help from co-workers using equipment at work to extract the bootloader from one of those devices then managed to overwrite the modified devices. In simplest overview we copied then entire nand device of the target firmware then pasted it onto the nand device with the unwanted firmware. We cloned it. Then modified the MAC stored in the NAND environment to match the original MAC.
Problem solved. Now I can flash what ever I want to either partition without issue just as if it was brand new. I will not be installing the OEM F/W ever again.
Over at OpenWRT there is a thread about recovering the bootloader, but that bootloader is the new modified version that I don't want. That process just brought me full circle back to the exact same problem I started with.
It took a lot of searching & reading. Just not in this forum. This problem provided a much needed distraction for myself & co-workers. Now back to finish prepping for the change out of 300+ enterprise access points over the upcoming four day holiday weekend.
