K5 FW 5.x ScreenSavers Hack

[knc1]

The small binary:

Dynamic section at offset 0xa04 contains 48 entries:
  Tag        Type                         Name/Value
 0x00000001 (NEEDED)                     Shared library: [libMagickCore.so.4]
 0x00000001 (NEEDED)                     Shared library: [libMagickWand.so.4]
 0x00000001 (NEEDED)                     Shared library: [libtiff.so.3]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 0x00000001 (NEEDED)                     Shared library: [libjpeg.so.8]
 0x00000001 (NEEDED)                     Shared library: [libfontconfig.so.1]
 0x00000001 (NEEDED)                     Shared library: [libfreetype.so.6]
 0x00000001 (NEEDED)                     Shared library: [libpng16.so.16]
 0x00000001 (NEEDED)                     Shared library: [libexpat.so.1]
 0x00000001 (NEEDED)                     Shared library: [libXext.so.6]
 0x00000001 (NEEDED)                     Shared library: [libXt.so.6]
 0x00000001 (NEEDED)                     Shared library: [libbz2.so.1.0]
 0x00000001 (NEEDED)                     Shared library: [libxml2.so.2]
 0x00000001 (NEEDED)                     Shared library: [libz.so.1]
 0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
 0x00000001 (NEEDED)                     Shared library: [libSM.so.6]
 0x00000001 (NEEDED)                     Shared library: [libuuid.so.1]
 0x00000001 (NEEDED)                     Shared library: [libICE.so.6]
 0x00000001 (NEEDED)                     Shared library: [libX11.so.6]
 0x00000001 (NEEDED)                     Shared library: [libxcb.so.1]
 0x00000001 (NEEDED)                     Shared library: [libXau.so.6]
 0x00000001 (NEEDED)                     Shared library: [libXdmcp.so.6]
 0x00000001 (NEEDED)                     Shared library: [libdl.so.2]
 0x00000001 (NEEDED)                     Shared library: [libm.so.6]
 0x0000000f (RPATH)                      Library rpath: [/usr/local/lib]

Note: The above IM convert is only present in the factory_<dev>_<rev>_initial firmware packages.

The large binary:

 0x00000001 (NEEDED)                     Shared library: [libfreetype.so.6]
 0x00000001 (NEEDED)                     Shared library: [libpng16.so.16]
 0x00000001 (NEEDED)                     Shared library: [libz.so.1]
 0x00000001 (NEEDED)                     Shared library: [libm.so.6]
 0x00000001 (NEEDED)                     Shared library: [libgcc_s.so.1]
 0x00000001 (NEEDED)                     Shared library: [libpthread.so.0]
 0x00000001 (NEEDED)                     Shared library: [libc.so.6]
 0x0000001d (RUNPATH)                    Library runpath: [/mnt/us/linkss/lib:/home/niluje/Kindle/CrossTool/Build_PW2/lib]

