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

How To Guide Global/US unbricking guide.

Search This thread

winterfoxx

Senior Member
Jun 11, 2020
71
8
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.
 

Attachments

  • 1638573955133.png
    1638573955133.png
    2.8 KB · Views: 109
Last edited:

akboy7015

Senior Member
Jun 13, 2014
76
21
OnePlus 6
Samsung Galaxy Tab E
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
 

winterfoxx

Senior Member
Jun 11, 2020
71
8
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!
 
Last edited:
  • Like
Reactions: akboy7015

panoramixmeister

Senior Member
Jun 2, 2011
226
67
Athens
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.

I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.

Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.

Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.

To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
 

winterfoxx

Senior Member
Jun 11, 2020
71
8
I have a CN variant of OnePlus 9 (LE2110) running the Global version of Oxygen OS 11.2.10.10LE25AA.

I installed the latest TWRP (3.6.0_11-0-lemonade) from the TWRP website and then I rooted the phone via TWRP with Magisk v23 and everything was fine.

Today I installed a new version of the launcher which was probably buggy, and it made the phone act funny even when I rebooted the device, so I booted the phone into TWRP recovery and dirty flashed the ROM and then reflashed Magisk for root. This is how I used to do it with my 5T.

Obviously, I have done sth wrong, and now the phone boots only in fastboot mode. When I try to boot into recovery, TWRP loads with the lockscreen but it doesn’t work, you cannot do anything, whatever you press it doesn’t react.

To my understanding, I have soft-bricked the phone and need to follow your guide to unbrick it?
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
 

iaio72

Senior Member
Jul 16, 2009
1,719
923
Rome
@winterfoxx,
thanks for this very useful guide, a curiosity, when you use the zip file linked from "OnePlus_9_Pro_India_OxygenOS_11.2.4.4", you flash the file inside the zip, "lemonadep_22_I.07_210412" which is for the Pro model? right? thanks
 

panoramixmeister

Senior Member
Jun 2, 2011
226
67
Athens
This guide is for phones stuck in edl mode. This won't work on CN phones to the extent of my knowledge. If you can get into fastboot, you can try and recover via a tool. I'm not sure why twrp is doing that, but can you try booting the twrp image instead of booting the flashed one? Sorry about the late response, by the way
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).

The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.

Thank you for the very helpful guide!
 

iaio72

Senior Member
Jul 16, 2009
1,719
923
Rome
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
 

papad13

Senior Member
Jan 23, 2009
62
12
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
So sad , I am in the same situation!
Did you figured it out ??
 

iaio72

Senior Member
Jul 16, 2009
1,719
923
Rome
from oxygen updater, I also tried to flesh the Open beta 1, but same result, the touchscreen does not respond, strange but with the rom for the pro version the touchscreen works fine, I'm looking for a way to solve but still nothing new....
 

allenjthomsen

Senior Member
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!
 
  • Like
Reactions: iaio72

winterfoxx

Senior Member
Jun 11, 2020
71
8
It worked perfectly for the CN variant (LE2110) that I have. The CN variant is running the Global version of OxygenOs (AA) so the only difference was that I had all three options checked (Sha256 check, Auto reboot and Use Lite Firehose).

The first few times I got the Sahara Communication Failed message but I followed your suggestion and changed USB port and cable and it worked flawlessly.

Thank you for the very helpful guide!
Congrats! I'm glad I was able to help
 

winterfoxx

Senior Member
Jun 11, 2020
71
8
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
Erm, try factory resetting it in twrp
 
  • Like
Reactions: iaio72

allenjthomsen

Senior Member
the one downside to this method that ive found is i am still unable to flash stock OP9 msm even after fixing i still get the device not match image error even after using the param from my stock msm backup files and flashing it directly to my device.
i verified before i even had this issue that my device was in fact a le2115 and backed up all partitions using msm.
 

allenjthomsen

Senior Member
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start

Although i would advise against taking the a12 update for multiple reasons
 
Last edited:

iaio72

Senior Member
Jul 16, 2009
1,719
923
Rome
i figured out the best way to flash stock global to device and not have a frozen screen if you update to a12
i can verify that you can shorten this down by a few steps also and it will still work .
At step 4 just flash global msm with step 2 options unchecked and device set as o2 and start

Although i would advise against taking the a12 update for multiple reasons
"a12" you talked aboit open beta? or we have official oxygen android 12? thx
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    Can you help finding the “param bin file global”
    Please ?
    Is this what you're looking for? You have to get if from the msm .ops.
    yes with "clean" installation or upgrade from oxygen 11, with oxygen 12 i have screen freeze too, i dont know why, i remain with oxygen 11
    remember when bricking op9:
    - msmtools india op9pro
    - unlock bl
    - then install twrp
    - install by adb sideload "downgrade india rom (op12/oxygen12) you find in post above
    - then allways by twrp in adb sideload install oxygen 11 that you want (i ve installed global version and worked too)

    wait a version of oxygen12 that work well!
    I had to edit the settings file in the IN msm tool to repack it with the T-Mobile msm files and restore that .ops file to have a working touch screen with 12.
    1
    I was

    Do you know if latest rev C.39 fixed the touchscreen issue?
    I don't install for now, I used StagOs based on Android 12
    1
    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.
    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.
  • 5
    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
    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.
    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.