Busybox HTC one - AT&T HTC One (M7)

[Q]how do I install busybox for att HTC one. Can I just go through the playstore?
Sent from my HTC One using XDA Premium App

-Epix- said:
[Q]how do I install busybox for att HTC one. Can I just go through the playstore?
Sent from my HTC One using XDA Premium App
Click to expand...
Click to collapse
Yes, But you need to be on a kernel that disables write protection to the /system partition. If you're using the stock kernel (even if you are rooted) you won't be able to install anything to the system

Alright. So I need to find. Tutorial for installing a custom kernel. Has there been any down sides to installing them yet. I'd hate to brick my one.
Sent from my HTC One using XDA Premium App

-Epix- said:
Alright. So I need to find. Tutorial for installing a custom kernel. Has there been any down sides to installing them yet. I'd hate to brick my one.
Sent from my HTC One using XDA Premium App
Click to expand...
Click to collapse
No, no real downsides. There is a stock kernel floating around and the only thing that's different than what's on your phone now is the write protection has been removed

Excellent Ok so I have searched the forums and I find some things that say kernel but could you point me to a link.
Sent from my HTC One using XDA Premium App

busybox
in my oppinion you don't need busybox on the new kernel because obviosly everything you need from busybox is located inside
system/bin & system/xbin or some similar applets for the one busybox does have
just download terminal emulator "you'll need root access first" type these codes:
Code:
#su
#cd system/bin
#ls
for more applets just type:
Code:
#su
#cd system/xbin
#ls
for me i find s-on and selinux in general very helpful .. specially in kernel protection if you make a deadly mistake that cause system faliure and lose your IMEI and whatever ... not anymore on the new kernel .. i just hope they fix wifi connection issue .. other than that ... i pefere htc one on any new samsung devices with needless hardware and annoying software like knox

i changed my mind ... its so not busybox at all on the system/bin !! its like apps binaries that used by applications to do its perpose
but i dont want to turn my seLinux off so is there a way to install busybox binaries on CWM like su binary and rooting process ??
EDIT : i was wondering why does busybox shutting down after trying to install applets on device so i entered recovery mode , and using adb shell there i found out the applets works fine there !!!
so i looked inside bin and sbin directories on recovery mode .. and they was located inside /sbin on recovery mode
just to let you know sbin recovery i believe is like another user .. maybe the root user if we looked to it as a linux system .

Busybox on rail
At Google play .... It installe busybox at recovery

Related

detecting rooted devices

