I bought the 3rd generation Xenium ICE chip. I installed it on my 1.0 Xbox. The Xbox worked and booted into the OS fine. The OS was 2.0 Prerelease so I flashed the mod chip up to 2.3. This worked nicely. Then I used the very handy hard drive tool in the OS onto my new 200 GB drive. I installed the 200 GB as the main drive. Then I added to the launch menu of the Xenium OS the "flash", or original kernal. I rebooted, launched the MS Dashboard, started a game in the CD, all was well. THEN, this is where something got jacked, I ftp'd the Evox files over. The bios file, the dashboard file and the ini file to the root of the E drive. Being confused, I went into the Xenium launch menu and selected the dashboard file and the Xenium reported to me that the this file was the wrong size. So I figured it must want the Evox bios file. I selected that. The Xenium liked it. Then I rebooted, selected Evox from the launch menu, and POW! The machine seemed to lock up, the screen went blue. I waited. The Xbox seemed to just be spinning. So I turned it off. The Xbox never rebooted after that. Now, I'm wonder, just what is the Xenium doing when you select a launch item? Is the bios loaded on the Xenium itself, from the disk, and the executed? Or does the Xenium load the bios into the Xbox bios chip each time you launch? I'm thinking that it loads the bios into the Xbox bios chip at each launch and here's why: Since my Xbox never booted again, I think the bios chip got corrupted. Even when I put in the old hard drive, it still would not boot. I even tried putting the Xenium into recovery mode and it only reported BootldrreadData Error, or something. Is it accurate to say that the Xenium ICE loads the bios from itself or the hard drive and puts it into the bios chip of the Xbox? If not, I just can't figure what else I could have done that would have so permanently disabled my Xbox. I used one of the M7 builds of the Evox bios file. There were only two that I had. One was just the M7, the other was the M7 with the eject fix. There was no _16 indicating the Xbox 1.6 that I recall. What could I have done better? I'm going to try, try again. Thanks
So after reading through the forum I discovered that the Xenium chip loads the bios modules into itself and not into the Xbox. Anyway, now I have this very important question: The next time I try this mod again how can I ensure the following: I want to backup the Xenium chip into a place where it will load the backup if I reboot the chip in restore mode? I figure, if I jack it up again, at least I might be able to recover if I had this information. Thanks.
After reading this forum, I think I know what I did. I probably didn't wait long enough for the Evox bios to be flashed onto the Xenium ICE chip and I therefore corrupted it. But I'm still wondering if there's any way to recover from such a disaster if anyone knows. Sincerely, Tony Garrido
