Database Users

Verizon G3 VS985 update not asking to download

I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.

System Updates Frozen
I have the System Updates App frozen in Ti BU. Haven't gotten any hint of an update and I hope it stays that way.

Same thing happened to me it tried installing the update all on its own luckily it said waiting for wifi network to update so I froze the system updates app with titanium back up.

RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
RyanEJ25 said:
I didnt see a thread already but my G3 started downloading an update this morning without me accepting or saying anything at all. Obviously with Root and TWRP(Bump) I did not want this. I pulled down the notification bar long pressed on the update download, hit app info, then force stopped the app. I went into Titanium backup, made a backup of System Updates 1_13_10_0 then uninstalled it. I don't know if the download will come back but I don't think so. Also the update was 220ish MB and I have no issues with the phone after uninstalling this. Sorry I didnt get a chance to take a picture of the update since it was almost done lol.
Click to expand...
Click to collapse

trailrunner76 said:
RyanEJ25, I experienced the same thing as you. I have a Verizon LG G3 (vs985), rooted.
Trying to get more info on this system update and what it contains. I don't think it's Android 5.0 lollipop update, but more like a Verizon bug update/improvements.
I tried to run the system update that was downloaded via WIFI, but it failed due to my LG g3 being rooted.
Before I go down the path of backing everything, unrooting and upgrading and then re-rooting, just wanted to make sure the update is worthwhile.
-Kevin
Click to expand...
Click to collapse
The main thing that threw me off was that USB charge modes have changed. Charge and internet connection are removed from PC connections other than that its general improvements to the keyboard and docs and stuff.

You can temp unroot, take the update, then reroot assuming Verizon didn't load a bullet that kills root.
Voodoo OTA Root Keeper
Sent from my VS985 4G using XDA Free mobile app

I'd tend to avoid the update, at least for now, if you want to keep root and twrp. Seems to be a number of people mentioning issues, including trouble reverting to 10b.
I also froze "System updates" with TiBU, going to stay on 10b until things clear up. Freezing that app seems to do the trick.

Why are you posting here, instead of the Verizon forum: http://forum.xda-developers.com/verizon-lg-g3/general
If you take the update, you can't re-root and you can't roll back.
Some people have maintained root after updating.

OTA Update removes root and repairs deleted files

My device was running Fire OS 5.0 and I installed my copy of Titanium Pro (used APK extractor on another Android device as play not working on 5.0).
I then proceeded to kill as many Amazon processes based on my Remove Bloat thread - I actually deleted them from the device so that they were no longer there. I kept the OTA processes in place - reset the device from [Recovery Mode] and upon boot joined WiFi and proceeded with the upgrade to 5.01
The update by the looks of things repaired the Fire OS and the system processes that I had deleted were now back on the device (Kindle Book Store etc). It also removed root from the device.
So just like everyone says - disabled OTA updates if you do not wish t remove root.

Were you able to reinstall root post update?

shinji257 said:
Were you able to reinstall root post update?
Click to expand...
Click to collapse
Would love to know also
Sent from my Amazon Fire 2015

i reinstalled the firmware to give it real factory reset, and applied OTA twice yesterday, but I could make it rooted after that. So I guess you can reinstall root again because the updated system did not reject root.

shinji257 said:
Were you able to reinstall root post update?
Click to expand...
Click to collapse
Yes I was able to root 5.01 after the OTA update

I would strongly advise everyone to disable the OTA processes. If you want to update a new device from 5.0 to 5.0.1 you can do so manually. Fire (5th Gen) updates are available here https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
Who knows when amazon will roll out the next OTA, tomorrow, next week, next month. And they certainly might block root with it. The fire cost us only $50, amazon may be losing money on the straight device price. They want us to spending money on all the premium amazon services that we are striping out as bloat. They may need the money to even break even.

