jefftheworld's Kobo Vox Guides

[kcarscadden]

Oddly enough, grep doesn't appear to be present on my Vox. I presume it should be in /system/bin?

I downloaded busybox installer and used busybox grep instead.

Where might one get grep, since it would be easier to use it directly?


Keith

[PeterT]

Originally Posted by kcarscadden

Oddly enough, grep doesn't appear to be present on my Vox. I presume it should be in /system/bin?

I downloaded busybox installer and used busybox grep instead.

Where might one get grep, since it would be easier to use it directly?


Keith

Not being an Android user (yet) have you looked at the BusyBox FAQ:

Installing Busybox

If the Busybox executable is renamed to one of the commands it supports, it will act as that command automatically:

 ln -s busybox pwd
 ./pwd

This allows you to create a bunch of symlinks or hardlinks to the Busybox executable, add them to your $PATH, and let a single Busybox provide a standard set of command line tools. The --list option to busybox gives the list of supported commands in an easily scriptable form. (The --list-full option gives full paths, such as usr/sbin/test, to help create a Busybox-based root filesystem.)

 mkdir bbdir
 for i in $(busybox --list)
 do
   ln -s busybox bbdir/$i
 done

To launch Busybox's built in command shell with the $PATH giving access to just Busybox's built-in commands:

 PATH=$(pwd)/bbdir bbdir/sh

[0b3d1ah]

Great guides!

But I have an issue....

I must type "SU" in connect bot or I get "permission denied'.

Once I type "SU", then if I enter your command, I get : "grep: not found"

Please help!

[jefftheworld]

Originally Posted by 0b3d1ah

Great guides!

But I have an issue....

I must type "SU" in connect bot or I get "permission denied'.

Once I type "SU", then if I enter your command, I get : "grep: not found"

Please help!

Try "su", small case. If that still doesn't work, then you've got one of two problems. Either Superuser isn't installed (you did root your Vox, right?) or it's been set to automatically deny permission to your terminal program. In which case you just open Superuser, double tap on the entry for your terminal of choice and hit "forget".

[0b3d1ah]

Originally Posted by jefftheworld

Try "su", small case. If that still doesn't work, then you've got one of two problems. Either Superuser isn't installed (you did root your Vox, right?) or it's been set to automatically deny permission to your terminal program. In which case you just open Superuser, double tap on the entry for your terminal of choice and hit "forget".

Yes, I rooted the Vox and connect bot appears in Super User with allow permissions. I removed it and the re authorized it when it asked. I still get the exact same results. Not sure where I am going wrong. I have included a couple of screen shots.

[kcarscadden]

Originally Posted by 0b3d1ah

Yes, I rooted the Vox and connect bot appears in Super User with allow permissions. I removed it and the re authorized it when it asked. I still get the exact same results. Not sure where I am going wrong. I have included a couple of screen shots.

grep is not included on the Vox. Install Busybox - it includes grep. Busybox is one of the apps included in Jeff's best apps in thread jefftheworld's Best App Package!


Keith

[jefftheworld]

Yeah, it's part of busybox. Either way, the grep commands are not required. It's just as confirmation that you're doing it right.

[0b3d1ah]

Cool thanks!

It worked without grep :-)

My Vox is now free of bloatware. Thanks for the great guides and all the help.

[mr_nobody]

Just a quick question re: rooting. If you root the device, can kobo software updates still be installed? Will the device need to be re-rooted after installing such an update as the imminent one we are hearing about? Thanks.

[mr_nobody]

Hate bumping my own post but does anyone know the relationship between rooting and the kobo updates? Thanks.

[hieronymos]

Originally Posted by mr_nobody

Hate bumping my own post

Vampire, behold! Don't you eat that kitten!

Just run Gingerbreak again.

[mr_nobody]

Thanks a lot, hieronymos, that makes sense!

[Haesslich]

Dunno, but I generally unroot devices or unjailbreak before I run any firmware updates, to avoid issues with system files not being upgraded to the correct version. If you used Gingerbreak, just open the app, click "Unroot Device", wait for it to restart, then apply the update and use the 'Root Device' option once the updates are done.

[Jesslynne]

I didn't think of that before updating. I had to reroot and remove all the apps I had removed before update.

[mr_nobody]

Yeah, quite possibly it is safer to "unroot" prior to an update. That's annoying that you have to re-remove apps after an update though.