Permission problem on storage/emulated/0 - Galaxy S 4 Q&A, Help & Troubleshooting

Hi all
I have Samsung S4 now for 3 years. It is rooted and I am using SuperSU. When last month I updated SuperSU through Google Play to buggy version 2.80, I lost root. To fix that, I installed 2.79 through TWRP and gained back the root. Then I updated to version 2.82 through Google Play, but yesterday discovered the problem with permissions on storage/emulated/0. The problem is, that this directory and all subfolders becomed read only. Or to be exacted, If I create a subfolder I got this error "su error: mkdir failed for /storage/emulated/0/test, Permission denied". Same error if I want to remove any file, etc. Also changing permission doesn't work.
Can anyone please help me?
thank you
best regards
Starlord

Stop updating SuperSU from the Play Store. There are always some sort of problems with it.
The most logical step is to completely unroot, then reroot again. Have fun.
Also, why do you get a su error? Creating folders doesn't require super user rights. Unless you tried to do it with the terminal emulator.

Related

TF101 Problem, kinda lost OS root?

Hoping for some help because I've ran into some really odd issues with SuperUser/root on my TF101.
I used the guide in the Dev Forum and flashed to Prime 1.4, everything was great and working well. I made a Nandroid of my base to fall back on.
ChainsDD updated SuperUser on 6/10 or 6/11 and I accepted the update from the market. When I launched SU, I was prompted to update the Binary, I granted SU root access and it said it completed. However, since then, no app that requires root has requested SU according to the log and Kernel Manager is telling me I don't have root.
If I open Terminal Emulator, it is automatically at a # rather than a $
In Root Explorer, tapping the Mount R/W button changes to R/O and I was able to successfully create and delete a test folder in /system
I need to get SuperUser functioning again, any thoughts or ideas?
What's a TF104 model device?
Um. you do know that # in terminal emulator indicates that the app currently has root access?
Open superuser, its being recognized as permanent root because you allowed it to have root access.
And its TF101 not TF104.
Sorry, misread the model...
I know the # means root that's why the title is kinda lost root...
I'm not getting any of the notifications that SuperUser granted access, like I used to. Also, Kernel Manager isn't being granted Root access when I launch it
I think the SuperUser binary update failed, I got the binary from goo-inside.me and flashed it from CWM. Then I cleared the SuperUser app data and launched it. I was again prompted to update the binary version. It failed and prompted me to to flash a zip that it downloaded to my SD card. That zip is a 0kb file.
Try downloading superuser from the market.
david279 said:
Try downloading superuser from the market.
Click to expand...
Click to collapse
Same results
Also, Superuser is now randomly Force Closing on launch.
Talked with ChainsDD, it's a problem with how he compiled Super User for honeycomb. Fix will be released tomorrow.
Sent from my gginggerfied EVO
Fixed binary has been posted to goo-inside.me
Sent from my gginggerfied EVO

Nexus 7 has root, but

When apps that ask for root permissions are launched, it doesnt work, example: TI backup says that the device isnt rooted and i might have to check the SU binaries. My N7 was rooted before a update for Superuser was available, now something happen after i updated it. But i dont know what...
That's weird. After you updated your SU, did you go to SU to update its binaries?
i did that twice, and it did say to update binaries...so...
you might need SuperSu instead
What Android version are you running?
Droid_Boi86 said:
i did that twice, and it did say to update binaries...so...
Click to expand...
Click to collapse
I had similar problems with "lightly rooted" stock (4.2.1/JOP40D) using a slightly older version of Superuser. Some apps could get root and others could not. But things have been in flux recently; read on...
I poked around a little bit and it appeared that the 4.2 multi-user stuff was interfering with the way that older versions of (ChainsDD's) Superuser worked, and at that time (only a couple weeks ago) ChainsDD had not released a newer update - things were still in flux.
I switched over to SuperSU, and no problems since... but....
...for me, installation of SuperSU didn't go swimmingly. As I recall the SuperSU install instructions say something like "you need to already have root to install the SuperSU `su' binary". Makes sense as it needs to write it's 'su' binary into /system, which in turn means it needs to get root privilege from a pre-existing su/Superuser installation.
So it poses a chicken-and-egg problem if you have lost root completely which I somehow managed to do... wait, I remember now! I had left the old 'su' binary in place, but had manually uninstalled "Superuser" from /system before I attempted the SuperSU install. Doh!
If you have lost root... you can manually install SuperSU offline inside the recovery via adb & the command line, which means getting both the SuperSU.apk and the 'su' binary ahead of time.
You can get the .apk from the market. You can attempt an install - it will download the 'su' binary and (no kidding) place a copy of it in /data/data/eu.chainfire.supersu/files/superuser.png
If you haven't lost root completely inside the booted OS, I suggest mounting /system in "rw" mode prior to running the SuperSU install and startup.
It looks like I am back a version or two - I have superSU v 0.99
4d7abc0eb5898cdb81bc233dcd16e052 /system/app/SuperSU.apk
0034ec008416b1c3fa7010deb8a3a758 /system/xbin/su
-rwsr-sr-x 1 root root 91992 Jan 10 16:40 /system/xbin/su
note the setuid,setgid bits on /system/xbin/su. Also - no symlink from /system/bin/su to xbin/su.
OK, sorry for the long post. There have been new releases from both chainfire (SuperSU) and chainsDD (Superuser) quite recently. Since I haven't had any troubles since 10 January, I haven't been following it closely - YMMV.
cheers

Tip for those with android is starting or preparing apps on every reboot

So ive noticed on most roms that when you remove default built in root, it gives you an android is starting or optimising message on every boot. I deleted built in root so i could root with supersu and install suhide so i could play pokemon go. Well su hide wont install with built in root still intact so i had to do a full unroot first. Thats where the optimising problem on every reboot began. But i managed to solve it by copying the su file from supersu to the /su/xbin folder. After that no more problems on reboot. Thought id share in case someone else was having this same annoyance.
how to do that .... full unroot built in root
copy su file to su/xbin folder how to do this ?????

Remount issues

Hello,
I am currently running the H918 model with twrp and full root. Root was successful and the phone is running well. Thanks to all those who put in their time and effort and providing such a quick root capability. Makes the phone even more amazing than it already is.
Unfortunately, I am having an issue with be able to modify system files as I am unable to edit them whatsoever. I have tried using adb and using mount and remount commands but nothing has worked. I was hoping if anybody would be able to assist me with my issue. Thank you.
I've tried reflashing super su and I have busy box installed. Adaway is working properly (only through system less root) and I have been able to hibernate apps through tibu. I still cannot edit any files under /system. Does anyone have any suggestions? Thanks.
use root explorer
Thanks for your response. I've tried many root managers (including root explorer), enabled root permissions, had them successfully granted through supersu and still a no go. I just ran recowvery again and flashed twrp (this time without formatting data) and I am still unable to edit any system files.

Accidentally uninstalled SuperSU

Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.

Categories

Resources