Just flashed Pons 10.2 ROM. Welcome back and thanks for the new rom. Seems to run pretty smooth. But when I run apps with superuser access I get a warning about using an old su binary 13. Any one want to help me get a new version on my phone? Is it as easy as installing SuperSU from the play store?
First problem I've heard of this. Have you tried to have Superuser update the binary? Also, you could just either install SuperSU from the Play Store, or flash the flashable zip of SuperSU (my recommendation if su isn't working; more pain-free and fool proof), provided by Chainfire. Or do the same with Superuser by Koush off the Play Store, but the only downside to that one is, it's older than the one available in the ROM. Koush doesn't update the Play Store religiously.
It only really shows up with Titanium Backup. Happened with Evolv 3.3 as well. As soon as I tried anything with Android 4.3 I get that warning. Loving your new ROM. Seems faster than 10.1. Going to try that SuperSU.zip now.
Open the su app and go to its settings menu. There will be an option in there to update the binary.
Related
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!!
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
Hi,
I'm currently on an Xperia Arc running FXP231 (CM10), which comes with SuperUser. I'm trying to switch to SuperSU, but so far no luck.
I've tried:
Downloading the flashable zip that is on SuperSU thread, and flashing it from CWM. The result is that SuperUser is removed, like it should, but SuperSU is not installed. It's not anywhere to be found. If I install it manually afterwards or beforehand, it will say that there is no super user application installed (i.e.: I've lost root).
Installing it from the Play Store. It installs fine, but as soon as I open it, it asks me to update the binary. It gives me two options: from CWM or "normal".
If I choose normal, it gives me "installation failed" no matter what, and then it closes.
If I try the CWM option, SuperUser is removed, but if I open SuperSU afterwards it will tell me that there is no super user application installed, which is rather frustrating.
Does anybody have any idea what might be going on and what to do about it?
Thanks.
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.
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
kroogar said:
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
Click to expand...
Click to collapse
First flash a good recovery. Personal opinion PhilZ touch---first go though the page and u can notice an super user option first do that it'll remove all root environment then install Busybox on Rails app from playstore, though i've been using TWRP since a long time coz of it's simple UI themable too but it's having binary-update script issues (root-->need busybox ---environment issues) , then u can use either on of em Superuser/SuperSu disable Superuser in CM to use SuperSU.
kroogar said:
Hoping for some help to understand this:
I've been running CM10.2M1 up until a few days ago. For some reason I have both the CM built-in Superuser app AND SuperSU 1.80 installed. So a few days ago I upgraded to CM10.2 stable and was immediately prompted if I wanted to give superuser access to SuperSU.
So I'm thinking that having two root access controlling apps might be overdoing it so I uninstalled SuperSU. But then this root checker app that I have claims my device is not rooted. WTF? But it seems to be right since none of my root requiring apps are working (apart from Titanium Backup which doesn't complain). Root Explorer, Busu Box Installer and others complain about missing root access.
So: What's the deal? Do I need both Superuser and SuperSU? And if not how do I uninstall SuperSU without loosing root?
I really hope someone can explain this in simple terms so that I can understand what's going on...
Have a nice weekend everyone
Click to expand...
Click to collapse
Also try uninstalling both rebooting & reinstalling Superuser.
OffcerClancy said:
Also try uninstalling both rebooting & reinstalling Superuser.
Click to expand...
Click to collapse
are you even able to remove stock superuser that's baked into the rom?
t1.8matt said:
are you even able to remove stock superuser that's baked into the rom?
Click to expand...
Click to collapse
Can't answer categorically, but, w/ROM I am running it was listed in Settings, Apps, Downloaded, and allowed for Uninstall option.
OffcerClancy said:
Can't answer categorically, but, w/ROM I am running it was listed in Settings, Apps, Downloaded, and allowed for Uninstall option.
Click to expand...
Click to collapse
Yeah, then it can be uninstalled. But on a rom like CMetal that I'm running right now, you can't uninstall superuser like that, it's baked in which might be what the OP is dealing with. To not use the built in superuser you just flash supersu over it and the system uses that for root access and not superuser.