Quote:
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
Code:
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).
Code:
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.