Database Info

Question [NEED HELP] OP9 LE2110 Tried to Use 1.2.4.4 FASTBOOT. EDL Bootloop

Will someone please help me, i cant figure out how to fix the phone. Both MSM Tools dont work, India version which is my origin, and the Global.
It says device model is wrong.

Well I did the FFastboo_SlotB.bat
from the First Sticky, OOS 1.2.4.4AA Fastboot.
it flashed everything and then it went to reboot Fastboot and I was stuck.

Now I get Device Not Matched Image on both MSM Global and MSM India

I'm in the same situation.

I was able to get my phone back into a semi-functional state, but I had to use the OP9 Pro Indian MSM tool (even though I have an OP9 5G Global) . All others failed with "Image not match device".
Now I'm trying ot figure out how to get back to the OP9 Global image.

Yeah, using the OP9 Pro MSM Tool and checking "Lite Firehouse" before flashing should bring your device back to life. Once your device is back on track, you can flash it with your MSM tool for the device.

zborn said:
Yeah, using the OP9 Pro MSM Tool and checking "Lite Firehouse" before flashing should bring your device back to life. Once your device is back on track, you can flash it with your MSM tool for the device.
Click to expand...
Click to collapse
Yeah thats what I though. I'm continuing to get the "Device not match image" error when attempting flash my device with the correct image now.

I finally got it to do something also. Im in the same position now as you are. OnePlus 9 Pro 5G.
My buddy told me to try and do DSU Loader: GSI+GSM Arm64 under Developers Settings and have the Global MSM Tool running.
Ima give it a whirl.

So after flashing OP9 Pro India, fastboot booted to twrp image and flashed latest full signed zip for my device ( OP9 Global). I booted to system and it worked but had some issues like uncertified play store. I then installed latestupdate via system updater and everything is good to go.

gorilla p said:
So after flashing OP9 Pro India, fastboot booted to twrp image and flashed latest full signed zip for my device ( OP9 Global). I booted to system and it worked but had some issues like uncertified play store. I then installed latestupdate via system updater and everything is good to go.
Click to expand...
Click to collapse
I thought your device was the same as mine LE2110?
So should I try and flash my OTA the India one

Yeah, it is. Thats the screwed up part. The only MSM tool that would work and not gove "device not match image" error was thr Oneplus 9 Pro India tool. Once in that, I could boot to twrp and flash full signed zip.

Weird.
Now I just did the same thing. Bam! Back to my DA OnePlus 9 version. Man it feels good.

I have exactly the same problem you managed to start again thanks to which msm version?

Well we did MSM India Pro...
Then use the MSM Tool that matches your phone.

ok weird at home any tool I have the same error

hello brother how are you?
i hope you will be fine
i need your help brother i also have le2110 in edl state
illusiveairforce said:
Well we did MSM India Pro...
Then use the MSM Tool that matches your phone.
Click to expand...
Click to collapse

Anyone who has installed the correct drivers and MSM tool keeps failing with "Image not match device" even though youre using the correct MSM tool for your device, try the One plus 9 Pro - India tool. From there, you can boot to twrp and flash latest full signed zip, then flash update from internal updater so correct image is on both partitions.

Question [Closed] Revive OP9 By Flashing 9 Pro Firm By MsM but now how to get back to original also sim not working.

Revive OP9 By Flashing 9 Pro Firm By MsM but now how to get back to original also sim not working.
How to flash original op9 firmware.
msm showing wrong device.
Please Help.

ahieje73 said:
Revive OP9 By Flashing 9 Pro Firm By MsM but now how to get back to original also sim not working.
How to flash original op9 firmware.
msm showing wrong device.
Please Help.
Click to expand...
Click to collapse
Fastboot boot TWRP and flash whatever firmware is for your device ,also flash to both slots.

mattie_49 said:
Fastboot boot TWRP and flash whatever firmware is for your device ,also flash to both slots.
Click to expand...
Click to collapse
Hey thanks for reply can you please share any thread about this or if thats not available can you please tell me the detailed step by step because i dont want to brick my device.
do i have to flash zip from oneplus website or payload dump files in twrp.

