Database Info

How To Guide MSM cannot recognize your phone aka. Sahara Connection error? Check this.

Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!

Enjoy it I struggled for a week. The result is ridiculous but successful

_MartyMan_ said:
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?

Big Update. my phone is coming back and free again )i think) No warranty, just wild QoL issues with the 9, it seems.
Im still very happy to get it back .
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yo i love you bro.....seriously you are the fkkkng mannnn omg

josc002 said:
Yes !! thanks @flameteam. My Oneplus 9 EU was really super hard bricked (turned to the "dark side") with no display whatsoever. I went for the EU package and the phone came back to life !!
This was the only way as some other download tool dedicated for the Oneplus 9 didn't work. Gave me "Sahara error. (with Windows 7, 10, different USB cables etc)
And , yes as strange as it sounds my Oneplus 9 now runs the OP9 Pro firmware ?!?!.
But this gave me the chance to install the stock OTA for Oneplus 9. It seems to work.
The question is if a full stock OTA OP9 actually cleaned out any trace of the previous Pro version ?
Click to expand...
Click to collapse
yes cleaning msm tool

The Indian version of MSM was able to restore my phone, but now I cant install any OTAs without bricking it. How did you get it back to a Global rom after the MSM retore?

I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.

_MartyMan_ said:
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
you still bricked foooo??? adb reboot edl launch msm tool in thank me lataaaa

Hallelujah!!!! IT WORKED!!!!!!!!! I've been bricked for a month!!

The question now is how do i get back to global? Any ideas?

Anyone???

YES

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.

lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
See above. I figured it out.

Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?

zborn said:
Ok. this worked for me... I was able to save my LE2110 from being hard bricked. THANK YOU.
Now, has anyone been able to go back to the non-Pro software?
If so, how did you do it?
Click to expand...
Click to collapse
See my response above.

ctonylee1965 said:
See my response above.
Click to expand...
Click to collapse
That didn't work for me. I just MSMed back to 9 firmware

lrod55 said:
I was finally able to unbrick by using this method after days of troubleshooting, but now how in the hell do I get the OnePlus 9 firmware back onto it? I've downloaded different (full zip) ota's, moved to root storage, and when I go to system settings --> local upgrade, the updates do not show up there. I tried flashing via TWRP and I believe it booted to inactive slot (where update was applied) and bootlooped. Eventually it booted back into slot A with OP9Pro firmware. I thought maybe I could use global msm tool for OP9 but the thread that says "UPDATED" downloads and then fails to open. So far only msm tool I have gotten to work for my phone was for the Indian OP9Pro variant.
Click to expand...
Click to collapse
I hard bricked my oneplus 9 first time and was panicking. Luckily I found this thread and your answer. You guys saved me hours and days of fixing this, most important of all, I can't tell me wife that I trashed a $800 phone after bought it a couple days ago. I was able to get my phone back into EU version using the MSM tool, lost my IMEI # and sim card won't work, So I was able to switch back to global after following your instruction. Thank you.

_MartyMan_ said:
Hi!
Today i successfully bricked my OP9 to the point where the global MSM tool couldn't recognize it anymore.
I tried everything, from different MSM tools to this thread. Nothing.
Then, Deus ex Machina, @flameteam recommended me to try Indian/EU version of MSM tool for OP9 Pro with Lite Firehose...
...It worked.
It makes no sense, but it worked for me. Try it. Good luck, and thanks a million again @flameteam !!
Click to expand...
Click to collapse
How did you do it? I am trying this method, but MSM tool gives me this error:

Widevine and MSM help

I got myself a second hand oneplus 7 pro gm1913, coming from a oneplus 5t. it's running the the latest OOS fully stock but widevine l3. Can someone help me on how to fix this. I've been reading up but i am out of the loop. This MSM tool seems to be a way to fix it. Flash back to 9 to hopefully get back widevine l1 and then update to 10 and to 11. Where can i get this msm tool or do i need to root to get back L1. I have no idea where to begin. It's all changed compared to the 5T. I feel like a total newbie again

