http://forum.xda-developers.com/showthread.php?t=1192300
I followed the step 1-3 to get S-off on the guide. I flashed a mod but there was a bug so i decided to do a recovery from the back up i made before I flashed the su-2.3.6.3-efgh-signed.zip for permanent root. When I downloaded and opened ROM manager It tells me I need to root first. When I open revolutionary it tells me I have S-off already.
Any chance someone can help figure this out.
aznboy189 said:
http://forum.xda-developers.com/showthread.php?t=1192300
I followed the step 1-3 to get S-off on the guide. I flashed a mod but there was a bug so i decided to do a recovery from the back up i made before I flashed the su-2.3.6.3-efgh-signed.zip for permanent root. When I downloaded and opened ROM manager It tells me I need to root first. When I open revolutionary it tells me I have S-off already.
Any chance someone can help figure this out.
Click to expand...
Click to collapse
Hi,
Best suggestion is to run revolutionary again.
This time go through the whole process.
When I run revolutionary it tells me I have S-off already. Shouldn't I be able to use rom manager if it tells me that? It said superuser was not found.
Just try flashing the su-2.3.6.3-efgh-signed.zip again you should then have root.
Don't I need to do it through CWM recovery? It won't let me go into CWM because it thinks I don't have root accesss.
aznboy189 said:
http://forum.xda-developers.com/showthread.php?t=1192300
I followed the step 1-3 to get S-off on the guide. I flashed a mod but there was a bug so i decided to do a recovery from the back up i made before I flashed the su-2.3.6.3-efgh-signed.zip for permanent root. When I downloaded and opened ROM manager It tells me I need to root first. When I open revolutionary it tells me I have S-off already.
Any chance someone can help figure this out.
Click to expand...
Click to collapse
update your superuser and binary versions (from market for app, binary update from within app itself) then you will not have problems with ROM Manager
Thank you guys for all your suggestion. I was able to fix it. I download superuser and it didn't work. What ended up working was going into bootloader, going into recovery and it booted it into cwm recovery from there I was able to flash the su file.
Hello!
I tried to root my long time stock sensation but faced some problems.
at first i got installation aborted and error while flashing superuser but managed to flash successfully thx to x_viper_x guide, after several attempts. But even after it said that the flash finished successfully rootchecker didnt find my phone rooted ( "No root access") so i flashed superuser again, checked again and the same... busybox also cant find root =\
there is any solution for this, without flashing custom rom?
FreakyDR said:
Hello!
I tried to root my long time stock sensation but faced some problems.
at first i got installation aborted and error while flashing superuser but managed to flash successfully thx to x_viper_x guide, after several attempts. But even after it said that the flash finished successfully rootchecker didnt find my phone rooted ( "No root access") so i flashed superuser again, checked again and the same... busybox also cant find root =\
there is any solution for this, without flashing custom rom?
Click to expand...
Click to collapse
if you are on ics you can try my one click root tool ...from my soff guide ..link in my signature
I decided to go back to stock when the new Jellybean finally rolled out.
So I wiped the phone. and put the factory boot.img back in and used the 4.0.4 RUU. (updated OTA after reboot)
Then I unlocked the Bootloader and put TWRP 2.5.0.0 on it.
Then I rebooted and downloaded SuperSU and Busybox from the Play store
I tried updated the Binary and it failed. So I flashed the UPDATE Super SU.zip
rebooted and was able to update the Binary. But everytime I try to update the busybox it says "it looks like the installation of BusyBox was not successful"
and when I delete Tmobile bloatware using TB (which promted and is granted Superuser permissions). The Phone will randomly reboot and when it restarts all the applications I just deleted are back.
What am I missing?
Like this:
usaff22 said:
Same as this problem, many people have asked a similar question before:
http://forum.xda-developers.com/showthread.php?t=2067495
Edit:
And these:
http://forum.xda-developers.com/showthread.php?p=39138367
http://forum.xda-developers.com/showthread.php?t=2190194
Click to expand...
Click to collapse
usaff22 said:
Like this:
Click to expand...
Click to collapse
Thanks.
I just didnt know what "keywords" to search for that.
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.