Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,779,023 Members 44,100 Now Online
XDA Developers Android and Mobile Development Forum

Busybox for Tizen Gear 1 + Gear 2

Tip us?
 
.Killabyte
Old
#1  
Junior Member - OP
Thanks Meter 1
Posts: 5
Join Date: May 2014
Default Busybox for Tizen Gear 1 + Gear 2

Sorry if this is known but I just saw this today and though some people might like to know. There's a link to Busybox within.
tizenexperts.com/2014/06/developers-install-busy-box-on-your-root-tizen-samsung-gear-smartwatch
 
lazer9
Old
#2  
lazer9's Avatar
Senior Member
Thanks Meter 417
Posts: 1,582
Join Date: Oct 2007
Location: Hermitage, PA

 
DONATE TO ME
Quote:
Originally Posted by .Killabyte View Post
Sorry if this is known but I just saw this today and though some people might like to know. There's a link to Busybox within.
tizenexperts.com/2014/06/developers-install-busy-box-on-your-root-tizen-samsung-gear-smartwatch
Can't figure out the sdb instructions to actually install it?
Verizon Galaxy S4 w/ Safestrap Recovery v3.72 & ★[ROM][AUG 21] Hyperdrive RLS18 KitKat ║ Tweaks ║ Only the Best! ║ ★ w/ NC2 Bootloader -On Stock Side!...

Gear w/ Tizen NE9-Rooted

Asus Transformer TF300T : ★★★[TF300 KitKat 4.4.4][CROMBi-kk RC2][F2FS | DATA2SD | ROM2SD | CM11 ][AUG 11]★★★

 
.Killabyte
Old
(Last edited by .Killabyte; 28th June 2014 at 04:08 AM.) Reason: added detail
#3  
Junior Member - OP
Thanks Meter 1
Posts: 5
Join Date: May 2014
Quote:
Originally Posted by lazer9 View Post
Can't figure out the sdb instructions to actually install it?
Yeah I got the same issue here so apologies. I pushed the file to a couple directories and did "root on" then "sdb shell" to make sure but when it goes to install it complains about needing something like 188kb free space (the package is half that).

So yeah obviously a regular sdb install won't work and it seems I don't know which directory to have the package in when I try to install but that's all I got.

Recreation steps:
1) Ran sdb devices until device was listed (had usb debugging enabled on the gear being rooted running the original Gear Tizen release)
2) Ran sdb root on again to be paranoid
3) Ran sdb shell
4) Copied the file in to /home with "sdb push filename /home". Later on I tried the same thing using the Tizen SDK explorer function to a few more directories since that has drag and drop.
5) Ran the install command it has (rpm -i busybox-1.17.1-2.3.armv7l.rpm)
6) Got free space error. Grr'd.

Here's some of my log excluding the first part:
C:\tizen-wearable-sdk\tools>sdb push busybox-1.17.1-2.3.armv7l.rpm /home
pushed busybox-1.17.1-2.3.armv7l.rpm 100% 75KB
1 file(s) pushed. 0 file(s) skipped.
busybox-1.17.1-2.3.armv7l.rpm 1172 KB/s (76839 bytes in 0.064s)

C:\tizen-wearable-sdk\tools>sdb shell
sh-3.2# ls
bin dev home lost+found opt run smack system var
boot efs initrd media proc sbin srv tmp
csa etc lib mnt root sdcard sys usr
sh-3.2# cd home
sh-3.2# ls
abuild app busybox-1.17.1-2.3.armv7l.rpm developer root
sh-3.2# rpm -i busybox-1.17.1-2.3.armv7l.rpm
installing package busybox-1.17.1-2.3.armv7l needs 188KB on the / filesystem
The Following User Says Thank You to .Killabyte For This Useful Post: [ Click to Expand ]
 
.Killabyte
Old
(Last edited by .Killabyte; 29th June 2014 at 11:56 PM.)
#4  
Junior Member - OP
Thanks Meter 1
Posts: 5
Join Date: May 2014
Ok so someone clued me in to the missing mount command and now I can get it installed! But like the article states the only advantage I see immediately is a working VI from sdb shell. There's no icon created in the launcher. The only way I know it's installed is when I run the command it tells me and busybox is in the /bin directory. Now some more adventurous people may Google and find out how to manually install busybox packages so for those let me know if you find anything cool!

Here's the log. This was on the initial Tizen release with the root package installed.
C:\tizen-wearable-sdk\tools>sdb devices
* daemon not running. starting it now on port 26099 *
* daemon started successfully *
List of devices attached
412ba0e141019466 device SM-V700

C:\tizen-wearable-sdk\tools>sdb root on
Switched to 'root' account mode

C:\tizen-wearable-sdk\tools>sdb shell
sh-3.2# su
sh-3.2# mount -o remount,rw /
//The line above was the missing step.
sh-3.2# exit

//Then I go back to command prompt to push the package again to root.
C:\tizen-wearable-sdk\tools>sdb push busybox-1.17.1-2.3.armv7l.rpm /
pushed busybox-1.17.1-2.3.armv7l.rpm 100% 75KB
1 file(s) pushed. 0 file(s) skipped.
busybox-1.17.1-2.3.armv7l.rpm 1316 KB/s (76839 bytes in 0.057s)

C:\tizen-wearable-sdk\tools>sdb shell
sh-3.2# mount -o remount,rw /
sh-3.2# rpm -i busybox-1.17.1-2.3.armv7l.rpm
package busybox-1.17.1-2.3.armv7l is already installed
sh-3.2# mount -o remount,rw /
sh-3.2# reboot
Rebooting.

The guy that gave me the said to do this again after. I imagine you might need to do this anytime you try to play around with Busybox if you don't see files listed when you do an "ls -a" or get permission errors:
sdb root on
sdb shell
sdb mount -o remount,rw /
exit

Hope this helps someone.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes