Method to upgrade to OFW with a Blu-Ray bypass CFW?

ptach

Forum Noob
Hey all,

I'm super green to this community, so apologies (as always) if the answers are hidden in some forum post I've not come across yet.

It's been a labour of love getting an old PS3 someone gave me back from YLOD, but feel I've hit a wall.
It's a fat CECHGxx with 3.70 OFW. It's hackable, as the OFW can be rolled back to 1.90.

The problem lies with the error code 8002f14e, when trying to upgrade the OFW. It gets to about 80% and then loops, I've read that this could be the Blu-Ray? Well when I was given the unit, I noticed that the clip for the drive on the motherboard had snapped off (just the actual black clip part, not the pins). I managed to get the drive working before trying to upgrade the firmware, with some strategically placed cardboard and tape. So unsure why it was still failing.

Tried the usual; formatted the HDD, created USBs, tried upgrading with the recovery mode, but no bones.

The only thing I can think of now, is using some CFW that bypasses the blu-ray drive, but just installs the OFW 4.81/4.82, then I can load a CFW (I state 4.81 because of COBRA CFW for NoBD).

What do you guys reckon? It's probably not worth all this effort, but as I said, it's a labour of love!
Any leads?

Thanks!
 
There is nothing you can do, excluding fixing your drive/connector. If you are on firmware higher than 3.55 there is no way to install CFW directly, so NO-BD patch can't be applied. Only on 4.81, and 4.82 can patch nor to allow cfw install (incl. NO-BD). So until you are not on 4.81/82 or 3.55 you need to fix your BD, or use hardware flasher.
 
Gah, thought as much. Thanks both.

Another last ditch effort, is it possible to be something other than the Blu-Ray? As I said, I managed to get it working before attempting the upgrade, I can't see it being anything else though, but don't really know what else I can do to fix it.

Think I'll sell it off for parts and put it towards a working one to hack.
 
Update error0x8002F14EError with installing Firmware update. (BD)Drive not found or disconnected. // or CoreOS region failure when in log "Update Core OS Package done(0x8002f14e)" or Revoke region failure when in log "Update Package Revoke list done(0x8002f14e)"

If it is not from the BD being missing, then it could be from corrupted parts of the system software. Which you would need to fix with a hardware flasher, if you didn't wait for new ps3xploit version.

Since that model stores all the firmware on the two NAND chips, formatting or using another HDD doesn't work like it might on a NOR model.

I think if it was the BT, it would give a different error. But worth a shot to check it out anyway. Or keep trying different freshly formatted FAT32 USB sticks. Maybe get lucky and one will finish.
 
oh, I didn't look the error up. ...just a suggestion if fixing the bd didn't work for some reason. ;)
 
Update error0x8002F14EError with installing Firmware update. (BD)Drive not found or disconnected. // or CoreOS region failure when in log "Update Core OS Package done(0x8002f14e)" or Revoke region failure when in log "Update Package Revoke list done(0x8002f14e)"
If it is not from the BD being missing, then it could be from corrupted parts of the system software. Which you would need to fix with a hardware flasher, if you didn't wait for new ps3xploit version.

Since that model stores all the firmware on the two NAND chips, formatting or using another HDD doesn't work like it might on a NOR model.

I think if it was the BT, it would give a different error. But worth a shot to check it out anyway. Or keep trying different freshly formatted FAT32 USB sticks. Maybe get lucky and one will finish.

Ah right, thanks for that. Haven't tried any CFW, as I knew I needed a flasher to get to 3.55, so just trying OFW to get to 4.81/4.82. We have an abundance of USB sticks at work atm, so might just get a decent batch together and blast through them on Sunday eve.

So do you reckon then, I should assume my BR is ok for now, and think of it more as an issue with the firmware on the NAND? If that's so I can look towards getting it onto OFW 4.82 and using the xpolit hack, instead of 4.81 and using a Blu-Ray bypass one.

Thanks guys, you're all big helps here!
 
Ah right, thanks for that. Haven't tried any CFW, as I knew I needed a flasher to get to 3.55, so just trying OFW to get to 4.81/4.82. We have an abundance of USB sticks at work atm, so might just get a decent batch together and blast through them on Sunday eve.

So do you reckon then, I should assume my BR is ok for now, and think of it more as an issue with the firmware on the NAND? If that's so I can look towards getting it onto OFW 4.82 and using the xpolit hack, instead of 4.81 and using a Blu-Ray bypass one.

