KaosEngineer

Use XBPartitioner's Help feature (press the Back button) to find which button / control is used to change the selected partition's size. If all space is allocated to the partitions you can't use it elsewhere. You must decrease the size of partition 7 (I see partition 8 selected / highlighted, not 7 to make a change) to then reallocate it to partition 6. However, the A button should cycle through the standard LBA48 setup schemes for partitioning the hard drive. All to partition 6, partition 6 up to 137GB / partition 7 takes the remainder, partition 6 up to 137GB / No partition 7 or equally split between partition 6 and 7. While running XBPartitioner from the Hexen 2019 disc depending on the BIOS it uses, you may not be able to make any changes. Copy / install XBPartitioner v1.3 to the hard drive's applications folder, remove the Hexen 2019 DVD, reboot into the replacement dashboard running from off the hard drive and start XBPartitioner v1.3 from there. Update: Is your controller an OEM MS controller or a third party one? Does the Back button not work to bring up XBPartitioner's Help page?

ERROR_PATH_NOT_FOUND 3 (0x3) The system cannot find the path specified. I'm not exactly what path it's trying to write to. If it was the configuration file, config.xml, it was read to set up the menus of the UnleashX dashboard. So, it should not have a problem writing to it. However, I don't recall seeing any such information in that file for screen calibration data. The replacement dashboard must be trying to write it elsewhere; but where? The skins folder, the path to where UnleashX's default.xbe or other named XBE file is running from. Both of those should be known. Update: There should be a UDATA folder present that stores information used by UnleashX. E:\UDATA\9e115330 Did you delete that folder? Is it present on the hard drive? Video calibration data may be in the file: E:\UDATA\93115330\0064122817A8\videoset.dat A 144-byte file on my console.

And, the SMD transistor (Q7C2) between the clock cap and Xyclops chip had 3.3Vdc present on the collector (pin labeled C below). ____ B --| | | |-- C E --| | ------ Updated: Added a better picture of the transistor from the ONSemiconductor datasheet. They are one manufacturer of this part - MMBT4403LT1 (part labeling 2T). Another Xbox Repair Manual states that the replacement part is an MMBT3906LT1 (part labeling 2A). Odd, not sure why it would not power on. Next, check the voltage level present at the PowOn control line of the motherboard PSU connector. Does it go high (3.3 or 5Vdc) when you press the power button and is low (0Vdc) when not pressed?

Thanks for measuring the voltage levels. I guess part of the system does still have 3.3Vdc in standby (while off). MS changed the voltage supply level that runs to pin 6 of the LPC debug port. Pre-1.6 consoles have a switched 5Vdc level while 1.6 versions have a constant 5Vdc present as long as AC power is connected. The 3.3Vdc must still run to the clock circuitry as it did in previous versions of the console. I need to see if I can track down (someday really soon now ) where the 3.3Vdc blue wire runs to on the motherboard.

Error 06 - hard drive cannot be unlocked. From XBOX Error Codes Explained- Go Here First! 6 - kernel - Cannot unlock HDDIf you understand the above, you should be able to understand what this means. It means you are trying to boot up the xbox with an harddisk that is locked in combination with ANOTHER motherboard than you are using it with right now.What can i do about it, you ask? Well place the harddisk back in the xbox where it came from. After that, UNLOCK the harddisk with the same procedure i explained above (see error 5). Now when the harddisk is UNLOCKED, put it in the xbox which gave you the error. Now when you boot up with the chip ON it should not give you an error anymore.However when you put the xbox on with the chip OFF your xbox will give you an error. (error 5) So to make sure you can boot original and boot with the chip ON. Next do the same as above: "Boot up your xbox with the chip on. Preferrably with a slayer evo-x cd. Now you choose "Eeprom management." Than you choose: "Lock hdd." It takes one second. After its ready it should say something like "Done"When it is ready just turn off your xbox. Disable your chip and try to boot original. Now there should be no more error. The wrong HDDKey was used to lock the hard drive for the Xbox you are trying to instsall it in.

Does the eject ring start flashing orange and the fan speed increases to 100%? Those are signs of detected overheating by the System Management Controller in the Xbox.

