still getting xbox error 06

weird thing happened a few days ago. i wanted to replace my dashboard on my 120gig hdd (hdd1) so i did what i usually do: wipe current dashboard (bear with me here), copy over new dash (no reboot!), check and double check that all files copied correctly. now i reboot, and to my suprise i get an error code. i dont remember which one, wasnt important at the time. so i think, "at least i have my eeprom backup disk!" i boot up xbhdm and unlock my drive. next i boot to to xbrowser, copy my previous dash files back to the appropriate directory and reboot back to the locking. it seems to lock fine, but when i put it in my xbox, SURPRISE! error 06. now even weirder, i go back to the lock/unlock screen in xbhdm and the drive unlocks fine. hmm. my curiosity tells me to try it in another xbox. i lock it with xbox2's eeprom and it boots fine. wait, im not done yet. maybe something happened to my disk i thought. so i swap in my other hdd i have for my xbox (40gig) boots fine. " so ill make another eeprom backup with this hdd" i think. i make the disk, which should have the same lockkey as my 120gig. i try tyo lock my 120 with the new disk. error 06. sorry for the long story, but i need help. i even tried rebuilding from scratch! NOTHING! please help me!

 

so no one has come across this problem?

 

Your eeprom.bin file must be corrupt or from another mobo... unless you have changed your eeprom data at some point with config magic.. it's as simple as that.

 

i have never used config magic. thats what makes it so strange. my 40gig locks and unlocks just fine, my 120gig wont 'properly' lock. help me please!

 

Isn't there locking capabilities in hdtools

 

im not sure what hdtools is. ive never used it before. by the way, i have a softmod, not hard.

 

It's an interesting one indeed.

Some drives have a maximum number of times (think it's 5) they can be locked/unlocked. It could be related to that, or it could be that for some reason this particular drive is locking to your pc mobo data rather than the data on xboxhdm.

Don't know if that helps any. It's all I can think of as you know what you are doing with this process.

I would investigate doing a hard reset on the drive hardware. Manufacturers site?

 

if i do a hard reset, would i have to go through the whole "build xbox harddrive from scratch" thing again? and i have locked/unlocked this drive at least 20 times easy. the max lock thing doesnt apply because it still works on other xboxes. it can be used in my pc without problems also. im pretty sure a chip would help a bit, but i dont want to spend any money on what should be a simple fix. thanks for the help.

 

i also noticed that when i press the Y button at my unleashx dashboard, where it says "serial number" i dont have a defined number. it just has a bunch of characters that i dont understand. is my motherboard corrupted? if so can it be fixed? please dont give up on me now.

 

Dunno... I wouldn't piss about with it TBH.. I think softmods are unreliable. I would stick a chip in the thing and be done.
It is very possible your eeprom has become corrupted, but the odd thing is it works with a different drive. How is the drive jumper set?

 

i checked the jumpers too. no dice. well, at least im the first to post about something like this. how could my eeprom become corrupted? and would i be able to do something with it if i did a TSOP?

 

TSOP works like a chip... but you need a booting box first.

I think your best course of action here is to attempt a direct read of the eeprom and compare that to how your drive is locked.
It is possible for the eeprom to become corrupted, but it normally takes use of that old nasty config magic to do it, and if it has then how are other drives locking successfully with exactly the same eeprom data?
That's what is stumping me.. It isn't logical unless somehow you have your eeprom files mixed up, or this mobo isn't the one you think it is (easily done.. I have been there once or twice).. doubtful.. I know you have this process down and dusted.

This thread http://forums.afterdawn.com/thread_view.cfm/357863 has heaps and heaps of information about drives and eeproms etc, and is probably well worth a read, otherwise you can browse llammas forums and see if anybody has come across the same problem before.

It's really odd that it's just that particular drive, and that it works in any other box while other drives will lock fine and run in this one.. If I was in this strange situation and had 2 I would just swap the one you use this drive in ..
I suspect it's something odd to do with that particular drive.. possibly some small fault in the locking that this particular mobo is picking up where others aren't..

Nice fault.. a totally new one to me.

 

since TSOP works like a chip, that means that i dont have to have my drive locked, right? my "problem box" boots with my 40gig in it. the other xbox isnt exactly mine, it belongs to a friend of mine who wanted to know whats up with this also. if it was mine, i would just switch it no doubt.

 

6 - kernel - Cannot unlock HDD

meaning that that hdd has a eeprom in combination with a different motherboard. every xbox has there own eeprom if you put a hdd in a xbox with a different eeprom thats on that xboxs mobo you will get an error 6

a xbox hdd unlocks and locks every time you start your xbox thats why you can hotswap your xbox so it cant be unlocked or locked only 5 times thats just silly.

 

Ahem.. moving on..

With the tsop it does depend on which bios you have flashed. Most xecuter and AFAIK all evoxM8 bios will run happily with an unlocked drive.

I have been trying to duplicate this fault with a maxtor 40 gig drive without any success. The only time it throws a 6 is when I either deliberately corrupt the key or flash the wrong data.

I'm mystified, and also intrigued by this one. I almost wish it was happening to me so I could investigate. The drive lock key is stored on an eeprom on the hdd... I would have my eeprom reader hooked to that like a shot

 

trust me, you dont want this to happen to you. i'll try a tsop. if that fails me, then i guess im in the market for another xbox. id rather have 2 than one with a chip. and i know what an error 06 means. apparently you didnt read the whole thread blacky. (damn that makes me sound racist)

 

Woah there..... You say you can lock another drive to this mobo and it works fine.....

Swap drives because I have a funny feeling about this particular hdd. I think it's reached it's maximum number of lock/unlock events. Wipe it completely and put it in something else for a while.. use it in your pc or something and see if it's playing up in any strange ways. Buying another xbox isn't going to help the situation with this drive.. It will probably do it again within hours or days of being put in another box.
I have seen similar activity with a nikimi 160 gig hdd.. xbox can't read sector0 from time to time but otherwise the drive is fine in anything but a softmod xbox.

 

If you have eeprom just format the 40 gig reinstall the C: (partion 3) and re lock it with xbox hdm

 

why would i format my 40 gig? it works fine.

 

yay! i either stumped everyone, or no one cares anymore. none the less, i just ended up convincing someone to give me their xbox. now i have two! ( or 1 and 3/4 at least) but thanks to everyone who put in their two cents, except the jackasses who said "just put a chip in it" (btw, tried that and IT DIDNT WORK!) my 120 and my 40 work just fine in this xbox with the same softmod ive done on my previous box and countless others. once again thank you.

sorry, but the jackass i referred to has been the most help. my apologies sir/ma'am.