[GUIDE] Complete Step-by-Step Convert T-Mobile to Global (or other) firmware

[mrokerya]

For T-Mobile the unlock.ops file link is given below:

unlock.ops

drive.google.com

Thank you very much, it was much needed. I have successfully converted my OP8 Tmo to dual sim global.

 

[thattechguy_69]

For T-Mobile the unlock.ops file link is given below:

unlock.ops

drive.google.com

thank you for providing backup, will upload it physically into this thread!

 

[wahaj786]

thank you for providing backup, will upload it physically into this thread!

HI I need your help. Been a week trying to convert.
So here is my issue. I'm on tmobile
-> I MSMED TO the os you gave like 10. something.
->Ticked the OEM unlocking.
->Rebooted into edl.
->Did the same as uh mentioned. Like rename and replace the unlock.ops with msm-folder/name.ops
->Instead of getting boot is corrupted. My device automatically booted into BL.
->Executed fastboot flashing unlock, but i got. Cannot unlock THW.
->I've token but whenever I unlock with token, I get IN2017 instead of IN2015.
->Dual sim doesn't work.
->If you please show me or tell me how can I fix it.
Main thing is unlock.ops didn't worked for me. Have tried everything.

 

[iMogul]

Thank you very much, it was much needed. I have successfully converted my OP8 Tmo to dual sim global.

What version of Global did you use?

 

[thattechguy_69]

HI I need your help. Been a week trying to convert.
So here is my issue. I'm on tmobile
-> I MSMED TO the os you gave like 10. something.
->Ticked the OEM unlocking.
->Rebooted into edl.
->Did the same as uh mentioned. Like rename and replace the unlock.ops with msm-folder/name.ops
->Instead of getting boot is corrupted. My device automatically booted into BL.
->Executed fastboot flashing unlock, but i got. Cannot unlock THW.
->I've token but whenever I unlock with token, I get IN2017 instead of IN2015.
->Dual sim doesn't work.
->If you please show me or tell me how can I fix it.
Main thing is unlock.ops didn't worked for me. Have tried everything.

Try it again but with this ops. See if it works, I have heard people with the same issue as you have. Do keep checking on this thread and see if they find a fix. As of now, I cannot tell you what to do and what not as I don't have my OnePlus to test it anymore, and I have never encountered this issue.

Best regards,

For T-Mobile the unlock.ops file link is given below:

unlock.ops

drive.google.com

 

[wahaj786]

Is that the sa

Try it again but with this ops. See if it works, I have heard people with the same issue as you have. Do keep checking on this thread and see if they find a fix. As of now, I cannot tell you what to do and what not as I don't have my OnePlus to test it anymore, and I have never encountered this issue.

Best regards,

Thanks for replaying.
Is that the same .ops? As on 1st page? Or a different one?
I've tried many times but my device still booted in bootloader.

 

[thattechguy_69]

Is that the sa

Thanks for replaying.
Is that the same .ops? As on 1st page? Or a different one?
I've tried many times but my device still booted in bootloader.

Someone made a backup of that ops before the link got removed. That's the one I uploaded so it should be the same

 

[dlhxr]

HI I need your help. Been a week trying to convert.
So here is my issue. I'm on tmobile
-> I MSMED TO the os you gave like 10. something.
->Ticked the OEM unlocking.
->Rebooted into edl.
->Did the same as uh mentioned. Like rename and replace the unlock.ops with msm-folder/name.ops
->Instead of getting boot is corrupted. My device automatically booted into BL.
->Executed fastboot flashing unlock, but i got. Cannot unlock THW.
->I've token but whenever I unlock with token, I get IN2017 instead of IN2015.
->Dual sim doesn't work.
->If you please show me or tell me how can I fix it.
Main thing is unlock.ops didn't worked for me. Have tried everything.

I have seen a device behave like this before. If you have the unlock token, before you run msmdownload tool with unlock.ops, just use your unlcok token to unlock device first and then everything will work.

For your current situation, you need to msmdownload back to original oneplus t mobile rom and then start everything over

 

[wahaj786]

I have seen a device behave like this before. If you have the unlock token, before you run msmdownload tool with unlock.ops, just use your unlcok token to unlock device first and then everything will work.

For your current situation, you need to msmdownload back to original oneplus t mobile rom and then start everything over

Nope it will not work.

 

[Zombify01]

I am using IN2019 (OP8 verizon). Currently on AICP (Android 12). Is there any process to convert to Global rom?

 

[thattechguy_69]

I am using IN2019 (OP8 verizon). Currently on AICP (Android 12). Is there any process to convert to Global rom?

the process on unlocking bootloader for verizon model is very similar to this guide but I doubt the dual sim would work so No.

 

[Zombify01]

the process on unlocking bootloader for verizon model is very similar to this guide but I doubt the dual sim would work so No.

IN2019 is single sim.

 

[ahmedali381]

Hi. I have Oneplus 8 T-Mobile already converted. Firmware is IN2015_11_F.13 OxygenOS 13, although in theme store it shows that your mobile has indian firmware because the price is in Indian Rupee. Dual sim seems to be working because both imei is shown, i haven't confirmed because I don't have dual sim tray. i want to install Coloros 13 on my oneplus 8. i downloaded the latest Coloros 13 for oneplus 8 and tried to install from local upgrade but it shows Verification failed. how can I install Coloros 13 safely? without loosing signal or dual sim functionality?..

 

