Print

[the soul poet]

Hi, followed tutorials and I got the pc to backup the firmware, however how do I know this is actually the firmware by way it was the only drive plugged in except floppy drive?

[majik655]

QUOTE(the soul poet @ Oct 28 2006, 05:42 AM)

Hi, followed tutorials and I got the pc to backup the firmware, however how do I know this is actually the firmware by way it was the only drive plugged in except floppy drive?

1. if the read worked 100% done then more than likely is fine..
2.  check orig.bin file and make sure it is 256k
3. open orig.bin file with 360 toolbox 2.0 if it opens sucessfully with NO errors
and shows you your dvd key in the key box (which you should probably copy)
then you are fine!    copy this key into hacked firmware of choice by simply opening
hacked firmware of choice with 360 toolbox ... erase the FFFF's shown in the key box...
then paste the key you copied from orig.bin into key box.. then press replace key button..
your hacked firmware is now ready to be flashed to the drive.

[langnao]

For samsung firmware, I would not recommend to use the toolbox to inject the key. Get the xtreme firmware package e.g 4.2 and use the 'make 4.2a' or 'make 4.2b' link from the package to inject the key. It so much easier and less steps to introduce errors.

If it is hitachi drive, even easier, just run the respective batch file to patch...

I think quite a few newbie could have use toolbox wrongly and thus screw up their drive ...


If you are afraid of corruption during dumping of firmware. Dump it twice, and hex byte by byte compare the files, they should be the same. The firmware is 256K in size. And pls, if possible, DON'T use a floppy disk for boot up to flash. It can give you write error when u dump the firmware to the disk and worse still, read error during reading of the hacked firmware to be transfered back to the drive and thus result in failure in flashing ...

[majik655]

QUOTE(langnao @ Oct 28 2006, 10:37 AM)

For samsung firmware, I would not recommend to use the toolbox to inject the key. Get the xtreme firmware package e.g 4.2 and use the 'make 4.2a' or 'make 4.2b' link from the package to inject the key. It so much easier and less steps to introduce errors.

If it is hitachi drive, even easier, just run the respective batch file to patch...

I think quite a few newbie could have use toolbox wrongly and thus screw up their drive ...
If you are afraid of corruption during dumping of firmware. Dump it twice, and hex byte by byte compare the files, they should be the same. The firmware is 256K in size. And pls, if possible, DON'T use a floppy disk for boot up to flash. It can give you write error when u dump the firmware to the disk and worse still, read error during reading of the hacked firmware to be transfered back to the drive and thus result in failure in flashing ...

First off let me say you are right I agree with you some what but please do not take the rest of this wrong.. its just me comming back to what I was saying ...

First off he has a samsung ms28 ...
toobox in my opinion is great for samsungs (of course 2.0 since it is more up to date)
but for hitachi's you are right.. that is where the errors come from because of the encrypting..not to mention it is not really needed since the patching is done in the release.. so even if you do the encrypting the release just does patching.. you do not use the image with hitachi's.. so yes ALOT of people can screw this up bad...

but for samsung it is great.. for 2 reasons.
IT IS COMPATIBLE
and if the image is corrupted at all toolbox will give you an error.  Hence why it is kinda good to just try to open the image just to see (it is just another check)
if it opens then it even shows you your dvd key immediately.  And there are no people complaining about toolbox putting in the code in the wrong area... such as KDX which always had issues!!! and still does!!

So yes you are right because it is easier to just have the patching or batch do it for you.. in fact you kinda do not have a choice unless you change things.. which newbs are or should not do.

Since he was wondering if it was good BEFORE doing auto patching and/or batching (which is perfectly fine and recommended anyway) then what I was saying is the way to go.  

But you are correct.. the ways you mention are easier because of less steps but not manually checked before hand as I was thinking he/she was asking about.

[langnao]

QUOTE(majik655 @ Oct 29 2006, 01:52 AM)

First off let me say you are right I agree with you some what but please do not take the rest of this wrong.. its just me comming back to what I was saying ...

First off he has a samsung ms28 ...
toobox in my opinion is great for samsungs (of course 2.0 since it is more up to date)
but for hitachi's you are right.. that is where the errors come from because of the encrypting..not to mention it is not really needed since the patching is done in the release.. so even if you do the encrypting the release just does patching.. you do not use the image with hitachi's.. so yes ALOT of people can screw this up bad...

but for samsung it is great.. for 2 reasons.
IT IS COMPATIBLE
and if the image is corrupted at all toolbox will give you an error.  Hence why it is kinda good to just try to open the image just to see (it is just another check)
if it opens then it even shows you your dvd key immediately.  And there are no people complaining about toolbox putting in the code in the wrong area... such as KDX which always had issues!!! and still does!!

So yes you are right because it is easier to just have the patching or batch do it for you.. in fact you kinda do not have a choice unless you change things.. which newbs are or should not do.

Since he was wondering if it was good BEFORE doing auto patching and/or batching (which is perfectly fine and recommended anyway) then what I was saying is the way to go.  

But you are correct.. the ways you mention are easier because of less steps but not manually checked before hand as I was thinking he/she was asking about.

I don't think toolbox does any check (checksum or whatever) on the firmware. to test for corruption or whatever. It just basically retrieve from 0x40EC the key (for samsung). I purposely screw up a whole chunk of codes + the key and it still open fine. Thus during dumping, due to whatever reason, the firmware might not be written correctly (a few bytes in wrong value or whatever) and toolbox will still open it good ...

[the soul poet]

cheers guys, was running out of time to go out so had to take a chance before I got an answer, I dumped firmware twice and compared em both twice with hex edit, I also used the make x41a.bat