Develop Bugs

[OPN105G][OOS TMO BE88CB] Unbrick tool to restore your device to OxygenOS

Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to the previous threads for
OP3, OP3T, OP5, OP5T, OP6, OP6T, OP7, OP7PRO, regular OP7T, T-Mobile OP7T, regular OP7TPRO, T-Mobile OP7TPro 5G, regular OP8, T-Mobile OP8, Verizon OP8, Visible OP8, OP8Pro, OP Nord, regular OP8T, T-Mobile OP8T, regular OPN10 5G and regular OPN100 here is the EDL package (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N10 bought from T-Mobile.
As this is a carrier specific MSM, it will only work with BE2028 model with build tag BE88CB
You should also be able to rollback your phone to a previous release of OOS with them if for some reason you want to go back to an older firmware
You can download the following versions:
ANDROID 10:
OOS 10.5.8
Mirror for first and last MSMs: https://onepluscommunityserver.com/
Instructions:
Launch MsmDownloadTool V4.0.exe.
On the login prompt select "Other" in the dropdown menu and click on Next.
Wait a few seconds until main window shows up.
Press Start button so that it waits for your device to be connected
Power off your device
Maintain volume up and down buttons to get into Qualcomm EDL mode.
Plug your device to your computer.
Should you not manage to do that and have adb access, you can use adb reboot edl instead
Wait ~300 seconds.
Enjoy your brand new device.
FAQ:
Does this work on Mac or on Linux?
Unfortunately no, tool is Windows only. You should need at least Windows 7.
Why is my antivirus freaking out when unzipping the archive or running the tool?
In an effort to protect reverse engineering from being done (and by extension prevent conversion process like it was done on 6T and 7Pro), OnePlus now use VM Protect V3 in their MSM tools. As this tries to detect debug environment, this is seen as malicious behaviour by some antivirus.
My device isn't detected
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsof...updateid=8ee52ba0-bdef-4009-88cf-335a678dd67a ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
If you can't get into EDL mode by hardware keys, you may use adb reboot edl (will require your phone to still have ADB access)
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
MSM tool is stuck on "Sahara communication failed"
Unplug your phone, get in fastboot mode, turn off phone, wait 15 secondes and get back in Qualcomm EDL mode. You can also try using a USB 2.0 port instead of a 3.0 one.
What is SMT Download mode?
Just don't try to unlock that mode, it will wipe your IMEI and your Widevine certificate if you use it.
How can I fix "SMT config not found" error?
Please refer to https://forum.xda-developers.com/showpost.php?p=83448961&postcount=61
Credits:
OnePlus for the device and OS

Reserved

I need this for the T-Mobile Variant.
- Works great! Thanks.

I learned a ton of hard lessons with this device. My maiden voyage of custom ROM and hackery. Now, unfortunately, I have to resort to a power greater than my own mind to restore my little N10 5G to sanity. Thank you for this post, and wish me luck,
Click to expand...
Click to collapse

Will the above work on the TMobile varent?

mbl1979 said:
Will the above work on the TMobile varent?
Click to expand...
Click to collapse
Duh

una ar oem aluna solucion

Can i use this to downgrade from 11 to 10..?

Fr4n©\<y said:
Can i use this to downgrade from 11 to 10..?
Click to expand...
Click to collapse
Yes. Moreover when boot to Android 10 and connect to WiFi it can be updated back to Android 11 ( through native update interface, did not check but got a prompt )

@Some_Random_Username
What if I have Unlocked Bootloader + TWRP + patched boot - will unbrick flashing restore these partitions to factory defaults ?
Will I lose bootloader unlock after flashing ?
Thank you

.

Testing

Would this also work on the Metro version?

Question Bricked and EDL doesn't work

It was only a matter of time before my first brick with this phone. Earlier this evening I tried to factory reset from TWRP and clean flash latest OOS, but it spewed out a whole bunch of partition errors. After various efforts, here's the current status: It won't boot to the OS from either slot. TWRP says no OS installed. On Slot A, it won't boot to recovery either, and the only thing I can get to is fastboot. On Slot B, I can get to TWRP recovery, but all storage is gone (and I've since done a full wipe so there's nothing on it anyway). Any attempts to do adb push or sideload result in the error "adb: error: failed to get feature set: no devices/emulators found", so I can't install anything unless there's another way I'm not aware of.
I'm trying to get into EDL by powering off the phone, then holding down both volume buttons while I plug in the USB cable. It shows up in Device Manager for about 2-3 seconds as "Qualcomm QDLOADER 9008" and then disappears for a second before going directly into fastboot. I've rebooted my computer to disable device driver signing and install the latest Qualcomm drivers per this guide, but the latest drivers are already installed. I've tried a different USB cable and a different USB port.
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?

terlynn4 said:
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
Click to expand...
Click to collapse
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.

Fishawy said:
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Click to expand...
Click to collapse
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.

terlynn4 said:
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
Click to expand...
Click to collapse
You don't have to stick to one model. You can use MSM of 11.2.2.2 EU or 11.2.4.4 India for example, then flash the stock update of a different region, as long as it's an upgrade not the same version.
I did upgrade from 11.0.6.6 AA to 11.0.8.8 EU locally on my 8 Pro. I would imagine it's the same, haven't tested it on my 9 Pro yet though.

I finally got it flashed back to OOS via TWRP and booting normally again. However, it concerns me that I couldn't ever get EDL working, in case I ever really need it. I'll have to keep working on that "just in case".
After trying several things in various orders, I reformatted /data, after which adb push started working. I was able to push the latest full .zip and after a couple more errors I was able to flash it to both slots and reinstall TWRP. I did get an error when I went to reboot that said something like "No OS installed... are you sure you want to reboot?" however it booted into the OS that time.
Anyway, thanks to those who offered suggestions. I'll update again if I ever figure out what's wrong with EDL.

Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.

Steve0007 said:
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Click to expand...
Click to collapse
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.

terlynn4 said:
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
Click to expand...
Click to collapse
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.

Samuel Holland said:
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Click to expand...
Click to collapse
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?

terlynn4 said:
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
Click to expand...
Click to collapse
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe

Samuel Holland said:
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Click to expand...
Click to collapse
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!

terlynn4 said:
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
Click to expand...
Click to collapse
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.

Fishawy said:
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Click to expand...
Click to collapse
The one that worked for me was the 32-bit setup.exe file from this guide. I uninstalled the existing driver I had installed, rebooted, installed this driver, and then EDL worked right away.

Question [SOLVED] Bricked OP9Pro, can't get to fastboot, sahara communication failed

Seems like I succesfully bricked my OP9Pro. Tried to restore in MSMDownloadTool v4.0. Oneplus 9 Pro LE2123.
Phone is detected correctly in Windows device manager(QDLoader 9008, I get to EDL by holding Vol+ and Vol- buttons and connecting the cable). When I try to flash, MSM breaks on Sahara communication failed(FH: 258).
Qualcomm drivers are from Windows Update Center(I connect my phone in EDL mode, click Update and in optional updates section there is the needed driver - Qualcomm Incorporated - Ports).
What should I do?
I saw a python EDL workaround script, but I'm not sure if helps me or if it even works (saw it somewhere on xda, the only thing I remember that it was in some of oneplus's devices thread and the sript name was edl.py, sorry
Tried on one laptop(Acer Nitro< none of the ports gave a succesful result). Gonna try on my second(Asus ROG GL702VMK, it seems to have better ports connection). Gonna write an update message.
I can't get to fastboot, recovery, etc. Phone seems to give no signs of life, there is even no charging notification when the cable is connected(but maybe phone isn't turned off actually, not sure)

