Quote:
Originally Posted by cscat
It is MY_KT_5.1.0.bin and when underlined it gave you that impression of space, but thanks again for everything knc1 and GM.
I have created a new Wiki page called Kindle Touch Firmware Updates Changelog in frustration of all little good/bad changes happened without Amazon mentioning them. Please feel absolutely welcome to add (in fact please do!). And I added a link to it from K5 Index page too. It'd be a good idea if this can be done with other Kindle devices too!
@Geekmaster: Considering your warning here, I would assume as kernels are different between 5.0.0 and 5.1.0, I should change kernel back to whatever 5.0.0 is with, eh?
P.S. Man! I don't like how Amazon >>> Lab126 is proceeding with this thingy!!!
P.S.S. I'm really sick of being scared by all these hidden updates. I've been a loyal customer (term coined by Geekmaster) but now this has to change! Everytime, I turn my Kindle on, I see Wireless/3G is turned on because when I wanted to turn it off, I had suddenly touched bottom of screen where there is an ad and it automatically turns Wireless on!!! NOW, I'm going to disable ads and screensaver and all update pushes!!! ENOUGH. |
I was referring to "of=/dev/mmcblk0pt1", which should not contain a 't' (as knc1 showed with his s//).
The main 5.0.0 kernel goes with 5.0.0 through 5.0.3, but then there is a 5.0.4 kernel, and now a 5.1.0 kernel.
The diags kernel first changed with 5.1.0, as I recall...
Try to use the kernel originally used with whatever partition version you use. We want to stay as close to *something* once shipped by amazon as we can.
There have been a LOT of reports of OTA updates bricking kindles, including kindles that did not have any jailbreak or hacks installed. Normally, when flashing firmware, it is best to be sure that the kindle is plugged in or has a full battery charge. Apparently, the kindles install OTA updates even with a low battery charge, so they fail during a restart when only partially updated, and then they cannot be restarted again. It appears that amazon uses some VERY UNSAFE firmware update methods...