UnwindingThree8 said:
I got myself a second hand oneplus 7 pro gm1913, coming from a oneplus 5t. it's running the the latest OOS fully stock but widevine l3. Can someone help me on how to fix this. I've been reading up but i am out of the loop. This MSM tool seems to be a way to fix it. Flash back to 9 to hopefully get back widevine l1 and then update to 10 and to 11. Where can i get this msm tool or do i need to root to get back L1. I have no idea where to begin. It's all changed compared to the 5T. I feel like a total newbie again
Click to expand...
Click to collapse
You will only get L1 Widevine after update from OS9 to OS10, on OS 9 you want get it. Charge your phone, download drivers and MSM Tool from de link below, follow the tutorial. After you flash MSM tool in EDL mode, you will get OS 9, set up your phone and you will receive an OS 10 OTA update, update and after check if you have L1 Widevine certificate, if so, continue and you will receive a new OTA update to OS 11 last build. You don't need to root to get back L1. MSM toll will wipe your full data and relock the bootloader.
I have the same model and used this tutorial and this MSM tool for 3 times, go ahead!
Here it is:
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com

If you have problems with Qualcomm drivers!
Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide
Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.
www.thecustomdroid.com

UnwindingThree8 said:
I got myself a second hand oneplus 7 pro gm1913, coming from a oneplus 5t. it's running the the latest OOS fully stock but widevine l3. Can someone help me on how to fix this. I've been reading up but i am out of the loop. This MSM tool seems to be a way to fix it. Flash back to 9 to hopefully get back widevine l1 and then update to 10 and to 11. Where can i get this msm tool or do i need to root to get back L1. I have no idea where to begin. It's all changed compared to the 5T. I feel like a total newbie again
Click to expand...
Click to collapse
Did you fixed the issue with MSM tool?

I fix this issue by flashing via MSM Tool using latest android 10 of OOS, then from that, you can just upgrade to android 11 as usual. As a matter of fact, I still manage to have widevine l1 even after opening the bootloader. But I went to install crdroid 8.6 and that messes up the widevine again. Well, atleast I know exactly how to fix it.

This thread must move to Q&A Forum.

madhuranand007 said:
This thread must move to Q&A Forum.
Click to expand...
Click to collapse
Spoiler: Thread moved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just report a thread when it needs maintenance

Hello,
Do you guys think EU, NA, IN firmwares aren't equal when it comes to DRM restrictions/restoration ?
I'm talking with a USA guy who can restore DRM L1 with MSM (he uses NA firmwares) on a A12.1 custom rom
Doing the same process with the same firmware but EU builds won't restore widevine L1..
What a mess
Your feedbacks are highly appreciated

ps : quote me so i won't miss your answer

Neil_Armstrong_ said:
Hello,
Do you guys think EU, NA, IN firmwares aren't equal when it comes to DRM restrictions/restoration ?
I'm talking with a USA guy who can restore DRM L1 with MSM (he uses NA firmwares) on a A12.1 custom rom
Doing the same process with the same firmware but EU builds won't restore widevine L1..
What a mess
Your feedbacks are highly appreciated
Click to expand...
Click to collapse
I don't think they are equal. I have a IN version OP7Pro and I had widevine l3 issues. I flashed OOS 10 through MSM tool and updated with system update and it didn't do anything. I am still on L3. That means things are different.

luarpc said:
You will only get L1 Widevine after update from OS9 to OS10, on OS 9 you want get it. Charge your phone, download drivers and MSM Tool from de link below, follow the tutorial. After you flash MSM tool in EDL mode, you will get OS 9, set up your phone and you will receive an OS 10 OTA update, update and after check if you have L1 Widevine certificate, if so, continue and you will receive a new OTA update to OS 11 last build. You don't need to root to get back L1. MSM toll will wipe your full data and relock the bootloader.
I have the same model and used this tutorial and this MSM tool for 3 times, go ahead!
Here it is:
[MSM Tool] Guac for All
To everyone who donated, I love y'all. This took a really long time to get lol but it's straight from support and I did not make any modifications to it; I hope it helps a lot of people. The revision is listed in the archive, I believe it's...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi bud, followed these steps and followed the steps of flashing MSM on the link attached and updated through to OoS10 and still at L3. Using GM1913 (EU OP7 Pro). any suggestions?

