@Sunshine can you help me i was trying to update my M7650 but unfortunately it was interrupted. now i cant use my m7650 because it keep on rebooting stuck on logo. i tried to use recovery firmware i got an error " device1: Fail to get fastboot handle! " please help me.

Hello,

Can anyone provide a competent guide and a firmware that allows manual band selection for this M7650 ... 

I'm trying to update to some beta version that supposedly allows this function..

I followed the golden standard guide attached to this M7650(EU)1.1_recoverFirmware zip but apparently I'm either too dumb or just can't get it right, because the device is not recognized even with all the qualcomm and adb tools and drivers in the world.

Thanks..

Hi @BigSmile99 the same here, I have never succeeded to do the upgrade of my M7650. Hope you will be more lucky than me ;-)

I want to let you know that I also was stuck on version 1.1.6. However I've managed it to upgrade the firmware from "1.1.6 Build 180723 Rel.1022n" to "1.1.9 Build 220418 Rel.1027n" and later on I even managed to upgrade to version "1.1.12 Build 240722 Rel.1036n". I will describe the progress I have done through. But be aware, what I describe is not supported and doing at your own risk. Your device may be bricked after these steps as I have changed variables, which are not ment to be changed by user, to bypass the upgrade check.

I have a TP-Link M7650(EU) v1.1 device. I wasn't able to update it's firmware by uploading the zip-file from the TP-Link website (tried all of them) and it could not found a newer firmware by using it's self-updating feature, also known as cloud download. And I'm not able to use the recovery image posted in this topic because the fastboot won't connect to the device. When I connect the device, with battery unplugged, it's not found as a fastboot cabable device, and such the recovery image cannot be loaded. I have tried using Linux and in Windows 11 to get fastboot working, but none of this was a success. I will maybe try someday with an old Windows laptop and try more Qualcomm USB drivers. But I think it's required to put the device first in a fastboot mode, like any other Android device? As the display only gives a icon with missing battery and no sign of fastboot. I have also tried setting everything back to factory settings, but it has no effect on getting fastboot working.

In this topic I found someone who did succesfully downgrade the firmware from 1.1.6 to 1.1.5, I tried this and suddenly I was downgraded to 1.1.5. However, I still wasn't able to update the firmware to a newer version, hence I had only downgraded to an older version and I could not found a way to upgrade to anything newer than version 1.1.5.

Then I discovered it was quite easy to get telnet access to the device using this linux shell script: https://github.com/m0veax/tplink_m7350/blob/main/open-v4.sh. Be sure that you have curl, jq, and netcat installed. The script only works when the password is still set to it's default password. I found also that in the firmware-file from TP-link there is a compatibility.txt-file, which contains a number like 76500001:0. When I have telnet access I could found this number back in the field product_id in the file /etc/config/product. I saw that in the zipfile of firmware version 1.1.5 the compatibility contains 76500001:0, which matched with the number I found on the device as product_id. The newer firmware, especially version 1.1.9 contains a compatibility number wth 76500002:0. First I thought it would maybe possible to edit the zipfile. However the firmware wasn't accepted and maybe that's because the firmware is signed by tp-link. As a kind of last-resort I tried to edit /etc/config/product on the device and set it to 76500002. I did not reboot the device, but now upgraded firmware 1.1.9 via the web-interface. To my suprise this worked, I have upgraded my device from a 2018 firmware to a firmware from 2022.

After upgrading, I was able to update to the latest ISP-files from 24071201. I could not found what maybe not could work because of this "hack". Device is still functioning perfect. I even was still able te get telnet access by using the same script. After this first upgrade step I could not upgrade to the latest version 1.1.11 or 1.1.11. The compatibility file contains now a third number and is 76501002:0:00000002. This last number I can match against update_ver from /etc/config/product. However, changing this number in the file had no effect and I wasn't still able to upgrade the firmware further. But the I changed the number by using uci, using this commands:

uci set product.info.update_ver=00000002

uci commit

After this, I was able to upgrade my device to the current latest version 1.1.12, from 2024, bringing the device fully up-to-date. Even telnet still worked on the device.

Sorry for my long story, but I wanted to describe my process as detailed as possible. Hope someone can use it and will issues still be fixed with it.

Short version:

When you have telnet access on version 1.1.6, first set the correct product_id:

uci product.info.product_id=76501002

uci commit

Upload via web interface firmware 1.1.9 to the device. Then gain again telnet access and set update_ver to 00000002 using this commands:

uci set product.info.update_ver=00000002

uci commit

Now the firmware can be upgraded by using the web interface to version 1.1.12.