Huh... This actually gave me some insight into the OTA bit. I went and pulled the latest update and it basically overwrites the system partition. That's why it seems to undo everything you did. This is good though because it also means if it won't boot then I should be able to get into 3e recovery and sideload the most recent update back to the device. I tested this by flashing google play then "repairing" using the update and google play was no longer present from this. It also doesn't seem to wipe userdata when doing this which is nice.

The annoying update

I'm running Android 6.0, and I am getting penetrated for updating to 6.0.1.
Well, my phone is unlocked, rooted and with TWRP recovery. I did the update to 6.0, but the procedure was quite time-consuming. Play back old backup that only had root but no other system modifications, unroot, flash stock recovery, update, and do the whole thing again. It was ok for a major update, but way to complex for a small one. I would like the security updates, but not at that cost.
What other options do I have? I can't seem to get rid of the annyoing, very pushy Update notification wich just *** pops up in the foreground. All I can do is delay it for 23h59min, which needs multiple inputs for that..
Is there a update file for en.EU that I can flash dirty via TWRP? Or a way to disable the update notifications?

dedors said:
I'm running Android 6.0, and I am getting penetrated for updating to 6.0.1.
Well, my phone is unlocked, rooted and with TWRP recovery. I did the update to 6.0, but the procedure was quite time-consuming. Play back old backup that only had root but no other system modifications, unroot, flash stock recovery, update, and do the whole thing again. It was ok for a major update, but way to complex for a small one. I would like the security updates, but not at that cost.
What other options do I have? I can't seem to get rid of the annyoing, very pushy Update notification wich just *** pops up in the foreground. All I can do is delay it for 23h59min, which needs multiple inputs for that..
Is there a update file for en.EU that I can flash dirty via TWRP? Or a way to disable the update notifications?
Click to expand...
Click to collapse
Capture the OTA zip for our common humans didn't received the OTA yet. Download the update, do not install and reboot in recovery. The OTA zip is in /cache folder. With TWRP in /cache and copy the zip to sdcard.

Update Notification states 24.201.3.en.EU
On a Moto X Style 6.0 24.11.18_clark_reteu.reteu.en.EU reteu with no other patch (Security patch level 1. Nov 2015).

dedors said:
Update Notification states 24.201.3.en.EU
On a Moto X Style 6.0 24.11.18_clark_reteu.reteu.en.EU reteu with no other patch (Security patch level 1. Nov 2015).
Click to expand...
Click to collapse
Thank you for your effort! But unfortunately this isn't the 6.01 OTA arriving in March, it's just a security patch from February... Bad news for some of us
On the other hand, you could ban the update notification 'hiding' the Motorola Update Services: adb pm hide com.motorola.ccc.ota
Or like you are rooted, you could freeze the app with some 3rd party like Titanium Backup.

dani_mola said:
Thank you for your effort! But unfortunately this isn't the 6.01 OTA arriving in March, it's just a security patch from February... Bad news for some of us
On the other hand, you could ban the update notification 'hiding' the Motorola Update Services: adb pm hide com.motorola.ccc.ota
Or like you are rooted, you could freeze the app with some 3rd party like Titanium Backup.
Click to expand...
Click to collapse
Sorry it's just the security patch. I got the Notification in February, got annoyed a few days with it, and then it dissapeared again, starting to show up again a few days ago.
I also just found out that I can block it via TB (Motorola Update Service), but to know the adb command is nice, thanks.
From what I read to now, the update is not easy, you basically have to start from scratch again, which is too time-consuming. I'll block it for now and check out what that march update may offer.

Yeah I've been getting the notification for about a week now myself. Been doing exactly the same thing as you by setting the notification to 23h59m just to get it to shut up otherwise it bothers me every time I wake my phone. I actually tried to run the update and it just went to TWRP and failed. Would love a way of updating without having to wipe.