Mister_T_97 said:
Hi bud, followed these steps and followed the steps of flashing MSM on the link attached and updated through to OoS10 and still at L3. Using GM1913 (EU OP7 Pro). any suggestions?
Click to expand...
Click to collapse
It worked with me. I'm using a Custom ROM now with L1. Try to update to last build OOS 11.9. Check if you have L1. There are people who get L1 flashing Magisk. If not try to flash OOS 11 on 2 slots, a and b.

Mister_T_97 said:
Hi bud, followed these steps and followed the steps of flashing MSM on the link attached and updated through to OoS10 and still at L3. Using GM1913 (EU OP7 Pro). any suggestions?
Click to expand...
Click to collapse
Try this too if doesn't work the other way.
Steps to go enable Widevine L1.
• Flash OOS 11 stable. eg.11.0.5.1
• Flash Magisk then enable Zygisk + denylist.(in denylist you should select show system apps in three-dot menu,then search gms, select com.google.android.gms and .gms.unstable)or use Magisk v23.0 for test purpose.
• Reboot.
• Verify if you have L1 working using app like DRM info.
• Local upgrafe OOS 11 stable (preferably same build).
• Reboot.
• Verify if you have L1 working using app like DRM info.
Note: you only need to do this once

How To Guide [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.
Safely convert regions (includes T-Mobile) as well as restore the ability to use OOS12 after using Indian MSM to recover from a brick (Windows only)
It seems lots of us have had to use the India 9 Pro MSM to recover our devices and in the process, we lose the ability to go back to OOS12 or ROMs based on that firmware because the touchscreen stops working and also trying to convert T-Mobile...
forum.xda-developers.com
**I forgot that OnePlus screwed up the wiping script on 11.2.10.10 so after discovering I couldn't root my device, I have attached 11.2.4.4 that is modded to flash to Indian variants as well. It works on my device in the same manner described in this post. If you use 11.2.10.10, you won't be able to unlock the bootloader and have a working phone, it will kick you to recovery with an error message and you can wipe system cache and it will act like it's booting but it never will. Only flash 11.2.10.10 if you are planning to stay with a locked bootloader or if you're going to OOS 12.**
I found this updated MSM Tool and figured that people would appreciate it.
Source of updated MSM Tool: https://yun.daxiaamu.com/OnePlus_Roms/一加9/9008线刷救砖包氧OS 11.2.10.10/
As an added bonus, I added multi-target support. If you have flashed your global OnePlus 9 with Indian firmware, this package may help you get back to global software. I have tested it by intentionally flashing my global 9 to India 9 Pro firmware again and I can confirm that it does work. Choose India in the Target dropdown box.
As for the settings for flashing Indian firmware back to global, I was getting the dreaded "device not match image" until I left sha256 checked and use lite firehose *unchecked*. I know this flies in the face of normal convention and I'm sure this will lead to some people having Sahara errors and I unfortunately don't know how to fix that. I would assume that when you have a device that's actually booting that you shouldn't need the lite firehose anyway. It wouldn't surprise me if some people find that they need a different combo. In order to get the OP9P firmware (which I also modified with multi-target to force it to flash to global because it wouldn't do it without the mod) to flash my global unit so I could test this, I had to uncheck Sha256 check and I left use lite firehose checked, so try playing with different combos instead of just declaring it doesn't work and please report which combos worked for your device so others can see.
It's honestly a real headache when you have to flash the Indian 9 Pro firmware because it breaks the ability to go to OOS12 unless you can flash back with the global MSM and clear whatever flag is being set that makes it think it's an Indian 9 Pro so having a tool available to be able to go back to global firmware should be a great boon for those of us who have a serial flashing problem lol.
Pro tip: Start the app and click Start before you connect your phone so it's already looking for the device when it reboots. You can use adb reboot edl to go right to edl mode rather than having to use the obnoxious key combo. If the process fails, press and hold volume up and power until the phone reboots to the OS and you can try again.
Screenshot of success:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
11.2.10.10:
3.56 GB file on MEGA
mega.nz
11.2.4.4: https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs
EDIT: I just tested this a second time, taking my device back to Indian 9 Pro and then using this MSM again. It flashed exactly the same way, giving me the device not match image error until I left Sha256 checked and unchecked use lite firehose.
EDIT 2: See ** message at the top.

