[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL

Search This thread
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.

IT DOES THE WORK!!!!!
After that the Phone restarts. directly switch off again. When off hold volume + and - again while you plugin the usb cable. now it should work. ;)
 

Mersine

Senior Member
Sep 13, 2012
141
24
Cali
Gaaaah I've never been this stuck before in all my bricking experience!!

1659660562335.png



Edit:

This morning it worked 🤣🥳

1659710897212.png

These are the best written instructions I've ever read.
 

Attachments

  • 1659710869584.png
    1659710869584.png
    26.5 KB · Views: 61
  • 1659710880036.png
    1659710880036.png
    23.5 KB · Views: 70
Last edited:

ewong3

Senior Member
May 28, 2015
235
49
sometimes you need an old pc with usb2 instead of the most up to date one with usb3 port - this worked for me
 

i_pk_pjers_i

Senior Member
Jun 8, 2015
259
72
FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
When you get the error, DONT DISCONNECT!!!!!!!!
Just PRess (VOLUME+) + Power Button and hold for few seconds.

IT DOES THE WORK!!!!!
Yep, this did the trick for me! I have a OnePlus 7 pro that I hard bricked (wouldn't even get to fastboot!!), it kept getting stuck at "Saraha Communication Failed", once I got to that error keeping Volume+ and Power Button held until it started flashing successfully did the trick for me. It even worked on the USB 3 ports of my Windows 10 laptop. Thanks so much!

I can't remember having this much trouble with MSM back in June 2021 but oh well lol at least it works again thanks to you!

It's honestly kind of wild how fragile this software is but at least there's great tooling like MSM to recover these situations.

edit: Just had to restore my OP7Pro again (went back to a clean LineageOS 18.1 with pico opengapps, it still reboots randomly every few minutes just like my OP5 on LineageOS 18.1 does too so a clean install didn't help), this time when it got stuck at "Saraha Communication Failed" the Volume+ and Power Button trick didn't work for me, I had to Volume+ and Volume- and Power Button all 3 at once for it to get past that error. I ended up using a new MSM to restore Android 11 instead of Android 9 this time, but the old MSM still had the same "Saraha Communication Failed" Volume+ and Power Button trick not working this time around too. This software is so fragile and random but at least it works eventually. I'm going to stick with OOS 11 stock for a while and see how things go, my days of custom ROMs and rooting may be over, at least for now.

edit 2: My OnePlus 5 on LOS 18.1 automatically reboots and my OnePlus 7 Pro on stock OOS 11 automatically reboots, both like every 5 minutes, what the hell is going on lol?

edit 3: The reboots on my stock OOS 11 OnePlus 7 Pro have become less frequent and as of today have stopped entirely. I'm probably going to stick with stock for quite a few months longer at this point but what a weird issue.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    FIX - PRESS (VOLUME+) + (VOLUME -) and connect the phone in EDL mode.
    When you get the error, DONT DISCONNECT!!!!!!!!
    Just PRess (VOLUME+) + Power Button and hold for few seconds.

    IT DOES THE WORK!!!!!
    3
    So, my phone's bricked - it won't boot, just brings up fastboot. As the solution to this problem appears to be to use the MSM tool to do an "actual" factory reset, I downloaded the MSM tool, and the decrypted ROM from this link: https://androidfilehost.com/?fid=8889791610682918291.

    First I tried this on a Windows 7 VirtualBox VM (I use Ubuntu on my actual computer). The drivers didn't even install right it seems, and the device (in EDL mode) wasn't even recognized. Then I tried it on my mom's Windows 10 laptop. MSM never showed the device as connected. I think possibly the lack of a USB 2 port could be the cause.

    Finally I set up a basic VM with Windows 10 and a USB 2 controller, and it worked-ish. MSM recognized the device, showed it as connected and started doing its thing, but stopped at "Sahara Communication failed". What is preventing it from getting past this? I'm using the cable provided in the box. Everything is recognized correctly. I've retried multiple times but still the same result.


    SUCCESS!
    I had a spare laptop lying around, and it has USB 2 ports. I loaded WIndows 10 onto it and tried the MSM from there -- AND IT WORKED!

    As much as I hate Qualcomm for their monopolistic business practices, I thank them for EDL mode. I also thank OnePlus for somehow failing to prevent the MSM tool from entering the hands of the public every time, and @Some_Random_Username for trafficking this good. Yeet!
    2
    Gaaaah I've never been this stuck before in all my bricking experience!!

    1659660562335.png



    Edit:

    This morning it worked 🤣🥳

    1659710897212.png

    These are the best written instructions I've ever read.
    1
    The USB controller is part of VirtualBox. I think you need to download and install the extensions pack for the USB 2.0 version. The problem is that the controller is not capable of the absolute direct communication that the software needs to work, or it just doesn't connect fast enough. This would be a great example of why Windows on a USB would be great, since you could just boot it. But then MS wouldn't be able to make its billions. So we lose.

    I'd try VMWare and KVM to see if they do any better. I'm not sure if WINE supports USB passthrough or not. Otherwise try to find a Windows box you can use.