Search the Community

The silicone wire is rated for 200 C and the Kynar is rated for 105 C. What is best for soldering traces, modchip lpc etc... What is your experience when using one or the other?

How to fix the 4 screens bug when patching to 720p in OGXHD

I've started to list the game's I've gotten this error with, alongside what method I was using to store them on my HDD Some would outright lock up the whole system. Any idea how I could fix this? If it matters, I'm using Cerbios 2.3.1 UDMA5 on a 1.0 System with a 2TB HDD, obviously with a SATA2IDE adapter. 007 - Everything or Nothing (US, Folder, Stuck on black screen) Psyvarier 2 - Extend Edition (JP, Folder (same results with CCI), Dirty/Damaged Disc) Guilty Gear X2 Reload (US, Folder, Dirty/Damaged Disc) Alien Hominid (EU, Folder, Stuck on a loading screen) Burnout 3 - Takedown (US, Folder, Stuck on a loading screen) Dead Man's Hand (US, Folder, Stuck on a loading screen) Doom 3 (US, Folder, Crashes on start screen) Doom 3 - Resurrection of Evil (US, Folder, Crashes on start screen)

I installed a LCD screen (SPI2Par2019 + HD44780 LCD). I have a Xenium. When the screensaver starts the text on the LCD screen disappears and I have to go to settings/LCD/ Enable LCD/VFD and change the value back to anything (well, in my case LCD - HD44780) for the text to re display on the screen...the value of LCD/VFD doesn't matter as far as getting the text back; it's the process of changing it to anything that brings it back. Is this a known issue? What's the fix? I've edited the LCD.xml w/ the suggested edit on ryzee119 spi2par2019 github

As the title says.. Console only outputs AV when I push down on the chip. If I push down on the chip I can boot to dash and use the console without issue... If I don't, the console doesn't frag or anything it powers up and by the sounds its making it seems that it is actually booting to the dash still, but just without outputting any AV.... I have reflowed the soldering on the pin header a couple of times and it made no difference. Anyone have any ideas? Console DOES frag if I remove the chip and unground the D0. Thats another issue though lol

