[Guide] Oneplus 7T T-Mobile to International Firmware Conversion Explained

Search This thread

thetoady

Senior Member
Mar 7, 2008
148
4
you're right! switched my primary calling and data sim to t-mobile sim and it worked from overseas in airplane mode and shows the icon on top. of VoWifi. thanks that's very helpful. just had a decently long chat with my parents to test it out. manually switching it when I have to call the US isn't such a big deal.

though when I just tried to reproduce it, it didn't work. so it seems temperamental.
 

Chxc

Senior Member
Nov 7, 2015
53
4
you're right! switched my primary calling and data sim to t-mobile sim and it worked from overseas in airplane mode and shows the icon on top. of VoWifi. thanks that's very helpful. just had a decently long chat with my parents to test it out. manually switching it when I have to call the US isn't such a big deal.

I'm glad you got it figured out.

As with manual switching, may I suggest to take a look with the App on play: Tasker. It might have the necessary privilege without system being rooted to automate your switching task. It's a paid app with a trial period, but I personally recommended it, strongly.
 

the_link_8

Member
Mar 28, 2019
19
2
You have to use a compatible fastboot.exe binary, I personally used the OnePlus suggested.

If your device doesn't detect the device, please check with your drivers to remedy your situation.
thanks i already did the whole process and now my phone is running the international version.
 
  • Like
Reactions: Chxc

thetoady

Senior Member
Mar 7, 2008
148
4
I'm glad you got it figured out.

As with manual switching, may I suggest to take a look with the App on play: Tasker. It might have the necessary privilege without system being rooted to automate your switching task. It's a paid app with a trial period, but I personally recommended it, strongly.

sort of. It works, but is unreliable to connect via vowifi. I have tasker (and have taser setup to enable call recording on each reboot, no root or bootloader unlocking neccessary)
 

Chxc

Senior Member
Nov 7, 2015
53
4
sort of. It works, but is unreliable to connect via vowifi. I have tasker (and have taser setup to enable call recording on each reboot, no root or bootloader unlocking neccessary)

It's my personal opinion this unreliability might has something to do with the rather opaque nature of VoWifi hand shake process. Thus, making it harder to anticipate edge cases in tasker.
 

thetoady

Senior Member
Mar 7, 2008
148
4
I'm not talkin tasker, I'm talking just doing it by hand in the settins menu, its unreliable to setup, and no idea why its happening. need logs
 

dimelus

Member
Feb 25, 2012
12
0
Can someone help me I already tried this multiple times.

I'm on step 8, after I run flash-all.bat (CMD with admin rights) after some steps my phone just boot T-Mobile rom.

If i try to go into recovery(power and vol+) there is a msg saying that the boot loader is unlocked and software integrity cannot be guaranteed and it just boot again in t-mobile rom.


What should I do?

I got this phone from B&H Photo Video as an T-Mobile Unlocked device.
 

Chxc

Senior Member
Nov 7, 2015
53
4
Can someone help me I already tried this multiple times.

I'm on step 8, after I run flash-all.bat (CMD with admin rights) after some steps my phone just boot T-Mobile rom.

If i try to go into recovery(power and vol+) there is a msg saying that the boot loader is unlocked and software integrity cannot be guaranteed and it just boot again in t-mobile rom.


What should I do?

I got this phone from B&H Photo Video as an T-Mobile Unlocked device.

CMD DOS environment =/= PowerShell

I have never got this last flash to work on anything other than admin priv PowerShell, neither should you.
 

dimelus

Member
Feb 25, 2012
12
0
CMD DOS environment =/= PowerShell

I have never got this last flash to work on anything other than admin priv PowerShell, neither should you.

Just tried with power shell

AfterRebooting into fastboot my phone just go directly to T-mobile stock rom... What should i do now?

If i turn it off and and do power and vol +it just start on t-mobile again...the phone don't go into recovery and my powershell is stuck on WAITING FOR ANY DEVICE.


EDIT:

