Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| projects:zte_mf28x [2024/03/10 20:04] – Andreas Böhler | projects:zte_mf28x [2024/08/07 10:33] (current) – Andreas Böhler | ||
|---|---|---|---|
| Line 8: | Line 8: | ||
| </ | </ | ||
| - | The following models | + | The following models |
| * MF282 | * MF282 | ||
| Line 19: | Line 19: | ||
| ===== ZTE MF282 ===== | ===== ZTE MF282 ===== | ||
| - | The MF282 is supported by OpenWrt 23.x onwards. In order to install it, you need to disassemble the device, attach serial console and perform a few commands in the UART shell. | + | The MF282 is supported by OpenWrt 23.05 onwards. In order to install it, you need to disassemble the device, attach serial console and perform a few commands in the UART shell. |
| <WRAP round important 80%> | <WRAP round important 80%> | ||
| Line 29: | Line 29: | ||
| ===== ZTE MF282+ ===== | ===== ZTE MF282+ ===== | ||
| - | This device has a completely different hardware. An OpenWrt port is work in progress. The modem is not Qualcomm-based but uses a Marvell PXA1827 module. | + | This device has a completely different hardware. An OpenWrt port is available, but this device is not supported by OpenWrt 23.05. The modem is not Qualcomm-based but uses a Marvell PXA1827 module. |
| The MF282+ can be identified by the model type " | The MF282+ can be identified by the model type " | ||
| Line 36: | Line 36: | ||
| The newer MF287 series is more powerful than the MF282 and features four Gigabit-ports, | The newer MF287 series is more powerful than the MF282 and features four Gigabit-ports, | ||
| - | OpenWrt supports all models from 23.x onwards. | + | OpenWrt supports all models from 23.05 onwards. |
| ==== Option 1: Install from OEM firmware ==== | ==== Option 1: Install from OEM firmware ==== | ||
| You need an exploit to get access to the stock firmware. Prepare the following: | You need an exploit to get access to the stock firmware. Prepare the following: | ||
| - | | + | <WRAP round important 80%> |
| + | **Required files** | ||
| * Static build of busybox for ARM, e.g. from https:// | * Static build of busybox for ARM, e.g. from https:// | ||
| + | * exploit.dat from https:// | ||
| + | * OpenWrt factory image - this is **not** listed in the table above. Please download it from [[https:// | ||
| + | </ | ||
| + | |||
| + | Then do the following preparatory steps: | ||
| + | |||
| + | * Set up a TFTP server - tftpd-hpa on Linux is tested, but tftpd32 should work as well | ||
| * Rename busybox to " | * Rename busybox to " | ||
| - | | + | * Put the OpenWrt |
| - | | + | |
| * Assign your computer the IP address 192.168.0.22 | * Assign your computer the IP address 192.168.0.22 | ||
| Line 57: | Line 65: | ||
| <WRAP round important 80%> | <WRAP round important 80%> | ||
| - | For the MF287Pro, you need to replace '' | + | For the MF287 and MF287+, you need to replace |
| + | For the MF287Pro, you need to replace '' | ||
| </ | </ | ||
| Line 73: | Line 82: | ||
| tftp -g -r zte.bin 192.168.0.22 | tftp -g -r zte.bin 192.168.0.22 | ||
| cat / | cat / | ||
| - | flash_erase /dev/mtd13 0 0 | + | flash_erase /dev/mtdXX 0 0 |
| - | dd if=zte.bin of=/dev/mtdblock13 | + | dd if=zte.bin of=/dev/mtdblockXX |
| reboot | reboot | ||
| </ | </ | ||
| Line 110: | Line 119: | ||
| <WRAP round important 80%> | <WRAP round important 80%> | ||
| - | Please double-check the partition number by running '' | + | Please double-check the partition number by running '' |
| </ | </ | ||
| < | < | ||
| ls -l /tmp/ubi0* | ls -l /tmp/ubi0* | ||
| - | ubiattach -m 14 | + | ubiattach -m XX |
| ubirmvol /dev/ubi0 -N kernel | ubirmvol /dev/ubi0 -N kernel | ||
| ubirmvol /dev/ubi0 -N rootfs | ubirmvol /dev/ubi0 -N rootfs | ||
| Line 137: | Line 146: | ||
| <WRAP round important 80%> | <WRAP round important 80%> | ||
| - | Unlocking does not work on the MF282+ aka DreiTube! The LTE module uses a compltely | + | Unlocking does not work on the MF282+ aka DreiTube! The LTE module uses a completely |
| </ | </ | ||
| Line 156: | Line 165: | ||
| setenv serverip 192.168.1.100 | setenv serverip 192.168.1.100 | ||
| setenv ipaddr 192.168.1.1 | setenv ipaddr 192.168.1.1 | ||
| - | tftpboot | + | tftpboot openwrt.bin |
| - | bootm 0x82000000 | + | bootm |
| </ | </ | ||
| * After a few minutes, OpenWrt has started | * After a few minutes, OpenWrt has started | ||
| Line 204: | Line 213: | ||
| Should you require more details for any of the steps provided, please have a look at the excellent documentation in the OpenWrt Wiki at https:// | Should you require more details for any of the steps provided, please have a look at the excellent documentation in the OpenWrt Wiki at https:// | ||
| - | ===== Exploit MF287+ in detail ===== | + | ===== Exploit MF287 in detail ===== |
| - | The settings file of the MF287+ is obfuscated and encrypted. Fortunately, | + | The settings file of the MF287 is obfuscated and encrypted. Fortunately, |
| <code python [enable_line_numbers=" | <code python [enable_line_numbers=" | ||