2T is an MMBT4403LT1G Ic max 600mA 2A is an MMBT3906LT1G Ic max 200mA

Are there any markings on top of the transistor? 2A or 2T Which transistor did you order as a replacement? MMBT3906LT1G or MMBT4403LT1G

The clock cap is a 1F super cap rated at 2.5Vdc. Brand: nichicon The 12Vdc line from the Power Supply Unit (PSU) reads 0.34Vdc or 12 - 0.34Vdc ~= 11.66Vdc. With no load attached to the 12Vdc line, the PSU's protection circuitry may automatically switch that supply level off - thus the 0Vdc reading when only the multimeter is connected to it. You measure 5Vdc at the standby pin on the motherboard's power connector. I think this graphic is in error for the Blue wire (PowOK) in STB (standby) mode. It should read 0Vdc, not 3.3Vdc. The v1.6 Xbox uses 5Vdc for the standby supply level, unlike all the previous vesion PSUs which use 3.3Vdc.

This download is the same application as found in ogXbox.com's download section; however, the files have been extracted from the XISO disc image and all the filler files removed ready to FTP to a subfolder of the Xbox's Apps folder to install it.

AFAIK, the dead zone is automagically adjusted by a particular game if it supports doing so. You can't save it. It's to be done each time a different app is executed.

Check the settings in the ind-bios.cfg file. The LED colors can be set to different colors in it. Also, the replacement dashboard can change the color(s) used when it runs. When running another app, the LED color should again revert to those set by the BIOS/Kernel configuration.

Upload the eeprom.bin backup file from the other Xbox to the current console's Y:\ folder. Use Chimp 261812 to unlock the 500GB drive using the motheboard's data then in the slave menu locking options use the Y:\eeprom.bin file to lock the hard drive for the other console. Remove the 500GB (SLAVE) connected hard drive and install it as MASTER in the other console.

I suggest running the Controller Test Application and see how the A B X Y button presses register in it. You can use Qwix to extract the content of the XISO (dot iso) image and remove all of the filler (dummy) files that are used to fill up a DVD-R disc when burning the app to media. After extraction and filler removal, upload the file set to a subfolder in your Xbox's Apps directory. You may have to rename the XBE file to default.xbe if not already so named so your replacement dashboard will add the Controller Test Application to its menu.

NULing the HDDKey most likely broke them if the saves were created before you NULLed it. Swapping HDDs doesn't affect the use of the save but changing the HDDKey does for those that are signed using it.

I believe the 4 thin traces from outside to inside are: - Power_Button - Eject_Button - Green_LED_Control - Red_LED_Control I may have Red and Green reversed. (more tracing of the signals needed). These LED control signals are raised or lowered to a logic HIGH or LOW by the System Management Controller - PIC processor (v1.0-1.5) or Xyclops chip (v1.6) - and each connects through a resistor (R3V2 and R3V3) to the base of a surface-mount drive transistor (which I believe are PNP MMBT3906LT1Gs at Q2V1 and Q2V2 respectively) located on the bottom of the motherboard near the front panel connector. The collector of Q2V1 through R3V1 and a resistor on top side which then connects to the front panel connector pin number N and M. The collector of Q2V2 through R3V4 and another resistor on top of the PCB to the front panel connector pins X and Y. The emitters of both Q2V1 and Q2V2 are tied to 3.3Vdc. I've not traced out the entire path of these signals as you can tell by the use of N, M, X and Y pin numbers they connect to. Continuing to trace signals below to fill in some of the pin number connections Front Panel Connector Pin Usage - Pin 1 (square pad) - Ground - Pin 2 (below pin 1) - Power_Button (Momentary Normally Open pushbutton) - Pin 3 - Ground - Pin 4 - Eject_Button (Momentary Normally Open pushbutton) - Pin 5 - GREEN_Left_LED to R2G9 to the collector of Q2V1 (???) - Pin 6 - RED_Left_LED to R2G10 to the collector of Q2V2 (???) - Pin 7 - RED_Right_LED to R3V4 to the collector of Q2V2 - Pin 8 - GREEN_Right_LED to R3V1 to collector Q2V1 - Pin 9 - No Connection - Pin 10 - Connector Key - No Pin present It's getting too late for me to try and trace these connections anymore tonight. Q2V1 - green drive transistor Q2V2 - red drive transistor I really need to get both the top and bottom layer images of the v1.1 motherboard combined into two layers of a single image that you can see the through-hole via connections between the top and bottom layers of the motherboard. Image cut from diy.sickmods.net's Hi-res scan of an all parts removed v1.1 motherboard (bottom side): http://web.archive.org/web/20111231000320/http://diy.sickmods.net/Tutorials/Xbox1/Hi-Res_Scans/ This most likely is not going to work but the pins are numbered: 9 7 5 3 1 o o o o o o o o o 1 8 6 4 2 0 It worked, not what I expected. All except for Grammarly messing up the text i quoted from Gorrillasnot.

