Related
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.
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.
I've got my eyes on a unlocked Verizon pixel 3 XL that's unlocked. How deep is Verizon's software in the pixel and would it even be possible to fully convert it to a regular Google pixel?
https://forum.xda-developers.com/pixel-3-xl/help/verizon-pixel-3xl-vs-google-pixel-3xl-t3863130
Please use the search function before posting a new topic. Multiple threads about the same thing only confuse and clutter. Thanks.
mac208x said:
I've got my eyes on a unlocked Verizon pixel 3 XL that's unlocked. How deep is Verizon's software in the pixel and would it even be possible to fully convert it to a regular Google pixel?
Click to expand...
Click to collapse
If the bootloader is unlocked I don't see any reason you can't use the non verizon firmware on it. The devices themselves are identical, just the firmware is different. Note that I have not done this so you're at your own risk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
If the bootloader is unlocked I don't see any reason you can't use the non verizon firmware on it. The devices themselves are identical, just the firmware is different. Note that I have not done this so you're at your own risk.
Click to expand...
Click to collapse
As far as I know it's sim unlocked. If that's unlocked, bootloader should be unlockable as well right? Or how does the process go on the pixel?
On 6T it's you get a sim unlock, then you send a request application, once approved they send you a .bin to unlock the bootloader thru fastboot
mac208x said:
As far as I know it's sim unlocked. If that's unlocked, bootloader should be unlockable as well right? Or how does the process go on the pixel?
On 6T it's you get a sim unlock, then you send a request application, once approved they send you a .bin to unlock the bootloader thru fastboot
Click to expand...
Click to collapse
No, sim and bootloader are two different things. You'd need the bootloader unlocked to flash the regular Google pixel firmware. Sim unlock just allows you to use the phone on different carriers.
Sent from my [device_name] using XDA-Developers Legacy app
spotmark said:
https://forum.xda-developers.com/pixel-3-xl/help/verizon-pixel-3xl-vs-google-pixel-3xl-t3863130
Please use the search function before posting a new topic. Multiple threads about the same thing only confuse and clutter. Thanks.
Click to expand...
Click to collapse
There was absolutely nothing helpful In that thread, just speculations.
jd1639 said:
No, sim and bootloader are two different things. You'd need the bootloader unlocked to flash the regular Google pixel firmware. Sim unlock just allows you to use the phone on different carriers.
Click to expand...
Click to collapse
I understand the difference so In another words the bootloader is not unlockable on the Verizon one and there is no process for once it's sim unlocked like it is on the Oneplus 6T (where sim unlock is required in order to unlock bootloader)
mac208x said:
I understand the difference so In another words the bootloader is not unlockable on the Verizon one and there is no process for once it's sim unlocked like it is on the Oneplus 6T (where sim unlock is required in order to unlock bootloader)
Click to expand...
Click to collapse
No you will not be able to unlock the bootloader on the Verizon variant weather it is sim unlocked or not. However you can uninstall all the pre loaded Verizon apps. I had the Verizon model and was able to uninstall all the bloat. The only difference is the bootloader and being able to root.
Misterxtc said:
No you will not be able to unlock the bootloader on the Verizon variant weather it is sim unlocked or not. However you can uninstall all the pre loaded Verizon apps. I had the Verizon model and was able to uninstall all the bloat. The only difference is the bootloader and being able to root.
Click to expand...
Click to collapse
Oh balls. So the only way it's to crack it? That's peachy
mac208x said:
There was absolutely nothing helpful In that thread, just speculations.
Click to expand...
Click to collapse
The very first post in that thread says the VZW bootloader can't be unlocked.
mac208x said:
Oh balls. So the only way it's to crack it? That's peachy
Click to expand...
Click to collapse
Correct, you might want to check this thread out. It is being looked in to but doesn't look all that promising.
Misterxtc said:
Correct, you might want to check this thread out. It is being looked in to but doesn't look all that promising.
Click to expand...
Click to collapse
I've read thru it, I mean someone will crack it sooner or later. Some fine folks brainstorming it. Wish it was as simple as on the one plus, you just wait 7 days and you're unlocked.
Is there a difference in model number or something on the box itself?
mac208x said:
Is there a difference in model number or something on the box itself?
Click to expand...
Click to collapse
If you want an unlockable bootloader steer clear of verizon plain and simple. No way around it
c_86 said:
If you want an unlockable bootloader steer clear of verizon plain and simple. No way around it
Click to expand...
Click to collapse
I know, was trying to make sure the one I was getting on eBay was infact a Google one. Apparently there's a major difference in the label. Same model number etc. However there's a lot more writing on it. Mention of imported by Google Canada which isn't present on the Verizon one.
Is there a way to flash unlock google global version firmware onto the Verizon pixel 6 pro without root/unlock bootloader like there use to be. Can't believe nobody has asked this yer
dprscorpio7 said:
Is there a way to flash unlock google global version firmware onto the Verizon pixel 6 pro without root/unlock bootloader like there use to be. Can't believe nobody has asked this yer
Click to expand...
Click to collapse
Haven't tried it yet, but I'm assuming the Android Flash Tool would work.
Android Flash Tool
flash.android.com
DarkusRattus said:
Haven't tried it yet, but I'm assuming the Android Flash Tool would work.
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Also, just to confirm there is no bootloader unlock for Verizon version right
dprscorpio7 said:
Also, just to confirm there is no bootloader unlock for Verizon version right
Click to expand...
Click to collapse
Correct, and likely never will have bootloader unlock (for this or any future Verizon phone) except perhaps paying someone to do so once anyone figures out some way to hack it. I wouldn't hold my breath, though. The only way in the past has been by vulnerabilities/hacks, or the one time Verizon accidentally let those on Android 7.10 on the Pixel 1 the ability to toggle OEM Unlocking, but they patched it in Android 7.11.
dprscorpio7 said:
Is there a way to flash unlock google global version firmware onto the Verizon pixel 6 pro without root/unlock bootloader like there use to be. Can't believe nobody has asked this yer
Click to expand...
Click to collapse
Unless you'll be using the device on an international carrier Google doesn't compile for, there's no reason to do so that I'm aware of, as the images aren't for branded devices, but for the carrier the device is being used on.
JW09I4 said:
Unless you'll be using the device on an international carrier Google doesn't compile for, there's no reason to do so that I'm aware of, as the images aren't for branded devices, but for the carrier the device is being used on.
Click to expand...
Click to collapse
I need the unlocked version from Google store. I still have a Verizon security check on the phone and I bought it unlocked from best buy... So that is the reason. I want to know if I can flash Google store stock firmware on this phone?
dprscorpio7 said:
I need the unlocked version from Google store. I still have a Verizon security check on the phone and I bought it unlocked from best buy... So that is the reason. I want to know if I can flash Google store stock firmware on this phone?
Click to expand...
Click to collapse
You can only flash a full firmware image with the bootloader unlocked, however you should be able to flash the OTA update required (you could also use Google's online Android Flash Tool).
AFAIK, there is no difference in the firmware between the unlocked vs branded devices besides bloatware from the carrier.
My understanding of the different images Google has compiled for specific carriers has to do with tweaks to the radio software and/or how the firmware interacts with the radio to ensure the best possible experience across carriers.
JW09I4 said:
You can only flash a full firmware image with the bootloader unlocked, however you should be able to flash the OTA update required (you could also use Google's online Android Flash Tool).
AFAIK, there is no difference in the firmware between the unlocked vs branded devices besides bloatware from the carrier.
My understanding of the different images Google has compiled for specific carriers has to do with tweaks to the radio software and/or how the firmware interacts with the radio to ensure the best possible experience across carriers.
Click to expand...
Click to collapse
Well I've got a best buy unlocked version and yes I can unlock bootloader no problem and still getting a Verizon security check on hotspot which is the reason for me needing different firmware on phone. So I'll go ahead and unlock the bootloader if you can point me in the direction links of information on the flash tool and firmware I'm looking for that would be great. I want the global firmware unlocked for pixel 6 pro link
Here's the image.
dprscorpio7 said:
Here's the image.
Click to expand...
Click to collapse
That's likely not going to go away with the Global image since the only differences between the images have to do with how the radios communicate with the arbitrary carrier [AFAIK]. If you're using Verizon, the Verizon image is the correct image to use.
For your issue, there are ways to get around it, possibly via the build.prop, but if not, then likely via a Magisk module.
The last Pixel I had before the 6 Pro was the Pixel XL and tethering up until then was controlled via a true/false [1/0] value within the build.prop, however that may have changed, but tethering is software-controlled, not radio-controlled.
Full firmware image (instructions) vs OTA image (instructions)
dprscorpio7 said:
Well I've got a best buy unlocked version and yes I can unlock bootloader no problem and still getting a Verizon security check on hotspot which is the reason for me needing different firmware on phone. So I'll go ahead and unlock the bootloader if you can point me in the direction links of information on the flash tool and firmware I'm looking for that would be great. I want the global firmware unlocked for pixel 6 pro link
Click to expand...
Click to collapse
I'm not entirely sure what you mean by Verizon security check. Do you have Verizon as your provider? If so then you're out of luck no matter what firmware you flash, hotspot will cost you. I'm not sure about what happens if you root though but that's a horse of another color. Lots of threads on bypassing hotspot restrictions if you have root.
This security check does not happen if you buy directly from Google store, so I need that firmware serial number and download file with how to flash it on my device.
dprscorpio7 said:
This security check does not happen if you buy directly from Google store, so I need that firmware serial number and download file with how to flash it on my device.
Click to expand...
Click to collapse
Please see my prior comment
roirraW edor ehT said:
Correct, and likely never will have bootloader unlock (for this or any future Verizon phone) except perhaps paying someone to do so once anyone figures out some way to hack it. I wouldn't hold my breath, though. The only way in the past has been by vulnerabilities/hacks, or the one time Verizon accidentally let those on Android 7.10 on the Pixel 1 the ability to toggle OEM Unlocking, but they patched it in Android 7.11.
Click to expand...
Click to collapse
That was awesome...
dprscorpio7 said:
This security check does not happen if you buy directly from Google store, so I need that firmware serial number and download file with how to flash it on my device.
Click to expand...
Click to collapse
This isn't even a security check? Did you read the pop up? It clearly states to call customer service to subscribe and activate the hotspot. If you don't pay for hotspot, it won't work.... Also, if you bought the unlocked version from Best Buy.. then it is unlocked... There is no other software to flash. However, if you bought (which I'm sure you did) the Verizon version from Best Buy then it is a carried branded device, and it is unfortunately not unlocked straight from Google.
teegraves58 said:
This isn't even a security check? Did you read the pop up? It clearly states to call customer service to subscribe and activate the hotspot. If you don't pay for hotspot, it won't work.... Also, if you bought the unlocked version from Best Buy.. then it is unlocked... There is no other software to flash. However, if you bought (which I'm sure you did) the Verizon version from Best Buy then it is a carried branded device, and it is unfortunately not unlocked straight from Google.
Click to expand...
Click to collapse
It is a security check, I promise you. I've had the pixels in the past and bad the same issue I'll show you that when I flash this unlocked firmware from Google store I guarantee you the security check or please subscribe will not pop up and will allow me to enable hotpsot
dprscorpio7 said:
It is a security check, I promise you. I've had the pixels in the past and bad the same issue I'll show you that when I flash this unlocked firmware from Google store I guarantee you the security check or please subscribe will not pop up and will allow me to enable hotpsot
Click to expand...
Click to collapse
Have you tried to install global firmware on verizon Pixel?
teegraves58 said:
This isn't even a security check? Did you read the pop up? It clearly states to call customer service to subscribe and activate the hotspot. If you don't pay for hotspot, it won't work.... Also, if you bought the unlocked version from Best Buy.. then it is unlocked... There is no other software to flash. However, if you bought (which I'm sure you did) the Verizon version from Best Buy then it is a carried branded device, and it is unfortunately not unlocked straight from Google.
Click to expand...
Click to collapse
It's a config file security check on carriers who charge separately for the ability to tether and has nothing to do with a carrier lock - if the device is bootloader unlocked, this could be bypassed previously
georgesurgeon said:
Have you tried to install global firmware on verizon Pixel?
Click to expand...
Click to collapse
Please see prior comment
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