How To Guide Global/US unbricking guide.

Search This thread

iaio72

Senior Member
Jul 16, 2009
1,740
927
Rome
yessss solved!
with my "strange method"....:D
- flash the fw indian op9 pro msmstools
- unlock bl
- flash twrp
- with oxygen updater i flashed open beta1 (op9 started but dont work the touchscreen)
- again i flashed op9 pro indian msmtools
- twrp flashed again and before bl unlocked too...
- and with adb sideload i flashed op9 india (downgrade from op1 you find it HERE
- now work all, touchscreen too, and i flash the correct oxygen 11 global from adb sideload too (from twrp)

thanks all for help
 

papad13

Senior Member
Jan 23, 2009
76
16
yessss solved!
with my "strange method"....:D
- flash the fw indian op9 pro msmstools
- unlock bl
- flash twrp
- with oxygen updater i flashed open beta1 (op9 started but dont work the touchscreen)
- again i flashed op9 pro indian msmtools
- twrp flashed again and before bl unlocked too...
- and with adb sideload i flashed op9 india (downgrade from op1 you find it HERE
- now work all, touchscreen too, and i flash the correct oxygen 11 global from adb sideload too (from twrp)

thanks all for help
Yes but if you install Android 12 have you got screen freeze ??? This is the question
 

iaio72

Senior Member
Jul 16, 2009
1,740
927
Rome
So If you flash the Android 12 you will have “screen freeze “ again
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!
 
  • Like
Reactions: JLvaldes7

winterfoxx

Senior Member
Jun 11, 2020
73
9
even with twrp flashed the device is frozen in recovery same as on the main screen even for me i had todo it the way i listed above to be able to even do anything on the phone and it was the only way for it to work correctly for me
2 - Flash Magisk zip file via twrp. 3 - Install kernel, i used arter97 kernel for OnePlus 9 series as it detects magisk and does not remove it.. i dont know if thats the same with others, i have no idea what im doing 4 - Reboot! Its worked well for me so far!

Found this in a custom rom discord. This may work for u
 

allenjthomsen

Senior Member
Nov 17, 2010
2,544
3,304
36
Tacoma, WA
OnePlus 7T Pro McLaren
OnePlus 9
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.
This method is how i fixed mine
2 - Flash Magisk zip file via twrp. 3 - Install kernel, i used arter97 kernel for OnePlus 9 series as it detects magisk and does not remove it.. i dont know if thats the same with others, i have no idea what im doing 4 - Reboot! Its worked well for me so far!

Found this in a custom rom discord. This may work for u
 

jab5555

Senior Member
Sep 13, 2012
106
23
OnePlus 9
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 does work on le2110 but I had to the msm tool DLL ufs from another source , unbricked mine a couple of days ,it's not rooted and strangely after updating it ota to 12 with no bugs lol but now the phone says it a le2115 😀
 
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.
 

Attachments

  • Screenshot 2021-12-26 080255.png
    Screenshot 2021-12-26 080255.png
    57.5 KB · Views: 51
Last edited:
  • Like
Reactions: JLvaldes7

JLvaldes7

Member
Aug 5, 2015
8
3
I was
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!
Do you know if latest rev C.39 fixed the touchscreen issue?

BTW if you plug a USB mouse via OTG you can control your phone an downgrade if needed using the .APK tool from OnePlus.
 
  • Like
Reactions: lukebukowiec

JLvaldes7

Member
Aug 5, 2015
8
3
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 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.
 
  • Like
Reactions: lukebukowiec
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.
 

Attachments

  • Screenshot 2021-12-26 095954.png
    Screenshot 2021-12-26 095954.png
    378.8 KB · Views: 154
  • Screenshot 2021-12-26 095915.png
    Screenshot 2021-12-26 095915.png
    233.9 KB · Views: 157
  • Screenshot 2021-12-26 051306.png
    Screenshot 2021-12-26 051306.png
    25.6 KB · Views: 151

BGW#10

New member
Dec 29, 2021
2
1
OnePlus 6T
OnePlus 9
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.
 
Last edited:
  • Like
Reactions: JLvaldes7

allenjthomsen

Senior Member
Nov 17, 2010
2,544
3,304
36
Tacoma, WA
OnePlus 7T Pro McLaren
OnePlus 9
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.
why are you using a modified msm when you can get back to stock A11 and update to A12 with no issues afterwards using stock msm files in a specific order which i have detailed near the beginning of this thread just change out global for tmobile firmware msm in the guide i provided.
also you can skip step 4 and then flash tmobile msm if thats the device you have.
 

BGW#10

New member
Dec 29, 2021
2
1
OnePlus 6T
OnePlus 9
why are you using a modified msm when you can get back to stock A11 and update to A12 with no issues afterwards using stock msm files in a specific order which i have detailed near the beginning of this thread just change out global for tmobile firmware msm in the guide i provided.
also you can skip step 4 and then flash tmobile msm if thats the device you have.
I get the device not match image error trying to flash the india 9 msm after the india 9 pro msm.

1640925349369.png
 
why are you using a modified msm when you can get back to stock A11 and update to A12 with no issues afterwards using stock msm files in a specific order which i have detailed near the beginning of this thread just change out global for tmobile firmware msm in the guide i provided.
also you can skip step 4 and then flash tmobile msm if thats the device you have.
When it gets to that point only the onp9 msm tool will allow people to to unbrick. To ubrink back to the tomible version the msm tool needs to be modified or you have to use in9p and use global ota to get off in9p , not sure about to tmo but modify the msm tool is the only way ive found out to get back to the original tmobile
 

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?