I managed to get into recovery(power and vol down, and went into advanced options and boot into recovery.

Now Power shell continue to do those things but there are tons of errors. (Screenshoot 6).

After it finished it just bot again on t-mobile
 

Attachments

  • Screenshot_5.png
    Screenshot_5.png
    41 KB · Views: 12
  • Screenshot_6.png
    Screenshot_6.png
    64.4 KB · Views: 10

Chxc

Senior Member
Nov 7, 2015
53
4
Just tried with power shell

AfterRebooting into fastboot my phone just go directly to T-mobile stock rom... What should i do now?

If i turn it off and and do power and vol +it just start on t-mobile again...the phone don't go into recovery and my powershell is stuck on WAITING FOR ANY DEVICE.

Are you surr you are using the latest fastboot binary?

This is the classic behavior of not starting the final flashing process using the latest fastboot.exe.

Please consider read more into the details of this guide. This stuff is all there.
 

dimelus

Member
Feb 25, 2012
12
0
Are you surr you are using the latest fastboot binary?

This is the classic behavior of not starting the final flashing process using the latest fastboot.exe.

Please consider read more into the details of this guide. This stuff is all there.

I'm actually new to all of this...

I download all the files from this topic, used power shell and did the manual commands copying and pasting from step 7.
 

thetoady

Senior Member
Mar 7, 2008
148
4
Unreliable in what sense? My curiosity runs amuck, hah.

not enabling reliably or staying connected (which makes me scared to even have it on overseas if I mistakenly call or accept a call without realizing it). If I jump between prefer mobile or prefer wifi, sometimes it enables when it didn't enable before.
 

Chxc

Senior Member
Nov 7, 2015
53
4
nope.


I'm trying to download everything again in a different pc...

Yesterday I tried all different guides on this...more than 10 hours trying haha

Just keep trying. The final fastboot.exe flash is a bit tricky. Took quite a bit hair pulling for me to get lucky.

Make sure, you are not suppose to enter the final flash command one by one, they should be queued with a single copy of paste on powershell or batch invocation.

During the final flashing process, you are NOT suppose to see fastboot screen on your device nor you need to touch it until it's all done and boot into the global firmware, during the middle reboot, 7T should display stock recovery screen (even though it's responding to fastboot commands, don't ask don't know)

Again, you are very close. Keep trying and gl.
 

Chxc

Senior Member
Nov 7, 2015
53
4
not enabling reliably or staying connected (which makes me scared to even have it on overseas if I mistakenly call or accept a call without realizing it). If I jump between prefer mobile or prefer wifi, sometimes it enables when it didn't enable before.

I definite see your reservation, it's definitely a lot more trickier when hefty carrier bills are involved.

If VoWiFi is perferred, then you should always prefer wifi as roaming mobile is always throttled to 128kbps on T-Mobile at least, not to mention real world roamed network's own congestion.

Additionally, you might be use the notification icons of the ugly VoWifi as some sort of indicator of success, but don't take my word for it. Give it a try yourself.
 

thetoady

Senior Member
Mar 7, 2008
148
4
yes, I base it on seeing the icon. And I have 256kbps (one plus plan), but in general my idea would be to use something like tasker to switch the sims around if I'm on wifi or not. so when I go out of wifi, it switches to local sim, when I'm back in wifi, it switches to t-mobile sim for vowifi.

with all that said, the design decision to require vowifi to only work on primary data sim seems to be a terrible design decision IMHO. I really wonder why it's required. especially when on wifi and the data sim isn't actualy going to be actively used.
 

Chxc

Senior Member
Nov 7, 2015
53
4
yes, I base it on seeing the icon. And I have 256kbps (one plus plan), but in general my idea would be to use something like tasker to switch the sims around if I'm on wifi or not. so when I go out of wifi, it switches to local sim, when I'm back in wifi, it switches to t-mobile sim for vowifi.

with all that said, the design decision to require vowifi to only work on primary data sim seems to be a terrible design decision IMHO. I really wonder why it's required. especially when on wifi and the data sim isn't actualy going to be actively used.

Could be a just a practical and security vulnerabilities perversion concern to making dropping and switching between unsafe, unreliable alternative Wi-Fi data paths possible by locking your primary data connection as fail safe.