does anybody know if there's a way to block an app fr detecting that your phone is rooted, i was trying to redeem my code for my digital copy to download fast five on my phone using pocket BLU, once it gets ready to download it let's me knw that it detected that my phone was rooted n doesn't let me download, i also had the same problem with blockbuster before I was rooted I purchased some movies but after I was rooted tried to go back to my movies n. same thing, detected my device was rooted... I was wondering if there's a way or hack that we can do to not make it detectable as being rooted, thanx
Sent from my PG86100 using XDA App
do you have the Superuser app auto allow root requests or do you have to manually allow each time?
ozkaya said:
do you have the Superuser app auto allow root requests or do you have to manually allow each time?
Click to expand...
Click to collapse
everytime u get an app that request root user permission I have to allow, it doesn't allow automatically but once I have aloud an app I don't have to do it again
You have to delete the root detection in some smali files to remove it.
私のEVO 3Dから送信される
Flip35 said:
does anybody know if there's a way to block an app fr detecting that your phone is rooted, i was trying to redeem my code for my digital copy to download fast five on my phone using pocket BLU, once it gets ready to download it let's me knw that it detected that my phone was rooted n doesn't let me download, i also had the same problem with blockbuster before I was rooted I purchased some movies but after I was rooted tried to go back to my movies n. same thing, detected my device was rooted... I was wondering if there's a way or hack that we can do to not make it detectable as being rooted, thanx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
a temporary fix:
1) rename /system/bin/su to anything else, example: /system/bin/jk. i prefer to use adb shell for the renaming.
2) run the application which looks for root
3) when done running the application which has root detection, rename /system/bin/jk back to /system/bin/su.
this should work because the root detection method most applications use is to only check if a file named /system/bin/su is present. if that file is present, they consider the phone rooted. they usually don't even attempt to open the /system/bin/su which would trigger the superuser apk, they usually only look to see if the /system/bin/su file *exists*.
hope that helps!
joeykrim said:
a temporary fix:
1) rename /system/bin/su to anything else, example: /system/bin/jk. i prefer to use adb shell for the renaming.
2) run the application which looks for root
3) when done running the application which has root detection, rename /system/bin/jk back to /system/bin/su.
this should work because the root detection method most applications use is to only check if a file named /system/bin/su is present. if that file is present, they consider the phone rooted. they usually don't even attempt to open the /system/bin/su which would trigger the superuser apk, they usually only look to see if the /system/bin/su file *exists*.
hope that helps!
Click to expand...
Click to collapse
after doing this is not gonna mess anything up with me been rooted, i'm still gonna b able to flash roms n all that?
joeykrim said:
a temporary fix:
1) rename /system/bin/su to anything else, example: /system/bin/jk. i prefer to use adb shell for the renaming.
2) run the application which looks for root
3) when done running the application which has root detection, rename /system/bin/jk back to /system/bin/su.
this should work because the root detection method most applications use is to only check if a file named /system/bin/su is present. if that file is present, they consider the phone rooted. they usually don't even attempt to open the /system/bin/su which would trigger the superuser apk, they usually only look to see if the /system/bin/su file *exists*.
hope that helps!
Click to expand...
Click to collapse
joey good **** man, u da man, got it downloading my movie now so it worked
Flip35 said:
does anybody know if there's a way to block an app fr detecting that your phone is rooted, i was trying to redeem my code for my digital copy to download fast five on my phone using pocket BLU, once it gets ready to download it let's me knw that it detected that my phone was rooted n doesn't let me download, i also had the same problem with blockbuster before I was rooted I purchased some movies but after I was rooted tried to go back to my movies n. same thing, detected my device was rooted... I was wondering if there's a way or hack that we can do to not make it detectable as being rooted, thanx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
There's an app on the market "temp root remover" this works great for me..is much easier...
Sent From My HTC EVO 3D ROOTED
luisrod03 said:
There's an app on the market "temp root remover" this works great for me..
Sent From My HTC EVO 3D ROOTED
Click to expand...
Click to collapse
so we can go unroot n root pretty easy?
Flip35 said:
so we can go unroot n root pretty easy?
Click to expand...
Click to collapse
Yes....on one click
Sent From My HTC EVO 3D ROOTED
luisrod03 said:
Yes....on one click
Sent From My HTC EVO 3D ROOTED
Click to expand...
Click to collapse
iight thanx ill give itt a shot
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
larsdennert said:
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
Click to expand...
Click to collapse
Try the app I put on the previous post that's going to give root access again...
Sent From My HTC EVO 3D ROOTED
larsdennert said:
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
Click to expand...
Click to collapse
yes try the app that luis posted it works flawless, i went in blockbuster and pocket BLU and downloaded all my movies without any issues got don't when to temp unroot remover one click n. back to normal, that app is definitely a life saver, thanx luis
Flip35 said:
yes try the app that luis posted it works flawless, i went in blockbuster and pocket BLU and downloaded all my movies without any issues got don't when to temp unroot remover one click n. back to normal, that app is definitely a life saver, thanx luis
Click to expand...
Click to collapse
you welcome.....
Ok tried to watch fast five from the market, got video playback not supported on rooted devices error 49. Tried to find "temp root remover" in market... No results... Tried renaming system/bin/su still wont work... Ideas?
Ok got the temp root remover but is not working... Help?
Edit... Found a fix. Must be a synergy thing cause got the app to work in viperROM... guess synergys just heavyhanded with the tweaks.
Sent from 3D A.W.E.S.O.M-O
motoelliot said:
Ok tried to watch fast five from the market, got video playback not supported on rooted devices error 49. Tried to find "temp root remover" in market... No results... Tried renaming system/bin/su still wont work... Ideas?
Ok got the temp root remover but is not working... Help?
Edit... Found a fix. Must be a synergy thing cause got the app to work in viperROM... guess synergys just heavyhanded with the tweaks.
Sent from 3D A.W.E.S.O.M-O
Click to expand...
Click to collapse
Yeah synergy is cool rom but the bad thing is that when trying to change system files is not going to let u....
Sent From My HTC EVO 3D ROOTED
Flip35 said:
after doing this is not gonna mess anything up with me been rooted, i'm still gonna b able to flash roms n all that?
Click to expand...
Click to collapse
as you found out, the temporary fix won't "mess" with anything as long as you restore the su binary back to its default name.
larsdennert said:
After you rename the file you lose root. How do you regain root privilege to rename the file? Do you chmod? How do you mount rw?
Click to expand...
Click to collapse
you don't lose root by renaming the su binary. by renaming the su binary, you're ONLY changing the name of the su binary. the su binary does not require itself to be named "su" to execute properly. of course, make sure not to run chmod and remove the setuid bit on the file.
command: mv /system/bin/su /system/bin/jk
now, instead of having to type "su" for root, you'll type "jk" or whatever the new name of the su binary is.
also, you can configure adb shell to always drop to root access by toggling the ro.secure value, either 0 or 1, in the default.prop file which is stored inside the ramdisk of the boot.img kernel file. many custom kernels toggle this setting so adb shell always drops to root, even if no "su" binary exists on the system.
worse case, if for some reason you make a mistake, you can always boot into the custom recovery which provides root access via adb shell (ro.secure is toggle as such in the ramdisk of the recovery custom kernel) and setup root access again from there.
hope the additional information and technical details help!
Temp Root Remover
After using this app or manually renaming in Terminal Emu. Root is still detected by Pocket Blu. Any suggestions?
senjam1 said:
After using this app or manually renaming in Terminal Emu. Root is still detected by Pocket Blu. Any suggestions?
Click to expand...
Click to collapse
Really??? I've been using the app fr the market temp unroot remover n it works

