Database Info

[Q] BusyBox Updater Breaks Root Access

There have been a couple similar posts, but none seem to provide any help, so I apologize for creating a new one if the answer is already out there.
With that said, I recently purchased a new LG Nitro HD and promptly used SuperOneClick to root it. Everything seemed to work fine (on the first try); I rebooted the phone, SU was there, all seemed well. The first thing I tried to use the root access for was to change the LCD Density, and that didn't work - so I tried to update the BusyBox on my phone, using "BusyBox Installer". After I did that, my root access seemed to "break", by which I mean superuser is still installed, and SuperOneClick reports my phone as rooted, but SuperUser cannot authorize apps (or doesn't even try) and attempting to run an app that requires root access simply fails, suggesting that my phone is not rooted. Typically, I would ODIN the SOB and be done with it, but I cannot find any PIT files for the Nitro HD (and I am assuming that would be necessary for me to do anything with ODIN). I've also tried using SuperOneClick to unroot and reroot the device, but now it hangs on step 7 every single time.
Does anyone out there have any suggestions at all?

I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.

Please advise - I am seeing this as well
SolusCado said:
I believe I fixed this issue. "Super Manager" appears to use its own busybox, which is enough to open the system directory in r/w mode and delete the busybox directory from system/xbin. This seems to have restored root access, though a lot of apps are still not working for me. Still, apps are prompting for su access and are showing up in su's list of approved apps - which is more than I could get before.
Click to expand...
Click to collapse
The new MeanROM ICS uses the new SuperUser - however, it breaks root access as you mention. Please advise the corrective action. Send PM if ncessary

[GUIDE]Fix Superuser Permissions!

DISCLAIMER: I am NOT RESPONSIBLE on anything that will happen on your device such as getting bricked or malfunctioning. I only posted this little trick I found out to help others who are also in the same boat. This method MAY or MAY NOT WORK on your device, so proceed at your own risk.
=====================================
Maybe some of you have not seen any Superuser prompt that appears whenever you run apps that needs root (example are Link2SD, Titanium Backup) and etc. Out of frustration last night, I tried to find a way to fix this and I have indeed found it.
But before that here are some of the prerequisites needed:
-Phone/Tablet must be ROOTED
-Has access to system using File Explorers such as Mi(UI) File Explorer, Root Explorer and other explorer that DO NOT prompts Superuser. What I mean here is that you can see /data, /mnt, /etc folders and the like.
..and here are the little steps in fixing it:
1. Download and install BusyBox from Google Play Store.
2. Open BusyBox, select 1.20.2.
3. Click install, and wait for it and it's done.
4. After BusyBox has been installed, download SuperSU from Play Store.
5. Install and let it load.
6. After loading, press YES when asked to update SU Binary.
7. When it's done, press back and try apps that needs root like Titanium Backup.
And there, notification prompt would appear again!
NOTE: UNINSTALL, take note UNINSTALL previous Superuser app through Root Uninstaller. Main reason why that should be uninstalled so that there would be no conflicts with the SU app.
OPTIONAL: you MAY UNINSTALL BusyBox app but I recommend not so to avoid any problems.
I have also applied this method to my tablet that's already rooted but doesn't have Superuser app yet. A simple press of thanks is highly appreciated. :3

hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.

ellynepain said:
hey, I've been trying and trying again but still can't... what should I do? root explorer cant fix my problem.. superSU, superuser fixer, it can't fix my problem too.
Click to expand...
Click to collapse
It's not working for me neither, i can't fix this superuse thing

ZTE V768 (Concord) and V768G (Midnight) Development

Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!

VROOT installs a app "Superuser.apk" not Kingroot
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!

abmx7 said:
Hi, thanks for the info.
When I install VROOT via windows, it installs an app called 'Superuser' which I suppose it is to manage root access permissions for other apps. I see no 'KingRoot' app as you mentioned. I only see this 'Superuser' app and a Chinese app.
Either way, this 'Superuser' app appears to not working properly because I am not getting any prompt to either deny or grant root acess to apps like TitaniumBackup or even Root Checker.
I can get root acess via ADB Shell with the su command, but on the phone the 'Superuser' app from VROOT is not prompting me to allow/deny root access.
Any suggestions?? Thanks!!
Click to expand...
Click to collapse
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810

pflatlyne said:
I was working on getting a custom recovery,but then I ended up getting a Nexus 4 (and then later a nexus 5) and abandoned it. Ill take another look at it. Now that I dont need the phone its less of an issue if I brick it,so I can be a little more agressive.
Try this thread. This is what worked for my V768
http://forum.xda-developers.com/showthread.php?t=2217810
Click to expand...
Click to collapse
anything i can help with getting a recovery working?

