Develop Bugs

Google VS. Non-Google Variant Differences

This thread is to gather technical clarification for those of us who have wondered about this:
If a Google phone (e.g. Pixel / Pixel XL) is purchased from another retailer (e.g. Verizon [with a locked bootloader]), other than the physical hardware, are there any technical differences in SOFTWARE and/or CODING that would restrict flashing OEM firmware from Google after the bootloader is unlocked?
***** (Is the Verizon variant restricted from flashing Google firmware?) *****
My apologies if this has been covered in another thread.

So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.

I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.

Radsolutionz said:
I bought Verizon pixel xl from best buy. It is sim unlocked. Bootloader is locked. It can be unlocked via depixel8 sunshine method. I flashed Google stock rom nde63p and rooted. All is working 100 percent.
Click to expand...
Click to collapse
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.

Radsolutionz said:
https://developers.google.com/android/images follow instructions exactly in the link. That's all I did. The toolkit does not work for this. Anymore problems I can assist you tomorrow. Just make sure ur phone is is bootloader mode. Also the image is fully extracted in your adb tools folder.
Click to expand...
Click to collapse
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.

1up1up said:
I'm certain I'm not missing anything here, according to steps required. It just isn't working for me.
Click to expand...
Click to collapse
Set it up on another computer and start from scratch. Windows 10 has some issues.... If it doesn't work and you want it done just get the device to me and I'll do it for u my self. Message me and I'll work it out with u.

My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app

suhailtheboss said:
My question is somewhat related so I'll post it in here.
If I unlock bootloader with depixel8, then flash the Google factory image and relock bootloader, in theory I should now have a Google version correct? Has and had success with this?
The reason I want to relock is to not trip safety net. Right now I'm enjoying the phone without root, but know I will want to root eventually and don't want to miss the easy conversion to a official Google model.
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
No. Until you see Jcase or another dev post a full Google Store conversion for the Verizon Pixel, do not relock your bootloader. That is, if you want to root your Verizon Pixel in the future.
Sent from my Pixel XL using XDA-Developers mobile app

1up1up said:
So I went ahead and downloaded the latest "7.1.0 (NDE63P, Oct 2016)" file and attempted to flash the "flash-all.bat" file on my Verizon Pixel XL through fastboot and was unsuccessful. Attached is a screenshot of the error.
It hangs at:
"(bootloader) Flashing active slot "_b"
I'm uncertain of what this means but it didn't work. It allowed me to exit and reboot to my current state before the flash. Maybe someone can chime in on this.
Click to expand...
Click to collapse
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.

1up1up said:
I too, also have a Verizon variant that is bootloader-unlocked with depixel8. What am doing differently that isn't working to flash the factory image NDE63P?
Click to expand...
Click to collapse
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.

