Hi All,
I have a Nexus 7 2013 and I wish to update it. However when the OTA update is run a error message appears. I rooted the tablet several months ago and have since then un-rooted it. When I run a root checker Superuser Binary Files are still installed alongside BusyBox. Could this be the reason as to why the OTA is failing if so, how do I completely remove the files?
Thanks
which SU , manager you used?
maybe you uninstalled the wrong way.
if bussybox is installed, open the remove binary and uninstall.
if not working, install the SU manager you used, go to setting of it and " remove root/binaries"
Related
So i tried to install and use galaxy unlocker from play store and when opened it says "cannot find superuser access". So I downloaded superuser from play store, uninstalled GU and reinstalled and same problem. Thought to myself huh? So I installed root checker and it says phone is not rooted. Weird because it is rooted running ICS 4.0.4 Any insight as to why this is showing up like this? Here is a screenshot of the build number and android version...
Before root and update...
Currently as of today....
You are probably using the wrong su.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Sounds like the su binary was installed in the wrong folder or it is an older version. Sometimes its in the /bin folder instead of the /xbin folder. What you need to do is download the ics SU zip files and flash them through CWM
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Boffortes said:
I know there's a dedicated SuperSU thread but being a newbie on this forum I cannot post there.
I have Teclast P78HD tablet (A31 and Android 4.4.2) which I have rooted using Kingo. There is no custom recovery available for this model, AFAIK, so zip option is out of question I think. Kingo installed SuperSU 1.9.1 which does work, but as Play offered an update I accepted it, got 2.0.1. A big mistake.
The system still works, it prompts to grant root access when an app needs it. But I cannot run the SuperSU app anymore, it asks if I want to update. If I select yes after a while it fails and tells to reboot and try again. Which of course gives the same result. Selecting cancel closes the program. Uninstalling the update returns the system back to working 1.9.1. I have tried also Settings / Cleanup / Reinstall and Settings / Cleanup / Switch superuser app but both fail similarily. I also tried to replace the APK in /system/app using ES File Explorer but this method also makes an app to ask for update.
Any ideas how to update SuperSU on this tablet? Maybe I should just forget the problem and use the current one, but it is somewhat old and the changelog lists many, many changes. Plus Play keeps offering an update which is somewhat annoying
Click to expand...
Click to collapse
uninstall supersu and try this one. some people have issues with supersu and have found superuser to work correctly.
Hello Folks,
Forgive me but I searched the forums and could not find any posts dealing with my problem.
I recently rooted my phone, Verizon Samsung Galaxy S4 i545 version 4.4.2, build i545vrufnc5 using Towel Root and used Root checker to verify. Root checker states it is rooted and I am using SuperUser Elite v3.1.3 however the outdated binary notification shows outdated binary (-rwxr-xr-x is in red) and when I tap to update I get the message "downloading manifest...... fail!? When I then hit "try again" I get "unfortunately superuser has stopped" and it closes. I also downloaded SU Updater and ran it, no help. I also have Busy Box and Root Explorer and Titanium Backup installed. su binary shows v1.99:supersu (0). There are no apps showing in su and I get no prompts when adding new apps to allow or deny? I am new at this and really ready to unroot and say the heck with it. I seen several posts about downloading a zip of the file and saving to sd card. Do I need a zip program first and how do I move it to the sd card if that is the case? I've tried uninstalling and reinstalling several times to no avail. Any help would be appreciated.
Thanks,
J-
1) try SuperSU instead
2) do u have custom recovery?
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that kingoroot superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the kingoroot superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Couldn't get it to install says it's arm device tries to install and says it's an arm64 device. Plus has to be flashed in recovery and one hasn't been built yet
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
erono said:
You can't manage Kingoroot su binary using SuperSU.
If you not install SuperSU su binary, SuperSU apk does not working.
Try this method to install SuperSU su binary.
https://forum.xda-developers.com/showpost.php?p=75242414&postcount=99
Click to expand...
Click to collapse
I installed supersu to find out if it was rooted since the root checker said it was not. the binary error was a confirmation that it was in fact rooted and it doesn't matter what superuser is used it will not allow pop up or apps to draw over other apps so when it's rooted with kingoroot it automatically grants root without a confirmation,as long as the kingoroot super user app is not installed and if SuperSU is kept installed default permission has to be set to grant for root to work. I in fact installed the SuperSU binary through an older version of the apk and it installed but still has no control over denying or granting permissions. Thanks for the advice though. I appreciate your willingness to help me
Joker1716 said:
I was able to use Kingoroot for PC to root my Fire HD 10. Updated to the newest Firmware. It would say it was rooted. But, Trying to give permissions and checking with root checker was not successful and said there was no root. I installed SuperSU apk it says the binary is occupied. So I Uninstalled the superuser apk. that was installed by Kingoroot and tried to change the build prop with a root browser text editor and it was successful so apparently it roots but superuser is not working to grant or deny permissions. It automatically grants permissions does not even open up superuser so its kinda dangerous but it is rooted and working. My experience is that superuser must be Uninstalled for root to work. I used twrp manager to backup my recovery img., and boot img. I am going to try to build a recovery for it but I'm not In a hurry plus I'm not sure if it will flash afterwards anyways but if you want root, Kingoroot for pc and Uninstalled the superuser apk it installs and you will have it
Installed magisk manager installed zip direct (recommended) it bricked the fire. And then I adb sideloaded the update and now I'm back in business reasonably easy to do but I do not recommend magisk at this time .
Going to try xposed next
Click to expand...
Click to collapse
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
smam1338 said:
Not trying to insult your intelligence or anything here, but you said newest firmware? Newest Fire firmware? Newest firmware isn't rootable from my understanding.
What firmware were you on when you started the root process?
Also, are you making sure that the Kingoroot "install our extra junk" box isn't checked (not sure that would prevent root success)?
It wouldn't open superuser. superuser should be set to "grant" because of how the Fire works, which it sounds like you are aware of based on your last post. I wouldn't say it's dangerous, per se.
I've followed this guide nearly a dozen times now and I've not run into the issue(s) you're having.
Click to expand...
Click to collapse
Prompt dialog not working in amazon fire devices.
erono said:
Prompt dialog not working in amazon fire devices.
Click to expand...
Click to collapse
Set prompt to grant and fixed.
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
stevenchun said:
yes. mind doesnt pop up supersu granting notification too
my fire hd 10 is on 5.6.1.0
someone told me it's amazon's own security measure
Click to expand...
Click to collapse
One can try this improvement :
SuperSU access workaround for Fire devices
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
This is downloading on my device? Is this going to brick it?
No it's fine. Lots of us received that update the days. I don't see anything new but the performance after the update seems very good.
Sent from my iPhone using Tapatalk
Why would you think it would brick your device?
Did any of the previous updates brick it?
I know the number looks strange - it really should be 5.6.... not 5.3, but that's a mistake on Amazon's end as the "Learn more" link to the User Guide has the correct number.
OP had probably downgraded his tablet to a earlier version of FireOS like I did and installed the play store and nova launcher. I havent used it in a few days but when i got it out today, it said it downloaded and installed 5.3.6.4 on 11/11/18 at 1:16am... which is weird because I had previously used this guide to downgrade to 5.4.0.0 ( https://forum.xda-developers.com/amazon-fire/help/fire-7-2017-7th-gen-downgrade-debloat-t3699937 ) and this "update" seems to have downgraded it even further. But nothing has changed except the version number. Lockscreen ads and all the bloat is still gone and nova is still my launcher, so having the update message appear is very head scratching...
BTW, i did the downgrade to 5.4.0.0 MONTHS ago, and have never seen an update message until today. In fact, if I went into the Device Options and selected System Update, it wouldn't allow me into the setting...it would just kick me back to the home screen. Now it DOES allow me into the setting. Very strange.
5.3.6.4 Update remove root?....
After receiving the 5.3.6.4 update on my HD 10 (11/15/18) -
Lock Screen Ads re-appeared on reboot
Titanium Backup - "no longer finds root" (and in turn, no longer works)
SuperSu - No longer works
Nova Launcher remains in-place oddly enough
I have since theoritically (read on) uninstalled all apps mentioned above and re-rooted via kingoroot and can access a root prompt via ADB (id reflects uid=0(root) gid=0(root) context=u:r:init:s0), however I have been unable to update the binaries for SuperSU despite multiple re-installs and reboots (I'm running the previously working v2.79 btw). Additionally, when I now run a fresh install of Titanium BackUp, all I get is an ongoing "Detecting SU & Busybox..." message onscreeen that leads to no where (I just re-installed BusyBox prior) AND when I run Root Checker, it relects no root as well, despite both kingoroot reflecting root within it's app and my ability to run su via an adb shell on my PC., though please also note that I am unable to run su via a shell/terminal emulater installed on the device ("su: not found").
Thoughts?....thanks in advance for the assist.
Peace.