So, does anyone know what the differences between the MR600's hardware version V1 and V2 are? Could it be easy to adapt the V2 image to work on the V1?
It's definitely not like they are a completely different device or have a different CPU/whatever...
Because by just flashing the V2 image on the V1 I'll get a brick, right?
When looking at the official TP-Link forum I can only see that software changes are mentioned: in the V2 you can select the LTE band, and IPSec VPN is gone.
I'm curious if there are actually any hardware changes that would require tweaks for OpenWRT to run properly...
Hi,
I flashed my MR600 V1 with the V2 firmware a few months ago and it has been running without problems so far. Only 2.4 GHz shows up though and I have not tested bandwidth or anything.
I'm just using it in our basement as a managed switch (VLANs not setup yet though) and access point which gets used very rarely. But it just worked with the V2 firmware.
When booting via TFTP you can select to just boot it into RAM without flashing it so I would think that it's actually not that risky. But I'm by no means an expert with this and also it's been a while since I did that.
No I have not tested cellular connection because it never worked for me even with the stock firmware. That's why I have two unused ones because Amazon didn't want them back haha. I might try when I flash the second one. I've seen the cellular modem detected at least in the interface section.
I know this is a rather old entry but has there been any update in that regard? I sadly didn't find anything and I really would like to avoid flashing the stock firmware just to to a firmware update.
mr600v2 user here. Wanna just drop my experience as an inexperienced user (and first openwrt approach).
Precompiled package 23.05.3 doesn't include luci-proto-qmi, so modem doesn't work out of the box.
Qualcomm modem doesn't get the apn from the wwan settings. I had to use uqmi tool to set it manually with --modify-profile 3gpp,1 .... bla bla ..., luckily it saves it internally in permanent memory
Qualcomm modem seems not to setup correctly after power up ( interface needs to be reinitialized manually after powerup )
Wifi is unusable as for stock, the @nerijus blob works great even if I don't like blobs from unknown sources.
That shit box is a mess to open up.
Currently I feels quite satisfied even if I feel stock rom is still more user friendly and feature rich as by now. (But miss vlans that I want to use).
Update,
Powercycle after powercycle it seems firmware get corrupted.
Description seems to fit that: https://github.com/openwrt/openwrt/issues/9729.
I'm reverting back to stock, as it's far too complicate for me to handle.
I have the same issue. Some users seem to use this device successfully? It works alright for me, but if you reboot, you might have bad luck and some important stuff is missing in the filesystem.
I also had to revert to stock firmware
Everything was working great on openwrt but just tinkering in the hope to get AT commands working, i accidentally changed modem's usb mode from default QMI to ECM through shell.
Now openwrt doesnt recognize it as usb and stock firmware also shows Internal error and doesnt reset/upgrade anything on modem. Couldnt pass any AT commands as /dev/ttyUSBx doesnt show up.
Opening the router just to find separate serial access for modem didnt help.
No guide seems to work. I have tried almost all the guide wrt ECM on openwrt.
These are the relevant outputs-
[ 3.226582] usbcore: registered new interface driver usbfs
[ 3.232290] usbcore: registered new interface driver hub
[ 3.237712] usbcore: registered new device driver usb
[ 3.261170] xhci-mtk 1e1c0000.xhci: supply vusb33 not found, using dummy regulator
[ 3.331560] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 9.022550] usbcore: registered new interface driver cdc_acm
[ 9.037893] usbcore: registered new interface driver cdc_wdm
[ 9.086523] usbcore: registered new interface driver usbhid
[ 9.092260] usbhid: USB HID core driver
[ 9.107416] usbcore: registered new interface driver usbserial_generic
[ 9.114185] usbserial: USB Serial support registered for generic
[ 9.146203] usbcore: registered new interface driver cdc_eem
[ 9.153679] usbcore: registered new interface driver cdc_ether
[ 9.165501] usbcore: registered new interface driver cdc_ncm
[ 9.172580] usbcore: registered new interface driver cdc_subset
[ 9.197354] usbcore: registered new interface driver huawei_cdc_ncm
[ 10.788367] usbcore: registered new interface driver qmi_wwan
[ 10.796362] usbcore: registered new interface driver rndis_host
[ 10.806425] usbcore: registered new interface driver cdc_mbim
[ 10.814208] usbcore: registered new interface driver ipw
[ 10.819893] usbserial: USB Serial support registered for IPWireless converter
[ 10.837557] usbcore: registered new interface driver option
[ 10.843461] usbserial: USB Serial support registered for GSM modem (1-port)
[ 10.855588] usbcore: registered new interface driver qcserial
[ 10.861627] usbserial: USB Serial support registered for Qualcomm USB modem
I guess the modem firmware is directly loaded from the modem chip. 25Q127 is 16 MiB Flash chip only used to store the router related OS. The one in the bottom right corner of the picture should be the modem chip.
Thank you all for sharing your knowledge here. With your help, I successfully flashed my TPGAU-provided MR600 router with OpenWRT. My goal was to change the IMEI of the 4G modem, which required access to AT commands. After multiple attempts, this method seemed to work for gaining access, although I was unable to change the IMEI.