Post: PS3 Error 8002F14E when installing Rebug 3.55.2 help?
06-06-2012, 11:40 PM #1
(adsbygoogle = window.adsbygoogle || []).push({}); I wanted to upgrade my PS3's FW to Rebug 3.55.2. My PS3 had Kmeaw 3.55 so I decided to first flash it to 3.55 OFW through the XMB and then flash it to Rebug 3.55.2, also through the XMB. The OFW 3.55 installed just fine, but not Rebug 3.55.2. My bluray drive is working perfectly and nothing in my PS3 is broken.

At around 9% through the installation of Rebug 3.55.2 I had an error with the code 8002F14E. I googled this error and some people were saying it's because of a bluray problem so I downloaded the Bluray Drive Bypass Rebug 3.55.2 and put it on my USB stick, but I couldn't get into recovery mode as the PS3 kept looping the update and kept producing the same error. So I formatted the PS3's hard drive and put it back into the PS3 and was able to get into recovery mode. I chose the last option which was System Update and it prompted me to format my hard drive by press Start + Select and I followed the instructions and the hard drive was formatted no problem, but then when it prompted me to update the firmware the same problem happened. It got stuck at 9% and showed an error with the code 8002F14E.

I tried formatting the hard drive again and using the OFW 3.55, but the same problem happened. I tried it with Kmeaw 3.55 and again, the same problem happened.

This has happened to me before in the past when I tried to go from OFW 3.55 to Kmeaw 3.55 and at that time, after I had exhausted all the possible solutions, I just turned off my PS3 for more than a day and then turned it back on and the firmware was installed successfully without any problems. Why do you think this happened? What's the cause behind this?

I also can't get into factory service mode either. I have ps3jig on my PSP and when I do the power+eject it works fine on my psp like the send request stuff, but my PS3 just boots up normally and goes either straight to the update screen again or back to the page that asks for me to press Start+Select, depending on whether I formatted my HDD or not.

Can I put the Lv2diag.self file along with the OFW 3.55 and try updating my PS3 like that? Or can you only do that using factory service mode?
(adsbygoogle = window.adsbygoogle || []).push({});
06-07-2012, 02:04 AM #2
wannabeprivate
Do a barrel roll!
Service mode works with the power-eject trick, and, with the jig in the usb port closest to the blu ray drive. If it doesn't work, then your ps3 is messed up, or, you aren't hitting the power and eject buttons within the allowable number of milli seconds..

What you could try doing, is, get it into service mode, then, put the rebug pup on the root of the thumb drive, along with the proper lv2diag.self file and boot up the ps3 with that thumb drive in the right-most port. Let it do its thing and it should turn off after a few minutes. Then put the lv2diag.self on the thumb drive by itself, and, boot that up to exit service mode.

Updating the ps3 via service mode does work, but just be careful. I was overly daring one time and converted my retail ps3 to a kiosk model via flashing kiosk firmware on it.. Kinda funny, but, managed to get the retail firmware back on it luckily.
06-07-2012, 02:33 AM #3
Okay so I just tried putting my PS3 into service mode using ps3jig on my psp. My psp is running 5.00 m33-6. Every time I ran ps3jig it would say Done, but the PS3 would still boot up normally. I googled this and found that other people were also having the same issue as me. Someone mentioned that you need to use a specific firmware, 5.50 GEN-D3 to get it to work.

Anyway, is there any other way I can get into service mode? Can you do it with an ipod touch?

Edit: I forgot to mention that my psp is a slim, version 2000. Maybe it doesn't work on slim PSPs?

Edit 2: I have the P3Go dongle. How do I use it to put my PS3 in factory service mode?
06-09-2012, 12:04 AM #4
Okay so I managed to get my PS3 in service mode, but it doesn't boot into the service mode normally. It just goes back to whatever it was doing, but there's a red screen of death and if I put the lv2diag.self file and a firmware, it works as would a normal PS3.

I tried downgrading to 3.41 and this is what the result was:

    
manufacturing updating start
PackageName = /dev_usb000/PS3UPDAT.PUP
settle polling interval success
vflash is enabled...
creating system regions...
create storage region: (region id = 1)
create storage region: (region id = 2)
format partition: (region_id = 2, CELL_FS_UTILITY:HDD0, CELL_FS_UFS)
create storage region: (region id = 3)
format partition: (region_id = 3, CELL_FS_UTILITY:HDD1, CELL_FS_FAT)
creating system regions done.
boot from nor flash...
creating nor flash regions...
create storage region: (region id = 2)
create storage region: (region id = 3)
creating flash regions...
create storage region: (region id = 1)
create storage region: (region id = 2)
format partition: (region_id = 2, CELL_FS_IOS:BUILTIN_FLSH1, CELL_FS_FAT)
create storage region: (region id = 3)
format partition: (region_id = 3, CELL_FS_IOS:BUILTIN_FLSH2, CELL_FS_FAT)
create storage region: (region id = 4)
format partition: (region_id = 4, CELL_FS_IOS:BUILTIN_FLSH3, CELL_FS_FAT)
create storage region: (region id = 5)
create storage region: (region id = 6)
Initializing
taking a while...
start Updating Proccess
Initialize elapsed time = 53 msec
check UPL
Check UPL elapsed time = 69 msec
check Package Size
get package size elapsed time = 18 msec
start Updating Package
Update packages num = 30
Update packages total size = 162260220
Update Package Revoke list
read package revoke list package (576 bytes) elapsed = 20 msec
update package revoke list elapsed = 204 msec
Update Package Revoke list done(0x8002f000)
Update Core OS Package
read core os package (5182047 bytes) elapsed = 250 msec
update core os package elapsed = 307 msec
Update Core OS Package done(0x8002f14b)
update package elapsed time = 782 msec
Updating or Verifying failure 0x8002f14b
UpMng.UpdatePackage() failure
manufacturing updating FAILURE(0x8002f14b)
Total Elapsed time = 15756 msec


If I try to update to the same version my console had before the update loop, which is 3.55, I get the same errors except instead of 0x8002f14b, it shows up as 0x8002f14e.

What should I do?
06-10-2012, 10:59 PM #5
Bump. I've so many solutions and none have worked. Surely, someone must know how to fix this? :(

Copyright © 2026, NextGenUpdate.
All Rights Reserved.

Gray NextGenUpdate Logo