Database Info

[Q] Just got the VZW update. How to turn it OFF?

Ok, this morning my phone started downloading the VZW update. I'm stock-Rooted with Wallet and Google Now running. When the update was finished downloading it gave me a few minutes to accept or to defer. I chose the defer button and then it ask's me to pick a time later today to do it. How do I get out of this? I don't want to run the update.
Thanks

dbow32 said:
Ok, this morning my phone started downloading the VZW update. I'm stock-Rooted with Wallet and Google Now running. When the update was finished downloading it gave me a few minutes to accept or to defer. I chose the defer button and then it ask's me to pick a time later today to do it. How do I get out of this? I don't want to run the update.
Thanks
Click to expand...
Click to collapse
Download Titanium Backup from the Play store, run it, go to the Backup/Restore tab, scroll down to "SDM 1.0" and uninstall it. You should probably make a backup of it first just in case you ever need to get it back, but I've never read of it being used for anything other than pushing Verizon OTAs, which you will probably never want to receive if you're rooted.
If you have the paid version of Titanium Backup, you can "freeze" the app instead, but uninstalling it with the free version works too.

Thanks, I really appreciate your help

I tried freezing it before I received the update and that didn't work. Guess its somehow overridden by Verizon.
Sent from my SCH-I535 using Tapatalk 2

ef-civic said:
I tried freezing it before I received the update and that didn't work. Guess its somehow overridden by Verizon.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had to reboot after freezing it for it to stop downloading

Jacquestrapp said:
Download Titanium Backup from the Play store, run it, go to the Backup/Restore tab, scroll down to "SDM 1.0" and uninstall it. You should probably make a backup of it first just in case you ever need to get it back, but I've never read of it being used for anything other than pushing Verizon OTAs, which you will probably never want to receive if you're rooted.
If you have the paid version of Titanium Backup, you can "freeze" the app instead, but uninstalling it with the free version works too.
Click to expand...
Click to collapse
I have not received any prompts for OTA updates yet and was curious as to why that is. Apparently, some ROMS are coded without the SDM 1.0 file because I am running Clean ROM 2.5 and cannot find SDM 1.0 anywhere in the list. Another reason why Scrosler and CleanROM are boss!

mooremh said:
I have not received any prompts for OTA updates yet and was curious as to why that is. Apparently, some ROMS are coded without the SDM 1.0 file because I am running Clean ROM 2.5 and cannot find SDM 1.0 anywhere in the list. Another reason why Scrosler and CleanROM are boss!
Click to expand...
Click to collapse
Any custom ROM worth its salt should not include the SDM app, CleanROM isn't special in that regard.

[Q] OTA update error, rooted using CF-Autoroot

Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?

oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
did you do any other system modifications? change kernels?

I'd just dirty flash 4.4.3 and call it a day.

Zepius said:
did you do any other system modifications? change kernels?
Click to expand...
Click to collapse
Nop, unless apps like titanium backup or file manager (only other apps that require root) change something. :/

Lokke9191 said:
I'd just dirty flash 4.4.3 and call it a day.
Click to expand...
Click to collapse
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!

oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
OTA is more complex if you're rooted.. There's more flashing involved if you have / want a custom recovery (which all rooted users should aim to have)
Just download the full rooted stock ROM in android development and flash it without wipe from recovery.
It's actually fewer steps anyway.
OTA = revert system changes, boot recovery, flash, re-flash recovery, re-root
Rooted stock = boot recovery, flash
No brainer really. Flashing an OTA if rooted is a fool's errand
Sent from my Nexus 5 using Tapatalk

oshera said:
Im no android expert(far from it), and prefer to stick to the most simple methods as long as i can run xposed framework.
this is why OTA without flashing or interfering with OS is best for me.
Keep this as last resort if no progress will happen regarding OTA updates.
Thanks!
Click to expand...
Click to collapse
lmao, its FAR from the most simple method. most simple method would be to dirty flash a 443 stock/rooted rom and call it a day, without over complicating anything.

oshera said:
Hi, have seen some posts for this issue but none really help me understand what went wrong (tried this update 3 times with same result)
I have nexus 5 with android 4.4.2, rooted with CF-Auto root.
Recently i received OTA update notification to 4.4.3, but when i'm trying to install it i get error without any info.
Before trying to update i completely uninstall xposed and all of its modules.
To my understanding using CF-Autoroot should not interfere with OTA updates.
Any ideas?
Click to expand...
Click to collapse
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.

