Here's my story. i had the new update brick my phone. i managed to backdate it to the I317UCUCNJ1 that worked previously, only for it to start begging for an update again and brick again i backdated once more, then deleted everything i could for the updates. now the Phone wont update, but it notify's me every damn day, several times, to get the update. i click ok and it just closes out, but how can i get this off
the problem is, the phone is rooted and it keeps bricking. if i flash it back to the previous version, what are my options? i've never had success with triangle away and i'd hate to really do some damage. its time for a new phone soon but i'm holding on to the 2 for now.
thanks for any help
If the phone is rooted...
Download the pro version of titanium backup from the play store....and freeze the software update apk from within titanium backup....and done...
The free method would be too locate the update apk and delete it using a root explorer app....
Either way....those nag screens for an update will stop...
Note:
UCUCNJ2 Update provides a partial patch for the stagefright exploit..
It is assumed that Samsung and ATT will be releasing another patch to fully isolate the stagefright bug...
If you want to stay fully protected....you could use an AOSP rom such as cyanide or CM 12.1 official as they are already fully patched.....but I'm not sure what OS you prefer...
I use both cyanide and CM12.1 official as I don't like bloated Samsung roms....g
Related
It seems like ever since the market updated to google play i can't download any new apps on my phone (the force close and disappear as soon as i open them). Also, when i try to update existing apps they also force close and disappear but they end up coming back if i restart my phone. Also applications that i've had on my phone that i don't use any more I can't get rid of. I delete them and they come right back as well.
I've tried to restore my phone in tons of diffrent ways, regular factory reset, ruu, thought hboot, and htc sync. Factory reset and hboot just give me a red exclamation that i can't get around, the ruu someone told me to use didn't work i believe because the version of android i'm running and htc sync always tells me my phone isn't connected when clearly it is because i can open it up and explore it on my computer.
I'm at a loss, anyone have any ideas?
Time for a new phone?
Maybe consider rooting? I actually haven't seen a dinc with GB 2.3.4 that upgraded to google play, for some reason I've seen it stay with the market. My phone hasn't been in stock for a long time so I couldn't really say if that were true now but I know that google play was first released back in March and mid-april when I first rooted my Dinc, it was still on the android market. That being said, the dinc is far from trash if you are willing to root and flash a custom ROM to it.
I've seen this problem on ROMs when the version of gapps wasn't compatible with the ROM anymore because either the ROM was updated or gapps was updated and compatibility was lost. Usually in that situation I would recommend that person to do a fresh flash of their ROM with the newest google apps but in your case I would suggest flashing a custom ROM for the first time. if that is not an option you want to explore at this time, I believe that if you place this PB31IMG.zip on the root of your SD card (which must be formatted to FAT32) and then get into hboot it will reflash gb for you which might do the trick.
http://www.mediafire.com/?1ovb6959r9qyg6w
my DINC upgraded to google play when it was on stock. But really, stock sucks and has bugs. Upgrade to a real firmware listed here
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Capa1970 said:
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Click to expand...
Click to collapse
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
WearySky said:
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
Click to expand...
Click to collapse
I am not rooted.
Capa1970 said:
I am not rooted.
Click to expand...
Click to collapse
I wasn't able to find any way to get around Knox without rooting, but I may not have looked hard enough.
If you're willing to root first, CF Auto Root was super easy to do:
http://forum.xda-developers.com/showthread.php?t=1963790
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Capa1970 said:
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Click to expand...
Click to collapse
That *is* a Knox message, for sure.
So it looks like the Cyanogenmod team were not able to circumvent Knox for their CM installer. It's probably just a matter of time. Here is the full Knox notification:
"An application attempted to access system on your device without authorization. This attempt has been blocked. Updating your security policy may solve this problem. Deleting applications obtained from unauthorized sources may improve security."
There are three options at the bottom of the screen: Cancel, Update, and View Apps.
Update: I was able two days ago to use the Cyanogenmod Installer and I am now running CM!! First time for me to ever root and flash a Rom (I was an iPhone guy).
The phone is faster and smoother. I never liked the Touchwiz lag and most of the Touchwiz features worked inconsistently. The only thing that I miss is the camera. I have not found any bugs yet and so am very happy thus far.
I have literally said yes to updating every time it pops up. I know it's the same, because it's the same size every time (293.3 MB). Not to mention I've said "accept" every time, installed, reboots my device, then couple days later it tells me to do it again. Another thing to note are the same 3 systems apps asking to be updated (Voice Mate Speech Pack, Voice Mate, Voice Mate Engine).
Text from the update:
This update will ensure your device is working at optimal performance with the Sprint Network. The update will require that your phone is rebooted and it will not be available for emergency calls while installing the software.
My LG G3 is the Sprint variant (ls990), rooted via Stump Root and on the stock android. I have used G3 TweaksBox, as well as installed Xposed.
PM me for a link to the screenshots.
Anyone with an answer? Google only refers to Lollipop updates that are still not here anyways
Plumato said:
I have literally said yes to updating every time it pops up. I know it's the same, because it's the same size every time (293.3 MB). Not to mention I've said "accept" every time, installed, reboots my device, then couple days later it tells me to do it again. Another thing to note are the same 3 systems apps asking to be updated (Voice Mate Speech Pack, Voice Mate, Voice Mate Engine).
Text from the update:
This update will ensure your device is working at optimal performance with the Sprint Network. The update will require that your phone is rebooted and it will not be available for emergency calls while installing the software.
My LG G3 is the Sprint variant (ls990), rooted via Stump Root and on the stock android. I have used G3 TweaksBox, as well as installed Xposed.
PM me for a link to the screenshots.
Anyone with an answer? Google only refers to Lollipop updates that are still not here anyways
Click to expand...
Click to collapse
You know OTA`s will only be installed when a device is unrooted and doesn`t have any system modifications. Either disable OTA notifications or flash a stock rom and have root removed or flash a custom recovery and rom.
gee2012 said:
You know OTA`s will only be installed when a device is unrooted and doesn`t have any system modifications. Either disable OTA notifications or flash a stock rom and have root removed.
Click to expand...
Click to collapse
I assumed that was the actual issue, thanks.
my issue still exists
Plumato said:
I assumed that was the actual issue, thanks.
Click to expand...
Click to collapse
Yaar my issue still exists its not rooted and I am using in Pakistan - also my Roaming setting crashes as soon as I open it. Would be better to root and add custom ROM to it?
A couple hours ago my phone with unlocked bootloader, twrp and magisk root installed an OTA update without me initiating it. This failed and the phone was stuck in twrp recovery and couldn't boot until I flashed a stock rom through fastboot and restored my backups.
Now I want to prevent this from happening again. How do I block the phone from checking for OTA updates?
I will have to install them manually anyway so the OTA checking is not helpful.
Same thing happened to me except I was dumb enough to try and install myself the update... You can install Titanium Backup and freeze the Motorola Update app. Also, you can go under dev options and disable automatic updates (this alone didn't work for me).
How to prevent OTA updates, without root, please?
I followed this guide, the method 4 worked for me when my phone was rooted.
http://www.droidviews.com/disable-ota-notifications-android-devices/
With help from the Google, I finally recalled how I'd done it in the past.
Initially, I thought rooting would stop OTA updates, but that may have been prior to Marshmallow or with SuperSU.
This time, I used Titanium Backup (must be rooted) to freeze the MOTOROLA UPDATE SERVICE app.
As soon as it was frozen, the OTA notification disappeared from the notification bar and I gave not seen it return, for a couple days.
Yay! I didn't want to go beyond the stock firmware version that is available and I really didn't want Oreo.
Another way is to use a firewall app.
Also you can just add Motorola's address to your 'host' file to block it
Im the opposite, I want the notifications, without the automatic installation.
Wonder if I changed the permissions of the folder the updates download to, would that prevent automatic install?
also, there is an option in developer options, to turn off OTA.
Does anyone know how to keep the system update notification from appearing in Oreo? No system notifications stop it nor does anything that can be done in the Updater app stop it. All searches come back with Nougat results only and seem to be about getting rid of the file if it has been downloaded or with stopping auto-update. I have not downloaded it and stopped auto-update, I just keep hitting later and then disagree to the second prompt immediately after the first is dismissed.
I have a rooted Mate SE on Oreo. I found the same thing. To make it go away I download the updates and apply them. Then I must reinstall TWRP and rerun Magisk to get root back.
I use, https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
To do the updates.
It's quick and painless - done it 5 times now with updates.
Bevnrick said:
I have a rooted Mate SE on Oreo. I found the same thing. To make it go away I download the updates and apply them. Then I must reinstall TWRP and rerun Magisk to get root back.
I use, https://forum.xda-developers.com/honor-7x/how-to/guide-honor-7x-flash-oreo-update-t3781649
To do the updates.
It's quick and painless - done it 5 times now with updates.
Click to expand...
Click to collapse
I appreciate the answer, and I had a feeling that just updating might be the only way. That post sure doesn't make it sound "quick and painless" to stay rooted and BL unlocked. I would definitely go through a lot if it were getting P, but I am willing to ignore the update if there is no real functional change.
Froze the EMUI System Update process with Titanium Backup. No notifications on two devices in over 24 hours with a couple of reboots included. I think that was the trick.