Can a modchip flash the Xbox TSOP?
 

From one night to the next my box changed (seemingly on its own) its boot procedure..

I had power set for the MSdash and Eject set for the Xenium OS and from there you can boot into EvoX..

So.. Without exageration it changed from one power down to the next power up.

The eject has remained the same but now for some reason the power goes straight into EvoX dash without going through the Xenium OS at all which was a total change from going into the MSdash.

Now it doesn't really matter anymore seeing as how I don't need to boot into the MSDash right away (banned from live) and I still have the Retail Kernal flashed onto the Xenium Chip..

But i'm curious.. What in the blue hell could've happened? During the first power up the eject led flashed yellow and I believe went into a black screen.
I powered down and it began to boot the way I mentioned above.

Another detail is that I had edited the Xbox logo screen for my M8_16 bios to be a red color and other small details about it. I completely deleted this bios modification from my mod chip and loaded the same M8_16 bios with defaults settings. Now again when I press the power button it starts up with the same red Xbox logo from the bios that doesn't even exist on the chip?

What in the heck? Tylers opinion is a glitch which I'm in total agreement with but I want to know what was going on during that flashing yellow LED. Is it in any way possible that the Xenium Mod chip could've flashed the TSOP with the M8_16 bios that had the red logo?.. If it doesn't exist on my mod chip where else could it be?

I replaced my msdash.xbe with my back up.. No change..
My INI files on the Xbox C: drive weren't modified.. And the bios boot procedure was still set the same boot sequence wise?..
Any theories or advice would be cool..

Well, this is a bit strange. First, I wanted to comment about your last problem with booting the red bios. Did you delete the bios or overwrite it? I am not sure how the chip is set up, but it might not have deleted the bios at all, rather just waits for you to overwrite it. I know some chips say something like "up to 1000 flashes" or something similar to that. Zeroing out a chip would waste a flash, although, 1000 times flashing the chip is probably not going to be reached.

Maybe someone othetr than myself could help you out, since I have not seen the Zenium OS at all. But, does the OS boot the Original bios, or is the chip disabled from the start? If the OS boots the bios, then you can probably change boot procedures in the OS settings. I dunno, that is all I got.

And to answer the topic, not without you knowing it. 1.6's don't have TSOP's to flash, and v1-1.5 require you to bridge 2 sets of points to disable the tsop flash protection.

Yes explain more on how you deleted your bios. Did you delete it from your hdd or through the chip?

I kinda think youve flashed your chip and its booting normally but maybe you didnt assign the correct options that you intended. When I get more time Ill do some research on how your particular chip works and Ill get back to you on exactly how you did yours.




Tyler!

Hey guys.. Well I'm guessing I deleted the Red bios straight from the modchip. The Xenium OS has a few options on the launch menu where you choose your bios and you can also edit the names remove and flash new ones.. Now I chose "remove bios" which I would think deletes it from the chip completely, but I didn't write the OS so I have no idea.. Maybe it did just take it off of the launch menu until its overwritten.

Quall the Xenium OS does have a few basic boot procedures but its more like a quick boot mode.. It doesn't let you specify what bios to boot up with. And I was unware about the whole TSOP situation.. I'd never really needed to read up on it. The Xenium OS can boot the Original Retail bios that I sort of uploaded fromt he box in an OS menu. When you go to flash the retail kernal you choose flash from TSOP instead of the other option which would be flash drive... So anyway when you go to launch a bios the Retail Kernal is still available.

T, Yea I thought about that too.. But I reflashed with the same red bios (tweaks and everything) that was working perfectly before.. I used EVTool for the editing. I saved a bin on my computer.. I checked the boot order and it was the same.. But reguardless I still had the same prob. I had the first boot device set to be EvoX and the second being the MS dash which was supposed to be linked to the power button. So I dunno I mess with the order afterwards and nothing made a difference. Dunno.. Kinda stumped.

Sorry the post jumps back and forth.. Just got up and i'm a little cloudy yet. I hope you can make sense of it