Troubles dumping oringal firmware from ms28

[Neurixus]

I 'm trying to flash my samsung ms28 with the ixtreme 1.2 rev c fast firmware by following the "textbook". I cannot successfully dump my original l firmware.

I'm using NtFS4DOS and the latest iprep with up to date definitions. My motherboard is a P4M800PRO-M478 (V1.0) with onboard VIA VT8237R Plus sata. I have installed the lasted drivers for my motherboard.

I have configured the sata in my bios to ide mode. I have the the power cable and video cable connected to the xbox 360. I power on my PC and xbox 360 at the same time.

When i get to the C:/IPREP directory i plug in the sata cable from my PC to 360. I have no other sata devices connected.

I type iDump 1234567 12345 and press enter. ( I'm using 1234567 12345 as an example. I am not going to post my real serial number)

I get two choices

1: ide pri master
2: VIA8237 pri master

At this point i power off my xbox 360 and select drive 2. i have tried waiting anywheres from 3 to 20 seconds before powering on my 360. The following happens

port: ec00, master slave: a0

Flash type: "SST(SST395F020)"
Reading....01%
Invalid opcode at 1CBD 01EB 0046 035A 00D0 00D0 0000 0008 00D0 00D0 0000 17DB 23FB
ixtreme => Backups\1234567\12345\ hacked.bin

SamTool v0.7i

File Backups\1234567\12345\orig.bin is not 256kb!!! Program aborted
C:\IPREP>

I spent a few hours trying to get this to work. I do not know what i am doing wrong . If anyone could help me i would greatly appreciate it

 

[zerach]

2: VIA8237 pri master what is this.(it should say xtreme pri master)
i dont think this is the 360 drive.do you have any sata drives in your computer other than the 360 drive

 

[Neurixus]

I have no other sata drives connected, only my ms28 . I think I may not be setting iprep up properly.
I have forced device and custom sata checked.

when I click on list SCSI devices the only drive i see is the one installed with Daemon tools (virtual dvd/cd drive), and is not supported by MTKFLash.

when i click on list ide based controllers the only selectetion that MTKFlash supports is "standard dual channel PCI Ide controller."

I select the standard dual channel PCI Ide controller and get Dev ID 11063149 Dev ID EC00E800.

Am i setting up iprep proplerly?

I normally have 2 sata drives connected to my pc, so i know the sata on my motherboard is working. I unplug those drives disconnected when i try to dump the firmware.

 

[zerach]

when you build your iprep.
load firmware
put a check in both force device and custon serial
click on the list scsi based(it should list you sata port ID & IO
put target drive in (your flash drive letter)
check format/make device
click do it

the thing is i dont know if it will work off the sata on your motherboard.the sam are very picky.
this is what i use for me sam drives.
http://tekgems.com/Products/la-pci22-vt6421l.htm

ive never done it off a cd i use a usb.maybe OliMaylen will see this and offer more.

 

[OliMaylen]

I agree with cofree, it sounds like your onboard SATA controller is not capable of flashing your drive. It sounds as though you are doing everything else fine. I use the NTFS4DOS method myself.

The SATA card cofree has shown you is not very expensive & WILL work. It is probably worth your while buying a PCI SATA card like that one.

You can find them on ebay also. Just make sure you get a card with the VIA VT6421L or VT6421A chipset. 6421L is the preferred card, but I use a 6421A just fine.

I'd say it's worth the money to buy a PCI SATA card such as these & know your definitely getting the right hardware to do the job.

Let us know how you get on.

 

[air9]

I'm getting the same error as pieman. The exact same thing happens when I try to dump the firmware on my ms28.

The only difference is that I'm using a VIA 6421A, and on my list it comes up as XTREME Pri Master.

I'm using NTFS4DOS, and when I use the iDump command it creates a 1kb orig.bin and a 256kb hacked.bin.

Then it gives me that same "File Backups\1234567\12345\orig.bin is not 256kb!!! Program aborted" error.

I've been at it for hours and was just wondering if anyone could help..

 

[zerach]

i dont do it the ntfs4dos way but what i do know is the orig bin MUST be 256k and the hacked bin will be 256k also

 

[air9]

As far as I can tell the NTFS4DOS way is just another way to get to your dumping/flashing utilities, so once I actually reach a command prompt it should be the same as how you do it. From what I read anyway.

My problem is that it creates an orig.bin that is only 1kb and then tries to check to make sure it's 256kb... Not sure why that's happening though. Perhaps my timing is just off?

Anyone know any more about this error?

 

[zerach]

try with a floppy just to do a idump.it should not hurt anything to try.