Ok, I got Xbox live a few days ago, and I am going to put some switches in today so I can enbale it or disable my mod chip, but I am a bit paranoid that I might logon by accident with my mod chip on. Does anyone have any ideas for safety mechanism? Is it possible to change the text under the xbox logo at boot up to say something like "Please Disable your Mod chip if using xbox Live" instead of Xecuter Lite?

I was also thinking if they was any possible way to change certain things in the bios such as where the evox dash is loaded from automaticly and point it to F or even point it to the CD drive and prompt to insert an evox CD instead of C so MS can detect it. That way when you turn the modchip on it will automaticly boot to evox or look for the evox CD.

Flash the chip with the colour BIOS that way if the x turns blue/red etc you will know the chip is on.

I've considered this have come up with an idea. What I was thinking it hooking up the disable switch to a relay switch powered by the HD power cable. The relay switch/es goes between you NIC port and your router/PC. Configure this so that when your mod is on it cuts the network connection.

Too bad for me, before I managed to implement it my xbox was banned. I will implement it as soon as I get my xbox unbanned.

Now I need to buy another xbox. What mod chip will fit current xboxs?

Yea, that's a good idea to. I thiink I'll do that for now until I can find another solution. Isn't there a program that changes the color in the bios, I for got what is what called, can someone jog my memory? Thx.

xbtool

What I have on mine is not a switch but a button. That when pushed in earths the D0. If you don't push the button it boots onboard bios. You can't make mistake cos you have to physically hold the button to enable the chip.

oh well duh, it looks like xbtool lets you change the boot partition!!! Well I'll just make it boot off F drive and stick evox on there. Will MS be able to detect evox on F???

Changing the boot partition is one thing, but Live still picks up the fact that you have modchip enabled. You do need your xboxdash.xbe to be original on dreve c: but still have to boot for Live with original bios.

u dont need to buy another box to get unbanned

use config magic

I know what you mean Regionfree. The setup I have is all original hardware and software on my xbox, except for a modchip that is in, but is disabled. All I really want to do is to be able to boot of CDR's. So When the mod chip is on it will boot to evox on F and when the mod chip is off, it will boot to XBOX dash on C as normal. I am just wondering if MS will be able to pick up that I have evox on F when the modchip is disabled while playing xbox live.

Just a dummy idea, but pull the CAT-5 cable out when your using non-standard stuff. No cable = no communication with the mother ship.

Steve

I have patched my BIOS so that the Xbox doesn't boot discs when it is reset or powered up, I also have the evox autoboot game option disabled.

To launch a game I have a menu item on the evox dash called "Launch Disc - do NOT use xbox live" that boots the disc. This "prevents" me launching an XBL game with the mod enabled simply by alerting me.

I also have a switched mod chip, and of course, when using the MS bios the disc boots normally because there is nothing to worry about.

I can still boot discs that I create myself -- if needed for recovery reasons etc..

This is a patch that I implemented myself.

i-ball, that is a stupid idea: to have a relay disable the port when the mod chip is on.
reason: you can't use any, any ftp features unless you go in and physically disable your work on the relays. plus, splitting the power cables is tricky at the easiest.

I did the same thing as Nullify. I have the partition 0 default.xbe changed to evoxdash.xbe. My CDRW boot discs have default and evoxdash.xbe on them, so they can be used on my or regular machines.

I run a matrix in mode 3, and have an item in evox to launch a DVD. I modified a menu program to say push eject now, and insert original game cd. Push eject, xbox reboots with stock bios, and runs the game. 100% safe.

rallycobra, yep, it works well doesn't it. It would be nice to see this patch implemented as a check box option in xbtool.

I like the idea with the button on D0! I may use that.


B.T.W, Was that guy kidding about the relay and the nic, or is he just crazy?

Why go through all this?

Just install an LED on the front (on = modchip on; off = modchip off).

Especially if you get a superbright ( >2000mcd) led, you won't make the mistake of getting on live.

If you have a matrix, it's even easier to install.



sharpie00

Some good ideas poping up, I think I'll disable the media check like NULLify said. There is an option for that in Xbtool anyway.

So will MS be able to see evox dash or anything else if I put it on F when my mod is disabled. I heard that the ms bios only supports 8gigs making it impossible to read F???

QUOTE (steveholtam @ Apr 11 2003, 07:19 PM)

