PS3 Blu-ray remarry issue

L

luvbuckets

Member
I'm having an odd issue and I think it may be a bug in evilnat 4.90 and the way it handles remarrying the bluray drive. I have a cechb01 Frankenstein I completed and wanted to swap the Blu-ray drive. So I went through all the steps I normally do and the drive works great...that is if it's on cfw. The minute I switch over to OFW and try to run a PS3 disc i get the error code "80010017". I've tried 4 different drives now and multiple discs. I could be wrong, but from what I've read online, this error seems to be related to some encryption/decryption issue. Almost as if I'm trying to run homebrew on an unmodded system. I know of one other person who's had this issue and his solution was to keep swapping Blu-ray drives. Can anyone try to point me in the right direction here? Anything i can do other than flashing back and forth from ofw to cfw a million times and trying a bunch of blu ray drives?
 
I've seen this issue being brought up for over two years now and nobody's seemed to have given a solution for it. After trying several drives (all drives from same model ps3) and new lasers. I've determined it's most likely an issue with evilnat and how it remarrys drives. On cfw the PS3 discs work fine. On ofw they refuse to work.

My fix was to enable qa flags, install rebug 4.86.1 (install nobd cfw if drive hasn't been remarried with evilnat first). Once on rebug I dumped eid root key and remarried in FSM. Then I disabled qa flags, installed OFW through safe mode and discs are reading fine now.
 
Can confirm its an issue with evilnats 4.90 i was getting the same error using the remarry process, all discs would read and play fine except ps3 discs once back on OFW, if u stayed on CFW they worked fine.

I did the same work around and used 4.85.1 rebug lite and it fixed the problem. For shits and giggles i installed 4.90 evilnat CFW, did the remarry process again and the errors came back.
 
wrx884 said:
Can confirm its an issue with evilnats 4.90 i was getting the same error using the remarry process, all discs would read and play fine except ps3 discs once back on OFW, if u stayed on CFW they worked fine.

I did the same work around and used 4.85.1 rebug lite and it fixed the problem. For shits and giggles i installed 4.90 evilnat CFW, did the remarry process again and the errors came back.
Click to expand...

Hey @ll

I'm having the same issue after I sucessfully remarried a BD-410 (with BMD-003) to my CECHC to replace a broken BMD-001 (BD-400) which I could still get the eid_root_key from. I did it with Evilnat CFW 4.91. So it's all very fresh.

The BD-Drive works flawlessly with PS2, BR-Movies and BR-Games in CFW.

I went back to OFW 4.91 and have the same Error Code 80010017 or FFFFFFFF when trying to load a game. Blu-Ray movies play fine though. Going back to CFW makes games work again, too.

Since i'm relative new, could any of you provide a more exact step-by-step guide for what I'd have to do to remarry it properly so it works with OFW as well?

That would be highly appreciated and probably help others, too. Thanks! :)
 
luvbuckets said:
Toggle qa flags. Downgrade to rebug cfw and remarry again through rebug. It's a pretty straightforward process...
Click to expand...

so toggling QA flag in evilnat 4.91, then just install rebug lite 4.85.1 and remarry bd with the key I previously exported with evilnat 4.91 ?
 
rattensuppe said:
so toggling QA flag in evilnat 4.91, then just install rebug lite 4.85.1 and remarry bd with the key I previously exported with evilnat 4.91 ?
Click to expand...

You can do the remarrying process on Evilnat 4.91, if I recall correctly, no need to downgrade. But most tutorials will be based upon REBUG 4.84.2.

The only thing YOU MUST NEVER, EVER DO IS UPDATE YOUR CONSOLE WHILE ON FACTORY SERVICE MODE.

I use caps because if you do that, you will never be able to exit FSM, rendering your console useless.
 
GuilloteTesla said:
You can do the remarrying process on Evilnat 4.91, if I recall correctly, no need to downgrade. But most tutorials will be based upon REBUG 4.84.2.

The only thing YOU MUST NEVER, EVER DO IS UPDATE YOUR CONSOLE WHILE ON FACTORY SERVICE MODE.

I use caps because if you do that, you will never be able to exit FSM, rendering your console useless.
Click to expand...

remarrying in evilnat causes the issue with the ofw.

that's what this thread is about ;)
 
Not sure if you've been following this thread but I suspect there's a bug with evilnat and the way it handles the remarrying process. A handful of us are experiencing issues when we revert back to ofw. The PS3 stops playing retail PS3 discs.
 
