Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:zyxel:t-56 [2024/12/10 11:12] – [Opening the case] frollic | toh:zyxel:t-56 [2024/12/12 12:34] – [Installation] frollic | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== ZyXEL T-56 ====== | ====== ZyXEL T-56 ====== | ||
| - | The Zyxel T-56 is an ISP (Odido) branded EX5601-T1. | + | The Zyxel T-56 is an ISP (Odido |
| - | Installation is different, due to locked down firmware and boot loader, but once installed, you get the same features. | + | Installation is different, due to locked down firmware and boot loader, but once installed, you get the same functionality as in the T1. |
| /*****/ | /*****/ | ||
| Line 15: | Line 15: | ||
| " | " | ||
| " | " | ||
| - | " | + | " |
| " | " | ||
| } --> | } --> | ||
| - | |||
| - | /* If no unsupported functions known, comment out the following datatable or delete it. */ | ||
| - | <!-- ToH: { | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | " | ||
| - | } --> | ||
| - | |||
| - | |||
| ===== Hardware Highlights ===== | ===== Hardware Highlights ===== | ||
| <!-- ToH: { | <!-- ToH: { | ||
| Line 49: | Line 38: | ||
| } --> | } --> | ||
| - | The T-56 requires serial | + | :!: The T-56 requires |
| - | Use the 1GbE Ethernet ports until you've TFTP booted | + | :!: The installation instruction will wipe the existing firmware, and maximize |
| - | The installation instruction | + | :!: Going back to stock will be hard(er), if not impossible. Backing up the stock firmware |
| - | Going back to stock will be hard(er), if not impossible. How to back up the current firmware, isn't documented in this guide. | + | Use the 1GbE Ethernet ports until you've TFTP booted the ubootmod-initramfs-recovery.itb image. |
| + | Until you reach the flashing section, everything will be done from RAM, if you reboot, you'll have to start over. | ||
| The **mt7986-ram-ddr4-bl2.bin** can be downloaded from https:// | The **mt7986-ram-ddr4-bl2.bin** can be downloaded from https:// | ||
| the rest from https:// | the rest from https:// | ||
| - | **Use the -ubootmod- | + | Use the **zyxel_ex5601-t0-ubootmod-** |
| - | Disassemble the device, and connect to the serial port, and switch it on. | + | * Disassemble the device, and connect to the serial port, and switch it on. |
| Verify serial' | Verify serial' | ||
| Line 73: | Line 63: | ||
| </ | </ | ||
| - | Close your term application and download the mtk_bootloader from https:// | + | * Close your term application and download the mtk_bootloader from https:// |
| There are premade binaries available for Apple and x86 in https:// | There are premade binaries available for Apple and x86 in https:// | ||
| - | Switch off the device, change the -s parameter making it match your serial port, and execute: | + | * Switch off the device, change the -s parameter making it match your serial port, and execute: |
| < | < | ||
| % mtk_uartboot -s [serial port] --aarch64 -p mt7986-ram-ddr4-bl2.bin -f openwrt-23.05.5-mediatek-filogic-zyxel_ex5601-t0-ubootmod-bl31-uboot.fip | % mtk_uartboot -s [serial port] --aarch64 -p mt7986-ram-ddr4-bl2.bin -f openwrt-23.05.5-mediatek-filogic-zyxel_ex5601-t0-ubootmod-bl31-uboot.fip | ||
| Line 84: | Line 74: | ||
| Handshake... | Handshake... | ||
| </ | </ | ||
| - | Switch on the T-56 and you should see | + | * Switch on the T-56 and you should see |
| < | < | ||
| hw code: 0x7986 | hw code: 0x7986 | ||
| Line 114: | Line 104: | ||
| ================================== | ================================== | ||
| </ | </ | ||
| - | Once mtk_uartboot finishes, you can start up your serial port application again, and see the boot loader looping, and requesting an image. | + | * Once mtk_uartboot finishes, you can start up your serial port application again, and see the boot loader looping, and requesting an image. |
| - | You can keep serial connected throughout the rest of the installation process. | + | (You can keep serial connected throughout the rest of the installation process.) |
| < | < | ||
| Line 128: | Line 118: | ||
| ERROR: can't get kernel image! | ERROR: can't get kernel image! | ||
| </ | </ | ||
| - | Reconfigure your TFTP host to use 192.168.1.254, | + | * Reconfigure your TFTP host to use 192.168.1.254, |
| < | < | ||
| Line 147: | Line 137: | ||
| </ | </ | ||
| - | You can connect the device to your existing network, and wget the files you need, or (Win)scp them over to the device' | + | * You can connect the device to your existing network, and wget the files you need, or (Win)scp them over to the device' |
| You also have the option to switch over to ssh, or keep using serial for the actual installation. | You also have the option to switch over to ssh, or keep using serial for the actual installation. | ||
| Line 154: | Line 144: | ||
| You'll need the following files transferred (or downloaded) to the router' | You'll need the following files transferred (or downloaded) to the router' | ||
| - | * kmod-mtd-rw*_aarch64_cortex-a53.ipk | + | * kmod-mtd-rw_*_aarch64_cortex-a53.ipk |
| - | * openwrt-mediatek-filogic*-ubootmod-initramfs-recovery.itb | + | * zyxel_ex5601-t0-ubootmod-initramfs-recovery.itb |
| - | * openwrt-mediatek-filogic-*-ubootmod-preloader.bin | + | * zyxel_ex5601-t0-ubootmod-preloader.bin |
| - | * openwrt-mediatek-filogic-*-ubootmod-bl31-uboot.fip | + | * zyxel_ex5601-t0-ubootmod-bl31-uboot.fip |
| - | * openwrt-mediatek-filogic-*ubootmod-squashfs-sysupgrade.itb | + | * zyxel_ex5601-t0-ubootmod-squashfs-sysupgrade.itb |
| < | < | ||
| Line 171: | Line 161: | ||
| </ | </ | ||
| - | (Up until now, everything you've done have been executed from RAM, if you reboot, you'll have to start over.) | + | **Flashing** |
| - | If you used one of the LAN ports to download the files required, you might want to disconnect it, it'll start generate annoying port status updates after you've executed the 1st ubimkvol | + | If you used one of the LAN ports to download the files required, you might want to disconnect it, it'll start generate annoying port status updates after you've executed the 1st command. |
| - | + | ||
| - | **Flashing** | + | |
| < | < | ||