ahieje73 said:
Hey thanks for reply can you please share any thread about this or if thats not available can you please tell me the detailed step by step because i dont want to brick my device.
do i have to flash zip from oneplus website or payload dump files in twrp.
Click to expand...
Click to collapse
Have you already tried downloading correct firmware from OnePlus site. And local upgrading?. And you will indeed have to look it up. This all requires some working knowledge of how all this works.

mattie_49 said:
Have you already tried downloading correct firmware from OnePlus site. And local upgrading.
Click to expand...
Click to collapse
no i am on lineage os now.should i do that first but for that i have to flash pro msm cause non pro msm shows wrong device.

┤Thread Closed├┤Duplicate of oneplus 9 got blacked out during flashing fastboot stock rom what can i do now├

Question LE2117 TMO/India Pro 5G to OP9 Locked BL?

Good evening,
Is it possible to recover from where I am (LE2117 model on OxygenOS 11.2.10.10.LE25AA, OTA Version OnePlus9Oxygen_22.O.13_GLO_0130_2111112106), or is my only option to be stuck on the OnePlus 9 Pro 5G India version for locked bootloader? If it's possible, what do I need to do? Work demands my phone to not be rooted...I'm not married to the concept of global or India region, and am fine with either.
[Marking each area with a reference at the bottom...]
Problem: I've attempted the OnePlus 9 5G T-Mobile to Global transition [REF001] on my LE2117 only to brick my phone midway through the process. The goal here is to get the phone on a NON-T-Mobile variant with a locked bootloader. Thankfully I'm rid of T-Mobile, at least...
Where I am now: I was able to recover the phone by using the MSM tool for OnePlus 9 Pro 5G India [REF002], then using the T-Mobile to Global "flash_all.bat" script [REF001] again with the payload of the global version [REF003]. The issue is that the phone's bootloader isn't locked, and if I lock it then everything is gone and I must start over at the beginning of this paragraph. I've attempted using the global MSM tool [REF004], but the issue is that it provides a Param Preload error for Unsupported Target IN. There was a reference somewhere about flashing the param.bin, though, that didn't seem to work...
Thank you for your insight and assistance!
REF001: Convert T-Mobile OnePlus 9 to Global (or other) firmware - https://forum.xda-developers.com/t/convert-t-mobile-oneplus-9-to-global-or-other-firmware.4277169/
REF002: OnePlus 9 Pro Oxygen OS India MsmDownloadTool - https://forum.xda-developers.com/t/oneplus-9-pro-oxygen-os-india-msmdownloadtool.4270589/
REF003: OnePlus9Oxygen_22.O.13_OTA_0130_all_2111112106 -
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.13_OTA_0130_all_2111112106_03a66541157c4af5.zip
REF004: GLOBAL OnePlus 9 MSM TOOL UPDATED -
GLOBAL OnePlus 9 MSM TOOL UPDATED
Frist off Im not responsible for anything that happens to your phone!!! VERY SIMPLE IF YOU ARE BICKED,BOOTLOOPED OR JUST WANT TO GO BACK TO 100% STOCK THIS WILL WIPE ALL DATA!!! AN RELOCK BOOTLOADER OOS 11.2.4.4.LE25AA MUST HAVE QAULCOMM...
forum.xda-developers.com

Run the Indian 9 Pro MSM again and download the global 9 downgrade package in the pinned post and flash that to get back on global firmware. The MSM re-locks the bootloader as part of the process and you don't need an unlocked bootloader to convert between variants if you use the official local upgrade function.

