Related
Hey everyone I'm new to the whole rooting thing I have a tmo G2 and I have done temp root using visionary. I'm trying to perm root now but now i'm running into a problem terminal emulator says my sdcard is not found
this is the message i get:
export PATH=data/local/bin:$PATH
$ $su
# cd/sdcard
cd/sdcard:not found
#
Your help is greatly appreciated !
nancee89 said:
Hey everyone I'm new to the whole rooting thing I have a tmo G2 and I have done temp root using visionary. I'm trying to perm root now but now i'm running into a problem terminal emulator says my sdcard is not found
this is the message i get:
export PATH=data/local/bin:$PATH
$ $su
# cd/sdcard
cd/sdcard:not found
#
Your help is greatly appreciated !
Click to expand...
Click to collapse
Put a space after the cd commandand you should be fine.
cd /sdcard
Please try a more descriptive thread title next time. Just about everyone posting in this forum is looking for "help" so that title is completely useless.
go on youtube and search "blackprince how to root your g2" and follow everything that he does in the video. thats what i did, and got it to work within 20 minutes. thats what i tell everyone!
PatrickHuey said:
go on youtube and search "blackprince how to root your g2" and follow everything that he does in the video. thats what i did, and got it to work within 20 minutes. thats what i tell everyone!
Click to expand...
Click to collapse
Do NOT follow videos! Videos are made EXCLUSIVELY by COMPLETE MORONS. If you can't read and understand the instructions in the wiki (you see the button at the top of the screen here?), then you SHOULD NOT be attempting advanced operations.
Info: For those of you who need more info on my SU Binary (/system/bin/su), it's NOT out of date. Its the newest version for galaxy s4 m919.
My problem: /system/bin/su (SU binary files) will not execute.
Why?...: Because, access to execute binary files on system is denied (I don't have root access/permission). EEEK.
here's the Logs from root checker Pro: (In no particular order)-
SuperSU application - is NOT installed.
SuperUser - Installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: -rwsr-sr-x root root 380532 2008-08-01 08:00 su
Analysis: Setuid attribute present and root user ownership present. Root access is correctly configured for this file! Executing this file can grant root access!
Standard Location
Check Command: ls -l /system/xbin/su:
Result: lrwxrwxrwx root root 2013-10-11 02:57 su -> /system/bin/su
Analysis: File: su is a symbolic link pointing to another file: /system/bin/su
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin
Root User ID and Group ID Status:
SU binary not found or not operating properly.
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
more details
Extra info that I didn't include: I originally WAS rooted, running stock Samsung ROM (factory ROM) and I rooted using ODIN. So after rooting, I installed CyanogenMod 10.1.3.1, which does not come with root installed by default.
*SIGH* So... I want to know how to root CyanogenMod... So supposedly following the instructions by Root checker pro Logs,
I need to execute /system/bin/su. (Which won't work, unless a magical "S-Off" appears so I can execute it. But, then executing would be pointless because I would be already rooted with S-Off.
Help please, anyone? Could I root cyanogenmod from the computer terminal? Is there a way to override system permissions and execute su binary?
As per all your other post. Have you enable Root in Developer Options? CM ROM now has root disable by default.
Root options...
Root options in CyanogenMod Developer Options are not displayed in my settings...
What exactly does the toggle panel say for it? I can take a screenie of my settings..?
sorry for my ignorance with CyanogenMod... The last time I flashed CyanogenMod
was with CyanogenMod version 5, lol. And that was 3 years ago (I had an HTC Inspire 4G)
System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]
In reply...
dynospectrum said:
System Settings, About Phone, tap on the build number repeatedly until it enables Developer Options. Press back, tap Developer Options. Change Root Access to 'Allow ADB & Apps.'
Let's hope this is the last thread you start for awhile. Search for these answers, they have been answered already ;]
Click to expand...
Click to collapse
Well then. That was not so loving and friendly. Lol. And I have done so, btw.. My developer options are enabled, but the root access panel is not
In there. infact, there was a new section called "SuperUser", and I had set the root access panel to "Allow ADB and Apps" like you said.
But in return, no cigar. No root rights, even still. :/
Same here I'm using beanstalk 4.3 and most of the root apps work but some don't for example gamekiller, the few times I installed it it denied it before the prompt window popped out then after a few tries it finally granted it but before I pressed grant it said WARNING GAMEKILLER HAS A COMMAND (not sure about that part) android.permission.ACCESS_SUPERUSER not declared so I went into super user settings and I checked that option so I tried searching a value number and as soon as I press search it doesn't do anything then I press help and it tells me it needs root access which has been give
Sent from my SGH-M919 using XDA Premium 4 mobile app
Download and flash in recovery: http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Yay.
I've flashed that in CM10 ROM several times, and no root. But no worries, I'm running an awesome, fast, great battery life AOSP Based ROM (Completely AOSP, actually) and it comes rooted
The ROM is actually solely based off of googles open source code from android 4.3, with a few of the major components hand-picked from other Dev sources. The ROM is called-
Google Edition s4
For all who wish to download this as well as I did, here's the link to this epic ROM:
http://forum.xda-developers.com/showthread.php?t=2341026
Thanks
Thank you, this method worked for me. So much misinformation out there, I tried like 20 other bogus remedies before this. I could hug you.
same problem
I rooted my phone before,then I unroot it. But now when I am trying to root it again I'm facing same problem with superuser, it's saying that su binary is outdated and its not updating also, and I don't have root permission so that I can fix it with several methods which I found by google it.
Sorry if the answer is somewhere in here but I have been looking for over a day.
This is what I have done:
I have a stock Verizon HTC One
Installed weak sauce gained root access.
Installed Firewater S-Off and HBoot worked Beautiful work thank you after hours of research. - For a Noob it went smooth.
Also flashed PhilZ Touch Advance and when I try to reboot it says: Root access is missing or broken.
Ran Root Checker: You have root access!
Super User Application Status:
SuperSU application - version 1.93 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwxr-xr-x root root 113036 2014-03-30 12:15 su
Analysis: Setuid attribute is NOT present BUT root user ownership is present. Root access is NOT correctly configured for this file!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
Root user id:
uid=0(root)
Root group id:
gid=0(root)
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
I'm sure the answer is in here I just dont want to F it up and my eyes are crossed from looking for answer.
Thanks Again.
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
That easy?
orangekid said:
How about just flashing a rooted ROM in your recovery and seeing if it's all good?
Click to expand...
Click to collapse
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
habatchaNow said:
Ok I will try that. Do you think the error is because I installed supersu incorrectly, or wrong method. I believe I dropped and dragged it to my download file then opened it with my file browser and installed. As long as that wont be an issue I will give it a shot. Thank You for responding to my noob question.
Click to expand...
Click to collapse
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
@PonsAsinorem might be able to help on this.
ROM .... Check
orangekid said:
It could be a number of things, but you were going to flash a custom ROM at some point anyways, right?
Click to expand...
Click to collapse
I took your advice and flashed the NuSenceSix. It went off without a hitch, holding breath eh entire time. Thank you for the push.
I went back to the firewater threads and one thing I didn't do was remove weaksause. Is that something I need to do if I want the root to be permanent? I don't need to go to the android development and go though that process emailing system info or whatever its called do I?
Also I was about to read up on radios and kernals for this ROM as well as try and figure out why I am getting that message in Rootchecker.
Thanks Again for your help.
Please
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Thank You
synisterwolf said:
@PonsAsinorem might be able to help on this.
Click to expand...
Click to collapse
Sorry for the late response; was at work.
habatchaNow said:
That would be awesome. Any suggestions would be greatly appreciated. As I was telling the Room Moderator I flashed the NuSense6 and it went off without a hitch. however it is Still showing the same messages with rootchecker.
Click to expand...
Click to collapse
If you're S-OFF, you're golden. Most anything after that is going to be a ROM issue. It's been a minute since I ran that ROM, but the early batches had issues with su being configured improperly. The easiest way to fix this would be to flash the update SuperSU zip in recovery.
I miss read the OP-
I thought he was saying that Philz recovery was showing Super User not installed on reboot when the rom is Rooted.
OP-
As for weaksauce, once you have s-off you will no long need the app. you can root any rom by flashing SU.zip if you have an S-off device running a custom recovery.
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Custom Recovery Version
PonsAsinorem said:
habatchaNow, what version of PhilZ are you running? There was a bug that misdetecting CM, but that's been fixed, and I don't think this rom ever had the false positive, because root actually wasn't configured properly at the time.
Click to expand...
Click to collapse
Let me see, it looks like my custom recovery is PhilZ 6.40.4 Cyogen Mod V6.0.4.8. I think the problem started when I installed and ran super su. I side loaded it( that's moving it onto my device via explorer right?) Do you guys recommend another ROM for my phone? I like the NuSence it just seems like a minor upgrade to the stock ROM. I don't know if this matters but when I open my files on the phone the "root" folder and "sbin" folder are both empty.
One of my challenges is that I don't even know what I don't know so, I really appreciate the help. If you ever need help or advice with health/life/investments I'm your guy.
If you like that ROM, then stick with it. I try not to steer people away from any ROM. To fix your su problem, try flashing this from recovery.
http://download.chainfire.eu/supersu
Hello,
I am trying to get UbuntuDesktop using Install or Mount from this forum runnning on my Samsung S4mini
http://forum.xda-developers.com/showthread.php?t=2627255
Anyhow always when I try to mount the linux.img it says: mount: permission denied (are you root?)
(please see the attached screenshot)
You probably first recommend me to check if I have my phone properly rooted and if I have the root privileges. Yes I have both.
For rooting I used this: http://forum.xda-developers.com/showthread.php?t=2364980
It worked successfully. The App RootChecker says, Phone successfully rooted, the App SuperSU also.
I installed Terminal Emulator for the Install or Mount and also BusyBox X+ for some missing commands. Both are in the list of SuperSU and when I am starting Terminal Emulator and typing "su" a message tells me that I have SuperUser rights.
Also the installation of Install or Mount was without any error - except at the end when it was trying to mount the linux.img.
I searched the forum and google for this problem - but all solutions are concerning problems when the users didn't type su or haven't properly rooted or something similar. Unfortunately I'm a new member and so not allowed to post my question in the Q&A of the Install or Mount. I hope it's ok to do it here now.
Hello Forum,
Sorry if this post isn't in the right place; i'm not very good at posting on forums.
My question: does a stock phone already have a SU binary installed?
My situation specifically:
Sony Xperia XZ2 Compact (H8324)
It seems there's a SU binary in /sbin
Trying to execute it results in Error: java.io.IOException: Cannot run program "su": error=13, Permission denied
It seems there's also a busybox installed but I can't get any details about it
I checked my phone with Root Checker Pro by Joey Krim because an app (CoronaCheck) by the Dutch government used to identify yourself and state your corona status (for entry to concerts, festivals, restaurants etc) gave me a warning that my details were not safe because my phone was rooted.
I did not root my phone. I bought it as a brand new phone that was stock in every way.
Does a stock rom have a su binary and busybox installed?
Any help would be welcome! Thanks.
bombastique said:
Hello Forum,
Sorry if this post isn't in the right place; i'm not very good at posting on forums.
My question: does a stock phone already have a SU binary installed?
My situation specifically:
Sony Xperia XZ2 Compact (H8324)
It seems there's a SU binary in /sbin
Trying to execute it results in Error: java.io.IOException: Cannot run program "su": error=13, Permission denied
It seems there's also a busybox installed but I can't get any details about it
I checked my phone with Root Checker Pro by Joey Krim because an app (CoronaCheck) by the Dutch government used to identify yourself and state your corona status (for entry to concerts, festivals, restaurants etc) gave me a warning that my details were not safe because my phone was rooted.
I did not root my phone. I bought it as a brand new phone that was stock in every way.
Does a stock rom have a su binary and busybox installed?
Any help would be welcome! Thanks.
Click to expand...
Click to collapse
Since i believe, on all stock android firmware, since android 6 ( Marshmallow ) it comes with Toybox installed.
Toybox is similar Busybox. Except for the latest version ( i believe ) of toybox these versions don't have ' root ' like functionality, which is why ' su ' command will fail. This is why you will see the commands in directories like /bin etc.
As for apps, the detection methods have changed to more then looking for ' just if your phone is rooted ( SU Binaries )' or not. ie: unlocked bootloader etc, and maybe playstore certification/safetynet. Blame Google for that.
Toybox - Wikipedia
en.wikipedia.org