Print

[hobogoonie]

Ok, sorry for being stupid. I've sucessfully flashed my drive this week with XTREM52D.BIN. My drive is an MS-25. It works fine.

I then flashed a friends MS-25 exactly the same. Fine.

The 3rd and last ddrive I did was an MS-28. I used Textbooks guide (superb) and also used XTREM52D.BIN. It worked fine.

Now my question is. Am I supposed to use a different firmware file on an MS-28?

What are all the different BIN files actually for?

 Also, I want to re-flash a friends Samsung. He has a very old firmware on it. Some kind of Sammy tho.

Are the other BIN files used when upgrading old flash?

Sorry for all these questions I just want to be 110% sure before I do another and wether I need to do anything to the ones I've already done.

Thanks.

[myfranco]

You need nothing to flash ms28. 4.x and above are based on ms28
For ms25 you need to spoof the fw.Use the .cmd file included in the firmware folder.

[Trune]

i couldnt work this out either.

I flashed an Ms-25 drive and didnt use any of the other files, other than the file starting with Xtreme*.*

So what are all the other bin files for?

[bigmac161]

Hi i flashed a ms-25 last night using the 52c-ms25.bin,loaded it into xtreme bootmaker got all the errors saying firmware unknown so klutsh told me to do this so XBM reads it

QUOTE

Only the xtrem52a.bin, xtrem52b.bin, xtrem52c.bin, xtrem52d.bin firmwares were added to the definition file.

You can easily add custom definitions to the xml file though, just use the MD5 XBM gives on an unknown.

for you file add something like
Code:
<firmware md5="2C9ECF2C43A0167C39385B2BA98A46C8">
<name>Xtreme 52c-ms25</name>
</firmware>
to the extremeDef.xml

Works with XBM now i just opened 360 toolbox and replaced the key with my orig one and all was fine

[hobogoonie]

I really dont get why their not already added to the definitions? seems a bit odd to me.

[gam3r]

id like to know why there are so many. Before you say search the forums or read the readme i have done it..

[scrano]

I hope I'm understanding what you're asking properly and I'll keep this as short as I can without leaving out anything I think you may want an answer too.

The short answer is that all of the .bin files included in the package are just templates used to create different versions of the Xtreme 5.2 firmware based on what your needs are.

You really shouldn't even worry about them anyways 'cause all you should be dealing with is the "Make Xtreme Firmware" file included in the package

The first option your given is to choose for your 360 DVD drive's default speed for all disc's based on what suits your needs best.

Then because the Xtreme 5.2 firmware is based on the Samsung MS28 because that firmware has several features (like firmguard) that are helpful for other version drives (like the MS25)

With some of the recent dashboard updates some 360's started checking to see that the drive in that console was the same model as the one that shipped with it. This caused e66 errors on a lot of consoles because the 360 would report that the drive was an MS28 (remember that's what the core of the Xtreme 5.2 firmware is).

An option was added so after people picked what speed they wanted their DVD drive to read their disc'c by choosing either the A,B,C or D versions of Xtreme 5.2 they then get the choice to choose what they want their new 5.2 firmware to report to the console as. So if they had an MS25 drive they would choose "Report As MS25". This stopped people gettting e66 errors. This is also very helpful for people that have switched from a Hitachi drive to a Samsung. If they originally had a Hitachi v46 drive, they could choose the "Report As HT46". This would tell the 360 that the drive was a Hitachi v 46 drive instead of a Samsung.

I hope this explains the need for all of the different .bin files in the Xtreme 5.2 firmware package

[Trune]

i see.

Should i have ran the Make xtreme firmware.bat file then?

I must admit i forgot, as i started following the Textbook PDF guide which told me to run the samhack after samread (power cycle first etc).

The drive works fine mind you.

However, was i supposed to run the Make "Xtreme Firmware.bat" to make my drive still look like a MS-25? Or does this not effect me because my console was made in 2005?

[scrano]

Yeah you just put your original firmware in the same folder as the "Make Extreme Firmware" file and then run the "Make Extreme Firmware" file, you then choose what options best suit you and it will create a custom hacked firmware that's already edited with your drive key. All ready to be flashed. Very simple

[bigmac161]

As far as ive been told the files in the xtreme FW folder are the same firmwares but for different drives alot of ppl just use the standard xtreme52.bin and use make firmware cmd but why spoof it into thinking its a ms-25 when there is a firmware allready there for the ms-25

