Develop Bugs

Busybox Error after Updating via Odin

I was running stock rom, rooted with bloat removed. I flashed the update through Odin, flashed CWM, and reinstalled Superuser through CWM, and when I went to update the binary in Superuser, I noticed that it said that Busybox was not found. So I installed Busybox Installer and tried to run, but got an error saying that there are problems with some core utilities necessary to load Busybox.
I then reflashed the update, CWM and Superuser, hoping that would fix the problem, but it hasn't.
My question is if there is anyway to load Busybox internally through CWM? Even if it is an older version of Busybox, once the core utilities are there, I can always update through the Busybox Installer.
Worst case scenario, I just back up through Titanium, flash back to complete stock, update, and then load CWM...but I always hate starting from the beginning if I don't have to.
The only apps I use that require root are SetCPU, and Titanium Backup. Would I even notice anything without Busybox working? I know Titanium used to be able to update Busybox right through the app, but then they updated and don't anymore...but I'm not sure if Titanium still requires Busybox to properly work.
I posted screen shots of the error messages I see in both Busybox Installer and when updating the binaries through Superuser. Any help would be greatly appreciated. Thanks!

Nevermind, I fixed it. For some reason, the Busybox app from Stephen (Stericson) was the one that kept giving me the error. So I downloaded the Busybox Installer app from JRummy16, and it worked flawlessly the first time. I went back in to Superuser to see if it recognizes it, and it does. So all seems to be good.
Moderator, please feel free to delete the thread. Thanks!

You solved my problem thanks man!!

Losing root for some reason?? Help

So I used odin to flash the official stock jelllybean rom then I used the Samsung toolkit to flash clockwork mod recovery and root. To root it said to flash a superuser zip in recovery. I did.after I reboot everything is working fine. Apps gain root access the promp pops up but after a few minutes it didn't anymore and I cant open busybox or setcpu because it cant gain access but the apps I already granted can. I updated su binary and it fails on gaining root access.
This happens with both super su and superuser. I also tried starting again by oding rom and rooting again. No luck. Please help
Sent from my SGH-T999 using xda premium

Sent from my SGH-T999 using xda premium

Ok, you can try a few things.
First since you have Root Explorer already granted, go into /system/xbin and make sure that there is a file named su. If not, then go into /system/bin and see if it is there. Follow this: If it is in /system/bin, copy it and put it in /system/xbin, check permissions and reboot. Then try an un-granted app and see if that works. Pay attention to the bin and xbin parts here ok.!?
^^^Edit: While you are in /system/xbin make sure that busybox is there also. Just to be sure it installed properly.
Second. If the above didn't work, the go to the market and ChainsDD used to have an app called SuperUser Updated Fixer or something like that. I remember a long time ago, I was having some trouble updating the binaries (as were tons of other people) and he came out with that handy little app. I have been using it since (whenever I have a ROM that uses SuperUser.apk).
Third: I literally just read over in mrRobinson's thread that ICS likes SuperUser, while JB likes SuperSU. Might be something to look into. Maybe swapping out the two apps, might alleviate the issue.

I tried swapping out to super su but was having the same problem. Instead of trying the root explorer method you posted I thought I would go ahead and clean install yet another time. I just wanted the update and root access to work no errors. So here's what I did to fix it and it worked however there's another problem now.
I factory reset, wiped caches
flashed jb stock firmware (instead of the stock fw i now flashed mr.robinsons prerooted firmware)
rebooted checked and saw super su was working fine with my apps.
flashed clockwork mod recovery
made a nandroid backup
flashed wildchilds stock deodexed jb rom (i needed a deodexed rom thats why i flashed this otherwise i would of just kept stock)
booted up and in the play store theres an update for Super Su however i cant update it, it gives me an error.
error retrieving information from server. cant download.tried wifi on off, mobile data on off, clearing google play data and cache. no luck. restored nandroid and there was no update so i clicked reinstall from playstore in su and when i went to go download it, it gave the same error.
So my previous problem is fixed and i dont seem to be losing root anymore but now I cant update SU anymore.

Never mind I seemed to have linked the two issues just because 1 happened before the other, but that might not be the case.
The Google play error is now happening with other apps that i try to update as well.
Is this happening to you guys too?