*deleted*

Thank you! I'll try it as soon as i need to MSM again

Hey guys.
After bricking my phone and getting into a eternal looping black screen with no hopes to solve it but to send it over to repair, I tried what @EtherealRemnant told me and it did work!!
1st the Indian MSM for OP9Pro and then this patched MSM.
When I ran the MSM tool I just did exactly what the post says. Checked sha256 and unchecked "Lite Firehouse" just like in the pic below and it just worked. I used the Vol+ and Vol- key combo pressed while plugging the Original OnePlus 9 USB-C cable to get to EDL mode after flashing the OP9PRO and skipping the initial config in order to get to EDL again and flash the magical MSM .ops file provided.
Thanks again for this

Hi, i have a good story.
My Oneplus 9 LE2110 got hardbricked some weeks ago and i wasn't able to find any MSM working for my device, until i found that the 9 Pro India MSM worked and i recovered my phone. But somehow, after flashing the normal OP9 firmware (through recovery because of global/india/europe MSM not working), and updating to OOS12 by OTA, my touchscreen just wasn't working on it, just was working on OOS11 and A12 custom roms. I decided to use Nameless but i just couldn't live thinking that OOS12 (and probably next updates) would never work again on my phone.
So eventually i found your post, tried your patched MSM and... IT WORKED AT THE FIRST TRY! my phone woke up on global OOS, i updated to latest A11 and installed OOS12 through OTA and my device (and touchscreen) are working perfectly! Thank you for your work!
If anybody has a bricked LE2110 with no screen, or you can't find any MSM working on your phone, just try this one. Thanks again @EtherealRemnant

@blosk It makes me so happy to see people benefiting from this! I originally made it for myself but when people started messaging me for help, I figured it was time to share. You are the third person in the last few days that I know of who had success!

Thank you for this @EtherealRemnant It is just what I needed.

EtherealRemnant said:
@blosk It makes me so happy to see people benefiting from this! I originally made it for myself but when people started messaging me for help, I figured it was time to share. You are the third person in the last few days that I know of who had success!
Click to expand...
Click to collapse
When I try to use either msm it gives me the Param preload device does not match image error I tried all the options switch around (sha256, lite firehose)

stez827 said:
When I try to use either msm it gives me the Param preload device does not match image error I tried all the options switch around (sha256, lite firehose)
Click to expand...
Click to collapse
Are you selecting the correct option in the dropdown?
If you are flashing a global unit that is still running global software, choose O2 in the dropdown. If you are flashing a global or other unit that was flashed with Indian 9 Pro, choose India in the dropdown.
Flashing India only seems to work with Sha256 checked and lite firehose unchecked so far.
Try changing the target to global as well just in case. Also try it with no target selected.
There is not a lot of troubleshooting that can be done here but you can try flashing an India OTA to get Indian firmware on both slots and see if that works. You can also try the oldest version India downgrade package and see if that helps.
If these ideas don't work, I don't know what to tell you. You're the first who couldn't get it to work so far. I have three PMs in my box from people who used the tool and haven't posted in this thread.

EtherealRemnant said:
Are you selecting the correct option in the dropdown?
If you are flashing a global unit that is still running global software, choose O2 in the dropdown. If you are flashing a global or other unit that was flashed with Indian 9 Pro, choose India in the dropdown.
Flashing India only seems to work with Sha256 checked and lite firehose unchecked so far.
Try changing the target to global as well just in case. Also try it with no target selected.
There is not a lot of troubleshooting that can be done here but you can try flashing an India OTA to get Indian firmware on both slots and see if that works. You can also try the oldest version India downgrade package and see if that helps.
If these ideas don't work, I don't know what to tell you. You're the first who couldn't get it to work so far. I have three PMs in my box from people who used the tool and haven't posted in this thread.
Click to expand...
Click to collapse
I tried all those trouble shooting steps none of which worked my phone is a T-Mobile OnePlus 9 but I bricked it when trying to convert to global but was able to bring it back with the Indian 9 pro msm then flash global it's after that and have been running nameless for a while now but now I need to update to c.48 to stay up to date with nameless could my phone being an le2117 not and le2115 have made an actual difference even though there is no hardware difference

