When is the OTA for JB coming to Verizon?

[Codec]

My phone is rooted so I don't work with Wi-Fi update.

 

[quickaudi]

nobody knows, including Verizon

 

[Turdbogls]

My phone is rooted so I don't work with Wi-Fi update.

what?

if you are rooted you can already run 4.2.1. i have been on it for a couple weeks now i think. there are CM10.1 and AOKP as well as some fully stock 4.2.1 builds available for Toro (the VZW Gnexus)

backup your apps with titanium
download the ROM and GAPPS package
boot into recovery
make a backup
wipe data/factory reset
install ROM
install GAPPS
reboot
Profit

 

[indianajonze]

what fully stock 4.2.1 builds do you recommend?

 

[mogelijk]

Although I'm sure you meant when 4.2 will be available from Verizon, I will point out that Jellybean has already been released (4.1.1) by Verizon for the GNex. As someone using 4.2 on a Galaxy Nexus, I can't think of much reason to want 4.2 over 4.1 right now.

 

[Codec]

Although I'm sure you meant when 4.2 will be available from Verizon, I will point out that Jellybean has already been released (4.1.1) by Verizon for the GNex. As someone using 4.2 on a Galaxy Nexus, I can't think of much reason to want 4.2 over 4.1 right now.

The OTA update had been released? I never got it, only the Wi-Fi.

 

[NSutherl]

what fully stock 4.2.1 builds do you recommend?

mmuzzy's stock 4.2 JOP40D build is the smoothest 4.2 ROM out there.

The OTA update had been released? I never got it, only the Wi-Fi.

If you got an update over wi-fi it is still the OTA. Didn't you say you are rooted? If you are rooted, there's a 95% chance you have a custom recovery installed (ClockworkMOD, TWRP, etc), in which case you won't receive an OTA.

 

[Codec]

mmuzzy's stock 4.2 JOP40D build is the smoothest 4.2 ROM out there.



If you got an update over wi-fi it is still the OTA. Didn't you say you are rooted? If you are rooted, there's a 95% chance you have a custom recovery installed (ClockworkMOD, TWRP, etc), in which case you won't receive an OTA.

i have ClockworkMOD, what do i do?

 

[NSutherl]

i have ClockworkMOD, what do i do?

See here. Click "How to flash a ROM via ClockworkMod custom recovery"

 

[nj02vette]

There is no 4.2 OTA update for Verizon GNex models, only 4.1.

If you want 4.2, the only option right now is to install a custom ROM.

http://forum.xda-developers.com/showthread.php?t=1762846
If you got an update over wi-fi it is still the OTA. Didn't you say you are rooted? If you are rooted, there's a 95% chance you have a custom recovery installed (ClockworkMOD, TWRP, etc), in which case you won't receive an OTA.

Unlocking, Rooting or having custom recoveries installed won't prevent you from receiving the OTA. In fact, as long as you've made no direct system changes, it won't even prevent you from installing the OTA.

I've installed many OTAs over CWM with no issue.

 

[Crashumbc]

There is no 4.2 OTA update for Verizon GNex models, only 4.1.

If you want 4.2, the only option right now is to install a custom ROM.


Unlocking, Rooting or having custom recoveries installed won't prevent you from receiving the OTA. In fact, as long as you've made no direct system changes, it won't even prevent you from installing the OTA.

I've installed many OTAs over CWM with no issue.

Your experience is contrary mine and many others then. You may get a notification of a OTA if your rooted. But I've never had one succeed to install with a custom recovery.

 

[Ravenwjf]

Your experience is contrary mine and many others then. You may get a notification of a OTA if your rooted. But I've never had one succeed to install with a custom recovery.

Same, I have never had an OTA work with CWM installed on my Galaxy Nexus. I am rooted and unlocked but no custom recovery on my N10 and I can install the OTA no issues.

 

[NSutherl]

Unlocking, Rooting or having custom recoveries installed won't prevent you from receiving the OTA. In fact, as long as you've made no direct system changes, it won't even prevent you from installing the OTA.

I've installed many OTAs over CWM with no issue.