Just a dummy idea, but pull the CAT-5 cable out when your using non-standard stuff. No cable = no communication with the mother ship. Steve

i'm pretty sure that doesn't work, i read somewhere that if you attempt to go onto xbox live, the system itself detects the chip and alters your X,Y,Z values, so even if the networking cable isn't in, the values will be changed and the ban packet will be sent the next time you connect. this could be wrong, but i have read this here and on quite a few differant xbox forums

REAPER

QUOTE (Reaper527 @ Apr 12 2003, 04:06 PM)

i'm pretty sure that doesn't work, i read somewhere that if you attempt to go onto xbox live, the system itself detects the chip and alters your X,Y,Z values, so even if the networking cable isn't in, the values will be changed and the ban packet will be sent the next time you connect. this could be wrong, but i have read this here and on quite a few differant xbox forums

The safest way for Xbox Live compatibility,
can be found in X-elixis Plug&Hack installation...

It works simple with 100% success,
as you have to physically unplug the plug-in,
and with the combination of a coloured bios,
you can see the results in your screen!
By unpluging the plug-in, nothing is connected on the mobo,
exept from 10 dead lines that M$ canot detect!

Of course that requires from you to open your console,
but with the combination of Xtension Switch,
you will be able to do it externally!
For this reason, a special mechanism has been added,
that permits the movement of the plug in while it is hooked on Xtension-Switch...

QUOTE (nasis x. @ Apr 12 2003, 04:29 PM)

QUOTE (Reaper527 @ Apr 12 2003, 04:06 PM) i'm pretty sure that doesn't work, i read somewhere that if you attempt to go onto xbox live, the system itself detects the chip and alters your X,Y,Z values, so even if the networking cable isn't in, the values will be changed and the ban packet will be sent the next time you connect. this could be wrong, but i have read this here and on quite a few differant xbox forums The safest way for Xbox Live compatibility, can be found in X-elixis Plug&Hack installation... It works simple with 100% success, as you have to physically unplug the plug-in, and with the combination of a coloured bios, you can see the results in your screen! By unpluging the plug-in, nothing is connected on the mobo, exept from 10 dead lines that M$ canot detect! Of course that requires from you to open your console, but with the combination of Xtension Switch, you will be able to do it externally! For this reason, a special mechanism has been added, that permits the movement of the plug in while it is hooked on Xtension-Switch...

or you could use an x2 lite with an external switch or an x2 pro using an x-ecuter bios and that will make the MS text switch with XECUTER2 , and if wanted a person can apply a color mod before flashing =)

As far as I am aware the MS BIOS can not see F: partition.

Personally, I boot from F: (i.e. that is where my evoxdash.xbe is) and my C: is completely virgin. I've also removed the possibility of launching the msdash with mod on (from evox etc), just in case an updated MS dashboard checks for the mod and sets a flag ready for the next time you connect to xbl. Some may call me paranoid

The "no-boot" patch involves changing "Device\CdRom0\default.xbe" (in the xbox kernel) to a another known file reference - so you can still boot your own discs. This is not an "option" in xbtool. You have to extract, change and repack the BIOS, is that what you meant by "option" - or am I missing something?

I agree with you NULLify, I am kinda parnoid also !

Well I though the option "DVD Drive Check" in xbtool disables the dvd drive boot, but I tried and it did not work. I now have evox on F with a red xbox logo at boot when the mod chip is on and have also removed the msdash shortcut (except XBMP automaticly still goes to C when I exit to Dash so it loads msdash ). Do you have any easy instructions for your no boot hack? I'd don't want to be able to boot any games unless I launch from the dash. I am trying to take every precation possible since I have read so many people getting band by accident.

The "DVD drive check" option in xbtool allows your xbox to be booted without a DVD drive connected.

As regards preventing a disc from being booted, there is probably more than one way to patch the bios, and I may have some redundant steps here, but it's better to include them rather than leave them out. I have noticed some inconsistencies if you miss out some steps.

- Start xbtool and "Open" the bios file, you can open an already patched bios file (with blue noani etc..)

- Click "Extract" and choose the same bios file again (this will decrypt the bios file.)

- A file has now been created called "xboxkrnl.img" in a folder with the same name as the bios file. Hex edit it, search for "Device\CdRom0\default.xbe". Replace the default.xbe part with something else, such as evoxdash.xbe, or whatever you like as long as you don't overwrite anything else. It is important you remember what you used in the eventuality you need to make a bootable disc.