Okay, firstly this is not a problem with Rocky's code per se, it's a problem with the XBMC code going back 18 years when the issue first appeared. I did flag it at the time and a few other softmod users on the forums (XBMC and Xbox-scene) did too. Full debug logs were provided but Gemini's dev Xbox was messed up after a RAM replacement so he couldn't test it. I ended up fixing it myself and did so into 2010 until I switched fully over to Xbox 360 and PS3. I've only recently started using my Xbox again to discover the bug still exists in new XBMC iterations. This bug only affects softmods patching kernels from the Conexant and Focus video encoder machines. So if you have a 1.6 (Xcalibur encoder) this won't affect you as Rocky has added some code which makes v1.6's work perfect with Cherry's eeprom-safe video-mode patch code on a softmodded 1.6 (it never used to). The code for the pre v1.6 kernels seems to screw up after a soft reboot. Also the bug doesn't affect using BFM bioses on a softmod, or if you compiled NKPatcher to do a 'full reboot' rather than a 'reboot to dash'. Here's how to reproduce the bug: Make sure sure you have enabled 'Enable video mode switching' in the XBMC4Gamers menu as we're going to boot at 50hz only game on an NTSC machine (or PAL machine set to NTSC) and vice versa ( a PAL machine booting an NTSC game), then repeat the boot process. Leave the 'For 60hz games' setting to 'Use NTSC-M & NTSC-J'. On an NTSC machine navigate to a 50hz only game (like Sensible Soccer 2006, SCAR or one of those Club Football games) and press 'white'. Make sure it it says 'Launch PAL' (if not select 'Launch in..', then select PAL). The game will launch fine in 576i. Now do an IGR back to dash. Now try to launch the game again (or any other 50hz only game). It will display a black screen and a rapidly expanding log file in XBMC that reads something like this (debug): 22:01:19 M: 44838912 NOTICE: Unmapped drive D 22:01:19 M: 44838912 NOTICE: Mapping drive D to Harddisk0\Partition6\Games\Scar - Squadra Corse Alfa Romeo (Pal) 22:01:19 M: 44838912 INFO: Mounting Harddisk0\Partition6\Games\Scar - Squadra Corse Alfa Romeo (Pal) as D: 22:01:19 M: 44838912 INFO: Launching xbe:d:\default.xbe 22:01:19 M: 44838912 DEBUG: Forcing video mode: 3 22:01:19 M: 44847104 ERROR: exception in CApplication::FrameMove() 22:01:19 M: 44847104 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist 22:01:19 M: 44847104 NOTICE: unload sections 22:01:19 M: 44847104 NOTICE: application stopped... 22:01:19 M: 44847104 NOTICE: Running the application... 22:01:19 M: 44847104 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist 22:01:19 M: 44847104 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist 22:01:19 M: 44847104 NOTICE: unload sections 22:01:19 M: 44847104 NOTICE: application stopped... 22:01:19 M: 44847104 NOTICE: Running the application... etc.. etc... (constantly looping) You have to power off and run the game from a fresh boot. To test the bug on a PAL machine (not a PAL machine set to NTSC) booting an NTSC game, again make sure you have enabled 'Enable video mode switching' in the menu. Select an NTSC only version of a game. We'll use the US version of Halo.. Navigate to the game and press 'white'. Make sure it it says 'Launch NTSC' (if not select 'Launch in..', then select NTSC). The game will launch fine. Now do an IGR back to dash. Now try to launch Halo again (or any other NTSC game). It will display a black screen and again a rapidly expanding log file: 20:41:33 M: 48623616 NOTICE: Unmapped drive D 20:41:33 M: 48623616 NOTICE: Mapping drive D to Harddisk0\Partition6\Games\Halo Combat Evolved (Usa) 20:41:33 M: 48623616 INFO: Mounting Harddisk0\Partition6\Games\Halo Combat Evolved (Usa) as D: 20:41:33 M: 48623616 INFO: Launching xbe:d:\default.xbe 20:41:33 M: 48623616 DEBUG: Forcing video mode: 1 20:41:33 M: 48652288 ERROR: exception in CApplication::FrameMove() 20:41:33 M: 48652288 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist 20:41:33 M: 48652288 NOTICE: unload sections 20:41:33 M: 48652288 NOTICE: application stopped... 20:41:33 M: 48652288 NOTICE: Running the application... 20:41:33 M: 48652288 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist 20:41:33 M: 48652288 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist 20:41:33 M: 48652288 NOTICE: unload sections 20:41:33 M: 48652288 NOTICE: application stopped... 20:41:33 M: 48652288 NOTICE: Running the application... etc.. etc... (constantly looping) Same process using US/NTSC version of Broken Sword on a PAL machine, but testing PAL-60 instead. Works first boot, then after soft reset and loading the game again, black screen: 20:47:25 M: 47874048 NOTICE: Unmapped drive D 20:47:25 M: 47874048 NOTICE: Mapping drive D to Harddisk0\Partition6\Games\Broken Sword - The Sleeping Dragon (Usa) 20:47:25 M: 47874048 INFO: Mounting Harddisk0\Partition6\Games\Broken Sword - The Sleeping Dragon (Usa) as D: 20:47:25 M: 47874048 INFO: Launching xbe:d:\default.xbe 20:47:25 M: 47874048 DEBUG: Forcing video mode: 4 20:47:25 M: 47882240 ERROR: exception in CApplication::FrameMove() 20:47:25 M: 47882240 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist 20:47:25 M: 47882240 NOTICE: unload sections 20:47:25 M: 47882240 NOTICE: application stopped... 20:47:25 M: 47882240 NOTICE: Running the application... 20:47:25 M: 47882240 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist 20:47:25 M: 47882240 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist 20:47:25 M: 47882240 NOTICE: unload sections 20:47:25 M: 47882240 NOTICE: application stopped... 20:47:25 M: 47882240 NOTICE: Running the application... etc.. etc... (constantly looping) The current ways to negate this are: After you've run one PAL 50hz game (or pure NTSC game for PAL users) and rebooted back to dash, do a 'Reboot' from the XBMC4Gamers options menu (black button). Now the game will work fine. Another way is to recompile your NKPatcher like so: %define IGR ; %define IGR_TO_DASHBOARD %define IGR_FULL_REBOOT ; %define IGR_MASTER_PORT 0 Bear in mind this will auto detach any ISO you may have mounted when you do an In-Game-reset, so you won't be able to browse any mounted virtual discs. Also, this method means each IGR does a full reboot, so it will take longer to get back into XBMC4Gamers. Or you can use the linked xbe which fixes these issues on pre v1.6 kernels. I modified and compiled from Rocky's latest sources for his v2.0.004 release. Just overwrite the 'default.xbe' in the XBMC4Gamers folder and power cycle your Xbox (you need to power cycle as XBMC caches itself to a virtual drive). XBMC4Gamers 2.0.004 default.xbe fix

