Related
Hey guys
Hoping someone can help me sort out my Galaxy Ace.
I've royally f**ked up my phone while trying to re-install stock email.
Followed some instructions and accidentally disabled execute rights to system/app folder using root browser in ROM Toolbox.
Phone is now in a boot loop.
I've updated from sd card to installed Clockworkmod recovery.
So far I've tried wiping cache and dalvik cache with no joy.
Also tried fix permissions, still nothing.
Hoping you can guide me through a fix for this.
Would greatly appreciate your help.
Cheers
Paul
factory reset it
tried that - not working either
mitchst2 said:
Hey guys
...accidentally disabled execute rights to system/app folder using root browser in ROM Toolbox.
Click to expand...
Click to collapse
Show us the instruction.
What exactly did you do?
Can't you connect your phone to the computer, maybe during recovery.
Open adb shell, and fix the permissions ?
chmod +x /system/app ?
Might have to remount system readwrite before that.
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
best of luck
nbreed said:
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
Click to expand...
Click to collapse
try plugging it up while its in cwm and access the adb shell while its displaying. the prompt should be ~# if its universal. maybe you can completely wipe everything and flash a recovery at the same time? that may keep it deleted. i dont know. just a suggestion. i hope you succeed... tell me how it goes.
thanks for answering.
i tried all that, even did a complete format of the internal sd card, in adb with parted and also in windows with a mounted card. it says it is deleted, but after reboot it is all back again...
Do you have a backup of a working ROM you can restore?
Crap.... Hmm... Have you tried any formatting software? Try to find a programmer who can wipe it completely, re partition, and reinstall the stock rom. Then try to restore to something before the problems
Sent from my R800at using XDA
Use flashtool. I've heard it can unbrick, maybe it'll help???
Sent from my R800at using XDA
nbreed said:
My P1000 shut down randomly, so I tried to put everything new on it. After flash and all the other stuff it won't run properly anymore. Everytime I get 'System UIDs Inconsistent'. used Odin and Heimdall, I did wipe the data and the cache, I can see with ADB it is gone, but after reboot all the corrupt apps and system failures are back again. I installed several different firmwares, nothing worked.
I have changed permissions with chmod and deleted by hand several files, amongst them the everytime restarting but crashing apps like skype and whatsapp.
When I perform wipe, delete, rename or move actions in ADB the results are what I wanted. But when I restart everything is back again. I even deleted almost anything, did not work.
This happened in all the roms I installed, so it must be a problem in the filesystem or so. Any idea how to permanently delete stuff while in adb shell? I already gave myself all the rights on the tablet, synced it after the deletes, nothing works.
Or does anybody know how to start from scratch?
I cannot start the tab anymore in normal mode, but I do have recovery mode and overcome cwm.
Click to expand...
Click to collapse
this Q
With Q???
Recovery rom can be installed, but is gone after reboot. Formatting in windows or linux (adb) performs without errors, but after reboot, yes you guessed right, it is back. So this internal sd card has a life of its own, the only thing I can do is install a working system with flashing, but then no app will work, every activation of whatever app will give inconsistent uids errors. And I cannot install new apps, because vending.apk (market) will crash. I installed vending by hand (adb), then it work for a moment, but after reboot to use it the normal way, again crashed.
AS LONG AS I CANNOT REPLACE THE SDCARD IT IS HOPELESS?!?
This morning I left the unwilling android tab in the power adapter to be fully charged for a new go. But: it is now a real brick. It won't power up any more, the button lights do not flash anymore, the only thing it does, is showing the battery. Never again will I buy such an expensive underdeveloped piece of plastic crap again!
Calm down... You need to boot into recovery mode and try using formatting the sd. If comp can recognize, format the sd with the computer. It's not the android. It's what you did. Sorry
ROOTED Xperia Play 4G 2.3.3
can you read? i did format the sdcard in adb with parted, i did format it on the pc. but when i reboot EVERYTHING is back again. before rebooting it is totally empty. after reboot the old non-working stuff is back.
end of android, no end of samsung for me
Help
How do I install the radio over abd
News on this issue?
nbreed said:
can you read? i did format the sdcard in adb with parted, i did format it on the pc. but when i reboot EVERYTHING is back again. before rebooting it is totally empty. after reboot the old non-working stuff is back.
end of android, no end of samsung for me
Click to expand...
Click to collapse
I have the very same problem, did you managed to fix it ??
Is there a way to pull a folder from your phone through stock recovery? I recently got an "Unfortunately, System UI has stopped" message that appears on both normal and safe mode boot and even after wiping the cache. Before I do a factory reset I wanted to pull the DCIM folder from the phone so I could at least save my pictures however other than with the adb sideload option, adb doesn't see the device. Any advice?
kylis105 said:
Is there a way to pull a folder from your phone through stock recovery? I recently got an "Unfortunately, System UI has stopped" message that appears on both normal and safe mode boot and even after wiping the cache. Before I do a factory reset I wanted to pull the DCIM folder from the phone so I could at least save my pictures however other than with the adb sideload option, adb doesn't see the device. Any advice?
Click to expand...
Click to collapse
Unfortunately it's not going to "see" it without root access.. If you can turn the phone on and try to just tap ok on the system UI failure to make it go away for a second and then try to get the phone into mtp mode before it pops back up again.
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.
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..