Interesting, there are 2 options that I can see you doing right now.
Do a backup of the modem filesystem and replace files with the ones from the firmware update (using Total Commander with ADB plugin or just direct ADB via PC)
Use this modem update file, which contains a newer version firmware code and see if it works.
replace files with the ones from the firmware update
Which files? I could use adb to upload the jar, if installed unzip it into /tmp and then cp the files into the right place. Although isn't this akin to what your new .zip file is but just now with my firmware in the list?
i think the last firmware update itself is only flashable directly by replacing the files, like the tp-link mr200 console updater does, do the same but with the original modem file linked in the main post
This comes across as a bit dicey given you will not give me file list of exactly what ought to copied. If I lose our Internet, I will get a lot of grief, and then be forced to go out and grab another Orange 12 month contract and free modem for crap 10Mbits Internet again to quickly fix the problem. Orange in a terrible ISP in Belgium anyway.
I prefer to wait until fibre is available, and get a fibre connection.
Do you know if the two antennae on the MR200 are for wifi or the LTE modem?
They are for LTE, about the file list, you copy everything from the system folder in the update zip, just replace all the files that can be replaced with those from the update zip/system folder, it shouldn't be dangerous since that's what's done by the TP-Link MR200 Console updater.
Off topic, have you got a way of measuring the LTE signal strength on the MR200?
The OpenWRT O/S disabled the signal strength LEDs. Or can these be enabled again?
you can flash back the ofw and return the device for warranty - at least this in what I did after bricking the uboot - but they had no more devices in stock (in Romania) and offered to return the money but I refused and repaired the device myself as described in the wiki with a rpi
Ah, not with carrier locked devices, mine for sure (WIND Hellas GR), would return Unable to mount VFS, and would kernel panic, no matter what, in my other thread, it seemed like it has something to do with U-Boot's ENV, which for the time being, I can't say much about.
The MR200 V2 dump did work with V1 properly, just needed to do a factory reset upon first boot, if you want V1, use your carrier's firmware or another carrier's one, like Orange.
The carrier is Orange ( Belgium ).
How sure are we to flash it back to factory ( or equivalent) with the stock Orange fireware?I really don't want to brick it, because I really like the MR200.