Verizon rooted non-DE. The KitKat OTA downloaded but I've "snoozed" the install as I don't want to lose root/tether.
Can I freeze something in TB to get it to stop asking me to complete the install? I'm afraid I'm going to hit the wrong button one time and mistakenly take the OTA.
TwinsMom said:
Verizon rooted non-DE. The KitKat OTA downloaded but I've "snoozed" the install as I don't want to lose root/tether.
Can I freeze something in TB to get it to stop asking me to complete the install? I'm afraid I'm going to hit the wrong button one time and mistakenly take the OTA.
Click to expand...
Click to collapse
if you already downloaded it, im surprised you are not in a bootloop right now because that is typically what happens. But use tibu to freeze moto ota (or something like that) and updater (or something like that). If you can't find what im talking about in TIBU then i can look it up and give you the exact names.
jayboyyyy said:
if you already downloaded it, im surprised you are not in a bootloop right now because that is typically what happens. But use tibu to freeze moto ota (or something like that) and updater (or something like that). If you can't find what im talking about in TIBU then i can look it up and give you the exact names.
Click to expand...
Click to collapse
Thanks! I found "MotorolaOTA 1.0" and "Updater 1.0" and froze those in tibu so we'll see what happens.
On my Moto X it first downloaded the OTA then asked if I wanted to install it, giving me the usual "you will not be able to use your phone for up to xx minutes during the installation". Then it gave me the option to not install, then if I didn't install, it gave me the option of when to be reminded and a check box for "auto-install". I kept the check box UNclicked and set the reminder for later tonight. That's how I avoided the dreaded bootloop.
Also if you change it for one minute earlier you will have a whole day without getting reminded.
TwinsMom said:
Thanks! I found "MotorolaOTA 1.0" and "Updater 1.0" and froze those in tibu so we'll see what happens.
On my Moto X it first downloaded the OTA then asked if I wanted to install it, giving me the usual "you will not be able to use your phone for up to xx minutes during the installation". Then it gave me the option to not install, then if I didn't install, it gave me the option of when to be reminded and a check box for "auto-install". I kept the check box UNclicked and set the reminder for later tonight. That's how I avoided the dreaded bootloop.
Click to expand...
Click to collapse
dont reboot your phone or that thing will go into bl and automatically try to upgrade to the ota from what i have read about others.
Thanks for the help, freezing those worked fine. Gave me some time to do research on the new KitKat root method and see if it will hold native wifi tether.
Sent from my GT-P6210 using xda app-developers app
Related
Hello everyone. I know I'm a noob, but am hoping I can get some help anyway. Tried searching and not too many people are having the same problem, so I started a new thread.
Anyway, I used the one click root found in this thread:
http://forum.xda-developers.com/showthread.php?t=1348557
( I tried to post in that thread, but can't since I don't have 10 posts )
I'm new to hacking and I'll be honest. I only wanted to root my phone so I could use wireless tether, and then use Titanium Backup to freeze a lot of the bloatware on the phone. I have no desire to install a different ROM. I'm happy with the one it has, and happy to take the updates Verizon pushes. Everything was good until the latest update came through. When it downloaded, and rebooted, instead of updating, it booted in clockwork mod recovery. No matter what I tried, I couldn't get the update to go through.
So I settled on never updating again and froze the updater to prevent my phone from trying to update and going to CMR at random times. About 4 days later, my bluetooth quit working. Couldn't figure out why. Thought I was going to have to send it in for warranty work, so I tried to undo all the mods. I unfroze everything, and then hit the one click unroot button. It said it worked. Problem is, superuser is still installed with no way to uninstall.
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Next I tried to go ahead and get the update since the unrooting process was supposed to have reinstalled stock recovery. Well, it didn't. I still ended up booting up into CMR again. STILL can't update even after unrooting. Double checked, and wireless tether and Titanium backup both say "no root". On a whim, I try the blue tooth and guess what. It worked. May not need to send the phone off for warranty work after all.
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
I know this is a lot of question and I'm a noob, but I'm a noob willing to learn. If this problem has been encountered before, I apologize in advnace for not finding the appropriate thread. I tried.
updater app
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
NewDroidXUser said:
My first question is this: How do I get superuser gone so my phone can be back to factory so they'll never know it was rooted?
Click to expand...
Click to collapse
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
NewDroidXUser said:
So my second question is this: Would freezing the updater cause the blue tooth to stop working? If so, how can I either keep it working or stop the updates without freezing the updater? It's like I have to choose between having blue tooth or having my phone randomly boot into CMR whenever it tries to update.
Click to expand...
Click to collapse
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
NewDroidXUser said:
Third question, pertaining specifically to the one click root I linked to above: How can I get rid of the CMR? Is it possible to root the phone without installing CMR? If I can get it unrooted back to factory ( without superuser or CMR ), how can I root it again so that it doesn't install CMR and keeps the stock one?
Click to expand...
Click to collapse
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
brad6360 said:
There's no need. MTMichaelson has come up with a easy way to keep your phone rooted during the upgrade from ZV7 to ZV8.
Yes it will. Several people have reported this in different threads. I'm not sure of a way around this, but I think others might have a way around it. If you follow MT's method to keep root during the upgrade, you want have to worry about it!
There's no need to do this either since you can keep root and upgrade.
Here's what you need to do.
1) Go here and root your phone again.
2) Go here to upgrade to ZV8 while keeping root. There's also a method for reinstalling CWM as the upgrade will remove it.
This will: keep your root, get you upgraded, fix your bluetooth and keep CWM.
Good luck!
Click to expand...
Click to collapse
Ah, thanks. I'll post again to update how that went. Though, I'd like to keep the stock recovery. I'll try to do it without CWM.
latenighter49 said:
Yes freezing the software update app will cause your Bluetooth to stop working. I used a app called Gemini app manager to go change the permissions of the software update app so it did not have any permissions to do anything. I have not been bothered with update prompts since.
Click to expand...
Click to collapse
How did you change permissions in Gemini? I turned off all the autorun features and was able to get Bluetooth working but I didn't see anything about permissions in the settings. I could have missed it though being at work and all. Will turning off all the autorun features of the Software Update app stop it from trying to download the update in the middle of the night when I'm not looking like it sounds like it should?
In gemeni select block app. It's the same as freezing in titanium backup.
Sent from my VS910 4G using XDA
Hello, everyone. Long time reader, first time poster.
I just finished rooting my new Developer's Edition GSM unlocked Moto X. As I started to freeze the usual apps that are necessary in order to stop OTA notices and lessen the likelihood of sending my device into a bootloop by mistake, I noticed that the apps that I had on my Verizon Droid Maxx aren't here. I saw some threads that stated that I needed to freeze update.apk, MotorolaOTA, FOTA, and rename otacerts.zip to otacerts.zip.bak.
Of all of those steps, I've only been able to do two of them: freezing MotorolaOTA and renaming otacerts.zip.
Where can I find the other two apps to freeze? Is it even necessary if I've already frozen MotorolaOTA and renamed otacerts? When I had my Droid Maxx, I was unable to click on System Updates in About Phone without the app crashing. Here, after freezing and renaming these two apps, I can still check for updates, which leaves me a little worried.
Thank you for your help.
3C_OTA.APK is one you want to rename.. It exists in /system/apps or /system/priv-app (I forget which).
KidJoe said:
3C_OTA.APK is one you want to rename.. It exists in /system/apps or /system/priv-app (I forget which).
Click to expand...
Click to collapse
Great, I went ahead and renamed that one 3C_OTA.APK.BAK. I can still check for updates in System Updates, which is something I couldn't do on my Droid Maxx after freezing all the OTA apps.
Is that normal for this phone? Are there any other apps / files I need to take care of?
Thanks for the reply!
Any other ideas? The fact that I can still check for an update makes me nervous. I'm just trying to confirm that this was all I needed to do.
defcoalknot said:
Any other ideas? The fact that I can still check for an update makes me nervous. I'm just trying to confirm that this was all I needed to do.
Click to expand...
Click to collapse
MotorolaOTA 1.0 is what I froze on my retail X (while it was downloading an update) and as soon as it was frozen, the download icon in the status bar disappeared :good: I'm not sure where the apk is located to move/rename since I used tibu to freeze it.
defcoalknot said:
Any other ideas? The fact that I can still check for an update makes me nervous. I'm just trying to confirm that this was all I needed to do.
Click to expand...
Click to collapse
Renaming 3C_OTA.APK has worked for me and others who wanted to block OTA notifications..
here are links to just a few times before that it has been suggested...
http://forum.xda-developers.com/showpost.php?p=51038059&postcount=5
http://forum.xda-developers.com/moto-x/moto-x-qa/how-to-upgrade-to-4-4-2-t2660439
http://forum.xda-developers.com/showpost.php?p=50960313&postcount=5
I'm sure if you searched, you could find more instances of it being suggested, and successful.
bb1981 said:
MotorolaOTA 1.0 is what I froze on my retail X (while it was downloading an update) and as soon as it was frozen, the download icon in the status bar disappeared :good: I'm not sure where the apk is located to move/rename since I used tibu to freeze it.
Click to expand...
Click to collapse
That's all I froze on my phone too.
I decided to go ahead & root my S6 using the PingPong Root found here.
All went correctly, but when I go to open SuperSU I get the error 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
Any ideas on how to go about installing the binary needed? Thank you!
Muscle Nerd said:
I decided to go ahead & root my S6 using the PingPong Root found here.
All went correctly, but when I go to open SuperSU I get the error 'There is no SU binary installed, and SuperSU cannot install it. This is a problem!'
Any ideas on how to go about installing the binary needed? Thank you!
Click to expand...
Click to collapse
You are not rooted then. Try again.
12MaNy said:
You are not rooted then. Try again.
Click to expand...
Click to collapse
Uninstalled both SuperSU & PingPong Root. Reinstalled and had got the same error as before.
This method is in beta, could the binary not be uploaded yet?
Muscle Nerd said:
Uninstalled both SuperSU & PingPong Root. Reinstalled and had got the same error as before.
This method is in beta, could the binary not be uploaded yet?
Click to expand...
Click to collapse
What happens when you run get root on pingpong? Sounds like it's not rooting you. Either 1) you did not open supersu before you ran get root on ping pong. Or 2) it failed to get root (either it tells you failed or it reboots automatically due to kernel panic). If your not getting a pop up saying root was successful, reboot now is recommended, then your not rooted.
_Dennis_ said:
What happens when you run get root on pingpong? Sounds like it's not rooting you. Either 1) you did not open supersu before you ran get root on ping pong. Or 2) it failed to get root (either it tells you failed or it reboots automatically due to kernel panic). If your not getting a pop up saying root was successful, reboot now is recommended, then your not rooted.
Click to expand...
Click to collapse
I don't get that pop up. But my device does reboot.
I tried opening SuperSU prior to PingPong, but it only has the original error 'no binary'. After you press okay, it prompts you to installing SuperSU once again? Odd... Once you install the 'new version' and open that, it'll automatically open PingPong. From there I select 'Download data' then 'Get Root!'. Which then tells me to wait with a popup, and that is when my S6 reboots.
Ok. Now leaving supersu and pingpong installed, reopen pingpong, cancel the install of supersu. Place the phone on a flat surface. Try just 'get root' again. Sometimes background processes can flip out when pingpong panics the kernel to elevate it's privlages. It's taken me 4 or 5 tries a few times I've used pingpong (others only 1 time, I've had to Odin my S6 about 30 times so far lol)
_Dennis_ said:
Ok. Now leaving supersu and pingpong installed, reopen pingpong, cancel the install of supersu. Place the phone on a flat surface. Try just 'get root' again. Sometimes background processes can flip out when pingpong panics the kernel to elevate it's privlages. It's taken me 4 or 5 tries a few times I've used pingpong (others only 1 time, I've had to Odin my S6 about 30 times so far lol)
Click to expand...
Click to collapse
Thanks for the prompt response Dennis!
I opened PingPong, canceled the install of SuperSU, then selected 'Get Root!'. Says my device is not supported (Though it is in the thread for PingPong). I select download data, (Says Device updated, please try Get Root again.) then I select get root. Unfortunately it reboots my S6 after about 2-4 seconds. I'll keep trying!
Aye, do the same steps I said, but add the download data before get root. Try to do it after everything settles from boot but before starting anything else.
_Dennis_ said:
Aye, do the same steps I said, but add the download data before get root. Try to do it after everything settles from boot but before starting anything else.
Click to expand...
Click to collapse
Will do! If this doesn't work after a few dozen tries I may just have to wait for a more stable release, eh?
Muscle Nerd said:
Will do! If this doesn't work after a few dozen tries I may just have to wait for a more stable release, eh?
Click to expand...
Click to collapse
That reminds me, what version are you using? Beta 6 or a different one?
_Dennis_ said:
That reminds me, what version are you using? Beta 6 or a different one?
Click to expand...
Click to collapse
Beta 6
Edit* Uninstalled both applications, and installed the 5.1 beta. When I select download data, it says to retry the Get Root as usual. Then I select Get Root, and it says 'Your device data is still not supported'.
Here's the quote from Idler in the thread. With option C. he says to possible do a factory reset? I have all of my contacts & photos backed up via my pc. Should I possible try and do a reset? Or do you think it's a waste of time.
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears.
If these doesn't help after 5 retries, there could be some issue, please collect the information in /proc/last_kmsg and send it to me.
Note: User reporting installing My Knox or enable other Knox feature (like enterprise provision or KNOX active protection) may cause reboot loop. Be cautious!
Click to expand...
Click to collapse
Ok beta 5.1 does not have hot data then. What is your device? Check settings>about device>baseband
Also from the Q&A in pingpong root thread:
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears​
Make sure to try that.
_Dennis_ said:
Ok beta 5.1 does not have hot data then. What is your device? Check settings>about device>baseband
Also from the Q&A in pingpong root thread:
Q: It just keeps rebooting, what can I do?
A: The exploit may panic the kernel and reboot your device. If the data is off, same could happen as well. When issue happens, try these:
a. Clean up background process before running root.
b. Turn on airplane mode after clicking "Download Data".
c. Backup your data and run factory reset.
d. Definitely avoid doing anything else when "wait!!!" appears​
Make sure to try that.
Click to expand...
Click to collapse
I have the G925AUCU1AOE2. I've tried all of those aside from the reset
Muscle Nerd said:
I have the G925AUCU1AOE2. I've tried all of those aside from the reset
Click to expand...
Click to collapse
Alright. Best bet. Is reboot. Let settle. Set screen timeout to 10 mins. Turn off all apps you have running in the background. Open pingpong. Download data. Turn on airplane mode. Place on desk. Run root. Don't touch until hopefully it says your rooted. Of course you'll need to I stall beta 6 again before you do the above.
If trying that 5 times doesn't work you'll have to head over to the pingpong thread cause I'm fresh out of ideas lol.
_Dennis_ said:
Alright. Best bet. Is reboot. Let settle. Set screen timeout to 10 mins. Turn off all apps you have running in the background. Open pingpong. Download data. Turn on airplane mode. Place on desk. Run root. Don't touch until hopefully it says your rooted. Of course you'll need to I stall beta 6 again before you do the above.
If trying that 5 times doesn't work you'll have to head over to the pingpong thread cause I'm fresh out of ideas lol.
Click to expand...
Click to collapse
Haha, no worries! I will give that a go.
Yay or nay towards a reset? I have a feeling I'll go through the hassle of resetting my phone & I'll have the same error.
Back up with smart switch. Reset but do not download any app but pongpong. That should help with the error, as it's cause by apps in the background running usually. After root restore via smart switch. All your apps come back, just not the app data unfortunately
_Dennis_ said:
Back up with smart switch. Reset but do not download any app but pongpong. That should help with the error, as it's cause by apps in the background running usually. After root restore via smart switch. All your apps come back, just not the app data unfortunately
Click to expand...
Click to collapse
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Muscle Nerd said:
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Click to expand...
Click to collapse
Glad to hear, now you just have to restore all your apps and stuff. I'd suggest titanium backup, back everything up and transfer to your computer. That way if you ever have to Odin you have all your apps set up and such for when you reroot after. Store them off the phone as Odin will wipe your phone completely usually.
_Dennis_ said:
Glad to hear, now you just have to restore all your apps and stuff. I'd suggest titanium backup, back everything up and transfer to your computer. That way if you ever have to Odin you have all your apps set up and such for when you reroot after. Store them off the phone as Odin will wipe your phone completely usually.
Click to expand...
Click to collapse
Will do, thank you!
Tom Dsgn said:
Dennis, you are a legend! Finally got my S6 rooted after 2 long days.
Decided to go ahead and backup everything on my phone and do a complete factory reset. I did like you had said and only installed PingPong. Booted up the application, got a shut down like I did previously. Tried again, but closed all my running apps and when I was prompted to install SuperSU (even though it was installed when I ran it the first time) I went ahead and installed it once again. And voila, the root went successfully!
:highfive:
Click to expand...
Click to collapse
How do i root my s6 been trying for weeks
The first few times I used Kingroot to achieve temp root, it worked great and then just went back to unrooted after a while. One time after rooting, it was spammed with error messages that the play store and other apps were crashing. I rebooted the phone and it seemed to fix it. The errors were gone and so was root. I tried kingroot again and I had the same problem. I did the same reboot and then deleted the kingroot app. I thought everything was fixed then until I plugged my phone in to charge. It shut down even though it was around 75%. I didnt know what i was doing so I put it in recovery mode and choose factory. I thought this would do a factory reset but now when my phone powers up all my apps and stuff is there. Please advise how to completely rid my device of kingroot. Thanks in advance
Update: When I started in factory mode, there was a testing app called commserver or something like that running. I saw in other forums to reboot to remove that and i did and it worked. Still would like advice on removing kingroot completely.
Jefff0101 said:
The first few times I used Kingroot to achieve temp root, it worked great and then just went back to unrooted after a while. One time after rooting, it was spammed with error messages that the play store and other apps were crashing. I rebooted the phone and it seemed to fix it. The errors were gone and so was root. I tried kingroot again and I had the same problem. I did the same reboot and then deleted the kingroot app. I thought everything was fixed then until I plugged my phone in to charge. It shut down even though it was around 75%. I didnt know what i was doing so I put it in recovery mode and choose factory. I thought this would do a factory reset but now when my phone powers up all my apps and stuff is there. Please advise how to completely rid my device of kingroot. Thanks in advance
Update: When I started in factory mode, there was a testing app called commserver or something like that running. I saw in other forums to reboot to remove that and i did and it worked. Still would like advice on removing kingroot completely.
Click to expand...
Click to collapse
To remove Kingroot completely, you need to reflash the system partition. You can do this by plugging your phone into a computer, installing the Verizon Upgrade Assistant, and using the "repair your phone" option. Doing this will wipe your phone, so backup any data first.
TheSt33v said:
To remove Kingroot completely, you need to reflash the system partition. You can do this by plugging your phone into a computer, installing the Verizon Upgrade Assistant, and using the "repair your phone" option. Doing this will wipe your phone, so backup any data first.
Click to expand...
Click to collapse
Thanks, I'm kinda a noob so could you walk through the steps like you were talking to a baby? Like do I put my phone in recovery mode and then download the version thing on the computer? How do you suggest backing up my phone? Sorry for the bother, I'm new to this stuff. Thanks again
Sure:
1. Boot your phone normally. Backup whatever data you want to preserve. Make sure that whatever backups you make are stored in a place that is outside of your phone.
The best way to backup your phone depends on what you want to backup. If you're worried about losing contacts, don't be. I'm pretty sure Google backs those up automatically. You can make sure by going to https://www.google.com/contacts/. If you see contacts there, you're good. If you're worried about losing pictures, plug your phone into a computer and use a file browser to copy the folder called DCIM to your computer. If you want to try backing up your texts, there's an app on the play store called Super Backup that might help. Just make sure that you transfer whatever backup file it makes to a cloud drive or your computer.
2. Plug your phone into a computer running Windows (I'm not sure if it what I'm about to describe works on a Mac or not, but I know that it does not work on Linux). You should get a pop-up that says something like "do you want to install the verizon upgrade assistant?" Install it. If you don't see the pop-up, install this instead: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. This is the Motorola Device Manager, and it's basically the same thing.
3. If you're using the Verizon tool, select "repair device" and follow the instructions. If you're using the Motorola tool, look for something that says "repair phone" or something like that, and follow those instructions.
4. The tool will wipe your phone, along with all of that nasty Kingroot stuff that tries to make modifications to /system despite the fact that /system is write-protected until you unlock with Sunshine (which is why it messed up your phone).
5. If you decide you want it, download Sunshine from here: http://theroot.ninja/download.html.
6. Go into your phone's security settings and allow installation of apps from unknown sources.
7. Click on the Sunshine apk that you downloaded to your phone to install it.
8. Open the Sunshine app and follow the instructions. If, when your phone reboots, you see a bootloader unlocked warning message instead of the black and white Motorola M symbol that usually appears, it was successful. If it was unsuccessful, keep trying. It should get it after a few tries.
Is there anyway to disable the system update notification? For a variety of reasons I don't want to upgrade to 6.0 yet. I have root on stock debloated 5.1
Thanks.
tk424 said:
Is there anyway to disable the system update notification? For a variety of reasons I don't want to upgrade to 6.0 yet. I have root on stock debloated 5.1
Thanks.
Click to expand...
Click to collapse
I tried two rooted debloated roms that both said OTA disabled and i got the nag notification on both. Disappointing!
Same here! I myself used TB to freeze all the system apps which were supposed to trigger the OTA updates, but I still got it. I moved the update.zip from the cache directory somewhere else, so if I accidentally hit update, nothing will happen. But still a nuisance.
Anyone with an idea?
Is this a new problem? For dumb reasons I ended up having to reflash Rydah's stock rooted 5.1 image yesterday and starting mostly all over, it's a pain in the butt. I did freeze pr.adapt and update center but this notification popped up to update. I definitely do not want to update. I thought the rooted ROM blocked updates? I guess not because the notification is there. I tried disabling Google play services notifications but the notification persists.
---------- Post added at 02:36 PM ---------- Previous post was at 01:39 PM ----------
OK guys, I got rid of my notification. I used titanium backup and froze everything I could on the following list,
http://forum.xda-developers.com/tmobile-g4/help/debloat-package-list-lg-g4-t-mobile-h811-t3168181
I froze very few from the following list, still working on it after my mishap yesterday.
http://forum.xda-developers.com/g4/help/lg-g4-stock-debloater-list-g4-variants-t3167297
The notification was still there, but I decided to reboot and now the notification is gone. Hopefully it sticks. Where can I find the update.zip so I can delete it and clear up some space.
waylo said:
Same here! I myself used TB to freeze all the system apps which were supposed to trigger the OTA updates, but I still got it. I moved the update.zip from the cache directory somewhere else, so if I accidentally hit update, nothing will happen. But still a nuisance.
Anyone with an idea?
Click to expand...
Click to collapse
Where is the update.zip hiding? I too am not ready to update, but cant block it. Thanks
jhmcat said:
Where is the update.zip hiding? I too am not ready to update, but cant block it. Thanks
Click to expand...
Click to collapse
Using a root explorer, in the internal memory, go to /cache. It's about 970mb.
waylo said:
Using a root explorer, in the internal memory, go to /cache. It's about 970mb.
Click to expand...
Click to collapse
Got it moved (not deleted). Thanks!
jhmcat said:
Got it moved (not deleted). Thanks!
Click to expand...
Click to collapse
Hmm, I found it comes back from time to time. So definitely need to get to the bottom of what pulls down the update. Still don't think we've nailed the offending apk/service.
waylo said:
Hmm, I found it comes back from time to time. So definitely need to get to the bottom of what pulls down the update. Still don't think we've nailed the offending apk/service.
Click to expand...
Click to collapse
As of yesterday and last night, update.zip did not return after I froze all those apps. I wish I could've pinpointed the exact app. All I can say was I froze all those apps on the first list, and maybe line one or two from the other list and the notification was still on the screen. I rebooted because after freezing so many apps, I was worried about a boot loop. My phone booted fine and the notification was gone and it didn't come back. I just checked cache and update did not come back
Well damnit, the update.zip came back probably last night. I don't have the notification though, that is gone but I'm not happy having that file come back. If anyone at all can pinpoint the reason it comes back, please post!
mattnin said:
Well damnit, the update.zip came back probably last night. I don't have the notification though, that is gone but I'm not happy having that file come back. If anyone at all can pinpoint the reason it comes back, please post!
Click to expand...
Click to collapse
Mine came back too. Deleted the update.zip again.. but would like to disable it for sure.
You could always try moving the files, then put a same-named read only (e.g. chmod 440) file in it's place - or maybe safer yet is put a directory of the same name there.