Database Info

[Q] Titanium Backup not working after root

Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...

Go into rom manager. Download SU and flash it in clockwork. Should fix ya.
Sent from my ADR6400L using XDA Premium App

ethanwinkley said:
Thunderbolt: after rooting, I can run root manager, flash thunderbolt cwm, boot into cwm and backup/etc. However, when I try to run TiBackup or Screen Resolution, or even terminal/su - access denied, device not rooted.
Anyone else experiencing this?
EDIT: read in another thread (search was not working when I posted this originally) to go to problems in TiBackup, then update busybox...
Click to expand...
Click to collapse
You could search market for busybox and install busybox and install busybox 1.18.3 then try

Just click Problems? in the bottom right of Titanium and let it install busybox for you. I was able to do that and restore all my apps.

Seems like you solved it for you, but for future reference for others, if you're having issues with Titanium only, it could be a the busybox problem, but if other root apps give issues (like Root Explorer can't mount /system as r/w), then the issue is with su or SuperUser not being installed properly.
I had to reboot twice after rooting before SuperUser apk got the notification requests to allow Titanium and RE to get su rights. After that, no problems.
In a nutshell, if you're not getting the SuperUser pop-up request on apps the first time you run them, your su isn't working right yet.

Delete please.

busybox not installed properly

i have a samsung epic 4g. iused super1click but it is saying that busybox was not installed properly and now rooted apps are saying i do not have root access but root checker says i have root access please help

download "busybox installer" from the android market. you can install the latest busybox from it

i installed busybox installer but it is sayin it is already installed but not installed correctly

go into /system/xbin and /system/bin and look for the file "busybox." delete it and try installing it again with busybox installer

i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app

nalanotae said:
i have tried that in both system/bin and system/xbin but it will not delete. do i need a specific file management app
Click to expand...
Click to collapse
i forgot to mention that you will need to mount your system as read/write. to do this, a file management app would be very helpful. root explorer in particular (a paid app, but as you may already know there are always ways to get apps for free; that is all i will say about warez as it is prohibited on xda). in root explorer, you can mount your phone between r/w (read/write) and r/o (read only). once you mount it as r/w, i believe you can now delete those files

one other thing i forgot to mention, i keep getting a notification that my su binary is outdated when i click to update it says fail.
ok so i was able to delete the busybox files out of the 2 folders but when i went to install it with the busybox app it says "it looks like busybox is installed but it does not appear to be the version that you selected to have installed, you may want to try the intalation again but this using a different istalation location." i try a different location and check my root checker and it keeps telling me that busybox is installed incorrectly

as i have not used superoneclick before, i have no knowledge about the su binary being updated. i used z4root to root my phone.
your best bet is to do one of the following:
a) if you can unroot your phone, then do so (i believe superoneclick allows you to unroot your phone). then try rooting it again using z4root. download z4root from here and tell me what options it gives you when you open the app (it should say either temporary root and permanent root; select permanent root). z4root should work on your phone as it has the same requirements as superoneclick (which is having android version 2.2/2.2.1)
b) if step a didnt work, post in the superoneclick thread for help. but step a should work

Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed

mjs1231 said:
Nexus 5
Rooted
Stock image
Used nexus root toolkit
Busy box crashes when attempting to install from within busybox
Says not installed
Used root explorer to check system/bin
And
System/xbin
No filename that says busybox
Not sure what to do.
---------- Post added at 10:47 AM ---------- Previous post was at 10:35 AM ----------
Resolved
Set system to r/w at boot as root.
Launched bb
Says installed
Click to expand...
Click to collapse
I have this same issue on my Nexus 6, i also used Nexus Root Toolkit, how did you set your system to r/w at boot as root?

I am not able to install buzybox due to "try to installing to a different location that may resolve isuue..please help me

I know this is old!
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!

Hello, i have bought busybox pro but i can't manage to install it through the app, in /system/xbin, i only have one file named "dexlist" and in /system/bin i have many files but none named busybox, when i try to install busybox on /su/bin, i get a message: "it looks like the installation of busybox was not successful / try installing it to a different location that may resolve the issue", but i tried differ'ent locations and it didn't work
---------- Post added at 09:03 PM ---------- Previous post was at 08:53 PM ----------
don't forget to reboot after unchecking "mount namespace separation" !! if not it won't work. my phone was quite long to reboot though...
it still doesn't work for me... on huawei p8 lite 2017 (PRA-LX1)

I'm still using the old version not BusyBox V+ .. anyone tried the latest version? it seems quite confusing and I couldn't execute scripts