- Click "Pack" and choose the xboxkrnl.img file you just changed. This will re-encrypt and write the bios file.

evox.ini could then contain:
Item "Launch Disc (don't use xbox live)",@14
or if you prefer with newer evox:
Item "Launch Disc (don't use xbox live)",ID_Launch_DVD

Regarding xbmp, I've changed my <dashboard>xboxdash.xbe</dashboard> in config.xml to evoxdash.xbe.

Thx a lot, you should sent this to XanTium and he will put it in the tutorial section on the site.

this is awesome, and I got it working, but I am wondering if any of you have noticed that you must keep the string the same length. It would make perfect sense to me, but you didn't mention it.

When I tried to change the string to: Device/CdRom0/xdefault.xbe (adding an x to the front)

It wouldn't boot at all, nothing came up on the screen after flashing. I flashed twice, and performed the edit on 2 different versions of the bios, with the same result.

When I changed it to: Device/CdRom0/xefault.xbe (only replacing the d with an x)

It works fine!

dKb

Just thought I'd add... If you don't have a multi-BIOS chip, or if you can't easily reprogram your chip externally, then you'll be pretty stuck if you mess up your files and EvoX doesn't boot anymore. The only way to re-install EvoX is with a boot CD, which won't boot anymore So your only choice would be to take out your chip, and re-program it with a BIOS that does boot CDs. This wouldn't be too practical for a lot of people. I guess you could have a fallback dashboard (the BIOS will try to boot nexgen.xbe if it can't fine evoxdash.xbe), but I believe that would only work if the BIOS can't find evoxdash.xbe It won't help if evoxdash.xbe is actually there, but won't boot.

Just a thought...

Nasis X, stop with your spam already! What happens when a younger sibling has the chip on and sticks in a live disc to play. You are done! A cheap mod with a modified bios is safer than your jerk and hack method.

Safest mod I have found so far is to modify the bios. The only way to mess up is if you put a live game on the HD, and run it from there.

dotKAMbot, you definitely DON'T want to put an X in front of device0, since the '' is part of the directory structure. You DO NOT have to keep the string length the same. There is room for several more characters in the three X2 bios versions I have modified. Best bet is to change default.xbe to evoxdash.xbe. That way, when you make an evox dash boot CD, you copy all of the dash files to the root. Put evoxdash.xbe in another folder, rename it to default.xbe, and add that to the root of your evox boot CD. The disc will work on any normal chipped box, and any others you create with a live safe bios. I do all of the boxes for my buddies, and it works fantastic.

Of course you won't be able to use Slayer's disc with this method, unless you duplicate the default.xbe into evoxdash.xbe in the root. If you can do this though, you probably won't need Slayer's disc! If I get some time, I'll try and type up a tutorial with some pics.

QUOTE (dzv @ Apr 22 2003, 03:48 AM)

If you don't have a multi-BIOS chip, or if you can't easily reprogram your chip externally, then you'll be pretty stuck if you mess up your files and EvoX doesn't boot anymore So your only choice would be to take out your chip, and re-program it with a BIOS that does boot CDs.

This requires clarifying. If you mess up because you changed something in the BIOS you weren't supposed to, then yes, you have a problem -- but why would you do that There is no problem if you want to boot the xbox with a disc for other recovery reasons.

As rallycobra and I have mentioned, here's how you create a disc that boots:

Instead of having a file called "default.xbe" on the disc, rename (or copy and rename so it boots on non-modded BIOS too) the file to whatever you changed "default.xbe" to in the BIOS - so it finds the file and boots the disc as normal.

Maybe a BIOS feature that checks outgoing communication with the NIC and if it detects data destined for the IPs of XBL servers and displays a message saying "turn me off". Don't know if its possible, but sounds good.

QUOTE (DWZ @ Apr 22 2003, 09:21 AM)

Maybe a BIOS feature that checks outgoing communication with the NIC and if it detects data destined for the IPs of XBL servers and displays a message saying "turn me off". Don't know if its possible, but sounds good.

Actually, I've proposed something similar for some time. I was surprised to see this thread did not already have a post from me in it (I was SURE I had replied to one EXACTLY like this a week or two ago).

