VZW apps on my phone? - Google Pixel 2 Questions & Answers

This may be a silly question but I hope someone can answer for me.
I am currently living in Thailand and picked up a Pixel 2 not too long ago. I got the OTA up to January while my phone was still stock/unrooted with my Thai Sim card. I then unlocked the bootloader rooted Magisk etc... At one point I flashed the stock image from google (not the UK or verizon variants) as I wanted to go back to stock.
I then updated to the February update by flashing the factory image without the -w to prevent wiping. Currently on OPM1.171019.019
Just earlier today I was snooping around and found the following installed but disabled:
My Module: com.vzw.apnlib
Retail Demo Mode: com.customermobile.preload.vzw
Vzw OMA Trigger: com.android.vzwomatrigger
vzw_msdc_api: qualcomm.com.vzw_msdc_api
VZW_Multicast_MW: com.qualcomm.ltebc_vzw
My question is, are these Verizon services baked into the stock image files? A Verizon had never been in the phone, as far as I know.
Thank you kindly

I know that this post is a few months old, but I was just searching for the same answer to this question regarding my phone. I am currently seeing these on my T-Mobile branded Snapdragon Note 8. If anyone out there might be able to help answer?

I think this thread and this thread are related.
For some reason there's a cross over between what the VZW and Google should be. It must have something to do with the partnership between them.
I just had the issue of VZW potentially (NOT confirmed) locking my boot loader...

Also on my Sprint G965U

same thing with me on a us cellular s8 that i bought brand new in store. I found a verizon service agreement in my network config. i called and questioned them about it, i asked what their affiliation with vzw was , they said they had none unless it was above their paygrade. they ended up telling me the phones are programmed for multi carriers from the manufact then the acutual carrier will optimize them which leaves pretty much dead files that cant be rewmoved. use activity launcher you dont need root and you can access almost every file in a readable state and also control tons of **** that is in your phone but cant access. i cant believe all the settings that you would never know about. anyway getting off track. back to vzw, i first thought vzw files on a new us cellular device meant maybe it was rerfurbished and they lied, i wish , bye bye contract lol. i think this could be made into a big deal, possible void a contract , going to go to the store and see what they think, i know they wont have a clue. thats what im hoping because ill easily take an s10+ and not pursue it any further haha

taldavid2 said:
This may be a silly question but I hope someone can answer for me.
I am currently living in Thailand and picked up a Pixel 2 not too long ago. I got the OTA up to January while my phone was still stock/unrooted with my Thai Sim card. I then unlocked the bootloader rooted Magisk etc... At one point I flashed the stock image from google (not the UK or verizon variants) as I wanted to go back to stock.
I then updated to the February update by flashing the factory image without the -w to prevent wiping. Currently on OPM1.171019.019
Just earlier today I was snooping around and found the following installed but disabled:
My Module: com.vzw.apnlib
Retail Demo Mode: com.customermobile.preload.vzw
Vzw OMA Trigger: com.android.vzwomatrigger
vzw_msdc_api: qualcomm.com.vzw_msdc_api
VZW_Multicast_MW: com.qualcomm.ltebc_vzw
My question is, are these Verizon services baked into the stock image files? A Verizon had never been in the phone, as far as I know.
Thank you kindly
Click to expand...
Click to collapse
it all comes down to business. those apps are preinstalled, yes, baked in? yes and no. they have read only permissions but are not an integral part of the system and can be removed. some users report having trouble using verizon apps with their verizon service after uninstalling com.vzw.apnlib i'm sorry you didn't get an answer sooner, but these things happen.

Related

Verizon Phones will get os updates the same day as google unlocked pixels