Not that a picture really matters. The solder needs to be removed to disconnect those three pads from each other. They should not be connected together in any way.

Which softmod is installed?

No, they need to be unbridged. You at least will have a short between ground and 3.3Vdc (LPC pin 9 - 1st pad below BT) and wherever the 2nd pad below BT connects to if you don't unsolder the bridge. Please post a picture of the bridged connections. Update: I think, not 100% sure though, I tracked down the signal on the corner pad (2nd down) from BT = Ground. It's not good to have 3.3Vdc (first pad down) and ground (second pad down) tied together when you power on the Xbox.

There are game exploit packages that run a TSOP BIOS flasher program instead of installing a softmod. When you boot the game and load the exploit save, it flashes the TSOP, as long as you've bridged the write enable points beforehand. NMS TSOP Flasher 2.0.rar (there is a 3.0 version but the site that hosted it recently went offline - eurasia.nu ) Hacky Rehash TSOP Flash Exploit v1.0 or Highway '007mech Flash Pack.rar. It too was developed and hosted on eurasia.nu but I found an xbins copy. I'm not sure if it is the latest release though. These three seem to be popular. The second, Hacky Rehash, is the latest released on 20100316. There are many other TSOP flashing exploit packages that use the raincoat flashing application.

Whoa, I missed this post ages ago. Changing the version of UnleashX will not delete any files on your System. How is the console modded? Where is UnleashX running from? Press Y and scroll down to the Path and Phy. Location entries. What values are shown for them? UnleashX 0.39.0528A Build 584 is the latest. UnleashX 0.38.0222A Build 572 is the next to next latest bug-free FTP server/client operation version. Rocky5 has a hex edit patched version of the 584 build that gets around some of the bugs especially the FTP client root folder listing bug of the official release. Official Releases: http://the-eye.eu/public/xbins/XBOX/Console Based Applications/apps/dashboards/UnleashX/UnleashX_0_39_0528A.rar http://the-eye.eu/public/xbins/XBOX/Console Based Applications/apps/dashboards/UnleashX/UnleashX_0_39_0222A.rar Rocky5 Patched 0.39.0528A Build 584: https://github.com/Rocky5/Xbox-Softmodding-Tool/raw/master/Extras Disc/Softmod/dashboards/UnleashX.zip

The screensaver is separate from the skin. It is not tied to any changes made to the skin. You'll have to set UnleashX Settings to use a different screen saver. Go to System -> Settings :: System Page :: Screen Saver Section :: Video File to set the path.

Here are 10 that I like. A few have Red, Green and Blue variations. Check other threads in the UnleashX Skins forum, there are links to other skins inside some of the posts there. Here are a few more:

Check the location where the music and sound files are being loaded from in UnleashX's System -> Settings -> System: Sound and Audio page. Maybe they are no installed on the hard drive at the associated paths for each sound. I'd add the skin to the default skins folder too. Press the Y button when on a menu to show the System Info Page. Scroll down to find the Path and Phy. Location where UnleashX is running from. The Skins folder should be created at that location.

Welcome to ogXbox.com from the end of the world! Too bad parts aren't readily available where you live. A 220V PSU for a 1.6 console is required. Older models won't work in a v1.6 console so make sure it is a v1.6 compatible power supply when you do find one.