Is UnleashX purposely restarting when attempting to add icons to the Xbox games list, or is there a potential issue with the software causing this behavior?

Thanks to SS_Dave I put the OEM dash file on the Xbox to try and boot to there from UnleashX. However when I try to run it I get Error 21. I think it got messed up by whoever soft modded the console before I bought it (it had been sitting in that shop for a few years), but even then I did a clean UnleashX install with Rocky5's tool. I'm pretty confused on what to do. Will I need to put in Halo 2 or something with XBL to update the OEM dash, and then reinstall UnleashX using the Splinter Cell exploit?

I acquired a 1.4 that had been TSOP'd at some point with a 120gb HDD. Something is buggy with the TSOP that I can't update or change the BIOS so I put it a Open Xenium that I had here. It powers on as it should and works normally except when I try to reboot it. It'll power up green at first and then start flashing red with no video. I'm assuming it's needing the caps replaced, although the 3 in front of the CPU & GPU seemed to have been replaced already as they are different than the rest (blue with gold stripe & writing). Any other suggestions before I start replacing all the caps?

Hey guys so anyways, I was trying to install addons for xbmc4xbox, but when it tries to install the add on, it gives me a error, the error says “Error - Install Impossible” idk what to do about it so can you help me please?

I received a broken 2001 1.0 Xbox for free. I removed the clock capacitor, rerouted some trace rot. After that, it seemed to be working great besides terrible disc reading (even after a pot tweak). I ignored the often suggested thermal paste replacement thinking "don't fix what ain't broke" and bought a new laser, after all, I got the thing for free. It's working great as far as I can tell. BUT the lingering thought of thermal paste wormed it's way into my brain, after all, most people seem to suggest it (sometimes to do it just cuz). The combination of so many people suggesting it, and some of the counter-arguments to it on this forum made me pretty anxious about the whole ordeal. Especially after investing money into this. SO when does one know when, or if they should change the paste? I basically have the oldest OG Xbox possible, and it seems to work fine. I noticed the fan area in the back can get warmish when reading discs - but I've never had an xbox, and this could be normal. I haven't modded it, so I don't know its temps. Should I be worried? or bothered? Should I mod the console just to see the temps, just to be sure? Is the Xbox good enough at knowing when it has overheated to reliably leave it alone until theres a tangible issue? TLDR; I'm overly paranoid about my newly acquired 1.0 xbox, and don't know how necessary it is, or when I should replace the thermal paste. Thanks for any replies! It's much appreciated.