FYI
http://www.droid-life.com/2016/10/12/verizon-pixel-xl-updates-google-same-time/
http://www.theverge.com/circuitbreaker/2016/10/12/13258286/verizon-google-pixel-fast-android-updates
Google also confirmed this.
From Ars
Update 2: Google agrees! The company told Ars "OS updates and monthly security patches will be updated on all Pixel devices (Verizon and non-Verizon versions) simultaneously."
Bootloader still won't be unlockable, but this is a step in the right direction.
Frankly, if software is updated quickly along with Google it makes an unlockable bootloader less important to a lot of people.
Verizon has a mixed past with this and Google. They screwed up the Galaxy Nexus but did OK with the Nexus 6.
I'm still happy to buy from Google since I see the ability to unlock the bootloader as insurance against Verizon changing it's mind a year down the road when everyone is paying attention to something new.
atlp99 said:
Frankly, if software is updated quickly along with Google it makes an unlockable bootloader less important to a lot of people.
Verizon has a mixed past with this and Google. They screwed up the Galaxy Nexus but did OK with the Nexus 6.
I'm still happy to buy from Google since I see the ability to unlock the bootloader as insurance against Verizon changing it's mind a year down the road when everyone is paying attention to something new.
Click to expand...
Click to collapse
So, with a locked bootloader, there's absolutely no way to flash the Google stock image over it, correct?
Let's say down the road someone figures out a way to root the device and unlock the one sold by VZW. Theoretically, couldn't we then flash the factory stock Google firmware, effectively turning it into the same model as the Google Store one? Then we wouldn't have to worry about VZW pushing updates that would relock it if we flashed those? Of course I know one wouldn't take an OTA on a rooted, unlocked phone, but if you had to return to stock...you could go straight to Google's firmware.
If the VZW phones are going to get updates pushed straight from Google, then those images would have to be different from all the other Google updates, right? They would have to include the VZW bootloaders...would there be a way to inject the Google Unlockable bootloader into that OTA and then flash that?
Jank4AU said:
So, with a locked bootloader, there's absolutely no way to flash the Google stock image over it, correct?
Let's say down the road someone figures out a way to root the device and unlock the one sold by VZW. Theoretically, couldn't we then flash the factory stock Google firmware, effectively turning it into the same model as the Google Store one? Then we wouldn't have to worry about VZW pushing updates that would relock it if we flashed those? Of course I know one wouldn't take an OTA on a rooted, unlocked phone, but if you had to return to stock...you could go straight to Google's firmware.
If the VZW phones are going to get updates pushed straight from Google, then those images would have to be different from all the other Google updates, right? They would have to include the VZW bootloaders...would there be a way to inject the Google Unlockable bootloader into that OTA and then flash that?
Click to expand...
Click to collapse
Assuming that we only have one US version (which I think has been confirmed), and the fact that verizon bloat gets installed on first boot with sim card activation, I want to say that the phones are the same. Maybe the only difference between the google phone and the verizon phone is the "oem unlock" toggle will not work on the verizon phones. Or maybe they will have different bootloaders. Then there would be multiple firmware images, one for verizon, one unlocked. If you could get root, then you could possibly get an ota for an unlocked phone and install it, thus replacing the verizon bootloader (if it is in fact different). I am growing more and more skeptical that there is any difference at all between the verizon and google phones. I wonder if this is all going to fizzle out in a week when everyone gets their phones.
I have 1 on preorder from google and an upgrade preorder from Verizon right now. I'm torn on which one to go with because I will save a good bit of money by going through Verizon. All I really want to do is root, so I "might" be worried for no reason. Time will tell.
Yeah, I canceled my order through the Google Play store to get it through VZW on my company account once I learned Big Red wasn't holding up the updates. Ultimately, I may be okay with the locked bootloader as I'm getting older and have 3 kids. I don't have to time to mess with android like I used to. :crying:
---------- Post added at 01:19 PM ---------- Previous post was at 12:42 PM ----------
dbrohrer said:
Assuming that we only have one US version (which I think has been confirmed), and the fact that verizon bloat gets installed on first boot with sim card activation, I want to say that the phones are the same. Maybe the only difference between the google phone and the verizon phone is the "oem unlock" toggle will not work on the verizon phones. Or maybe they will have different bootloaders. Then there would be multiple firmware images, one for verizon, one unlocked. If you could get root, then you could possibly get an ota for an unlocked phone and install it, thus replacing the verizon bootloader (if it is in fact different). I am growing more and more skeptical that there is any difference at all between the verizon and google phones. I wonder if this is all going to fizzle out in a week when everyone gets their phones.
I have 1 on preorder from google and an upgrade preorder from Verizon right now. I'm torn on which one to go with because I will save a good bit of money by going through Verizon. All I really want to do is root, so I "might" be worried for no reason. Time will tell.
Click to expand...
Click to collapse
If this phone is truly carrier unlocked, if you paid for it outright at Best Buy or where ever you decided to get it and took it to another carrier, how would future updates work? Maybe the Google store phones IMEI's are all stored as the unlocked bootloader batch and get updates from set A, while all other IMEI's get updates from set B to maintain the unlockable bootloader. If I'm on AT&T, with a phone purchased from any store other than Google, what's to keep that phone from getting the same Google update as the ones bought from the Play Store? I'm sure hoping there will be a way to flash the stock Google image over the top of the VZW phones, that would be ideal.
Jank4AU said:
If this phone is truly carrier unlocked, if you paid for it outright at Best Buy or where ever you decided to get it and took it to another carrier, how would future updates work? Maybe the Google store phones IMEI's are all stored as the unlocked bootloader batch and get updates from set A, while all other IMEI's get updates from set B to maintain the unlockable bootloader. If I'm on AT&T, with a phone purchased from any store other than Google, what's to keep that phone from getting the same Google update as the ones bought from the Play Store? I'm sure hoping there will be a way to flash the stock Google image over the top of the VZW phones, that would be ideal.
Click to expand...
Click to collapse
Good point. If 2 separate firmware images are in circulation, Google has to give you the ability to get updates after you leave Verizon (I hope...). The more I think about it, the more I believe that there isn't going to be any difference. Fingers crossed that evleaks and every android blog site blew this way out of proportion.
Nexus 6 was sold by Verizon and was identical to the google play store phone. Bootloader could be unlocked and any factory image could be flashed on it.
The Nexus 6 was basically this way. Verizon kept their hands off it except for the branding on the back of the phone body. If they treat the pixels the same as the Nexus 6, there is little to no reason to buy straight from Google if you want to buy from Verizon.
The only difference for me is that i would have been able to spread out payment on my bill if I went through Verizon. Buying through Google meant that I had to pay for it up front.
For me, avoiding the possibility of an non unlockable bootloader was worth paying up front for.

