Related
Hi everyone,
I have a Nexus 5 that was purchased from TELUS (in a rush since I couldn't wait for a google play store version to make it here). Is there any way for me to flash or change my phone to get it's updates from google directly, and thus removing TELUS from the equation? EG my update to 4.4.3 was way behind google's push, and since it is a Nexus 5 there's no customizations that I can think of that TELUS would actually do to this phone.
I'd really like to have this device as if it came from the play store.
Thanks!
There is no such thing as carrier branded software on a nexus (with exception of Verizon on the Gnex... but different story).
Updates aren't always going to be on time; you just have to wait.
korockinout13 said:
There is no such thing as carrier branded software on a nexus (with exception of Verizon on the Gnex... but different story).
Updates aren't always going to be on time; you just have to wait.
Click to expand...
Click to collapse
So to state the obvious then, my phone doesn't communicate with TELUS update servers, it's straight to google? Is there a way I can check this in developer options or anything?
froek said:
So to state the obvious then, my phone doesn't communicate with TELUS update servers, it's straight to google? Is there a way I can check this in developer options or anything?
Click to expand...
Click to collapse
every single current nexus gets its update from google(or gets updated manually). updates are promised to go to everyone within a 3 week period. if you somehow changed any system files, you wont get an ota. just update your phone manually, its easy and faster.
simms22 said:
every single current nexus gets its update from google(or gets updated manually). updates are promised to go to everyone within a 3 week period. if you somehow changed any system files, you wont get an ota. just update your phone manually, its easy and faster.
Click to expand...
Click to collapse
Where's the best place to locate all OTA files? Is there a place to browse to select, or is it always like in this post where they mention the link only:
http://forum.xda-developers.com/showpost.php?p=53135171
froek said:
Where's the best place to locate all OTA files? Is there a place to browse to select, or is it always like in this post where they mention the link only:
http://forum.xda-developers.com/showpost.php?p=53135171
Click to expand...
Click to collapse
http://www.randomphantasmagoria.com/firmware/nexus-5/hammerhead/
all official nexus factory images https://developers.google.com/android/nexus/images
but there isnt a page with all official otas.
Great! Thanks very much everyone
Maybe there is already a thread of this somewhere already, but I didn't see one, apologies if it is, just thought I'd share my thoughts. Or maybe this is just super obvious so nobody posted about it. Anyway...
So as of the time of this writing they're still accepting people into the Oreo Beta. I only registered my phone about an hour ago (just before midnight, Nov. 1st) in the Samsung+ app and it let me get the Beta, so I imagine all the spots aren't full yet.
To those of you on the wrong carrier (But still in the U.S.) the process is easy! Simply go to this tutorial HERE to flash the unlocked firmware on your device.
After set-up, download the Samsung+ app, and register for the beta. Then, head to "Update" in your settings, and search for updates. It will have to go through *every* update between that firmware and the latest release, before finally downloading Oreo. My phone updated *four times* so be prepared to waste some time.
cadetprewitt1992 said:
Maybe there is already a thread of this somewhere already, but I didn't see one, apologies if it is, just thought I'd share my thoughts. Or maybe this is just super obvious so nobody posted about it. Anyway...
So as of the time of this writing they're still accepting people into the Oreo Beta. I only registered my phone about an hour ago (just before midnight, Nov. 1st) in the Samsung+ app and it let me get the Beta, so I imagine all the spots aren't full yet.
To those of you on the wrong carrier (But still in the U.S.) the process is easy! Simply go to this tutorial HERE to flash the unlocked firmware on your device.
After set-up, download the Samsung+ app, and register for the beta. Then, head to "Update" in your settings, and search for updates. It will have to go through *every* update between that firmware and the latest release, before finally downloading Oreo. My phone updated *four times* so be prepared to waste some time.
Click to expand...
Click to collapse
Why do you say non tmo
pro_granade said:
Why do you say non tmo
Click to expand...
Click to collapse
Because so far only t mobile and Sprint carriers and g950u1 users can get the beta. Other carriers can't so that's why he said for non tmo and Sprint users
adj998 said:
Because so far only t mobile and Sprint carriers and g950u1 users can get the beta. Other carriers can't so that's why he said for non tmo and Sprint users
Click to expand...
Click to collapse
It's closed now, they removed the script to even bring the beta button onto the app, if you use the fiddler thing to make it come up, it makes no difference, and I private glitch I had to get the beta signup to come up doesn't work either.
pro_granade said:
It's closed now, they removed the script to even bring the beta button onto the app, if you use the fiddler thing to make it come up, it makes no difference, and I private glitch I had to get the beta signup to come up doesn't work either.
Click to expand...
Click to collapse
That's too bad. I lost beta apparently. I was running TURBO rom and registered then I flashed g950u1 firmware, still had the beta but after 12 hours I never got the update, now I'm back on VZW AQJA firmware and it's gone. Oh well, maybe someone will make a flashforward zip or I cross my fingers and Samsung releases this sometime early next year
Greetings!
I have (2) unlocked Pixel 2's (not rooted) and neither have seen the OTA update to 8.1. Am I the only one experiencing this or are others still waiting for the push? I'm fully capable of grabbing and installing the new images but wanted to see how Google handles these. It seems a bit weird that this has been released but not pushed.
Thoughts?
The pushing out is always done in phases, with just a few getting it in first few days then a larger-scale rollout after that. Some have received it without taking any action themselves, but I think the majority haven't yet.
Large Hadron said:
The pushing out is always done in phases, with just a few getting it in first few days then a larger-scale rollout after that. Some have received it without taking any action themselves, but I think the majority haven't yet.
Click to expand...
Click to collapse
Ok.... Thank you. This confirms it isn't that i need to be too concerned with. A phased approach is better in catching problems early on without impacting majority.
Yeah it will take some time to arrive (totally random). If you want to rush this you have two options:
Option a) Download the full OTA and upload it using ADB from the PC to the Android Recovery.
Option b) Now that there's an official OTA from 8.1 DP2 to 8.1 stable. You can try enrolling into the beta, after doing this, there's a chance you receive the OTA to 8.1 stable because Google roll outs the OTA to all the enrolled people when released. If you receive the OTA to 8.1 DP2 unenroll before applying the OTA and keep waiting.
Sent from my Pixel 2
Will it come to rooted phones? And will I lose root after applying the OTA?
Sent from my [device_name] using XDA-Developers Legacy app
I received my Pixel 2, two days ago and after going through the usual setup, I was offered 8.1 update(size a little over 1GB). Phone came with September patch out of the box. From my previous experience, it may take up to 2 weeks to get the update, but average about 5-7 days.
Large Hadron said:
The pushing out is always done in phases, with just a few getting it in first few days then a larger-scale rollout after that. Some have received it without taking any action themselves, but I think the majority haven't yet.
Click to expand...
Click to collapse
thesebastian said:
Yeah it will take some time to arrive (totally random). If you want to rush this you have two options:
Option a) Download the full OTA and upload it using ADB from the PC to the Android Recovery.
Option b) Now that there's an official OTA from 8.1 DP2 to 8.1 stable. You can try enrolling into the beta, after doing this, there's a chance you receive the OTA to 8.1 stable because Google roll outs the OTA to all the enrolled people when released. If you receive the OTA to 8.1 DP2 unenroll before applying the OTA and keep waiting.
Sent from my Pixel 2
Click to expand...
Click to collapse
Thank you. I'm trying to be patient on this one. The only reason that I have questioned it is due to not being able to root my phone as is. I'm suspecting that with a fresh update to 8.1 the process steps will work correctly.
It's funny in that all i want to do is to block ads. LOL
That you again for your insites.
Weird. I own a Pixel 2 yet the December OTA offers an update for the Pixel 2 XL. Has anyone else experienced this? Should I avoid the update?
I got the update, something like ~600 MB. I haven't noticed any differences yet aside from the AR stickers in the camera, which are kind of fun.
I have a question in regards to getting the OTA updates.
I'm in Australia and got my pixel 2 xl on a plan with Telstra as they are the exclusive carrier here. But I use a Vodafone sim in the phone.
Will this cause me to not get the OTA updates?
Way too long time passed, and I'm still waiting. This is pretty annoying. Now I enrolled to beta to get it, but still nothing. -.-
Are OTA updates not possible for unlocked and rooted phones?
Everytime I try to install the OTA 8.1.0, my Pixel2 downloads the update and installation fails with the error message installation problems.
don't bother. 8.1 is trash. the battery has gone to complete crap on this phone now since 8.1
Sent from my Pixel 2 using Tapatalk
Is anyone else still waiting for the December update to be available for OTA download? Google Pixel 3, unlocked, not rooted, not happy. Never waited this long before.
Is it a Verizon phone? Verizon updates are supposed to roll out this week. The update for non-Verizon phones was available last Monday.
I don't get OTA updates on my rooted phone because of root. I don't know if just being unlocked prevents OTA. You can always download the factory image and manually update. The images are at https://developers.google.com/android/images.
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Fat fingers! 1st sentence intended to be "Thank you for the response".
BlackKeys said:
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Click to expand...
Click to collapse
In that case, you will have to apply the update manually. The factory image is at the URL I gave previously. Edit flash-all.bat/sh to remove the -w from the last line in the file so the phone is not wiped.
You could also apply just the OTA manually. The OTA images are at https://developers.google.com/android/ota. I have not done that - I use the factory image method.
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
BlackKeys said:
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
Click to expand...
Click to collapse
You can search for update errors in logcat. See https://forum.xda-developers.com/t/tutorial-how-to-logcat.1726238/ on how to get a logcat. If you did the manual "Check for update" look in the log at the time you did the check. Logs are kept for quite a while, so the info should still be available.
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
dcarvil said:
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
Click to expand...
Click to collapse
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
TonikJDK said:
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
Click to expand...
Click to collapse
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
dcarvil said:
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
Click to expand...
Click to collapse
That has always been there, very sure of that. A lot of us went done that rabbit hole with the Pixel 1 or 2. We never new for sure what it did, but I remember freezing it and had all kinds of connection problems.
Other carriers have those types of things too. They are built into the image and go live when the phone sees what carrier it is on.
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
T-Mobile I'd imagine. Just use Pixel Flasher or https://flash.android.com
I joined the beta program
BladeRunner said:
I joined the beta program
Click to expand...
Click to collapse
How is it? Stable enough to daily drive? I was stuck on the Nov. 22 patch as well until I sideloaded via ADB last night.
Nov 1 is the latest Play System Update afaik, at least thats what the QPR shows....
Google is having problems
This is one of those moments where it's not you it's them is actually true and not gaslighting . Play Updates are not rolling out properly
BladeRunner said:
I have a Pixel 7 Pro purchased through T-Mobile. 100% stock, no modifications. Google Play System update is Nov. 1. I am still on the November security patch. Attempting the system update results in ""Your system is up to date" Is this a google problem, TMobile slow update or a phone problem?
Click to expand...
Click to collapse
Seems you are not alone.
T-Mobile is running way behind on Google Pixel security updates
Timely updates are supposed to be a prime Pixel perk
www.androidpolice.com
Yeah I am on December update very annoyed with Google nothing has changed
Deleted
That sucks and should not be the Pixel experience. I would call T-Mobile and ask them why you are on an old update?
I have had decent updates so far but would be rather upset if I had a security update that was older than other OEM as that is part of the reason for getting a Pixel.
Sign up for Beta and you'll get QPR2 Beta 2. In my experience, it is much more fluid and responsive than previous builds. It fixes the scrolling issues and seems to have improved battery compared to the December update.
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Colchiro said:
My wife's P7 still is on Dec update and says it's up to date. I manually flash and root mine, but not about to go to that work for her phone.
Click to expand...
Click to collapse
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
EtherealRemnant said:
Can't you just adb sideload update.zip without having to even unlock the bootloader?
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Google provides the means to update it yourself manually easily if you're not willing to wait for your turn. Their tools aren't even that complicated to use. I don't understand the big deal when you have manufacturers like Samsung that can take 3-6 months or longer to update between major version releases, Motorola that updates whenever they feel like it and only gives 2 years of major version updates, and OnePlus that's always behind like 2 months in security updates.
Click to expand...
Click to collapse
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Colchiro said:
I could, but it's my wife's phone so I don't want to mess with it. I'd have to pry it out of her hands first.
Click to expand...
Click to collapse
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Also mine show November as last play service update (I'm on the beta). Italian unlocked phone
Nov is the latest still for play system. There wasn't a Dec and Jan hasn't rolled out yet
EtherealRemnant said:
If she's complaining about it, 10 minutes in your hands beats you hearing about it for however long it takes for the update server to decide it's her turn.
Click to expand...
Click to collapse
There's also the indeterminate minutes, if/when something goes sideways...
This is being delayed for un-branded devices as well, such as mine purchased G-Store direct, based on some sort of carrier-block. I'm tempted to go dig through some dev-docs, to see if I can find this (could be an section not published for most, I suppose), but I figure to what end, mostly.
As you mention, easy side-load, but without knowing why this is being blocked for non-TMo (branded, so not gated by their release of their OTA) devices, it's a gamble of sorts...
I just posted in another thread that I think this is an odd situation. I use an MVNO Boost Mobile that uses T-Mobile and I got the update on the 5th. Maybe I got it before they pulled it? Why would they hold the update back to T-Mobile customers but not the MVNO?