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..
Related
Hi Guys,
Every ROM I flash I try to Freeze/Uninstall and remove from Boot Many, the YouTube App.
I don;t use it ever, but even if it says freezed successfully it still comes back after reboot.
What's so special about it and will it creat a problem if I delete it and main question is how?
Thank you
odeccacccp said:
Hi Guys,
Every ROM I flash I try to Freeze/Uninstall and remove from Boot Many, the YouTube App.
I don;t use it ever, but even if it says freezed successfully it still comes back after reboot.
What's so special about it and will it creat a problem if I delete it and main question is how?
Thank you
Click to expand...
Click to collapse
In my other android device experience, Nook Color / Simple Touch, YouTube is instrumental in the Google Apps authentication process. For instance to get market working on nooted versions of those devices you had to sign into YouTube first.
Why are you trying to get rid of it?
promiseofcake said:
In my other android device experience, Nook Color / Simple Touch, YouTube is instrumental in the Google Apps authentication process. For instance to get market working on nooted versions of those devices you had to sign into YouTube first.
Why are you trying to get rid of it?
Click to expand...
Click to collapse
Never used it, if I need to I can view it in the brother. Just another app that loads up on boot and sits there using the battery
odeccacccp said:
Never used it, if I need to I can view it in the brother. Just another app that loads up on boot and sits there using the battery
Click to expand...
Click to collapse
Fair enough. Why don't you give it a try? Make a nandroid backup and then delete the file via ADB in recovery mode (or move it to /data/local/tmp for easy restore). Clear Cache / Dalvik reboot and see if anything isn't working properly.
I would say you can delete via ADB in ICS but many people, myself included, are having issues mounting /system in ICS. It could be possible that this failure for /system to consistently mount could be why TiBu isn't freezing it properly.
Use root uninstaller, its how I have removed all system apps since my gb 2.3.1 days on my x10. A very effective method
Thank you for responces.
The proper way I found would be to transfer it to a User App and uninstall.
odeccacccp said:
Thank you for responces.
The proper way I found would be to transfer it to a User App and uninstall.
Click to expand...
Click to collapse
Just delete the .apk before you even put the zip on your phone
xcrazydx said:
Just delete the .apk before you even put the zip on your phone
Click to expand...
Click to collapse
What do you use to modify and save zip's, just WinRar will do?
odeccacccp said:
What do you use to modify and save zip's, just WinRar will do?
Click to expand...
Click to collapse
I use 7zip. open the archive and delete it, or add whatever .apk you desire. I always do this before I even flash a rom. Winrar should work fine, though.
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
Go into the settings of ES file explorer and check everything under root settings. The only folder you want to get rid of is the Apps in the vendor folder. Anything else can harm the system. I just used the cut feature on the apps folder and pasted it to my sd card to make sure it worked first. Good Luck!
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
theonyxphoenix said:
. then switch to boot in parent mode, .
Click to expand...
Click to collapse
how ?
theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
Guess I missed something and should've read better, how did you set it to boot only into parent mode.
Sent from my SAMSUNG-SGH-I957 using xda premium
theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
How do you set it to boot into parent mode?
byohaserd said:
How do you set it to boot into parent mode?
Click to expand...
Click to collapse
Did you try going to settings -Security - put a TIC in " Set Parent Mode as default mode " ?
---------- Post added at 07:15 AM ---------- Previous post was at 07:07 AM ----------
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
---------- Post added at 07:28 AM ---------- Previous post was at 07:15 AM ----------
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
I used TWRP to do anything - rooted or unrooted you can make change as you wish .
when you are in TWRP mount system then use advanced and file manager
hope this helps
I did not see that until you mentioned it...thanks
I was able to get it to work by going into a startup manager and freezing kidsmode2 and nabimode. I erased the apps folder though cause I wanted the space freed up.
Sent from my NABI2-NV7A using xda app-developers app
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Rest to Factory setting
mikewhit001 said:
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Click to expand...
Click to collapse
1-switch off.
2-press power button & vol + together.
3-press vol - to go to recovery kernel and press vol + to select it.
3-android model should come lying down with red triangle!.
4-press vol - & vol + together.
5-select the system reset and press power button.
6-after that switch off and on with all new factory settings.
Best Regards.
Eric Karz said:
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
Click to expand...
Click to collapse
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Nabi 2 Charge/Reboot problem
t499user said:
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Click to expand...
Click to collapse
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
I flashed your package but the android upgrading still shows up for me,only for a few secs and it seems as if no programs get upgraded...what are your thoughts on this? How can I find the stray files that are causeing this?
Sent from my NABI2-NV7A using xda app-developers app
stuck in TWRP
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
mikewhit001 said:
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
ALD3 said:
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
Click to expand...
Click to collapse
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
mikewhit001 said:
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
Click to expand...
Click to collapse
Ok your backups are all bad, that's why it finishes so quick and won't boot out of TWRP recovery. You will have to download a image file and get it into the TWRP folder on your sdcard. You will have to download it on your computer unrar it and name the folder something like unrooted 1.9.37 and transfer it to your micro sdcard. Then put micro sdcard back in tablet. In TWRP recovery, you will have to go into Advanced>File Manager. In file Manager, you will have to click on external sdcard and copy the file from there back to sdcard>TWRP>backups>serial#>unrooted 1.9.37 it doesn't matter what the folder name is that you put in the serial# folder but the all the others are as named and your new folder HAS TO BE IN THE SERIAL# FOLDER, or Restore will not see it. When that is done go back to main menu and Restore, you should see your new folder, choose it and swipe to restore. This should take 10+ minutes. You should be able to reboot to system then.
Unrooted1.9.37 file to download
https://www.box.com/shared/ew0jcmch2ohvr43ubjqe
This thread can help you a lot quicker.
http://forum.xda-developers.com/showthread.php?t=1905674
If you have problems, PM me and I will send you my email so we can work quicker and won't trash up this thread.
I'm having the same issue since the gapps update, where the Nabi shuts itself down while charging. Sometimes it can be a real pain to reboot after it does this.
Funhog51 said:
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
Click to expand...
Click to collapse
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
streetglide13 said:
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
Click to expand...
Click to collapse
In es go to the menu where you turn on root explorer and tap the words 'root explorer' then a menu will pop up, tap mount r/w and then set /system to rw. You then should be able to delete the files. After you're done deleting set system back to read-only.
After much trial and error, I'm happy to announce that I have gotten Google Wallet working 100% on the Photon Q! I tested it out tonight, successfully made NFC purchases at two different locations. This is the first phone I've had with NFC, and contactless payment is pretty darn cool! And one 'plus' of this method is that it uses an unmolested Wallet apk. Personally, I didn't want to risk using a modified apk (as some other workarounds do) with financial information. So without further ado, here's the process:
What you will need:
Root access
Custom recovery (I used TWRP)
Root capable file explorer (I used ES File Explorer)
Xposed framework installer
Xposed patcher to disable region/device checks for Wallet
Google Wallet apk
Modified build.prop (optional) ONLY FOR PHOTON Q w/ OFFICIAL JB UPDATE
The process is based on the instructions here with a few modifications. Big thanks to Entropy512 for the original write up and Xposed module that makes this possible!
1. Place the Xposed framework apk, Xposed patcher apk, Wallet apk, and modified build.prop on your SD card (internal or external.) I had to name the file build.prop.txt to upload it here, rename it so it's just build.prop either before copying it to SD or once it's on SD but before moving to the next steps.
2. Boot into recovery and make a nandroid backup. This is essential! Not only will it save you if something goes wrong, but you will need it later.
3. Install the Xposed framework installer apk, then open it and allow it to install the framework. You will need to give it root access.
4. Install the patcher apk to disable region and device checks for Wallet. It will prompt you to activate the module, go ahead and do so. Reboot.
5. Open your root explorer and mount the system partition with R/W permissions. On ES File Explorer, this is on the tool bar to the left. Copy the modified build.prop to /system/ and allow it to overwrite the existing file when prompted. (see note below) DO NOT REBOOT!
6. Install the Google Wallet apk. Open it and run through the setup (link to your Google account and add/select a payment method.)
7. After Wallet setup is complete, reboot into recovery. Use the restore option and bring up the backup you made before starting. Select ONLY the system partition, make sure all other partitions are deselected. Run the restore operation.
8. Wipe cache and dalvik cache (may not be necessary, but it can't hurt.) Reboot the phone and try it out!
Note about the build.prop: If you prefer to edit the original build.prop yourself rather than using the pre-modified one that I'm providing, here are the lines that need to be changed:
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
ro.product.brand=Samsung
ro.product.manufacturer=Samsung
If you reboot after installing Wallet and don't go into recovery, the phone will show the "Bootloader unlocked" screen and then hang at a black screen with the backlight on. Just power off, boot into recovery, and proceed with the system partition restore. I have tried numerous times to just replace the build.prop with the original after setting up Wallet, and it always hangs at the black screen when I reboot. Don't waste your time with that, just go to recovery and restore the system partition.
This was tested on the official JB OTA update, though it should work on the stock ICS ROM as well, though you will need to edit your build.prop rather than using the one I've provided. I'm not sure if it will work on CM, Carbon, or any other ROM, test at your own risk and keep a backup.
I hope some of you find this useful! I have gotten a lot from this community and would like to give something back.
Interesting.
I think with adb you can save yourself a few steps - like restoring the system partition .
But regardless, that is cool. I always wanted to try Google Wallet, and was confused when this phone didn't offer it... but did have NFC.
Good to see my friend Entropy512 is still around as well! I will have to give this a shot, thanks for the detailed writeup.
arrrghhh said:
Interesting.
I think with adb you can save yourself a few steps - like restoring the system partition .
But regardless, that is cool. I always wanted to try Google Wallet, and was confused when this phone didn't offer it... but did have NFC.
Good to see my friend Entropy512 is still around as well! I will have to give this a shot, thanks for the detailed writeup.
Click to expand...
Click to collapse
Very possible. I'm not that well versed with adb beyond basic push/pull operations, figured I'd better not mess with what works! If you try this and are able to make it work in a more simplified way I'd be happy to amend the original post. :good:
How would you save time with ADB? Replacing the build.prop with the original one?
Any idea why the system doesn't boot after restoring it? Something with the framework?
Interesting
Great writeup, I went from bum to buying **** with my phone in about 10 minutes. Make sure to follow instructions carefully and you shouldnt have a problem, the writeup was spot on and I love the capability offered to me by my photon q now
so i followed the steps in the first post, but obviously i missed something. when finished i go to open wallet and i get the message stating "not yet available for your device......." I will try the process again tomorrow, but any suggestions?
Aaargh! said:
so i followed the steps in the first post, but obviously i missed something. when finished i go to open wallet and i get the message stating "not yet available for your device......." I will try the process again tomorrow, but any suggestions?
Click to expand...
Click to collapse
I got this after i rebooted my device, so it initiall did work and then it stopped after a soft reset due to battery loss. Trying again, then goign to the store before the phone resets. Dang it
so i have tried three times with no success. Wallet sets up, but after restoring system partition and booting back-up, wallet does not work. Same error as before.
So i re-ran Xposedinstaller and let it do its thing, rebooted and i can now open Wallet and access it. This was after following the Ops instructions completely. I have not tried to make a purchase, but at least it opens
I made an in store purchase today and it worked perfect. Pretty cool technology
Sent from my XT897 using xda app-developers app
I'm unable to get this to stick on CM 10.1 06/06 build. I was able to set it up and had a banner saying my device wasn't supported at the top, then the next time I ran the app it would close the app after displaying a notification about my device not being supported. Unfortunate because this area has a ton of support for Offers.
Solust said:
I'm unable to get this to stick on CM 10.1 06/06 build. I was able to set it up and had a banner saying my device wasn't supported at the top, then the next time I ran the app it would close the app after displaying a notification about my device not being supported. Unfortunate because this area has a ton of support for Offers.
Click to expand...
Click to collapse
After following install instructions, try running Xposedinstaller again. this is what i did and Google Wallet finally stuck. I am stock JB, but it is worth a try
Aaargh! said:
After following install instructions, try running Xposedinstaller again. this is what i did and Google Wallet finally stuck. I am stock JB, but it is worth a try
Click to expand...
Click to collapse
I can confirm that this made it "stick" for me as well. I'm on the 6-15 nightly of CM 10.1.
Sent from my XT897 using xda app-developers app
CM11?
Does anyone have google wallet tap and pay working on CM11 with this phone? If so, what method did you use to make it work? It seems what's described here is for JB/CM10...
Hi everyone!
I'm having difficulties with the malware that I, nor all AV and anti-malware apps I've tried cannot delete. I'm sorry if this thread was discused previously, if so just send me a link.
Here's what happened:
I clicked on a link in a web browser, and than phone flashed several times as application "Firewall" was starting.
Anyway AV app detected a virus and tried to clean it, but failed.
The malware is on the phone as "SecurityService" system app in /system/priv-app/.gmp.apk
I cannot delet file it's write protected. I've tried several methods nothing worked.
Any ideas?
If you're rooted, you can uninstall system apps.
Sent from Hell
No, I cannot... Can you give me some tip how to, maybe I Didn't try it.
Most of the time the app which you get when you root can be used to uninstall system apps.... If you don't seem to find it google for root apps uninstaller and install one of them
Sent from Hell
Nope... I tried several of them but they all failed. They either crash, freez or say something like "unable to uninstall", "failed to uninstall", "can't uninstall for unknow reason" and things like that. This malware protected itself somehow. Any other ideas?
dtalic said:
/system/priv-app/.gmp.apk
Click to expand...
Click to collapse
Just delete the folder with a root file explorer. If the "." in front of the file name is correct, it looks like it's trying to mark itself as a hidden file, which may be why the other methods aren't working.
Yes there is dot (.) in front of file name. But if you are suggesting me to delete folder "priv-app" where the file is, I don't think that's a good idea at all. It's packed with system apps files such as dialer, calendar, contacts, etc... Anything else?
I could show you some screenshots if it would help anyone to maybe figure out what to do... Although I wrote what is going on...
dtalic said:
Yes there is dot (.) in front of file name. But if you are suggesting me to delete folder "priv-app" where the file is, I don't think that's a good idea at all. It's packed with system apps files such as dialer, calendar, contacts, etc... Anything else?
Click to expand...
Click to collapse
Don't delete the folder, delete the apk
Sent from Hell
I cannot delete it. Root Explorer just say "can`t delete file" (or something like that). And dozens of other apps say the same. That is my main problem.
dtalic said:
I cannot delete it. Root Explorer just say "can`t delete file" (or something like that). And dozens of other apps say the same. That is my main problem.
Click to expand...
Click to collapse
You can delete anything in TWRP. Just mount system and then use unternal file manager to delete the app.
That sounds promising. Im quite unfamiliar and new to all this, can you either explain me how to, or send me a link with explanation...
dtalic said:
Yes there is dot (.) in front of file name. But if you are suggesting me to delete folder "priv-app" where the file is, I don't think that's a good idea at all. It's packed with system apps files such as dialer, calendar, contacts, etc... Anything else?
Click to expand...
Click to collapse
I should have paid more attention to the file path. Since Lollipop, installed apks are given their own folders. It looks like you're on Kitkat or earlier.
Most root explorers have a toggle between read only and read/write. Check that.
Yes i know about that. Switching to r/w mode didn't help.
i googled twrp as optimumpro suggested and it seems like something that really would work, BUT my phone is not supported any other suggestions?
I also tried "force remove app (by recovery exploit)" option offered by titaniumbackup, but that also failed saying that file couldnt be found!?
dtalic said:
That sounds promising. Im quite unfamiliar and new to all this, can you either explain me how to, or send me a link with explanation...
Click to expand...
Click to collapse
You need to have TWRP recovery. Boot in recovery, go to Mounts and mount System. Then go back to the main screen, choose Advanced, then File Manager. Go to the directory where your file is, click on it, then choose Delete. You'll get a warning that operation is irreversible. Swipe to execute. That's it.
If that doesn't work for you, then reinstall your current rom without wiping data. This way, your System partition will be reformatted, original system apps installed and data preserved. Depending on the rom you flash, you may lose root and/or Supersu, so, you'll have to redo those.
Ok, I think im following you, optimumpro. I also saw some instructions on youtube. But did you see that i wrote that my phone is not supported in twrp. I need to install it, right? I mailed them, maybe they will add my phone for installation too. Or can i risk trying to install twrp using settings for some other device? There is a ZTE, but not my model...
dtalic said:
Ok, I think im following you, optimumpro. I also saw some instructions on youtube. But did you see that i wrote that my phone is not supported in twrp. I need to install it, right? I mailed them, maybe they will add my phone for installation too. Or can i risk trying to install twrp using settings for some other device? There is a ZTE, but not my model...
Click to expand...
Click to collapse
Unlikely that another device recovery would work. You can use terminal to execute rm "your file" in the directory your file is in. First type su to get root rights. If your rom has no terminal, get it from f-droid. Also see if whatever recovery you use has a file manager or terminal. But again, just reinstall your rom without wiping data...
Ok, here's where im now: tried to use terminal to remove file, but couldn't, it said that i don't have permissions for that. Tried to change permissions, couldn't. As i see it, i should find a way to delete file in recovery. Because i couldn't install twrp, i looked for another recovery file manager. Found "aroma", tried it, but also couldn't install it (none of several versions, followed instructions, but just got message something like "not able to verify... ",something like that... Now, im willing to reinstall rom, but how do i do it? I don't even care for wiping data, I'll just make backup and start all over again
That type of malware usually makes itself immutable so that it can t be erased (even when in recovery, immutable that is), and by reading your post I guess that it s what is happening on your phone.
It s easy to undo if you are rooted and have busybox installed.
Open your android terminal, or connect your phone through adb, then type:
lsattr system/priv-app/.gmp.apk
Most likely it will show something like:
-------------iA----------
The "i" means that the file is immutable, ie is write protected.
To undo this type:
busybox mount -o remount,rw /system
then type:
chattr -i system/priv-app/.gmp.apk
Now you can erase the file, and don t forget to erase its dex in the dalvik cache ([email protected]@[email protected]).
The malware may have some hidden stuff in the system/etc or the system/usr folder(check the install date and time, it should be the same than for .gmp.apk), and it may be immutable too so if that s the case just follow the above procedure again (you ll have of course to change the path, for example if there s a suspicious file called xyz in the system/etc folder then type chattr -i system/etc/xyz).
Let us know if it worked...
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
memrah said:
Hello,
I have a rooted Samsung Galaxy Note 3. I was experimenting with the build.prop file, having made a backup of the original version of it. After making some changes to the build.prop file and rebooting the device, the vast majority of the apps stopped working and what is worse, I somehow lost my root access. My original plan was to revert to the original version of the build.prop file if things didn't work as expected but now all I have is read-only access to the /system folder and I can't edit the build.prop file or replace it with the backup of the original I made. I also tried accessing the filesystem via an adb shell, but I still only get read-only access to the system areas. The problem is now 95% of my apps crash before they even start and I can't even run SuperSU, or playstore. I have Total Commander installed, and it is one of the very few apps that work, but again, I only get read-only access to the system area. All I need to do is delete the problem build.prop file and rename the backup file oldbuild.prop file, but how do I re-gain read/write access to the /system folder??
I would truly appreciate any help, ideas or advice
Thanks a lot
PS. I do not have a custom recovery installed. Just the Samsung stock recovery
Click to expand...
Click to collapse
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
-Hope- said:
The solution would be flashing twrp, then using its build in terminal or adb shell to replace the infected build.prop
Click to expand...
Click to collapse
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
memrah said:
Thanks for your answer. I did manage to revert to the correct build.prop file and get rid the bad one. For some reason though, when I restarted my phone it is now getting stuck at the Samsung logo screen with a pulsing blue status LED. I know for a fact that the build.prop file is the correct/original one. So I'm clueless about what might be causing it to get stuck during boot. Any ideas or suggestions? Thanks in advance.
Click to expand...
Click to collapse
Clear cache
-Hope- said:
Clear cache
Click to expand...
Click to collapse
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
memrah said:
-Hope-, Thanks a lot for your help. I tried clearing the cache, didn't work. Tried a factory reset via Recovery mode, didn't work, so I think I will need to flash the ROM. Do you know where I can download a stock factory ROM for the Note3 that is unmodified and not tampered with (malware free), just the way Samsung released it?
Once again, thanks a lot for your help
Click to expand...
Click to collapse
Updato.com
Sammobile.com < official site
Thanks. I flashed my Note3 with stock Lollipop ROM downloaded from Sammobile.