How To Guide 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)

Search This thread

Loshim

Member
Mar 19, 2020
19
0
what do you mean when you say this? "and then do the OTA process to get back to where you want to go."

i finish this step "factory reset it in the settings", now my phone dont have more tmobile stuff, Can I leave it like this or what is the next step?
 

EtherealRemnant

Senior Member
Sep 15, 2007
4,430
1,745
38
Denver, CO
Google Pixel 7 Pro
what do you mean when you say this? "and then do the OTA process to get back to where you want to go."

i finish this step "factory reset it in the settings", now my phone dont have more tmobile stuff, Can I leave it like this or what is the next step?
If you factory reset and lost the T-Mobile stuff, check settings and see what version you are running. The loss of the T-Mobile stuff sounds like a successful conversion.

Also, I mean install the OTAs to get to the version you want to use once the conversion is done.
 
It's not the MSM Tool that's borked, it's the ROM itself.
ok maybe i missed it in the thread but how do you know its the rom?
here is the most recent reply i have from oneplus in regards to the issue:

Hi Joseph

Greetings from OnePlus Customer Support. Hope you are in best of your health!

We have escalated this case to our relevant team and they have provided us update on the bootloader unlocked failed issue.

Scenario1: The unlock code/token does not correspond with IMEI. If the reason is 1, we recommend you to verify if you have applied the unlock folder with correct unlock code.

Scenario1: The device was booted by you previously and Param was broken. If the reason is 2, we could only recommend you to firstly contact TMO to help to flash the device, if they can't then send the device to our service center.

We believe we have explained your situation clearly, if you still have any other questions, please feel free to revert to us.

Hope you and your loved ones stay safe and healthy!
 
It's not the MSM Tool that's borked, it's the ROM itself.
So I went ahead and figured out my device was still reading as the OP9 Indian variant and was stuck on Tmobile variant. I used the OP9 Pro Indian variant again to get it off of the fiasco I created, used the Tmobile MSM targeted at the Indian variant. But the device still read as the OP9P Indian. That's when it all clicked for me and I made a MSM Tool to read the device as OP9P Indian but flash me the regular OP9 Indian variant. Indian on Indian and back on the correct model. This Fixed my bootloader unlock issue and I can now use FBE to do whatever deed I may need to do :) Thought i would share my process. I could upload my MSM I made if anyone could use it or needs it.
 
  • Like
Reactions: EtherealRemnant

EtherealRemnant

Senior Member
Sep 15, 2007
4,430
1,745
38
Denver, CO
Google Pixel 7 Pro
So I went ahead and figured out my device was still reading as the OP9 Indian variant and was stuck on Tmobile variant. I used the OP9 Pro Indian variant again to get it off of the fiasco I created, used the Tmobile MSM targeted at the Indian variant. But the device still read as the OP9P Indian. That's when it all clicked for me and I made a MSM Tool to read the device as OP9P Indian but flash me the regular OP9 Indian variant. Indian on Indian and back on the correct model. This Fixed my bootloader unlock issue and I can now use FBE to do whatever deed I may need to do :) Thought i would share my process. I could upload my MSM I made if anyone could use it or needs it.
It's so damn stupid that we have to juggle 500 MSM Tools to fix all this crap. OnePlus really needs to get it together. Glad that you figured it out though.
 
  • Like
Reactions: YourLocalDund33

AtoZ0to9

Senior Member
Jul 27, 2007
9,705
3,028
OnePlus 5T
OnePlus 9
Ah, forgot. Guess I'm just behind. So far I've rooted and debloated c.61. I'll look into some modules possibly. I mainly just want to strip the phone down to what I need, try to black out everything, wish swift themes had a12 support. Harden up the permissions, maybe sandbox all social apps. I'm just playing around. What can FBE do for me other than flash?
 

EtherealRemnant

