• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[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
524
108
23
Spain
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?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 164
    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.
    13
    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!