Xbmp Ntsc-j Error
Posted 18 January 2005 - 06:17 AM
Sorry to start another topic on this error but the search function and sticky didn't help me - a customer of mine brought his box back to me after changing the settings in XBMP to NTSC-j and messing with the resolution. His box now behaves as follows:
- "Chip off" boot: Box boots, normal green flubber animation and sound, then goes to error 21.
- "Chip on" boot: Box boots, blue modded flubber animation with sound, goes to xbox logo splash screen except the top corners of the picture are skewed inwards (I can tell because my BIOS splash screen background is white, so I have 2 black triangles top right and top left on my picture), then box reboots itself, then green flubber animation, then error 21.
- "Chip on" boot, evox bootdisc in DVDROM (I was trying to load enigmah to switch the videomode back to PAL) - box boots, blue flubber animation, skewed xbox splash screen, reboot and repeat over and over again. There's nothing wrong with the bootdisc, I've used it to flash modchip BIOSes and format HDDs in 50+ xboxes.
I cannot get this thing to boot a disc (so no videomode switchdisc fix), it doesn't load the dash so obviously FTP is out. I haven't yet tried to boot with a movie DVD or a retail game in the drive, and I haven't yet tried booting with the vid cable unplugged (suggested fix which apparently worked for others in this forum). I'll try all these options tonight. Failing that, has anyone else had this error, do they know what causes it, and were they able to fix it?
Posted 18 January 2005 - 11:25 PM
1) Boot xbox with video cable unplugged (eject light will flash green and orange) and an Enigmah Videomode boot disc in the DVDROM
2) Wait until you hear the DVDROM stop reading, then push "A" (for PAL) or "B" (for NTSC)
3) Reboot xbox
Your video mode should now be back to normal, and your xbox should boot.
I actually used an EvoX-based boot disc similar to Slayer's, with the Enigmah videomode switcher loaded as an app from it, but it still worked.
Cheers guys, hope that helps someone!
Posted 23 January 2005 - 05:07 PM
Posted 24 January 2005 - 12:03 AM
Posted 27 January 2005 - 12:50 AM
The sticky made no mention of a looping Error 21 so my situation was (slightly) different...and I read a couple of other posts in this forum from ppl who were having similar issues to mine and weren't able to resolve them...I realise that what I posted is very similar to what's in the sticky but I thought I'd give a little more detail on the offchance that it was useful to someone, which (apparently judging by Fleck's post) it has been.
Posted 27 January 2005 - 12:53 AM
Yeah, this won't work for softmods unfortunately, I have no experience with them at all!
Posted 28 January 2005 - 12:37 AM
As I said, you found a good fix for those chipers! lol... my other thread got closed when i tried to tell them about it not working on my softmod. but the disk will work on a softmod as long as you can set the settings in Avalaunch to "write -back" to the eeprom. I hope this helps in conjunction with RustAngel's guide.
Posted 28 January 2005 - 11:29 PM
Your thread did not get closed because you said that the disc didn't work on a softmod, it got closed because you did not appreciate the help that was given to you. And for the record, it does work on a softmod, regardless of whatever settings you put in avaluanch.
If you have a virtual eeprom active, then the change will be applied to that, if you do not, then the call to the kernel will not be interrupted and it will write directly to the eeprom. avaluanch bypasses the call to the kernel and writes directly to the eeprom, so i can see why you would think that it didn't work, but it did. this is the whole point of the virtual eeprom, to prevent eeprom misuse and misfunctional softmods
Posted 19 June 2005 - 09:25 PM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users