marleyfan61 said:
Did you uninstall Xposed from within the app? If you simply uninstalled it the same way you install regular aps (by dragging to uninstall from the app drawer) then it doesn't completely uninstall.
Click to expand...
Click to collapse
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises

oshera said:
Thank you!
That fixed my problem, after uninstall from within the app i could use OTA updates without flahing anything!
And thanks for everyone else for advises
Click to expand...
Click to collapse
Glad it worked for you. For future reference, do read this sticky - http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
(along with the other stickies in that forum)

How to stop lollipop from installing automatically?

I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.

Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.

Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.

I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.

I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.

Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850

So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.

Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.

jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.

aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.

adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.

[Q] VoLTE OTA update from AT&T - do I need to un-root to be able to install this?

My G3 has 5.0.1 and I have rooted it. Nothing more.
I got notification of the latest update, which had VoLTE, something about Uber (which is already in my bloatware) and something else.
I have only rooted this phone, however while I was searching around on xda to see if anyone else has gone through this update with root, I found a 1-line fix to disable authentication on WiFi tether. I did that, and then some time later I got a pop-up saying my phone is suspected of being rooted, so the update would be disabled. I then reversed the WiFi tether change, and checked for update and it _seems_ like it is ready to do the update.
But, has anyone out there gone through this update while rooted? Did that work and you only had to root again?
Or do I have to un-root?

pourhaus said:
My G3 has 5.0.1 and I have rooted it. Nothing more.
I got notification of the latest update, which had VoLTE, something about Uber (which is already in my bloatware) and something else.
I have only rooted this phone, however while I was searching around on xda to see if anyone else has gone through this update with root, I found a 1-line fix to disable authentication on WiFi tether. I did that, and then some time later I got a pop-up saying my phone is suspected of being rooted, so the update would be disabled. I then reversed the WiFi tether change, and checked for update and it _seems_ like it is ready to do the update.
But, has anyone out there gone through this update while rooted? Did that work and you only had to root again?
Or do I have to un-root?
Click to expand...
Click to collapse
I'm in the exact same boat as you. Can't finish the update due to being rooted before. Even if you factory reset it will still say you're suspected of rooting.
Here is my thread just in case you want to give it a glance.
http://forum.xda-developers.com/att-lg-g3/development/to-pick-ota-trapped-root-t3106573
Here is the link to unroot back to 10D
http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827
I haven't exactly solved this issue yet but I'm working on it >.<
Btw don't use that unroot link just yet. I need to confirm and read around before finding out if it's a viable method for our situation yet.

pourhaus said:
My G3 has 5.0.1 and I have rooted it. Nothing more.
I got notification of the latest update, which had VoLTE, something about Uber (which is already in my bloatware) and something else.
I have only rooted this phone, however while I was searching around on xda to see if anyone else has gone through this update with root, I found a 1-line fix to disable authentication on WiFi tether. I did that, and then some time later I got a pop-up saying my phone is suspected of being rooted, so the update would be disabled. I then reversed the WiFi tether change, and checked for update and it _seems_ like it is ready to do the update.
But, has anyone out there gone through this update while rooted? Did that work and you only had to root again?
Or do I have to un-root?
Click to expand...
Click to collapse
I had to un-root, update, then root again using one click.

rrktt said:
I had to un-root, update, then root again using one click.
Click to expand...
Click to collapse
To be specific about "un-root".
You don't mean that you simply unrooted via SuperSU, do you? I assume you actually restored back to stock KitKat 10d, correct? And then took the OTA update straight to 21l, correct?
(And where can you tell the phone to check for updates again? or did you just wait for it to pop up in the notification area?)
Thanks

ultrasuper said:
To be specific about "un-root".
You don't mean that you simply unrooted via SuperSU, do you? I assume you actually restored back to stock KitKat 10d, correct? And then took the OTA update straight to 21l, correct?
(And where can you tell the phone to check for updates again? or did you just wait for it to pop up in the notification area?)
Thanks
Click to expand...
Click to collapse
I unrooted back to stock kitkat 10d and took the OTA update to 21l.
To check for the OTA update, go to General --> About Phone --> Software Update --> Update now
I did try to update when rooted before restoring back to stock. It failed during installation with a message about suspicion of rooting.