You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using

Shooter7889 said:
You need to click the box to "use lite firehose" beforehand running your msm. And change target to OS or EU depending on which one ur using
Click to expand...
Click to collapse
Thanks for advice, I got further but now it stopped on Param Preload with "Device not match image"
I use MSMDownloadtool for EU and my phone is EU version(LE2123)

So, I am kinda happy cuz I booted to system.
I used this guide(https://forum.xda-developers.com/t/global-us-unbricking-guide.4370463/). Used MSM Download tool with Indian f/w.
Then I tried to return to EU version, but I got the same param preload error. I used this version of MSM and it flashed successfully.
So now I guess the issue is solved. Thanks @Shooter7889 for ur advice with lite firehose

Uncheck "check sha256" for mismatch device issue. Or find correct msm. You're welcome. I had same issue after bricking my 9pro and not being able to run msm successfully.

Question Bricked flashing Lineage and MSM will not work

Long story short, I was having tons of bugs in A12 from camera rebooting phone to not receiving phone calls so I decided to flash LOS 18.1 and ended up bricking my device presumably because I didn't downgrade to OOS11 beforehand. Currently, I can only enter fastboot and LOS recovery. MSM tool will not read my device at all. I can see it in device manager as some extremely generic QUS...... device and when I try to update the drivers, it crashes. I have tried USB-C, USB 3.2, USB-3, and what is presumably a USB 2.0 port to no avail. Is there anyway to flash OOS 11 from fastboot?

Use these drivers for the Qualcomm device, reboot the phone with both volume buttons and power.
Then try the MSM tool (remember to choose the regional version on the top), don't connect via a USB hub, connect directly to your computer (I usually find USB 2 is better than USB 3
If you get an error in the MSM Tools when you try to flash then reboot the phone back into EDL mode while the MSM tool is still open and attempting to flash, it'll usually pick up properly after the reboot.
If you still have problems then try disabling driver signature verification : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/

djsubterrain said:
Use these drivers for the Qualcomm device, reboot the phone with both volume buttons and power.
Click to expand...
Click to collapse
SWEET BABY JESUS THANK YOU FOR THIS
I was trying to do this with the 64-bit drivers and was consistently seeing "Param preload failed" after 9 seconds exactly.

ddxBrandon said:
SWEET BABY JESUS THANK YOU FOR THIS
I was trying to do this with the 64-bit drivers and was consistently seeing "Param preload failed" after 9 seconds exactly.
Click to expand...
Click to collapse
Up and running again?

djsubterrain said:
Up and running again?
Click to expand...
Click to collapse
I had the LE2127 unlocked and rooted (after learning about the MSM tool, the model differences, modem headaches, etc.)
My ultimate goal was to flash Lineage on it and use a custom kernel for battery life. But apparently I'd have to re-flash T-Mobile's firmware version NON-HLOS.BIN after every OTA, and frankly that's a pain in the ass.
I was trying to use the T-Mo MSM tool to get it back to stock locked, but that was stopping me. Finally got it done. T-Mo wouldn't take the phone back. Got a Pixel 6. The 9 Pro is on "free" promo anyway, so I might start messing with it more, or sell it / donate it to a developer.

Send it back to oneplus they have tools even better than msm.

djsubterrain said:
Use these drivers for the Qualcomm device, reboot the phone with both volume buttons and power.
Then try the MSM tool (remember to choose the regional version on the top), don't connect via a USB hub, connect directly to your computer (I usually find USB 2 is better than USB 3
If you get an error in the MSM Tools when you try to flash then reboot the phone back into EDL mode while the MSM tool is still open and attempting to flash, it'll usually pick up properly after the reboot.
If you still have problems then try disabling driver signature verification : https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Your instructions worked for Windows 11. I had to reboot with driver signature verification disabled in order for MSM tool to recognize the phone as connected.
Thank you.

[QUESTION] Device auto exits EDL Mode after 5 seconds [Solved]

UPDATE: The issue stands solved [see post 5].
........................................................................................................................................................................
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode as Qualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.

My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me

ohwarumbloss said:
My way was :
Launch MSM Tool
Launch Phone into Recovery
Connect USB Cable
Advanced -> allow ADB
On PC : adb reboot edl
As soon as the Device Screen turns black, Phone gets detected in MSM Tool and then Start Process. That worked for me
Click to expand...
Click to collapse
I face the same issue on my OnePlus 9 and this help me. Thank you so much.

binary**# said:
I am facing a rather intriguing issue wherein the device tends to automatically exit EDL Mode after around 5 seconds. During that short-time frame, the Device Manager recognizes it in EDL Mode asQualcomm HS-USB QDLoader 9008. Even the MSM Tool is able to identify the connected device. However, right after a few seconds the device gets booted to the OS.
So could anyone let me know why is this happening and more importantly how it could get rectified. [Windows Driver Signature Verification is disabled and Qualcomm USB Drivers are successfully installed].
Moreover, currently I'm on Pixel Experience ROM. So are custom ROM's known to cause any conflict with EDL Mode?
EDIT My device is not bricked and I could easily access the OS [Pixel Experience]. However, I still want to use MSM Tool as opposed to say, Fastboot Enhance Tool, for testing purpose. So any insights in this regard will be highly appreciable.
Click to expand...
Click to collapse
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.

raoakashyadav said:
were you able to find any work around. I am currently on OOS 12 F.22. I am having another issue of widevine L1 certification as my device has L3 certificate. To rectify this i am trying to use MSM tool.
Click to expand...
Click to collapse
Sorry for the delay in reply. Yup, I fixed this issue via the Disable Driver Signature Verification tweak as shown in this video. In short -->
Install Qualcomm USB Driver and download MSM Tool.
Boot your device to EDL Mode and connect it to your PC.
Then DO NOT disable Driver Signature Verification on your PC.
So as of now, your device will be listed as Qualcomm HS USB QDLoader under Device Manager but will have a yellow exclamation mark [because Drive Signature is enabled]. But at the same time, Windows will hold your device in this ELD Mode and wouldn't let it boot to the OS [which is what we wanted].
So while having your device connected to your PC in EDL Mode, now disable Driver Signature Verification. With this, your device should now stay in EDL Mode and will be listed without any yellow warning sign under Device Manager. You could now proceed ahead with the flashing via MSM Tool without any issues.