ultravioletnanokitty said:
Currently, we only have root access on these devices. I am currently working on a recovery build, and I have plans for CM7 and CM9 builds in the future. Here's how to consistently and easily get root access on the Tracfone V768G and almost certainly V768 (I have a V768G):
Root
The only functional root exploit I have found is via an obscure Chinese program called VROOT. While there is much speculation in other threads as to the nature of this program (and potential for malware), I have had success with it on multiple occasions where no other tool I tried worked. I have seen no evidence that it installs anything other than its strange app market (as an easily-removable user app!) and a superuser program called KingRoot (as a system app, where it should be). While it appears entirely benign and functional, I personally prefer to use superSU. Therefore, the below instructions will include the removal of KingRoot and installation of SuperSU in its place. It is assumed that you have ZTE's preloaded drivers installed and that you have confirmed adb is working.
Unfortunately, VROOT is a Windows-only application, though it works perfectly in a Windows virtual machine (that's how I use it!).
Download VROOT and the newest SuperSU
Install and run VROOT. It might take more than one try to succeed.
Confirm that KingRoot is installed, and uninstall the 100% Chinese app that is also present. At this point, your device is rooted. You can simply keep KingRoot, but I would advise continuing to install superSU.
Extract "common/Superuser.apk" from the downloaded SuperSU zip and install it on the device via adb or the file manager.
Open SuperSU and grant it root permissions when KingRoot prompts you. Swipe over to the settings pane and select "Switch superuser app".
Follow its instructions. After rebooting the device, simply install SuperSU again, open it, update the su binary when prompted, and select "Install SuperSU inte /system" from the settings pane. You're done!
Click to expand...
Click to collapse
Edit: was able to root with kingoroot my bad.

i need a custom recovery for it please

[Resolved] How to Root BLU Life One 2015

Here is how to root the new BLU Life One, there are probably many ways to do it but this was the best way that I could find.
Note that I tried to root with framaroot, towelroot, and iroot and their apps have failed.
Try this of your own free will, I am not responsible for anything happening to your device (it worked for me so it should work for you).
What you will need:
kingoroot, supersu, busybox, root checker, and titanium backup.
First things first,
Go into settings and check the box next to "Unknown sources".
Next open up the internet tab and search for Kingoroot (kingorootapp dot com)
Click the download button for android (not the windows one)
When it finishes downloading, click in the drop down menu and install the apk.
Open the kingo root app, and click root circle.
After the app is finished rooting your device, you can download Root checker in the play store to ensure that your device is indeed rooted.
Now, I personally don't like kingo root, so the next steps are optional.
In the play store download three apps, SuperSU ( i use chainfire), busybox, and titanium backup (i suggest buying the paid version, it is well worth the money).
Next open up SuperSU (KingoUser should ask to grant SuperSU root access, allow it), and install the SU binary. Do not reboot system.
Next open titanium backup, click the middle tab, then scroll down until you see SuperSU. Long press, and then press install to system apps. (you can do this manually by using ES file explorer and copying the SuperSU.apk file [may need to download it from the internet] in to the/system/app folder.
Now restart your device.
When the device boots back up, check and make sure that your device is still rooted by using root checker again.
If it is still rooted, open SuperSU and make sure you dont have to install the binarys again (you shouldnt have to).
Next uninstall the kingo root app (it will not let you uninstall the kingouser app, for this you must use titanium backup)
Now go into your system, applications and then disable kingouser app.
After doing so, check and see if your device is still rooted (it should be)
If it is still rooted, proceed to use titanium backup to uninstall kingouser app.
Lastly install busy box. If you get an error saying "unable to install choose another location" simply click on where it says "/system/xbin" and change it to "system/bin".
And there you should have a freshly rooted device with no kingoroot. Not saying Kingoroot is bad, i just have always used SuperSU
Credits:
To the developers of kingoroot, supersu, busybox, root checker, and titanium backup!

ikpb said:
Here is how to root the new BLU Life One, there are probably many ways to do it but this was the best way that I could find.
Note that I tried to root with framaroot, towelroot, and iroot and their apps have failed.
Try this of your own free will, I am not responsible for anything happening to your device (it worked for me so it should work for you).
What you will need:
kingoroot, supersu, busybox, root checker, and titanium backup.
First things first,
Go into settings and check the box next to "Unknown sources".
Next open up the internet tab and search for Kingoroot (kingorootapp dot com)
Click the download button for android (not the windows one)
When it finishes downloading, click in the drop down menu and install the apk.
Open the kingo root app, and click root circle.
After the app is finished rooting your device, you can download Root checker in the play store to ensure that your device is indeed rooted.
Now, I personally don't like kingo root, so the next steps are optional.
In the play store download three apps, SuperSU ( i use chainfire), busybox, and titanium backup (i suggest buying the paid version, it is well worth the money).
Next open up SuperSU (KingoUser should ask to grant SuperSU root access, allow it), and install the SU binary. Do not reboot system.
Next open titanium backup, click the middle tab, then scroll down until you see SuperSU. Long press, and then press install to system apps. (you can do this manually by using ES file explorer and copying the SuperSU.apk file [may need to download it from the internet] in to the/system/app folder.
Now restart your device.
When the device boots back up, check and make sure that your device is still rooted by using root checker again.
If it is still rooted, open SuperSU and make sure you dont have to install the binarys again (you shouldnt have to).
Next uninstall the kingo root app (it will not let you uninstall the kingouser app, for this you must use titanium backup)
Now go into your system, applications and then disable kingouser app.
After doing so, check and see if your device is still rooted (it should be)
If it is still rooted, proceed to use titanium backup to uninstall kingouser app.
Lastly install busy box. If you get an error saying "unable to install choose another location" simply click on where it says "/system/xbin" and change it to "system/bin".
And there you should have a freshly rooted device with no kingoroot. Not saying Kingoroot is bad, i just have always used SuperSU
Credits:
To the developers of kingoroot, supersu, busybox, root checker, and titanium backup!
Click to expand...
Click to collapse
Hi, thanks for this info, works for me. You should publish this info in the official Blu Life One thread. Thanks again for this.

if someone here has a working blu life one 2015, could you do a rom dump. a bunch of us have soft bricked phones and can't get them working. Blu doesn't have the stock rom available

Hey thanks for this guide! I have one problem I'm hoping you could shed some light on. I've followed your steps and when I try to update the SU binaries it fails every time. The kingroot worked and the kingroot su asked if I wanted SuperSu to have root access and I selected yes. Each time it fails to update it suggest I reboot and try again, but I haven't yet.
Thanks again
Robert

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