Post by: masta2000 on September 19, 2007, 05:21:00 PM
i installed a maximus 79 passkey flawlessly on my drive. The first boot i do (not connected to the computer) the blue light that is supposed to turn on when in mode b doesnt turn on. So i look around the maximus passkey site and they say that if the setup is good, boot it using slax. So i boot the xbox connected to the computer with slax, before the login screen, i turn the xbox on. At that time, the blue light flickers (in mode b?). so i reboot the computer and the xbox (i think this is where i screwed up). The main light is flickering and wont eject (modeb ?). I reboot both since my computer was jammin on bootup, and , since then, the drive doesnt react to ejects or in windows (slax gives me 0x80).
I had moded many ms25/28 and one of two older hitachis, but this was a while back and i didnt quite remember the whole process, which is why i made some bad decisions, ie rebooting when the main xbox light was flickering ...
Anyway, does this mean my drive is completly bricked?
Anyhelp is great ....
Thanks, Masta
This post has been edited by masta2000: Sep 20 2007, 12:22 AM
Post by: masta2000 on September 19, 2007, 07:37:00 PM
At least with the key i can get another drive ...
Thanks alot guys
Post by: masta2000 on September 20, 2007, 08:09:00 AM
Post by: masta2000 on September 22, 2007, 03:33:00 PM
How about people who have the necessary equipment to extract the key from the chip and everything?
I'm willing to invest into these services ...
Im situated in Canada ...
Thanks
Post by: masta2000 on September 24, 2007, 02:58:00 PM
Post by: kingpip on September 24, 2007, 11:23:00 PM
Post by: Toddler on September 25, 2007, 11:23:00 AM
QUOTE(masta2000 @ Sep 19 2007, 06:21 PM) 
i installed a maximus 79 passkey flawlessly on my drive
Post by: masta2000 on September 27, 2007, 08:29:00 AM
Im guessing theres nothing to do then ?!?!
Could someone please point me out towards a drive repair/service specialist?
Post by: neildo on September 27, 2007, 11:08:00 AM
Turns out I had to run Slax cd anyway on the system to really make sure the drive went into mode b. I assumed that part wasn't needed as the Maximus tutorial says the blue led coming on signifies mode b.
Post by: masta2000 on September 28, 2007, 12:58:00 PM
I installed the ribbon cable also, points were all good, triple/quadruple checked for continuity, it was good.
I just cant understand how just booting it would screw the firmware .. i didnt even try to flash ...
I get error e64 when plugged into xbox and no response when plugged into windows/cpu
This post has been edited by masta2000: Sep 28 2007, 08:00 PM
Post by: HamsterZZ on October 01, 2007, 06:56:00 PM
I didn't flash it though since I had bad luck flashing 78s and I just put the key on Samsung instead.
One thing I noticed, is that it that the LED would only come on after a cold bootup. If I powered down the 360 with the power button, it wouldn't come on when I powered it up again. I had to remove the power cable, wait 5 seconds, plug it back, and then power it up again.
So basically, I didn't use SLAX at all in this process and got a good dump of a 79FL with passkey.
Post by: astra221 on October 02, 2007, 06:41:00 AM
So in your case there is probably a glitch where it disables itself or gets confused, thus granting mode b.
I just ordered one and its going to be my first time using a passkey.
This post has been edited by astra221: Oct 2 2007, 01:43 PM
Post by: neonmod on October 02, 2007, 09:16:00 AM
QUOTE(astra221 @ Oct 2 2007, 01:41 PM)
On the maximus website it states on the Question & Answer(Q4) that when your done finishing with a good flash, no need to disable passkey, the passkey disables(the modeB ) itself automatically.
Correct, on boot up the passkey checkes the firmware in the drive.
If it's original it turns on modeB, if a hack firmware is detected the passkey disables itself.
It looks like this drive dumps and flashes fine with the VIA VT6421 cards, not mine anyway which is a Newlink with ALI chipset.
I have ordered the via card.
Post by: masta2000 on October 03, 2007, 08:48:00 AM
Still original firmware on the drive. My guess is that the passkey corrupted it.
I disabled the key by bridging the j1 jumper. The drive doesnt react to ejecting, and i get the e64/65 error...
From what i understand, my last solution is to get the eeprom removed to get the key so i can flash it onto another drive ...
Post by: neonmod on October 03, 2007, 11:05:00 AM
QUOTE(masta2000 @ Oct 3 2007, 03:48 PM)
I never had the chance to flash it ... (IMG:style_emoticons/default/sad.gif)
Still original firmware on the drive. My guess is that the passkey corrupted it.
I disabled the key by bridging the j1 jumper. The drive doesnt react to ejecting, and i get the e64/65 error...
From what i understand, my last solution is to get the eeprom removed to get the key so i can flash it onto another drive ...
That what eventually happened to me but i got further than you managed,
i had perfect solder connections, no shorts, blue light as expected and read disks fine in windows (ModeB), just could never read the firmware from the drive with FW4.0, everything else worked 90% as prescribed, just not the final dump/flash stage, then after so many attempts to read the FW the drive decided to die on me(E64) no eject, dead,.
Luckily managed to get a replacement elite.
I wish there was some way to software check the 79 passkey for errors or reflash it with Maximus passkey firmware in case the passkey is corrupt somehow, at least then i would know what may have been the cause of the failure.
I think i may wait this one out this time.
This post has been edited by neonmod: Oct 3 2007, 06:18 PM