XTREME 5.2 why so many versions?

[zana]

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.

 

[ivanhoe]

No, you should have used different version on the MS25. When he goes on Live and does the Fall update he quite probably will get the E66 error

The versions A, B, C & D are diferrent flavours that have different spin speed behaviour (see the readme). The others (-ms25 etc..) spoof the respective drive so as to avoid the E66 error. MS28's do not need to do this since the Xtreme 5.2 firmware is based upon a MS28 kernel to start with.

 

[zana]

OK, So I understand that A, B, C and D are different flavours. But On the 2 MS-25's I did I used XTREM52D and one is mine which has gone on live without a problem. Which file should I have used again and should I think about changing the firmwares again? 52d-ms25? I have of course a backup of original firmwares. How do I go about re-flashing?

surely they should have called the 28 version 52d-ms28? would that of not made sense?

been using xtreme bootmaker, do i need to create a firmware using a bat file or is it simply a case of inserting the correct key?

thanks for advice, i'll get there in the end.

might have to do a mates hitachi 78 today too :s

 

[ivanhoe]

Correct, use 52d-ms25 for MS25's

Reflash as you would doing an upgrade - covered in the tutorial - either use Enable approach, or bad-flash -you do not need to go back to original first

It may have made some sense to name the ms28's with ms28 tag, but I guess they figured that people would primarily use the included "make xtreme firmware.cmd" file, which steps you through the creation process to make sure you get the right one.

I suggest using the bootdisk you already have, creating a new hacked firmware with your orig.bin file and the cmd file I mentioned above. Boot to DOS and flash manually with ;
mtkflash w /m /sata hacked.bin

As mentioned already, this would be along with either the Enable approach, or bad-flash

 

[zana]

Thanks for the advice. Just a thought then, maybe an addition to the textbook tutorial about this issue. Just been reading about 'make extreme firmware'. when using textbooks tut, and xtreme bootmaker, theres no indication at all that ms-25 owners need to spoof the firmware.

Just a thought. Thanks again.

 

[ivanhoe]

Actually, if you used the new x360sam file, then it probably patched it for you anyway, doing away with the need to explictly choose the MS25 version... this probably explains why you have not got the E66 error after updating on Live....

Sorry, I patch everything manually, so I clean forgot about this latest feature of teh new x360Sam.... An easy check would be to open the hacked firmware that ended up being flashed on to the MS25 in the firmwaretoolbox, and see what it is reported as spoofing. If it comes back as MS25, then you are all clear

 

[zana]

Ah, so your saying even though I chose the incorrect firmware.bin (in terms of spoofing) the update.zip to x360sam now would have seen that and corrected it?

 

[ivanhoe]

I believe so - there are two small hexedits that need to be done that are the only difference between all the flavours. The new x360sam (from 11th Sept 2006 or higher) autochecks what your original firmware is after extraction, and applies this patch.