GT-I9300 with siyah kernel 1.5. Trying to enable swap partition by using hardswap mod:http://forum.xda-developers.com/showthread.php?t=1814311. But after I installed terminal emulator, there's no free command. The terminal displays "/system/bin/sh: free: not found ".
Another question is that when I was installing the zip in cwm, one line of the output was "script successfully installed to init.d", but I can't find that folder at all. Where is it?
Try installing busybox. Download an app that does this by searching for "busybox" on the market.
Stericson's (don't know if I spelt that right) or JRummy's busybox installers should be fine.
Sent from my GT-I9300 using xda app-developers app
zhshr said:
Another question is that when I was installing the zip in cwm, one line of the output was "script successfully installed to init.d", but I can't find that folder at all. Where is it?
Click to expand...
Click to collapse
Look in: /system/etc :highfive:
Related
I've seen many posts saying you can run zip files designed for CWM from terminal emulator. I've tried this but I must not be doing it right. Can someone give me a sample command line sequence of what you type to run it? Do you use the full file name with the .zip extension included?
Sent from my SCH-I500 using XDA App
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
eastwood1 said:
I am rooted but i have been reading on installing a recovery. I don't have a sd card at the moment so not sure if i can use ADB to install a recovery. Why cant i just install recovery through Rom Manager?
Click to expand...
Click to collapse
Someone with more knowledge will need to chime in, but I I'd bet the build we are using isn't official, and probably can't be installed through Rom Manager. Give it some time, eventually things will work as normal
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
And you can use the internal storage to copy over the recovery. I used terminal emulator and the internal memory when I did mine.
Click to expand...
Click to collapse
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
eastwood1 said:
Can you explain to me how you went about installing the recovery with only internal storage? I would like to give that a try but not sure the best way to go about it. What commands to use and such, thanks.
Click to expand...
Click to collapse
To all,
I couldn't be bothered with learning ADB, but wanted a custom recovery on my SIII ... maybe you can relate?
Here's the easiest way to do it -- and you don't even need a computer!!! You do, however, already need to be rooted before you can use this method ...
Download your recovery of choice (.. as of this writing, I think there are two: CWM and TWRP ..) and make sure you place a copy in the root drive of your sdcard. Rename it recovery.img, if you want to follow the terminal directions listed below ...
Then, download a terminal emulator onto your device (I use Better Terminal Emulator Pro, which is a paid app) and fire it up.
Once in the terminal emulator, type the following commands one line at a time, waiting after each line for the appropriate prompt:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
# reboot recovery
Your device should then boot into the custom recovery, which serves as immediate confirmation that you did things correctly.
I just used this method to install birdman's twrp8.img to my SIII and it worked like a charm.
http://forum.xda-developers.com/showthread.php?t=1764398
I dont think that will work. Notice the command says sdcard.
The internal memory on the sgsiii is labeled sdcard for whatever reason. The external sdcard slot is under mnt/extsdcard in root explorer if that helps.
Sent from my SGH-T999 using xda premium
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
You need to be rooted and have a "su" command. Typical "rooted" roms include supersu , or equivalent, and busybox (which provides the basic Linux commands). I would install super super and busybox from Google play and try again.
You need the SU command to switch to root user in the shell to have the rights to use dd to overwrite the recovery partition.
I can confirm that the dd command works as that is how I loaded cwm on my s3.
Sent from my SGH-I747M using xda app-developers app
eastwood1 said:
Ok i open Better terminal emulator Pro and it has
/ $ .. when i add in the SU it says
bash: -c: command not found
what am i doing wrong?
I have downloaded and renamed the TWRP.IMG to recovery.img
Click to expand...
Click to collapse
See if this helps.
http://forum.xda-developers.com/showthread.php?t=1739426
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Pompsy said:
For what its worth the reason ROM manager doesn't work is because there is not an official CWM Recovery out for the Verizon S3. We are using the Sprint Recovery
Click to expand...
Click to collapse
There's no official CWM Recovery for any US versions of the GS3, Sprint included. The only official GS3 recovery available is for the international version. The one we're all using right now (I believe) was built by Team Epic. They're historically Sprint devs and so they built it for the Sprint version; however, as you know it works on more than just the Sprint version. Eventually, I'm sure there will be official recoveries direct from Koush.
Personally, I prefer TWRP (bettery touch control layout and options such as compression to save space), but that too is a work in progress.
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.
[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
Hello!
I have flashed my SGS-I9100 successfully with CM11 M3 (Version 11-20140210-SNAPSHOT-M3-i9100).
Now, I want to install app "OpenVPN Settings" that is depending on a specific binary openvpn.
In order to install this binary, the developer provides another app "OpenVPN Installer".
The issue with CM11 is that this installer app cannot set /system (and its related partition) to rw mode in order to put the binary to /system/xbin.
In /system/xbin another binary file "busybox" is located.
I have attached a screenshot displaying the app log.
Question:
Is there a workaround e.g. to manually set /system to rw mode and then complete the installation?
If yes, how would that realised?
Or are there other options to fix this issue?
THX
Yes with root explorer. Don't forget to set root in phone settings.
Sent from my GT-I9300 using XDA Premium 4 mobile app
andrewwright said:
Yes with root explorer. Don't forget to set root in phone settings.
Sent from my GT-I9300 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
THX
Issue solved.
With this I was able to install on cm11 M5 on GNex
https://code.google.com/p/android-openvpn-installer/issues/detail?id=23#c10
Step by step please.
msfcyber said:
Step by step please.
Click to expand...
Click to collapse
uninstall OpenVPN installer you've installed from play store
download this OpenVPNInstaller-debug.apk
install it manually (from download folder tap on the .apk file, if you can't do it google for "installing apk")
run the OpenVPN Installer you've just installed
install openvpn with default options
done
you can use then OpenVPN Settings
penzoiders said:
uninstall OpenVPN installer you've installed from play store
download this OpenVPNInstaller-debug.apk
install it manually (from download folder tap on the .apk file, if you can't do it google for "installing apk")
run the OpenVPN Installer you've just installed
install openvpn with default options
done
you can use then OpenVPN Settings
Click to expand...
Click to collapse
hi Penzoiders
I'm having the very same problem but cannot download the apk above, is it possible you upload it somewhere again???
Many thanks!!!
karmacoma92 said:
hi Penzoiders
I'm having the very same problem but cannot download the apk above, is it possible you upload it somewhere again???
Many thanks!!!
Click to expand...
Click to collapse
the file is still there
this is the relative post
https://code.google.com/p/android-openvpn-installer/issues/detail?id=23#c10
this is the link of the file itself:
EDIT: the file link is broken if you post it here... you have to download from the google code website link here above
downloaded! I will try it right now and let you know
Thanks!
Edited: I was able to install it properly and the OpenVPN Settings finds the setting however I have to fix something in my config since it does seem to work, will try it later....
Many thanks again
I wonder why is this one working, is it installing the binary in a different way??