Print

[syntaxerror329]

I am just going to cut and paste the email i just sent to maximus and see if anyone here in the forums can help me.

I have done 4 drives with passkey so far and 2 drives are now bricked. The first two I did ok were 0079FK drives. The next 2 have been 0079FL and on the first FL one it bricked before I could even read. On the second one I did today I was able to read and flash without a hitch but on power up of the 360 I got the E64


I also got an email today from another guy in my area asking me for help with the same issue. Here is a copy of his message to me.

“Hi Greg I have an E64 error on a Hitachi 79 drive.  Used the 79passkey.  Any ideas?  Everything went smooth and even loaded up a backup but afterwards I got the E64 error.  This happened on two of the systems that I did.  I used FWtoolbox 4.0.  thanks.”

The system I am having trouble with today is a Pro System w/ HDMI and a manufacture date of September 3, 2007

I read some threads regarding this and it looks like I am not alone? Any suggestion for unbricking drive?

[andrew.brazil]

QUOTE(syntaxerror329 @ Oct 15 2007, 08:40 PM)

I am just going to cut and paste the email i just sent to maximus and see if anyone here in the forums can help me.

I have done 4 drives with passkey so far and 2 drives are now bricked. The first two I did ok were 0079FK drives. The next 2 have been 0079FL and on the first FL one it bricked before I could even read. On the second one I did today I was able to read and flash without a hitch but on power up of the 360 I got the E64
I also got an email today from another guy in my area asking me for help with the same issue. Here is a copy of his message to me.

“Hi Greg I have an E64 error on a Hitachi 79 drive.  Used the 79passkey.  Any ideas?  Everything went smooth and even loaded up a backup but afterwards I got the E64 error.  This happened on two of the systems that I did.  I used FWtoolbox 4.0.  thanks.”

The system I am having trouble with today is a Pro System w/ HDMI and a manufacture date of September 3, 2007

I read some threads regarding this and it looks like I am not alone? Any suggestion for unbricking drive?

I think that is something related to the black epoxy removing process. After you flash your drive, the drive board is heat, but after a few time it gets cold and maybe some solder "shrink". Get it? I had the same problem with 2 drives. I heated them again using some solder flux and they are back to live.

Brgds.

[syntaxerror329]

Well i have considered heat as a possible cause but I really don't think heat did it. The reason i say that is after heating drive it still worked. It was a hour after i heated it before I tested it because I put 2 tiny drops of epoxy on either side of my flat cable socket and waited for the glue to get really hard before plugging in my flat cable. I also shield the rest of the PCB from the heat with tin foil and only expose the part i need to remove.

It then booted a DVD, Tray worked, I read the firmware, i flashed it. Then i connect it to 360 and E and now passkey doesn't light up anymore and drive is basically dead. This was the cleanest install i have ever done of passkey.

I have already ordered a samsung off ebay. Actually i got a laughter today when i checked the guys feedback i noticed maximus bought 3 of them himself. (he probably bricked a whole bunch with passkey too)

I think i am going to remove the EPROM off my dead drive and read it in my programmer and compare it to my hacked.bin to see if this was just a bad flash. I will report back here with my findings.

If anyone else needs me to read their SST39SF020A with my EPROM programmer I am located in Niagara Falls, Ontario just email me at greg(at)boxxdr(dot)com.

[syntaxerror329]

Well almost a whole month later and i finally decided to remove my eprom and dump the firmware.
I have confirmed that my flash was not bad. It was an identical match to what i flashed to it so somehow i was able to flash this drive fine but still brick it.

I have done one more 79FK since this one with my passkey and this time i did not use a heat gun. Instead i just heated up the tip of a small screwdriver and heated up the epoxy i was removing with my soldering tip. It removed the epoxy fine. (you dont need to remove much of course)

On this most recent one i had some issues with the drive showing up in windows and then disappearing before i could read or flash it. I used some contact cleaner to make sure all my flux was cleaned up and retried it and it worked prefect.

So for me I have flashed 2 79FK's with passkey fine and bricked two 79FL's

I am going to be doing a 5th one soon wish me luck everyone.

[Boba_Fett]

So has anyone been able to perfectly flash a v79FL?

[syntaxerror329]

I was on the Infectus website today and noticed a news item from september.

079KEY v1.2 AVAILABLE - All FL firmwares supported!

This acknowledges that their previous version had issues with the FL's.
Is it not true the code they used is based on the same code as the 79passkey?
If so i would think maximus' product maybe also needs an update.

He must be bricking drives too becuase he bought 3 replacment drives off the same guy i did on ebay.
Items 260164943656, 260165038059, 260164567302 lol. (he could have just been fixing systems i know)

So i would still like to hear from anyone that has done 10 or 20+ of these how thier luck has been and what they are doing or doing differnt.

Thanks

[Boba_Fett]

But you've actually had success with a few Passkey79s with some FLs, right? Maybe there are some different subset versions of the FL...

[Discwizard]

Well, I have done 9 version 79's. Two of them were FK's and the rest were FL's. ALL of them worked no problem. The first time was kind of tricky, but it has been smooth sailing since (crossing my fingers now) I have used the Maximus passkey on all of them. I have an onboard VIA8327 SATA, and using Toolbox 4.0 (I will use 4.5 from now on though). So, I don't believe that there is any reason to think that there are some rogue set of V79's out there, but who really knows?
I really think it has more to do with SATA incompatibilities more than anything, since it is the only common ground we don't all stand on......We ALL use a Hitachi 79FL/FK drive.......We ALL use Firmware Toolbox to patch/dump/read the firmware.......We ALL used the same device (passkey) to enable read/write to the firmware chip, but very few of us have the same EXACT hardware specs in our PC's.
Just a theory, who knows....I could be drinkin' donkey sperm tomorrow-sheesh.

[Boba_Fett]

QUOTE(Discwizard @ Nov 19 2007, 09:32 AM)

Just a theory, who knows....I could be drinkin' donkey sperm tomorrow-sheesh.

 (IMG:style_emoticons/default/laugh.gif)

That quote made my day. +1 lulz to you sir!

[syntaxerror329]

Just did a 79FL (Drive had date of July 2007 on it)

Worked like a charm,

I used a heat gun to remove the epoxy. I tried a few other ways like heating up the epoxy with my soldering iron tip and that didn't work good at all so went back to the way i know.

I didn't even test this one for any shorts or anything. I soldered in the flat cable socket and it looked so good i just forgot to test it.

So my score is now 2 x 79FK's Good 1 x 79FL Good 2 x 79FL's Bricked.

So passkey must not be so bad after all. (sorry maximus for doubting you)

[huobin]

I moded almost together 10  79fk and fl by maximum 79 passkey and toolbox 4.5, . All successed. passkey removed after flashed.

all reading / flashing no problem, but still some problem happens later:

1) one week before, i flashed one 79fl, it  read the game the first boot up after flashing. the second time power on,  i got  e64 error, after power off and reboot, everything fine untill now.

2) another one,  after 1 week playing, it doesn't read any games even original version. but if keep opening and closing the dvd tray, it may play the game after several try. no any error message.

3) 3rd report from customer is: system keep saying disk dirty after playing 2 days without any problem on one game disk, but other games all ok.  the disk is actually very clean.

they r all very new system 79 fl. what i m afraid any new stuff microsoft put in system??

[Riddick77]

Hello!


I have a same problem! I install the maximus passkey ,in my Elit Xbox360,the drive is FL ,then i have E64 code!!!! I repair many consoles before,i check the installation 5 times! But my drive now don't open the tray,and i have E64!!!!! Sorry my weak english! Please Help!!

This post has been edited by Riddick77: Dec 2 2007, 12:32 PM

[brad8314]

I'm having this problem with my 79FL as well. flash went fine removed passkey no probs. booted and played a game fine, shut it off and now get e64 and the dvd drive won't open. sometimes it will work but most times it won't.

[Yanmar]

Hi,

Samething for me. I have many experience in 79fl drive and i bricked one... After that i checked why. And  i found that my original .bin wasn't the same that the others. For to do a fast check. Open your original.bin file. and with xboxtool 4.5 go in tool and click on "recover lost original file". A while after xboxtool should be ask for a name for to save the new file. If this appen, the original.bin is right. But if toolbox doesn't find any recover file. This is not good and dont flash the drive. You will have a 64 error. I thought that my file was corrupted but after many test... no. I know my orig.bin file is ok.

I know that my .bin is right. I took the key for to spoof a ms28 succesfully.

2 day ago, i had the same problem again. But this time i didn't flash the drive (IMG:style_emoticons/default/smile.gif)

I took the .bin file with 2 differents sata card for testing. A via 6421 and a intel ich5. I compare both file with hexworshop. It match perfectly. Both card are able to flash 79fl. Anyway i know because i already flash many drive before with this both card.

Where is the problem... 2 version of 79fl firmware ?  An intermittent  problem with maximus passkey ?

There are a problem... the forum are full of 79fl with e64.

Bye

Yanmar

[huobin]

i m afraid M$ has sth new on 79fl,  maybe the position of the key string need a sepecial condition or just bug on the ixtreme file for 79fl

notice, no problem on 79fk!