Busybox and root checker report device not rooted...? Am using root req's apps - Google Pixel Questions & Answers

Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)

kerryh420 said:
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
Click to expand...
Click to collapse
IDK about the root situation, but the way I usually install busybox on the pixel is goto the play store and search busybox and pick the one by meefik. Then open it and change the install location from system/xbin to just system/bin (so remove the x)

kerryh420 said:
Unlocked bootloader. Installed twrp successfully. Flashed majisk successfully yet busybox will not install and root checker reports root not obtained... Huh?
Is this because root checker and busybox look for supersu to be in a certain place and when they can't find it they report no root?
If majisk is essentially root then why does it fail the checks? I am able to install and use apps that require root... What gives? (Sorry for being dumb)
Click to expand...
Click to collapse
This is the best BusyBox installer in my opinion.
From this thread. Works for system or systemless installations.
Flash in TWRP.

Related

Root was succesful, superuser is installed, but I don't have Root access.

I rooted my Motorola Charm with superoneclick 1.7, or atleast I thought I did. superoneclick 1.7 did say the rooting was succesful and I have superuser installed.
But when using Link2SD it says I didn't have root access. So I checked with Root Checker and apparantly Link2SD is correct. This is what Root Checker has to say:
Root Access is not properly configured or was not granted.
Alternate su binary location:
/sbin/suermission denied
SU binary not found in the system delcared PATH
Does anyone know what could be the issue? And if not, then would anyone know what is the safest way to proceed from here? I already have superuser and superoneclick says it is Rooted, I'm not sure what would happen if I were to root it again.
I had the same problem with my Milestone, rooted it using AndRoot. I used Superuser to update the su binaries, but still nothing. Then a simple reboot fixed it
My Milestone2 rooted successfully by SuperOneClick 1.3 ,
you can use the 1.3 version to root
milest0ne2 said:
I had the same problem with my Milestone, rooted it using AndRoot. I used Superuser to update the su binaries, but still nothing. Then a simple reboot fixed it
Click to expand...
Click to collapse
Edit: after a second reset it worked! Thank you very much!

Root checker says I have root but apps can't gain root access.

Hello I have an unusual problem. I am modifying the ROM for my Rockchip device (rk3066). I want the firmware image to flash already rooted. I have installed busy box, su binary, and Superuser.apk. When I flash the ROM then use Rootchecker, it says I have root access. However, when I use an app that requires root it cannot gain root access. Can anyone explain to me what is going wrong?
Please be very basic in any explanation as I am a super noob trying to learn.
Thanks in advance for any help given. It will be very appreciated.
Melikey said:
Hello I have an unusual problem. I am modifying the ROM for my Rockchip device (rk3066). I want the firmware image to flash already rooted. I have installed busy box, su binary, and Superuser.apk. When I flash the ROM then use Rootchecker, it says I have root access. However, when I use an app that requires root it cannot gain root access. Can anyone explain to me what is going wrong?
Please be very basic in any explanation as I am a super noob trying to learn.
Thanks in advance for any help given. It will be very appreciated.
Click to expand...
Click to collapse
There might be something wrong with the superuser app itself. Try using SuperSU.
http://forum.xda-developers.com/showthread.php?t=1538053
Does it work?
Basically you need to tick "prompt", if you had ticked "deny for all" , superuser will not prompt you for answer when an app needs root, so have it on "prompt" in super user settings, If superuser or SU icon is in apps drawer , open it and check its settings menu.
How to get Root Access?
a) Update SU Binaries, reboot
b) Check Development Option for Root Access settings or Performance settings for Superuser Settings
c) Flash Super Su Zip in Recovery
Problems that may arise in the future : Read How To SU
Check this out! Links to useful Guides and " Banned " Documentaries ​
install supersu
So I tried updating the su binary from the superuser app. It says it installed OK but then says it can't gain root access.
I also tried using Supersu app. It says that there is no su binary installed. But, it definitely is there.
I also tried simple root checker. It verified that busy box is installed.
If you have a recovery installed unroot and reflash the binary n app
Sent from my WT19i using xda app-developers app
I appreciate all the input, but I think this is going off point. I have no trouble routing my tablet with the told that are out there. I can't build it into a complete ROM. I am trying to build a custom ROM
with the root built in.
Sent from my XT912 using Tapatalk
Root not routing / tools not told

just rooted, got a question with superuser app

so i have used kingo root (not kingroot) app to root my phone, it all went well, but, i keep hearing supersu app is a must, is there any working method for replacing kingoroot superuser with supersu? will i be fine with kingo superuser? i heard its very tricky to do this and you need to use the terminal app, but if supersu is a must have ill do it, looking forward to any working methods, thanks!
mladen190 said:
so i have used kingo root (not kingroot) app to root my phone, it all went well, but, i keep hearing supersu app is a must, is there any working method for replacing kingoroot superuser with supersu? will i be fine with kingo superuser? i heard its very tricky to do this and you need to use the terminal app, but if supersu is a must have ill do it, looking forward to any working methods, thanks!
Click to expand...
Click to collapse
It doesn't sound like your root method was successful. If you were successful it looks like it would install their version of SU for you. http://www.kingoapp.com/faq.htm I'm not a fan of "one click root" (No one here is) I would suggest that you learn ADB to get proper root access. I would be concerned that you have now gained root access (which makes your device vulnerable) and are having to install their version of SU. That seems way too risky to me.

Root Kindle Fire HD 10

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

Question Messed up my root.. How to recover

So I have root via root checker and root beer is telling me I have root. All my apps that required root are working, but in magisk I can't access the modules.
No new apps are being promoted for root.
When I try to adb flash , it says there's a write error.
Latest everything on a p7p
What do you mean you can't access modules? Are the modules enabled or disabled in magisk? For new apps wanting root, when you look at the permissions in magisk, is root granted/enabled for those apps?
What write error? You need to be more specific with regards to your issues

Categories

Resources