Custom screensavers on new K4NT 4.1.0

[gers1978]

I got a K4NT 4.0.1 brand new yesterday and immediately updated to 4.1.0.

I've tried all different methods mentioned on these boards to get custom screensavers working, and I always either get Update Error 3, Update Error U007 or simply nothing happens (RUNME.sh) is still on the root of my Kindle after restart.

I know it can be done, as my girlfriend's K4NT 4.1.0 is done with the simple method (i.e. screensaver folder on root of Kindle) and my old K4NT 4.1.0 was done (with the linkss/screensaver folder).

The only difference I can see is that both of the older ones had custom screensavers applied on 4.0.1 then were updated.

[knc1]

Is this a K4 SO (Special Offers) machine?

[gers1978]

No, standard £89 Kindle.

[knc1]

Originally Posted by gers1978

No, standard £89 Kindle.

What are the first four characters of the serial number?

[gers1978]

B00E, why?

[knc1]

Originally Posted by gers1978

B00E, why?

Because of two reasons:

You where not clear as to what error code(s) you where seeing in response to what actions you took;

There are known to be some national variations of the firmware without changes in the public firmware version.

/etc/version.txt will have the build id number and build date in it, but we (members of mobileread) have not started collecting an index of which ones have which problems.
So even if you told us that information, it wouldn't mean anything at the moment.

But now that we have your model number, someone might recognize it as one of the problem models.

[gers1978]

Originally Posted by knc1

Because of two reasons:

You where not clear as to what error code(s) you where seeing in response to what actions you took;

There are known to be some national variations of the firmware without changes in the public firmware version.

/etc/version.txt will have the build id number and build date in it, but we (members of mobileread) have not started collecting an index of which ones have which problems.
So even if you told us that information, it wouldn't mean anything at the moment.

But now that we have your model number, someone might recognize it as one of the problem models.

Ok, thanks

[gers1978]

I've been trying again today using all methods I can find, and at no point does the RUNME.sh ever execute (I'm assuming this is the case as every time I reboot, the RUNME.sh file is always still on the root of my Kindle

[geekmaster]

On the new firmware versions you need to boot to diags to INSTALL the data.tar.gz payload, then you need to boot again to run that payload.

The RUNME.sh does not delete itself. Depending on which payload you installed, it may create a RUNME.done that PREVENTS it from running again. You need to delete any RUNME.done to run it again on the next reboot.

[gers1978]

So put an ENABLE_DIAGS file onto the root, then what?

EDIT: Got it, I booted into DIAGS mode with data.tar.gz in place, did a Reboot from Diags mode, then Exited Diags, then put RUNME.sh on the root then Restarted

[coolwes123]

I was following the steps but as I went into diagnostics mode my Kindle screen went completely black with white lines in the middle. I tried the full hard reset on it but its not working. I have no idea what to do can someone help me???? D:

[geekmaster]

Originally Posted by coolwes123

I was following the steps but as I went into diagnostics mode my Kindle screen went completely black with white lines in the middle. I tried the full hard reset on it but its not working. I have no idea what to do can someone help me???? D:

Charge the battery with a wall charger first. Then boot to fastboot with MfgTool and charge it some more. Then trying diags again...

We recently discovered that some kernel images are a little short (up to 64 bytes too short), which can cause problems in some cases. That could be why the 4.0.1 images sometimes caused problems for some people. New kernel images will be uploaded if needed (soon).

[coolwes123]

Originally Posted by geekmaster

Charge the battery with a wall charger first. Then boot to fastboot with MfgTool and charge it some more. Then trying diags again...

We recently discovered that some kernel images are a little short (up to 64 bytes too short), which can cause problems in some cases. That could be why the 4.0.1 images sometimes caused problems for some people. New kernel images will be uploaded if needed (soon).

Thanks, all I had to do was charge it.

[coolwes123]

I was trying to log into root in my kindle but when I type the password mario it says access denied isn't that supposed to be the password?
or did it change when my kindle got updated to 4.1.0?

[knc1]

It changed.
Help available in the wiki index for the K4