Quote:
Originally Posted by knc1
@ixtab: Maybe we should just delete wifid.conf from the Kubrick images?
|
Hmm. That seems to be a Kindle 3 issue. First off, I don't know where that file really is, and second, I'm afraid of the K3 because of its "partition" layout which I don't understand. And third, Kubrick can't do anything at the filesystem level with a K3 because of (see "second").
In other words: The K3 is a black box for Kubrick, so all it can do is use k3flasher to write blobs to a few parts of the MMC, but without actually knowing or understanding what those blobs mean. For the K4/K5, Kubrick can "interact" with the filesystem, because the device allows it to. For the K3... it can't