stez827 said:
I tried all those trouble shooting steps none of which worked my phone is a T-Mobile OnePlus 9 but I bricked it when trying to convert to global but was able to bring it back with the Indian 9 pro msm then flash global it's after that and have been running nameless for a while now but now I need to update to c.48 to stay up to date with nameless could my phone being an le2117 not and le2115 have made an actual difference even though there is no hardware difference
Click to expand...
Click to collapse
It could if it's recognizing it as a T-Mobile model. I can modify a tool to flash T-Mobile models but it will take me a bit because it's a huge file to upload.

EtherealRemnant said:
It could if it's recognizing it as a T-Mobile model. I can modify a tool to flash T-Mobile models but it will take me a bit because it's a huge file to upload.
Click to expand...
Click to collapse
That would be awesome don't be in any rush I may not be able to tinker with my phone today as I really need it to be working even if it's on an outdated version of nameless but it would be amazing if you could do that

stez827 said:
That would be awesome don't be in any rush I may not be able to tinker with my phone today as I really need it to be working even if it's on an outdated version of nameless but it would be amazing if you could do that
Click to expand...
Click to collapse
Is the error saying unsupported target at all? If it's not I don't think it will make a difference but I don't mind doing the mod regardless.

EtherealRemnant said:
Is the error saying unsupported target at all? If it's not I don't think it will make a difference but I don't mind doing the mod regardless.
Click to expand...
Click to collapse
It says device does not match image not unsupported target

It's also possible that Nameless changed something that is causing the device not to be recognized correctly. If you flash the 9 Pro MSM and then immediately use the modded MSM it should work in theory but I don't have any experience with these T-Mobile models.

EtherealRemnant said:
It's also possible that Nameless changed something that is causing the device not to be recognized correctly. If you flash the 9 Pro MSM and then immediately use the modded MSM it should work in theory but I don't have any experience with these T-Mobile models.
Click to expand...
Click to collapse
When I first tried it that's what I did flashed India 9 pro msm then tried the fix msm but no luck and it being a T-Mobile model theoretically shouldn't make a difference as it's the same hardware just a different model number

stez827 said:
When I first tried it that's what I did flashed India 9 pro msm then tried the fix msm but no luck and it being a T-Mobile model theoretically shouldn't make a difference as it's the same hardware just a different model number
Click to expand...
Click to collapse
Well you're the first person this hasn't worked for so I'm grasping at straws trying to figure out why.

EtherealRemnant said:
Well you're the first person this hasn't worked for so I'm grasping at straws trying to figure out why.
Click to expand...
Click to collapse
Yeah oh something else I have done is I originally used to EU9pro MSM but that seems to be very unlikely to have done anything as I used the Indian 9pro MSM

stez827 said:
Yeah oh something else I have done is I originally used to EU9pro MSM but that seems to be very unlikely to have done anything as I used the Indian 9pro MSM
Click to expand...
Click to collapse
Yeah I doubt that's the issue. It's strange that you're not getting unsupported target on either selection in the drop-down though. You should get it on the O2 for sure since you used the India MSM last.

EtherealRemnant said:
Yeah I doubt that's the issue. It's strange that you're not getting unsupported target on either selection in the drop-down though. You should get it on the O2 for sure since you used the India MSM last.
Click to expand...
Click to collapse
Oh I get unsupported target on O2 but not India sorry

Question Having issues after Converting OnePlus 9 5G LE2117 to Global

Hi everyome,
I have a OnePlus 9 5G LL2117. I have used the MSM Global tool about 3 weeks ago to convert it to GLobal (LE2115) Oxygen OS & ran Oxygen OS 12 fine w/ no issues.
I did a soft reset last night and when my phone restarted I saw it said it had No Sim/network detected and emerngecy calls only. I tried the MSM converstion tool again & it does restore the phone to OxygeOS 11 but the phone model is still LE2117. Even the softare updates say they are for LE2115.
What should I do?
See the attached phtoos below. I really would appreciate some help in this matter. The phone works fine for the moment.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before, the device was just fine and it showed in the about section as LE2115.
Now after using the MSM tool : https://forum.xda-developers.com/t/...r-other-firmware.4277169/page-3#post-85143501
Now, when I go to software update it prompts me to install to something meant for LE2115. I already did install an Oxygen OS 11 update meant for LE2115 and I'm still able to use it on Verizon
If, I do install this update as I tried once before. I'm out of luck as the SIM is disabled and cell service will NOT WORK.
This was never an issue when the phone was originally converted to global 3 weeks ago & I even installed the C.61 update & worked fine on Verizon.
What do I do?
Thanks so much

