I only tried installing the factory-to-dwrt.img from the Linksys OEM firmware as the very name of the file suggests. I just assumed people would understand that is what was done.
MR7500 with R61848 installed on Linux2/mtd15.
I reset r61848 to factory defaults being issuing nvram erase && reboot. (Gremlin repellent.)
After reboot I changed the password & username.
I used the GUI to flash this file: https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2025/11-05-2025-r62540/linksys-mr7500/dd-wrt-webflash.bin
Router failed to boot three times and reverted to r61848.
I then followed these steps: CLI Flash: 'cd /tmp' then 'wget {file URL}' (http only) or 'curl -O {file URL}' (http, https, ftp) 'write {file} linux' then 'reboot'.
Router failed to boot three times and reverted to r61848.
Router failed to boot three times and reverted to the OEM firmware.
I repeated this three times, because have I have issues with the OEM not flashing correctly the first time. Still no boot.
End process.
I re-flashed r61848 using the OEM firmware.
I did that using a Windows 10 pro desktop at home with my FTTH ISP.
Next I switched to a Fedora laptop and completed the following using a different ISP to eliminate any possibility of download errors.
Yes, I compared checksums. They matched.
Begin process
MR7500 with R61848 installed on Linux2/mtd15.
I reset r61848 to factory defaults being issuing nvram erase && reboot. (Gremlin repellent.)
After reboot I changed the password & username.
I used the GUI to flash this file: https://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2025/11-05-2025-r62540/linksys-mr7500/dd-wrt-webflash.bin
Router failed to boot three times and reverted to r61848.
I then followed these steps: CLI Flash: 'cd /tmp' then 'wget {file URL}' (http only) or 'curl -O {file URL}' (http, https, ftp) 'write {file} linux' then 'reboot'.
Router failed to boot three times and reverted to r61848.
Router failed to boot three times and reverted to the OEM firmware.
I repeated this three times, because have I have issues with the OEM not flashing correctly the first time. Still no boot.
End process.
---------------------------------------------------------
Move forward to late Saturday night after my reply to KP.
---------------------------------------------------------
For this portion I used the Windows 10 desktop since the quirky TTL adapter I have is not compatible with Linux as per the manufacturer. That's probably why I got five of them for $12 on Amazon. I used Tftpd64 in windows for the file transfer.
I interrupted the boot process, by pressing any key, before the two seconds elapsed.
I used the following to flash the factory-ddwrt.img file to both partitions:
The router failed to boot three times, switched partitions, failed to boot three times and switched partitions again. This repeated until I interupted it.
Here is a snippet of the console log showing two bootups:
Code:
Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset), D - Delta, S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.XF.0.3-00098-IPQ60xxLZB-1
S - IMAGE_VARIANT_STRING=IPQ6018LA
S - OEM_IMAGE_VERSION_STRING=crm-ubuntu121
S - Boot Interface: NAND
S - Secure Boot: Off
S - Boot Config @ 0x000a602c = 0x000002e5
S - JTAG ID @ 0x000a607c = 0x001260e1
S - OEM ID @ 0x000a6080 = 0x00000000
S - Serial Number @ 0x000a4128 = 0x69d9d351
S - OEM Config Row 0 @ 0x000a4188 = 0x0000000000000000
S - OEM Config Row 1 @ 0x000a4190 = 0x0000000000000000
S - Feature Config Row 0 @ 0x000a4130 = 0x0000000008200001
S - Feature Config Row 1 @ 0x000a4138 = 0x02c3e80383000009
S - PBL Patch Ver: 1
S - I-cache: On
S - D-cache: On
B - 3413 - PBL, Start
B - 592 - bootable_media_detect_entry, Start
B - 4339 - bootable_media_detect_success, Start
B - 5207 - elf_loader_entry, Start
B - 5380 - auth_hash_seg_entry, Start
B - 7847 - auth_hash_seg_exit, Start
B - 8342 - elf_segs_hash_verify_entry, Start
B - 103699 - elf_segs_hash_verify_exit, Start
B - 107891 - auth_xbl_sec_hash_seg_entry, Start
B - 108035 - auth_xbl_sec_hash_seg_exit, Start
B - 114588 - xbl_sec_segs_hash_verify_entry, Start
B - 114589 - xbl_sec_segs_hash_verify_exit, Start
B - 115519 - PBL, End
B - 97447 - SBL1, Start
B - 237351 - GCC [RstStat:0x0, RstDbg:0x600000] WDog Stat : 0x4
B - 239791 - clock_init, Start
D - 3629 - clock_init, Delta
B - 249276 - boot_flash_init, Start
D - 26077 - boot_flash_init, Delta
B - 277733 - sbl1_ddr_set_default_params, Start
D - 244 - sbl1_ddr_set_default_params, Delta
B - 284351 - boot_config_data_table_init, Start
D - 4819 - boot_config_data_table_init, Delta - (575 Bytes)
B - 294355 - CDT Version:2,Platform ID:8,Major ID:3,Minor ID:0,Subtype:2
B - 299022 - Image Load, Start
D - 6618 - OEM_MISC Image Loaded, Delta - (0 Bytes)
B - 308355 - Image Load, Start
D - 5063 - PMIC Image Loaded, Delta - (0 Bytes)
B - 316254 - sbl1_ddr_set_params, Start
B - 321226 - CPR configuration: 0x366
B - 324428 - Pre_DDR_clock_init, Start
D - 213 - Pre_DDR_clock_init, Delta
D - 0 - sbl1_ddr_set_params, Delta
B - 359534 - Image Load, Start
D - 518 - APDP Image Loaded, Delta - (0 Bytes)
B - 378413 - Image Load, Start
D - 519 - QTI_MISC Image Loaded, Delta - (0 Bytes)
B - 380945 - Image Load, Start
D - 915 - Auth Metadata
D - 671 - Segments hash check
D - 23210 - QSEE Dev Config Image Loaded, Delta - (36490 Bytes)
B - 406107 - Image Load, Start
D - 6497 - Auth Metadata
D - 10339 - Segments hash check
D - 348463 - QSEE Image Loaded, Delta - (1436620 Bytes)
B - 755088 - Image Load, Start
D - 641 - Auth Metadata
D - 976 - Segments hash check
D - 35929 - RPM Image Loaded, Delta - (102800 Bytes)
B - 792664 - Image Load, Start
D - 701 - Auth Metadata
D - 3294 - Segments hash check
D - 131241 - APPSBL Image Loaded, Delta - (568944 Bytes)
B - 941382 - SBL1, End
D - 844332 - SBL1, Delta
S - Flash Throughput, 4000 KB/s (2145429 Bytes, 456022 us)
S - Core 0 Frequency, 800 MHz
S - DDR Frequency, 466 MHz
Regardless of how or what I have said R62540 still does not boot on the MR7500 in my possession.
Note: For those of you that haven't read my previous post. This is not that mutant MR7500-RM2.
However, I am not entirely satisfied I have eliminated the possibility of file corruption. I have SHA256 checksums, but nothing to compare them with.
Does this provide an adequate enough summation of my ineptitude?
Joined: 18 Mar 2014 Posts: 13883 Location: Netherlands
Posted: Sun Nov 09, 2025 15:20 Post subject:
Not wanting to discourage anyone but the Linksys MR series is not on my recommended list.
They do not have the real CPU/Soc but IPQ60XX and have "only" 512 MB RAM which is on the low end.
Also on Openwrt problems are reported for MR series.
Router/Version: Wa7510 v1
File/Kernel: tl-wa7510n-webflash 05-Nov-2025
Previous/Reset: tl-wa7510n-webflash 05-Nov-2025
Mode/Status: Ap/ gets stucked,its unusable
Issues/Errors: its been long time upgrade build fw,power led all time on, lan led fast blinks looks like is unusable
Router/Version: Linksys MR7350
File: dd-wrt-webupgrade.bin
Firmware: DD-WRT v3.0-r62540 std (11/05/25) (prev. DD-WRT v3.0-r62508 std (11/02/25))
Kernel: Linux 6.6.116-rt29 #4449 SMP Mon Nov 3 08:27:03 +07 2025 aarch64
Mode: Gateway, SFE disabled, 2.4G (20MHz mixed, WPA2 Personal, WPA3 Personal / SAE - CCMP-128 (AES)) and 5G (80MHz AX / AC / N Mixed, WPA3 Personal / SAE - CCMP-128 (AES)) wifi, bridged VAP on 2.4GHz, Wireguard for external access, WAN disabled, Keep Alive reboot 6:02 in the morning, using my own local NTP
Reset: No
Status: Installed at release.
No new entries in oops Partition.
Sometimes everything works after a reboot, sometimes some devices cannot connect on wireless.
If everything is fine it does not stay so. Roughly after 15-30 hours on wireless 2.4GHz or 5GHz or my VAPs sometimes IPv6 ceases to work, or IPv4 and IPv6.
Either rebooting solves this or a click on save & apply in GUI.
So I enabled keep alive reboot again.
Maybe I have to restart then (zero db issue) or devices connect again in an instant until internet ceases to work again on wireless.
*shrugs*
This MR7350 wasn't my best investment (also the MR7500 is sitting on the bench since a few months).
Maybe it is time to look for other AX capable DD-WRT routers and give those MR devices a rest for a few months.
Joined: 18 Mar 2014 Posts: 13883 Location: Netherlands
Posted: Tue Nov 11, 2025 13:25 Post subject:
Quote:
This MR7350 wasn't my best investment (also the MR7500 is sitting on the bench since a few months).
Maybe it is time to look for other AX capable DD-WRT routers and give those MR devices a rest for a few months.
Joined: 04 Dec 2007 Posts: 1252 Location: Murrysville, PA
Posted: Tue Nov 11, 2025 13:30 Post subject:
egc wrote:
Quote:
This MR7350 wasn't my best investment (also the MR7500 is sitting on the bench since a few months).
Maybe it is time to look for other AX capable DD-WRT routers and give those MR devices a rest for a few months.
One with the real IPQ807X Soc and at least 1 GB RAM
If you can spare the coin, the MX8500 has worked well for me. _________________ Linksys MX8500 DD-WRT v3.0-r62966 std (12/06/25)
Linux 6.6.118-rt29 #4715 SMP Sat Dec 6 10:22:51 +07 2025 aarch64 Gateway, AP, DNSMasq, SmartDNS, NSS-ECM-SFE, QCA NSS, no STP
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
Cloudflare DoH & DoT, No QoS, No Forced DoT, 802.11k
2.4GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
5GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
Netgear AX1800 WiFi Mesh Extender
Xfinity 1.2Gbps/40Mbps
@egc any recommendations? I'm eying the Dnyalink WRX36, but this has the 8072 chipset if not mistaken... . Also they are almost impossible to get anymore.
The very few reports I found here look promising, but... without recent tests who knows.
@MLandi unfortunately the MX8500 isnt available anymore.
MR7350 development looked promising, same for MR7500 and I'm sure those platforms will get their quirks ironed out. But for now I want at least one stable AX device while testing the MR series.
Tired of messages not reaching me, devices yelling for internet while connected or missed VoIP calls.
Joined: 04 Dec 2007 Posts: 1252 Location: Murrysville, PA
Posted: Tue Nov 11, 2025 15:58 Post subject:
Zyxx wrote:
@egc any recommendations? I'm eying the Dnyalink WRX36, but this has the 8072 chipset if not mistaken... . Also they are almost impossible to get anymore.
The very few reports I found here look promising, but... without recent tests who knows.
@MLandi unfortunately the MX8500 isnt available anymore.
It certainly is from Amazon. I just added it to my cart, all I would need to do is hit "Place your order". It would arrive in two days.
Edit: BLASTED AMAZON! They did the old bait and switch! I tried to open the product I bought a month ago and they switched it for the AX4200. I wish I could trust searching on Amazon. Sorry about that _________________ Linksys MX8500 DD-WRT v3.0-r62966 std (12/06/25)
Linux 6.6.118-rt29 #4715 SMP Sat Dec 6 10:22:51 +07 2025 aarch64 Gateway, AP, DNSMasq, SmartDNS, NSS-ECM-SFE, QCA NSS, no STP
VAP on wlan1 for internet devices
IPv4 & IPv6 (Prefix Delegation)
Static Leases & DHCP
Cloudflare DoH & DoT, No QoS, No Forced DoT, 802.11k
2.4GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
5GHz: AP, AX Only, ACK Timing 300, WPA2 & WPA3 w/AES & GCMP
Netgear AX1800 WiFi Mesh Extender
Xfinity 1.2Gbps/40Mbps
Joined: 18 Mar 2014 Posts: 13883 Location: Netherlands
Posted: Tue Nov 11, 2025 16:09 Post subject:
Zyxx wrote:
@egc any recommendations? I'm eying the Dnyalink WRX36, but this has the 8072 chipset if not mistaken... . Also they are almost impossible to get anymore.
The very few reports I found here look promising, but... without recent tests who knows.
@MLandi unfortunately the MX8500 isnt available anymore.
MR7350 development looked promising, same for MR7500 and I'm sure those platforms will get their quirks ironed out. But for now I want at least one stable AX device while testing the MR series.
Tired of messages not reaching me, devices yelling for internet while connected or missed VoIP calls.
In the syslog. Is the 24-hour WAN IP from the ISP settings? If so, you may have to adjust your NTP interval to less or more than 24 hours. There is also the process_monitor and check_ps functions in DD-WRT that should alleviate the issue, but this seems like it stops everything. I thought BS had changed the way dnsmasq operated at boot to alleviate the problem...
Thanks panic and duh on me...I've been skimming for other things so much I probably locked it out of my radar. I'll followup on the others and see what happens and yeah, this version I'm not certain it isnt resolved yet and unfortunately as we approached the 48 hours, ISP did maintenance that took everything down for almost a day so will have to wait another 2 day cycle to see if it might be resolved.
Also from the other thread about this i will just copy what I confirmed there a couple days ago
Quote:
ALSO I confirmed that when this happens the router and internal network is fine as far as contact and talk between devices. Just lost the connection out and it turns out in to the network.
it does happen regardless of WAN ip time, meaning whatever the refresh is from the internet provider and unfortunately, that you cannot contact the router remotely, at least via ssh or telnet from the internet. So essentially it loses its wan connection even though it says it still has it, which is I guess why the router doesnt have any log entries related.
I currently dont run any watchdog type stuff on the router, though i do end up knowing within a short window when it has lost connection because other devices like switchbot and such notify me from their servers that they have lost contact. See the 11/5 build thread for more info on that.
I will change the ntp settings and a few others to test out and post what i find.
.
