• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[OPN100][OOS 81AA/83BA] Unbrick tool to restore your device to OxygenOS

Search This thread
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 and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.

You should 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 :)

Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.

BE81AA tools (global firmware):

ANDROID 10:



BE83BA tools (european firmware):

ANDROID 10:



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.

How can I check my device project ID?

Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.

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:
@lsthps for testing 10.5.2 BA version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
 
Last edited:

yandere2016

Member
Nov 5, 2018
7
0
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 and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.

You should 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 :)

Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.

BE81AA tools (global firmware):


ANDROID 10:

OOS 10.5.3

Mirror for first and last MSMs: https://onepluscommunityserver.com/



BE83BA tools (european firmware):

ANDROID 10:



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.

How can I check my device project ID?

Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.

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:
@lsthps for testing 10.5.2 BA version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
Can you add OOS 10.5.7?
 

Ralyks

Member
Aug 1, 2017
5
0
So I've been trying to root my device and bricked it by using a process that won't work on my HD1907 T-Mobile Variant. Tried a few different methods and finally was able to get ADB/Fastboot to recognize my device as an "Android Device" by installing the OnePlus drivers for my phone. Well, now it's not working at all. Can't turn off the phone to get it into EDL since it just automatically boots up on it's own, but I can get it back into Fastboot mode. What sux is that I can't seem to get ADB to recognize the device anymore. Also, I haven't been able to use this method since my device shows up in Device Manager as an "Android Device", not the "QHUSB_BULK" that you mentioned in the post. Any tips on getting this method to work? Should I be able to just uninstall the OnePlus drivers and Install the Qualcomm drivers instead? Is there a way to get ADB to recognize my device and then try to flash a stock OS to the device that way?

Please, any advice would really be greatly appreciated.
 

jgardner7289

New member
Jul 21, 2018
1
0
Thanks, you are a lifesaver! I got myself into a weird position when trying to install Magisk (flashed the wrong boot.img) and this saved me. I got my phone from Amazon (listed as "OnePlus Nord N100 Midnight Frost Unlocked Smartphone, 4GB+64GB, US Version, Model BE2011") and although it was not the T Mobile variant, the pre-installed image lacked the ability to flash a local update (the gear icon was absent in settings -> system -> system updates). Now I have flashed stock Oxygen OS and all is well. As a side question, any clue what kind of weird build it may have shipped with?
 

alexspecht

New member
Sep 19, 2015
4
0
THIS SAVED ME!

I just bought Nord N100 BE2011 from Best Buy (in California US)

I made the same mistake of extracting the updated boot.img 10.5.7 and patching it with Magisk without updating the rest of the system first. So the Boot partition was updated to 10.5.7 while the Oxygen OS and other modules were still on the stock 10.5.3

While the phone was rooted and I was able to install apps and google play etc.. the Phone and Voicemail Functions died with UI Error (SOFT BRICK)

This MSM Tool worked,

I did as the OP says, Download the File above (2.4 gb)

I downloaded the qualcomm drivers first from https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/

then boot to edl using adb command:

adb reboot edl

Check to see if phone shows up in device manager as QDLOADER 9008. It is under COM ports

Then unplug the phone leaving it in EDL mode and run the MSM tool

when executing the MSM application it will prompt for login select: "other" from drop down

once the MSM program shows up plug in the phone

It should indicate that it is connected

press start.

On first attempt i received Error and followed the OP:

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.

(to get it out of edl mode and into fastboot hold power and vol-up)

This worked and the download took 5 minutes.

Phone rebooted to factory settings (after being bricked) and I can receive calls

Cheers,
Alex
 

Assis Brandão

Senior Member
Sep 16, 2012
60
19
Sobral
I received the Android 11 update and Wifi stopped working perfectly with constant drops. My version is EU, so I used this tutorial to revert to Adroid 10 and Global, and it worked perfectly.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    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 and Nord N10 5G here are the EDL packages (also known as MSM tools or unbrick tools) that can revive a bricked OnePlus Nord N100.

    You should 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 :)

    Please note that on N10 crossflashing regional builds is no longer possible by EDL, flash is tied to device project ID. I therefore expect same to happen on N100. For reference EU devices project ID is 20883 while international devices project ID is 20881.

    BE81AA tools (global firmware):

    ANDROID 10:



    BE83BA tools (european firmware):

    ANDROID 10:



    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.

    How can I check my device project ID?

    Use getprop ro.boot.project_name. This however involve having ADB access or access to OxygenOS to use Termux or whatever terminal emulator you prefer.

    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:
    @lsthps for testing 10.5.2 BA version on his device
    Votton for providing a server as an alternative mirror
    OnePlus for the device and OS
    1
    Worked great, thank you! Just one click and the device is back to life. Awesome!
    1
    Added MSM tool for global build (10.5.3 BE81AA).
    1
    Do you happen to have the Metro branded MSM tool?
    Unfortunately no but feel free to DM me so that I can tell you how you can try to obtain it.
    1
    Added OOS 10.5.7 (EU) and 10.5.5 (global) MSMs