Print

[Tron[ADS]]

I have an MS28 that has an unusual key, which after discussion with Caster420 some months back, we identified that it was incorrectly triggering the "no valid key" found in SAMTOOL. The key is infact genuine, and was written back to the drive under 5.2 and later 5.3 guises.

And so to Ixtreme1.0........ unfortunately, I now seem unable to create a valid Ixtreme firmware bin file as the creation code is dumping me out because its thinking I have a bad orig.bin, when its prefectly good, just unusual in its more than 3 duplicated bytes.

I've sent Caster420 a PM asking for his advice on the matter, but have also posted here for advice so I can try to figure it out.

What I am doing is placing my orig.bin file in a folder, along with the fw folder, new version of samtool, and "make ixtreme firmware.cmd". I then run "ixtreme firmware.cmd", and it seems to first shell out to samtool to verify orig.bin. This thinks there is no valid key, returns an error, and the whole thing exits with no ix10.bin created.

What I have tried to do is delete samtool.exe, and run the cmd file. I then get an error message indicating samtool not found, followed by "Ixtreme v1.0 firmware created : ix10.bin".

BUT, when I inspect ix10.bin,Ive found that where the key on my orig.bin is located at byte 40EC, there is no corresponding key found there in ix10.bin. In fatc Ive searched in the whole file for some bytes from my key, and its not there anywhere.

Obviously im a bit stuck, and what I need to know to fix it myself really is, is the ix10.bin file identical to xtreme10a.bin (as its a ms28 reporting as a ms28) but with the unique key insterted into it, or is there more to it than that. What Im thinking is, could I rename xtreme10a.bin and manualy add my key to it in the right place using my hex editor ?

Please help !

This post has been edited by Tron[ADS]: May 30 2007, 07:23 PM

[sosotiit]

if you know how to work wiht an hex editor transfer it at the same postion using this by caster
Using A Samsung With A Hitachi Motherboard, How to properly create your Samsung Xtreme firmware.

soso

[Tron[ADS]]

I'll take a look at that docco, but im not sure how relevant it will be to me, as that seems to be how to manualy edit firmware to spoof for Hitachi's....mine is a simple Samsung MS28 to Samsung MS28.

I think I can give it a go without any real risk of damage... heres my plan of attack..

1. Run someone elses orig.bin through make.bat and produce ix10.bin
2. find a binary compare utility and compare ix10.bin to xtrem10a.bin
3. hopefuly I'll see ONLY the key bytes at 4000- different.
4. if thats the case, ill simply manualy inject my personal key into xtreme10a.bin and give that a go.

Sound reasonable ?

Anyone suggest a freeware hex/binary compare utility ?

[sosotiit]

the first part is hex editing,
but basically transfer in hex editor from address 4000 to well after you key let say 4200 the the ixtrem10a.bin
-soso

[Tron[ADS]]

Thanks for your input.....Ive had another idea which ive just tried out, see if this makes sense....

What ive just done is edited 2 bytes in the key of my orig.bin which takes away the duplicate key issue in samtool.
Ive then run the make firmware cmd, which now doesnt complain, and produced an output file.
Ive gone into the output file and found the 2 digits I changed in exactly the same place, and changed them back to what they were in my original backup.

So, I "THINK" I not have a good ixtreme1.0 firmware file to flash........

What do you reckon ?

This post has been edited by Tron[ADS]: May 30 2007, 08:08 PM

[sosotiit]

not sure  (IMG:style_emoticons/default/uhh.gif) , not saying no, just not familiar with that. Maybe caster will get back to you.
-soso

[Tron[ADS]]

He has gotten back to me, and he remembered the weird key of mine. He has suggested I use firmware toolbox, load my orig.bin up, copy the key, then load uop xtrem10a.bin up  and replace the key with mine, then flash the resulting xtreme10a.bin

Comparing that with my method shows that mine places the key in the same location as the original, but fwtoolbox places it earlier in the 4000- block.  I know there are varying amounts of padding in this area, but what I dont know if it matters how many "pads" there are.

Im tempted to flash mine first to see if it works, based on the closest to original version as possible theory....but ive asked Casters advice on that, so I'll wait to see what he thinks.

I think its pretty much resolved now, but I hope this thread will help someone else in the future though....if anyone else has an oddball key like mine.

And the final reply from caster is that it doesnt matter, either mine or FWtoolbox will work. Ill be flahsing mine later, based on the premise of it being identical to the original.

Thanks everyone.

[sosotiit]

Yes toolbox lose the placeholder!!, note that no one knows what they are used or if they are used for something. Just like you I prefer an exact replica of key and placeholder.

I usually  transfer in hex editor from address 4000 to 4200 the hacked.bin, If you want to validate just make sure you have all FF after you key to 6000.

good luck
soso