Following the instructions above about flashing it to DD-WRT, how does it know what partition to flash it on? For first time flashing, how does it know to flash it to the non-stock partition? Or is it just lucky that it doesn't flash to the stock partition? Or do both partitions have factory stock FW on them from the getgo and that is why it doesn't matter the first time?
It flashes to the partition that you are not on at the time.
You may want to stick with linksys firmware. _________________ I am far from a guru, I'm barely a novice.
Posted: Thu Mar 23, 2017 18:57 Post subject: Upgrading Firmware
I had a question about updating the firmware. Last year i first time install v3.0-r30880M kongmv, since then i haven't had many issues except for the Samba occasionally stopping. Not a big deal but when away from home, and im not able to access my Nas drive gets annoying. So i was wondering if the latest Kong version has had this issue fixed? And if so what would be the best way of upgrading it? Is it better to just return to stock and reflash a new version or to upgrade it (bin)?
In my opinion(for what its worth), it is safer and better to telnet in and reboot into the linksys partition. Then flash full 3rd party software image from the Linksys gui. if you are running a 3rd party software and use their upgrade process, you overwrite the Linksys image. _________________ My "WRT" rant, and why I have gone ddwrt on x86, no more consumer routers. ( ac86u as access points & bridges )
Oh ok, that's what ai figured, i tend to always double check with other just in case. Does it make a difference to reset to factory for the dd-wrt before booting back to stock and reflashing?
Also i was curious to know what the best method to finding out the most stable or best choice of version to choose from? Since there are 3 sources now? and a ton of different updates i'm unable to find any update info on.
i dont reset. All my settings stay. When i boot back into Linksys, my settings are there. When i flash ddwrt from Linksys gui, ddwrt boots with all my settings, including all my custom rules etc.
almost 24hr on the new ddwrt image _________________ My "WRT" rant, and why I have gone ddwrt on x86, no more consumer routers. ( ac86u as access points & bridges )
I'm currently on stock firmware and want to try a specific BS build, but all of his latest builds include 2 files.
ddwrt-linksys-wrt1900ac-webflash.bin
factory-to-ddwrt.bin
We can't go from linksys to ddwrt from a .bin though. Very confused. I don't want to brick. I don't have a jtag cable.
Joined: 14 Dec 2015 Posts: 774 Location: 127.0.0.1
Posted: Fri Mar 31, 2017 7:02 Post subject:
crimghost wrote:
I'm currently on stock firmware and want to try a specific BS build, but all of his latest builds include 2 files.
ddwrt-linksys-wrt1900ac-webflash.bin
factory-to-ddwrt.bin
We can't go from linksys to ddwrt from a .bin though. Very confused. I don't want to brick. I don't have a jtag cable.
He changed that a while ago, you can rename the factory.bin to .img if you want to.
The factory.bin works fine going through the Linksys update, it will complain it's not a recognized file or something like that.
You probably already know the webflash.bin is for flashing within DD-WRT, which would overwrite the Linksys partition. _________________ Tutorial for flashing WRT series WRT Installation,Upgrade & Basic Setup–Cliff Notes
r52242: WRT3200ACM, WRT1200ACv1 & 1 Velop in bridge mode(IoT subnet), r52242 WRT1900ACv1 AP
Velop:2 WHW0101, RE6500, RE9000(AP)
Spectrum - 1000/50
SysLog Watcher 5, New security Onion box coming soon, Fingboxes, PiHoles, NEMS, Cacti, rpisurv
I'm currently on stock firmware and want to try a specific BS build, but all of his latest builds include 2 files.
ddwrt-linksys-wrt1900ac-webflash.bin
factory-to-ddwrt.bin
We can't go from linksys to ddwrt from a .bin though. Very confused. I don't want to brick. I don't have a jtag cable.
He changed that a while ago, you can rename the factory.bin to .img if you want to.
The factory.bin works fine going through the Linksys update, it will complain it's not a recognized file or something like that.
You probably already know the webflash.bin is for flashing within DD-WRT, which would overwrite the Linksys partition.
I thought the webflash.bin was for updating DD-WRT rather than flashing the other partition?
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Tue Apr 04, 2017 14:02 Post subject:
MystaMagoo wrote:
ATHF wrote:
crimghost wrote:
I'm currently on stock firmware and want to try a specific BS build, but all of his latest builds include 2 files.
ddwrt-linksys-wrt1900ac-webflash.bin
factory-to-ddwrt.bin
We can't go from linksys to ddwrt from a .bin though. Very confused. I don't want to brick. I don't have a jtag cable.
He changed that a while ago, you can rename the factory.bin to .img if you want to.
The factory.bin works fine going through the Linksys update, it will complain it's not a recognized file or something like that.
You probably already know the webflash.bin is for flashing within DD-WRT, which would overwrite the Linksys partition.
I thought the webflash.bin was for updating DD-WRT rather than flashing the other partition?
You are correct that the webflash.bin is used for updates. Updates are done within the DD-WRT UI. Now the important to know if you do not already.
The WRT's have 2 partitions. When you flash new firmware the inactive partition is where the new flash goes not to the currently active partition. Simple rule, flash always goes to the inactive partition whether new install or update. This is a safety feature so that if there is a bad flash you can get back to a good flash.
This thread has explained a lot about how to boot into the inactive partition. But, once I've booted into the second, stock firmware, partition how do i boot back into DD-WRT? I'm not that familiar with the stock firmware, so is there a command window or would I telnet into the router?
Under troubleshooting there is an option to restore previous firmware.
That will boot into the other partition. _________________ I am far from a guru, I'm barely a novice.
