Xbox 1.6 problem - Error Code 06

paragon_au

Junior Member
Jul 31, 2005
11
0
I modded my 1.6b xbox. All went well.
Except for one problem, when I turn off the chip, it boots up as per normal with the xbox logo. Then I get the error code 06, I didn't know what it meant so I just keept going. ([font=verdana, arial, helvetica] As I now know: 6 - kernel - Cannot unlock HDD).

I downloaded x2_5025_v16plus_512k and used http to flash it onto the xbox.
It got flashed to bank 1, but when I boot up it tells me "Xecuter2 config live loading..." and just stays there forever.

I am thinking this might be something to do with the error code. That the hard drive can't be unlocked, so the config file can't be written.
If that's where the config file is written.

OR

Maybe I am missing something, do I need to transfer the x2config.ini file to the xbox? I had thought it was auto-created with defaults if none was loaded.
How do I transfer it to the xbox?

OR

Am I just totally confused. I can't figure out what to do.
Can anyone help?
[/font]
 

Big_Whoopin

VIP Member
Jan 29, 2004
811
0
SE Pennsylvania, USA
Don't know why your box is locking up after the config live loading screen. That screen can sit for 5-10 seconds depending on your setup, but then you should get the flubber animation.

But for your info...
First, if the BIOS you flashed is 5025 and that isn't a typo, I would recommend putting 5035 in there in its place. 5035 is the current release and has fixes that corrected problems and/or added more features.

Your HDD does not need to be locked or even partitioned for the X2 BIOS to boot. If your HDD is blank you will though need media to boot from. Without this you should still receive an error, not just a lock up.

The config file does not get written, it only gets read. If the BIOS cannot find x2config.ini on the E or F drive it should load using default settings. The only way the file gets created on the HDD is when you put it there.

While I can't provide you a solution to your problem hopefully you will now have a bit better understanding as to how things *should* work.

-Whoopin'
 

paragon_au

Junior Member
Jul 31, 2005
11
0
I figured it out.

Me and 3 of my mates (other 2 had 1.6, I had 1.6b) were all doing our mods at the same time.
And I put one of their hard drives into my xbox when I but it all back together. That was what was causing it.
As soon as I changed it to my hard drive, everything went perfectly.

Thanks whoopin'
 

Big_Whoopin

VIP Member
Jan 29, 2004
811
0
SE Pennsylvania, USA
That explains the error code 6 from the MS BIOS, but I didn't think the X2 BIOS would lock up due to a locked drive. I would have thought that it too would display a code 6.

Glad to hear you got it sorted tho.

-Whoopin'