[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS

Search This thread

fermion120

New member
Jan 19, 2011
1
1
Unfortunately, no MSM package works for me to unbrick my AC2003 (EU),
always get the error "device not match image"
Qualcomm Driver looks fine, Phone is in EDL mode and MSM tool seems to establish a connection to the device.
Tried also different firmware versions and also global region, with same result.
Has anyone an idea, how to fix this?

How i messed it up:
  • bought phone AC2003 in EU on Nov/2021 and upgraded to latest stock OOS 11 --> WORKED
  • unlocked bootloader and flashed to LineageOS 17.1 according installation guide --> WORKED
  • switched back to stock OOS EU 10.5.5 via FASTBOOT method --> WORKED!!
    • used a OOS 10.5.5 fastboot image because adb sideload with OOS 11 OTA zip did not work in LineageOS recovery, problem was, that device name did not match to image: "OnePlusNord" vs. "Nord"
  • locked bootloader again, as I assumed device has 100% stock firmware -> BRICKED!!
 
Last edited:
  • Like
Reactions: vvnpyr

mbootsman1

New member
Jan 10, 2022
3
1
OnePlus Nord
Thanks for all these tools everybody!
OnePlus Nord EU version here.
I have installed a custom ROM, was not happy, and want to go back to Stock ROM.

MSMDownloadTool gets connected to phone (Qualcomm HS-USB QDLoader 9008 on COM9)
When I reboot phone to EDL mode, it is detected in MSMDownloadTool. I select EU for target, and press start.

The process halts at "param preload failed".
Tried different versions of the MSM package, but none work. Any tips for me?
The attached screenshot shows target as O2, I have tried with EU versions too.
 

Attachments

  • msmfailed.png
    msmfailed.png
    24.5 KB · Views: 143
  • Like
Reactions: vvnpyr

Spectreunkown

New member
Jan 24, 2022
1
0
Hi OG Some_Random_Username. Thank your for your reply.

The specific OP7 Pro I have is GM1915, T-Mobile. Mentioned on that page:
"GM1910, GM1911, GM1913 and GM1917 models are supported."

I did find https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7_Pro/T-Mobile_GM31CB/
But doesn't look like it matches the version I have.

Is there a specific MSM tool for the GM1915 variant?

Thanks again for your assistance!

Update:
Tried the link above for the T-Mobile GM31CB and it also does not work - MSM tool is still giving me
"Firehose Communication Handshake Failed"

I guess I am just using the incorrect version of the MSM tool and can't seem to find the right one for the GM1915 version 😫
Hi,


I am having the same issue!!! "Firehose Communication Handshake Failed"
Not many people are facing this issue but there is no solution out there yet. :cry::cry:

I found only a few (Including you) who is facing this issue.
I am facing this issue on my Oneplus 8 device.

Please do let me know if you find anything.

Attaching the screenshot of the error.

@Some_Random_Username
Any help?
 

Attachments

  • WhatsApp Image 2022-01-24 at 6.19.56 PM.jpeg
    WhatsApp Image 2022-01-24 at 6.19.56 PM.jpeg
    95.4 KB · Views: 6,447

ranaerys

Member
Nov 15, 2020
35
5
Hello everyone!

I tried a couple a couple different customs roms but want to go back to stock because i can't live without my banking apps. I installed the stock rom with lineageos recovery but wasn't passing safetynet because of the unlocked BL. So I put the stock recovery back (Indian one as I couldn't find the EU one to match my phone) and locked bootloader which resulted in a soft brick. I managed to get it back to lineageos recovery + "stock" rom but still wish to restore phone to its original state.

Is MSM the right tool for this? If I use it can I still get OTA updates to get back to OOS11? I really don't want to be stuck in OOS 10.

Thanks for your work and any info you might provide!

EDIT: It did everything I hoped for. Thanks to OP and the devs!
 
Last edited:

ajaygrylls

Member
Nov 16, 2020
20
1
Guys, please help me. I flashed my Nord using msmtool. It booted without issues but when I updated my software, it enters crashdump mode. I tried reflashing but same happens all the time. Unable to flash custom rom too coz it's entering crashdump mode even with custom rom flash. I'm now using phone on A10 without upgrading it. Please help me solve this.
 

Attachments

  • 1649819948946.jpg
    1649819948946.jpg
    6.6 MB · Views: 110

abidmajid

New member
Jun 28, 2022
1
0
Hyderabad, India
Hi, thank you for the amazing guide but unfortunately my fingerprint registers halfway and resets and I read somewhere its because of the persist.img I didn't backup mine can somebody help me with this?
 

zaoms

Senior Member
Jul 23, 2014
233
36
Istanbul
my phone cannot enter EDL mode. It enters for 5 seconds and then boots back to fastboot mode. what can i do
 

happy619

Member
Feb 12, 2018
11
0
Recently on doing MSM for Indian firmware on my nord device shows play store uncertified and am unable to use NFC but if I MSM to Global on oos10 and oos11 my device is certified but as soon as I upgrade to 12 it becomes uncertified. Anyone knows a fix or is this a known bug on OOS12 and indian firmware ?
 

bera2001

New member
Nov 9, 2017
2
0
Can I get the EDL package for the latest Oxygen OS 12 on Oneplus Nord, my device is facing Qualcomm crashdump mode error, which is only fixed after installing android 10 ROM through EDL mode, after which if I apply a system update it again causes that error. Please help.
 

Attachments

  • IMG20221009142640.jpg
    IMG20221009142640.jpg
    2.4 MB · Views: 14

vvnpyr

Member
Oct 7, 2022
7
0
Hi,


I am having the same issue!!! "Firehose Communication Handshake Failed"
Not many people are facing this issue but there is no solution out there yet. :cry::cry:

I found only a few (Including you) who is facing this issue.
I am facing this issue on my Oneplus 8 device.

Please do let me know if you find anything.

Attaching the screenshot of the error.

@Some_Random_Username
Any help?
You need to reboot your phone for handshake to be fixed, cant flash twice on one session
 

vvnpyr

Member
Oct 7, 2022
7
0
Unfortunately, no MSM package works for me to unbrick my AC2003 (EU),
always get the error "device not match image"
Qualcomm Driver looks fine, Phone is in EDL mode and MSM tool seems to establish a connection to the device.
Tried also different firmware versions and also global region, with same result.
Has anyone an idea, how to fix this?

How i messed it up:
  • bought phone AC2003 in EU on Nov/2021 and upgraded to latest stock OOS 11 --> WORKED
  • unlocked bootloader and flashed to LineageOS 17.1 according installation guide --> WORKED
  • switched back to stock OOS EU 10.5.5 via FASTBOOT method --> WORKED!!
    • used a OOS 10.5.5 fastboot image because adb sideload with OOS 11 OTA zip did not work in LineageOS recovery, problem was, that device name did not match to image: "OnePlusNord" vs. "Nord"
  • locked bootloader again, as I assumed device has 100% stock firmware -> BRICKED!!
I'm facing the same issue, have you found a solution yet? I'm contacting Oneplus support
 

vvnpyr

Member
Oct 7, 2022
7
0
Thanks for all these tools everybody!
OnePlus Nord EU version here.
I have installed a custom ROM, was not happy, and want to go back to Stock ROM.

MSMDownloadTool gets connected to phone (Qualcomm HS-USB QDLoader 9008 on COM9)
When I reboot phone to EDL mode, it is detected in MSMDownloadTool. I select EU for target, and press start.

The process halts at "param preload failed".
Tried different versions of the MSM package, but none work. Any tips for me?
The attached screenshot shows target as O2, I have tried with EU versions too.
Did you find a solution for this?
 

Top Liked Posts

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

    You can also rollback your phone to a previous release of OOS with them if for some reason you would like to go back to an older firmware :)

    You can download the following versions:

    AC01AA tools (global firmware):
    ANDROID 10:


    AC01BA tools (european firmware):
    ANDROID 10:


    AC01DA tools (indian firmware):
    ANDROID 10:


    Warning:

    As this happened on OnePlus 8 and OnePlus 8 Pro Pro, it is advised to take backup of /persist partition before crossflashing (eg going from European to Indian build) as fingerprint reader may give an error related to enrollment issue. You can do so by using dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img (you must have root access, see https://forum.xda-developers.com/oneplus-nord/how-to/guide-how-to-root-oneplus-nord-t4139411 for that) and moving it to your computer/cloud.

    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.
    Click on Target button and select O2 while using global tool or India while using indian tool or EU when using european tool.
    Press Start button (this is done so that device will be "captured" automatically by tool instead of going back to normal boot after 10 seconds)

    Power your device off.
    Let it cool down for one minute.
    Maintain volume up and volume down keys for at least 40 seconds to get into Qualcomm EDL mode.
    Plug your device to your computer using stock OnePlus cable. (You may let volume keys go once done.)
    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.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) 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.

    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, all credits to @Shadow12347 for finding it out.

    Credits:

    @Lord Ace for testing 10.5.2 Indian tool on his device.
    OnePlus for the device and OS
    2
    It worked for me,
    After unlocking and locking bootloader and ended with corrupted device on locked bootloader
    This method helped to solve it.

    Thank You
    2
    Small token for the help: Transaction ID: 5NF52401AU895305W
    2
    This is a brand new set and I first noticed it after I set up my phone. The usual data transfers, reinstalling apps etc. But now, it will not go away. Im thinking it's like that out of the box, just that I did not notice it earlier.

    So far I have not had any issues functionality wise and my local OP support tells me to ignore it and a future update will fix it. They're not sure of the cause either and could not fix it.

    This message keeps coming back even after multiple factory resets + a ROM reflash. I'm trying to rule out a hardware issue.

    I did notice that this app is one of those that you remove when you debloat your OP set. I'm sure it would go away if I did that but if theres an underlying issue I might just be setting myself up for a catastrophic failure in future.

    @ Some_Random_Username

    I have a NVBackupUI(thread here) error msg that refuses to go away.

    I have used your guide to reflash OOS 10.5.2 but the error message is still there.

    Do you by any chance have any idea on a way to resolve this?

    Unfortunately no idea, MSM tool in upgrade mode doesn't touch to NV items.
    Either wait a new OOS build after 10.5.4 or RMA your device.

    Hi, my friend really messed up with his phone. Phone currently have encrypted data partition. Problem is that msmtool doesn't detect phone at all, also device manager doesn't show it while its in msmtool. Anything he can do?

    Make sure his device is off before trying to get in Qualcomm HS-USB 9008 mode, that was something we ran into during testing.
    Also as a sidenote encryption state of the phone doesn't matter to use this tool.