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
Related
Tried to run a fix permissions and I got "An error occurred while attempting to run privileged commands!".
I'm running the 8/1 OTA, new hydra kernel, and 2.15.X radio.
Has anyone encountered this before??
For the record, I already updated to superuser 2.3.1 and it's still not working.
Not sure if this should be in the themes and Apps section or General.....I have had the same issue although I don't get any error when I try to run the fix permissions option it goes to a black screen then stalls. This didn't start happening until I upgraded to the newest Superuser Permissions.
Yeah I actually tried switching super user apps, but it didn't make a difference
-Sent from your mom's phone.
I just tweeted a message to Koush about it. Hopefully we'll get a reply.
Keep us updated. I just ran into this issue too. Did a backup last night with no issues, but suddenly today, I'm getting that message.
any word on this
I'm on cm6.0.1 now and no longer having the issue. Never got a reply from koush though.
-Sent from your mom's phone.
I don't mess with Fix Permissions anymore. It really screwed me up the first time I worked on SkyRaider, and a bunch of strange things began to happen. I find my phone tends to run better just leaving everything as-is.
Asterdroid said:
Tried to run a fix permissions and I got "An error occurred while attempting to run privileged commands!".
I'm running the 8/1 OTA, new hydra kernel, and 2.15.X radio.
Has anyone encountered this before??
For the record, I already updated to superuser 2.3.1 and it's still not working.
Click to expand...
Click to collapse
I was experiencing a similar deal and the only solution was; removed, rebooted and reinstalled the app......that resolved all the issues. My current setup: Leaked Hybrid Froyo 2.2 version 3.21.605.1, radio 2.15.00.07.28, Hydra 2.6.32 occuv-v10, S-OFF and what not.......Good Luck !
Another thing, in my case I was not even able to uninstall the app using the MENU/SETTINGS/APPLICATIONS/MANAGE APPLICATIONS procedure so I used 'Root Explorer', search for the app, Mount R/O and "adios"........
been reading about a bug do to "Bash" in the new roms, not sure what the fix is as i don't use RM but i think in the skyraider 3.0 rc3 tread there is a temp fix for this issue
i have been having an issue with rom manager also every time i tell it to install a zip from sd or do a back up or even reboot into recovery i get an error that says the update.zip failed signature veri. also it says the update.zip is in /cache
this thing up dates every time superuser has been closed, or I reboot my phone...why will it not hold the update?
In CWM you need to Flash the Su Binary Update Fix.
Download Here: http://www.multiupload.com/RIAHB3BS8C
Axiomkid said:
In CWM you need to Flash the Su Binary Update Fix.
Download Here: http://www.multiupload.com/RIAHB3BS8C
Click to expand...
Click to collapse
thanks I appreciate it!
Which ROM/kernel?
I'm actually going to be releasing a kernel which disables root injection because of issues that have cropped up since ChainsDD resumed updating his binary.
Entropy512 said:
Which ROM/kernel?
I'm actually going to be releasing a kernel which disables root injection because of issues that have cropped up since ChainsDD resumed updating his binary.
Click to expand...
Click to collapse
Im using infused 2.2.3 and your daily driver most current kernel.
I flashed the su binary fix and it seems to have fixed the problem.
What do you mean no root injection? And what problems were encountered?
Hey I also wanted to take a moment to say thanks for your work on this forum and with the development...it makes it nice for noobs like me to get the absolute most out of their phone. It is hugely appreciated.
Many kernels (including all voodoo ones except for my latest release) that will automatically root the device on bootup.
I removed it from my latest kernel due to all the problems autoroot scripts have caused lately. LB pushed a fixed script to me - but by the time he did it I had already completely yanked it.
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
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...
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
ExcludedDroid said:
Hi, as the title states, yesterday I received a notification from Verizon that a new update is ready to be installed. I can only defer it for 5 days, which I did. I'm running TouchWiz Eclipse ROM 1.0. I went ahead and renamed SMD.apk to SMD.bak, because I read somewhere that's what I needed to do to prevent Verizon from pushing updates.
What I wanted to do is confirm that what I did would work (as in prevent Verizon from updating my awesome ROM and thus bricking my device). Also, I think the update is already downloaded and just ready to be installed. Will that affect anything? Would renaming SMD.apk still prevent it from being installed, or is that only to prevent it from being downloaded?? Please halp!!
Cheers,
ED
Click to expand...
Click to collapse
Best way to check is to go into Settings/About Phone/Software Update. If it force closes then you're all set. Renaming or uninstalling "smd 1.0" causes the phone to not actively poll for future OTAs from that moment on. Using a file explorer, check in /cache and delete the update.zip for VRBMF1 cuz you deferred the OTA which means it saved to your phone already.
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
ExcludedDroid said:
I checked Settings>About device but there's no Check for upgrade option. I assume it was taken out as part of the ROM. I went ahead and deleted some sort of fupgrade in /cache. Then went and wiped cache in recovery and fixed permissions just to top it off. I think I'm good!! Thanks
Click to expand...
Click to collapse
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
xavierxxx2p said:
i think eclipse is aosp not touchwiz , iam running the same thing but its aosp eclispe here the link to verified
http://forum.xda-developers.com/showthread.php?t=2142267 if it is you will never have problems of verizon trying to push ota updates
Click to expand...
Click to collapse
There is a touchwiz version, it just wasn't updated in awhile and it's pretty buried in the development section.
Sent from my SCH-I535 using Tapatalk 4 Beta