• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

T-Mobile 7T Conversion to International WITHOUT unlocked bootloader/SIM unlock!

Search This thread

[email protected]

Senior Member
Aug 27, 2010
1,774
1,292
44
Brooklyn, NY
superstarmobility.weebly.com
Please check these and tell what value it shows

cat /sys/class/power_supply/bms/charge_full_design

cat /sys/class/power_supply/bms/capacity

cat /sys/class/power_supply/bms/capacity_raw


I want to see if the battery value is 3588....if it is then I think there's is something causing this to show this value instead of 3800.
 

Hussain_97

Senior Member
Feb 3, 2017
248
42
hey bro , i am currently on Android 11 oxygen os 11.0.1.4 ,
so after unlocking bootloader through msm ,
Should i have to flash android 10 os 10.0.4 that bytimes mention above in post ? and then flash Os 10v16 that you mentioned ?
basically 10.0.4 is flashed throgh msm for unbricking , because i assume changing from 11 to 10 would required msm tool to force firmware change
 

HueyT

Senior Member
Apr 3, 2014
4,184
1,956
New Albany, IN
OnePlus 7T
hey bro , i am currently on Android 11 oxygen os 11.0.1.4 ,
so after unlocking bootloader through msm ,
Should i have to flash android 10 os 10.0.4 that bytimes mention above in post ? and then flash Os 10v16 that you mentioned ?
basically 10.0.4 is flashed throgh msm for unbricking , because i assume changing from 11 to 10 would required msm tool to force firmware change
Not unless you truly want oos10 v16. If you go on to oos11 then you don't need oos10 v16. You can jump from oos10 v4 straight to oos11
 
  • Like
Reactions: Hussain_97

Hussain_97

Senior Member
Feb 3, 2017
248
42
After bootloader unlock using msmtool, then install oos10 via fastboot
yes bro now i flashed os 10 thats is given in this instructions , and during flashing through fastboot , the mobile restarts into recovery and then i reboot to start the phone ,
it shows T Mobile Logo and HD1907 shows in setting, after setting up ,again goes to fastboot mode and flashed the same Os 10 through flash-all.bat file but still its firmware HD1907 and android version is 10 .
what should i do now to get a global working rom ?
 

Hussain_97

Senior Member
Feb 3, 2017
248
42
now i flashed latest os 10 that you gave in above comments to user bytimes ,
i used payload dumper to get image files then i flashed but still its firmware HD-1907 ,
And i see error during flashing system.img "Failed [remote partion not founs] "

and maybe thats the reason its firmware not Changing and also i tried using msm to force firmware change by setting target to O2 but i got error at the start "device image not match"
 

HueyT

Senior Member
Apr 3, 2014
4,184
1,956
New Albany, IN
OnePlus 7T
When u see the pink TMobile splash screen, use the buttons to go back to bootloader screen, then type "fastboot reboot fastboot" to enter fastbootD. Reflash oos10 and should work now as when not in fastbootD, flashing system and other important partitions don't take
 

Hussain_97

Senior Member
Feb 3, 2017
248
42
When u see the pink TMobile splash screen, use the buttons to go back to bootloader screen, then type "fastboot reboot fastboot" to enter fastbootD. Reflash oos10 and should work now as when not in fastbootD, flashing system and other important partitions don't take
yes it worked , the problem was with the adb drivers , i installed manually and it easily installed :) Thanks buddy for your help ☺️
 
Last edited:

TheCashews

Member
Dec 2, 2013
31
16
I just wanted to comment that I spent several hours not being able diagnose why my device wasn't being detected in fastbootd - it's because I didn't have the necessary drivers. I was able to use the all-in-one tool to "Install Drivers" and it solved the issue for me. I wasn't able to flash the rom successfully before that. Hopefully this saves someone else the headache.
 

lorismarcos

Senior Member
Sep 24, 2007
178
25
Hello all,

