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!
Purchased my Pixel from local Verizon store outright cause they were sold out everywhere. I am currently using it on Cricket but have not received the 7.1.1 update. I'm wondering if I will need to insert Verizon sim card or side load every update or if Wi-Fi/Cricket will be sufficient for latest updates. My bootloader is unlocked but I am not rooted or have TWRP installed. Anybody in similar ssituations or have answers?
AndroiderM said:
Purchased my Pixel from local Verizon store outright cause they were sold out everywhere. I am currently using it on Cricket but have not received the 7.1.1 update. I'm wondering if I will need to insert Verizon sim card or side load every update or if Wi-Fi/Cricket will be sufficient for latest updates. My bootloader is unlocked but I am not rooted or have TWRP installed. Anybody in similar ssituations or have answers?
Click to expand...
Click to collapse
That is a really good question that I have not really found the answer to yet. I posted it on G+ but never really got a definitive yes or no. I have a VP with a Google Fi sim in. I didn't get the update either and just sideloaded it night before last. If you're unlocked you will have no issues sideloading or even flashing a full image for that matter. Just don't relock it.. like ever. All I can do is sideload an OTA at this point being bl locked on 7.1.1. By my choosing, btw. Here is the G+ community you might want to join.
https://plus.google.com/u/0/communities/101424233094080678997
bobby janow said:
That is a really good question that I have not really found the answer to yet. I posted it on G+ but never really got a definitive yes or no. I have a VP with a Google Fi sim in. I didn't get the update either and just sideloaded it night before last. If you're unlocked you will have no issues sideloading or even flashing a full image for that matter. Just don't relock it.. like ever. All I can do is sideload an OTA at this point being bl locked on 7.1.1. By my choosing, btw. Here is the G+ community you might want to join.
https://plus.google.com/u/0/communities/101424233094080678997
Click to expand...
Click to collapse
I was forced to pay for a month of Verizon prepaid to purchase the phone from them so I slapped my Verizon sim that still has service back in the phone. Still no update, tried with Wi-Fi on and off. I'm wondering if the update has been pushed out to everyone yet. I did get the November update when I first got the phone so who knows
I'm sure you will get the update at some point during the staged rollout. It will take a few weeks to roll out to everyone. If you can't wait install it manually.
Solved
rpjwalter said:
I'm sure you will get the update at some point during the staged rollout. It will take a few weeks to roll out to everyone. If you can't wait install it manually.
Click to expand...
Click to collapse
Just got the update with my Cricket sim in.
AndroiderM said:
Just got the update with my Cricket sim in.
Click to expand...
Click to collapse
Cool!
I have the Google store version but running on Verizon and still have 7.1 so don't fret
On BL unlocked Verizon Pixel.
I had taken the beta to android O but I decided to return to NHG47L (the May Verizon build) because O was laggy and terrible for my battery life. I did the standard procedure, removing -w from the flash-all.bat file. After it was finished, I left the phone to boot for 10-15 minutes before giving up. I tried rebooting a few times but it still didn't work. Finally I decided to try to return to the April build but I appear to still be having the same issue.
Any help getting my phone back up and running would be greatly appreciated.
FrostedWaffle said:
On BL unlocked Verizon Pixel.
I had taken the beta to android O but I decided to return to NHG47L (the May Verizon build) because O was laggy and terrible for my battery life. I did the standard procedure, removing -w from the flash-all.bat file. After it was finished, I left the phone to boot for 10-15 minutes before giving up. I tried rebooting a few times but it still didn't work. Finally I decided to try to return to the April build but I appear to still be having the same issue.
Any help getting my phone back up and running would be greatly appreciated.
Click to expand...
Click to collapse
I think Verizon images are for those using Verizon sim cards. I have a Verizon pixel without a Verizon sim and received the Google 7.1.2 version. Im not sure if it works like this. If it is like this you maybe need to install the Google factory image.
matiamb said:
I think Verizon images are for those using Verizon sim cards. I have a Verizon pixel without a Verizon sim and received the Google 7.1.2 version. Im not sure if it works like this. If it is like this you maybe need to install the Google factory image.
Click to expand...
Click to collapse
I have a verizon pixel. I ended up just using the android O factory image with the wipe and I'm back up and running again
If you just unsubscribe from the beta, it should prompt you for an update that will downgrade your phone back to 7.1.2
Solved
Used patched version of odin to flash the samsung unlocked firmware (G955U1) from the firmware servers. No more Verizon Splashscreen and spay/bixby work fine
I've been using android devices all my life and have rooted every single device I've owned in the past (probably 4-5 devices). I know the risks and I know how to flash my device and such but I got my S8+ from verizon about 3 months ago before the international unlocked version was released. I only bought it from verizon because their phones are carrier unlocked by default. I use google's project fi.
Verizon is somewhat good with bloatware I can disable or uninstall all of their applications and I haven't found my device to be slowed or burdened by their addons so I never felt the need to root my device which was nice but I got the Bixby update today and I cannot use it unless I update my system software. Tried to update it and it attempts to connect via verizon and ultimately fails saying it cannot connect to the update server. I expected this -- I think it's due to me not using verizon and not having the phone registered with their service.
Want to use Bixby and also would like to flash a stock updated (latest stock version) ROM as I don't care for any new features or custom ROMs because this phone is perfect as it is so far.
Phone software/model specs:
model is SAMSUNG-SM-G955U
kernel version 4.4.16 march 11th, 2017
sev 8.1
android 7.0
aspv march 1st, 2017
knox 2.8
If I follow my usual rooting route properly is it safe to root my phone? Asking because S8+ root is relatively new. I won't ever sell the phone so I don't care if the warranty goes void or something like that.
Essentially looking to turn my Verizon version into a completely US unlocked phone with a stock clean ROM. Is there any possible way I can perform this and still be able to use Samsung Pay? Not a necessity but I do enjoy it.
No root is out
joshclouds said:
No root is out
Click to expand...
Click to collapse
Alright, If I flash the newest version of the samsung firmware onto my device (force update it) will SPay and Bixby still work? And my Knox will be fine?
Both should be intact and working as far as my knowledge goes Bixby for sure spay shouldn't be affected. Let me get this straight you have a Verizon s8+ flashing the unlocked firmware correct?
joshclouds said:
Both should be intact and working as far as my knowledge goes Bixby for sure spay shouldn't be affected. Let me get this straight you have a Verizon s8+ flashing the unlocked firmware correct?
Click to expand...
Click to collapse
I have the S8+ G955U. It's verzion and has the ****ty verzion startup screen and sound it's just annoying. I really want to use Bixby voice as I just got the update from samsung but it says I have to have the newest samsung firmware to use it. I cannot update my phone normally because I don't use verizon I use google fi. So I want to try to flash the standard US carrier unlocked firmware onto my phone from sammobile (not the verizon variant). Is this safe?
the firmware list I'm choosing from: (spaces added so because account is not old enough to post links)
www . sammobile . com/firmwares/galaxy-s8/SM-G955U/
Which one on that list should I use? Obviously I'd choose the first one which is the Verizon firmware but I really would like to just have pure Samsung unlocked stock firmware so I don't have verizon apps & the verizon startup screen.
That's a tough decision I too have a Verizon s8 and it was plagued with the bloat and the splash screen when booting but I used a package disabler to get rid of many if the unwanted and unnecessary packages I didn't like as for using Bixby and getting rid of the splash screen.... It is safe to flash unlocked firmware many people have done this and there is a thread here on xda somewhere all about carrier switching the s8+ to the unlocked firm I could find it if you'd like?
joshclouds said:
That's a tough decision I too have a Verizon s8 and it was plagued with the bloat and the splash screen when booting but I used a package disabler to get rid of many if the unwanted and unnecessary packages I didn't like as for using Bixby and getting rid of the splash screen.... It is safe to flash unlocked firmware many people have done this and there is a thread here on xda somewhere all about carrier switching the s8+ to the unlocked firm I could find it if you'd like?
Click to expand...
Click to collapse
If you could get that thread for me that'd be perfect. Thanks for the help. Really wishing I waited the extra 3 weeks and bought the unlocked version instead.
Updating because I was able to solve it myself. I used a patched version of Odin to bypass the model mismatch error and flashed a new system image and csc (G955U1 model image) that wasn't for my G955U Verizon model.
Bixby works, KNOX is fine, SPay is solid. Verizon splash screen is gone and the phone (from the settings point of view) has no carrier and is fully unlocked and void of bloatware.
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