dbrohrer said:
Update your adb drivers. You need sdk version 25. Your error, [bootb doesn't exist] is because you are using an older sdk that can't handle all of the new partitions in the Pixels. There was no boot_a or boot_b in Nexus, which is why it doesn't know where to send the files.
Click to expand...
Click to collapse
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?

Mike02z said:
Most likely you are trying to flash-all with an older version of the SDK or using another older tool. flash-all only seems to work with the latest SDK or the latest tool. You can flush each of the 14 img files individually as well.
Click to expand...
Click to collapse
I updated SDK and all is working.

1up1up said:
I updated SDK and flash was successful. Can you please help me understand this too: now that the Google Firmware has been flashed, does that "change" the phone from a "Verizon" model to a "Google" model? Also, why is it that in Developer Options, "OEM Unlocking" is still grayed out?
Click to expand...
Click to collapse
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
I see... Thank you very much for explaining that.

dbrohrer said:
Glad to hear you got it flashed. You answered your own question. Currently there is not a way to convert the Verizon model to the Google model. They are in fact exactly the same in hardware and firmware. Zero difference. The reason that it is grayed out is because when the phone first boots up it checks for a whitelist (or maybe a blacklist) by CID or MEID. If you're phone is listed as a Verizon device, the OEM unlock option is grayed out. That is the way they locked it down. They just grayed out the toggle for the locked phones.
For the time being, the only option you have is to leave the bootloader unlocked. If you lock the bootloader, there is a good chance that it will be permanent after the November security patch. Maybe later someone figures out how to fool the check at first boot (or change the CID...). Or install a custom rom. This would be the only way to turn the device into a "Google" model.
Click to expand...
Click to collapse
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?

coolhandz said:
Aside from the option to unlock/relock being greyed out, will unlocking disable the updates? I was reading another article that said if you unlock the Verizon pixel using depixel8, then you would not be able to take OTA updates. Aside from unlocking for custom roms, is there any real need to unlock?
Click to expand...
Click to collapse
Unlocking will not disable updates. In Developer Options there is a toggle to disable this. Depending on what you do to your phone after bootloader unlock, disabling this might be important to prevent bootloop during an update.
Aside from root, various flashable mods, custom rom, or custom kernel, there is not really a need to unlock. Your phone is certainly less secure by doing so. If you plan to stay completely stock, keep your bootloader locked.

Verizon pixel xl bootloader and bootloader images

If you end up unlocking the bootloader of a Verizon pixel XL correctly using depixel8, couldn't you install the system.img provided by Google that will,when relocking the bootloader, revert you to the locked stock bootloader version of the pixel XL instead of going back to the Verizon based factory bootloader?
Maybe I am misunderstanding the issue? Can anyone clarify this?

rester555 said:
If you end up unlocking the bootloader of a Verizon pixel XL correctly using depixel8, couldn't you install the system.img provided by Google that will,when relocking the bootloader, revert you to the locked stock bootloader version of the pixel XL instead of going back to the Verizon based factory bootloader?
Maybe I am misunderstanding the issue? Can anyone clarify this?
Click to expand...
Click to collapse
It's not that simple. 1st, if one's VZW device bootloader is unlocked using dePixel8, it will in all likelyhood remain unlocked in the future when flashing updates. 2nd, the bootloader.img file is identical between VZW and Google Store versions. It appears that there is something hardcoded in the IMEI on VZW devices that identifies them, then the bootloader software becomes "unlockable" when it sees that flag.
Repeating old ground, dePixel8 works on devices that are on 7.1. But the exploit has been patched by Google on 7.1.1 (December update).

cam30era said:
It's not that simple. 1st, if one's VZW device bootloader is unlocked using dePixel8, it will in all likelyhood remain unlocked in the future when flashing updates. 2nd, the bootloader.img file is identical between VZW and Google Store versions. It appears that there is something hardcoded in the IMEI on VZW devices that identifies them, then the bootloader software becomes "unlockable" when it sees that flag.
Repeating old ground, dePixel8 works on devices that are on 7.1. But the exploit has been patched by Google on 7.1.1 (December update).
Click to expand...
Click to collapse
It's the Cid. Verizon models have the Verizon Cid. I think it's like VZW001

toknitup420 said:
It's the Cid. Verizon models have the Verizon Cid. I think it's like VZW001
Click to expand...
Click to collapse
Pretty sure it's not the cid. If I recall right most of all this has been covered in this long thread over in the Guides & News section. Where I recall reading at least one person that was able to confirm that it isn't the CID alone, if at all.

Thanks guys.. it makes my decision easier not to buy the VZW version easier. The deal they have is good, but not worth my time if I can't unlock it like the Google version.

rester555 said:
Thanks guys.. it makes my decision easier not to buy the VZW version easier. The deal they have is good, but not worth my time if I can't unlock it like the Google version.
Click to expand...
Click to collapse
If you hurry up and get one soon it won't be on 7.1.1 yet. Probably not till the end of January will they actually ship with it. They won't unbox phones to install the update. People are still getting them now with 7.1

I much prefer not to have to deal with that BS and wait for price decreases for the Google store version or through other means.

replacement device unlocking question

So, i broke my direct from google pixel xl, that was unlocked. I had insurance through verizon and they sent me a new one. Now, i know the verizon versions are locked, which is what i didn;t want, but i had no choice through asurion. The phone i received is on NHG47L which isn't the verizon version, but the OEM unlock is still grayed out. can anyone tell me why i can't unlock even though this seems to be a google fi/tmobile build?
i have no put a sim in it yet, i've only connected it to wifi. i'm waiting till i have a firm answer one way or the other.

@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3

cam30era said:
@Legacystar,
See post #25 > https://forum.xda-developers.com/pixel-xl/help/oem-unlocking-disabled-google-store-t3507209/page3
Click to expand...
Click to collapse
i did connect it to wifi, it did not change the OEM unlock option.

@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.

cam30era said:
@Legacystar,
One can sideload any version of security update via ADB. If you've connected to internet and bootloader unlock is still grayed out, then it sounds like you do indeed have a VZW version.
Click to expand...
Click to collapse
Would flashing a factory image do anything, maybe a previous version?

Legacystar said:
Would flashing a factory image do anything, maybe a previous version?
Click to expand...
Click to collapse
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.

cam30era said:
If you can't unlock your bootloader, then you can't flash a factory image. If this is a VZW version, there's nothing you can do.
Click to expand...
Click to collapse
so, if the bootloader was never unlockable, how would one change the software version?

Legacystar said:
so, if the bootloader was never unlockable, how would one change the software version?
Click to expand...
Click to collapse
ADB sideload. Or wait for OTA to be pushed.

cam30era said:
ADB sideload. Or wait for OTA to be pushed.
Click to expand...
Click to collapse
i meant, how did this phone's software get changed?

Legacystar said:
i meant, how did this phone's software get changed?
Click to expand...
Click to collapse
The firmware is downloaded based on the sim in the device. Not where it was purchased

pcriz said:
The firmware is downloaded based on the sim in the device. Not where it was purchased
Click to expand...
Click to collapse
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?

mattwheat said:
So theoretically, I could purchase a VZW pixel XL never connect to WiFi or data, and get home insert a T-Mobile sim and check the "OEM unlocking" then unlock the bootloader via fastboot. Then once I've flashed recovery and pure Nexus or any other rom install my VZW sim and profit?
Click to expand...
Click to collapse
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.

pcriz said:
You still need to use the bootloader exploit before the firmware updates to 7.1.1, can't just unlock via fastboot like a play store model.
Click to expand...
Click to collapse
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.

mattwheat said:
Well I bought the 128gig pixel XL. Didn't let the sales person activate it for me or turn it on. I got it home and pulled the Sim and started it up with no Sim or wifi. My luck the freaking lcd doesn't work. It responds to touch and the phone boots but the screen would not light up a bit. So I took it back and exchanged for another. ....did the same with the Sim and no wifi.... Booted and straight to "About Phone" and of course it's on 7.1.1 already. This is the first phone I've had in 5-6 years that wasn't rooted and bootloader unlocked. What makes it even worse is it's a Google branded phone. I can't believe Google allows VZW to lock it down like this.
Click to expand...
Click to collapse
Verizon isn't the only carrier to lock it down. Google has never been implicitly root friendly, also I'm sure a partner ship with verizon is to their benefit. Like getting their foot in the door to a wider market. The trade off is the bootloader.

Verizon Pixel Bootloader

Okay so I just got a replacement on my Verizon Google pixel and after everything was setup I noticed that in the developer options it gave me the option to unlock my Bootloader. I know the Verizon models are locked and after 7.1 the exploit was patched. I have all the Verizon bloatware so is this just a bug or is it possible? I turned off all automatic updates just in case so should I go ahead and try?
youtu.be/yYbhMk4fnLM

The0nlyboss said:
Okay so I just got a replacement on my Verizon Google pixel and after everything was setup I noticed that in the developer options it gave me the option to unlock my Bootloader. I know the Verizon models are locked and after 7.1 the exploit was patched. I have all the Verizon bloatware so is this just a bug or is it possible? I turned off all automatic updates just in case so should I go ahead and try?
youtu.be/yYbhMk4fnLM
Click to expand...
Click to collapse
If you want to try unlocking your bootloader go for it. But there's not much benefit to unlocking your bootloader unless you plan to root or flash a custom rom or custom kernel or something. Simply unlocking the bootloader but otherwise staying fully stock will not allow your phone to pass safety net so you won't be able to use Android Pay. There have been a few other posts from Verizon customers where they got phones with the option to unlock the bootloader enabled so you probably just got lucky.

The0nlyboss said:
Okay so I just got a replacement on my Verizon Google pixel and after everything was setup I noticed that in the developer options it gave me the option to unlock my Bootloader. I know the Verizon models are locked and after 7.1 the exploit was patched. I have all the Verizon bloatware so is this just a bug or is it possible? I turned off all automatic updates just in case so should I go ahead and try?
youtu.be/yYbhMk4fnLM
Click to expand...
Click to collapse
If it was shipped from Carol Stream, Illinois and if you pop in your SIM and the Verizon website calls it a non-VZW phone., then you got a Google Edition. Since OEM unlocking is not grayed out on yours, it's almost for certain a Google Edition. Same happened to me, the bloatware came when the Verizon SIM was inserted.
I agree with the above jhs39 post, though, only do it if you have a reason. I wanted the Pure Nexus ROM and ViPER4Android so I did it.

jhs39 said:
If you want to try unlocking your bootloader go for it. But there's not much benefit to unlocking your bootloader unless you plan to root or flash a custom rom or custom kernel or something. Simply unlocking the bootloader but otherwise staying fully stock will not allow your phone to pass safety net so you won't be able to use Android Pay. There have been a few other posts from Verizon customers where they got phones with the option to unlock the bootloader enabled so you probably just got lucky.
Click to expand...
Click to collapse
I don't have the need for it unlocked now but is it possible that an update can remove the option as I do want to flash a rom in the future.

3aucla1r3 said:
If it was shipped from Carol Stream, Illinois and if you pop in your SIM and the Verizon website calls it a non-VZW phone., then you got a Google Edition. Since OEM unlocking is not grayed out on yours, it's almost for certain a Google Edition. Same happened to me, the bloatware came when the Verizon SIM was inserted.
I agree with the above jhs39 post, though, only do it if you have a reason. I wanted the Pure Nexus ROM and ViPER4Android so I did it.
Click to expand...
Click to collapse
Ah I see. It was shipped from that location and I checked the IMEI on Verizon's website and it says it's not capable for some reason so I'm guessing it's a GE.

The0nlyboss said:
Ah I see. It was shipped from that location and I checked the IMEI on Verizon's website and it says it's not capable for some reason so I'm guessing it's a GE.
Click to expand...
Click to collapse
Yeah but it really is capable, just put the SIM in

If you plan on flashing custom in the future then I would unlock now so you don't have to lose all you're data later. Rather wipe while it's new and doesn't have months of data on it.

You never know when you might get screwed over by an update and or want to flash back a version.
I say unlock to give yourself a few more exit strategies should anything go wrong and if you decide to root and rom at some point later you aren't gonna wipe your device.
If you want to pass safety net for android pay you just need to flash a custom kernel.

The0nlyboss said:
I don't have the need for it unlocked now but is it possible that an update can remove the option as I do want to flash a rom in the future.
Click to expand...
Click to collapse
That's true. But if you use Android Pay or any other apps that require safety net they will stop working unless you flash a custom kernel. If that doesn't matter to you then you should unlock the bootloader while you can.

Question 2023 T-Mobile vs Unlocked OP 9 Pro

Question:
I own a T-Mobile account. Just went through major drama w/ amazon seller, a T-Mobile phone that wouldn't unlock because it wasn't paid off, and more. Never mind that.... sending it back.
I want to know if I can buy a non-US and/or unlocked OP 9 Pro and still have it work with my T-Mobile sim?
I want in the end, ideally, to have a OP 9 Pro running the very latest Oxygen OS/updates and have it be rooted. But again, w/ a T-Mobile sim.
Advice? Has anyone else faced this?

shonkin said:
Question:
I own a T-Mobile account. Just went through major drama w/ amazon seller, a T-Mobile phone that wouldn't unlock because it wasn't paid off, and more. Never mind that.... sending it back.
I want to know if I can buy a non-US and/or unlocked OP 9 Pro and still have it work with my T-Mobile sim?
I want in the end, ideally, to have a OP 9 Pro running the very latest Oxygen OS/updates and have it be rooted. But again, w/ a T-Mobile sim.
Advice? Has anyone else faced this?
Click to expand...
Click to collapse
Not Sure about non us but unlocked yes you can

shonkin said:
Question:
I own a T-Mobile account. Just went through major drama w/ amazon seller, a T-Mobile phone that wouldn't unlock because it wasn't paid off, and more. Never mind that.... sending it back.
I want to know if I can buy a non-US and/or unlocked OP 9 Pro and still have it work with my T-Mobile sim?
I want in the end, ideally, to have a OP 9 Pro running the very latest Oxygen OS/updates and have it be rooted. But again, w/ a T-Mobile sim.
Advice? Has anyone else faced this?
Click to expand...
Click to collapse
Don't send back.... Using the T-Mobile app and chat you can be over complementary and ask for full unlock and should be able to get it that way. Option 2 is to use a modded MSM tool to convert to Global, unlock bootloader, us a modded Glo to TMO MSM TOOL to get back to TMO firmware and update. But recommend to stay away from A13 for now
.

TheGhost1951 said:
Don't send back.... Using the T-Mobile app and chat you can be over complementary and ask for full unlock and should be able to get it that way. Option 2 is to use a modded MSM tool to convert to Global, unlock bootloader, us a modded Glo to TMO MSM TOOL to get back to TMO firmware and update. But recommend to stay away from A13 for now
.
Click to expand...
Click to collapse
Was your recommendation to avoid updating based on the trouble that DaveImagery was having with achieving root? If so, I can assure you rooting the T-Mobile android 13 update is no different than rooting the global or eu firmware, aside from having to always temp boot TWRP rather than actually install it. TWRP acts up sometimes but it works. I think he was either having a problem with the driver's, USB port, or cable, or something went wrong when he pulled the boot image via MSM tool.

Masterchief87 said:
Was your recommendation to avoid updating based on the trouble that DaveImagery was having with achieving root? If so, I can assure you rooting the T-Mobile android 13 update is no different than rooting the global or eu firmware, aside from having to always temp boot TWRP rather than actually install it. TWRP acts up sometimes but it works. I think he was either having a problem with the driver's, USB port, or cable, or something went wrong when he pulled the boot image via MSM tool.
Click to expand...
Click to collapse
I just want to wait awhile to ensure all the kinks are out be for updating. Any new features etc...

shonkin said:
Question:
I own a T-Mobile account. Just went through major drama w/ amazon seller, a T-Mobile phone that wouldn't unlock because it wasn't paid off, and more. Never mind that.... sending it back.
I want to know if I can buy a non-US and/or unlocked OP 9 Pro and still have it work with my T-Mobile sim?
I want in the end, ideally, to have a OP 9 Pro running the very latest Oxygen OS/updates and have it be rooted. But again, w/ a T-Mobile sim.
Advice? Has anyone else faced this?
Click to expand...
Click to collapse
If you got the factory unlocked one then sure, it'll work with a t-mobile sim. The question is whether it will be 100% compatible with t-mobile's network or not. I don't know the answer to that question. It's worth noting however that the T-Mobile variant is slower to get updates, and just got Android 13 this month. If I'm not mistaken, the global and EU variants got Android 13 last year. This fall/winter the other variants will probably be getting android 14, while the t-mobile variant waits until next spring.

T-Mobile updates are slower because they are more refined and sometimes include multiple updates in one update. That is why they are slower..

shonkin said:
Question:
I own a T-Mobile account. Just went through major drama w/ amazon seller, a T-Mobile phone that wouldn't unlock because it wasn't paid off, and more. Never mind that.... sending it back.
I want to know if I can buy a non-US and/or unlocked OP 9 Pro and still have it work with my T-Mobile sim?
I want in the end, ideally, to have a OP 9 Pro running the very latest Oxygen OS/updates and have it be rooted. But again, w/ a T-Mobile sim.
Advice? Has anyone else faced this?
Click to expand...
Click to collapse
What did you decide to do?

shonkin said:
Question:
I own a T-Mobile account. Just went through major drama w/ amazon seller, a T-Mobile phone that wouldn't unlock because it wasn't paid off, and more. Never mind that.... sending it back.
I want to know if I can buy a non-US and/or unlocked OP 9 Pro and still have it work with my T-Mobile sim?
I want in the end, ideally, to have a OP 9 Pro running the very latest Oxygen OS/updates and have it be rooted. But again, w/ a T-Mobile sim.
Advice? Has anyone else faced this?
Click to expand...
Click to collapse
im on an unlocked (purchased new) OP9 pro and I have no issues. I've always wanted to see if TMO modem works better, but it works great enough that it't more of just a curiosity.

TheGhost1951 said:
What did you decide to do?
Click to expand...
Click to collapse
I decided to stay with what I got, esp. as the seller also (belatedly) included the original 65w fast charger. I did a bit of whining. So now I'm trying to get my employer to leverage t-mobile into unlocking the phone, since we've been w/ them a long time and it technically is my employers' phone. (They appreciate my geek interests and are willing.)
If I can get it unlocked, the next questions will be about just how flexible T-Mobile's sim will be with various rooted Oxygen OS's.
I used to root all the time.... my Samsung Note 4 (dang I loved that phone), my OnePlus 2 (rebuilt from 2 broken ones... by me!), and so on. But Samsung's Note 9 wasn't rootable (I didn't have the Exynos version). So I got stuck. This time I bought the OnePlus 9 Pro intentionally in order to play w/ rooting again.
But the whole thing has gotten more interesting. TWRP... does it still work and do the awesome backups / restores of multiple different systems on the same phone? And Magisk.... sheesh... so much I don't know.

shonkin said:
I decided to stay with what I got, esp. as the seller also (belatedly) included the original 65w fast charger. I did a bit of whining. So now I'm trying to get my employer to leverage t-mobile into unlocking the phone, since we've been w/ them a long time and it technically is my employers' phone. (They appreciate my geek interests and are willing.)
If I can get it unlocked, the next questions will be about just how flexible T-Mobile's sim will be with various rooted Oxygen OS's.
I used to root all the time.... my Samsung Note 4 (dang I loved that phone), my OnePlus 2 (rebuilt from 2 broken ones... by me!), and so on. But Samsung's Note 9 wasn't rootable (I didn't have the Exynos version). So I got stuck. This time I bought the OnePlus 9 Pro intentionally in order to play w/ rooting again.
But the whole thing has gotten more interesting. TWRP... does it still work and do the awesome backups / restores of multiple different systems on the same phone? And Magisk.... sheesh... so much I don't know.
Click to expand...
Click to collapse
TWRP is a little wonky, Magisk is a yess!

If you have no luck through TMO with unlocking the bootloader, let me know. There is another way to do that.

TheGhost1951 said:
If you have no luck through TMO with unlocking the bootloader, let me know. There is another way to do that.
Click to expand...
Click to collapse
How exactly would that work? I've read that using the T-Mobile->EU MSM allows you to unlock the bootloader without an unlock token, but wouldn't using another MSM to go back to T-Mobile firmware re-lock the bootloader? Would the fact that it's already been unlocked previously allow it to be unlocked again without a token, even after flashing back to the T-Mobile firmware? Mine came sim unlocked and didn't have any trouble getting an unlock token so I never tried the workaround and I've just flashed the unlock token every time.

Masterchief87 said:
How exactly would that work? I've read that using the T-Mobile->EU MSM allows you to unlock the bootloader without an unlock token, but wouldn't using another MSM to go back to T-Mobile firmware re-lock the bootloader? Would the fact that it's already been unlocked previously allow it to be unlocked again without a token, even after flashing back to the T-Mobile firmware? Mine came sim unlocked and didn't have any trouble getting an unlock token so I never tried the workaround and I've just flashed the unlock token every time.
Click to expand...
Click to collapse
I have a modded TMO to Glo and a modded Glo to TMO.....I have used it before....

So it is in fact possible to skip waiting for a token. You have to use MSM to convert to EU then you're free to do whatever since the bootloader is now unlocked? Am I understanding? I'd like to personally flash Lineage as soon as I'm unlocked, will the above process work for me?

TheGhost1951 said:
I have a modded TMO to Glo and a modded Glo to TMO.....I have used it before....
Click to expand...
Click to collapse
I believe you. What I'm saying is that according to what I have read, every time you use a MSM tool it locks the bootloader. So you convert to eu, and unlock the bootloader without an unlock token, because this specific firmware is unique in its ability to be unlocked without a token. Then you flash the T-Mobile firmware with another MSM which locks the bootloader all over again, and now you are once again on T-Mobile firmware with a locked bootloader and no unlock token. My questions are:
1) Does the fact that you previously unlocked the bootloader permanently do away with the need for an unlock token, even after you MSM back to T-Mobile firmware and re-lock the bootloader?
2) If so then how do you unlock the bootloader the second time after you MSM back to T-Mobile firmware? Do you repeat the same procedure you did on the EU firmware, or do you just run the "fastboot oem unlock" command from now on?

Masterchief87 said:
I believe you. What I'm saying is that according to what I have read, every time you use a MSM tool it locks the bootloader. So you convert to eu, and unlock the bootloader without an unlock token, because this specific firmware is unique in its ability to be unlocked without a token. Then you flash the T-Mobile firmware with another MSM which locks the bootloader all over again, and now you are once again on T-Mobile firmware with a locked bootloader and no unlock token. My questions are:
1) Does the fact that you previously unlocked the bootloader permanently do away with the need for an unlock token, even after you MSM back to T-Mobile firmware and re-lock the bootloader?
2) If so then how do you unlock the bootloader the second time after you MSM back to T-Mobile firmware? Do you repeat the same procedure you did on the EU firmware, or do you just run the "fastboot oem unlock" command from now on?
Click to expand...
Click to collapse
The way it is done with the modded MSM Tool to go from Global back to TMO it does not lock the bootloader. Can't explain why, but it doesn't. A pure TMO MSM Tool will relock the bootloader. Been there and done both ways.

In a few days I will do it again just to triple check the procedures and create the necessary modded MSM Tool zip files to share.

Another way to get unlock token is by booting to bootloader and run the command to get unlock code. Copy the long list of numbers along with IMEI and serial number and email OnePlus support with the information stating the TMO unlock token website is not working for you and they will generate a token for you. I had to do that when my first token quit working....

How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com