I converted my tmobile one plus 9 to a global version. When I first tried i ended up with a brick, none of the msm tools worked all giving me the sahara connection error. I ended up being able to use a msm for the one plus 9 pro and then using twrp to flash a none pro rom to get me to a global rom.
I want to go back for a few reasons but whenever i run any tmobile msm tools i get an error say "unsupported target EU". I've tried different drivers with no luck.
Restore OnePlus 9 to Stock via Fastboot Commands
This guide assumes you have the SDK Platform Tools installed and working, along with USB drivers for your device (if needed), and have your full update zip which you've already extracted the payload.bin from, and then dumped the images using...
forum.xda-developers.com
Is the likely answer. Not 100% on that as i haven't tried it. But since msm not working would seem this only option
I looked at that thread, though it seems to need a stock rom or flashable update which I don't believe we have for the TMobile varient
Deadrider2 said:
I looked at that thread, though it seems to need a stock rom or flashable update which I don't believe we have for the TMobile varient
Click to expand...
Click to collapse
I'm sorry i didn't think to mention, you could try to use the rom included in the t-mobile msm and run it thru payload dumper. Then follow steps in that thread
Related
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.
Hi all,
I've unlocked my bootloader, installed the EU ROM and found too much missing for my liking. I was unable to load Gapps due to TWRP issues and I'd like to return back to the global ROM but i'm struggling:
1) I'm not 100% sure I've got the global ROM, I've come across 3x separate links (more exist) that have different global ROMS, what is the official ROM link? (there is even multiple global ROM like Taiwan, Indonesia, EEA, Russia, turkey...) Link 1 Link 2 Link 3.
2) When attempting to follow Xiaomi community guide and using their own unique ROM link, MiFlash errors during installation due to error: "Antirollback check error". People discuss editing batch files which aren't there and at this point im too afraid to brick my device.
Please help, i'd like to reflash the global ROM in a safe manner and i'm not sure how best to go about doing this
1) I recommend stock rom, not custom rom.
The link is a custom rom.
I use the normal global rom version, not for a specific country.
2) I write directly in fastboot mode, not using the miflash tool.
Extract the ROM file and run the flash_all.bat file.
https://c.mi.com/oc/miuidownload/detail?guide=2
Thanks, i'm assuming the stock ROM is from the same link?
I've tried using flash_all.bat however the command prompt that runs immediately shuts after executing. I assume its again due to the anti roll back checks. How can i stop this and more importantly is there a risk of bricking if messed with?
Edit: Got it working eventually. For anyone else in the same position don't use Powershell. Use Windows command prompt, "cd" to the directory of the extracted Zip. Just run "flash_all.bat" from command prompt and let it run.
Thanks osebee
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
Hello,
Just got a Oneplus 9 today. Installed Jaguar to try it out. Wanted to go back to stock to compare a few things.
I grabbed the "stock" files and tried to flash using this guide: https://forum.xda-developers.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/
This bricked the phone.
I was able to restore the phone via MSM using the Indian one (lemonadep_22_I.07_210412), but in OxygenOS it states the Phone is a 9 Pro.
I tried flashing the STOCK file again just to see (since I now know I can recover in EDL), but it bricked the phone again.
This allowed me to confirm that for Global LE2115, the European MSM (lemonadep_22_E.05_210324) also works to restore the device!
Unfortunately again, it says the Phone is a 9 Pro.
How would I proceed if I wanted to return a LE2115 to stock and relock the bootloader?
Thanks
Found my answer in this post: https://forum.xda-developers.com/t/fixed-hard-bricked-le2115.4452435/#post-86967531
Copy pasta:
To get back to global firmware, flash this in the local upgrade tool.
https://oxygenos.oneplus.net/OnePlu...all_2107082125_downgrade_059624cc7298428b.zip
It is the global downgrade package. It will wipe your phone and when it comes back, you will be back on global software.
After you flash that, go to OTA upgrade and it will say it's going to download C.48 but it will actually install 11.2.10.10 and then you will have the latest OOS11.
Click to expand...
Click to collapse
Can confirm this works!
I used the unnbrick tool from one community server and restored my one plus 9 5g 2115.to stock and locked the bootoader. But I could not get to install any rom because it always took me to crash dump. Hope it helps to get back to proper version for you
A week ago, I wanted to try updating my OP9 LE2117 to OOS12 that was on global firmware, since I was rooted and had TWRP on my device, I needed to go back to stock, so I followed this thread using the modded india TMobile MSM to OnePlus 9 pro firmware, and then downloaded OOS 11.2.10.10 here "signed flashable zips > LE25AA Global > 11.2.10.10", then used fastboot enhanced to flash the payload.bin file to go back to OnePlus 9 firmware with OOS11, and I did a local update to OOS12 C.48, but after I did, the phone touchscreen was unresponsive and didn't work, and the dual sim bug was present "where my phone couldn't recognize my sim unless I eject it and inserted back in it the sim, the only thing I could do to interact with the phone is the buttons on the phone and using a USB C wireless mouse, so I india MSM again and fastboot enhanced back to 11.2.10.10, I've also tried flashing a custom rom on the device, I've flashed Lineage OS 19.1, even though the compatible devices didn't list LE2117, surprisingly I was able to boot into LOS 19.1 but same thing, unresponsive touchscreen, only operable with USB C wireless mouse, is there is a reason why the touchscreen is unresponsive, and if there is a solution to get OOS12 on the device without any touchscreen issues/sim issues? Any help will be appreciated. If you need any more info I'm more than happy to provide
This is my first post on XDA forums, long time lurker here.
U will first have to msm to tmo modded with target id india then convert to global u wont have any touchscreen issues
TMO MSM India mod.zip
drive.google.com
rizzmughal said:
U will first have to msm to tmo modded with target id india then convert to global u wont have any touchscreen issues
Click to expand...
Click to collapse
Any exact guide on this?
underworld737 said:
Any exact guide on this?
Click to expand...
Click to collapse
Flash the msm above mentioned then just follow other safe convert mothod
rizzmughal said:
Flash the msm above mentioned then just follow other safe convert mothod
Click to expand...
Click to collapse
just tried flashing the tmo modded msm with sha256 checked and use lite firehouse unchecked, but i was getting "unsupported target eu", so i tried with sha256 unchecked and use lite firehouse checked, still got the same problem, currently the device is running 11.2.10.10 with twrp & magisk, flashed the payload.bin file via fastboot enhanced after using the oneplus 9 pro india msm.