[TOOL] 6T MsmDownloadTool v4.0.59 (OOS v9.0.13)

Search This thread

mat334

New member
Nov 21, 2021
1
0
This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.

Contains the latest MsmDownloadTool v4.0.59 and OOS v9.0.13 which is compatible with International and McLaren editions.

OOS v9.0.11 can also be used to convert a T-Mobile model into a fully fledged International model, more info here.

  1. Make sure that your phone is switched off.
  2. Open device manager on your Windows PC.
  3. Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
  4. Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
  5. If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download one of the drivers below and install.
  6. Run MsmDownloadTool V4.0 and click Start.
NOTE: This will completely wipe your device and relock your bootloader.

Downloads
6T MsmDownloadTool v4.0.59 (OOS v9.0.13)
6T MsmDownloadTool v4.0.58 (OOS v9.0.12)
6T MsmDownloadTool v4.0.58 (OOS v9.0.11)
6T MsmDownloadTool v4.0.58 (OOS v9.0.6)
6T MsmDownloadTool v4.0.58 (OOS v9.0.5)
Driver
Alternative driver

Shameless plugs - OP referral link for any peops that would like $20/£20/€20 discount: OnePlus or PayPal donation link: PayPal.
I tried to convert my onplus 6t blocked t-mobile to international, I must have made a mistake because, my cellphone does not turn on any more I have all tried, to press the volume long time, just press the button power ....
What do I do to make it work again? Please answer me quickly I need my cell phone as fast as possible.
 

lloydsw

Senior Member
Feb 19, 2012
207
31
OnePlus 8T
Samsung Galaxy Tab S8
do you happen to have instructions for that process?
Yeah, I posted my comment on the wrong thread. This thread is the one I followed to convert TMO to international. This is the thread I used to convert back. Sorry about that!

 

Timmmmaaahh!

Senior Moderator
Staff member
Sep 11, 2012
5,657
1
13,743
Bruges
OnePlus One
OnePlus 6T
┤Thread Cleaned├
Password protected files should always raise a red flag and since it eventually lead to another development forum I am compelled to share the following:
11. Don’t post with the intention of selling something.
  • Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and to offer support, but not to post with the intention of selling. This includes promoting sites similar / substantially similar to XDA-Developers.com.
  • Do not post press releases, announcements, links to trial software or commercial services, unless you’re posting an exclusive release for XDA-Developers.com.
  • Encouraging members to participate in forum activities on other phone related sites is prohibited.
  • Off-site downloads are permitted if the site is non-commercial and does not require registration.
  • Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if both of the following conditions are met:
    A) The site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership, who actively maintains an XDA-Developers support thread(s) / posts, related to the download.
    B) The site is a relatively small, personal website without commercial advertising / links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)

    Read more...
If there is a useful file to share, make sure it is accessible to everyone. Thank you for your understanding. If you feel the need to discuss this, please drop me a PM.

Have a wonderful Monday everyone!
Timmy
 
Quick question... I have to do this to an OP 8T - use MSM to reflash the original system partitions. The MSM tool located in the 8T forum comes up with various trojans when running the 3 MSM exe files through the virustotal website's file scan. Even the .dll comes up with a warning. The msm tool in this forum does not.

Can I use the msm.exe tool in this forum, but use the 8T file payload from the 8T forum to reflash my 8T to factory? Are they compatible or is each MSM tool unique to an OP phone version? TIA.
 
Jan 24, 2011
16
0
Hello. Please help.
I did some tests on my OP6T and now I can not restore with msmdownloadtool.
I get Firehose firehose read data errno: "31"
I even tried reinstall computer with win10.
I now have a broken linageos 18.1 and recovery.
I failed to install twrp, i got qualcomm crashdump.
Now I would like to go back to stock. Even though it lags.
Please advise.
Regards
*/HEnrik
 
Last edited:

OnePlusFan88

New member
Apr 6, 2022
1
0
Hello. Please help.
I did some tests on my OP6T and now I can not restore with msmdownloadtool.
I get Firehose firehose read data errno: "31"
I even tried reinstall computer with win10.
I now have a broken linageos 18.1 and recovery.
I failed to install twrp, i got qualcomm crashdump.
Now I would like to go back to stock. Even though it lags.
Please advise.
Regards
*/HEnrik
I think we got the same error when i tried to flash twrp few days ago. Just flash the lineageos recovery in fast boot mode
 

tutakanemm

Senior Member
Been struggling with getting my phone back up and running since yesterday. Anyone ever ran into this issue before?

View attachment 5456703

I get this no matter which version of theMSMdownload tool I use. I've tried flashing several different versions with fastboot, each one taking me to the Crash Dump mode screen.

View attachment 5456705
Use the patched file to run the MSM tool, its on OPs comment, named MsmDownloadTool V4.0_factory_patched.exe download that and flash itll bypass those checks restricting you and convert to international version.
 

eagleshigh5

New member
Dec 12, 2021
3
0
Hi All,
my Wifi will not work despite restoring using either the .12 and .13 versions of MSM tool. Has anyone encountered this or knows of a solution please?
 

ChenYuanKai

