Mutiple sata controllers and a TS-H943 MS25 probs

[TheOtherside]

Fine where to start

My motherboard is a Asus A8N-SLI Deluxe
There are two sata controllers onboard

Nforce 4 sata controller and a Sillicon Image 3114 controller.

I'm using the following tutorial
http://360mods.net/Downloads/details/id=61.html

In that tutorial they make use of the xtreme bootmaker.

First I tried it with the Silicon Image Sata controller.
It's reconized by Xtreme boot maker and makes a XBF on C:

I'm Using NTFS4Dos

Then I'm booting my PC with the Sata kabel plugged in/Xbox powered off.
Until I get to command and power on my Xbox

Then I'm going to the right folder:
C:
cd XBF
samread 1234567 12345 (sn)
1 IDE
2 IDE
3 Xtreme
4 Sil 3114

I'm choosing option 4, But then nothing happends and only shows code's like these: A800 of A000

---

Then I Tried the Nforce Sata controller
Kabels switched
And here aswell no problems in Xtreme Bootmaker.
Same boot procedure etc. But now:

1 IDE
2 IDE
3 Xtreme
4 Xtreme

That doens't work either 

When i Browsed on the forums i've read that the Sillicon Image controller is pretty buggy.  (Sil 3114)
But the Nforce 4 should work fine with a prober mtkflash.

Well i've found the mtkflash for NF4, it does show my controllers now, but when he try to read my firmware out i get messages like.
xx should be xx

What could it be? is the mtkflash for NF4 not the right one for my NF4?

[glaze83]

make a dos boot disk. People have had problems flashing with ntfs4dos.

As well, boot up your 360 and wait for it to finish its flashing lights sequence before you turn on your comp.

And yes, definately use the nforce chipset with a hex edited mtkflash and not the sil.

[TheOtherside]

Ok i've checked my mtkflash with the hexeditor this is the code what Xtreme Bootmaker makes:

Device ID:
10DE0054

I/O Port:
09F00970

This is my m32info sheet, can someone confirm that these numbers are correct?


Because i'm getting a message:

Port 9f0 a0 (or b0) 00
00 should be 70

So something must be 70.

[TheOtherside]

All the sudden it worked .

Xtreme bootmaker with USB stick
Copy MTKFlash-NF4 to usb stick
shutdown pc
connect drive
power on Xbox 360 and PC at the same time.
boot from usb
Samread xxxxxxx xxxxx
done

shutdown, disconnect sata kabel
power on 360 and pc
boot again from usb
samhack xxxxxxx xxxxx
flashing

OMG that it could be this simple  stupid ntfs4dos 

Thanks for the advice glaze83

[TheOtherside]

OMG the E66 problem 

[gigabite]

Try re-flashing your drive (if you have some cash - not expensive try and buy a VIA VT6241A Sata PCI card, worth the money and works with everything !

gigabite

[TheOtherside]

Yeah, i'm thinking about that too,

I found the problem in the firmware, but now my problem is i can't seem to reflash the bloody thing, like before i get an error when I try to read or flash it.

Status 50 should be 70

or

Status 51 should be 70

That thing drives me nuts!

[gigabite]

Ow ow ow I know I have to make my guide I promise it'll be out soon!!  Ok, in XBM apply Bokes ms28 patch this will work for you promise, only reason you can't get it because code 70 hits straight straight after power on, no matter how fast you can push buttons you will never get it without this patch (unless you haven't manually hex edited or used XBM to auto detect you sata channel)

gigabite - it will work!!

[TheOtherside]

Well I'm affraid it doens't work, or i'm doing something wrong

ok started XBM
selected firmware 42b (or do i have to select my hacked firmware?)
device selected
patch for MS28drives (I have a MS25 drive)
Bootable USB stick

Then I copied my hacked firmware in (device):\Backup\xxxxxxx\xxxxx\hacked.bin

Right, shut down PC
Connect cable to sata and DVD drive.
Boot both machines ( also tried: Boot PC, at command boot Xbox. Boot Xbox Fully to dash boot PC. )
Command prompt.
samhack xxxxxxx xxxxx
devices
1
2
3
4

port 9f0 a0
nothing happeds
<escape>
Status = 51 should be 70

 

[TheOtherside]

Do i need to make use of the E800.iso?

Sorry for dubble posting

[edit]

That did the trick!! Because the Xtreme firmware 4.2 has a firmguard I was unable to read/write any data from firmware.
Inserting the Enable 0800 disc i was able to reflash my drive. It's working like a charm now

[Arakon]

..which happens to be written in the very same readme that comes with 4.2 in the first place.

[TheOtherside]

Well, it doesn't say if something went wrong while flashing your 4.2 firmware and you wan't to flash your firmware again you have too use the E 0800 disc.

You have to use the methode for upgrading from 4.0/4.1 wich is described and that works yes.