Related
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
Latest end-user Omnirom 4.4.2 for the LG P500 can be found here:
http://jenkins.androidarmv6.org/job.../archive/omni-4.4.2-20140214-p500-NIGHTLY.zip
I am starting this to stimulate interest in the Omnirom, get/give advice and help on how to get it working on our device. My hope is that one of the devs would take this over and move from a discussion to a dev thread if need be. I can really offer no help at this point as I have not yet gotten this installed and running.
Another reason to start this is to keep from less than courtiously cluttering other threads with this stuff.
Finally, cm-11 for our device is quite problematic so I seek another Kitkat chocolate treat
==================================
Omni has two big problems holding up a working install on our device:
1. Omni is not rooted by default. I tried flashing a superuser.zip, still had no root. I have copied a full cm-11 su (binary) to the zip, tried that but installation was aborted for other reasons so could not yet test this approach. Please, devs, give us normal root in this ROM. Not so useful without it.
2. No adb until boot completed and I approve it. Great idea for security, but this thing is still experimental. So I cannot ride herd on the installation as I am accustomed nor run a certain script that I need from later cm10.* and cm11. As it turns out, Omni will run the script, cm11 would not. However, once I have attempted an Omni boot, I cannot get adb back outside of that successful boot until I restore another ROM! Means no adb reboot, adb reboot recovery, nada. Makes things very very problematic.
Omni will run my /data/local/userinit.d/ scripts which recent cm10.* and cm11 refuse. I always ran ICS this way, and I could presumably get a complete startup sans boot this way. To try this next--caution: Kitkat Link2sd mount script is not identical to previous ones so this must be placed to try this. Using the older version (maybe newer one as well!), everything simply FCs out, get nowhere. Link2sd needs root the create the script normally, Xposed needs root to get going, and Titanium and other tools are more useful with root as well. Lack of root is the main problem right now. Please ...
==========================
The usual disclaimer: If you have rooted your device, the warantee is void. Of course, for this oldie but goodie, that is just a distant memory. However, these phones are still being sold so if you got a new one, be warned.
I can not be responsible for brickage and breakage. Especially without that always active adb umbillical, it is much easier to soft-brick the device and it can get hairy-scarey getting back to recovery. Again, be warned.
The recent JB and KitKat ROMs are too large for our devices and must be trimmed before installation. My philosophy is that anything not needed to get Android up and running does not belong on system. Practically, anything installable from Play or side-loadable as user apps should be removed from system/app. Examples are Calendar (install Play version), calculator, camera/gallery, browsers, emailers and such. There are superior choices on Play or side-load those included with the ROM. If using Google Search, also remove the quicksearchbox. system/usr/srec, system speech recognition config, can be pushed to sdext and symlinked from there, freeing a good few meg. You do not need a lot but do need a few meg free on system.
Link2sd or equivalant is needed to keep data space available. Things get flakey when data space gets too low. Gluttonous apps like the newer Swype and Tapatalk (just a few examples--great apps, do not get me wrong) will very quickly run you out of data space and gobble up too much RAM as well, slowing the works. Choose wisely
So here is my next trial:
BACKUP!
Make sure no old 11link2sd script is on /data/local/userinit.d/
Wiped dalvik-cache, restored the sdext from the backup since the CWM seems to wipe this as well.
Wiped cache partition (actually, no longer used for very much!).
Installed the omni nightly which formats /system and proceeds.
Installed the minimal GAPPSlight.zip.
Reboot.
Came up just fine. First asks to enable adb for this computer, said "yes," "always for this computer."
Adb now active and adb, in any event, adb does have root!
Went to link2sd. Cannot get root. Went through all the setup options (including root for apps and abd!). Still not root.
So copied a new 11link2sd to /data/local/userinit.d/
Power menu advanced reboot active in setting and it actually works, avoiding above-mentioned fears
Rebooted.
Bootup runs all my scripts so now have all the link2sd-linked apps.
I could call this a BUG: It neither re-asks the adb question nor places it online. So ... no more abd
Still no root -- tried to activate exposed which without root will not do anything.
Rebooted anyway.
Came up just fine, as before. No root, no Xposed, Still no abd.
Comments:
Otherwise, works just fine, seems responsive. If I were willing to live without root, I could go on with it as a daily driver. Next trial, I will not check "always for this computer." Maybe then it will re-ask me and so re-enable abd.
Shares with cm-11 the flash of a disabled homescreen before the lockscreen. Harmless (as long as it is very brief).
Shares with cm-11 the "upgrading ... restarting apps ..." message on each reboot. Harmless, as long as linked apps, dexes are not being unlinked. Did not check, but cm-11 was no longer do that with the newest link2sd version.
The screen begins to turn off much more quickly. In cm-11, this took a good few minutes, eating the battery as it went.
Background processes came up more quickly (subjective) than cm-11, even though some lacked root to function correctly.
Did not really check if it shares the dissappearing data space problem which for many is a showstopper in cm-11. Initial space seemed appropriate, not half of expected amount. Without adb, can be checked using the SLW storage widget. I should really have done this.
Root remains the main problem with this. Neither flashing a superuser nor placing a full cm-11 su on the ROM enable root. Someone know how?
Attempts at getting root:
The recommended way is to flash SuperSU's zip (available from their XDA thread, surprisingly, not from Play). Since flashing this has twice bricked me up, I am loath to try that once more.
First attempt was the create an init.d type script to start the su daemon. I had placed a Cm-11 su on the ROM's zip before flashing. Voile, manually running that script from adb got me root. The command on adb shell hung up but it had run. Link2sd made its mount script (of which I have my own copy so whatever ...), even accepting the previous approval!
So I placed it on /data/local/userinit.d/ with all my others. On reboot, daemon was indeed running. Tried to activate Xposed. Attempts hung up, then failed. Running superuser (installed from Play as user app, symlinked) would FC. Noticed that I had multiple incidences of the su running which might be indicative of something!
So went back to recovery, removed my script, and flashed the CMW superuser.zip. On reboot, daemon was running. However, any attempt to use superuser FC'd. Removed the apk from system/app, rebooted to regain use of my installed version. Same result.
This issue of root needs be properly resolved to use this ROM.
So back to recovery and cm-10.2 which meanwhile may well be the optimal ROM for this device!
BTW: If the always for this computer was not checked on giving adb permission, after reboot and after a while, the question will be re-asked and one can get adb once again which is good new, though a bit less convenient.
This omni ROM from my humble opinion is quite bizarre and funny. What's really the intention to release ROM that need rooted device to install it (need recovery so first device must be rooted), but then rooted apps didn't work since no SU installed .
Sorry omni devs and anyone. No offence. Just express my opinion.
I tried Superuser.apk and SU from xda but failed.
Sent from my Optimus One using xda app-developers app
Some things I'd like to ask/share
1. My play store isn't working. I've trimmed the ROM n installed gapps too n installed play services too. Bt when i open play store, it works fine. But i can only see spinner loading under 'My Apps' n when I install any app, it gives fc. Then i have to clear data to open it again. What to do? Is it something to do with dpi? Because I've changed the dpi.
2. How to change tiles? I can't get its settings.
3. Any other int2ext script working?
4. Screen record has a very low fps and after recording, the phone becomes unusable. Have to restart
5. I found this ROM more snappy than any other CM11. Thanks to performance controls. Its awesome!
6. Only if root worked, this would be the BEST KitKat ROM for our phone.
(I'm trying to fix it too)
This ROM can be used aa a daily driver if u don't use much apps and root isn't a big issue. Great work
:thumbup:
EDIT:
Link for root in Omni ROM:
http://forum.xda-developers.com/showpost.php?p=50863602
Sent from my LG-P500 using XDA Premium 4 mobile app
Tried again to get root:
I can, in adb shell, su --daemon.
This gets me root for this session. Link2sd will create its mount script!
Rebooted. Thought that the root could be magically persistent as someone posted on some thread somewhere (did a lot of searching! and there were two instances the last time when I used a init.d script to do this). It was not so did su --daemon. Tried to use Xposed. Chugged a while, permission denied. CWM superuser's UI does not work on cm-11, not on this either. But it did not FC!
So I adb pushed SuperSU to system (I have enough room!). It wanted to install its binary. So I rebooted into recovery and flashed that.
On reboot, the su daemon was indeed running It has an 'R' instead of an 'S' on the column before its name. SuperSU also had a process running so thought hey, OK (and it did not brick the phone this time!). Tried to run Xposed. Simply sat there. Tried to run SuperSU, said it needed its binary and could not install it. Yuk! Never did like this app. On cm-10.2, even if CWM superuser wants a new binary, its UI will work anyway. Tried to run that. FC this time.
I never did check free data space.This after several successful reboots with no alarms about it. Overlayed the SLW widget onto link2sd and ran it. Only had 20meg. Fact is I had never ran link2sd to clean up dalvik and such so tried it now. Relink all apps simply chugged along. This can take time, even if it reports nothing to do! Finally lost patience with it but could not kill link2sd with back key (My fault? Options do not take effect until setting run, even if they were checked, it seems). Have to consider the possibility that the "disappearing data space" bug may be in this ROM as well as cm-11 (which, if so, would place it in the AOSP code!). No real way to check it without working root so everything plays.
Rebooted recovery, back to cm-10.2. BTW: the su daemon here has the 'S'.
rhar**** said:
Some things I'd like to ask/share
1. My play store isn't working. I've trimmed the ROM n installed gapps too n installed play services too. Bt when i open play store, it works fine. But i can only see spinner loading under 'My Apps' n when I install any app, it gives fc. Then i have to clear data to open it again. What to do? Is it something to do with dpi? Because I've changed the dpi.
Click to expand...
Click to collapse
Don't know. I only change DPI using Xposed which has not been enabled yet
2. How to change tiles? I can't get its settings.
Click to expand...
Click to collapse
I assume you mean those on the right-side pulldown. Have not found the interface either. Toggle to get that and enough of them are there.
3. Any other int2ext script working?
Click to expand...
Click to collapse
Need root. I did get link2sd to create it mount script after su --daemon.
4. Screen record has a very low fps and after recording, the phone becomes unusable. Have to restart
Click to expand...
Click to collapse
Never tried it. May also be DPI related?
5. I found this ROM more snappy than any other CM11. Thanks to performance controls. Its awesome!
6. Only if root worked, this would be the BEST KitKat ROM for our phone.
(I'm trying to fix it too)
This ROM can be used aa a daily driver if u don't use much apps and root isn't a big issue. Great work
:thumbup:
Click to expand...
Click to collapse
Yeah. Since I can get link2sd mounts either by running the daemon once or placing my copy, I have all my apps available (root ones will not be very happy). I used Xposed and need one round of root for this but that, as opposed to link2sd, did not work.
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+.
Sent from my LG-P509 using Tapatalk 2
ibub said:
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+.
Sent from my LG-P509 using Tapatalk 2
Click to expand...
Click to collapse
Is that su in /system/xbin is binary command to get root access on system file? You must run this command in terminal. However, Terminal.apk only can be launched if SU.apk or Superuser.apk present in /system/app.
So, in my opinion SU or Superuser is needed to run rooted apps (such as TB, Link2SD). Maybe Busybox is required too?
Sent from my Optimus One using xda app-developers app
ibub said:
I have to admit that I do not know much about how su works. But the same su file is present in /system/xbin and is listed in file_contexts. SU.apk or supersu.apk have not been included in /system/app for at least cm10.1+. :confused
Click to expand...
Click to collapse
System/xbin/su is the binary. One included on the ROM is tiny, barebones (no root). I replaced it with one from cm-11. When it is working right, I believe this gives you the dialog: Allow-Deny, Now-10min-always and such. It also has a daemon mode which services root access. I have not gotten the dialog on the Omni after manually starting the daemon.
That daemon needs be started early-on. Even an init.d script may not be good enough (Omni has real init.d capability as opposed to cm-11!). There is a "persistant-root" item in cm-11's build.prop. Maybe this will work here too the with cm-11 binary?
The apk is a user installable app (or gets placed on system by flashing zip). This gives access to the application-by-application permissions granted or denied in the above dialog, enabling changing them. SuperSU offers the most alternatives but is the most ticklish. CWM superuser is simpler, less finicky but seems not to work on 4.4.*. This is part of the problem. On cm-11, I have root, have the above dialog, superuser does not FC but no UI. On the Omni, since root was achieve manually after-the-boot, more problematic.
There are other apks around, superuser-elite, paid versions, etc. They are not exclusive--I had three of them around until I removed them and kept CWM. Any one of them good on cm-11? Should!!! work here too, he-he. The apk is not necessary to service root (i.e. mine is link2sd-symlinked and before link2sd gets its root, no mount script so no app seen).
xu3sno said:
Is that su in /system/xbin is binary command to get root access on system file? You must run this command in terminal. However, Terminal.apk only can be launched if SU.apk or Superuser.apk present in /system/app.
So, in my opinion SU or Superuser is needed to run rooted apps (such as TB, Link2SD). Maybe Busybox is required too?
Click to expand...
Click to collapse
Busybox is there, we do not have gnutls like normal distros--most everything goes through included busybox.
Terminal will work without the apk on /system/app. Cannot judge from the Omni because of no or incorrect root
I just learned a new set of tricks.
[email protected]:/ $ su -h
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
[email protected]:/ $
Sent from my LG-P509 using Tapatalk 2
ibub said:
I just learned a new set of tricks.
[email protected]:/ $ su -h
Usage: su [options] [--] [-] [LOGIN] [--] [args...]
Options:
-c, --command COMMAND pass COMMAND to the invoked shell
-h, --help display this help message and exit
-, -l, --login pretend the shell to be a login shell
-m, -p,
--preserve-environment do not change environment variables
-s, --shell SHELL use SHELL instead of the default /system/bin/sh
-v, --version display version number and exit
-V display version code and exit,
this is used almost exclusively by Superuser.apk
Click to expand...
Click to collapse
Yes, this simply a root version of sh. The one on this ROM probably will not allow anything.
The one from cm-11 will check permissions, give the dialog to ask if root working correctly.
Latest build omni-4.4.2-20140227 is up, triggered by androidmeda :good:
http://jenkins.androidarmv6.org/job/omni/4/
Download here:
http://jenkins.androidarmv6.org/job/omni/4/artifact/archive/omni-4.4.2-20140227-p500-NIGHTLY.zip
Will try is that SU or Superuser included
EDIT:
Just flashed it with clean install.
1. System reboot took under 3 minutes :good:
2. su binary exist at /system/xbin but not link to busybox binary which is present also at /system/xbin.
3. Installed Terminal.apk, it works but denied to run su command line
4. Installed Root Explorer.apk, works fine but failed to access root, such to change permission R/W of /system folder.
5. Referring to 3 and 4, apps need root access failed to work.
6. Tried to install SuperSU flashable zip, it replaced su binary from stock and it caused apps which is need root access (in my case gooim manager, root explorer, and Link2SD) not responded and apps're getting hang
7. Installed Superuser, launched it, works but need su binary.
Do we need latest SuperSU or Superuser, hence su binary is compatible with Android 4.4.2 ?. The installed one is for Android 2 and 3.
xu3sno said:
Latest build omni-4.4.2-20140227 is up, triggered by androidmeda :good:
http://jenkins.androidarmv6.org/job/omni/4/
Download here:
http://jenkins.androidarmv6.org/job/omni/4/artifact/archive/omni-4.4.2-20140227-p500-NIGHTLY.zip
Click to expand...
Click to collapse
Do not know what has changed. There have been kernel merges, etc.
***
2. su binary exist at /system/xbin but not link to busybox binary which is present also at /system/xbin.
3. Installed Terminal.apk, it works but denied to run su command line
***
Click to expand...
Click to collapse
The /system/xbin/su included with this ROM is for no-root access allowed. A blocker.
I placed the su from a cm-11 ROM. This can run its daemon and get root access. Works for link2sd but nothing else (i.e. Xposed), apparently. According to some googled posts, that daemon must be started very early on (as I stated before). I had it in an init.d script. Started but had same negative results. May try the persist.sys.root_access=1 flag in build.prop. Maybe the internally buried code in boot.img will start the daemon as requested here (if it was not removed). There is no explicit script in the cm-11 ROMs to start that daemon.
i have got an idea. But where is the source?
is this the source?
If yes, then where is settings?
EDIT:
Ok got it. Editing
rhar**** said:
i have got an idea. But where is the source?
is this the source?
If yes, then where is settings?
EDIT:
Ok got it. Editing
Click to expand...
Click to collapse
Okay. Waiting for edited omni ROM (SuperSU included ?), as you did with cm-10.1.5-KITKAT-Update_3 :good:
Wish you luck
Sent from my SM-T311 using xda app-developers app
rhar**** said:
i have got an idea. But where is the source?
is this the source?
If yes, then where is settings?
EDIT:
Ok got it. Editing
Click to expand...
Click to collapse
Great. SuperSU itself is problematic but will suffer with it if it works. Would prefer generic like other ROMs.
Anyway, as in my OP, I would be looking for a dev to take this thread over as a dev thread (or open one).
Another OMNI build
Another Omni build is released @ Jenkins, triggered by Androidmeda.Can d'load it from : http://jenkins.androidarmv6.org/view/All/job/omni-experimental/12/
sumansur2008 said:
Another Omni build is released @ Jenkins, triggered by Androidmeda.Can d'load it from : http://jenkins.androidarmv6.org/view/All/job/omni-experimental/12/
Click to expand...
Click to collapse
Labeled for commits about boot animation.
Anyway, downloading.
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root the Moto X, Moto G and the Droid Series(maybe others but these for sure) running 4.4.3 and below. It does NOT and WILL NOT root 4.4.4 so stop asking about it!
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]ninglogic.com! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Also if you are currently rooted with Pie root please reboot before running my app, to clear Pie's su daemon, and to unmount Pie's xbin.img. Then just click Make it ra1n on Moto, and wait for it to say Root Acheived Enjoy! If you encounter any issues please uninstall v1.0 then re-install v1.1.
Download link:
Version 1.2 for 4.4.2 devices
Version 1.2 for 4.4.3 devices
Version 1.1
Version 1.0
Known Issues: If after running it says Failed to Achieve Root, close the app and clear it from most recent's then reopen the app.
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg (I will try to update this video with the full installation steps)
Changelog
-v1.2 10/5/2014
---Created a new bin.img from the tmo 4.4.3 sbf to fix the wifi issues
---Changed the modstring for the XT1032 hopefully it works now if it doesn't then there isn't anything else I can do
---Redid the device check to not allow unsupported devices to run the app
-v1.1 9/22/2014
---Added Moto G support, if I missed a model number let me know
---Fixed the issue with Xposed not working by mounting a bin.img over /system/bin
---Added in the ability to Uninstall the app and all files
---Added in various checks and prompts
Additional Thanks:
Verttex(Dier325) - for being my main tester and testing the numerous test apk's I sent him
jpond83 - for testing
mohlsen8 - for testing on the Moto G
NipplesOfTheFuture - for testing, some workflow ideas, and for convincing me to try and get the bin.img method working correctly
iKrYpToNiTe said:
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND!
Towel Pie Root is a one click untethered app to root Motorola devices running 4.4.2 maybe 4.4.3 and below.
I want to started off by Thanking Geohot for Towelroot and JCase for Pie root, without them this wouldn't have been possible and I take NO credit for their exploits. If either of them doesn't want this posted they may contact me and I will gladly remove it.
Towel Pie Root combines Towelroot's futex exploit with a modified version of Pie root's xbin.img mount into one app. To achieve a one click untethered root for write protected devices! This DOES NOT remove write protection, and is still technically a temp root, I did include the option to enable root on boot. Which will re-root your device every time you reboot your phone, it also includes the option to perform a full reboot, or a soft reboot from within the app.
Here is a more technical description of what my app does. It includes TR's libexploit.so(aka the native exploit by Geohot) which I use to gain root privileges. Once it has root privileges it then echo's the file path to my modified Pie root file to uevent_helper. It then causes a hotplug event to trigger the kernel to execute the file path just echoed to uevent_helper. My modified Pie root files, kill TR's daemonsu and mounts Pie root's xbin.img over /system/xbin. Then it copies the newer version of SuperSU's su binary and executes the new daemonsu daemon and viola root
If you enjoyed my app, please donate to Geohot at https://towelroot.com/, and JCase at [email protected]! I do not want any donations, I set out to develop this app purely as a challenge to broaden my development skills not to get a donation.
Installation Instructions: You need to have unknown sources checked in Settings>>Security, and if you have Towelroot installed uninstall it. In order to use TR's exploit I had to name the app's package name to the same name as TR's package name, so you will have to uninstall TR to install my app. Then just click Make it ra!n on Moto, and wait for it to say Root Acheived Enjoy!
Download link: http://www.androidfilehost.com/?fid=23578570567716728
Screen Recording: https://www.youtube.com/watch?v=f6fXs3VJQHg
Click to expand...
Click to collapse
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
doitinthedirt said:
Thank you Sir, and Jcase and geohot... now the big question... I just factory reset 4.4.2 and rooted Pie.. installed your entitlement hack.. worked dandy... than I tried the tr... and guess what..... your app no longer works.. so, do I need to do another factory reset and install this new towelpie app or will your entitlement hack not work with this either? Or should I be the test pilot and find out myself...
Click to expand...
Click to collapse
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
chrisp6825 said:
For future reference, you can (attempt to) uninstall using adb. It takes a bit more knowledge, but it's simpler.
adb uninstall (package)
tapa'd on my moto x
Click to expand...
Click to collapse
I tried! I couldn't get to ADB while in fastboot. How would I get into ADB Shell if I can't get into anything outside of recovery?
chrisp6825 said:
No need to factory reset. Just make sure you uninstall the towelroot app.
Then install this Towel-root-pie app. JUST this app. Run it, you should be good from there.
iKrYpToNiTe, I know you don't want creditz, but this is also such a helpful and much appreciated tool. I do want to thank you for sharing it with us.
My thanks go out to jcase and geohotz as well. A smörgåsbord of thanks to all of you!!
tapa'd on my moto x
Click to expand...
Click to collapse
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
doitinthedirt said:
Worked perfect! thanks!
So I was already Pied... Pie files already pushed to phone prior to running trpie app.. does this app do the pushing or do we still need to run Pie on its own to push the files?
Click to expand...
Click to collapse
According to the message the OP sent me, PIE is no longer necessary - at all. He advised me that you can run this app on a bone-stock Moto X that has never had PIE used on it.
Have fun guys, AND HIT THE "THANKS" BUTTON TO THE OP!!!!!!
tronmech said:
Not good, I can't get it to stop rebooting. 4.4.3 moto g. Selected root on reboot, and now it reboots over and over.
Edit: Factory reset my phone through recovery using instructions at https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97329/p/30,6720,9050
I'm at least back where I started from.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
windraver said:
side note, don't try it on the moto G. I'm stuck in a bootloop.
edit: was going to try and uninstall the app before it reboots but so far no good.. might have to factory reset
edit2: apparently I'm not fast enough to hit okay for the uninstall.
edit3: YES! I win. I uninstalled faster than towelpieroot could trigger the reboot! whew... took like 20 tries...
Click to expand...
Click to collapse
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
iKrYpToNiTe said:
I'm sorry it caused bootloops for you, I remove 4.4.3 from the OP so others don't try.
Click to expand...
Click to collapse
I --really-- can't believe this isn't getting more attention than this!!! Not to mention more "THANKS" for the OP?!?!
Guys, if you use this method, SHOW SOME APPRECIATION! Five-Hundred-Seven (507) views, as of this posting, and only 7 "THANKS"? Where's the other 500?
EXCELLENT Job, Sir.
I have been having issues using this method. I was already using Pie for several weeks and wanted to try this to survive reboots. As soon as I installed and ran it I actually lost the root that I already had. The Towel Pie Root app would say that I had root access but none of my other apps would agree. I would get the message at the bottom of the screen stating the app was granted super user permissions but then the app would tell me that i don't have root, I tried adaway, xposed, and root checker. I uninstalled SuperSU and switched over to the ClockworkMod SuperUser and that worked for root. The problem that I had after that is that the root apps that I was using no longer work. Adaway shows as disabled and when I try to enable it it fails. The same whit xposed, every time I try to update/install it fails. I removed Towel Pie Root and went back to rooting with Pie and I am getting the same results. Has the Towel Root portion of this changed something that I am now going to have to factory reset?
Edit:
After a few more reboots once TowelPieRoot was removed and starting Pie again from the beginning I now have root as it was with everything working. For now I am just going to keep things the way they were. I have my terminal emulator setup to run the last Pie command on every start so it always attempts to root first. This makes it really easy regain root even if my device does get restarted and I lose root..
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
I like the app.. seems to work great.. but the only issue I have is is the OTA going to be stopped from downloading? I have two moto x, one still on 4.4 and rooted with slap, and a new one on 4.4.2 rooted with this app. below is a shot of what I get when i force check an update with the slapped moto, this is with the 3c_OTA files renamed to .bak
I dont get the same message with the new moto on 4.4.2, what I get is "your moto is up to date" and the same two 3c_OTA files are also renamed to .bak files.
xposed works with gravity
yabbandroid said:
wow thanks, will this work with Xposed framework? I was looking for a simple root method without voiding my warranty, this seems nice, I'm gonna try it, thank yoU!
Click to expand...
Click to collapse
yes, it works. have it running now. make sure that you softboot from within xposed.
i realize this is my first post here, finally decided to sign up ONLY for the reason to thank the OP for this.
I've been frustrated trying to get towel to work come to find out that geohot sold out and replaced the .apk on the site, wow........ then you had something secret for us and it was this thread and release of towelpie, GREAT work and goodjob!
xt1058 worked in 4.4.3!
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
yamaha83 said:
most excellent!!!!!!!!
---------- Post added at 09:16 PM ---------- Previous post was at 08:38 PM ----------
can someone tell me or point me in the direction of how to get the exposed modules up and running. i use this towel root, then open exposed framework installer and hit install/update and get a pop up with some info where the last line says "failed to create a backup or /system/bin/app_process" i hit ok and there is still red dashes under active columns for both App_process and XposedBridge.jar? am i missing a step? the towel root app says "root achieved enjoy" when i use it.
Click to expand...
Click to collapse
You have to do a softreboot in exposed to get it to activate.
wooddale said:
You have to do a softreboot in exposed to get it to activate.
Click to expand...
Click to collapse
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
yamaha83 said:
i tried that? it seems i have root since i can access the system folder with Solid Explorer. but when i open framework installer. hit install/update i get the error, when i softreboot and go it and hit install/update i get the same error. i have the instal set to classic, should it maybe be something different?
Click to expand...
Click to collapse
Were getting off topic here PM me Thanks
Hey all, long time no see. Anyways, I'd like to be able to do quite a few adb commands without actually using adb here locally on the device. So I was curious and started thinking, could you use adb to grant a terminal emulator app (i.e. Termux, the one I use) permissions such as DUMP and WRITE_SECURE_SETTINGS, or whatever else it may need to perform certain commands like clear cache and install apps. I obviously don't have root (Dag on US Carriers). Maybe I don't have a great understanding of what these permissions do? Any help is appreciated.
Unfortunately you cannot just pop into adb and try to give the app the permission, as termux doesn't request it. Termux:API does not as well. I saw somewhere over on Github some guy edited the source of Termux:API and added more APIs to use, I just don't know how to compile an app from source)
Thanks,
Gavin
Craz Basics said:
Hey all, long time no see. Anyways, I'd like to be able to do quite a few adb commands without actually using adb here locally on the device. So I was curious and started thinking, could you use adb to grant a terminal emulator app (i.e. Termux, the one I use) permissions such as DUMP and WRITE_SECURE_SETTINGS, or whatever else it may need to perform certain commands like clear cache and install apps. I obviously don't have root (Dag on US Carriers). Maybe I don't have a great understanding of what these permissions do? Any help is appreciated.
Unfortunately you cannot just pop into adb and try to give the app the permission, as termux doesn't request it. Termux:API does not as well. I saw somewhere over on Github some guy edited the source of Termux:API and added more APIs to use, I just don't know how to compile an app from source)
Thanks,
Gavin
Click to expand...
Click to collapse
Terminal Emulator is the same thing as ADB shell(adb shell, not the normal adb), anything that can be done from PC using ADB shell can also be done using Terminal Emulator app, the commands are the same except the "adb" or "adb shell" part is removed from the command.
For example "adb reboot recovery" would instead be "reboot recovery" or "adb shell dumpstate" would instead be "dumpstate".
Some commands might not work or might need other protocols, parameters or switches added to the command.
But, unfortunately, you can't set Termux or any other app to have access to change or pull anything from system without root, if you don't have root, you're wasting your time. You cant change anything about the system without root unless you have TWRP, it can do whatever it wants to do and the device can't stop it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Terminal Emulator is the same thing as ADB shell(adb shell, not the normal adb), anything that can be done from PC using ADB shell can also be done using Terminal Emulator app, the commands are the same except the "adb" or "adb shell" part is removed from the command.
For example "adb reboot recovery" would instead be "reboot recovery" or "adb shell dumpstate" would instead be "dumpstate".
Some commands might not work or might need other protocols, parameters or switches added to the command.
But, unfortunately, you can't set Termux or any other app to have access to change or pull anything from system without root, if you don't have root, you're wasting your time. You cant change anything about the system without root unless you have TWRP, it can do whatever it wants to do and the device can't stop it.
Click to expand...
Click to collapse
I understand it's the same thing, and I'm not wanting to change anything related to the system. I'm wanting to do commands such as install apps and clear data. It gives me errors when I try and do this, because I don't have permission. If I am understanding correctly, you can decompile an app, add in the appropriate APIs for the permission, and recompile it. This way you won't get an error when you try to give it a permission (adb shell pm grant com.termux android.permission.WRITE_SECURE_SETTINGS). It tells me the app doesn't request this permission.
Craz Basics said:
I understand it's the same thing, and I'm not wanting to change anything related to the system. I'm wanting to do commands such as install apps and clear data. It gives me errors when I try and do this, because I don't have permission. If I am understanding correctly, you can decompile an app, add in the appropriate APIs for the permission, and recompile it. This way you won't get an error when you try to give it a permission (adb shell pm grant com.termux android.permission.WRITE_SECURE_SETTINGS). It tells me the app doesn't request this permission.
Click to expand...
Click to collapse
If you want the app to be able to access those permissions then you need to push the app to /system to make it a system app, apps outside of system can't access those permissions.
After moving the app to system, boot to recovery and wipe only the cache partition(if you have custom recovery, wipe dalvik cache also), then reboot the device.
But, unfortunately, you aren't rooted so it isn't an option for you, you need to root your device.
But even that won't help, see here:
https://stackoverflow.com/questions...-permission-error-even-when-added-in-manifest
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you want the app to be able to access those permissions then you need to push the app to /system to make it a system app, apps outside of system can't access those permissions.
After moving the app to system, boot to recovery and wipe only the cache partition(if you have custom recovery, wipe dalvik cache also), then reboot the device.
But, unfortunately, you aren't rooted so it isn't an option for you, you need to root your device.
Click to expand...
Click to collapse
Take SystemUI Tuner from the Play Store for example, it requires those permissions to do its thing. It does NOT need to be a system app to utilize them, they just need to be granted manually via adb. Greenify does this as well.
As for root, I would if I could. Verizon Note 9 is locked down like Fort Knox.
Craz Basics said:
Take SystemUI Tuner from the Play Store for example, it requires those permissions to do its thing. It does NOT need to be a system app to utilize them, they just need to be granted manually via adb. Greenify does this as well.
Click to expand...
Click to collapse
Yes, some apps can access that permission, but it's built into the app, it isn't just granted via adb or terminal. Read some of the link that I posted above. As far as I knew, accessing secured settings/permissions required root and/or unlocked bootloader, but, things always change. Granted, over the years, things change and trickier things have to be done get mods and apps to do certain things without root, but it's not quite changing/accessing the system.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yes, some apps can access that permission, but it's built into the app, it isn't just granted via adb or terminal. Read some of the link that I posted above. As far as I knew, accessing secured settings/permissions required root and/or unlocked bootloader, but, things always change. Granted, over the years, things change and trickier things have to be done get mods and apps to do certain things without root, but it's not quite changing/accessing the system.
Click to expand...
Click to collapse
Just took a look, strange. Greenify and SystemUI Tuner are considered 3rd party, correct? Maybe it's it's something with their signature? (I don't know much about signatures either)
And yes I'm aware you have to add it into the app, the app requests it and you can grant it via adb.
Think my question is answered now anyway, no lol. Thanks for your responses man.
I plan on rooting my OnePlus 7 Pro when I get it.
I really don't want to have anyone turn Zen mode on (I don't plan on using it at all). It's pretty stupid that OnePlus didn't require authentication before entering Zen Mode (so you'd have to authenticate before Zen actually locks your phone down). Since they didn't do that, did anyone make a mod (magisk or otherwise) which completely nukes the feature?
i'll make one if u want to try it out
I'd love to, although I won't be receiving the 7 Pro for another week probably, I gotta get it forwarded from the US.
I really want that thing disabled. Ideally in a Magisk module or just generally something that won't break SafetyNet (because I use Google Pay)
no prob i'll get it ready
Thank you! I'd recommend making a post on the mods section and linking it here, rather than just giving me the zip, so that everyone could enjoy preventing their friends from bricking their phones!
Plus, if it's a Magisk mod, we can just use the built in applock to secure Magisk, and BAM! Phone secured!
Lirannl said:
Thank you! I'd recommend making a post on the mods section and linking it here, rather than just giving me the zip, so that everyone could enjoy preventing their friends from bricking their phones!
Plus, if it's a Magisk mod, we can just use the built in applock to secure Magisk, and BAM! Phone secured!
Click to expand...
Click to collapse
I would but there is someone already doing a DeBloat Thread and didn't want to step on toes. But I will so some custom ones upon request
I will also send u a link in PM just in case this thread gets lost by the time u get ur phone.
Here is Zen Mode DeBloater Module
you could use pm disable/uninstall to remove applications on current user setup.
doesnt require root
virtyx said:
you could use pm disable/uninstall to remove applications on current user setup.
doesnt require root
Click to expand...
Click to collapse
Would it work if u can't disable
Bradl79 said:
I would but there is someone already doing a DeBloat Thread and didn't want to step on toes. But I will so some custom ones upon request
I will also send u a link in PM just in case this thread gets lost by the time u get ur phone.
Here is Zen Mode DeBloater Module
Click to expand...
Click to collapse
Judging by this conversation, I assume that it's just a system app then? I just don't know because I don't have my OP7P yet.
Lirannl said:
Judging by this conversation, I assume that it's just a system app then? I just don't know because I don't have my OP7P yet.
Click to expand...
Click to collapse
Correct it's located in /system/app/OPBreathMode
Bradl79 said:
Would it work if u can't disable
Click to expand...
Click to collapse
you need an app like "app inspector" or "package name viewer" something that can get you the full name of the folder of the apk.
once you do that
in windows adb with usb debugging on
adb shell pm disable-user --user 0 com.whatever.whatever
and then to enable again
adb shell pm enable <package_to_enable>
deleted
I did that using adb, but instead of disable i uninstalled it.
I just froze it in TiBackup
Same here, Froze it with TB...
I tried to do it through termux with magisk module debloater(termux emulator) but couldn't find it looked through all sections but it's not in there any ideas?