SamyGO

Himmm, could you enable debug and watch process from ExLink cable to identify where is the problem? Thanks.

Erdem, I tried to decrypt an image encrypted with the patch-tool you developed. I get a message I think thats the error preventing successfull flashing.

Just feeding 16 bytes at the end of de-/encryption is the wrong way. You need to call a final-routine.

mprotect wrote:Erdem, I tried to decrypt an image encrypted with the patch-tool you developed. I get a message

Code: Select all

Decryption failed (final).

I think thats the error preventing successfull flashing.

Just feeding 16 bytes at the end of de-/encryption is the wrong way. You need to call a final-routine.

Himm, I am unaware of that. I thought that because 32 byte blocks used on AES. So thats corrupts the image than file not flashed.
I will check that script and try to fix that ASAP. Thanks.

EDIT:
I have investigate the script and saw that, I add padding bytes after the encryption, while writing to file! There is also problem on signature area which is null '\0' (0x00) instead of '0's (0x30). Signature needed to be in ASCII I think. About finalizing AES, In python, there is no finalize required. I fixed the scripts padding areas and it works as it Encryption_Update application if you update its salt section with "SamyGO__" string.

So lets try again to Flash your device with PRE3 release.
Thanks.

this failure comes when starting the Firmwarepatcher (pre3_0.16)
greets
rubinho

rubinho76 wrote:this failure comes when starting the Firmwarepatcher (pre3_0.16)

Code: Select all

 File "SamyGO.py", line 505
    print 'Error AES Block size is not 16!' )
                                            ^

greets
rubinho

I really upset to myself. I am coding as a dump this days. That '(' needed to removed. There is also some problems too at CRC check code. I removed all and now its looks working. Now uploded the PRE4. Please test if you has a courage to venture this programmer mistakes.

I just tested PRE4 a bit. After patching validinfo.txt looks like this: I think there's missing a leading '0' in the checksum (checksum is right).

mprotect wrote:I just tested PRE4 a bit. After patching validinfo.txt looks like this:

Code: Select all

*007_exe.img_ 3961f0a*011_appdata.img_67487d54

I think there's missing a leading '0' in the checksum (checksum is right).

I though that I fixed that error at PRE4. Fixed in PRE5...
I don't know how much PRE release before release

At last. If you verify the update, than I will release final v0.16. It's really good to announce that in weekend holiday.