Greetings, I have a Project Fi Android One X4. Two days ago I went back to Project Fi Oreo stock after being rooted in order to receive the OTA. I received the January, February, and March security updates. But once I attempt to get the April one with 8.1, the system says I am up to date. I attempted to sideload the April OTA but got the message many get about not being able to mount. I know that these updates are not rolled out all at once, but I see many here in the forum already got it. Is there any way I can force the OTA? Thanks in advance for the help!
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
jfalls63 said:
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
Click to expand...
Click to collapse
Same issue for me. The ADB sideload/SD card problem doesn't make sense.
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
ptn107 said:
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
Click to expand...
Click to collapse
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
rczrider said:
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
Click to expand...
Click to collapse
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Thanks for all the responses! I see that I am not the only one with this issue. I think that like jfalls63 said, of we don't get the update in the coming days we will have to wait for the full firmware release. It is not convenient since I want to root and wanted to do it in 8.1, but there is not much we can do about it if we cannot find an alternative.
QWZR II said:
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Click to expand...
Click to collapse
You're right; I haven't had any reason to do either since the update and it wasn't until after I posted that I saw another thread mentioning this issue. Sure enough, same is true for me.
Still, the update was pushed to one of our phones only a couple of days ago, so if they pulled it, it's only been within the last 72 hours or so.
I'm experiencing a similar thing (https://forum.xda-developers.com/moto-x4/help/oreo-8-1-update-stuck-loop-t3788293), so this seems to be a prevalent problem.
When I have time, I'll go through the Moto forums and see if anyone has any helpful information.
I'm on Fi and I received the 8.1 update just fine. I haven't unlocked my bootloader yet to root it, but otherwise I'm on the gravy train. Once they release a full sized firmware I plan to reflash to get my space back, and then root.
The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.
Related
I've got a Nexus 6 with Verizon Wireless. It is purely stock: I have never rooted or modified the phone in any way other than accepting the standard OTA updates pushed out by Google/Verizon.
I've been patiently waiting for the OTA update to upgrade my phone to Nougat, but I haven't seen any updates in over a month. My phone is currently running MOB31H (6.0.1) which, according to the Google Factory Images page is the security update from October 2016. However, according to the same page there have been two security updates in November (MMB31C and MOB31K), and there have been two versions of Nougat released since then (NBD90Z and NBD91P). My phone has not seen any of these updates, despite repeatedly checking for updates via the settings menu.
I've got a few questions along these lines:
1) I've seen rumors about trouble with Nougat, which suggests maybe Verizon/Google have been delaying a widespread roll-out. However, I have not seen anything posted recently about this (latest reports are from early October), and what I did see seemed focused on other phones (not the Nexus 6). Are there any known issues with Nougat running on the Nexus 6 that would make me want to delay upgrading manually?
2) Is it unusual for my Nexus 6 to still be running 6.0.1 with the October security update? Shouldn't it have at least received the November security updates? Have others experienced this issue?
3) If I download the OTA directly from Google and sideload the update, will this disable the automatic OTA updates in the future? I'd like to at least apply the November 6.0.1 security updates to keep my phone secure.
4) If I want to update my phone to Nougat manually, can I simply download the OTA for Nougat and follow the instructions Google includes for sideloading the OTA update? Or do I have to download the entire 7.0 factory image and install that image? I have experience installing the factory images (I have a Nexus 10 that I've had rooted for a while, so I've gotten good at installing the factory images whenever a new image is released) but it is still a bit of a pain and I would prefer the OTA updates for my phone if I can.
4a) If I can update via the OTA, can I pick the latest OTA (NBD91P), or do I have to go incrementally (install NBD90Z first then update to NBD91P)?
5) Only tangentially related question: I've noticed that Google has included the month and year on more recent factory images, but is there any way to determine the exact date that an image was released? For example: I see there are two November OTA updates for Nexus 6, how can I tell if MOB31K was released this morning vs. November 2? If it was released this morning that may explain why I haven't seen the update yet, but if it was released November 2 I would be surprised I haven't seen the update yet.
Thanks in advance for any help.
1. Verizon has no control over updates on this device. That said, no major issues with the stock ROM.
2. Not unusual at all. When I received my N6 earlier this year it stopped updating after the latest Android 5.0.1 update. I had to flash an Android 6.0.1 image manually.
3. No.
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
5. No way to tell outside of paying attention here, since someone will inevitably announce the release of the latest version. Of course, once you've installed the latest image, OTA updates should continue as usual if you don't modify the firmware like most of us do.
Thanks for the helpful reply! One quick follow-up:
Strephon Alkhalikoi said:
4. Both methods should work. However, in upgrading from Android 6.x to 7.x installing the latest full factory image rather than the OTA I feel will give you less headaches. Just get the latest and flash it.
Click to expand...
Click to collapse
I will likely follow your advice regarding updating from the full factory image instead of the OTA. My main limitation is my two-factor authentication. Because I haven't rooted, it is a pain to transfer some of that from one device to another (in some cases it requires disabling two-factor authentication and re-enabling it on each site, and I have at least 12 website that are using two-factor authentication on my device). I need to make sure that I don't accidentally lose the authentication tokens.
If I get lazy, or just want to "risk" using the OTA: Can I use either OTA image (the one from October or November) to upgrade from 6.0.1 to 7.0? Or does the one from October apply a full update and the November is just an incremental update intended to by applied to an existing 7.0 build?
Both are full updates. I'm not sure as to how well your current data will transition over to Android 7.
I would look into finding a means of backing up your authenticator.
Wife and I just upgraded to Pixel XL. Wife was behind on updates on her Shamu, so I initiated the ota update to 7.0. Update went fine, but when I checked the build number, it is NBD91L.
I didn't think that was possible. The only reference I could find online to this build is that it was an iteration of AOSP leading to NBD91P. No sim card was in the phone at the time of update.
Not really concerned by it, and I know I can just download the ota zip for 91P and sideload it, I just thought it was weird.
Has anyone else had this happen?
I received the same OTA version on my Nexus 6 Shamu.
I was on 7.0.0 NBD90Z, Oct 2016 (I flashed from googles factory images) then, a week or so back I got an OTA for November security update and it gave me NBD91L.
I thought was strange also since it isn't even listed on the google factory image page......Not sure why we both have that image....Anyone else know why this image exists but isn't listed and we weren't given the 91P update? I am on Verizon (is this a vzw specific update?)
I was even thinking of wiping and moving to 91P just to be safe, but wanted to see if anyone else had 91L before I did so....
Also, I am sure the Dec security patch is only days away (probably just wait for that then wipe and start fresh with the new image)
Drootz! said:
I received the same OTA version on my Nexus 6 Shamu.
I was on 7.0.0 NBD90Z, Oct 2016 (I flashed from googles factory images) then, a week or so back I got an OTA for November security update and it gave me NBD91L.
I thought was strange also since it isn't even listed on the google factory image page......Not sure why we both have that image....Anyone else know why this image exists but isn't listed and we weren't given the 91P update? I am on Verizon (is this a vzw specific update?)
I was even thinking of wiping and moving to 91P just to be safe, but wanted to see if anyone else had 91L before I did so....
Also, I am sure the Dec security patch is only days away (probably just wait for that then wipe and start fresh with the new image)
Click to expand...
Click to collapse
My Nexus 6 is still on this build. I didn't think much of it because I gave the phone to my mother in law. I figured she would update when she sees the prompt but she hasn't received one since this build. Pretty disappointing. I know I can side load it but I shouldn't have to after this length of time.
Sent from my Nexus 6P using Tapatalk
Just got my OTA update notification. Update went smoothly (sorry, forgot to check file size before updating. Confirmed BlueBorne vulnerability is fixed.
Not sure if this is unique to me, but post-update, my phone is now telling me my SD card is unsupported and asking me if I want to format. Really hoping to avoid backing up a 200GB card, formatting and restoring this weekend. Not sure if anyone else is having this issue too or if just my luck to have to deal with, but just a warning out there to those who may decide they want to unmount their SD cards before updating.
FWIW, my device seems to be running just a bit smoother after a day of use. No noticeable change in battery life. Pleased with the update so far.
quick newbie question, I have the G935A , fully stocked, but using it on a Canadian network, I was told I won't get the update via OTA so I installed Smart Switch, but it also says my device is up to date which has the May security patch installed (that's what it came with when I bought it last month). Any idea where I can find just the OTA patch and update the phone ?
bestjsg said:
quick newbie question, I have the G935A , fully stocked, but using it on a Canadian network, I was told I won't get the update via OTA so I installed Smart Switch, but it also says my device is up to date which has the May security patch installed (that's what it came with when I bought it last month). Any idea where I can find just the OTA patch and update the phone ?
Click to expand...
Click to collapse
If you aren't running on an AT&T network, you might seriously consider switching to the U firmware. Of course, Samsung conveniently forgets the U firmware exists too, so that might not gain you a whole lot at the moment.
I have the U firmware and I've been checking for updates, but nothing (I'm on the August security patch). Is there a way to force the update or use Odin or side load it? My phone was originally built for the Sprint network, then the previous owner flashed it to work on AT&T. I was not able to get any updates (was stuck on the May security patch). I used Odin to put the U firmware on it and then got 3 security patch updates after that.
caferacer73 said:
I have the U firmware and I've been checking for updates, but nothing (I'm on the August security patch). Is there a way to force the update or use Odin or side load it? My phone was originally built for the Sprint network, then the previous owner flashed it to work on AT&T. I was not able to get any updates (was stuck on the May security patch). I used Odin to put the U firmware on it and then got 3 security patch updates after that.
Click to expand...
Click to collapse
The U firmware always lags the carrier firmware. August is sadly the current date for the unlocked devices for now.
All I had to do was be patient. I got the newest update (4BQJ5 - November security patch) this morning.
So wonder why I have never gotten a single update pretty much since I got this phone 6 months ago. When i got it the first thing i did was unlock the bootloader and rooted it.
So I saw there was a June update of this year. Well I decided to go and look at my phone and oh look! June 1 update! yea from 2017. So when I do an update I get a "Check for update was not available at this time. Try again later"
I don't have any of the update apps blocked with Titanium either. Any help and\or ideas would be great.
On my Turbo it would still get updates, but fail because of TWRP at least and i would flash stock recovery just to update then flash twrp back on.
Thanks
Magisk Manager v16
Rooted
Unlocked
Recovery - TWRP 3.2.1-r16
Build: NPS26.116-45
Stock ROM
I installed the November Update in 5th and few seconds ago a new update showed up with 1.82GB.
Did anyone has the same, I am a little bit nervous to install.
I had this same issue with my wife's p4a 5g. in the process of updating mine to the Nov security update (finally got around to opting out of the beta so I could update it) and then I'll see if mine does the same thing.
UPDATE: Finally got the security update installed and my 4a 5g also has the upgrade notification. After doing some digging around, it seems that Google accidentally pushed the VZW specific update to all Pixels (the update in question is this one: 12.0.0 (SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs)). I will most likely ignore this update if that's the case. (took almost an hour to optimize apps for the security update, not looking forward to doing that again right now lol).
same here..lets see if the build number will be sam
Hersfeld said:
I installed the November Update in 5th and few seconds ago a new update showed up with 1.82GB.
Did anyone has the same, I am a little bit nervous to install.
Click to expand...
Click to collapse
Same here.
Just 2 days ago i did a clean install of nov 5 image SP1A.211105.003
I received the update the same day pixel 6 was launched,today received another update to install 12.i paused it until be sure whats going on
Mine installed ...
Previously : SP1A.211105.003
After : SP1A.211105.002.A1
According to their release details
Pixel 4a 5G: Android 12 – SP1A.211105.003, SP1A.211105.002.A1 (Verizon, Verizon MVNO), SP1A.211105.004 (Telstra, Optus, Vodafone AU) – Factory image – OTA (2) (3)
Same thing is happening on the Pixel 5 and 6. I'm currently on the ,003 firmware on my Pixel 5, even did a clean factory install. Still getting an update notification. It would be nice if Android would define the version of the update...
If you are rooted, DO NOT take the automatic update. If you do, you will have to wipe to re root.
clark71822 said:
I had this same issue with my wife's p4a 5g. in the process of updating mine to the Nov security update (finally got around to opting out of the beta so I could update it) and then I'll see if mine does the same thing.
UPDATE: Finally got the security update installed and my 4a 5g also has the upgrade notification. After doing some digging around, it seems that Google accidentally pushed the VZW specific update to all Pixels (the update in question is this one: 12.0.0 (SP1A.211105.002.A1, Nov 2021, Verizon, Verizon MVNOs)). I will most likely ignore this update if that's the case. (took almost an hour to optimize apps for the security update, not looking forward to doing that again right now lol).
Click to expand...
Click to collapse
But is working fine with the Verizon firmware?
Good day; would a factory reset be a solution to revert back to the global version ? Thanks !
Saturnin97 said:
Good day; would a factory reset be a solution to revert back to the global version ? Thanks !
Click to expand...
Click to collapse
No.
Use the Android Flash Tool to install the global version. Data wipe/factory reset should not be necessary.
Update no longer available for me. Seems like Google realized their mistake.