KaosEngineer

It's so much easier to just use Evoxdash to try and flash the TSOP. If the points are not connected, it will report the TSOP flash chip's ID: Manufacturers ID 09 Device ID 00 !!Flash not writeable!! The values 09 00 are the first two bytes of an Xbox BIOS instead of the any Xbox flash memory chip's ID. However, evoxdash cannot flash a Winbond flash memory chip. You need to use raincoat, XBlastOS or Gentoox Loader to flash it. For other brands, as long as the evox.ini file has the proper set of Flash= lines it should be able to ID the flash memory chip once writeable and flash the BIOS to it.

But, you can play them. The mounting of the ISO done by running the default.xbe file (the attach app from NKPather's driveimageutils). Doing so is available for most softmods. NKPatcher added hooks to mount the disc image. For hard mods, you need to add the patches to the BIOS that boots from the modchip. There's an app that does so then chain loads the configured default dashboard after it applies them to the BIOS/Kernel which actually runs from RAM.

Yes, Rocky5's Xbox Softmodding Tool's NKPatcher app has that operation built in. Select it from its menu.

The maximum file size allowed by the FATX filesystem used on the Xbox's hard drive is 4GB's. The game is larger than that so multiple slices, IIRC <filename>.partNN.iso files, are created. NKPatcher's attach app can mount up to 8 of these part files (slices) which look like one disc to the Xbox. What are the names of the files it created?

SmartXX OS is the software that controls the functions of the modchip itself. You still have to flash a modified Xbox BIOS to the modchip. Xbins FTP server is still online. There are also two web sites that have a copy of it available to download using a web browser instead of an FTP client. https://downloads.diodematrix.com/homebrew/xbins/Console Based Applications/bios/SmartXX OS/ The other one is offline due to a problem with their network card and I believe repair efforts have been slowed due to the CORVID-19 pandemic. Modified Xbox BIOS to Use Evolution-X M8plus F and G prepatched dot bin file found on the HeXEn 2018 disc in the bios subfolder or use EVTool v1.0.9 to patch the original M8plus.bin file yourself, save it and flash to the modchip. iND-BiOS 5003 or Feb-11-05 Beta (aka 5004), or X2 5035

You will need to split the XISO file at an even 2,048 byte sector break. DVD sectors store 2,048 bytes of user data. Each file needs to be less than 4096MB's in size. I believe the isoripper included with NKPatcher's driveimageutils actually splits them at 4094MB's instead of 4096MBs to make sure they are less than the FATX filesystem's maximum allowed file size. The XISO can be split into a maximum of 8 parts (slices as called in the image utils source code). IIRC, the set of files need to be named as follows: <filename>.part1.iso <filename>.part2.iso ... up to ... <filename>.part8.iso Or, <filename>.part01.iso, etc. instead. Note: <filename> is the name you give the files. Use the same <filename> for all of the part files. The isoripper application from NKPatcher's driveimageutils generates it from the name of the game disc being ripped or from the disc's TitleID. Its been awhile since I used it to rip a game to recall which was used. Edit: From the source code, the Slice size is set as: /* Slice the ISO into parts this big. Keep it divisible by the sector size 2048. */ #define DEFAULT_ISO_SLICE_SIZE 0xffe00000 A Slice is the maximum size in bytes for any one of the eight (8) part files.

Are these the names of the files or just the folders they are stored in? If only the folders, what are the names of the files in each? Edit: I was editing this message right before you posted the Enter the Matrix.rar file and posted it right after your post

There most likely exists an ACL (Action Control List) for DVD2Xbox to patch the default.xbe file and shorten the long file names so they can be stored on the Xbox's hard drive. The easiest way to run it is from an XISO disc image. If it's over 4GBs, the disc image needs to be split into multiple files that can be mounted by NKPatcher's driveimageutils' attach app. Softmodded console is the easiest to use the XISO dot iso files on but a hard modded console can be made to work with it as well for a limited number of modified BIOSes.

Need to use a different way to obtain that file listing. The XML Filezilla creates for how we did it before has way too much extraneous info included: Use the search option in the text menu to limit the files it lists - path of Enter the Matrix look for *. After the search has finished, copy and paste the list of files it shows in results window (ctrl-A, ctrl-C). Paste (ctrl-V) the copied content into a text editor and save the file.

What?

You can't FTP the extracted XDVDFS file set from the Redump-style archive as there are files with names too long for the FATX filesystem used on the Xbox's hard drive. Filename length of FATX is limited to a total of 42 characters which includes the 4 (dot and 3 letter extension) used by most filenames.

If you have an older *non-Xbox Softmodding Tool* softmod installed, use the contents of the Quick Upgrade.zip archive to upgrade it. It's much smaller than the Extras Disc and only needs to be uploaded to the console using FTP to the E drive as instructed in the archive's *Read Me.txt* file. You'll find in in the Xbox Softmodding Tool repository under the Build v1.1.7 / Installer Variants folder - Quick Upgrade.zip.

The first JST cables I found are not the correct pin spacing. The pin pitch (distance between pins is 1.25 or 1.27mm not 2.54mm (0.1") There are listings for them too on eBay. https://www.ebay.com/itm/US-SELL-10-SETS-3Pin-15cm-Micro-JST-Molex-Picoblade-1-25mm-Male-Female-PCB-Board/272897774450?epid=2171152476&hash=item3f89f99372:g:jJIAAOSwgxxZlnO7 (not exactly what you need as it has the male cable with 3 wires and the mating female through hole connector). The wire length of 15 centimeters (150mm) should be long enough (I believe the originals are ~5 3/4" = 146.05mm). The front panel all black cable connectors have an even narrower pin pitch than most all the other connectors on the X3 modchip. Probably 1mm but I don't have anything to measure them. I used the LPC debug header pin spacing (0.1" pin pitch) to compare the spacing for the 3-wire JST connector. All 3 pins of it fit within the 0.1" spacing between 2 pins of the LPC pin header.

There are a couple of USB programmers. One's a simple one that can flash a very limited set of chips PLCC-32 being one of them but the drivers are not signed and many antivirus programs claim the software for it is a virus. But, it's not from what I can tell. I found something similar to it but can't find the one I mentioned above. On eBay, for US$20.00+ $6.50 standard S&H, Programmer BIOS PLCC-32 (SST49 W49 PM49 W39 82802) The other is the XGECU TL866 II plus which supports 1000's of different chips. (Many different bundles available for a variety of price points; however, all are more than $20 of the first option listed.)

I don't know if it matters but the nfo file states that it is only for X2 5032. This app must have been released before the X2 5035 BIOS.

Since the modchip is directly soldered to the motherboard, the easiest way to fix it is to remove the SST49LF020 from the socket. There's a specialized PLCC-32 extractor tool (US$42.63) made to go under the chip in the rectangular corner slots to pull it up and out. (I use a small flat bladed screw driver and go back and forth between the two corners to carefully pry up one corner then the other until the chip pops out.) Then, use an external programmer capable of flashing an SST49LF020 chip to reflash it with the correct bios's dot bin file.

What made you decide to flash the OLD Evox D.6EjectFix BIOS to the modchip? The latest Evox BIOS version release for a v1.0-1.5 Xbox is M8plus.bin.

With all the information that skin shows, you'd think the author would have included the Kernel version too.

The PC not recognizing it - you mean the operating system - Windows. It does not know how to read an Xbox hard drive. What do you mean by humming/spinning all the time? Can you post a video of it with sound to YouTube? A hard drive does hum and spin all the time. I don't understand what is wrong without hearing and/or seeing the Xbox try to bootup.

M8plus F and G from the Hexen 2018 disc. I'm not sure how the M8plus BIOS on the 2019 disc is configured. iND-BiOS.Beta.Feb-11-05.67.bin - upload the ind-bios.cfg file to the root folder of the C drive before flashing the BIOS to the TSOP. Or, x2_5035_vOld_512k.bin - upload the x2config.ini file to the root folder of the E drive before flashing the BIOS to the TSOP.

Hmm, that may be a problem. I expected it to say TSOP 1MB, ST 49LF080, or something else indicating that XBlastOS recognized the flash memory chip it was going to be re-flashing. Do you have TeamViewer installed on your computer? If not, can you install it? Do you have a Discord account? If so, use ogXbox.com's PM system to send me the account info (userid#number).

Good idea @SS_Dave.

Yes, use the Network flash option. But first, what's printed on the first line of the screen after enter the Flash menu? Flash menu : <text shown here = ???>

The problem can also be caused by trace rot of the eject signal line on the bottom of the motherboard. There are four traces that carry front panel control signals to/from it to the System Management Controller (SMC - a PIC processor on v1.0-1.4 Xboxes) for Power and Eject plus the Red and Green LED drive transistor control signals. Traces in the order seen above, inner most to outer edge of the PCB: Red LED drive transistor control signal from PIC processor pin #2. Green LED drive transistor control signal from PIC processor pin #3. (I may have these two reversed.) Eject signal to PIC processor pin #5. Power signal to PIC processor pin #18.

Move to the right using the D-pad to highlight the Settings icon. Press (A) on the controller to see the Settings menu options. D-pad down to Flash menu and press (A). Post the text you see on the top line of the screen: Flash menu : <what's printed here>