General [OPN200][OOS 17AA] 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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.

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

DE17AA tools (global firmware):


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

edale1

Senior Member
Sep 5, 2016
135
72
Wait... We finally got MSMTools for the Unlocked variant? When'd/How'd this happen?
 

drfsupercenter

Senior Member
Aug 21, 2010
84
14
It seems like oneplus finally released the msmtool for global/unlocked version.

Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):

Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.

After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.

The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
 
Last edited:
  • Like
Reactions: Vortell
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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.

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

DE17AA tools (global firmware):


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:
@drfsupercenter for testing 11.0.3 version on his device
Votton for providing a server as an alternative mirror
OnePlus for the device and OS
great thanks lol
 
It seems like oneplus finally released the msmtool for global/unlocked version.

Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):

Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.

After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.

The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
I changed everything related to project ID and everything in that post, but mine still says
1657050276926.png
 
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).

Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.

I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
 
Last edited:
You didn't follow the instructions correctly.
Re-read the instructions, especially the editing project id step.
The error message mentioned "image 2083c", which means there are lines from 2083c ops not replaced with values from 20818 ops yet.
You need to replace all those lines:
BasicInfo Project=
Version=
ModelVerifyPrjName=
ModelVerifyRandom=
ModelVerifyHashToken=
in the settings.xml from unlocked 2083c ops with the values in the settings.xml from metro/tmo 20818 ops. (better to use copy&paste to avoid typos).

Also you need to copy the modified unlocked/global ops to the msmtool folder of the metro/tmo version and replace the original metro/tmo ops.

I believe 2083c is the unlocked version and 20818 is the metro/tmo version.
I can't tell what's wrong.

XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="0" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="anxKohPaJKUq2kVPIbXgD7RXNa96iUeGFZa1GzbYH6OIorf7RCneJCCgkJlSlN" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-77" BuildTime="1631716601" ApplicantIP="not sure if this is sensitive" />

Everything you listed is changed, the unlocked ops is also put into the tmobile msm

for example, here's the tmobile one
XML:
<BasicInfo Project="20818" TargetName="SM4350" Version="dre8t_10_O.05_210713" MemoryName="ufs" GrowLastPartToFillDisk="true" LogEnable="false" LogPositionIndex="-1" DelayStartTime="0" UseGPT="true" CheckImage="false" CheckHwVersion="false" NeedUsbDownload="true" BackupPart="false" BackupPartId="" ChipType="1" FactoryID="20818US" MinToolVersion="5.0.3" SupportHwID="false" SupportRfID="false" SupportPrjID="false" CheckRfVersion="false" CheckProjectVersion="false" SkipImgSHA256Check="true" ParamVersion="1" SkipParamProcess="false" ModelVerifyVersion="0" ModelVerifyPrjName="" SkipCheckHWVerByCustFlag="false" DefaultCleanFRP="true" FrpPartitionLabel="frp" CarrierID="1" CarrierNoneEnable="true" AutoDetectDDR="false" DPPackingVer="0" ProjectSoftwareIDSupport="false" ATOBuild="false" SkipMultiImageIdentify="true" RandomPadding="CQLTBL0oxs4BM2pdtK1y8Q1rvzgUtd033KWDfU1dM3mh3bKuwJs4jrtcqa6iB7lERIP4kOf5RRmS16MxPDz74tjvRq" ModelVerifyRandom="RG8sc2EUOj51TeCw" ModelVerifyHashToken="F9417334897C488DEA1DA5AC787906F743E85C17B47EB9669FFE96F11529D33C" Applicant="Unknown" Hostname="rd-build-74" BuildTime="1626183302" ApplicantIP="eeeeeeee" />
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    edit2: is this the right thread if i want to rollback t-mobile to 11? i am so confused and just want to find the simplest way to rollback with a boot locked t-mobile version.
    I think you want this thread:
  • 3
    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 is the EDL package (also known as MSM tool or unbrick tool) that can revive a bricked OnePlus Nord N200.

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

    DE17AA tools (global firmware):


    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:
    @drfsupercenter for testing 11.0.3 version on his device
    Votton for providing a server as an alternative mirror
    OnePlus for the device and OS
    1
    I can confirm this works for the "unlocked" version that I bought at Best Buy. Thanks for posting!
    1
    It seems like oneplus finally released the msmtool for global/unlocked version.

    Follow this guide to flash global/international unlocked firmware to metro/tmo version with locked bootloader (convert metro/tmo version to an unlocked international/global version):

    Basically, you need to change a few lines inside "settings.xml" about the project id so that it would not complain about non-matching project id/wrong model when cross flashing global rom to metro/tmo hardware.

    After crossflashing global rom to metro/tmo verion of hardware, it can then take international ota so it will behave exactly like the unlocked version.

    The only difference is about unlocking bootloader, and you will still need to go through the oneplus/T-Mobile portal to request the bootloader unlock bin to unlock the bootloader, while the true unlocked version doesn't need.
    1
    edit2: is this the right thread if i want to rollback t-mobile to 11? i am so confused and just want to find the simplest way to rollback with a boot locked t-mobile version.
    I think you want this thread: