Unable to change folder access permission, even with root - General Questions and Answers

I have found that my LG G5 /sdcard/DCIM has access permission of 0x770. I suspect this is the reason that video files are not visible when I connect it to my PC using MTP mode.
So I tried to change it. First, tried ES File Manager with root turned on and / mounted rw. However, properties of the folder does not have any way to change access permission.
So I installed Terminal Emulator and su to root. chomd 777 does not work -- it reports no error but the result is 771. chmod a+rwx or chmod o+rwx does not work either.
How could I change the permission?
Thanks

Related

how do you change folder permissions???

hi
how does one change folder permissions? i have read that you cam do it with the root explorer app but is there a way to do it on the pc using the sdk? i connected my phone to the pc and issued the adb shell command and then attempted to use the chmod command but got a read only file system message.
dsMA said:
hi
how does one change folder permissions? i have read that you cam do it with the root explorer app but is there a way to do it on the pc using the sdk? i connected my phone to the pc and issued the adb shell command and then attempted to use the chmod command but got a read only file system message.
Click to expand...
Click to collapse
1) If you have ADB setup on your computer, hook your phone into the computer and connect into it via ADB.
2) Once in, "chmod" the directory or file(s) you wish to change permissions for.
IF you don't have ADB:
1) Download a terminal
2) su - to root
3) Change your directory
4) "chmod" to whatever pemissions you want
it means that folder/file you're chmod'ing was mounted ro. you cant change anything if its mounted as ro. to check just enter "mount" and you can see what are mounted as rw, ro etc
yantz
I would also suggest changing it back when you're done. This helps prevent you from accidently overwriting or deleting something and have to reflash if you're rooted.

su not updated

I have my Polaris NAND flashed with 2.6.25 kernel + casacristo's RLS18 ROM.
I have updated from the market the Superuser but now I get the pessage that SU is not updated and to download the new one (3.0.3.2).
I download the new one , the Root access is granted but at the end more or less I receive this message translated from italian:
...
...
md5sum ... OK
Mod file su 06755... OK
Moving su to its final position ... failed...
TRY Again
I tryed several times but ... no chance to update it... how can I manage ?
miazza
Here is latest su binaries v3.0.3.2. Download and unzip file. Push this to /system/bin and /system/xbin and then change rights with chmod to 6755. Reboot phone. Done.
Thanks, I will try.
Shall I do via ADB or can I try with RootExplorer for example ?
miazza
ADB, unless your root explorer can set 6755 rights
whitealien said:
ADB, unless your root explorer can set 6755 rights
Click to expand...
Click to collapse
It worked great. I managed with RootExplorer but it can be done also via FTP with Filezilla.
Thanks
miazza
file permissions doesn't work
Hi,
I use a HTC wildfire S, who have been rooted, but still in original ROM.
My SU doesn't want to be updated, as described in the first post.
So I downloaded the ZIP, and put SU on the sdcard. With ROOT BROWSER I copy it on /system/bin (SU have been copied automaticaly in /system/xbin).
I tried to change the permissions files, but after reboot, permissions are ---rwxr-x.
I tried with ADB. My phone is well recognised :
C:\Program Files\Android\android-sdk\platform-tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
SH191TR05136 device
When I tried to change permissions file SU :
C:\Program Files\Android\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
$ chmod 6755 /system/bin/su
chmod 6755 /system/bin/su
Unable to chmod /system/bin/su: Read-only file system
$ chmod 6755 /mnt/sdcard/temp/su
chmod 6755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$ chmod 755 /mnt/sdcard/temp/su
chmod 755 /mnt/sdcard/temp/su
Unable to chmod /mnt/sdcard/temp/su: Operation not permitted
$
Do you have an idea ? Thanks by advance, because right now, my phone is not still root...
I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza
miazza said:
I have no idea about how ROOT BROWSER works.
With RootExplorer you can tap the su file and keep it untill the permission window appear. At that point you can change all the file rights.
Another way for doing it is via FTP by using SwiFTP.
ciao
miazza
Click to expand...
Click to collapse
Root browser seems to work the same way.
How can you use FTP with a phone ? It's suppose to use an IP adress. But by USB, there is not... But I will,l try asap.
However, my apps couldn't take root permissions, so I feel bad...
Use SwiFTP (it should be free from the market).
It works over Wireless connection to your internal WLAN and provide you with an FTP address like 192.160.0.x.
While you are connected through FTP client (like Filezilla), you can see your mobile File System as well as your SD.
with a right click on the su file you can change your rights.
But I do not know if it works even if you are not rooted...
miazza
I solved my problem my re-rooting my phone, using http://forum.xda-developers.com/attachment.php?attachmentid=672519&d=1312136127.
My phone says that the binary SU was obsolete, but when I tried "AGAIN" to update it, it was successful that time.
Strange, I don't understand why now the update was ok. But all is right.
Thanks everyone for the help.

Accidently Remove Write And Execut Permission from root /System folder what do?

Accidently Remove Write And Execut Permission from root /System folder what do?
poloroid prof700 is a china maded 4.2.2 jellybean running device.
I am rooted that device and every thing fine with key root master
I was try to change a folder permission from root via x-plore file manager with mount write permission via supersu accidently i was changed the folder permission for system folder in root. I removed all permissions except read .
Now No bootup just showing first image of poloroid and its automatically loading recovery secction. I cant access root via adb
adb shell
this command showing
exec '/system/bin/sh' failed permission denied (13) android
adb remount
its showing operation not permitted
and please help me how can give back the permission to the system folder
sorry for my bad english:crying::crying:

[Q] Cannot change File Permissions (solved)

AT&T D850
Stock, rooted, Bump'd TWRP recovery installed
I noticed today that when viewing a files' properties in Solidexplorer, the Change Permissions button was missing.
I made sure the latest busybox was installed and noticed there that "chmod", "chown", and "chcon "are NOT re-linked to "busybox" but left linked to "toolbox". I didn't want to change the symlink without explicitly trying the chmod command (via toolbox and busybox) first to see if it worked.
I opened Terminial Emulator, su'd to root, then navigated to an mp3 file I have on my external sdcard, and issued both
Code:
chmod 777 "file"
busybox chmod 777 "file"
and nothing happened.
No error, but no change in the permission either (it is 770).
Anyone have a clue as to what's wrong?
UPDATE:
The problem appears to be caused by me not being thorough, not SELinux.
In summary, the SDcard is formatted as exFat which doesn't retain Linux file permissions, therefore, issuing a chmod yields no result, but no error. Solidexplorer is "smart enough" to know that fact and so there is not button to change permissions available.

[Working]Root Kindle Fire HD8 6th Gen

Ladies and Gentleman,
I was able to root the HD8 6th Gen using Kingoroot while in airplane mode. I download the executable and ran it directly from my computer. My Fire tablet is on version 5.3.1.1 and was never registered with Amazon. I can run su in adb but the SuperUser app is not working on my tablet. I am looking into replacing the KingoRoot SuperUser app with SuperSU. I suggest you block updates as soon as you achieve root.
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Decided to try this on 5.3.2.1, ran Kingroot for PC few times (version 3.4.0 build 1142). Did not work. Hope it works for you 5.3.1.1 guys.
I believe 5.3.2 can be downgraded to 5.3.1.1 but I also believe 5.3.2.1 is confirmed to not be downgradable.
I was lucky and got my BF unit with 5.3.1.1 and blocked OTA right away
I register to reply this thread and tell everyone that 5.3.1.1 CAN BE ROOT using KingoRoot(not KingRoot)
blocked OTA and planning to place Kingoroot with Supersu now.
go kingoapp.c0m(replace 0 with o) and download the PC one.
Tried APK one but seems stuck at 90% or not enough patient?
---------- Post added at 05:17 PM ---------- Previous post was at 05:12 PM ----------
chemie99 said:
look at this thread to see if you can remove Kingroot and replace
https://forum.xda-developers.com/am...rtool-root-t3272695/post69855730#post69855730
This applied to 7" but may be same issue you are having. Note I would suspect you at least need to install the app since you used the PC version but then that might allow replacement fully. The Rootjunky script basically installs supersu and removes the kingroot app following this approach: https://www.droidmen.com/remove-kingroot-kinguser-with-supersu/
So now the questions are:
* Does the app work too or just PC version
* Does a device which has been used and registered with Amazon work? I am on 5.3.1.1, have OTA disabled, have Novalauncher sort of working, and managed to get Amazon to disable the ads lock screen but right now the device does not leave home due to Opendns constraints as I did not want to lose 5.3.1.1 while waiting.
Click to expand...
Click to collapse
my device is registered with amazon and it works
Detailed instruction on post#38
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
chemie99 said:
so what is difference between
kingoroot
and kingroot
??
I am familiar with Kingroot but kingoroot seems to be another animal? Is kingo safe? We have a total of 3 lifetime posts from two accounts who are speaking its benefits....
Click to expand...
Click to collapse
honestly I dunno, I'm new to android, just bought the kindle to start playing with android...
but I found it difficult to replace the kingoroot with supersu, when I type su in terminal, it show nothing, can't give root permission to terminal emulator.
I replaced kingoroot with supersu following instruction from androidforums.com/threads/script-replace-kingoroot-with-supersu.919175/
After it's done, supersu doesn't prompt for root access. So I set 'default access' to 'grant' in supersu settings, and it seems to be working.
g4ry12 said:
Decided to try this on 5.3.2.1, ran Kingroot for PC few times.
Click to expand...
Click to collapse
I was not paying attention, it's KingoRoot, not KingRoot. Downloaded KingoRoot for PC (v1.4.9), and tried on 5.3.2.1. Rooting failed, unfortunately.
I ran the PC kingo and rooted.
I then tried to remove and replace with supersu and it failed
I lost root
I tried to rerun Kingo PC but it wanted debugging enabled even though it was
tried the apk kingo (from kingoapp.com; playstore it is a adware hack)
got stuck at 90%
exited and kindle was really sluggish; maybe something to do with my novalauncher or something?
power off reboot and stuck in boot up (Fire image). Now can't boot.
Message is be careful with kingo when removing....will try restore now.
Edit: wiping data and cache did not help. Did brick recovery to 5.3.1.1 (which is what it was on when I got it), and managed to recover. Glad I don't have to send this one back to Amazon!
I will now restart kingo root effort and if it works will report back steps (including supersu replacement).
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. For example, Titanium BackUp is unable to detect "Su and Busybox" so no go.
I am able to pm disable the firelauncher for example but that is about it
chemie99 said:
So I have root according to kingo but "root checker basic" says I do not have root.
Try to open "superuser" (which is a kingo superuser app) and it is just a blank screen then back to Home.
The removal tool that @2ig2ag linked did not work.
It failed on "mount -w -o remount /system" with "mount: operation not permitted"
I also tried to manual cp the su file over and get error "read only file system"
Edit: Despite kingo saying you have root, you don't. At least not complete root. I am unable to copy anything into system/app via ES File explorer too. I am unable to grant programs that want access, that access. I am able to pm disable the firelauncher for example but that is about it
Click to expand...
Click to collapse
I soft-bricked once, stuck at fire logo, sideload adb and resumed normal.
I didn't use the root checker to check, the superuser included will crash when I launch it,
but I can su in adb shell..
@2ig2ag's way not work for me either,
I cannot run the script, it said permission denied, then I try to run it manually,
I can remount /system, it do not show any error, but I am stopped at "cp ./su /system/xbin/daemonsu",
it said "daemonsu" text file in use.
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
chemie99 said:
tried ultra explorer as another way to get to /system and it just locks up when trying to detect root.
Tried manually installing supersu.apk and it locks up and requires reboot to get back to working device.
@phpbb88 I retried "mount -w -o remount /system" and it worked; maybe I wasn't in su at the time. I get the same error on file copy
So to summarize:
you can: adb su
you can: pm disable fire launcher and OTA (not sure if unrooted allows this too?)
you can not:
write to /system
install any apk that require root and grant root access
switch to supersu
adb remount (fails)
I would not call this a successful root. I am not even sure of the pm disables will last more than 24 hours.
Click to expand...
Click to collapse
I am using a file explorer called "ES File explorer", it cannot view the system file when it is not root.
After Kingoroot, I can view them, but I still cannot create file in /system by using that File explorer.
However I can successfully create a dir in /system in adb shell, shown below.
[email protected]:/system # mkdir 123
[email protected]:/system # ls
123
app
bin
build.prop
data
etc
fonts
framework
lib
lib64
lost+found
media
priv-app
recovery-from-boot.p
sbin
security
sqfs
tts
usr
vendor
xbin
[email protected]:/system #
I have made progress...with kingo install I did this:
copy the files of the kingo root removal to sdcard/kingo
adb shell
su
mount -w -o remount /system
cd /sdcard/kingo
cp ./su /system/xbin/daemonsu
fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so
with adb window still open, run PC program and remove root
then
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
./step1.sh
got some errors
then sideload the supersu apk via ES file explorer
then allow supersu to do it thing and reboot.
Now I have supersu running!''
edit:
but do I have root?
Titanium backup still fails but ultra explorer does say it has root
now adb shell su fails.....
chemie99 said:
I have made progress...with kingo install I did this:
copy the files of the kingo root removal to sdcard/kingo
adb shell
su
mount -w -o remount /system
cd /sdcard/kingo
cp ./su /system/xbin/daemonsu
fails because it is locked. Then I started to think that the steps were for the kingo app and not the PC so
with adb window still open, run PC program and remove root
then
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
./step1.sh
got some errors
then sideload the supersu apk via ES file explorer
then allow supersu to do it thing and reboot.
Now I have root with supersu!
Titanium backup still fails but ultra explorer does say it has root
Edit: hmmm..
now adb shell su fails.....
Click to expand...
Click to collapse
I cannot run the step1.sh, still show permission denied.
I tried manually, but got another permission error...
[email protected]:/sdcard/Kingo # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo # daemonsu -d &
[1] 8434
[email protected]:/sdcard/Kingo # ./step1.sh
sh: ./step1.sh: can't execute: Permission denied
[1] + Done daemonsu -d
126|[email protected]:/sdcard/Kingo # cp ./su /system/xbin/su
[email protected]:/sdcard/Kingo # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/ku.sud
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo # ./chattr.pie -ia /system/xbin/supolicy
sh: ./chattr.pie: can't execute: Permission denied
126|[email protected]:/sdcard/Kingo #
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device.
Supersu does manage to install itself but root checker still says I do not have root.
chemie99 said:
after the errors, did you install supersu.apk?
I ignored the errors thinking they were from differences between kingo apk and kingo PC versions of what they put on device
Click to expand...
Click to collapse
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
phpbb88 said:
I didn't finish all the steps in step1.sh, cause I have installed SuperSU at the beginning of time,
I then try to run Supersu and it said blahblahblah error, need to reboot my device.
wola, i lost my connection to root adb shell, and now going to root it again
Click to expand...
Click to collapse
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
chemie99 said:
I only install supersu as the step after running step1; it worked, and took hold (at least no errors and opening the program looks normal). The issue is that it won't grant access to anything (TB, flashfire, etc)
Click to expand...
Click to collapse
Kingoroot PC asked me to grant root access to it by pressing OK on my device's pop up when my device is under root,
but my device wouldn't show anything.
Is there any problem on fire OS that wouldn't show this pop up?

Categories

Resources