Can I root my Samsung S7 and gert rid of "all things ATT"..?

So, I'll apologize if this has already been dealt with previously, but I just need to verify what I've been told by a friend who knows Android systems (and Samsung S7 phones) a LOT more than I will ever attempt to understand..
About a year ago, I bought a Samsung Galaxy S7 from a 'rebuilder' (my term) who mentioned at the time "... it was ATT phone..", and, yes, when I turn it on it does the ATT circle jerk logo and has an ATT logo on the back of the phone. This was of no real concern to me, because my service purveyor uses the ATT system (Consumer Cellular), so it's worked well enough. But unfortunately, it also has a boatload of 'semi-proprietary' ATT trash in the phone which I'd like to get rid of. To confuse the matter even more, it appears that I cannot 'unlock' the phone because it has not been associated with an actual active ATT account for close to two years, and it APPEARS that now they refuse to accommodate an unlock code for this phone.
So... according to my friend (Mr. Android Phone), I can 'root' this phone to 'factory original firmware' and make it (in essence) just a plain-old-vanilla Samsung S7 without this rather bogus ATT firmware and the myriad of craplets I'd like to get rid of..
So, I'm here looking for "expertise" in such things because I certainly don't want to 'brick' this pretty nice phone, but I also want to get this to a point where there is no association with ATT in any manner. So my question sorta comes down to: "can I root this and be rid of all things ATT?", and "will this allow me to achieve an 'unlock' without having to play ATT's games? (I had QUITE the discussion with an ATT 'support' dude a couple of hours ago when he flatly refused to give me an unlock code so I could simply ATTEMPT to see if Consumer Cellular's T-Mobile service might work better at my home, since CC tells me I'm right in the center of a brand new rebuilt 4G service area).
Does any of this make any sense to anyone? Pardon my ignorance, but if the IMEI # is somehow 'tethered' to ATT and they won't "release" it, how does rooting help with this? - or is this something more like an 'association' of the IMEI # AND the ATT firmware...? GAH!! I'd just like to be totally rid of all this ATT junk and have the freedom to choose whichever service I want.
CentennialMan said:
So, I'll apologize if this has already been dealt with previously, but I just need to verify what I've been told by a friend who knows Android systems (and Samsung S7 phones) a LOT more than I will ever attempt to understand..
I'd just like to be totally rid of all this ATT junk and have the freedom to choose whichever service I want.
Click to expand...
Click to collapse
Hi There that's a lot of words partner! I'll try make the answer easy to understand and I've cut out much of the post so my reply isn't huge.
1. Yes you can install vanilla firmware which will remove all branding from AT&T and you don't need to root the phone to do this. here is the firmware for your device >>here<< You can also use XAS or XAA. You will see the guide and the Odin you need to flash this firmware.
2. This is another version of Odin on this website if you have any issues with the one on Sammobile. >>here<<
3. Unfortunately you cannot unlock the phone unless the original cell phone provider gives you their half of the unlock key as a code to input to the phone. In the UK once a phone is out of the initial contract period it is illegal for the provider to refuse to give you this code whether your still with them or not. I know in the USA you guys gets ****ed over. The original account holder of the phone can ask for the unlock code but not you.
4. Changing the firmware and unlocking the phone to any network are two different things, flashing unbranded firmware will not unlock the phone the network is tied to. They don't make it that easy!
5. As far as i know T Mobile (USA) has also moved to G930U firmware so you could be lucky with a T Mobile SIM working once the phone is flashed with this firmware but don't hold your breath. Check Sammobile for the T Mobile firmware too.
6. IMEI number is tied to the phone so in theory it can be changed after the phone is rooted and you are able to modify the EFS partition but it is extremely difficult even for veterans like me and it causes lots of problems with cell network registration. Leave well alone if you don't want a completely useless device.
Things to make flashing go easier
1. Turn off FRP lock or sign out of the Google account on the phone or delete it before you do anything, you can put that account back on the phone after flashing.
2. If you enable Developer options make sure " usb debugging" is enabled and OEM unlock, not essential but can help when things go wrong.
3. Anything you want to keep, pics media etc back up or move to SD card, the SD card won't be touched when flashing firmware.
4. Please follow the guides on how to flash correctly.
Any other questions please ask.
It should be noted that if it's an ATT phone it's Snapdragon therefore permanently bootloader locked, OEM Unlock won't actually do anything, that setting only works on Exynos.
The only root method for Snapdragon is to use a leaked engineering bootloader to gain system access, and you can only install the leaked bootloader if your phone is already running old firmware. For up to date phones there is no root method.
Beanvee7 said:
It should be noted that if it's an ATT phone it's Snapdragon therefore permanently bootloader locked, OEM Unlock won't actually do anything, that setting only works on Exynos.
The only root method for Snapdragon is to use a leaked engineering bootloader to gain system access, and you can only install the leaked bootloader if your phone is already running old firmware. For up to date phones there is no root method.
Click to expand...
Click to collapse
Hello mate i'm not sure if your aware but AT&T were initially Qual comm but they've also been using Exynos for a while.
cooltt said:
Hello mate i'm not sure if your aware but AT&T were initially Qual comm but they've also been using Exynos for a while.
Click to expand...
Click to collapse
Source?
Beanvee7 said:
Source?
Click to expand...
Click to collapse
Don't be smart you know how to use Google?
I did google it, I wouldn't have asked for a source if I found something. But it doesn't matter, you're the one making unsubstantiated claims, the burden is on you to prove it. But since you asked for it:
AT&T's website says Snapdragon
https://i.imgur.com/TdV62Mq.jpg
https://www.att.com/buy/phones/samsung-galaxy-s7-32gb-black-onyx.html
GSM Arena says Snapdragon
https://www.gsmarena.com/samsung_galaxy_s7_(usa)-7960.php
Wikipedia says Snapdragon
https://en.wikipedia.org/wiki/Samsung_Galaxy_S7#Qualcomm_Snapdragon_820_Models
There isn't a single page when googling AT&T S7 Exynos that backs your claim up. The USA also uses completely different network technology than internationally, using the S7 Exynos in the USA is already known to cause issues with LTE, VoWiFi etc. They'd have to do a hardware refresh of the Exynos SoC if they wanted to support it in the USA, which they ain't going to do a for a 3 gen old phone.
Beanvee7 said:
I did google it, I wouldn't have asked for a source if I found something. But it doesn't matter, you're the one making unsubstantiated claims, the burden is on you to prove it. But since you asked for it:
AT&T's website says Snapdragon
https://i.imgur.com/TdV62Mq.jpg
https://www.att.com/buy/phones/samsung-galaxy-s7-32gb-black-onyx.html
GSM Arena says Snapdragon
https://www.gsmarena.com/samsung_galaxy_s7_(usa)-7960.php
Wikipedia says Snapdragon
https://en.wikipedia.org/wiki/Samsung_Galaxy_S7#Qualcomm_Snapdragon_820_Models
There isn't a single page when googling AT&T S7 Exynos that backs your claim up. The USA also uses completely different network technology than internationally, using the S7 Exynos in the USA is already known to cause issues with LTE, VoWiFi etc. They'd have to do a hardware refresh of the Exynos SoC if they wanted to support it in the USA, which they ain't going to do a for a 3 gen old phone.
Click to expand...
Click to collapse
lol ok.

