Hi!
I come from the Galaxy S series (S4, S5, S7) phones and I m considering of buying a Google Pixel 3
I can find many decent options, all of which are carrier unlocked
My concern with the Pixel 3 is whether I ll be able to install Android vanilla (without any carrier-related bloatware)
For all of my Samsung's so far, I could easily pick the retail ROM (well not exactly 'vanilla'!) from sammobile and load it with Odin (without breaking the knox)
Can I do something similar in the Pixel 3 or are there any security mechanisms to prevent me? (I m talking about installing original ROM - not custom..)
Bonus question - does any of you know if the Pixel 3 from Verizon and US Cellular have branding [carrier logo(s)] on the device?
Thank you in advance!
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Note10.1Dude said:
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Click to expand...
Click to collapse
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
jstoner said:
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
Click to expand...
Click to collapse
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
dcarvil said:
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
Click to expand...
Click to collapse
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
jstoner said:
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
Click to expand...
Click to collapse
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
dcarvil said:
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
Click to expand...
Click to collapse
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
jstoner said:
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
Click to expand...
Click to collapse
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
dcarvil said:
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
Click to expand...
Click to collapse
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
jstoner said:
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
Click to expand...
Click to collapse
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
dcarvil said:
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
Click to expand...
Click to collapse
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
jstoner said:
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
Click to expand...
Click to collapse
Hmmm I think the way it works is that when the phone is produced, for a specific carrier, and the carrier wants it to have a sim, it's put in at the factory. So, I think, sealed with a sim in it, possible.
I don't think us cellular uses e-sims. Double check that but it doesn't look like one of the carriers that's capable of e-sims.
cheers, good luck. I have a vzw coming today, hoping it's new and can unlock as others have... we'll know soon.
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
jstoner said:
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
Click to expand...
Click to collapse
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
dcarvil said:
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
Click to expand...
Click to collapse
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
jstoner said:
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
Click to expand...
Click to collapse
If security is a concern, you'll want to go to Android 11. 10 has not been updated since August 2020, when Android 11 came out. Also, I believe there have been camera improvements since August 2020, which would not be in the latest Android 10 build.
I have not seen any reports of stability problems with the June 2021 Android 11 update, which has the latest security patches.
I don't know if you can do an OTA update to Android 11 from Android 9. You might have to go from 9 to 10 to 11. You can flash the Android 11 image without going to 10 first.
I intend to do via flashing (whichever version I decide in the end). Not a fan of OTA
Related
I recently bought a verizon Pixel and have already unlocked the bootloader and flashed a stock image NDE63V that comes directly from google. I'm using it on T-Mobile. If I relock the bootloader at this point will everything be ok? I've read something about people saying it would brick the phone if you relock after flashing unsigned code, but the official stock images from google are signed. Will I get official updates for the unlocked google store version of the Pixel?
-edit- I decided to live dangerously, re-locked the bootloader, and now I have a completely stock google store pixel
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
brainymd said:
My understanding is it will revert back to Verizon boot loader with updates. Am I wrong in that assumption. I am in the same boat and would like convert to google stock and use on T-Mobile with OTA updates
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't think anyone knows. Right now I flashed stock google ROM through fastboot which replaced bootloader image, I am using it with T-Mobile, and I relocked bootloader. I'm going to assume it would get stock google updates.
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
I also have a Verizon version. Is there an advantage to flashing the Google version of updates as opposed to Verizon? For the moment I have an unlocked bootloader with TWRP and SuperSU installed. I tried installing an OTA update and it failed.
If I want to install one of the image updates posted (such as NDE63X from Verizon available right now) do I need to run the "flash-all" script? Could I just flash system or something else? Or should I expect it to overwrite my custom recovery and I'll have to restore that?
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
mruno said:
As of right now, I do not know of any advantages of the Google image vs Verizon's other than lack of bloatware.
I have not performed an update myself, but I think this guide should help you.
Click to expand...
Click to collapse
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
mruno said:
I just got my Verizon pixel a couple days ago. I immediately uninstalled the Verizon sim card and did not enabled wifi until after I unlocked the bootloader and installed the Google's NDE63V. I then disabled Automatic System Updates within Developer Options and sometime after I installed TWRP, root, and a custom kernel I noticed a system update was available.
It turned out to be NDE63X. From what I understand that is a Verizon only image. This makes me believe what others have been saying, Verizon IMEIs are being pushed Verizon updates.
I followed the guide here to disable any future update notifications since I will be sideloading OTAs manually.
If you relock the bootloader you may not be able to unlock it again as I am guessing a future Verizon update will block dePixel8.
Click to expand...
Click to collapse
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
ohioDroid said:
Thanks for the help, I followed the guide and installed the updates. Unfortunately I did not get any new gestures available (Lift to Wake or Double Tap) as I had hoped... either those are not in the Nov 2016 Verizon system.img, or they are an app update I haven't received yet.
Click to expand...
Click to collapse
If the gestures were not in that update, they should be soon in an upcoming OTA according to reports. I am currently using the double-tap gesture with the ElementalX kernel (enabled within its app).
Edit: I think this app can enable lift to wake. I bookmarked it after finding a post about it here until I read Google will be adding this feature soon.
fink.nottle said:
Yes, they may block it in the future, but can't you always flash the November image (since it's signed), and dePixel8 again ? Do updates have the ability to change the trusted key or prevent flashing an older image ? I'm guessing yes, since that's what Lenovo does for its BIOS, but I haven't looked at Android that closely.
Click to expand...
Click to collapse
I am not sure as I haven't had a nexus device since the Samsung Galaxy Nexus on Verizon .
On a lot of their devices Verizon likes to update bootloaders to only accept new updates. It's likely that if they patch out the ability to use dePixel8 in a future update, they will prevent people from flashing older builds. C'Est la Vie I guess
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
aholeinthewor1d said:
Just got my pixel yesterday but still using my s5 for now. I've gone from a droid x - GS 3 - GS4 - GS5. Development for each of those phones seemed really good. I was always jealous of other devices who's bootloaders were unlockable right away because of the crazy amount of development for them (Nexus). Most of the reason I got the Pixel was because I thought it would be just like the Nexus devices as far as development goes but so far it doesn't seem like it's going that way. I know it's somewhat new but just curious if people think it's going to pick up?
Click to expand...
Click to collapse
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
tobalaz said:
Just got my Pixel 2 days ago through Verizon, had it shipped to me instead of getting it at the store.
I did an initial charge and then set up the phone, during setup, it allowed me to choose which Google and Verizon apps were being installed.
I don't get any Verizon screens, just the Google boot animation. There isn't even a Verizon logo on the phone. I don't even see anything Verizon unlit after the SIM is detected.
I was wondering if anyone else that got their Pixel through Verizon has carrier markings or bloat on it? And if it does, did you go 32gb or 128gb and did you get yours via mail or from the store?
Click to expand...
Click to collapse
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
jmartin72 said:
Yes, it will most definitely pick up. The Partitions are different than any other phone, and as soon as we have a stable TWRP then the custom ROM's will pour in. Just give it some time, and be happy with stock for now. Good times are coming, and I'm looking forward to using this phone for the next two years.
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
The only Verizon bloat that comes is three apps that can be uninstalled. other than that, there is no Verizon logo anywhere.
Click to expand...
Click to collapse
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I bought my Verizon Pixel yesterday. Unlocked in 20 seconds and within a few minutes TWRP 3.0.2-0 for sailfish is installed and SuperSU 2.78-SR5 has been flashed. Works perfect.
aholeinthewor1d said:
Thanks for the reply! I've unlocked bootloader already but haven't rooted or anything yet. Been busy so I need some time to read through the Pixel forums more. I do remember seeing mention of something with the partitions on the Pixel causing issues with TWRP. Do you have a link by any chance or something that explains what is going on with it and how the partitions are different? Just want to read up on it. Been with my s5 for soooo long so coming to a new device basically means starting over and learning lots of new stuff. Software versions, unlocking, rooting, etc
Click to expand...
Click to collapse
I feel your pain! I'm also coming from the S5 for 2.5 years. Had everything (almost) perfect with systemless root, twrp, xposed, adaway, etc. (but no Android Pay) . Now with this Pixel and Verizon-depixel8 unlocked bootloader, I'm trying to piece together the best plan for having the most stuff working.
So far, bootloader unlocked, and I flashed the full 7.1.1 images from Google. Then I tried using the setup wizard and it brought over my account info and wifi passwords and such from my S5 by directly connecting the phones, and it downloaded my apps from google play, but I need app-data.
So, now I'm thinking this would be the process if you want to have a rooted pixel, and be able to reboot into a "clean" boot for Android Pay?:
1) boot TWRP alpha2 (since RC1 having problem rooting?)
2) install TWRP alpha2 zip
3) install stock-safetynet kernal to boot_a
4) boot into boot_a
5) setup Android pay, add credit cards, etc.
6) boot into TWRP and install root with SR5 to boot_b
7) boot into boot_b and restore other app backups with Titanium Backup, install Adaway/hosts
8) no Xprivacy /Xposed available yet, right?
9) restore backed up apps from old phone with Titanium Backup (from cloud, etc.)
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
bobhinkle said:
I have one question with this, I have a Verizon pixel with unlocked bootloader. I just wanted to make sure I can flash the Google image and still use on Verizon. Will I lose any features like the advanced calling stuff?
Sent from my Pixel using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes you can still use it on Verizon. Advanced Calling is a feature i am not too familiar with. Is that HD Calling? If so then yes that will work as well works on my phone without issue.
So from here I can flash Google's bootloader and Google image and then when updates come out just use the Google ones
Sent from my Pixel using XDA-Developers mobile app
Question for those with a Play store version of the Pixel: what is your bootloader version on the 7.1.1 software?
For reference my Verizon store Pixel has BL version 8996-12001-1610061102.
Thanks in advance!
I'm considering buying a used Google Pixel that was purchased via Verizon. Through researching, it sounds like I should be able to just pop in my AT&T SIM and it should work. Is this correct?
What I don't want is a phone that has Verizon bloatware installed and delayed updates. Will I be able to install non-Verizon factory images? I see There multiple 7.1.2 factory images listed at https://developers.google.com/android/images for the Pixel. (N2G47O, May 2017) and (NHG47L, May 2017, Verizon). Will I be able to install the N2G47O version or would I be stuck installing the Verizon branded version.
Thanks for any help.
Also with the same question
Enviado desde mi Redmi Note 3 mediante Tapatalk
beand1p said:
I'm considering buying a used Google Pixel that was purchased via Verizon. Through researching, it sounds like I should be able to just pop in my AT&T SIM and it should work. Is this correct?
What I don't want is a phone that has Verizon bloatware installed and delayed updates. Will I be able to install non-Verizon factory images? I see There multiple 7.1.2 factory images listed at https://developers.google.com/android/images for the Pixel. (N2G47O, May 2017) and (NHG47L, May 2017, Verizon). Will I be able to install the N2G47O version or would I be stuck installing the Verizon branded version.
Thanks for any help.
Click to expand...
Click to collapse
I just recently picked up a google pixel , I traded a galaxy s7 edge for it. The google pixel was originally verizon, I just popped in my tmobile sim card and it was good to go. The only set back is if you want to unlock the bootloader, from reading various forums its possible IF the phone is on 7.1. Apparently if you upgrade with a non verizon sim or over wifi itll allow you the option to unlock the bootloader. You can uninstall all verizon apps, as for the image you are probably stuck on the verizon one for the time being till an unlock for a bootloader comes out. People have reported contacting google and being able to rma their verizon phone for a non verizon one to unlock the bootloader.
Hello, I'm new here.
I purchased a used AT&T Kyocera Duraforce Pro (E6820), and I use T-Mobile. It's the exact same hardware as the T-Mobile version, just a different ROM*, and the T-Mobile one has a few customizations that sound worthwhile as a TMO customer. Anyone have any ideas how I could acquire and flash the T-Mobile ROM?
*(as per Kyocera's website - the page where they post GPL sources e.g. kernel - and the carriers' pages, the ROMs are E6820 6.0.1 (1.802TC) vs E6820 6.0.1 (3.030AT))
If you haven't updated it (software version 1.015AT), then we're both in luck. If it's on anything newer than 1.017AT there's no way for me to do what's necessary to determine/enable crossflashing or downgrading between versions or, in your case, simply enable radio bands 12, 66 & 71... although you could try asking AT&T for the carrier unlock code, which will probably allow at least partial functionality w/a T-Mobile SIM. I might be able to determine the code for your device myself otherwise, but I'll need details you'll have to get from files you can only hopefully access without root, as those kernel sources are mostly useless as far as providing the information needed & nobody gives af about this phone, aside from the handful of people who have posted on here about it that at best don't seem to get what (short of leaked engineering files) it takes to modify something this locked down & recent. In short, "no." E6810 is the only one with consumer flash restore, E6830/E6833 is the only one with provider available OEM service flash ability, and E6820 (your version, if it's an earlier one) is the only one that shipped with firmware which isn't too recently patched to get root without using a yet published exploit or methods that first require files nobody but factory techs & provider/OEM engineers have, or at the very least what you might well be holding (if older & not updated) plus a lot of work & luck on my part or probably eventually some 14yo in Russia, but so far I don't think anyone's even managed to get temporal root on it aside from myself & while you could technically, maybe, hot-flash from that, if it still works on newer builds, it's unstable & there's no image for you to flash unless I can get recovery imageloading over usb or from SD working enough someone can dump one. The only image available is 5.420VZ & that won't flash on anything but E6810 because, if nothing else, you can't get it to where it'll enter the mode to receive it & do so. Likewise, I don't have the Sprint service utility, but it won't work on anything other than E6830/E6833, so I don't even know what means is used on E6820 at all w/o looking at files contained in areas completely inaccessible without root. I might, however be able to get that information from the OTA update file or just get root, depending on your current version
Diactoros said:
Hello, I'm new here.
I purchased a used AT&T Kyocera Duraforce Pro (E6820), and I use T-Mobile. It's the exact same hardware as the T-Mobile version, just a different ROM*, and the T-Mobile one has a few customizations that sound worthwhile as a TMO customer. Anyone have any ideas how I could acquire and flash the T-Mobile ROM?
*(as per Kyocera's website - the page where they post GPL sources e.g. kernel - and the carriers' pages, the ROMs are E6820 6.0.1 (1.802TC) vs E6820 6.0.1 (3.030AT))
Click to expand...
Click to collapse
Did you find a way?
chikosneff said:
Did you find a way?
Click to expand...
Click to collapse
Unfortunately, no. It works on T-mobile with the AT&T ROM, but wifi calling doesn't work, which is really a problem. I'd still be glad of any insight anyone could provide.
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Dishe said:
There's been a lot of new users picking up cheap G7 ThinQ G710ULM (US Unlocked) versions on ebay lately, then getting frustrated when they find out it a hacked Sprint version (G710pm).
I'm finding posts from new users on different corners of the internet, Telegram groups, Reddit, etc, usually saying that they can't upgrade from Oreo and their device is missing a serial number, and the IMEI is actually from the Sprint pm version. I couldn't find a lot of info in one place about these handsets, so I'm starting this thread to discuss them. There's a good chance any ULM on ebay for a good price is one of these. I bought 3 of them for different people from different sellers, and this was the case on all of them. I almost returned them all and gave up until I did some research and found out THIS ISN'T NECESSARILY A BAD THING!
In fact, it may actually be beneficial compared to the real ULM version in some ways. First of all, it WILL work with T-mobile USA just fine. The bands all seem to work, it even supports WiFi calling and VOLTE, and there's a chance even B71 will work (although this isn't 100% verified, it shows up as an available band to test in the service menu). The real ULM supposedly skips this band. Some people even say the real ULM version is also missing bands for AT&T, but the PM crossflashed version seems to connect to them (this might be an isolated incident or fluke, but at least one redditor claims this was his experience). I'm still not clear on how the unlocked official US version can be missing AT&T bands, so I'd love for other people to maybe chime in here with their experiences.
Yes, you can update to Pie. The OTA updates won't work, likely because of the missing serial number. On that note, I'd LOVE to find out why that is. Can anyone explain why these crossflashed devices are missing the SN? Does that happen on other crossflashed devices?
Either way, follow this guide here:
https://forum.xda-developers.com/lg...how-to-install-pie-stock-treble-aosp-t3914079
Note, this guide was written for flashing a European variant, but the same steps apply. Just choose a kdz for the ULM variant from here: https://lg-firmwares.com/lg-lmg710ulm-firmwares/#tab=firmwares
^ I recommend the latest Google Fi firmware version, which is G710ULM20e_00_NAO_US_OP_1010.kdz , from 2019-11-14
There is a more recent version from BPT, but it is unclear what that firmware is for. BPT seems to be some sort of regional carrier, so you are better off with the regular USA or Fi version.
Also note, you may need to use 7zip to extract the dll file from that guide. That took me a while to figure out, as Windows explorer throws an error with it. Once you finish, your phone will reboot with a shiny new (relatively) up to date Pie firmware!
There. You now saved yourself a few bucks and got a solid phone. Feel free to share your experiences with the handset here.
Click to expand...
Click to collapse
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
loonycgb2 said:
The devices lose the s/n and possibly imei because people are flashing using lgup 1.14 dev version which causes issues with nvdata.
Click to expand...
Click to collapse
Wow, that's some good info right there, thank you for sharing!
Hmm- messing with nvdata though? So you're saying the SN missing is some sort of accident or goof? That doesn't sound so cool. Should I be concerned anything else is messed up? There's a ton of these in the wild now and it seems the SN is the only weird side effect that has been noticed.
As far as I know the IMEI is fine (looking it up reveals it is a PM imei, which is correct, and it does work with voice over Wifi and VOLTE, which I think wouldn't work if the IMEI was messed up). In fact, it's interesting because when that screen loads in Settings>About, etc, it shows "checking" under S/N, then checking goes away and it comes back blank. None of the other fields seem to need any sort of checking first. There's something fishy about how the S/N is stored that it has to check it first and then error out.
Lgup 1.15 fixes this when you go back to oreo then update to pie.
Click to expand...
Click to collapse
Hmm. It came with Oreo, and I used 1.15 to flash to Pie. So you're saying I should flash another Oreo kdz with my LGUP and it will magically fix any corrupt NVdata?
Also crossflashed devices do not get ota because lgup marks these devices as crossflashed in nvdata using a 0x01 value for certified_device
Click to expand...
Click to collapse
Oh, that is unfortunate. And that value stays with it forever, even if you go back to it's native firmware? I'm assuming that value can't be manipulated with any of the tools we have available.
Thank you so much for sharing this knowledge. Any insight on how the bands work? Is that from nvdata as well, and completely independent of firmware? So essentially, I have whatever band support a G710pm has? Or perhaps was it manipulated by the seller/refurbisher, who possibly used some nvram voodoo tricks which killed the S/N as a result?
Even tho the s/n is blank and at time if you try to show the imei it might also be blank, it is still stored internally and not lost forever.
There is multiple oreo's which for ulm is 10g and 11g, but i would have said flash to the original firmware but you cannot as sprint kdz is not available and the people who have an Original firmware still on device cannot or will not back it up for us.
The value for certified device returns to normal when flashed to the original firmware as lgup has an internal database used for identifying models.
As far as the basebands, all g7 thinq's come with the same bands no matter the firmware or region. The difference is the kdz gives band priority to the ones prefered by the carrier.
All of that can be changed by getting into the lg data secret menu or the dialer code menu
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
netookska05 said:
Remember now bootloader and root for the LG g7 is just the beginning. You talk about nvdata you might as well throw out EFS backup as well.
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
I prefer the manual backup using adb shell you can do it with terminal emulator as well.
Qfil is very powerful for Qualcomm devices and we'll figure out how to make back ups of all partitions that involve serial numbers and IMEI ( nvdata and efs).
Just wait you'll see.
Click to expand...
Click to collapse
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
netookska05 said:
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly. For our devices TWRP is barely universal. People selling crossflashed phones know this which is why they sell them.
Click to expand...
Click to collapse
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
loonycgb2 said:
Thats already been possible since day 1, use qpst with your msl code to backup qcn with imei and s/n.
Click to expand...
Click to collapse
Can you please elaborate for those unfamiliar with this?
Dishe said:
I don't understand. What does twrp have to do with any of this? My bootloader is locked and the stock recovery is still there. The devices are likely just flashed with LGup as is, and that doesn't seem to have effected much outside of a missing SN.
Are you saying that my cross flashed phone would effect things if I tried to root somehow? Or am I missing the point here?
Can you please elaborate for those unfamiliar with this?
Click to expand...
Click to collapse
Using TWRP to create a backup of efs. Sometimes the restore is faulty.
EFS partition holds up the unique IMEI number of the device, also other identifying numbers like MAC address, MEID, and ESN are stored up in this partition.
Check you IMEI with this.
https://imeipro.info/check_lg.html
To get your sn.
Oh ok.
So I don't actually need to know my SN but I'd like it to not be blank if flashing back to a previous version would restore it... Especially if there are possibly other parts of nvram that may be corrupt that I'm unaware of?
Thanks for the info. The one I got said it can't work on Sprint or Verizon networks, and is missing the serial #, as you said.
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
vishal198900 said:
I got just one from bay with S/N missing and software version G710ULM10g. Latest patch level Sep 1, 2018 (Android 8.0.0). Is there any way to install Android 10 based ROM?
Assuming that after following the steps (Part 1 only) (hope we can skip part 2?) to somehow install G710ULM20e_00_NAO_US_OP_1010 (Android 9), is there a way to follow similar steps after part-1 to update it to Android 10 based ROM?
It would be great if someone can help to install Android 10 directly from Android 8.0 (without the need to installing Android 9). I am not sure if its even possible to get Android 10 on such bay unlocked devices without S/N.
Click to expand...
Click to collapse
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
I just got a 710pm off ebay. I unlocked the bootloader, crossflashed to ulm pie, and rooted. It works just fine. [emoji106]
Sent from my LM-G710 using Tapatalk
netookska05 said:
If you must know the serial number there is a one site that you enter imei and it'll tell you what it is. Just gotta search on Google.
Serial number is lost when bootloader is unlocked. You can regain it if you relock and go back to stock. Not sure what version of g7 you have. More likely it's probably crossflashed and sold like that so there won't be a kdz to go back to stock.
Click to expand...
Click to collapse
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
netookska05 said:
Android 10 has a thread they tell you what kdz to crossflash too and how to update to android 10 with the activity launcher app.
Click to expand...
Click to collapse
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
vishal198900 said:
I don't know if there's much use of serial number. Isn't it better to have unlocked bootloader?
Can you please help me with the correct thread post for crossflashed devices like mine bought through ebay? I appreciate your help.
Click to expand...
Click to collapse
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
netookska05 said:
Here's the crossflashing thread using command line lgup.
Thread: https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
There's another lgup dualmode you can use the partion dl option to install the Korean kdz that Android 10 uses. Search for that.
To install the Android 10 LGUP_FOTA.up update which you use activity launcher to install.
Thread:
https://forum.xda-developers.com/lg-g7-thinq/how-to/android-10-beta-lg-g7-g710n-t4059483
Click to expand...
Click to collapse
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
vishal198900 said:
Thanks. My phone (G710PM) is cross-flashed with G710ULM firmware Android 8. Please suggest is below plan will work?
1) First update existing firmware to stock Android 9.0 i.e. G710ULM20e_00_NAO_US_OP_1010 using these steps.
2) Then install Lineage OS 17.1 (based on Android 10) because it needs stock Android 9.0 as a pre-requisite using these steps.
Click to expand...
Click to collapse
Yes it will work.
I'd also like to add that Google Pay will not work, at retail brick and mortar stores.
A pop up says device may be rooted or modified.
I have magisk installed and it seems to trick Schwab banking app.
Edit:
Edit: I followed the instruction from the following video, and was able to get GPay to accept the card. Also Gpay needs to be manually hidden in magisk, be sure to select 'display system apps' to find it.
https://www.youtube.com/watch?v=wKYC0r-m0Mo
Click to expand...
Click to collapse
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
captain barbosa said:
I am not an expert but I just bought one of these Ebay phones. It has Pie but what would like to know is how can I get the security updates? Or is that not possible? Please help. Thanks in advance.
Click to expand...
Click to collapse
If you're on Pie, I doubt you have one of these Sprint phones. Check if you pass SafetyNet and if so, you have a native ULM model. Most G7 variants receive very few updates (including the ULM).
Hey all,
I bought a new OnePlus 8 5g T-mobile phone for my wife. She's on the RedPocket annual GMSA/ATT plan. I've stopped the auto OO11 update and I've gone into *#*#4636#*#* and selected "LTE Only" for the connection type (like I did with my old OP6) but it doesn't stick after a reboot.
My real question is:
Since 4G LTE seems to work properly with the T-Mobile stock OS, what are the reasons for converting over to the international version?
Will 4G still work after I update it to OO11.x? I don't mind it having the T-Mobile boot or bloat. I have mostly disabled/uninstalled the apps she doesn't need.
Thanks!!!
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware, and even if you don't really "care" about it, every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
FoxyDrew said:
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware. And even if you don't really "care" every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
Click to expand...
Click to collapse
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
chuddler said:
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
Click to expand...
Click to collapse
np man, that guide is very complicated for no reason, converting to global is rather simple, but it's a 3 step process. This all assumes you can unlock your bootloader though.
1.) MSM back to stock T-Mobile Android 10 firmware. Specifically this one. This will re-lock your BL if its unlocked.
2.) Let that boot up, go into settings to enable OEM unlocking, and then unlock the bootloader.
3.) Once the bootloader is unlocked, flash THIS global Android 10 ROM via fastboot. There's a flash-all.bat file to make it simple. Once you've finished this step your essentially done, and on global firmware, you just need to...
4.) Boot the phone up and take the OTA update in settings to Android 11. There will be 2 OTAs to take, one FULL OTA to Android 11, than an incremental one to the latest Android 11 build
Optionally afterwards you can re-lock your bootloader, or keep it unlocked and root if that's what you/she wants.
If you're not familiar with MSM tool, and the drivers it needs, check out this thread.