Note: The above IM convert is installed as part of the screensaver add-in.
(And NiLuJe's build system is leaking the build path into the runpath.)
While it is off of the kindle, do:

strip --strip-unneeded <filename>

That should down-size it.

So this second one is bigger because all of the external libraries listed in the first but not listed in the second are already built into the convert binary.

[nasser]

strip command not available on my kindle (KT3, G000KA, 5.8.0-Factory)
If I try strip on my PC (Ubuntu 14.04 32-bit) on the files copied over from kindle, I get error message

strip: Unable to recognise the format of the input file `convert'

So... my original question: what if i rename/delete /mnt/us/linkss/bin/convert and instead copy or link to /usr/local/bin/convert...?

[knc1]

FAT-32 does not support links.
/usr/local/bin only exists in factory_* images, not in customer_* images
making a copy should work.

Ubunta must have re-organized their installs -
They used to build/ship the general purpose strip command not the architecture specific build.

Yup - that's it:

 $ ssh mrdcorn
Welcome to Ubuntu 12.04.5 LTS (GNU/Linux ps34532 x86_64)

$ strip --help
Usage: strip <option(s)> in-file(s)
- - - -
strip: supported targets: elf64-x86-64 elf32-i386 elf32-x86-64 a.out-i386-linux pei-i386 pei-x86-64 elf64-l1om elf64-k1om elf64-little elf64-big elf32-little elf32-big plugin srec symbolsrec verilog tekhex binary ihex
Report bugs to <http://www.sourceware.org/bugzilla/>

Older version of Ubuntu

strip: supported targets: elf32-i386 a.out-i386-linux pei-i386 elf32-little elf32-big elf64-ia64-little elf64-ia64-big pei-ia64 elf64-little elf64-big elf64-alpha ecoff-littlealpha elf64-x86-64 elf32-x86-64 pei-x86-64 elf64-l1om elf64-k1om elf32-littlearm elf32-bigarm elf32-hppa-linux elf32-hppa elf32-tradbigmips elf32-tradlittlemips ecoff-bigmips ecoff-littlemips elf32-ntradbigmips elf64-tradbigmips elf32-ntradlittlemips elf64-tradlittlemips elf32-powerpc aixcoff-rs6000 elf32-powerpcle ppcboot elf64-powerpc elf64-powerpcle elf32-s390 elf64-s390 elf32-sparc a.out-sparc-linux elf64-sparc a.out-sunos-big elf32-i386-freebsd coff-i386 elf64-x86-64-freebsd elf64-l1om-freebsd elf64-k1om-freebsd elf32-m32r-linux elf32-m32rle-linux elf32-m68k a.out-m68k-linux coff-m68k versados ieee a.out-zero-big aixcoff64-rs6000 aix5coff64-rs6000 elf32-sh64-linux elf32-sh64big-linux elf64-sh64-linux elf64-sh64big-linux elf32-sh-linux elf32-shbig-linux elf32-spu plugin srec symbolsrec verilog tekhex binary ihex trad-core
Report bugs to <http://www.sourceware.org/bugzilla/>

Try installing 'build essentials' - or whatever Ubuntu calls it.

[Yourcat]

Together with the armel cross gcc the cross strip utility will install.
Do both 'convert' executables work and support the same options?

[NiLuJe]

@nasser: As @knc1 correctly guessed, mine is (mostly) statically linked, while the default one is fully dynamically linked.

Mine's also much, much newer, and much, much faster, so you won't be able to use the default one. (i.e., I built it for a reason ;p). At best it'll crash by going OOM or produce broken output, at worst it won't even run because of unsupported options.

We're talking something like 10MB here, are you really that short on storage space? .

@knc1: Everything should already be stripped, FWIW . And, yeah, libtool leaks the build rpath by default.

[nasser]

Originally Posted by NiLuJe

At best it'll crash by going OOM or produce broken output, at worst it won't even run because of unsupported options.

Thanks for the explanation, NiLuJe! Lucky I didn't try to replace it with the built-in one and possibly brick my new kindles!

Originally Posted by NiLuJe

Mine's also much, much newer, and much, much faster, so you won't be able to use the default one. (i.e., I built it for a reason ;p).

I just checked the build dates across 3 kindle versions:
pw3(/etc/local/bin): 6.6.9-5 Q16 2016-04-04
kt3(/etc/local/bin): 6.6.9-5 Q16 2016-04-04
------------
pw1(linkss/bin): 6.9.0-0 Q8 arm 2014-11-25
pw3(linkss/bin): 6.9.2-0 Q8 arm 2015-08-20
kt3(linkss/bin): 6.9.4-9 Q8 arm 2016-07-08

I can see that you've been updating the build continuously!

Originally Posted by NiLuJe

We're talking something like 10MB here, are you really that short on storage space? .

No! Plenty of space on the new Kindles. Was down to 200MB on my old PW1.. but then I couldn't have tried this on that anyway as the jailbreak for that didn't involve getting an initial factory image onto it. Just my curiosity...

Also, in my poking into the factory image, I see that there seems to be some usbnet and x11vnc stuff there too...
But that's a story for another thread!

[XXCoder]

Originally Posted by knc1

Maybe if there was a way to pre-test all images.

Just picking images at random could cause hard to find problems if one or more images in the set being selected from was 'bad'.

Yes. Very much a yes. I had 4 bad images and I had to do batches of 10 images a time and fixing found bad pictures. Took me quite a while!

Maybe it can be special program that's called by SS function that evals pictures according to strict formatting then moves non-working images to "needFix" folder or something.

[NiLuJe]

@XXCoder: Current snapshots have "Process staging directory" button that forcefully reprocesses everything in the staging directory to make it compliant.

Automating the detection of "bad" images might be doable, but it's potentially fragile and hard to make 100% exact, so, meh :/.

[normanr]

Any chance of a 0.25 release with KFX support? I made sure I had the latest version in the first post (0.24.N - r12287) installed, but it doesn't work with KFX format. I tried the latest snapshot (r13408) and it works great.

Even a note in the first post mentioning that KFX support is only currently available with snapshots (and a more obvious link to the snapshots thread) would be helpful.

[NiLuJe]

@normanr: You're checking old files, the packages in the first post were (stealthily, granted) updated when KUAL 2.7 was released. They're new enough to handle KFX.

[eschwartz]

Using the snapshots is always a good -- actual releases are kind of haphazard.

[knc1]

Current jail break instructions:

It is our policy to use a 'single point of maintenance' model for our released items, with one exception:

• NiLuJe's snapshots, use: (filter prefix: tools, show threads).
  Users should always check the snapshot thread for the most recent build of our after-market add-ins.

[XXCoder]

Originally Posted by NiLuJe

@XXCoder: That's already what's being done . There's even an option to make sure that happens every time the device reboots.

@knc1's comment stands, though, if you happen to have bad images in your pool, that can make it trickier to pinpoint the broken ones.

Sorry but language is little confusing, "being done" is present tense. Is it still being worked or was it done as added as feature?

Originally Posted by NiLuJe

@XXCoder: Current snapshots have "Process staging directory" button that forcefully reprocesses everything in the staging directory to make it compliant.

Automating the detection of "bad" images might be doable, but it's potentially fragile and hard to make 100% exact, so, meh :/.

I'm sure image formatting is standardized, so it should be doable to just load image and check definitions, in least it should be usable image, if gibberish when it passes this test.

[knc1]

Done as an added feature.
Addition is complete.
Get a copy from the snapshots thread to be certain.

[thekoggles]

I've managed to get this installed(only took nearly ripping my hair out, maybe I can't read), but none of the images I try work. I've even tried using the default image, and merely pasting the image into it via an editor and that fails.

I do not know what I'm doing wrong...