An unlocked bootloader will not prevent you from receiving OTA updates, but having a custom recovery will. Maybe what you did was install the update via CWM with a flashable zip made from OTA?

Usually what happens is someone who has a locked bootloader with stock recovery will receive the OTA from Verizon, grab the source files, and post it on XDA. Then devs will take the OTA files and turn them into a flashable zip so those who have an unlocked bootloader and custom recovery installed can receive the update.

 

[nj02vette]

An unlocked bootloader will not prevent you from receiving OTA updates, but having a custom recovery will. Maybe what you did was install the update via CWM with a flashable zip made from OTA?

Usually what happens is someone who has a locked bootloader with stock recovery will receive the OTA from Verizon, grab the source files, and post it on XDA. Then devs will take the OTA files and turn them into a flashable zip so those who have an unlocked bootloader and custom recovery installed can receive the update.

Admittedly, I could be completely wrong.

I installed many OTA updates on my older rooted Droid X with CWM installed....but with a locked (encrypted) bootloader. It was never an issue. But with the bootloader locked, perhaps recovery was done differently.

Similarly, many OTA updates on my unlocked/rooted GNex, but with no CWM installed.

So that may be the difference.

 

[NSutherl]

Admittedly, I could be completely wrong.

I installed many OTA updates on my older rooted Droid X with CWM installed....but with a locked (encrypted) bootloader. It was never an issue. But with the bootloader locked, perhaps recovery was done differently.

Similarly, many OTA updates on my unlocked/rooted GNex, but with no CWM installed.

So that may be the difference.

While I can't speak for the DX, the fact that you can accept OTA's on your GNex makes sense, since you don't have a custom recovery installed. A custom recovery (not an unlocked bootloader) is one of the red flags that OTA's check for when determining if your phone is eligible for the OTA.

 

[Ravenwjf]

So I have had my Nexus 10 since right before Thanksgiving and it came with 4.2 and had the 4.2.1 update right out of the box. So..... Around a month and a half 4.2.1 has been out. I am hoping Verizon hasn't just quit on doing updates already. I haven't ROM'd yet because I have actually been enjoying stock but if no update by the end of February I think I am finally going to go with Shiney. I wish there was some word. I know that Verizon is several updates behind now.....

 

[quickaudi]

VZW is so behind that they (Moto?) released (on accident?) a 4.1.2 update for the Droid Razr/Maxx that would have put it officially ahead of the VZW Nexus.

Whiskey. Tango. Foxtrot.

 

[DWasilew]

There's really no point in waiting on a VZW update that will probably never come. If you're already rooted and want a stable stock ROM, there are plenty that are better now than the offical OTA (if it ever gets pushed) will be. If you don't like it, you can always go back to your stock backup.

Also, read up on the file directory changes that occur when going from 4.1 to 4.2 and have your recovery up to date. That way you're not freaked out when you upgrade and your backups are "missing".

 

[nomarsgirl]

I suspect we have seen the last official update for the VZW Nexus. Verizon is not good about supporting the devices on their network, but won't relinquish the control to the manufacturers. They are much more interested in selling new phones than supporting the ones already on their network.

When you buy a new phone from Verizon, you need to either be willing to live with it the way it is for the life of the contract, or Root/ROM it. If you do get an OTA update, consider it a bonus.

Mine shipped with ICS and I got the official JB upgrade in late September (I think). I don't really care about the newer JB. I'll probably start to feel some regrets when phones running KLP come out. I'm sure I'll root the phone when/if KLP-based ROMS are out for the VZW Nexus.

 

[trophynuts]

I suspect we have seen the last official update for the VZW Nexus. Verizon is not good about supporting the devices on their network, but won't relinquish the control to the manufacturers. They are much more interested in selling new phones than supporting the ones already on their network.

When you buy a new phone from Verizon, you need to either be willing to live with it the way it is for the life of the contract, or Root/ROM it. If you do get an OTA update, consider it a bonus.

Mine shipped with ICS and I got the official JB upgrade in late September (I think). I don't really care about the newer JB. I'll probably start to feel some regrets when phones running KLP come out. I'm sure I'll root the phone when/if KLP-based ROMS are out for the VZW Nexus.