Senior Member
Sep 15, 2007
4,430
1,745
38
Denver, CO
Google Pixel 7 Pro
Ah, forgot. Guess I'm just behind. So far I've rooted and debloated c.61. I'll look into some modules possibly. I mainly just want to strip the phone down to what I need, try to black out everything, wish swift themes had a12 support. Harden up the permissions, maybe sandbox all social apps. I'm just playing around. What can FBE do for me other than flash?
FBE can extract images from a payload.bin but it's mostly just useful for flashing OTAs directly in fastbootd (less likely to have something fail than using fastboot in my experience as long as you don't ignore any errors that crop up).
 
  • Like
Reactions: AtoZ0to9
So I went ahead and figured out my device was still reading as the OP9 Indian variant and was stuck on Tmobile variant. I used the OP9 Pro Indian variant again to get it off of the fiasco I created, used the Tmobile MSM targeted at the Indian variant. But the device still read as the OP9P Indian. That's when it all clicked for me and I made a MSM Tool to read the device as OP9P Indian but flash me the regular OP9 Indian variant. Indian on Indian and back on the correct model. This Fixed my bootloader unlock issue and I can now use FBE to do whatever deed I may need to do :) Thought i would share my process. I could upload my MSM I made if anyone could use it or needs it.
Can you please upload the MSM tool you made? I think I'm facing a similar issue so it'll help me troubleshoot. Thanks.
 
I cannot find a clear guide to convert the le2127 to global. One newer post says you can side load C.62 EU or C.63 NA if your on C.17 or C.19 Them another post says to downgrade from 12 to 11 With a modified MSM tool then use the FBE tool but it sounds like that's for the TMO-OP9 ?
What is your problem?
 

EtherealRemnant

Senior Member
Sep 15, 2007
4,430
1,745
38
Denver, CO
Google Pixel 7 Pro
I cannot find a clear guide to convert the le2127 to global. One newer post says you can side load C.62 EU or C.63 NA if your on C.17 or C.19 Them another post says to downgrade from 12 to 11 With a modified MSM tool then use the FBE tool but it sounds like that's for the TMO-OP9 ?
Because of the need to have the custom radio for the OP9P, you need to use the modified EU MSM Tool from that forum to do the conversion. You will lose the radio otherwise.
 

Mehedi27

Member
Feb 20, 2014
29
0
Try this one.


That one is also multi target. Both of these have been tested, I don't know why it's not working for you. You can also try not selecting a target and see what happens, I have found I don't always need to select the target if my device firmware hasn't been too corrupted.

Beware that with this one, you can't unlock the bootloader until after you go to OOS12 because OnePlus bugged the erase script on 11.2.10.10.
Why is this happening? How it can be solved
 

