Print

[Pecker8u]

QUOTE(Exobex @ Aug 14 2006, 09:28 PM)

Worked fine for me.
Try this:-
Boot with power connected, wires disconnected, SATA disconnected
When ready to read firmware, connect SATA, connect wires, read
Use your favourite method of copying the drive key (X360SAM, hexedit, etc.)
Shut down, disconnect wires, disconnect SATA
Boot with power connected, wires disconnected, SATA disconnected
When ready to write firmware, connect SATA, connect wires, write

Thanks for this.

I cant understand how disconnecting the wires upon bootup will help as the drive has no power and the Xbox does not recognise the drive. Is that right?

[Exobex]

QUOTE(Exobex @ Aug 14 2006, 09:28 PM)

Boot with power connected, wires disconnected, SATA disconnected

QUOTE(Pecker8u @ Aug 14 2006, 11:14 PM)

Thanks for this.

I cant understand how disconnecting the wires upon bootup will help as the drive has no power and the Xbox does not recognise the drive. Is that right?

Why does the drive have no power?

[Pecker8u]

QUOTE(Exobex @ Aug 15 2006, 12:30 AM)

Why does the drive have no power?

When the wires on the drive are disconnected, the DVD drive simply does NOT power up. If reconnected the drive does not start to power up, it is simply left in the same state.

Anybody with F/W=ms28 and done this resistor switch trick successfully please fine tune details on how to get around my issue.

Regards

[kutje]

i think it has to do with our hardware.

i have intel socket487 mb with onboard sata. the trick didnt work (yet).

[Pecker8u]

QUOTE(kutje @ Aug 15 2006, 05:44 AM)

i think it has to do with our hardware.

i have intel socket487 mb with onboard sata. the trick didnt work (yet).

I don't think so. I think it has to do with the Xbox DVD drive booting wires disconnected, it seems to plague everything else as it causes the Xbox to flash green light and power disabled on DVD drive.

Any ideas anyone?

[neomaximus2k]

Well I have followed these instructions right down to the T and sadly it didnt work (IMG:style_emoticons/default/sad.gif)

I am thinking there is a problem with the NFx Chipset boards with the 28 firmware but sadly having trouble hunting down a good board.

I am after a VIA8237 chipset wether it is a controller card of main board i dont mind even with my contacts in the hardware industry having a hard time.

btw I am UK based (IMG:style_emoticons/default/sad.gif)

[Exobex]

I did it with a VIA EPIA SP13000, onboard VIA8237 SATA (which doesn't work with Hitachis, so I use a cheap USB-SATA adapter from eBay for those), PnP OS disabled.

[neomaximus2k]

QUOTE(Exobex @ Aug 15 2006, 04:50 PM)

I did it with a VIA EPIA SP13000, onboard VIA8237 SATA (which doesn't work with Hitachis, so I use a cheap USB-SATA adapter from eBay for those), PnP OS disabled.

Well I now have the 3 biggest hardware distributers in europe hunting down a controller card or board with that model SATA lets hope I can find one

[bninja]

i have a 28 and after dumping, patching and reflashing my drive i've got no love

i checked my firmware and it has this line repeated over and over...

 002122232425262728292A2B2C2D002F003132333435363738393A3B003D00004041424344454647
 48494A4B4C000000005152535455565758595A5B005D0000606162636465666768696A0000006E6F
7071727374750077007900007C7D7E7F
!"#$%&'()*+,-./.123456789:;[email protected][.]..`abcdefghij...nopqrstu.w.y..|}~

that's a bad thing right?
if i understand correctly i had a bad dump of the orig.bin and now i'm rooted...

[pizza-man]

i tried and tried and nowt
wont read firmware
also read all tutorials about it

[bninja]

you need to give more information about what you've tried and where you've encountered problems
have you hex edited mtkflash for the chipset of your sata controller?

[neomaximus2k]

QUOTE(bninja @ Aug 16 2006, 01:47 PM)

you need to give more information about what you've tried and where you've encountered problems
have you hex edited mtkflash for the chipset of your sata controller?

Well i feel like this guy.  Originally I could not get the MS28 to read on an NF4 chipset board, it would see the drive in the bios but not when it came to mtkflash, after hexxing the software twice to make sure it was correct it was still doing the same thing and that is when it came to reading the info off the chipset it sits there and does sweet FA, even after leaving it for an hour.

I have even gone so far as to buy a different board (Intel chipset  ASRock - ASROCK SKT-478 P4I65G S/V/L M-ATX 800FSB )

it recognised the sata chipset ich5 but when it came to reading info of the firmware it just sits there..

This is now becomming very anoying and is costing me a lot of money (IMG:style_emoticons/default/sad.gif) has anyone had problems with this and how did they overcome the problem.

[bninja]

well the steps i followed are

pc and 360 off
plug in sata cable to 360, leave the 360 off and boot the pc
once booted type in "mtkflash r /sata /m orig.bin"
turn on 360 and press enter on pc straight away
once option is presented for master/slave, connect wires and press "1" (or correct option)

this worked for me to both read and write the drive... but it didn't turn out to good in the end...

[neomaximus2k]

QUOTE(bninja @ Aug 16 2006, 02:33 PM)

this worked for me to both read and write the drive... but it didn't turn out to good in the end...

dare I ask why?

[dimmellee]

Well it worked for me, connected the wires, powered on pc, waited a couple of seconds, powered on 360. When i got to the dos prompt, typed mtkflash r orig.bin, disconnected the wires, pressed enter, selected my channel and dumped the firmware. Turned off 360.Hexedited 4000-4200 into the xteme 3 firmware. connected the wires, powered on pc, waited a couple of seconds, powered on 360. When i got to the dos prompt, typed mtkflash w /m patch.bin, disconnected the wires, pressed enter, selected my channel and flashed the firmware.
Reconnected the wires and job done. I am useless at soldering but I still managed. easy job.