On 27 Sep I received OTA update for my unlocked US Note 8: N950U1UESCRH7. The size was 56,28 MB and it only seemed to contain the 1 September 2018 security patch. Other than updates for other models, there were no additional features like VR Emoji or Super Slow Motion...
Later I noticed while searching that the size of the CRH7 update (I believe on Sammobilec.om) supposedly was approximately 3.5 GB. This was a surprise to me.
Just now I am downloading the CRH7 FW Update through SamFirm (which is still working great!) with a size of 3426 MB.
My questions:
1. Is it common that your may not receive the full FW Update through OTA, but only a part (i.c. the security update)?
2. Could it be that I only received the partial/smaller update as I was outside USA while updating?
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.
My AT&T SGS7 edge was updated to 4BRA1 last night. Besides the January 1 Android security patch, does anyone know if there's anything else different I should notice with this update?
Not noticing anything new, although I expect if I dug deeply a few preloaded apps may have been updated. With a 40MB update, can't expect much besides the security patch.
tamanaco said:
My AT&T SGS7 edge was updated to 4BRA1 last night. Besides the January 1 Android security patch, does anyone know if there's anything else different I should notice with this update?
Click to expand...
Click to collapse
Heres what the ATT Update site says: Android device security updates, including Meltdown and Spectre migration patches (on SPLs Jan. 1 or later)
If you ever want to check out the updates, you can always find it here: https://www.att.com/devicehowto/tut...tep_KM1135854?make=Samsung&model=SamsungG935A
Hope that helps...
Can i update from G935AUCS4API2 (6.0.1) directly to G935AUCS4BRA1 via ODIN and will it wipe my data and would you recommend to factory reset if yes then before update or after update?
My Unlocked Note 8 was in the Pie beta and in March, it got 2 updates. I think the final was supposed to get me to the final build of Pie. But since then, checking updates just says I'm up to date.
I'm on N950U1UEU5DSC1/N950U1OYM5DSC1/N50U1UEU5DSC1 Security patch level: March 1, 2019. Kernel version 4.4.153.
No matter how many times I check for updates, nothing is offered.
Actually, the SmartSwitch app installed to my PC worked to just get me to the May 1st update.
So guys I'm on android 10 one ui 2.0 the very first version of it dec 2019
And just decided to get the newer version of 2.0 the jan or feb patch but the ota update comes up with april 2021 update
N960FXXS8FUC4 this is I think 2.5 one ui the very latest version, do Samsung delete older updates off the sever now and just push the latest updates?I'm 17 updates behind I was expecting to be able to update 1 by 1
Instead of being forced to jump to the very latest version in 1 hit
Bump for help guys please help guys this forum Is dead i know due to the note 9 being old but i would really appreciate the help
Maybe I should remake this thread and put it into the s20 section because that forum is not dead?
I don't believe Samsung delete previous OTA updates from their servers.
OTA updates are incremental, in other words each update will apply changes from a specific previous version to update it to a specific newer version.
So for example a recent over the air (OTA) update would be for 8FUC4 to update to 8FUD1, this update would only be downloaded by your phone if it was on 8FUC4, also when the phone reboots to install the update it again checks that the current software is, in this example 8FUC4 and will only install the update if 8FUC4 is the currently installed software.
If you update automatically in this manner then it's one upgrade at a time I believe.
If you want to update in one jump to a particular firmware then you would need to manually download a specific "full firmware " from an independent website such as Sammobile, usually approximately 4Gb in size to your pc and then flash thus full firmware using ODIN software
My phone uk note 9 unlocked doesn't update each fw one at time like I would like ,im currently 17 updates behind and when I go to update via ota its skips all 16 updates and offer me to install the lastest version of android so Samsung must delete the old firmware from the fota servers
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.