i am using void.delta+caveman's v1.1 kernel...however with this setup i have a crazy problem..
To reboot into recovery i usually "su" in the terminal and execute "reboot recovery"..It always worked on other roms like LOL..However in this rom, it seldom boots into recovery .most of the time when i execute "reboot recovery" it just reboots and also corrupts some files, once it broke my wifi (cudnt log into my router anymore) ,once instead of booting into recovery it just rebooted and corrupted all my messages..just wiped all messages i had and messaging app kept crashing !!!Any ideas guys i really love this setup and dont want to switch to other roms ..HELP!!!
I do not exactly see how is this related to busybox? (Anyway, you can install different versions of busybox to test, but I frankly doubt busybox is the issue here at all.)
Fixed it !!! installed latest busybox using busybox installer from market
Good to hear. The latest being? Have 1.19.0 here ATM.
Related
I have the latest 2.0.2.A.0.24 version of android and have rooted my phone with superoneclick but cannot install busybox. It shows the following message when I run it:
"Please wait while we locate BusyBox and gather system data..."
After a few minutes the message goes away and it says:
"Your phone is rooted
BusyBox was not found"
I have tried pressing the install button but it does not do anything???
Has anyone come across this problem before??
Is busybox installed from the market?
Sent from my X10i using XDA App
It had this exact problem (with market busybox), I had to wait quite a while after pressing install, then it worked.
Have a little patience
did you install superuser
Did you reboot after rooting?
sent from my free x10 2.2.1 with dark theme using tapatalk
1. reboot.
2. install superuser
3. busybox
and you're good to go.
rash799 said:
I have the latest 2.0.2.A.0.24 version of android and have rooted my phone with superoneclick but cannot install busybox. It shows the following message when I run it:
"Please wait while we locate BusyBox and gather system data..."
After a few minutes the message goes away and it says:
"Your phone is rooted
BusyBox was not found"
I have tried pressing the install button but it does not do anything???
Has anyone come across this problem before??
Click to expand...
Click to collapse
you need to reboot your phone after the root in order to install the busy box.
had the same problem like yours.
worked for me should work for you as well !Q!!!! cheers
Hi,
I had the same problem. Made a reboot before retrying, and that's OK. Thanks
I installed busybox by "smart install"
I had problems, including version revert after reboot.
I reflashed the ROM (wiped data)
I installed busybox again.
But the problem remained.
It reverts to older version after I reboot device.
I've tried to flash busybox via CWM but that didn't help.
Has anyone had similar problem? How did you fix it?
I tried between three ROMs, which were all stock-based.
Moved to Q&A
Some custom kernels have autoroot(root+busybox install on boot) feature, so busybox gets installed again by the kernel on every boot.
Are you using mesa kernel? If yes, you can't upgrade busybox, it will always revert to old version...
As I wrote on my previous question, I softbricked my phone yesterday when I installed BusyBox X and CWM recovery on my phone. I got a replacement phone and I am cautious on bricking the phone. I am trying to figure out if I did a wrong combo in installing these two things. I had this phone in the summer and I'm trying to remember from memory how this goes.
First I installed LGPwn and rooted it that way, then I installed BusyBox X and pressed the button that said install, finally I installed the L9 bootstrap recovery and rebooted. Then I proceeded to install 2 zip files, 1) Black Status Bar tweak by Mateo1111 and 2) Hide QApps also by Mateo1111. I restarted the phone and was greeted with the error of com.android.phone has stopped and encrypted/ reset phone. Did I do anything wrong? If so, please help me out!
The problem you had was actually with busybox. I had the same problem after I rooted my L9. I rooted and then installed busybox and everything seemed fine, I then booted to cwm and made a nandroid backup, then after booting back to android os, I was greeted with "Encrypting - Reset Phone" To recover from this, I booted back to recovery and restored the backup and then everything was fine. When it comes to busybox the L9 is very particular. Mine wouldn't work with busybox by stericson I had to use busybox x. If you tried busybox x and had that problem you might want to try busybox by stericson and install version 1.21.0 and use smart install.
xdrc45 said:
The problem you had was actually with busybox. I had the same problem after I rooted my L9. I rooted and then installed busybox and everything seemed fine, I then booted to cwm and made a nandroid backup, then after booting back to android os, I was greeted with "Encrypting - Reset Phone" To recover from this, I booted back to recovery and restored the backup and then everything was fine. When it comes to busybox the L9 is very particular. Mine wouldn't work with busybox by stericson I had to use busybox x. If you tried busybox x and had that problem you might want to try busybox by stericson and install version 1.21.0 and use smart install.
Click to expand...
Click to collapse
Thanks for your reply! I did install the other version of BusyBox by Stericson and it worked flawlessly. No errors so far, and I have my phone set up the way I like it.
Awesome... Glad I could be of help.
Hi! I've just rooted my device (Nexus 5) with Chainfire auto setup and I've downloaded Superuser by Clockworkmod. When I opened it up, it showed a message saying that I needed to update the SU binary, I went back to the Play Store, I read the description and I found a link, that allows me to install it from a recovery files. Once I downloaded it I opened the app again using the recovery files, Android crashed and rebooted itself, but during the boot it showed a dead android image (the one with the red triangle). I've turned off my device (Nexus 5) and then I've reboot it, now all works fine. I'm terribly scared, what the hell happened? It's my fault or Superuser just crashed?
SimoPiersi said:
Hi! I've just rooted my device (Nexus 5) with Chainfire auto setup and I've downloaded Superuser by Clockworkmod. When I opened it up, it showed a message saying that I needed to update the SU binary, I went back to the Play Store, I read the description and I found a link, that allows me to install it from a recovery files. Once I downloaded it I opened the app again using the recovery files, Android crashed and rebooted itself, but during the boot it showed a dead android image (the one with the red triangle). I've turned off my device (Nexus 5) and then I've reboot it, now all works fine. I'm terribly scared, what the hell happened? It's my fault or Superuser just crashed?
Click to expand...
Click to collapse
You didn't do any damage to your device. What it seems like is that you only have root access and not a custom recovery like ClockWorkMod or TWRP so when you went back to the app it went to boot you to recovery to install them and it rebooted you to the stock recovery which does not allow installation of files that aren't signed with a specific factory key. You should be able to update the binary with the normal install mode on the Nexus without issues. If you want a custom recovery, there are various ways to do it, but the easiest would be with the GooManager app (free in the Play Store) where you grant it SU access, hit Menu > Install OpenRecoveryScript and let it do it's thing. Then when you boot to recovery, you will have a version of TWRP. This is a great custom recovery. Touch based, Fast. Allows you to back up all the important parts of the phone so you have a system backup - called a nandroid (which you should do and save to a safe spot) as well as install custom versions of android, themes, kernels, and all types of other mods as well as a way to do a complete factory and /sdcard wipe if ever needed.
Thanks GOD!
es0tericcha0s said:
You didn't do any damage to your device. What it seems like is that you only have root access and not a custom recovery like ClockWorkMod or TWRP so when you went back to the app it went to boot you to recovery to install them and it rebooted you to the stock recovery which does not allow installation of files that aren't signed with a specific factory key. You should be able to update the binary with the normal install mode on the Nexus without issues. If you want a custom recovery, there are various ways to do it, but the easiest would be with the GooManager app (free in the Play Store) where you grant it SU access, hit Menu > Install OpenRecoveryScript and let it do it's thing. Then when you boot to recovery, you will have a version of TWRP. This is a great custom recovery. Touch based, Fast. Allows you to back up all the important parts of the phone so you have a system backup - called a nandroid (which you should do and save to a safe spot) as well as install custom versions of android, themes, kernels, and all types of other mods as well as a way to do a complete factory and /sdcard wipe if ever needed.
Click to expand...
Click to collapse
That's why I love XDA Developers, because there are people that knows what they are saying! Thank you so much. Now I'm wondering if I should install a recovery mod as you suggested. Do you think I have to install Tasker as well? My first idea was to install Xposed modules, after rooting my device, but when they say "be careful it could **** UP your device" I wonder "Why the hell you should say that when I want to install them?", so I still think about that. Thank you again!
SimoPiersi said:
That's why I love XDA Developers, because there are people that knows what they are saying! Thank you so much. Now I'm wondering if I should install a recovery mod as you suggested. Do you think I have to install Tasker as well? My first idea was to install Xposed modules, after rooting my device, but when they say "be careful it could **** UP your device" I wonder "Why the hell you should say that when I want to install them?", so I still think about that. Thank you again!
Click to expand...
Click to collapse
Tasker is not necessary for any of this. Tasker is for automating your phone to do certain tasks under specific conditions you set up. Such as setting your phone to turn on wifi based on location. You certainly don't NEED a custom recovery, but if you like to play with your phone, then it is a great way to be able to make a complete backup to restore in case of emergency. When you install and activate the Xposed framework, it will also create a zip file on your storage that will disable it while flashed through a custom recovery. If things go super wrong, you can also restore the phone via PC using fastboot tools and factory img files from Google. What I like to do is:
Download factory img files and set up adb and fastboot
Root
Recovery
Nandroid
Backup Nandroid and complete storage to PC
Flash whatever roms or mods
If it completely bricks and you lose access to storage then restore system from PC then redo recovery, copy files and nandroid back to storage and restore backup
bam - back in business.
As it says in the subject, a string of events occurred while upgrading a CM nightly, and I somehow lost root in the process. I have TWRP installed, and tried downloading a superuser zip and installing it from recovery, but the app doesn't appear to have access to a su binary. Phone seems to be functioning fine, I'd just like to get my root back.
Mods, feel free to delete this post. Flashing a newer version of supersu fixed my problem.