| QUOTE (EmperorPsiblade @ Oct 9 2004, 10:07 AM) |
| hmmmm... can anyone else confirm this? |
http://forums.xbox-s...pic=271536&st=0
ahh..some info..
yeah i duno guys but something is fishy with that update
like i said the hd's were unlocked to update the OS
then relocked.
and there was nothing wrong with the installs.. or the lpc rebuild.
two seperate chips..two seperate boxes. both new..
now i have heard of loading the msbios onto the chip before
right now that seems to be the only option to fix these two boxes to make them xbox live compatible
where and how can i get the MSBios bin file????
or do i 'take' it from the xbox itself ?
i didn't see it on xbins :)
any links or info on my doing this would be great
jROC
WOOT... IT worked.....I downloaded the MS_5838 bios from Xbins
Flashed the Xenium Ice.
And boom it loaded just fine...
So the box is now fully functional.
But the question still remains... whats wrong with the onboard bios ??? and why did the Xenium OS kill it ?
jROC
This post has been edited by jROC99 on Oct 9 2004, 10:32 PM
| QUOTE (omg @ Oct 9 2004, 10:46 AM) |
| didnt they say you couldnt update to the latest os on a 1.6 that you had to update it on another xbox |
That's Xenium Blues, not Xenium ICEs
Sounds to me like an EEPROM issue, not a BIOS issue.
Its possible to erase the EEPROM, its much much harder to erase/corrupt the BIOS, and would normally require hardware modificaiton (but I don't know if this is the case on the 1.6)
| QUOTE (jROC99 @ Oct 9 2004, 10:07 PM) |
WOOT... IT worked.....I downloaded the MS_5838 bios from Xbins Flashed the Xenium Ice.
And boom it loaded just fine... So the box is now fully functional.
But the question still remains... whats wrong with the onboard bios ??? and why did the Xenium OS kill it ?
jROC |
Hmmm
And you're sure you've wired up the d0/lframe correctly?
It really sounds like its forced to ground!
yea check your wiring in my opinion, i just did a 1.6 w/ a xenium ice, tested tsop(retail bios, i know there's not really a tsop) and evox m8, both work fine.
all i used was the HDD version of the 2.0.1 update and burned it to an cdrw
This post has been edited by emailer33 on Oct 10 2004, 11:44 AM
/me doesn't get it.... His update worked fine; and it has worked fine for many here... Hrm..
Is it the MS dash or the bios which is dead?
The dash I can believe, the bios is write-protected normally.
If its the bios, then you should be able to load a bios to the xenium and everything will work fine. If its the dash, then that won't fix it (but it could be other things)
It's the BIOS. And loading of the chip works fine. Its just loading off of the TSOP that doesn't work apparently (though it does for me).
What happens if you put if back to 2.0.0?
For V1.6 boxes use the MS_5838 bios (256k)
For anything else..try the MS_5101 (256k)
jROC
yay, 5101 works.... didn't work before, but it works now o.O