View Single Post
Old 05-01-2012, 08:26 AM   #3
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by knc1 View Post
Note 2: For one of the commands that now returns "applet not found" try (here, using ls as an example):
/bin/busybox ls
And then tell us if that avoids the "applet not found" message.
The above request is the first of a series of requests to walk you through fixing the damage done to your system files.
From your original post, it reads as if you missed screwing up: /sbin, /usr/bin, and /usr/sbin

The Busybox in the K3, version 3.2.1 firmware is a static build - perhaps you have lucked out and the build in version 3.3 is also a static build.

The next request(s) will be dependant on the result you get from the first one above.

Last edited by knc1; 05-01-2012 at 08:30 AM.
knc1 is offline   Reply With Quote