I will be getting my hands on the device soon and I figured I'd get a head start on what it takes to add openwrt support to it. I've extracted the dts from the original firmware if anyone is interested:
Edit: I've read the talks of using the Ruijie RG-X60 initramfs image to boot. Based on the Ruijie dts file and the dts dump from the original firmware, the MTD partitions are clearly different so an mtd backup will not work. A new DTS file needs to be created as a starting point. I can tackle it but won't be able to test it until I get access to the device (~2 weeks).
Unfortunately, due to the storage differences of the TP-Link and this device, I don't think your backups are of any use. Also, due to you running sysupgade, that process may have overwrote all but 2 of the partitions (except BL2 and u-boot-env partitions).
What you can hope for is someone providing you a backup of the device with the right storage configuration and using mtk_uartboot to boot it to perform a restore. That's assuming the device's bootloader is unlocked, which it may be based on previous posts.
I have a make-shift initramfs and sysupgrade image with the appropriate storage configuration if someone wants to volunteer in trying it and performing a backup of all the storage partitions to help you and others.
The image I created requires more work i think to get it fully working, or it may already work, it's untested. However, it won't do any harm to boot to memory, just do not perform a sysupgrade. Let me know if someone wants it.
Edit:
Removed non-functional initramfs image
Just an update...
I have the device in hand now and I think I'm getting close to getting this device functional on Openwrt.
After sysupgrade:
As previously posted, UART causes kernel panic when loading wifi even on OEM firmware. I've found this workaround:
- Power off your device and make sure your UART adapter is NOT plugged into PC.
- Turn on the device, once you see lights, plug your UART adapter in and press 0 to interrupt uboot.
- After this point, loading an initramfs image via tftp should not cause kernel panic anymore for the duration of the device being powered on.
If you ever power off your device (not soft reboots), you'd need to perform these actions again. Basically make sure UART isn't connected when device powers up.
Edit:
I believe I have everything functional on Openwrt now and can sysupgrade in serial to a working device.
However, I'm trying to figure out how to get a modified firmware to load on the OEM firmware upgrade page. I'm able to get the file to be accepted but results in a *** Cannot find volume 'kernel' *** error when trying to boot.
If anyone knows how to build an alternative firmware acceptable by the OEM firmware upgrade process. Please let me know.
1 Like