You've completely converted. Of course your gonna get updates for the global unit. Not 100% sure maybe someone else can chime in but you need to back-pedal. Get back to where you were. I'd try using your correct version of msm tool. Not global version. Use T-Mobile

Yeah but then how come last time my model was showing as LE2115? and I was able to update to Android 12 fine?

luckychukiye said:
Yeah but then how come last time my model was showing as LE2115? and I was able to update to Android 12 fine?
Click to expand...
Click to collapse
You didn't update without issues so that's null and void.

Alright. What should I do? Keep it on this & try to update later? Oxygen OS updater does seem to detect the phone can be updated. .
Thanks for the confirmation of it being converted to Global

There shouldn't be any issues with your device running global firmware as the hardware is largely the same. You would be the first one I will have heard of that can't run global software. Are you saying that since your MSM you actually tried updating to C.61 and lost the radio again or are you just assuming that you will? I would go through the update process and if you lose the radio, factory reset, and see if it's just something that's happening with the update causing problems because there is no reason it should be breaking.

When I last did the MSM tool conversion 2 weeks ago it update to Oxygen OS 12 & I updated to C.61 right before I did that accidentally soft reset. It was working fine.
After I did the MSM tool conversation a day ago again and tried to update to C.64 I lost cell radio.
I just got this OnePlus 9 in December/January and even back then I had issues updating to Oxygen OS 12 but was told to wait by OnePlus themselves. What do you think?
As you said my phone is in global so it should run fine? Maybe wait and try again later? Should I do it via Software Update or Oxygen OS updater?

It makes no sense that you would lose radio updating to OOS12, I've never heard of anyone else losing it. There are lots of these T-Mobile converted to global devices out there because they were able to be gotten so cheaply from T-Mobile so if it was a real issue, it would be reported a lot more. Also, the update to C.61 is incremental right now, so you can also just choose to take C.48 and wait.

Yeah. For C.48 though. Should I update to it via Oxygen OS Updater from the Play Store or Software update? Right now it prompts me to do this i software update.
Also, updating to 12 one thing I didn't like is the notifications and extra bundles apps 11 d didn't have

Also, is it normal for my device to still say LE2117 on the about page?

