I rooted my first Evo and had no problems until I had a screen issue. I re-rooted it and returned it for a replacement. They gave me a refurb, which they swore they didn't, but it was obvious that the phone had been used before. Didn't root because it had issues with the screen again. I now have a new one again and have tried rooting using Revolutionary.io and the tutorial like I did the first time. It's giving me an hboot version of 6.16 with s-off (I started with hboot 2.16) but it's still not rooted. I have the clockwork mod installed and can run a full backup but ROM Manager nor Titanium backup can attain root. What did I do wrong? What do I do next? I've been searching all over and can't quite figure out what went wrong. Thanks in advance.
Wipe cache and dalvik cache in recovery and flash this http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
It's the super user app and binaries. Which is what grants root access.
Edited with correct link.
With the phone booted up, go into the superuser app and force it to check for updates. You should be on 3.0.3.2 if not have a look here and download the binaries! Then try again.
I checked before I got started and it said that SU was v3.0.6 (40). When I tried to have SU update itself, it said it was a legacy version, couldn't find Busybox and failed to give root. When I tried to flash the .zip file you linked to it said every thing went fine but it's still at v3.0.6 (40). I'm kind of confused. Still no root.
The superuser app and su binaries are two different things. So you most likely are up to date. It also sounds like you need busy box. Look up busy box installer on market.
You will also likely have to refresh the two apps, simply clear their data, after you have busy box. Then restart them and allow root access.
Sent from my PC36100 using xda premium
I have the busybox installer in my app tray but when I run it to install busybox it says I don't have root and can't install.
You need to wipe data on all of your apps that require root. And refresh all of them. Also look into your superuser app and check if any settings are denying root.
Sent from my PC36100 using xda premium
Well, SU has nothing in it. Nothing in the logs or apps list, I open it and it's empty. I went in to the applications menu setting, selected each app that would need root and cleared their data. Only one app had any data, that was ROM Manager, I think. I even booted into recovery and had it fix permissions. Still the same thing. ROM manager can't fix permissions (no root), SU has nothing in any lists, TI Backup won't run because of no root and BusyBox won't install because of no root.
This is also weird. You guys AND the SU Update built into the program are saying that I should be running SU version 3.0.3.2, but I'm running version 3.0.6 (40) and that it's legacy. When I try to run an update from the SU in my programs tray it does this.
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3.2
Checking installed version = legacy (in red)
Fixing database... okay!
Checking for busybox... not found (in red)
Downloading custom busybox... okay!
checking md5sum... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... okay!
Gaining root access... fail! (in red)
Are you using a custom ROM?
You have the custom hboot, so revolutionary worked... You can access recovery and use the commands, so you have to have root, it's just something in the ROM...
Tell me what ROM version you are on, in settings > about phone > software
Did you get the "efghi" version or the "d?" sounds like you flashed the donut version....
Again su binaries: 3.0.3.2 and Superuser: 3.0.6 are two different things the binaries are the actual code to allow "switch user" access and Superuser is the app that controls the permisions.
Your version should not be "legacy" it should be 3.0.3.2 efghi
I have run custom ROM's in the past on my other rooted Evo, but this one is the bone stock ROM. I haven't really had the chance to use any custom ROM's yet. I wasn't sure if it would work until I got this problem resolved. My version is:
Android Version
2.3.3
Kernel
2.6.3510-g13578ee
[email protected] #1
Build Number
4.54.651.1 CL134969 release-keys
PRI
2.15_003
PRL
61086
Ok, so you were correct in that I had installed the "d" version instead of the "efghi" version. I flashed the correct version and everything is able to get root access now! The only other problem I have now is trying to install busybox, it gets root but fails to install "failed to copy over busybox to /system/xbin/". I cleared all data and tried again. And of course, Titanium backup can't get root because of no busybox. The main thing I'm wanting to do is remove Sprint's bloat and wait for Deck's ICS build to get WiMax support.
imheroldman said:
Are you using a custom ROM?
You have the custom hboot, so revolutionary worked... You can access recovery and use the commands, so you have to have root, it's just something in the ROM...
Tell me what ROM version you are on, in settings > about phone > software
Did you get the "efghi" version or the "d?" sounds like you flashed the donut version....
Again su binaries: 3.0.3.2 and Superuser: 3.0.6 are two different things the binaries are the actual code to allow "switch user" access and Superuser is the app that controls the permisions.
Your version should not be "legacy" it should be 3.0.3.2 efghi
Click to expand...
Click to collapse
Whoa that was my bad, browser must of skipped when I was copying....sorry
Finally, success! Apparently since I hqd installed the busybox installer before I fully had root it didn't install properly. I uninstalled and re-installed it and everything is working great. Thanks for your help, guys!
Sent from my PC36100 using XDA
Glad to hear it! Superuser and su should now update auto-magically!
Sent from my PC36100 using xda premium
Having similar S Off Issue
Ok, I have an EVO 4G (Supersonic) with HBoot 2.16.0001 and used the following "Guide" to root: http://forum.xda-developers.com/showthread.php?t=1218386
(Showing S OFF)
(Android Version
2.3.3
Kernel Version
2.6.35.10-gc0a661b
[email protected] #1
Build Number
4.24.651.1 CL61076 release-keys
Software Number
4.24.651.1
PRL Version
60690)
After reading this(and having basically the same problem... showed S OFF/SU saying not rooted... almost word for word what "toothles" put) ... I went into ASTRO File Manager to see if I indeed had "d" or "efgh".... Shock... "d". Hooked my phone to the PC and removed the .zip and other files it created.... Replaced it with the efgh(3.0.6-efgh-signed.zip) file from Superuser Site: http://hosted.androidsu.com/superuser/
Then back to HBooter... Recovery (Revolutionary)... File from .zip... Then loaded the efgh.... So now this is what my Superuser shows:
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.1.1
Checking installed version = 3.03 (in red)
Unpacking sutools... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Gaining root access... okay!
Remounting /system as rw... okay!
Copying su to /system... fail! (in red)
Then "Try again" at bottom.
I've looked for answers, and had hope when I found this..... Any suggestions would be well received.... I know this is the place to go when one has Android issues... Have found solutions here for other issues and have sent many a person here when they have had issues. Thanks for your time; and if I should have posted it somewhere else... Sorry.
Related
Hi everyone,
I have some problems with my Desire and need your help, which is highly appreciated
I rooted my Desire (PVT4) a while ago and flashed AmonRa Recovery 2.0.1 in order to install CustomRoms. I used DeFrost 6.1 for quite some time before i flashed GingerVillain 2.7 and recognized the following issues:
If i open ConnectBot or TerminalEmulator, i always get "not found" or "permission denied". I.e. i wanted to ship the Dalvik Cache to my SD when i had GingerVillain installed and tried to get some more internal space. So I entered "su" in ConnectBot but it said "su not found". If i enter cat/proc/mtd to determine if it is S-off or on (i don't remember if i changed it) i get the same result..."not found"...
I have root access and i can flash ROM's etc. but i can't use any terminal commands... Furthermore, the Superuser-App told me that there is an update available but i can't install it. I can't flash the zip in the recovery ("Can't open su-2-3-1-bin-signed.zip") . So i tried updating using the app itself but now it says: Su binary voutdated...
Something's wrong in here...What can I do to fix this?
Current Settings:
Android 2.3.3
LeeDroid GB 3.0.8.2 (With HTC Sense, App2SD+ working fine)
Baseband: 32.49.00.32U_5.11.05.27
Kernel: 2.6.35.10-g308ba26
Superuser: 2.3.6.3
Not every Rom is loaded with commands for Terminal emulator...
Regarding Superuser, there is application in android market called "superuser update fixer"..download and install it...update issue will be solved...
You should install busybox.
Swyped from Oxygen with Transparent XDA App
First of all thx for your replies
jjdoctor said:
Not every Rom is loaded with commands for Terminal emulator...
Regarding Superuser, there is application in android market called "superuser update fixer"..download and install it...update issue will be solved...
Click to expand...
Click to collapse
I had this problem since i switched to GingerVillain ROM and also now on LeeDroid GB. It should definitely work with GV, not sure bout LeeDroid though.
I installed SU Update Fixer, it says that there is no problem. I tried forcing a fix but the app is shut down... Superuser details: v2.3.6.3, Su binary v.2.3.1-ef
MatDrOiD said:
You should install busybox.
Swyped from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
If i open Titanium Backup, it says busybox and root access ok. Busybox 1.18.4
Any other suggestions on how to fix this?
Sometimes the superuser app/process just shuts down, too. After reboot it works again...something's just not totally right i guess.
I switched to Leedroid and the problem basically disappeared... Strange though
Sent from my HTC Desire using XDA App
I was running stock rom, rooted with bloat removed. I flashed the update through Odin, flashed CWM, and reinstalled Superuser through CWM, and when I went to update the binary in Superuser, I noticed that it said that Busybox was not found. So I installed Busybox Installer and tried to run, but got an error saying that there are problems with some core utilities necessary to load Busybox.
I then reflashed the update, CWM and Superuser, hoping that would fix the problem, but it hasn't.
My question is if there is anyway to load Busybox internally through CWM? Even if it is an older version of Busybox, once the core utilities are there, I can always update through the Busybox Installer.
Worst case scenario, I just back up through Titanium, flash back to complete stock, update, and then load CWM...but I always hate starting from the beginning if I don't have to.
The only apps I use that require root are SetCPU, and Titanium Backup. Would I even notice anything without Busybox working? I know Titanium used to be able to update Busybox right through the app, but then they updated and don't anymore...but I'm not sure if Titanium still requires Busybox to properly work.
I posted screen shots of the error messages I see in both Busybox Installer and when updating the binaries through Superuser. Any help would be greatly appreciated. Thanks!
Nevermind, I fixed it. For some reason, the Busybox app from Stephen (Stericson) was the one that kept giving me the error. So I downloaded the Busybox Installer app from JRummy16, and it worked flawlessly the first time. I went back in to Superuser to see if it recognizes it, and it does. So all seems to be good.
Moderator, please feel free to delete the thread. Thanks!
You solved my problem thanks man!!
OK, since search is down, I'm going to be a noob and ask something I know has been asked before...
I installed and ran V6 Supercharger yesterday, but wasn't completely sure if it worked properly, so I decided to start again. So I went back to tutorial and started again, first trying to re-install Busybox 1.18.2, as directed. I got message "unable to load busybox onto /sys/xbin". Odd.
So I backed out and opened Busybox installer again, this time got error message "No Root Access!". Tried that a few times, but same message. So I opened Titanium, No Root, MyBackUpRoot...NO ROOT!! 4Ext is also reporting errors, although it does accept SU Permissions...
Ummm...help??
E: Build.prop Editor, ROM manager, RAM Manager Pro, Root Explorer, ES Explorer all granted SU Permissions...
I think I know what may have happened, although don't know how or exactly why... Thinking busybox.apk has been deleted from /system somehow.
I am able to boot to recovery and doing nandroid now, so I obviously still have root. Going to wipe Dalvic and reflash ROM.
Fingers crossed.
Nope.
Did fresh download of Runnymede 6041 and reflashed.
Still same problem. Titanium does not see root, neither does busybox or MbR.
Really not happy now.
Edit: If anyone reading this has experience, where would I find the Busybox.apk, to verify if it was missing and how would I replace??
Have you try to clear superuser data in settings-applications-manage applications ?
I had this problem when I restore data for superuser using mybackup root.
Also check how much free system space that you have before downloading a new busybox. Maybe the free space is not enough for the new busybox.
Download program called visionary and install it. Open it then press (temproot) then keep going on what u doing. Make sure that u having 2.2 android or custom ROM. I did that and update worked as it should with no problem
Sent from my HTC Desire using XDA
Thanks for replies guys.
@mahmoud, want to point out I am root and s-off with custom ROM etc. Not sure if temproot will help me. I'm pretty sure the original Busybox file that is installed during unrEVOked has gone missing. Is that what happened for you too??
As I say, I can still boot to recovery and most SU apps are working...just not those that need Busybox.
@ckp, I will try that this evening. Cheers.
777ace said:
Thanks for replies guys.
@mahmoud, want to point out I am root and s-off with custom ROM etc. Not sure if temproot will help me. I'm pretty sure the original Busybox file that is installed during unrEVOked has gone missing. Is that what happened for you too??
As I say, I can still boot to recovery and most SU apps are working...just not those that need Busybox.
@ckp, I will try that this evening. Cheers.
Click to expand...
Click to collapse
Aaaaaahhhhh ok. Sorry I misunderstood u. What happened to me is that I wanted to root my phone and I couldn't use unrEVOked
Coz it always show me CID MISSING so I downloaded 3 apps and rooted my phone without computer. Visionary, superuser and ROM manager. I had to update busybox in superuser app. But it didn't update until I did temproot using visionary app. I don't know if that will help u or no. But nothing will happen if u downloaded visionary and temproot then try busybox.. let me know if u had any thing. Goodluck
Sent from my HTC Desire using XDA
777ace said:
OK, since search is down, I'm going to be a noob and ask something I know has been asked before...
I installed and ran V6 Supercharger yesterday, but wasn't completely sure if it worked properly, so I decided to start again. So I went back to tutorial and started again, first trying to re-install Busybox 1.18.2, as directed. I got message "unable to load busybox onto /sys/xbin". Odd.
So I backed out and opened Busybox installer again, this time got error message "No Root Access!". Tried that a few times, but same message. So I opened Titanium, No Root, MyBackUpRoot...NO ROOT!! 4Ext is also reporting errors, although it does accept SU Permissions...
Ummm...help??
E: Build.prop Editor, ROM manager, RAM Manager Pro, Root Explorer, ES Explorer all granted SU Permissions...
Click to expand...
Click to collapse
AFAIK, Titanium uses its own Busybox, so I would suggest uninstalling Titanium, reflashing Busybox (I don't know if it's possible), then reflashing Titanium. I hope this will help.
Thanks Coempi, but I did that already... Somehow, whatever tells Busybox or Titanium that I have root, is not doing that.
Dunno wtf just happened, but I uninstalled Titanium again, rebooted (again) and installed Busybox straight up... Everything back to normal, but nfi what I did.
I guess sometimes its the simple things, yeah...??
Thanks for help all.
777ace said:
Dunno wtf just happened, but I uninstalled Titanium again, rebooted (again) and installed Busybox straight up... Everything back to normal, but nfi what I did.
I guess sometimes its the simple things, yeah...??
Thanks for help all.
Click to expand...
Click to collapse
I'm glad it worked out finally.
Sent from my HTC Desire using Tapatalk
So I used odin to flash the official stock jelllybean rom then I used the Samsung toolkit to flash clockwork mod recovery and root. To root it said to flash a superuser zip in recovery. I did.after I reboot everything is working fine. Apps gain root access the promp pops up but after a few minutes it didn't anymore and I cant open busybox or setcpu because it cant gain access but the apps I already granted can. I updated su binary and it fails on gaining root access.
This happens with both super su and superuser. I also tried starting again by oding rom and rooting again. No luck. Please help
Sent from my SGH-T999 using xda premium
Sent from my SGH-T999 using xda premium
Ok, you can try a few things.
First since you have Root Explorer already granted, go into /system/xbin and make sure that there is a file named su. If not, then go into /system/bin and see if it is there. Follow this: If it is in /system/bin, copy it and put it in /system/xbin, check permissions and reboot. Then try an un-granted app and see if that works. Pay attention to the bin and xbin parts here ok.!?
^^^Edit: While you are in /system/xbin make sure that busybox is there also. Just to be sure it installed properly.
Second. If the above didn't work, the go to the market and ChainsDD used to have an app called SuperUser Updated Fixer or something like that. I remember a long time ago, I was having some trouble updating the binaries (as were tons of other people) and he came out with that handy little app. I have been using it since (whenever I have a ROM that uses SuperUser.apk).
Third: I literally just read over in mrRobinson's thread that ICS likes SuperUser, while JB likes SuperSU. Might be something to look into. Maybe swapping out the two apps, might alleviate the issue.
I tried swapping out to super su but was having the same problem. Instead of trying the root explorer method you posted I thought I would go ahead and clean install yet another time. I just wanted the update and root access to work no errors. So here's what I did to fix it and it worked however there's another problem now.
I factory reset, wiped caches
flashed jb stock firmware (instead of the stock fw i now flashed mr.robinsons prerooted firmware)
rebooted checked and saw super su was working fine with my apps.
flashed clockwork mod recovery
made a nandroid backup
flashed wildchilds stock deodexed jb rom (i needed a deodexed rom thats why i flashed this otherwise i would of just kept stock)
booted up and in the play store theres an update for Super Su however i cant update it, it gives me an error.
error retrieving information from server. cant download.tried wifi on off, mobile data on off, clearing google play data and cache. no luck. restored nandroid and there was no update so i clicked reinstall from playstore in su and when i went to go download it, it gave the same error.
So my previous problem is fixed and i dont seem to be losing root anymore but now I cant update SU anymore.
Never mind I seemed to have linked the two issues just because 1 happened before the other, but that might not be the case.
The Google play error is now happening with other apps that i try to update as well.
Is this happening to you guys too?
sometimes when i power off my phone it doesnt boot anymore it gets stuck on boot loop. for example all i did was fix permissions in cwm and it got stuck on boot loop.
Did you Odin root66?
Yeah I odined the root 66 fw by Robinson. That has fixed losing root. Super user is working fine. The only remaining problem is that I get into a boot loop sometimes when I restart for some reason like when I fix permissions.
Sent from my SGH-T999 using xda premium
I only had root on my phone for TiBackup and I had Clockwork installed, as I was thinking about installing an a rom. Then AT&T pushed this crap down, and removed / disabled all of that for me. Nothing like shields popping up constantly. Thanks!
I installed CF-Auto-Root-d2att-d2uc-samsungsghi747.zip, which was modified on Nov 20th, 2013. That somewhat worked, as I kept getting SuperSu stopped working constantly, but TiBackup said it had root access. The Shield kept popping up saying crap was blocked still.
Following the directions here: http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/ I reinstalled my clockwork, told it to boot into recovery via it's menu, and installed UPDATE-SuperSU-v1.43.zip. That fixed everything. No more shield, and root is back.
I can now start SuperSu, view it's settings, etc.
All is right with the world again.
Just did a full backup and got a shield warning, so this root is "different" than the way it used to be.
Since you are rooted would you mind pulling the modem?
Just use Terminal Emulator and Copy and Paste this into it
su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
You have only one quote there?
I just ran:
su
pm disable com.sec.knox.seandroid
It came back and said disabled.
I then ran another full TiBackup. No *****ing/shield.
RockRatt said:
Since you are rooted would you mind pulling the modem?
Just use Terminal Emulator and Copy and Paste this into it
su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
RockRatt said:
Since you are rooted would you mind pulling the modem?
Just use Terminal Emulator and Copy and Paste this into it
su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
i pulled already and post in other threat where you asked..
Thanks
Sent from my SAMSUNG-SGH-I747 using Tapatalk
dansthunder said:
I only had root on my phone for TiBackup and I had Clockwork installed, as I was thinking about installing an a rom. Then AT&T pushed this crap down, and removed / disabled all of that for me. Nothing like shields popping up constantly. Thanks!
I installed CF-Auto-Root-d2att-d2uc-samsungsghi747.zip, which was modified on Nov 20th, 2013. That somewhat worked, as I kept getting SuperSu stopped working constantly, but TiBackup said it had root access. The Shield kept popping up saying crap was blocked still.
Following the directions here: http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/ I reinstalled my clockwork, told it to boot into recovery via it's menu, and installed UPDATE-SuperSU-v1.43.zip. That fixed everything. No more shield, and root is back.
I can now start SuperSu, view it's settings, etc.
All is right with the world again.
Click to expand...
Click to collapse
I also did the OTA update but I completely removed KNOX. Still getting FC on the latest version of Supersu, even if I did get temporary root. When I tried installing 1.43, it tells me to update the Su Binaries, which I looked up and apparently you need the latest SuperSu, which doesn't work. I believe I am only getting temporary root right now. Everytime I install TWRP it gets removed, TiBu now says I have no root access. I am positive I removed Knox. I used TiBu to freeze everything as well as root explorer to delete anything Knox. I also ran the Knox Cleaner zip just in case. No more knox dialogs but no root and no SuperSu . How did you get 1.43 working??
bkong said:
I also did the OTA update but I completely removed KNOX. Still getting FC on the latest version of Supersu, even if I did get temporary root. When I tried installing 1.43, it tells me to update the Su Binaries, which I looked up and apparently you need the latest SuperSu, which doesn't work. I believe I am only getting temporary root right now. Everytime I install TWRP it gets removed, TiBu now says I have no root access. I am positive I removed Knox. I used TiBu to freeze everything as well as root explorer to delete anything Knox. I also ran the Knox Cleaner zip just in case. No more knox dialogs but no root and no SuperSu . How did you get 1.43 working??
Click to expand...
Click to collapse
I installed the latest SuperSu via Clockwork sideload,(think that's the proper term) which was updated on the 23rd. (via the url in the original post) Otherwise it was still force closing constantly. Updating via Google play doesn't do enough. Flash the zip via your manager and it should solve your problem.
edit: btw, after the root alone, I couldn't even open the SuperSu app, it immediately crashed. But, TiBackup said I had root, which was a first. That's when I hunted down the SuperSu files.
To recap, I did:
Install the chainfire root via odin as it requires. When my phone was up, I had the shield still going nuts, supersu force closing, but I went into Clockwork, which I already had installed before the OTA, told it to install the recovery, and then rebooted into that recovery from within clockwork menu. From there, I installed the SuperSu update zip, and that fixed the constant force close of SuperSu. After that, went to terminal and did a su disable on knox.
I followed the instructions and was able to gain root access again without the shield popping up when I opened superSU. I then also went into Terminal Emulator and did a "su pm disable com.sec.knox.seandroid" which appeared to work, however....
When I tried to debloat some of the AT&T/Samsung apps using Clean Master (from KS Mobile - available in the Play Store), it asked for SU rights and I granted them, but when the un-installation of the built in apps began... the stupid shield popped up again and Clean Master failed to uninstall everything.
Edit: Froze Knox services with Titanium Backup. The shield didn't show up, but it (Clean Master) still failed to uninstall any of the apps.
Edit2: Ashaman got rid of the stuff for me, naturally. But I'm a noob to all of this and don't know if Clean Master not working correctly is a root issue alone, or a combination of issues with 4.3 OTA/root & Clean Master. Debloating with rooted 4.1.2 OTA worked fine with Clean Master.