It should have wiped the entire partition before the error message. If you do not want the error message, the quick and dirty way is to add 2>/dev/null to the end of the command.

The "right" way is more complicated (which I try to avoid whenever possible), and requires that you find out how many blocks your destination has. There are a number of ways to do that. Using "fdisk -l" is one of them (but those are 512-byte blocks, so you have to divide by 8 to get 4K blocks), or you can use "df" (but that gives 1K blocks so you need to divide by 4). Then you need to add the computed block count to the "count=" parameter of "dd".

As you can see, it is a lot more complicated than my one-line answer, which just ignores the "normal" error when the device gets full.

Another way would be just to write enough to "kill" the partition format, such as "count=1000" or something...

The point is to make the partition no longer mountable, so that the startup scripts will reformat that partition during the next reboot.

the original 5.0.4 firmware update,and after the error the kindle stucked at the "wait a moment while your kindle starts up"and I failed to reset it by holding the power button,the only way to recover it is to selectboot to main via mfgtool,this also happen when i tried to reboot my device through restart the device in the setting menu

the original 5.0.4 firmware update,and after the error the kindle stucked at the "wait a moment while your kindle starts up"and I failed to reset it by holding the power button,the only way to recover it is to selectboot to main via mfgtool,this also happen when i tried to reboot my device through restart the device in the setting menu .

the original 5.0.4 firmware update,and after the error the kindle stucked at the "wait a moment while your kindle starts up"and I failed to reset it by holding the power button,the only way to recover it is to selectboot to main via mfgtool,this also happen when i tried to reboot my device through restart the device in the setting menu

what's more,I tried to jailbreak it by use yifanlu's jailbreak.mp3 and uninstall jailbreak.bin. however it's impossible to run the bin since the kindle stucked at the wait for kindle restart screen in all condition

what's more,I tried to jailbreak it by use yifanlu's jailbreak.mp3 and uninstall jailbreak.bin. however it's impossible to run the bin since the kindle stucked at the wait for kindle restart screen in all condition

The mp3 jailbreak method was disabled in firmware newer than 5.0.0.

You can use a RUNME.sh with my generic data.tar.gz.

You should try setting the bootmode idme var to main.

If you can boot to main using MfgTool, then you should be able to use MfgTool to boot to fastboot or diags.

In fastboot, do:

fastboot setvar bootmode main

or in diags, from a RUNME.sh (or from an SSH shell if you installed mmcblk0p2_ssh) do:

If you did, that might prevent the update to 5.0.4. You can flash a 5.0.0 main kernel image, but somebody needs to upload one and provide a link to it.

Or you can flash a main mmcblk0p1 image from a 5.0.4 kindle.

Another thing that can prevent updates to 5.0.3 or earlier is having changed files that the update wants to patch. The 5.0.4 update replaces entire files as needed instead of patching them, but it also updates the main kernel and may fail if that is not what it was looking for.

If you did, that might prevent the update to 5.0.4. You can flash a 5.0.0 main kernel image, but somebody needs to upload one and provide a link to it.

Or you can flash a main mmcblk0p1 image from a 5.0.4 kindle.

Another thing that can prevent updates to 5.0.3 or earlier is having changed files that the update wants to patch. The 5.0.4 update replaces entire files as needed instead of patching them, but it also updates the main kernel and may fail if that is not what it was looking for.

i have flashed a 5.0.4 kernel,can you provide a 5.0.0 kernel image?or when the 5.0.5 is released it will be possible for me to update?

If you did, that might prevent the update to 5.0.4. You can flash a 5.0.0 main kernel image, but somebody needs to upload one and provide a link to it.

Or you can flash a main mmcblk0p1 image from a 5.0.4 kindle.

Another thing that can prevent updates to 5.0.3 or earlier is having changed files that the update wants to patch. The 5.0.4 update replaces entire files as needed instead of patching them, but it also updates the main kernel and may fail if that is not what it was looking for.

or is it possible that i can get a main mmcblk0p1 image from a 5.0.4 kindle?and now de RUNME .sh doesn't work any more,i couldn't install my Chinese language pack either,why?

i have flashed a 5.0.4 kernel,can you provide a 5.0.0 kernel image?or when the 5.0.5 is released it will be possible for me to update?

There is now a download link for touch main kernel 5.0.0 in the first post for this thread.

Quote:

Originally Posted by qtybest

or is it possible that i can get a main mmcblk0p1 image from a 5.0.4 kindle?and now de RUNME .sh doesn't work any more,i couldn't install my Chinese language pack either,why?

You can get a main image from a 5.0.4 kindle with the "dd" command, as documented in many posts.

RUNME.sh is launched by a payload that is installed by various data.tar.gz files. Some payloads only work booting from main (not diags). Others only work on SOME kindle models and can severely brick a kindle if installed on the wrong kindle model. That is why I wrote a generic data.tar.gz that has a generic payload that works on ALL kindle models. I tested the payload that it contains on DX,DXG,K3,K4,Touch. The K3 and earlier need the payload installed manually because they do not automatically extract data.tar.gz. My generic payload also works booting from both main and from diags. In fact, it MUST boot from diags for a RUNME.sh to be able to write to the idme vars (such as bootmode). The idme command in the main boot is read-only.