I unlocked and rooted N5 as soon as I got it way back when but I don't recall if I ever installed busybox. I wiped my device to install the 4.4.3 update since one of my files/folders was altered from stickmount. I just installed TWRP and flashed supersu but now I am wondering if I need to install busybox?
I have the pro (paid version) already so not an issue of buying it, running stock rom and kernel for now just custom recovery and root.
Thanks
You don't need busybox unless some of your apps require it
Sent from my Nexus 5 using XDA Free mobile app
BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts.
If you have a root app that need BusyBox to function then yes you need it. Most root apps I have on my phone have their own counterpart already imbedded in the apps, for example Titanium Backup, which is why it works without BusyBox.
Also most custom roms already have busybox included as standard. BusyBox might be needed on Stock, only if you have a root app that needs it to function.
Btw it wont hurt you to install it if you are unsure if any of your app requires it
Skickat från min Nexus 5 via Tapatalk
Thanks all, I wasn't sure but now at least I know.
I know many roms already include it but I am running stock right now.
Related
I'm trying to use the Droid Explorer app to browse the file system on my phone without using the command line. However, to fully use the browser, busybox needs to be installed on the phone. I was wondering if anyone else has done this? I understand that the Madaco ROM has this pre-installed, but was wondering if there was a way that install busybox without flashing the ROM. Thanks.
I've heard that busybox can be hard to load (nvr done it myself), that's why I just use a custom ROM to get it. Even though it is not mentioned, busybox is in the latest Fresh ROM as well.
lostnfound53 said:
I'm trying to use the Droid Explorer app to browse the file system on my phone without using the command line. However, to fully use the browser, busybox needs to be installed on the phone. I was wondering if anyone else has done this? I understand that the Madaco ROM has this pre-installed, but was wondering if there was a way that install busybox without flashing the ROM. Thanks.
Click to expand...
Click to collapse
I think I saw it on this forum... or by a google search... but to install busybox, you download it (again, I think I got the binary from this forum) and put it in a folder like /data/busybox (or on MoDaCo it's in /system/xbin) and then you run busybox --install (or something like that) and it creates all the symlinks.
In order to use the functionality, you have to put into your path the folder where busybox is installed (or at least the symlinks). I found it easier to just install MoDaCo's ROM since you get a lot of other cool things like WiFi tether, apps2sd, superuser whitelist, etc.
Please forgive my "or something like that"'s, but I don't have the exact link to reference... I found the answer (like I said, I think on this forum) just by searching.
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
50cr473s said:
I'm using a cm nightly with the new super user built into the ROM. So, can I uninstall the app or what?
Free your mind!
Click to expand...
Click to collapse
Uninstalling it would remove root. You can replace it with another superuser app.
I'd be careful with this. I did it by accident (switched ROMs, had a had SuperSU installed on my old ROM, but new ROM came with its own SU program. When I reinstalled everything I included SuperSU) and it messed everything up - no programs could successfully get root access. I ended up just wiping and re-installing the ROM, this time not re-installing SuperSU on top of it and sticking with the built-in one on Viper.
Is there really any difference between SU apps? Hardly seems worth the hassle.
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
50cr473s said:
I'm using cm's app which is open source and built to be compatible with android platform, thus the ability to be integrated into the ROM. I've noticed that when I switch ROMs(e.g. carbon's unofficial port) Supersu is there in the app tray(instead of cm's) and cm's is in the settings. I had supersu installed before, but removed it when I installed cm's app. Oh my I've gone crosseyed. I've decided that it works as is and my only need is to clean up a little. I was just wondering if any one knew about specifically CM's super user?
Free your mind!
Click to expand...
Click to collapse
Well here's two cents for what its worth. When I moved from Rooted Stock (with SuperSU) to CM10 based Rom (LiquidSmooth), the CM10 app superseded from under Settings. SuperSU had to ask that app for permission before opening its own shop. From then on SuperSU ruled.
You don't necessarily have to do this. I did it because I like and support Chainfire's work. You can uninstall SuperSU if you are getting a CM based ROM with their app. It does not matter either way. They both are good.
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
You could have flashed root back just the root zip
a box of kittens said:
You could have flashed root back just the root zip
Click to expand...
Click to collapse
I tried and failed. Recovery Flash had error unable to obtain Root.
Perseus71 said:
Now as to SuperUser is concerned, I had a string of bad luck on ICS when that app tried to update SU Binary and ended deleting it. Of course I lost Root and since it was messed up, I could not use any Rooting Tools to get back.
Click to expand...
Click to collapse
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
bliind said:
The SuperUser in CM now is not the same as it used to be, this is a new, open source SuperUser built by Koush and designed to be integrated into the system. Also this new version has two ways of updating the binary should one fail you.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Yes I am aware of CM's inbuilt app. My comment that you quoted, pertains to the SuperUser App by ChainsDD as against SuperSU by Chainfire. This for the part 2 of OP.
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
50cr473s said:
Do either of the devs have a thread pertaining to switching su apps? I couldn't find anything?
Free your mind!
Click to expand...
Click to collapse
Here's SuperSU. Best to download the App from Google Play. The thread can be confusing.
The CWM Superuser app on Google Play.
The original Superuser App by Chainsdd. As before best get it on Google Play.
i always download the supersu cwm flashable from the supersu thread, then after you flash it you can disable the original one.
I was just wondering if anyone here has any experience with using Mobile Iron with a phone that has been rooted for a few small tweaks and then unrooted.. Does it work? Can Mobile Iron tell that you were once rooted but are no longer?
I've got an AT&T Galaxy S3 that was recently upgraded via OTG to Android 4.3 with Knox and the new bootloader, etc. Unfortunately, the 4.3 upgrade has disabled my ability to tether. I'd like to apply a mod that fixes that limitation, but I don't want to lose the ability to get work email and such on my phone via Mobile Iron.. Any thoughts on whether or not it should be possible to:
1. Temporarily uninstall Mobile Iron
2. Root my phone and apply the tether mod
3. Remove root from my phone
4. Reinstall Mobile Iron and have it work?
Any thoughts, suggestions, advice would be greatly appreciated!
Thanks
MrSimmonsSr
Sent from my Sero 7 Pro using Tapatalk 4
For the record, just wanted everyone to know this seems to have worked like I'd hoped! I used CF-Autoroot to root my S3 running 4.3.. (The first time I tried it I bricked my device because I didn't think to unencrypt it before I applied root. Don't do that! I had to flash the 4.3 update twice to get it all working again! )
But once I did that I was able to root the fresh install, remove tons of bloatware and apply a tether hack. Then I unrooted and reinstalled Mobile Iron and Touchdown.. So far no issues!
Sent from my Sero 7 Pro using Tapatalk 4
Hi Mr,
currently I am doing research on MDM solutions and I found some information about the detection methods MDMs use to detect root. The following four are commonly used (https://www.netspi.com/blog/entryid/209/android-root-detection-techniques):
1. Check default files and configs.
2. Check if there is a Superuser app.
3. Check permissions of some folders (i.e. /data)
4. Check is "su" commands can be executed.
I don't expect or expected it to cause any problems! Dependant on the security policy, installing some apps like thether hack, might cause a security alert though.
Sometimes applications that require root will trip the application that wants to ensure root doesn't exist. For example Citrix Home detected BusyBox existed on my system & thus flagged my phone as rooted.
There is also an Xposed Module which will attempt to hide root:
http://www.xda-developers.com/android/xposed-module-to-cloak-root-access-from-apps/
http://forum.xda-developers.com/showthread.php?t=2574647
I just purchased RAM Manager Pro but noticed that when I opened the app for the first time I got a popup that said I am missing busybox. Is this an app that is required in order to make RAM Manager Pro work properly? why is it required and if it isn't required why is it asking me to install?
Thanks
BusyBox is a collection of powerful command-line tools in a single binary executable that can be run for UNIX based systems, including Android. So in short busybox hmmm.... Allows more Linux commands!
Some apps require busybox to be installed. To install busybox just root your phone then go to the Play Store and install busybox installer and let it install.
If your phone isn't rooted and you don't want to root your phone then ask the developer for a money refund.
Please press the thanks button if I helped ^_^
Sent from my Nexus 7 using XDA Premium 4 mobile app
It seems Android pay is blocking custom ROMS and root. Hiding the SU binary and pushing a stock build.prop dont seem to alleviate the situation. Does anyone know of a workaround that allows one to keep his root and/or ROM?
I saw this pic on reddit when a user asked google http://imgur.com/FVhQPTz
It uses the SafetyNet API.
Tried setting it up on a stock / signed ROM, went through fine. Tried to backup the app+data and restore it on a custom ROM. Saw my complete account screen for a split second before the 'add new card' window came back and wouldn't go away.
This would not surprise me. Don't be surprised if you can't get around it. Root is too much of a security risk for something like that
I'm not very good with hacks and workarounds but I tried this and it didn't work.
http://androiding.how/android-pay-with-root/#comment-779
Note 2/i317 AT&T/unlocked sim/CyanideL ROM v19/Shift Kernel 5.7
SafetyNet API - fix Android Pay issue with Root / Custom ROMS / xposed
New Last Night...
http://repo.xposed.info/module/com.pyler.nodevicecheck
No luck on a Moto X (2014)...anyone else having any luck?
Nope
No luck on Safteynet API, root cloak, disabling root aps, etc. LG G3 modified stock rom and kernel.
in SuperSU i just disabled SU, NOT unroot, and then it allowed me to add card. im stock rooted s5
Same here
I'm reading that "custom ROMs are missing some proprietary files that Android Pay relies upon"
http://android.wonderhowto.com/how-to/get-android-pay-working-rooted-device-0164604/
It may allow you to add the card, but when you re-enable SU, Pay will not go through when trying to use it.
Downgrade to an 8.x version of Google Wallet. All versions in the 9.x range were preprogrammed to disable themselves when Android Pay came out. I switched back to 8.0-R190-v25 that's preinstalled on my Nexus 5 and disabled automatic updates for Android Pay on the play store.
If you have something like Titanium Backup (which most would if they're rooted), you can also detach Wallet form the Market, meaning it shouldn't know to update it.
Okay, let me start off by saying I thought I could not give up root for Android Pay. I tried workarounds, e.g., temporarily disabling supersu, which let me add cards but wouldn't actually process payment at store.
I have a Nexus 5 on Sprint, with official 6.0 factory imgs installed. I have TWRP recovery and an (obviously) unlocked bootloader. While rooted, I flashed ElementalX kernel (allowing for double-tap to wake, swipe to sleep, and under-volting--3 features I can't live without), modified build.prop to allow multi-window mode, and ran ADB commands to enable tethering (courtesy of Reddit instructions).
I then completely uninstalled SuperSU and BusyBox (no easy task--had to delete system apks and reboot numerous times). I also had to delete su and busybox entries from system/xbin for unrooting. After a reboot, I successfully installed Android Pay, added credit card, and have successfully used it at several retail outlets. More importantly, my kernel DT2W/swipe to sleep/undervolting options still work, as does tethering and multi-window. Apparently AP doesn't check for build.prop or boot mods, nor does it check for bootloader state or stock recovery. I do miss quickboot options I had with root however.
If I absolutely need something that requires root, e.g., Titanium Backup restore, etc, I can just boot into TWRP recovery through old-school holding down power/ volume button technique (hence why I miss quickboot features), flash SU and BusyBox zips I have on internal SD, reboot, do my business, and then unroot like I did above. FWIW unrooting is MUCH more difficult than rooting, but still very doable once you figure out all the steps.
Can you post the steps for cleanup? I have been trying it myself and have had no luck with getting A-Pay to actually work correctly.