[knc1]

Originally Posted by coplate

yeah, that is the same failure - the SP01 header missing.

Do you know if your user is using windows, mac, or linux?

And I would need to be reminded which file he is using.

I think I can give you a command to combine the headers with the existing package, and it will not require kindletool

it would be a very small file, and the command would look roughly like this, but it depends on the operating system.

copy sp01.header + update_factory.bin = update_factory.signed.bin

And then you would use that signed file. - This would only work if the device is already properly jailbroken.

Here is how I tested it on linux - but I did not install

I did those kindletool command I showed to create the FB03 package type. ( recovery2 )

The signature part of the file only includes the actual data, not the package type.

Then I ran this:

dd if=update.fb03.bin bs=192 skip=0 count=1 of=sp01.header
cat sp01.header update.bin > update.sp01.bin

It may be easier to get your person to download kindletool and run those command I gave though.

Or if you can do these commands And give them this fle to try. I dont have a good place to do this and make the file public

the FB03 ( recovery2) packages are safer, bucause you can put the device type in them, so you are less likely to brick someones device, buy using the wrong package.

There is a problem with any system image package signed with our key -
We only put our key into the 'main' system.

System image packages must be installed while the Kernel is still running its ram resident system.
And we do not put our key into its initramFS.

For a very good reason we have never put our key into the initramFS.
Specifically to prevent the Kernel from installing anything (from our KindleTool) while running ram resident.
The only way something from our KindleTool can be installed is while running in 'main' and the user intentionally puts the package onto the system.

It is a security thing.