[HELP] Remarry DECR1000A Blu-Ray drive

I can only repeat the advice said above, try to replace NOR flash with its firmware from original to the donor PCB. Can you do that or to ask someone to do that?

 

No I do not know what it is and I do not know anyone who can do it ... So I think I'm stuck.

 

Try to ask someone from any service center that repair telephones for example. They can do that (I mean swap them). Dont't know its price but thats not a big problem for them.

 

But there's no other way to do that? I know you told me it is not recommended to use the Factory Menu, but many people have to associate a new drive with their PS3, so why would not it work on a DECR?

 

If zecoxao said you will stuck in it - you will stuck.

 

did you replace the ribbon cable?

 

Yes !

 

Then i'm affraid your daughterboard is dead, which is a shame because you'll not be able to find a similar one (those bluray drives have JTAG enabled and they're different from the retail ones)

Edit:
But if you still want to try to remarry your drive, i suggest you do it through linux and not through FSM. I remember when we got two DECR-1000As that it was a pain in the ass to put one of them back to normal when in FSM

 

Ah ... Well, I believe you for the FSM case, so I will not try ... And I have never touched Linux in my life so without detailed tutorial I do not think to get there ...

BUT I made another discovery (but that can serve nothing): I plugged in my DECR1000A an BD drive of an old PS4 Fat (I do not know the model of this player but it is not a KEM-400AAA like that of the DECR, DECR's BD Drive has a unique contrary to the old BD-DRIVE I plugged has a double lens) but it has a daughter card. And surprise: with this BD drive connected to the DECR1000A, the lens lights, the disc rotates but stops! But the PSN games do not work (which I think is normal, the daughter card is not married to the DECR1000A).

My question is this: the BD drive of my DECR1000A does not have the lens that turns on and the disk does not turn, does it come from the daughter card (which may be dead) or the drive itself ?

 

it's the daughter card.

 

BIG SURPRISE : I just made another try, the daughter card does not have to be completely dead because ... I managed to launch a PSN game! I think there are two problems: the drive itself (lens problem, but which will be repaired on Monday when I have received the new KEM-400AAA) and may be a bad contact on the daughtercard. I will pass on this card my electronic contact product, and do other tests, I keep you all informed!

EDIT : Hmmm... Curious problem! When the daughtercard works, and when I reboot the DECR, the card works once every two ... There must be a bad contact or something else ... I will give you news of my other tests when I receive my KEM-400AAA (Monday, normally)

 

Wouldn't using finalize.self from 3.55 or lower get you out of it?

 

I'm not sure if you were in the group when it was attempted, but finalize.self didn't work. and i certainly don't want to be the one to try that out

 

I probably was there but not paying attention xD
And yeah I wouldn't want to try that the hard way either xD

 

I have a spare working BD drive taken from DECR. Let me know if you are keen, do take note that I am in Singapore, so shipping might be costly.

Cheers!

 

Why not but it depends on the model of the daughter card? I have just tested the BD player of the DECR1000A in another PS3 (without the daughter card of the DECR but with that of the PS3, of course) and the drive itself works. . We only need a new daughtercard only.

If it's exactly the same model, is it still necessary to "marry" the new card with the DECR, or just interchange the cards? Our daughtercard model is BMD-001.

 

Why should he not use FSM? Does the Lv2Diag.self file that takes retail consoles out of FSM need to be resigned to Debug to run at start-up on a DECR?

 

Because

 

Because it's a "system debugger" and it has a different System Controller IC than that of other units. It seems to require a different set of service center tools than the ones that are public (the ones that leaked are meant to be used on retail units).

Simply by having different firmware a "intelligent" peripheral device may behave differently and respond to completely different command sets, which can make higher level software "confused".

There's a reason "If zecoxao said you will stuck in it - you will stuck." was said a couple posts above and it's highly related to the fact that you're sailing uncharted territory. Follow the advice of people more experienced than you.

 

I am following his advice, I just wanted the real reason other than a precaution.

Isn't a DECR actually just a revised DEH-R1040? I thought System Debuggers were the ones that Sony uses to debug the chain of trust & make the actual Firmware (or System Software as they call it)