Hit a wall so to speak. *flashing problem*

[FunkyMonk]

See, that shop is in Canada so i'll be waiting a few weeks on it.

What about this one or this

yea
those are what i would get.
the v3 is on pre-order as far as i know.
the v2 is the one that is out now.

the thing is the v3 will do the hit drives and the lite-on when it comes out.

So just to confirm, this one http://www.mrmodchips.co.uk/catalog/pro ... 0c1d1adf63" onclick="window.open(this.href);return false; Will do me for now at least ya?

When do they think they'll have the lite-on drives flashed?

[FunkyMonk]

Just tried again, with a new cable using the iextreme 1.4 firmware. This is where its at in the command prompt woindow.

FLASHIX.bat

╔══════════════════════════════════════╗
║ ║
║ C4EVA: iXtreme v1.4 Multi Speed ║
║ HITACHI ALL VERSIONS 32-59 8in1 ║
║ ║
║ Updates your x360 DVD drive firmware ║
║ ║
╚══════════════════════════════════════╝


WHAT IS THE HITACHI DRIVE LETTER? = h

CHOSE A FIRMWARE SPEED: 2x 5x 8x 12x = 12x

NAME THE BACKUP FOLDER [Aa-Zz] [0-9] = X16S-0000

. . . . . . . . . . . . . . . . . . . . . . . . . . .

FLASHING DRIVE h:\ HITACHI V.47_16s FIRMWARE SPEED 12x


Flashing 01/11 Sector 90003000 (Xtreme Custom Code)

And in the folder "X16S-0000" are these files. "47_16-12x.bin" - "key.bin" - "was.bin"

Just posting this as it might help narrow the problem down somewhat!

[CoFree]

So just to confirm, this one http://www.mrmodchips.co.uk/catalog/pro" onclick="window.open(this.href);return false; ... 0c1d1adf63 Will do me for now at least ya?

yes that will work

im not sure when the lite-on fix will be out in the wild.

[FunkyMonk]

I don't think mode-b is your problem. Windows is seeing the drive and so is firmware toolbox. There is some sort of communication problem going on here from what I can tell. Have you tried a different sata cable by chance?

Have tried a new cable mate. Made sure everything was tight and secure. Same story though. The controller card I'm using is confirmed to be one that works. Is there maybe something i have to do to configure it properly maybe?

Out of curiosity. Have you heard of people having as much trouble as i am, flashing their 360's?

[FunkyMonk]

I'm giving it a go now on my brothers machine. Using slax, i get this,

sata1: softreset failed retrying in 5 secs
sata1: port is slow to respond, please be patient (status Oxff)
sata1: Comreset failed

Thanks sadalius, i'll give that a try too.

Just to come back to this. Originally i thought this must have something to do with the 360 drive being connected. But no, its actually a problem with my brothers pc(i guess?). Cause i've tried booting up slax without the HItachi drive connected or powered on and still getting this "error".

I've read one or two things about RAID settings?

[sadalius]

And in the folder "X16S-0000" are these files. "47_16-12x.bin" - "key.bin" - "was.bin"

Just posting this as it might help narrow the problem down somewhat!

Use firmware toolbox to try and open the was.bin file and see what it shows for the key. If its all 0's or f's, maybe even a valid key.

If you get a valid key, then its actually reading the firmware, just having trouble flashing for some reason or another. When you tried firmware toolbox, was you able to get a successful dump of the firmware?

[CoFree]

"X16S-0000" are these files. "47_16-12x.bin" - "key.bin" - "was.bin"

if you did get a good copy of your firmware.
make sure to make some copies of it for safe keeping.

[FunkyMonk]

Use firmware toolbox to try and open the was.bin file and see what it shows for the key. If its all 0's or f's, maybe even a valid key.

Ok, i'll give flashing it another go and see whats in that .bin file(i've deleted them already). Just to clear up, the files i posted were as a result of trying to flash it the "normal" way(iextreme 1.4) i.e. not using firware toolbox. But its still okay to open the .bin file with FWToolbox?

UPDATE: Appears to be a valid key. *******************************
edit by:cofree

