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.
Related
OK, so I finally got the system update for the D2G yesterday. I'm not new to this whole game, so I removed Clockworkmod, unrooted, and installed the update. The update downloads fine, but the with the little Android guy screen, I get an "!" in a triangle and then the phone reboots.
Maybe I didn't remove clockwork all the way? Don't you delete hijack and logwrapper, and then rename the logwrapper.bin to logwrapper?
well basiclly the phone needs to be untouch in terms of the file structure, in my case, I deleted a few of the stock apk files and when I tried to do the update it would fail because the stock apps were missing and the update is a patch not a full system OS so it cant install the default apps, I had to install them back to the system/app with root explorer and then set the permissions back to what they needed to be, unforchenitly a hard reset would not install the stock apps. Also make sure anything that the root touched has been set back to default
I have the same problem too. I can't get the update to work at all after installing Fission ROM. I even restored from a nandroid from a fresh D2G. It worked fine on the untouched phone tho. I checked all the files in the /system/app and they were there. Is there any magical restore .zip perhaps?
If anyone is looking for the update: http://dump.no/files/2501381a2bd4/Blur_Version.2.4.29.A956.Verizon.en.US.zip MD5: a493e4efc9d27c8932d604806f817a85
evilp8ntballer7 said:
well basiclly the phone needs to be untouch in terms of the file structure, in my case, I deleted a few of the stock apk files and when I tried to do the update it would fail because the stock apps were missing and the update is a patch not a full system OS so it cant install the default apps, I had to install them back to the system/app with root explorer and then set the permissions back to what they needed to be, unforchenitly a hard reset would not install the stock apps. Also make sure anything that the root touched has been set back to default
Click to expand...
Click to collapse
I never touched anything... I stopped using Titanium Backup a long time ago when I uninstalled everything verizon and had the same OTA problem you described. I am at a loss for the problem that I have! All I ever did was root and put on clockwork, and I made sure they were gone when I updated.
Please, someone help!
did you uninstall of freeze any of the stock apps in /system/app? You need to restore them in order to successfully apply the OTA update. One file missing or modified in /system and checksums will fail/update fails.
leobg said:
did you uninstall of freeze any of the stock apps in /system/app? You need to restore them in order to successfully apply the OTA update. One file missing or modified in /system and checksums will fail/update fails.
Click to expand...
Click to collapse
the only time I touched anything in /system was when I removed clockwork by deleting hijack and renaming logwrapper.bin. Can anyone give me a number of files I'm supposed to have in /system, or maybe a way to go back to stock. Man, that SBF would be mighty helpful right now...
There is system dump laying around. I'll PM you the link (not sure if appropriate to post it here). You can use it to compare content and recover missing file(s).
leobg said:
There is system dump laying around. I'll PM you the link (not sure if appropriate to post it here). You can use it to compare content and recover missing file(s).
Click to expand...
Click to collapse
Hi, I've been trying to find an answer, and I think you could help me.
I had the same problem as this person you were helping, but I already knew that I should look through the system dump and compare. I did that, and deleted one file called dbus.conf from /system/ect. Now, my phone just does the DROID animation over and over again! Please help, I made a copy of dbus.conf on my computer and did a nandroid backup. Please, you or someone else on here, HELP!
So you are in a boot loop. If you can't get the phone to boot into clockwork recovery, today is your lucky day! SBF was finally released!!! Get the SBF and reflash /system
leobg said:
So you are in a boot loop. If you can't get the phone to boot into clockwork recovery, today is your lucky day! SBF was finally released!!! Get the SBF and reflash /system
Click to expand...
Click to collapse
Where is it? Isn't it only available to those with some app called TBH (or something like that)? And now I have to wait for a public release? And, if I'm wrong, can you give me a link to thee file? I can't find it anywhere...
Thanks for your help, I really appreciate it!
I would recommend you to approach the team black hat members and talk to them directly about how to get the sbf while your phone is non functional.
Sent from my DROID2 GLOBAL
But where is the system update located? I checked on the verizon website and there is nothing there. Also, do you have to be a verizon customer to get the update?
Sent from my DROID2 GLOBAL using XDA App
hi,
i did a big mistake. I wanted to install some vpn apps, which requires write permission on /system. I downloaded root explorer und tried to set all permissions for the system folder. But the app stills lacks the wanted permissions, so i started root explorer again and additionally checked the checkboxes under "special permissions". After doing that android crashed, the "systemui" process crashed and restarted and crashed ...
I rebootet the device, but i only see "google" and then comes a reboot and the device boots into recovery (TWRP 2.6.3.4). I already tried the "fix permissions" under advanced, but it didn't helped.
Is there any way to fix whatever i did wrong and not lose any data?
Any help would be greatly appreciated
Greetings k1x1987
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
d
jyuuken said:
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I don't want to miss something this time and complety brick my device. Could you/anybody tell me exactly what and how do flash to recover my device?
I did all the rooting stuff with the "Nexus Root Toolkit" program and followed strictly guides, except this time
Do i have to flash the rom with ADB? which file(s) should i flash system.img only? Or i have to flash more files?
A short noob guide would be really appreciated :good:
Greetings k1x1987
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
es0tericcha0s said:
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
Click to expand...
Click to collapse
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
k1x1987 said:
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
Click to expand...
Click to collapse
Just flash the system.img in fastboot.
Most devs recommend wiping /system first.
fastboot erase system
fastboot flash system system.img
I would also erase cache too.
fastboot erase cache
That will clear the cache, not the dalvik, but think that should be enough to get going.
...and once it is fixed, never change system permissions again.... Same a Linux, never change permissions at /root
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
k1x1987 said:
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
Click to expand...
Click to collapse
Using fastboot, flash the cache image from the factory image, fastboot flash cache cache.img
^ That should do the trick. If not, well, let's not go there yet. The cache should fix it. If that does, do yourself a favor and back up your EFS folder and save it somewhere safe. Either use TWRP or flash the EFS backup tool from here: http://forum.xda-developers.com/showthread.php?t=2514095
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
-----SOLVED NOTE----
I did a reflash of the stock rom one more time with ODIN and it seems to have solved the problem. However I still have absolutely no idea about what was wrong with the phone, or why the first successful flash did not take care of the problem.
And a piece of advice, do not edit platform.xml. I swear I edited it correctly and then reverted to the correct settings, did using 3 spaces instead of a tab caused an error??? This will remain a mystery for me...
---------------------------
Hello All,
So I have the Verizon S3 i535, I edited the platform.xml file to give write permissions to external sd card and all hell broke loose after I reverted those changes. All of a sudden every app is getting that "unfortunately stopped" message. I cannot send any file to neither the internal nor the external sd card from my pc, file browsers cannot read any file on any of these cards, I tried pushing with adb but that does not work either. I tried factory reseting, and hard reseting to no avail.
I tried reflashing the stock rom with ODIN but after the flashing process nothing changes? (Does that have to do with me being on NE1).
I do not understand what is going on with the phone right now, flashing should have restored everything, I still get com.google.process.gapps stopped working then all sorts of apps stopping in the same manner, I still can't copy any file to any sort of storage on the phone.
Any idea what has happened and how I could fix it?
Thanks in advance.
That type of editing is not something I have done on Android.
Is there any chance it is a permissions issue and could be fixed with root permissions to a file manager or with adb?
dawgdoc said:
That type of editing is not something I have done on Android.
Is there any chance it is a permissions issue and could be fixed with root permissions to a file manager or with adb?
Click to expand...
Click to collapse
I would be willing to try that however I cannot connect to play store, neither the internet app connects to the internet so I cannot install apk's. I cannot "push" apks to the storage too I tried it via pc and via adb. So I cannot even install a root file manager.
Kingo root however accesses the system (through the pc) and manages to install itself. I have no idea how it can do it.
guguma said:
I would be willing to try that however I cannot connect to play store, neither the internet app connects to the internet so I cannot install apk's. I cannot "push" apks to the storage too I tried it via pc and via adb. So I cannot even install a root file manager.
Kingo root however accesses the system (through the pc) and manages to install itself. I have no idea how it can do it.
Click to expand...
Click to collapse
Glad to see you solved the problem.
I was speaking of using an adb shell to change the permissions of platform.xml to 0644 (-rw-r--r--) if they were set to something else. (I just checked my /system/etc/permissions/platform.xml to verify that was the settings on my device. I wasn't any more specific before because I hadn't checked the file locations nor its permissions.)
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..