|
|
@ -16,24 +16,11 @@ The build is automated in a [script](./make.sh). Change the release |
|
|
|
1. Adds signal LED script into the build |
|
|
|
1. Adds signal LED script into the build |
|
|
|
1. Builds the image |
|
|
|
1. Builds the image |
|
|
|
1. Creates the recovery image suitable for a fresh device |
|
|
|
1. Creates the recovery image suitable for a fresh device |
|
|
|
1. Starts the TFTP server, so the revocery image can be uploaded |
|
|
|
1. **Attention:** Starts the TFTP server, so the recovery image can be |
|
|
|
|
|
|
|
uploaded |
|
|
|
|
|
|
|
|
|
|
|
## Recovery image preparation |
|
|
|
## Recovery image preparation |
|
|
|
|
|
|
|
|
|
|
|
The recovery image is used to replace the stock firmware with OpenWRT via |
|
|
|
|
|
|
|
TFTP. Citing the MR200 OpenWRT |
|
|
|
|
|
|
|
[manual](https://openwrt.org/toh/tp-link/archer-mr200): |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
> Turn on the device while pushing the WPS button until the WPS light turns |
|
|
|
|
|
|
|
> on. At that point, the bootloaders integrated tftp client with the ip |
|
|
|
|
|
|
|
> address of 192.168.1.1, tries to connect to a tftp server running at |
|
|
|
|
|
|
|
> address 192.168.0.66 and getting the file named |
|
|
|
|
|
|
|
> **ArcherC2V1_tp_recovery.bin**. so you need to be running a tftp server |
|
|
|
|
|
|
|
> with the ip/netmask of 192.168.0.66/23 and connect it to lan port1. It is |
|
|
|
|
|
|
|
> vital that your firmware includes the bootloader at the very beginning |
|
|
|
|
|
|
|
> (without any extra tp-link header) as the bootloader will start writing |
|
|
|
|
|
|
|
> the firmware to flash with the starting address of 0x00000000. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Manual recovery image preparation: |
|
|
|
Manual recovery image preparation: |
|
|
|
|
|
|
|
|
|
|
|
```bash |
|
|
|
```bash |
|
|
@ -54,27 +41,23 @@ sudo systemctl start atftpd.service |
|
|
|
#curl -O tftp:/192.168.0.66/ArcherC2V1_tp_recovery.bin |
|
|
|
#curl -O tftp:/192.168.0.66/ArcherC2V1_tp_recovery.bin |
|
|
|
``` |
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
## Revert to TP-Link stock firmware |
|
|
|
**Attention:** following this step can possibly brick the device. Double |
|
|
|
|
|
|
|
check everything before proceeding! Citing the MR200 OpenWRT |
|
|
|
**Important:** Always revert back to the same stock firmware version which |
|
|
|
[manual](https://openwrt.org/toh/tp-link/archer-mr200): |
|
|
|
was used to prepare the recovery image. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To avoid the possibility that the firmware file will be un-published fro |
|
|
|
|
|
|
|
mthe vendor, it is stored is stored in the [firmware](./firmware) folder in |
|
|
|
|
|
|
|
this repository. There is also an `extracted_firmware.bin` created out of |
|
|
|
|
|
|
|
this stock firmware, should the ned to revert back be required (for |
|
|
|
|
|
|
|
instance to install newer firmware released by the vendor, that would |
|
|
|
|
|
|
|
update the 4G router firmware as well - something OpenWRT cannot do). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Manual steps to revert to stock from OpenWRT: |
|
|
|
> Turn on the device while pushing the WPS button until the WPS light turns |
|
|
|
|
|
|
|
> on. At that point, the bootloaders integrated tftp client with the ip |
|
|
|
|
|
|
|
> address of 192.168.1.1, tries to connect to a tftp server running at |
|
|
|
|
|
|
|
> address 192.168.0.66 and getting the file named |
|
|
|
|
|
|
|
> **ArcherC2V1_tp_recovery.bin**, so you need to be running a tftp server |
|
|
|
|
|
|
|
> with the ip/netmask of 192.168.0.66/23 and connect it to lan port1. It is |
|
|
|
|
|
|
|
> vital that your firmware includes the bootloader at the very beginning |
|
|
|
|
|
|
|
> (without any extra tp-link header) as the bootloader will start writing |
|
|
|
|
|
|
|
> the firmware to flash with the starting address of 0x00000000. |
|
|
|
|
|
|
|
|
|
|
|
```bash |
|
|
|
After the upload the router reboots itself and after this point, |
|
|
|
cd firmware |
|
|
|
**upgrading** should be always the preferred option to this one, because it |
|
|
|
dd bs=512 obs=512 skip=257 count=15744 if=Archer\ MR200v1_0.9.1_1.2_up_boot_v004a.0\ Build\ 180502\ Rel.53881n.bin of=extracted_firmware.bin |
|
|
|
is not touching the bootloader. |
|
|
|
scp extracted_firmware.bin root@openwrt:/tmp |
|
|
|
|
|
|
|
/usr/bin/ssh root@openwrt |
|
|
|
|
|
|
|
mtd -r write extracted_firmware.bin firmware |
|
|
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## 4G signal LED integration |
|
|
|
## 4G signal LED integration |
|
|
|
|
|
|
|
|
|
|
@ -120,6 +103,28 @@ cd /tmp |
|
|
|
sysupgrade openwrt-19.07.7-ramips-mt7620-ArcherMR200-squashfs-sysupgrade.bin |
|
|
|
sysupgrade openwrt-19.07.7-ramips-mt7620-ArcherMR200-squashfs-sysupgrade.bin |
|
|
|
``` |
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Reverting to TP-Link stock firmware |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Important:** Always revert back to the same stock firmware version which |
|
|
|
|
|
|
|
was used to prepare the recovery image. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
To avoid the possibility that the firmware file will be un-published fro |
|
|
|
|
|
|
|
mthe vendor, it is stored is stored in the [firmware](./firmware) folder in |
|
|
|
|
|
|
|
this repository. There is also an `extracted_firmware.bin` created out of |
|
|
|
|
|
|
|
this stock firmware, should the ned to revert back be required (for |
|
|
|
|
|
|
|
instance to install newer firmware released by the vendor, that would |
|
|
|
|
|
|
|
update the 4G router firmware as well - something OpenWRT cannot do). |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Manual steps to revert to stock from OpenWRT: |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
```bash |
|
|
|
|
|
|
|
cd firmware |
|
|
|
|
|
|
|
dd bs=512 obs=512 skip=257 count=15744 if=Archer\ MR200v1_0.9.1_1.2_up_boot_v004a.0\ Build\ 180502\ Rel.53881n.bin of=extracted_firmware.bin |
|
|
|
|
|
|
|
scp extracted_firmware.bin root@openwrt:/tmp |
|
|
|
|
|
|
|
/usr/bin/ssh root@openwrt |
|
|
|
|
|
|
|
mtd -r write extracted_firmware.bin firmware |
|
|
|
|
|
|
|
``` |
|
|
|
|
|
|
|
|
|
|
|
## Credit |
|
|
|
## Credit |
|
|
|
|
|
|
|
|
|
|
|
The authors of the LED script are users **asenac** and **spamcop**, |
|
|
|
The authors of the LED script are users **asenac** and **spamcop**, |
|
|
|