fi2 encoder/decoder

flarn2006

40

Re: fi2 encoder/decoder

« Reply #70 on: 06 / August / 2010, 21:17:13 »

Advertisements

I want to use this, but I don't have a G9 or a G10. Where can I find the key for the SX110IS?

Logged

fe50

3139
IXUS50 & 860, SX10 Star WARs-Star RAWs

Re: fi2 encoder/decoder

« Reply #71 on: 07 / August / 2010, 03:58:49 »

Quote from: flarn2006 on 06 / August / 2010, 21:17:13

I want to use this, but I don't have a G9 or a G10.

You don't need a G9 or G10 - just a dump file to "extract" the keys from

... read the first posts in this thread ...

Logged

-->FIRMWARE DUMPS<-- * Manual * Lua * me

flarn2006

40

Re: fi2 encoder/decoder

« Reply #72 on: 07 / August / 2010, 16:57:59 »

Yeah, but what address?

Logged

emlyn

88

Re: fi2 encoder/decoder

« Reply #73 on: 20 / August / 2010, 17:38:09 »

I've found the key/iv for the Ixus 130 (SD 1400 IS), it's probably the same for all 2010 cameras.
In the 1.00c dump, the key is at address 0xFFFF3568 and the iv (unchanged from G10) is at 0xFFBEDC48.

EDIT:
The addresses are with the file loaded to 0xFF810000, so they are at offsets 0x7E3568 and 0x3DDC48 respectively from the start of the file.

EDIT2:
Fixed the address of the iv, somehow I had the wrong value.

« Last Edit: 09 / September / 2010, 03:40:45 by emlyn »

Logged

hwntw

159

Re: fi2 encoder/decoder

« Reply #74 on: 20 / August / 2010, 18:14:26 »

Will you dare to go into print with said strings?

Logged

Ixus 300HS S100

Windows 10

emlyn

88

Re: fi2 encoder/decoder

« Reply #75 on: 20 / August / 2010, 18:32:52 »

Quote from: hwntw on 20 / August / 2010, 18:14:26

Will you dare to go into print with said strings?

See your private messages.

Logged

ultimA

137

Re: fi2 encoder/decoder

« Reply #76 on: 24 / August / 2010, 00:30:54 »

I wanted to bring manual loading support to the SX20. I know it is stated a thousand times that CHDK does not support this for this camera, but it was never said why. I thought it was because no one has bothered finding the key/iv for it. So I spent hours crawling the ASM-jungle and when I finally found them, in the middle of my ecstasy (no complaint about the bad format of the update file anymore), I received the infamous E31 error. The CHDK splash screen even shows up a for a sec, and the camera turns off.

So, since this was never really answered before (or at least I could not find it nowhere after reading through all the related forums and wiki pages): Why doesn't it work? Does anybody know what is needed to make it work? I know some other cameras have the same problem, such as the G11. What is the exact reason for this "SUBCPU" error (which is overly annoying as it shows up permanently in the ver.req screen), which code in CHDK is responsible for it and what would have to be done to support manual loading on these cameras?

Logged

waldo

238

Re: fi2 encoder/decoder

« Reply #77 on: 11 / September / 2010, 11:46:12 »

I have started porting the S95. I can find the standard "d4" IV, but cannot find the d4 or d4a key. However, I found what appears to be the key at offset 0x7E3624 from the beginning of the S95 1.00E dump located at http://drop.io/chdkdumps3

Can someone check me on this? Should we call this the "d4b" key?

Logged

reyalp

13946

Re: fi2 encoder/decoder

« Reply #78 on: 11 / September / 2010, 16:27:16 »

Yes

Make sure you can create a working FI2 with this.

Logged

Don't forget what the H stands for.

waldo

238

Re: fi2 encoder/decoder

« Reply #79 on: 13 / September / 2010, 21:28:44 »

I can confirm that a build with the "d4b" key on the S95 boots and lets me turn LED's on and off. Changing the key slightly gives the message "Update File Error !" after selecting "Firm Update". I assume this means my key is correct.

Logged