Which Firmware???ms25 samsung!!!

[pc69]

hi guys...

i was trying to make a usb flash drive with extreme bootmaker...when i chose for extreme firmware open file...i selected...52c-ms25...but it said unknown firmware and there were.. many numbers...after that i chose xtrem52c...and he accepted...but Textbook said i must choose a firmware whom ends with ms25?????

can i use xtrem52... is there a difference ???? why didnt xtreme bootmaker accepted the firmware 52c-ms25???

any help is welcome...thx

 

[xbboy]

Whenever I first opened the hacked firmware(5.2c) into boot maker it gave me an error message also. I just opened it up again and it worked.

 

[pc69]

i mean it doesnt recognize the firmware 52c-ms25...my question is can i use xtrem52c?

 

[jrx]

it is happening to me 2. can someone please help. i have 4.2 right now and want to get 5.2

 

[ally1440]

Just use xtreme52x.bin x being the type u want! make a flash drive with that and make sure u drag the updated samread onto the flash drive just past over the current one's on there.

u need to do this because you have a ms25 drive. if u just flash with xtreme52x.bin and the old samread you will change the drive type to a ms28 which can cause the E66 ERROR for not having the correct drive type that was assigned to the console serial nimber.
the updated samread keeps the drive type as the old samread just wrote over it. ie changing the drive model.
i did it and i changed my drive to a ms28 by mistake and i found that i was getting loads of reading errors like dirty disks and unplayable game.
when i changed it back to a ms25 all the games worked fine.

hope this help u all out.
mayo

 

[CaptJake]

Or use the new Samtool v0.5: http://x-projects.org/index.php?option=com_docman&task=cat_view&gid=13&Itemid=37

Or you can just compare the md5 checksum of the file with this list and ignore XBM's warning (I use winmd5sum ):
52a-ms25.bin aace0314a1364fab222f588695178271
52b-ms25.bin 5f966d4d87402ca063ad47dfb3cff5eb
52c-ms25.bin 2c9ecf2c43a0167c39385b2ba98a46c8
52d-ms25.bin 71f6d91db4df24dc44ecd85c1877b52a

 

[Textbook]

The "not recognized" error is just an MD5 verification.

For future people who find this post .. it is a good idea to actually understand the programs that you are using. What they are doing, etc.

An MD5 verification means a file is hashed and returns an MD5 checksum of that file (see pk's post above). Every single different file will have its own unique checksum. When you try to load a firmware (bin file) with XBM, it checks the MD5 checksum of that file. Then, it compares it with a small database of valid, confirmed working files. If the MD5 does not match up, it gives you a warning saying "this firwmare file is not recognized" and asks if you want to download a "database update" from x-projects website.

Well, Klutsh , owner of x-projects was changing servers so the site wasn't up, and the "database update" wasn't working.

As you can see, this entire process is just to verify that the firmware you loaded is valid and legit. Although it has not happened yet, somebody could easily trick others into making a fake firmware, releasing that, and intentionally bricking people's drives. That is why the MD5 check is in place, to prevent that. It is nothing more than a "is this firmware valid?" checker.

If you get this error, but downloaded your firmware from Xbins, then ignore it. Xbins will always have valid tested firmware files and you shouldn't need to verify them.