Verizon/Visible on OxygenOS 12?
I installed the C.44 update hoping all of the "No Service" issues of the initial release would have been fixed, but I still could not connect to the Verizon network. After 2 hours of chatting with an online rep at Visible (Verizon's MVMO) she...
forum.xda-developers.com
Like this user

EtherealRemnant said:
It makes no sense that you would lose radio updating to OOS12, I've never heard of anyone else losing it. There are lots of these T-Mobile converted to global devices out there because they were able to be gotten so cheaply from T-Mobile so if it was a real issue, it would be reported a lot more. Also, the update to C.61 is incremental right now, so you can also just choose to take C.48 and wait.
Click to expand...
Click to collapse
Also, oddly when I did convert the phone back to the TMObile version before converting to Global. It had no signal or anything despite saying the phone is network unlocked. Why is this?

Quite frankly I am stumped as to what your issue could be. If you're having it on stock software too, it's likely hardware.

I had the same issue converting. I found that flashing this fixed it for me:
[TMO] OOS/COS DATA FIX
TO CLARIFY THIS IS A ROOT ONLY FIX After gaining root install given module. Data is now retained. Even after reboot(s). No empty slot or waiting. Issue is TMO variant is showing muli sim. So props were added to make it like a conversion to single...
forum.xda-developers.com
You would need to be rooted though, as this is a magisk module. Maybe if we can get a tweaked stock rom with the sysprop updated, we wouldnt need to root.

Thanks
How would I go about doing this from where I am now? since I'm on OS 11. What would I need to do to flash this?

I wonder why it worked fine before

Try this MSM. It's modded to flash full global 11.2.10.10 to T-Mobile variants. The modded MSM Tool you used seems to be leaving traces that make the phone think it's dual SIM in OOS12, same thing that happens with the India firmware on global units. I modded this one myself and it's untouched stock global 11.2.10.10 that was just modded to target TMO instead of O2.
3.57 GB file on MEGA
mega.nz
As global units aren't dual SIM either, full global firmware should not have the dual SIM bug. If this doesn't work, that module seems to be your only choice.

Also., what if I go the custom rom route?
Would I need to do anything with Magisk ? There are roms that have full Verizon support

luckychukiye said:
Also., what if I go the custom rom route?
Would I need to do anything with Magisk ? There are roms that have full Verizon support
Click to expand...
Click to collapse
Not in my experience, no. It's an OOS bug. I got it with Indian firmware and with ColorOS.

Yeah. Again this phone was working fine so I don't think I need to do any of that stuff. The phone is working right now as I'm typing this.
What rom are you using and on what network? V Verizon as well?
I even called OnePlus and they confirmed people were complaining about Verizon SIM not working on their OnePlus phoens and told me it was a software bug

Question Poco X3 Pro stuck on MIUI 12.5 and can't update

Hi all,
i've just bought a Poco X3 Pro from Amazon and i was playing with it in order to decide if i'll keep it or not. The first thing that i wanted to do, was to update to the MIUI 13 to check if it was slower on that software, but the phone doesn't see any update and it is stuck at MIUI 12.5 (Global 12.5.5.0 RJUEUXM which seems to be the EEA/EU version). I've tried to search for update, i've tried to change the region, to enable "Receive updates before" but nothing changed.
I've tried also to download the update to use the "Choose package" option but it doesn't accept anything that i give to him. This is a first for me.
Is there anything else that i can try to do instead of unlocking the bootloader to use miflash? Just because i don't want to wait the 168 hourse of the process.
Thanks in advance!

nope, for me you need to unlock the bootloader to install any custom roms miui/aosp that's the only way i think.

Z4buz4 said:
Hi all,
i've just bought a Poco X3 Pro from Amazon and i was playing with it in order to decide if i'll keep it or not. The first thing that i wanted to do, was to update to the MIUI 13 to check if it was slower on that software, but the phone doesn't see any update and it is stuck at MIUI 12.5 (Global 12.5.5.0 RJUEUXM which seems to be the EEA/EU version). I've tried to search for update, i've tried to change the region, to enable "Receive updates before" but nothing changed.
I've tried also to download the update to use the "Choose package" option but it doesn't accept anything that i give to him. This is a first for me.
Is there anything else that i can try to do instead of unlocking the bootloader to use miflash? Just because i don't want to wait the 168 hourse of the process.
Thanks in advance!
Click to expand...
Click to collapse
Try to use XiaoMiTool V2, it should update your phone to latest stock rom without needing to unlock bootloader.

The 13.0.2 (stable beta) EEA Rom was pulled as far as I know, but the predecessor 13.0.1 has never been available via OTA since then. It will probably only be possible again with the next update to bring a 12.5.5 EEA device to MIUI 13 via OTA.

thorin0815 said:
The 13.0.2 (stable beta) EEA Rom was pulled as far as I know, but the predecessor 13.0.1 has never been available via OTA since then. It will probably only be possible again with the next update to bring a 12.5.5 EEA device to MIUI 13 via OTA.
Click to expand...
Click to collapse
So what i am experiencing should be normal because i've got the EEA version?
Popletenec said:
Try to use XiaoMiTool V2, it should update your phone to latest stock rom without needing to unlock bootloader.
Click to expand...
Click to collapse
Never used it before, i'll search for it. Thanks!

At least I've read of some cases in a German forum, so I assume that's why it's not updated for you either.

I have the same problem. Got an X3 Pro off Ebay. Came with a Euro charger in the box but ROM shows as MIUI 12.5.5.0 Global version in the settings section on the phone.
Tried to use XiaoMiTool v2 but that detects the ROM as EEA.
So I am stuck not knowing what to do.
I want to stay bootloader locked, for now any way, so I am really frustrated.

gandalf_grey91 said:
I have the same problem. Got an X3 Pro off Ebay. Came with a Euro charger in the box but ROM shows as MIUI 12.5.5.0 Global version in the settings section on the phone.
Tried to use XiaoMiTool v2 but that detects the ROM as EEA.
So I am stuck not knowing what to do.
I want to stay bootloader locked, for now any way, so I am really frustrated.
Click to expand...
Click to collapse
EEA/EU versions are also Global ones, but with EU law restrictions and they are named Global as well. Check the underlined part in your phone, does it have EU in it as well?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I've tried with XiaoMiTools v2. It sees as the last possible update for the EEA the 12.5.5.0 update and it's unable to install the MIUI 13 EEA that i've previously downloaded. It doesn't neither allow me to install the global one, asking for the unlock of the bootloader which i'm still waiting.

There are two types of update files. One for the recovery, the other for fastboot. Are you sure you downloaded the right one for the Xiaomi tools?
Here you can download both types for 13.0.1:
https://xiaomifirmwareupdater.com/archive/miui/vayu/
For 13.0.2 I only saw the update for the recovery, but I've only scanned it for some seconds.

thorin0815 said:
EEA/EU versions are also Global ones, but with EU law restrictions and they are named Global as well. Check the underlined part in your phone, does it have EU in it as well?
View attachment 5661291
Click to expand...
Click to collapse
Yep, shows RJUEUXM.
BTW, what sort of EU law restrictions are we talking about?

The restrictions refer to Poco/Xiaomi and not to us users. User privacy is protected by EU laws. Well, at least in theory. ;-)

