Category Archives: Gaming Consoles
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
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.
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
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
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.
Some Additional Info as the Christmas Eve Release of iXtreme LT+ v3.0 Nears
With the final testing stage of BenQ and phat Lite-On underway in preparation for the scheduled Christmas Eve release of c4eva’s iXtreme LT+ v3.0, we thought we’d drop some additional bits of info into your Stockings in the form of answers to some recent questions.
Version 3.0 of iXtreme LT+ for BenQ and Lite-On (both phat and slim) does in fact retain support for truncated backups, although it is strongly recommended to use full burns made with a compatible Lite-On iHAS drive flashed with the iXtreme Burner MAX fw. Support for truncated backups, however, remains excluded from Hitachi in its forthcoming 3.0 version.
While abgx360 v1.0.6 remains in progress, the new version of Xbox Backup Creator can be used temporarily as an alternative for injecting the necessary new AP25 topology data files into existing backup ISOs. XBC doesn’t perform the same degree of validation of topology data files, and provides no means to verify their authenticity or correctness, so be very cautious if using files from unknown sources until abgx360 is released. In addition to extracting/injecting AP25 topology data files, the new XBC also works with the existing 0800 v3.0 ripping firmware to dump backup ISOs that include proper topology data from original game discs. At the time of writing, it has yet to be definitively determined whether the new XBC will be released alongside LT v3.0, or if it will be released later. The new abgx360 is still under heavy development, and will release in due time.
Recently, there have been some rumors and bogus info spread by a sad individual that is attempting to trick and confuse people with fake release dates, false info, bogus IRC channels and Facebook accounts (note: we don’t post on Facebook, only Twitter), and mislabeling things as “official” when they are in fact not. We’d like to remind users that the only official sources for news and info from c4eva and the team are here at c4evaSpeaks.com, the #c4e channel on EFNet IRC, the Team-Xecuter, JungleFlasher, and abgx360 websites, as well as reliable news outlets such as Xbox-Scene. Be wary of news or information from other outlets that don’t cite the official #c4e IRC channel or one of the aforementioned sites as the original source.
Here is some further details about the upcoming iXtreme LT+ v3.0, which is now targetted for release sometime after December 6, 2011. Earlier this week, Microsoft’s Major Nelson announced December 6 as the official release date for the final version of its Fall 2011 Dashboard Update. Scheduling LT+ v3.0 for release after this date will allow c4eva and the team a chance to analyze the final update so as to ensure no additional changes to v3.0 are necessary.
With the new iXtreme LT+ v3.0, original game discs will need to be analyzed by Xbox Backup Creator in order to gain disc topology data. This data replaces the need for AP2.5/dae.bin data and enables any AP2.5 challenge to be answered correctly. C4eva noted that the topology data method is very efficient — using only 24kB of space — and extremely accurate. Due to differences between them, each game will require its own individual set of topology data. A risk of backups being detected poses itself if the same topology data is used between two different titles. This risk is mitigated by using abgx360 to make certain that the backup contains the appropriate topology data.
Backups will remain the same layout, but will either need to have the topology data inserted by the new abgx360, or be re-dumped with the new Xbox Backup Creator. C4eva reconfirmed that all current AP2.5-active XGD2 and XGD3 backups with old AP25 replay data are not backward-compatible with iXtreme LT+ v3.0 and will indeed need to be patched or re-dumped and re-burned. Non-AP2.5 titles, however, will remain unchanged and do not require re-burning.
Sign in to Xbox LIVE this Holiday Weekend from Thursday November 24 through Sunday November 27, and get free access to movies, sports, music, online multiplayer gaming and more with Xbox LIVE Gold. After the 27th you’ll need to man up and subscribe…but use and abuse it while it lasts
Don’t have an Xbox 360 yet? Christmas time is nearly here and Santa HAS TO bring you one!! Check out some of the awesome sweet-ass deals below from TakeALot:
- R2,199 - Xbox 360 Slim 4Gb Console
- R2,699 - Xbox 360 Console Slim 250GB + Forza 3 + Crisis 2 Live token + 3 months Live membership
- R3,299 - Xbox 360 Console (4GB Flash Memory) with (Kinect Sensor + Carnival Games)
- R3,299 - Xbox360 250gig Black Console + Gears of War + Forza 2 + PGR + Mass Effect + 2 x Wireless Controllers
A lot has been happening on the PS3 side of things this week, homebrew being released, new updates pushed by awesome devs, but one in particular stands out with all these releases. A few hours ago the famous dev that brought to you the first Custom Firmware and the PL3 and PSFreedom. KaKaRoTo, is now back with a new announcement via his twitter, says that he has jailbroken firmware 3.73. Very good news indeed for those of you who are stuck at 3.73. However like his first CFW release this will not allow for backups or any backup managers to run as this would require LV2 peek/poke to run properly. However, he does state that homebrew will work just fine on his upcoming jailbreak. And more good news to follow up with this. He will be releasing this, once he has perfected it.
It seems that a lot of misunderstanding has been going on about the jailbreak announcement made by KaKaRoTo, with that being said he has updated his blog with what seems to be information about his jailbreak and explanation as to what is to be expected by it. Here it is straight from his blog.
I’ve been flooded with questions on twitter and I’ve read many posts on news sites and I’ve seen some stuff being said on IRC and I thought I needed to clarify a few things…
First of all, I didn’t expect to see my tweet front paged on all ps3 hacking news sites.. although I should have expected it.. but anyways, the “jailbreak” is not ready to be used, at all. I only tweeted that because I was excited having it working and I wanted to share my excitement with everyone. But this is a bit equivalent to the day I released that create_cfw.sh script that created the very first CFW/MFW but it still took a couple of months before a real, easy, multiplatform and fully fledged solution was released : PS3MFW.
We are currently at the same state, I have the proof of concept, it works, but a solution that anyone can use where they just click a button and their PS3 gets jailbroken is still far from ready.
I’ve seen people say (and even write it in their front page news) that I’ll release it in two weeks after I come back from vacation. That is not true and I never said that. What I said was that for the next 2 weeks, the project is on hold until I get back.. but when I get back, then I will continue working on it, and it will then take some more time before it’s ready and released.
Some asked if it’s based on what gitbrew was doing/suggesting or if I used someone else’s exploit or work. No, this solution is my own idea and 100% my own implementation. However, the actual solution for the full jailbreak involves some components on which I will not work, and I expect/hope that someone else will provide the solution for that.
Some speculated it might be what I spoke about back in March which I later said I wasn’t pursuing by lack of motivation.. and yes, you are right. The same hack I had in March is still valid today, I told a few people about it (rms, Mathieulh, an0nym0us, and a couple more), but no one was interested in pursuing it further and actually exploiting that flaw (mainly because it requires a huge amount of work to get a proof of concept working). 10 days ago (I started on the 11th), I got bored and decided to start poking at it again, and yesterday (a lot faster than I thought it would take), I got my first pkg installed on 3.73 firmware.
On twitter, I said “do not update if you are on 3.55″, I said that in response to someone who said he would update. Because of that, people speculated that you need to be on 3.55 first, and then install something before doing the upgrade. No, that’s not it, that would be useless. The purpose of my solution is to jailbreak a ps3 that is already on 3.73 firmware and which had never been jailbroken before. I told people not to update because, first of all, it’s not yet ready, and second of all, the 3.55 firmware gives you a lot more possibilities than what can be achieved on 3.73.
So what is this jailbreak? I won’t say because I don’t want Sony to block it in a firmware update (and yes, they potentially could) before it’s even released (and yes, I will release it when it’s ready). But I will explain this to you : in order to run your homebrew apps, you need two things. First, to be able to install them on the ps3, and second to be able to run it once installed. I did only one of these two things.
Some may say it’s not a real jailbreak, but the way I see it, there are three ‘jails’ on the ps3, I broke the first one which prevents you from installing anything, so now you can install your .pkg, great, but it won’t run, that’s the second jail. The third jail is being able to modify the firmware (peek&poke).
The second jail (running apps) is something that can be done, but it’s not my area of expertise (npdrm algo), so I will not be working on that. I am waiting for someone else to achieve it (some have succeeded but do not wish to release it, at least not for now) then I will release.
The third jail (modifying the firmware) is not possible with my method, this means that you will not have a “CFW”, you will run your homebrew applications and games on an official firmware. This also means that without peek&poke support, none of the backup managers will work. So, again, my solution is piracy-free, and as always, I do not plan on working on a way to enable piracy (or even legal backups).
Overall, the purpose will be to allow people who are on 3.73 firmware to enjoy the homebrew games that were released, to play a bit with Eskiss, and to use Showtime for playing their movies. This should be more than enough for everyone.
Finally, I will conclude by replying to another question I received : Do you accept donations? The answer is yes. I do accept donations but I do not seek them out. I will include a donate button to the bottom of this post, so if anyone wishes to donate, they can do so, however, I want to make it clear that whether or not you donate does not and will not affect in any way, the release, or the progress of the work I’m doing. If you donate, you would do it as a sign of appreciation of my efforts, and not in exchange of any favors or anything crazy like that.
That’s about it I think… If you have any more questions, please refrain from asking them, I get enough as it is already.. I also said everything I needed to say and I don’t want to give any more information than that (for now).
This is only for those that are on 3.73, those that aren’t please remain on 3.55
The recent silent DAE update stopped all AP2.5 / XGD3 backups from booting. Until a solid solution is released, here is a simple workaround.
For this example we are going to use MW3.
1. Get a USB flash drive, At least 1GB in size and format it (FAT)
2. Insert into Xbox and goto memory devices. Select USB and configure it as a storage device.
3. Download the this MW3 Title Update. Click here.
4. Download Horizon (Great game modding app btw – JTAG / Glitchers should be using the crap out of this – you can use other apps but this is my tool of choice). Click here
5. Select Tools > Device Explorer
6. Plug in USB device to PC
7. Device will be detected. Select Inject File
8. Load the the MW3 TU that you downloaded.
9. Connect the USB stick to your Xbox. Restart and boot your MW3 backup.
Notes: You may have to delete the system cache after every time you do a fresh boot of the game. But hey, it works.
You can get other title updates from here: http://www.xbuc.net
iXtreme LT+ v3.0 is on the way! Yesterday, having revealed to the team yesterday an idea for countering the recent dae.bin/AP2.5 update, c4eva has today confirmed that he has in fact completely done away with the need for dae.bin/AP2.5 data. Although it’s early stages, c4eva has successfully completed several tests which validate this new method and classified his solution as the “silver bullet” for AP2.5. Rather than using captured challenge results each time the dae.bin changes, the new method builds a complete set of profile data for each disc and works for all AP2.5 challenges, regardless of how the dae.bin is changed. As a result, the format of backup ISOs will be changing as the AP25 replay sector will no longer be included and the profile data will instead take its place. Though c4eva noted that it will take some development time as it’s not a quick fix, both he and the team will now be putting their full efforts behind bringing this solution to life in the form of new versions of iXtreme LT+, Xbox Backup Creator, and abgx360.