Quote:
Originally Posted by Usodimare
- - - -
I went through the /etc/usbnet/config script file and all commands start with "K3": as already mentioned my Kindle is K4, may be there is the problem?
- - - -
|
No.
USBnetworking only provides the USB networking.
It is the way the Kindle detects if it can call home which the file controls. That is provided by the Amazon system.
The K3 was the first Kindle model to offer Wifi -
This:
Quote:
You don't need a rooted Kindle.
In the topmost level of USB storage, create the file named:
WIFI_NO_NET_PROBE
All capitals, no extension, no contents.
|
Has worked on all models, all firmware versions, since then; except for yours.
So keep looking for something done different from the directions on your device.
You still haven't answered my question about what PC you have.
(The entire world is not limited to using Windows, despite Bill Gates wishes.)
So I can't give you specific directions.
Be sure you are using the USBnetworking package from:
https://www.mobileread.com/forums/sh...d.php?t=225030
Read that first post to learn how to unarchive *.xz archives on your PC, whatever it happens to be.
Read each and every file in that archive that has: "README" as part of its filename.
Disable USB networking (it should not matter, but disable it anyway).
Disable ssh networking over Wifi (it is not enabled by default, but disable it anyway).
Follow the directions to install the proper package (hint, it has: k4 as part of its filename).
Ensure the USB cable is disconnected while trying to install the package.
Ensure that USB networking is disabled while trying to install the package.
Ensure that the USB networking configuration file in visible USB storage still has the default settings as shipped in the archive.
NOTHING installs anything prefixed: k3 into /etc/usbnet/config
(Be certain you are not looking at: /mnt/us/etc/usbnet/config (I.E: the one in visible USB storage.)
Figure out where that came from (prior owner? prior efforts to make it work without a network connection?) Wherever it came from, for whatever reason, fix it.
When all else fails - use Kubrick on the device (the one from the sticky on this forum includes the jb already; others, check with that website for specifics) - update to the current firmware version for the K4 by following the directions on Amazon for updating the K4.