How To Guide Convert your T-Mobile (LE2127) to EU via MSM, No unlock.bin needed!

Search This thread
I see, I installed the EDL tool you linked but it doesn't want to connect to my phone, saying unsupported device.
1652124459074.png
\

Also not seeing the 9 pro in the EDL loaders for that, only the 9.
1652124580575.png


So I guess I am just going to have to wait for my unlock.bin... unless you have any ideas?
 
Mar 10, 2019
14
1
Hi XDA-developers :)

I need to convert My unlocked (t-mobile) oneplus 9 pro to dual sim global !!

Can you help me to doing this ?

I have no problem to pay who helped me?

I was try doing this by following these to methods
1 - https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/
2- https://forum.xda-developers.com/t/tmo-9-pro-modem-retention-data-fix.4292445/

and always getting [only 1 Sim working on dual sim global Rom]
..............................................................
Thanks to [email protected]

Thanks and appreciation to all the developers at XDA .

Sorry for bad English !

My telegram Ch : https://t.me/AbdulGhani_Gailan
 
Jul 25, 2022
14
3
If you don't have root or unlocked bootloader backup using MSM tool. When in the screen where you would normally flash the rom, press F8 key. You will see list of partition, password is oneplus to use backup.
I just tried this method and it was seemingly successful, but where are the backups stored? I did MSM -> F8 ->Modemst1/2 + Persist -> Check read back -> Successful

Edit: I figured it out, they're in my C: drive
 
Last edited:

Vikranthalti

Member
Aug 12, 2022
7
0
*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
*** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
*** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
*** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE



Disclaimer: I initially did not want to release this conversion because you still need to unlock the bootloader to fix modem, but this conversion lets you unlock the bootloader without needing unlock.bin. Since OnePlus's website is currently broken, the only way to backup the partitions above is via EDL. I've had the conversion tested and there seem to be no issues, and you can make the backups afterwards. Just keep in mind that if something goes wrong and the above partitions are lost, you are really screwed and there's no way back. If you are not comfortable with this, turn back now.

General notes:

  • NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
  • The T-Mobile modem is not compatible with any other variant's NON-HLOS, meaning you need to flash back the T-Mobile modem in order to have cell connectivity.
  • Dual-SIM does not work.

Prerequisites:
  • You must be SIM unlocked. This conversion will not SIM unlock you.
  • Verify "Enable OEM unlocking" is not greyed out in Developer Options
  • Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
  • Back up all data, it will be wiped.

Download:

Steps:
  1. Unzip both the conversion and modem zip files.
  2. Execute MSMDownloadTool V4.0.exe and msm normally.
  3. Connect to wifi (not sure if necessary)
  4. Go to Developer Options -> Enable OEM Unlocking. If this is greyed out, it means you are still SIM locked and didn't read the whole guide (You may need to reboot a few times, but if it stays greyed you are still locked). MSM back to T-Mobile and get it unlocked first.
  5. Reboot to bootloader
  6. Unlock your bootloader, no unlock.bin needed:
    Code:
    fastboot oem unlock
    or
    Code:
    fastboot flashing unlock
  7. Follow instructions on phone to unlock bootloader.
  8. Boot back to bootloader and flash modem:
    Code:
    fastboot flash modem_a NON-HLOS.bin
    fastboot flash modem_b NON-HLOS.bin
  9. You are done converting. Make sure to keep NON-HLOS around, you'll need to flash it after every OTA.

Fastboot method:
* The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
* You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
* Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
* Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
* Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
* When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.

Steps to convert your device to EU
  1. You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
  2. Download and unzip the conversion package:
    • EU 11.2.3.3
      MD5: cb949816fa80d5f0d984359b819426c3
  3. Boot to bootloader.
    • From adb:
      Code:
      adb reboot bootloader
    • From fastboot/bootloader:
      Code:
      fastboot reboot bootloader
  4. Execute "flash_all.bat" from the unzipped directory from step 2.
  5. Reboot into recovery, and wipe everything.
  6. Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
  7. Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
  8. Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
    Code:
    fastboot flash modem NON-HLOS.bin
  9. After each Full OTA you take in the future, you will need to repeat step 7 & 8

