Games won't load w/1.2C on MS25, key is correct, help!

[Xboxdawg]

I need some help. I've looked through all the tutorials and a lot of posts but haven't found a solution yet.

I have flashed my Samsung MS25 drive to ixtreme 1.2c. However it will not load originals or backups of my originals. It will only play DVDs. I used Firmware toolbox to see if the key transferred and it did. It matches my original. I flashed it back to the orig.bin (factory setting) and it didnt' work. I flashed it back to xtreme4.2a and it still won't boot originals. I checked the key in a hex editor and it is the same as my orig.bin. Any ideas?

Here are the steps I took to flash it. Tell me if I did something wrong...

I have a Samsung MS25 drive. It was flashed to Xtreme 4.2a. I had saved the orig.bin file and still have the USB drive with the backup files, etc that I created to flash it originally.

I downloaded iextreme 1.2c as well as Iprep and the rev 5 def. I copied my orig.bin (that was created when I originally flashed the drive to 4.2a to the iXtreme1.2c directory. Ran "Make iXtreme firmware.cmd" . Told it to not spoof to ms 28, the keys it showed matched and it said ****SUCCESS**** Drive key copied. I renamed the ix12.bin file to hacked.bin.

I next opened Iprep directory. Copied the rev 5 file into there. Then ran Iprep. It found my Sata port, I created a bootable USB drive using the iexteme 1.2c firmware. I copied the hacked.bin file to the USB drive.

Then I booted on the USB drive, booted up the 360, attached the SATA cable from the PC and inserted the 0800 dvd into the 360 to turn off the firmguard. I typed mtkflash w /m /sata hacked.bin It asked me to select the port, I did so. It found it and flashed each of the 4 banks, gave me the checksum and said it was finished. I shut the PC and 360 off. Connected the 360 sata cable back to the drive and tried it on the TV. Tried an original, it says to play it insert it into a xbox 360, same with a backup. It plays a DVD though.

I then tried flashing it again. same results.

I booted on my other USB drive and did the samorig to flash it back to original but same results. Tried SAMHACK to put 4.2a back on. It flashed it to that according to firmware toolbox, but it still won't play an original game.

HELP!!!!!!!!!!!!!

Thanks,
XBD

[Protonus]

I had this same problem, but for different reasons I think.  First, you DO want to spoof to MS28. Your MS25 "becomes" an MS28 complete with it's firmguard protection after you load the hacked firmware. So say YES when it asks.  That's probobly why this failed.  You need to spoof to make it work right.

I would first flash back to your original bin. This will probobly require the bad flash or 0800 disc method to do as if it DID successfully load the new firmware the firmguard will be in place.  Upon flashing back to your ACTUAL orig.bin (the very first one you made, from the first time you dumped your 360's firmware) - you should now be able to play normal original 360 games again.  This should always works.

After that if flashing back to orignal works, Then "make" the new firmware again using your orig.bin.

You do not need to rename the ix12.bin file it creates to "hacked.bin' like you did....  You can flash with that filename just fine.  Also, no need for iprep unless you need it to make a boot drive.  if you do use iprep just make sure to copy your ix12.bin file to the directory where you have MTKflash AFTER you run iprep or whatever just to make sure it doesn't over write it.

Hope this helps.

[Xboxdawg]

Thanks for the idea. I flashed back to my original firmware (the one I dumped when I flashed originally to 4.2a). It still will not play original games or backups, only DVDs.

I used firmware tool box to view the key, it is there and it says the ROM version is: Samsung-TSH943A-ms25.

When I dumped the 4.2a firmware it showed it as Samsung-TSH943A-ms28 [XTREME4.2A]. So apparently it was spoofing to a ms28.

I don't understand why it's not working when I flash it back to original or 4.2a.

Anyone have any ideas? This is about to drive me crazy! I've flashed my 360 and a couple others and have never ran into anything like this.

Thanks

[Xboxdawg]

I just thought of one other thing. MS repaired this 360. It had the 3RLOD. However I got the same unit back and the same dvd drive. It was still flashed and would play my backups. Is it possible that MS changed my motherboard and therefore changed the key of my drive??? I didn't dump the firmware before I flashed it with 1.2c because I thought it was the same. So I used my orig.bin from the original dump when I did 4.2a.

If they changed my motherboard and key am I screwed? Any thoughts would be GREATLY appreciated. Here I am on the eve of the release of Madden and my 360 won't play games! aaaaaaaarrrrrggggghhhh!!!

Thanks,

XBD

[oc]

Hehe.. I think you are right, ms did changed your key.
Best idea send it back to ms, claim they did not fix for you.

[Xboxdawg]

I've had it for a few months now, so not sure that would work. Wonder why they would change the key but not the firmware?

Anyone else got any ideas?

Thanks,

XBD

[Protonus]

Hehe.. I think you are right, ms did changed your key.
Best idea send it back to ms, claim they did not fix for you.

I think you're/he's right... That sounds likely.  Man that sucks.  I'm with him send it back again lol.

[Xboxdawg]

I don't really want to that, that's basically fraud. I wish there was a way to recover the key from the motherboard. That's the only thing I can imagine it would be, that they just injected the key instead of flashing the firmware.

[Protonus]

You flashed this before sending it to them right?  That means your warranty should have already been void.. were you just careful with the sticker?  Sending it back to them again is not really any worse then having sent it to them after opening it anyways...

Or you could just wrap it in towels and let it get the RROD again.. does yours have the new GPU heatsink?  If you trash the box I'll at least buy the heatsink off ya ;-)

[Xboxdawg]

They worked on it back in early May. It does not have the new heatsink.

XBD