1) Original android version is 7.0 (with security updates to April 2017)
2) Security updates July 2017
3) Security updates Nov 2017
4) Updates to Android version 8.0 (Feb 2018)
If I"m to do a hard reset in March 2018, will my LG G6 be in 1), 3) or 4)? and if its in 3) or 4), can I get it back to 1)?
Thanks.
Whatever ROM you will be with any security update available at that moment, hard resetting the phone will delete any data, not ROM configuration. So you phone will be at vanilla state, like you've just unpacked it and turned it on for the first time, but with the ROM which was already installed right before the reset.
You can get back to 1) but there is no sense in doing so, old ROM, less fixes, everything outdated.
Got it, thanks!
Related
Update LMY48T really messed up my phone so I reverted back to LMY48M via a TWRP backup. There is a new security update being released soon, and I would like to give it another try. Do the factory image security updates include all previous updates as well, or does each one need to be installed in sucession and therfore would not work?
Long story short, my Nexus 6P will not update to 7.0. I just got the OTA update notification today but when I downloaded it and waited forever for it to optimize my apps, my phone boots into 6.0.1. I tried getting 7.0 from the android developer program about a month ago and I was able to download it then too, but again, the phone just goes back to 6.0.1 for some reason. I decided to just wait until I get the OTA but the problem has still persisted. Any ideas on why its stuck on 6.0.1? Any way to fix this?
Also, I bought this phone about 1 and a half months ago used from eBay. It has been working perfectly fine. Just wanted to put that info out there.
It's possible you bought the phone rooted and/or with a custom ROM or recovery? If you aren't completely stock, an OTA update will fail. This isn't necessarily a single 'right' answer question, but you should probably flash the factory image for a completely fresh install. Grab the factory image at https://dl.google.com/dl/android/aosp/angler-nrd90u-factory-7c9b6a2b.zip and follow the guide, section 14 at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and you should be able to update.
I just got the 7.0 OTA myself completely stock and when it rebooted it's still on 6.0.
Nobody else is having this problem?
I think you've both misread the update info. I received MTC20L update yesterday, which said that it contains September security patches and also prepares the device for Android 7.0.
The update never claimed that your device will update to Android 7.0. But don't worry, we'll get it soon, at least I hope so!
MTC20L is the Aug security update and the factory image has been posted for 1.5 months, so odd that you're getting it now. Most people would have been receiving N OTA updates. The only way for us to guess what is going on with the OP is if he edits it to include the build number.
I also just got MTC20L yesterday.6.0.1. No idea why no 7.0. Waiting sucks..........It's been a month since "rollout".
It's true I didn't read what the update was yesterday, but I'm 95% sure it had something with "7.0" on there. How do I know what I installed yesterday? I'm on 6.0.1, with the Sept 6 security patch, and MTC20L.
MTC20F was the August update, MTC20L is September one, released 6.9.
I took the developer preview (mistake as it was a hassle that I had to fix) but remember guys, Android N updates in the background, so while it reboots to update, it doesn't take forever with the whole "android is upgrading" screen. I got the NRD90T OTA yesterday (wierd because the NRD90U is on the webpage) and later in the day I gave it a reboot just the set it straight again. I forget the actual wording but there is a secondary partition for updates so they do it in the background, and then revert back after a reboot.
So about a year ago, I did a factory reset while on the last beta, about a month before the final release was pushed out to everyone. I was properly enrolled in the beta program, so I didn't flash it myself.
After the reset, I was still on the beta but once the update was pushed out, I never received it. Manually checking for updates didn't find anything.
Security patch level: 12/1/2016
Baseband: 4ZPLN
My kernel version is is from "Fri Dec 23" which I'm assuming is 2016?
I have a Mac on High Sierra and I tried using Smart Switch but it would not find my phone. It would tell me to unplug the phone and try again, but I still got the same message.
What are my options now, since it has been a whole year like this. I put up with being on older software for all this time but now I think I've definitely pushed my luck with security patches, as well as getting the full features from Sprint in regards to optimization.
How do I get myself back up to speed? I'm already on 7.0, as I mentioned, so I'm hoping whatever needs to be done won't require a clean wipe.
PS, I took a look at my Samsung Members app and Samsung account and it had two devices listed as tied to my account. I think it's the same device, my S7, but one that has a check mark next to it was "last accessed" on the day I performed the factory reset, last January. The second one was last accessed currently, so I'm assuming it's the same device but Samsung sees it as two different devices.
Hello,
since march 2019 update, my phone Nokia 5 TA-1053, cannot "see" any further updates. It's June by now, and I was unable to update my phone by OTA with april and may 2019 updates.
What have I done, and didn't work:
1) clear cache partition from recovery mode
2) clear cache and data for Carrier Services app
3) clear cache and data for update service
4) trying all above without SIM card(s) inside the phone
Nothing is working. I'have bought this phone in November 2017 (in shop, without branding of any sort), and had no problems with system to this day. What can I do to update my phone, except wiping all system and data? @edit:
1) never rooted
2) never installed custom firmware
3) only official updates
grimHog said:
Hello,
since march 2019 update, my phone Nokia 5 TA-1053, cannot "see" any further updates. It's June by now, and I was unable to update my phone by OTA with april and may 2019 updates.
What have I done, and didn't work:
1) clear cache partition from recovery mode
2) clear cache and data for Carrier Services app
3) clear cache and data for update service
4) trying all above without SIM card(s) inside the phone
Nothing is working. I'have bought this phone in November 2017 (in shop, without branding of any sort), and had no problems with system to this day. What can I do to update my phone, except wiping all system and data? @edit:
1) never rooted
2) never installed custom firmware
3) only official updates
Click to expand...
Click to collapse
well, it kinda strange.. mine already installed june 2019 update.
FauzanAdli said:
well, it kinda strange.. mine already installed june 2019 update.
Click to expand...
Click to collapse
My phone says that there is no new updates, and my system is up to date.
Fix for missing OTAs
1. Backup any photos etc you want to keep
2. Switch off phone.
3. Remove SIM.
4. Switch phone back on.
5. Factory restore/erase (without SIM).
6. When phone restarts, set location as India, connect to wifi (do not insert SIM yet), download all updates, OTAs should appear
7. Once all OTAs installed, reinsert SIM
This worked for me.
I have been seeing a similar issue of delayed OTA update availability. In my case it seems to help to reboot the device, then it sometimes finds the new update.
Hy,
December Update out now.
Greets
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Wondering if people stuck on September version can finally update without resetting data.
Please let us know if you're in this group.
laviniu_c said:
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Click to expand...
Click to collapse
I would say the same. Can't expect anything better than this from these system updates.
until when mi a2 will receive updates? will this be the last?
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
birdflesh said:
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
Click to expand...
Click to collapse
thanks for the info! Mi A2 security patches until Aug 2021 (Mi A2 release August 2018)
Since that update my battery drains way faster.
Since that update my battery drains way faster.
+1
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
ota should work with an unlocked bl, IF you have not changed the system. unlocking means you could change it, it doesnt in itself deny ota updates
salmonthefish said:
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
Click to expand...
Click to collapse
I´m also waiting for anyone that reported that made the update. I have Setember Update with bootloader unlocked because of camera2api, i don´t made any system changes, and i get all the updates until september without problemes. After that i get Bootloop on October and don´t update anymore. If anyone upgrade from setember with sucess please report.
ki69 said:
because of camera2api
Click to expand...
Click to collapse
you answered your own question. if you've unlocked AND made ANY changes to the system ota can bootloop ofcourse.
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Aerobatic said:
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you.
A question, if i unlock the bootloader afterwards will the same issue pop up again?
salmonthefish said:
A question, if i unlock the bootloader afterwards will the same issue pop up again?
Click to expand...
Click to collapse
I believe neither Xiaomi nor Google can answer this question.
Anyway,
1) right now factory reset for unlocked MiA2 is needed only once when updating from any previous ROM version to any currently available ROM version >= 11.0.15.0;
2) having unlocked phone one is sure that his data can be restored in any future mishap;
3) unfortunately unlocked phone prevents usage of most of banking apps unless Magisk + Riru + edXposed installed with MagishHide On and GooglePlayServices in Blocked List (SafetyNet issue).
So everyone decides himself whether to
a) keep phone untampered (with risk of loosing data with next OTA bootloop),
b) or unblock phone and then stay with updating stock (spending some time to get root, make SafetyNet passable, remove annoying settings suggestions, customize UI, etc.) ,
c) or unblock phone and then revert to Android 9 10.0.17.0 (disabling updates),
d) or unblock phone and then escape to a Custom ROM.
I personally prefer option (b) since my first Android gadgets (never bought a phone/tablet which had problems with rooting).
19Gerhard85 said:
Since that update my battery drains way faster.
Click to expand...
Click to collapse
19Gerhard85
after updating "Google Find my Device" app battery holds like before all ok now but i never use that app not even logged in calendar app also updated at same time but i don't thin it was calendar