KaosEngineer

Read this thread:

Clean the flux off the bridged soldered joints and post a couple of new pictures. Show a larger area around the bridge connection than previously posted.

One of the bridges must not be making all the proper connections if the TSOP is detected as not being write-enabled. A V1.0 Xbox has one bridge on the top and one on the bottom of the motherboard, not two on the top. https://www.biline.ca/xbox_solder.htm Update: Forget what I said. I miss read your soldered locations. You do have one on top and one on the bottom. Are you sure you didn't break a trace on bottom connection? Wait, it's R7D3 to be bridged on the top? Oh, you have that too. Just a different angle. The solder doesn't look too good looks more like a dab of non-conductive grease.

Check the UnleashX Skins Forum for posts about other skins as well.

All the solder on the pin header connections to the LPC Debug port are just sitting on top of the pin not making a connection to the motherboard. The solder should flow into and around each pin inside the thru holes of the motherboard. If it FRAGs with the modchip connected, D0 is grounded forcing the loading of a BIOS from the LPC attached flash memory device on the modchip. However, the BIOS is not loading thus the FRAG. Reflow all of the LPC pin header solder joints to make a good connection to the motherboard not a ball sitting on top of each pin. See: https://learn.adafruit.com/adafruit-guide-excellent-soldering/common-problems

Hmm, not that it should matter as UnleashX's settings are to only be for UnleashX Disable the Enable 480p, 720p and 1080i options. I'm not sure they can be changed when the top line: Video Standard is set to PAL. You might try EnigmaH again, set the Video Standard to NTSC, run the MS dashboard and disable the high resolution modes (you will have to have a high-definition cable connected to see these options to disable them in the video settings), run EnigmaH again to change the video standard back to PAL then try playing a PAL game. It could be a bug in the XDK code that's trying to run a PAL game in high-definition that does not support it. The 480p, 720p, 1080i flags would never be enabled on a standard PAL console as they were not available to use with it.

The video settings in UnleashX only work for UnleashX. They do not change the settings used by the console when running a game. Those settings in the MS dashboard are saved to the configuration EEPROM and do control the mode a game will play in PAL or NTSC.

I'm not sure how often the HTTP (Web browser accessible sites) update the content they make available from the XBINS FTP server. The FTP site is still accessible. Go onto IRC EFNet channel #xbins to obtain login authorization and credentials to access it from your favorite FTP client. Or use the Auto-Xbins 2008 Windows application. It does all the work in the background to gain access and contains an FTP client to download the files available there. (My virus detector doesn't like it - Windows Defender so I have to add it to the allowed exclusions list.)

I see now, HDD Raw Copy Tool writes a hard drive image to either a dot img (Raw image) or imgc (Compressed image) file. A large file to download again. Especially if it is corrupt again. If so, it must be that way from the source.

Many of the old scene releases removed or re-encoded some video/audio files to allow them to fit on a DVD5 disc. I'm not sure if working Blinx 2 you found is larger than 4.7GBs.

What file type is the Origins download? Is it a dot ZIP or RAR? You would need to extract it first. I would think it's just a dot BIN file, not compressed.

First, select the Source FILE then click the Continue >>> button. Next, select the Target device/drive not the FILE and click the Continue >>> button. Next, click Start to copy the SOURCE File to the TARGET drive. Note: Make sure the TARGET drive is the Xbox drive not your computer's OS drive. All data will be wiped out of the TARGET device - overwritten with the SOURCE file content.

Sneaky Team Xecuter didn't do a 1-to-1 connector run: X3 to X3LCD pin number: 1 - 1, 2 - 2, ... 20 - 20 but instead connected: X3 to X3LCD pin numbrs: 1 - 2, 3 - 4, 5 - 6, etc Swapping the top and bottom rows from the X3 to the X3LCD side.

Of that I'm not sure. The project I worked on used the Arduino as the MASTER device all the time. I see the 7-bit's in the address are shifted one bit to the left. The LSB of the byte sent is the Read/Write control bit. A6-7 A5-6 A4-5 A3-4 A2-2 A1-2 A0-1 R/W-0 - Address Byte Bit Usage - Bit position

