Thank You for your continued support and contributions!
Perhaps I'm not understanding this correctly, but isn't the code that checksums the new firmware file already on the player?
Changing the part of the firmware that dictates what happens when the checksums don't match in the firmware being transfered won't help any.
If there's a way to run .bin files (an ARM emulator perhaps?) that might allow the firmware to be debugged, but without knowing the checksum algorithm, the only option is to access the firmware data on the ZVM, and modify it that way.
Do I understand this right, or am I just saying stupid things?
I've been able to get the ARM code for the nk.bin using EMU8086 emultator, but the firmware uploader is too big to load for some reason. If anyone knows of anythin that will disassemble a file n output the ARM code to a txt file to read through, that would be very benificial. Where would the algorithm be tho? Surely it will only be in the bootloader? Because creative will calculate it at their end n only on the player. There would be no need for the nk.bin nor the firmware updater program to calculate the checksum.Since this is the case, would it be possible to modify some firmware to be uploaded directly to the HDD, which would output the algorithm? Long shot I know but might be worth a hefty effort if it works?
Well sure, if you can post the code for it I'll take a look. But why would the checksum of the firmware ever need to be calculated unless verifying it to be real and when first inserting the checksum into the file?
I've been able to get the ARM code for the nk.bin using EMU8086 emultator, but the firmware uploader is too big to load for some reason.
If anyone knows of anythin that will disassemble a file n output the ARM code to a txt file to read through, that would be very benificial.
Since this is the case, would it be possible to modify some firmware to be uploaded directly to the HDD, which would output the algorithm? Long shot I know but might be worth a hefty effort if it works?
If, say, the firmware updater does indeed calculate the checksum of the nk.bin file and then upload it to the firmware, and the firmware is merely a series of commands designed to upload an inbuilt nk.bin file, can we not change the nk.bin file slightly, put it back into the firmware updater program, and then try that to upload it to the Zen?
Quote from: iSE on July 11, 2007, 11:56:28 AMIf, say, the firmware updater does indeed calculate the checksum of the nk.bin file and then upload it to the firmware, and the firmware is merely a series of commands designed to upload an inbuilt nk.bin file, can we not change the nk.bin file slightly, put it back into the firmware updater program, and then try that to upload it to the Zen?You could try, if you know how : )
Didn't you try this on the previous page?
I don't know that this will work, but assuming the firmware updater .exe file uses the same checksum algorithm as the firmware itself, wouldn't it be possible to use the updater to generate the checksum we need, without having to know the algortihm?
Page created in 0.125 seconds with 21 queries.