Also, in your opinion, does the plus worth the extra $10 a month for doubling from 128 to 256 mbps for roaming?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    The benefits of firmware conversion:
    1. Completely remove T-Mobile app and any underlying software (there aren't a lot, but why not competently gone)
    2. Use dual sim supported by the hardware. You'll need to get a new dual sim tray. Just remember to unlock network lock so you can use other carriers, which is a different but simpler process.
    3. Get on the faster firmware release schedule of stock firmware because it doesn't need to be certified by T-Mobile, which are always generations behinds.
    1
    Preparation:
    1. Notes are important, please pay attention
    2. ONLY use stock USB-A to USB-C cable
      • I have tried the stock cable from Axon 7, fail fail and more fail, don't make this mistake
    3. DON'T store flash files on USB storage.
      • fastboot will timeout if your flash files are stored at a slow storage device such as a USB drive, or slow computer with eMMC drive
    4. Download and extract the patched MSM download tool and related flash files (credit)
    5. Download and extract TWRP 3.4.0-2 Test by mauronofrio (credit)
    6. Download and extract 10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT.zip (credit)
    7. Optional: Unlock bootloader at this official OnePlus page with those steps
      • automated process you have to wait 1 whole week for
      • if you take this route, you will have an easier time get into EDL
    8. Optional for Driver and boot into EDL: Download and extract the TOOL ALL IN ONE (credit) (untested) (can skip this step if you have driver and completed preparation step 7)
    Flash Operations:
    1. Run the MSM executable with Administrator Privilege
    2. Boot into bootloader on 7T (if you already have adb connection, adb reboot bootloader would work as well)
      1. Restart device: Vol Up + Power
      2. Boot into recovery: when system reboot from step 4, immediately press and hold Vol Down + Power until recovery screen
      3. Boot into fastboot: English -> Advanced -> fastboot
    3. Boot into EDL on 7T
      • If you have OnePlus unlock token from Preparation step 7
        1. Connect USB cable to both PC and 7T
        2. on MSMDownloadTool, click Enum to display your device
        3. fastboot flash cust-unlock unlock_token.bin
        4. fastboot oem unlock
        5. fastboot boot twrp.img
        6. when TWRP boot: adb reboot edl
        7. on MSMDownloadTool it will now show connected
      • If you don't want to wait for token (untested)
        • Use TOOL ALL IN ONE
        • Or, hold down the buttons then click start in MSM. If you release the volume buttons early it will kick you out of EDL--well at least for me. you can release the buttons once MSM starts (credit)
    4. When MsmDownloadTool display connected, hit Start until 7T display CORRUPT message (normal behavior) and reboot into fastboot by ITSELF. If your 7T doesn't get into fastboot screen automatically, something is wrong with previous step, redo EDL flashing and do NOT proceed.
    5. Start Power-Shell with Administrator Privilege and go to the extracted path of 10.0.13-global-oneplus7toxygen_14.o.19_ota_019_all_2009281709_1026-fastboot.zip (DO NOT USE DOS, it will fail you miserably)
    6. Unlock bootloader: .\fastboot flashing unlock_critical (suggested, because it works, so I didn't test the oem unlock method)
    7. To avoid potential conflict with installed fastboot binary (possibly lower version), you can either
      • edit the flash-all.bat, and change fastboot to .\fastboot, such that only the local fastboot binary will be invoked instead of pathed binary
      • OR run those identical commands with copy and paste
        Code:
        .\fastboot -w
        .\fastboot flash boot boot.img
        .\fastboot flash dtbo dtbo.img
        .\fastboot flash modem modem.img
        .\fastboot flash reserve reserve.img
        .\fastboot flash recovery recovery.img
        .\fastboot --disable-verity flash vbmeta vbmeta.img
        .\fastboot --disable-verity flash vbmeta_system vbmeta_system.img
        .\fastboot reboot fastboot
        .\fastboot flash abl abl.img
        .\fastboot flash aop aop.img
        .\fastboot flash bluetooth bluetooth.img
        .\fastboot flash cmnlib cmnlib.img
        .\fastboot flash cmnlib64 cmnlib64.img
        .\fastboot flash devcfg devcfg.img
        .\fastboot flash dsp dsp.img
        .\fastboot flash hyp hyp.img
        .\fastboot flash imagefv imagefv.img
        .\fastboot flash keymaster keymaster.img
        .\fastboot flash LOGO LOGO.img
        .\fastboot flash multiimgoem multiimgoem.img
        .\fastboot flash odm odm.img
        .\fastboot flash oem_stanvbk oem_stanvbk.img
        .\fastboot flash opproduct opproduct.img
        .\fastboot flash qupfw qupfw.img
        .\fastboot flash storsec storsec.img
        .\fastboot flash tz tz.img
        .\fastboot flash uefisecapp uefisecapp.img
        .\fastboot flash xbl xbl.img
        .\fastboot flash xbl_config xbl_config.img
        .\fastboot flash system system.img
        .\fastboot flash vendor vendor.img
        .\fastboot flash product product.img
        .\fastboot reboot
      • Few notes
        • User data is wiped, again, lol
        • reserve partition flashing can produce error msg: FAILED (remote: '(reserve_a) No such partition'), it is OK but others should not Fail
        • Device will reboot once during the flashing process
        • After reboot, device will NOT go into fastboot screen but instead go into stock recovery screen, however fastboot will pick up and resume flashing the rest, ONLY IF YOU ARE UNDER POWER-SHELL, so DO NOT flash under DOS
        • if anything else fails besides the reserve partition, repeat step 7
    8. Device will boot into system, you may use the OS updater to upgrade to the lastest firmware then relock bootloader or proceed with root with Magisk

    Hope this will save you some precious time. Major kudos for previous contributions from post 1 and post 2.

    All steps are recorded from memory, please let me know if any mistakes are in need of correction.

    Tested working on Dec 5, 2020
    1
    hi, i went to the link where you can request for the token for unlocking the bootloader and it is asking me for the unlock code and i do not know what that is, i think that it is asking for the sim unlock code but i bought this phone in ebay and it came already unlocked so i do not know what to do, so if someone could help me out with this i will appreciate that.
    Follow the Oneplus instructions, there isn't anything better that explains the process.

    Please understand the difference between carrier sim unlock and device bootloader unlock before proceeding.

    The Oneplus link is used for official unlock of bootloader, not carrier sim unlock. Carrier sim unlock happens inside the OS.
    1
    So I did this process yesterday and since this thread was quite valuable to me I feel like sharing some insights.

    First of all it is really important to fix "the drivers". If you connect your phone in adb, fastboot or EDL mode you have to figure this out first. Wrong drivers usually can be spotted in Device Manger with a Yellow exclemation mark. Yes - ADB/fastboot and EDL are different drivers.

    If you have problems connecting in ADB/fastboot mode download drivers here https://developer.android.com/studio/run/win-usb and install them like this https://developer.android.com/studio/run/oem-usb#InstallingDriver

    If you have problems with EDL follow this link: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4004005/ read "My device isn't detected when I click on "Enum" button"

    I usually do not just "install drivers from exe". I go to the device manager, look for uninstalled devices and right-click update drivers so this specific device gets this specific driver. This may be an overkill in 2020/Windows 10 but why change a running system..

    You can test those drivers quite easy.
    1. First download & unzip the android plattform tools (https://developer.android.com/studio/releases/platform-tools).
    2. Enable USB Debugging in Dev-Options on Android
    3. Point CLI to your folder where you unzipped said toolset
    4. Type adb devices in CLI - if it shows a device your ADB drivers work.
    5. Then reboot your device to "fastboot" you can do this with button mashing or since ADB works just type adb reboot bootloader
    6. Wait for reboot, then type fastboot devices if it shows a device your fastboot drivers work.
    7. Boot back to Android again (click power when it sais "start")
    8. Go back to step 3 and type adb reboot edl (again you could boot into EDL with som button mashing but why do it the hard way)
    9. To test EDL you have to use the MSM Toolset (patched or not doesn't matter) - if it says connected this means your EDL drivers work too

    It is crucial to test this bevore thinking about flashing for obvious reasons. And you learned to boot into all the modes via CLI which is nice.

    With this out of the way I would like to add some thoughts to the inital post:

    1. When flashing the device (Step 7 in initial post) my device booted into T-Mobile start screen for some reason instead of booting into fastboot and continuing pushing images. This was not the case if I booted into Recovery Mode (fastboot -> choose recovery mode with volume keys -> enter PIN -> choose English -> something something fastboot) and Chose "Fastboot" manually. After this the flashing worked flawlessly
    2. I "patched" the tooling (fastboot.exe, adb.exe) from the link in inital post with the latest files from google sdk, this did not work. Use the tools inside "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT"
    3. For easy of use I created my own flash_all.bat with the local reference to fastboot.exe (see attached) as explained in intial post. This goes inside "10.0.13-GLOBAL-OnePlus7TOxygen_14.O.19_OTA_019_all_2009281709_1026-FASTBOOT"
    4. Since I was impatient I used the method with the patched MSM Tool to unlock the bootloader - I can confirm this works. After relocking the bootloader picky apps like Netflix work too.
    5. I did skip step 3.5 "fastboot boot twrp.img" since I didn't understand what it does - it works without this

    Hope this helps.

    Thanks for the guide chxc
    1
    1. When flashing the device (Step 7 in initial post) my device booted into T-Mobile start screen for some reason instead of booting into fastboot and continuing pushing images. This was not the case if I booted into Recovery Mode (fastboot -> choose recovery mode with volume keys -> enter PIN -> choose English -> something something fastboot) and Chose "Fastboot" manually. After this the flashing worked flawlessly

    When did you do this? Immediately after running the MSM patched toolset?

    Actually nevermind, I understood what you meant. During the flash you didn't let the mobile show the T-Mobile screen and went into recovery directly.
    The flashing continued for me, but gave several errors at the end:

    ending sparse 'system_a' 1/5 (523136 KB) FAILED (Write to device failed (Invalid argument))
    fastboot: error: Command failed
    Invalid sparse file format at header magic
    Sending sparse 'vendor' 1/2 (785569 KB) OKAY [ 18.609s]
    Writing 'vendor' FAILED (remote: 'Partition not found')
    fastboot: error: Command failed
    Invalid sparse file format at header magic
    Sending sparse 'product' 1/2 (785436 KB) OKAY [ 19.774s]
    Writing 'product' FAILED (remote: 'Partition not found')
    fastboot: error: Command failed
    Rebooting OKAY [ 0.000s]

    It occasionally gives remote: 'Flashing is not allowed for Critical Partitions' if I retry.


    EDIT: changed USB port and it worked. Gotta find a way to lock the bootlocker now.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone