Posted: Mon Aug 19, 2019 3:00 Post subject: Problem with 1900ac V2 build r40672 (won't accept flash)
Hi all,
I have a problem with the r40672 build for the WRT 1900ac V2. Struggling to get the router to accept the build I eventually hard bricked it.
I purchased a serial cable and ran the procedure to "run update_both_images" (with the factory firmware). I am assuming this updates both partitions?
Worked like a charm. Came back up on factory image just fine.
After it came up, I tried to flash the factory-to-ddwrt.bin again. This time I had the serial cable attached and logged the session.
The router tried to come-up on the newly flashed partition 3 times before reverting back to the first one.
Below is the kernal panic from the console. It panicked in the same place all three times. Again, this happened _after_ I had already successfully done "run update_both_images" and _then_ tried to flash to the factory-to-ddwrt.bin .
Is it possible that the factory-to-ddwrt.bin is trying to do some magic to ensure that it gets installed on partition 1 instead of partition 2? And, if this is the case, then is it possible this mechanism is not working?
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Aug 19, 2019 4:05 Post subject: Re: Problem with 1900ac V2 build r40672 (won't accept flash)
Surphr33k wrote:
Hi all,
I have a problem with the r40672 build for the WRT 1900ac V2. Struggling to get the router to accept the build I eventually hard bricked it.
I purchased a serial cable and ran the procedure to "run update_both_images" (with the factory firmware). I am assuming this updates both partitions?
Worked like a charm. Came back up on factory image just fine.
After it came up, I tried to flash the factory-to-ddwrt.bin again. This time I had the serial cable attached and logged the session.
The router tried to come-up on the newly flashed partition 3 times before reverting back to the first one.
Below is the kernal panic from the console. It panicked in the same place all three times. Again, this happened _after_ I had already successfully done "run update_both_images" and _then_ tried to flash to the factory-to-ddwrt.bin .
Is it possible that the factory-to-ddwrt.bin is trying to do some magic to ensure that it gets installed on partition 1 instead of partition 2? And, if this is the case, then is it possible this mechanism is not working?
Refer to the stikies at the top of the forum and various posts regarding newer builds.
Newer builds are too large to install on partition 2 for 1900's and 1200's.
You must force install to partition 1 on these newer builds.If you are going from stock it is best to first install a factory to dd-wrt build that is old (pre-2019) first then upgrade to the newer build first by forcing partition 1 install with the command "ubootenv set boot_part 2" then doing the upgrade.
There are other ways that work also and are explained in the stickies. _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
Joined: 30 May 2017 Posts: 582 Location: Rural Manitoba
Posted: Mon Aug 19, 2019 14:41 Post subject:
Surphr33k wrote:
Thanks @wened. Will I need to go back and redo the serial "run update_both_images" to repair partition 2 or is there an easier way?
It is my guess that partition 2 is likely in tact with stock firmware, so don't worry about it. You can upgrade via GUI by simply flashing "factory to dd-wrt" with an older build such as r35898 which will install on partition 2 (assuming you are on 1 now, although it doesn't matter).
Once updated to r35898 or so, don't enter any parameters just Administration->Command-> ubootenv set boot_part 2 Run Commands
Administration->Firmware Upgrade Select webflash file desired and execute.
This puts the desired build on partition 1
Unless the size of the new builds is decreased you will never be running on partition 2, it is just a failsafe if for some reason Partition 1 gets bricked. I have never had to serial any 1900, have done so with some other single partition routers _________________ Starlink & DSL -> TPLink TL-R470T+
->
WRT3200acm Master WDS 5GHz 80Mhz CH 100 (+6) r55819
Ath1 2.4Ghz Disabled
99 Static Leases
ExpressVPN
WRT3200acm r55819 WDS Station 5Ghz
Ath1 AP N/G Mixed Channel 11 HT40
WRT1900Ac V1 5Ghz r55819 WDS Station
(Defective, no 2.4Ghz but 5Ghz works great)
WRT1900AC V1 5Ghz AC 80Mhz WDS Station r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT1900ACS SPARE r54914
WRT1900AC SPARE r54914
WRT1900AC V1 5Ghz AC 80Mhz WDS-AP r55819
2.4Ghz AP Ch1 HT20 Mixed
WRT54G DD-WRT v3.0-r37305 micro AP CH 6 Mixed - Not in use