It could be that the actual address is 1 off of what your Arduino is expecting. I recall something from an old robotics project about the Arduino's address being off by 1. Try to send data to either address 0xe8 or 0xea. I could be completely off here. I've not used an Arduino for several years or have the source to look at the old project notes anymore. Or, do I, ...hmm..., is that dropbox account still active. 0xE9 = 1110 1001 But,... I thought the SMBus/I2C only used 7-bit addressing (128 devices addressable - 0x00-0x7F). Where's 0xE9 fit? See: https://www.totalphase.com/support/articles/200349176-7-bit-8-bit-and-10-bit-I2C-Slave-Addressing

Get the Aladdin installed and hotswap should be no problem. D0 wire from X2.6 to Aladdin's D0 pad.

Download it, extract the archive, Ftp the files to the Xbox to install it and run it! Easy

unknown flash, halting! means the flash memory chip is write protected. It cannot be reflashed while write protected. The first two bytes the flashing software obtains when reading the chip id - manufacturer ID and product ID are 0x09 and 0x00 (the first two bytes of the BIOS) not the chip's ID bytes.

It's 11MB/s (100Mbps). But yes, still slow compared to SATA 6Gbps max.

Do you know that it has the X3 BIOS flashed to the banks on the chip 1-4 or 5-8? You do not have to use the X3 BIOS with this chip. You can't use all the features the chip provides without using it though. The X3 modchip can have any mix of 256KB, 512KB or 1MB BIOS's that fit on evenly divisible bank boundaries: 1MB BIOS's only work when flashed to a group of 4-256KB banks: 1-4 or 5-8 512KB BIOS's only work in 2-256KB banks: 1-2, 3-4, 5-6 or 7-8 256KB BIOS's work in any single 256KB bank: 1, 2, 3, 4, 5, 6, 7 or 8. You cannot overlap 2 different sized BIOS's that would occupy another BIOSes bank(s). ----- Aladdin modchip: You installed one onto the pin header where the X3CE fragged and it to fragged. Double check the pin header soldering for good connections. The X3CE uses all 16 pins and the Aladdin only needs the first 12. Pin 1 is the square pad and the numbering alternates right to left for the odd and even pin numbers. 16 15 14 13 12 11 10 09 08 07 06 05 04 03 02 01<--Square pad LPC Debug Port pinout: http://xboxdevwiki.net/LPC_Debug_Port

With the X3 installed, you should be able to install any empty hard drive and format it using the X3ConfigLive Hard drive tools menu. Then, boot HeXen to build the NTSC or PAL drive (install content to the C and E drives/partitions of the newly formatted drive.) Hexen menu options 3.5.3 or 3.5.4 Update: Hexen can format a drive too. Without one installed I think a BIOS other than X3 will FRAG. They expect a hard drive to be present.

Download the pre-built XBMC4Gamers archive from the link provided in the description of the github.com repository. FTP it to your Xbox and try it. Install it to a different location than the one previously installed by the Extras disc (e.g., F:\Apps\XBMC4Gamers). I've not used the Extras disc to install the app. Do you know where it installed XBMC4Gamers to on the Xbox's hard drive?

If you disable or disconnect the X3 modchip from the memory upgraded motherboard, does it still FRAG? Not sure if you already said that it did or didn't in any previous post. If FRAG'ing, there's a hardware problem. The memory chips must not be connected properly. They are oriented in the correct direction?

A 1.6 Xbox requires a 1.6 BIOS. It will not work with a 1.0-1.5 BIOS flashed to the modchip. A 1.0-1.5 Xbox can boot a 1.6 BIOS; however, it is highly recommended to flash a v1.0-1.5 version of the BIOS instead of using the 1.6 BIOS on them.

You got em all and them someone else got another. Welcome to ogXbox.com. Mod it or lose it, KaosEngineer