yes. no problem
Any news on a working image v19 or v20 for my Archer MR200 V5.2? Things I need are sshd, iptables, iproute, snmp, hostpad (2.4GHz 802.11n 5GHz 802.11ac), 4G LTE Modem (Band 3 and 8) and working ethernet ports. Plain simple router setup without graphical user interface. That's it.
yes v19 is available. if you are looking for modem band lock, then I haven't been able to do it yet. the qualcom modem mdm9207 lacks AT command instruction. although it should be able to support band lock from the original firmware
Problem is I have 3 antennas surrounding my house and my rooftop antenna is aligned to the antenna with line of sight. This antenna submits the signal on band 3 as for now. You mean with v19 I can't lock the modem to this band? No TTY ports available for now?
Forgot to mention I need ipv4/dhcp support for the wwan interface. And I made a little typo in my post above, hostpad should be hostapd. The v19 image for the MR200V4 from mrhaav seems to lack dhcp support for wwan and I'm in doubt that his image will work with the V5.2 hardware and it probably doesn't support band locking either. So I'll stay on the stock fw for now.
Yes cant lock band yet with this modem MDM9207. Needs the AT command list for this modem but cant be found. TTY port is available. ipv4/ipv6 is supported with mrhaav uqmi fork. I tested it.
you can try from this link
Have you tried
AT+CLAC
AT+QCFG="band" or AT$QCBANDPREF=?
Not yet. Maybe will try it later when i have the chance.
Actually I did tried some known commands just to test it but I dont remember the exact commands. It doesnt work.Thats when I reach the conclusion that the commands is unknown. The original firmware probably use some qmi cli commands to lock the modem band
@gurangax Could you help me create a back to stock tftp image for the 5.2? None that I create (with dd bs=512 skip=1 count=16000 if=original.bin of=tp_recovery.bin) work, the power LED just keeps blinking but with no access to the router 
Ok will do so later. Did you tried to install openwrt?
Yes, I did and that all worked fine. I just want to test some things with the modem on stock, and that is where I stumbled upon this small issue 
have you tried hard resetting the modem after trying the stock firmware? I think I experienced the same thing as you when trying to revert back to stock. I may have flashed the firmware from my original dump to recover it. I will send a link to stock recovery later.
Here is the link. I sent 2 files. 1 is from tp-link website (mr200v5), another one from my mr200 v5.2 dump. Try the web version first. if doesnt work try my dump and let me know. I can't test it on my router at the moment, cause it is being used by the family.
ah welp, both unfortunately with the same result, power LED blinks, there's some LAN activity but I can't access the router. How would you go about hard resetting the modem? I've got access to it via adb when I use OpenWrt.
Also still weird: The MR200 v4 tp_recovery.bin works, for some reason. But the device absolutely is a 5.20
I'll send another test file later. When you say mr200v4 tp_recovery.bin do you mean the openwrt or stock mr200v4 version. And yes v4 and v5 are compatible. Theres probably some circuit redesign and settings used in the stock firmware for each one.
If you can show the serial tty output would be great for diagnostic
I mean the stock version and something must be different with the 5.x files since cutting out the relevant parts works perfectly with v4 and the router comes online.
Is there an alternative to flash the up to date modem FW, since that's primarily what I need. I have access via serial and adb and the thing identifies as Qualcomm modem, but not a specific vendor like Quectel, so honestly no idea...
maybe you can try with v4 stock and update the firmware from there with v5 file.
It is possible when flashing certain data gets deleted and thats why it doesn't work after that. A factory data reset might help
Yeah, I can't unfortunately, TP-Link doesn't allow to flash v5 from v4
try reset it after flash v5
To reset the TP-LINK Archer MR200 to its default settings, you have to do the following steps:
- Turn on router.
- Press and hold the WPS/Reset button until the router's Power LED flashes.
- Device is automatically restarted.
- Router has been reset to factory settings.
And if you can get the terminal output would be great for diagnostic
Alright, connected via serial, this is the error with the stock v5.2 tp_recovery.bin (via TFTP):
SQUASHFS error: squashfs_read_data failed to read block 0x66c5a4
SQUASHFS error: Unable to read metadata cache entry [66c5a4]
SQUASHFS error: Unable to read inode 0x1020156b
VFS: Cannot open root device "mtdblock2" or unknown-block(31,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00 128 mtdblock0 (driver?)
1f01 1280 mtdblock1 (driver?)
1f02 6592 mtdblock2 (driver?)
1f03 64 mtdblock3 (driver?)
1f04 64 mtdblock4 (driver?)
1f05 64 mtdblock5 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
Ah, and when flashing it via TFTP, this is the output:
RESET MT7628 PHY!!!!!!..................................................
starting recovery...
TODO, Read MAC Address from Flash
netboot_common, argc= 3
NetTxPacket = 0x83FE4200
KSEG1ADDR(NetTxPacket) = 0xA3FE4200
NetLoop,call eth_halt !
NetLoop,call eth_init !
Trying Eth0 (10/100-M)
Waitting for RX_DMA_BUSY status Start... done
ETH_STATE_ACTIVE!!
TFTP from server 192.168.0.225; our IP address is 192.168.0.2
Filename 'tp_recovery.bin'.
TIMEOUT_COUNT=10,Load address: 0x80060000
Loading: T T checksum bad
checksum bad
checksum bad
checksum bad
Got ARP REQUEST, return our IP
checksum bad
T Got ARP REPLY, set server/gtwy eth addr (8c:ae:4c:fe:01:94)
Got it
#################checksum bad
################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#########################################
done
Bytes transferred = 8192000 (7d0000 hex)
NetBootFileXferSize= 007d0000
Erase flash !!
From 0x20000 length 0x7A0000
..........................................................................................................................
Copy 0x80080000 to 0x00020000, count 0x7A0000....
..........................................................................................................................