sometimes when i power off my phone it doesnt boot anymore it gets stuck on boot loop. for example all i did was fix permissions in cwm and it got stuck on boot loop.

Did you Odin root66?

Yeah I odined the root 66 fw by Robinson. That has fixed losing root. Super user is working fine. The only remaining problem is that I get into a boot loop sometimes when I restart for some reason like when I fix permissions.
Sent from my SGH-T999 using xda premium

Re-installing su on Jelly Bean after removing it with Smelkus

Hi guys, I made a mistake while playing with Smelkus (Ra-supersonic-v4.3-smelkusMOD).
While in recovery, I went into the Developer Menu and entered on the "Install eng (unguarded) su" option, which after rebooting, disabled root access from my EVO. Now, every time I try to get root access I get a segmentation fault error.
I'm using MazWoz 4.2.1 Jelly Bean B4.
Short of re-flashing the ROM, Is there anything I can do to regain root access? I really got it working the way I want it, so I don't want to wipe everything if I can avoid it.
Thanks! Oh, by the way, I made no back up ...(I know, my mistake).

Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.

Edit: Sorry, earlier it was in the dev section.

connman said:
Have done the same thing trying to get SU to work properly with a rom. Easiest way is just to restore a nandroid backup.
Click to expand...
Click to collapse
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?

Krazy4evo said:
Unfortunately, I did not make a nandroid backup for this ROM (been using it for only 2 days!).
Anyway, here's what I did so far:
1)I "Pushed" the Superuser.apk found on the MozWoz Rom to my EVO using "adb."
And it did not work. The superuser application installed properly on my device because I can launch it fine from the app drawer, but it does not give me root privileges.
Any other suggestions?
There's gotta be a way to solving this. Exactly, what does the "Install eng (unguarded) su" option on Smelkus do anyway? Does anybody know?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium

the.emilio said:
http://androidsu.com/superuser/
Download the ARM zip, flash in recovery. You also need the binary and not just the apk. That's why it still didn't work. If it still fails after this then clean wipe and flash ROM again.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.

Krazy4evo said:
I flashed the ARM zip files with varying results, but none gave me root access.
Anyway, the only way I gained access was to reflash the ROM....
I hope this saves time for any one who's ran into this issue. Nothing but flashing the ROM seemed to work.
Click to expand...
Click to collapse
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.

connman said:
Glad that you got it figured out.
Like the.emilio said, there are two parts to the SU. You had just downloaded the apk (the app) but that needs the binary (instructions) to work.
I would have thought that the ARM files would have done this.
At any rate, you're back and working, so that's good news. My advice would be to now go make a nandroid backup. That way as you discover and play with this new rom, if you break something, you can easily return to a known "good" state without too much hassle.
Saved my bacon more than once over the years.
Click to expand...
Click to collapse
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.

Krazy4evo said:
I barely ran the ROM for 2 days before realizing I had not made a backup -lol!
My guess is that Smelkus was intended to be used with GB, so it created ROM root privileges that were different from later version of su? Maybe Smelkus needs to do a kernel check before enabling certain options?
Anyway, it's great to be back. And yes, I made a backup shortly after getting everything to work.
Click to expand...
Click to collapse
Hmm. I'm running Smelkus in Provision/Jellyvision, which is a JB rom (great rom, by the way and very stable on our Evo). In fact, smelkusmod was recommended by the developer of Provision/Jellyvision as the recovery. It's based on AmonRA, so should be pretty compatible regardless.

Install unguarded su installs some old superuser hack as the su binary. Not sure what it was for, but it had a purpose at some point. The regular "Install or fix su & superuser" choice installs a normal (but quite old) version of the superuser.apk and binary and sets their permissions. Both should be avoided at this late stage of Evo use. I think Diablo updated to SuperSU on his version, but if you need to install Superuser (koush), SuperSU, or SuperUser it would be better to use the latest version of their respective flashable zips.
Recovery is entirely separate from the ROM and kernel you are running, so it doesn't matter if you have Jelly Bean, ICS, GB or even Android at all for that matter. All recoveries - stock, CWM, TWRP, RA, etc - are basically a mini-OS with their own kernel and init. It boots and runs the program, recovery. Recovery then executes built in commands and scripts included with it. When a ROM developer recommends a recovery, they are just promoting what they like. Any recovery can do the job in their own manner.
In your case, after installing that unguarded su, you could have done any of the following steps to recover:
Flashed a current Superuser zip if it was already on your phone
adb pushed one and flashed
Booted up the ROM, downloaded one, go back to recovery and flash
Flashed the ROM and gapps again, wiped cache and dalvik and rebooted
Restored backup if available

