I hard bricked my OnePlus 9 (LE2113) while I was trying to unlock the bootloader. I tried flashing with Global, EU and Indian variants of MSM Tools but none of them worked.
I'm holding Power and Vol Up to reboot, then I hold Up and Down Volume buttons, plug in with USB cable and start MSM Tool. Every time I try to flash with "Use LIte Firehose" unchecked I always get the "Sahara communication" error at exactly 18 seconds. With "Use LIte Firehose" checked however download completes normally but phone is still hard bricked. This happened on every MSM Tool I tried.
I tried this on two laptops (Win 10 with USB 2.0 ports & WIn 11 with USB 3.0 ports) but ended up with the same results. I'm also using official cable. I have Qualcomm drivers installed.
Can anyone help me? Phone is hard bricked. I can't access anything besides EDL.
Just noticed this thread after your comment in the MSM thread.
Please review my reply. In a nutshell, I bricked my OP9 to a point nothing would work, tried everything for days. Thankfully, EtherealRemnant told me about a specific MSMToolkit for Indian OP9Pros that would get my phone up and running and then be able to flash a proper OP9.
I just compressed it and uploaded it for you, in case you haven't grabbed it yet. Its hosted on mega, so the download should be acceptable wherever you reside on this dirty space ball we call home.
IndianOP9-ProMSM aka The Last Hope
And again, good luck, you got this!
applyscience said:
Just noticed this thread after your comment in the MSM thread.
Please review my reply. In a nutshell, I bricked my OP9 to a point nothing would work, tried everything for days. Thankfully, EtherealRemnant told me about a specific MSMToolkit for Indian OP9Pros that would get my phone up and running and then be able to flash a proper OP9.
I just compressed it and uploaded it for you, in case you haven't grabbed it yet. Its hosted on mega, so the download should be acceptable wherever you reside on this dirty space ball we call home.
IndianOP9-ProMSM aka The Last Hope
And again, good luck, you got this!
Click to expand...
Click to collapse
I managed to flash with Lite Firehose but phone is still dead. I had some issues with phone being recognized but it somehow connected. I have also noticed that device under Ports (COM & LPT) is being recognized even after unpluging the phone, weirdly.
deleted because double post sorry
your device is an eu model i would not answer it with the india msm tool or the modded msm tool, you should get it to work with the eu msm tool
I don't know to what extent the modded msm tool has been processed (my concern is that if certain data on the mobile phone is changed from eu to india, I am concerned that the eu msm tool will no longer work with the eu mobile phone afterwards because certain data now identify cell phone as india model)
Related
I have an extremely big problem, maybe someone could help me here?
So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.
Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.
I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
Rayekk said:
I have an extremely big problem, maybe someone could help me here?
So today I tried to flash diffrent OOS version on my OnePlus 9, I did it with fastboot, after the command "fastboot reboot fastboot" the screen on the phone went blank and there was a sound on the computer as if the phone was still connecting and disconnecting. Now, the phone does not respond to the buttons, the charger, I cannot enter the fastboot, only the EDL mode works, but I cannot use the MSM because it does not detect the phone, I get the "sahara communication failed" notification all the time, previously the same MSM version was working.
Probably the most important thing is that it turned out that the OOS I tried to flash was actually ColorOS, I didn't pay attention to it, I don't know how it happened.
I feel like an idiot, I'm afraid that I will not save this phone myself and that the repair service will also not accept it under warranty, any suggestions?
Click to expand...
Click to collapse
See link below. Worked for me I was in same position.
ctonylee1965 said:
See link below. Worked for me I was in same position.
Click to expand...
Click to collapse
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Rayekk said:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Click to expand...
Click to collapse
Make sure you look at the rest of the instructions to get back on global from Indian.
Rayekk said:
Thank you very much! Tbh I can't understand how and why it works, but it worked!
Click to expand...
Click to collapse
Brother what is your phone model is it Chinese (Le2110)? or another model ?
bro i have the same issues , did u found any solution & can you help me plz
See if these steps work for you: (last post)
Display becomes unresponsive after OOS 12 update
I upgraded my OnePlus 9 LE2115 from OOS 11 to OOS 12, and every time the phone reboots after completing the update, the touch screen is completely unresponsive, so it stays stuck at the lock screen forever. I upgraded from OOS 11.2.10.10 to OOS...
forum.xda-developers.com
Hey, i have hardbricked my OnePlus 9 and now i have the connect and disconnect-problem in the EDL-Mode. My Model is a Lahaina and i hope it is the same like a Lemonade or a OnePlus 9. I was on the latest Android 12 for the OP 9 before it gets bricked. How i bricked my phone: First i have unlocked the Bootloader and after that i was trying to boot into TWRP. The bootscreen from TWRP comes and the screen gets black and then into boot dump mode. okay, then i installed this: https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/unread and the message <awaiting any device> shows up and i disconnected my phone. After that my phone just shows black and on the pc it just shows up the "QDLoader" (yes, the driver is installed) . How i could bring my phone back to life and fix the partitionproblem/connect & disconnect problem. The MSM just shows "Status of Connection: N/A" and "Waiting for device". I am using an Laptop with Windows 10 on it and an intel chipset.
I think i have killed the partitioning of the oneplus by downgrading from A 12 to A 11. Thanks for your help. By the way: I have downloaded the MSM with Indian OS and I have still the same problem.
I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?
kischde said:
I´ve got exactly the same situation and problem as DerBaLu841... Anything to do for now or is the OP9 finally hard bricked now..?
Click to expand...
Click to collapse
Check this out:
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
DerBaLu841 said:
Check this out:
MSM cannot recognize your phone aka. Sahara Connection error? Check this.
Hi! Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore. I tried everything, from different MSM tools to this thread. Nothing. Then, Deus ex Machina, @flameteam recommended me to try...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi! Have you telegram? Can I ask to you help with the method you posted?
I have a hard bricked OP9 and have tried alot of different guides from here or other ressources.
The problem is somewhere in the process something is not supported and the how to dies there.
MSM download tool prompts that says "Packed image not exists!"
OP9 LE2113 version (EU Version i guess)
Phone is black screen and can not be detected through ADB or fastboot. Either through the Qualcomm HS-USB QDloader 9008 Drivers.
Before it bricked it was unlocked (bootloader) Not sure it is anymore
Can someone send me a link or guide that can guide me the right direction?
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Ill try that this evening, ill let u know ill turn out.
I typically run into sahara connection because i dont have connection through ADB of fastboot
#gorilla p
Try the Oneplus 9 Pro India recovery tool. I know it doesnt make sense, but its the only thing that has worked for many, including myself and I have a OP9 5G North America.
Once recovered, the OS will boot but buggy. You can then restore to correct image via twrp full zip
Click to expand...
Click to collapse
i have used this link
https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_9_Pro/ India version
And at the moment it is booting.
Unticked reboot and SHA check, This is indeed a good day !
Ive got a working phone again,
I will mark this thread as solved
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Raccroc said:
Don't like Android v.12 at all, so decided to test our a v 13 build. Even worse. So, decided to roll back to v11... something very bad happened along the way.
After getting the 11 dev version installed, I was installing another v11 rom and ended up with a Recovery boot loop,. Somewhere along the way while trying to fix that, my screen that will no longer come on at all. No vibrations or display no matter what I do.
Turns out, Windows could see it plugged in; albeit as Unknown Device (Device Descriptor Request Failed). After lots of holding down buttons, lots of driver installs, disabling windows signatures, lots of different USB cables, leaving it on the charger overnight, and trying both USB and the USB-C ports, I finally got it to go from Unknown Device to Qualcomm HS-USB QDLoader 9008.
Tried MSM, but after 10-12 seconds I would get Sahara communication failed.
Back to troubling shooting... Start MSM as amin, swap usb cables, test all ports, ect., no luck.
Somewhere along the way, it seemed to get even worst... now, after 10 seconds or so after plugging in the phone, it will disconnect, followed by reconnecting a few seconds later. It is being detected as as the Qualcomm and it shows the com port it is connected to, but the device will drop out of device manager every few seconds before reconnecting. It is acting like it is in some soft of EDL bootloop.
I tried uninstalling the Qualcomm drivers and tried several different driver versions ( unsigned 2.1.0.5, Authenticode Signed 2.1.1.2, and Digitally Signed 2.1.2.2).
Outside of that, I am at a complete loss of what to try or do. Any suggestions?
Click to expand...
Click to collapse
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
mattie_49 said:
First try and go ahead and pick target and the start button on MSM tool. Then try the 3 button combo till it reboots edl. When MSM tool connects it should start process without rebooting device.
Click to expand...
Click to collapse
So, that actually stablized the driver connection; however, it also brought be right back to Sahara Communication Failed.
Progress (I hope)!
Thread '[Solved!] MSM Download Tool Issues - Sahara Communication failed, phone exits EDL' https://forum.xda-developers.com/t/...communication-failed-phone-exits-edl.4245913/
Thanks for the info and links. I am on Windows 11, which seems to be an issue for some. I will see about trying it on my wife's v10 laptop tonight and see if that changes anything.
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Raccroc said:
Solved!
Three button reboots and then both volume buttons to get back to EDL as soon as the driver dropped seemed to work. Took a few tries (on Win 11 using original usb-c cable) but it installed the rom and booted up.
'course, now is on an India variant, so I still gotta get back to LE2115, but that is another story for another thread.
Click to expand...
Click to collapse
There is a global msm with target id india
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
rizzmughal said:
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
I know thats when ur phone was hard bricked now this one will work for u to get back to global 2115
Raccroc said:
Thanks for the link, I will give that a go.
Most of the MSM packages I could find for the LE2115 specifically either were bad links or had viruses. I did find a global version, which is what I was originally trying to use; however, when I finally got past my other issues, it gave me some sort of hardware version mismatch error in MSM (don't remember the exact message).
Somewhere along the way, someone suggested the India version. That one worked and I wasn't going to quibble at the time, as my main concern was just getting the lights to come back on.
Now I have a phone with a working display, that is my next todo...
Click to expand...
Click to collapse
Index of /list/Unbrick_Tools
These are def not viruses and windows has warned me of these as well on Win 11. Just accept and install. These are legit af
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Raccroc said:
Completely back up and running again. Ran into the touchscreen issue, but fixed by using the linked Global MSM above.
As an FYI: the virus issue was from a FizzyAps post linking MSM for LE2115 on a Google Drive share. Couldn't download the file because it didn't pass Google's virus scan.
https://forum.xda-developers.com/t/global-oneplus-9-msm-tool-updated.4284779/
Click to expand...
Click to collapse
Good deal. That's all we here for neway is to help one another.
Hello . I have OnePlus 7 pro I update it to android 12 and the next day something went wrong and my phone started an error Qualcomm crash dump something... Now it is stuck in EDL . Display none , power key And volume key works but keep booting in EDL even without connecting the USB cable . I flash the firmware with msm tool firmware flashed %100 but it didn't boot still in EDL .can someone guide me how to fix it
Can someone help!
jahanzaiblohani said:
Can someone help!
Click to expand...
Click to collapse
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
darksx said:
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
Click to expand...
Click to collapse
Drivers are correct and I was flashing it with USB 3.0 port .
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
KyRol said:
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
Click to expand...
Click to collapse
I have the old stock ROM which I flashed it in EDL but phone didn't boot when it is completed phone reboot too but not in normal mode in EDL again
Most often people have bad experience with qualcomm drivers. So make sure that you have some released after 2020 year, as oneplus 7 pro was released in 2020 year. Another issue is related to usb 3.x, better avoid that and try USB 2.0 instead, most of people have best results with older interface of that kind. EDL is kind of old solution, so better to stay away with USB 3.x and use USB 2.0.
Have you got any idea your flash is successful in edl tool? Have you got clean results or warnings/errors?
To be honest with you, I have to use EDL too, because I did wrong upgrade. I used custom ROM instead of stock ROM. Now I have not access to fastboot nor adb via USB either.
try different EDL ROMs, I found 2 threads. one is here, second there. As almost nobody anserws our questions, I will let you know what I did if I do it successfully.
Well, I discovered that I'm in pretty bad situation. In my case not only adb and fastboot does not works. It appears that EDL does not work either. Why? because I connected another oneplus phone over USB to PC and EDL mode was detected spot on. In case my o+7pro, well still same error as previously with adb/fastboot over USB. Something messed with USB on my phone at software side.
So I have to get motherboard get cheap. I do not thik that I can desolder flash or eMMC and revert that so easy.
Sorry Man, can not help you any
further. Turns out my issue is signifigantly other than yours.
Trying to flash my friend's phone back to stock but having some issues, you might have seen twixyfig's post in the OnePlus 9 Pro threads, but it's a regular OP9 and not the Pro.
Anyways, I have been trying to flash to working condition but MSM won't help. It keeps saying "No valid trg ID" and "Param preload" for a while now. This happened because we tried to root the phone but failed. The bootloader is unlocked, and fastboot works too.
TIA.
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
shadabkiani said:
Whenever you post asking for help, always make sure to add as many details as possible. Your phone model, variant, current firmware, the tool you are using, the tools you used before, the steps you took before you started facing issues, every detail you can possibly tell. Only then someone might be able to help.
Click to expand...
Click to collapse
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
twixyfig said:
So its a oneplus 9 (Chinese model), before it got bricked it was on android 12, we tried MSM V5.1.89 and CMD, cmd said " No boot.img found "
Click to expand...
Click to collapse
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
shadabkiani said:
Download the MSM Tool (Global) from this link. Global works on Chinese variant (LE2110) too. Have proper drivers OnePlus drivers installed. Turn off your phone and set it aside, do not connect to PC yet. Run the MSM Tool exe file. Once its loaded, click Start and it should wait for device. Now on your phone, hold vol+ and vol- buttons (no power button), and connect the cable to phone. This will make the phone enter EDL mode. The PC would recognize the device (USB plugged in sound) but phone screen would still be black. On MSM, the flashing would start and would be done in about 4-5 mins. Good luck.
Click to expand...
Click to collapse
Thanks! Im gonna try this today and give you an update when something happens
twixyfig said:
Thanks! Im gonna try this today and give you an update when something happens
Click to expand...
Click to collapse
I think you were trying Indian MSM Tool. That might be the problem.
When your open MSM Tool, choose Others as login.
Write me in dm and I will help you, I think I can solve your problem
you can download OP9PRO India MSM tool(OnePlus_9_Pro_India_OxygenOS_11.2.4.4) and
1.unzip OP9Pro India ROM and download to your phone(select the firhose chebox)
2.if you success to download it,your phone will restart to the OOS.
3.Login your Google account and unlock OEM,then reboot your phone
4. install "Oxygen Updater", VERSION 5.7.3，you can find it on github.
5.download OOS for OP9 , archive name is "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip"
6.enter the oxygen updater,and flash "1797d47ddef0fca1411fb006b9c7a1a7ba33d818.zip" to your phone
7.reboot and fixed!
PS: my english is so suck,try to read it!
good luck!