Thanks guys, you're all big helps here!
The BD is still working? Plays discs, and you are able to open apps and psn games normally? I would double check that the drive is fully operational. All contacts on both ends of ribbon are good. If any are sketchy, snip with very sharp scissors so contacts are even. Cut business card and insert with ribbon, then Gorilla tape it. (If you have a known working BD logic board you can try that. They don't even need to be married to update to OFW. Borrow one from a friend with the same model?)

But yeah, if the PS3 is working like it should except being able to update. Then probably a malformed ROS header or corrupt region in the one it is not booting from. Make sure you pay attention to the error codes each time you try. Sometimes the weird ones like that will give multiple codes.
 
You can check the ribbon cables with a multimeter to see if there is some track broken in the middle. This uses to happen when you bend the ribbon cables back and forth, so is usual if you or the previous owner opened the PS3 many times

Take the ribbon cables to a table, and lay them over the table with the copper "contacts" of the extremes aiming to top
Then use a book or some weight to place in the middle of the ribbon cable to keep it static in that position (so you have your hands free to do other thing)

Then, with the multimeter, check in continuity every one of the copper tracks of the ribbon cable, one by one... and with one hand in each extreme
If continuity is infinite (the multimeters represents this with an 1) = the track is good
If continuity is 0, or intermediate values, or inestable = the track is partially or completly broken at some point in the middle ribbon cable

----------------
Incase of finding a broken track (and for ghetto repairs glory bonus) you can use the trick playerkp420 mentioned
Cut the ribbon cable (at an undefined point because you dont know where is broken) and use a cutting knife (like shaving it cowboy style) or sandpaper... to remove the plastic covering layer... until you make new copper "contacts" visibles

----------------
And review what you did with the cardboard to fix the broken "clip" of the motherboard connector
What you need to keep in mind is there is a lot of pins in the big connectors, the pins are very small, but the pressure you are adding with the cardboard (guetto style) needs to be spreaded very well along ALL the pins
Maybe the pins of the center have good pressure... but the ones at the sides not... and this is not going to work

To solve this problem, you need to use some material that preserves his dimmensions
In other words... dont use cardboard !!!
Is much better to use some plastic material... i cant make you any recomendation, because what you need to do is to rush your house to see what can you find that fits a bit what you need XD
Better targets to find some kind of plastic sheet materials are:
-bedrooms (office materails and things related with paper and books)
-kitchen (food product packages, etc...)
-bathroom (plastic bottles, boxes, etc...)

If you find a plastic a bit "gummy" (kind of material where you can make a mark with your nail but not very deep and if you wait it returns to original form) is nice because will work as an "spring" and with luck it will keep his dimensions and pressure indefinitelly
If is solid... then you need to try to find the best thickness that fits inside the hole, but dont force it much, the pins itself are bent and works as "springs" naturally
 
Last edited:
Sorry guys!

Thanks for all your worthwhile support there, but the damn thing has just YLOD'd again, so I'm going to save myself the frustration in the future, and just sell it off for parts and buy something that's more easily hacked.

I know it's a commonly asked question, but as I'm posting anyway, do you lot have a recommended/reliable model to get for hacking? Then I can keep my eyes peeled on eBay.

The BD is still working? Plays discs, and you are able to open apps and psn games normally? I would double check that the drive is fully operational. All contacts on both ends of ribbon are good. If any are sketchy, snip with very sharp scissors so contacts are even. Cut business card and insert with ribbon, then Gorilla tape it. (If you have a known working BD logic board you can try that. They don't even need to be married to update to OFW. Borrow one from a friend with the same model?)

But yeah, if the PS3 is working like it should except being able to update. Then probably a malformed ROS header or corrupt region in the one it is not booting from. Make sure you pay attention to the error codes each time you try. Sometimes the weird ones like that will give multiple codes.

You were right btw, must've been a break in the ribbon at some point. I swapped the ribbon for another, but the update still kept failing with the same error. I've not received a different error so far.

Swapped the bluetooth out just to check, still failing at the same point.

I got to about 4 loops, and then the YLOD. Unlucky this time I suppose!
 
Update error0x8002F14EError with installing Firmware update. (BD)Drive not found or disconnected. // or CoreOS region failure when in log "Update Core OS Package done(0x8002f14e)" or Revoke region failure when in log "Update Package Revoke list done(0x8002f14e)"
If it is not from the BD being missing, then it could be from corrupted parts of the system software. Which you would need to fix with a hardware flasher, if you didn't wait for new ps3xploit version.

Since that model stores all the firmware on the two NAND chips, formatting or using another HDD doesn't work like it might on a NOR model.

I think if it was the BT, it would give a different error. But worth a shot to check it out anyway. Or keep trying different freshly formatted FAT32 USB sticks. Maybe get lucky and one will finish.

so i'm getting the error at 6%, which based on the install breakdown and order comes to one of these
Update Package Revoke list
read package revoke list package (576 bytes) elapsed = 6 msec
update package revoke list elapsed = 331 msec
Update Package Revoke list done(0x8002f000)
RL_FOR_PACKAGE.img copied from PUP to trvk_pkg
Update Core OS Package
read core os package (5193774 bytes) elapsed = 324 msec
update core os package elapsed = 1965 msec
Update Core OS Package done(0x8002f000)
Core OS package (CORE_OS_PACKAGE.pkg) is unpkg'ed from PUP and written to ros

can it be a bad HDD? i have tried a working one and its still the same thing. why would this cause a break? what can i do
 

Similar threads

Back
Top