First of all just wanted to say a very big thank you to all in this thread.

With your help i managed to convert my t-mobile rom into an EU.

All your comments, especially about drivers and stuff, really helped because i was lacking the qualcomm drivers, so the msm tool would not recognize my phone on edl mode.

Also it's very nice to read through a whole thread that ppl are not complaining or being mean to each other. Very wholesome thread indeed. I'm impressed with you all :)
----------------------------------------------------------------Question
Now my question is this: I noticed ppl managing to re-lock bootloader by flashing international rom ->doing an OTA update-> factory reset-> fastboot lock bootloader command.

Will this by any chance work with the europa fastboot rom?
Can anyone comfirm?
Thanks in advance
 

HueyT

Senior Member
Apr 3, 2014
4,184
1,956
New Albany, IN
OnePlus 7T
Hello all,

First of all just wanted to say a very big thank you to all in this thread.

With your help i managed to convert my t-mobile rom into an EU.

All your comments, especially about drivers and stuff, really helped because i was lacking the qualcomm drivers, so the msm tool would not recognize my phone on edl mode.

Also it's very nice to read through a whole thread that ppl are not complaining or being mean to each other. Very wholesome thread indeed. I'm impressed with you all :)
----------------------------------------------------------------Question
Now my question is this: I noticed ppl managing to re-lock bootloader by flashing international rom ->doing an OTA update-> factory reset-> fastboot lock bootloader command.

Will this by any chance work with the europa fastboot rom?
Can anyone comfirm?
Thanks in advance
Yes, even india
 
  • Like
Reactions: lorismarcos

AlbertoxHP

New member
Sep 20, 2021
2
0
Hola estoy en bootloop luego de seguir este proceso con mi rom t-mobile a internacional, esto es lo que me aparece al instalar por fasboot:


Borrando "datos de usuario" OKAY [0.126s]

