Here's the story:
I have a Samsung MS-28 drive that I have wired with a switch for the VCC trick to get it to flash. For the past year and a half, when I want to flash it, I flip the switch on power up for about 3.5 seconds, then in DOS, I do an MKTFLASH on it and away I go.
Two days ago, my Xbox died. I have a working one with a broken Hitachi 78FL DVD. I desoldered the SST chip off the broken DVD and got the key from my external programmer. No problem so far.
I pasted the key into the latest ix12.bin I had been using for the MS-28 file and flashed it onto the MS-28. I neglected to spoof the MS-28 to a Hitachi 79, so when I fired it up in the new console, it gave me the appropriate error.
I took the drive back out of the box and went to reflash it, as I always have. Well, it didn't work... The VCC trick wouldn't yield a BIOS recognition of the drive (shows up a TSS whatever). When I tried to flash it, it recognized the SST chip as a 29SF, instead of the 39VF it really was. It would also be stuck at Updating... 00%.
I tried for hours to get past this (10 sec trick, etc...)
I figured the drive was bricked, and since I don't have an adapter to read the 39VF chips and the epoxy is a pain anyway, I figured the drive was bricked for all intents and purposes.
As a last try, I slipped the Enable 0800 disc into the drive and let it do it's thing. After it ejected, I tried flashing again, and voila, it flashed right up with the new spoofed firmware. It now works perfectly.
So my question is: Why did the VCC trick, which I have been using for the past year and a half not work this time? I used the same ix12.bin file I had been using, the only difference was that I had a different key flashed onto it and had tried to boot it in a xbox console that was expecting a Hitachi. Otherwise, everything else was identical to past attempts of which I had no problem.
Can anyone shed some light on what went down? It is really confounding me at this point, since the firmware was EXACTLY the same, except for the key.