Detecting the packet, which is also a precursor to going 'stealth' on XBL, would, in my version, cause the system simply to reboot, but a message would be nice, displayed on the screen, then a gamepad press would cause the system to reboot.

Something like:

Attempt to access Xbox Live detected. You must run Xbox Live sessions under the original Xbox BIOS.

This system will reboot

QUOTE (rallycobra @ Apr 22 2003, 03:36 AM)

dotKAMbot, you definitely DON'T want to put an X in front of device0, since the '' is part of the directory structure. You DO NOT have to keep the string length the same. There is room for several more characters in the three X2 bios versions I have modified. Best bet is to change default.xbe to evoxdash.xbe. That way, when you make an evox dash boot CD, you copy all of the dash files to the root. Put evoxdash.xbe in another folder, rename it to default.xbe, and add that to the root of your evox boot CD. The disc will work on any normal chipped box, and any others you create with a live safe bios. I do all of the boxes for my buddies, and it works fantastic.

I understand it isn't a great idea to change the directory structure, but you can. It just will be impossible to boot from a disk then. Anyway, that isn't what I did. For some reason, when I put the path into this forum, it took out the slashes. I fixed the post, and also my hex editor that was doing some whack sh@t when I did an insert. All is cool and working.

dKb

QUOTE (BenJeremy @ Apr 22 2003, 02:46 PM)

QUOTE (DWZ @ Apr 22 2003, 09:21 AM) Maybe a BIOS feature that checks outgoing communication with the NIC and if it detects data destined for the IPs of XBL servers and displays a message saying "turn me off".  Don't know if its possible, but sounds good. Actually, I've proposed something similar for some time. I was surprised to see this thread did not already have a post from me in it (I was SURE I had replied to one EXACTLY like this a week or two ago). Detecting the packet, which is also a precursor to going 'stealth' on XBL, would, in my version, cause the system simply to reboot, but a message would be nice, displayed on the screen, then a gamepad press would cause the system to reboot. Something like: Attempt to access Xbox Live detected. You must run Xbox Live sessions under the original Xbox BIOS. This system will reboot

other thread: http://forums.xbox-scene.com/index.php?act...f=3&t=45520&hl=

haha... you did reply to another post just like this, with this idea, but this thread is much better, with actual solutions. It is a great idea and could even be a step in the direction of playing on live with the chip enabled.

Now, this would take some serious programming, but what if you had the bios detect when live edits your status on your local xbox, and prevents that, or just "watch" for the packet that reports you to live, and stop it, or remove it. This would essentially allow you to play on live with your mod chip enabled. To find out what the packet or edit looks like would probably take a bit of work. We could set up a closed off network (even an xbox with a crossover to a linux box) and have ip addresses of known xbox live servers (especially the authentication servers) on the network, run a packet sniffer, and check out all the packets the xbox sends out.

This process would become even more tricky if the packet that reports your modded xbox is also one of the initial authentication packets. You would essentially have to cleanse the packet of the report or replace the packet. In this case, doing a bios mod may not be the way to go. What may be possible would be to have a computer between your xbox and the internet running some software that removes the report from the packet, or sends a clean one in its place. This makes authentication tough though.

What would make this super tricky, is if MS encrypted these packets. Then, it may not be possible, since there would possibly be a fresh hash with every connection that wouldn't be predictable. Who knows? I hope I have more time soon, cause now I am getting ideas.

The point is, that this check has to be taking place locally on our machines, maybe in the code of the games somewhere. If this is the case, there must be some way around it. Has anyone tried these paths before, or at least thought them out more than I have?

I have a question that maybe someone knows the answer to. I have heard people say that even if you aren't connected to the network, and you try to go on live, your xbox is marked, so that the next time you connect sucessfully, even if the chip is disabled, you will be banned. Does anyone know where the mark goes? Lets say I disconnect my xbox from the network, try to update splinter cell (unsucessfully of course), and then replace my eeprom before the next time I try to connect with the xbox linked to the network. Will I still get banned if the chip is enabled or is this just a urban legend?

peace,

dKb

QUOTE

As rallycobra and I have mentioned, here's how you create a disc that boots: Instead of having a file called "default.xbe" on the disc, rename (or copy and rename so it boots on non-modded BIOS too) the file to whatever you changed "default.xbe" to in the BIOS - so it finds the file and boots the disc as normal.

Yeah, I didn't think about that. I guess I didn't have my thinking cap on at the time

