I have been doing some searching on
Code:
E _otaupexec:def:signature verification failed on
and found this page
http://jyavariousideas.blogspot.com....1_archive.html
It seems to be very relevant. One thing I did not mention is that I am in Australia in case that makes any difference.
Anyway, it appears I would be missing a signature for the non-Amazon .bin installs to be verified and that the relevant one would need to first be added to the kindle eg:
Quote:
o what we first do is install an extra RSA key in the device.
that's what the update file update_freekindle.bin is for.
update_freekindle.bin uses a "feature" (some would call it a flaw) of the tar compressor. Kindle binary package are just gzipped tar files slightly encrypted as discovered by Igor Skochinsky. When extracting the content of the update, the Kindle simply call tar on it.
Tar follows simlinks ; and we use this to write where we're not supposed to.
Copy the file update_freekindle.bin on the Kindle USB disk ; then:
go to HOME
MENU -> Settings
MENU -> Update Your Kindle
DO NOT SELECT RESTART, or you will brick your Kindle (though there's a way to get out of that infinite reboot)
That update will fail ! (Error 004). This is normal.
What this package does is add our key to the list of keys available. So next time the Kindle will check the signatures of the files we are installing, the verification process will succeed.
|
This of course appears to be for the Kindle2, but does seem relevant.
I would have expected that using Kubrick to flash 3.4 would have put the required signatures in place, but is it possible that this did not happen?
Is there any way I can interact with file listings on the kindle in the system area to confirm?
And/or how could I manually (re)place the required signature file into the relevant location?
Thanks