Mobileread Kindlet Kit update failing Kindle Keyboard B008

[motiv8d]

I am trying to install " Mobileread Kindlet Kit" so that I can install KUAL to in turn enable me to install BackDoorLock.

I have first used Kubrick to install 3.4 firmware which I read is already jailbroken.

I have copied "Update_mkk-20141129-k3w-B008_install.bin" to the root folder of the kindle keyboard (v3).

Then ran "Update Your Kindle"
It completes only 1 block of the progress bar (<10%) then shows an error "your update was unsuccessful".

Can anyone see what I am doing wrong? or what step I am missing?

NB: The device is currently unregistered as I wanted to install the hacks first.

Thanks

Jesse

[knc1]

Are you doing this with the USB cable disconnected?
Register the device (although it shouldn't matter).

[motiv8d]

Hi KNC1. Thanks for your reply.

I do not know how I could do this WITH the USB Cable connected to my Ubuntu machine. It goes into USB drive mode when connected and says to use the kindle, "eject it from the computer". However when I unmount then "udisks --detach", the kindle, it stays in drive mode and there is no way for me to perform an update.

# umount /dev/sdf1
# udisks --detach /dev/sdf
Detach failed: Error detaching: helper exited with exit code 1: Detaching device /dev/sdf
USB device: /sys/devices/pci0000:00/0000:00:16.0/usb9/9-3)
SYNCHRONIZE CACHE: OK
STOP UNIT: FAILED: No such file or directory

So I can only do the update with the USB cable entirely DISCONNECTED.

I have since updated the kindle to 3.4.2 from 3.4 (this was necessary to enable me to connect wifi). The procedure I used to do this was the same as I have been trying to use for the MKK. However, this update worked flawlessly.

I have then registered successfully.

--- Should I be using a different update procedure for the MKK??? ----
I am using:

Menu - Settings - Menu - Update your Kindle

after copying the .bin file to the root of the kindle.

Trying again resulted in the same update fail.

I have also since tried to use the file "Update_mkk-20141129-k3w-B008_uninstall.bin" as an update using the same procedure and this fails at the first segment of the progress bar also.

I have tried these updates with both the wifi turned on and off.

Also I have put onto the kindle keyboard wifi - "KUAL-KDK-1.0.azw2"
When I go to it, right click, then choose open, it says:
"The device is not registered as a Test Kindle to run this title...."

--- I am wondering if this means that after using Kubrick my device is somehow still not jailbroken? ---

[knc1]

The term (and command) you are looking for is named: eject not detach

[motiv8d]

Thanks, again, but still the update is borked.

The eject command "udisks --eject /dev/sdf" now works. However, attempting the update of the MKK .bin file does exactly the same, ie at 1 block in the progress bar it terminates and reports that the update was unsuccessful.

So I have now tried every combination of these:

• Update_mkk-20141129-k3w-B008_install.bin (Menu-Settings-Menu-UpdateYourKindle)
• Update_mkk-20141129-k3w-B008_uninstall.bin (Menu-Settings-Menu-UpdateYourKindle)
• KUAL-KDK-1.0.azw2 (Right click - Open)
• Plugged into USB of Ubuntu (ejected through command line using 'udisks --eject')
• Not plugged into any USB
• WIFI Enabled
• WIFI Disabled
• Unregistered
• Registered (excl plugged into USB)

Just to confirm my serial starts with B008 and it is the kindle keyboard wifi model.

Again, the Kindle update from 3.4 to 3.4.2 using the same procedure works fine. Is there any possibility that the two .bin files for MKK are corrupt?
They have cleanly extracted from "kindle-mkk-20141129.zip"

Also thanks for your patience, especially on the detach/eject command. I should have tried that.

[knc1]

Do you have a GUI installed?
Open file manager, right click the "Kindle" disk, your choices are:
un-mount
eject

You want eject.

If you have a headless (command line only) install, use the:
eject
COMMAND, not an option to udisks.

You seem to have a failing flash chip.
You should probably force the K3 to run an fsck on it (do not try it from outside of the Kindle, make the Kindle do it itself).

[motiv8d]

Thanks, but since your last recommendation of "--eject" I have no problem ejecting the kindle, thus I have been able to make the update attempts with USB plugged as well.

My problem is that the MKK .bin updates are not being accepted. However, the 3.4.2 update worked flawlessly. Which in turn make me sceptical that an fsck will detect problems, but I am happy to try.

However, I have no idea how do get the kindle to do an fsck itself. Could you please let me know?