Member
Nov 16, 2021
9
0
My phone is T-Moblie OnePlus 6T, model number is A6013, network lock has been removed! OxygenOS9.0.11 wants to upgrade android 10, is that ok?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 171
    This tool can be used to revive a bricked OP6T and remove the 'Device is corrupt' error message on boot.

    Contains the latest MsmDownloadTool v4.0.59 and OOS v9.0.13 which is compatible with International and McLaren editions.

    OOS v9.0.11 can also be used to convert a T-Mobile model into a fully fledged International model, more info here.

    1. Make sure that your phone is switched off.
    2. Open device manager on your Windows PC.
    3. Press and hold the Volume Up & Volume Down buttons then connect to your PC using your data cable.
    4. Once the device is connected to your Windows PC, check if the phone is being recognized (Other > QUSB_BULK or Ports > Qualcomm).
    5. If showing as Other > QUSB_BULK either wait for Windows to install the Qualcomm driver or download one of the drivers below and install.
    6. Run MsmDownloadTool V4.0 and click Start.
    NOTE: This will completely wipe your device and relock your bootloader.

    Downloads
    6T MsmDownloadTool v4.0.59 (OOS v9.0.13)
    6T MsmDownloadTool v4.0.58 (OOS v9.0.12)
    6T MsmDownloadTool v4.0.58 (OOS v9.0.11)
    6T MsmDownloadTool v4.0.58 (OOS v9.0.6)
    6T MsmDownloadTool v4.0.58 (OOS v9.0.5)
    Driver
    Alternative driver

    Shameless plugs - OP referral link for any peops that would like $20/£20/€20 discount: OnePlus or PayPal donation link: PayPal.
    15
    My observations from my journey (Fastboot only, Bootloader Locked):
    1) made sure my Windows computer was in test mode (powershell... bcdedit... find the instructions on how to do this). SUCCESS!
    2) Phone kept going into Fastboot mode whenever plugged in -> found a thread that mentioned forcing it off by holding Power + BOTH Volume buttons (10 seconds). SUCCESS!
    3) got Qualcomm drivers to recognize phone when plugged into PC = allowed my device to be seen from MSM tool (along the way, downloaded and used both OP drivers in 1st post - maybe it helped, maybe not). SUCCESS!
    3) In the MSM tool, I would get the "sahara communication failed". Unplug phone and plug in, MSM starts again, but gets another "sahara" message. Repeat dozens of times, to no avail. FAIL!
    4) Was using the OOS 9.0.13 file and MSM tool, but read a thread that suggested using an older set, so I switched to using the OOS 9.0.5 file and MSM tool. Get another "sahara" message FAIL!
    5) Followed some suggestions to hold volume up and power button (not sure why). Phone goes into Fastboot mode, and the phone would only register as Android Bootloader Interface when Fastboot was on. Could not upload any other driver for it to work. FAIL!

    So: The phone is in Fastboot mode, is still plugged into the computer; the MSM tool from the 9.0.5 tool is still open, still set on "Sahara" error message from before; I have loaded both Qualcomm drivers the OP has listed in post #1, yet the phone still reads as "Android Bootloader Interface" and not Qualcomm when in Fastboot mode. FAIL! FAIL! FAIL!

    6) Turned off phone by holding down Power + BOTH Volume buttons (because anything else forces the phone back into Fastboot mode because it is plugged in!) and suddenly the MSM tool starts downloading the appropriate files to fix my phone. SWEET SUCCESS!!!!!!

    This post is mainly to help myself in the future should another brick happen, but to help others as well learn from my mistakes. I read a lot of posts and started inching closer and closer to my ultimate goal of full stock restoration - thank you to all at the XDA community and Youtube as well. But this post is also to illustrate that not everyone's situation is the same, and it can be incredibly frustrating when your situation does not fit the bill.

    Thanks to everyone, and good luck with yours!
    9
    TMO

    I did a dump of every partition, except data, the second I unlocked my bootloader.

    Well, it isn't RSA signing that is bricking the TMO version -- the certs are identical. What is interesting is this:

    Code:
    1423:d=5  hl=2 l=   3 prim: OBJECT            :organizationalUnitName
    1428:d=5  hl=2 l=  42 prim: PRINTABLESTRING   :General Use Test Key (for testing 13 only)

    The question is, is that the Google test cert? If so, you guys lucked out and can sign your own firmware.

    Sorry I can't explain the bricks, but it is most definitely not due to different RSA signatures.

    -- Brian
    8
    U mean not to flash otas and critical?? Full rom imgs have proven to work..my only concern is if critical is updated by OnePlus in the future and they make it mandatory to have a certain version of critical in order to boot new firmware. In which case then tmo users are stuck till tmo itself issues updates.

    Sent from my ONEPLUS A6013 using Tapatalk

    If by critical you mean, the bootloader, modem firmware, trust zone, etc.... yes, those are the ones that are RSA signed.

    If someone wants to dump xbl_a from both the TMO and international versions, I will be glad to double check .. maybe TMO had a change of heart with the OP6t.

    FYI - I don't own the phone, just trying to help people keep from bricking their devices.

    -- Brian
    8
    @Dark Nightmare & @hartleyshc I've got TWRP now decrypting correctly. Anyone wanna brave the waters and test?

    Edit: False alarm. Gimme a little bit to figure something out!