Got root working again after 4.3 OTA...

I only had root on my phone for TiBackup and I had Clockwork installed, as I was thinking about installing an a rom. Then AT&T pushed this crap down, and removed / disabled all of that for me. Nothing like shields popping up constantly. Thanks!
I installed CF-Auto-Root-d2att-d2uc-samsungsghi747.zip, which was modified on Nov 20th, 2013. That somewhat worked, as I kept getting SuperSu stopped working constantly, but TiBackup said it had root access. The Shield kept popping up saying crap was blocked still.
Following the directions here: http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/ I reinstalled my clockwork, told it to boot into recovery via it's menu, and installed UPDATE-SuperSU-v1.43.zip. That fixed everything. No more shield, and root is back.
I can now start SuperSu, view it's settings, etc.
All is right with the world again.

Just did a full backup and got a shield warning, so this root is "different" than the way it used to be.

Since you are rooted would you mind pulling the modem?
Just use Terminal Emulator and Copy and Paste this into it
su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

You have only one quote there?
I just ran:
su
pm disable com.sec.knox.seandroid
It came back and said disabled.
I then ran another full TiBackup. No *****ing/shield.
RockRatt said:
Since you are rooted would you mind pulling the modem?
Just use Terminal Emulator and Copy and Paste this into it
su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse

RockRatt said:
Since you are rooted would you mind pulling the modem?
Just use Terminal Emulator and Copy and Paste this into it
su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/modem.bin bs=4096
Next use root explorer or other file program and go to Sdcard and you should see a modem.bin there. Just Upload it to drop box or something and post up the link here and I can make a flashable modem or give to Destruct so he can make the flashable modem zip and add to his thread. This would be very cool for the community. Thanks ahead if time.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
i pulled already and post in other threat where you asked..

Thanks
Sent from my SAMSUNG-SGH-I747 using Tapatalk

dansthunder said:
I only had root on my phone for TiBackup and I had Clockwork installed, as I was thinking about installing an a rom. Then AT&T pushed this crap down, and removed / disabled all of that for me. Nothing like shields popping up constantly. Thanks!
I installed CF-Auto-Root-d2att-d2uc-samsungsghi747.zip, which was modified on Nov 20th, 2013. That somewhat worked, as I kept getting SuperSu stopped working constantly, but TiBackup said it had root access. The Shield kept popping up saying crap was blocked still.
Following the directions here: http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/ I reinstalled my clockwork, told it to boot into recovery via it's menu, and installed UPDATE-SuperSU-v1.43.zip. That fixed everything. No more shield, and root is back.
I can now start SuperSu, view it's settings, etc.
All is right with the world again.
Click to expand...
Click to collapse
I also did the OTA update but I completely removed KNOX. Still getting FC on the latest version of Supersu, even if I did get temporary root. When I tried installing 1.43, it tells me to update the Su Binaries, which I looked up and apparently you need the latest SuperSu, which doesn't work. I believe I am only getting temporary root right now. Everytime I install TWRP it gets removed, TiBu now says I have no root access. I am positive I removed Knox. I used TiBu to freeze everything as well as root explorer to delete anything Knox. I also ran the Knox Cleaner zip just in case. No more knox dialogs but no root and no SuperSu . How did you get 1.43 working??

