Ok heres the story. My mate wanted me to update his firmware for him to ixtreme, he said it had been crashing during gameplay, so i thought it probably need a firmware update, his drive is the ms25, sweet i thought should be done in a couple of minutes.
I prepped my usb device with iprep, booted away, drive was detected and started the flash, i already had his orig.bin so i just made the firm and flashed away. 100% on all 4 banks, turned it off plugged in the cables and RROD (IMG:
style_emoticons/default/blink.gif) It didnt matter what i did the RROD was there.
Anyways, he was cool, he bought a new core system and gave me the old one. Sweeeet.
So i got a couple of Q's about this. Firstly, i used the mtkflash w /m sata hacked.bin command, this is the way im used to doing it, would that have made any difference to the RROD?? should i have used the iflash command?
I also used the MTKFLASH commands in iprep for his new MS28 and it backed up the Orig.bin fine but it wouldnt flash using those commands, it would get to 50% on 3 banks and then give an error on the 4th, so i used the idump 1234567 12345 method and it worked a treat 100% on all 4 banks. I got a Via 8237 chipset and use the 10 second method.
Another weird thing, i thought id use his old ms25 drive for creating my backups, i fount the old xtrm0800 firmware for windows recognition and flashed it to the drive using the iflash method, plugged the drive back in and the RROD has gone, could a bad flash have caused the RROD??
Also the drive is an MS25, but the sticker where the drive says MS25 was another tiny little sticker, i peeled that off and it says underneath F/W = MS22, is this a typo from samsung, or was there an MS22 in the earlier models?
So anyway, i got a working 360 for nothing and the drive is great for creating ixtreme backups in one easy click (IMG:
style_emoticons/default/biggrin.gif)
Author
Topic: Couple Of Q's (Read 38 times)