[WhisperPntr]

I believe I bricked my OP8 by flashing the wrong .op file. Sigh, shouldn't have worked on this late at night.

Now it continually loops into Crashdump mode and I cannot enter fastboot, recovery or ADB.

All my computers only have usb 3.0 ports. Is it possible that using 2.0 will save it or am I S-O-L?

 

[thattechguy_69]

I believe I bricked my OP8 by flashing the wrong .op file. Sigh, shouldn't have worked on this late at night.

Now it continually loops into Crashdump mode and I cannot enter fastboot, recovery or ADB.

All my computers only have usb 3.0 ports. Is it possible that using 2.0 will save it or am I S-O-L?

if it continues to loop into crashdump mode then ur phone is still possible to be unbricked. And I believe its USB 2.0. Force Shutdown phone. Boot it to EDL Mode using power button and volume keys and plug it in to PC and start MSM tool.

 

[MohmmadUzairKhan]

Hi. I have Oneplus 8 T-Mobile already converted. Firmware is IN2015_11_F.13 OxygenOS 13, although in theme store it shows that your mobile has indian firmware because the price is in Indian Rupee. Dual sim seems to be working because both imei is shown, i haven't confirmed because I don't have dual sim tray. i want to install Coloros 13 on my oneplus 8. i downloaded the latest Coloros 13 for oneplus 8 and tried to install from local upgrade but it shows Verification failed. how can I install Coloros 13 safely? without loosing signal or dual sim functionality?..

Roll back to Oxygen OS 11 then Flash Color os 13.


and after that do let me know dual sim work on color os 13 oneplus 8 Tmobile

 

[WhisperPntr]

Oh my friggen god, so super duper incredibly happy! Thanks to OP and people on here I now not only have EVO X 7.5 with dual sim on my TMO OP8 but I unbricked what I thought was a hard bricked OP8.

For anyone who had the absolute misfortune of a crashdump due to misflashing the wrong .ops file, there's hope. I had that, the DIAG 900E only driver, alongside zero fastboot and recovery. It seemed hopeless, but being desperate and in lieu of the advice above and from other sites I kept trying and finally the following revived my phone:

1) I had to use a usb 2.0 port. It can be inbuilt or it can be from a hub but you really need usb 2.0.
2) I had to use a different cable than the one from oneplus. I ended up using the one used to charge my wireless headphones.
3) You should try windows 10 and above. Others may have had luck with windows 7 and native usb 2.0 but not in my case.

I had both the msm download and device manager open and ready. I kept the usb port in the system, then while holding down both volume buttons and power, quickly connected the usb C end into the phone. You can try without the power button but regardless you need to see 9008 pop up under ports in device manager. If the phone under device manager still remains as 900E then you have to start the process over again until it shows EDL (9008). If it shows bulk you need to reinstall your drivers.
On MSM immediately ENUM and Start.

If the above doesn't work, look for resources as if it showed issues only after msm there's still a good chance you can save it.

 

[NorlanBustilloX]

EDIT so you can ignore the rest: Somehow I manage to continue with the process, but I´m stuck on the Fastloader section. I´m on the screen with the big START button, but when I run the adb commnad (fastloader devices), no response.

I made sure to turn on OEM Unlocking before preceding, and now the "FAILED (remote: 'Flashing Unlock is not allowed (THW.)')
fastboot: error: Command failed" message appears. Also, "adb devices" doesn´t show anything, yet "fastboot devices" show one device.




Original Message: Hi! I stumbled upon this amazing post but I´m having issues, so I was wondering if anybody could help.

Little backstory of why I´m here: So, I bought my phone two years ago, IN2015 and was working fine until two weeks ago when the screen turned green and had it replaced. The new screen´s fingerprint wasn´t working, so I contacted the technician and said I had to factory reset the phone, so the new finger print could be recognized. Not sure of how true is that, but I went on ahead and did that. Last night he gave me the phone back, but as soon as I started checking it, I noticed it was now IN2017 (I´m not too faithful with whatever he did to my "phone", if it is still mine). When I tried to restore my phone´s backup, the system gave me the warning that the backup was made using a newer software than my current one (made with 13 and now I have 12). So, that´s basically the reason of my visit here. I want to restore my phone to Global (for better updates) and restore my settings.

Now the issues. So, since starting the post, some stuff are expected to be known by users (and yes, I get it, *this is not a common-guy-like-me sruff*). For example, turning on Test Mode, disabling device driver signing and that, was something I had to Google and modify several aspects of my PC to get it to work (if it is even working, as I read that in Test Mode, there is a huge watermark and I´m not seeing it).

Then, when starting the MSM Tool, no devices show up. I´ve selected Other, my phone is connected and has USB Debugging enabled, yet, nothing shows up.

I´m still at step 1 and already having lots of issues Is there a video tutorial using *this* guide I could refer to? Seemed straight enough, but guess I´m having a really hard time (also the stress factor of losing my stuff and/or bricking the phone).

Sorry, but if anyone could assist, I´d be thankful.

 

[naeem044]

C:\Program Files\Minimal ADB and Fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed (THW.))
finished. total time: 0.016s

 

[NorlanBustilloX]

Should I lose hope and stop trying?