OpenWrt Forum Archive

Topic: back to original/other firmware

The content of this topic has been archived on 23 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hello All,

I just discovered that switching from OpenWRT to dd-wrt is harder than I thought. Well, I found a couple of tutorials but my system (Linksys WRT1900ACS) does not have neither "linux" nor "firmware" MTDs. Only:

dev:    size   erasesize  name
mtd0: 00200000 00020000 "u-boot"
mtd1: 00040000 00020000 "u_env"
mtd2: 00040000 00020000 "s_env"
mtd3: 00100000 00020000 "devinfo"
mtd4: 02800000 00020000 "kernel1"
mtd5: 02200000 00020000 "rootfs1"
mtd6: 02800000 00020000 "kernel2"
mtd7: 02200000 00020000 "ubi"
mtd8: 02600000 00020000 "syscfg"
mtd9: 00680000 00020000 "unused_area"

Which one should I flash with "mtd -r write <...>"

If you have Luci installed you can just download the stock firmware from Linksys and then in Luci go to System > Backup/flash firmware and flash the stock firmware, then install whatever you want to from the stock firmware. If no Luci, just copy it to /tmp and then run sysupgrade from terminal

sysupgrade -n /tmp/linksys.stock.firmware.whatever

in LUCI I get the error "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform" when I try to flash with FW_WRT1900ACSV2_2.0.1.177097_prod.img

andriusi wrote:

in LUCI I get the error "The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform" when I try to flash with FW_WRT1900ACSV2_2.0.1.177097_prod.img

Edit - Before you try this, make sure you have the right firmware, in your original comment you say you have a WRT1900ACS, but the firmware you list in your second comment is for WRT1900ACS V2 (FW_WRT1900ACSV2_2.0.1.177097_prod.img)

Hmm, that sounds like the issue LEDE currently has, try running sysupgrade with the -F option to force it -


sysupgrade -n -F /tmp/linksys.stock.firmware.whatever

(Last edited by mikemccartney on 20 Dec 2016, 04:30)

Switching from openwrt to dd-wrt is pretty simple.

Don't use mtd but sysupgarde like @4mikemccartney2016 suggested.

1.) download the latest version of  dd-wrt for your WRT1900ACSv2 here: htttp://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2016/

Note: The link might be different, please check!
          An extra t has been added to the above link because linking is not allowed here. Just remove that extra t in htttp to get the correct link.

2.) use winscp to copy the file to /tmp
3.) you need to rename the file to change the file extension

mv /tmp/factory-to-ddwrt.bin /tmp/factory-to-ddwrt.trx

Note: It is important to download and use factory-to-ddwrt.bin and not ddwrt-linksys-wrt1900acsv2-webflash.bin

          ddwrt-linksys-wrt1900acsv2-webflash.bin should ONLY be flashed from GUI (Luci) interface

4.) run sysupgrade with -F option to force the upgrade process

sysupgarde -n -F -v /tmp/ddwrt-linksys-wrt1900acsv2-webflash.trx

Note: The options means:
         
           -n  ==> don't keep settings
           -v  ==> more verbose
           -F  ==> Force

5.) Reboot the router if not done automatically after the upgrade process has finished.

For future use, you can switch the firmware to which ever you want.
         
         Switch dd-wrt to openwrt
         --------------------------------
         First check which partition is booted with is command:
          ubootenv get boot_part

          If the result is part 1, change the partition with:
          ubootenv set boot_part 2 && reboot

          But if the part is 2, change the partition with
          ubootenv set boot_part 1 && reboot


         Switch openwrt to dd-wrt
         --------------------------------
         First check which partition is booted with is command:
          fw_printenv boot_part

          If the result is part 1, change the partition with:
          fw_setenv boot_part 2 && reboot

          But if the part is 2, change the partition with
          fw_setenv boot_part 1 && reboot

(Last edited by omostan on 27 Dec 2016, 23:37)

The discussion might have continued from here.