PS3 PS3 2503A, bricked?

Andry90120

Andry90120

Member
Hello guys! The console of a friend of mine broke after an infortunate jailbreak (CFW) attempt, and we don't know that to do.
Sadly he doesn't remember when he started to have problems, because he did it like a year ago (Probably started to have problems after NOR dump)
We also looked for the date code, and his console it's a 0D.
The console, always go in safe mode automatically when he starts up, this what we tried, the console says the 4.84 or higher update is needed.

•Swap the HDD's
•Format the HDD using the PS3 method
•Repair database, etc...
•Installing CFW (We tried with Ferrox 4.87, and REBUG 4.86)
•Installing HFW (4.84.2)
•Installing OFW (4.87, and then 4.84)
•Installing NOBD/NOBT CFW (Ferrox 4.87)

Everything we tried, gives us error 8002F2C5 or 8002F281.
 
0x8002F281: Error with installing Firmware update. Check the connection of the Wifi/BT board.

Which suggesting that WiFi/BT is broken and You would be able to install only "no BT" CFW versions.

However, if Your friend tried to install CFW on none compatible PS3 (CECH-25xx are compatible and not, depend of factory fw version which tells if have new boot loader or old), then I don't know if this would be one of a reason of such errors (I also never installed noBT CFW so if this errors is displayed only on this specific Ferrox, then probably it is not the problem and BT/WiFi is ok).
 
Last edited:
Andry90120 said:
Hello guys! The console of a friend of mine broke after an infortunate jailbreak (CFW) attempt, and we don't know that to do.
Sadly he doesn't remember when he started to have problems, because he did it like a year ago (Probably started to have problems after NOR dump)
We also looked for the date code, and his console it's a 0D.
The console, always go in safe mode automatically when he starts up, this what we tried, the console says the 4.84 or higher update is needed.

•Swap the HDD's
•Format the HDD using the PS3 method
•Repair database, etc...
•Installing CFW (We tried with Ferrox 4.87, and REBUG 4.86)
•Installing HFW (4.84.2)
•Installing OFW (4.87, and then 4.84)
•Installing NOBD/NOBT CFW (Ferrox 4.87)

Everything we tried, gives us error 8002F2C5 or 8002F281.
Click to expand...
Did you try with a different thumb drive? It needs to be MBR, FAT32 formatted.
 
Berion said:
0x8002F281: Error with installing Firmware update. Check the connection of the Wifi/BT board.

Which suggesting that WiFi/BT is broken and You would be able to install only "no BT" CFW versions.

However, if Your friend tried to install CFW on none compatible PS3 (CECH-25xx are compatible and not, depend of factory fw version which tells if have new boot loader or old), then I don't know if this would be one of a reason of such errors (I also never installed noBT CFW so if this errors is displayed only on this specific Ferrox, then probably it is not the problem and BT/WiFi is ok).
Click to expand...

IDK, he claims that WiFi/BT works perfectly, and we also tried to install a NOBD/NOBT update, but didn't work.
Sadly we don't know if the console it's CFW compatible, because he did not used the MinVersChecker, but looking at the date code, it's a 0D, and where assuming that he's lucky if not mistaken, 0D date code it's 3.50 or something like this.
 
jcorrea said:
Did you try with a different thumb drive? It needs to be MBR, FAT32 formatted.
Click to expand...

Nope, the thumb drive is FAT32, but we didn't checked if it's MBR or GPT.

edit: Anyway, the PS3 was able to find the USB files, because we never had the message of "No data found" or something like that.
 
It's always recommended to check with minver check pup. There is a small chance its not CFW compatible even with the datecode 0D, Sony have been known to refurbish systems and put new motherboards into older cases.
 
DeViL303 said:
It's always recommended to check with minver check pup. There is a small chance its not CFW compatible even with the datecode 0D, Sony have been known to refurbish systems and put new motherboards into older cases.
Click to expand...

Damn... I didn't know about that.
If so, there is a way to save his console, he should use Teensy or something like that?
 