Attachments

  • IMG20220929141919.jpg
    15.4 MB · Views: 24

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    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 variants, the fastboot scripts are just bricking them. Well I found a fix for these issues. Those who just want to convert can skip the MSM Tool process and get right to the conversion process as long as they're already running OOS11.

    First thing is first, you need to be on OOS11. If you have a T-Mobile variant and you have flashed it with India firmware, you have to use a modded T-Mobile MSM: https://forum.xda-developers.com/t/...ariant-flashing-as-well.4454357/post-87050821

    If you have a T-Mobile variant that hasn't used the Indian 9 Pro MSM Tool, is on OOS12, and you're just wanting to convert, you need this tool: https://forum.xda-developers.com/t/oneplus-9-11-2-22-2-t-mobile-msm-download-tool.4276119/

    If you have a global variant or a global variant that has been flashed with Indian firmware, you can use this MSM (choose O2 for global or India for India in the Target dropdown, check Sha256, uncheck use lite firehose, it's a multi-target MSM Tool): https://mega.nz/file/ZWtGxTSb#UZ6aSOR2UTYrCao2fQNJ1IN5LSxPNBOxzel1kihnnJs

    If you don't know how to use the MSM Tool, there are other guides around here, that's outside of the scope of this post.

    Once you are back on OOS11, unlock the bootloader. We also need USB debugging enabled.

    Now we need a tool called Fastboot Enhance. This wonderful tool allows you to directly flash OTAs from fastbootd and it doesn't have the same brick risk that flashing with fastboot scripts does.

    Download it and unzip it somewhere.

    Next we need the OOS11 global downgrade package (or whatever region you are wanting to switch to, global is recommended for T-Mobile variants) from here: https://forum.xda-developers.com/t/oneplus-9-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4254579/

    Fire up command prompt in the folder you have your platform tools and run:

    adb reboot fastboot (if you do adb reboot bootloader you will then need to type fastboot reboot fastboot to get to fastbootd)

    This will take you into fastbootd. It will have a screen that has three different languages to choose from on it. Go ahead and fire up Fastboot Enhance now.

    It may take a few seconds for the app to recognize the device but when you see it in the list, double-click it to get to the main screen.

    Screenshot 2022-06-23 192151.png

    Check that it says that the device is in fastbootd. Now we just need to click Flash Payload.bin and choose the OTA we downloaded earlier (we don't even need to extract the zip, the app does that for us). If it pops up with an unrecognized partitions error, you're either not in fastbootd, you didn't MSM back to stock (you cannot do this with a custom recovery), or you grabbed an OOS12 OTA. Do not continue and check that everything is correct otherwise you will brick and have to start all over with the MSM Tool. Likewise, if it pops up an alert about cow partitions, don't continue. Go to the partitions screen and search for cow and delete them all.

    Once it's done, boot the device, factory reset it in the settings (this is mandatory as Fastboot Enhance does not erase the device like a normal downgrade would do and this can cause problems), set it back up, and then do the OTA process to get back to where you want to go.
    1
    THANK YOU SIR, true gentleman. Your post I guess was the only one convincing enough that it was finally brushed through the beta testing phase enough that it would be worth trying. No real risk here considering its just using that awesome tool you mentioned in the post, which i've never heard of. will be using for now on. Dunno about any testing with this method so i thought i would owe the community my post. i saw the sahara error post not too long ago talking about a fix with no testing yet xD that made me laugh honestly. But yeah my phone is now converted global through payload.bin flash in fastbootd. Tmo Variant had me & my girls phone networked unlocked through the one guy that was doing it for free on here a while back.. then applied for unlock code and did it officially, never tried to convert due to brick concerns, so i had the easy route through the methods involved in this post, considering i was still on oos 11 with bootloader unlocked when reading this. anyways, i think its safe to say its fixed pretty hyped to flash roms now and not get bootlooped and excited to see where this variant is gonna go! thanks again mate.
    1
    It's not the MSM Tool that's borked, it's the ROM itself.
    So I went ahead and figured out my device was still reading as the OP9 Indian variant and was stuck on Tmobile variant. I used the OP9 Pro Indian variant again to get it off of the fiasco I created, used the Tmobile MSM targeted at the Indian variant. But the device still read as the OP9P Indian. That's when it all clicked for me and I made a MSM Tool to read the device as OP9P Indian but flash me the regular OP9 Indian variant. Indian on Indian and back on the correct model. This Fixed my bootloader unlock issue and I can now use FBE to do whatever deed I may need to do :) Thought i would share my process. I could upload my MSM I made if anyone could use it or needs it.
    1
    So I went ahead and figured out my device was still reading as the OP9 Indian variant and was stuck on Tmobile variant. I used the OP9 Pro Indian variant again to get it off of the fiasco I created, used the Tmobile MSM targeted at the Indian variant. But the device still read as the OP9P Indian. That's when it all clicked for me and I made a MSM Tool to read the device as OP9P Indian but flash me the regular OP9 Indian variant. Indian on Indian and back on the correct model. This Fixed my bootloader unlock issue and I can now use FBE to do whatever deed I may need to do :) Thought i would share my process. I could upload my MSM I made if anyone could use it or needs it.
    It's so damn stupid that we have to juggle 500 MSM Tools to fix all this crap. OnePlus really needs to get it together. Glad that you figured it out though.
    1
    Ah, forgot. Guess I'm just behind. So far I've rooted and debloated c.61. I'll look into some modules possibly. I mainly just want to strip the phone down to what I need, try to black out everything, wish swift themes had a12 support. Harden up the permissions, maybe sandbox all social apps. I'm just playing around. What can FBE do for me other than flash?
    FBE can extract images from a payload.bin but it's mostly just useful for flashing OTAs directly in fastbootd (less likely to have something fail than using fastboot in my experience as long as you don't ignore any errors that crop up).