Thank you for your response EtherealRemnant -
I've followed the steps and am probably doing something wrong. I've run the OP9PRO India MSM, unlocked OEM for the flash (because trying local upgrade (downgrade) at this point doesn't show the packages), flashed to either global downgrade package, and attempted the global MSM tool for re-lock. I'm still getting the Unsupported Target IN or Device Not Match Image error. Which part of this am I doing incorrectly?

TuufLess said:
Thank you for your response EtherealRemnant -
I've followed the steps and am probably doing something wrong. I've run the OP9PRO India MSM, unlocked OEM for the flash (because trying local upgrade (downgrade) at this point doesn't show the packages), flashed to either global downgrade package, and attempted the global MSM tool for re-lock. I'm still getting the Unsupported Target IN or Device Not Match Image error. Which part of this am I doing incorrectly?
Click to expand...
Click to collapse
You may actually be running into the same problem I did with the downgrade package where it just vanishes from the storage. Do it like this on your computer:
adb push packagename.zip /sdcard/
When I did this, it didn't mysteriously vanish anymore.
If this doesn't work, you may unfortunately be stuck unless you can get someone to modify an MSM Tool for your purposes.

Finally, a solution that hopefully others can also follow to install different versions of their official builds as well (just exchange REF004 with your appropriate compressed zip containing the payload.bin.):
[Adding references for those who found themselves in my same predicament...]
After utilizing the MSM Download Tool for OnePlus 9 Pro 5G [India Region] [REF001], I unlocked the bootloader and leveraged the TWRP App for OnePlus 9 [REF002] by booting towards it [REF003] and installing/flashing the latest version of the OnePlus 9 5G [Global] [REF004] (it defaulted to slot B.) Re-locking the bootloader [REF005] allowed the phone to automatically wipe, and boot directly into the latest Global install.
Shout-out to ctonylee1965's post that's nearly buried in an off-related thread, or I wouldn't have found this solution.
[Original Discussion: https://forum.xda-developers.com/t/...a-sahara-connection-error-check-this.4308601/]
ctonylee1965 said:
Got back to global. Took me a day to figure it out. Enable OEM Unlock and USB debugging. I flashed temp TWRP, installed the OS Zip file from OnePlus support site. Rebooted into recovery, formatted and wiped system. Booted into global. This installation is in SLOT B. Slot A will still have horrible Indian Rom (only horrible because it shouldn't be installed on my Global Unlocked Phone, no disrespect to my Indian brothers.) Note when logging in for the first time let global do its OTA update before you do anything else, especially before you reboot. The Indian version is installed in slot A. REBOOT after OTA installed. Don't reboot before OTA does its thing. This will ensure Slot A has a clean installation. I made the mistake of rebooting before the OTA and I could not do anything with slot A. Relock the bootloader, it will wipe and you will boot into a pristine Global OS 11.2.8.8 Rom.
Click to expand...
Click to collapse
Thank you EmerealRemnant for your assistance as well!
REF001 - MSM Download Tool for OnePlus 9 Pro 5G [India Region] - https://forum.xda-developers.com/t/oneplus-9-pro-oxygen-os-india-msmdownloadtool.4270589/
REF002 - TWRP for OnePlus 9 (lemonade) - https://dl.twrp.me/lemonadep/
REF003 - TWRP Commands To Use (Scroll Down) - https://twrp.me/oneplus/oneplus9.html
REF004 - OnePlus 9 5G (Global) Official Build - https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1617074715494
REF005 - Re-locking the bootloader (fastboot oem lock) - https://ihax.io/relock-bootloader-a...ommand to reboot your device: fastboot reboot

It seems strange you had to do all that work when all I had to do was flash the downgrade package...

Question LE2113 (EU) on India firmware

Hi everyone,
Unfortunately I had a bricked Oneplus 9 device with only EDL mode. I was able to MSMTool with the indian Oneplus 9 Pro version.
Afterwards I used another bundled MSM package to install Oneplus 9 firmware. On which I'm now stuck.
I tried to use Oxygen Updater to download and install the latest EU update but it throws errors. Can anyone help me please?
Thank you!!!

You can try doing MSM to Global, then in Local upgrade you can switch versions. Good luck

If you're stuck on Indian firmware, use my modded MSM Tool.
[Locked] Global 11.2.10.10 MSM Tool (added experimental support for Indian variant flashing as well)
This method is outdated. You must use this method or you will run into problems...
forum.xda-developers.com
Make sure to leave Sha256 checked and lite firehose unchecked or it may give you a device not match image error.

Question L2117 - Bootloop after successful MSMDownloadTool flash - Now what?

I have a T-Mobile OP9 that I just purchased used. The bootloader was unlocked and I received the file along with the phone. The phone was originally on A11 L2115 (but still showed L2117 in Settings / About). I rooted and grabbed the modemst1, modemst2, and persist.img files with Partition Backup before anything else. I then subsequently updated officially to A13 through an update via local storage then through the OTA updater and it was then fully seen as L2115. I then realized that the rom I wanted needed A12 firmware so I went back to A11 then unlocked bootloader again and attempted to update firmware only off the CrDroid A12L update page. I chose not to flash the modem during that flash and then afterwards my service stopped working. It read the IMEI and baseband and would recognize that it was T-Mobile but no calls/text/data. I then got the bright idea to go back to Tmobile A11 through MSM then unlock bootloader, root, and use Partition Backup to restore the modems and persist imgs. After that, even though I can successfully flash the full Tmo MSMDownload Tool ops file, it only bootloops. If the MSM tool can't fix it - is it done for?

es0tericcha0s said:
I have a T-Mobile OP9 that I just purchased used. The bootloader was unlocked and I received the file along with the phone. The phone was originally on A11 L2115 (but still showed L2117 in Settings / About). I rooted and grabbed the modemst1, modemst2, and persist.img files with Partition Backup before anything else. I then subsequently updated officially to A13 through an update via local storage then through the OTA updater and it was then fully seen as L2115. I then realized that the rom I wanted needed A12 firmware so I went back to A11 then unlocked bootloader again and attempted to update firmware only off the CrDroid A12L update page. I chose not to flash the modem during that flash and then afterwards my service stopped working. It read the IMEI and baseband and would recognize that it was T-Mobile but no calls/text/data. I then got the bright idea to go back to Tmobile A11 through MSM then unlock bootloader, root, and use Partition Backup to restore the modems and persist imgs. After that, even though I can successfully flash the full Tmo MSMDownload Tool ops file, it only bootloops. If the MSM tool can't fix it - is it done for?
Click to expand...
Click to collapse
Sounds like it's not factory resetting when running MSM tool. Boot into recovery and wipe device. Then it will boot.

Regrettably, I've already tried with and without wipes in recovery. I've successfully flashed the recommended T-mobile firmware and there seems to literally only be one option to try for this variant I've seen anywhere. I know the file, Downloader, drivers and USB cable work as I used it to successfully go back a couple of times before the reflashing of the modems and persist files. It also passes still without error but it'll reboot after it sets on the T-mobile boot up for a couple of minutes.
mattie_49 said:
Sounds like it's not factory resetting when running MSM tool. Boot into recovery and wipe device. Then it will boot.
Click to expand...
Click to collapse

es0tericcha0s said:
Regrettably, I've already tried with and without wipes in recovery. I've successfully flashed the recommended T-mobile firmware and there seems to literally only be one option to try for this variant I've seen anywhere. I know the file, Downloader, drivers and USB cable work as I used it to successfully go back a couple of times before the reflashing of the modems and persist files. It also passes still without error but it'll reboot after it sets on the T-mobile boot up for a couple of minutes.
Click to expand...
Click to collapse
U can fix ur bricked device anytime with op 9 pro india msm but i would say if u want try global u shuld try msm conversion without unocking bootloader if problem exist flash 2115 a11 with fastboot enhance u will be out of bootloop i have been there solved it this way

Thanks so much for the reply. I downloaded an Indian 9 Pro firmware but I couldn't get it to flash. Is there a specific one? I used the one recommended in the main thread for unbricking, I thought but I've been trying so many things at this point its blurring together.
Is it possible to fastbootd flash when locked to a different model's firmware?
rizzmughal said:
U can fix ur bricked device anytime with op 9 pro india msm but i would say if u want try global u shuld try msm conversion without unocking bootloader if problem exist flash 2115 a11 with fastboot enhance u will be out of bootloop i have been there solved it this way
Click to expand...
Click to collapse

I was able to recover with the Indian version - thanks! Still don't have my baseband or IMEI though.

es0tericcha0s said:
I was able to recover with the Indian version - thanks! Still don't have my baseband or IMEI though.
Click to expand...
Click to collapse
Flash modded tmo msm with target id india

rizzmughal said:
Flash modded tmo msm with target id india
Click to expand...
Click to collapse
I did try this last night. I am able to flash this successfully, but it sends me into a bootloop.
Same as the original Tmo MSM did before I flashed the Indian 9 Pro MSM (I haven't had luck changing the Target back to something that will work with the original Tmo MSM file yet). With or without factory data reset, I get a bootloop on a Tmobile version of the MSM. Boots up fine with Indian 9 Pro.
I can also switch to global firmware with the official 1+ zip after it boots with the Indian MSM either via temp custom recovery or via local storage updates but it still leaves me with null IMEI and no baseband. I've tried to flash just the Tmo NON-HLOS.bin file in fastbootd while on the Indian firmware and just got a bootloop too. It definitely seems related to the me screwing up the baseband / radio situation but seems odd that the normal fixes aren't sticking. At least I got it to boot to something, but it's still unuseable.

es0tericcha0s said:
I did try this last night. I am able to flash this successfully, but it sends me into a bootloop.
Same as the original Tmo MSM did before I flashed the Indian 9 Pro MSM (I haven't had luck changing the Target back to something that will work with the original Tmo MSM file yet). With or without factory data reset, I get a bootloop on a Tmobile version of the MSM. Boots up fine with Indian 9 Pro.
I can also switch to global firmware with the official 1+ zip after it boots with the Indian MSM either via temp custom recovery or via local storage updates but it still leaves me with null IMEI and no baseband. I've tried to flash just the Tmo NON-HLOS.bin file in fastbootd while on the Indian firmware and just got a bootloop too. It definitely seems related to the me screwing up the baseband / radio situation but seems odd that the normal fixes aren't sticking. At least I got it to boot to something, but it's still unuseable.
Click to expand...
Click to collapse
U cannot flash modem or anything thru fastboot without unlock bootloader

rizzmughal said:
U cannot flash modem or anything thru fastboot without unlock bootloader
Click to expand...
Click to collapse
Right, but I can go back to the Indian 9 Pro MSM then unlock. I just re-attempted the flash for the Tmobile MSM target IN and same - bootloop. It flashes everything successfully with no errors. I have tried with and without all of the boxes checked. It won't work with either Lite Firehose or SHA256 checked. Have flashed, reset, then flashed again. Doesn't seem to make much sense that one version will work but the actual one for my phone will not. I really, really dislike the T-Mobile variants of the past few 1+ phones. It really limits them and makes it a huge hassle to run anything custom.
I believe it is my EFS partition that is corrupted when I attempted to restore the modemst1 and modemst2 files through Partition Manager.

Update: I've fixed my baseband issues by fastboot wiping the modemst1 and 2 partitions. This has allowed me to now successfully flash and boot the Tmo firmware via the modded MSM for target IN. Now I am just left with repairing the IMEI which now reads 0.
Update 2: Was able to restore IMEI once I got the bootloader unlocked and reflashed my modemst1 and 2 with Fastboot Enhance.
Whew. Thanks for all the help!

es0tericcha0s said:
Right, but I can go back to the Indian 9 Pro MSM then unlock. I just re-attempted the flash for the Tmobile MSM target IN and same - bootloop. It flashes everything successfully with no errors. I have tried with and without all of the boxes checked. It won't work with either Lite Firehose or SHA256 checked. Have flashed, reset, then flashed again. Doesn't seem to make much sense that one version will work but the actual one for my phone will not. I really, really dislike the T-Mobile variants of the past few 1+ phones. It really limits them and makes it a huge hassle to run anything custom.
I believe it is my EFS partition that is corrupted when I attempted to restore the modemst1 and modemst2 files through Partition Manager.
Click to expand...
Click to collapse
That might be possible u shuld go for bootloader unlock first of all everything great to hear that u got it fixed