DeTard said:
Yeah I've been getting the notification for about a week now myself. Been doing exactly the same thing as you by setting the notification to 23h59m just to get it to shut up otherwise it bothers me every time I wake my phone. I actually tried to run the update and it just went to TWRP and failed. Would love a way of updating without having to wipe.
Click to expand...
Click to collapse
Are you getting 'eu' variant 6.0.1 ota notif.? If yes, it should be great if you capture it for us

Always capture an OTA if possible

dani_mola said:
Are you getting 'eu' variant 6.0.1 ota notif.? If yes, it should be great if you capture it for us
Click to expand...
Click to collapse
Sorry no, I have the en.US OTA.

Google Keep, Calendar and Reminders notifications not working on Android Oreo.

Hello guys,
I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization.
I formatted the phone after receiving the Oreo OTA and the phone is full stock.
Anyone know how to fix this issue?
Thanks!

VSTOLL said:
Hello guys, I've noticed this issue this week. I'm not receiving any notifications from Google Calendar, Keep and Google Now reminders, and this is a pretty big problem for me, as I rely a lot on Calendars for my organization. I formatted the phone after receiving the Oreo OTA and the phone is full stock. Anyone know how to fix this issue? Thanks!
Click to expand...
Click to collapse
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.

v12xke said:
Did you mean you did a factory reset from recovery instead of format? You have to be unlocked to fastboot format partitions... but it is the best way to wipe your phone if you are.
What is your build number under Settings>>About Phone (at the very bottom)? If you are indeed stock (including recovery), the only thing I can think of would be to first wipe the cache partition from recovery. If your build number ends with .017 then you can also sideload a full OTA of build .019, also from stock recovery. Options are limited unless you are unlocked and have a custom recovery. Note the process of unlocking the first time will factory reset your phone and wipe userdata, so make sure your stuff is backed up.
Click to expand...
Click to collapse
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates.
My build number ends with .019

VSTOLL said:
I just went into the recovery mode and did a data/cache wipe, like I always do after big updates. My build number ends with .019
Click to expand...
Click to collapse
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?

v12xke said:
When you go into Settings>>Users and Accounts>>Google>>Account Sync ... are there failed or hung syncs? Now do a manual sync and see if any hang. If you see old time stamps there and they won't refresh manually, you can REMOVE ACCOUNT and then ADD ACCOUNT. I would try this regardless. Are you bootloader locked?
Click to expand...
Click to collapse
There was no failed or hung syncs but I removed and added my account again anyway.
I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events.
My bootloader is locked.

VSTOLL said:
There was no failed or hung syncs but I removed and added my account again anyway. I'm afraid that this issue is bacause of the Doze feature. If I create a test event to notify in 5 minutes, it works, but I have to wait to see if it will notify my real events. My bootloader is locked.
Click to expand...
Click to collapse
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.

v12xke said:
If what you suspect is correct, thousands of other users would be actively complaining of such a major issue, and not just N6P users.... every Nexus/Pixel phone running 8.0 already. That's a lot of phones. Doze works better than ever on 8.0 for 99.9% of regular users. Sometimes you just have to wipe the phone and start over from a clean slate. Unlocking your bootloader would allow you to use Google's purpose-based script and full image to restore your phone to a like-new state. That or you will have to live with it and wait until the next full OTA image is posted next month. I don't mean take the small incremental OTA, I mean sideload the full OTA image from Google's Dev site. They are about ~1 GB in size.
Click to expand...
Click to collapse
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?
I found this post: https://productforums.google.com/fo...utm_source=footer#!topic/calendar/FzD9Y6ojci4
Theres a reply by Mikel Rodriguez that says:
"The cause of the calendar notifications failure is a change in the architecture of the calendar provider module. It is a content provider located at the application framework layer. Supposedly they changed the architecture of the module because it wasn't compatible with the doze feature of Marshmallow. So, all phones running Marshmallow or higher are fully affected by the failure. The only solution is to root, install titanium backup, make a backup of package com.android.providers.calendar, then uninstall it, then download and install the same package for version 5.1.1 (Lollipop). Because that version is not compatible with doze, it is necessary to remove it completely. Download "Boeffla Doze Control", open it and turn on "disable doze at start up" and "show toast message", then reboot, then open it again and check that doze status is off. That means that doze is not working. Calendar notifications will work again if you follow all the steps."
I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?

