PS3 How to Remarry BlueRay Drive on CFW PS3 Step by Step

Hey Louay, thanks for the tutorial. I could remarry my BD drive by following the first method. I have a fattie that could update but not run any apps or discs, and I almost took it apart, then I thought "maybe the previous owner changed the drive before breaking almost everything", and that was it.
 
ElGris said:
Hey Louay, thanks for the tutorial. I could remarry my BD drive by following the first method. I have a fattie that could update but not run any apps or discs, and I almost took it apart, then I thought "maybe the previous owner changed the drive before breaking almost everything", and that was it.
Click to expand...
Happy for you to get it works :)
 
Good morning.
Try the remarry process and when I launch it I get the following "error sys_storage_open err 80010006" I have checked that the connection of the Blue Ray to the motherboard is correct. Do you know what may be failing?
Thank you
 
Hello, I've tried the steps from the second method, however I ran into an error "sys_storage_open err: 8001006". I thought it might've been a firmware issue so I tried method 1, and same thing. I've made a forum post under general discussion detailing what's happened, however no one has responded. To not clutter up the replies here, I'll just link it in this reply. Hope you can help!
 
Maybe @Louay knows something about it. I didn't run with that issue, and don't know what it could be. There's also another guy in this page with the same problem.
 
ElGris said:
Maybe @Louay knows something about it. I didn't run with that issue, and don't know what it could be. There's also another guy in this page with the same problem.
Click to expand...
Yeah I hope he can figure it out. I do have a second ps3 to troubleshoot if it is indeed the hardware. But if it's about system storage, it can't be that.
 
Tried something, so I updated to the normal rebuy cfw to see if it was the firmware that could be the issue. But when I went to update it gave me the error 8002f14e at 81%. Which was the problem originally with the "fixed" logic board except it would stop at 61% instead. Any idea what the ps3 checks for at 81%? I know at 61% is when it checks if the logic board works or not but I don't know about 81% Because when I switched to the confirmed working blue ray drive it went through the update no problem. So it definitely could be something on the logic board. Just need to know what it's checking for on the logic board itself.
 
That 8002f14e error means you have problems with the daughter board (logic board of the drive). You could updated with the one you wanted to use via this tutorial, right? Could you put the models of both consoles you're using for this? Which is the one with the damaged BD drive?
 
ElGris said:
That 8002f14e error means you have problems with the daughter board (logic board of the drive). You could updated with the one you wanted to use via this tutorial, right? Could you put the models of both consoles you're using for this? Which is the one with the damaged BD drive?
Click to expand...
I originally updated to the noBD cfw because I was tired of pulling the drive out so many times and used a working one at the time. Mind you it wasn't because of laziness, I literally took out and placed back in the drive like 10 times and didn't bother doing it to update to the noBD, so it was my fault there and possibly why I didn't notice this error early on. And both console models are CECHA01. The one having issues is the one I've been talking about and is also the one with the damaged drive, the second ps3 is working and is the one I use all the time.
 
Hmm, you have then one drive for two consoles, right? Haha. You should get an used drive from a CECHG or H, those run very good. But about the error "sys_storage_open err: 8001006" I still don't know what it could be, maybe you're missing one step of the tutorial?

If the drive works fine, and you can update normally with it in both consoles, maybe you're forgetting to do something. I did twice this tutorial and had no problem.
 
ElGris said:
Hmm, you have then one drive for two consoles, right? Haha. You should get an used drive from a CECHG or H, those run very good. But about the error "sys_storage_open err: 8001006" I still don't know what it could be, maybe you're missing one step of the tutorial?

