Editing Downgrade BluRay Playback Issue

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

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:
This page was created originally by nikitis with other contributors with other fixes and have been included in the correct order one should try to fix the issue.
=PS3 BLU-RAY PLAYBACK PROHIBITED ROOT CAUSE ANALYSIS=
 
==Introduction==
There was some confusion on methods to fix and reasons why the issue occurred.  It's been 11 years since last edit, and we have a little more clarity on the issue and why it occurs, see [[Downgrade BluRay Playback Issue#Overview|Overview]] for an update on findings.
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.
 
First, check [[Downgrade BluRay Playback Issue#FIX - " playback of bds is prohibited on this system. "|FIX - " playback of bds is prohibited on this system. "]] for easier methods to correct the issue.
 
Linux methods: If those fail, try Glevands method in Linux [[Fixing DRL and CRL Hashes]] to check for mismatches.  If it's not a mismatch then check the original but drastic method by nikitis using [[Downgrade BluRay Playback Issue#The nikitis method|The nikitis method]] for Full Factory Reset via Linux.




*Updated on 01-31-2023
== 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 ===  
==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.
The reason this occurs is for 1 of 2 reasons.
Reason 1:
There was a foul up with the implementation of the Sony blu-ray CSS copy protection system and some incorrect values got stored onto your blu-ray drive that was a mismatch of what your drive is aware of, so if it fails to play, it may be assuming you might have tampered with your drive.  To prevent possible hacking attempts to copy movies from the disc to a digital medium it was designed to prevent playback.


Reason 2:
It was intentional by Sony as a security mechanism to add your console id to CRL/DRL list when an MKB.ini file is read from a blu-ray disc.  Sony's system of updating blu-ray drives with known compromised drives/consoles is done by obtaining the console id somehow (using hacked system on PSN for example), they copy your console id and add it to the next version of the CRL/DRL.  You go to the store, and buy said movie containing updated mkb.ini file, insert it into your blu-ray drive with nice warm popcorn in hand, girlfriend (or boyfriend, we don't discriminate here) is sitting next to you ready to relax and get the error.  Movie night is ruined :(  Your console id actually matches what is on the CRL/DRL and is blocked.  What's worse is Sony will ask you to send the console in to be fixed, charge you $150, and will send you a new system instead without any of your saved games / data.


Solution:
You can unbrick with methods below, and it's intense, however you will only be able to play movies with a lower MKB.ini version because any newer movie with an updated MKB.ini version will contain your console id if it was bricked for Reason 2.  You'll know this is the case if you do the fix, and enter an early blu-ray movie and it plays fine, but insert your latest movie, and it bricks again.  If it doesn't brick again, then it was Reason 1, and you should have no further issue playing movies in the future unless the same "technical glitch" happens again down the road, but likely will not.


=== Reproducing Issue ===
==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 ====
===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 NOR non-volatile memory that rely on HDD volatile memory for dev_flash3 and are unaffected
##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 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 ====
===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 ===
==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 ===
==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 321: Line 305:
#Reset the HRL on the drive to match the DRL1 and DRL2 files
#Reset the HRL on the drive to match the DRL1 and DRL2 files
##This third Lv2diag.self should have been included in the DGF.rar package by the original creators to prevent this whole issue.
##This third Lv2diag.self should have been included in the DGF.rar package by the original creators to prevent this whole issue.
#Having a BluRay Movie Title next to you
##Enter Factory Service Mode and insert the BluRay Movie Title. It should now get recognized and you can leave FSM again.
==== DRL Tools ====
[https://web.archive.org/web/*/http://ps3devwiki.com/files/devtools/DRLtools/DRLtools_0.90.rar DRLtools_0.90.rar]
The tools in the suite are:
* [https://web.archive.org/web/*/http://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)
* [https://web.archive.org/web/*/http://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)
* [https://web.archive.org/web/*/http://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>
===== 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.
===== 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.
# 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.
===== Detailed instructions =====
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.
====== 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.
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.
=== Fix your DRL/CRL issues on GameOS with PS3 Linux ===
If you have Linux installed or want to do a Linux install with OtherOS++, and you hope the issue is Reason 1 as mentioned in the Overview:
see: [[Fixing DRL and CRL Hashes]]
This method sets the CRL/DRL to match fixing the issue, if a mismatch is the cause of the issue.
If it's reason 2, Skip to the "nikitis" method using linux to zero out the CRL/DRL, and HRL on flash and then recreating cvtrm using Linux.  This is essentially a factory reset.  (Please note that this method will work for reason 1 and 2, but if reason 2, you will only be able to play older movies than the one that bricked your console in the first place.  If you enter in a newer disc it will brick again because your console id matches the DRL on the disc and newer discs.)
=== rewrite DRL/CRL hashes with multiMAN ===
since multiMAN ver 04.11.11:
* 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 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" or tried the MultiMan blu-ray fix method. (Non-Linux method to correct matching.  Assumes it is a matching error and not a buggered cvtrm.)
}}
This method will fix your PS3 if you follow the steps, it is in depth, and it will essentially factory reset your blu-ray drive and cvtrm.  If like me, you have tried all of the above and still receive a "Prohibited Error" this is one last very drastic measure you may take.  This requires a flasher as you are going to purposely RSOD your PS3. 
Overview:
This method is done via an OtherOS++ Install using ps3dm tools for Linux.  It zeros out CRL / DRL / and HRL locations.  If all 3 are not cleared, i.e. only 2 of 3 are cleared, this method will fail.  Clear all 3 and then reset cvtrm using ps3dm tools, and it will work again with all movies if the issue was Reason 1 for the fail in the main overview.  If this error occurred as a result of your console being in the actual DRL, then you'll only be able to play older movies than the one inserted to brick your drive the first time.  (has to be an older mkb.ini)  Any newer mkb.ini will contain your console id and WILL cause the error again.  I'm sorry :(
Requirements:
* A Linux Distro installed, or at least a petitboot which can boot Red Ribbon OS.
* 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'' of these items, then this method ''will'' fail you.
* 3.55 CFW installed.  Preferably my 3.55 NOTHEROS++RSOD CFW.  WARNING: METHOD WILL NOT WORK WITH 4.xx+  Must downgrade to fix.
First extract your NOR / NAND Data.  Search twice for both entries of OCRL and delete them with a Hex editor. (HxD will work.)
Mine was located at 0xF69400 & 0xFA9400.  And zero the OCRL0200 line and data lines just below until there is nothing but 00's.
Secondly, look for the HRL line somewhere on your Dump.  (Should be located at F60000 and FA0000 on NOR's, find equivalent on NAND.) and 00 out the 3-5 lines there until it's all 00's.  DO NOT DELETE IT, OVERWRITE WITH 00's at both spots. 
0xF60000  10 00 00 0C 00 04 10 03 00 00 00 01 20 00 00 34 --
0xF60010  00 00 00 00 00 00 00 00 5B 3F 73 B4 9A 86 C7 B2  | Zero Lines out (Sometimes there are 5 lines and possibly longer
0xF60020  A0 D1 1E AF A7 9B 97 E2 7A CB 05 2B 4D 61 26 AE  |                  as HRL grows.)
0xF60030  13 CA 29 84 19 93 15 E1 4A DB 2C B7 7C 00 E4 EB --
...
&
...
0xFA0000  10 00 00 0C 00 04 10 03 00 00 00 01 20 00 00 34 --
0xFA0010  00 00 00 00 00 00 00 00 5B 3F 73 B4 9A 86 C7 B2  | Zero Lines out (Sometimes there are 5 lines and possibly longer
0xFA0020  A0 D1 1E AF A7 9B 97 E2 7A CB 05 2B 4D 61 26 AE  |                  as HRL grows.)
0xFA0030  13 CA 29 84 19 93 15 E1 4A DB 2C B7 7C 00 E4 EB --
Third, Go to Address's on NOR: 0xEC52B0 and 0xEE52B0.  Here you may see 1 to several, 6 line entries above this address.  You need to Zero all of that data above these lines.  Example:
0xEC5260  00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 12 --
0xEC5270  10 70 00 00 02 00 00 01 10 70 00 00 03 00 00 02  |
0xEC5280  DA 52 64 4B F1 BA A4 C8 2A 99 4F C6 70 BC 9A D6  |
0xEC5290  86 EE 8C B6 70 10 47 40 80 18 06 1A 8C 92 51 52  | Zero Lines (And above if there are more entries until you reach the void of 00's)
0xEC52A0  CC 51 94 80 54 D^ 4D 9E 91 A8 66 3E 93 A5 C7 84  |
0xEC52B0  22 BB 99 63 09 E4 63 CF 56 F3 39 6C B6 D8 75 93 --
...
0xEC52C0  00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF --  Do not touch this line.
...
&
...
0xEC5260  00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 12 --
0xEC5270  10 70 00 00 02 00 00 01 10 70 00 00 03 00 00 02  |
0xEC5280  DA 52 64 4B F1 BA A4 C8 2A 99 4F C6 70 BC 9A D6  |
0xEC5290  86 EE 8C B6 70 10 47 40 80 18 06 1A 8C 92 51 52  | Zero Lines (And above if there are more entries until you reach the void of 00's)
0xEC52A0  CC 51 94 80 54 D^ 4D 9E 91 A8 66 3E 93 A5 C7 84  |
0xEC52B0  22 BB 99 63 09 E4 63 CF 56 F3 39 6C B6 D8 75 93 --
...
0xEE52C0  00 00 00 00 00 00 00 00 FF FF FF FF FF FF FF FF --  Do not touch this line
The cleaning part is done.  Flash this back to your PS3, the HRL is blank, and so is the data in CVTRM area.  This WILL RSOD your PS3.
Now the reason for having a linux distibution installed or petitboot access.  After flashing it back, power off your PS3, turn on and you will get a RSOD.
Power off, then use the cold boot method to boot directly into petitboot, and load Red Ribbon Live Disc.  Grab the information on how to re-initialize CVTRM using the linux method (RSOD Linux Fix).  Once fixed and re-initialized, reboot into GameOS, and your blu-ray player should be able to play blu-rays again! 
Alternative Method:
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]]
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, it has been tried and tested on many consoles and worked on pretty much all of them.
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.
Good Luck!
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 which are zeros and is like a fresh factory drive. 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. "''' ===
'''NOTE FROM 2022''': the below methods are from 2014, I found methods 2 and especially 3 to be very outdated and convoluted, referencing files that are no longer very easy to find online. I was able to resolve the issue using a guide for setting up a new Blu Ray drive as if the drive in the system was a freshly installed one, the exact guide I followed was [https://psx-place.com/threads/my-adverture-of-remarry-bluray-drive-on-4-86.30896/ "My adverture of Remarry BluRay Drive on 4.86" by tryingbe] on  but if you need to find another one searching google for "Remarry Bluray Drive" should bring up some results.
==== 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 )<br />''o You should hear a beep, it has restored order in parts of VTRM''<br />''o At this point if you always put the same disc BR you will have another error message.''  (This is because your console id was added to the official Sony DRL/CRL list and was located on the blu-ray disc you used to brick it the first time, I'm sorry but you can only play older movies safely, any new movies will continue to brick your blu-ray drive.  - nikitis)
# Install now still RECOVERY MODE the 3.55 OFW then turn off the console.
# Unplug the console wallsocket ​​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 renamed as lv2diag.self in the root of FAT32 USB drive. You should hear one beep, it means that the job was done.<br />''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. (Assuming there was just a mixup in the CRL/DRL, if your console id is truly on the disc, then it won't work for that disc and newer, only older -nikitis).
{{Hardware Flashers}}<noinclude>[[Category:Main]]</noinclude>
Please note that all contributions to PS3 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS3 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)

Templates used on this page:

Retrieved from "http://www.psdevwiki.com/ps3/Downgrade_BluRay_Playback_Issue"