Service Required After Switching To Ntsc And Enabling 1080.
Posted 17 January 2010 - 10:02 AM
1. FTPd the latest build of XBMC on. Worked fine.
2. Copied a shortcut to C: to make XBMC the default dash. Worked fine.
3. Used Enigmah (already installed) to switch to NTSC. Worked fine.
4. Switched to NTSC mode on Microsoft dash, ticking all the boxes labelled 480, 720, 1080, etc. Hit apply.
5. Switched off xbox at power switch.
Since then when I boot into the Microsoft dash, it takes a really long time on the 'Big X' screen then at length I get the "Service required. Call Customer Support." message with the console LED flashing red/green.
Booting to XBMC just does not happen. It basically seems to hang on the 'Big X' screen.
I wondered about overhauling the install using Slayer's EvoX disc, and tried to do so. This may give a clue to diagnose the problem... On bootup, the 'Big X' screen remains for a long time, so long you'd think it has frozen. Slowly you begin to notice that the display has begun to gradually fade into the Slayer's screen. If you wait long enough (and I'm talking 25 mins or so), you have fully faded into the Slayer's screen. I tried selecting a full install, and the same deal... it takes 25 mins to load/fade in each page. I never got to the actual install. It just took too long and I wondered if something else was really wrong.
Have I fried a display adapter or something in switching to HD or NTSC mode? If anyone recognises these symptoms please let me know! I'm happy to find any more info to help as required. Thanks everyone!
Posted 17 January 2010 - 10:48 AM
The xbox should detect that it doesn't has a component out and revert to normal video mode.
If you have the error screen, do you have a number in the upper left corner of the screen?
Posted 17 January 2010 - 01:26 PM
I just tried with the normal AV cable and got the same thing.
On the error screen I have a number 16.
Thanks for the help!
Posted 19 January 2010 - 08:04 AM
see Llamma's Explanation of Error Codes
I would figure that somehow there are files missing that won't allow the $dash to boot correctly. If possible, try a recovery from a Evox boot disc, or the likes. Hope this helps.
Posted 21 January 2010 - 01:08 AM
Thanks for the help phoenixnz. I followed a procedure recommended for fixing up Error Code 16. I used a Slayer disc to unlock a hard drive from an older xbox, put it into the 1.6 and booted up using the mod chip. Then without physically disconnecting the power, I put the 1.6's hdd back in and tried to boot up using a Slayer disc. It still can't do it unfortunately - not even in glacial time like was happening earlier. I'm now getting Error Codes 13 and 14 which are related to dashboard files.
I'm now going to look into an EvoX boot disc as suggested.
Posted 21 January 2010 - 05:56 AM
So... is there enough information here for anyone to offer a diagnosis? What could have gone wrong? Is there something else I could try?
The confusing thing is that I don't think I stuffed around with the dash files too badly. I updated XBMC and only after switching to NTSC and 1080 video did I have trouble booting up a dash.
Posted 26 January 2010 - 08:42 AM
I placed a retail hdd from my other modded xbox in there and it boots up without any problems.
I will be having a look at ways to test the Seagate drive and reinstall on there.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users