bkong said:
I also did the OTA update but I completely removed KNOX. Still getting FC on the latest version of Supersu, even if I did get temporary root. When I tried installing 1.43, it tells me to update the Su Binaries, which I looked up and apparently you need the latest SuperSu, which doesn't work. I believe I am only getting temporary root right now. Everytime I install TWRP it gets removed, TiBu now says I have no root access. I am positive I removed Knox. I used TiBu to freeze everything as well as root explorer to delete anything Knox. I also ran the Knox Cleaner zip just in case. No more knox dialogs but no root and no SuperSu . How did you get 1.43 working??
Click to expand...
Click to collapse
I installed the latest SuperSu via Clockwork sideload,(think that's the proper term) which was updated on the 23rd. (via the url in the original post) Otherwise it was still force closing constantly. Updating via Google play doesn't do enough. Flash the zip via your manager and it should solve your problem.
edit: btw, after the root alone, I couldn't even open the SuperSu app, it immediately crashed. But, TiBackup said I had root, which was a first. That's when I hunted down the SuperSu files.
To recap, I did:
Install the chainfire root via odin as it requires. When my phone was up, I had the shield still going nuts, supersu force closing, but I went into Clockwork, which I already had installed before the OTA, told it to install the recovery, and then rebooted into that recovery from within clockwork menu. From there, I installed the SuperSu update zip, and that fixed the constant force close of SuperSu. After that, went to terminal and did a su disable on knox.

I followed the instructions and was able to gain root access again without the shield popping up when I opened superSU. I then also went into Terminal Emulator and did a "su pm disable com.sec.knox.seandroid" which appeared to work, however....
When I tried to debloat some of the AT&T/Samsung apps using Clean Master (from KS Mobile - available in the Play Store), it asked for SU rights and I granted them, but when the un-installation of the built in apps began... the stupid shield popped up again and Clean Master failed to uninstall everything.
Edit: Froze Knox services with Titanium Backup. The shield didn't show up, but it (Clean Master) still failed to uninstall any of the apps.
Edit2: Ashaman got rid of the stuff for me, naturally. But I'm a noob to all of this and don't know if Clean Master not working correctly is a root issue alone, or a combination of issues with 4.3 OTA/root & Clean Master. Debloating with rooted 4.1.2 OTA worked fine with Clean Master.

Root not working, stock Nexus 5x using Root Toolkit, trying to avoid a wipe

Hey all,
I realize this might need a wipe, but honestly if there is a fix it will save me a few hours headache of reloading and re-configuring everything.
Currently my phone will not root properly. I'm using the latest release MTC19V. I used the Nexus Root Toolkit to upgrade without wipe from the previous version like I normally do. After upgrading, I used the root function. There were no errors, however some applications are stating SU is not present.
SuperSU thinks everything is fine. Root requests are popping up normally.
BusyBox states "the su binary was not found on your phone", even after SuperSU pops up and I grant it permission. I assume BusyBox is no longer installed.
AdAway states "su binary could not be found" after I grant permission.
Greenify gets root access fine.
Xposed is working.
Also, after it is rooted, I no longer have access to DATA services over the 2G/3G/LTE networks, there is a "!" icon by the signal bars. WiFi works fine. If I flash back to stock without wipe, everything works normally.
I have tried:
- Unroot, flash back to stock MTC19T
- Removing all apps and installs of Xposed, SuperSU, BusyBox
- Using the uninstall and clean options in SuperSU
Going to keep messing around, but if anyone can point me in the right direction to avoid a full wipe, that would be fantastic.
Thanks.

Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk

PiousInquisitor said:
Duck the toolkit. Flash the latest SuperSU in TWRP.
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.

Tarv said:
Tried manually flashing SuperSU 2.74 directly from TWRP. Looked successful, still the same issue.
Click to expand...
Click to collapse
Ok, the regular ole busybox and adaway don't work with systemless root. There are additional things that need to be flashed. When I get to my computer I'll post a link to the files.
Sent from my SM-G930V using Tapatalk
---------- Post added at 05:00 PM ---------- Previous post was at 04:51 PM ----------
Flash the systemless hosts file from THIS link to get adaway working.
Try THIS busybox. If it doesnt work try THIS one.

Hi Tarv, I've given you a "thanks" because you've saved me the time of writing pretty much what you wrote regarding my Nexus 6P. I started to experience this problem yesterday. Here are some details.
Everything was working fine. All my Nexus rooting through the years has successfully been done via NRT. NRT is not the problem, as this problem began long after already being rooted and well after using it recently to update to the newest 6.01 security patch.
I think the problem might be a corruption of the Busybox installation, though I'm open to being told that I don't I have a clue of what I'm talking about. I'm referring to the applets or whatever they're called, not the installation app.
The reason I think this is because I noticed a few days ago that when I tried to update Busybox to the newest version (1.24.2 from 1.24.1) via the Busybox Pro installer by Sterickson, it indicated the installation was successful, but the version number shown as being installed was still the old one. When I looked at the directory where Busybox was installed (/su/xbin), all of the applets were zero bytes. This bugged me, so I foolishly decided to uninstall the applets via the Busybox Pro installer and then reinstall, even though a warning popped up that this might cause problems.
It was after this that I lost my data connection (LTE, HSPA, etc.). Also, as you described, the Busybox installer will no longer proceed beyond saying that the su binary can't be found. Other installers also fail, including Busybox on Rails. Most root apps work fine, but not Adaway. Otherwise, the 6P with root works as expected, including using Xposed modules.
Upon unrooting, everything goes back to normal regarding the data connection. Rooting again results in no data connection.
There's probably a method via ADB to correctly reinstall Busybox, but I don't want to do that until someone confirms this is the likely issue. Otherwise, I suspect a full reinstallation of the OS might be needed.
OK guys and gals, ideas?
Sent from my Nexus 6P using XDA Labs

Spikedude said:
I think the problem might be a corruption of the Busybox installation
Click to expand...
Click to collapse
Spikedude,
I think I was in the same boat. Before it stopped working, I too was seeing BusyBox 1.24.1 and not able to upgrade to 1.24.2. I also did an uninstall.
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
I used the other method of installing BusyBox as PiousInquisitor mentioned, and it installed properly, although it's using 1.24.1. BusyBox by Stericson still does not show it's installed.
I also think the installer from Stericson is busted and what caused this whole mess.

Tarv said:
I've since wiped the phone to get it working (my proximity sensor is busted and I need Xposed to disable the sensor). Everything is working, but again BusyBox was not installing (using the Stericson version that NRT installs). It would say it was installed successfully, but it would never show it was actually installed.
Click to expand...
Click to collapse
Hey Tarv,
Thanks for the update. When you wiped the phone, what method did you use? Factory reset from within settings, or using NRT to flash stock and unroot with the "no wipe" option to preserve user data disabled?
Also, you might be right about the broken Stericson Busybox installer. Busybox on Rails looks like a good alternative. I've disabled the NRT option to install Busybox by Stericson when rooting, so I'll just install Busybox on Rails after the fact.
Sent from my Nexus 6P using XDA Labs

Spikedude said:
When you wiped the phone, what method did you use?
Click to expand...
Click to collapse
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader

Tarv said:
Flash stock + unroot (wipe mode on)
Lock Bootloader
Unlock Bootloader
Click to expand...
Click to collapse
Thanks Tarv,
Followed your procedure and am once again rooted and have data connectivity.
Unfortunately, installation of Busybox was not successful. Tried the BB on Rails version, but it only installs to /system/xbin, not /su/bin. As a result, the same root apps that didn't work previously still don't work. BB by Stericson pops up the success message, but then indicates BB is not installed.
So almost back to square one. I'll try going back to stock and rerooting using NRT again, but this time enable BB installation as part of the rooting process. Maybe...
UPDATE:
First, I may have spoken too soon about BB on Rails not working. I based that on root mode of ES File Explorer not working properly, but that might be an ES problem. Play Store reviews are also complaining about the ES root problem. So maybe installation of BB to /system on systemless root is ok?
I wiped and rebooted with NRT, and allowed it to install BB by Stericson. This worked fine, allowing installation of 1.24.2 of BB to the /su/xbin directory. Originally it indicated /su/bin, and that the "cat" file was missing (whatever), but after reinstalling to xbin a couple times and some restarts it all looks normal. Adaway works, full data connectivity works, etc. Trying to flip the root mode switch in ES pops up an error, but I can still explore root, so no big deal (I'm using Solid Explorer more anyway).