I'm a bit confused.
I just purchased an unlocked Pixel 7 Pro 256GB from Amazon -- Amazon is seller, NOT 3rd party seller with Amazon Fulfilment. I'm trying to root it now. I've been able to unlock the bootloader already. So I'm attempting to download the latest factory image but I'm quite confused as to which one to download. My current build number is TD1A.220804.009.A2. The A2 suffix seems to indicate that this build that came on this phone is for Telstra (AU) Australian market. My question is why is it on the unlocked model that Amazon USA is selling? But then there's no US image except for T-Mobile/Google Fi. Should I download the Global image or stick with the Telstra AU image?
Very confused.
I think all 3 are essentially the same; the only differences are special modifications to the radio for specific carrier (Telstra, Fi, T-Mobile) signals. I imagine, for your purposes, the A2 would be fine.
You might want to wait a couple of days as Google will release a new security firmware update in the next few days...
simplepinoi177 said:
I think all 3 are essentially the same; the only differences are special modifications to the radio for specific carrier (Telstra, Fi, T-Mobile) signals. I imagine, for your purposes, the A2 would be fine.
You might want to wait a couple of days as Google will release a new security firmware update in the next few days...
Click to expand...
Click to collapse
Thanks for the suggestion. May I ask what build you're on? And what country you're in?
Lakino said:
Thanks for the suggestion. May I ask what build you're on? And what country you're in?
Click to expand...
Click to collapse
No problem!
I'm in the US, on the Verizon network; that's how I learned since I asked the same thing about the difference between the verizon firmware update and the global one -- that it's basically the same other than special considerations to a specific network. The build I'm in is the Feb image TQ1A.230205.002.
Get on Google's website, get a US Verizon image, and flash it. Done. No issue.
Schroeder09 said:
Get on Google's website, get a US Verizon image, and flash it. Done. No issue.
Click to expand...
Click to collapse
I believe the OP is on Telstra (or at least his device has its firmware version), the last Verizon image was in November -- so that is very outdated -- and it might do OP best to wait until March's images are released as it will in a couple of days...
But, if anything, flashing a Global image probably wouldn't do any harm even if OP decided to flash that one either...
simplepinoi177 said:
I believe the OP is on Telstra (or at least his device has its firmware version), the last Verizon image was in November -- so that is very outdated -- and it might do OP best to wait until March's images are released as it will in a couple of days...
But, if anything, flashing a Global image probably wouldn't do any harm even if OP decided to flash that one either...
Click to expand...
Click to collapse
I guess my confusion stems from getting a Pixel 7 Pro from US Amazon that has a Telstra AU image preloaded. I'm in CA and my carrier is Xfinity -- which uses Verizon as their backbone. I'm not sure if I can just flash any of these builds on my Pixel 7 pro. Are their hardware differences between the models that are sent around the world? Can I flash the global build onto my Pixel 7 Pro?
So I think you "should" be fine but maybe someone else has a better answer for ya....however, if you can d/l an image just get the standard non-carrier version. I have been on Verizon forever and never use their image. Sometimes I will pull the radio out from it and see if that works better, but usually it does not as best as I can tell.
Also, maybe try this for your version answer...in Settings go to About Phone and then Regulatory Labels. There you will see the Model number for your particular P7P. Do a Google search on that and see what you find and post here to see if anyone can assist further.....mine is GE2AE as an example and I purchased direct from Google in California. Your CA maybe Canada
GL!!!
cmh714 said:
Also, maybe try this for your version answer...in Settings go to About Phone and then Regulatory Labels. There you will see the Model number for your particular P7P. Do a Google search on that and see what you find and post here to see if anyone can assist further.....mine is GE2AE as an example and I purchased direct from Google in California. Your CA maybe Canada
GL!!!
Click to expand...
Click to collapse
Thanks. Mine is also GE2AE. I'm in California.
It's got regulatory approval for USA, Canada, EU, UK, AU/NZ, and JP.
So it sounds like I should be able to flash the generic Global build then.
13.0.0 (TQ1A.230205.002, Feb 2023)
There actually is a variant specifically for Verizon and Verizon MVNOs -- of which Xfinity is one.
13.0.0 (TD1A.221105.003, Nov 2022, Verizon, Verizon MVNOs)
But that Verizon variant is Nov 2022. I'll try the latest Global version I guess once March 2023 update comes out in a few days
edit: It still seems exceptionally odd to me that the P7P that Amazon is shipping from their USA warehouses came with an .A2 suffix variant which indicates it's meant for Telstra -- a big carrier in Australia.
Like I said, I dont use the Verizon version, I have always used the standard version. Also as I mentioned, usually the Verizon radio file is differnet, so I have tried flashing that, but never see any real gain. YMMV.
Also, since the March update will be this week, you may as well wait a few days.....IMHO. GL!
Use whatever version is the most recent. If there isn't a Feb Verizon version that means the Verizon specific network changes have been merged into the main branch.
Happens all the time, there will be separate versions now and then until they get it all merged into one. It has always been that way for the Pixels.
Lakino said:
I'm a bit confused.
I just purchased an unlocked Pixel 7 Pro 256GB from Amazon -- Amazon is seller, NOT 3rd party seller with Amazon Fulfilment. I'm trying to root it now. I've been able to unlock the bootloader already. So I'm attempting to download the latest factory image but I'm quite confused as to which one to download. My current build number is TD1A.220804.009.A2. The A2 suffix seems to indicate that this build that came on this phone is for Telstra (AU) Australian market. My question is why is it on the unlocked model that Amazon USA is selling? But then there's no US image except for T-Mobile/Google Fi. Should I download the Global image or stick with the Telstra AU image?
Very confused.
Click to expand...
Click to collapse
A2 is what I've been using on unlocked same phone from Google play.
Just a heads up, but the global image works on every carrier in the United States. Just stick with the global builds so that some carrier bloatware isn't pulled in during your re-imaging.
So, although there are separate T-Mobile and Verizon factory images - you do not need to use them as the radio images in all of the US builds (and the global build) have the same available bands. The bands that are used are dictated by your SIM or eSIM. This information was provided to me when I had asked a Google rep why there was a T-Mobile factory image (as at one point, there hadn't been separate T-Mobile builds in the past).
Regardless, I have tested this as I have a pSIM (T-Mobile) and an eSIM (Verizon). I only use the global builds and get full network speeds and can connect to the UC and UW towers with both services - no issues whatsoever.
I'm on Verizon. I noticed the best battery life on November. I suspected I may have been because it's the only month since the p7p released that had a VZW-specific release file. I even asked if anyone else could confirm that the differences in radio files between the VZW update and the global could be the reason why many, many people noticed the best battery life on the November update. I asked multiple times to people noting the best battery life during November if they happened to be VZW customers who had chosen this update file. I never have heard an answer or discussion, so I'll ask here again since the topic of discussion is now in the foreground.
Could all the idle drain issues many people discovered since nothing that November update as the best all be VZW users who are now suffering from un-optimized, global radio.imgs in the update . zip? Are past radio files compatible with newer versions? For example, if tomorrow there is no VZW-specific update . zip file could I replace the march radio.img in the .zip with the VZW radio.img from November and then flash_all.bat that modified update .zip to be able to enjoy the optimized VZW radio? What other files are specific to VZW?
Just an FYI, I got an A2 Pixel from Amazon also. It sounds like it's safe to use the global image to root, correct?
bird333 said:
Just an FYI, I got an A2 Pixel for Amazon also. It sounds like it's safe to use the global image to root, correct?
Click to expand...
Click to collapse
For the final time, YES, it is safe to use the global image even if you have an Australian Telstra firmware version on your device even though it was bought from Amazon US...please be finally reassured that it won't break anything and/or be of any issue...
simplepinoi177 said:
For the final time, YES, it is safe to use the global image even if you have an Australian Telstra firmware version on your device even though it was bought from Amazon US...please be finally reassured that it won't break anything and/or be of any issue...
Click to expand...
Click to collapse
Better to be safe, asking questions thrice, than to end up with a bricked paper weight.
Samuel Holland said:
A2 is what I've been using on unlocked same phone from Google play.
Click to expand...
Click to collapse
Thanks for your data point.
NippleSauce said:
Just a heads up, but the global image works on every carrier in the United States. Just stick with the global builds so that some carrier bloatware isn't pulled in during your re-imaging.
Regardless, I have tested this as I have a pSIM (T-Mobile) and an eSIM (Verizon). I only use the global builds and get full network speeds and can connect to the UC and UW towers with both services - no issues whatsoever.
Click to expand...
Click to collapse
Thanks for your feedback.
bird333 said:
Just an FYI, I got an A2 Pixel from Amazon also. It sounds like it's safe to use the global image to root, correct?
Click to expand...
Click to collapse
Thanks for chiming in with your A2 build from Amazon. At least now I know I'm not the only one getting an A2 build from Amazon USA.
simplepinoi177 said:
and it might do OP best to wait until March's images are released as it will in a couple of days...
Click to expand...
Click to collapse
I'm starting to getting antsy waiting. The previous 3 months, they've released an update by the 6th or earlier, but nothing yet on Google site. Come on Google! Release the March 23 update already!
Lakino said:
I'm starting to getting antsy waiting. The previous 3 months, they've released an update by the 6th or earlier, but nothing yet on Google site. Come on Google! Release the March 23 update already!
Click to expand...
Click to collapse
I feel you! This is rather unusual (although it has happened from time to time)...
many in other threads are voicing how anxious they are in waiting too... Google usually aims for the 5th, unless the 5th lands on the weekend (as it was in this case), then it usually aims for the Monday after. What's really crazy is the fact that Samsung has released their March update before Google; Samsung in the past would release months, close to year after Google's update!
We're all
Related
I bought a Pixel 2 black at bestbuy an brought it back to the Netherlands where i live. I out in my t-mobile sim al works great. Accept i was woundering if i would get OTA updates? It has the securtity patch of September.
In the Verizon forum they say it makes no differance. But you buy a Pixel for the fast updates but it's 2 month behind
https://community.verizonwireless.com/thread/940020
Thanks
Erik1805 said:
I bought a Pixel 2 black at bestbuy an brought it back to the Netherlands where i live. I out in my t-mobile sim al works great. Accept i was woundering if i would get OTA updates? It has the securtity patch of September.
In the Verizon forum they say it makes no differance. But you buy a Pixel for the fast updates but it's 2 month behind
https://community.verizonwireless.com/thread/940020
Thanks
Click to expand...
Click to collapse
You won't get OTA updates, I was in the same boat as you. Verizon even says you need an active Verizon sim card installed to receive the updates on their Pixel 2 web page for update info. I have the Verizon Pixel 2 with a Vodafone sim card in the EU. The only way you'll get updates is to download the OTA file yourself (you can get it from Google) and use ADB. I'm up to date now and there were no issues doing it that way.
IDroidThere4Iam said:
You won't get OTA updates, I was in the same boat as you. Verizon even says you need an active Verizon sim card installed to receive the updates on their Pixel 2 web page for update info. I have the Verizon Pixel 2 with a Vodafone sim card in the EU. The only way you'll get updates is to download the OTA file yourself (you can get it from Google) and use ADB. I'm up to date now and there were no issues doing it that way.
Click to expand...
Click to collapse
I know. Flashed the OTA file with ADB. No problems . As long as Google keeps posting the OTA files ?
Erik1805 said:
I know. Flashed the OTA file with ADB. No problems . As long as Google keeps posting the OTA files
Click to expand...
Click to collapse
Yeah, sorry, when I replied to this message I dind't realize you had posted the other one as well. I'm hoping they keep the OTA's online too. Fingers crossed!
Now that you are mentioning this. Maybe these Verizon stuff is the whole reason they started uploading OTAs first.
Sent from my Pixel 2
Hi guys - currently it's not possible to get the pixel 2 in Ireland. I am going to New York and was thinking of buying the device straight from the Verizon store. From everything i've heard, it will work fine in the EU, also i'll save a little on the exchange rate (it comes in at around €700).
The updates thing is a major downside though - it's a good few months now since the last post on this - just wondering if anybody has had trouble downloading the updates directly from google?
PeterFitz said:
Hi guys - currently it's not possible to get the pixel 2 in Ireland. I am going to New York and was thinking of buying the device straight from the Verizon store. From everything i've heard, it will work fine in the EU, also i'll save a little on the exchange rate (it comes in at around €700).
The updates thing is a major downside though - it's a good few months now since the last post on this - just wondering if anybody has had trouble downloading the updates directly from google?
Click to expand...
Click to collapse
No trouble in downloading the OTA file and flashing it. (Pixel 2)
Thanks for coming back Erik. So, next question, how do I do that? :laugh: As a relative newbie, do this, is there much to it?
PeterFitz said:
Thanks for coming back Erik. So, next question, how do I do that? :laugh: As a relative newbie, do this, is there much to it?
Click to expand...
Click to collapse
Here you find all the info and the OTA files
https://developers.google.com/android/ota
Great, thanks again Erik.
Last question, is there much Verizon bloatware on the device?
PeterFitz said:
Great, thanks again Erik.
Last question, is there much Verizon bloatware on the device?
Click to expand...
Click to collapse
On mine none, using it in the Netherlands with T-mobile
Erik1805 said:
On mine none, using it in the Netherlands with T-mobile
Click to expand...
Click to collapse
Hi all, just to say I bought the Google Pixel XL 2 (64GB) in a New York Verizon Store (came to about €790).
It's working fine in Ireland with no problem and seems to be getting the updates also.
Does your Carrier get in the way of receiving updates, I've had a Nexus 5X and a Pixel 2 before and as far as i remember the carriers Virgin Mobile and Bell never got in the was of updates. Then again i did used to flash updates sometimes so idk maybe they did? Anyway i have the Essential Phone from Koodo and i never got the July Security patch also i still never got Android 9.0 according to to Essential Sprint? and Telus do further testing before releasing updates. I contacted Koodo and they said they do testing on Pixel and Essential updates So i want to know if anyone has a Pixel phone with a carrier in Canada, Do the carriers delay and test updates on them? I wanna get a Pixel 3 but not from koodo if i gotta wait a month or more for updates. Oh and i was told and read many people take out the Koodo sim cards and slap in a different carrier sim card and thats how they've been downloading the 9.0 update on Essential from Koodo.:silly:
I have pixel 2 on Koodo, I got the Android 9 update the day it was released.. I've had multiple Nexus, pixel devices and never once missed or was late with an update.
k.s.deviate said:
I have pixel 2 on Koodo, I got the Android 9 update the day it was released.. I've had multiple Nexus, pixel devices and never once missed or was late with an update.
Click to expand...
Click to collapse
Good to know, idk why they fool around with the Essential Phone, Just gimme my update.
Where is the update, I'm on Telus.
I wonder if I just have to pop in a Rogers SIM like I did with my Essential, just to get the update, because Telus won't let the update through
It seems as though no Canadian carrier has made the update available.
I'm wondering if this is on Google or the carrier. I would assume carrier...
Edit:
According to Fido's software update schedule, the December update will release December 19. A little behind, but oh well I guess. Hopefully this is earlier if not the same day for other carriers.
Quick question - if I've got an LG g7 one running in another region on another carrier (even though it's originally a Canadian released phone), how can I receive the updates (both security and pie)?
bryanzs said:
Quick question - if I've got an LG g7 one running in another region on another carrier (even though it's originally a Canadian released phone), how can I receive the updates (both security and pie)?
Click to expand...
Click to collapse
I can't say for sure as I've never tested this, but I honestly don't see why you wouldn't still receive any updates through the normal OTA process. If you don't, I'll do some research and see if there's firmware for this phone anywhere.
(I just picked this phone up a few days ago so I'm still learning about this particular model and the Android One program.)
Thanks, techboy11. Actually, I think the powers that be at LG must have heard my complaint, because I appear to be getting the update today! I'm glad to see that it's working as expected, because my main reason to get the G7 One was for the "Android One" experience (and the regular updates that that implies).
Dec update
Hi Everyone, just got Dec update for my G7 one, 263.9 MB includes bug fixes, security and system improvements. I'm with koodo.
Bell here, also got it. The update says
"LG is pleased to provide a new, free software update for your Android Smartphone. This release includes various bug fixes, security and system improvements."
Sounds like LG is pushing it, not the carriers. If the carriers were in control, it would probably drop on different days.
For anyone on Bell who may not have for some reason received the update, here is the OTA zip to do what you want with. I am not sure if this is applicable to other carriers as I've noticed the file sizes are different. For Bell mine was 260.4 MB compared to a Koodo 263.9 MB update.
techboy11 said:
For anyone on Bell who may not have for some reason received the update, here is the OTA zip to do what you want with. I am not sure if this is applicable to other carriers as I've noticed the file sizes are different. For Bell mine was 260.4 MB compared to a Koodo 263.9 MB update.
Click to expand...
Click to collapse
I'm on Bell and it was 263.9 MB
ChrisAG said:
I'm on Bell and it was 263.9 MB
Click to expand...
Click to collapse
Well that's interesting. That zip is the one I recieved at 260 MB. Wonder why there's a minor size difference ?
techboy11 said:
Well that's interesting. That zip is the one I recieved at 260 MB. Wonder why there's a minor size difference ?
Click to expand...
Click to collapse
Was yours sent to you by someone packaged as a zip or did it appear on your phone as an update?
ChrisAG said:
Was yours sent to you by someone packaged as a zip or did it appear on your phone as an update?
Click to expand...
Click to collapse
It appeared on my phone as that size of update and I grabbed the OTA link/file myself at the same size.
On Fido in Ontario here. Just did a manual check and I received the December security update.
I recently purchased a Oneplus 8 from T-Mobile, I paid in full and I'm using it on T-Mobile prepaid now. I do see on T Mobile's website that there was an update that went out in June, Build Number 10.5.10. I'm currently on Build Number 10.5.7, and I've tried several times to go into Settings>System>System Update to check for updates and nothing is available whatsoever. I know that updates are normally staged, but shouldn't that be available for all devices by now? Is me being on T-Mobile prepaid somehow hindering my ability to get updates? Any thoughts?
Try loading Oxygen Updater from the play store and see if that helps
Alan
alan sh said:
Try loading Oxygen Updater from the play store and see if that helps
Alan
Click to expand...
Click to collapse
Unfortunately I already tried that and it didn't work
The current versions are:
INDIA: Oxygen OS 10.5.10.IN21DA
EUROPE: Oxygen OS 10.5.9.IN21BA
NORT AMERICA: Oxygen OS 10.5.11.IN21AA
Go to https://www.oneplus.com/support and click on Software Upgrade and be sure to have the settings so that you get the version for North America witch is 10.5.11.IN21AA. As you now have AA at the end I suppose you are in the USA.
Follow the instructions on the web page to place the file as it is on the phone and do a local update.
succumbtothegreater said:
I recently purchased a Oneplus 8 from T-Mobile, I paid in full and I'm using it on T-Mobile prepaid now. I do see on T Mobile's website that there was an update that went out in June, Build Number 10.5.10. I'm currently on Build Number 10.5.7, and I've tried several times to go into Settings>System>System Update to check for updates and nothing is available whatsoever. I know that updates are normally staged, but shouldn't that be available for all devices by now? Is me being on T-Mobile prepaid somehow hindering my ability to get updates? Any thoughts?
Click to expand...
Click to collapse
Being on TMO prepaid may be different. There may be a roll out for you but I don't know. The TMO build should be 10.5.10.IN55CB which is for TMO. A lot of people move to international due to the lack I'm updated from TMO.
I am on TMO but I'm rooted and running the international version of 10.5.11.IN21AA. Happy modding!
Nathan.7118391 said:
Being on TMO prepaid may be different. There may be a roll out for you but I don't know. The TMO build should be 10.5.10.IN55CB which is for TMO. A lot of people move to international due to the lack I'm updated from TMO.
I am on TMO but I'm rooted and running the international version of 10.5.11.IN21AA. Happy modding!
Click to expand...
Click to collapse
I think it may be because I'm on prepaid. I did a chat with Oneplus and I got the usual, nothing helpful, they just said the updates aren't available in my region??? I'm in the US so that makes no sense. Oh well. I requested the unlock token on Tuesday, so I'll be on the INT'L version soon enough. Just frustrating
Update:
I decided to do the MSM flash for 10.5.7 and that actually solved my problem and I am getting updates now.
Google delivers Android 13 December 2022 update for Pixel 7 and Pixel 7 Pro
Google has announced a major feature update for Pixel smartphones running Android 13. As of the December 2022 update, the likes of the Pixel 7 and Pixel 7 Pro support a dedicated reader mode and can share digital car keys with other compatible smartphones, among other changes.
www.notebookcheck.net
I put mine on the beta channel release. Coming from a P6P, using straight talk, it would not accept the sim.
Called Straight talk, which was useless. They said I had to buy a new sim card. Saw on a thread here that the
beta channel rom fixed it. Sure enough! After reboot, the sim card worked!
I was expecting 5g update, disappointing...
Nothing here. UK Sim free.
eagledipesh said:
I was expecting 5g update, disappointing...
Click to expand...
Click to collapse
I wouldn't hold your breath. They either chose horrible hardware, don't know how to fix it, or won't because we will buy a new Pixel. With that being said, I actually think that the 7 Pro is an improvement over the 6 pro. My battery and performance is dramatically improved because of the updated Tensor chip and I don't have the cell standby bug that plagued me in the 6 pro.
eagledipesh said:
I was expecting 5g update, disappointing...
Click to expand...
Click to collapse
This isn't the full release notes.
That article from notebookcheck.net referencing the Google Blog only concerns the "Android Feature Update", which is for GMS Android users. There is also a "Pixel Feature Drop" which Pixel users will likely get tomorrow. Plus there will likely be other "fixes" and whatnot.
biggiesmalls657 said:
I wouldn't hold your breath. They either chose horrible hardware, don't know how to fix it, or won't because we will buy a new Pixel. With that being said, I actually think that the 7 Pro is an improvement over the 6 pro. My battery and performance is dramatically improved because of the updated Tensor chip and I don't have the cell standby bug that plagued me in the 6 pro.
Click to expand...
Click to collapse
Unfortunately for me the bug still exists P7P. I am not sure if different hardware release have different modems. But my phone is useless at the moment.
xpact said:
Unfortunately for me the bug still exists P7P. I am not sure if different hardware release have different modems. But my phone is useless at the moment.
Click to expand...
Click to collapse
What's your setup? I'm rooted custom kernel and 1 ESIM using Xfinity Mobile. I also didn't restore settings with 6 pro backup. I flashed BL and modem before clean flashing stock to root
biggiesmalls657 said:
What's your setup? I'm rooted custom kernel and 1 ESIM using Xfinity Mobile. I also didn't restore settings with 6 pro backup. I flashed BL and modem before clean flashing stock to root
Click to expand...
Click to collapse
I am in 5G unsupported country and I am using physical SIM I have tried to disable DSDS but it didn't seem to stick. I have tried with stock and beta QPR1 same result. Which custom kernel would you recommend? I think the issue is with the radio and the Samsung Shannon 5300G. I am not sure if there is a radio firmware I could try.
"I am in 5G unsupported country"
I fail to understand the complaints from people who live in "unsupported" countries!
Why would you even consider buying ANY phone that is unsupported in any way?
The fault is yours not Googles! YMMV
jaseman said:
"I am in 5G unsupported country"
I fail to understand the complaints from people who live in "unsupported" countries!
Why would you even consider buying ANY phone that is unsupported in any way?
The fault is yours not Googles! YMMV
Click to expand...
Click to collapse
Probably because they wanted a pixel but Google only officially sells phones in like 4 countries (exaggerating but probably not by much). I want phones available outside of the USA all the time but my wonderful carrier (verizon) and to a degree the other carriers as well suck and want big money to certify the ability to use their towers (bands). Stuck mainly with iSheep, Samdung, One Plus (already settled) and Google (constant hardware problems).
It will be difficult for me to make you understand anything since you fail to understand simple things like why anyone would pick a Google phone instead of another brand. Anyway I had Nexus and Pixel phones in the past and they have worked just fine. I was very well aware 5G and VoLTE don't work and I was not after these features. I would be perfectly fine with just 4G. Mine Pixel 6 Pro and Pixel 2 XL worked flawlessly. I might have a faulty hardware I am not sure at this point. If you could not help me at least don't blame me for my choices, the money I have spent are mine not yours. Like I have said I know since the beginning some of the feature would not work and this was a risk I was willing to take since I wanted a "clean" android and rootable + unlocked bootloader (there are not many phone manufacturers offering such features). I was not expecting the Pixel to not support any well established telecom standards. Aside from that I live in Europe and I bought the phone from neighboring country. It is not from Japan or US/Canada with different bands.
@xpact , it might be your phone or possibly faulty modem hardware. I am in the US using the 7P7 (rooted, unlocked) without any issues (I keep 5G off) 99% of the time. Once in a while I have to restart my phone or turn airplane mode on and off because I would randomly lose service. Its pretty rare though and even less now after the November update.
Question for the group and I hope I'm in the right spot. I got my 7 pro last week. So I went to the Factory image page. I'm on Verizon so I took the verzon update. Now I see a update just for global. Should I wait on the Verizon or can I just install the global one? I'm new to Pixel experience.
foamerman said:
Question for the group and I hope I'm in the right spot. I got my 7 pro last week. So I went to the Factory image page. I'm on Verizon so I took the verzon update. Now I see a update just for global. Should I wait on the Verizon or can I just install the global one? I'm new to Pixel experience.
Click to expand...
Click to collapse
You can install the global one.
foamerman said:
Question for the group and I hope I'm in the right spot. I got my 7 pro last week. So I went to the Factory image page. I'm on Verizon so I took the verzon update. Now I see a update just for global. Should I wait on the Verizon or can I just install the global one? I'm new to Pixel experience.
Click to expand...
Click to collapse
I bought the unlocked P7P from Google and Verizon is my carrier. I have only been flashing the generic firmware to avoid VZW bloatware as much as possible. I haven't had any issues.
xpact said:
It will be difficult for me to make you understand anything since you fail to understand simple things like why anyone would pick a Google phone instead of another brand. Anyway I had Nexus and Pixel phones in the past and they have worked just fine. I was very well aware 5G and VoLTE don't work and I was not after these features. I would be perfectly fine with just 4G. Mine Pixel 6 Pro and Pixel 2 XL worked flawlessly. I might have a faulty hardware I am not sure at this point. If you could not help me at least don't blame me for my choices, the money I have spent are mine not yours. Like I have said I know since the beginning some of the feature would not work and this was a risk I was willing to take since I wanted a "clean" android and rootable + unlocked bootloader (there are not many phone manufacturers offering such features). I was not expecting the Pixel to not support any well established telecom standards. Aside from that I live in Europe and I bought the phone from neighboring country. It is not from Japan or US/Canada with different bands.
Click to expand...
Click to collapse
I'm in Europe too and have the p7p from Germany, all works fine, no faulty hardware at all. Where did you buy your phone? I'm on stock firmware but had rooted it and there was also no problems, I often think to myself wtf you are always doing with your phones?
Thanks guys. I'm off to see the Wizard.
Gerr1 said:
I'm in Europe too and have the p7p from Germany, all works fine, no faulty hardware at all. Where did you buy your phone? I'm on stock firmware but had rooted it and there was also no problems, I often think to myself wtf you are always doing with your phones?
Click to expand...
Click to collapse
I bought it from Germany as well ) The previous pixel I had I bought it from UK and the Nexus 6P from UK as well. But the ones from UK I did not bought on first date but few months after they might had different hardware modem revisions.