Something looks broken in this instruction: a mailto hyperlink snuck in I think?
3 Likes
Sure!
TLDR - you used a single-` when highlighting that code when it should have been ```, which preserves formatting like newlines. As a result, the preview is unreadable since it's very important those be on separate lines.
Also, I didn't originally notice this, but you do have a mailto: stuck inside your last uboot config command somehow. This will break people's devices if they run that without fixing it first.
Original-A to replace
The code below, provided by hnyman, will set the relevant U-Boot variables:
bootcmd=run openwrtusb; run openwrtboot openwrtboot=setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0 openwrtusb=usb start && fatload usb 0:1 0x44000000 openwrt-ipq807x-generic-dynalink_dl-wrx36-initramfs-uImage.itb && bootm 0x44000000
New Version, A
The code below, provided by hnyman, will set the relevant U-Boot variables:
bootcmd=run openwrtusb; run openwrtboot
openwrtboot=setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0
openwrtusb=usb start && fatload usb 0:1 0x44000000 openwrt-ipq807x-generic-dynalink_dl-wrx36-initramfs-uImage.itb && bootm 0x44000000
Original-B to replace
fw_setenv openwrtboot 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm [0x44000000#config@rt5010w-d350-rev0](mailto:0x44000000#config@rt5010w-d350-rev0)'
New Version, B
fw_setenv openwrtboot 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0'
Hello.
This broke my device when I tried setting the usb recovery. My router is now stuck on the purple led. Didn't even realize the mailto stuck in as I was simply following the instructions.
Is the only way to recover my router through the serial port? And if so, how?
I'm afraid I'm not the right person to ask, I'm only just learning how to work with uboot, but it should be possible.
Check over at the parent topic: Dynalink DL-WRX36 Askey RT5010W IPQ8072A technical discussion
For anyone coming in the future, just insert a usb drive with the initramfs file. The usb recovery part worked. The router is just stuck on trying to figure out wtf mailto is doing in the bootloader.
1 Like
You should edit your erroneous message, and remove the strange mailto part and extra brackets etc.
(There has already been accidents due to that advice. E.g. [Solved] Bricked DL-WRX36 Install after following instructions )
2 Likes
This looks like an error, please confirm.
It's an error, compare it with the wiki entry.
I've added a warning to the wiki page.
1 Like
That is a huge error, causing unbootable router. (The boot from image on USB stick should still work)
As @S7venLights hasn't responded to the earlier discussion, I forcibly edited his message to remove the erroneous part.
EDIT:
For users with the mangled openwrtboot item (with "mailto" garbage), you should be able to recover rather simply:
Just have the correctly named initramfs image on the USB memory stick (as old, small and simple as possible) and you use it to boot into the recovery initramfs image, and from SSH console use the fw_setenv command to correct the openwrtboot item that you now have mangled from S7venLights advice. After that the normal image should again work.
The normal openwrtboot set up with fw_setenv:
fw_setenv openwrtboot 'setenv bootargs console=ttyMSM0,115200n8 ubi.mtd=rootfs rootfstype=squashfs rootwait; ubi part fs; ubi read 0x44000000 kernel; bootm 0x44000000#config@rt5010w-d350-rev0'
7 Likes
So weird, maybe markdown formatting or some copy paste actions added mailto to the text. Sorry I only checked notifications now. But I see a moderator fixed it.
Sorry about that, I don't know how it happened but when I edited the message after your feedback, somehow mailto worked it's way in there. Maybe the markdown editor confused a string of text as an email??
So sorry about that @sulwh, see my last two replies. I don't know how that happened. Sorry for the headache. I see @hnyman fixed the instruction error, thank you.
@frollic , the weird error 
was fixed and you can revert the wiki page.
Sorry again to all, I believe the original instructions were verbatim, an edit later introduced the error. I hope the guide can still help people.
1 Like
warning's been removed.
2 Likes
I got through it all on step 2 and after reboot the device still wont load. I think I even got to setting the usb recovery last night as those commands on the other window are selected like I copied it to use on putty... no matter the reset putton pushed or with/without usb no go on the boot. might just open this bad boy now and get to serial... smh
well, interestingly enough... after getting a 4 pin copnnector soldered on and putty running, it booted up fine and after luci installed has been running without issues.
[Moderator edit: @black_jmyntrn had added the part above this (but under the line I added) in an additional post, but I split that out into a new thread... I copied the above sentence back into this thread where it belongs]
2 posts were split to a new topic: Alternate Antennas for Dyanalink DL-WRX36?
Just wanted to share another success report with the DL-WRX36 and OpenWrt v23.05.2, used as a privacy-respecting home wireless access point. Had previously been using OpenWRT since 2009 on a Linksys that finally died earlier this year.
Official instructions worked as expected. Helped reading them and this install thread a couple times over.
Many thanks to all that help with this FOSS project. We added something to the tip jar.
1 Like
Yet another success story to share.
I have 23.05.2 on my Dynalink DL-WRX36. Only once was the OEM password entered as this process was so smooth and well documented that following the instructions made this a easy install. I did read them all multiple times beforehand and read other surrounding posts - all of which helped.
I did get to use the commands readied in the 2 March 2024 update. What an interesting thing to have an editor to, Odd how a simple @ will provoke an algorithm to consider code as email, but I missed out on all that!
I did have the USB drive not inserting into the proper place or however being not right for this router, and it was not a new or fancy one only a ADATA 16G USB3.0 device, once changed to a KOOTION 32GB USB 3.0 from Amazon that was purchased after the ADATA, the file was seen and it flashed quickly.
I did use LUCI to upgrade with the sysupgrade.bin file and that was smooth as expected. But trying to boot from the USB Recovery method has me wondering if that is working well. I have the same initramfs-uImage.itb file that I used during install and that is referenced in the fw_setenv command #3 - on the same confirmed USB Thumbdrive, and the router will boot fine with the USB drive attached or not, but I am not sure how to tell if it really did boot from the thumb drive or the ROM, maybe after a newer release than 23.05.2 and it will be clear. Still It would be nice to know the recovery works before I need it!
Overall a well documented install procedure with wonderful coding. It is truly amazing to experience all the benefits of the people that spend so much effort in this, You are appreciated! Another true win for OpenWRT and likely to give me a lengthily service life. Now I can get on moving my Archer A7 (running 23.05.2) to replace my Netgear EX2700 (running 19.07.10) as a wireless repeater as the EX2700 is temperamental.
4 Likes
Welcome to the forum donfede, glad you could make use of the thread
Hi all, the firmware has been updated to 23.05.3 on 25 Mar and comes with some security patches.
- (I had some issues with WiFi config after upgrading, read the last 2 paragraphs of this post before upgrading)
You can see official instructions for upgrading. In step 1 however it's easier to download firmware at this link. Just search there for: Dynalink DL-WRX36
Don't neglect to generate a config backup archive, according to those official instructions, before upgrading, as you could lose all your settings if you don't.
After the upgrade you can restore the settings from the same LUCI menu (System>Backup/Flash Firmware) using the 'Upload archive...' button.
Note
You may need to re-enable your WiFi networks after restoring backups at Networ>Wireless
PS. It is important to at least verify the hash of the firmware before upgrading to avoid issues. When uploading the firmware upgrade to the router, it will show you a sha-256 hash number of the image before you flash/install it. Check that it matches the sha shown where you downloaded the sysupgrade image. Read of comprehensive verification options here).
Finally don't forget to update your OpenWRT packages afterwards and from time to time.
issues with WiFi after upgrade
After upgrading and restoring my Config Backup Archive I had an issue where the WiFi networks were present but not enabled. I enabled them, but then only the 5G raido 0 was active. If I clicked restart on the 2.4Ghz radio 1 it would not activate.
I then reset my router at System>Backup/Flash Firmware
(A full reset may not be necessary, maybe try deleting and recreating your wireless networks first)
And recreated my networks (Luckily I have the SSIDs and Passwords in my password manager, be sure to save yours too)
After enabling my 2.4Ghz network Radio 1 automatically became active and same goes for Radio 0.
After this your WiFi should work normally.
However! I don't know if it's just my devices, but Radio 0 5ghz has never worked properly with my O-WRT. Not in 23.05.2 either. Right now it says the radio 0 is on, but my devices can't detect my 5G SSID.
The first time I installed O-WRT My 5Gz network worked for moments and after a reboot wouldn't turn on again... perhaps I'll open a separate thread about this
Does anyone know the best way to be notified of firmware updates? RSS feed, Github perhaps?