i have a verizon droid bionic 4g and i installed the latest update for 4.1.2. i did the root method on ubuntu 12.10 i386 and its weird how it ended up. i followed exactly what tom did on youtube and his seems to work properly. my issue is with su. when opening the app it says su binaries out of date. i click install and it says update failed....everytime. i tried install by recovery and it doesnt do anything.so how does that work out??
in addition to it acting weird i use rootchcker basic and it will say phone not rooted but if i click again it will say its rooted? dont know what is going on here but a little help would be nice.
Related
If you noticed, Superuser updated to 2.3 - make sure you do an nandroid backup before you attempt to apply it. I was able to apply it, and when I attempted to launch the application, it FCed on me. I was able to grant ROM Manager SU rights, but I just wanted everyone to be aware. You can see the original Superuser 2.3 thread here.
I did a nandroid restore and got rid of it since it was FC like mad.
SU 2.3.1 is up, and so far seems to be working without any issues.
maltzer said:
SU 2.3.1 is up, and so far seems to be working without any issues.
Click to expand...
Click to collapse
FYI, I am also using 2.3.1 without problems. The only crash I noticed was when you checked the log before actually trying anything that used superuser it caused a FC. After using a couple of root apps, I can check the log without a crash.
Can I flash the 2.3.1 over the 2.3 version? I can't find any confirmation that this is the right procedure to update su.
Can't even get this to install properly on the Captivate. Installation aborted every time in recovery mode.
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
might be helpful
rajendra82 said:
When I try to install from the market, I get package not signed properly error. What is the correct procedure to update your SuperUser.apk file?
Click to expand...
Click to collapse
if you go to the g1 thread and go to themes and ****....they got the apk for free......just gotta sideload it...ya digg
oh yeah it works perfect on my captivate....
I have su 2.3.1 and it works perfectly i upgraded it from market had 1.8 before i think on one of the one click root packages. No issues at all though and im back on stock rom right now.
ok so as the title says.... when i boot my phone up it says SU binary outdated, tap here to update.... so i tap and i get a fail...
Downloading manifest... fail!
also ran into this issue today. Whats the solution? Just wait until things become fixed?
Well, I know this is HTC section but It think this does not matter....
(Nexus-S, CM7, matr1x kernel)
same issue occurred on my nexus one with CM7.0 latest nightly ROM. trying to tap updating fail...... seeking for resolution to settle this issue....
i forget what i did exactly, but try replacing 'su' and 'superuser.apk' with a newer one..., make sure your updater/update-script is installing su properly
my friends droid X is doing it too..anyone know whatsup w/ it?
im thinking of uninstalling su and downloading it again off the market....yay or nay?
Got that last week. I hate the new superuser. Didn't work the same as the last version. Oh well, I'll just have to deal with it. BOO HOO HOO!
su binary outdated -nexus s
same thing happened to me. I got a notification saying su binary outdated click here to update. I clicked it and it failed to connect. so I just kept clicking retry again and again it worked after about 5 tries.
I went into the android market and updated it through there. It worked fine after that. =]]
I tried updating and I get the following message
"cannot update the su binary on phones that have some kind of write proteccion on the system partition like S-on"
Then I installed and ran the "fix" and when trying to fix, it force closes.
I have now deactivated the outdated su binary warning window from popping up but I am still wondering how to fix the problem.
cheers
Error : We are root but unable to push SU... It does this every time then recommends unrooting and trying again..
Any thoughts?
im having the same problem. it gives me a build prop error and states how it hopes i dont have a version that has the exploit fixed.
Fixed it by using my Mac... PC wasnt playing nice.
it happened to me too. as long as you see SU app there your rooted should be fine
I've been viewing these forums for quite sometime just never posted before. I was one of the people with the LG Revolution that lost the Super One Click Root when the OOA Update hit over the summer.
I have SU still installed and its been updated even though I can not gain root access and since I do not have root access I am unable to uninstall it. I have tried the One Click Root Tool for the LG Esteem after upgrading to GB. It say's that its completed but Root Check denies the fact it is rooted.
I tried Super One Click and it states the device is in fact rooted but when I try to use any root access apps it states "Unable to write". Any ideas on why it still wont allow the root to edit the read/write access for my device?
Thank you,
Mike
hey :9 I'm having the same issue. Heres to hoping someone figures it out
Ronin_EMT said:
I've been viewing these forums for quite sometime just never posted before. I was one of the people with the LG Revolution that lost the Super One Click Root when the OOA Update hit over the summer.
I have SU still installed and its been updated even though I can not gain root access and since I do not have root access I am unable to uninstall it. I have tried the One Click Root Tool for the LG Esteem after upgrading to GB. It say's that its completed but Root Check denies the fact it is rooted.
I tried Super One Click and it states the device is in fact rooted but when I try to use any root access apps it states "Unable to write". Any ideas on why it still wont allow the root to edit the read/write access for my device?
Thank you,
Mike
Click to expand...
Click to collapse
Do you know how to use adb?
Sent from my VS910 4G using xda premium
I'm from the Esteem side and some people were having the same problem after the superuser unroot fiasco and people couldn't re-root with the original one click because it did not clear the old su. Check over on Android forums/Esteem/All things root section. It was fixed by adding a few command lines to the script to clear the old su and give you the new su and binaries. HTH
Sent from my LG-MS910 using Tapatalk
aplusgfx said:
I'm from the Esteem side and some people were having the same problem after the superuser unroot fiasco and people couldn't re-root with the original one click because it did not clear the old su. Check over on Android forums/Esteem/All things root section. It was fixed by adding a few command lines to the script to clear the old su and give you the new su and binaries. HTH
Sent from my LG-MS910 using Tapatalk
Click to expand...
Click to collapse
Ty this worked wonders! I found it rather fast. Only problem with this guys batch is the fact you have to manually reboot your device for it to work. After I rebooted my apps were asking for SU access!
Here is a link for anyone else suffering from the unable to root because of SU already locked on your device.
androidforums.com/esteem-all-things-root/435750-one-click-root-updated-final-w-superuser-3-0-6-binary-3-0-3-download.html
Just remember after you've run the batch file to unplug your device and reboot.
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
neil.io said:
Apologies if this is blindingly obvious, but I've googled and searched and have found a lot of conflicting information this, so bear with me:
I went through the Moto bootloader unlock process for my Rogers Moto X and when I boot into fastboot it says it's unlocked. I then installed SuperSU and it seems to be working when I launch apps that require SU access. And some sites say if I'm on 4.4.3 it's impossible to make /system writeable. Basically, I'm still unable to install stuff that writes to /system like Busybox.
I've read about how /system is write-protected but haven't figured out how to actually fix this - some posts say start in recovery and I should be able to write to /system, others say it should work after I've gone through the Moto bootloader unlock process.
Can anyone here help a rsomewhat-newb get this sorted?
Click to expand...
Click to collapse
You flashed the latest version of TWRP custom recovery?
samwathegreat said:
You flashed the latest version of TWRP custom recovery?
Click to expand...
Click to collapse
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
neil.io said:
Think so - this was the image file I used: twrp-2.6.3.1-ghost-4.4.img
Click to expand...
Click to collapse
That might be the issue. It might not be compatible with 4.4.3
Try this one: http://techerrata.com/browse/twrp2/ghost
Also, which version of SuperSU are you using? There was a new one released recently. Find it here: http://download.chainfire.eu/451/SuperSU/UPDATE-SuperSU-v2.01.zip (Flash it from within TWRP - install ZIP)
Please update, and then advise whether or not your issue is resolved.
EDIT: Also, make sure you are using the "stericson" busybox variant. Others have been reported to cause issues.
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
neil.io said:
Thanks a lot for the fast responses - really appreciated.
I redid recovery using the version you linked to and also reinstalled SuperSU (I was using the current version already). When I try to install Busybox using the Stericson version as you mentioned I get an immediate error that it wasn't able to open a shell w/ root access. Running Root Checker tells me that root access is working, so I'm not sure what I've missed.
Again, many thanks!
Click to expand...
Click to collapse
Open SuperSU, and check to see if busybox is listed under apps. There should be a green "#" symbol next to it. It SHOULD have prompted you to grant access to it, so perhaps at some point you either denied the su request, or didn't see it. If you see a RED "#" symbol, tap it, and change to "Grant".
Please advise...
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
neil.io said:
It is, and it did have a green # beside it. I tried removing it and it requested permission as expected, but still failed.
I can't seem to get anything to install to system - Adaway also fails, for example.
Click to expand...
Click to collapse
I would suggest a full return to stock (follow the return to stock thread in the general sub-forum). This is not normal....
You appear to be using the XT1053, correct? Take caution to NOT downgrade or you could end up with a brick.
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
samwathegreat said:
Flashing the entire stock SBF can actually fix a corrupted filesystem - this is my best guess at what might fix your issue.
Click to expand...
Click to collapse
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
neil.io said:
Thanks again for the help. I just flashed the stock SBF and that seems to have fixed whatever was blocking Adaway from properly writing its hosts file, but Busybox stubbornly refuses to install. I got the permission request for SU when I launched it, but it fails just after I initiate the install. I tried changing the location to /system/bin with no luck.
Any other suggestions? I'm ready to give up for now, but it's frustrating when my Nexus 4 was so simple to set up.
Click to expand...
Click to collapse
How did you SBF to stock? Did you use RSD Lite? Did you retain userdata, or wipe everything (suggested)?
The stericson variant installs fine for me...granted I'm on 4.4.2 (the latest for my variant).
I did NOT use smart install...just used regular install to /system/xbin (You might consider trying smart install if you haven't yet...)
Honestly, I'm out of ideas. Although the "stericson" variant is recommended, perhaps you should try another version from the market if you need busybox.
I've done extensive searches and haven't found anyone else having a similar issue - even with Moto X on 4.4.3
I gave up and used the recovery method. Really odd - it does seem like the other installer apps couldn't mount /system as writeable, but it's weird that other apps that installed to that area worked.
Anyway, thanks again!