FAQ
  • Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
    A: You didn't read the full post.
  • Q: Why is there no conversion to Global?
    A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
  • Q: Can I re-lock the bootloader after conversion?
    A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
  • Q: Where is the Linux guide?
    A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
  • Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
    A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
  • Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
    A: MSM
  • Q: Help, "not enough space to resize [system, product, system_ext]"
    A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
  • Q: Help, something went wrong!
    A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
  • Q: Help, I see "Invalid sparse file format at header magic"
    A: Ignore this message, not an error


Fixing the About Phone page

These steps are optional, and will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
  1. You need to rooted with Magisk
  2. Download and install the magisk module: here
  3. Reboot, the About Phone page is filled out.


Issues so far (please post if you run into more):
  • Dual SIM does not work
  • Dialer's vvm doesn't seem to work with T-Mobile, might be a T-Mobile issue though.
  • You must flash the T-Mobile modem after every OTA
  • Wildvine L1 is a crapshoot, you may or may not be lucky. Worked for me with only magiskhide enabled and blocking Google Play Services, but many people not having the same luck.
What appears to work:
  • Everything else.

Much appreciation for everyone that help develop and test
@razercortex
@retryfail
@amaroney55
Hi can anyone explain how to Backup the modemst 1,2 and persist I am new to this stuff.
 

Mr Hassan

Account currently disabled
Feb 14, 2016
935
57
OnePlus 10 Pro
Hi XDA-developers :)

I need to convert My unlocked (t-mobile) oneplus 9 pro to dual sim global !!

Can you help me to doing this ?

I have no problem to pay who helped me?

I was try doing this by following these to methods
1 - https://forum.xda-developers.com/t/...7-to-eu-via-msm-no-unlock-bin-needed.4272837/
2- https://forum.xda-developers.com/t/tmo-9-pro-modem-retention-data-fix.4292445/

and always getting [only 1 Sim working on dual sim global Rom]
..............................................................
Thanks to [email protected]

Thanks and appreciation to all the developers at XDA .

Sorry for bad English !

My telegram Ch : https://t.me/AbdulGhani_Gailan
On fb one page available they also can do it but he have his own terms & conditions
 

TheSayaMan

Senior Member
Sep 12, 2016
607
261
OnePlus 9 Pro
I have a issue with no sim detected. I have Verizon. Any fix? I went through MSM tools again to reflash because if I reflash the T-Mobile modem, I end up bricked. I have the T-Mobile model that's carrier unlocked. Thanks!
 
  • Like
Reactions: wfred

TheSayaMan

Senior Member
Sep 12, 2016
607
261
OnePlus 9 Pro
Ok, I figured it out finally after so much frustration. I used the EU MSM and reflashed then downloaded the Oxygen Updater app and performed all Global local upgrades through the app and everything is working perfectly now. I'm on current Android 12, Global with fully working phone, calls, texts, data. I don't know why doing this instead of just updating through the built in system updater would make any difference at all but it seems to have!! You will also have to root and use the magisk data fix module, otherwise it will not stick, it will keep going in and out.
 

samdaman91

Member
Aug 9, 2019
49
2
so i have a OnePlus 9 pro t-mobile and i was able to successfully put in the official Global build in it (11.2.10.10.LE15AA). i had cell service and data. however when i upgrade the phone to android 12 i lose all service. what do i do next? I have backed up my original MODEMST1/2 AND PERSIST PARTITION images before i changed my ROM.
 
so i have a OnePlus 9 pro t-mobile and i was able to successfully put in the official Global build in it (11.2.10.10.LE15AA). i had cell service and data. however when i upgrade the phone to android 12 i lose all service. what do i do next? I have backed up my original MODEMST1/2 AND PERSIST PARTITION images before i changed my ROM.

