Tag Archives: flash xbox 360
iXtreme LT+ v3.0 for 0272/0225/0401/1071 Slim Liteons
Official release of the iXtreme LT+ v3.0 for 0272/0225/0401/1071 slim Liteons
- Support for topology data on AP25 enabled titles. Will correctly answer any ap25 challenge eliminating need for dae.bin to create a backup.
- No need to make new backups everytime dae.bin is updated on console
- Extra support for rare firmwares
Topology Data
When ap25 was first introduced I devised a way of calculating any challenge which I called the silver bullet which I made reference to along time ago.
This was withheld until it was absolutely necessary. It was easier to replay the fixed challenges.
With unique per console ap25 challenges it has become necessary to use the silver bullet.
A series of measurements are taken across the disk. This topology data is then used to calculate a response to any ap25 challenge.
It is very important that the drive used to create the topology data is reliable at reading discs as bad topology data equals bad ap25 responses.
Liteon drives using 0800 v3 seem to be more accurate for this purpose. Only ap25 enabled titles require topology data. Activation of ap25 on older non-ap25 games although technically possible is highly unlikely.
Currently topology data for xgd3 titles are similar and topology data from one xgd3 title will pass on another xgd3 title although this is not advisable.
Per title title topology data is best as there are slight differences between titles and newer titles could have different topology than existing ones.
abgx360 v1.0.6 Released
Changes affecting all platforms:
- XGD3 support.
- Replaced AP25 replay sector support with support for topology data (for consoles which do AP25 checks — make sure you have LT+ v3.0 or later).
- Added “Min Kernel Required” (to boot the game) when checking an XEX.
- Added improvements to AutoUpload (used by uploaders) including extended C/R for SS (using the original disc) to make sure files uploaded to the database have very accurate angle measurements.
- Added optional command line argument “–speed” for setting drive speed when checking a burned DVD. Example: “–speed 12″ will attempt to set the drive speed to 12x. You can try to set any speed you like, but setting a speed higher than what your media supports may cause read errors if the drive’s firmware doesn’t govern it. “–speed 0″ will set the drive’s default speed.
- Added optional command line argument “–showsstable” for when you want to see the SS C/R data but you still prefer medium or low verbosity. The SS C/R table has also been updated with “Mod?” being split into “Tol” (response tolerance) for the CCRT entry and “Mod” (response modifier) for the drive entry, also “Pad?” has been renamed to “Typ” (type). Thanks Redline99!
- Added vendor specific additional info and bus type when displaying optical drive names (bus type displayed on Windows only).
- Updated the list of optical drive sense code errors.
- Updated the game ratings definitions.
- Fixed a bug which negated the ability to recover from a write error when rebuilding an ISO using the low disk space method. It’s unlikely that a write error would be recovered on subsequent retries, but at least now it will write the data in the correct place if it does recover.
- Fixed a bug which caused “Unknown Media: 0×00000000″ to be displayed if the “Secure Virtual Optical Device” media flag was set and the “XGD2 Media Only” image flag was not set (The “XGD2 Media Only” flag has also been renamed to “Original Media Only” in abgx360 since they are using the same flag for XGD3).
- The archaic caution message about angle 359 was removed, but you are still able to “fix” it if you still have iXtreme < v1.4 (really old and not suitable for XBL anyway).
- Ability to “extract entire video partition (253 MB)” was removed; this doesn’t make sense for XGD3 and isn’t even very useful for XGD2 since it was just including a bunch of padding data that isn’t even part of the real video partition… it was only needed for very old methods of concatenating with stealth files and a game partition to make a working backup.
Note: The way video is checked/fixed is now a little different for both XGD2 and XGD3. The previous way was to check/fix both L0 video and L1 video off of L0, and then to check/fix “SplitVid” (L1 video on L1) afterwards by comparing it to L1 video on L0. Since XGD3 has no room for L1 video on L0, and to keep things consistent, video will now always be checked/fixed according to L0 on L0 and L1 on L1, and the “SplitVid” check is now gone (nominally). The only effective difference is that L1 video on L0 is no longer checked, but this is not a problem… it’s not even supposed to be there and it’s not visible to the host console when using a “safe” custom firmware. You can rest assured that only old and unsafe custom firmwares will read L1 video from L0; newer ones will read it properly from L1 (this is necessary in order to replicate the read/seek performance of an original disc).
There is also a big annoying yellow message if you have “Check/Fix Video padding” enabled and you check an XGD2 game with L1 video on L0 (or any data in that area). To make the message go away you will need to either add command line option “–pL0″ to confirm that you want to blank it out (XGD2 ISOs without L1 video on L0 will appear to have bad video data when checked with older versions of abgx360), or you can simply disable “Check/Fix Video padding”, as it still makes no difference in terms of stealth… this option only exists as a way to make sure ISOs are “clean”, with no extra data in areas that aren’t CRC checked. Note that this version of abgx360 doesn’t care about L1 video on L0… it will pad L0 video with zeroes whenever video is autofixed or manually patched.
Sorry if the command line options are annoying (you can add them under the “Misc” tab of the GUI), but you can be sure that an improved v1.1.0 GUI is in the works…
Note: The GUI has not been changed and will still display version 1.0.2, don’t worry about it as long as the CLI app displays v1.0.6
Download from www.abgx360.net or download abgx360 1.0.6 here
Patch and Play XGD3 Game Backups LT+ 3.0
Tool Needed:
1. Xbox Backup Creator v2.9 Build:0345
2. AP25 Topology Data (See Below)
Patching Current Games:
1. Until the new ABGX is released, games cannot be burned as they traditionally were.
2. Instead We will be using Xbox Backup Creator to inject the new Topology data for your games.
Follow These Steps:
1. Open Xbox Backup Creator v2.9.
2. Click on the Image Tools tab.
3. Change the Action from Extract to Inject.
4. Hit AP25 Sector.
5. Select the ISO you want to Patch. Then Select the corresponding AP25 Patch that you downloaded.
Master Topology Files:
http://www.xbox360iso.com/individual-xgd3-ap2-t536386.html (Need to register)
Thanks to kill_seth for his tutorial 
Source: http://www.xboxmb.com
iXtreme LT+ v3.0 for BenQ and Phat Liteons
C4Evas iXtreme LT+ 3.0 in association with Team Jungle & Team Xecuter
- Official release of the iXtreme LT+ v3.0 for BenQ and phat Liteons
- Support for topology data on AP25 enabled titles. Will correctly answer any ap25 challenge eliminating need for dae.bin to create a backup.
- No need to make new backups everytime dae.bin is updated on console
- Topology Data
When ap25 was first introduced C4Eva devised a way of calculating any challenge which he called the silver bullet which I made reference to a long time ago. This was withheld until it was absolutely necessary. It was easier to replay the fixed challenges. With unique per console ap25 challenges it has become necessary to use the silver bullet. A series of measurements are taken across the disk. This topology data is then used to calculate a response to any ap25 challenge. It is very important that the drive used to create the topology data is reliable at reading discs as bad topology data equals bad ap25 responses. Liteon drives using 0800 v3 seem to be more accurate for this purpose. Only ap25 enabled titles require topology data. Activation of ap25 on older non-ap25 games although technically possible is highly unlikely.
Currently topology data for xgd3 titles are similar and topology data from one xgd3 title will pass on another xgd3 title although this is not advisable. Per title topology data is best as there are slight differences between titles and newer titles could have different topology than existing ones.
If you are using the latest dashboard and your xdg3 game backups are not working any more, you will need to get it flashed with LT+ 3.0.
How to Copy XDG3 Xbox 360 Games
***INSTRUCTIONS FOR BURNING XGD3 BACKUPS WITH IMGBURN v.2.5.6.0
http://nickthegr33k.eu/XGD3burn.pdf
INSTRUCTIONS FOR BURNING XGD3 BACKUPS WITH IMGBURN v.2.5.5.0
We recommended that you use the latest version of ImgBurn (v2.5.5.0 at the time of writing, downloadable at http://www.imgburn.com/index.php?act=download). Older versions may handle this process differently and/or give a different set of errors.
Although it is set by default in ImgBurn, please ensure that under Tools > Settings > Write, you have “Layer Break (For DL Media)” set to “Calculate Optimal”.
Please ensure that the layerbreak is set as 2133520 in the .dvd file. If you already have the XGD2 (or other) layerbreak value set in ImgBurn, the .dvd of the XGD3 ISO will override that setting and use the proper layerbreak.
As mentioned above, ImgBurn will automatically reposition/limit the layerbreak to 2086912 when burning to regular DVD+R DL discs.
Step by Step:
- Choose “Write image file to disc”, and after loading the .dvd file, click “Write”.
- ImgBurn will pop up a notice saying that there is not enough space on the disc to burn the image, and asks if you would like to continue anyway. Click “Yes”.
- Another message might pop up saying that optimal layerbreak position exceeds L0 capacity. Click “Yes”.
- An error will then pop up noting that “Set L0 Data Zone Capacity Failed”. Click “Continue”.
- The image will begin writing to the disc.
- Nearing the end of the write process, ImgBurn will pop up an error at around 97% or 98% (this is what we want — it’s intentional!). Click “Cancel”.
- A notice will then pop up asking if you would like ImgBurn to try and perform the “‘Close Track/Session/Disc’ functions”. Click “Yes”.
- Let the disc finalize, and you’re done!
INSTRUCTION FOR BURNING XGD3 BACKUPS WITH GROWISOFS
truncate –size=8547991552 xgd3game.iso
growisofs -use-the-force-luke=dao -use-the-force-luke=break:2086912
-dvd-compat -speed=4 -Z /dev/dvd=xgd3game.iso
XGD3 BACKUPS OVERVIEW
To end the confusion once and for all, *yes*, original XGD3 discs have a higher linear/track density and therefore a higher physical capacity than XGD2 and regular DVD+R DL media. As a result, XGD3 ISO backups are larger as well.
For XGD3 backup support, c4eva has introduced in LT+ v2.0 the LT-MAX feature, which allows for XGD3 backups to use the maximum possible layerbreak for regular DVD+R DL media, and therefore all of the available space (8,547,991,552 bytes) of a regular DVD+R DL disc.
Since there is still not enough space on a regular DVD+R DL disc to hold the entire XGD3 game partition, not to mention the Layer 1 Video partition, this is not at all recommended as being “safe” for Xbox LIVE.
XGD3 backups will still boot and play fine on LT+ v2.0 as long as the last approximately 1.7% of the game partition does not contain any of the actual game assets, which it usually won’t because the end of the game partition is near the inner edge of the disc, and developers will try to keep their game data near the outer edge (middle of the game partition) to maximize read performance.
Another necessary condition to booting and playing XGD3 backups on regular DVD+R DL media is that the kernel or game code itself must not perform any CIV (Content Integrity Verification) checks on any part of this last approximately 1.7% of the game partition (or at least it must not take any action after CIV failures). Even if there are no actual game assets in this area, there is still pseudo-random padding data which can be checked through CIV, and such checks can even be added later to the game code through title updates, or to the kernel through system updates.
Just like XGD2, XGD3 backups still require the correct dashboard version-specific AP2.5 replay data. As they’ve done previously, MS has the ability to change the DAE.bin by way of a system update, meaning you may need to re-patch/re-burn at some point. The abgx360 application and database will be updated accordingly to support XGD3.
BEST PRACTICES AND SETTINGS
The P2P XGD3 ISO rips that were floating around before this point are for ODDEs and are not compatible as-is with LT+ v2.0. Their PFI, DMI and SS sectors are in the wrong PSN (Physical Sector Number) locations and they are missing the critical AP2.5 replay sector and SS replay table. If you intend to play XGD3 backups on a firmware- flashed 360, it’s up to you to make sure you’re using proper ISOs made with 0800 v3.0, and to double-check by running them through abgx360 before burning.
Keep in mind that this is the first of several potential disc-based backup solutions for XGD3. As such, it’s recommened that all subsequent releases maintain the full ISO size and associated layerbreak (2133520) in the .dvd, which will help to ensure that they will be forward-compatible should any media manufacturers step up with new larger-capacity discs (which will be necessary in order to make XGD3 backups as safe as possible on Xbox LIVE).
The actual layerbreak for XGD3 ISOs is 2133520. However, when burning XGD3 ISOs to regular DVD+R DL, ImgBurn will automatically reposition/ limit the layerbreak to 2086912 in accordance with the disc’s maximum Layer 0 data zone capacity (2,086,912 [LBA: 0 - 2086911]). The LT-MAX feature in LT+ v2.0 will compensate for this and allow you to play XGD3 backups with this wrong layerbreak, and therefore wrong game partition data PSN locations.
In the case of growisofs as instructed below, in order to avoid errors when burning XGD3 to regular DVD+R DL, you may choose to first truncate the ISO to 8,547,991,552 bytes, and burn using a reduced associated layerbreak of 2086912. This should give you exactly the same end result as if you followed the instructions below for ImgBurn on Windows.
Sourced from RROD-GOW3.NFO
Latest Xbox 360 Update Disables Flashed Drive
All Xbox 360 LIVE gamers should have the latest dashboard update as of 20 May 2011. Mine took 3 shut downs to install and there are some pretty awesome things in it. (see related article) One of the “free gifts” you won’t notice right away unless you own a flashed DVD drive is that those have been crippled. You will no longer be able to play burned games.
The new dashboard update features the new XDG3 format, the flashed DVD firmware installed on the drive will revert back to its original stock DVD firmware making it unable to read pirated games. There are reports circulating around the internet that pirates can still flash it again but there are risks now of Microsoft detecting it right away.
Arrgh! Shiver me timbers Batman, looks like a pirate needs safer waters.
If yours is updated and reverted back to stock and you want to play you game backups again, let me flash it for you. Check out my link here.