That's why I've written "if I recall correctly" because of some people having this issue, but don't remember if there was a fix released recently or if it was an isolated case.

Evilnat has released CFW 4.91 which has lots of improvements.
 
I don't think it's fixed. This is the only thread I could find that even suggests it's an issue with evilnat. I don't think it's an issue with the eid root key either.I compared both files (rebug and evilnat) in hexedit and they're identical.

@rattensuppe you want to toggle qa flags in evilnat and reboot before downgrading. The reason for this is because you're going from 4.91 --- to a lower firmware. Once on rebug the remarry process is almost identical. Only difference is you need to install rebug toolbox in the package manager and then go to system files.

Once you have rebug toolbox installed you can run it and dump root key. It dumps it into the hdd:\games folder. It will tell you where it is when it dumps successfully. Copy all of the files it outputs in the "USDIR" directory to the root of a thumb drive and then go into fsm and remarry.
 
GuilloteTesla said:
That's why I've written "if I recall correctly" because of some people having this issue, but don't remember if there was a fix released recently or if it was an isolated case.

Evilnat has released CFW 4.91 which has lots of improvements.
Click to expand...

like I wrote, I've got the issue with evilnat 4.91 as well and needed a guide to know how to fix it like luvbuckets and wrx884 did.

I wanted to know what exactly i need to do to fix the issue.

1. Can i downgrade directly to rebug lite 4.86.1 from evilnat 4.91 after enabling QA flags in evilnat? do i need to prepare anything else?

2. can I use the eid_root_key I already exctracted with evilnat 4.91 for the remarrying process in rebug lite ?

@luvbuckets thank you!
 
rattensuppe said:
like I wrote, I've got the issue with evilnat 4.91 as well and needed a guide to know how to fix it like luvbuckets and wrx884 did.

I wanted to know what exactly i need to do to fix the issue.

1. Can i downgrade directly to rebug lite 4.86.1 from evilnat 4.91 after enabling QA flags in evilnat? do i need to prepare anything else?

2. can I use the eid_root_key I already exctracted with evilnat 4.91 for the remarrying process in rebug lite ?

@luvbuckets thank you!
Click to expand...

1. Yes, you can downgrade to any CFW you like after enabling QA flags. The only condition is to not downgrade lower than the factory FW. This can be check with Evilnat's CFW Tools or with minVerChk.

2. Yes, the ERK is unique per each console. The dump method is the same.
 
Yes you can downgrade directly. As long as you toggle qa flags. I would use the files rebug toolbox generates and not use the evilnat files.
I can't verify that it works with evilnat eid root key. Technically it should work the same. I dumped with rebug and used those files. That's what worked for me. If your screen goes black when running any homebrew in rebug, then you'll need to install a rebug (nobd) firmware, dump eid root key and copy to thumb drive with something like multiman. Then go back to regular rebug to remarry. I don't believe you can remarry bd drive in a nobd firmware.
 
If the eid root key is the same in hex, then I'm sure I can use it without having to export it again.

also i exported it with the regular evilnat cfw, since nobd wasn't or isn't available for 4.91 yet.

I don't want to unscrew the ps3 and put in the old daughterboard. so if the key files are the same, I'll just try marrying it again with the other cfw first.
 
REBUG generates more than just one file when it dumps eid root key. Not sure if those other files are needed for the remarrying process? Guess you're about to find out though. Good luck.
 
luvbuckets said:
REBUG generates more than just one file when it dumps eid root key. Not sure if those other files are needed for the remarrying process? Guess you're about to find out though. Good luck.
Click to expand...

i see. well then i guess i have to try that too.

i always only read about that one key file that's necessary for remarrying up until now

thanks


*edit*

thanks a lot guys. that worked.

it was enough to re-marry the bluray-drive in rebug lite 4.86.1 (rebug toolbox 02.03.07 but not used) using the eid root key I exported with evilnat 4.91 before (not using a nobd fw to dump it by the way).

(i had to enable update debug as well to downgrade. otherwise it threw a file corrupt error)

Afterwards I installed 4.91 OFW and there were no more errors. BD-410 working like a charm in my cechc.
 
Last edited:
Wasn't trying to bother you with it evilnat. You're the only one working on cfw for the PS3. Your work is greatly appreciated. Like I mentioned before. I compared the two eidrootkey files (one from evilnat and one from rebug). Both were identical according to hexedit. So it might have to do with the actual process evilnat uses to marry the drive? Just figured that might help.
 
You must log in or register to reply here.

Similar threads

Back
Top