I would like to purchase a Pixel but i have some concerns. I'm on the Verizon network and some of the things I hate about Verizon are....
#1 They never update phones
#2 Locked Bootloader so I can't root my phone
#3 Loaded with Bloatware.
It seems like the Pixel solves most of these problems, right? I guess my questions are; if I buy a Pixel off ebay and bring it into Verizon for activation will they lock my phone and load it with bloatware? Will they make it impossible for me to root it? Will it be updated ever? I'd hate to purchase one of these only to have it turn out to be yet another typical Verizon bloatware/locked/never updated phone.
As long as it is the Google version none of that will happen. Lots of us with the Google version on VZ and it is fine.
But you need to ne certain it is the Google version and not the VZ version. I would be very careful on Ebay. I wouldn't buy it unless I could get my hands on it and unlock it first.
Oh wow. So the Verizon version cannot be unlocked at all? Even with depixel8? I was trying to find a way to distinguish between the Verizon and Google store versions and I stumbled onto this post where they break down the SKU meaning. One of the posts says...
What we're currently sure of is that the SKU is formatted as follows:
G-2PW[Model][Region]00-0[Country/Carrier][Storage]-[ColorCode]
Model:
4: Pixel
2: Pixel XL
Region:
1: North America
2: Rest of the World
Country/Carrier:
1: USA (non-carrier specific)
2: USA Verizon
3: Canada (?)
4: ? (Probably Europe)
5: India (probably rest of Asia as well)
Storage:
1: 32 GB
2: 128 GB
ColorCode:
A: Quite Black
B: Very Silver
C: Really Blue
So if I want a black 32 GB no-Verizon-bloatware-locked-version I would want SKU G-2PW4100-011-A, right?
A VZ version beyond 7.1 cannot be depixel8'd. I don't know the details of the sku system.
I have the Verizon version and think it's fine. I'm getting updates fine. In fact I'm on the beta version of Android O
That said when browsing the file system I did notice a bunch of Verizon folders. Not sure what's in then but I don't think it's completely bloat free but someone else can comment.
Oh and fun fact, I'm using my Verizon Pixel on T-MOBILE'S network. So maybe that's why I'm getting updates. No idea.
Sent from my Pixel using Tapatalk
Updates are available on Googles site the same day for Verizon as well as the Google version of the phone. Updates are not an issue with the Verizon version of the phone. Literally the ONLY difference is one has an unlockable bootloader and one does not (unless it was 7.1). It's that simple.
So if the bootloader is locked I cannot root the phone, right?
The current root methods require an unlocked bootloader.
Related
Hi all,
My SGS2 recently just died all of a sudden and while trying to flash a new firmware it bricked. =( Hence I'm currently looking for a replacement phone and have always wanted to get the Razr Maxx HD simply for it's battery life (a phone that has to be continuously plugged in to use all features is so pointless). Unfortunately, I am from Singapore which means the purchase is rather "risky" since it's expensive to ship and return is not an option. Hence I have some questions that will help me make a decision. Hope you guys can help me out. That fact that the 2 models are in the same forum doesn't really help make things clear.
1) Boot Loader
I've read that Dev version comes unlocked while Consumer (Verizon) version comes locked. I've also seen instructions on rooting the Verizon version; I'm a little confused. Can I or can I not root the consumer version?
2.i) Rooting
This is actually quite similar to (1). There are some apps that I use that requires rooting (e.g. Titanium Backup); rooting is essential to me. If I were to lay my hands on a non-Dev version, can I root it?
2.ii) Rooting
The current "procedure" for rooting is to downgrade to ICS 4.0.4 and then root, right? Is it safe to update to JB after that? There appears to be several posts claiming that they've lost their root after update. I assuming they didn't follow the post linked below? Also, rooting will not be possible (yet) if the firmware is on 4.1.2?
Ensuring Root After Updates?
3) Carrier Unlocked
I need to get an unlocked version for it to work with anything else other than Verizon - am I right? I've seen someone post that the XT926 is only locked in the US; it'll work on any other GSM carrier in the rest of the world. Is this true? Or did the guy mix it up with the XT925? There are many such posts.
4) Where to buy
Since return and shipping is an issue, I'm trying to stay away from eBay (unless the seller has good record). Unfortunately, many online retailers seem to be out of this phone! Can someone recommend a place where I can purchase the phone from? It does not have to ship internationally as I am able to arrange for courier services.
Thanks for the help!
P.S. I'm really dying to get this phone. I just need to have those questions answered before I splurge a rather large amount of money to ship it over.
Just started looking because I need a new phone and I'm not sure I can last till the GS4 comes out, the DNA has weak battery and poor storage and the note 2 is too much so late after it's release
1. The boot-loader for the verizon model is locked
2. You can root on ICS then upgrade with voodoo root keeper to 4.1.1; however there are reports that 4.1.2 has some issues with doing that. Verizon's can only downgrade to ICS from 4.1.1; if it comes with 4.1.2 it isn't rootable (yet)
3. Supposedly, verizon's works out of the box on all GSM except AT&T and Tmobile but I've seen some people have had some issues or at least someone did in india though
4. have you looked at like amazon wireless 650 no contract in us
Wirefly also has some in stock and on sale. I'm not sure of places that offer international shipping, though a bunch offer free shipping so it probably offsets anyways
There is only the T926 in a maxx version
This place might ship to singapore phone price 700
Hi! Thanks for the reply.
Yes, I am looking for the "Maxx HD", aka the XT926.
Anyway, can I summarize that, if I were to lay my hands on a "consumer" version,
1) Bootloader is locked; I won't be able to flash custom ROMs
2) Rooting is possible if the phone ships with ICS. Can also possibly upgrade to 4.1.1 after rooting.
I have the MAXX HD and to answer as I can:
Bootloader is locked on the consumer version. I believe the developer edition is unlocked.
The consumer version can be rooted if it is not on the 4.1.2 release. Earlier releases can be back-leveled to 4.0.4 which can be rooted. Once rooted, root can be preserved with OTA Root Keeper. SuperSU seems to survive updates as well if it is set to preserve itself.
I believe you can use custom ROMs if you have root (I started fiddling with Safestrap when I had issues with the update and had to fastboot my phone to stock.)
Once at 4.1.2 the phone cannot be back-leveled and cannot be rooted (yet hopefully).
As I understand it: GSM is locked domestically (US). Unlocked internationally if the phone has been activated domestically first.
Hey,
To add on to what others have said -- yes the phone is SIM unlocked, though it will *not* work on ATT/TMobile in the US without a firmware tweak (search around, it's an easy thing to do -- though I haven't done it myself.) The most recent update fixed the issue with roaming in India, though I haven't verified that myself. But the phone will definitely work in Australia as that's where I have been using it.
The phone works fine with the following caveats:
1. There is annoying "This SIM card is from an unknown source" warning when you turn the phone on. Easily bypassed by pressing "OK"
2. Tethering will not work on foreign SIMs, it tries to communicate back to the VZW network to verify your eligibility, which of course fails on a foreign SIM.
3. If you actually care about using the phone internationally on VZW's network, you need to call and have your account setup to allow for 4G international roaming (this is different then the 3G intl feature)
-- Dan
Thanks for the reply guys.
With regards to what dbeedle said, it means that I just can't grab the phone off AmazonWireless and ship it out of the US because it has to be activated domestically?
As for the caveats mentioned by Dan,
1) Yea, I can definitely live with that. I don't turn my phone on/off frequently.
2) Tethering will be an issue (I use it sometimes)
3) Not a concern for me.
Also, the Dev edition is not available with the maxx battery
University of Pi said:
Just started looking because I need a new phone and I'm not sure I can last till the GS4 comes out, the DNA has weak battery and poor storage and the note 2 is too much so late after it's release
1. The boot-loader for the verizon model is locked
2. You can root on ICS then upgrade with voodoo root keeper to 4.1.1; however there are reports that 4.1.2 has some issues with doing that. Verizon's can only downgrade to ICS from 4.1.1; if it comes with 4.1.2 it isn't rootable (yet)
3. Supposedly, verizon's works out of the box on all GSM except AT&T and Tmobile but I've seen some people have had some issues or at least someone did in india though
4. have you looked at like amazon wireless 650 no contract in us
Wirefly also has some in stock and on sale. I'm not sure of places that offer international shipping, though a bunch offer free shipping so it probably offsets anyways
There is only the T926 in a maxx version
This place might ship to singapore phone price 700
Click to expand...
Click to collapse
Bootloader has been unlocked on the non dev. edition xt926 Verizon phone!!!
an21281 said:
Bootloader has been unlocked on the non dev. edition xt926 Verizon phone!!!
Click to expand...
Click to collapse
Hi! Are you referring to this post?
baineteo said:
Hi! Are you referring to this post?
Click to expand...
Click to collapse
No this one... http://www.droidrzr.com/index.php/topic/15008-motorola-bootloaders-cracked/
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
an21281 said:
No this one... http://www.droidrzr.com/index.php/topic/15008-motorola-bootloaders-cracked/
http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
Click to expand...
Click to collapse
Well well.. that's definitely good news!
One last question, does the phone has to be activated in the US before it can be used? I don't use to have a USD700 piece of kevlar sitting on my desk..
Will the Motorola XT926 work in Australia
Hi Dan,
Thanks for the info I have a Motorola Verizon XT912 which works fine in Australia but also has the annoying "SIM is from an unknown source" message and I also could not get tethering to work with an Aust SIM.
Now, I would like to buy the XT926 however sellers on ebay are quoting... "* Quad-band GSM and 3G support (available only outside of the United States with Verizon roaming)" That concerns me however I don't believe it's true.
So you have not had any issues with your XT926 working on GSM and 3G in Australia ?
Thanks
David
Cpudan80 said:
Hey,
To add on to what others have said -- yes the phone is SIM unlocked, though it will *not* work on ATT/TMobile in the US without a firmware tweak (search around, it's an easy thing to do -- though I haven't done it myself.) The most recent update fixed the issue with roaming in India, though I haven't verified that myself. But the phone will definitely work in Australia as that's where I have been using it.
The phone works fine with the following caveats:
1. There is annoying "This SIM card is from an unknown source" warning when you turn the phone on. Easily bypassed by pressing "OK"
2. Tethering will not work on foreign SIMs, it tries to communicate back to the VZW network to verify your eligibility, which of course fails on a foreign SIM.
3. If you actually care about using the phone internationally on VZW's network, you need to call and have your account setup to allow for 4G international roaming (this is different then the 3G intl feature)
-- Dan
Click to expand...
Click to collapse
Moto_Dave said:
Hi Dan,
Thanks for the info I have a Motorola Verizon XT912 which works fine in Australia but also has the annoying "SIM is from an unknown source" message and I also could not get tethering to work with an Aust SIM.
Now, I would like to buy the XT926 however sellers on ebay are quoting... "* Quad-band GSM and 3G support (available only outside of the United States with Verizon roaming)" That concerns me however I don't believe it's true.
So you have not had any issues with your XT926 working on GSM and 3G in Australia ?
Thanks
David
Click to expand...
Click to collapse
be cautious of these sellers on ebay. i just helped another member a couple days ago who bought an unlocked 925 from there (or so he thought).
after i had him check a few things for me, i confirmed without a doubt, it was a locked 926. now he has to file a claim.
you would be better off getting it from swappa.
here are the specs for the 926, it will not work on any other frequencies than those listed. others are just not built into the phone, so there is no way they can work, as far as im aware.
im not sure how they apply to your situation. i think you would have to find out what they use in your area, and see if they are listed in the specs.
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.
First of all, I don't live in the US. I have a friend there who can order one and ship it to me.
The Kinda Blue Pixel 2 looks nice and I wonder if I can just order it despite being limited to Verizon option? I don't root my phone so the bootloader locking isn't really an issue for me. I have read some threads saying that it's not carrier-locked. Can someone please clarify if I can just order it and ignore all the Verizon things? Will I need to register the SIM card that is included (can I just throw it away)? With whom do I need to contact if I were to send it back for replacement later? (Google or Verizon)
Any additional info is appreciated, thanks.
You can buy the kinda blue and put your own sim in. It is not carrier locked. You will have all the Verizon bloatware on it which you can disable. But it'll work. I almost did it too, but decided to go with Google black one in case I wanted to flash it although likely hood is very low.
docmalc said:
You can buy the kinda blue and put your own sim in. It is not carrier locked. You will have all the Verizon bloatware on it which you can disable. But it'll work. I almost did it too, but decided to go with Google black one in case I wanted to flash it although likely hood is very low.
Click to expand...
Click to collapse
I believe you can't unlock the bootloader for the Verizon version. The Pixel was that way. You had to use a hack to do it. There may be some delay as the original tool may not work this time around.
Sent from my Nexus 5X using Tapatalk
Tidbits said:
I believe you can't unlock the bootloader for the Verizon version. The Pixel was that way. You had to use a hack to do it. There may be some delay as the original tool may not work this time around.
Click to expand...
Click to collapse
Yeah, I'm pretty sure I've seen in confirmed somewhere that you cannot unlock the bootloader on the Verizon Pixel 2 (just like with the Pixel 1). Also, I think you will be dependent on Verizon for software updates (although with the Pixel 1, I think they have just stuck to Google's schedule). I don't think it's worth it for just a color.
My understanding for the bloatware, however, is that it's on all of the Pixels (that's, I believe, how it worked with the Pixel 1). It just doesn't show up unless you put a Verizon SIM in the phone.
So from what I have read online, Verizon phones will have the bootloader locked. The bloatware will come pre-installed on "Verizon" branded phones. The unlocked phones will get Verizon crap if a Verizon sim is installed. I believe about 4 programs will be pushed down. However, it could be uninstalled vs just being disabled. As for the software updates, Google will release updates to both versions of the phone. Verizon will not be able to touch the software and will have to release it immediately to "Verizon" branded Pixels.
When I purchased my Nexus 6P several years ago, I just swapped my Verizon SIM out of my Note 4 and went on my merry way. My Dad asked for a phone recommendation and I recommended the Pixel 2, thinking it would work the same way. Now I discover there's a carrier-unlocked version and a Verizon version. I don't want the Verizon bloatware on his phone and would rather not have to begin by deleting a bunch of apps (if Verizon will actually allow me to uninstall any apps [they love to install bloatware as system apps])as I'm the first step in his tech support hierarchy. I doubt I'll root his phone but I definitely don't want to have a locked bootloader which seems to be the Verizon standard.
If I get him the carrier-unlocked version and put his Verizon SIM card in, will it work on Evil Red's, I mean Big Red's network? I couldn't find any radio differentiation on Google's tech specs page.
Thank you for any information you can provide me.
Narsil007 said:
When I purchased my Nexus 6P several years ago, I just swapped my Verizon SIM out of my Note 4 and went on my merry way. My Dad asked for a phone recommendation and I recommended the Pixel 2, thinking it would work the same way. Now I discover there's a carrier-unlocked version and a Verizon version. I don't want the Verizon bloatware on his phone and would rather not have to begin by deleting a bunch of apps (if Verizon will actually allow me to uninstall any apps [they love to install bloatware as system apps])as I'm the first step in his tech support hierarchy. I doubt I'll root his phone but I definitely don't want to have a locked bootloader which seems to be the Verizon standard.
If I get him the carrier-unlocked version and put his Verizon SIM card in, will it work on Evil Red's, I mean Big Red's network? I couldn't find any radio differentiation on Google's tech specs page.
Thank you for any information you can provide me.
Click to expand...
Click to collapse
It'll work they are all the same. Just don't put the sim in until after the setup process. From my understanding if you get the one from Verizon it will not install Verizon apps if you setup the phone without a sim in it. However you couldn't unlock the bootloader(there's a hack for it I believe).
Verizon installs the MyVerizon and go90 apps from the play store after setup if you have a vzw sim in it which can both be uninstalled. (Google store version does this too)
Only difference in versions is the verizon branded model comes with a sim in it and oem unlock is greyed out
Thank you! I've ordered the Carrier-Unlocked model from the Play Store for him and will set it up for him when it arrives.
I like the blue version, but it seems that Verizon model has it and not the carrier unlocked version. So the question is, if I will pick Verizon from google store, will the unit come carrier unlocked or it will be locked to Verizon?
Charkatak said:
I like the blue version, but it seems that Verizon model has it and not the carrier unlocked version. So the question is, if I will pick Verizon from google store, will the unit come carrier unlocked or it will be locked to Verizon?
Click to expand...
Click to collapse
It's carrier unlocked they all are. The only thing you can't unlock is the bootloader.
Sent from my Pixel 2 using Tapatalk
Tidbits said:
It's carrier unlocked they all are. The only thing you can't unlock is the bootloader.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Oh, that isn't an issue for me. All I need the phone to be sim unlocked. I have heard that original pixel phone which was purchased form Verizon had also bootloader locked. What some users did, was that when they bought the phone new, removed Verizon sim, then turned of phone without the sim card and went through the set up. After that they were able to toggle OEM unlock. I don't know if it is the same for Pixel 2 phones.
Charkatak said:
Oh, that isn't an issue for me. All I need the phone to be sim unlocked. I have heard that original pixel phone which was purchased form Verizon had also bootloader locked. What some users did, was that when they bought the phone new, removed Verizon sim, then turned of phone without the sim card and went through the set up. After that they were able to toggle OEM unlock. I don't know if it is the same for Pixel 2 phones.
Click to expand...
Click to collapse
From this point around it Sims that was fixed. You won't get the apps but the bootloader stays unlockable.
Sent from my Pixel 2 using Tapatalk
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.