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
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.
So 2 month ago, I had registered for the developer Preview of Android 9 on the official website. Got the regular updates until September 1st. Yesterday, we got the official release of the android Pie and I tried to download it. After downloading the 1.4GB update and restarting my phone, it says that the update failed. But when I attempt to check for the latest update, it tells me that I have the latest release and the date the last security patch is on 1st September. Customer care wasn't of any help, so I was hoping you guys would know what's going on here
Cheers
try to clear data of google services framework, restart your phone and check again
Happened to me as well as my cousin who was on Oreo. It shows update failed but we are both on Android 9 with build number 3.22C (0WW_3_22C).
After checking out the new build, there is no change in latest beta and the Android 9 update, I think they have pushed the same ROM with some certifications. All the bugs that was on last beta still persists on this stable build.
On firmware finder is a new EMUI update available, check:
https://pro-teammt.ru/en/online-firmware-database-ru/?firmware_model=WAS-&firmware_page=0
It's available for many variations of the device, however not for was-lx1a c432, which is the device I have at hand atm...
Of course Huawei support doesn't know anything!
Has someone with a fitting variation of the p10 lite received the update already by normal OTA?
I could flash another cust (c55) via HWOTA and everything was fine, except it showed the build as 8.0.0.46 (1HAM) instead of 8.0.0.393...
Hence I reverted via HiSuite to Nougat and updated all the way to 8.0.0.390 from 2019, where it stops for lx1a with cust c432 - which surprises me as I thought that the free EU version (dual/4GB) certainly had it's own build up and running, however no, doesn't look like it...
It should be possible to manually flash the updated partitions via fastboot individually or again use HWOTA again and ignore the wrong build number as THIS most likely will be the very last update for this 3+ years old device anyway.!
Not sure if anyone is still listening here anymore, didn't see any recent conversations here in 4 to 6 weeks I'm playing with this device :cyclops: which is of course kinda normal for aged phones like this one
Edit:
As suggested in this thread:
https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946
My lx1a is in fact a l21a (c432) and firmware is already available, I'll check it out now, however it's still weird as firmware finder usually suggests the right firmware by searching for lx1a, never before I had to look up l21a...
Gonna report about success later on!
Edit2: when initializing the update via dailer it says the update is incompatibile, even though I setup the dload folder according to the guidelines (zip not update.app) and have the correct package L21A_EU - never gonna understand the way Huawei thinks with this...
Forced update doesn't work for same incompatibility reasons!
Edit3: just tried using update.app files instead of zips but no chance, still errors out.
Also tried firmware finder erecovery DNS method but this gives me a "none authorized update", like using the l21a package on the lx1a isn't supposed to work... I'm running out of ideas!
Last Edit:
Nothing worked so I unlocked the Bootloader to use HWOTA8 to update to package (full) L21AC432B394 and it perfectly worked...
Now finally I'm on 8.0.0.394 c432 with July 2020 security patch and little added functionality, kernel was compiled on 15th of July 2020 - 3+ years and a update has been released, that's actually a big surprise considering it's Huawei and a low level device!
Greetings Sam
what do you think of this update? battery life improved with this new kernel? or nothing has changed?
roxkiller said:
what do you think of this update? battery life improved with this new kernel? or nothing has changed?
Click to expand...
Click to collapse
It didn't change anything obvious, same UI, same experience - Huawei today (assistant app) was added, however no one is forced to use it BUT the most important feature in this update for me is the the 1+ year of security patches, remember it's March 19 to July 20 - I mean it's still Oreo but at least up to date on a security level, system, vendor, kernel, pretty much all parts where updated and improved, it even feels little faster but this could also be because of the factory reset I did to flash the update (unlocked and locked the device in order to use HWOTA8)...
If you want details install firmware finder, search for WAS-L and check out the changelog of 8.0.0.394, maybe the link above provides a changelog, don't remember... There is a pretty long changelog, technically this is not only a security update but a functionality update, I just don't remember all aspects of it!
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
hawkerpaul said:
I have been on Android 12 (official OTA) for about 2 weeks now.
A couple of nights ago, I got an OTA message to welcome me to Android 12, and to download the 1.8Gb update.
I've not had any issues with A12, but I look through the Goggle forums, and see many who have, so I went ahead with the update.
I'm on UK EE.
Turns out, this update is a Verizon build.
The first full Android 12 OTA I had:
Baseband: g7250-00147-210811-B-7631450
Build number: SP1A.211105.003
After the "new" update this is now:
Baseband: g7250-00147-210830-B-7686829
Build number: SP1A.211105.002.A1
I went on Full OTA images to sideload my original (and correct) build back on but it refuses, saying that my current version is newer than the one I'm trying to download, and that a "downgrade" is not possible.
My question is, when the December OTA comes through, will my phone automatically get the correct build and get rid of this rogue Verizon build?
Or will I have to decline the update, and do a manual sideload of the new OTA (non-Verizon) build?
Thanks
Click to expand...
Click to collapse
According to the Google Pixel Community Forum this is going to be fixed automatically by the Global December build.
Hi,
I am stuck on android 11 with oneui 3.1. my current version have the security patch from november 2021...
I am up to date according to the phone (OTA)
My current version is RP1A.200720.012.G781USQS6DUJ4
And the service provider version is SAOMC\_SM-G981U\_OYN\_XAA\_QQ\_0006 XAA/XAA/ATT
Does anyone have any idea how I can update my phone ?
phone AT&T if you and the phone are still in the states.
alternatively you can download the latest update and flash it yourself. in that situation though such a big jump would be best starting over and downloading your apps from scratch or at least wipe your cache.
But I'm french and bought it in france (new, not second hand). I never went in the us, and I'm not planning to...
Is there another way? Maybe using a vpn?
I might be willing to flash an update manually but I would like to have ota update in the future...
Edit: Also I have no idea which version to flash manually