I am currently setting up a brand new HDD (6TB) with Cerbios and using CCI's. As the full set contains a LOT of games I want to split them alphabetically.. However the folder art that I have created displays but disappears when scrolling. This only happens when "Enable Resources" is on. If I disable resources then the folder art will stay in place and not disappear. See video for example. https://1drv.ms/v/s!AqFpyG7Ugkl6gv8sPcUgOjpVrGKH3g?e=R4jyZ2https://1drv.ms/v/s!AqFpyG7Ugkl6gv8sPcUgOjpVrGKH3g?e=R4jyZ2 I have the folder artwork placed inside the folder root, along with the game folders for that letter. I have tried naming the art folder.jpg,icon.jpg and poster.jpg, same result each time. Have even tried having a _resources folder with the artwork in (which failed completely as it just showed as another folder. Obviously I want resources enabled. So my question is does anyone know how I can change this behaviour?? @Rocky5 If you're here, do you have a suggestion from your huge wealth of XBMC knowledge? Also anyway I can use folders AND keep fast game parsing on? Thanks in advance to anyone who can help me out here...

Hey guys so anyways, when I try to transfer xbmc4xbox via my windows 11 laptop, it gives me an error. The error says something about 255 or something like that, so how do I get rid of this error? PS: my Xbox IP address is configured on the laptop btw.

Hi I have an issue with another xbox of mine. when I want to save changes in xblast it only shows the background and does not reboot, but changing in the menu does work/ fan speed does change exepte it does not wanna keep it. I testet 3 chips and all have the same issue. this Xbox had a leaked clock cap and two traces where rotten but everything else works fine. example: Gruß Hero

I can see that the laser module has problems going up all the way as well. The drive tray catches on the spindle when trying to eject and then tries to close back up but the laser module and thus the gearing isn't cycling all the way and so the drive ends up popping back out and catching on the spindle again. I probably need to remove the drive tray to even start this, But where should I be checking to see why the laser module isn't dropping all the way to allow the drive tray to clear? Edit: The laser module IS dropping all the way. I can see that the tray is lowered all the way in this white piece of plastic that slides over when the tray starts to open. I can see that the black tab is all the way at the bottom of the slope in the mechanism. Why would the spindle still be sticking up too far? The tray looks straight... But the rear of the tray is still catching on the spindle. I cannot visually understand what is happening. Anyone seen this before? I may just cut away the plastic that's catching on the spindle and see if the laser module raises to the correct height when closed. The Xbox has never been opened before me so I have no idea what it possibly could have been that changed. I just tried to open the drive fully and I manuevered the rear of the tray past the module... and the laser just tried to read a disc with the tray all the way out... WTF? That spindle looks a bit high for resting position when fully closed.

My in January repaired 1.4 Xbox console is dead today, it didn't turn on Both the power and eject button does nothing. It played fine a week ago. I opened it up, disconnected the PSU from the mainboard and used a multimeter to check the voltage between the grey pin and ground according to the diagram below (Delta PSU). It only jumps to 0,05-0,1v when it's connected to a power outlet. It gives no 3,3v. Does it mean the PSU is dead and not easily fixable?

Sorry, but I have to annoy you again... I once again bought a cheap ogxbox at a flea market. So far so good. Unfortunately, the box now has an error that I've never had before... and I don't know how to fix it either... When I turn on the box, the box starts to "pump". The LEDs flash alternately. go off and then on again. Fan stops and starts again, screen is black, hard drive is clicking and turning. After 5 - 10 seconds, the box is stable, the fan is running, but the LEDs continue to flash in all colors. Despite this, no error code is displayed even after a long period of time. When I press the eject button now, the DVD doesn't respond at all. If I then start the box via the eject button, the error pattern is the same at the beginning, but then the DVD is opened and the box then boots normally. Then I can even turn off the box completely and turn it on normally. Everything works as it should. If the box was switched off again for some time, the problem starts all over again. The box is a version 1.4 with TSOP patch, but the box also has the same quirks with modchip and original MS BIOS. I've changed pretty much everything that can be changed. IDE cable, yellow DVD cable, DVD ROM, hard disk, power supply unit ... the CPU/GPU cooling paste has also been renewed and the clock capacitor has been removed ... I don't see any signs of wear on the board, and the capacitors still look good... As always, any help or hint is appreciated... Cheers and Thanks

