Topic: Playing On Xbox Live (Read 67 times)

JonDante · « **on:** November 27, 2003, 03:09:00 PM »

I am a bit confused...does your M$ dash boot or not?

When did it say it needed servicing?

Do you still have Evox on your stock drive?

The fact that the chip is not flashing simply means that Evox is not telling it to. I assure you, the chip is still there.

I am more interested in your opening screen...the BIOS part.

More details.

JD

zanderch · « **Reply #1 on:** November 27, 2003, 03:59:00 PM »

Thanks for your reply. When I select the "Flash to TSOP", the Xbox does a soft reboot, and then it says, immediately following the "X", "Your Xbox need service".

dtechlogic · « **Reply #2 on:** November 27, 2003, 04:20:00 PM »

because your xbox has a unlock HDD that's the reason you get the message you must lock the HDD first.

zanderch · « **Reply #3 on:** November 28, 2003, 07:08:00 AM »

My harddrive IS still locked, it even says so in EvoX. The original dash IS on the stock harddrive, because when my chip is on, I can start the MS Dash and it works just like new.

zanderch · « **Reply #4 on:** November 28, 2003, 07:09:00 AM »

Sorry, Yes. I do mean "Switch" to TSOP.

issues_i3oy · « **Reply #5 on:** November 30, 2003, 11:24:00 AM »

maybe when you installed EvolutionX on your stock HDD you renamed your m$ dash to msxboxdash.xbe and evoX is xboxdash.xbe? If so, the rename it;)

JonDante · « **Reply #6 on:** November 30, 2003, 03:31:00 PM »

Actually it sounds like everything is working correctly when I go back and look at your first post. You have installed Evox 3971 so you are going to get a blinking blue light. IF you switch to TSOP does it boot normally as you stated in your first post?

IF it does, then all is fine, and you should be good for LIVE.

JD

dtechlogic · « **Reply #7 on:** November 30, 2003, 03:43:00 PM »

same here it sound like everything is working perfectly so what could be wrong with his xbox then. Just double check everything if your xbox is sure that it is lock and try again and another thing does it display the code number for that error or anything similar to it.

Heykrop · « **Reply #8 on:** November 30, 2003, 06:10:00 PM »

The problem could be that when he had the larger Drive in the system he had updated the M$ Dash to a newer version than the original drive has. This happened to me. I pulled the original drive with 4034 version dash and some time after putting in a larger drive I updated to the first Live dash. When I tried to go back to the original drive, with the Mod off, I got a service error. I used an EvoX CD-RW to boot the system with the original drive installed and then updated the M$ dash with a copy of what was on the larger drive. When I was done I booted with the Mod off and all was fine. NOT sure but the dash version info may be in the eeprom and that may be what was causing the problem. Dash versions did not match.

The other possibility for yours would be if you had ever run the DVD REGION PATCH on the original drive. That patch turns the M$ dash into Unsigned Code and as sutch the TSOP will not allow it to boot. To fix it you would need to get a clean copy of the original dash and use an EvoX CD-RW to FTP the clean one onto the drive in place of the patched one.

Author Topic: Playing On Xbox Live (Read 67 times)