[Q] Improperly rooted - Sprint Samsung Galaxy S III

I'm kind of new to Android, but I have decent computing experience. My problem is that I recently rooted my SPH-L710 (stock rom) and when I ran Busybox I received the error message "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is improperly rooted. Try removing the superuser/supersu permissions, uninstalling this app," etc etc.
I have attempted various methods using things like root explorer and terminal emulator to remove/ change the permissions so I might delete the su file, to no avail as the phone isn't properly rooted. One thread on here mentioned that formatting the sd card - I assume it meant the phone itself - would do the trick. After that, I would of course have to flash a rom, correct? Thanks for your time.

I would do the rooting process over again, with a new download of all files.
Do you have cwm or another custom recovery working?
sent from a secret underground bunker

winstonmarrs74 said:
I'm kind of new to Android, but I have decent computing experience. My problem is that I recently rooted my SPH-L710 (stock rom) and when I ran Busybox I received the error message "There was a problem opening a shell with root access. This is either being caused by superuser/supersu or by a device that is improperly rooted. Try removing the superuser/supersu permissions, uninstalling this app," etc etc.
I have attempted various methods using things like root explorer and terminal emulator to remove/ change the permissions so I might delete the su file, to no avail as the phone isn't properly rooted. One thread on here mentioned that formatting the sd card - I assume it meant the phone itself - would do the trick. After that, I would of course have to flash a rom, correct? Thanks for your time.
Click to expand...
Click to collapse
try flashing this in recovery http://downloads.androidsu.com/superuser/su-bin-3.1.1-arm-signed.zip its the binary files required for SuperUser if your having trouble with gaining root access

Annnnd try opening super user or super such right after booting
Sent from my SPH-L710 using xda app-developers app

mjben said:
I would do the rooting process over again, with a new download of all files.
Do you have cwm or another custom recovery working?
sent from a secret underground bunker
Click to expand...
Click to collapse
I'm running CWM. I've successfully rooted a few times before, but this last time it didn't work. I unrooted and then rooted again three times and even re-downloaded all the files (cwm, odin, rom) but I can't seem to fix this. I'll attempt it again and hopefully it'll take this time.

Fantastic! I flashed the su binary zip, rebooted and superuser was already to go and phone is now properly rooted. Thanks very much! :good:

