Convert T-Mobile to International (with Bootloader Re-LOCK)

[thattechguy_69]

I am on a converted tmobile IN2017 to IN2015 Global Rom. I have updated to OOS12 and have been on it for maybe a month. I want to flash an Android 12 custom rom. What is my best path for success? Should I go all the way back to Android 10 Tmobile version IN2017 using MSM tool?
Edit: Nevermind, I figured it out

you can download the downgrade files like the local update apk and the oos 11 ota, then install custom roms in oos 11

 

[DerrickTight]

you can download the downgrade files like the local update apk and the oos 11 ota, then install custom roms in oos 11

Yeah I noticed that a gentleman had left a link to it a few pages back. Works like a charm. Now on Evolution 12 and its awesome. OOS12 was too buggy.

 

[thattechguy_69]

Yeah I noticed that a gentleman had left a link to it a few pages back. Works like a charm. Now on Evolution 12 and its awesome. OOS12 was too buggy.

Im loving oos12 c.16

 

[DerrickTight]

Im loving oos12 c.16

I loved it too till my keyboard wouldn't manifest and I had to reboot twice a day to make it pop up. And for some reason the PlayStore kept resetting its settings to AutoUpdate Apps and on any network. I dont like that kinda stuff. But it worked great for a while and it started getting laggy and slow.

 

[Melcore127]

im kinda off topic here but ive been waiting for my tmobile unlock file and for some reason im kinda worried cus i dont have a tmobile sim and im out of the country so how will ik when they procces this and does it really take 2 weeks ?

Im loving oos12 c.16

 

[sturner1254]

if your talking about the bootloader unlock you will get an email when its done. and mine was a week exactly.

 

[Melcore127]

if your talking about the bootloader unlock you will get an email when its done. and mine was a week exactly.

oh ok is there any problems if im a different country and stuff

 

[sturner1254]

shouldnt be as long as you have internet access.

 

[thattechguy_69]

im kinda off topic here but ive been waiting for my tmobile unlock file and for some reason im kinda worried cus i dont have a tmobile sim and im out of the country so how will ik when they procces this and does it really take 2 weeks ?

just make sure your phone is already carrier unlocked and request the bootloader file unlock.bin on their website and like @sturner1254 said, it is exactly one week from the time you submit one.

 

[Melcore127]

just make sure your phone is already carrier unlocked and request the bootloader file unlock.bin on their website and like @sturner1254 said, it is exactly one week from the time you submit one.

yup i got mine today , now to load evo x on my phone thanks
yea my phone is carrier unlocked ive made sure of it
now all i gotta do is just use the token unlock my boot loader and load a custom rom like u would for any other OP8 phone

 

[sturner1254]

so far so good. mine has stayed on the latest A10 without forcing update to 11. it still annoys me with notifications though even though i tried to block them. so far working very smooth,

 

[Melcore127]

does anyone have problems downloading roms with twrp

 

[Melcore127]

each time i try to install via twrp icant seem to get the twrp folder in there to install the custom rom package

 

[thattechguy_69]

each time i try to install via twrp icant seem to get the twrp folder in there to install the custom rom package

I have never used twrp on my device. Just use recovery method. I think its more convenient

 

[Melcore127]

i boot into twrp then go to wipe and format data

I have never used twrp on my device. Just use recovery method. I think its more convenient

ok lemme try their recovery method

 

[Melcore127]

So guys update it actually worked and oh my evolution x is amazing now one thing could I lock the boot loader now will it do anything or cause any problems

 

[thattechguy_69]

So guys update it actually worked and oh my evolution x is amazing now one thing could I lock the boot loader now will it do anything or cause any problems

You cant really lock the bootloader on custom roms since its not the original OS and the phone will corrupt itself. The only exceptions are using Pixel Experience, self signed build of lineage os, and Jaguar ROM.

 

[TalionDread]

Sorry for spamming the board today, but I think I figured it out.

Thanks to @thattechguy_69 for all the work here so far. This is just to help anybody who is having issues like I did.

The "critical partitions" issue appears to be a DRIVERS issue, not a fastboot version issue or anything else with the actual phone or ROM files. I had installed all of the drivers that every guide said to install, but I stumbled upon this post by @FoxyDrew that solved my issue.

Here's how I finally got into 10.5.12.IN21AA (Global ROM) on my IN2017:

1. Just to be safe (not sure if it's necessary) boot into TEST MODE on your Windows machine. I did all of this from Test Mode.
2. Download the files from the zip attached at the bottom of the first post on this thread. Install both files (OnePlus USB Drivers and QDLoader HS-USB Driver).
3. At some point I THOUGHT I installed the Fastboot drivers, but maybe I messed that part up or maybe it was before I was in Test Mode. Regardless, download the Google fastboot driver zip in this post. Unzip it to your desktop.
4. Open the extracted folder and then the usb_driver folder inside, then right-click on the android_winusb.inf file and select Install. Confirm the installation.
5. Plug in your phone.
6. Open Device Manager. Your phone should show up under "Universal Serial Bus controllers" as "IN2017" when it is in CHARGING ONLY mode, and under Portable Devices when in File Transfer mode or PNP mode. If not, you'll need to fix your USB drivers from step 2 above.
7. Make sure you can get adb commands to work, then reboot to the bootloader ("adb reboot bootloader" should get you to the FastBoot Mode menu with the big green "START" banner at the top) and make sure fastboot commands also work ("fastboot devices" will show you if your phone is detected properly).
8. Check Device Manager again while in bootloader mode - your phone should now show up under "Android Phone" as "Android Bootloader Interface." If it shows up as IN2017 with an exclamation mark, you need to fix the issues with the fastboot driver in step 4 above. I actually did this step while at the "waiting for device" message while flashing the Global ROM and it kick-started the installation's second phase.
9. I also followed some steps from this post by @awsan - I copied the entire platform-tools folder that I downloaded from his post (r31.0.2) into the 10.5.12-GLOBAL folder, replacing all duplicate files. I don't think booting into fastboot like he says to do (language selection splash screen) worked, I had to boot into the bootloader from there to get the flash-all.bat to start.
10. From here, I think I just double-clicked the flash-all.bat and everything worked properly - with the note that I was stuck at "waiting for device" after the first reboot command in the middle of the installation. The process in step 4 got me through this.

This fixed my issues with not being able to flash critical partitions (because I suspect they re-lock when fastbootd switches into bootloader if you manually do it). Now it doesn't hang at all. I am going to play around with this to make sure I didn't miss anything and see if it works with other TMo firmware versions and the newer 11.0 Global ROM.

I have not tried locking the bootloader yet.

Oh, and 5G and VoLTE both appear to be working.

Thank you for sharing!!! Was pulling my hair wondering why the heck I couldn't figure this out. Finally working now.

 

[longlivandroid]

Does anyone have their phone restart twice? When I restart my phone, it seems to restart one more time shortly after I start to use it. It works fine after that but I've noticed that it happens consistently and I was wondering if there's something I can do to prevent that. Thanks!

 

[thattechguy_69]

Does anyone have their phone restart twice? When I restart my phone, it seems to restart one more time shortly after I start to use it. It works fine after that but I've noticed that it happens consistently and I was wondering if there's something I can do to prevent that. Thanks!

yeah in my experience on oos 12 but it was gone after c.16