Thank You for your continued support and contributions!
After every firmware update the hash of the firmware image must change, correct?. So how does the firmware on chip inside the player recognize the changed hash?
I'm thinking the firmware updater software may tell the firmware on chip what the new hash is. [if so we can just patch the update software with the chksum of hacked image?]
Quote from: Couch on May 06, 2007, 09:42:05 PMAfter every firmware update the hash of the firmware image must change, correct?. So how does the firmware on chip inside the player recognize the changed hash?The hash is stored in firmware update and checked when you do the update.Quote from: Couch on May 06, 2007, 09:42:05 PMI'm thinking the firmware updater software may tell the firmware on chip what the new hash is. [if so we can just patch the update software with the chksum of hacked image?]"Just" doing that is what the last 8 pages of this thread have discussed. If you're interested, you might want to read the thread.
What about updating the wiki? Keeping all the discussed ideas there so people can first check that?
Some functions I've found in the .exe (named them myself):FirmwareChk at 00413E10 (big function, has a lot of checks of nk.bin in it)...ChkSumInit at 004229B0 (has something to do with the CheckSum; I strongly believe it is SHA1 or RIPEMD160) --> this one uses a lot of SHA1 constants, so I believe the SHA1 hash is generated here
Can you post the text of these, please?
Quote from: iSE on May 07, 2007, 11:04:59 AMWhat about updating the wiki? Keeping all the discussed ideas there so people can first check that?I like that idea, 'cause it's a drag to have to sift through the entire thread.
im noob but this is little bit stupid and you should know something like this exists http://imajr.com/198300734_3_78515
so has anyone hooked the hard drive up to the computer and read its contents yet?would it be possible, if the firmware sits on the drive, to just overwrite it with modified firmware, or do one of the chips verify it?
Page created in 0.077 seconds with 18 queries.