View Single Post
Old 05-01-2012, 07:47 AM   #2
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 nobody_nowhere View Post
Hello guys, I have a Kindle 3 Wifi with FW 3.3 installed.
I messed around a lot in my terminal, installing new hacks etc. but now recently, my Kindle was not able to connect to wi-fi. I did a Reset to Factory defaults hoping that would solve the problem, but it didn't work.
Everytime, I try connecting to a wi-fi network. It says "Local network connection failed."
I have restarted router, and even resetted it, disabled all security options (so that my password couldnt be wrong).
I have messed around a bit in the /opt directory and BTW, to try to update Busybox, I copied all files in /opt/bin to /bin. (I updated Busybox in /opt/bin using optware) My terminal works fine most of the time except when it says eg.
#login
login: applet not found
For a lot of commands it's like this.
Please HELP me...
Also could somebody point me to a link containing all the /opt and /bin directories????
PLEASE HELP, My K3 is close to being bricked, since I can' run that many cmmands...
I suggest that the first thing you do is switch back to the original /bin/busybox.

Just move that one file from the backup copy of /bin that you made before you tried to replace everything there.

Note 1: The Busybox application has a number of build-time options that determine how it provides the internal applet functions.
If the optware Busybox wasn't built with the same "access" options as the Kindle Busybox (even if the same version) you are likely to get "applet not found" errors.

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.

Note 3: If the new (optware) Busybox is not built as a "static" executable, you may also be having library file mis-matches.
I didn't see in your original post where you modified the contents of /lib - so:
Don't do that now!

Last edited by knc1; 05-01-2012 at 07:54 AM. Reason: typos
knc1 is offline   Reply With Quote