[Q] Kernal/Busybox questions

Is busyBox built into CWM recovery kernals? is this common practice?
if so, and "I believe it is" How can I update my busyBox Version?
The experience Im having is on stock 2.3.4 when I check with root checker pro .apk it shows BusyBox Version 1.19.2cm71 installed in /sbin/ So I try to update to BusyBox version 1.19.4stericson via his BusyBox installer .apk Then check with Root checker Pro .apk and all is well Untill I reboot My phone Imediatly after reboot Root cheker shows the old Busy Box version again.
So I geuse what Im asking for is verification basicly.
Is there not a tool to incorporate CWM into existing stock recovery like the one used for the OG transformer Tab?
By the way to all comers who would like to bash my noobness Bring it!
I say this because I can learn more from the bashing than from no response/answer at all.
That being said Thanks to the Devs that do chime in with direct, and helpful responses. Its much appreciated by me as this is my main source of refferance for android learning. My post count is so low because I read !
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Pirateghost said:
busybox is a binary located in either /system/bin or /system/xbin
its not something included in a kernel
Click to expand...
Click to collapse
Thanks for your response, but I Know what busybox is and where its supposed to be but if you have CWM recovery do me a favor and check your "/sbin" folder on "root of phone" not in the "/system" folder there you will see "busybox" in "/sbin". Also there is an app called "root checker" by Joey something or other if you run this app and swipe to the left you'll see the screen verify busybox click it and it will tell you where its installed and what version is installed.
I originaly thought same as your reply and its true as long as you install busybox While using stock recovery. Meaning if I install busybox to "/system/xbin" with CWM recovery installed my newer busybox version won't stick. (Only good until reboot)
I've completely reverted to stock 2.3.4 GB and checked the /sbin folder before and after installing codeworkx 5.0.2.3 CWM revovery and These were my findings.
However on the skyRocket I do not seem to have this problem I believe this is why.
Pirateghost said:
skyrocket has separate recovery partition.....their CWM isnt injected into kernel....
Click to expand...
Click to collapse
While Great for My "I727" that doesnt help me on my "I777"
rdannar said:
If you newwest busybox then search and find a cwm zip for root and flash it... Easiest way..
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks but not at all what I was talking about.
Phatboyj420 said:
Thanks but not at all what I was talking about.
Click to expand...
Click to collapse
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
rdannar said:
if it doesn't stick you probably have two versions... One in bin and one in xbin. delete old one. flash in cwm so it corrects symlink to newwest busybox. your syymlink are probably not correct. The install script changes the symlink of the file.. That is why you use cwm to flash
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thanks again but your still off please re-read O.P.
Ive done all that you suggest. in doing so I,ve learned that when I manualy delete busybox from "/sbin" it gets re-written upon reboot.
The only Rom with CWM recocery That I've found this not to be true in is "task650's" latest ICS release UCPLC5, It does initialy install busybox but not to
"/sbin" and it does'nt get re-written on every reboot. Thus allowing the users busybox update to stick. Thanks for that Task.
I experience the same troubles with GB SpeedMod Kernel v2.21 which includes CWM 5.0.2.3, so I searched around and found this thread.
Running StockROM (GB 2.3.6) the updates of BusyBox (have it in /system/xbin) work perfectly, no second version anywhere (/system/bin or /sbin).
Flashing SpeedMod Kernel with CWM delivers a second copy of BusyBox into /sbin, where busybox itself is a symlink to recovery in the same directory. Bad enough that an update to the latest BusyBox version seems to be fine but doesn't stick after reboot (as mentioned by Phatboyj420, for clarification: the update in /system/xbin sticks but the update or deletion of BusyBox in /sbin is reverted as part of kernel during reboot), so e.g. Ghost Commander shows some errors (owner and file permissions) which are related to this mixed version status and disappear after updating BusyBox (till the next reboot).
To confirm that CWM delivers BusyBox to /sbin I looked into the source of SpeedMod v2.21 (find it here!). Just unpack it and have a look into /initramfs/out/sbin.