Question Flashing unlocked firmware over carrier firmware?

Like the title says, is this possible and can it be done without wiping user data? Thanks.
Probably not worth the trouble. Always assume you will lose the data and back it up redundantly.
I thought there be a night and day difference when I got the unlocked N10+ N975U1 vs the AT&T variant N975U. There wasn't. The unlocked version actually had some bloatware not on the AT&T variant
Easiest and safest thing to do is package blocked the carrier bloatware. Verizon does some screwy modes to their devices so getting rid of that be nice. AT&T does not, that surprised me. Some users might like some of the AT&T apps.
It was successful, thank goodness. See my follow up here https://forum.xda-developers.com/t/f721u1-firmware-now-available.4484639/
Notice much difference?
Yeah the main stuff are:
1. Rcs with jibe server works now. Before it used att server so it wouldn't connect properly with other users
2. System updates come directly from Samsung instead of att
NguyenHuu said:
Yeah the main stuff are:
1. Rcs with jibe server works now. Before it used att server so it wouldn't connect properly with other users
2. System updates come directly from Samsung instead of att
Click to expand...
Click to collapse
Don't use either.
Updates is one of the first things I disabled on my N10+'s. One's on Pie, the other 10, I prefer Pie though. Once Google started rolling out scoped storage I bailed.
&
AT&T/Samsung have a nasty habit of screwing up older devices with firmware upgrades. Just had a pair of Buds+ screwed up like that a few months back, now they need the firmware rolled back*. S4+, same deal a few years back, but bootloader was updated too, no rollback.
If an OS is running fast, stable and fulfilling its mission... I let it be.
*I have 2 new pairs of Buds+, they sound identical and like my original pair use to, grrrrr.
Went with them because Samsung's newest release lack the features I want. Rather annoying.
The Buds+ have a 11 hr run time, light, don't fall out and sound good.
Sorry I should've posted my question here, instead of creating a new thread.
I recently purchased a flip 3 and am on a payment plan, tmobile won't unlock my phone unless I pay it off in full. Is it possible to flash the default software of the unlocked model so I can get updates from Samsung and still have my sim work? I'm not switching carriers, do I need the tmobile version of firmware for data/phone to work if the phone isn't unlocked?
boxface said:
Sorry I should've posted my question here, instead of creating a new thread.
I recently purchased a flip 3 and am on a payment plan, tmobile won't unlock my phone unless I pay it off in full. Is it possible to flash the default software of the unlocked model so I can get updates from Samsung and still have my sim work? I'm not switching carriers, do I need the tmobile version of firmware for data/phone to work if the phone isn't unlocked?
Click to expand...
Click to collapse
Phone service will still work perfectly fine on U1 firmware, but you may lose lose some carrier-specific features like wifi calling etc. But.... the U1 models don't always necessarily get faster updates than the carrier models. For example, with the most recent update, the carrier model got it 2 weeks before the unlocked model. So if that's your only reason for wanting to change firmware, I'd advise against it.
Notify Update
- U model update history
Notify Update
- U1 model update history
iBowToAndroid said:
Phone service will still work perfectly fine on U1 firmware, but you may lose lose some carrier-specific features like wifi calling etc. But.... the U1 models don't always necessarily get faster updates than the carrier models. For example, with the most recent update, the carrier model got it 2 weeks before the unlocked model. So if that's your only reason for wanting to change firmware, I'd advise against it.
Notify Update
- U model update history
Click to expand...
Click to collapse
What I'm concerned about is tmobile eventually stopping the updates way sooner than Samsung. The carriers don't usually update a phone as long as the vendor so to avoid that I would rather not use T-Mobiles version. Thanks for the reply, it was very helpful.
iBowToAndroid said:
Notify Update
- U1 model update history
Click to expand...
Click to collapse
boxface said:
What I'm concerned about is tmobile eventually stopping the updates way sooner than Samsung. The carriers don't usually update a phone as long as the vendor so to avoid that I would rather not use T-Mobiles version. Thanks for the reply, it was very helpful.
Click to expand...
Click to collapse
Incorrect. Every single model's lifespan for updates has always been the exact same, whether U or U1
I downloaded the unlocked firmware via Frija for SM-F711U1 / XAA and flashed it onto my At&t unit using patched Odin. Lost my data since the install didn't work without flashing CSC but booted up and working just fine now. No At&t bootscreen or bloat