I think you'll see another official update from VZW for the G Nex.

Also lets not forget that VZW doesn't and isn't capable of getting their hands on the Iphone update process. Apple handles it 100%. Google could do the same if they wanted to spend the money to pay VZW to look the other way. Or whatever black magic voodoo it is that Apple did to achieve that.

 

[kinfolk248]

I think you'll see another official update from VZW for the G Nex.

Also lets not forget that VZW doesn't and isn't capable of getting their hands on the Iphone update process. Apple handles it 100%. Google could do the same if they wanted to spend the money to pay VZW to look the other way. Or whatever black magic voodoo it is that Apple did to achieve that.

Apple tells Vzw and whoever else, this is the way it is if you want our product and since everyone wants apple products on the shelf the have to go for it. Its the same way the big boys in agriculture tells walmart this is the price of the product deal with it.

I wish google would boss up and put up some type of regulations on android, something, anything. No phones less than 2 versions behind, updates must go out within 6-8 weeks, something!!!!!!!

 

[jhawkkw]

Apple tells Vzw and whoever else, this is the way it is if you want our product and since everyone wants apple products on the shelf the have to go for it. Its the same way the big boys in agriculture tells walmart this is the price of the product deal with it.

I wish google would boss up and put up some type of regulations on android, something, anything. No phones less than 2 versions behind, updates must go out within 6-8 weeks, something!!!!!!!

Basically due to the success that the iPhone had on AT&T, Apple felt they had the right to dictate all terms about their device, even on Verizon's proprietary network. Verizon apparently thought it was worth it and yielded to Apple's demands. I do wonder how things would be these days if Verizon continued to tell Apple to shove it.

 

[kinfolk248]

Basically due to the success that the iPhone had on AT&T, Apple felt they had the right to dictate all terms about their device, even on Verizon's proprietary network. Verizon apparently thought it was worth it and yielded to Apple's demands. I do wonder how things would be these days if Verizon continued to tell Apple to shove it.

Thats an easy answer, verizon wouldnt have it...

 

[mogelijk]

Apple tells Vzw and whoever else, this is the way it is if you want our product and since everyone wants apple products on the shelf the have to go for it. Its the same way the big boys in agriculture tells walmart this is the price of the product deal with it.

I wish google would boss up and put up some type of regulations on android, something, anything. No phones less than 2 versions behind, updates must go out within 6-8 weeks, something!!!!!!!

The problem is, Google isn't the one that needs to do it (other than the Nexus). While Google does make Android, it is the phone manufacturers that create the drivers for the individual phones, as well as compiling the Android source code to run on their processor. In Apple's case, since there are technically the manufacturer (despite subbing it out to Foxconn), they update both the OS and the drivers.

Basically, it is companies like Samsung that need to take control from Verizon (no GS4 for you unless we control the updates...). Unfortunately, I can't see Samsung or any of the other manufactures willing to do that -- they don't see how it adds to their bottom line, if anything it slows down people from buying new phones to get the new OS. Though maybe if Motorola did it (since they are owned by Google), if they stole sales from other manufacturers it might force them into providing the updates.

 

[kinfolk248]

The problem is, Google isn't the one that needs to do it (other than the Nexus). While Google does make Android, it is the phone manufacturers that create the drivers for the individual phones, as well as compiling the Android source code to run on their processor. In Apple's case, since there are technically the manufacturer (despite subbing it out to Foxconn), they update both the OS and the drivers.

Basically, it is companies like Samsung that need to take control from Verizon (no GS4 for you unless we control the updates...). Unfortunately, I can't see Samsung or any of the other manufactures willing to do that -- they don't see how it adds to their bottom line, if anything it slows down people from buying new phones to get the new OS. Though maybe if Motorola did it (since they are owned by Google), if they stole sales from other manufacturers it might force them into providing the updates.

Yea i know, thats why i say google should stop putting old versions of android open like it is. 4.2.1 is the current version, so 4.1 could be the oldest that samsung, lg, whoever could use as a platform. Stop letting people use 4.0 at stage late in the game...

there are ways to unify android put i dont think google really cares. They are just selling and making profits, but down the line I see this coming back on them!