Herramientas F2FS: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Información: deshabilitar la política basada en montón
Información: nivel de depuración = 1
Información: Trim está deshabilitado
Información: Establecer conf para Android
Información: segmentos por sección = 1
Información: Secciones por zona = 1
Información: tamaño del sector = 512
Información: sectores totales = 203820072 (99521 MB)
Información: zona alineada segmento 0 blkaddr: 512
Información: agregar tipo de cuota = 0 => 4
Información: agregar tipo de cuota = 1 => 5
[f2fs_init_sit_area: 634] Relleno del área de asiento en el desplazamiento 0x00600000
[f2fs_init_nat_area: 668] Relleno del área nat en el desplazamiento 0x00e00000
[f2fs_write_root_inode: 1281] Escribiendo el inodo raíz (nodo activo), 1b800 0200 en el desplazamiento 0x00112640
[f2fs_write_default_quota: 1357] Escritura de datos de cuota, en el desplazamiento 0001be01, 0001be02
[f2fs_write_qf_inode: 1448] Indo de cuota de escritura (nodo activo), 1b800 0200 en el desplazamiento 0x00112641
[f2fs_write_default_quota: 1357] Escritura de datos de cuota, en el desplazamiento 0001be03, 0001be04
[f2fs_write_qf_inode: 1448] Indo de cuota de escritura (nodo activo), 1b800 0200 en el desplazamiento 0x00112642
[f2fs_update_nat_root: 1502] Escribiendo la raíz nat, en el desplazamiento 0x00000e00
[f2fs_add_default_dentry_root: 1699] Escribiendo raíz dentry predeterminada, en el desplazamiento 0x0001be00
Información: Relación de sobreaprovisionamiento = 0,640%
Información: segmentos de sobreaprovisionamiento = 635 (GC reservado = 320)
[f2fs_write_check_point_pack: 827] Escribiendo segmentos principales, cp en offset 0x00000200
[f2fs_write_check_point_pack: 982] Resumen de segmento de escritura para HOT / WARM / COLD_DATA, en el desplazamiento 0x00000201
[f2fs_write_check_point_pack: 1009] Resumen de segmento de escritura para HOT_NODE, en el desplazamiento 0x00000202
[f2fs_write_check_point_pack: 1021] Resumen de segmento de escritura para WARM_NODE, en el desplazamiento 0x00000203
[f2fs_write_check_point_pack: 1032] Resumen del segmento de escritura para COLD_NODE, en el desplazamiento 0x00000204
[f2fs_write_check_point_pack: 1040] Escribiendo cp page2, en offset 0x00000205
[f2fs_write_check_point_pack: 1060] Escribiendo páginas de bits NAT, en el desplazamiento 0x000003fe
[f2fs_write_check_point_pack: 1081] Escribiendo cp página 1 del paquete de punto de control 2, en el desplazamiento 0x00000400
[f2fs_write_check_point_pack: 1100] Escribiendo cp página 2 del paquete de punto de control 2, en el desplazamiento 0x00000405
[f2fs_write_super_block: 1133] Superbloque de escritura, en el desplazamiento 0x00000000
Información: formato exitoso
Enviando 'datos de usuario' (85 KB) OKAY [0.015s]
Escribiendo "datos de usuario" OKAY [0.003s]
Borrando 'metadatos' OKAY [0.007s]
Borrado exitoso, pero no formateado automáticamente.
El tipo de sistema de archivos sin procesar no es compatible.
Finalizado. Tiempo total: 8.211 s
Enviando 'boot_b' (98304 KB) OKAY [2.150s]
Escribiendo 'boot_b' OKAY [0.518s]
Finalizado. Tiempo total: 3.830 s
Enviando "dtbo" (16384 KB) OKAY [0.452s]
Escribiendo 'dtbo' OKAY [0.095s]
Finalizado. Tiempo total: 0,620 s
Enviando 'modem_b' (165396 KB) OKAY [5.257s]
Escribiendo 'modem_b' OKAY [0.743s]
Finalizado. Tiempo total: 6.053 s
Enviando 'reserva' (250164 KB) OKAY [8.599s]
Escribiendo 'reserva' FAILED (remoto: '(reserve_b) No existe tal partición')
fastboot: error: el comando falló
Enviando 'recuperación' (98304 KB) OKAY [4.893s]
Escribiendo "recuperación" OKAY [0.328s]
Finalizado. Tiempo total: 5.281 s
Reescritura de la estructura vbmeta en el desplazamiento: 0
Enviando 'vbmeta' (8 KB) OKAY [0.012s]
Escribiendo 'vbmeta' OKAY [0.003s]
Finalizado. Tiempo total: 0.089s
Enviando 'vbmeta_system' (4 KB) OKAY [0.008s]
Escribiendo 'vbmeta_system' OKAY [0.004s]
Finalizado. Tiempo total: 0.056 s
Reiniciando en fastboot OKAY [0.003s]
<esperando cualquier dispositivo>
Finalizado. Tiempo total: 16.733 s
Enviando 'abl_b' (1164 KB) OKAY [0.081s]
Escribiendo 'abl_b' OKAY [0.014s]
Finalizado. Tiempo total: 0.212 s
Enviando 'aop_b' (200 KB) OKAY [0.009s]
Escribiendo 'aop_b' OKAY [0.006s]
Finalizado. Tiempo total: 0.094s
Enviando 'bluetooth_b' (828 KB) OKAY [0.048s]
Escribiendo 'bluetooth_b' OKAY [0.018s]
Finalizado. Tiempo total: 0.274 s
Enviando 'cmnlib_b' (384 KB) OKAY [0.010s]
Escribiendo 'cmnlib_b' OKAY [0.008s]
Finalizado. Tiempo total: 0.068s
Enviando 'cmnlib64_b' (500 KB) OKAY [0.015s]
Escribiendo 'cmnlib64_b' OKAY [0.009s]
Finalizado. Tiempo total: 0.092s
Enviando 'devcfg_b' (52 KB) OKAY [0.002s]
Escribiendo 'devcfg_b' OKAY [0.005s]
Finalizado. Tiempo total: 0.076 s
Enviando 'dsp_b' (65536 KB) OKAY [3.279s]
Escribiendo 'dsp_b' OKAY [0.409s]
Finalizado. Tiempo total: 3.728 s
Enviando 'hyp_b' (480 KB) OKAY [0.041s]
Escribiendo 'hyp_b' OKAY [0.010s]
Finalizado. Tiempo total: 0,120 s
Enviando 'imagefv_b' (20 KB) OKAY [0.021s]
Escribiendo 'imagefv_b' OKAY [0.005s]
Finalizado. Tiempo total: 0.074 s
Enviando 'keymaster_b' (248 KB) OKAY [0.177s]
Escribiendo 'keymaster_b' OKAY [0.007s]
Finalizado. Tiempo total: 0.269s
Enviando 'LOGO_b' (6540 KB) OKAY [0.566s]
Escribiendo "LOGO_b" OKAY [0.050s]
Finalizado. Tiempo total: 0,781 s
Enviando 'multiimgoem_b' (16 KB) OKAY [0.020s]
Escribiendo 'multiimgoem_b' OKAY [0.006s]
Finalizado. Tiempo total: 0.074 s
Cambiando el tamaño de "odm_b" OKAY [0.006s]
Enviando 'odm_b' (912 KB) OKAY [0.223s]
Escribiendo 'odm_b' OKAY [0.286s]
Finalizado. Tiempo total: 0.558 s
Enviando 'oem_stanvbk' (2480 KB) OKAY [0.154s]
Escribiendo 'oem_stanvbk' OKAY [0.021s]
Finalizado. Tiempo total: 0.208s
Formato de archivo disperso no válido en header magic
Enviando 'opproduct_b' disperso 1/1 (391796 KB) OKAY [9.016s]
Escribiendo "opproduct_b" OKAY [3.260s]
Finalizado. Tiempo total: 25.777 s
Enviando 'qupfw_b' (72 KB) OKAY [0.002s]
Escribiendo 'qupfw_b' OKAY [0.002s]
Finalizado. Tiempo total: 0.036s
Enviando 'storsec_b' (24 KB) OKAY [0.001s]
Escribiendo 'storsec_b' OKAY [0.005s]
Finalizado. Tiempo total: 0,115 s
Enviando 'tz_b' (3092 KB) OKAY [0.079s]
Escribiendo 'tz_b' OKAY [0.029s]
Finalizado. Tiempo total: 0,152 s
Enviando 'uefisecapp_b' (124 KB) OKAY [0.004s]
Escribiendo 'uefisecapp_b' OKAY [0.005s]
Finalizado. Tiempo total: 0.046 s
Enviando 'xbl_b' (3120 KB) OKAY [0.224s]
Escribiendo 'xbl_b' OKAY [0.078s]
Finalizado. Tiempo total: 0.340 s
Enviando 'xbl_config_b' (124 KB) OKAY [0.005s]
Escribiendo 'xbl_config_b' OKAY [0.011s]
Finalizado. Tiempo total: 0,129 s
Formato de archivo disperso no válido en header magic
Cambiando el tamaño de "system_b" OKAY [0.005s]
Enviando 'system_b' disperso 1/5 (523136 KB) OKAY [29.696s]
Escribiendo "system_b" OKAY [3.170s]
Enviando 'system_b' disperso 2/5 (523148 KB) OKAY [33.593s]
Escribiendo "system_b" OKAY [3.176s]
Enviando 'system_b' disperso 3/5 (523640 KB) OKAY [22.297s]
Escribiendo "system_b" OKAY [3.169s]
Enviando 'system_b' disperso 4/5 (524256 KB) OKAY [22.455s]
Escribiendo "system_b" OKAY [3.148s]
Enviando 'system_b' disperso 5/5 (197932 KB) OKAY [7.510s]
Escribiendo "system_b" OKAY [1.413s]
Finalizado. Tiempo total: 190.558s
Formato de archivo disperso no válido en header magic
Cambiando el tamaño de 'vendor_b' OKAY [0.005s]
Enviando escaso 'vendor_b' 1/2 (523681 KB) OKAY [12.063s]
Escribiendo 'vendor_b' OKAY [3.157s]
Enviando 'vendor_b' disperso 2/2 (427876 KB) OKAY [10.100s]
Escribiendo 'vendor_b' OKAY [2.669s]
Finalizado. Tiempo total: 65.627 s
Formato de archivo disperso no válido en header magic
Cambiando el tamaño de 'product_b' OKAY [0.006s]
Enviando 'product_b' disperso 1/3 (523616 KB) OKAY [12.163s]
Escribiendo 'product_b' OKAY [3.180s]
Enviando 'product_b' disperso 2/3 (523628 KB) OKAY [12.485s]
Escribiendo 'product_b' OKAY [3.165s]
Enviando 'product_b' disperso 3/3 (245308 KB) OKAY [11.390s]
Escribiendo 'product_b' OKAY [1.675s]
Finalizado. Tiempo total: 99.562 s
Reiniciando OKAY [0.000s]
Finalizado. Tiempo total: 0.002s
 