[Q] Busybox installed into both /bin and /xbin?

I have BB 1.18.4 still from the old doomlord kit, installed into system/xbin, and I noticed that some mods/tweaks/apps require it installed in /xbin, while others need it into /bin. So my question is, if I use Busybox Installer to install the 1.20.2 to both folders, will it harm my device having two busyboxes installed at the same time?
You could install it in xbin and then symlink it to bin.
Sent from my Nexus 7
Err, how to symlink it? I find something like console commands searching around, but i don't know where to put them =(
I think you have some learning to do.
You can install busybox in both directories. The order of directories in $PATH will prevent issues with having it installed twice.
Sent from my Nexus 7
Thanks, I'll go directly with the double install then.
Just one more thing that just happened, I usually use Busybox Installer for that, but when I select the installation for the right version, before dowloading the install files, it stops and says I have a bad internet connection, even tho my 3G works perfectly. Did anyone else experience this?
BillGoss said:
I think you have some learning to do.
You can install busybox in both directories. The order of directories in $PATH will prevent issues with having it installed twice.
Sent from my Nexus 7
Click to expand...
Click to collapse
Yeah, I know this is old thread, but I have some related questions: if busybox is already installed in system/bin by kingroot, why should I install a binary update in system/xbin as busybox installer wants to do by default? If it is in both paths, which one is going to do the job? or... Why do I actually want to have two busybox copies in two separate directories if I "can" have just one? And last: most people suggest to install busybox in system/xbin, so why kingroot choose to do it in system/bin?...
Man quetion.. I'm curious what the answers are to these please!..

[Q[ Busybox mixup

Hey,
So a few months ago, I installed either an older version of Busybox, or the newer version I installed never stuck. Basically, I have two folders that contain the busybox commands: /sbin and /system/xbin. In Terminal Emu., when I enter a Busybox command, it seems to only acknowledge the older folder (/sbin). eg if I type in "busybox ifconfig..." or "busybox ipconfig...." I'm told that there's no such command, in so many words. How do I go about fixing this?
Would it mess anything up if I moved the contents of the newer folder (/system/xbin) into /sbin ?
Also, should there be a busybox file located anywhere (ie a file in root that's executed when "busybox" is typed into Term. Emu?) I can only locate the one in the internal sdcard directory ("busybox-stericon")
Thanks
bump
Alot of people are having the same issues on the reviews on gapps. Might be an error with gapps
Sent from my YP-G70 using xda app-developers app
alljokingaside said:
Hey,
So a few months ago, I installed either an older version of Busybox, or the newer version I installed never stuck. Basically, I have two folders that contain the busybox commands: /sbin and /system/xbin. In Terminal Emu., when I enter a Busybox command, it seems to only acknowledge the older folder (/sbin). eg if I type in "busybox ifconfig..." or "busybox ipconfig...." I'm told that there's no such command, in so many words. How do I go about fixing this?
Would it mess anything up if I moved the contents of the newer folder (/system/xbin) into /sbin ?
Also, should there be a busybox file located anywhere (ie a file in root that's executed when "busybox" is typed into Term. Emu?) I can only locate the one in the internal sdcard directory ("busybox-stericon")
Thanks
Click to expand...
Click to collapse
All files in /sbin are part of the kernel. Changes to this folder will be lost after a reboot. The only busybox you need is the one in sbin. It will be run when you type commands in terminal. Any other busybox should be deleted to avoid conflicts
Sent from my Galaxy Nexus using xda app-developers app
and I'll assume, then, that copying over the files from /system/xbin to /sbin won't cause any conflicts, since the files in sbin are like a subset of /system/xbin. thanks a bunch!
edit: blerg. apparently, I just learned to read. changes to /sbin will be lost
is there anyway that you're aware of to modify that folder? sbin's is missing a few useful commands eg ifconfig, iplink, etc
alljokingaside said:
and I'll assume, then, that copying over the files from /system/xbin to /sbin won't cause any conflicts, since the files in sbin are like a subset of /system/xbin. thanks a bunch!
edit: blerg. apparently, I just learned to read. changes to /sbin will be lost
is there anyway that you're aware of to modify that folder? sbin's is missing a few useful commands eg ifconfig, iplink, etc
Click to expand...
Click to collapse
It's the initramfs in the kernel, so you'd have to recompile it.
Sent from my Galaxy Nexus using xda app-developers app
Mevordel said:
It's the initramfs in the kernel, so you'd have to recompile it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
thanks for all the support. i suppose the initramfs is a file. Will decompiling/recompiling it w/ apkmultitools do the trick? I realize that this question's mad noobish, but hey- it is what it is.
thanks again
alljokingaside said:
thanks for all the support. i suppose the initramfs is a file. Will decompiling/recompiling it w/ apkmultitools do the trick? I realize that this question's mad noobish, but hey- it is what it is.
thanks again
Click to expand...
Click to collapse
I mean it's integrated into the kernel when the kernel is compiled. you'd have to recompile the kernel.
Sent from my Galaxy Nexus using xda app-developers app
figures.
ok- so when you type in a busybox command (eg ifconfig), does it respond? Busybox, when installed, adds commands and links it when you type it in in the terminal, so, I suppose my follow up question is - how do i re-link the commands to the proper path?
on second thought, this problem may have occurred roughly when I flashed paranoid android, reverted (no camera=not a daily driver) and re-flashed Entropy's kernel. additionally, root in terminal emulator, ever since, has shown "sh-3.2$" at the prompt. (PATH=/data/local/bin:$PATH)
for some reason, I'm starting to think it wasn't always this way.

Busybox Update

Hello i have some problems while updating Busybox on my phone
i'v tried with theese two applications.
https://play.google.com/store/apps/details?id=stericson.busybox&feature=search_result
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&feature=search_result
but after reboot busybox fall back to the old version "1.16.2" (more details on the attachment)
sorry for my bad english, and thanks for help
ps: i tried to install on bin, and xbin
Busybox is embedded in ne kernels, so every reboot you reload the old version.
To fix permanently, decompile the kernel IMG and update busybox in the ramdisk
Sent from my MT11i using xda app-developers app

Categories

Resources