When you tried firmware toolbox, was you able to get a successful dump of the firmware?

Ya, think so, everything went perfectly(up until the compare firmwares stage) according to the instructions you gave me. I'll try the FWToolbox method again and pay closer attention to the firmware dump.

UPDATE: Okay, this is a bit strange. Before when i tried to flash using the FWToolbox i got an this error.

but now. It went past that stage without a hitch. Problem now is that the i can't get the drive to stay closed?

[CoFree]

that is a good key.make some copies of it for safe keeping.

man
this drive is being a pain.
im not sure why it wont stay closed.
if you hit eject 2 times it should open,then 2 more hits should close and it stay closed.

[FunkyMonk]

that is a good key.make some copies of it for safe keeping.

man
this drive is being a pain.
im not sure why it wont stay closed.
if you hit eject 2 times it should open,then 2 more hits should close and it stay closed.

Well firstly. My drive is a bit funny anyway. I haven't been able to close it by pressing the button for a good time now. Always had to push it closed. Would that be having an effect?

Anyway. Went through the FWToolbox proccess again. Thought i had it this time. Drive stayed closed, when i pressed the button to "read and detect differences" it went without a glitch. But then when i pressed "start flashing" i got this error.



But the drive IS recognised by Windows!!

[FunkyMonk]

OK, so i've tried flashing my brothers 360 now too. His was RROD, so i took the drive out which was also an Hitachi. Getting the EXACT same sort of errors. So it must be something to do with my PC?

[sadalius]

Have you updated your sata drivers lately?? If so, you might want to uninstall it and re-install it. If your using a sata add on card, maybe even try it in a different PCI slot. Something is breaking down at the communication level, particularly when you try to transmit data to the drive, and now drives.

EDIT: WAIT A MINUTE!! Has either of these drives been flashed before?

[FunkyMonk]

EDIT: WAIT A MINUTE!! Has either of these drives been flashed before?

Well the first one, my one , definitely hasn't been. The second one, my brother, may have, he bought it on ebay, but its been used on LIVE loads and was never banned. So doubtful?

Don't know where i'm at now. When booting slax, i get to the spinning up disk part, so i open the tray, and the booting process carries on. But when i close the tray, it will open itself up by itself. So what i was doing to get around this, was simply turning the 360 off while the tray was open, so when it came to booting up slax and i got to the "spinning up disk" part, then closing the tray to finish booting and then booting windows etc.

And on my brothers PC, slax wouldn't even load properly full stop, with or without the 360 connected. This what happening during the slax booting proccess.

sata1: softreset failed retrying in 5 secs
sata1: port is slow to respond, please be patient (status Oxff)
sata1: Comreset failed

Thinking of maybe a clean install of Vista. Willing to try anything at this stage. Have a connectivity kit ordered. Pray to god if i haven't it sorted by then that twill do the trick.

[sadalius]

Well, I thought I had a thought there for a second. If the drive had already been flashed, it would have needed to go through the restore process, but since it hasn't, that knocks that out.

On the ejecting thing. When the drive is in mode-b, and you open the drive, it will take two or three presses of the eject button to close the drive to where it will stay closed. Or you can close the drive tray with your hand manually and it will stay closed. So if you were turning off your 360, the drive may not have been in true mode-b. Although if you were having to close the tray manually and it showed up in windows, it should for sure have been in mode-b.

[FunkyMonk]

On the ejecting thing. When the drive is in mode-b, and you open the drive, it will take two or three presses of the eject button to close the drive to where it will stay closed. Or you can close the drive tray with your hand manually and it will stay closed. So if you were turning off your 360, the drive may not have been in true mode-b. Although if you were having to close the tray manually and it showed up in windows, it should for sure have been in mode-b.

See, my drive is ever so slightly "bad word" anyway. The close button doesn't really work on it. Well the button does work, but something doesn't "catch" when its pressed, if you catch my drift. I've had to close my drive by hand for a few months now. But even when i was closing it by hand, it wouldn't stay closed, unless i had done the slax boot with the tray already open. Getting a bit confusing here now, lol.

But ya, the drive was indeed showing up in Windows. So safe enough to assume that its in mode-b?