taiger9810

New member
Aug 16, 2019
1
0
OnePlus 7T
Here is a patched MSM download tool for TMobile OP7T.
It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.

1) Download the patched MSM download tool: https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing

2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.

3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
Code:
fastboot flashing unlock_critical

4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495


How to enter EDL mode:
Me dejo de funcionar wifi no tiene dirección Mac
 

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    Here is a patched MSM download tool for TMobile OP7T.
    It will bypass the need to sim unlock before unlocking the bootloader, and will also bypass the need of an unlock token file from OnePlus (hence skip the wait period of 1 week to get the privilege to unlock). It will NOT sim unlock the phone.

    1) Download the patched MSM download tool: https://drive.google.com/file/d/12y3lO0wIgb2_LSDeVw9x_2C_HjbgZlb_/view?usp=sharing

    2) Run the tool, connect your phone in EDL mode (see below how to do it if you don't know), ensure the "sha256 check" is NOT checked, click the Start button and wait until it's completed.

    3) The phone will show a red warning saying "device is corrupt", just ignore that and wait some time. It will fallback in fastboot because it's not able to boot. Now run the following fastboot command:
    Code:
    fastboot flashing unlock_critical

    4) Bootloader is now unlocked. Update your fastboot executable, otherwise you'll encounter errors and modem issues. Download it here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip. Then boot the phone in fastboot mode, and follow the steps 7, 8 and 9 of this nice guide : https://forum.xda-developers.com/oneplus-7t/how-to/guide-t-mobile-brand-conversion-to-t4019495


    How to enter EDL mode:
    [...] Getting into EDL mode took me a while because I'd never had to do that on any previous phone way back when I used custom ROMs. Note that in EDL mode the screen is blank, and apparently it times out after 10 seconds. So the way to do it is to power off the phone and disconnect the USB if it's connected. Then press both volume UP and DOWN at same time, then while holding those buttons down, insert the USB which should already be connected to your computer. The best way would be to have the MSM program already open on your PC, then put phone into ELD mode. I had my left hand holding the volume buttons on the phone (press hard with two fingers to be sure), used right hand to plug in USB, then right hand on the mouse to work MSM. Once the USB is plugged in, watch the MSM window and look for it to say "Connected". Then just click the Start button. You can then release the volume buttons on the phone and let MSM do its thing. [...]
    3
    so I'm gonna write my own summary hoping it fills any gaps. thanks to everyone else for providing very useful information and thanks to OP for putting in the work for figuring this out.

    1. first and foremost, make sure all of your drivers are correct. this is a must. boot into fastboot and EDL modes and check your device manager to make sure their drivers are properly installed. I had issues with getting the fastboot driver to work on my desktop but was picked up easily on my laptop. i still ended up pursuing fixing the driver on the desktop but no drivers from anywhere would work. i ended up going into windows update and installing the optional driver updates--some of these might be named samsung, but install any that sound related to android. this finally fixed the fastboot driver error on my desktop. the fastboot driver on my device manager was called "kedacom USB device">android bootloader interface

    2. I used the "all in one tool" available on this forum to get into EDL mode but you can do it manually too, it's not hard. as mentioned before, you will need to 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. MSM took me about 130 seconds. This was over USB 3.0 port. I had no issue with USB 3.0 ports throughout the process but YMMV. At the end, it will give you a bootloader unlock menu and ask whether to unlock it or not. no one mentioned it before, but you have to manually click yes to unlock it. you will be kicked back into fastboot mode with the bootloader status as unlocked.

    3. I downloaded 10.0.9 global rom package, because i'm planning to relock the bootloader after. if you plan to keep bootloader unlocked just update to latest zip available. if you're planning to relock, make sure the zip isn't the latest version as you won't be able to OTA update from the OS if it's latest version (until there's another update). Copy the contents of the global rom zip into your ADB folder. The ADB tools inside the global rom zip might be older so I decided to keep the files in the ADB folder as is (i.e. the ones linked in OP) and not overwrite with the ADB files from the global rom zip. I went to CMD into the adb folder and ran the flash bat command. The first time it went to the "waiting for device" stage but did not go back into fastboot mode to continue, instead went to pink TMO bootscreen and eventually into the OS. I manually went back into fastboot mode via recovery mode and tried again. This time it went through it all (ignore the errors as mentioned in the CMD screen)

    You're done here if you want to keep the bootloader unlocked

    4. If you plan to relock bootloader, go into settings menu and look for update. you should get one, download it and install it. Once installed, factory reset and let it boot into OS. Then go into fastboot mode and relock bootloader with commands below

    check to make sure phone is being picked up by bootloader

    Code:
    fastboot devices

    command to relock bootloader

    Code:
    fastboot oem lock

    I went back into the fastboot menu to make sure it's locked and did another factory reset

    I can confirm that play store shows as certified and google pay cards can be added but I have not confirmed anything beyond that or checked netflix

    i hope this helps somewhat, good luck!
    2
    Tested, 100% working.
    No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
    This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.
    2
    Tested, 100% working.
    No risks, if there is an error you can just flash the stock TMO msm and you'll be 100% stock and working.
    This is to bypass the need to sim unlock and to bypass the wait period of OnePlus. But this does not sim unlock the phone.

    Confirmed! Presently bootloader unlocked and global rom installed. Will receive my unlock token on Friday......hee hee.
    Wanted to say thank you for putting this together and making it dummy proof.
    2
    I'm not sure. In my case, I had a driver that appeared to be correct but the MSM tool would just hang. If you have the phone running in edl mode you could check the driver version in device manager but I'm not sure how to verify which one is the correct one.

    This is the driver I ended up using.

    https://drive.google.com/file/d/0B0Fg_uwj-hWoYndYTTMwQUZ2RlU/view

    In addition, you'll need these drivers for windows too, in order for the phone to be recognized when it reboots into fastbootD.


    FastbootD is when the phone reboots for the firsttime after you run flash-all.bat, you get the screen saying hold the power button to pause booting, and then it brings you to the screen with the oneplus logo, and 3 language choices. Without these drivers it never gets recognized and can't continue.

    Between the OPS instructions and the ones posted by Vallan, i was able to do this yesterday on the Tmobile unlocked sim phone that b&h had for 299 on Black friday, works great and it auto updated itself to the latest OTA from oneplus. After doing that update, do a factory reset on it and then you can re-lock your bootloader if you want to.