How To Guide Global/US unbricking guide.

Search This thread

JLvaldes7

Member
Aug 5, 2015
8
3
Thats how I had to do it as well usb mouse until today.... An let me rephrase my previous comment I read it back and it looked intimidating. I took the T-Mobile msm tool and just combined the OP9 Pro IN settings.xml with the T-Mobile one... Run opscrypto to extract all the files changed the header and footer into it to make the tool think it was that version run opscrypto to put it back together. C.39 working and no touchscreen issues, I am having issues with my sim card not registering at all but that seems to be more common and not something this process caused.
Is there a way you can upload your Tool Version?
 

blumenthala

Senior Member
Jan 13, 2010
103
18
Las Vegas
OnePlus 5
OnePlus 9
Please help! I got the "Device not match image" error in the Global MSM tool. Tried it again and now I'm getting a device issue in Device Manager. See screen shot. Is there anyway to fix this error so that I can get back into EDL mode?
 

Attachments

  • Screenshot 2022-01-04 172252.png
    Screenshot 2022-01-04 172252.png
    6.6 KB · Views: 29
  • Haha
Reactions: Master Santa
Please help! I got the "Device not match image" error in the Global MSM tool. Tried it again and now I'm getting a device issue in Device Manager. See screen shot. Is there anyway to fix this error so that I can get back into EDL mode?
The fix the device manager unplug and power up your phone (Vol + | Power ) and power it back down and then plug in usb holding both volume keys for EDL... Is this originally a TMO version? Most people have to end up using the Oneplus 9 Pro India msmtool.
 
This worked for me and allowed me to get back to the tmobile software. I was curious to see if the stock tmobile msm tool would work afterward since it is now running tmobile software but it's giving me an invalid target IN error. (My phone is an le2117)

This leads me to believe that even though it is running the correct version of the software, there is still something deeper from this modification that is making it believe that it is still running the IN 9pro software, at least in the eyes of the msm tools.

I was curious and I tried this modification with the IN 9pro settings to the global .ops and it allowed me to msm the global software even though I was coming from the tmobile version. Is this normal behavior and is there something that can make things fully stock?

Edit: I just updated to Android 12 on the phone and the dead touch screen issue is gone. However, it takes a while for the phone to recognize my sim card. I can only text and make calls and there is no data. The service also cuts out periodically. Tried flashing the modem and killed the phone. Modified msmed back to global.
Correct about the target error when trying the stock tmo version. The target version seems to be written in phone somewhere which is why you could use the IN 9p. The change in settings just added the IN target to the TMO software.
 

warglock

Member
Sep 6, 2011
27
11
Praise be. Your guide saved my bacon.

I flashed a new ROM, somehow got TWRP installed as recovery (?) as I installed LOS Recovery and it stalled mid update. Phone would not display any image but I would get a chime when I plugged it into my computer. Your bit about the India MSM tool did the trick.
 

winterfoxx

Senior Member
Jun 11, 2020
73
9
Praise be. Your guide saved my bacon.

I flashed a new ROM, somehow got TWRP installed as recovery (?) as I installed LOS Recovery and it stalled mid update. Phone would not display any image but I would get a chime when I plugged it into my computer. Your bit about the India MSM tool did the trick.
I'm glad I could help!
 

orangekid

Sr. Mod / Mod Committee / RC-RT Committee Lead
Staff member
Apr 10, 2009
14,677
8,698
Thats how I had to do it as well usb mouse until today.... An let me rephrase my previous comment I read it back and it looked intimidating. I took the T-Mobile msm tool and just combined the OP9 Pro IN settings.xml with the T-Mobile one... Run opscrypto to extract all the files changed the header and footer into it to make the tool think it was that version run opscrypto to put it back together. C.39 working and no touchscreen issues, I am having issues with my sim card not registering at all but that seems to be more common and not something this process caused.
@XxBigBuckxX

I am running into this issue when trying to encrypt my new extract folder, how did you do it?

Also, is there a way you could upload your modified file for tmobile OP9?

1648309761318.png
 

20PercentRendered

New member
Jun 6, 2022
3
0
I tried both of these MSM tools to no avail. Both of them gave me "Unsupported target EU". What can I do next? The EU MSM tool gives me "device not match image". I have a regular OnePlus 9.
 

EtherealRemnant

Senior Member
Sep 15, 2007
3,986
1,311
38
Denver, CO
I tried both of these MSM tools to no avail. Both of them gave me "Unsupported target EU". What can I do next? The EU MSM tool gives me "device not match image". I have a regular OnePlus 9.
Use the Indian 9 Pro MSM. When that boots, flash the EU OnePlus 9 downgrade package to get back to normal EU OnePlus 9 firmware.

India 9 Pro MSM: https://www.androidfilehost.com/?fid=2188818919693804748
EU downgrade package: https://oxygenos.oneplus.net/OnePlu..._downgrade_for_Android12_df4ed5eca9914248.zip

If you are having issues with the phone deleting the downgrade zip, make sure the bootloader is unlocked and use adb push nameof.zip /sdcard/ to get it to the root storage, then you use the system update local upgrade tool.

Alternatively you can flash the downgrade package with TWRP.
 
Last edited:

20PercentRendered

New member
Jun 6, 2022
3
0
Use the Indian 9 Pro MSM. When that boots, flash the EU OnePlus 9 downgrade package to get back to normal EU OnePlus 9 firmware.

India 9 Pro MSM: https://www.androidfilehost.com/?fid=2188818919693804748
EU downgrade package: https://oxygenos.oneplus.net/OnePlu..._downgrade_for_Android12_df4ed5eca9914248.zip

If you are having issues with the phone deleting the downgrade zip, make sure the bootloader is unlocked and use adb push nameof.zip /sdcard/ to get it to the root storage, then you use the system update local upgrade tool.

