Database Info

[Q] Rooted with CWM, can't update binary

Hey everyone,
Earlier this week I was on here trying to figure out how to get rooted. A very helpful member explained how I could do it with CWM and flashing the superuser zip file. I did this and successfully rooted my phone!
Now it keeps prompting me to update the superuser binary. But I get the error "Failed to find currently installed su binary. Update cannot continue"
I'm still rooted, and my WiFi tethering still works, so is outdated binary a problem? How can I fix this and get it updated?

TomB985 said:
Hey everyone,
Earlier this week I was on here trying to figure out how to get rooted. A very helpful member explained how I could do it with CWM and flashing the superuser zip file. I did this and successfully rooted my phone!
Now it keeps prompting me to update the superuser binary. But I get the error "Failed to find currently installed su binary. Update cannot continue"
I'm still rooted, and my WiFi tethering still works, so is outdated binary a problem? How can I fix this and get it updated?
Click to expand...
Click to collapse
do you know the version of superuser you flashed? should've been 2.3.6.3 or something... you may need to update the app in the market (3.0.5 is what is current I think) and then the update should go through fine, or it'll at least stop prompting for it

anoninja118 said:
do you know the version of superuser you flashed? should've been 2.3.6.3 or something... you may need to update the app in the market (3.0.5 is what is current I think) and then the update should go through fine, or it'll at least stop prompting for it
Click to expand...
Click to collapse
I'm getting the same error with 3.0.4 and 3.0.5. Also if you check the app in the market, the reviews are filled with comments from users having all kinds of problems across numerous phones since superuser was updated to 3.0.4 or 3.0.5. Not sure what is going on, but it seems to be a pretty widespread problem for which no one has yet found a solution.

landshark68 said:
I'm getting the same error with 3.0.4 and 3.0.5. Also if you check the app in the market, the reviews are filled with comments from users having all kinds of problems across numerous phones since superuser was updated to 3.0.4 or 3.0.5. Not sure what is going on, but it seems to be a pretty widespread problem for which no one has yet found a solution.
Click to expand...
Click to collapse
ah good to know, I've been running a test build of Nitros new Eclipse rom and I've been bugging him that superuser binary won't update lol

Just checked, and I have version 3.0.5. Sounds like it might just be an issue with the update?

TomB985 said:
Just checked, and I have version 3.0.5. Sounds like it might just be an issue with the update?
Click to expand...
Click to collapse
Yep. The app description now has a *Note that reads "app and binary will have different versions. the app is updated more often than the binary is" Stick with version 2.3.6 and you should have no problems.

landshark68 said:
Yep. The app description now has a *Note that reads "app and binary will have different versions. the app is updated more often than the binary is" Stick with version 2.3.6 and you should have no problems.
Click to expand...
Click to collapse
I rolled back to an older version but it still gets pretty annoying when it says to update binary every time I use a root app
blazing through on my 4G Droid Charge

Wifi SU binary update issues

Ok so over the weekend I decided to root my Charge and after going through the steps on youtube for the latest gingerbread Root charge I had success.
I found a apk file for a wifi tether and got it up and running, however I was receiving a SU binary update out of date and needed to update. My upload/download when the program was pretty slow too(.40kb/.23kb) so I decided to update.
However after getting through the Fixing database, Checking busybox, current install path and downlading new binary ok, when I get to checking md5sum I get a FAIL. So I rolled back SU and downloaded barnacle. It would work the first time I start it after downloading, again crappy speeds. After I stopped and restarted it I get these errors and the wifi tether doesn't start:
- NAT: Could not set NTU of pdpbr1: Invalid argument
- WIFI: Could not set ad-hoc mode of eth0: Invalid argument
- Connected to NAT
- Running...
- WIFI: Conld not set ssid of eth0: Invalid argument
- Stopped unexpectedly!
Trying to keep SU updated besides the binary I get the same errors with both programs from the start. I have root checker and am rooted correctly. What am I missing or doing wrong?
Also I was recently told I needed to boot into Clock Work Recovery, which I didn't have installed and turn off SU. I don't even know how to do that.....but I did just install clockwork recovery but still have no idea how to turn off SU. HELP please.
X

OK so I got clockwork recovery up and flashed. I still have the binary needs updated. I have the 3.0.3 zip file and when it goes to flash it it fails and reboots my phone. Please someone help. I've got binary 2.3.1 currently and can't get any higher

Google search for ChainsDD's superuser website (guy who made superuser I guess), from there you can download the most current superuser apk and binaries to flash in CWM plus update super user in the market afterwards if possible then update binaries through the app like normal and it should work... also what tethering app are you using? a common one is wifi tether version 3.1 beta6 in which there's a known issue that the app will not turn off tethering unless the phone is rebooted causing problems like yours and seems to be why it only works after you reboot
there is a newer version that is 3.1 beta7 I think and that apk is supposed to be fixed for that... also within the tether app set the master settings or something (haven't used it in a while lol don't remember what its called) to the Samsung Fascinate profile and use soft tap
sent from my Acer Iconia A500 beast of a tablet via XDA app

I tried that last night as well. I found the latest 3.0.6 and flashed it using clockwork. It showed and updated my SU to v3.0.3, HOWEVER...the Su binary version was still at 2.3.1 and won't update. I still get the same errors as above.
I was using Barnacle and another stable wifi, can't remember the name atm and its no longer on the phone. I have the file at home.

Anyone? I've emailed ChainsDD with no reply either.

what kernel are you using?

Running 2.6.35.7 EP3

Help, still can't figure this out.

Anyone have an answer on why this is happening? Did I forget to do something? Should I startover with another flash? If so, can anyone point me to where I can get back to stock or what I need to do?
Thanks
X

