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

Search This thread

Niraj Prajapati

New member
Jun 14, 2021
1
0
hello all,

this androidfilehost urls are slow as hell and downloading keeps failing after 12-15 mb, can anyone share it via drive please? any version is okay. i just need to wake my OP6T device. It's URGENT please !!!

thanks
 

Kaneki

Senior Member
Sep 23, 2015
530
108
23
Spain
Xiaomi Mi Pad 5
Not works for me...

I followed all the steps and tried with diffferent cables but this message "Sahara communication failed, please try again after power off phone" and i already have my phone powered off...

Any help?
 

Shafin Uddin

Senior Member
May 21, 2013
186
26
Dhaka
Not works for me...

I followed all the steps and tried with diffferent cables but this message "Sahara communication failed, please try again after power off phone" and i already have my phone powered off...

Any help?

Try restarting your PC, had the same problem and a restart fixed it.
 

Everio9000

Senior Member
Jan 23, 2011
149
34
Alicante
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!

Thank you. I follow all your success and fails and I could restart my 6T. Thank you !!!
 

3MrBojangles3

Senior Member
Apr 30, 2021
131
20
OnePlus 7T
OnePlus 8T
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!
Your problem with the msm tool was that you were putting it into fastboot mode and running it. That is your problem. In order to use the msm you need to put the phone in EDL mode. Emergency Download I think it stands for. And you get it there by unplugging your phone, turning your phone off, and then by holding both volume buttons firmly and plugging in your cable while still holding the volume buttons down. That puts it into EDL mode. The screen doesnt come on. If it does then repeat the steps. You can hold the volume buttons down until you start the msm tool otherwise you only have like 10 seconds to start the tool before your phone powers up. If your phone ever won't turn on then hold down the power button and the volume up button and it will boot up. Takes 5-10 seconds
 

louis1642

New member
Sep 15, 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 downloaded the MSM tool from the first link (v4.0.59) but I could not open the .rar file neither with 7-zip nor with WinRar. So I downloaded v4.0.58, but same problem occurred. Any help?
 

Dadditz

Senior Member
Jun 28, 2017
633
366
MATRIX, build 7.22.06.14
OnePlus 6T
I downloaded the MSM tool from the first link (v4.0.59) but I could not open the .rar file neither with 7-zip nor with WinRar. So I downloaded v4.0.58, but same problem occurred. Any help?
Hi,
I downloaded version v4.0.59 just for trial
and it works perfectly.
Unzipped with 7zip without any problem.
(windows 7 system).
You may have some kind of problem
on your computer or the file
gets corrupted while downloading.
Try updating your programs
and check the MD5 when you download
the tool again.
Good luck. 🤞 :)
 
  • Like
Reactions: louis1642

JimFre

Member
Jul 30, 2013
29
2
This tool saved my old 6T and made it possible to get it back to stock so I can get it ready to be sold. Thanks to everyone writing their experiences. The thing that worked for me was getting the unit into EDL mode, I would never have figured that part out by myself
 

masulzen

New member
May 4, 2021
2
1
This tool saved my life, thank you so much.
To those having driver issues, I downloaded the first driver linked in OP and that made the device show up in the application.
I am using Windows 10.
OOS OTA updates did not show up after installation so I am using the 3rd party Oxygen Updater app to restore most recent OOS firmware.
Thanks again!
 

bradmillerbiz

Member
Jul 21, 2016
10
2
Can I use the latest version posted here (v4.0.59) to return to stock from LOS 18.1 (Android 11). Do I need to do anything different from the regular instructions? Thanks.
 

EngineManShawn

Senior Member
Jan 4, 2012
238
29
Scranton
OnePlus 6T
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.
Thank you for this wonderful quick and easy tutorial and the patched files. Device now working again!!
 

ptuner

Senior Member
Oct 3, 2020
69
0
Any guides out there getting your device to 11.1.1.1 after MSMing to 9.11?
 
Last edited:

bradmillerbiz

Member
Jul 21, 2016
10
2
I think I may be F'd. Got the "sahara comminication" error and now my phone wont turn on at all or even charge. Help, please?
 

Babelman

New member
Oct 5, 2021
3
1
Done this today, no problems, the immigration numbers are both the same? Any other changes recommended, can I use two sims? Any help welcome as I a new to this..
 

GWARslave119

Senior Member
Jan 29, 2017
294
17
40
Houston
OnePlus 6T
Been struggling with getting my phone back up and running since yesterday. Anyone ever ran into this issue before?

temp.png


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.

temp2.png
 

Top Liked Posts

  • 1
    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?
  • 1
    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?
  • 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!