Busybox
Example if use custom rom viper10 you can set system r/w in tweak > misc

lovemajj said:
Hello readers,
I am aware that my resolution might not help everyone but it will definitely help some. This might only help if you are rooted and using the SuperSu app..
I know this is a really old thread. But there might still be people out there that have this problem and are having a hard time finding the the answer for it. I was just 5 mins prior searching on google for an answer but could not find one.
And so how did I fix it you may ask? (I hope)
Well long story short I turned the following option of in the SuperSu application: "Mount namespace separation"
I thought of this because I had seen a pop-up message when using Titanium Backup that if I experience problems, I should disable that option. And it was probably referring to the Titanium Backup app alone and not any other. But I gave it a shot and it worked.
In detail for those who need it:
It does not matter if you have the Busybox (by Stephen (Stericson)) application installed during this or not. (I had it uninstalled during)
Open the SuperSu app, swipe left on the screen twice so you get to the Settings page (or just click the Settings tab)
Scroll down until you see the option "Mount namespace separation".
If it is activated, disable it.
Reboot
Go ahead and install Busybox if you haven't.
Open Busybox and wait for it to load completely
Click install
Hurray!
Click to expand...
Click to collapse
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:

Williquah said:
Hey, really glad you posted this even though you said it was old, and I'm still on it :laugh: but the combo of your solution, and mounting my /system as "r/w" through Root Explorer worked on my 6P on Oreo!! (OPR6)
Thanks again!! :good:
Click to expand...
Click to collapse
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update

idbl_fanatic said:
What exactly do you mean by "and mounting my /system as "r/w" through Root Explorer" can you explain further? I can't get Busybox to install after OPR6 update
Click to expand...
Click to collapse
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.

Williquah said:
I'd be happy to help. It's been a little while and I haven't repeated the process yet so forgive me if I'm not super clear, even though I think I should be.
So what I meant was get the app Root Explorer ($3.99 on the app store) I don't know how 'piracy' is really looked at on XDA, though I can't imagine well, but you can download the Root Explorer 'pro' apk, and then - as long as it helps - purchase the app from GPlay to make sure to support the devs, which is what I did.
So to get to the actual process - should be quite easy as I did this on OPR6 myself - open Root Explorer, navigate to the "root" tab at the top. Then you should see "Mounted as r/o" and right next to it, a button that says "Mount R/W". Toggle that button, and the text on the left should state "Mounted as r/w", then try to install busybox (however you prefer - I used BusyBox Free by Stephen (Stericson) like I always do).
Hope you are successful with that method, please keep me updated with your outcome so I can help as best as I can.
Click to expand...
Click to collapse
Well that didn't work
Update, I had to change the path to /system/bin instead of /system/xbin

[Q] Superuser can't grant root acess and crashes.

Hey,
A few days ago, my Superuser app stopped granting root access, and now it crashes ranodmly.
I know I'm not the first one and I read many things about it but everything I tried was unsuccessful.
I tried to update the Superuser app but it needs root access at the end of the process.
I checked if my phone was still rooted with a "Check Root" app and it's still rooted.
I tried to install BusyBox, but it needs root access.
I tried to uninstall the Superuser app and the re-install it but since it's a default app included with my ROM I can't uninstall it.
I have a Galaxy Appolo running with Kyrillos 9.7.
Does anyone know how I can fix this ?

Superuser app is being reported to have issues at some point. Try Chainfire's SuperSU app, and see if that works.
If that too didn't work, maybe your root permissions have been messed up, not sure though.

coolsandie said:
Superuser app is being reported to have issues at some point. Try Chainfire's SuperSU app, and see if that works.
If that too didn't work, maybe your root permissions have been messed up, not sure though.
Click to expand...
Click to collapse
I installed it, but when I launch it it tells me to update the SU binaries. I tried to do it but the process just seems to take forever, so I suppose it's not working.

Gangstalin said:
I installed it, but when I launch it it tells me to update the SU binaries. I tried to do it but the process just seems to take forever, so I suppose it's not working.
Click to expand...
Click to collapse
Then I guess there are problems with your root permissions maybe. Try other Superuser app just to confirm it, and if needed re-install your ROM as a last resort.

Gangstalin said:
I installed it, but when I launch it it tells me to update the SU binaries. I tried to do it but the process just seems to take forever, so I suppose it's not working.
Click to expand...
Click to collapse
Try a custom rom with pre rooted busybox and suprer su
If it doesnot work unroot ur phone and root again
This should fix ur problem:thumbup:
HIT THANKS IF I HELPED
Sent from my GT-S7500

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