Hi,
I am a proudly possessor of a Galaxy nexus.. I have a stock ROM 4.02 and I haven't my update to 4.04 yet.
I tried to force the OTA update killing the process (Framework) but still nothing.
I not want to flash another ROM loosing my data.
Thank you all in advance.
You know there are apps out there to back up and restore all of your data. Also I know I saw the update for you to manually download it from Droid life. Just Google that and I think it told you on the sitehow to do it with out bring rooted and not losing your data.
Sent from my Galaxy Nexus using Tapatalk 2
Updates are rolled out in BATCHES. Not everyone receives the update AT THE SAME TIME.
A few thousand one week, a few thousand the next.
My friend is still on 4.0.2 and his is supposed to be updated FIRST.
Just wait.
Flashing is fun!
sidus86 said:
Hi,
I am a proudly possessor of a Galaxy nexus.. I have a stock ROM 4.02 and I haven't my update to 4.04 yet.
I tried to force the OTA update killing the process (Framework) but still nothing.
I not want to flash another ROM loosing my data.
Thank you all in advance.
Click to expand...
Click to collapse
Install "Android System Info" app from market and see in System > BuildInfoOS > Product, if your product is "yakju", then it's a matter of time till you receive OTA update notification. But if the product code is other than "yakju" (e.g yakjujp, yakjuxw, etc.), then you might need to wait longer to get OTA update.
Though you can always convert your product to "yakju" from any other build if you want. But keep in mind that this process will wipe your data. So make a backup before you dive into that.
If you change your mind and wanna flash to "yakju", the following thread might help you.
http://forum.xda-developers.com/showthread.php?t=1626895
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Capture the URL for it ?
Here is the link: https://ota.googlezip.net/packages/ota-api/google_marlin_marlin/d872269d3aff80d3b7f81d28c972d1d59f36f8f6.zip
(I'm not allowed to link to it directly due to my account age - sorry!)
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
This happened to me. I have a Verizon version dePixel8 and sideloaded E build a few days ago. Today I got the update message and it upgraded to K in about 2 minutes.
Gather this is for the Verizon models?
Ohber1014 said:
I just received an OTA notification on my pixel XL to update to 7.1.2, although I'm already on 7.1.2. I have a Google store device, and I flashed the current 7.1.2 build N2G47E when it became available. The OTA says it is 17.6 MB and I am using it on Verizon. What would this update even do?
Click to expand...
Click to collapse
It's an update specifically for the Verizon Pixels. It contains a number of bug fixes and improvements according to the release info. A simple Google search will locate more info including the specifics of the bug fixes and improvements.
So this OTA will update my Google store device to the Verizon build? Weird. I'll just flash the whole build later.
So, after applying this update - what build does it show?
Just flashed the OTA. It does indeed update Google Store devices to the Verizon build of 7.1.2, NHG47K. Looking in the OTA zip, the update may only affect the system and vendor partitions.
I had this happen after I flashed the January build I think it was. I have a play store pixel on vzw and it was trying to update my regular stock rom the vzw-specific version. It sounds like if you're on vzw service then you'd benefit from their improvements. I'm waiting for beans to update his rom before I update from 7.1.1. I just hope it includes these vzw changes.
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
alsip1023 said:
It would be nice to know what changed. I, for one, would rather not be bothered with the Verizon version of the OTA. I don't want any of the apps, bloat, etc that they're surely going to try pushing. There is a reason I bought from Google and not Verizon.
Click to expand...
Click to collapse
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
hub1 said:
The only difference between the VZ model and the Google model is the VZ model has a locked bootloader. If you put a VZ Sim in either one it will install 3 apps that you can uninstall completely, not just disable.
Click to expand...
Click to collapse
I was referring to the difference between the 7.1.2 builds, not the phones.
alsip1023 said:
I was referring to the difference between the 7.1.2 builds, not the phones.
Click to expand...
Click to collapse
So was I.
TonikJDK said:
I put it on my Google phone since it has a different radio for Verizon. There is no extra bloat or anyrhing, just like there wasnt when the phone first came out. The image is from google, the updates are from Google. None of that is going to happen. Except for the bootloader VZ is playing by Google's rules on this phone.
Google makes carrier specific images all the time. This is no big deal.
Click to expand...
Click to collapse
Thanks for playing the guinea pig. Good to know nothing obvious was added in terms of bloat.
With that being said, that Pixel update is handed to Verizon to "test and certify". Then it is sent to the Pixels. Verizon only promised to not delay updates. They may still add apps, bloat, etc... Should they so choose.
Added information:
Google Store Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the right (as in enabled) but is overall greyed out after "K" update.
Verizon Purchased Pixel XL: Unlocked since 7.0.1, shows unlocked, and the bar is flipped to the left (as in disabled) but is overall greyed out after "K" update.
Not sure what this means. If anything, I found it interesting. Once it's unlocked, unless I submit a relock, it can't be relocked by OTA right?
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
gordonlw said:
Found this thread in a search. I have a playstore pixel xl unlocked bootloader, stock root on verizon. I sideloaded 7.1.2 build N2G47E. After sideload the system update still shows. Before re-rooting I tried to install it but it always comes back "Couldn't update, installation problem". I verified that the sideload installed and am in fact on N2G47E.
I even reset the phone, locked the bootloader and it still failed. I have since unlocked & re-rooted running stock. Update still shows and still fails. I've turned off auto updates so it only happens if I manually check and try to install. Other than this the phone is running fantastic.
Should I sideload the verizon ota build? I know I'll loose root but want to make sure bootloader stays unlocked and can re-root after moving to Verizon build. Can anyone confirm this? Post above seems to confirm the bootloader stays unlocked but doesn't mention root. Btw to root I am not flashing twrp, just fastboot to it and flash su.
Click to expand...
Click to collapse
Hello,
You bought a Google version, you are fine. You can sideload Verizon's OTA if you are on Verizon's network. Otherwise, no benefits...
Even true Verizon's unlocked Pixel owners, as long as they don't lock bootloader, it will stay unlocked, no matter what they flash FYI.
You can install SU with fastboot boot twrp as well.
Cheers...
Worked great thanks!
Guys, I'm reading mixed articles and opinions online and I'm returning to Android after a long time with iOS. The only incentive for me here would OTA updates the day of release. I'm thinking of getting the phone from Verizon and wondering if their updates arrive the same day as Google releasing them, or is there a delay?
Kind regards
Prasad
You will always have a little delay before yout get the OTA, because they are released by stages. I always download the OTA image from google and sideload it via stock recovery. Its the fastest way and you don't need an open bootloader or something.
hells
The way I get the OTA updates, is, I pop out my Sim, clear data from Google play store and Google play services, and then reboot. When I check for an update it will say up to date, but when I put my SIM back in and check again about 30 seconds later the update is already installing.
Only downfall to this method is you have to set up android pay again.
Otherwise you can download the OTA from googles website but it's a pain to do, and it's a big download.
The check for updates issue has been fixed in Google Play Services v12.2.09 or later which is still in beta but I believe a stable version will be released in March. I checked within 1 hour after the March security update was released and had the update available for download. I am running the beta GPS currently.
There is no delay. The pixel series receives their updates directly from Google and can update the day google releases.
Title says it all, is there a non root way to hurry up the update? I haven't had the popup to update android and was hoping there's a way to check for updates
Settings/system I believe, to check for updates or you can download and sideload the update.
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Sideload the OTA
NippleSauce said:
Aside from pressing "System Update" under the "System" panel in the Settings menu, the only other way to push the update forward would be doing it manually (using adb through command prompt).
But the probable reason as to why you aren't getting an option to download the update yet is due to your phone carrier. When Google releases new factory images for the next update build, the phone carriers take the image and modify it first, usually to add some bloatware apps into the mix. It's at that point where they will send the update out and you will get the notification to download and install the update. That's how they can get their apps/bloatware onto a bunch of phones. It's basically a practice of coercion that most phone carriers use to force out more app installations of their own, crummy apps/bloatware lol.
This next part is just a guess, but I'm assuming that they do this in an attempt to pull in a little more money. It's a real shame =/.
Click to expand...
Click to collapse
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
pcriz said:
Umm I might be wrong but wouldn't that mean there is a downloadable version of the "carrier" build with these modifications. I know some months google does release carrier builds but they drop the same day as the none carrier ones. And my understanding was that usually those builds exist to better utilize the network capabilities of a specific network.
But this month for instance has one build for the 6 models. If what you discribe is true then the builds pushed to carrier models would have a different hash check.
Click to expand...
Click to collapse
You're pretty much correct here. I suppose that Google was a bad example to use. But essentially, the carrier builds allow the applicable carrier to also push apks through when you pull the update OTA. They're not necessarily packaged within the factory image - so I had some horrible word choices in my initial post as they don't really modify the image lmao. But (when looking at the older builds) if you just install the stock build instead of flashing one of the carrier builds, then you won't have to worry about any carrier apps being pulled in along with your OTA update.
But heck, if you're rooted and want to maintain root (and are thus manually updating whilst having OTA disabled), then you wouldn't have to worry about this at all, haha.
Samsung phones were a better example of this, as whenever I would do an OTA update on my S21U, it would also install around 4-5 T-Mobile bloatware apps. But if you manually installed the stock image, that wouldn't happen anymore when updating OTA.
I currently have my bootloader unlocked and ProtonAOSP installed.
I am selling the phone and want to put it back to stock. What is my best route to get there?
simply flash the factory images.
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
EDITED: to add, be certain you sign out of your google account on the device before resetting, this will avoid any FRP after you sell.
Mustardman666 said:
I currently have my bootloader unlocked and ProtonAOSP installed.
I am selling the phone and want to put it back to stock. What is my best route to get there?
Click to expand...
Click to collapse
Android Flash Tool
flash.android.com
And then lock the bootloader.