Xbox LIVE System Update 13146 (2.0.13XXX) May 2011 FAQ
Xbox LIVE System Update 13146 (2.0.13XXX) May 2011 FAQ
Published byX_Splinter on 2011-06-02 Category: Xbox Live | Page Views: 10287
Introduction
The Xbox 360 System Update 2.0.13XXX was released to the public by Microsoft in May 2011 in the form of a worldwide mandatory dashboard update.
This update has the particularity of flashing the firmware of your DVD Drive to a new stock firmware which may or may not be to fight piracy. This update was intended to make the xbox 360 ready for the new Xbox Game Disc format (XGD3) that will be used in future game titles releasing later in 2011. It also changes the AP2.5 challenges.
The way people with modded consoles should proceed are:
1. Don't update.(Until a game forces you)
2. If you really want to update, flash to old stock OFW before updating, preferably with the original drive model.
3. If you've updated already, don't flash back to current CFW. Wait for LT+ 1.9 or 2.0
4. Phat Hitachis aren't being flashed during the update so you'll still have old CFW after the update. XBL detectable status: unknown.
FAQ
Some drives are flashed during the update process. This is overwriting current drive firmware, whether it is custom or original. This is the reason why all backups are failing to boot for some people after the update, because the drive no longer has CFW. Re-flashing back to current CFW (detectable) will allow current backups to start working again, except for the 6 known AP25-active titles which have a new challenge set in 13140-6. Existing backups of these games with current genuine AP25 patches won't boot if you have an AP25-supported drive.
Slim Lite-On 0225 and 0401 and all Hitachi drives are not being flashed.
Where can I get the new OFW flash files?
The new full 256 KB OFW flash files for Slim Lite-On 9504, Phat BenQ and Phat Lite-On drives can be found in the official 13146 System Update. Open the su20076000_00000000 file and extract the appropriate $flash_oddupd.xex file for your drive with wxPirs (mirror). Then extract the FIRMWARE.bin file with XeXtractor or XexTool.
Samsung drives are updated with files from $install_extender.xex which contains 4 smaller patches rather than full fw files: ms25p1f9, ms25p2f9, ms28p1f9, ms28p2f9. Each patch is 48.4 KB and makes some changes in parts of the firmware. Therefore you must obtain the new OFW dumped from an actual Samsung drive. dragoscojan's ms28 drive was patched with ms28p2f9 with the 13141 beta update in early April. If you have a Samsung dump from a 13146 update please PM me.
I've updated to 1314x and my drive has been flashed to new OFW, can I flash my drive back to LT+ 1.1 to play backups?
Yes, but only if you're not concerned about being flagged or XBL banned.
So flashing back to LT+ 1.1 is detectable?
Yes. Custom firmware is designed to imitate OFW as close as possible so the console cannot detect it. LT+ 1.1 is based on old stock OFW so it imitates old stock OFW. Updated 1314x consoles are expecting to be communicating with a drive with new OFW. This is the first time in the console's history that drives are being officially flashed so when a drive is flashed to new OFW you should treat it like a "brand new drive model". And typically when a new drive model appears it often requires a new custom firmware version.
I'm not going to risk flashing back to current CFW. So how can I play backups with my newly updated console?
Wait for LT+ 1.9 which is based on new OFW.
Can I install the update with the drive disconnected?
No.
Is the drive key in the keyvault/drive changed or zeroed during the update?
No.
I have updated to the new OFW. How can I obtain and inject my drive key?
Older versions of JF do not recognise the new OFW fw versions. Use JF 0.1.83 or later. You can also try Electon^-'s e-Tool.
I have a non-JTAGable console with no drive key. Can I install this update so that maybe the drive key in the keyvault will be inserted back into the drive during the flashing process?
No. The update will start to run but you'll get an error message code like 3151-3355-1600-xxxx-xxxx-xxxx and the entire update will fail. If you flash one of the full new OFWs (any or no key) to the drive first then run the System Update the dash will be updated leaving the drive alone and the key won't be inserted. This way you can update consoles without known drive keys to 13140 and later.
My drive is flashed with CFW and the new System Update is failing to install. How can I install it?
Regardless of what drive you have, you should flash to old stock OFW before updating. If you have CFW the update will fail for some drives:
If you have retail dash 12625 or earlier:
For some CFW drives (Samsung, slim Lite-On), the new update will fail to install. You need to flash the drive to stock OFW before the update can proceed.
"Defosho", "dragoscojan", "elmsnapesta", "kryno 696" and "Electon^-" take credits in this FAQ
Terminator: Survivors confirmed for Xbox Series, PS5 & PC via Steam Play as a survivor in the aftermath of Judgment Day in Terminator: Survivors, a new open-world survival game by NACON (@Nacon). Build the resistance and defy the machines in Terminator: Survivors, com..
HQ Network: 10,572 | 
Guests: 6655 |
Members: 0
Printer Friendly Page
X_Splinter on 2011-06-02