Thank you!
evo4gnoob said:
try flashing this in recovery (SU url I can't post...) its the binary files required for SuperUser if your having trouble with gaining root access
Click to expand...
Click to collapse
I would like to take this opportunity to thank you. I had been having issues trying to get root on my Sprint GS3, and nothing worked until I used that SU.
:laugh:

Paleogryph said:
I would like to take this opportunity to thank you. I had been having issues trying to get root on my Sprint GS3, and nothing worked until I used that SU.
:laugh:
Click to expand...
Click to collapse
No problem m8 glad I could help
Sent from my SPH-L710 using xda app-developers app

Related

[PATCH] Install Superuser, Busybox and Rooted Kernel (For Use After Obtaining S-OFF)

The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
rmk40 said:
The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
Click to expand...
Click to collapse
This the same file on Rootwiki? Or is it the same minus the kernel?
http://rootzwiki.com/showthread.php?587-ROOT-Gaining-root-after-s-off
rmk40 said:
The first thing anyone is going to want to do once AlphaRev's S-OFF process is complete will be to get your device properly rooted within Android. I have created a simple update zip which will take care of the following for you:
Re-install the stock kernel, using a rooted ramdisk (credit jcase).
Install the Superuser app and su binary in /system/xbin.
Install and setup Busybox in /system/xbin.
Simply install this patch via CWM and reboot. From there you can proceed to run any root apps you need (such as Titanium).
Click to expand...
Click to collapse
THANK YOU SO MUCH YOUR THE BEST lol
That's the method I used. Worked a treat when I found it at rootzwiki last night. Many thanks!
Sent from my ADR6350 using XDA App
Is busy box already on cm7?
Sent from my Incredible 2 using XDA Premium App
Superuser keeps force closing when I use ROM Manager or Wireless Tether.
knipp21 said:
Is busy box already on cm7?
Sent from my Incredible 2 using XDA Premium App
Click to expand...
Click to collapse
I think so. I was told not to install this patch after cm7.
MotorcycleMike said:
Superuser keeps force closing when I use ROM Manager or Wireless Tether.
Click to expand...
Click to collapse
Try going into the application menu and clear the data for superuser. Fixed my fc problems on my phone.
Sent from my ADR6350 using XDA Premium App
The attached zip goes on the root of the sd card correct? then boot into CWM and install zip?
dobosininja said:
Try going into the application menu and clear the data for superuser. Fixed my fc problems on my phone.
Sent from my ADR6350 using XDA Premium App
Click to expand...
Click to collapse
Fixed mine as well. Thanks!
bluedegeon said:
The attached zip goes on the root of the sd card correct? then boot into CWM and install zip?
Click to expand...
Click to collapse
that is correct
ltredbeard said:
that is correct
Click to expand...
Click to collapse
Thanks!
Sorry maybe this is a stupid question.. How can we use CWM to flash this .zip if CWM won't work without a root first???
demersk89 said:
Sorry maybe this is a stupid question.. How can we use CWM to flash this .zip if CWM won't work without a root first???
Click to expand...
Click to collapse
AlphaRevX patches CWM for your recovery during the S-OFF process. And even if it fails you can follow a guide posted on this forum on how to fastboot it.
I flashed this .zip through CWM and Titanium backup won't work. It's telling me that it is unable to find root. I clicked the "Problems?" button and still nothing happened. I remember with the Eris it would run the busybox after you pushed that button. I might just try to install busybox manually as described on Titanium's wiki.
Any other thoughts before I do that?
I flashed this file on my stock but rooted/soff incredible 2, and i seem to have lost root privileges. Luckyily I made a backup before I flashed this so now I'm back to my original problem, of not being able to fix permissions via rom manger because it doesn't see root.
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong? Does fastboot need to be turned off?
Sithben24 said:
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong?
Click to expand...
Click to collapse
Turn off fast boot in settings>applications. Turn off. Keep down held while powering on.
Sent from my ADR6350 using Tapatalk
Sithben24 said:
Hey, I have S-Off and patched CWM, but when I hold down the volume button and try to power on, it goes straight to the HTC screen. What am I doing wrong?
Click to expand...
Click to collapse
Menu/settings/power/uncheck fastboot
Perfect. Thanks guys!

Revolutionary Rooted but Not???

First I wanted to say hi to all of you. Evo 4G is my second Android phone. I'm still a noob in training but I'm getting by.
I'm having a bit of a issue with trying to use some apps for root only and keep getting that I need to be rooted. Yes S-Off is displayed but I'm still running into this issue no matter what. Did I miss something? I'm still searching the forum to find a answer but I haven't found anything as of yet.
Let me know what you guys think.
Thanks
Z3r0
Edit: I figured out what the problem was. Me being stupid and not reading enough. Mods go ahead and lock/delete this thread.
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Greenfieldan said:
As someone previously stated, you'll need an app called "superuser" to allow apps to use root permissions.
Click to expand...
Click to collapse
This.
Running Revolutionary Roots your phone, but you need superuser to give programs root access. To give programs root access, you will need a rooted ROM with the superuser application or just download the superuser app.
oldwesterncowboy said:
to double check, there is an app in the market called "root check" by joeykrim.
and for apps to gain access to the phone you should have the app "superuser" it gives other apps permission to access root.
Click to expand...
Click to collapse
Yeah I figured that out after reading the sticky at the beginning. My fault for not paying attention. I'm now rooted and loving it.
Thanks for the reply's guys.
I really did it now!!!
Ok so I'm back to ask some questions due to a noob mistake. Now I have been reading many of the threads that are available to fix my actual issues that I'm dealing with. I'm going to be very detailed so I apologize in advance.
So like a dumb dumb I decided to unroot my Evo as I was sure/ uncomfortable using the rooted OTA update to up date. So now I did some more reading and I did not need to unroot. Sorry I dont' know what I was thinking.
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
I was able to update the root OTA update but that was all that was done. So now I'm here asking for more help as I did more reading how to fix the current issue I'm having and its not working.
PLEASE Help me or guide me in the right direction to fix this.
This is all I am trying to accomplish:
1. Figure out why and what happend and get my Evo rooted
2. Apply the Amon RA recovery
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Anyone have any ideas?
Sent from my PC36100 using xda premium
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
revolutionary s-off
Another noob here.... Ok I used revolutionary.io to root my 2.3.3
Hboot says s-off, downloaded superuser app, and astro file
Why does it say can't delete file when I try to delete pre installed files like Amazon mp3, ect
Ran root checker app from market said
Root Access is not properly configured or was not granted.
Superuser.apk - com.noshufou.android.su - version 3.0.5 is installed!
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
The adb binary is set to default shell user access as a standard non-root user
Standard su binary location: ls -l /system/bin/su:
/system/bin/su: No such file or directory
Standard su binary location: ls -l /system/xbin/su:
/system/xbin/su: No such file or directory
Alternate su binary location:
/sbin/su: Permission denied
Alternate su type binary location:
/system/xbin/sudo: No such file or directory
SU binary not found or not operating properly
tommytomatoe said:
So are you s on or s off when you go into hboot?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
z3r0t0l0rEnCe said:
s on which I know is not rooted. No matter what I try it refuses to accept the revolutionary root program. Should I try a different root method or is Revolutionary for 2.3.3 the only method? I've looked and can't find any other way.
Click to expand...
Click to collapse
What is your HBOOT version, when you go into Bootloader?
Last I checked revolutionary won't s-off anything besides hboot 2.15 & 2.16. Not even the revolutionary hboot 6.xx
tapatalk signature here. lovely.
2.16
Sent from my PC36100 using xda premium
z3r0t0l0rEnCe said:
2.16
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Captain_Throwback said:
First, I would flash an unrooted stock ROM - the latest, if possible (see this post).
Then, try rooting via Revolutionary again (revolutionary.io). Sometimes during the unrooting process, everything isn't completely restored to stock, so you might just need to flash a completely stock ROM to get back to the point where Revolutionary will work again.
Click to expand...
Click to collapse
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
z3r0t0l0rEnCe said:
Thanks for the heads up on this info. Now with the Stock RUU being RUU_SuperSonic_GB_Sprint_WWE_4.53.651.1_Radio_2.15 .00.0808_NV_2.15_release, does the 2.15 represent the HBOOT? As mine is the 2.16 or does that not matter?
Click to expand...
Click to collapse
The file name has nothing to do with the HBOOT version. It doesn't matter. If the HBOOT version you currently have is newer than the version in the RUU, it will simply skip updating it.
Ok ill test it when I get home from work tonight.
Sent from my PC36100 using xda premium
z3r0t0l0rEnCe said:
I've tried to run Revolutionary but all it does is aborts the operation everytime. I tried to change the recovery from Clockwork to Amon RA as I read that it is better so I tried to do that too. Nope that doesn't work either.
Now if I need to completely wipe my phone I will do it if that is what you think is needed to be done. I know how to back up my app/ contacts etc. So just assist this dumb dumb please!
Click to expand...
Click to collapse
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
IamNotSureX said:
All you need to is flash another hboot for the evo. (Any of them will work. Doesn't really matter. Look around for the files and a guide is out there I'm sure. If not, PM me. Anyway, flash it. And then run revolutionary. It should work then.
I did not know that, tommytomatoe. But regardless, what I suggested would work if my thinking is correct.
Click to expand...
Click to collapse
He said he has Hboot 2.16. If I'm not mistaken you cannot downgrade your Hboot version from something like 2.16 to 2.15 or 2.10. Either way, Revolutionary will be able to root 2.16 just fine. Seems like all he needs to do is follow Captain Throwbacks advice to get his phone out of "What the hell are you doing to me" mode.
I have yet to perform the flash. I got caught up at work late last night. I'll do it tonight for sure when I get off work.
Thank you all for the input and I'll let you all know if my Evo will let me get it out of ""What the hell are you doing to me" mode.

[Q] Rooted Question / App Confusion

Please know in advance I've read top to bottom and through page after page of post and guide here and on other site before rooting, and I searched before posting this question...
-I rooted my Dinc using Unrevoked3, just this past Saturday.
-I successfully installed Titanium Backup and successfully have used it for back-up.
-I UNsuccessfully did an install of Root Explorer. They told me it sounds like I'm likely not rooted.
-I downloaded ConnectBot, typed Su in the cmd line and received a "Permission denied".
Unrevoked3 and the use of Titanium Backup tell me I am rooted. Root Explorer not getting permission and cmd command tell me I'm not.
Should I simply run the Unrevoked3 process again?
My end goal is to flash a custom rom ideally with better battery life, a better bluetooth (my stock set-up stinks on bt devices) and a different look like CM7.
Here is my software info it if matters:
Android Version 2.2
Baseband 2.15.00.07.28
Kernal Version 2.6.32.17-g9a2fc16
Software 3.26.605.1
I thought I read and re-read and search extensively, much appreciate any help!!
MeatplowMike said:
Please know in advance I've read top to bottom and through page after page of post and guide here and on other site before rooting, and I searched before posting this question...
-I rooted my Dinc using Unrevoked3, just this past Saturday.
-I successfully installed Titanium Backup and successfully have used it for back-up.
-I UNsuccessfully did an install of Root Explorer. They told me it sounds like I'm likely not rooted.
-I downloaded ConnectBot, typed Su in the cmd line and received a "Permission denied".
Unrevoked3 and the use of Titanium Backup tell me I am rooted. Root Explorer not getting permission and cmd command tell me I'm not.
Should I simply run the Unrevoked3 process again?
My end goal is to flash a custom rom ideally with better battery life, a better bluetooth (my stock set-up stinks on bt devices) and a different look like CM7.
Here is my software info it if matters:
Android Version 2.2
Baseband 2.15.00.07.28
Kernal Version 2.6.32.17-g9a2fc16
Software 3.26.605.1
I thought I read and re-read and search extensively, much appreciate any help!!
Click to expand...
Click to collapse
Sounds like you don't have superuser installed. If you do try uninstalling it and download it off the market.
jackbtha1 said:
Sounds like you don't have superuser installed. If you do try uninstalling it and download it off the market.
Click to expand...
Click to collapse
Even if you have it installed, search Superuser in the Market, download/install. Then open the Superuser app itself, hit Menu - Preferences, then scroll down to Su binary vX.Y.Z (X Y Z will be numbers). Touch it and update the su binary, hopefully that'll let you as it'll ask you to "Allow" root access.
I did the update and it failed, twice I'll try the remove and reinstall method next. Thx for the advice.
Sent from my ADR6300 using XDA App
So Superuser won't even allow for a removal. It was "remove updates", "clear data" or "force stop" only.
Sent from my ADR6300 using XDA App
MeatplowMike said:
So Superuser won't even allow for a removal. It was "remove updates", "clear data" or "force stop" only.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I actually remember running into this on my brothers phone a while back. I think I installed busy box off the market and it solved that problem. Not sure if that would work but worth a shot.
jackbtha1 said:
I actually remember running into this on my brothers phone a while back. I think I installed busy box off the market and it solved that problem. Not sure if that would work but worth a shot.
Click to expand...
Click to collapse
Very true, I had a similar issue once trying to uninstall apps, they'd always reappear after reboot. Needed busybox installed which fixed it.
EDIT: Instead of trying to unistall it, go to the Superuser site here, and there's a 3.0.6 flashable zip file that you can flash in ClockworkMod Recovery, maybe give that a try...? But install busybox too as mentioned above by jackbtha1.
Huge thanks for the advice. I installed Busybox and it fixed the problem immediately after I rebooted. I didn't know it was needed because Superuser, in the binary update logged that it had success with busybox, yet I'd never installed it. Alls well, thanks! Odd that Titanium was working on it's own without permissions.
NOW... if anyone wants to hold my hand through flashing a ROM on this thing. It seems many of the walk-thru guides are a year old or the updated process is scattered.
Before you install any roms make a stock backup so you have something to fall back on.
https://market.android.com/details?id=com.koushikdutta.rommanager
Sent from my Incredible using XDA Premium App
MeatplowMike said:
Huge thanks for the advice. I installed Busybox and it fixed the problem immediately after I rebooted. I didn't know it was needed because Superuser, in the binary update logged that it had success with busybox, yet I'd never installed it. Alls well, thanks! Odd that Titanium was working on it's own without permissions.
NOW... if anyone wants to hold my hand through flashing a ROM on this thing. It seems many of the walk-thru guides are a year old or the updated process is scattered.
Click to expand...
Click to collapse
The reason TiB worked was it uses a modified busybox within the app itself, so that's why it worked okay.
Sent from my ADR6300 using xda premium
Glad to hear everything worked out for you. Now as far as flashing a custom Rom do some research first and make sure you make a back up before flashing anything.

[Q] Improper Root, Help Required. New To Android

Alright so here's the deal, installed Clockwork Recovery just fine, transferred CWM_SuperUser_v3.0.7 onto phone and installed just fine, went to use Root Checker Pro and this is what i got (screen shots below) so whats my next step and how do i go about it? Any and all help will be greatly appreciated
Did you actually root the phone, or did you just download the apps from the market? If you haven't rooted the phone yet, then CWM, and SU won't do you any good as they need root access to perform the needed operations. If you haven't already, refer to this thread for rooting instructions: http://forum.xda-developers.com/showthread.php?t=1739426 Hope this helps!
Did you get a prompt when you ran Root Checker? It looks like everything's set up fine and you just failed to acknowledge that the app wanted superuser access.
I didnt get any prompts from Root Checker, is it possible thay the .zip file I used was bad or corrupted and simply didnt work? What about trying a different .zip?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] Need help, temp rooted phone.

I rooted my phone and it is temporary only since if I boot my phone, it will be back to normal until I start the root again from the WeakSauce2 app. I am new to rooting so please help me out! I pretty much don't know what to do with this temp root besides downloading rooted apps in play store.
If I were to fully root my phone and do the process, would there be any way to save my files before it wipes my phone?
raymart said:
I rooted my phone and it is temporary only since if I boot my phone, it will be back to normal until I start the root again from the WeakSauce2 app. I am new to rooting so please help me out! I pretty much don't know what to do with this temp root besides downloading rooted apps in play store.
If I were to fully root my phone and do the process, would there be any way to save my files before it wipes my phone?
Click to expand...
Click to collapse
Sunshine doesn't wipe. You run it and get s-off. Then flash twrp and make a backup.
Sent from my HTC6525LVW using Tapatalk
Can I jump in on this subject. I'm new to the vzw m7 and I been doing some research and decided to root my phone using Weak Sauce 2 . So I downloaded sauce it said root activated then I downloaded Supersu opened supersu up get message says:The SU Binary needs to be updated.Continue? Then I press continue of course, error: installation failed please reboot and try again.I have rebooted countless times to no avail:beer:
So I go to Root Checker to check status and wow it says Congratulations! This device has root access? Htc6500LVW 4.4.3 I can install root apps like TB,Root Explorer,Etc and It grants permission.What is going on with this what am I missing .I'm try to hold off on sunshine for now because I just spent my allowance on this phone..Thanks in advance.
Sent from my Nexus 4 using XDA Free mobile app
WelfareBaby said:
Can I jump in on this subject. I'm new to the vzw m7 and I been doing some research and decided to root my phone using Weak Sauce 2 . So I downloaded sauce it said root activated then I downloaded Supersu opened supersu up get message says:The SU Binary needs to be updated.Continue? Then I press continue of course, error: installation failed please reboot and try again.I have rebooted countless times to no avail[emoji481]
So I go to Root Checker to check status and wow it says Congratulations! This device has root access? Htc6500LVW 4.4.3 I can install root apps like TB,Root Explorer,Etc and It grants permission.What is going on with this what am I missing .I'm try to hold off on sunshine for now because I just spent my allowance on this phone..Thanks in advance.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
You are temp rooted. That's it. Can't update binaries because you can't flash anything and because system write protection is still on. You need to s-off as soon as you can of you want to disable system write protection and be able to update binaries, flash a custom recovery and flash a custom Rom.

Categories

Resources