Good thinking in that regard. You may still have to flash the T-Mobile modem, iirc, which was something necessary for conversion when the device was initially released.
 

rafal.polska.b

Senior Member
Mar 22, 2015
252
64
Gdynia
This thread is for converting from LE2127 (T-Mobile) to LE2123 (EU)
My understanding is that tools and binaries used for this conversion are not correct for performing conversion from LE2121 (India) to LE2123 (EU)
So my question is: can someone to guide me how to do conversion (rebranding) from LE2121 (India) to LE2123 (EU)?
 

TheSayaMan

Senior Member
Sep 12, 2016
607
261
OnePlus 9 Pro
This thread is for converting from LE2127 (T-Mobile) to LE2123 (EU)
My understanding is that tools and binaries used for this conversion are not correct for performing conversion from LE2121 (India) to LE2123 (EU)
So my question is: can someone to guide me how to do conversion (rebranding) from LE2121 (India) to LE2123 (EU)?
Simple. Just do local upgrades to EU from IN. Keep in mind that your target ID will remain. That can't be changed.
 

User NiNaNo

Senior Member
Mar 17, 2017
60
7
So if I convert to EU OOS, can I install any custom ROM on it, even if I did not unlock the bootloader from tmobile?
 

User NiNaNo

Senior Member
Mar 17, 2017
60
7
I just used this tool to convert a Tmo 9 Pro on A12 to EU. Process worked flawlessly. However, I did not need to flash the modem in the OP. After converting, booted to system, unlocked bootloader. On the reboot after that, installed my Visible sim, and immediately got mobile data. Updated to 11.2.10.10 (I'm staying on A11). and the modem was still good.

So not sure if anyone else will have this luck, but try your sim before flashing the modem. Maybe updating to A12 while still on the Tmo firmware causes the modem to stick.
Yeah, same for me. So, the first time I convert from tmo to eu and then unlocked the phone, update to the lastest version then flash the modem but it gave me crashdump so I use msm to go back to eu again, and I just put my sim in the phone, and call, data are working for now. So I'm thinking of not flashing the modem for now.

After the update to A12, sim cannot be read, so I came back to tmo msm rom. Also, I tried the same method on the post but I think the modem seems outdated that's why I keep getting crashdump mode, how do I extract tmo modem from A12 with a locked bootloader?
 
Last edited:
  • Like
Reactions: handydandy

Appreciative

Senior Member
Mar 6, 2015
176
99
Yeah, same for me. So, the first time I convert from tmo to eu and then unlocked the phone, update to the lastest version then flash the modem but it gave me crashdump so I use msm to go back to eu again, and I just put my sim in the phone, and call, data are working for now. So I'm thinking of not flashing the modem for now.

After the update to A12, sim cannot be read, so I came back to tmo msm rom. Also, I tried the same method on the post but I think the modem seems outdated that's why I keep getting crashdump mode, how do I extract tmo modem from A12 with a locked bootloader?
Go back and read post #388. He did what you are trying to do.

Correct. I should reword that, though. You can unlock the bootloader without the unlock.bin from OnePlus, using this process, but you will still need a SIM-unlock from T-Mobile.
You do not have to be sim unlocked to unlock the bootloader on this phone. I verified you can use EU to bypass OnePlus cust-unlock.bin OR you can use the cust-unlock.bin if you choose, it works either way. But you will need to use the One+_TooL (or an equivalent method) to allow the OEM unlock toggle to be turned on: https://forum.xda-developers.com/t/...ader-unlock-enabler-engineer-decrypt.4380419/

Unless I misunderstood you, which may be the case. He said was on an mvno but it showed him as unlocked. I'm not sure about that status
 
Go back and read post #388. He did what you are trying to do.


You do not have to be sim unlocked to unlock the bootloader on this phone. I verified you can use EU to bypass OnePlus cust-unlock.bin OR you can use the cust-unlock.bin if you choose, it works either way. But you will need to use the One+_TooL (or an equivalent method) to allow the OEM unlock toggle to be turned on: https://forum.xda-developers.com/t/...ader-unlock-enabler-engineer-decrypt.4380419/

Unless I misunderstood you, which may be the case. He said was on an mvno but it showed him as unlocked. I'm not sure about that status


Yeah, I forgot that this particular method bypasses the need for SIM-unlock. My mistake.
 

CZ Eddie

Senior Member
Sep 27, 2011
6,332
2,377
Austin, TX
So, this is weird. I'm permanently SIM-unlocked. I just did it 30 minutes ago.
And while in TMO ROM, I'm able to slide the OEM Unlock toggle to enable.

So, I then MSM the EU Conversion.
But when I check there, the OEM Unlock is greyed out and I'm not able to toggle it.
I rebooted a few times with no change.

I MSM back to TMO once again and I'm still SIM-Unlocked and can still toggle the OEM Unlocking option in Developer Options.

What am I doing wrong?


EDIT:
I guess the SIM unlock just needed a few hours to completely work because I tried the EU conversion a second time about seven hours later and it's working fine now!
 
Last edited:

N1ldo

Senior Member
Nov 1, 2011
140
25
Marinha Grande / Leiria
  1. Download and unzip the conversion package:
    • EU 11.2.3.3
      MD5: cb949816fa80d5f0d984359b819426c3
  2. Boot to bootloader.
    • From adb:
      Code:
      adb reboot bootloader
    • From fastboot/bootloader:
      Code:
      fastboot reboot bootloader
  3. Execute "flash_all.bat" from the unzipped directory from step 2.
  4. Reboot into recovery, and wipe everything.

Where is this rom (EU 11.2.3.3) with that .bat file?

 
  • Like
Reactions: handydandy

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I don't think that is a good idea, maybe a last resort. You could try the method @TinkerNerd described in their post (#402) as you'd asked before. It could be that when the repair store unbricked it, the device is no longer shown as an LE2127? Just a guess. But if you have access to fastboot, there's still a lot you can try to fix things.
    It had the "unsupported device in" issue even before I bricked it lol. But I don't know how did the store unbrick my phone. I had tried using MSM with the T-mobile 11.2.6.6 package (210707). I saw him using the same repo website with me and they did not work neither. I only know that he used MSM with 210707 but don't know which exact one he got from or anything else he did to make it work. My device was showing as 2127 indian rom until I OTA it to oos12.c60+ (maybe 63) when I got to oos12 the le2127 became 2125 not sure what the rom was(maybe AA global) then I got connectivity issues so I tried to revert to oos11 and then I bricked my phone. Now my device is 2127 with acb rom(T-mobile). Thank you for the advice.
    1
    It had the "unsupported device in" issue even before I bricked it lol. But I don't know how did the store unbrick my phone. I had tried using MSM with the T-mobile 11.2.6.6 package (210707). I saw him using the same repo website with me and they did not work neither. I only know that he used MSM with 210707 but don't know which exact one he got from or anything else he did to make it work. My device was showing as 2127 indian rom until I OTA it to oos12.c60+ (maybe 63) when I got to oos12 the le2127 became 2125 not sure what the rom was(maybe AA global) then I got connectivity issues so I tried to revert to oos11 and then I bricked my phone. Now my device is 2127 with acb rom(T-mobile). Thank you for the advice.

    Yeah, if you've got the T-Mobile FW on it, it should be showing as an LE2127. As far as the error goes, I have not heard of that before now. Sorry I can't be more help on this matter. I think the method above is likely to work, though. I might be able to answer questions on other matters. Good luck and I hope you figure it out.
    1
    I believe this is because of the Indian variant (in/IN). There is a known issue when you flash IN (or have IN) firmware, it causes an issue for MSM tools. @EtherealRemnant made a thread and released a modified tool that may help you at least get back to a condition where you can use other MSM tools?

    That thread is https://forum.xda-developers.com/t/...-for-indian-variant-flashing-as-well.4454357/

    I have tagged him as he's still active and knows more about this than I do
    Unfortunately my tool wouldn't work on a 9 Pro as it's made for the 9 and the T-Mobile 9 Pro is so finicky that I never even bothered trying to make a mod for it after all the headaches I had trying to make one for the regular 9 T-Mobile model. People need to just start shipping those POS devices back.
  • 15
    *** Use this at your very own risk.
    *** You will lose all data
    *** Backup your working modemst1/2 and persist. If you lose these for any reason, it's unique to your device and not recoverable if you didn't back up (via MSM or other people).
    *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took. If you just ran a bunch of unknown commands, I would tell you to MSM.
    *** Know how to use the MSMTool, Don't start before figuring it out. https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-glo-in.4272549/
    *** DO NOT ATTEMPT THIS IF YOU ARE NOT FAMILIAR WITH ANY STEP DESCRIBED IN THIS GUIDE


    General notes:
    • NR and LTE bands are read only and not modifiable, not in modem.img or any other partition. You cannot get global bands by flashing a global ROM, nor can you lose TMO bands by flashing another ROM.
    • If you wish to unlock the bootloader without unlock_code.bin, you MUST do it from OOS11. If you upgrade to OOS12/OOS13, you will need the unlock_code.
    • The T-Mobile NON-HLOS is no longer necessary as of OOS13 release. If you must stay on OOS11 or OOS12, make a backup of the T-Mobile modem partition for the OOS version you want to stay on.
    • Dual-SIM does not work.

    Prerequisites:
    • This conversion will not SIM unlock you. You can only SIM unlock on a T-Mobile ROM, meaning if you want to do that in the future, you must go back to a TMO ROM (and wipe)
    • Familiarity with MSMDownload tools. If the regular MSM tool doesn't work for you, turn back now.
    • Back up all data, it will be wiped.

    Download:

    Steps:
    1. Run the MSM file normally.
    2. Unlock your bootloader if necessary. Now is the time if you don't have unlock.bin
    3. Patch up to Android 13 while on Wifi if your mobile data doesn't work. Use this time to go to another variant (GLO, IN, etc) as needed.

    Fastboot method:
    * The steps in this guide will convert your TMO LE2127 to EU 11.2.3.3. This is intentionally not the latest version to force you to take a FULL OTA.
    * You must already have the bootloader unlocked with an unlock_code.bin
    * You can use this guide to convert to your own variant by extracting payload and flashing from a full OTA. No support will be given if you choose to manually do it.
    * Use the latest platform tools: https://developer.android.com/studio/releases/platform-tools. DO NOT USE MINIMAL ADB, it has not been updated for years.
    * Fastboot can't see your device? https://forum.xda-developers.com/t/...stboot-mode-windows-10.4194491/#post-84943553
    * Test that you can boot to fastbootd prior to starting, "fastboot reboot fastboot" and you should see the OnePlus logo with the text "fastbootd" on top. Do not continue if this doesn't work.
    * When encountering issues, describe all steps you took, paste any outputs, and take screenshots. Make sure to include the output of fastboot --version in your post.

    Steps to convert your device to EU
    1. You need your device bootloader and SIM unlocked. See https://forum.xda-developers.com/t/how-to-unlock-the-t-mobile-bootloader.4256319/
    2. Download and unzip the conversion package:
      • EU 11.2.3.3
        MD5: cb949816fa80d5f0d984359b819426c3
    3. Boot to bootloader.
      • From adb:
        Code:
        adb reboot bootloader
      • From fastboot/bootloader:
        Code:
        fastboot reboot bootloader
    4. Execute "flash_all.bat" from the unzipped directory from step 2.
    5. Reboot into recovery, and wipe everything.
    6. Once fully booted, connect to WiFi and download Oxygen Updater and take the FULL OTA (11.2.4.4 as of this writing)
    7. Do a regular reboot, don't reboot to fastbootd, bootloader, recovery, etc. Reboot to system.
    8. Reboot into bootloader or fastbootd, and flash the T-Mobile modem.
      Code:
      fastboot flash modem NON-HLOS.bin
    9. After each Full OTA you take in the future, you will need to repeat step 7 & 8

    FAQ
    • Q: The most recent version is 11.2.4.4, why is this guide converting to 11.2.3.3?
      A: You didn't read the full post.
    • Q: Why is there no conversion to Global?
      A: Global variant uses the Google incremental OTA server, and full OTAs are not always provided. There's no functional difference, and EU has better privacy requirements anyways. You can do it manually by extracting payload.bin and running the same flash script. No support will be provided if you choose to flash to Global.
    • Q: Can I re-lock the bootloader after conversion?
      A: While you can go ahead lock your bootloader after conversion, I don't recommend it as you will not be able to take incremental OTA due to modem changes, and lose connectivity if you take a full OTA. To fix it, you need to unlock the bootloader and end up wiping.
    • Q: Where is the Linux guide?
      A: Too lazy, if you're using Linux, you can make your own bash script from the Windows batch script.
    • Q: Help, I see is 'fastboot' is not recognized as an internal or external command.
      A: Your fastboot.exe is not in your $PATH. You can either drop fastboot into the same folder as flash-all.bat, or you can fix your $PATH
    • Q: Help, I cannot boot to fastbootd because previous flashes messed things up.
      A: MSM
    • Q: Help, "not enough space to resize [system, product, system_ext]"
      A: MSM. If the error is on Vendor, it might still work and boot with a generic Android boot logo. If so, take the full OTA as described in the guide.
    • Q: Help, something went wrong!
      A: Post in here the starting state of your device (Device model, ROM version, etc), all steps you've taken since unlocking bootloader, and the output of whatever is causing you trouble. Chances are, the answer is MSM, but read my MSM warning.
    • Q: Help, I see "Invalid sparse file format at header magic"
      A: Ignore this message, not an error


    Fixing the About Phone page

    These steps are optional, and is only applicable for OOS11. It will fix the "About Phone" page. There are no performance differences. All that's done is change build.prop to reflect the correct model.
    1. You need to rooted with Magisk
    2. Download and install the magisk module: here
    3. Reboot, the About Phone page is filled out.


    Instructions to Bootloader Unlock a SIM locked device:

    1. In ADB:
      Code:
      adb shell pm uninstall -k --user 0 com.qualcomm.qti.uim
    2. Reboot
    3. Go to dev settings and enable OEM Unlock
    4. Reboot to bootloader
    5. Code:
      fastboot oem unlock
      No unlock.bin needed


    Issues so far (please post if you run into more):
    • If your mobile data doesn't work on OOS13, PM me details including HW Revision in About Phone.
    What appears to work:
    • Everything else.

    Much appreciation for everyone that help develop and test
    @razercortex
    @retryfail
    @amaroney55
    5
    Due to OnePlus's incompetence on running a website, the MSM conversion is released today to enable bootloader unlocking for folks who are SIM unlocked but can't download an unlock.bin
    3
    Link to the tg group I'm willing to help or find a fix for this also my Bluetooth will randomly disconnect then reconnect my Garmin watch. I did notice it disconnected my airpod before once but haven't had that happen yet just happens more often with my Garmin watch.
    If you don't have root or unlocked bootloader backup using MSM tool. When in the screen where you would normally flash the rom, press F8 key. You will see list of partition, password is oneplus to use backup.
    2
    Thank you for all the help it helped me convert my first oneplus device Im glad I did it.
    2
    You can dump partitions without root using edl.py https://github.com/bkerler/edl/

    This is entirely on your own, I will not be supporting this tool :)