Related
My lame 4 year old Android finally died (well, actually more like the touch screen went epileptic), and I'm going to pick up a Note 3 from a VZW store in a couple hours.
(Even more insane, I'm going to drop my month-to-month unlimited data plan for the carrier subsidy and re-up with BigRed for 2 years - but that's a topic for another time)
Anyway, what I wanted to ask was this: is there any reason that I should insist that the VZW rep just leave the phone in the box rather than activating it in the store (and risking an OTA update)?
I'm comfortable doing the activation later if there is a credible reason to take the phone home and check it's bootloader version info before I boot it normally for the first time. (I suspect that the Note 3 inventories are moving at a good clip, so a unit bought from a VZW store might have recent firmware anyway).
Apologies for the lame question; I had 4 candidate phones in mind (Sammy S4, LG G2, HTC One) and didn't have much time to become an expert in the current state of affairs about rooting all of them... other than to note that Samsung has recently become much more restrictive in the past couple of months (e.g. with the S4/Knox stuff).
tia
The most current version is MJE. Which you can root with Kingo app. MI9 was what the phone had when it first came out. Which was rooted by designgears with de la vega. Then mJ7 was released and we had to use Kingo. So since the second update everyone has had to use kingo.
So if you want to root that's what your going to have to use.
bftb0 said:
My lame 4 year old Android finally died (well, actually more like the touch screen went epileptic), and I'm going to pick up a Note 3 from a VZW store in a couple hours.
(Even more insane, I'm going to drop my month-to-month unlimited data plan for the carrier subsidy and re-up with BigRed for 2 years - but that's a topic for another time)
Anyway, what I wanted to ask was this: is there any reason that I should insist that the VZW rep just leave the phone in the box rather than activating it in the store (and risking an OTA update)?
I'm comfortable doing the activation later if there is a credible reason to take the phone home and check it's bootloader version info before I boot it normally for the first time. (I suspect that the Note 3 inventories are moving at a good clip, so a unit bought from a VZW store might have recent firmware anyway).
Apologies for the lame question; I had 4 candidate phones in mind (Sammy S4, LG G2, HTC One) and didn't have much time to become an expert in the current state of affairs about rooting all of them... other than to note that Samsung has recently become much more restrictive in the past couple of months (e.g. with the S4/Knox stuff).
tia
Click to expand...
Click to collapse
My reccomendation is this 1. Stay far away from the Smartwatch they will try and sell you 2. Ignore their offered Insurion Warantee, and go with Square Trade (Just Google it)
No issues with rooting and custom ROM's are doable. Gopher it man!
If it's not too late, get the 6 GB plan for $30 instead of the 2 GB for $30 they will try to out you on. If you do not do it at the time you buy the phone there is no other way to get it. If you already have the 2 GB plan it is impossible to get onto the 6 GB one.
The only way you can get it is when you are upgrading and loosing unlimited. The system will not let you get the plan if you are not about to loose unlimited.
Here's a more detailed thread on Howard forums: http://www.howardforums.com/showthread.php/1816163-6-GB-for-30
@jack584
Thanks. I gave it a bit of thought; the other alternative to the Max 6GB plan is a 2 GB "loyalty" data plan for $60/mo. Someone coming off of a month-to-month unlimited plan has 14 days to waffle about their decision.
Phone is rooted. (Kingo + safestrap + SuperSU replace)
For grins (post-rooting), I started the OTA and let it download (phone came out if the box with MJ7). When the download finished, I pulled the OTA file out of /cache/fota/ and then "took" the OTA. Naturally it failed I guess I'll see if I get nags now...
I am new to rooting mainly because I never wanted to void the warranty on my device. Ever since the latest update that trashed my phone with bloatware and slowed it down, I decided to take the plunge. While digging around and trying everything I could I discovered that the update that trashed my phone is the update that wont allow me to root it!!! Has anyone figured out a way to get around Verizon's lock and do you think it will be possible?
best guess (from a novice at best) is that with the S5 being almost two years old, most dev's have gotten tired of continually trying to work around samsung and verizons frustrating vice grip on the bootloader and root.
and went and bought a moto x pure.
and lived happily ever after
I've had my Nexus 6p for 1 week and I have not received any OTA update notifications. I'm still running MDA89D (latest is MDB08M??)
I'm on Verizon (with a sim from my Note 4) and have not done any modifications to the phone yet (bootloader, root, etc)
Am I being too impatient? According to the factory images page, (https://developers.google.com/android/nexus/images?hl=en) I'm already 3 releases behind??
Same for me, however I had to go get a new nano Sim from the Verizon store. I'm also not rooted/unlocked and have not received one update.
Sent from my Nexus 6P using Tapatalk
2 phones here (one for me, one for my wife). Mine received an update but hers did not. Interestingly enough, however, mine was up and running without the sim card in it for a while prior to putting it in...I just don't understand how Verizon could be blocking anything...I mean the update comes through Google, not Verizon.
Maybe if there's continued reports of it I'll try stealing my wife's phone and removing the sim card to see if it immediately then gets an update. Sure is odd...
ohlin5 said:
2 phones here (one for me, one for my wife). Mine received an update but hers did not. Interestingly enough, however, mine was up and running without the sim card in it for a while prior to putting it in...I just don't understand how Verizon could be blocking anything...I mean the update comes through Google, not Verizon.
Maybe if there's continued reports of it I'll try stealing my wife's phone and removing the sim card to see if it immediately then gets an update. Sure is odd...
Click to expand...
Click to collapse
Interesting. My nephew got his update the day he got the phone. He was running only on wireless because he did not have his Verizon sim card yet. I'm going to try pulling my sim and leaving it on wireless a while. I'll report back if I find anything interesting. Thanks!!
I completely set up my 6p on wifi for a day before getting my nano Sim installed, so no update for me in that respect either.
Sent from my Nexus 6P using Tapatalk
Definitely some interesting results here. However, the nexus' updates are different in that OEM's and carriers are kind of "cut out" of the loop....the updates come from Google unless I'm completely missing something. So, my guess would be that maybe, like most updates in general, Google releases them in waves based off SN or IMEI numbers or whatever. I would say chances are good that in the next week or 2 it's hit a lot more devices. Time will tell!
I've been on wifi only since I've gotten my 6p two days ago and no update here. @ohlin5 might be right.
I haven't inserted vz sim yet at all. I received K update at first boot and then M update next day.
I am a bit confused because the help page from Google about system updates mentions that updates should come within 2 weeks of release, but could take longer depending on your carrier.
Not sure if my screenshot image is uploading or not. The quote from the help page is,
"Android updates: Nexus 4, Nexus 5, Nexus 6, Nexus 7, Nexus 9, and Nexus 10 devices get the latest version of Android directly from Google. These devices will receive Android version updates for at least two years from when the device first became available on the Google Store.
Once an update is available, it can take up to two weeks for it to reach your device. Based on your carrier, it may take longer than two weeks after release to get an update."
So is Verizon involved or not? It's very confusing. And a bit disappointing to be so far behind on releases for a new Nexus. I've had my 6P for 5 days now on Verizon, but no update for me either. Still on MDA89D.
kappadappa said:
I am a bit confused because the help page from Google about system updates mentions that updates should come within 2 weeks of release, but could take longer depending on your carrier.
Not sure if my screenshot image is uploading or not. The quote from the help page is,
"Android updates: Nexus 4, Nexus 5, Nexus 6, Nexus 7, Nexus 9, and Nexus 10 devices get the latest version of Android directly from Google. These devices will receive Android version updates for at least two years from when the device first became available on the Google Store.
Once an update is available, it can take up to two weeks for it to reach your device. Based on your carrier, it may take longer than two weeks after release to get an update."
So is Verizon involved or not? It's very confusing. And a bit disappointing to be so far behind on releases for a new Nexus. I've had my 6P for 5 days now on Verizon, but no update for me either. Still on MDA89D.
Click to expand...
Click to collapse
That's interesting....I wonder if it maybe has something to do with an update needing to be approved by a carrier, first? I honestly don't know that much about the process...I'm not sure if it just comes straight from Google, goes from Google to carriers for carrier certification and THEN Google ships it to those phones on that carrier, or if it just gets passed to the carrier and on to the phones on that carrier from the carrier themselves. Long story short it once again confirms that no wireless company sucks worse than Verizon. I suppose I should be happy that I even have a nexus with them but I can't bring myself to be grateful for them. Has anyone who hasn't gotten an update tried pulling your sim card and booting the phone up after that to see if it triggers any updates to come through? I feel like that information might help in troubleshooting.
ohlin5 said:
... Has anyone who hasn't gotten an update tried pulling your sim card and booting the phone up after that to see if it triggers any updates to come through? I feel like that information might help in troubleshooting.
Click to expand...
Click to collapse
I tried pulling the sim and rebooting but still no update.
So ive had mine on Verizon for a week now from the moment i turned it on. I didn't know there was any updated available and i have been waiting for Wug NRT to update his toolkit for the N6P. i just noticed he did about an hour ago unlocked my bootloader and when it powered back up it had an update so i accepted it and when it rebooted im now running MDB08L ?! I haven't seen this version and on the Wug toolkit there is no option for it. Is this maybe an official build for Verizon? Has anyone else see this version or are running it on there device?
I had my 64 gb for a few days only on wifi and never had an update either
Never had an update either after two weeks with both the 5x and the 6p on Verizon. Ended up flashing the factory images myself since it is a nexus after all ☺
I've had mine for a few days now with no update...on Fi! I'm sure it's just Google staggering the deployment. For some reason, I always seem to be at the tail end of the staggering.
Sent from my LG-v410 using Tapatalk
You could always flash if you are impatient.
Sent from my Nexus 6P using Tapatalk
1barlog17 said:
So ive had mine on Verizon for a week now from the moment i turned it on. I didn't know there was any updated available and i have been waiting for Wug NRT to update his toolkit for the N6P. i just noticed he did about an hour ago unlocked my bootloader and when it powered back up it had an update so i accepted it and when it rebooted im now running MDB08L ?! I haven't seen this version and on the Wug toolkit there is no option for it. Is this maybe an official build for Verizon? Has anyone else see this version or are running it on there device?
Click to expand...
Click to collapse
.
No Verizon doesn't build it's all Google. I believe the current complete build is K.
OTA Updates L & M I believe are the new Monthly Security Updates. (Update site doesen't include info on update content)
As L & M were released on same day expect to got from D to K to M.
That's what I think I know anyway. lol
It's an algorithm based on IMEI. You'll get it eventually. The carrier doesn't have anything to do with it.
I will agree it seems to be taking longer this time than usual and I usually got them late on my N5. I'm still on old build as well.
Sent from a 128th Legion Stormtrooper 6P.
Mine updated this afternoon!
[hfm] said:
It's an algorithm based on IMEI. You'll get it eventually. The carrier doesn't have anything to do with it.
I will agree it seems to be taking longer this time than usual and I usually got them late on my N5. I'm still on old build as well.
Sent from a 128th Legion Stormtrooper 6P.
Click to expand...
Click to collapse
Actually the carrier does have something to do with it. They have to approve updates for phones on their networks, even if there is nothing for them to do with it. Better off just flashing them through twrp.
I've been on Android since the Original Moto Droid days. Rooted every one. My phone is an 11 and I was still running MOAR rooted but it was getting wonky. I went ahead and flashed the stock 6.0.1 tar and gave up my beloved root. Having the old unlimited data plan still, the wifi hotspot is a must with me. I made sure foxfi worked on the wife's stock phone before I flashed mine. It does. Interestingly though, I am able to use no lock screen at all on my phone running foxfi. This is with trusted credentials installed. If I ever have to send this back for replacement on extended warranty, maybe I'll get a 13 come back and get back in to the game. There are some pretty nice phones on the market and I'll probably upgrade in the coming year. Maybe I'll research and see at that time if there are any other VZW brands that are unlocked.
ADIOS FOR NOW !!
Just trying to gauge rate/actuality of this occurring. I haven't yet received an update OTA since getting my Pixel 2 mid October. I finally sideloaded the Dec update, but am intent on waiting to see if the January update ever comes via OTA push.
sdsurferbob said:
Just trying to gauge rate/actuality of this occurring. I haven't yet received an update OTA since getting my Pixel 2 mid October. I finally sideloaded the Dec update, but am intent on waiting to see if the January update ever comes via OTA push.
Click to expand...
Click to collapse
I received the pushed OTA, though it failed since I have TWRP, Magisk, and Snoke Kernel.
If your impatient just flash the factory image or the OTA.
Diesel_Jeremiah said:
I received the pushed OTA, though it failed since I have TWRP, Magisk, and Snoke Kernel.
If your impatient just flash the factory image or the OTA.
Click to expand...
Click to collapse
When did you get it?
And yes, I'm impatient. I'm impatient for it to work like it's supposed to. I don't want to have to sideload updates every month.
sdsurferbob said:
When did you get it?
And yes, I'm impatient. I'm impatient for it to work like it's supposed to. I don't want to have to sideload updates every month.
Click to expand...
Click to collapse
I have two Pixel 2 phones. On the second one it came in two days ago.
Google is going to push the OTAs in batches. Other than flashing the Factory Image or OTA I don't know what to tell you other than wait?
Tap the system update button?
Diesel_Jeremiah said:
I have two Pixel 2 phones. On the second one it came in two days ago.
Google is going to push the OTAs in batches. Other than flashing the Factory Image or OTA I don't know what to tell you other than wait?
Tap the system update button?
Click to expand...
Click to collapse
Tapping update doesn't help (yet, which has been covered extensively). You answered the question, thanks.
Anyone else?
sdsurferbob said:
Tapping update doesn't help (yet, which has been covered extensively). You answered the question, thanks.
Anyone else?
Click to expand...
Click to collapse
Yeah I received mine. Bought from VZW. I had just flashed September to roll all the way back. Maybe that's why.
I received the OTA in India..
Anyone captured the OTA link for the P2? As in the 40MB update, not the full OTA you can download from Googles OTA site.
I have still not got the OTA in India..... Google should really fix this.
Sent from my Pixel 2 using Tapatalk
nickporwal said:
I have still not got the OTA in India..... Google should really fix this.
Click to expand...
Click to collapse
Same here.. (from Belgium)
Don't get it here in Germany.
Gesendet von meinem Pixel 2 mit Tapatalk
My wife's Nexus got it on Cricket (AT&T) my business Pixel got it on AT&T, and my Google store bought pixel2 on Verizon not available yet. This has happened to me ever since I put a Verizon simm in it, was fine on AT&T. Now I give up after 30 days of no OTA and reset phone then it comes in. a real PIA to put all the passwords and accounts back. If it isn't pushed to me by next billing cycle I'm done with Verizon. My belief is since they sell them, when you buy a phone from Google direct and it sees a Verizon simm, it hands over updating to Verizon. Verizon says no, not true, but nobody can explain why then a reboot removes the authentication for Verizon and it OTAs perfect.
MLT2004 said:
My wife's Nexus got it on Cricket (AT&T) my business Pixel got it on AT&T, and my Google store bought pixel2 on Verizon not available yet. This has happened to me ever since I put a Verizon simm in it, was fine on AT&T. Now I give up after 30 days of no OTA and reset phone then it comes in. a real PIA to put all the passwords and accounts back. If it isn't pushed to me by next billing cycle I'm done with Verizon. My belief is since they sell them, when you buy a phone from Google direct and it sees a Verizon simm, it hands over updating to Verizon. Verizon says no, not true, but nobody can explain why then a reboot removes the authentication for Verizon and it OTAs perfect.
Click to expand...
Click to collapse
I thought maybe you were onto something, so I shut down, removed my Verizon SIM (phone was bought direct from Google), started back up, tried checking for updates a few times, still nothing, rebooted, repeat, still nothing.
I never got a notification to install the January security update. I restarted my phone earlier today and right when it started up I got a notification about finishing system update. Took a look in settings and apparently I now have the January security update. Looks like it downloaded/installed automatically. I am on Verizon with the Unlocked Pixel 2 from the Google Store, I am on build number OPM1.171019.013.
Not sure how this happened. I got a notification and had to manually click "Install" for the December update. Wasn't auto-updates a feature of Oreo they discussed a while back, being able update while the phone is on and when you restart it finishes the update?
At this point, half a week after release, I'd be wary of reading anything into the pattern of who has got it and who hasn't (obviously people who still haven't had previous updates are a different matter). We know that OTAs are released in batches, with very small fraction getting it in first couple of days, then larger but still small fraction, before finally rolling out generally, and it's claimed that it's random who gets it when. With the small number of (self-selecting) replies here I doubt we can make any meaningful test of whether it truly is random.
FWIW I just got it a few minutes ago (restarted and the notification popped up). UK, non-carrier model. Remarkable how long a very small update takes to install though...
Just received the update! So random...
I just downloaded the 48 megabyte January security patch via OTA download to my Pixel 2 purchased from Google. It took a really long time to install, like at least 30 minutes. This may be why people that sideloaded the OTA had a slow down while setup processes were running in the background, after the update my phone is just as snappy as ever.
Got mine today, though while I happened to be on a wifi network that was identifying my location as Mountain View, as opposed to Portland where I actually am...
sdsurferbob said:
I thought maybe you were onto something, so I shut down, removed my Verizon SIM (phone was bought direct from Google), started back up, tried checking for updates a few times, still nothing, rebooted, repeat, still nothing.
Click to expand...
Click to collapse
I should have said "factory refresh", not reboot. pulling simm never worked either. Yesterday it came in, FIRST TIME EVER since owning Pixel 2 on Verizon. Curious though, it NEVER notified an update was available, nor that it had downloaded one, I had simple rebooted my phone and told me installing an update. Never let me refuse it or delay it. Weird.
Diesel_Jeremiah said:
I have two Pixel 2 phones. On the second one it came in two days ago.
Google is going to push the OTAs in batches. Other than flashing the Factory Image or OTA I don't know what to tell you other than wait?
Tap the system update button?
Click to expand...
Click to collapse
Except this doesn't apply if you rooted your phone, which is the case for most of xda's pixel 2 userbase