Alternatively you can flash the downgrade package with TWRP.
That just gave me "Unsupported target EU" aswell.
Edit: Ran it again, works now. You need to set India in the "target" dropdown.
 
Last edited:

orangekid

Sr. Mod / Mod Committee / RC-RT Committee Lead
Staff member
Apr 10, 2009
14,677
8,698
Ya the only way it works is using the India ROM target stuff to get it to take, super weird...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    Global/US OnePlus 9 Unbricking Guide
    Tested and used on a LE2115 variant device.

    YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST DITCH ATTEMPT BEFORE SENDING IT TO ONEPLUS (THEY WILL FIX IT FOR YOU, UNLOCKED BOOTLOADER OR NOT)


    • Step 1: Boot your device into EDL mode. (If it's not already), then plug it in.
      • If it isn't, and you're in fastboot, you can boot into it via fastboot oem edl (correct me if I'm wrong here)
    • Step 2: Download the MSM tool.
      • The proper MSM tool can be found here.
        • I'd recommend using Internet Download Manager to speed it up.
      • Unzip it using something like 7-zip into the root folder of any drive (the root folder meaning the topmost, any subdirectories may have issues).
      • Some AVs may flag MSM, so please make an exception (it's safe, you can ask basically anyone)
    • Step 3: Install the right drivers. (If they aren't installed)
      • The proper drivers can be found here.
        • Use the readme.txt file in the driver zip, it'll explain how to do everything.
    • Step 4: Run the "MsmDownloadTool V4.0.exe"
      • Set the dropdown to "Others" and click next.
        • 1638573762606.png
      • Check the "Use Lite Firehose" box, and uncheck the "Sha256 check" box.
        • 1638574266179.png
      • Click on "Start" once your phone is detected.
        • 1638573835258.png
    • Step 5: Let it run for around 300-350 seconds (that's how long it took mine). Once it says "Completed" (if it errors, see below), congrats! You've unbricked your OnePlus 9!

    Errors


    If an error occurs, don't worry! See here for the potential errors and how to solve them.

    • Sahara Communication Failed
      • When this happens, try using a different cable (one included in box is best), and try a different port. If both fail, try on another computer.
    • Device not match image!
      • Okay, this one WILL take much longer than the previous one, but this is still fixable.
        • Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
        • Close the old one.
        • Flash using the above guidelines aswell.
        • Once finished (you have to wait the 300 seconds), hope that it works lol.
          • If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
            • Set up Magisk (too many guides for it, not going to explain it here.
            • Flash magisk by booting into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img) (install menu, then find magisk's file), then copy TWRP's image to the device and install the ramdisk via the image (should be in advanced).
            • Install this app.
            • When setting up, grant it root access, and make sure to select the Stable (Full) channel, and set your device to OnePlus 9. (NOT THE INDIA VERSION, NO MATTER WHAT IT SAYS.
            • Go into settings, and enable Advanced Mode (this is req'd)
            • Go to the main page, and click download update.
            • When it finishes, let it do automatic install (UNCHECK ALL BOXES OR IT WILL ERROR!)
            • Congrats! You fixed it!
        • If it doesn't work, you may have to send it off to OnePlus. They will still do repairs even on unlocked bootloaders assuming that you're in warranty.
    2
    I used an USB mouse to downgrade using the rollback packages.

    I'm scared to update too. I'm glad I found someone with the same issue.
    Thats how I had to do it as well usb mouse until today.... An let me rephrase my previous comment I read it back and it looked intimidating. I took the T-Mobile msm tool and just combined the OP9 Pro IN settings.xml with the T-Mobile one... Run opscrypto to extract all the files changed the header and footer into it to make the tool think it was that version run opscrypto to put it back together. C.39 working and no touchscreen issues, I am having issues with my sim card not registering at all but that seems to be more common and not something this process caused.
    1
    Nice guide ! Just one question, the TWRP link is for OnePlus 9 pro, it is normal?

    Other point, to be complete, you should specify how to boot in EDL mode and add fastboot commands for every operations, like flashing twrp
    Yup, it's normal. I use that specific TWRP on my LE2115. I'll make the edits right away! Thanks for the suggestion!
    1
    I managed to do as described step by step in the guide, after the flash of the original rom via "oxygen updater" but on restart there is actually the stock rom but the touch remains blocked, I also tried to do a factory reset but nothing changes, my phone gets stuck on the first screen and the touch does not respond, any advice? Thank you
    i had to do this with the latest a12 update broke the screen like your saying and this is the steps i had to take to fix it


    Device not match image!
    • Okay, this one WILL take much longer than the previous one, but this is still fixable.
      • Download this MSM tool instead following the same guidelines as above. (I am aware it is the wrong version, however this is the only working fix to the extent of my knowledge.)
      • Close the old one.
      • Flash using the above guidelines aswell.
      • Once finished (you have to wait the 300 seconds), hope that it works lol.
        • If it does, it'll reboot into OxygenOS. Go through setup as normal (the cursed camera cutout is also normal), finish it, and then you will have to:
          • Set up Magisk (too many guides for it, not going to explain it here.
          • Boot into TWRP using fastboot (fastboot boot twrp-3.6.0_11-0-lemonadep.img
          • Flash 11.2.10.10 ota zip in twrp via adb sideload and reboot and you will have working screen and everything else.
          • at this point do not update to A12 update aka the c36 ota in settings or you will face the same issue and have to redo this process
          • Congrats! You fixed it!
    1
    Please help! I got the "Device not match image" error in the Global MSM tool. Tried it again and now I'm getting a device issue in Device Manager. See screen shot. Is there anyway to fix this error so that I can get back into EDL mode?