Schtrom360Xtract v2.1

Schtrom released a new version of Schtrom360Xtract, a tool that will allow you to easily dump Xbox/Xbox360 gamedata, extract/patch the Security Sectors and fully prepare the image for burning in 1 step. This new version comes with support to create stealth media discs (xtreme v3.0+):

What's new/fixed (since v2.0):
* now extracts video.iso, pfi.bin and dmi.bin for xtreme 3.0 style images
* also tested with xtreme V3.2
* single extraction of video.iso, pfi.bin, dmi.bin, ss.bin and game.iso supported
* the extraction can be done from original discs, copied discs and image files
* two whole disc extraction methods:
-xtreme 3.0 style (video.iso, pfi.bin, dmi.bin)
-xtreme 2.0 style (blank.iso, no pfi.bin, no dmi.bin)
* injection of video.iso, pfi.bin, dmi.bin, ss.bin and game.iso to an image
* automatic detection of Xbox1 or Xbox360 game discs depending on the size
* stealth checks added for Xbox1 and Xbox360 copied discs and images by acidflash
* DVD-ROM support for USB SH-D162C by acidflash
* It seems to be the best to use blocks of 16 sectors when reading the discs, especially for error corrections on Xbox1 discs this works best

* On error every sector of the failed block (2048 Byte * 16 sectors) is read again before the sector is filled with zeros, this seems to give the similar results as isobuster
* Many functions have been rewritten, now we have functions like MySendCDB to send a variable length command to the device
* I used a lot more MFC CStrings, cause the code get's more readable than with c style strcpy and strcat
* MyExtractSectors is a very huge function, cause we can gain a lot of time in comparison to calling MySendCDB every loop and init all the structs
* The most functions now accept file or device handles, so we don't need to open/close devices and files all the day
* Before the video.iso extraction the cd tray must be ejected and loaded on the original Xbox drive, this is only necessary if the game data is already visible at video extraction start
* The pfi.bin and dmi.bin extracted on the original Xbox drive with xtreme 3.0 has a "four byte left shift" compared to the SH-D162C, so on extraction on the Samsung drive I implemented this shift, thanks to kreon who helped me with the last 4 missing bytes on the samsung and c4e for his immediate response in the forums
* Differences between an SH-D162C xtreme 3 and an Xbox xtreme 3 image:
0xFD8FA00: 69 bytes challenge/response data missing in the security sector of the samsung
* Warning: if you compare Xbox1 images extracted on SH-D162C and TS-H943A you get different results even with isobuster, the SH-D162C seems to have a better error correction and can read sectors the Ts-H943A can't read
* Now I also try to support copied disks, they are checked for valid pfi, dmi and ss data, first I try to extract the data in the usual way (cdb), if this fails I read the sectors where the data resides on a copy, thanks for acidflash and Redline99 for help on checking for valid bytes
9 after extraction every file is checked on valid size

Official-Site: N/A by Schtrom on www.xboxhacker.net