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: | ||
{{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 | |||
== 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. | ||
=== Reproducing Issue === | === Reproducing Issue === | ||
| Line 325: | Line 311: | ||
==== DRL Tools ==== | ==== 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> | ||
| Line 358: | Line 344: | ||
=== | === 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 === | === 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. | ||
=== | === 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 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 | 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 | 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. "''' === | ||
| Line 466: | Line 448: | ||
# RECOVERY MODE downgrade in the console CFW 3.55 CFW if you are 4.xx | # 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 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.'' | # 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.'' | ||
# Install now still RECOVERY MODE the 3.55 OFW then turn off the console. | # Install now still RECOVERY MODE the 3.55 OFW then turn off the console. | ||
# Unplug the console wallsocket for 5 to 10s. | # Unplug the console wallsocket for 5 to 10s. | ||
# Spend the console FSM ( Factory Service Mode) | # 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 ;)'' | # 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 | # 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> | ||