VSTOLL said:
My phone is already on the last OTA and I wiped it twice, is it going to make a difference just trying again?....... I don't know how much of this is true, but there's quite a lot of people with the same problem. Maybe there's some app that is conflicting with the notifications?
Click to expand...
Click to collapse
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.

v12xke said:
Taking a 40MB incremental OTA over the air and then doing a factory reset of your device is not the same as sideloading a 1GB full OTA image. Both of which you can do locked with stock recovery, but you can only sideload a newer build OTA (without some editing of the install script). If the full OTA image doesn't correct your problem, there is no further recourse but to unlock the phone and use the Google tool to restore your phone. As I said earlier a locked bootloader severely limits your options. I'm not suggesting you root the phone, I'm saying unlock it so that you are then able to properly format the partitions and install a full image.
I read the post and maybe that would work as a kludge. Sounds reasonable for a guy already rooted and has TiBu like me.... but would probably be overkill for someone like you starting with a locked bootloader. If you put that forward to prove that tons of people have the same issue, it fell short. I say live with it until the next OTA image is posted, DON'T take the over the air incremental and sideload that full OTA. Then if it doesn't work, unlock and flash a full image.
Click to expand...
Click to collapse
I'll wait for the next OTA then, and if it doesn't fix I'll try formatting and restore it with the Google tool you said.
By the way, I didn't received a incremental OTA. I live in Brazil, so the update arrived later here, I received it 2 weeks ago and was a 1GB download and I haven't received any security or incremental updates since that day.
I set an event and it'll remind me in 2 hours, I'll let my phone down and will not use it to see if the nofication will work, if it doesn't, I'll try this app: https://play.google.com/store/apps/details?id=com.github.quarck.calnotify&hl=en

Installation problem in January security patch with oreo

i uninstalled magisk completely,
unrooted
flashed stock boot.img
relock the bootloader
but OTA giving error of "installation problem"
what to do???

Well you always have the option of flashing oreo image.
I dont know any othet way.
Still didn't got January update.

alkesh95 said:
Well you always have the option of flashing oreo image.
I dont know any othet way.
Still didn't got January update.
Click to expand...
Click to collapse
To get update:
Settings-apps- show system apps- Google services framework app- storage- clear chache- clear data-driven force stop- disable- enable - go back to settings- software update- refresh the page.
You will find the update ready to install

hemanth_gunasekaran said:
To get update:
Settings-apps- show system apps- Google services framework app- storage- clear chache- clear data-driven force stop- disable- enable - go back to settings- software update- refresh the page.
You will find the update ready to install
Click to expand...
Click to collapse
I am aware of that. But i rely heavily on notifications from my apps.
Waiting for rollout to reach me.
Thanks.

slowy77 said:
i uninstalled magisk completely,
unrooted
flashed stock boot.img
relock the bootloader
but OTA giving error of "installation problem"
what to do???
Click to expand...
Click to collapse
I did same way...
I got update. .. Again rooted... Did u edit any system files ? Or using adway? Or fonts?

what do i need to update to the current oreo, how about performance, battery, audio?

ajegile said:
what do i need to update to the current oreo, how about performance, battery, audio?
Click to expand...
Click to collapse
Man, no offense, but do some reading. People are telling everywhere we have to wait for the next stable build from Xiaomi. The first stable build was buggy, and that is why is stopped.
Be patient, probably we will get update by the end of January, for those who already did update to Oreo, they got January security patch to fix some bugs. For now, it is better to stay on Nougat.

Watch this video to learn how you can flash the stocks ROM in order to install the OTA update , this method is also help you to overcome from the Bootloop https://youtu.be/sbkZoYs0LP0