KaosEngineer

It's not the password that's NULL'd (32 0's) but the HDDKey used along with other information read from the HDD that the BIOS computes the HDD locking/unlocking password. As the algorithm now uses the same seed (HDDKey) for any NULL'd console which was unique before NULLing. The computed password for the HDD used on any NULL'd console will be the same for that particular HDD. A different drive will have a different computed password as it's model and serial number are unique to that HDD.

Any game that came out after Halo 2 also contains the dashboard updater to MS dashboard version 5960. If that's the version already installed it won't do anything but return to the game's menu.

Get it by downloading from mediafire or mega links posted in the first post of this thread .

It may or may not be flashable in the Xbox. Some cheapmod designs could be while others not so but could be reflashed externally. What kernel/BIOS version is it booting? Which replacement dashboard is it currently running? Update: Looks like this modchip should be reflashable in the Xbox as the SST49LF020's pins 7 (WP#) and 8 (TBL#) that write protect sectors in the flash from being reprogrammed when low (grounded) are tied to 3.3Vdc (HIGH) which disables write protection.

The Xbox's always-on standby power supply is 3.3Vdc on all versions except the 1.6's where it is 5Vdc.

The X3 modchip can have other BIOS's flashed to it and you can selectively boot one of them from the X3 Config Live menu. When powering on the Xbox, hold the white button until the X3 Config Live menu appears and use the BIOS menu to select a different bank to boot one of the supported BIOS's. P.S. I use M8plus BIOS myself. I've not tested the iND-BiOS 5003, X2 4981 or X2 5035 BIOSes..

Which dashboard are you now running? Does it show the same kernel version as before?

Nice, I found the manual for the AID 3.0 disc but not the image to burn to media. It lists the BIOSes included. Evox's M8 and M8plus are based on the MS kernel version 5838 and thus the BIOS shows that kernel version. The AID 3.0 disc had several different versions of the M8/M8plus BIOS available: EvoX M8 EvoX M8 Stealth 137 GB+ EvoX M8 v1.6 EvoX M8 1.6 Stealth 137 GB+ EvoX M8 Plus EvoX M8 Plus Stealth 137 GB+ EvoX M8 Plus v1.6 EvoX M8 Plus v1.6 Stealth 137 GB+ It should be one of these. BIOS Version Naming Convention Notes: Stealth = Boots F Partition before C. Ejectfix = The DVD Tray will not reset the Xbox when opened. 137 GB+ = Support for G Partition. A must use if you have a 120 gb+ HDD.

Evolution-X +3935 is the dashboard. The BIOS must be an old one. I've not seen one before your screenshot that showed AID 3.0 underneath the big-X logo. Do you have a full screenshot of the Evox dashboard? Does it show the kernel version?

Here's documentation on how to do it with XBMC4Xbox - Using Trainers - same should apply when using the XBMC4Gamers skin..

