What is the best way to block OTA updates without flashing a new rom? I am rooted, and have removed some bloat as well a changed the mms.apk, as well as the lock screen. I have also fixed permissions through rom manager. I can use adb etc... Best suggestion?
If you installed CWM recovery you won't receive any updates.
ikon8 said:
If you installed CWM recovery you won't receive any updates.
Click to expand...
Click to collapse
false, you have to change some stuff in the build.prop
magneticzero said:
false, you have to change some stuff in the build.prop
Click to expand...
Click to collapse
You'll still receive update notifications but they won't install. But you're correct that you'll still receive notifications about an available update until you change the fingerprint in build.prop
Is there any particular format to change the fingerprint? Or do I simply change it from what it states to something different? And I assume we are talking about the line ro.build.fingerprint= verizon...etc.
When an update is available you can change the fingerprint to match the update's fingerprint so that it stops notifying you of the update. And yea, it's the ro.build.fingerprint= line.
Or ask someone with the .9 rom or something to upload their build.prop and steal that and hope you dont get an update nag message
Thank you!
Related
I'd be grateful if people on 10.4.2.17 or 10.4.2.18 could check and let me know if the full version numbers on their stock Browsers include the correct build number.
I am currently on 10.4.2.17 though my Browser version says 10.4.2.15 and I believe this may be responsible for my failures to update to 10.4.2.18. Just wan't to check that the build number went up for everyone's Browser with the .17 upgrade.
Many thanks.
Restorer said:
I'd be grateful if people on 10.4.2.17 or 10.4.2.18 could check and let me know if the full version numbers on their stock Browsers include the correct build number.
I am currently on 10.4.2.17 though my Browser version says 10.4.2.15 and I believe this may be responsible for my failures to update to 10.4.2.18. Just wan't to check that the build number went up for everyone's Browser with the .17 upgrade.
Many thanks.
Click to expand...
Click to collapse
Mine says 17
flumpster said:
Mine says 17
Click to expand...
Click to collapse
Thanks. Thought so since all my other systems apps also say .17.
I do remember messing about with the browser after updating to .17 trying to get the damn sync with Google to work so what I think I've done is to restore the wrong version. Looks like this has been a big enough change to the system partition to stop the new update working :crying:.
So my next question is how and where do I get hold of the browser.apk from 10.4.2.17?
Restorer said:
Thanks. Thought so since all my other systems apps also say .17.
I do remember messing about with the browser after updating to .17 trying to get the damn sync with Google to work so what I think I've done is to restore the wrong version. Looks like this has been a big enough change to the system partition to stop the new update working :crying:.
So my next question is how and where do I get hold of the browser.apk from 10.4.2.17?
Click to expand...
Click to collapse
Gimme 5.. I'll pull it out the rom for you.
edit... there you go, attached.
flumpster said:
Gimme 5.. I'll pull it out the rom for you.
edit... there you go, attached.
Click to expand...
Click to collapse
Thanks mate. Will I also need the odex file for the .17 version or are they all the same?
Restorer said:
Thanks mate. Will I also need the odex file for the .17 version or are they all the same?
Click to expand...
Click to collapse
The odex file gets created from the apk. If you have a browser odex file then delete it and when you replace with the new browser.apk and restart it should create it.
flumpster said:
The odex file gets created from the apk. If you have a browser odex file then delete it and when you replace with the new browser.apk and restart it should create it.
Click to expand...
Click to collapse
OK, thanks. The new browser appears to be working just fine. I doubt it's the odex file since I have rebooted a few times. I will delete it though and see what happens.
Grrrr. No good - the droid's still going belly up after a minute or 2. But I am now getting a different error message. Instead of the Unknown Error I now get "The application is not compatible with the device ROM".
I've been right through /system and can't see anything else that would be out of place.
Is there anywhere in particular the update checks? I've tried factory reset and downloaded other copies of the update zip in case I got a bad one. Can you think of anything else I might try?
Restorer said:
Grrrr. No good - the droid's still going belly up after a minute or 2. But I am now getting a different error message. Instead of the Unknown Error I now get "The application is not compatible with the device ROM".
I've been right through /system and can't see anything else that would be out of place.
Is there anywhere in particular the update checks? I've tried factory reset and downloaded other copies of the update zip in case I got a bad one. Can you think of anything else I might try?
Click to expand...
Click to collapse
It is normally caused by something that has changed. Did you edit the build.prop? did you freeze any apps ? did you delete any apps ?
flumpster said:
It is normally caused by something that has changed. Did you edit the build.prop? did you freeze any apps ? did you delete any apps ?
Click to expand...
Click to collapse
The only thing I can think of is if there is a separate Google Bookmarks Sync apk that came with the .17 ROM? I was using an older version of this. If so can you pull me one and I'll try that.
Also I had been using browser2RAM before the update but I uninstalled it properly before doing the OTA update. It hadn't stopped me updating before either.
Restorer said:
The only thing I can think of is if there is a separate Google Bookmarks Sync apk that came with the .17 ROM? I was using an older version of this. If so can you pull me one and I'll try that.
Click to expand...
Click to collapse
Discovered how to extract the system apps from the blob file so found the syc apk (called ChromeBookmarksSyncAdapter) and got that working. While I was there I noticed that odex files were included in the ROM so installed the browser from there along with its odex but still the update failed :crying:.
I think now all I can do is go through the system.img from the .17 update and see if I can see anything different from what I have currently on the device.
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Alternatively, you can simply freeze the System Updates process via Titanium Backup, as discussed in the Bloatware thread.
What OTA ?
Cruiserdude said:
What OTA ?
Click to expand...
Click to collapse
I think they are just being proactive... in case one comes this year.
Cruiserdude said:
What OTA ?
Click to expand...
Click to collapse
My thoughts exactly. Disable updates for what? Verizon has their heads up their asses in that regard.
Wildcat2083 said:
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Click to expand...
Click to collapse
Thanks for the information. Verizon began pushing an OTA to my LG G3 today. It was very annoying, thanks again!
Thank you, but it seems I'm too late.
Now, event though I've unchecked it, I keep getting a menu to do an update. I keep pressing back to get out of the update now or schedule an update later, but I can't seem to get it to go away, Gonna try the titanium update freeze of the updater.
Disabling the System Updates apk also works.
Sent from my VS985 4G
Thanks for sharing!
Tillmorn said:
Alternatively, you can simply freeze the System Updates process via Titanium Backup, as discussed in the Bloatware thread.
Click to expand...
Click to collapse
Alternatively you can do what OP said since its easier and requires no third party apps or root. But hey, cool story bro.
Thank you. This method works. I tried the other two and they didn't work. The "hidden menu" version came up with a different menu than in the description and TiBU didn't stop the notifications (for me). First I tried moving the update files to a new directory I created, but the update message had already been triggered.
If you pull down the notifications and long-press on the OTA, you can disable the app and remove the icon from the screen.
Wildcat2083 said:
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Click to expand...
Click to collapse
Wildcat2083 said:
I found a useful trick to keep the ota from showing up, if you enter ##3328873 in tge dialer pad and enter 000000 for the service code you then can uncheck the ota-dm mode this should prevent any ota
Click to expand...
Click to collapse
At first I thought this worked, but it ended up not working. As you can see in the image below, I have the ota-dm unchecked, which worked for a while, but today the system update dialog/notification came back.
killswitch23456 said:
At first I thought this worked, but it ended up not working. As you can see in the image below, I have the ota-dm unchecked, which worked for a while, but today the system update dialog/notification came back.
Click to expand...
Click to collapse
Getting this too
Same here
Use Rom toolbox pro to freeze the 2 ota apps, titanium is junk.
Afterwards, delete any files in root/cache/fota.
Sent from my VS985 4G
Or use free app called Uninstall Expert and freeze it that way too
Sent from my Verizon LG G3 using Tapatalk
NetworkingPro said:
Alternatively you can do what OP said since its easier and requires no third party apps or root. But hey, cool story bro.
Click to expand...
Click to collapse
If you've already got root...which most people who are trying to stop OTAs have because they're wanting to keep root...why would you not simply freeze the process while you're going about the task of freezing all the bloat from Verizon? To me, that's easier as it allows a single action to restore everything back to stock settings (plus root and Bump) instead of having to use multiple methods to get back to such a state. But to each their own. I understand that some people like having their mobile OS weighed down from carrier installed garbage. Regardless, what kind of person knocks someone else for daring to add to the discussion with another method that, for many (especially those eventually wanting to flash ROMS), streamlines everything?
What are the exact names of the OTA apks? I looked in system/app and system/priv-apps.. Nothing really reads as system Ota or Ota something. Maybe I missed it. I would like to rename them manually.
Edit: is it LGFOTA.apk and its odex file?
Edit: ok thats not it update popped up after reboot. I now think its LGDMSClient.apk
jfriend33 said:
Or use free app called Uninstall Expert and freeze it that way too
Sent from my Verizon LG G3 using Tapatalk
Click to expand...
Click to collapse
This worked for me! Thank you very much!
MunkinDrunky said:
What are the exact names of the OTA apks? I looked in system/app and system/priv-apps.. Nothing really reads as system Ota or Ota something. Maybe I missed it. I would like to rename them manually.
Edit: is it LGFOTA.apk and its odex file?
Edit: ok thats not it update popped up after reboot. I now think its LGDMSClient.apk
Click to expand...
Click to collapse
It's a blue icon called 'system updates' in your application manager in your settings.
Has anyone been able to successfully disable the system update notification on the watch for the 5.0.2 update yet? If so, would you mind sharing your technique and what is required (root, adb, etc...) I've not yet rooted but unlocked my bootloader and have installed Arter97's 2.1 Kernel. I toyed around with the idea of trying to rename or delete the update.zip in the /cache partition, but I apparently have insufficient permissions via adb to that partition, probably due to not rooting. If I simply deleted the update.zip, I expect that it will simply download again and I'll have this same issue again right? Thanks all.
Nobody has figured this out? I just don't to update; seems like more problems that I don't want.
altivoid said:
Nobody has figured this out? I just don't to update; seems like more problems that I don't want.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=59230170
Why is not possible to update from previous versions is that?( ota)
And is there a way to be alerted(get notofation on the phone) to update existing modules instead of occasionally enter the Xposted?(Was the only way my understanding?)
adome5 said:
Why is not possible to update from previous versions is that?( ota)
And is there a way to be alerted(get notofation on the phone) to update existing modules instead of occasionally enter the Xposted?(Was the only way my understanding?)
Click to expand...
Click to collapse
Up.. Someone?
adome5 said:
Up.. Someone?
Click to expand...
Click to collapse
Because it's not coded yet. Xposed is an open source project, by the way. You want installer to be able to update over-the-air? You want periodic update check and notifications? Go on, code it and submit a pull request.
To be honest I do not know how to do it and I just noticed that and thought to offer it as a proposal for streamlining. Also for alerts and regarding the automatic update ...
Introduction:
As we all know, the A2017U, and G come bundled with a few themes and that's it. Well, the Axon 7, Chinese variant, not only includes more, but also a theme store that you can download from. This thread contains packages from the Chinese ROM that will enable your phone to use the theme store with a small caveat--you have to register for a ZTE Account (more on that below) and log in to it in order to download themes. ZTE's theme engine is pretty basic and doesn't really allow for much customization, but anything is a welcome addition to what we currently have.
What ZTE's theme solution does:
-Changes Icons
-Changes wallpaper
-Basic color schemes for settings, and some ZTE apps
-Changes Lockscreen appearance
Procedure
First, you'll need to register an account here. It is all in Chinese, so I would suggest using Google Translate so that you can understand what you're doing. You'll need to click the "email registered" tab because registering with your phone number will not work. Once you have registered and validated your account, you can use it to log in to the theme store on your phone and begin downloading themes.
Current issues
ZTE's dynamic lock screen doesn't allow you to swipe to unlock your phone when you have notifications and they're visible. What you'll need to do is to tap the "bell" icon to hide your notifications in order to swipe to unlock. Fingerprints bypass this. I'm sure someone talented can decompile the two lock screen apps and figure out how to change this. I won't be doing it.
Download: ZTE-A2017-ThemeStoreMOD-by-freeza_DrakenFX
This flashable will include the following:
ZTE Account
Theme Store
Lock Screen Framework
ZTE Lock Now
app permissions whitelist so these apps should automatically be granted the proper permissions
Thanks
DrakenFX for being awesome, giving me the idea to try this, and giving me the ZTE Account registration link.
Great work! I know this a stretch but wondering if this works on LOS or RR?
EDIT: Finally tried it on RR. It didn't work. Guess it's only for stock atm.
So this way you can get the stock theme on the European model?
razorsbk said:
So this way you can get the stock theme on the European model?
Click to expand...
Click to collapse
I guess there isn't a stock theme in there, but maybe there is. Could someone confirm?
All I want is a ZIP that gives me a dark theme for apps like Settings. I don't really want to install all this just to get access to a theme store that may or may not have a dark theme. If anybody spots one in there and can make a ZIP out of it, I'll be eternally grateful.
Sorry for the noob question, but how do I install this?
@freeza, is this a lock screen, could you share the theme name to download.
@freeza it's ok on A2017U 7.0, but seem not work well on A2017U 7.1.1 .
@freeza
How to flash this on stock 7.1.1
with twrp as mount system as read only??
Or
With stock recovery
Should i need root or not
Also should i disable system write protection
I flashed this once in twrp as mount system as read-only but after flashing device stay in in the warning screen like forever
tamahouse02 said:
@freeza it's ok on A2017U 7.0, but seem not work well on A2017U 7.1.1 .
Click to expand...
Click to collapse
This Theme works and should work in any N base software ( probably MM as well )
Druboo666 said:
@freeza
How to flash this on stock 7.1.1
with twrp as mount system as read only??
Or
With stock recovery
Should i need root or not
Also should i disable system write protection
I flashed this once in twrp as mount system as read-only but after flashing device stay in in the warning screen like forever
Click to expand...
Click to collapse
Easy, boot to TWRP and flash zip file = DONE.
then proceed with ZTE account creation
DrakenFX said:
This Theme works and should work in any N base software ( probably MM as well )
Easy, boot to TWRP and flash zip file = DONE.
then proceed with ZTE account creation
Click to expand...
Click to collapse
Having bootloop after flashing zip
Druboo666 said:
Having bootloop after flashing zip
Click to expand...
Click to collapse
Were you rooted? or which variant are you? IF you can give a little more info, it wont be so hard to help
I registered with email, but logging in, in the app, only allows logging in with a phone number. What?
Edit: Nevermind, tapping "others" in the bottom left allows logging in by email.
Edit 2: And am I just doing something wrong, or do the icon packs not work? I thought it might just be an issue with Nova Launcher, but the icon themes don't seem to work on the stock launcher either.
Edit 3: I just noticed there's an app called Screen Lock installed now (which does exactly what it's name says) did that come as a part of this installer?
DrakenFX said:
This Theme works and should work in any N base software ( probably MM as well )
Click to expand...
Click to collapse
Nope,
After I applied the theme
- Lockscreen is applied for a few second, then be replace again by stock android lockscreen (not ZTE lockscreen)
- The quick setting panel not change color follow the theme, even the setting did
DrakenFX said:
Were you rooted? or which variant are you? IF you can give a little more info, it wont be so hard to help
Click to expand...
Click to collapse
No i am not rooted
my phone model is A2017U
Is there any black theme so we can make good use of the amoled screen or not?
Thanks
Is there a way to uninstall after flashing? I only installed it to see if I could figure out where the image for the clear view background (for axon 7 clearview windowed case) is stored. It didn't help me figure it out, so I was wondering if I can uninstall it. Thanks.
bafangul said:
Is there a way to uninstall after flashing? I only installed it to see if I could figure out where the image for the clear view background (for axon 7 clearview windowed case) is stored. It didn't help me figure it out, so I was wondering if I can uninstall it. Thanks.
Click to expand...
Click to collapse
Restore your backup. Hope you backed up your Rom before you flashed.
tolymatev said:
Restore your backup. Hope you backed up your Rom before you flashed.
Click to expand...
Click to collapse
Thanks tolymatev. I didn't think of that. And then again I didn't think of backing up before flashing either. Slowly learning.
bafangul said:
Thanks tolymatev. I didn't think of that. And then again I didn't think of backing up before flashing either. Slowly learning.
Click to expand...
Click to collapse
There's other ways, Im just not sure what's in the zip. You can check what's in the zip, what gets flashed to your system and then use root explorer or something similar to manually delete the apk/files that were flashed. Be careful though. Definitely backup before you do that.