Installed using the instruction in the wiki. Downgraded to 6118 and then proceed to flash totolink_x5000r-squashfs-sysupgrade.bin with OEM gui. System bootloops as it turns on and off. Re-flashed to 6118 OEM firmware and finds that flash totolink_x5000r-initramfs-kernel.bin works. The initramfs-kernel firmware sticks even after rebooting but cannot flash squashfs-sysgrade.bin successfully. The Totolink x5000R is manufactured in 2022 and I am suspecting some hardware might have changed even though the box still lists the hardware at V1.0. Any help would be greatly appreciated.
Only way of knowing would be using serial.
Could also try an older release.
EDIT: wrong URL.
no it's an mt7621 device
No, it's not an mt7622 device, my bad.
Here's the correct url
https://downloads.openwrt.org/releases/22.03.0/targets/ramips/mt7621/
I've tried 21.x as well. I've gone through 5 different versions of the firmware and all bootlooped. I tried every version of 22.x and they bootlooped as well...
Serial it is then, I guess 
I even exchanged it to make sure I didn't get a bad unit. Guess I'll look at how to connect using serial.
does this device have a reset button? if so try reset button after you flash openwrt.
Tried that as well but it would kick it to the OEM firmware update page.
but is not really clear if factory.bin or sysupgrade.bin is needed for installation
edit no factory.bin
try flash two times sysupgrade.bin
One of the very thing I've tried. Just baffling thatInitramfs.bin works but the sysupgrade.nin doesn't.
As with my Belkin RT1800 & offical release possible U-boot is not the same
Post your U-boot for compare
I have opened up the router. Upon inspection on the hardware, Totolink has switch their NOR Nand chip to a different company on top of using a new and faster ram. New NOR nand chip is made by Zbit Semiconductor part #ZB25VQ128ASIG (old chip is Eon EN25QH128). New ram part number is NT5CC128M16JR (DDR3-1866 13-13-13) while the old part number is Nanya NT5CC128M16IP (DDR3-1600 11-11-11). Box still list the hardware at V1.0.
I am assuming the change in the NOR nand chip is a possible culprit in the firmware not being flashed when updating. When I ssh in while the router is flashed with INITRAMFS firmware, I do not see any mtd or firmware drives mounted in /dev.
Do you think the switch of the NOR nand chip is the reason for the bootloop after flashing?
test with a serial console
if you have to unsolder the spi flash memory consider replacing it with a 32 M as I did in many of my boxes
i use with many compatibility with old U-boot Macronix MX25L25635E
it will still work for 16M firmware
1 Like
I've finally got my serial to usb connectors and can finally diagnosis the bootloop in earnest. As I suspected, the new spi-nor is what's causing the bootloop as its JDEC ide byte is not in the kernel. This the the JEDEC id bytes: 5e 40 18 5e 40 18 for the Zbit 25VQ128ASIG. Is it as simple as adding in the chip code into the kernel code and recompile the image in order for me to install OpenWRT onto the router? Thanks!
As for Tenbay -> 405-mtd-spi-nor-Add-support-for-BoHong-bh25q128as.patch
or replace SPI as me
Flash memory 16M is almost unknown : BoHong bh25q128as replaced by a Macronix 32MB
no problem with flash boot ( tftp -> console 2 ... ) for flash old 16M content
build new firmware for 32M flash memory
for read old content : CH341 -> NeoProgrammer_2.1.0.19
after write content in as MX25L25635E or WINBOND 256MB
startup -> tftp key 2 .... OpenWrt firmware
firstboot -> reboot -f
Variant for 32M version
modify in mt7621.mk
IMAGE_SIZE := 32448k
modify in mt7621_tenbay_t-mb5eu-32M.dts
reg = <0x90000 0x1F70000>
build
flash new firmware with tftp
@wopo
Bro, has your problem been solved?
1 Like