Post by: M3_DeL on January 21, 2003, 05:31:00 PM
Be forewarned.
In order to install a new HD you must use a different bios!!!!!!!!!
Refer to this thread it you have a soldered in Matrix or want to flash via EvoX.
Helpfull thread
Post by: M3_DeL on January 21, 2003, 06:57:00 PM
Post by: xbox_freak!! on January 21, 2003, 07:02:00 PM
Post by: xbox_freak!! on January 21, 2003, 07:03:00 PM
Post by: Cheerio on January 21, 2003, 05:52:00 PM
not a frozen italian loaf on an ide cable.
Post by: xbox_freak!! on January 21, 2003, 05:53:00 PM
| QUOTE (Cheerio @ Jan 21 2003, 08:52 PM) |
| m3 - it helps to have a physical working harddrive - not a frozen italian loaf on an ide cable. |
lmao.....could I have cheese with that?
Post by: M3_DeL on January 21, 2003, 07:10:00 PM
I have never had the problem like i did with the X2 Bios.
Plese respond if you have installed a new Zeroed HD with X2 bios on it?
The problem I ran it was it wasn't booting the evoX disk when I had the blank drive in, but when I put the oem back in it booted the disc fine!!!!
This post has been edited by M3_DeL: Jan 22 2003, 03:12 AM
Post by: gabvey on January 21, 2003, 08:17:00 PM
But it was a F-boot variation of the x2.
I had no problem booting on cd when I first format the new drive. (However I had to find a cd that was compatible the DVD player, but that's another story).
Now I use a 4974 bios patched with xbtools (still booting on F) and I have no problem at all.
Gabriel
Post by: M3_DeL on January 21, 2003, 08:20:00 PM
I am curious anyone else try this with a vigin X2 bios.....no variations??????
Post by: Perplexer on January 21, 2003, 11:05:00 PM
Oh, did I mention that the first chip shipped with a bad flash? Between these two problems, drove me freaking nuts. Bastards never heard of quality control?
Post by: M3_DeL on January 22, 2003, 12:27:00 PM
Post by: Cheerio on January 22, 2003, 12:39:00 PM
Post by: Cheerio on January 22, 2003, 11:29:00 AM
Post by: equilibrium on January 22, 2003, 11:31:00 AM
seems a bit of an assumption that ALL xecuters/xecuter BIOSES have this problem. 
Post by: 420247 on January 22, 2003, 12:42:00 PM
Post by: M3_DeL on January 22, 2003, 11:38:00 AM
I know my shit, I've done this enough times to know that what is happening is not normal.
Let me explain it to you again. I had put the new HD in and the evoX disk in (boom error 16) I stick the old drive in (No problems) I put the new HD in again (boom error 16)
Error 16 is a dashboard error.
something tells me that the BIOS is looking for stuff on the HD first.....
Post by: M3_DeL on January 22, 2003, 11:39:00 AM
Im not worried about the chip, just the bios......the chip I used was the Matrix. I tried every mode and every jumper setting. so not quite sure what is going on
Post by: equilibrium on January 22, 2003, 11:44:00 AM
| QUOTE |
| More info on the two HD setups....did you use the default bios or did you flash it, and if you flashed it what bios EXACTLY ???? Im not worried about the chip, just the bios......the chip I used was the Matrix. I tried every mode and every jumper setting. so not quite sure what is going on |
I've not flashed my bios on my chip at all so it's 'original'. I have a 1.1 PAL xbox with a phillips drive. I basicly installed the chip one day and then installed the new hdd and evox etc the next. So nothing was done to the BIOS on the chip.
Post by: M3_DeL on January 22, 2003, 11:47:00 AM
Once I flashed the chip with the old Xecutor1 bios everything worked right away!!!!!!
Post by: M3_DeL on January 22, 2003, 11:47:00 AM
Post by: M3_DeL on January 22, 2003, 11:55:00 AM
Post by: Perplexer on January 22, 2003, 07:29:00 PM
| QUOTE (Cheerio @ Jan 22 2003, 07:39 PM) |
| dude, 100's of people have used x2 bios. 100's. and 3 people have a problem.....it just looks alot like end user error - |
User error
I see where you're coming from, but take a look at some of my other posts, and you should get a pretty good idea that I know what I'm doing.
I can't argue that this problem is affecting a very small percentage of people, but it IS happening, and seems to be affecting only those people with a specific 1.0 mainboard/4973 BIOS combination.
No combination of hard drives (I tried four, including the original), jumper settings, etc. would get past error 16, but once I flashed to a 4974 BIOS, *boom* booted up fine. This seems to be the cure for everyone with the same hard-drive-swap-error-16 symptoms.
Post by: M3_DeL on January 23, 2003, 10:18:00 AM
| QUOTE (xbox_freak!! @ Jan 22 2003, 05:50 PM) | ||
if its a brand new drive no need for 0ing |
brother I did that because i didn't know what else might be wrong?!?!?! So no one could say oh well you need to zero it out or anything!!!!!
Post by: manekineko on January 23, 2003, 01:07:00 PM
Post by: indotoonster on January 23, 2003, 06:29:00 PM
I'm wondering if it had anything to do with the modchip used. You used Matrix, I used Matrix. Could it possibly be a Matrix + X2 BIOS combination?
cheers,
indotoonster
Post by: exstazi on January 23, 2003, 07:01:00 PM
Post by: xbox-fun on January 25, 2003, 03:54:00 PM
But... i found out what was going wrong !!!
Before swapping to the new drive, my xbox was not connected to power outlet during some time. And when you try to run an xbox that was previously out of power, you are automatically directed to time and date setting screen, even if you have a CD inserted
But with a brand new blank disk in, the box fail to find anything and go into error 16 !
So i just put back the original drive, set time and date, swap again to the new blank drive, and this time my CD boot fine
I think there's no bios issue at all. Don't you ?
Hoping it can help...
See ya !
Post by: bluespot on January 25, 2003, 11:39:00 PM
It seems that the Xecuter BIOS will throw that error once it attempts to boot to a nonexistent F: partition (such as the case with the original xbox HDD) without even checking it's other boot options.So getting this error and want your box to boot again? You need to connect a hard drive with a valid dash on the F: drive. Borrow one from a friend
Boot it once to set the time, and then you can disconnect it and put in your new drive that needs partitioning etc. Either that or you can solder in a 32 wire homebrew and boot your original Xbox HDD with an Evox BIOS
Post by: indotoonster on January 26, 2003, 12:22:00 AM
| QUOTE (xbox-fun @ Jan 26 2003, 12:54 AM) |
| Hi there ! I had the same problem just a few days ago with X2 4974 on a PAL 1.1 box. I was very confused because i already had changed original drive by a 30GB one with no problem but this time i got error 16 when i wanted to put a brand new 120GB But... i found out what was going wrong !!! Before swapping to the new drive, my xbox was not connected to power outlet during some time. And when you try to run an xbox that was previously out of power, you are automatically directed to time and date setting screen, even if you have a CD inserted But with a brand new blank disk in, the box fail to find anything and go into error 16 ! So i just put back the original drive, set time and date, swap again to the new blank drive, and this time my CD boot fine I think there's no bios issue at all. Don't you ? Hoping it can help... See ya ! |
xbox-fun, you genius!
it all makes sense now. yes, i think i had to set the time when i inserted my original HD again. very interesting. thanks for this, it's been worrying me for a while now.
cheers,
indotoonster
Post by: weazil on January 30, 2003, 04:14:00 PM
M3_Del you are right evidently there is problems with some x2 bios's I was running 4974 Blue, and no hard drive would work, I either got error code 7 or 16 depending on the jumper settings. Saw your post and reflashed the bios to D6, and retried all the previous hd's that wouldn't work and they all came up fine.
Used Slayers disk to format / install. after up and running I deleted slayers stuff and put my original info on it. wanted to take the modchip out and just leave it as is but when modchip is disabled it gives error code 5 hd not locked. When I tried to lock it, config magic reports hd unable to lock. on both 13 gig drives i tried.... one wd and one maxtor.
any ideas on the locking part?
Post by: StupidIdea on February 02, 2003, 06:22:00 PM
Searched around at home found a different hard drive (I've got lots of hardware), and it worked perfectly.... Now I can play MGS2
Post by: M3_DeL on February 03, 2003, 01:49:00 PM
1. put in orig HD and set the time then try the new HD
2. Zero out the entire new drive using xboxhdtool
3. if none of that works try a different bios.
My thing is why is this bios looking at the HD first. There should be no need for that at all. Unless it is strickly a time issue, then yes it would look for the orig dash.
Post by: Madman on February 06, 2003, 09:24:00 PM
Post by: Kenny Midget on April 18, 2003, 02:48:00 AM
Post by: M3_DeL on May 09, 2003, 05:49:00 PM
This might need to be moved and pinned....this IS an issue with the bios.....the guy today had a 1.1 board
Post by: gainpresence on May 09, 2003, 05:59:00 PM
Post by: M3_DeL on May 09, 2003, 07:18:00 PM
Post by: kidkinetix on October 12, 2003, 01:06:00 PM
Post by: kidkinetix on October 13, 2003, 12:19:00 AM