Question Purchased a Verizon variant through Google Store, paid in full... Fully unlocked in 60 days, or is this a trick?

I haven't purchased a new phone since before 802.11ax came out. It's been... a long time, to say the least.
I'm reading mixed signals. Can I unlock, root, and do whatever anyone else can do with this hardware - or will they strangle my balls still?
I'm on Verizon too, but purchased the unlocked version. The Verizon bootloaders have driven me nuts in the past...
Fully unlocked amas in carrier unlocked. Only way you can unlock the bootloader of a pixel 7 device in the USA is if you bought an u locked variant directly from Google. You can't unlock any Android device bought from Verizon.
Usually it means you can't unlock the bootloader but that's only after the first firmware update.
So if you don't update it and wait then it should work. That's how it went with the vzw variant of the pixel XL anyways... I bought 2 of them because like a dupe I let it update without even thinking.
Then I got another and before anything I unlocked the bootloader, installed twrp, got root and then put my sim card in and I manually installed Google's updates and everything was fine.
Dunno if that changed or not...but it will ship with the ability to unlock it, or should because it's flashed with the stock Google firmware
The above post only applies to the original Pixel 1.
When Verizon says "unlocked" they mean carrier unlocked.
You can only get a bootloader unlocked if you buy direct from Google and buy the Google version of the phone, not the Verizon one they list.
What @jdoe6783 and @TonikJDK said. When all United States carriers volunteer information about "unlocking", they only mean carrier unlocking - i.e. you can then use your Verizon Pixel 7 Pro on a different carrier.
As I say in Post 2 in my thread:
roirraW edor ehT said:
Verizon variants:
Will never be able to have their bootloader unlocked. It's like winning the lottery, and just as rare and relatively random. There is nothing that anyone on XDA can do to help you unlock your Verizon variant.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Curious why you would even buy the carrier variant from the google store? I mean if you are paying in full, just buy the unlocked version.
Ok. Thank you, all. Once the device is carrier unlocked, will I be able to remove the Verizon bloatware? That's my biggest concern now. I can live with a locked bootloader as long as the provided OS allows me to control what software is and is not running.
I bought the carrier variant for a few reasons:
I've already settled on Verizon as my carrier for the long haul. I bounced around between MVNOs, Google Fi, and T-mobile before landing on Verizon ~18mo ago. It has been a better experience for a little less money after taking advantage of so many promotions - several of which hinge on my home ISP being Verizon as well.
The trade-in value is pretty solid. I don't value it at $700 like they say as it's really just $19/mo off my bill for 3 years. It's not clear to me what happens if I upgrade my device or decide to cancel service in that time... they just stop providing the discount?
I never felt the need to root my last phone. I did it for a while, and many of my necessary apps detected this and stopped working. I've gathered that this is something the community has addressed now, but it still speaks to the time/benefit of going through the process to root and try out different things that rooting enables. I have less time to research and try out various options than I once did. My suspicion is that I'll be happy enough with the factory OS. The only things that would change this would be if I cannot remove Verizon bloatware. I'm not forefiting that kind of control of my $1k phone for a $20/mo reimbursement.
mmWave sounds cool, but I'm not convinced it'll have a meaningful impact on my usage. Perhaps when I'm in a large city and there's congestion on the other bands... This is a very minor point.
shiftr182 said:
Curious why you would even buy the carrier variant from the google store? I mean if you are paying in full, just buy the unlocked version.
Click to expand...
Click to collapse
agreed...
you can always buy the Google unlocked variant and just activate it on your carrier (in this case, Verizon as OP's carrier), instead of purchasing the specific carrier variant.
At the very least I plan on purchasing the unlocked variant and activating it on Verizon....
If anything, @SethW, if it is truly important to you to do all the additional "fun" stuff like root, tether, custom ROMs, and all the other stuff (like it is to many/most of us on this forum)...you should still be in the return period. You might want to try the route of returning it and purchasing the Google unlocked variant to be certain you can unlock the bootloader -- and therefore root and other things.
EDIT
@SethW's reply just popped up while I was replying and just got in right before my post, so I wanted to address it...
SethW said:
Ok. Thank you, all. Once the device is carrier unlocked, will I be able to remove the Verizon bloatware? That's my biggest concern now. I can live with a locked bootloader as long as the provided OS allows me to control what software is and is not running.
I bought the carrier variant for a few reasons:
I've already settled on Verizon as my carrier for the long haul. I bounced around between MVNOs, Google Fi, and T-mobile before landing on Verizon ~18mo ago. It has been a better experience for a little less money after taking advantage of so many promotions - several of which hinge on my home ISP being Verizon as well.
....My suspicion is that I'll be happy enough with the factory OS. The only things that would change this would be if I cannot remove Verizon bloatware. I'm not forefiting that kind of control of my $1k phone for a $20/mo reimbursement.
Click to expand...
Click to collapse
It's okay to be on Verizon. I've been with them for decades and okay with them. It's good that you tried out a bunch and have your reasons to use them. By all means, you can/should use the P7P with them.
But to address your other concerns about the Verizon bloatware -- I'm fairly certain if you purchased the carrier specific Verizon variant, it will have its bloatware and you will not be able to remove it. There might be tricks to hide & help ignore it, but [usually] you aren't going to be able to remove it (at least without root, which you will not be able to do since Verizon bootlocks their devices; also, if it were rootable, you would have an unlocked variant and would not have bloatware in the first place ) [fun fact: in the earliest days of Android smartphones, the whole reason to root one's phone was to get rid of said bloatware; now, one has to purchase directly from Google and get their variant to even get a chance to root outside of carrier control]. Now I've never purchased a carrier variant from Google nor have I met anyone who has, so it might be different since you purchased it from Google store and not Verizon store, but I can't imagine Verizon wouldn't hold Google to their restrictions even if it's from Google's store -- I mean, what's the difference/purpose selling a carrier variant without any of said carrier's restrictions when Google could just sell Google's unlocked variant and just load it on the carrier's network?
TL;DR If it's a carrier (Verizon) variant, it most likely will have the carrier's bloatware; and you cannot remove it; even if the OS is as customizable as Android.
I'm definitely thinking about a return already. The agreements states 'unlocked after 60 days' which I read as fully unlocked, rather than some partial unlocking they've come up with. It really hinges on whether or not I can fully control the OS of the phone after it's 'carrier' unlocked.
EDIT - in response to @simplepinoi177 's edit
Well then. Returning it for sure. Didn't even think to mention ad-blocking apps and such but I rely on those. Makes my stomach turn when I see someone using a device without robust ad-blocking. Without root, that's probably on the chopping block too.
SethW said:
I'm definitely thinking about a return already. The agreements states 'unlocked after 60 days' which I read as fully unlocked, rather than some partial unlocking they've come up with. It really hinges on whether or not I can fully control the OS of the phone after it's 'carrier' unlocked.
Click to expand...
Click to collapse
Keep in mind, it's not just Verizon. All U.S. carriers, when they say unlocked, they only mean carrier unlocked. It's not just something Verizon came up with. As far as they're concerned, it will be fully unlocked.
SethW said:
EDIT - in response to @simplepinoi177 's edit
Well then. Returning it for sure. Didn't even think to mention ad-blocking apps and such but I rely on those. Makes my stomach turn when I see someone using a device without robust ad-blocking. Without root, that's probably on the chopping block too.
Click to expand...
Click to collapse
Good luck with your return and re-purchase!
simplepinoi177 said:
you can always buy the Google unlocked variant and just activate it on your carrier (in this case, Verizon as OP's carrier), instead of purchasing the specific carrier variant.
At the very least I plan on purchasing the unlocked variant and activating it on Verizon....
Click to expand...
Click to collapse
The unlocked phone from Amazon is the same as the unlocked one from Google, isn't it?
Wi1son said:
The unlocked phone from Amazon is the same as the unlocked one from Google, isn't it?
Click to expand...
Click to collapse
Yep
Wi1son said:
The unlocked phone from Amazon is the same as the unlocked one from Google, isn't it?
Click to expand...
Click to collapse
EtherealRemnant said:
Yep
Click to expand...
Click to collapse
Also, if you check the Amazon description, under "Wireless Carrier", it states "Unlocked", so it's a safe bet that it's actually unlocked like the Google variant and not the way carrier's state "unlocked" like it's not "contractually bound" or "locked" to the carrier....
If you have the Verizon model, you can disable some of the VZW bloatware with ADB, but not all of it. If you disable some of the VZW specific packages, it won't boot and you will have to go through recovery. I was really annoyed when I found out that I couldn't unlock the bootloader on the VZW model of my Pixel 3XL. On my previous phone I had relied on particular mods to make my life easier (I'm unilaterally deaf).
I would certainly return it for the unlocked Google version while the window is open, just in case you ever need to unlock the bootloader.
Refused delivery and requested FedEx return it to sender - as instructed by Google Support. In spite of this, FedEx tried to delivery every day for the past week. They're finally sending it back to Google. I suspect they'll refund it soon. I'm really annoyed that I'm apparently going to miss out on the $200 google store promotion. I was looking forward to trying out the pro earbuds for free.

Question One UI 5 Upgrade issue

I hope you guys can help me. I should have come to you all first.
I have S22 Ultra Snapdragon Unlocked Verizon SM-S908U1 VZW/XAA/XAA
Still haven't gotten One UI 5.
Tried to get OTA not available. Tried using Smart Switch, nothing. Tried going to Verizon website. They have posted that you can use their upgrade assistant tool. Didn't work.
So I called VZ tech support. They said i should have gotten the update and transferred me to Samsung tech who had me 1st try and reset my apps. The tech told me if that didn't work to call back. Gave me a ticket number to reference.
Well, it didn't. So I call back and the 2nd tech guy didn't even want to attempt to help me. He immediately told me I had to take my phone to a service center. He told me I could go to Best Buy or U Break. At this point my head is about to explode.
I go to Best Buy. They aren't set up yet as a service center. But when I tell the guy what's up, he tells me it's probably a corrupt OS and to take it to U Break and they can fix it.
When I got to U Break, they acted like they had never worked on an unlocked phone before. I told them I wanted to be sure the flashed it with the Unlocked firmware. They looked at me like I had 2 heads. They wanted me to call Samsung clarification. So Samsung said that all the firmware was the same. That it's the carrier that locks it. So I tell U Break to flash the phone. 4 hours later U Break calls me to tell me my phone will not take the One UI 5 flash. Everything if boots, it boots to One UI 4.1. They said they could leave it that way or mark my phone as unrepairable. I call Samsung back. I get told that they will not go by the word of their authorized service center. That to replace the phone, I have to mail it to Samsung for them to inspect. If they deem it unremarkable, they'll send me a replacement. Turnaround time about 2 weeks! Meanwhile I'm without a phone, my only means of communication. Or I can pay $99 deductible and replace it under Samsung Care. A phone that I've only had since June and I just made my 4th payment on, a phone I didn't Break.
I said screw it and picked up my phone and brought it home. Naturally it was wiped.
Now for my issue. Sorry to be so long winded. Just wanted to give you guys the back story.
I start to load my phone and notice that the "code" not sure the correct term, changed from VZW/XAA/XAA to VZW/VZW/XAA. I lost one of my fonts I purchased. And my phone just doesn't seem the same.
I tried to flash the One UI 4.1 XAA OS using Odin and it didn't change anything and I still can't get One UI 5.
Is my phone now locked? What can I do at this point?
Thanks for your help
My daughter's un-rooted, unlocked S22 on Verizon hasn't gotten it yet either. The unlocked versions are generally about a week behind.
1. Only Verizon and T-Mobile branded models have gotten the Android 13 update. The U1 is Unlocked firmware and will probably take a week or so longer. The only way you'd get it now is to flash to T-Mobile or Verizon firmware, which I don't recommend because they're bloated, lack certain Samsung features, and require a wipe when switching. Also, Verizon doesn't release all of its firmwares so you'd have to flash a version of 12, then upgrade.
2. There is NOTHING wrong with your phone. An unlocked phone on VZW will show VZW/VZW/XAA. If it was showing VZW/XAA/XAA, then the CSC (carrier coding) didn't fully change when inserting the SIM card.
3. Be patient, the changes in One UI 5 are minimal and there are possibly bugs. Wait for the stable release.
Guyinlaca said:
1. Only Verizon and T-Mobile branded models have gotten the Android 13 update. The U1 is Unlocked firmware and will probably take a week or so longer. The only way you'd get it now is to flash to T-Mobile or Verizon firmware, which I don't recommend because they're bloated, lack certain Samsung features, and require a wipe when switching. Also, Verizon doesn't release all of its firmwares so you'd have to flash a version of 12, then upgrade.
2. There is NOTHING wrong with your phone. An unlocked phone on VZW will show VZW/VZW/XAA. If it was showing VZW/XAA/XAA, then the CSC (carrier coding) didn't fully change when inserting the SIM card.
3. Be patient, the changes in One UI 5 are minimal and there are possibly bugs. Wait for the stable release
Click to expand...
Click to collapse
Not sure why people flipping out over this. Just relax the Unlocked Phones with no Carrier Firmware installed will be last to upgrade. All the Carriers get priority first. It's always been this way.

Categories

Resources