Hi Guys I am new here and have soft modded my og xbox and installed XBMC4Gamers dash, however some games are just not being recognized by the dash. I have tried so many different solutions, such as copying from different flash drives, hdd.....etc, nothing helped. When ripping the games from a disc, they work fine, and most work ok after copy, but some just show these weird names as you can see in the screenshot. Xbox is running a 1TB hdd, for those games that wont work, artwork installer just marks them as being corrupt. Has anyone else had this issue, any help would be greatly appreciated. Thank you!

I've a Xbox with 1.4 board, softmodded with Rocky5's Xbox Softmodding Tool. It doesn't have the clock capacitor anymore. The console was working for a while until for some moment the power button doesn't respond to turn on the console and needed to use the eject button for it. And it automatically boot up when you shut it down in software or when the power cord was plugged out and back in. But all this only happen when the console is warm (=when played games for a while). If it's cold, the power button works fine. I thought it was the trace corrosion mentioned on the forum, but I took the board out to have a look on it and the traces seem to look fine, no corrosion. After I put it back together the problem still exist and even getting worse: when it's cold everything works fine, but after playing a game for about 30min it will shutdown itself and the power button problem returns. And when restarted with the eject button, sometimes it keeps working for some minutes but most of the time it shuts down after some seconds, just before or right after the dashboard is loaded. But if I let is rest for some hours, everything will get back working for some (short) time. What can be the cause of these "trace corrosion"-like symptoms, but only when the console is warm/played some games?

lynx crashing when injecting files

chimp clones to new HDD with out problems but i get error 16 when i put in the new drive after cloning. i tried the 'fix error 16' button in chimp, it said it was good but when i put back in the new HDD i still get Error 16. The stock 10GB HDD i got with the xbox still works if i connect it. i then tired booting the xbox with the 10GB HDD then turning off the xbox and putting in the new HDD but then i got error 13. plz help i already spent like 70$$ on this shit. my xbox is soft modded i removed the clock capacitor i have a compatible HDD, 40-pin/80-wire IDE cables, a working SATA to IDE converter Thank you

I could play almost every game I've tried, if one of them behaved incorrectly I downloaded an other version and eventually it was perfect. But not with this game... I tried many different version, and all of them giving me the exact result.I start the game, and the black screen remains, even my monitor lose the signal coming from the xbox. The xbox is not turning off, it keeps running. I tried playing it from the HDD. Is this one of those games that can only be played from DVD? Or its something with uncommon copy protection, like Fight Club?

Spent the last few weeks modding the thing and just noticed this Besides from trace rot (which I don't have the skills or time to fix), could it be anything else I can try? It happens even with the AV cable disconnected, so it's not that short circuiting. Thanks heaps guys.

For some reason when I turn on the Xbox I am greeted with the error code 05 (unlocked hard drive). But I thought an unlocked hard drive was usable with a mod chip installed? - Re-soldered the wires from the D0 point, BT point mod chip flashed red, BT is joined to the mod chip so it is always on. Despite all of this the Xbox boots up displaying the error code 05. and no sign of the chip working its magic. Thanks, Pez.

I'm very new to the modding scene. I'm using pretty cheap Component cables but everything looks and sounds fine in 480i. I've tried using MS dash to enable the settings but it seems to have no effect. It stays ON in MS even after reboot but there's no change. Once I enable any of the HD settings in UnleashX and reboot, I hear everything but no video outputs. I've tried each one 1 at a time and just 2 and all 3. Same result, no video output. For info, It's a v1.6 with an Aladdin XT, I Added 2Tb HDD. Unlocked. And it's NTSC. Am I missing something simple or could this be bad cables or motherboard issue? Every guide I've seen makes it look so simple. When I plug in my composite cable it will automatically reboot and I don't have the option to enable or disable HD. I can't set it to default with composite cables. The only way I can undo it is by listening the audio and going through the menu blind and changing it back with my component cable. Which isn't that difficult. I can't find this specific issue here so if it exists I'd be happy to read the thread. Thank you.