If the drive works fine, and you can update normally with it in both consoles, maybe you're forgetting to do something. I did twice this tutorial and had no problem.
Click to expand...
No, I have two drives. One working which is from my working ps3 (the one I always use). And the other which is from the non-working ps3 (the one in question with the sys_storage_open err: 8001006). I've been using the drive from the working ps3 to troubleshoot what maybe the problem on the non-working ps3. The logic board had an issue with a power inductor missing which I soldered back on (from the non-working ps3) Which did allow the drive to take in disks, spin, focus the laser and such, but not show up on screen. Which I had the feeling it might've been an issue with it not being married to the ps3. And that's what brought me here. I assumed with the error code being "sys_storage_open err: 8001006" it would've been pertaining to something being wrong with the software side of things (because of the storage_open part of it). But now I noticed when I switch firmwares to the official rebug, (with the non-working ps3's logic board that I fixed by soldering that power inductor mentioned earlier) It gets hung up at 81% of the installation. So it may still be something to do with the logic board and this is a new finding I just learned today. Using the drive from the working ps3, switches firmwares just fine. But the non-working ps3's stops at 81% and gives that error mentioned earlier.
 
That's what I meant to say, you only have one working drive, the one of the PS3 you always use. The other one has a problem with the console reconizing it 'cause it lauchs that update problem you're mentioning, right?

Now, forget about the drive with the update problem, and use the one you know is good. And re-install the No-BD CFW and try again, you must be forgetting something.

It's wierd though, 'cause until now I knew that that update problem, related to the drive, was only in case of dead logic boards, but in this case the drive takes discs..
 
ElGris said:
That's what I meant to say, you only have one working drive, the one of the PS3 you always use. The other one has a problem with the console reconizing it 'cause it lauchs that update problem you're mentioning, right?

Now, forget about the drive with the update problem, and use the one you know is good. And re-install the No-BD CFW and try again, you must be forgetting something.

It's wierd though, 'cause until now I knew that that update problem, related to the drive, was only in case of dead logic boards, but in this case the drive takes discs..
Click to expand...
That's what I also thought originally, fixing the board has allowed the drive to take disks, spin them up, read them and do everything that a normal drive would. Not sure why it won't show up on screen.. I could be missing something, but I have tried switching logic boards between the drives to see if maybe the drive hardware might be the problem, which is a no. Both drives good but the 1 logic board bad. I'd like to have at least two boards fully working without having to buy one since I was looking on ebay and they're pretty scarce. Ebay international stuff also doesn't come cheap. I don't really want to marry the working drive to the ps3 since that would mean I'd still need another logic board for the working ps3.. Or find out what could be the problem with the broken logic board. It gets stuck at 81% which means it's some other component of the board that I don't know. At 61% that means it's a dead logic board, but this one isn't... that's what boggles my mind.
 
You can try to find some fat PS3 on market place there where you live. You can use a CECHA->K drive, so maybe you need to dig a little bit. And about the non working drive, the only thing I can recommend you is to clean good the sockets of the logic board.
 
ElGris said:
You can try to find some fat PS3 on market place there where you live. You can use a CECHA->K drive, so maybe you need to dig a little bit. And about the non working drive, the only thing I can recommend you is to clean good the sockets of the logic board.
Click to expand...
Roger dodger, I'll see what I can do. If anything, I'll keep trying to find whatever wrong is with this damn logic board. Wouldn't wanna throw it away since it *almost* works. I hope the dude who has the same problem as me has an answer to his though. Then hopefully it might work for me too.
 
ElGris said:
You can try to find some fat PS3 on market place there where you live. You can use a CECHA->K drive, so maybe you need to dig a little bit. And about the non working drive, the only thing I can recommend you is to clean good the sockets of the logic board.
Click to expand...
Heyo, new development. So I attempted to remarry the working drive to the ps3, and the error is CEX_drive_init_pblock() failed. This is a working logic board by the way, it's been tested and we know it's working because it's from the working ps3. I also just tried out a game before removing it and it read and played everything just fine. So now this can't be the broken logic board anymore. Both system and logic board are working.
 
ExtremeCaliber said:
Heyo, new development. So I attempted to remarry the working drive to the ps3, and the error is CEX_drive_init_pblock() failed. This is a working logic board by the way, it's been tested and we know it's working because it's from the working ps3. I also just tried out a game before removing it and it read and played everything just fine. So now this can't be the broken logic board anymore. Both system and logic board are working.
Click to expand...
That message you got means the remarry process successed. You miss this in the tutorial "CEX_drive_init() failed if blueray failed to remarry/sometime it show failed but remarry done properly"

Now you only have to install a normal CFW, for example Rebug 4.85 and test the drive with some games. I did this twice and twice I got that error code, but the remarry thing worked.
 
ElGris said:
That message you got means the remarry process successed. You miss this in the tutorial "CEX_drive_init() failed if blueray failed to remarry/sometime it show failed but remarry done properly"

Now you only have to install a normal CFW, for example Rebug 4.85 and test the drive with some games. I did this twice and twice I got that error code, but the remarry thing worked.
Click to expand...
Hello if that message appear maybe the remarry process failed or succeded but you can test that by Installing a normal CFW Rebug or Ferrox 4.85 if it doesn't show to you error 8002F14E then the remarry process succeded and you will not face blackscreen when you launch an app,homebrew...etc
 
Louay said:
Hello if that message appear maybe the remarry process failed or succeded but you can test that by Installing a normal CFW Rebug or Ferrox 4.85 if it doesn't show to you error 8002F14E then the remarry process succeded and you will not face blackscreen when you launch an app,homebrew...etc
Click to expand...

I could be wrong, but as far as i know you don't need a married drive to install CFW? ANY drive connected will get you past the 8002f14e error and allow FW to install fully. The only way to know if its actually married properly is to boot applications on normal CFW or load disc contents.
 
You must log in or register to reply here.

Similar threads

Back
Top