Can't Recover Sammy Drive! Options

[v1per]

Hi Folks,

I borked my drive using an Ali chipset pci card, which hung on writing (having successfully copied the original firmware, fortunately!).
I've just received my VIA VT6421L card, and have tried to recover the drive.
I've tried the hotswap method, as well as the "response code 70" related method, but no luck.

I get as far as:

Port: d8a0,Master/Slave: A0
Flash Type "SST(SST395F020)

Erasing..... Chip Erase...

But then it hangs.
I've put a copy of my orig.bin file (256k) on the USB Stick.
Am I missing something here?

If there isn't a solution, does anyone know where I can get a new drive/repair, without buying a new console?

I'm in the South of France, by the way.

Cheers!!

[angry_rabbit]

As mtkflash sees the chip it's obvious its a problem in the pc harware. Try a nforce 3/4 mobo that will work!

This post has been edited by angry_rabbit: Oct 6 2006, 12:21 PM

[v1per]

I can't try it on another mobo, as I'm in the middle of nowhere, and ordering a new mobo would be yet more expense!
Any other ideas folks?!

[Gazcoigne]

why is it saying erase??

try the old school method with a floppy drive always works for me and i have a via 6421L card also.

have you hex edited mtkflash correctly to be compatible with your via 6421?? if not thats the reason it stalls.

firstly, hex edit UR OWN version of mtkflash as the dl versions you can get wont work as each card can vary slightly.

then create a bootable floppy disc, and put the edited mtkflash.exe and mtkflash.typ, and your orig.bin onto the floppy drive

boot to the a prompt then power the samsung drive, then type

mtkflash w /m orig.bin

that will restore the drive to original state.

[angry_rabbit]

Just unbricked a friend's sammy(m28) from a faulty patching attempt. Noticed that having firmware source on a floopy, mtkflash has difficuilty updating the f/w. It burns 15 banks then goes into a continious error loop. However, if the bin file is off the hd then everything is sweet!

[v1per]

Still no joy.

I edited MTKFLASH, and I still get the

Port: d8a0,Master/Slave: A0
Flash Type "SST(SST395F020)

Erasing..... Chip Erase...

message, before the PC hangs.

I used X360SAM.4 to flash, and it saved 3 files in the "backups" folder

hacked.bin (256k)
orig1.bin (68k)
orig.bin (256k)

I've been using the 256k "orig.bin", which I assume is correct?!

Also used the following for the Hex (on the VIA 8237 line)

06 11 49 32 a0 d8 c0 d8

Nom VIA VT6421 RAID Controller
Fabricant VIA Technologies, Inc.
Statut OK
ID du périphérique Plug-and-Play PCI\VEN_1106&DEV_3249&SUBSYS_32491106&REV_50\4&10416D21&0&10F0
Port E/S 0x0000D8A0-0x0000D8AF
Port E/S 0x0000D8B0-0x0000D8BF
Port E/S 0x0000D8C0-0x0000D8CF
Port E/S 0x0000D8D0-0x0000D8DF
Port E/S 0x0000D8E0-0x0000D8FF
Port E/S 0x0000DC00-0x0000DCFF

Should be working, shouldn't it?!

Please help!

This post has been edited by v1per: Oct 7 2006, 09:02 AM

[v1per]

BUMP!

[Hoggy]

angry rabbit, can you please explain what you mean? i tried to flash and it got the 1st 15 banks like you say then freezes, i use a usb stick, wot are you saying? dont put the fw file to be flashed on the usb stick? i am confused and you help would be greatly appreciated

thanks

[angry_rabbit]

I quiet don't understand why mtkflash doing this! Others have also noticed this effect too. If the number of files are reduce in the partition then mtkflash works ok. If I use the same floopy over again and again the problem appears. Reformat and start again and everything is sweet again. The only thing that comes to mind is the bin file becomes fragmented and it seems to have a detrimental effect in flashing the 020 by putting in delay's or loosing track in flashing the chip. There seems to be a similar effect flashing 162c with keon's patched f/w. If his file is in the same sub as sdfwin then it spits the dummy. Putting the file in a temp folder the flashing works .....very strange!

[Hoggy]

thanks for the reply

so basically reformat my usb stick, put original.bin or hacked.bin if i wish along with modified mtkflash that i used to read and everything should be ok?

in root? in different folder than mtkflash or doesnt matter?

[DgrMouse]

When flashing sammy's, I have always used a bottable froppy and done everything from there.

Never has a problem with sammys this way. A tried and trusted method for me using either a nforce4 or via chipsets

[awaddon]

Hi guys

I know this is probably a little late, but if you still have the drive maybe you can still resurrect it!

I have flashed a few xboxes with ms25 ms28 and I have just got the same problem when using the 10 second trick

I got Erasing ... Erasing Chip..

after that when i turned on the xbox all i got was a flashing power light!, tried to do 10 second trick and wouldn't even see the drive at all!

so just before giving up and buying a new drive, i tried one more time, typed the mtk flash command and hit enter!, it showed me options 1 and 2,... 2 being my xtreme backup option on my via sata card and instead of turning off the xbox to do the 10 second trick, i just hit 2 straight away and POW it kicked it back into life and it started updating! woohoo!!!

All is ok now and boots just fine!!

hope this helps!