Thanks

[knc1]

Originally Posted by motiv8d

Thanks, but since your last recommendation of "--eject" I have no problem ejecting the kindle, thus I have been able to make the update attempts with USB plugged as well.

My problem is that the MKK .bin updates are not being accepted. However, the 3.4.2 update worked flawlessly. Which in turn make me sceptical that an fsck will detect problems, but I am happy to try.

However, I have no idea how do get the kindle to do an fsck itself. Could you please let me know?


Thanks

You never did say if you have a GUI installed.
I will assume not, since everyone has a command line terminal installed, like it or not.

The name of the working place does not matter, here: ~/K3

core2quad ~ $ mkdir K3

core2quad ~ $ cd K3

core2quad K3 $ wget http://mr-public.auth-2ac4bfee353948ec8ea7fd1710574097.storage.sbg1.cloud.ovh.net/Touch/kindle-mkk-20141129-r13408.tar.xz
- - - progress feedback - - -
2017-04-17 07:34:09 (301 KB/s) - `kindle-mkk-20141129-r13408.tar.xz' saved [239180/239180]

core2quad K3 $ tar --extract --file=kindle-mkk-20141129-r13408.tar.xz

core2quad K3 $ ls
DevCerts  kindle-mkk-20141129-r13408.tar.xz

core2quad K3 $ md5sum kindle-mkk-20141129-r13408.tar.xz
79bb349c9d8e4b66e37c4b441eca9353  kindle-mkk-20141129-r13408.tar.xz

core2quad K3 $ cd DevCerts

core2quad DevCerts $ md5sum Update_mkk-20141129-k3w-B008_install.bin
da6b46c5c1ca078ed664ce75b4f4739f  Update_mkk-20141129-k3w-B008_install.bin

Use the result of the last two commands to see if:
*) The archive transferred to your PC without harm
*) The mkk install_*.bin was written to your PC from the archive without harm

Now plug in USB cable, K3 <-> PC
I assume here that your Ubuntu automation has just auto-mounted the Kindle's user area to:
/media/Kindle

Ensure there is not any other update_*.bin file on the K3 (you MUST only have a single update_*.bin file on the device at once).

core2quad DevCerts $ ls /media/Kindle/*.bin
- - - none found - - -

core2quad DevCerts $ cp -a Update_mkk-20141129-k3w-B008_install.bin  /media/Kindle

core2quad DevCerts $ md5sum /media/Kindle/Update_mkk-20141129-k3w-B008_install.bin

da6b46c5c1ca078ed664ce75b4f4739f  /media/Kindle/Update_mkk-20141129-k3w-B008_install.bin

core2quad DevCerts $ sudo eject /media/Kindle

Disconnect the USB cable.
You don't have to try any other combination or order of commands.

Compare the md5sum you computed at each step with the above values.

If the MKK installer file made it safely from the attachment to the K3 visible top level of user, USB storage - - -
If the MKK installer file is the ONLY *.bin file on the Kindle - - -
Try the installation again.

If it fails, report the exact wording of any message.

Use the search function on the Kindle to search for:
;dm
and then read the system log file created, discover what messages the above attempt created (I am pretty sure NiLuJe logs progress).
Don't forget the "code .... /code" tags when posting the 'tail' of the system log file.
'tail' however many lines of the log that seem related to the install attempt.

[motiv8d]

Hi knc1
Thanks so much for your detailed reply.
Sorry I missed the gui Q. Yes I do have a gui (Linux Mint / Ubuntu) however, I much prefer to do work like this with CLI in a terminal so I have a bash record of it and it reduces the chance of errors IMHO.

The logs look helpful. The checksums verified with the same MD5 as yours.
The relevant line in the log seems to be:

system: E _otaupexec:def:signature verification failed on "/tmp/.update-tmp.14149/update-filelist.dat"

The relevant section of the log is:

170417:040800 system: I mntroot:def:Making root filesystem read-only
170417:040800 system: I S50updater:def:updater started
170417:040800 system: I S50updater:def:Waiting for wand to shutdown
170417:040800 system: I S50updater:def:wand shutdown complete
170417:040801 system: I S50updater:def:read bundle line [/mnt/us/Update_mkk-20141129-k3w-B008_install.bin]
170417:040801 system: I S50updater:def:Applying update /mnt/us/Update_mkk-20141129-k3w-B008_install.bin
170417:040801 system: I S50updater:def:Size of update: 58262 bytes
170417:040801 system: I S50updater:def:Version before update: 004-S402_luigi-268724
170417:040801 system: I _otaupexec:def:processing update /mnt/us/Update_mkk-20141129-k3w-B008_install.bin
170417:040801 system: I _otaupexec:def:version is "FC02"
170417:040801 system: I _otaupexec:def:update image checksum OK
170417:040802 system: E _otaupexec:def:signature verification failed on "/tmp/.update-tmp.14149/update-filelist.dat"
170417:040802 system: E _otaupexec:def:signature verification failed
170417:040802 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=20C:from pmic
170417:040804 system: E S50updater:def:OTA update failed (1)
170417:040804 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/Update_mkk-20141129-k3w-B008_install.bin"
170417:040804 init: Switching to runlevel: 5
170417:040805 ar6000: Shasta Atheros Ar6000 WiFi Driver

The MD5 of the files extracted from your archive (DevCerts) do differ from the MD5 of the ones I was originally using (Mobileread Kindlet Kit), although the problem remains the same. The filenames were identical so MD5 differences between the same? files extracted from two archives does seem strange)

#md5sum /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_install.bin
da6b46c5c1ca078ed664ce75b4f4739f  /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_install.bin
#md5sum /installs/kindle/firmware/Mobileread\ Kindlet\ Kit/Update_mkk-20141129-k3w-B008_install.bin
463bdec3e263a74bd238a368f0f8791f  /installs/kindle/firmware/Mobileread Kindlet Kit/Update_mkk-20141129-k3w-B008_install.bin

#md5sum /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_uninstall.bin 
7d268648596883cf1c75730d5ae60ac6  /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_uninstall.bin
#md5sum /installs/kindle/firmware/Mobileread\ Kindlet\ Kit/Update_mkk-20141129-k3w-B008_uninstall.bin 
c88e27dd2536802df43e78aaa46ce57e  /installs/kindle/firmware/Mobileread Kindlet Kit/Update_mkk-20141129-k3w-B008_uninstall.bin

cp -a /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_install.bin  /media/jesse/Kindle/
md5sum /media/jesse/Kindle/Update_mkk-20141129-k3w-B008_install.bin 
da6b46c5c1ca078ed664ce75b4f4739f  /media/jesse/Kindle/Update_mkk-20141129-k3w-B008_install.bin

Although the core information should be in this post and in particular that:

_otaupexec:def:signature verification failed on "/tmp/.update-tmp.14149/update-filelist.dat"

I will make a subsequent post with the exact steps I followed and screen shots for full information.

[motiv8d]

I have been doing some searching on

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:

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

[motiv8d]

This is additional information to above two posts. It is for completeness only to show the specific steps I took.

Obtain new firmware from knc1 to extract to DevCerts and check md5sums:

#md5sum /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_install.bin
da6b46c5c1ca078ed664ce75b4f4739f  /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_install.bin
#md5sum /installs/kindle/firmware/Mobileread\ Kindlet\ Kit/Update_mkk-20141129-k3w-B008_install.bin
463bdec3e263a74bd238a368f0f8791f  /installs/kindle/firmware/Mobileread Kindlet Kit/Update_mkk-20141129-k3w-B008_install.bin

#md5sum /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_uninstall.bin 
7d268648596883cf1c75730d5ae60ac6  /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_uninstall.bin
#md5sum /installs/kindle/firmware/Mobileread\ Kindlet\ Kit/Update_mkk-20141129-k3w-B008_uninstall.bin 
c88e27dd2536802df43e78aaa46ce57e  /installs/kindle/firmware/Mobileread Kindlet Kit/Update_mkk-20141129-k3w-B008_uninstall.bin

Connect Kindle and copy new file to root

cp -a /installs/kindle/DevCerts/Update_mkk-20141129-k3w-B008_install.bin  /media/jesse/Kindle/
md5sum /media/jesse/Kindle/Update_mkk-20141129-k3w-B008_install.bin 
da6b46c5c1ca078ed664ce75b4f4739f  /media/jesse/Kindle/Update_mkk-20141129-k3w-B008_install.bin

Unmount and Eject Kindle, then unplug USB

umount /dev/sdf1
udisks --eject /dev/sdf

Initiate the update (.bin)
Home - Menu - Settings - Menu - Update Your Kindle
http://imgur.com/TAa181R

http://imgur.com/rYDsDKN


Makes only 1 progress bar
http://imgur.com/Guscksn


Fails (log shows E _otaupexec:def:signature verification failed)
http://imgur.com/emo5jCt


After restarted
Search for ";dm" (without quotes) to generate logs

Connect Kindle
Copy logs from /media/jesse/kindle/Documents to pc

Tail relevant part orelevant log section of all_logs_as_of_Thu_Apr_20_02.11.39_GMT_2017.txtf logs files for borked install

170417:040800 system: I mntroot:def:Making root filesystem read-only
170417:040800 system: I S50updater:def:updater started
170417:040800 system: I S50updater:def:Waiting for wand to shutdown
170417:040800 system: I S50updater:def:wand shutdown complete
170417:040801 system: I S50updater:def:read bundle line [/mnt/us/Update_mkk-20141129-k3w-B008_install.bin]
170417:040801 system: I S50updater:def:Applying update /mnt/us/Update_mkk-20141129-k3w-B008_install.bin
170417:040801 system: I S50updater:def:Size of update: 58262 bytes
170417:040801 system: I S50updater:def:Version before update: 004-S402_luigi-268724
170417:040801 system: I _otaupexec:def:processing update /mnt/us/Update_mkk-20141129-k3w-B008_install.bin
170417:040801 system: I _otaupexec:def:version is "FC02"
170417:040801 system: I _otaupexec:def:update image checksum OK
170417:040802 system: E _otaupexec:def:signature verification failed on "/tmp/.update-tmp.14149/update-filelist.dat"
170417:040802 system: E _otaupexec:def:signature verification failed
170417:040802 eink_fb: I bs_cmd_ld_img_upd_data_which:def:temp=20C:from pmic
170417:040804 system: E S50updater:def:OTA update failed (1)
170417:040804 system: I S50updater:def:Deleting OTA bundle file "/mnt/us/Update_mkk-20141129-k3w-B008_install.bin"
170417:040804 init: Switching to runlevel: 5
170417:040805 ar6000: Shasta Atheros Ar6000 WiFi Driver

Picture series is at http://imgur.com/a/zmj9s

[motiv8d]

It seems that Kubrick for a Kindle 3 (Keyboard) B008 K3W DOES NOT also jailbreak the device.
Thus my much earlier question is very relevant.

--- I am wondering if this means that after using Kubrick my device is somehow still not jailbroken? ---

The Kubrick I used was this one:
kubrick-k3-k4-k5-ISO-DVD.zip

From my previous thread here https://www.mobileread.com/forums/sh...71&postcount=7 I thought that Kubrick for Kindle 3's used an image that was already jailbroken.

It seems to me that this is NOT the case.

To resolve I have:
Obtained kindle-jailbreak-0.13.N.zip from https://www.mobileread.com/forums/sh...ad.php?t=88004 and copied file Update_jailbreak_0.13.N_k3w_install.bin to copy to the root of the device and Home - Menu - Settings - Menu - Update Your Kindle.
It showed successful update.

I was then able to:

1. Install the MKK as mentioned in this thread I was having so much trouble with due to "Signature Verification Failed"
2. Install KUAL using the AZW2 book open method of KUAL-KDK-1.0.azw2
   
   Thanks for your help on this knc1. The log file information was extremely helpful to me working this out.
   
   All the best
   
   Jesse

[knc1]

Originally Posted by motiv8d

- - - -

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?
- - - -

It does include our signature certificate (I.E: Jailbreak):

Originally Posted by ixtab

Version 3.6
- - - -
Kubrick Features:

• - - - -
• Can (optionally) install the device jailbreak (K4/KT); the K3 image always includes the jailbreak.
  - - - -

- - - -

It is very possible (and relatively common on a K3) that the Kubrick copy of the firmware did not install.
How much longer than 2 hours did the installation process run?

Originally Posted by motiv8d

- - - -

_otaupexec:def:signature verification failed on "/tmp/.update-tmp.14149/update-filelist.dat"

- - - -

You are not running the firmware image that is included in Kubrick.

Originally Posted by motiv8d

- - - -
Fails (log shows E _otaupexec:def:signature verification failed)
http://imgur.com/emo5jCt
- - - -

You are not running the firmware image included with Kubrick.

Originally Posted by motiv8d

It seems that Kubrick for a Kindle 3 (Keyboard) B008 K3W DOES NOT also jailbreak the device.

The Kubrick I used was this one:
kubrick-k3-k4-k5-ISO-DVD.zip

I have not been able to find a file by that name that is linked to in the first post of Kubrick.
Please quote the link you used so the image can be checked for a missing certificate.

Originally Posted by motiv8d

From my previous thread here https://www.mobileread.com/forums/sh...71&postcount=7 I thought that Kubrick for Kindle 3's used an image that was already jailbroken.

It seems to me that this is NOT the case.
- - - -

It is the case, the Kubrick image does include the jailbreak (MR developers' signature certificate).

Originally Posted by ixtab

Version 3.6
- - - -
Kubrick Features:

• - - - -
• Can (optionally) install the device jailbreak (K4/KT); the K3 image always includes the jailbreak.
  - - - -

- - - -

What you are seeing is a K3 that is not running the firmware included with Kubrick.
At least not the Kubrick linked to from here in the first post of the Kubrick thread.
It is possible that you are running a modified Kubrick image from somewhere else (one that was intentionally modified to leave out the jailbreak).

One more time:
How much longer than 2 hours did Kubrick run during its installation phase?

[motiv8d]

Hi knc1

Thanks for your reply. I will do my best to clarify. I am guessing the confusion could be due to the subsequent install of 3.4.2 update post Kubric?

I am well aware that the FAQ for Kubric states that K3 is jailbroken. Just not my experience

The duration of kubric process I cannot say exactly, but it would have been close to 4 hours.

Prior to kubric, my firmware version was 3.4.2.
After kubric it was 3.4.
I could not get MKK .bin to install after this. You suggested to register as I noted it was not registered at that time.
I could not connect to wifi with it.
So I then installed the update from Amazon of 3.4.2.
I was then able to connect to wifi and register.

The Kubrick DVD I obtained from here (I just confirmed this by re-downloading and comparing the md5):
https://www.mobileread.com/forums/sh...d.php?t=206064 and specifically http://ixtab.tk/kubrick-k3-k4-k5.zip

#md5sum boot.iso 
5a8382450a2f239fc27fbbb3c7b24e76  boot.iso
#md5sum kubrick-k3-k4-k5-ISO-DVD.zip 
1140067d372e0ac8b3627fd799519ddc  kubrick-k3-k4-k5-ISO-DVD.zip
#ls -laht
784M Apr 15 11:41 kubrick-k3-k4-k5-ISO-DVD.zip
784M Aug  4  2013 boot.iso

After that after not being able to install MKK .bin, or use KUAL, I installed the following to gain wifi access and register:

#ls -laht
2.2M Apr 15 11:25 Amazon Update Update_kindle_3.4_3.4.2_B008.bin
#md5sum Amazon\ Update\ Update_kindle_3.4_3.4.2_B008.bin 
cb152c924f2ed61ef3223efb8f4ef959  Amazon Update Update_kindle_3.4_3.4.2_B008.bin

This was from https://www.amazon.com/gp/help/custo...g=thedigrea-20
and specifically https://s3.amazonaws.com/G7G_Firmwar...3.4.2_B008.bin

I have just checked the DVD I burned to use Kubrick of all the MD5sums of each individual file based on the md5sum list burned onto the DVD from the image. Two files failed the check.

#md5sum -c md5sum.txt | grep -vi 'OK$'
boot/isolinux/boot.cat: FAILED
boot/isolinux/isolinux.bin: FAILED
md5sum: WARNING: 2 computed checksums did NOT match
#md5sum boot/isolinux/boot.cat && cat md5sum | grep -i boot.cat
995f2867af47135b7c58a125a20fd3e8  boot/isolinux/boot.cat
184040516e41b4ecc95e699d4e1a9843  boot/isolinux/boot.cat
#md5sum boot/isolinux/isolinux.bin && cat md5sum | grep -i isolinux.bin
ad9b8227fd6599c5063dd34349be4ff9  boot/isolinux/isolinux.bin
19fed27714d24da7e14f07fc47c9616b  boot/isolinux/isolinux.bin

Thanks

Jesse

[knc1]

Originally Posted by motiv8d

- - - - -
I am well aware that the FAQ for Kubric states that K3 is jailbroken. Just not my experience
- - - - -

The quotes I made from the first post of the thread apply to the files linked to from within the first post of the thread.

Other files are described elsewhere.

You can't expect any of the directions to generalize across in-line linked and external file sources, that isn't even a realistic case.

Use the files linked to in the same post as the description and then you can expect them to be as described and behave as expected.
That is a general rule you can apply to everything posted in this forum.

Or in contrast:
Thou shall not attempt to cross-breed descriptions and files from different locations.
or
Thou shall leave the dance with the one that brought you.