Editing Downgrade BluRay Playback Issue
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
=PS3 BLU-RAY PLAYBACK PROHIBITED ROOT CAUSE ANALYSIS= | |||
==Introduction== | |||
Many users have experienced the loss of blu-ray playback on the PS3 after performing a system firmware downgrade to a previous version. Little was known about the cause of this prohibition early on, but this document will outline the causes and effects. | |||
==Overview== | |||
By the end of this document you will know the issue, the causes, and what is affected. | By the end of this document you will know the issue, the causes, and what is affected. | ||
==Reproducing Issue== | |||
To reproduce the issue a few pre-requisites must be met: | To reproduce the issue a few pre-requisites must be met: | ||
===Pre-requisites for Issue=== | |||
#Service JIG device | #Service JIG device | ||
##PSGrade | ##PSGrade | ||
| Line 42: | Line 26: | ||
##3.41 modified version in the DGF.rar is not recommended but is not at issue | ##3.41 modified version in the DGF.rar is not recommended but is not at issue | ||
#PS3 with large NAND (fat models CECHA-CECHG) | #PS3 with large NAND (fat models CECHA-CECHG) | ||
##Keep in mind there are CECHG systems with small | ##Keep in mind there are CECHG systems with small NAND non-volatile memory that rely on HDD volatile memory for dev_flash3 and are unaffected | ||
#USB flash device | #USB flash device | ||
##Any freshly-formatted (BLANK) usb-based flash drive can be utilized | ##Any freshly-formatted (BLANK) usb-based flash drive can be utilized | ||
| Line 48: | Line 32: | ||
===Steps to Reproduce Issue=== | |||
Steps required to reproduce the issue is the same methodology used to downgrade. | Steps required to reproduce the issue is the same methodology used to downgrade. | ||
| Line 98: | Line 82: | ||
===Analyzing UPDATE_LOG.TXT=== | |||
An analysis of the UPDATE_LOG.TXT follows: | An analysis of the UPDATE_LOG.TXT follows: | ||
| Line 291: | Line 275: | ||
==Restoring Service== | |||
:There are two different methods of restoring service as it was from backup, real backup, and derived backup. The two methods only differ in the origination of the backup files to be utilized, both methods ultimately will utilize the same files. | :There are two different methods of restoring service as it was from backup, real backup, and derived backup. The two methods only differ in the origination of the backup files to be utilized, both methods ultimately will utilize the same files. | ||
| Line 307: | Line 291: | ||
==Fixing== | |||
With the root cause of the issue understood, potential methods of fixing the issue can be brain stormed and the original source of the issue can be outright blamed. | With the root cause of the issue understood, potential methods of fixing the issue can be brain stormed and the original source of the issue can be outright blamed. | ||
| Line 324: | Line 308: | ||
##Enter Factory Service Mode and insert the BluRay Movie Title. It should now get recognized and you can leave FSM again. | ##Enter Factory Service Mode and insert the BluRay Movie Title. It should now get recognized and you can leave FSM again. | ||
=== DRL Tools === | |||
[ | [http://www.ps3devwiki.com/files/devtools/DRLtools/DRLtools_0.90.rar DRLtools_0.90.rar] | ||
The tools in the suite are: | The tools in the suite are: | ||
* [ | * [http://www.ps3devwiki.com/files/devtools/DRLtools/DRLtools_0.90/DRLbackup_PS3_0.90.pkg DRLbackup_PS3_0.90.pkg] (used to backup DRL1 / DRL2 files to a USB drive) | ||
* [ | * [http://www.ps3devwiki.com/files/devtools/DRLtools/DRLtools_0.90/DRLgen_WIN_setup_0.90.exe DRLgen_WIN_setup_0.90.exe] (Windows .net 2.0 application to derive DRL1 / DRL2 files from an MKB_RO.inf file) | ||
* [ | * [http://www.ps3devwiki.com/files/devtools/DRLtools/DRLtools_0.90/DRLcopy_PS3_0.90.pkg DRLcopy_PS3_0.90.pkg] (to restore previously backed-up DRL1 / DRL2 files or to copy derived DRL1 / DRL2 files from DRLgen) | ||
DRLGen Source: <span style="text-decoration: line-through;">[http://www.multiupload.com/QX8EDV4NTC DRLGen.rar (4.53 MB)]</span> | DRLGen Source: <span style="text-decoration: line-through;">[http://www.multiupload.com/QX8EDV4NTC DRLGen.rar (4.53 MB)]</span> | ||
==== How it works ==== | |||
Each Blu-Ray movie contains a Media Key Block (MKB) as part of its copy protection scheme. Newer movies feature higher MKBs; the latest one is MKB v20. Addtionally, each BD movie has a unique encrypted title key. Both are stored inside the AACS/MKB_RO.inf file of each disc. Fixing BD playback requires exact knowledge of which was the first instance of the highest MKB played so far. DRLgen can be used to identify the Blu-Ray movie with the highest MKB, and then create replacement DRL1/2 files for your PS3 which then restore BD playback. | Each Blu-Ray movie contains a Media Key Block (MKB) as part of its copy protection scheme. Newer movies feature higher MKBs; the latest one is MKB v20. Addtionally, each BD movie has a unique encrypted title key. Both are stored inside the AACS/MKB_RO.inf file of each disc. Fixing BD playback requires exact knowledge of which was the first instance of the highest MKB played so far. DRLgen can be used to identify the Blu-Ray movie with the highest MKB, and then create replacement DRL1/2 files for your PS3 which then restore BD playback. | ||
==== Requirements ==== | |||
# A means to access Blu-Ray title discs to gather the AACS/MKB_RO.inf file, a Blu-Ray drive in a Mac / Windows PC makes the process easiest. Alternatively, SAK v1.0 can be installed as an OtherOS on the PS3 with firmware 3.15 or lower to accomplish this task. | # A means to access Blu-Ray title discs to gather the AACS/MKB_RO.inf file, a Blu-Ray drive in a Mac / Windows PC makes the process easiest. Alternatively, SAK v1.0 can be installed as an OtherOS on the PS3 with firmware 3.15 or lower to accomplish this task. | ||
# Explicit knowledge of EVERY blu-ray title the blu-ray drive has played and the MKB versions of those discs. WARNING: While you can safely check every BD's MKB with DRLgen, you should limit the number of attempts of installing DRLs on the PS3, as the full details of the AACS "traitor tracking system" are not well known. | # Explicit knowledge of EVERY blu-ray title the blu-ray drive has played and the MKB versions of those discs. WARNING: While you can safely check every BD's MKB with DRLgen, you should limit the number of attempts of installing DRLs on the PS3, as the full details of the AACS "traitor tracking system" are not well known. | ||
# A FAT32 USB storage device to store and retrieve MKB_RO.inf and DRL files. | # A FAT32 USB storage device to store and retrieve MKB_RO.inf and DRL files. | ||
==== Detailed instructions ==== | |||
Full instructions are(sic: was?) available on the Project #PS3bluray wiki http://ps3bluray.info/?title=DRLtools | Full instructions are(sic: was?) available on the Project #PS3bluray wiki http://ps3bluray.info/?title=DRLtools | ||
==== About the tools ==== | |||
=====DRLgen===== | |||
DRLgen is a new and SAFER utility that uses the MKB_RO.inf from a Blu-Ray disc to derive correctly formatted DRL1 and DRL2 files easily every time. No difficult hex editing or byte-counting is involved. It is important to note that DRLgen uses the AACS' specification for the MKB format and does not simply assume DRL records start at a specific position and are of a specific length. The previously leaked information makes all these assumptions and is flat out INCORRECT in many situations today, and is NOT future proof and could lead to permanently broken playback. | DRLgen is a new and SAFER utility that uses the MKB_RO.inf from a Blu-Ray disc to derive correctly formatted DRL1 and DRL2 files easily every time. No difficult hex editing or byte-counting is involved. It is important to note that DRLgen uses the AACS' specification for the MKB format and does not simply assume DRL records start at a specific position and are of a specific length. The previously leaked information makes all these assumptions and is flat out INCORRECT in many situations today, and is NOT future proof and could lead to permanently broken playback. | ||
=====DRLbackup===== | |||
DRLbackup previously released, has been updated to work in cooperation with the other two tools. As a best practice, a backup of the DRL1 / DRL2 files should be made prior to any system downgrade. Use in conjunction with DRLcopy for a completely recreatable process to downgrade your Large NAND PS3 and restore Blu-Ray playback in the future. | DRLbackup previously released, has been updated to work in cooperation with the other two tools. As a best practice, a backup of the DRL1 / DRL2 files should be made prior to any system downgrade. Use in conjunction with DRLcopy for a completely recreatable process to downgrade your Large NAND PS3 and restore Blu-Ray playback in the future. | ||
Note: The location of saved files has changed, users of the older version of the tool should place their saved DRL files into a 'PS3bluray' folder in the root of the USB storage device for compatability with the new DRLcopy tool. | Note: The location of saved files has changed, users of the older version of the tool should place their saved DRL files into a 'PS3bluray' folder in the root of the USB storage device for compatability with the new DRLcopy tool. | ||
=====DRLcopy===== | |||
DRLcopy is a new PS3 tool that uses the output of the new version of DRLbackup (or properly located DRL backups from the previous version) and/or the derived DRL files from DRLgen to restore your blu-ray functionality after a firmware downgrade. | DRLcopy is a new PS3 tool that uses the output of the new version of DRLbackup (or properly located DRL backups from the previous version) and/or the derived DRL files from DRLgen to restore your blu-ray functionality after a firmware downgrade. | ||
== | == fix your DRL/CRL issues on GameOS with PS3 Linux == | ||
see: [[Fixing DRL and CRL Hashes]] | see: [[Fixing DRL and CRL Hashes]] | ||
== rewrite DRL/CRL hashes with multiMAN == | |||
since multiMAN ver 04.11.11: | since multiMAN ver 04.11.11: | ||
* Added option in “Settings” – Fix Broken Blu-ray Movie Playback<br /> | * Added option in “Settings” – Fix Broken Blu-ray Movie Playback<br /> | ||
The function will rewrite DRL/CRL hashes if there is a mismatch and will fix “Playback Prohibited” error on 3.41/3.55/4.21/4.30 firmwares. | The function will rewrite DRL/CRL hashes if there is a mismatch and will fix “Playback Prohibited” error on 3.41/3.55/4.21/4.30 firmwares. | ||
== | == If all else fails - nikitis method == | ||
{{warning|content=WARNING: Do not try this method until you've done the DRL/CRL matching using a linux distro above using the "fix your DRL/CRL issues on GameOS with PS3 Linux" | {{warning|content=WARNING: Do not try this method until you've done the DRL/CRL matching using a linux distro above using the "fix your DRL/CRL issues on GameOS with PS3 Linux" as the matching is also required. And tried the MultiMan blu-ray fix method. | ||
}} | }} | ||
If like me, you have tried all of the above and still receive a "Prohibited Error" there is one last very drastic measure you may take. This requires a flasher as you are going to purposely RSOD your PS3. | |||
Requirements: | Requirements: | ||
* A Linux Distro installed, or at least a petitboot which can boot Red Ribbon OS. | * A Linux Distro installed, or at least a petitboot which can boot Red Ribbon OS. | ||
* Red Ribbon Live Disc. | * Red Ribbon Live Disc. | ||
* Make sure your PS3 is has petitboot setup in such a way you can cold boot into petitboot. If you cannot do ''all'' | * Make sure your PS3 is has petitboot setup in such a way you can cold boot into petitboot. If you cannot do ''all'' this, then this method ''will'' fail. | ||
First extract your NOR / NAND Data. Search twice for both entries of OCRL and delete them with a Hex editor. (HxD will work.) | First extract your NOR / NAND Data. Search twice for both entries of OCRL and delete them with a Hex editor. (HxD will work.) | ||
| Line 434: | Line 410: | ||
If you have 3.55 installed, you may go into Factory Service Mode using eclips3 usb key etc and run the RSOD lv2diag.self and it will re-initialize as well. | If you have 3.55 installed, you may go into Factory Service Mode using eclips3 usb key etc and run the RSOD lv2diag.self and it will re-initialize as well. | ||
See also: [[RSOD Fix]] | See also: [[RSOD Fix]] | ||
WARNING: Does not work for 4.XX CFW's at the moment. | |||
Final Notes: | Final Notes: | ||
If this last ditch effort does not work, then you either did something wrong, forgot to do the CRL/DRL Matching method via linux as stated above first, or your drive has a hardware issue | If this last ditch effort does not work, then you either did something wrong, forgot to do the CRL/DRL Matching method via linux as stated above first, or your drive has a hardware issue. | ||
NOTE: Only attempt if you feel your PS3 is worthless without a working blu-ray drive. And I am not responsible for any damages you may inflict upon your PS3 or yourself using this method if it does not work for you. | NOTE: Again please only try this method after you have tried all the other less intrusive methods (i.e. Multiman, CRL/DRL via Linux hash matching etc) as you could ruin your PS3 permanantly if you don't know what you are doing or do not do this correctly. Only attempt if you feel your PS3 is worthless without a working blu-ray drive. And I am not responsible for any damages you may inflict upon your PS3 or yourself using this method if it does not work for you. | ||
Good Luck! | Good Luck! | ||
| Line 445: | Line 423: | ||
Thoughts on why this works: | Thoughts on why this works: | ||
I had RSOD my system and re-initialized CVTRM without success of fixing the blu-ray player, so my thoughts are that data that is zero'd is related to CRL/DRL somehow in CVTRM. I had even zero'd out HRL and OCRL lines and used RSOD Fix with no success, It wasn't until I zero'd out all 3 areas that it worked for me. I had tried for many months to come up with a fix for this with much trial and error. I think without blanking out those areas it reinitializes CVTRM with the bad data and your blu-ray still will fail. But once blanking it out and then doing a RSOD fix, it reinitializes it based on what is currently on your blu-ray drive | We don't really know for sure why. I had RSOD my system and re-initialized CVTRM without success of fixing the blu-ray player, so my thoughts are that data that is zero'd is related to CRL/DRL somehow in CVTRM. I had even zero'd out HRL and OCRL lines and used RSOD Fix with no success, It wasn't until I zero'd out all 3 areas that it worked for me. I had tried for many months to come up with a fix for this with much trial and error. I think without blanking out those areas it reinitializes CVTRM with the bad data and your blu-ray still will fail. But once blanking it out and then doing a RSOD fix, it reinitializes it based on what is currently on your blu-ray drive and everything matches up. That is my theory anyway. There could be a simpler way to fix this and I challenge someone to figure out the relationships so we can better understand this process. | ||
== '''FIX - " playback of bds is prohibited on this system. "''' ==--[[User:Elrat|Elrat]] ([[User talk:Elrat|talk]]) 13:17, 4 June 2014 (EDT) | |||
--------------------------------------------------------------------------- | |||
I. METHOD 1 | |||
- Via Multiman , select the " Broken BR " option, it will align values DRL1 and 2 with values in the area VTRM dump . | |||
- Put a BR . If that does not work and tells you the message " Playback of bds is prohibited on this system . Contact technical support for assistance " , go to the following . | |||
II . METHOD 2 | |||
- Download the app and take a DRLgen BR disc randomly . | |||
- Under Multiman will take MKB_RO.inf file the same disk, then use it to generate both DRL1 and 2 from the soft DRLgen . | |||
- Copy these two files to a key, then replace the console via Multiman . These are in DEVFLASH3/data-revoke/drl | |||
- Once replaced , rerun the " Broken BR " option , you should have a message that the settings are restored. | |||
- Put a BR . If that does not work and tells you the message " Playback of bds is prohibited on this system . Contact technical support for assistance " , go to the following | |||
III . METHOD 3 | |||
- After method 2 , you still have the same problem. This is due to the VTRM area completely " upside down " , we are going to restore order . | |||
- RECOVERY MODE downgrade in the console CFW 3.55 CFW if you are 4.xx | |||
- Install in RECOVERY MODE CFW 3.55 - NOTHEROS - RSOD.PUP ( MD5: f237eb38bcd9d2e02337e9b5d2979a88 ) | |||
- Install and run the file rsodfix.gnpdrm.pkg ( MD5: cbb08c8bca7022da050c0647c6ab69f6 ) | |||
''o You should hear a beep, it has restored order in parts of VTRM'' | |||
''o At this point if you always put the same disc BR you will have another error message.'' | |||
- Install now still RECOVERY MODE the 3.55 OFW then turn off the console. | |||
- Unplug the console 220 for 5 to 10s. | |||
- Spend the console FSM ( Factory Service Mode) | |||
- Run the FactoryServiceMode_Lv2diag_RSOD.self file ( MD5: 4c2848d2687fafdf77aaf1244b9e6c07 ) to do this just put the file in the root | |||
a USB drive to FAT32. You should hear one beep, it means that the job was done. | |||
''' | ''o At this stage VTRM structure your own ;)'' | ||
- Install now in RECOVERY MODE V1.01 CFW 4.50 ROGERO then put your BR disk first, it should work. | |||
{{Hardware Flashers}}<noinclude>[[Category:Main]]</noinclude> | {{Hardware Flashers}}<noinclude>[[Category:Main]]</noinclude> | ||