Bricked my Dynalink DL-WRX36, what did I do wrong?

[joshmcorreia]

I just bought a Dynalink DL-WRX36 and I managed to brick mine during part 2 of the install. Does anyone see what I did wrong, if anything? It's not serving a default gateway and I can't SSH into it anymore. From what I can tell I followed the wiki install instructions correctly.

Part 1:

$ ssh admin@192.168.216.1 -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa
admin@DL-WRX36:~# fw_setenv bootcmd 'usb start && fatload usb 0:1 0x44000000 openwrt-23.05.3-ipq807x-generic-dynalink_dl-wrx36-initramfs-uImage.itb && bootm 0x44000000; bootipq'
admin@DL-WRX36:~# reboot

Part 2:

$ scp openwrt-23.05.3-ipq807x-generic-dynalink_dl-wrx36-squashfs-factory.ubi root@192.168.1.1:/tmp/factory_image.ubi
$ ssh root@192.168.1.1
root@192.168.1.1's password: 

BusyBox v1.36.1 (2024-03-22 22:09:42 UTC) built-in shell (ash)

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.3, r23809-234f1a2efa
 -----------------------------------------------------
root@OpenWrt:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "0:sbl1"
mtd1: 00100000 00020000 "0:mibib"
mtd2: 00080000 00020000 "0:bootconfig"
mtd3: 00080000 00020000 "0:bootconfig1"
mtd4: 00300000 00020000 "0:qsee"
mtd5: 00300000 00020000 "0:qsee_1"
mtd6: 00080000 00020000 "0:devcfg"
mtd7: 00080000 00020000 "0:devcfg_1"
mtd8: 00080000 00020000 "0:apdp"
mtd9: 00080000 00020000 "0:apdp_1"
mtd10: 00080000 00020000 "0:rpm"
mtd11: 00080000 00020000 "0:rpm_1"
mtd12: 00080000 00020000 "0:cdt"
mtd13: 00080000 00020000 "0:cdt_1"
mtd14: 00080000 00020000 "0:appsblenv"
mtd15: 00100000 00020000 "0:appsbl"
mtd16: 00100000 00020000 "0:appsbl_1"
mtd17: 00080000 00020000 "0:art"
mtd18: 06100000 00020000 "rootfs"
mtd19: 00900000 00020000 "0:wififw"
mtd20: 06100000 00020000 "rootfs_1"
mtd21: 00900000 00020000 "0:wififw_1"
mtd22: 01600000 00020000 "ubifs"
mtd23: 00080000 00020000 "0:ethphyfw"
mtd24: 00280000 00020000 "certificate"
root@OpenWrt:/tmp# ubiformat /dev/mtd18 -y -f /tmp/factory_image.ubi
ubiformat: mtd18 (nand), size 101711872 bytes (97.0 MiB), 776 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 775 -- 100 % complete  
ubiformat: 776 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 96 -- 100 % complete  
ubiformat: formatting eraseblock 775 -- 100 % complete  
root@OpenWrt:/tmp# ubiformat /dev/mtd20 -y -f /tmp/factory_image.ubi
ubiformat: mtd20 (nand), size 101711872 bytes (97.0 MiB), 776 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 775 -- 100 % complete  
ubiformat: 776 eraseblocks have valid erase counter, mean value is 0
ubiformat: flashing eraseblock 96 -- 100 % complete  
ubiformat: formatting eraseblock 775 -- 100 % complete  
root@OpenWrt:/tmp# cat /sys/class/mtd/mtd18/offset
127926272
root@OpenWrt:/tmp# fw_setenv mtdparts 'mtdparts=nand0:0x6100000@0x7a00000(fs),0x6100000@0x1000000(fs_1)'
root@OpenWrt:/tmp# fw_setenv bootcmd 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0'
root@OpenWrt:/tmp# reboot
root@OpenWrt:/tmp# Connection to 192.168.1.1 closed by remote host.
Connection to 192.168.1.1 closed.

[joshmcorreia]

In case it helps anyone in the future, make sure you copy every command I put my command history into a diff-checker to see if I missed anything and, assuming it wasn't a copy-paste error of my logs, it's because I missed the fw_setenv mtdids 'nand0=nand0' command while working on an in-progress edit of the wiki. Now I get to retry over serial and see if I can do it right this time

[CrunchyTalos]

This is very helpful to me while I'm highly considering upgrading to the dl-wrx36. Did you get functionality back over serial?

[joshmcorreia]

The serial connector is still on its way in the mail so I haven't had a chance yet but I did see that other users successfully fixed theirs over serial

[joshmcorreia]

My serial connector came in the mail and I did in fact get functionality back over serial! Woohoo! Also I updated the documentation on the wiki so it should be much harder for someone to brick their router.

[CrunchyTalos]

Good to know. Thanks so much for the info. I was wondering today actually if everything would work out for you and it did! Much appreciation for the information. I was thinking of getting an rax120 (Netgear AX12) but I think the support for the dynalink wrx-36, and ongoing development, might be the better choice at this point in time since I'm in the market for an upgrade to my home WDS network AP.