I have just received my Nexus S back from Samsung service. They had to replace the headphone jack.
My phone shows the they system as at 2.3 and that no system updates are available.
On boot the Nexus shows the unlocked padlock. Would the unlocked bootloader prevent OTA from being available?
Before I sent the phone in for service I reset the phone to factory defaults. Would that have had anything to do with this?
----
Could it be that 2.3.1 and 2.3.2 have been pulled from the OTA servers and 2.3.3 isn't being pushed out?
Supermighty said:
I have just received my Nexus S back from Samsung service. They had to replace the headphone jack.
My phone shows the they system as at 2.3 and that no system updates are available.
On boot the Nexus shows the unlocked padlock. Would the unlocked bootloader prevent OTA from being available?
Before I sent the phone in for service I reset the phone to factory defaults. Would that have had anything to do with this?
----
Could it be that 2.3.1 and 2.3.2 have been pulled from the OTA servers and 2.3.3 isn't being pushed out?
Click to expand...
Click to collapse
You just have to wait, it'll push eventually. Or search out the thread titled '2.3.3 link' and do it manually.
Sent from my Nexus S using Tapatalk
Sorry if my post was unclear. I wasn't asking about installing the update. I was asking:
Would an unlocked bootloader prevent OTA from updating?
Supermighty said:
Sorry if my post was unclear. I wasn't asking about installing the update. I was asking:
Would an unlocked bootloader prevent OTA from updating?
Click to expand...
Click to collapse
No, it will not.
So if that wouldn't prevent OTA from updating, is my phone not updating to 2.3.2 because 2.3.2 has been removed from the OTA update server?
Thank you.
http://forum.xda-developers.com/showthread.php?t=967953
use the Full ROM link to update to 2.3.3
and yes before you ask. colors will look differently
rename zip to update.zip
put it on sdcard
boot into recovery [vol up + power -> recovery]
flash update
reboot
done.
Supermighty said:
So if that wouldn't prevent OTA from updating, is my phone not updating to 2.3.2 because 2.3.2 has been removed from the OTA update server?
Thank you.
Click to expand...
Click to collapse
no, unlocked bootloader wont stop your OTA. as said already, you just have to wait your turn till google servers ping your device to push the update out. it happens in waves. you could do it manually too, but just wait around and it comes eventually.
Related
Can&How to force SNS check for OTA 2.3.2 update.
Thankyou
You can't. You either get the .zip posted on the thread in General and update manually or you wait.
You can go into settings, about phone, firmware update.
Sent from my Nexus S
kenvan19 said:
You can go into settings, about phone, firmware update.
Sent from my Nexus S
Click to expand...
Click to collapse
that doesnt really force the update, that just installs it if the phone was already presented with the OTA
slowz3r said:
that doesnt really force the update, that just installs it if the phone was already presented with the OTA
Click to expand...
Click to collapse
I thought it forced a check for the update, or at least it did on my Epic.
kenvan19 said:
I thought it forced a check for the update, or at least it did on my Epic.
Click to expand...
Click to collapse
nope, the closest thing you can get to "forcing the phone to get the update" is the
*#*#CHECKIN#*#* method. and even then all the CHECKIN command does is gets the phone to call home to the mothership and say "hi im here"
kenvan19 said:
I thought it forced a check for the update, or at least it did on my Epic.
Click to expand...
Click to collapse
Hard to say. Maybe the difference with your Epic is that the update comes from Samsung and on the Nexus S it comes from Google.
With the NS on both updates so far, I was not able to magically make it appear on my device by using the Settings or the checkin dial code. I think that for those it showed up after checkin, it was just coincidence...
distortedloop said:
Hard to say. Maybe the difference with your Epic is that the update comes from Samsung and on the Nexus S it comes from Google.
With the NS on both updates so far, I was not able to magically make it appear on my device by using the Settings or the checkin dial code. I think that for those it showed up after checkin, it was just coincidence...
Click to expand...
Click to collapse
Perhaps it is the difference in where the update is coming from, I've been running 2.3.1 with CM7rc8 for a few days now don't really plan to update
The way to force the NS to get the update is to download the zip and go into recovery and update it. No root, changing recovery to apply.
1) Download it (Search forums for it.. its in General)
2) Rename to update.zip if it isnt already
3) Put it on root of sd card
4) Boot into recovery (search forums, if you dont know how)
5) Apply update.zip
6) Reboot... you're on 2.3.2
NOTE: The file you are downloading is exactly identical to what you would get from the OTA. So you're doing the same thing. When you get the OTA, you're downloading it from the same source. The URL was received from aLogCat.
Sup guys I got the 5.0 update notification about a week back. I didn't install waiting for some apps I use to be updated. Now that they have the update is gone and my phone says up to date on 4.4.4. I seen the 5.0.1 is coming soon. Did they pull it for 5.0.1?
No. They update people in batches or slots. If you ignore your slot, you have to wait for it to come around again
rootSU said:
No. They update people in batches or slots. If you ignore your slot, you have to wait for it to come around again
Click to expand...
Click to collapse
Wow really I did not know that.
r.storm85 said:
Wow really I did not know that.
Click to expand...
Click to collapse
hi, if you are still interested in upgrading right now, you can always download the image from the official site:
https://developers.google.com/android/nexus/images
after downloading, all you need to do is get to bootloader mode (assuming you already unlocked bootloader), changed the flash-all script so it doesnt wipe everything off your phone (or skip userdata.img)
or use one of the many 1-click program available on xda
I am not waiting for OTA, heeeeellllll nooooooo!!!
Just woke up to another OTA and wondering if anyone has updated yet? not sure if its 5.1.1 or not.
Hard to tell since you don't say what you currently have. Could be the latest 5.02 or something else.
I got it too and installed it. I'm still on 5.0.2
From what I read it's just a small security update and to allow roaming in Puerto Rico. Nothing big
Phone info after the update:
It allows roaming in Puerto Rico and fixes reactivation lock and that's it really
Sent from my SM-G920V using Tapatalk
I would be careful updating if you have root as the kernel is dated June 17th.
Well I have OTA's blocked to prevent them. I don't see a reason to let this one install.
Official changelog from Verizon. Build number: VRU2AOF1.
Anyone know what they changed with RL? How does that affect you if you've had legit trouble turning the feature off?
How do I manually turn that off?
What app(s) do I freeze to turn off OTA? I'm using Titanium, and i just don't want to fudge it up.
I'm guessing System Updates 1.0? Is it just that, or am I missing it?
So I am rooted and I accidently hit it. I'm stuck on the Verizon red logo after boot..
Nevermind, force reset and phone booted up. The security update said it has been updated but I am still rooted.
nvertigo said:
So I am rooted and I accidently hit it. I'm stuck on the Verizon red logo after boot..
Nevermind, force reset and phone booted up. The security update said it has been updated but I am still rooted.
Click to expand...
Click to collapse
Did you root with RL on? I had trouble with RL and am scared to root it now and even more so to take the update.
What a useless update, just give us 5.1.1 already Verizon.
nvertigo said:
So I am rooted and I accidently hit it. I'm stuck on the Verizon red logo after boot..
Nevermind, force reset and phone booted up. The security update said it has been updated but I am still rooted.
Click to expand...
Click to collapse
odd considering it usually wouldnt work at all if youre rooted..
and of1 as it stands is most likely not able to be rooted
Sent from my SM-G925V using XDA Free mobile app
segadennisis76 said:
What app(s) do I freeze to turn off OTA? I'm using Titanium, and i just don't want to fudge it up.
I'm guessing System Updates 1.0? Is it just that, or am I missing it?
Click to expand...
Click to collapse
Either delete the following folders or freeze the apks with TB, I prefer to delete them. Removing the following apks will free you of OTAs and most of the annoying pop-ups.
SDM.apk system/app (OTA Updater)
SecurityLogAgent.apk system/app (Samsung Security Pop Up)
SPDClient.apk system/priv-app (Samsung Security Policy Update)
No way in hell am I updating my phone for that whack ass update.
I wonder if any of our ROM dev's will even debase.
I mean I guess the kernel / radio change may make it worth it but I will wait for 5.1.1.
musicfreak190 said:
No way in hell am I updating my phone for that whack ass update.
I wonder if any of our ROM dev's will even debase.
I mean I guess the kernel / radio change may make it worth it but I will wait for 5.1.1.
Click to expand...
Click to collapse
Same here, I'm waiting for 5.1.X and a safe way to root it. I have no plans at all to update my ROM to the new update.
If you value root....
If you like having root DO NOT update to OF1. It looks like rollback is prevented in this update... Thanks Verizon!!
Lifetrip718 said:
Did you root with RL on? I had trouble with RL and am scared to root it now and even more so to take the update.
Click to expand...
Click to collapse
??
Even though the instructions clearly say to turn OFF RL before rooting... but if you have OF1, you can't root it anyway, or at least not yet. PingPong method is no longer valid on that OTA and further.
Misterxtc said:
If you like having root DO NOT update to OF1. It looks like rollback is prevented in this update... Thanks Verizon!!
Click to expand...
Click to collapse
Wow.. Preventing roll back? Closing up root vulnerabilities? This is more than just a security move. Honestly is some scumbag stuff going on here. I don't want to leave Verizon but they are making it hard. They spend all this time working on some stupid ass update meanwhile Spring GS6 just got 5.1.1..
If they spent less time worrying about users flashing older Stock images and Rooting and working on the latest software I would have nothing to say.
I really hope Ping Pong can Root this soon. Flashing backwards prevention will only prevent people who are already on OF1 obviously but I feel bad for them.
Hello all,
I just received a new Nexus 5 with Android 4.4.2 (KOT49H) bought online.
The vendor, at my inquiry, replied that it was new and not refurbished or regenerated.
The OTA says "up to date" and won't update to lollipop. (I haven't touched anything yet from first boot)
Can't figure out what's wrong. Anyone has any idea?
PS: I checked with cpuz to see if the hardware is correct and it doesn't seem to be a chinese replica. (lol)
thank in advance.
I just bought a new nexus 5, unlocked it and flashed the 6.0 factory image. Not point in waiting for OTAs.
Now, you could download each OTA from the OTA thread in General and sideload them all in turn but that's just long...
EddyOS said:
I just bought a new nexus 5, unlocked it and flashed the 6.0 factory image. Not point in waiting for OTAs.
Now, you could download each OTA from the OTA thread in General and sideload them all in turn but that's just long...
Click to expand...
Click to collapse
The point is that it won't update to 4.4.3 neither... and it seems strange.
Anyone could point to a cause?
Could be the OTAs aren't actively being pushed. As I said, you could maunally download them and sideload them one at a time to get updated OR just flash the 6.0 factory image and be done with it
EddyOS said:
Could be the OTAs aren't actively being pushed. As I said, you could maunally download them and sideload them one at a time to get updated OR just flash the 6.0 factory image and be done with it
Click to expand...
Click to collapse
Fair enough, 6.0 it is
Hey all,
I've restored my girlfriends pixel using the original android 8 image. (It was using PureNexus before). However, she just got the update notification (september update?) but it doesn't do anything when she taps it. The phone should not be rooted, as I used the original clean factory image.
Any suggestions? I've looked at this thread https://forum.xda-developers.com/pixel/help/taking-september-security-update-rooted-t3672586 and so am prepared to download the latest update and remove the "-w" part, but shouldn't it allow her to take the update anyway? Am I going to have to always do this every time they release an update?
Thanks!
It should work, so long as you restored everything to stock - system, bootloader, recovery (dunno if radio matters).
If it's not working most likely there's something custom hanging around somewhere...
I believe it will also fail to update if the bootloader is unlocked. Not sure if you have a VZW device but that's how it works for them. I just update by flashing the full factory image, not an OTA file. Removing the -w will retain user data.
FernBch said:
I believe it will also fail to update if the bootloader is unlocked.
Click to expand...
Click to collapse
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
jss2 said:
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
Click to expand...
Click to collapse
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
joeyfeffer said:
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
Click to expand...
Click to collapse
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
TonikJDK said:
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
Click to expand...
Click to collapse
Oh gotcha gotcha.
Weird issue though I couldn't get update to the latest image. I was only able to flash the bootloader and radio. When I tried updating the image it said it couldn't find some of the files. Do I still need to keep the line as "fastboot -w update" when updating the image? won't the "-w" do the wipe?
Nevermind I figured it out. I guess I was inputting the wrong command.