anyone know if google pulled the OTA update due to issues.? its been three weeks now and my stock nexus 4 hasn't received it. i bough it directly from google so i though they would be the first devices updated. i don't want to update it manually with the OTA files in case there are any issues with it
phrozenstare said:
anyone know if google pulled the OTA update due to issues.? its been three weeks now and my stock nexus 4 hasn't received it. i bough it directly from google so i though they would be the first devices updated. i don't want to update it manually with the OTA files in case there are any issues with it
Click to expand...
Click to collapse
If you sideload the OTA it's exactly the same as if Google had pushed it to you. Just fyi. I'm not sure if they canceled the ota but I've been on lollipop since they released the ota files with no issues after a sideload.
No, they didn't. I received OTA a week ago, as have some of my friends (Serbia).
after hearing about nexus 4 issues like with texting i wanted to wait until google delivers it to my phone, i already loaded the OTA on my nexus 4 2012 so it would be easy for me to do
Related
Hello,
I bought a Nexus S (Vodafone) yesterday and noticed that I am on 2.3.1. I have checked for updates OTA but it says that I am up to date.
I found a site, which describes how to upgrade to 2.3.2 but I'm wondering if there is anyway to debrand so that in future I will get all OTA updates from Google?
I searched for it and found this thread for the Nexus One:
http://forum.xda-developers.com/showthread.php?t=798602
and wonder if it also applies to the Nexus S? Also, he mentions passimg file. What is a passimg file? Is it contained in the update.zip??
Thanks,
Keith
Welcome to the club. You can manually update but there is no reason we should have to. Google should have taken care of all it's Nexus owners, making sure that all of the OTA updates have been pushed out. Sadly, this seems not to be the case. As a Nexus One and a Nexus S owner the bleeding edge OTA's are what attracted me to the platform . I find myself continually questioning the value of the Nexus platform if Google continues to let customers fall by the wayside. I don't want to hear any crap about patience and time. Google has had ample time to push the OTA to everyone at this point.
Keithod said:
Hello,
I bought a Nexus S (Vodafone) yesterday and noticed that I am on 2.3.1. I have checked for updates OTA but it says that I am up to date.
I found a site, which describes how to upgrade to 2.3.2 but I'm wondering if there is anyway to debrand so that in future I will get all OTA updates from Google?
I searched for it and found this thread for the Nexus One:
http://forum.xda-developers.com/showthread.php?t=798602
and wonder if it also applies to the Nexus S? Also, he mentions passimg file. What is a passimg file? Is it contained in the update.zip??
Thanks,
Keith
Click to expand...
Click to collapse
I have Nexus S from Vodafone[CPW] too, since yesterday. Mine was too on 2.3.1, OTA update didn't work so updated manually. I don't think there is any branding at all. Didn't see any logos or anything. Which one do you have, Super Amoled or Super Clear LCD?
try checking in: *#*#2432546#*#*
but theres really no problem with manual update.. place the update.zip on the sdcard root directory then boot into recovery..
Now on 2.3.3
Just updated to 2.3.2 then to 2.3.3 and everything went okay!
I tried the *#*#checkin#*#* code Albertogg but it didn't seem to work for me. It said "checkin succeeded" but still no updates.
And Kave, it says i9020 so I think that means S-AMOLED...
Thank you everyone for your input.
I stuck on 2.3.2 too. I try to check-in many times
Hi,
I would like to know about new Android Security update for Nexus 4.
Please let me know from where we can download it.
Apparently they have sent the patch out to all OEMs' in the last few days according to news sources. But some how must of forgot to send themselves a copy
meangreenie said:
Apparently they have sent the patch out to all OEMs' in the last few days according to news sources. But some how must of forgot to send themselves a copy
Click to expand...
Click to collapse
There isn't an update to download it will either be pushed to your device by Google or more than likely included in the next OTA which is rumored to be dropping anytime. The only way to be safe is to not install any apps that do not come from the playstore, i.e. turn off install apps from unknown sources in your system settings.
kzoodroid said:
There isn't an update to download it will either be pushed to your device by Google or more than likely included in the next OTA which is rumored to be dropping anytime. The only way to be safe is to not install any apps that do not come from the playstore, i.e. turn off install apps from unknown sources in your system settings.
Click to expand...
Click to collapse
Thanks for reply...
I thought Nexus 4 will be first to get any update as its Google...
Same case with Google Maps 7 is not available in Play store.
[email protected] said:
Thanks for reply...
I thought Nexus 4 will be first to get any update as its Google...
Same case with Google Maps 7 is not available in Play store.
Click to expand...
Click to collapse
Google has had the code to repair the exploit since about March so not sure why they are taking so long to get it out. Probably because it's not really all that big an issue as long as you only download apps from a trusted source. They sent the code to fix the exploit to their OEM's about a month ago and they updated their own version of Android are in the process of sending the update out to the various carriers. It will probably still take the OEM's a few more months to update all their phones and some older phones I'm sure will never be updated.
Guess what guys, the Cyangenmod team implemented the security patch to their rom already.
Sent from my Nexus 4 using Tapatalk 2
Is any one else still waiting on the march ota update coming through? I have a 6p and a Nexus 9 and neither have received the update yet but I see a lot of people have received it.
Further more I have also registered my n9 for the android n beta 2 days ago and have still not received an update for that either.
Does Google just hate me and not want to send updates to my house or are other people waiting also?
Both phones are stock and never rooted. I'm in the UK
Just sideload the OTA, and you won't have to wait any longer. Link to the 6P OTAs...
Official Stock Firmware
http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
I was running the N preview via OTA. I opted out of the beta and instantly got the OTA to go back to Marshmallow. Once I booted into Marshmallow, I got the OTA for the March build.
Sent from my Nexus 6P using Tapatalk
For reasons that haven't been specified yet, the builds labeled MOB30D have been removed from the Nexus Factory Image page.
I uploaded it on the mirror, so, you can download if you want flash it. [Nexus 7 (2013) Wi-Fi]
https://mega.nz/#!15kGUSYA!6mKmEy1oZldroLtBDgOepWBt25xTqeVc7jC9TJ1Efyg
Weird they pulled it. Whats up with that. I didn't flash it. Notice any problems or super-secret files left in there?
I haven't flashed it either. I assume the found a bug.
Sent from my Nexus 6P using Tapatalk
I flashed it but I not noticed any issues so far
I still haven't flashed it but have been listening to some Mobb Deep. MOB30D!
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Candy[MAN] said:
Anyone having issues with this release? Debating whether or not to flash my unit. I notice that the Nexus 7 WiFi has binary files available with a MMB29X release.
This is interesting....found this link on Sprint's website: https://community.sprint.com/baw/message/1038775
Almost seems like MMB30D was suppose to have been the mid-March security release.
Features/Enhancements:
•Revision of March Android Security Update to include new fixes
For those who flashed this MMB30D onto the Nexus 7, what is the date in ABOUT PHONE. Is it April 1 or April 2?
Click to expand...
Click to collapse
2 april
The last image for the Nexus 7 2013 razor that I see is still MMB29V.
So much for Google being responsive in getting security updates out. I would have thought that after making a big deal out of that mid-March kernel fiasco that they would have fixed and re-released the images for the three devices that they pulled for whatever reason on Monday. It's now the weekend and no explanation or update from Google. Why am I not surprised?
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
what make you guys think this is for flo razor if sprint say : Nexus 5 software update - version MOB30D
and when we download, it says RAZOR !?! WTF !
Displax said:
Build "MOB30D" again available for download via direct link.
On site, it still not displayed.
https://dl.google.com/dl/android/aosp/razor-mob30d-factory-15169856.tgz
Click to expand...
Click to collapse
Was this link not working before (after it was pulled) or was it just taken off the site?
Candy[MAN] said:
Was this link not working before (after it was pulled) or was it just taken off the site?
Click to expand...
Click to collapse
All direct links stopped working after ~20 minutes after hiding from site.
And today they start working again, but still not displayed in the list.
I just factory defaulted my Nexus 7 (2013) device and installed this new factory image (MOD30D). Once I logged into my Google account, I got an email that I successfully logged into a Nexus 7 (2102).......2012??? WTF?
I wonder if there is/was an issue with the image's fingerprint where it would think that the 2013 model is actually a 2012 model.
Builds MOB30D for both models Nexus 7 2013, finaly, available in the list.
https://developers.google.com/android/nexus/images
These builds are uploaded again to nexus pages. And include a lots of bug fixes.
Just flashed new image with WUG, rerooted, flashed Xposed and ElementalX
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
DaveImagery said:
I'm confused. I flashed MOB30D when Google first posted it, but then took it down. Now MOB30D is back up. Do I need to re-lash it?
Click to expand...
Click to collapse
They probably took it down for some reason first time. Flash again.
htb2050 said:
They probably took it down for some reason first time. Flash again.
Click to expand...
Click to collapse
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
DaveImagery said:
These monthly updates while obviously a good thing, there also kind of a pain in the ass. Every month I have to flash the new image, re-root the phone, use Titanium Backup, to go in and delete enough from sys partition, to flash Xposed, followed by flashing my beloved ElementalX kernel. Unless there is some way to streamline all that, a noob like me isn't aware of. Presumably we got just a couple weeks till the May security update anyway. I'll wait.
Click to expand...
Click to collapse
Use WUG no wipe option, then root with WUG. Not all that difficult.
Sent from my Nexus 7 using XDA-Developers mobile app
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
Unless he is willing to manually update, there are only a few options. One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA. The other is borrowing a SIM from a different carrier for a few minutes, trying to update the system in settings, and then switching the SIM back. This will sometimes trigger an OTA. Finally, a more drastic measure would be to do a factory reset. Other than that he will just have to wait.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
NoobInToto said:
You could try checking if his phone is enrolled in android beta program. If it is, you could try unenrolling from the beta program, and the phone may get further update (only a mild possibility, but it has happened atleast once to a n6p I know).
Alternatively, if you want the update badly, you could download the full ota image and do a ADB sideload via stock recovery. Pretty simple process, works with locked bootloaders.
Click to expand...
Click to collapse
I'm in the same boat ?
v12xke said:
One would be try enrolling and then un-enrolling in the 8.0 beta program. Others have reported soon after un-enrolling they received an OTA.
Click to expand...
Click to collapse
Didn't work.
andMego said:
My friend has a Nexus 6P and hasn't yet gotten Oreo, any idea why? He hasn't done any modifications like root to the device. He is still on the August security patch. He checked for updates many many times. He even called Google and TMobile.
Click to expand...
Click to collapse
My wife's Nexus 5X on T-Mobile just got Oreo a few days ago. I'm still waiting (but hopeful) for my Nexus 6P update. Neither of us were rooted or beta.
I was stuck on the August security patch too. I didn't realize it until September and then October rolled around.
I'm also on TMobile. I ended up just ended up manually updating. Worked without issue.