Jump to content


Photo

Ms25 (28) Not Flashing


  • Please log in to reply
5 replies to this topic

#1 jds1469

jds1469

    X-S Enthusiast

  • Members
  • 23 posts

Posted 15 May 2007 - 05:13 AM

I am doing a friends box that used to have a MS28 inside which broke. He purchased a MS25 hoping it would work. I am trying to use the Textbook.pdf to do this but everything is out of date on this. on XBM do i set it to report as a 25 or 28 (as i said before im swaping out a 28 for the 25)

I have been saying to report as a 28

Ok so I set up my firmware up in the General options along with the SCSI controller.
In basic disk I put in my serial number, select xtreme 5.xa, report as ms28, and select my USB stick drive. click "Create Disk" and it says something like "Happy Flashing" ok so thats done.

now when I go to do the "sameread 1234567 12345" it goes as far as asking me to select my SATA controller "XTREME"

Then it says "SAMSUNG/XTREME.BIN not found




im about to tell this guy to go trade this in for one with the Hit drive in it

#2 jds1469

jds1469

    X-S Enthusiast

  • Members
  • 23 posts

Posted 17 May 2007 - 12:01 AM

NE1?

#3 Havok

Havok

    X-S Messiah

  • Moderator
  • PipPipPipPipPipPipPip
  • 3,745 posts
  • Xbox Version:unk
  • 360 version:unknown

Posted 17 May 2007 - 01:51 AM

Try just using MTKFlash by itself...

just do a "mtkflash r /m orig.bin"

You do have to set it to report as a MS28...

Also what SATA card are you using?? You need to do the VCC trick (dangerous) or use a VIA based chipset (10 second trick) for reading/flashing the drive.

#4 piggelin

piggelin

    X-S Young Member

  • Members
  • Pip
  • 47 posts

Posted 17 May 2007 - 06:50 AM

QUOTE
Then it says "SAMSUNG/XTREME.BIN not found


rename the hacked firmware to XTREME.BIN and put it in the SAMSUNG folder.

then try samread once again

#5 jds1469

jds1469

    X-S Enthusiast

  • Members
  • 23 posts

Posted 17 May 2007 - 03:15 PM

crap now i get E 66 when i start the system

#6 Havok

Havok

    X-S Messiah

  • Moderator
  • PipPipPipPipPipPipPip
  • 3,745 posts
  • Xbox Version:unk
  • 360 version:unknown

Posted 17 May 2007 - 04:44 PM

E66 should be very easy to fix...

If the original drive was a MS28 you have to make it report as such... so I would try that again. If you have a valid ORIG.BIN make sure you don't accidently overwrite it.







0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users