[scrano]

QUOTE

As far as ive been told the files in the xtreme FW folder are the same firmwares but for different drives alot of ppl just use the standard xtreme52.bin and use make firmware cmd but why spoof it into thinking its a ms-25 when there is a firmware allready there for the ms-25

You're part right but it's a pointless way of doing it when there's a much easier way

First of all the Xtreme firmware for MS25 uses an MS28 for the core of the firmware, it is for this reason that you need to spoof the firmware to report as the drive that you need it too

Secondly the .bin firmware files in the Xtreme firmware package are only for for Samsung drives (not Hitachi's) and they have been hex edited, so when they are loaded in Firmware Toolbox they identify themselves as whatever drive for. As they are, they are missing drive keys which is why they are more or less just templates. You can hex edit any of them with your drive key manually and they will work, but you need to choose the appropriate one for your drive.

This is why the Make Xtreme Firmware file is included in the folder to begin with

I suggest to have a better read of the ReadMe file included in the package so you underatand how to use it

[bigmac161]

QUOTE(scrano @ Jan 20 2007, 04:58 PM)

I suggest to have a better read of the ReadMe file included in the package so you underatand how to use it

I have and i do understand but if i know my drive is a ms-25 and i prefer to add my key manually so i can double check it,it would be just as simple just to use the firmware for my drive and copy and paste my cd-key using 360 toolbox thats all i was saying,i dare say after using the cmd a lot of ppl still check their keys in toolbox or keychecker just to be sure

[gam3r]

i thought you could just load e.g xtreme52c.bin into xtreme bootmaker and run samhack/read? is that ok or am i talking rubbish? all the tut's i have read dont mention using the makextreme.bat

[scrano]

QUOTE

I have and i do understand but if i know my drive is a ms-25 and i prefer to add my key manually so i can double check it,it would be just as simple just to use the firmware for my drive and copy and paste my cd-key using 360 toolbox thats all i was saying,i dare say after using the cmd a lot of ppl still check their keys in toolbox or keychecker just to be sure

That's totally your choice and their is nothing wrong with that and you can just use any of the ready made firmware .bin files like you said if you want, but what I'm saying is why would you go ahead and do something manually when you have a ready made wizard (which is basically what the Make Extreme Firmware file is) to do it for you (which by the way I'm yet to see screw anyones firmware or drive keys up). I mean Commodore4Eva includes the Make Extreme Firmware file in the package for a reason (simplicity). If it's good enough for him then it's good enough for me

QUOTE

i thought you could just load e.g xtreme52c.bin into xtreme bootmaker and run samhack/read? is that ok or am i talking rubbish? all the tut's i have read dont mention using the makextreme.bat

You can defiinitely just use that method. If you do choose to use the Xtreme Boot Maker and samhack/samread method then you need to remember  that you've still gotta choose the appropriate speed firmware for you (A,B,C or D) and then choose the version of that speed firmware that reports the appropiate drive back to your 360, otherwise you risk gettingthe e66 error. Also keep in mind that X360SAM (which is the samhack/samread tool) is the method that the Make Extreme Firmware file uses to create your hacked firmware anyways so you're not gaining any advantage anyways.

The only reason using the Make Extreme Firmware file method has yet to be inlcuded in any tutorials is because either they don't think that it needs to be, because A.) it's very easy to use, B.) the ReadMe clearly explains how to use it, or C.) they just haven't gotten around to it yet.

If you do use the wizard (the Make Extreme Firmware file) you can still always check your hacked firmware with Firmware Toolbox to see if your key is right if you want.

[hobogoonie]

Ok, so I want to flash an MS-25. But all I have used is Xtreme bootmaker and textbooks tutorial. I like the way xtreme bootmaker prepares my USB perfectly. But if I use 52d-ms25.bin XTREME bootmaker does not recognise it as a valid firware file. Am I ok to use this? Also, does it basically report the drive backas an ms-25 to avoid the e66 error?

The only reason I ask is so I know wether I can leave the make xtreme firmware util alone and just use xtreme bootmaker. I've no problem if I cant use it, I would just prefer it that way.

One more thing, I had read somewhere that not all of the key programs use the full range for the key? I cant remember where I read it, but am i safe in just using xtreme?

Would using bootmaker with 52d-ms25.bin setup be the way to reflash an ms-25 wrongly flashed with XTREME52d.bin using badflash 10sec method?

sorry for the mountain of questions. I do apologise.