Kindle Touch update 5.1.1

[Alb]

Ups!

[Alb]

Originally Posted by jswinden

Look at the number of posts for those claiming to have seen the 5.1.1 update. Of the four I saw who claimed to have seen it, one has 13 posts, one 1 post, one 2 posts, and one 6 posts. It is clear that all are new comers to this forum and possibly new to Kindles. I still suspect this is just pure BS or they simply don't know what they actually saw. I still have not seen any credible evidence that 5.1.1 ever existed other than in someone's imagination.

TO DOUBTERS:

[geekmaster]

Originally Posted by Alb

TO DOUBTERS:

...IMG...

Yours is not the only posted photo showing 5.1.1. So far, all reported 5.1.1 kindles have been foreign (non-US) versions, and were shipped with 5.1.1 preinstalled.

There are reports of some kindles reverting from 5.1.1 back to 5.1.0 after an OTA update, and a reboot.

[Alb]

I've tried many times [] install the 5.1.0 version, but my kindle does not go back to 5.1.0.



[WTF!]

[NiLuJe]

@Alb: Official updates are mostly delta updates, not full firmware image dumps => no OTA downgrade (at least with the 'usual' Update 5.1.0 update file from Amazon... Actually building a proper OTA 5.1.1 -> 5.1.0 'update' would be a pretty convoluted process, and it might have to lie a bit about what it does, because I'm not sure the OTA updater will let an update targeting a build revision lesser than the source revision run...).

[Alb]

NiLuJe: I supposed it.
Thanks!

It will be necessary to do the work [difficult work] that Geekmaster indicated before.

[dukesilver]

Alb, do you see any parental controls somewhere in the 5.1.1 settings? just curious

[Alb]

No, really not.

[geekmaster]

Originally Posted by Alb

NiLuJe: I supposed it.
Thanks!

It will be necessary to do the work [difficult work] that Geekmaster indicated before.

If you are referring to the RUNME.sh script I mentioned, that is actually quite easy. I described the steps needed. It was just easy enough I had hoped somebody else would do it. This is not the only thread I had requested somebody write this script in. My first request was the first day 5.1.1 was reported. I suppose when I get time in a few weeks, I will have to write it myself. This is a DEVELOPER'S corner thread (posted to the wrong forum IMHO), not just a "please help me" forum. The major developer's here want to get back to working on the big projects, hoping that others will contribute to the simpler tasks (such as the RUNME.sh full image backup script I suggested), so we can get firmware images to study...

To learn a little about script writing, perhaps you can get some inspiration by studying my "eink algorithmic art shell scripts" thread.

P.S. The above suggestions are not specifically for Alb, but for ANYBODY here who wants to contribute to kindle development, and is willing to learn. You can learn more about kindle development (even simple scripts) in the kindle developer's corner forum.

[Alb]

Great! Jajajaja.

My dreams are very simple: no codes, no vivid and intense video games, no... Only dreams [¡?] and snoring.



Anyway don't worry, I can wait, I'll be patient.

Thanks.

PS: ok, ok, tomorrow I will read the steps needed to do the RUNME.sh script you mentioned. I understand this is not just a "please help me forum", of course. But I am really slowly reading english (this is my only problem).

This: https://www.mobileread.com/forums/sho...d.php?t=170929

And this: https://www.mobileread.com/forums/sho...d.php?t=180113

[eureka]

@Alb, there is no need for experimenting with RUNME scripts:

• install (and then enable) USB networking,
• connect to KT with SSH client (Putty or something),
• issue

  dd if=/dev/mmcblk0p1 of=/mnt/us/p1.img

• wait some minutes (it's safe to interrupt this process in any time, but you'll get an incomplete image, so be really patient).

[geekmaster]

Originally Posted by eureka

@Alb, there is no need for experimenting with RUNME scripts:

• install (and then enable) USB networking,
• connect to KT with SSH client (Putty or something),
• issue

  dd if=/dev/mmcblk0p1 of=/mnt/us/p1.img

• wait some minutes (it's safe to interrupt this process in any time, but you'll get an incomplete image, so be really patient).

It helps a LOT to use a larger blocksize (especially when writing TO mmc you should use the same as the erase block size = 4K).

Do this: dd if=/dev/mmcblk0p1 of=/mnt/us/mmcblk0p1_5.1.1.img bs=4K

It will be less write-wear on the mmc, and it will run a lot faster.

Using the smaller default 512 byte block size for dd does a lot of unnecessary read-modify-write cycles. It is also a good idea to identify the firmware version number, and for a diags partition add "diags" to the filename, to prevent confusion when supporting multiple devices.

[Alb]

Geekmaster and Eureka, sorry, but I don´t understand the steps very well.

So, I need to get the RUNME scripts (or a full image backup script or whatever) of my KT (with the last updated firmware). Isn´t it?

Because the aim is: understand what makes the Jailbreak and Hackfont don't work (don't run) with the firmware version 5.1.1. Understand and solve that problem.

And then I need to know how take the RUNME scripts for you (you, and Geekmaster, etc.: the people who really know about it).

Ok. But, sorry, sorry, I don't see clearly what are the steps of this process. (Process= take the RUNME scripts...)

I feel quite awkward!

[NiLuJe]

@geekmaster/@eureka: Err, wasn't the point of doing it in a diags RUNME instead of USBNet to be able to dump an *unmounted* part? Because doing it from usbnet on main would be dumping main from main == bad, no? (And since it's an unknown firmware/kernel, doing it from a flashed older diags+ssh isn't a great idea either).

(Take that with a grain of salt, I'm not familiar with the RUNME stuff, and I still can't remember wich part is main/diags... ^^)

[Alb]

For all: but, really is not an other way to install or view more fonts in the KT?
With Calibre, for example.
Hack Font is the only way to do it?