Post by: ricjax99 on November 11, 2004, 05:30:00 AM
Heeeeeeeeeeeeeeeeeeeeeelp!
Post by: g0tr3wt23 on November 11, 2004, 06:25:00 AM
What it sounds like happened is that the guy who modded your box flashed the onboard bios (your TSOP) with something other than a MS bios and that that bios is looking first for some reason for your msdash before your evox dash. Either he used two different bioses, edited one incorrectly, or there is a problem with the evox configuration file on your 120 gb hdd. Either way if you wanna go on xbl you're going to need to reflash the TSOP with the standard MS bios. You can do this and reload the entire evox suite using a utility called slayers. You can download it from the "usual places"... search for something called xbins.
I'd say boot your 120gb drive into evox (chip on of course). FTP all your games and data to your computer. Get a copy of slayers and burn it to a cd. Reflash your TSOP with a MS bios. The turn your chip on and boot into slayers and lock your hdd. Turn chip back off and boot and it should work. I'm still pretty n00bish at all of this myself so don't take all of this as gospel. But sounds like you need to do a little reading in the newbie section. There are some awesome tutorials. I can understand you want to get up and running as quick as possible but I'd plan on staying off xbl for as long as it takes until you get this figured out. Whoever modded your box needs to write out EXACTLY what they did and in what condition your xbox was shipped to you. That would help everyone troubleshoot your problem much easier.
Post by: solid7x2 on November 11, 2004, 06:31:00 AM
but if you lock the drive and then turn off the chip and it goes to retail bios, i wouldnt worry about it.
if you lock the drive and turn the chip off, and something else happens, let us know and we can help u better (if u cant get in contact with that guy)
Post by: g0tr3wt23 on November 11, 2004, 06:50:00 AM
| QUOTE (solid7x2 @ Nov 11 2004, 03:34 PM) |
| sounds right to me, except for maybe 'flashing both bios' may mean there are 2 banks for bios' on the chip, and he flashed both the same... again, I would contact the guy... but if you lock the drive and then turn off the chip and it goes to retail bios, i wouldnt worry about it. if you lock the drive and turn the chip off, and something else happens, let us know and we can help u better (if u cant get in contact with that guy) |
Yeah but just flashing both banks on the chip with the same bios wouldn't keep the box from booting normally when the chip was off right? At that point the standard MS BIOS on the TSOP shoudl tak eover....
Post by: solid7x2 on November 11, 2004, 07:29:00 AM
try this and report back
Post by: g0tr3wt23 on November 11, 2004, 07:36:00 AM
| QUOTE (solid7x2 @ Nov 11 2004, 04:32 PM) |
| you cannont load the original bios with the chip off unless the hard drive is locked... you MUST lock the hard drive with config magic try this and report back |
He said he used a stock xbox hard drive from a DIFFERENT xbox. That would mean that the stock hard drive he put in was unlocked. If the system booted with the chip off and a hard drive that was unlocked then the TSOP on his motherboard has been flashed with a different BIOS and needs to be restored. The standard MS bios will not boot an unlocked hard drive and his hard drive must have been unlocked if it came out of a different xbox and still booted in his. Ergo his tsop bios is NOT retail MS if I am interpreting everything he said correctly.
Post by: g0tr3wt23 on November 11, 2004, 10:21:00 AM
| QUOTE (ricjax99 @ Nov 11 2004, 05:37 PM) |
| The drive it worked on was a OEM one taken straight out of an unmodded xbox, that worked this would be locked? The drive that won't work is the unlocked 120gb so if i lock that should it then work?  Thanks for helping out guys, mucho appreciated  |
ack
You really need to be asking these questions in the other forum bro but anyways...
When you lock a hard drive in an xbox: that hard drive is matched to that xbox. You can't take it out and put it in another xbox and have it work without first unlocking it.
The retail MS bios requires that your hard drive be in a locked state to operate...
What you seem to be saying is that you took a standard hard drive out of a different xbox and put it in your xbox WITHOUT first unlocking it on the other xbox and then not locking it on yours after you transferred it. If the chip was off and the machine booted with an unlocked drive that was from another xbox then the TSOP on your motherboard has been flashed and you need to reflash it with the MS bios. The only way that other xbox drive could have booted in your xbox was if your tsop has been flashed with somehting other than an ms bios. The hard drive you transferred HAD TO BE UNLOCKED ON THE OLD BOX AND THEN LOCKED ON THE NEW BOX or it would not have worked.
Modchips do not require the hard drive to be locked in order to run. Your hard drive only needs to be locked if you are using MS BIOS with modchip off and/or intend to play on XBL.
Use the search function
Post by: solid7x2 on November 11, 2004, 10:36:00 AM
| QUOTE (g0tr3wt23 @ Nov 11 2004, 04:39 PM) |
| He said he used a stock xbox hard drive from a DIFFERENT xbox. That would mean that the stock hard drive he put in was unlocked. If the system booted with the chip off and a hard drive that was unlocked then the TSOP on his motherboard has been flashed with a different BIOS and needs to be restored. The standard MS bios will not boot an unlocked hard drive and his hard drive must have been unlocked if it came out of a different xbox and still booted in his. Ergo his tsop bios is NOT retail MS if I am interpreting everything he said correctly. |
I think we are interpreting this differently...
Just because he used a stock xbox hard drive from a different xbox, doesnt mean it is unlocked.
| QUOTE |
| If the system booted with the chip off and a hard drive that was unlocked then the TSOP on his motherboard has been flashed with a different BIOS and needs to be restored |
this is why im saying he should lock the hard drive and see if it boots. if it does, then it should mean his TSOP is fine. and anyways this isnt the case because he cannot boot with the chip off
Post by: solid7x2 on November 11, 2004, 10:48:00 AM
Post by: g0tr3wt23 on November 11, 2004, 11:00:00 AM
| QUOTE (ricjax99 @ Nov 11 2004, 04:05 PM) |
| Basically: When an original xbox hard drive is connected and the chip is off the xbox boots to the M$ Dashboard and plays original games fine (and refuses to play backups) When it has a 120gb hard drive connected and the chip is off the xbox doesn't boot the M$ Dash it displays a screen that tells me my box is faulty (i think i need to check that tho) it deffo doesnt boot the Ms dash tho. I have EvoX on there bear in mind. Sorry i can't be more specific |
Read what this kat is saying.... in a previous post he said he took a stock hard drive out of A DIFFERENT UNMODDED XBOX and threw it into his without first unlocking it in the old one and then locking it in the new one. THE STOCK DRIVE WOULD HAVE HAD TO BE UNLOCKED IN THE OLD BOX AND THEN LOCKED IN THE NEW ONE TO BOOT IF THE TSOP BIOS WAS MS!!! But the system somehow booted to an msdash even though the hard drive he put in was from a different unmodded xbox (locked) and his chip was off? THATS A TSOP FLASH and quite possibly a screwed up or missing evox.ini file!!!
Arg why have I had to say this fourteen times?!
Post by: solid7x2 on November 11, 2004, 11:14:00 AM
I understand what you are saying about how the random stock hard drive shouldnt work in his box with the original bios. So there is reason to believe there was a TSOP flash.
I hope we can also agree that if the random stock hard drive appears to be locked, and to get the 120 gig to work, he should lock it and it should boot to the 'original' bios (although weather its original or not is what we are debating i guess)
Im thinkin he should flash the TSOP with the actual original bios and lock the 120 gigger as first steps... the rest should just be taking the usual precausions and clearing out C and E if desired...
can we agree on this?
Post by: g0tr3wt23 on November 11, 2004, 12:45:00 PM
| QUOTE (solid7x2 @ Nov 11 2004, 08:17 PM) |
| Ok, I think we are arguing similar things... I understand what you are saying about how the random stock hard drive shouldnt work in his box with the original bios. So there is reason to believe there was a TSOP flash. I hope we can also agree that if the random stock hard drive appears to be locked, and to get the 120 gig to work, he should lock it and it should boot to the 'original' bios (although weather its original or not is what we are debating i guess) Im thinkin he should flash the TSOP with the actual original bios and lock the 120 gigger as first steps... the rest should just be taking the usual precausions and clearing out C and E if desired... can we agree on this? |
mosdef ;-)
I'm still insanely curious to know how the "stock" hard drive he put in worked at all... I was under the impression that a locked hard drive from another xbox would not work in a different box with or without a modchip.... I have been known to be wrong tho
Post by: g0tr3wt23 on November 11, 2004, 12:46:00 PM
| QUOTE (ricjax99 @ Nov 11 2004, 08:34 PM) |
| Just checked my system info and I have the following: K: 1.00.4983.64 D: 1.00.5960.01 Not sure what to make of this myself  |
the 4983 sounds like the last version of the xecuter2 bios that was released although I don't know what the other number beginning with d: means... or whether or not the xecuter bios is on the modchip or tsop... :-/ ain't too well versed in the software area of xbox mods
Post by: ricjax99 on November 12, 2004, 05:59:00 AM
Cheers for your help guys