Print

[scrano]

The Make Extreme Firmware file is there to simply make life easier for you.

You are fine to use any of the .bin files in the package as long you pick the one that suits your needs.

The latest version of Xtreme Boot Maker was written before Xtreme 5.2 and this is why your getting the error.

You need to first decide what speed version of the firmware that you need (A,B,C or D) and then you would pick the version that is correct for your console.  So if you wanted the D version of Xtreme 5.2 and you needed it to report to your console that your DVD drive was an MS25 you would use 52d-ms25.bin.

I hope this helps

[Trune]

yeah very helpful thanks.

Chosing speed of the firmware wasnt a problem etc, but it seems i may have selected the wrong file, seeing as i just flashed with the xtreme named firmware. Not the drive specific one. Works fine mind you. lol.

Should i reflash with the Ms-25 file? or just leave it be seeing as it works ok?

[scrano]

I probably wouldn't worry too much about it at the moment, 'cause like you said it's working, and you don't have an e66 error to worry about.

You need to keep in mind though that when MS does future dash updates that they will more than likely check these things more thoroughly, which might mean an e66 error after an update.

The next time you update your firmware, or when MS decides to do it's next dash update (whichever comes first), I would seriously consider doing it then (It's just an extra precaution)

I hope this makes sense and helps you

[bigmac161]

QUOTE(hobogoonie @ Jan 22 2007, 07:56 AM)

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?

yes like ive said in my previous post

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

QUOTE

Code:
<firmware md5="2C9ECF2C43A0167C39385B2BA98A46C8">
<name>Xtreme 52c-ms25</name>
</firmware>

to the extremeDef.xml this is found in "C:\Program Files\X-Projects\Xtreme Boot Maker JUST OPEN WITH NOTEPAD AND ADD THE md5 error code

[hobogoonie]

Thanks, just what I wanted to hear!

Just to confirm though, to re-flash my MS-25, Can I just go over the top of the old one using badflash recovery?

[Trune]

out of interest, is there a site which tells you the right MD5 codes for the files?
I looked in readme but couldnt find it.

Btw thanks for everyones help, especially scrano. Much clearer now.

[scrano]

@hobogoonie With the MS25 you shouldn't need the bad flash recovery unless the current firmware on the drive is messed up or something. If it's functioning properly (loading original and backups) you should be able to just flash straight over it with your normal flashing method.

@Trune Sorry I don't know of a site that will help you with the MD5 hashes

[dyb]

i need some help. i bought a 360 today and got a ms25 samsung dvd, now how do i know what speed (a b c or d ) suits me best and should i use the 52x-ms25.bin file or x52x.bin ?

[hobogoonie]

The speed A,B,C or D is completely up to you. If you read the Readme that comes with Xtreme 5.2 it explains what the difference is in each flavour (A,B,C or D). Personally I've been using the D version. With this version it runs all backups at 4x, so its quiter and supposedly may read cheaper media better. If you put in an original then a backup it will then run backups at full 12x unless you turn your 360 off and on again. So with the D version the option is there to play backups at either speed. Its up to you.

Read this whole thread for an explianation on which bin file to use. But if like me, you use xtreme bootmaker and an updated X360SAM this will ensure your drive reports back as an MS-25 (spoofed) even though the firmware you are putting on it is mainly based on the MS-28. So, it shouldnt matter as long as you choose the right flavour. but just in case 52d-ms25.bin or (with xtreme bootmaker and update) XTREM52D.bin

It worked for me. Just make sure you do plenty of reading before you attempt it. I reccomend Textbooks guide.

[Trune]

Hobo, i used Xtreme Bootmaker, and updated x360sam... does that mean my drive is reported as MS-25 too? If so cool.

Btw, any way to get originals to read slower too? The sound from the slower backups is bliss!!

[v3rb]

what the code to add ms25 5.2d firmware to xtreme boot maker

[hobogoonie]

Trune, you are fine mate. The easy way to check your drive is being spoofed is to load your hacked firmware file into Firmware tools and in there it tells you at the top that the drive is being spoofed. I checked both of mine and they were good.

I also did another 28 in the same way (xtreme + upddated SAM) and when its hacking the firmware it says something like 'using version string Tsst-corp-943? - MS-25' I guess thats where the updated SAM stepped in and auto-spoofs the firmware.

I think you can set XTREME up to boot everything at slow speed cant you? I'll have a look.......

..... Hmmm, actually, maybe you cant. Just backup your original and use the backup I guess? Saves your originals getting scratched anyways. Just another point, one of my backups came up with a disc read error. As i'm using 5.2D I inserted an orig to up the read speed then re-tried the backup. It worked. Hope this helps.