Ok, i watched your sign-up video, i read the READ BEFORE POSTING posts, i searched the search, and there is NOT ONE STRAIGHT answer to the most obvious and common issue: su binary update.
There is no official thread titled "su binary" which would be NICE if somebody post a link to the latest version of su binary, tells people which version of Superuser app it is compatible with (i know there's at least 3, CWM, ChainSDD, and Chainfire) I cant even google this binary. I cant even tell if somebody is developing on this binary.
I just don't understand how nobody brought up this issue in any manner. Nobody asked whether the binary code is available in the market, needs to be downloaded from the web and flashed on the phone, etc. In worst case scenario, if su binary is discontinued, then just say "It is no longer supported. Forget about rooting from now on."
I have T-Mobile GS4 (SGH-M919) running Android 4.2 baseband UVUAMDL, i rooted the phone using MotoChopper that gave me Superuser app by CWM.
If you can be ANY help, please reply with some kind of answer that somebody can actually understand. If you have no clue about a single word i just posted, there you go. There is no answer to this "su binary" issue, so forget about rooting and what not. Save your soul from googling 5 hours a day here and web, looking for answers that no one ever asked.
You're very welcome.
Superuser update
Cowls192,
There are a couple of ways to update SU ... I can share at least two ways.
1) If you have experience using Terminal and can get a hold of the updated SU binary, then you can simply copy it to
the appropriate place. I forget whether the location of the original SU binary is under the /sys or /system folder.
2) I'm quoting from DroidXForums here so take it for what it's worth ..
"The new superuser : su v2.3-ef can also be downloaded from the Google market."
I hope that this small bit of information shows you that the answer CAN be found with patience.
Lacking patience ... this IS a great place to find help!
If you found this to be of help, please condiser clicking the THANKS button.
Solidified
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
cowls192 said:
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
Click to expand...
Click to collapse
Hi. Im a noob and I am trying to update the su binary. I have a galaxy tab s. I just recently did the super su root but I cant. It installed correctly but the binary won't update. I've searched the Web but no clear answers. I've checked if the root is installed correctly and its not. I don't know where to look for any help is greatly appreciated.
Hello.
Same situation here...
Can't update bynary in SM-T700 - 5.0.2 LP...
me too...
me three.....I can,t update....
I used kingroot app, then superSU-ME, and superSU told me to update the su binary.(Another superuser app told me that my binary still remained "kinguser_su(348)")
Same here, from a nexus 6p
I have a Nexus 6p which I thought was already rooted, but when I used the root checker, it says my phone isn't properly rooted. Also, when I try running Super User it keeps saying that I'm missing the su binary or that it needs to be updated. I have no idea what the next step is now. Can someone help me figure out what I need to do?
Dg60069 said:
Hi. Im a noob and I am trying to update the su binary. I have a galaxy tab s. I just recently did the super su root but I cant. It installed correctly but the binary won't update. I've searched the Web but no clear answers. I've checked if the root is installed correctly and its not. I don't know where to look for any help is greatly appreciated.
Click to expand...
Click to collapse
idioleat said:
me three.....I can,t update....
I used kingroot app, then superSU-ME, and superSU told me to update the su binary.(Another superuser app told me that my binary still remained "kinguser_su(348)")
Click to expand...
Click to collapse
Those still having trouble ensure your device is rooted and also if su still can't install binary try another version some versions have trouble installing binary.
cowls192 said:
Couple things to straighten up here.
Okay, the whole problem with "su binary update failed" is because my phone was NOT rooted. End of that story.
After my phone was rooted successfully, it didn't ask me to install su binary, being out of date, nothing like that.
At this point, i will just assume that whenever app is released/updated, let it be Superuser SuperSU or else, the app itself includes su binary already.
It is still difficult to find answers and solutions for folks who are new to smartphone or Android world...and i mean VERY new, like he/she just got an Android phone for the first time in life today!! A lot of unnecessary questions and replies can be reduced if SOMEBODY creates FAQ or intro to rooting and flashing tips.
Finally, i have T-Mobile GS4 (SGH-M919), and although i read a post saying that su binary is not compatible with SuperSU at this point, (see, it's even harder to search for posts i read recently) after successfully rooting my phone, SuperSU DID NOT ask or even say anything about "su binary" whatsoever, so that made me smile today.
Thanks for those who took few seconds to read my posts, and i really hope somebody is being helped after reading these messages.
Click to expand...
Click to collapse
POST FOR EVERYONE WHO HAS TROUBLE FINDING/UPDATING THE BINARIES:
1. The SuperSU app version number corresponds to the su binary version. To check the version of the su binary go to Settings --> Apps --> SuperSU and look at the version number.
2. SuperSU app will push a notification if the binary needs to be updated.
3. You will also see a popup window once you open the SuperSU app in case there is a new version
4. To be sure you have the latest version you can follow one of the links below which will have the download for the latest recovery-installable zip that will root and install the SU app along with the latest binaries:
Stable (recommended): http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
5. There is a thread dedicated to binary update problems. You will have more luck there: http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365
6. Also remember to visit the official post for any future updates and extra info: http://forum.xda-developers.com/showthread.php?t=1538053
NOTE: In most cases you have to update the SU app to get the latest binary version.
janekmuric said:
POST FOR EVERYONE WHO HAS TROUBLE FINDING/UPDATING THE BINARIES:
...
will have the download for the latest recovery-installable zip that will root and install the SU app along with the latest binaries:
Stable (recommended): http://download.chainfire.eu/supersu-stable
Beta: http://download.chainfire.eu/supersu-beta
Latest: http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
It is exactly how I'm doing and every time get: "binary update unsuccessful"
Sent from my E2303 using Tapatalk
pawwaap said:
It is exactly how I'm doing and every time get: "binary update unsuccessful"
Sent from my E2303 using Tapatalk
Click to expand...
Click to collapse
Then you didn't root properly. Try different root methods or re-root your phone.
Related
So I rooted my phone using the SuperOneClick method, and got my superuser app and everything but when I try to run Barnacle Wifi Tether, Superuser never prompts, and Barnacle complains that I haven't rooted my phone.
So I go into the preferences of Superuser snooping around to see whats wrong, and I come across (under the general tab) Su binary vnull. I tap it to check for updates and it goes like this:
Working...
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = legacy
So it says at the top new version of su binary found.
Update now?
I tap update and this happens:
Working...
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... fail!
I can keep tapping try again over and over but it never really gets past that step sooo, I'm stuck. I was hoping someone could help me out? If you can't, thanks for reading. If you can, I'd appreciate it very much! I live out in the middle of nowhere with no such thing as internet (other than what I can hardwire tether) and all I want to do is connect my Wii to the wifi on my phone.
I have the same problem. A work around is this...
You can download the appropriate su binary here...
androidsu.com/superuser
Then, flash it through recovery. It should update the binary no problem. However, it does not correct the problem. At least you'll have an updated binary.
If someone else knows what the problem is, that would be helpful in easier updates in the future.
Thanks for the quick reply! Though, can you explain what you mean by "flash it through recovery"? That's the only terms I'm not familiar with regarding this. Thanks again!
You need to use Clockwork Mod Recovery.
1) Install Rom Manger from the market.
2) Open up Rom Manger and install Clockwork Mod Recovery. Choose the appropriate phone model.
3) Reboot into recovery from Rom Manager.
4) Flash update using zip.
5) Select appropriate zip.
6) Reboot
How do I install Clockwork Mod Recovery? Where? Sorry if I'm asking to many questions.
taplamp said:
So I rooted my phone using the SuperOneClick method, and got my superuser app and everything but when I try to run Barnacle Wifi Tether, Superuser never prompts, and Barnacle complains that I haven't rooted my phone.
So I go into the preferences of Superuser snooping around to see whats wrong, and I come across (under the general tab) Su binary vnull. I tap it to check for updates and it goes like this:
Working...
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = legacy
So it says at the top new version of su binary found.
Update now?
I tap update and this happens:
Working...
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... fail!
I can keep tapping try again over and over but it never really gets past that step sooo, I'm stuck. I was hoping someone could help me out? If you can't, thanks for reading. If you can, I'd appreciate it very much! I live out in the middle of nowhere with no such thing as internet (other than what I can hardwire tether) and all I want to do is connect my Wii to the wifi on my phone.
Click to expand...
Click to collapse
i dunno how u have rooted your phone... but u shud do it this way. i have galaxy y and i did it this way and this might help!!!!
go to this site
http://forum.xda-developers.com/showpost.php?p=18811169&postcount=16
Are you reading?
kingsnakelegend said:
You need to use Clockwork Mod Recovery.
1) Install Rom Manger from the market.
2) Open up Rom Manger and install Clockwork Mod Recovery. Choose the appropriate phone model.
3) Reboot into recovery from Rom Manager.
4) Flash update using zip.
5) Select appropriate zip.
6) Reboot
Click to expand...
Click to collapse
Yes, I'm reading.
I'm no stranger to modding phones. Just android OS'. No need for the big red lettering.
I downloaded ROM Manager. There is no option within this app to download and install this Clockwork Recovery Mod.
There is a button that says, "Flash ClockworkMod Recovery" and underneath it says, "You must have the ClockworkMod Recovery installled to flash and restore ROMS"
But being that I've explained that I'm unfamiliar with the terminology, "Flash ClockworkMod Recovery" Doesn't sound the same as installing. Is that the button I should tap?
has anyone found a easy solution for this? i rooted my X10i on 2.3.3 stock and could update binary fine before now i've flashed DooMLoRD's v06 1113MHz overclocked kernel and flashed the RevolutionHD ROM im having problems updating my binary it says
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = 2.3.2-efgh
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... fail!
Failed to find currently installed su binary. update cannot continue
im guessing that means i have not got any su binary atall?
---------- Post added at 02:19 AM ---------- Previous post was at 01:48 AM ----------
also i can't seem to download the latest superuser app from the market, it says your device is not compatible
I'm having the same message as TC. I'm on a SGH-T679 right now which doesn't have a version of CWM available for it yet (at least its not listed in ROM Manager). Any other way to install it? Can I just use ADB to push it to it?
Sorry buddy
taplamp said:
Yes, I'm reading.
I'm no stranger to modding phones. Just android OS'. No need for the big red lettering.
I downloaded ROM Manager. There is no option within this app to download and install this Clockwork Recovery Mod.
There is a button that says, "Flash ClockworkMod Recovery" and underneath it says, "You must have the ClockworkMod Recovery installled to flash and restore ROMS"
But being that I've explained that I'm unfamiliar with the terminology, "Flash ClockworkMod Recovery" Doesn't sound the same as installing. Is that the button I should tap?
Click to expand...
Click to collapse
I am with you buddy. That is one thing I have noticed with people familiar with programming, they seem to be oblivious when providing steps because many of their steps include further steps they simply view as inherent and fail to explain in depth. His steps do not clearly define what needs to be done to those not familiar. Of course they tend to get mad more often and say "If you don't understand you should't be messing with it anyways!" or something, unfortunately. I have been looking for a few hours hoping to find someone who not only knows how to do this, but is also familiar with technical writing, which is hard to do on this site surprisingly haha.
taplamp said:
Yes, I'm reading.
I'm no stranger to modding phones. Just android OS'. No need for the big red lettering.
I downloaded ROM Manager. There is no option within this app to download and install this Clockwork Recovery Mod.
There is a button that says, "Flash ClockworkMod Recovery" and underneath it says, "You must have the ClockworkMod Recovery installled to flash and restore ROMS"
But being that I've explained that I'm unfamiliar with the terminology, "Flash ClockworkMod Recovery" Doesn't sound the same as installing. Is that the button I should tap?
Click to expand...
Click to collapse
Although I imagine you may have figured this out by now -- yes, in this case (and I find it hard to believe that anyone who's familiar with modding phones wouldn't infer this) you're being expected to understand that "Flash ClockworkMod Recovery" would install it to your phone. Press that button and then follow the rest of the directions that several people have already given you in plain english.
Incoherent said:
I am with you buddy. That is one thing I have noticed with people familiar with programming, they seem to be oblivious when providing steps because many of their steps include further steps they simply view as inherent and fail to explain in depth. His steps do not clearly define what needs to be done to those not familiar. Of course they tend to get mad more often and say "If you don't understand you should't be messing with it anyways!" or something, unfortunately. I have been looking for a few hours hoping to find someone who not only knows how to do this, but is also familiar with technical writing, which is hard to do on this site surprisingly haha.
Click to expand...
Click to collapse
This question has nothing to do with "programming" knowledge or talking in obtuse technical terminology -- it's just the basic assumption that if someone has found the XDA-Developers forum and has rooted their phone, they typically don't have to be told that flashing something to their phone installs it.
Same issue
I have the exact same issue as the Taplamp.
Here are the steps I have tried with the same issue -
1. When running SU Bionary update, it fails @ Md5sum.
2. SU Update Fixer Fails @ Root access.
3. Installed Clockworkmod failed to install/run because "An error occurred while attempting to run privileged commands"
4. recovery will boot up fine, however, when trying to load Update.zip, fails and aborts install (without clockworkmod installed) - figures!
5. Resetting catch and wiping memory and reactivating the phone will allow it to work for a few seconds then starts failing.
6. I went to the source and got the updated information on androidsu.com/superuser but when trying to flash it fails.
I may aim to flash my phone via RSD Lite but if anyone has any ideas, I am open to try.
------------------------------------------------------------------------
I do have two rooted droid's, both the same phone. Would it be possible to copy/paste the files on the working one over the one failing?
I would try this, however I am at work.
Does not work with CWM flashing...
I have the same problem: "md5sum...fail".
I tried with "su update fixer" and also with "CWM". No success.
Can anyone help us please?
I figured it out ! WORKS 100%
What you have to do:
1. Download & install BusyBox.
2. Open BusyBox and inside the program make the update (it will show you the update, don't worry)
3. After the update is finished, try to update superuser md5sum.
4. ENJOY !!! This is how simple it worked for me!
Hit a thanks for me...
track13 - That method worked for me, so thankyou!
For the record the steps I completed were:
(1) Install Busybox from Google Play (https://play.google.com/store/apps/details?id=stericson.busybox&feature=search_result)
(2) Re-ran the Superuser (SU) update
That's it!
track13 said:
I have the same problem: "md5sum...fail".
I tried with "su update fixer" and also with "CWM". No success.
Can anyone help us please?
I figured it out ! WORKS 100%
What you have to do:
1. Download & install BusyBox.
2. Open BusyBox and inside the program make the update (it will show you the update, don't worry)
3. After the update is finished, try to update superuser md5sum.
4. ENJOY !!! This is how simple it worked for me!
Hit a thanks for me...
Click to expand...
Click to collapse
I do appreciate the effort that you've put forth in finding a solution and I can see that you've helped a couple of other users as well! Awesome.
Unfortunately though, by the time I came back to the xda-developers forums I've been trying to figure out how to remove all traces of root and removing the Superuser.apk because the only reason I originally wanted to root was to freely use wireless tethering apps, but since FoxFi's release, I've lost the need for it.
So now I'm trying to get rid of Superuser because I've got an upgrade in a few months and I'd like to trade this device in towards credit, anyone got experience with this?
Thanks again, track13.
it worked for me
tnx it worked for me:
[1]:
1) Install Rom Manger from the market.
2) Open up Rom Manger and install Clockwork Mod Recovery. Choose the appropriate phone model.
3) Reboot into recovery from Rom Manager.
4) Flash update using zip.
5) Select appropriate zip.
6) Reboot
[2]:
1) Install Busybox from Google Play (https://play.google.com/store/apps/d...=search_result)
2) Re-ran the Superuser (SU) update
taplamp said:
So I rooted my phone using the SuperOneClick method, and got my superuser app and everything but when I try to run Barnacle Wifi Tether, Superuser never prompts, and Barnacle complains that I haven't rooted my phone.
So I go into the preferences of Superuser snooping around to see whats wrong, and I come across (under the general tab) Su binary vnull. I tap it to check for updates and it goes like this:
Working...
Downloading manifest... okay!
Parsing manifest... okay!
Latest version = 3.0.3
Checking installed version = legacy
So it says at the top new version of su binary found.
Update now?
I tap update and this happens:
Working...
Fixing database... okay!
Checking for busybox... okay!
Checking current install path... /system/bin/su
Downloading new binary... okay!
Checking md5sum... fail!
I can keep tapping try again over and over but it never really gets past that step sooo, I'm stuck. I was hoping someone could help me out? If you can't, thanks for reading. If you can, I'd appreciate it very much! I live out in the middle of nowhere with no such thing as internet (other than what I can hardwire tether) and all I want to do is connect my Wii to the wifi on my phone.
Click to expand...
Click to collapse
Ok so I know this thread has been dead for a while but I just wanted you and anyone else out there in the realm of this question and goal to know barnacle or any other tether like it that creates an adhoc network to share it's connection can't be used on a wii, wii is incapable of joining an adhoc wifi network, so you'll need to find another wifi solution anyhow.
Thank boss ama give that a try I got no pc and phone is galaxy j100
I've read the dedicated thread on rooting the TF700t with DebugfsRoot_v1.9 (http://forum.xda-developers.com/showthread.php?t=1706588&page=48).
I did successfully root a TF700t with 9_4_5_22.
Now I tried the same method after upgrading another TF700t from stock to 9_4_5_26.
Everything works fine during rooting (I've tried both manual and automated DebugfsRoot 1.9) with the following exceptions:
1. during the 3rd stage of rooting, I get
/system/bin/sh: /system/xbin/su: not executable: magic 7F45
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
I tried both under XP and 7/32 on the same device, no errors but root does not seem to be active. Between rooting attempts, I restored stock ROM.
Other details:
Asus USB drivers installed (off Asus website)
Asus synch is disabled and prevented from launching.
Security/Unknown sources is checked.
Developer options / USB debugging is ON/checked.
What do you think goes wrong?
Any help is appreciated. Thx
the same..
I have nearly the same problem...
I have updated my rooted .21 to .26, then unlocked it and as it seems have lost root. I dont really know if it happened afted updating or afted unlocking...
None of my R-applications can get root, and so on...
I've tried to use the same method i used to get root on .21 and got this:
Step 2 - Rooting...
debugfs 1.42 (29-Nov-2011)
debugfs: rm: File not found by ext2_lookup while trying to resolve filename
debugfs:
debugfs: debugfs: Allocated inode: 1469
debugfs: debugfs: debugfs: debugfs:
Rebooting...
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
And still no root...
What am i doing wrong? What to do next?
Thanks!
Is it a superuser problem?
EnginesRun said:
2.
Superuser access does not seem to be active after rooting. I did uninstall and re-install Superuser with no superuser access success.
Any help is appreciated. Thx
Click to expand...
Click to collapse
Can't help yet but I am having a similar problem with SU; its presence suggest I have root but it denies everyone else SU permissions...
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
alienedd said:
After rooting, run SuperUser explicitly from the applications menu. Then try your apps that require root access. I noticed that I had the issue of running the DebugFS root batch and then later was not able to properly run Adaway. Ran SuperUser, then everything went smooth.
I think someone already mentioned this in another thread.
Click to expand...
Click to collapse
nope. doesnt help in my case..
---------- Post added at 10:17 AM ---------- Previous post was at 09:37 AM ----------
ok, i've solved my problem.
the idea mentioned by alienedd helped me to see that i could have a working root but faulty superuser app.
so i started with installing it from market.
then i ran DebugfsRoot_v1.9.
till it got to this point:
Testing superuser...
uid=0(root) gid=0(root) groups=1003(graphics),1004(input),1007(log),1009(m ount),1011(adb),
1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),30 03(inet),3006(net_bw_stats)
uid and gid should both be 0.
Are they? (y/n):
Click to expand...
Click to collapse
then i have cleared all the data held by superuser app through settings\apps, stopped it and uninstalled.
after that i continued with the script and it installed me superuser app again.
after installing i've launched it and then ckecked my root-needed apps. they are ok now.
Ahhh, yeah. Read about that in the DebugFS thread that sometimes one needs to uninstall superuser then reinstall for it to run properly. Didn't think about that. Glad that its all working now for yas.
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
henbone11 said:
I have tried all of this with 4 different packages (3 of the automated root from here and 1 from a link in the [RESOURCES] thread in the dev forum. every time, each package says that I have root, but when I check I do now. I followed what masseselev said and it failed as well. I have spent the better part of 5 hours trying to root. I guess I should say that I just got my infinity last night...and like a crackhead applied .26 ota without thinking about it. but I have read where the automated works fine with .26. I am pulling my hair out trying to figure out why I cant get root on this thing. the packages always say that they were successful and that I have root, but I do not. no apps can gain root. terminal emulator still shows $ after trying to enter "su". I have tried several different root checkers and they all say I do not have root. any other ideas? I should also say that I have not unlocked the bootloader.
Click to expand...
Click to collapse
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
alienedd said:
What exactly are you doing as its kind of hard to determine what has gone wrong?
DebugFS works with .26 OTA and you don't need an unlocked bootloader for it to work (though having root might cause problems for getting OTAs and the unlocker to work).
Click to expand...
Click to collapse
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
henbone11 said:
just trying to run the debugFS automated tool. it runs fine, and gives all indications that it works successfully. but I still dont have root. its driving me crazy. I have run 2.0, 2.1 and 2.2 packages and all said I was rooted...but I dont think I am. I have installed and uninstalled superuser and rebooted numerous times. I went ahead and unlocked the bootloader and it still wont work. I can open a command prompt from within the package folders (2.0, 2.1 and 2.2) and run adb shell, then su and it shows #. but if I do it from terminal on the infinity it shows $ when i do su. sorry if im vague, im just brain fried at this point and dont know what else to do.
Click to expand...
Click to collapse
Yeah, I understand. Um, I know I've repeated this several other times but I don't see it in your list of things you've done. Were you able to open up the superuser application? It seems that if it opens, you have root, and in some cases might not work until it is opened. It's both fortunate and unfortunate that I did not encounter many problems while rooting so my experience with possible errors isn't that expansive. However, you've run the package(s) completely so it's not a driver issue and you can adb and see su access. It just seems like the tablet isn't recognizing that it does have it.
yeah, I ran superuser immediately after rooting. then rebooted each time. http://forum.xda-developers.com/showpost.php?p=29951628&postcount=494
lol thats everything that I have tried. kinda sucks, but im sure someone will figure it out at some point.
weird thing is, if I run a command prompt from within the package folders I see that its rooted. if I run terminal on the device it says permission denied and prompt is still $. just odd.
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
alienedd said:
I'm sure that sparky can give you help in the main thread as he has a whole lot more knowledge about the possible failings. Also, read over some of the other threads here as there seem to be quite a few people with errors that I don't even understand why they are happening. Maybe a something like simply the drivers? http://forum.xda-developers.com/showpost.php?p=29974269&postcount=9
Other then that, I'm at a loss bud. Do mention the fruits of your research though as I'm sure it would definitely be helpful to others.
Click to expand...
Click to collapse
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
henbone11 said:
yeah, we have been trying to figure it out...no joy. I have seen quite a few people with the same issue. hopefully someone can sort out why its happening soon. even if I cant root, at least knowing why would somewhat appease me.
Click to expand...
Click to collapse
Perhaps this then?
d14b0ll0s said:
Perhaps this then?
Click to expand...
Click to collapse
Ok, I followed this http://forum.xda-developers.com/showpost.php?p=28519641&postcount=11 and was successful in rooting mine and my gf's infinity's.
one thing though. after manually rooting, after the final reboot, go into the Superuser app. DO NOT UPDATE IT FROM WITHIN THE APP. for some reason, updating from within Superuser borks the app. at least it did for mine and my gf's.
optional:
close Superuser. go to the play store and download busybox installer (needed to run titanium backup), root checker (there are a ton, just pick one of the top ones), adaway, ota rootkeeper and titanium backup. doesnt matter what order. I would run busybox installer first though once you have everything installed. after busybox installs, you can run root checker, adaway or titanium to check root. I say after you install busybox because some apps do require busybox to be installed before they consider you rooted. if you get the superuser prompt to allow/deny, everything is working fine. once you know that you have root and everything is working ok, run ota rootkeeper.
my only question at this point is regarding OTA updates. to my understanding, simply rooting will allow you to continue to receive OTA updates, but unlocking the bootloader will prevent you from getting OTA updates...is this correct?
i am hopeing someone can help me out here.
s4 mk2 build#
it seems i cannot update binaries on supersu that is stopping me from rooting my phone
Saferoot seemed like a no brainer just hit a couple keys and command prompts do everything so
I tried the saferoot way which i think half worked. the issue i am having is it seems i am stuck on trying to update supersu binaries. nomatter what i try it wont update.
i have tried thru the play store and downloading to my sd card. although on my card i must admit that i just didn't know which file to load being new to this.
in case those pictures dont show up
i downloaded root checker and it says
Check Command: ls-l ?system?bin?su:
Result: rwsr-sr-x root root 46596 2014-02-19 15:22su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can gain root access!
this leads me to believe i am pretty damn close right?
anyway could you give me a hint as to the way you rooted your phone?
or to someone else that doesn't mind noob questions like this.
Thank you for reading my breakdown and responding if you can.
Chris
Hi
cfh1030 said:
i am hopeing someone can help me out here.
s4 mk2 build#
it seems i cannot update binaries on supersu that is stopping me from rooting my phone
Saferoot seemed like a no brainer just hit a couple keys and command prompts do everything so
I tried the saferoot way which i think half worked. the issue i am having is it seems i am stuck on trying to update supersu binaries. nomatter what i try it wont update.
i have tried thru the play store and downloading to my sd card. although on my card i must admit that i just didn't know which file to load being new to this.
in case those pictures dont show up
i downloaded root checker and it says
Check Command: ls-l ?system?bin?su:
Result: rwsr-sr-x root root 46596 2014-02-19 15:22su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can gain root access!
this leads me to believe i am pretty damn close right?
anyway could you give me a hint as to the way you rooted your phone?
or to someone else that doesn't mind noob questions like this.
Thank you for reading my breakdown and responding if you can.
Chris
Click to expand...
Click to collapse
●●You have Knox Avoid Warranty?
OK I have run the pie exploit about 100 times every time I get the correct output but when I use root checker it says I don't have root I try to install super su and it says there are no binaries installed what am I missing my device shows up I put the update package in my sdk folder advice pushes the files I reverted back to 19.5.3 I get the exact same message that is expected when everyone else runs pie please help I have a Verizon Droid mini do I need to disable fire walls or avg
ojodetigre said:
OK I have run the pie exploit about 100 times every time I get the correct output but when I use root checker it says I don't have root I try to install super su and it says there are no binaries installed what am I missing my device shows up I put the update package in my sdk folder advice pushes the files I reverted back to 19.5.3 I get the exact same message that is expected when everyone else runs pie please help I have a Verizon Droid mini do I need to disable fire walls or avg
Click to expand...
Click to collapse
I got the same error messages. Get Root Check, and ignore the errors, and once it's sent, see if that works. It doesn't allow you to update the binaries though, until you do the full root with the WPnomo described in the Pie thread
Elaborate
livinitwarrior said:
I got the same error messages. Get Root Check, and ignore the errors, and once it's sent, see if that works. It doesn't allow you to update the binaries though, until you do the full root with the WPnomo described in the Pie thread
Click to expand...
Click to collapse
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
ojodetigre said:
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
Click to expand...
Click to collapse
You need to make sure everything like your firewall, avg, security is all turned off or it won't work.
Rooted Droid Ultra
ojodetigre said:
So I got root checker it says I am not rooted so your telling me that I should just ignore everything and run the full root process because everyone else says that root checker should say I'm rooted is there any other programs I need besides sdk I read somewhere that I need Java setup correctly to execute scripts and also I read that I may have to create a junk file on my phone that will allow the scripts to be pushed to I'm so lost I am about to give up someone please help me out I'm new member so I can't post in development
Click to expand...
Click to collapse
sorry, I never got a notification from this. No, root checker SHOULD tell you if you have root. Are you running each of the 4 commands separately?
livinitwarrior said:
sorry, I never got a notification from this. No, root checker SHOULD tell you if you have root. Are you running each of the 4 commands separately?
Click to expand...
Click to collapse
I plug my phone in, cd to the path of my sdk, adb devices to make sure it's recognized then run the four commands separately and phone does nothing it doesn't reboot just stays the same run root checker and it says I'm not rooted the guy before you says to turn avg and firewalls off I'm going to try that when I get home
ojodetigre said:
I plug my phone in, cd to the path of my sdk, adb devices to make sure it's recognized then run the four commands separately and phone does nothing it doesn't reboot just stays the same run root checker and it says I'm not rooted the guy before you says to turn avg and firewalls off I'm going to try that when I get home
Click to expand...
Click to collapse
Reboot? It shouldn't reboot. The phone should technically do nothing until you do root checker. The way this root works, it's tethered, and gets wiped once you reboot unless you do the next steps of using wpnomo
Sent from my XT1080 using XDA Premium 4 mobile app
Just asking a little thing. USB debugging enabled?
Rooted Droid Ultra
Pie alone isn't going to give you the root that you are looking for. All Pie does is give you root access to the /system partition.
You need to go here: http://bit.ly/1sxDN9t and disable Write Protection, which will allow you to flash the SU binary that gives full root.
After that is done you need to install Safestrap ((Can be found here: http://bit.ly/1jq4WeO) Our device is the XT1080), reboot into recovery and flash: http://download.chainfire.eu/396/SuperSU/
Now when you boot up you will have permanent root, and root check / SuperSU should show up properly.
Through OTA?
miketoasty said:
Pie alone isn't going to give you the root that you are looking for. All Pie does is give you root access to the /system partition.
Click to expand...
Click to collapse
Will root access survive through an OTA update to 4.4.4?
joshs997 said:
Will root access survive through an OTA update to 4.4.4?
Click to expand...
Click to collapse
Yes after you do all the steps and buy SuperSu pro and enable survival mode to be able to update and keep root
Rooted Droid Ultra
joshs997 said:
Will root access survive through an OTA update to 4.4.4?
Click to expand...
Click to collapse
Root survives but write protection gets disabled. So the root is basically useless.
I've never really had to use adb much before on any of my other devices. It's eating my lunch, and is frustrating because everyone is saying how easy it is. I honestly am having issues simply pushing the pie exploit to my phone. When I do, all correct directories, it gives me the adb info and shortcut stuff, definitions, etc. Any help would be appreciated. Just don't know adb well at all.
Edit: nm. got it.
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
There is a Lollipop update available for the device as of early February, 2016. I have found a way for users to update if the OTA fails (see below). I've also updated the below posts with information regarding the Lollipop update and moved the KitKat notes to another location (link for old notes is below)
Ota - lmy47v1218_2217
For those who are having trouble applying a FOTA on the DuraForce, check /cache/fota/xyz_fotalog_123.dat It's a text file that contains a lot of really good info on what is going on during a FOTA. Including errors. Keep a look out for signature mismatch errors.
I had errors with the following files. Took me a few tries to get the OTA applied as each attempt resulted in one error.
Uninstall Xposed (moar hacks)
/system/usr/keylayout/gpio-keys.kl (disable PTT/Speaker buttons)
/system/etc/permissions/platform.xml (sd card "fix")
If trying to address the issues manually does not work, follow the procedure below.
Download "vanilla" system image from HERE (link)
Extract zip file
Ensure at least 2Gb of storage is available for internal data
adb push mmcblk0p21_KVT49L_0617_0132 /storage/sdcard0/
adb shell
su
dd if=/storage/sdcard0/mmcblk0p21_KVT49L_0617_0132 of=/dev/block/mmcblk0p21
Reboot phone once it completes. It will take awhile and not report anything during the process.
After phone boots, run "adb reboot recovery"
Wipe data / factory reset
Wipe cache
Reboot
Run software update
General Notes - Lolipop
Force Reboot: Pwr + Vol Up + Vol Dn + Back + Home + App Switcher buttons for ~10-30 seconds
Root: Use KingRoot from http://king-root.net/ -- I used the android APK successfully
SD cards bigger than 32Gb still do not work correctly on stock firmware
Known Working Customizations
To be determined
KitKat Notes
All previous notes for KitKat have been moved to a document in box. The notes can be found HERE (link)
Sources / Mirror(s)
The OSS drop is available on Kyocera's developer site: http://www.kyoceramobile.com/support/developers/
Misc file mirror: https://nuskunetworks.box.com/s/p5hwq3hboctl0saze0wkcv3jzfefuw45
Do you trust Kingo?
I'm THRILLED to hear you were able to root and freeze all the AT&T crapware. I can't wait to do the same. But how do you feel about Kingo? I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
kemonine96 said:
Welcome to the Kyocera DuraForce super thread
There isn't much information floating around for the DuraForce and I've created this thread to aggregate information as it's found so we have a single place for useful information, hacks, etc.
I'll keep the thread as up to date as possible and organize any information from future posts into the originals so people can find information easier.
If you're looking for root, look no further than Kingo. I can confirm the Windows version of Kingo is working on the AT&T varient of the DuraForce.
Click to expand...
Click to collapse
tomzweifel said:
How do you feel about Kingo?
Click to expand...
Click to collapse
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
tomzweifel said:
I'm almost leaning more to keeping the bloat, kind of the devil you know, you know?
Click to expand...
Click to collapse
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Components to clean up?
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
kemonine96 said:
I've used it a few times over the last year and can only complain it does a sloppier job compared to SuperSU. Every pre-canned root wants to crap all over /system and none is better than the other so long as you get the su binary in a working state IMHO. I know Kingo is harder to clean up after than SuperSU / others but it's a hell of a lot easier to just use Kingo to root and cleanup after. Stacking root exploits and similar like Kingo is doing is a huge PITA and best left to those specializing in such things.
Fair enough, I was able to replace Kingo with SuperSU pretty easily:
Install SuperSU from Play Store
Run SuperSU and update su binary via "Normal" mode
Authorize SuperSU when Kingo prompts
Allow SuperSU to replace su binary
Freeze/Remove Kingo
Reboot and enjoy SuperSU
Optional: cleanup other Kingo remnants
Click to expand...
Click to collapse
tomzweifel said:
Any chance you can steer me towards the "remnants" that need to be cleaned up and where to find them, just to make sure I get it all? I'm probably going to go though this exact process tonight or tomorrow.
Thanks for the information!
Click to expand...
Click to collapse
Unfortunately I don't have notes on what Kingo leaves around on /system... Some searching online or poking about /system should yield results.
New OTA Update
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
tomzweifel said:
I just got notified of an available OTA update but I can't find a changelog or any info on it yet. I'll be sure to post it if I find it.
Click to expand...
Click to collapse
Please do. I haven't gotten any notifications yet and I'm kinda curious what the OTA will contain.
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Dkesler76 said:
http://www.att.com/esupport/article.jsp?sid=KB426870&cv=820
Software update includes
Kyocera Remote Lock
Miscellaneous improvements, fixes, and security updates
Click to expand...
Click to collapse
Thanks for the heads up. Too bad it's not L.
kemonine96 said:
Thanks for the heads up. Too bad it's not L.
Click to expand...
Click to collapse
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to free up some time this weekend and I'm going to be pulling the OTA and seeing what I can do for re-packing it for those of us who are rooted and/or de-bloated.
Will post back with more info after I've had some time to poke at the OTA some.
Edit 1: Looks like this has patches for system and boot. /cache/delata looks like the directory where everything was downloaded. Hopefully binwalk and some other tools will yield useful information on what's contained within.
Edit 2: Looks like I was able to install the OTA despite being rooted. I'm waiting for 1st boot to verify root persisted and I'm also working on mirroring a number of partitions that can be used to "go back" to stock as well as images for updated partitions post-OTA.
Dkesler76 said:
np yeah i wished it was to lol... seems that my phone wont take the ota i did delete the bloatware....probably why it wont update u know how to force the ota or do u know where i can get the apks to reinstall them to update it... ty dan
Click to expand...
Click to collapse
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Good news everybody! The ATT OTA doesn't remove root and can be installed as-is provided you've not de-bloated the ROM or installed Xposed. If you've de-bloated (see below) you'll need to restore the missing bloatware and if you've installed Xposed, you'll need to uninstall it prior to applying the OTA.
In one of the early OP's there's a link to the "misc file mirror" that contains partition images for boot and system partitions. These are from an ATT device and can be used to restore back to a state that'll allow the OTA to apply.
Happy hacking and OTAing everyone.
kemonine96 said:
I managed to get a stock boot and system partition uploaded today that you should be able to use to restore the de-bloated apps. The image is here
You can use a Linux machine (or other methods) to extract the APKs and put them back or use busybox + dd to restore the contents of the partition (you may need to re-root if writing the partition using dd). There are some good guys on XDA and elsewhere on how to restore a partition image on an Android device.
Edit: The posted file is for an ATT device
Click to expand...
Click to collapse
weird i tried dd and busy box and no go not showing up on device
Dkesler76 said:
weird i tried dd and busy box and no go not showing up on device
Click to expand...
Click to collapse
What isn't showing up?