Andry90120 said:
Damn... I didn't know about that.
If so, there is a way to save his console, he should use Teensy or something like that?
Click to expand...
Well it seems its not a brick due to someone patching a non compatible console, If it was it would just shut down after patching and not boot up at all after.

So look into other solutions for now, the fact its getting to safe mode is a good sign and means its technically not a brick really..


It sounds to me like it has a BT or BD issue and the console was not patched for CFW at all. This means you are in a normal update loop caused by the hardware fault. The solution for that would be to fix the hardware so it can install an update, OR you could patch the system for CFW via hardware flasher like an E3.
 
Last edited:
Andry90120 said:
Nope, the thumb drive is FAT32, but we didn't checked if it's MBR or GPT.

edit: Anyway, the PS3 was able to find the USB files, because we never had the message of "No data found" or something like that.
Click to expand...
Maybe it's a pendrive problem...
 
As has been said
Try another usb stick if you can get one. Even a usb micro sd card reader.

If not then try fully formatting your usb drive not fast format.

Try a different hdd it may be faulty and in a pc the bad sectors are marked and re-mapped to spare areas on the hdd. The ps3 uses its own format and from experience I do not believe it does this re-map so you could be transferring the update ready for installing onto a dead area.

After that then its looking like the WiFi or bt has been damaged during the hardware downgrade
Left something to touch the pcb maybe like a rouge screw. Enough to short power to one or the other or other suck damage.
You may get lucky by stripping the console down again and eye balling the damage or finding the item thats causing this.

If your in the UK I may be able to help more.
 
DeViL303 said:
That is possible too, it's always worth trying a different USB stick in these situations. I always use an old 2GB stick for this kind of thing.
Click to expand...
Already saw a 100MB usb stick "marked" as 16GB, and OS shows 16GB but when I try to fill it, the data just become corrupted and then I discovered the real size of it.
 
Andry90120 said:
The console, always go in safe mode automatically when he starts up, this what we tried, the console says the 4.84 or higher update is needed.
Click to expand...

QA flag wasnt - isnt enabled? Valid dump avaible? If so then try use a flasher. E3 for example. Then go back 3.55 if the device is not just jailbrakable but downgradable too...
...just an idea...
 
szunyi84 said:
QA flag wasnt - isnt enabled? Valid dump avaible? If so then try use a flasher. E3 for example. Then go back 3.55 if the device is not just jailbrakable but downgradable too...
...just an idea...
Click to expand...

Sadly I don't know if QA flag was enabled, but I think that wasn't enabled to be honest. We don't even know if the console is downgradeable too (Because the data code says that's a 3.50, but we don't know if the previous owner swapped the case, and I don't know it's sure to run MinVersCheck in safe mode)

jcorrea said:
Already saw a 100MB usb stick "marked" as 16GB, and OS shows 16GB but when I try to fill it, the data just become corrupted and then I discovered the real size of it.
Click to expand...

We did every test possible about the USB, it's a legit 2GB 2.0 USB, no errors. But in case, I suggested him to buy a new one just for the PS3.

Anyway, since it's like that's a HDD related problem (That it's strange anyway, because we swapped the HDD, and still have problems) We'll try to connect to the PC and do a format.

Sadly I can't look if his console haves something damaged because he's in UK, and i'm in Italy, so, I need to rely to what he writes. :/
 
Andry90120 said:
Sadly I don't know if QA flag was enabled, but I think that wasn't enabled to be honest. We don't even know if the console is downgradeable too (Because the data code says that's a 3.50, but we don't know if the previous owner swapped the case, and I don't know it's sure to run MinVersCheck in safe mode)
Click to expand...
Is safe, but there is something weird with it if you do this:
1) disconnect hdd and format it in PC
2) connect back the hdd in PS3
3) enter recovery menu and try to install the MinVerCheck

At that point it happens some kind of error... i dont remember what, maybe the console crashes or doesnt displays anything, or dunno, dont remember well... the point is the MinVerCheck is not ging to give you the info you need
But is not dangerous because it happened to me in a CECH-25xx and the PS3 is still alive, didnt bricked :D

