Related
I currently have a Moto G 8GB rooted on ver 4.4.2 stock rom
For the last 2 weeks I have been getting pop ups telling me to update my phone to 4.4.4 but because I am rooted I always pressed 'No, maybe later', but today I was unlocking my phone and i saw the pop up to update, i wasn't thinking and I accidentally pressed 'Yes, im in'. About 10 seconds after pressing Yes, im in' I saw a system update download notification, so i instantly turned my phone off. When ever I turn my phone on the system update downloading notification comes up.
What can I do to stop the update?
Thanks in advance for the help!
As far as I know you can't stop the download, but when I did an update on stock after the download finishes you are asked if you want to install it, click no and then delete the update from your phone,
Sent from my bricked Moto G
You can turn off you cellular data and that will also stop the download. But once it is back on then the download will continue unless there is a way to delete the actual file. But if you are on WiFi then just turn that off. Either way, you can stop the download but what you do after that is unknown.
plewis1981 said:
As far as I know you can't stop the download, but when I did an update on stock after the download finishes you are asked if you want to install it, click no and then delete the update from your phone,
Sent from my bricked Moto G
Click to expand...
Click to collapse
Thanks for that. I have got the update downloaded but I don't know where it is stored. Can you tell me where I can find the file?
SkitzXDA said:
Thanks for that. I have got the update downloaded but I don't know where it is stored. Can you tell me where I can find the file?
Click to expand...
Click to collapse
I'm not to sure about that,but you may be able to find it with this app https://play.google.com/store/apps/details?id=com.levelokment.storageanalyser it will show the contents of your SD partition in order of how much data is contained in the folders from highest to lowest, I think the update is between 400 and 450MB
Sent from my bricked Moto G
plewis1981 said:
I'm not to sure about that,but you may be able to find it with this app https://play.google.com/store/apps/details?id=com.levelokment.storageanalyser it will show the contents of your SD partition in order of how much data is contained in the folders from highest to lowest, I think the update is between 400 and 450MB
Sent from my bricked Moto G
Click to expand...
Click to collapse
I think the update file.zip on SD card only about 167MB if you from 4.4.2 to 4.4.4.When u on 4.4.3 to 4.4.4,the update file about more than 10MB as i know.
Sent from my XT1033 using Tapatalk 4
@SkitzXDA ..... Look in the file folder named .... /cache
go to Settings>Apps>All
Select Motorola OTA
Disable it.
You are done .
KapilFaujdar said:
go to Settings>Apps>All
Select Motorola OTA
Disable it.
You are done .
Click to expand...
Click to collapse
No idea if this works, but the file is under /cache. Not on your internal memory, but in the actual /root directory of your phone. You'll need a Root explorer to find and delete the file. Good luck!
Thnaks Guys for all the help. I fixed the problem by downloading the update and then deleting it from the /cache folder
May I ask if I am already rooted and unlocked in 4.4.2, can i just OTA update to 4.4.4?
Will root still intact (using root keeper or whatever)?
-Zeta- said:
May I ask if I am already rooted and unlocked in 4.4.2, can i just OTA update to 4.4.4?
Will root still intact (using root keeper or whatever)?
Click to expand...
Click to collapse
You've to remove root and make sure. you didn't modify anything in the /system partition.If you did debloat your phone or modified /system, then you need to flash the stock one first, then you can update and root your device again.
SkitzXDA said:
Thnaks Guys for all the help. I fixed the problem by downloading the update and then deleting it from the /cache folder
Click to expand...
Click to collapse
I'm having the same problem except I can't find it in my cache folder.
In my cache folder there are: backup, lost+found, recovery folders, none of which seems to have a 160MB~ file.
RealyPssd said:
I'm having the same problem except I can't find it in my cache folder.
In my cache folder there are: backup, lost+found, recovery folders, none of which seems to have a 160MB~ file.
Click to expand...
Click to collapse
You can wipe cache partition in recovery.
unknownemous said:
You can wipe cache partition in recovery.
Click to expand...
Click to collapse
Thanks, I had done that to try and fix another problem I was having and it worked.
Hello, all!
I'm wondering, how do you cancel an OTA update once it has started? I mean after it has downloaded, and you have chosen to install it.
Here's my problem: Everyone talks about how running an OTA update unroots your phone. No problem, I can just re-root it. What no one talks about (at least I didn't run across it before doing this) is installing OTA updates when you have TWRP installed...
So, my phone downloaded the update, and it asked me to install it. I accepted, it restarted, and TWRP came up. From there, nothing happened. I tried restarting it, and it booted up just fine. After about a minute of being up, the "Phone is shutting down" (or something along those lines) message pops up, and it reboots again.
I'm wondering, how do I go about cancelling the update? I've read online I need to download the update manually and run it through TWRP, but until I learn how to do that (and spend a few hours downloading it on this freaking slow internet connection), I would like to be able to use my phone.
Another alternative that I don't know whether is possible, can I somehow use TWRP to browse to where the OTA update was downloaded to, and install it through there? If so, what would the procedure be for doing so?
Thanks!
ElectroPulse
ElectroPulse said:
Another alternative that I don't know whether is possible, can I somehow use TWRP to browse to where the OTA update was downloaded to, and install it through there? If so, what would the procedure be for doing so?
Click to expand...
Click to collapse
Boot into TWRP, click install, click(Up A Level) until you are at "/" and look in the cache folder for the update zip.
It should be in there.
meekrawb said:
Boot into TWRP, click install, click(Up A Level) until you are at "/" and look in the cache folder for the update zip.
It should be in there.
Click to expand...
Click to collapse
Thanks for the reply!
Is it the "Blur_Version21.23.4.peregrine_retus.retus.en.US.zip" file? If so, that didn't work... Unfortunately it failed.
Here's what it said just before failing:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/cache/..."
Error flashing zip '/cache/..."
Updating partition details...
Any ideas?
Thanks!
ElectroPulse
ElectroPulse said:
Thanks for the reply!
Is it the "Blur_Version21.23.4.peregrine_retus.retus.en.US.zip" file? If so, that didn't work... Unfortunately it failed.
Here's what it said just before failing:
Verifying current system...
"/system/bin/debuggerd" has unexpected contents.
E: Error executing updater binary in zip '/cache/..."
Error flashing zip '/cache/..."
Updating partition details...
Any ideas?
Click to expand...
Click to collapse
You must have stickmount installed. Uninstall it and try again.
Note: If you changed or deleted anything in /system partition the install will keep failing. You'd have to fastboot flash the system img's from the 4.4.3 firmware.
meekrawb said:
You must have stickmount installed. Uninstall it and try again.
Note: If you changed or deleted anything in /system partition the install will keep failing. You'd have to fastboot flash the system img's from the 4.4.3 firmware.
Click to expand...
Click to collapse
Thank you for the reply.
Nope, Stickmount is not installed. Not sure what other apps there are that could cause this.
Not sure whether I've changed anything in /system... I don't believe I have, but an app I installed very much could have.
I'll look up this "fastboot flash" you are referring to.
Anyway, for now I am good. I copied the .zip OTA downloaded file to another location, hit the "clear dalvik and cache," rebooted, and I'm back to a working 4.4.3.
Problem solved until I decide to try to get 4.4.4 installed! (which I may never end up doing... Now that Cyanogenmod is officially out for Peregrine, I'm probably going to flash it with that when it gets stable enough (i.e. no RAM issues)).
I have rooted my A9 and deleted various system files to my liking. Im wanting to disable OTAs but ive noticed that things are different in the file system while browsing with root explorer. I installed the fotakill as a precation but I couldnt find any info on whether or not it would work on marshmallow. Also, I searched for the wssyncmldm.apk that att used for ota updates but couldnt find it either. Can anyone point me in the right direction? or will otas stop automatically now that ive alterned the system?
Just use titanium to freeze softwareupdater
I just wanted to follow up. After a few days rooted and deleting some system apps the "att software update" is totally gone from my settings. This is interesting because I didn't delete anything related to updating.
Sent from my HTC One A9 using Tapatalk
You can do the "freeze" trick. But, if you are rooted: Root Explorer and just rename /system/priv-app/Updater/Updater.apk to Updater.bak
Restart. It will completely remove the updater option from your About/Software update location and won't check for updates any longer.
Hello
I'm trying to update from 41.2.A.7.35 to 41.A.7.53 using flashtool. I am relatively familiar with Flashtool at this point. I have installed stock firmwares a couple of times. Each time I have flashed a firmware i checked all boxes in the "Wipe" pane giving me a fresh install.
What i was curious about was, how can i prevent from formatting my drive each month when a new update rolls out. So what setting do i leave checked and unchecked in the flashtool? I'm mostly concerned with retaining apps and appdata along with settings and messages.
Thank you
I normally mark all in wipe section. Today i flash customized AU without problems.
normally no wipe neccessary
Hummusman said:
how can i prevent from formatting my drive each month when a new update rolls out. So what setting do i leave checked and unchecked in the flashtool?
Click to expand...
Click to collapse
If you do not upgrade the Android version, or go from 39... to 41... or you have "strange" behavior before or after the upgrade: do not wipe anything
Some partitions like /system are overwritten anyway. If you are root you might get away with wiping cache/dalvik if anything feels strange.
When switching ROMs or upgrading Android versions I use Titanium backup to shorten the process:
- look for unsaved apps after upgrade -> bloat candidates, let TB delete deal with them after looking at the list and deciding what to let go
- restore all user apps with data
- manually restore all logins of apps that have accounts e.g. email (the time consuming part)
I use Apex launcher and its setting are restored too, so I will have a familiar look and feel even on a different ROM.
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Thank you! This saved me from several hours of tweaking this stupid samsung security.
Thank you @Chamelleon! I was about to get in to a full reflash stock, reroot, reinstall situation. Damn, I love xda!
BTW, the thing I did differently was to remove the three lines inclusive of
<disabled-components>
<item name="com.samsung.android.kgclient.receiver.KGAgentReceiver" />
</disabled-components>
...and changed enabled="3" to enabled="1" in this line
<pkg name="com.samsung.android.kgclient" ceDataInode="2643" enabled="1"
Probably not required, but thought I'd mention it.
Galaxy Tab S6
Android 9
Stock-Rooted
i cant find the line even if i search it
I tried attempted to debloat an S8 (running Pie), but I started receiving this message afterwards. There's no “com.samsung.android.kgclient” in the package-restrictions.xml file. Is there any other place this restriction could be enforced?
Found Another Way 2
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
I went in and deleted package-restrictions.xml and the bak file, I can reboot now and get in with the message, I initially uninstalled payment services, I tried flashing a zip of payment services apk couldn't get that going, now I'm getting android set up pop ups and my twrp won't boot to the recovery loader from within the app, and super su has lost all the settings for applications!?¿ rlly don't want to do a clean flash and re root ... bloody system packages arggghf help
Wow, this was easy. Thanks!
harismuntazir said:
in my case i copied the file package restrictions but did not found the line or the package in it.
What I Did
1. download the Samsung payment services apk from apkmirror.com
2. installed this app as a system app using lucky patcher.
Note: i guess we can use the adb tool too to install apps as system apps.
3. Nothing just restart and done.
Also this can be overcome in every restart without installing the above app. As you may have noticed device waits some time after the restart before pushing the notification and locking the device. What i found is that if we restart the SystemUI it disables the lock and does not show it up until next restart.
Enjoy and Keep Sharing.
Click to expand...
Click to collapse
Hi..how to restart system ui within so limited time
Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" /> line from the file. It can have different values but package name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
i cant find this xml anywhere, please help
Any advice if twrp isn't yet installed but device is already rooted?
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
JoshReuben said:
Solution is to reboot to Samsung recovery and factory reset. Worked for me.
Click to expand...
Click to collapse
luckily factory reset solves it. i was already getting anxious about paying "ransomware" to samsung service oof
thanks
but my TWRP doesnt mount data
CANDco said:
but my TWRP doesnt mount data
Click to expand...
Click to collapse
Only hard reset can fix Your phone then. If TWRP can't mount data it means that your phone is encrypted and without full wipe you won't be able to unlock it.
Thanks! I just fixed my m51 with this method. I was thinking about restoring full TWRP backup or flashing stock rom as last resort. So glad I found this thread.
I don't know what is wrong with my phone. I disabled the app, and got the message. I did what you suggested and rebooted. but the app re-enabled itself. I tried disabling again and the message came up again. I checked and that line is no longer in my package-restrictions.xml
Luckily for me, just rebooting unlocks my phone, but I think that defeats the purpose....
I kinda want to get rid of that app
adb shell pm enable com.samsung.android.kgclient
will solve the problem
jafferkhan said:
i cant find this xml anywhere, please help
Click to expand...
Click to collapse
Man, that was a trip to do, but on my unlocked S9+, it worked! I could only see the exact file when I opened the .xml file with wordpad on my Win. 10 to edit it, otherwise it's very hard to spot scrolling in TWRP on the device, particularly since the long package list can freeze up while you scroll down.
I should add, that I used an OTG USB Bridge with a type C connector to paste the copied .xml file to the connected flash drive I mounted in TWRP (just scroll up through the directories for "OTG USB' to find the drive to paste it), then put it on my PC, this made the process go even faster.
But it's better to proactively check what apps can be disabled, removed, or in my case frozen with Titanium Pro, before ever having to deal with such a scare as this!
Chamelleon said:
If you ever lock Your Samsung because of disabling Samsung Payments or by debloating and You have TWRP installed here is a fix.
Boot to TWRP and using File Manager copy data/system/users/0/package-restrictions.xml to SD and then copy this file to PC to and open in notepad or any text editor.
Remove <pkg name="com.samsung.android.kgclient" ceDataInode="-4294836077" enabled="3" enabledCaller="0/" />line from the file. It can have different values butIpackage name must be the same. Remove whole line, save file and place it back to data/system/users/0/. I suggest to delete old package-restrictions.xml and package-restrictions.xml.bak before placing back edited file.
That's it, phone should be unlocked now.
Click to expand...
Click to collapse
What are procedures on how to remove the file after disabling the package, my Samsung A03 CORE can't mount. So kindly assist me here..