LOL
Many thanks for explaining.
Sounds good, in theory.

thorin0815 said:
There are two types of update files. One for the recovery, the other for fastboot. Are you sure you downloaded the right one for the Xiaomi tools?
Here you can download both types for 13.0.1:
https://xiaomifirmwareupdater.com/archive/miui/vayu/
For 13.0.2 I only saw the update for the recovery, but I've only scanned it for some seconds.
Click to expand...
Click to collapse
You're right, i'm an idiot :'D I've tried to use the recovery one with XiaomiMiTools. I'll try with the fastboot one and i'll update you about if it works.
Thanks!

Am in the UK and have received the 13.0.1 update via OTA about a week ago.

Hmm, have the same problem with my Poco X3 Pro. Bought it as new back then and updated MIUI whenever possible. Now I am stuck at 12.5.5.0 global and cannot update. Even downloading the latest update again (like suggested by Xiaomi support) does not work - it downloads but just doesn't install.
If I try to install that download manually with stock Updater app it says that the downloaded update (which was downloaded by that app itself BTW) cannot be veryfied. So I am completely locked to 12.5.5.0 it seems.
Since I do not want to root the phone nor apply a custom recovery or so - is there any other possibility to finally update to latest MIUI?

You all can't wait to flash even buggier MIUI 13, because... why?! Does Poco give out rewards for having the latest build? For what reason do you NEED it so much?

Personally I'd like to stay uptodate, especially for Android and Security Patches. Being stuck at 12.5.5.0 left me with Android 11 (at least this was shown) and very old security patches. If there es an easy and convenient way to get those updates in w/o hazzling around with root, custom recovery, several tools and PC - I am in, just point me to it.
I finally managed to update. After my 12.5.5.0 was unable to update itself with the last version it downloaded itself (which for me was a clear bug and hence another reason to move on) I downloaded latest official global stable MIUI13 for Poco X3 Pro and installed it with the system updater app. Worked flawlessly.

I have the same problem, but with MIUI 13.0.1.0, clearly there are several new updates for EEA after it, but it doesnt see any OTA, a manual download just installs the same version, and any new official stabel non beta packages it outrigth refuses to install in the manual updater u can unlock in the upodater app.
Oddly for the official stable versions i got off the update tracker from this forum, clearly labelled as non beta, the updater errors tellign me its a version for beta testers so i cannot install it.

Hi all i tried the same since morning and did not want to lose all my business or mobile banking apps ...
The easiest way to upgrade my MIUI was to switch Region from Germany to UK.
I imediatley got the OTA Option for MIUI 13. Maybe later will try to switch to India
So no need for FASTBOOT or wiping your data!