dotKAMbot,
Only proven way to get banned from live is to :

1) be hooked up to an internet connection
2) run a modified bios
3) Access a Live feature

Unless all 3 critera are met, you will not get banned.

There was a lot of FUD about flags and other stuff being written to the HD and caught on the next boot, but this has never been confirmed. All urban legend.

A subnote is that beta testers that were using modified bioses got banned when Live! came out of Beta. It think MS had a eeprom list, and banned thousands of boxes at once.

And for the love of all things holy! You guys want a bios that sniffs every network packet and looks for a live packet? Talk about cpu overhead! Buy a box for $200 or less with a coupon, sell the controller and pack in games on ebay, and you now have a legitimate live box, and an extra box when friends come over! You guys are going to have a computer sit between the internet and the xbox to sniff packets? The developers have much cooler stuff to work on!

Just spend 5 minutes to modify the bios to make it live safe and you are golden.

QUOTE (rallycobra @ Apr 22 2003, 09:43 PM)

dotKAMbot, Only proven way to get banned from live is to : 1) be hooked up to an internet connection 2) run a modified bios 3) Access a Live feature Unless all 3 critera are met, you will not get banned. There was a lot of FUD about flags and other stuff being written to the HD and caught on the next boot, but this has never been confirmed. All urban legend. A subnote is that beta testers that were using modified bioses got banned when Live! came out of Beta. It think MS had a eeprom list, and banned thousands of boxes at once. And for the love of all things holy! You guys want a bios that sniffs every network packet and looks for a live packet? Talk about cpu overhead! Buy a box for $200 or less with a coupon, sell the controller and pack in games on ebay, and you now have a legitimate live box, and an extra box when friends come over! You guys are going to have a computer sit between the internet and the xbox to sniff packets? The developers have much cooler stuff to work on! Just spend 5 minutes to modify the bios to make it live safe and you are golden.

Actually, it's a one byte check, initially, for a vast majority of the packets.

As the routine that would hook could send the packet along to the real routine, as soon as it identifies it as a packet it doesn't want. You don't need, nor want, to check all of the bytes in every packet.

I wouldn't replace the packet, anyway.... just stop the machine with the message displayed and reboot after the user hits a button. Stealth is likely possible.... M$ CANNOT change the way they handle the protocol now, without breaking all previous XBL games - that's the disadvantage of running on a console, from their perspective.

The deeper question is what evils an XBL 'Stealth' feature would bring.

Certainly it would bring the wrath of M$, which would redouble efforts to foil us, probably getting nasty. It would also lead to countless cheaters, making XBL no fun for most people (especially those who pay for BOTH games and service). It would ruin the service.

So instead of going stealth, the best solution is one that prevents you from accidentally running your modded Xbox on XBL by rebooting the system or blocking packets outright.

QUOTE (BenJeremy @ Apr 23 2003, 02:17 AM)

The deeper question  is what evils an XBL 'Stealth' feature would bring. Certainly it would bring the wrath of M$, which would redouble efforts to foil us, probably getting nasty. It would also lead to countless cheaters, making XBL no fun for most people (especially those who pay for BOTH games and service). It would ruin the service. So instead of going stealth, the best solution is one that prevents you from accidentally running your modded Xbox on XBL by rebooting the system or blocking packets outright.

Yeah, you bring up a good point here. Maybe it is best to just leave well enough alone. I am actually very happy with the current patch that won't allow me to boot from a real game. The point you make about the people who pay for both games and service certainly rings true. I guess I wasn't really thinking about them. (which includes myself)

I am not completely sure that I agree about the whole idea of a flood of cheaters. It is certainly possible to cheat on many PC games, and I don't think it has a huge impact from what I have seen. Really though, it only takes one cheater to ruin a game I assume.

When all is said and done, the number of live games I will actually want to play is very limited and so far I have them all. I just enjoy coming up with ideas and solutions to problems.

@rallycobra: thanks for the info on the banning. I feel a little better about it now.

QUOTE

You guys are going to have a computer sit between the internet and the xbox to sniff packets? The developers have much cooler stuff to work on!

What developers are you referring to? I wasn't aiming my suggestions in any specific direction. I was simply thinking out loud. Since I don't do any kind of MS development, and very much dislike any languages any of the xbox applications are written in, the only way I could accoplish this is by using a separate box to analize traffic and take action.

dKb