Blog
Team Matrix veröffentlicht Freedom Manager V3.0
Montag, den 23. Januar 2012 um 09:58 Uhr
Mit dem Freedom Manager v3.0 veröffentlich das Team Matrix eine neue Revision seiner Software. Mit dieser neuen Version ist iXtreme LT+ 3.0 nun auch auf Freedom PCB´s zu flashen. Ergo lässt sich damit unter anderem das "Silver Bullet" Feature der LT+ 3.0 nutzen.
Somit lassen sich alle XGD3 und AP2.5 Spiele via Topology Data Patch in der ISO problemlos abzpielen. Der Freedom Manger v3.0 befindet sich ab sofort in unserer Download Sektion.
iXtreme LT+ 3.0 für Xbox 360 Slim veröffentlicht
Montag, den 16. Januar 2012 um 16:27 Uhr
Firmware Guro C4Eva meldet sich zurück. Mit der neune iXtreme LT+ 3.0 kommen diesmal alle Besitzer einer XBox360 Slim mit einem Lite On 16D4S Laufwerk auf Ihre Kosten. Somit werden nun folgende LiteOn Laufwerke unterstützt : 0272(9504) /0225 /0225u /0401 / 1071 (Slim). Ebenfalls neu ist der JungleFlasher in der der Version 0.1.92beta. Der neue Flash wird ab sofort in unserem Shop angeboten.
Die Release notes lesen sich wie folgt:
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.
One liteon to go and four Hitachis. Have a great year everyone.
Thanks go to Team Jungle and all testers for their hard work and efforts in the development process.
Thanks also go to Team Xecuter for their support to this project.
Xk3y Firmware 1.20Beta & Remote Update 1.1 veröffentlicht
Freitag, den 06. Januar 2012 um 08:58 Uhr
Das XK3Y Team veröffentlicht ein Update für die Remote des Xkey ,mit dem das Problem mit dem Dauer eingeschalteten Display fixed.
Das ganze funktioniert indem die Remote mit dem PC verbunden wird.
Ebenfalls neu ist die Beta Firmware 1.2.0 Beta für den Xk3y. Beides ab sofort in unserer Download Sektion zu finden.
Die Release notes lesen sich wie folgt:
Firmware update for the remote to solve the "always on" when receiving power in standby mode.
Firmware Updater for xk3y Remote
Contents:
xupper.exe - An old DriveKey tool, we are reusing the bootloader in the remote & this tool can update it.
remote_1_1A.upd - The FW update file
To use:
1. Unpack the rar file
2. Plug your remote into PC, holding down the up & down buttons while plugging in. The display will stay blank and the blue LED will light
3. Run xupper.exe, it should detect the remote and display "Connected: Firmware update mode" and "Updater v 1.3"
4. In the top menu bar select "File | Open", select "Programmer Updates (.upd)" in the file filter and load file "remote_1_1A.upd"
5. In the top menu bar select "Programmer | Update Programmer Firmware" & the update will run, takes about 10 seconds & the display turns on
6. You're done! Disconnect the remote and use as normal.
V1.1
R7 users:
-The remote display will turn on when initially connected (or remain on when the console turns off) for 30 seconds and then turn off.
-When the console is off pressing a button on the remote will cause the display to turn on again for 30 seconds
R6&R7 users:
When the console is turned on the remote display will turn on shortly afterwards.
The remote display will turn off 30 seconds after 30 seconds of inactivity, it will turn back on when a button is pressed.
01.20Beta1 [04/01/12]
Added support for all XGD2 games
Added Ext4 support
ABGX 1.0.6 mit XGD3 Support erschienen
Mittwoch, den 04. Januar 2012 um 11:42 Uhr
Nach langer schöpferischer Pause ist heute das neue ABGX erschienen. Besonderheit an der neuen Revision ist die XGD3 Unterstützung.
Gleichwohl bei dieser Revision weiterhin Version 1.0.2 angezeigt wird, handelt es sich um die Version 1.0.6
Letztere befindet sich ab sofort in unserem Download Bereich.
Die Release notes lesen sich wie folgt :
- 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: 0x00000000" 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
XboX Backup Creaotor 2.9 Build 350
Mittwoch, den 28. Dezember 2011 um 08:46 Uhr
Mit der neuen Ixtreme LT + 3.0 muss jeder wieder seine Origianle neu auslesen mit dem neuen XboX Backup Creaotor 2.9 Build 350, welches bei uns im download Bereich zu finden ist.
Alle XGD3 Spiele und AP25 Spiele die vorher ausgelesen wurden, speziell für die LT + 2.0 werden mit der LT + 3.0 nicht laufen.
Uns ist auch aufgefallen, das es für diverse release auch PPF patche gibt. Diese brauchen nur in das ISO reingepatched zu werden, welches man ggfls. von seinen Original noch auf der HDD rumliegen hat.
Zitat von der Team Xecuter Seite :
1. Making Your Own Rips
When ripping your own discs with the latest Xbox Backup Creator v2.9 Build 350 you should have “processing AP2.5″ unchecked. This adds an extra hour to each game rip and is not required. This option is only used when topology data is being collected for development purposes.
Remember that angle measurements need to be as accurate as possible. If you rip your own you are using just 1 set of measurements. Your laser may be weak or you may have just one measurement out of hundreds that is out of bounds of the accepted values and your disc will error and you will be flagged for an AP2.5 Failure (See point #3)
FYI the accepted values are -/+ 22 (even though originals rarely go above -/+ 2 with a perfect quality laser – the extra is allowed for those that have a poor quality laser)
The median files that are created are the work of HUNDREDS of dumps per game over many different consoles and many different drives. Then using a complex algorithm millions of individual results are then calculated to give the absolute best timing scenario possible. The median files that are provided give a deviation of -/+ 8 (The original target was 9 – so anything below this is considered awesome).
To give you an idea of what we are talking about here is the deviation data when using the median file on an XGD3 title: http://pastebin.com/VSNkwF3m
As you can see the results are superb and rarely go above -/+ 4 with a maximum of 8 in just one instance.
However if you rip your own you may find that some angles will go up to -/+ 100 which is WAY over the -/2 22 threshold and will give you a bad image.
So when ripping your own images, uncheck Process AP2.5, patch with the given median file and then burn. There may be a simple app coded for you to check the deviation values of your own rips in the near future.
Note: The XGD3 Median Topology file covers ALL current XGD3 games. This includes other languages too. There is no need for you to check the profile of your game at this moment in time. if you are 100% certain that the median file does not work with your XGD3 title then you need to rip the original game using the new XBC and test it again. If it then DOES work then you need to report it with the Profile ID of the game and the AP25 topology file (after checking process AP2.5 of course). If you can’t do this then dont bother posting about it.
2. Bogus Median Files
We have noticed that some people have been uploaded bogus median files which are blank. These have been causing errors and making invalid images. Thanks to these assholes, many people have lost time and money.
The official and original download link for the median files is this: http://bit.ly/u6ZaKY
3. AP2.5 Flags & You
If you are flagged for an AP2.5 failure do not panic. This does NOT mean that you are going to get banned. Originals fail all the time due to a poor laser so this should largely be ignored. It’s fair to say that those who have countless failures will probably draw attention more than those with just a few. Take from that what you will. The point to be made is, if you are flagged, it doesn’t really mean shit.
4. Burning XGD3 Titles
When burning XGD3 titles use a Liteon iHAS Burner with the Burnermax firmware and verbatim MKM-001 or MKM-003 discs. There will be no other support or advice given on any other burner or any other media especially truncated versions. If you are too cheap to invest in an $18 burner and media that costs less than $1 then you deserve all the problems that you encounter.
X360key Firmware V1.12 Veröffentlicht
Mittwoch, den 28. Dezember 2011 um 08:40 Uhr
Die Jungs von Xkey haben eine neue Firmware herausgebracht.
es wurden einige klene sachen gefixed.
Allerdings das Highlight bei dem Update ist, das bei dem ASIA Xkey der " Lock " entfernt wurde.
Xkey Homepage :
Seasons Greetings from the xk3y Team. Firmware v1.12 without language restrictions! When xk3y was first launched we produced an OEM version for one of our Chinese partners. This version was locked down to a few Asian language to promote sales in Asia and discourage resellers to export the OEM version to other regions. Sadly, some unscrupulous resellers still sold the OEM version to other regions, leaving end users with xk3y devices that would only display Asian languages on the remote.
We have always stressed that this is an OEM version and not something we support, as we do not offer it for sale. When these issues first surfaced, we discontinued the OEM deal and has since only supplied the standard version. However, in the interest of consumers who have received the OEM version we have decided to remove all language restrictions in the firmware, starting with version 1.12.
- Fixed "Network Fail" Message
- Latest Mr_Waffles Web app
- Asian Language lock removed
- Improved French language strings
- Added more languages
TUR Turkish
Das update ist wie gewohnt bei uns im Download Bereich zu finden.....
iXtreme LT+ 3.0 veröffentlicht C4E is back for christmas
Dienstag, den 27. Dezember 2011 um 12:19 Uhr
Firmware Guru C4E sorgt am heiligen Abend erneut für eine Überraschung. Mit der iXtreme LT+ 3.0 wurde wieder einmal auf die Schnelle auf Microsofts neuestes Dashboard Update reagiert.
In beeindruckender Geschwindigkeit wurden so wieder Haus und Tor gegen diesen Patch geöffnet.
Die release notes lesen sich wie folgt :
C4E’s iXtreme LT+ 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 I devised a way of calculating any challenge which I 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 title topology data is best as there are slight differences between titles and newer titles could have different topology than existing ones.
I would like to wish everyone a merry xmas and a happy new year. I look forward to the challenges ahead.
Thanks go to Team Jungle for their hard work and efforts in the development process.
Thanks also go to Team Xecuter for their support to this project.
Team Matrix kündigt Matrix Glitcher II an
Donnerstag, den 22. Dezember 2011 um 12:08 Uhr
Das bekannte Team Matrix, welches sich mit dem berühmten Modchip Matrix Infinity für die Playstation 2 einen renommierten Namen gemacht hat, meldet sich erneut zurück.
Diesmal allerdings mit einem Modchip namens Matrix Glitcher 360 II der basierend auf den GliGli Hack (Reset Glitch Hack) auf sämtlichen Xbox 360 Konsolen (ausser Xenon) laufen soll.
Neu ist das konfigurierbare Glitch Timing, was für eine bessere Stabilität sorgen dürfte.
Einige Key Features in der Überischt :
- Booten von unsignierten Code auf der Xbox 360 und XBOX 360 Slim
- Kompatibel mit X360 (außer Xenon) und X360 Slim
- Funktioniert mit allen X360 NAND-Programmierern
- Kompatibel mit allen X360 Kernel-Versionen
- Schnelle Installation (7 Drähte zur Slim oder 6 Drähte auf Phat )
- Kompakte Größe der Leiterplatte
- Starten des X360 unsignierten Code innerhalb von max 2 Minuten
- Matrix Design und Qualität
- Budget Preis
Weitere Beiträge...
Seite 1 von 27