I think, the XISO's will take less space in the long run than extracting the files/folders from them. Any file less than the cluster size will take a full cluster to store on the HDD - 32KB or 64KB for large extended partitions. (Update: Long filenames are not problem as a DVD disc image is mounted that doesn't have the FATX filename length limitation. The mounted image looks like a DVD disc is loaded. Also for games larger than 4GB's in size, the max size of a single file allowed in FATX, the ripper splits the image into multiple files <4GB each that are mounted as one larger than 4GB disc for those games that require it.) You'll need the NKPatcher driveimageutils-v1.0.1 archive which contains an attach and detach XBE as well as an Xbox XISORipper app to create the XISO images from original discs. It rips the disc image and includes the default.xbe (attach app with the game's name set as it's XBE Title). And, the CDROM modchip archive. (Update: Not really needed as I've attached a pre-compiled patcher below named evoxdash.xbe.) As most modchip BIOS's are set to boot evoxdash.xbe as the first xbe in the boot order, name the XISO patcher - evoxdash.xbe - and rename your current default dashboard that's already named evoxdash.xbe to evox.xbe. Here's my precompiled XISO patcher XBE named evoxdash.xbe (Size: 10,232 bytes, SHA-1: 7E486314DE185FB68B274FC52843E751C03C52B9) It chain loads evox.xbe after patching the in-memory BIOS routines to be able to mount/run the XISO images with the NKPatcher driveimageutils' attach app - default.xbe. You either use the ripper to create the XISO image and it adds the attach app into the game's name rip subfolder in your Games folder on F (or G if you edit the ripper's config file) for the game's XISO (dot iso file) or add the default.xbe attach app if you already have the ISO in a subfolder. However, if you do it this way, you'll need to edit the attacher's, default.xbe, XBE Title to see the game name in the menu. (Use XBMC or UnleashX's File manager to change the XBE Title.) Works with the following BIOS/Kernel versions: 3944, 4034, 4817, 5101, 5530, 5713, 5838 and Evox M8plus (it's kernel version is 5838 so duh). Update - sorry the above list is not quite right (the source file's comments had not been updated to match the actual code): 3944, 4034, 4817, 4981, 5003, 5035, 5101, 5530, 5713, and 5838. Modchip BIOSes: X2 4981, iND-BiOS 5003, X2 5035 and M8plus are supported. P.S. If you don't boot a bank flashed with a supported BIOS, the patcher will still load your default dashboard (C:\evox.xbe) without applying the patches to an unsupported kernel version.

If you boot HeXEn, press the Y button to see UnleashX's System Info page. Scroll down to the Kernel Version value, what is it? Any color mod, etc to a BIOS will change the MD5 hash making it hard to determine exactly which BIOS you are running. Evox BIOS has a purple EvoX shield in the upper left hand corner of the flubber animation and X2 BIOS's replaced the text below the big-X logo at the end of the animation with Xecuter Rox My Box instead of Microsoft.

Is your Xbox already modded? If not, the easiest way to mod it is softmodding. To Get Started You'll need the following items: 1. Xbox controller port to USB female cable or other such adapter to connect a USB flash drive to the Xbox controller port 2. Xbox compatible USB flash drive device <=4GB in size. Plug it into the adapter and see if the Xbox will recognized and format it. Note: All data on the flash drive will be lost. 3. Original game disc for one of the following games: Splinter Cell - original or platinum hits release MechAssault - original only, not platinum hits 007 Agent Under Fire - original or the correct platinum hits version that's not patched Tony Hawks Pro Skater 4 - any version 4. Rocky5's Xbox Softmodding Tool

I don't think the X2 4974 actually has any LBA48 patch installed or can have for that matter. You'll need to reflash your modchip with a newer BIOS that does. X2 5035, X2 4981, X2 4983, Evox M8plus, iND-BiOS 5003 or iND-BiOS Beta (aka 5004). Any BIOS that has a .67 and .06 version use the .67 version even if you plan to use only partition 6.

Yes, if you are booting one of the supported BIOSes.

Play them by mounting the ISO. Mod it or lose it, KaosEngineer

The ISORipper included with the driveimageutils rips the image into multiple ISO parts that fit within FATX's 4GB max file size limit. The ISORipper app also creates the attach default.xbe with the game name from the game's default.xbe file. The attach app will mount multiple parts of the disc image as one disc to the system. From driveimageutils-v1.0.1.zip 's readme.txt: ISO image ripper / CD&DVD ripper Insert a game disc into the drive and run the utility. There's no display output or sound or anything but just wait. For example, ripping a 6.7 GB game will take about 40 minutes on my Xbox. After ripping, the utility returns to the dashboard and you should be able to see the game in your games list. The ISO image will be ripped to f:\games or g:\games depending on free space. These directories can be changed by editing backup.cfg. In addition to the .iso files, a default.xbe will also be created. This is the virtual disc attacher utility. The title name is automatically copied from the game d:\default.xbe. The same attacher file is included in the component directory of this package. and Virtual disc attacher This is the file automatically created by the ISO backup utility and is also contained in component\attach.xbe. When this xbe is run it will attach all files with a .iso extension in the same directory in alphabetical order using an nkpatcher 8 system call. In case there are several .iso files in the directory, these are assumed to be parts of the same big ISO file. Since Xbox FATX file system has a file size limitation of 4 GB, big ISO files need to be sliced into smaller parts. The ISO backup utility will do this automatically. After attachment, this program will quick reboot the system. If the attached ISO image contains a default.xbe in its root directory, the kernel will execute it as is usual. Running the attacher on game ISO images will, therefore, launch the game.

Softmodded or hardmodded system? Did you use Chimp 261812 clone the old to new HDD? Either way, you can FTP the stock MSDash 5960 file set to the Xbox's C drive. You just need the 5960 files to do so. Xbox Softmodding Tools Extras disc or Hexen 2018 StockFiles folder has them.

Not quite. NKPatcher softmodded systems like those modded with Rocky5's Xbox Softmodding Tool can use the driveimageutils v1.0.1 attacher default. xbe file to mount the XISO-format ISO disc image to play the game. Upload the dot ISO file and the attacher default.xbe file to a folder in your Games path, reboot and play the game. You'll need to edit the XBE Title to see the correct name in the menu. UnleashX and XBMC4Xbox's file manager can edit an XBE's internally stored Title. See: https://imgur.com/9CbLEL for UnleashX For those with a modchip installed, there's also a CDROM Modchip patcher to run before your dashboard to allow you to use the same driveimageutils attacher method. Update: the drive image util's attacher mounts the disk image so it looks to the console as if a DVD disk is loaded in the DVD drive. On a softmodded system, there's also a detach app to unmount the disk image after using IGR to return to the dashboard. After detaching, you can use the DVD drive again to load discs. For hardmodded systems, power cycle the system to unmount the image.

The HDDKey stored on each Xbox console was unique. After NULLing the console's HDDKey, it no longer is unique to each console (32 0's) but the same HDDKey (actually you could use any value as long as you set them the same on all your consoles to easily swap drives between them). The HDD password generated will then be unique for each different HDD used, but not for each different console too.

At the top of XBPartitioner v1.3, the LBA48 patch version will be printed. What version is it? What kernel version are you running? Press the Y button at UnleashX's menu to display the System Info page. Scroll down to find the Kernel Version. The BIOS will need to be updated. A version compatible with your motherboard version will need to be used. There are v1.0-1.5 and 1.6/1.6(b) versions. The latest Xecuter BIOSes for X2 modchips are X2 5035 (512KB) or X2 4981.67 or X2 4983.67. There are other dev team BIOS's that you can use as well. Evolution-X's M8plus for all motherboard versions are available or iND-BiOS 5003 or 5004 for v1.0-1.5 MBs.

It's not the HDD lock password that's all zeroes but the HDDKey used to generate the password. The password is still unique to each HDD that is installed; however, since part of the algorithm's parameters are all 0's, the computed password for every NULL'd HDDKey Xbox will be the same for the particular HDD used. The Xbox computes the password using the HDDKey and information from each different HDD (model/serial number) every time the Xbox boots to unlock it. Softmodded systems still use the stock MS BIOS thus the HDD must be locked as the password is still computed to do so.

For a 1TB HDD, I think splitting it is better. Update: Not everyone agrees with me - @Forlorn Penguin - I see said to use only F. When split equally between F and G, the cluster size is 32KB instead of 64KB. The cluster size is the minimum size a file will occupy on the HDD. So, if the app has many small files (<cluster size), each file will use up 1 cluster of the available HDD storage space. 32KB cluster max partition size 512GB 64KB cluster max partition size 1,024GB (1TB).

What's the other console doing or not doing?

Works similar to Virtual CD/DVD software on a PC, It mounts the disc image to the D: drive so to the Xbox it thinks a DVD is loaded into the drive. The disc image can be split into multiple files to and mounted as one large image as the Xbox's FATX filesystem only allows for files to be 4GBs in size and a couple games go over that limit in 1 file. There's also a disc ripper included in the package that creates the image file(s). I think it places the mounting app's default.xbe into the folder with the image and may change the internal XBE Title to match that of the extracted game's default.xbe. The XBE title string is the text seen in a menu entry.