-------------------
The hdd format in PC is something you should do incase of problems, sometimes it happens the hdd contains some kind of rare problem (hard to know why it happens, i dont understand it) and the format in PS3 doesnt solves that problem

Btw, in my previous post i mentioned to install 4.87 OFW because incase of problems using an official firmware for repair purposes is going to "ease your mind"... you know is 100% official code, so "it should work"
The other CFW's mentioned before should work as well, you could use 4.87 HFW instead but pssss, doesnt matters
The point is that 4.87 OFW is vulnerable to an exploit used in the bg toolkit so is fine... incase the installation is completed thats the next step you should do to install a CFW

Get a "noBD" CFW at hand too ready to install, you can check the error codes here btw:
https://www.psdevwiki.com/ps3/Error_Codes
Andry90120 said:
Everything we tried, gives us error 8002F2C5 or 8002F281.
Click to expand...
*The description of error code 0x8002F2C5 was written by me btw :)
*The description of error code 0x8002F281 assumes you have a PS3 model where the wifi/BT module was located in a separated circuit board connected to the main motherboard by a ribbon cable... in a CECH-25xx motherboard is integrated so there is no ribbon cable to check
 
sandungas said:
Is safe, but there is something weird with it if you do this:
1) disconnect hdd and format it in PC
2) connect back the hdd in PS3
3) enter recovery menu and try to install the MinVerCheck

At that point it happens some kind of error... i dont remember what, maybe the console crashes or doesnt displays anything, or dunno, dont remember well... the point is the MinVerCheck is not ging to give you the info you need
But is not dangerous because it happened to me in a CECH-25xx and the PS3 is still alive, didnt bricked :D

-------------------
The hdd format in PC is something you should do incase of problems, sometimes it happens the hdd contains some kind of rare problem (hard to know why it happens, i dont understand it) and the format in PS3 doesnt solves that problem

Btw, in my previous post i mentioned to install 4.87 OFW because incase of problems using an official firmware for repair purposes is going to "ease your mind"... you know is 100% official code, so "it should work"
The other CFW's mentioned before should work as well, you could use 4.87 HFW instead but pssss, doesnt matters
The point is that 4.87 OFW is vulnerable to an exploit used in the bg toolkit so is fine... incase the installation is completed thats the next step you should do to install a CFW

Get a "noBD" CFW at hand too ready to install, you can check the error codes here btw:
https://www.psdevwiki.com/ps3/Error_Codes

*The description of error code 0x8002F2C5 was written by me btw :)
*The description of error code 0x8002F281 assumes you have a PS3 model where the wifi/BT module was located in a separated circuit board connected to the main motherboard by a ribbon cable... in a CECH-25xx motherboard is integrated so there is no ribbon cable to check
Click to expand...

Thanks for the reply!
We tried to install OFW (4.84, and then we jumped to 4.87) but anything, it still gives error (0x8002F2C5 if not mistaken)
Now we are trying with NOBT 4.86 REBUG REX (I wanted to try with 4.84, since it's the installed on the console) but we're even unsure that the console had a proper JB on :/
 
Can you ask him to make a new dump and see what the validators report. Or any chance he still has his original dump somewhere?
Need to get past the guess work now and find out what's on that nor
 
baileyscream said:
Can you ask him to make a new dump and see what the validators report. Or any chance he still has his original dump somewhere?
Need to get past the guess work now and find out what's on that nor
Click to expand...

Tomorrow I'll try to ask if still haves the original dumps, but I don't think tbh
 
szunyi84 said:
QA flag wasnt - isnt enabled? Valid dump avaible? If so then try use a flasher. E3 for example. Then go back 3.55 if the device is not just jailbrakable but downgradable too...
...just an idea...
Click to expand...
Downgrading to 3.55 is not required for anything anymore, Also ANY console that is jailbreakable is also downgradable to at least 3.56. .
 
You must log in or register to reply here.

Similar threads

Back
Top