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.
{{Outdated}}
 
Check [[Downgrade BluRay Playback Issue#FIX - " playback of bds is prohibited on this system. "|FIX - " playback of bds is prohibited on this system. "]] for additional details
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.
 
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 ==
== PS3 BLU-RAY PLAYBACK PROHIBITED ROOT CAUSE ANALYSIS ==
=== Introduction ===
=== 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.
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 ===
Line 325: Line 311:


==== DRL Tools ====
==== DRL Tools ====
[https://web.archive.org/web/*/http://ps3devwiki.com/files/devtools/DRLtools/DRLtools_0.90.rar DRLtools_0.90.rar]
[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:
* [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)
* [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)
* [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)
* [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)
* [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)
* [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>
Line 358: Line 344:




=== Fix your DRL/CRL issues on GameOS with PS3 Linux ===
=== 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]]
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 ===
=== rewrite DRL/CRL hashes with multiMAN ===
Line 370: Line 352:
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.


=== The nikitis method ===  
=== 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" 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.)
{{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.
}}
}}


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.   
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.   
 
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:
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'' of these items, then this method ''will'' fail you.
* 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.
* 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.)  
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 412:
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, it has been tried and tested on many consoles and worked on pretty much all of them.
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 425:
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 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.
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. "''' ===
=== '''FIX - " playback of bds is prohibited on this system. "''' ===
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)