Native Fonts & ScreenSavers Hacks for Kindles 2.x, 3.x & 4.x

[omegauo]

Originally Posted by NiLuJe

@omegauo: Unrelated issue. The jailbreak itself is at its essence a single file, nothing to do with the SO.

Thanks, I just checked amazon and it said it was special offers. I got it off ebay so I guess the guy didn't know.

It's odd it only showed up now though, I've had it for a week and was using it when I loaded books.

[NiLuJe]

@omegauo: Not that unheard of. I have yet to see any on my PW, for example (granted, wireless's been off most of the time).

[bluen]

I have a kindle keyboard 3G. I thought I uninstalled all the hacks before trying to update to 3.4 but was unable to update. I got this in the logs below, any suggestions would be appreciated. (I hope this is the right place to post this and apologize if it is not, posted somewhere else but did not get any responses)
Thanks!

ota_install: C defatchatchinfo="/usr/var/cache/fontconfig/f394b45e7a2716944ea2c0aeb5c008aa-arm.cache-2"atch failure

ps dont know why the weird emoticons are showing up above for the letter p

[twobob]

Originally Posted by bluen

I have a kindle keyboard 3G. I thought I uninstalled all the hacks before trying to update to 3.4 but was unable to update. I got this in the logs below, any suggestions would be appreciated. (I hope this is the right place to post this and apologize if it is not, posted somewhere else but did not get any responses)
Thanks!


ota_install: C defatchatchinfo="/usr/var/cache/fontconfig/f394b45e7a2716944ea2c0aeb5c008aa-arm.cache-2"atch failure

ota_install: C def:patch:patchinfo="/usr/var/cache/fontconfig/f394b45e7a2716944ea2c0aeb5c008aa-arm.cache-2":patch failure

ps dont know why the weird emoticons are showing up above for the letter p

wrap it in [ code] blocks [/ code] (without the space)

[bluen]

Originally Posted by twobob

wrap it in [ code] blocks [/ code] (without the space)

Thanks. Does anyone know how to fix what is in the fontconfig folder?

[NiLuJe]

@bluen: Unless you played with fontconfig manually, that shouldn't happen...

Just to make sure it's not something wonky on the fonts hack side, run the 'dummy' update attached to the first post, and post/attach the 'update_testupdate.log' (or something, not at home right now, not sure of the filename) it will create at the root of your kindle.

[bluen]

Originally Posted by NiLuJe

@bluen: Unless you played with fontconfig manually, that shouldn't happen...

Just to make sure it's not something wonky on the fonts hack side, run the 'dummy' update attached to the first post, and post/attach the 'update_testupdate.log' (or something, not at home right now, not sure of the filename) it will create at the root of your kindle.

Thanks, log attached.
On a factory reset deregistered Kindle, I ran the 0.11.N jailbreak and the dummy update. The update.testupdate.txt is attached (renamed .log to .txt)

[bluen]

NiLuJe,

Tried also to upload original log I made when I first tried to update to Amazon's 3.4 update but was too large to upload. Look in your pm and I will send you a link to download this log, thanks.

[twobob]

Originally Posted by bluen

NiLuJe,

Tried also to upload original log I made when I first tried to update to Amazon's 3.4 update but was too large to upload. Look in your pm and I will send you a link to download this log, thanks.

just zip it up.... then you can have 20 Mb IIRC

[NiLuJe]

@bluen: Well, after a factory reset, of course the testupdate log is clean .

One thing you can try is to run

fc-cache -rfv

over SSH (after switching the rootfs rw), that should rebuild the fontconfig cache, hopefully there's not some magic involved, and it'll match the expected md5sum.

[bluen]

Originally Posted by NiLuJe

@bluen: Well, after a factory reset, of course the testupdate log is clean .

One thing you can try is to run

fc-cache -rfv

over SSH (after switching the rootfs rw), that should rebuild the fontconfig cache, hopefully there's not some magic involved, and it'll match the expected md5sum.

Thanks I will look into process for being able to SSH.
Did you look at the log I sent you via pm? That will be a log for installing 3.4 and is where I saw the patch error.

[bluen]

I'm a linux noob but managed to install a stand alone terminal and executed commands.
Got the following output below in the terminal; still kindle refused to update and gave same u006 error.

"usr/share/fonts/ skipping no such dir
tmp/root/.fonts skipping no such dir
/usr/java/lib/fonts caching, new cache contents; 27 fonts 0 dir
usr/var/cache/fontconfig: cleaning cache directory
/tmp/root/ .fontconfig: not cleaning non existent cache directory
fc-cache: succeeded"

[NiLuJe]

@bluen:

After making the rootfs rw (mntroot rw)? With a ro rootfs, it probably ends up in a tmpfs, which is not what we want .

[bluen]

yes made it writeable before i executed commands

[NiLuJe]

@bluen: Huh.

Well, then, your best bet is to extract the files in question from a full 3.3 rootfs backup or go the long way and do a full flash (cf. the debricking thread/k3flasher).