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
Related
Hi,Noob here,
I have a SCH-I800 branded for US Cellular. I tried rooting it with SuperOneClick and got "OK" and confirmation from it that my Tab was rooted. I tried Titanium to do a backup and it said my Tab wasn't rooted. I downloaded and tried Root Checker and it said the Tab wasn't rooted but that BusyBox was installed correctly. I rebooted the Tab and now it's looping in bootloader with the US Cell logo only. It loads into recovery and I tried wiping the cache and doing a factory reset, but it's still looping. Now what? I've done some searching but I guess I don't know what to put in the search field as it keeps coming up with no matches.
Help!
UPDATE (4/3/11): I haven't been able to use ADB with the Tab, so I bit the bullet and flashed stock Verizon firmware and that worked like a champ! And, it's rooted as well...not sure why unless SuperOneClick did transfer the files and exploit and it worked. So, I now have a US Cellular Tab running rooted stock VZW firmware. I just followed this guide: http://forum.xda-developers.com/showthread.php?t=967175
And I'm lovin' my Tab again
Not sure whats preventing it from booting.
Does ADB work?
If so maybe you can follow the steps in the manual rooting method & maybe that will fix what superonleclick screwed up.
See this thread http://forum.xda-developers.com/showthread.php?t=859712
Please note I used the su named su-v3
Thanks
I forgot about that in my panic! I'll give that a try and report back.
Update
I was finally able to work on the Tab last night for a few minutes. Tried ADB, as suggested. My PC sees the tab and loads the drivers when I plug in the USB, but I get "device not detected" when I try to do the manual root. I'll try connecting to Kies later today, but it didn't connect to Kies before the crash. Anyone have a link for the stock US Cellular CDMA Tab files?
Update...Got Adb to work by putting the tab into recovery. Now when I try to do the manual root it errors with "file or directory does not exist." If I try to push RATC to just /data, I get "permission denied ". Is there a directory that doesn't need permission that I can push RATC into?
Sent from my DROIDX using XDA Premium App
I used z4root to root my tablet. Working fine. Also installed cwm. No errors or problems.
Sent from my SCH-I800 using XDA App
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
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.
Hey guys I'm having a issue i was wondering if anyone could help.
i have rooted my HTC One (M7) when i accidentally wiped my entire phone i managed to install a new rom and every time i try to flash a new rom it gives me a status 7 now i installed root checker basic and it gives me this result this device does not have a proper root access and supersu tells me there is no SU binary installed i have tried to install the OTA date and it still gives me error 7 would any of you know what i could do to fix my problem no rome will flash on my phone
S -Off
and does wiping your entire phone delete the root? if not why does my root checker basic app have that error
Thanks
SourSoap said:
Hey guys I'm having a issue i was wondering if anyone could help.
i have rooted my HTC One (M7) when i accidentally wiped my entire phone i managed to install a new rom and every time i try to flash a new rom it gives me a status 7 now i installed root checker basic and it gives me this result this device does not have a proper root access and supersu tells me there is no SU binary installed i have tried to install the OTA date and it still gives me error 7 would any of you know what i could do to fix my problem no rome will flash on my phone
S -Off
and does wiping your entire phone delete the root? if not why does my root checker basic app have that error
Thanks
Click to expand...
Click to collapse
I guess the below two links will help you to resolve this error, though I didn't face this error, looks like this could be resolved...
http://highonandroid.com/android-roms/how-to-fix-status-7-error-with-cwm-recovery-on-rooted-android/
http://www.youtube.com/watch?v=QW1znjDLe-k
Hope this helps!!!
Hit thanks only if this helped you
I know these phones are a bit dated, but I have a pair of AT&T SGH-I747's that I've been trying to get rooted. Using Kingoroot, they both crashed and rebooted at different %'s and upon reboot one failed and one passed the root checker test.
The one that passed crashes upon attempting to do anything with root (seemingly as soon as an app requests the permission), this includes attempting to update the binary for SuperSU and any other root-based app.
The one without root continues to crash upon re-attempting the root process. Attempting a CF-Autoroot via Odin elicited a crash during the "Extracting" step on the phone (the actual Odin part went fine).
Is there any way to fix whatever may have been damaged/corrupted by the initial crashes and start over, or otherwise repair it? If there is a crashlog somewhere I can access I will post that if someone tells me where it may be.
Thanks in advance.