xconcepts said:
Anyone have an answer on why this is happening? Did I forget to do something? Should I startover with another flash? If so, can anyone point me to where I can get back to stock or what I need to do?
Thanks
X
Click to expand...
Click to collapse
if there's no fix by now then yeah I'd start over... find the Fix Your Phone sticky in the dev section and grab the stock EE4 .tar file as well as the pit file, flash them both in Odin (pit in PIT section and the rom in PDA with the repartition box checked) and when you boot up you should be at fresh new stock EE4 froyo... it'll probably prompt you to update to GB at that point which you can either do or ignore and put CWM on there and flash your rom of choice
sent from my Acer Iconia A500 beast of a tablet via XDA app

Htc One S Root SuperSU0.99 issue

Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck

Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.

I started this thread just because of the issue SUPERSU 0.99 brings to HTC One S with Jelly Bean update.
I hope i can help someone because i didnt find any solution to my problem until i flashed superuser and it solved my problem.

shadowch31 said:
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
Click to expand...
Click to collapse
I agree that this adds clutter, but I have been lightly following the threads for the JB ROMs and tried using superuser (though not the rc) without it working (still unable to update system). It's good to have this kind of solution in its own thread but general would probably be a better section.
Sent from my HTC One S Special Edition using xda app-developers app

This doesn't belong in the dev section for multiple reasons
Sent from my HTC VLE_U using xda app-developers app

Im sorry i didnt see that it was Development section. If someone can move it pls do so.

everyone uses SU...... this is very important for everyone using JB... leave it in here...
I feel it belongs here... this is where SU apps are in the development section... SO, this is where it should stay... (that is just my opinion)

I never want to start this thread like an development because im not a developer.
Reason is that i want to share my issue with anyone who is facing the same problem as i did.
Just like i said if someone think this thread doesn´t belong here then admins can move it to right section.

Updated to JB with OTA yesterday night.
Short version:
-Initially rooted with CWM recovery-> flashed MoDaCo stock recovery
-Apply OTA
-Flash CWM recovery
-Used CWM recovery to flash SuperSU 0.99 zip
-Uninstall/reinstall SuperSu from the Market
When starting SuperSU, it asks for update, if agree -> reboot.
BUT
When using root needing apps, like Titanium backup or FX file manager, they ask for root permission through SU and everything runs normally.
So SuperSU seems to work, only the front end app has some bug. I'm staying with that config waiting for an update.

Hi, same problem here on S3 cpu. Is this method works on S3 cpu as well? Thx for replying.

Hi. I think I have a problem with SuperSU (or something else??). I first started SuperSU last thursday (31.1.2013.). It ask me to update binary, I hit OK, and then it took about half hour to restart. System then recovered, and everything seem to be OK, but it's not!
When I connect my HTC One S to PC I only see files created (photos, videos) until 31.01.2013. Also, when I run Settings -> Memory com.android.settings crashes.
What to do?
I'm new to android. Plese help!

bihslk said:
Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Click to expand...
Click to collapse
I'm glad I ran across your thread. It helped me tremendously...
Da Baron

Any idea on how to get SuperSU work instead of SuperUser? I purchased SuperSU in the play store and I think it just looks better...

SuperSu Survival Mode Question

I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?

Just leave it where it is. I'm not even sure if it'll work with an ota. The nexus 5 is so easy to root that I've never tried it. It had been helpful on some other devices butt it's not needed with the n5
gee2012 makes a good point for cm roms of you want to maintain supersu
Edit out of curiosity I did enable survival mode on 4.4. It does survive update to 4.4.2

Sanvido said:
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Click to expand...
Click to collapse
You can turn it on all the time, also when you flash CM superSU will remain the main superuser app.

You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.

Thanks guys for the answer.

Charlular said:
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Click to expand...
Click to collapse
^^^
Well, of course you would keep root with OmniROM, since it is a rooted rom.
Why wouldn't it keep root when you're using a ROM that requires root to begin with?
Forgive me for being a compleat (sic) Nitwit... but I thought that Rootkeeper and Survival Mode in SU were supposed to keep root through an OTA update for the stock ROM, like going from 4.3 to 4.4 which I think is impossible because when I tap 'check for updates', the message comes up that (and I'm paraphrasing here'... can't be updated because your system has been modified.
When reading through all the caveats in OTARootkeeper in the Play Store, it seems to say that you can un-root temporarily in order to install a new ROM update, and then re-enable root.
Of course, then the Dev. goes on to say that OTARootkeeper won't work with SuperSU installed because OTARootkeeper has it's own version of SU built in.
Am I right or wrong... and if I'm wrong, I wish that somebody would explain it to me exactly where.
Am I correct in assuming that OTARootkeeper will allow temporarily un-rooting for the purpose of installing let's say, an update to the stock ROM which I happen to be running, and then re-rooting and still keep root status?
I've had OTARootkeeper installed for quite a while, but I read that it no longer works with 4.3 to 4.4 stock ROM updates anyway, so I guess my comments become moot.

Lost Root on Stock ROM - Solved

Sharing this here in case it saves somebody else an hour or so.
I rooted my stock Infinity ROM at ICS and have followed all the OTA updates to current 4.2.1 just using OTA Rootkeeper, apparently successfully. It was only recently when I tried to add another app that required root that I discovered I couldn't grant root permissions. To make it worse, I cleared SU data in an attempted fix which successfully removed root from apps that had been OK :crying:
Then I came across this fix that had been applied to a TF300:
http://forum.xda-developers.com/showthread.php?t=2183105
It works as described on the TF700 too and seems to have completely fixed my problem.
Thanks to Koush for the fix to blubbhome for posting it somewhere I could find it.
I am out of warranty now and about to install a different ROM so thanks to all devs for the good work.