i am rooted and on CM7 build 29. everything works great, no forcecloses. i went into teminal emmulator and typed su enter and i get su permissions denied. i am still a noob. anyone else having this problem? anyone know what would be causing this or how to fix it?
cveez11 said:
i am rooted and on CM7 build 29. everything works great, no forcecloses. i went into teminal emmulator and typed su enter and i get su permissions denied. i am still a noob. anyone else having this problem? anyone know what would be causing this or how to fix it?
Click to expand...
Click to collapse
just because you have s=off, and flashed a custom ROM doesn't mean you are automaticallyrooted. Download VISIONary.apk and install. Open click "temp root", then permaroot. And you are good to go.
i have already done temp and perm root with visionary previous to flashing custom roms. do i need to do this after rebooting the phone each time?
cveez11 said:
i have already done temp and perm root with visionary previous to flashing custom roms. do i need to do this after rebooting the phone each time?
Click to expand...
Click to collapse
nope. S=off means the security protocol is not checking for SU access. However you do need to do it after you turn S=off so it will stick.
ok. ran it again and it is working. thank you so much!!
Related
Ok I used bubby's simple one click root I got s-off but my phone didn't take the root any help would be greatly appreciated thank you
check in your app folder if you have super user you are in fact rooted....if for some reason it was not installed go into a terminal emulator and type in "su" and you should get a superuser request and that would confirm you are rooted if it works...
Do you have clockwork recovery?
Sent from my HTC Desire HD using XDA Premium App
ThEiiNoCeNT said:
check in your app folder if you have super user you are in fact rooted....if for some reason it was not installed go into a terminal emulator and type in "su" and you should get a superuser request and that would confirm you are rooted if it works...
Click to expand...
Click to collapse
How would he get a su request if its not installed?
If the app isnt there, then its not there....
Calnshel said:
Ok I used bubby's simple one click root I got s-off but my phone didn't take the root any help would be greatly appreciated thank you
Click to expand...
Click to collapse
If you have s-Off then you can try re-flashing the rooted stock PD98IMG.zip from bubby's package. It's extracted into a temp dir on your computer when you run bubbys tool.
I'd guess it gets deleted once you close bubbys tool, as its only extracted temporarily for use by the tool, so you may have to start up the tool to get it to extract it, then find it before closing the tool again.
Once you find that PD98IMG.zip, put it on your SD card and reflash it that way.
Yeah I have superuser but it fc's on me and I have clockwork it's got me stumped maybe I'll try and reroot it again
Calnshel said:
Yeah I have superuser but it fc's on me and I have clockwork it's got me stumped maybe I'll try and reroot it again
Click to expand...
Click to collapse
If you're S-OFF and you've got clockwork, then you're pretty much as rooted as you need to be. Just install a custom ROM of your choice through clockwork. Any of the popular ones from the DEV thread should be properly configured for su, etc.
Calnshel said:
Yeah I have superuser but it fc's on me and I have clockwork it's got me stumped maybe I'll try and reroot it again
Click to expand...
Click to collapse
This problem has been encountered before, I believe. I forget the specifics of the fix, I think it's in bubbys thread somewhere, but it has to do with clearing data/cache for the superuser app and/or redownloading superuser from the market.
Check the thread for the exact details. May even be in the FAQ for bubbys tool (linked in post #1 of that thread).
I'm running 4.1.1 on my I9020A rooted. Stock Rom and Kernel. I searched the forums and the web, and every article I find gives instructions on going back to 2.3.X, THEN removing root. I don't want to go back, in fact I only want to un-root shortly, then go back to a rooted phone.
So my question is, Can I go through the locking steps of un-rooting, but leave the current ROM (4.1.1) installed?
Christopher_M said:
I'm running 4.1.1 on my I9020A rooted. Stock Rom and Kernel. I searched the forums and the web, and every article I find gives instructions on going back to 2.3.X, THEN removing root. I don't want to go back, in fact I only want to un-root shortly, then go back to a rooted phone.
So my question is, Can I go through the locking steps of un-rooting, but leave the current ROM (4.1.1) installed?
Click to expand...
Click to collapse
Delete, IN THIS ORDER:
/system/Superuser.apk
/system/xbin/su
/system/bin/su
Reboot your phone.
Root gone. If you want to root again, go to Androidsu.com, download the appropriate zip file, flash it, and you have root again.
oldblue910 said:
Delete, IN THIS ORDER:
/system/Superuser.apk
/system/xbin/su
/system/bin/su
Reboot your phone.
Root gone. If you want to root again, go to Androidsu.com, download the appropriate zip file, flash it, and you have root again.
Click to expand...
Click to collapse
Thanks for the quick reply! Should I additionally go through the fastboot steps of locking the bootloader as well?
Christopher_M said:
Thanks for the quick reply! Should I additionally go through the fastboot steps of locking the bootloader as well?
Click to expand...
Click to collapse
No. Unlocked bootloader and root are 2 different things.
polobunny said:
No. Unlocked bootloader and root are 2 different things.
Click to expand...
Click to collapse
What he said. Unless you're returning your phone for warranty repair or you're worried about security (like me), there's no reason to lock your bootloader.
I see. Thank you guys!
I have no Superuser.apk in the System/ folder.
I can only find com.noshufou.android.su-1.apk in data/app/
The other two files you listed I have found.
Christopher_M said:
I have no Superuser.apk in the System/ folder.
I can only find com.noshufou.android.su-1.apk in data/app/
The other two files you listed I have found.
Click to expand...
Click to collapse
That's the one. Delete it, it's the app to manage the su rights. su in xbin/bin is the binary for SuperUser
Ok, so I attempted to unroot. I opened es file explorer (Which launched with SU rights) and I was able to delete com.noshufou.android.su-1.apk in data/app/.
Then when I tried to delete su in /xbin, I was denied. Tried deleting su in /bin as same results. Denied.
Any thoughts?
Just flash stock. Now unrooted. To go back flash CWM and SU. This sounds a lot easier if oldblue's suggestion isn't working for you.
Use this for step by step.
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
jayjay3333 said:
Just flash stock. Now unrooted. To go back flash CWM and SU. This sounds a lot easier if oldblue's suggestion isn't working for you.
Use this for step by step.
http://forum.xda-developers.com/showthread.php?t=1785672
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yea, that was the conclusion I was coming too. Thanks for the help guys. :good:
You need to delete su binary via adb. Don't believe you can delete it while phone is under Android...
polobunny said:
You need to delete su binary via adb. Don't believe you can delete it while phone is under Android...
Click to expand...
Click to collapse
I'm new to android / linux. Been a Windows admin for 15+ years. I thought it not possible to delete SU while using SU, but I figured I'd try anyway. So ADB requires phone in FASTBOOT mode, correct?
Christopher_M said:
I'm new to android / linux. Been a Windows admin for 15+ years. I thought it not possible to delete SU while using SU, but I figured I'd try anyway. So ADB requires phone in FASTBOOT mode, correct?
Click to expand...
Click to collapse
No, just debugging mode.
MercilessLTD said:
No, just debugging mode.
Click to expand...
Click to collapse
In this case I think he would need to be in fastboot though.
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
Have you verify that your phone successfully rooted? Check it with root checker from the market.
ShapesBlue said:
I'm not sure if this works at this point but Chainfire had a super SU zip especially for 4.3 roms on his website. This may fix your issue
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Have you got a link? I'm looking but not finding.
nook2hd said:
If you have root before 4.3, my experience may be helpful to you: http://forum.xda-developers.com/showpost.php?p=49334077&postcount=21
Though, I didn't have problem with KNOX, my problem was SuperSU fail to update su binary.
Click to expand...
Click to collapse
I did have my phone rooted prior to the OTA. I've been rooting my phones for years, but have never messed with adb shell. I read your post before posting this question but it is kind of greek to me. I've always used the usual run this, run that, Odin this, CWM that type approaches. My SuperSU binary won't update because it can't disable KNOX.
buhohitr said:
Have you verify that your phone successfully rooted? Check it with root checker from the market.
Click to expand...
Click to collapse
I already used root checker to verify the phone did not root successfully.
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
I have the zip file. I downloaded it awhile ago. It's dated from October.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
---------- Post added at 01:44 PM ---------- Previous post was at 01:32 PM ----------
voigts said:
Have you got a link? I'm looking but not finding.
Click to expand...
Click to collapse
Best bet is his thread here on xda. He has a flashable zip
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
buhohitr said:
Use saferoot to install SuperSu, then run adb command as:
adb shell
You should see "$" prompt
Then type
/system/xbin/su
You should see "#"
Please verify.
Click to expand...
Click to collapse
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
voigts said:
I uninstalled SuperSU that I installed via Google play. I ran saferoot and let it do its thing and install SuperSU. When I get to the part of updating SuperSU, it fails to install. I ran your commands in adb, and I got the #.
Click to expand...
Click to collapse
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
buhohitr said:
Once you got the # , then run the following:
mount -o remount,rw /system
rm /system/bin/su
mount -o remount,ro /system
After this open SuperSu app and see if you can update. If updated successfully then reboot your phone.
Click to expand...
Click to collapse
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
voigts said:
Many thanks. It worked! :good: SuperSU updated just fine, and root checker shows root access. What did these commands actually do and what was the problem?
Click to expand...
Click to collapse
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
buhohitr said:
You have Superuser and SuperSu in your phone and the Superuser is the default one which root no longer working. So these commands basically remove the Superuser "su" executable file, which allowed your SuperSu to be updated and became a default root.
Click to expand...
Click to collapse
Makes sense. I get the concept. Thank you very much for your help. I Googled over and over and couldn't come up with an answer.
Using Saferoot with Knox disable
voigts said:
I have gone to the Saferoot thread http://forum.xda-developers.com/showthread.php?t=2565758 and am trying to root my S3 on the ML1 update. Everything in the install.bat runs fine, but when I get to the part where I need to open SuperSU and have it update binaries, I hit normal as instructed,KNOX is detected, and it fails to disable KNOX. No amount of searching is finding me an answer how to remedy this. I don't really care about trying 25 different ROMS or such, but just want root access again for Titanium Backup. Ideas?
Click to expand...
Click to collapse
I had tried the saferoot and it failed several times, until i installed kies 3 here's how finally was able to root my SCH-R530u Us cellular phone with JB 4.3:
downloaded saferoot & unzipped, then installed kies 3 & run it (make sure your phone is detected ok in kies) after kies opens & your phone is recognized open saferoot and run it. wait for the phone to restart, then go to play store and download supesu and install it or update it, then open supersu & it should ask to install binary. that should do it! Hope this helps:victory:
voigts said:
I've been trying to get this OTA 4.3 rooted with no success. I ran the saferoot install.bat, and after multiple tries, it finally managed to disable KNOX. I cannot however get SuperSU to update the binaries. I've run it a bunch of times. SuperSU managed to turn off Superuser citing a conflict, but simply fails at installation. I downloaded the 1.91 SuperSU update, and have tried multiple times to flash via stock recovery. After verifying update package comes up, it fails to verify update signature, ends, reboots, and doesn't install. I uninstalled SuperSU and tried to flash and it doesn't install.
I have Googled and Googled with no solutions.
I am also finding that this OTA isn't very stable. I am having intermittent weird issues like today my camera just wouldn't work for a while until reboot, and the phone has turned itself off a couple of times.
Click to expand...
Click to collapse
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
LYwaa said:
can you please tell me how did you manage to disable knox because i have the same exact problem tnx
Click to expand...
Click to collapse
I'd try to help but I know hardly anything about Knox. Try sending a PM to the person
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
So I flashed CM 11 and I am really enjoying this ROM. When initially setting up I mistakenly let Google restore my apps. I was not aware that SU was already built into CM 11, so I ended with SuperSU and SU installed at the same time. A few of my rooted apps were allowed root access, but now every time a new app ask for SU permission it is denied.I have deleted SuperSu and rootchecker says I have root.
Does anybody have a suggestion?
Reflash SuperSU from custom recovery.
iBolski said:
Reflash SuperSU from custom recovery.
Click to expand...
Click to collapse
Thanks for the reply. This worked. Is their a problem using SuperSu while SU is running as a system app...should I try to delete SU?
blindman75 said:
Thanks for the reply. This worked. Is their a problem using SuperSu while SU is running as a system app...should I try to delete SU?
Click to expand...
Click to collapse
Not that I know of. I've been using SuperSu all the time. I prefer it because:
I paid for it, so I want to get my money's worth!
Chainfire seems to always be on top of the latest fixes, including how Lollipop may have to require custom kernels, which means unlocked bootloaders. Uh oh.
I rooted my device using the root specific to this device. Now when I open up Super SU it says the SU binary needs to be updated. How do I go about this?
just go to settings ... is not hard ...
xotz said:
just go to settings ... is not hard ...
Click to expand...
Click to collapse
It doesn't work. Fails, and reboot to twrp does nothing. Im with OP.....how do you update the binary? Im trying to install xposed and I suspect this old binary is the reason it won't install.
carnivalrejectq said:
It doesn't work. Fails, and reboot to twrp does nothing. Im with OP.....how do you update the binary? Im trying to install xposed and I suspect this old binary is the reason it won't install.
Click to expand...
Click to collapse
did you figure it ? im having the same issue
Potatoverlord said:
did you figure it ? im having the same issue
Click to expand...
Click to collapse
I do not remember....sorry lol no longer have the phone.
Maybe flash the latest version of supersu from twrp? I'm just guessing because I run a stock unrooted rom.