rrktt said:
I unrooted back to stock kitkat 10d and took the OTA update to 21l.
To check for the OTA update, go to General --> About Phone --> Software Update --> Update now
I did try to update when rooted before restoring back to stock. It failed during installation with a message about suspicion of rooting.
Click to expand...
Click to collapse
Yup I just had to go through all this as well. Luckily it all went smoothly and my phone is back up to spec and loaded the way I use it daily. Took about 12 hours of deliberate effort though haha. I guess I never really knew how much stuff I had on the phone and how much time goes into editing settings and logging into everything. Anyways UltraSuper you're right. Had to use the link I posted above using LG Flash Tool and go back to kit kat then you can upgrade easily to 21l, LG one click root, use AutoRec to flash TWRP then do your first backup just in case something goes south but it's doubtful. My phone is stable as it was out of the box.

So what does this update offer? Is it worth the hassle of redoing everything?
sent from a device using an app

Did you do a twrp restore after the update? did Xposed work in the new update?
I may do this tonight
Thanks.

joeclark said:
So what does this update offer? Is it worth the hassle of redoing everything?
sent from a device using an app
Click to expand...
Click to collapse
To be honest I went through the whole process and I'll probably never use volte. I did it more just to have a clean start. I've been flashing like crazy and things were starting to get buggy. If things are running smooth for you I don't see the value in it unless you're planning on using volte.
Sent from my LG-D850 using Tapatalk

joeclark said:
So what does this update offer? Is it worth the hassle of redoing everything?
sent from a device using an app
Click to expand...
Click to collapse
VoLTE. That is the only notable thing about the update. A couple of pieces of bloat are in there as well. VoLTE is still new and not available everywhere yet and is only able to be used by a select few models of phones. Read up on it and decide. I personally do not see the need for the hassle atm so will wait until another day.

Stock ROM: Root & OTA Updates

My new MOTO G 2015 XT1540 16GB/2GB will be delivered early next week. I have been trying to do all my reading in advance. Ideally I would like to keep the stock ROM, root the device, and keep receiving OTA updates.
My understanding to date is it is possible root without installing (flashing) TWRP. And by fast booting TWRP (vice installing) I can root the phone, keep the stock boot loader, and receive OTA updates as long as I completely unroot the device prior to updating. What is not clear to me is if I can keep receive OTA updates and not break the phone under the following circumstances:
1) custom kernel installed
2) adding apps to the system such as Cerberus (I know it can be elsewhere)
3) adding apps that require root such as Adfree (modifying host file)
4) freezing or removing system apps (bloatware)
Any suggestions how to proceed would be greatly appreciated.

Freezing/adding apps doesn't affect ota's,

HelpMeruth said:
Freezing/adding apps doesn't affect ota's,
Click to expand...
Click to collapse
Uhh, yes it does, at least sometimes. My last OTA failed until a bug report to Motorola traced it to system apps I had frozen. I don't think it matters now, at least with Titanium and Marshmallow. Many of the system apps I uninstall or freeze come un-frozen after a reboot. All that I uninstall become installed again after a reboot. I don't know if that's a Titanium Backup problem with Marshmallow or what.

Tel864 said:
My last OTA failed until a bug report to Motorola traced it to system apps I had frozen.
Click to expand...
Click to collapse
So your update simply failed with no ill effect on the phone?
Were you using the stock kernel?

MrTooPhone said:
So your update simply failed with no ill effect on the phone?
Were you using the stock kernel?
Click to expand...
Click to collapse
No lasting ill effect. Yes, everything stock. I had previously un-rooted which won't stop the OTA download, just the install. When the install still failed, I had forgotten that I'd frozen some Google apps, Gmail, Play Movies & TV, and Google Play Music. When the OTA kept failing to install, Motorola had me send a bug report. After I unfroze the above apps, the update seemed to go through fine. This had not happened on earlier versions of Android, so I'm thinking something changed or maybe it was just a bug in my software, who knows. You don't get a lot of feedback from Motorola. I think you have a better chance of winning the lottery or getting struck by lightning.