Why are you posting in this thread?
Did you apply a patch on the Flash memory? Or installed an app that may have patched the Flash memory?
1. If you did NOT use a ps3xploit tool to bring that error about, you should create your own thread.
2. If you did use a ps3xploit tool you must provide more information such as console model, firmware version, steps you did before the error etc.. Can you still boot into XMB using the original hdd?
0x8002f313 errors are thought to be related with ROS region corruption in the Flash Memory, in other words a CoreOS installation issue.
Hello, I dont know if Im posting in right thread or should create my own thread about problem, sorry if I messed up.
Some story of this PS3, CECHL03, VER-001:
Bought it for cheap and wanted to try to fix it. Previously it would shut off randomly (thought that it was because of overheating) and tried to jailbreak it to see temperatures and that was stupid of me for risking and it shutdown in the middle of jailbreaking - console got bricked. Also, before jailbreaking, noticed that when changing resolution would give static noice display, for second or so. And display would turn off after while but console would still keep running, till you turn on monitor again. Another giveaway that it was not overheating issue but still did jailbreak.
After that tried to check Syscon for errors and it gave me nothing, well what to expect after bricking console I thought.
Few days ago I got Teensy 2.0++ and today I managed to connect it to PS3, successfully dumped NOR memory (what was remaining of it) and wrote new one and I think I was successful. I had dumped NOR via ps3xploit (before jailbreaking and checked) and patched it.
But after uploading patched NOR memory - console still does not power on. Syscon doesnt give errors (kinda)
Here what I did:
1. Followed steps of this guide (first post of this thread). Downloaded 4.87 system version bin file and patched my existing NOR dump from ps3xploit. (before it got bricked)
2. Followed 3rd step. PyPS3patcher gave no errors on my NOR dump, only PS3 Dump Checker v1.0 said bad on ROS0 HASH. Force patched it anyways.
3. Modified Teensy to use 3.3v with regulator.
4. Soldered to board all the wires for my board (VER-001). By following photo from psdevwiki.
5. Powered Vcc SB with 1.5v battery. As it was required, otherwise would get NOR chip manufacturer and chip type "Unknown". Also tried to dump NOR memory with unknown. (I hope it didint messed up things)
6. Wrote my patched NOR dump.
After that, without disconnecting/unsoldering Teensy I tried to boot PS3. Without HDD, BD drive, top shield. PSU was plugged onto 12V rails. Console now took longer to get YLOD, before it would get YLOD almost instantly or after few seconds if I remember correctly. Now it takes about 4 seconds I think. After no success, connected USB-TTL to check syscon if it gives any errors - no errors at all. No new errors in 'errlog' and with bringup. After that I thought maybe Teensy interfering and/or maybe because not everything is connected and it is not booting up. After desoldering and putting everything back together (except top plastic cover). Console still doesnt boot. Checked syscon - no errors either.
Just to be sure if syscon is still working, tried to power on 12V from PSU and it did gave error A0003001. So it seems it is working, kinda?
After trying to to boot few more times without "bringup", I saw new error codes in errlog.
Maybe it is not booting properly because something is wrong with HDMI and that way syscon doesnt log as error or just sometimes?
After that tried to format HDD, maybe previous PS3 OS is bugged - still doesnt boot. But havent tried to install new OS and havent tried to do it at all, but PS3 should still boot somewhat with freshly formated HDD? Or no?
My next move is to try to install fresh PS3 OS on hdd if its possible, maybe it will help.
Or maybe I should investigate more around HDMI chip area on motherboard? Because I could see on motherboard that there was liquid.
Or maybe I wrongly patched my NOR dump? I cant remember if console was updated to latest version 4.87 or 4.88. And maybe I used wrong .bin file and thats why console still doesnt boot?
Maybe someone can give me more directions, what I should do now? Would really appreciate it.
Because Im kinda lost. Syscon doesnt give errors (kinda, at least when tried to do bringup, no errors showed up). And Im thinking that maybe my NOR dump was bad or patched, wrote to NOR incorectly. But I desoldered teensy wires and really hoping that its not the case..
Code:
Pinging...
Set SB to tristate
NOR chip manufacturer: Samsung (0xec)
NOR chip type: K8Q2815UQB (0x7e0601)
STATUS_TRIST_N: LOW
STATUS_RESET_N: HIGH
STATUS_READY: HIGH
STATUS_CE_N: LOW
STATUS_WE_N: HIGH
STATUS_OE_N: HIGH
Resetting NOR...
Ready.
Dumping NOR...
16384 KB / 16384 KB
Done. [0:01:18.395000]
Closing serial device...
Done.
Code:
Pinging...
Set SB to tristate
NOR chip manufacturer: Samsung (0xec)
NOR chip type: K8Q2815UQB (0x7e0601)
STATUS_TRIST_N: LOW
STATUS_RESET_N: HIGH
STATUS_READY: HIGH
STATUS_CE_N: LOW
STATUS_WE_N: HIGH
STATUS_OE_N: HIGH
Resetting NOR...
Ready.
Buffered programming mode not supported for Samsung K8Q2815UQB!
Programming in unlock bypass mode (writewordubm)...
Writing...
16384 KB / 16384 KB
Done. [0:05:51.805000]
Verifying...
16384 KB / 16384 KB
Done. [0:01:18.390000]
Closing serial device...
Done.
Code:
Pinging...
Set SB to tristate
NOR chip manufacturer: unknown (0xff)
NOR chip type: unknown (0xffffff)
STATUS_TRIST_N: LOW
STATUS_RESET_N: HIGH
STATUS_READY: HIGH
STATUS_CE_N: HIGH
STATUS_WE_N: HIGH
STATUS_OE_N: HIGH
Resetting NOR...
Ready.
NOR Released
Closing serial device...
Done.
Code:
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
>$ shutdown
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.6.0
#!(Build ID: 3440,37120,
#!Build Date: 2008-12-26_15:20:27)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
Unless I misunderstood, you are posting in the wrong thread as you did not brick with a ps3xploit software flashing tool. If so, you should create your own thread.
Unless I misunderstood, you are posting in the wrong thread as you did not brick with a ps3xploit software flashing tool. If so, you should create your own thread.
Oh.. Thought it is the same method, mistook it for this ** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com/bgtoolset/. My bad. Because I followed this video
, but for 4.87 version (process is same) and console shut off in the middle of flashing NOR memory (27:18 in video). After that couldnt turn on console anymore. Followed this guide to unbrick, but no success.
Oh.. Thought it is the same method, mistook it for this ** ** www.ps3xploit.net > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com) > Domain no Longer owned by team** (NEW URL = http://ps3toolset.com/bgtoolset/. My bad. Because I followed this video
, but for 4.87 version (process is same) and console shut off in the middle of flashing NOR memory (27:18 in video). After that couldnt turn on console anymore. Followed this guide to unbrick, but no success.
Sorry but I won't watch the video, however if you used the PS3 Toolset to patch the Flash memory & the console shut down in the middle of it (power outage or accidental power switch off), this is the correct thread.
About the guide & your failure to revive the console, you need to wait for @littlebalup to reply.
Yes, used PS3 Toolset to patch Flash memory and console shut down while patching. The video is just a reference, in case I was explaining my issue wrong.
Thank you, I will wait for his reply.
--EDIT--
Checked my dumps, maybe I have indeed chosen wrong bin file to patch my dump?
My original NOR dump: ROS0 Version: 488.00; ROS1 Version 484.000
Patched NOR dump: ROS0 Version: 487.00; ROS1 Version 487.000
Yes, used PS3 Toolset to patch Flash memory and console shut down while patching. The video is just a reference, in case I was explaining my issue wrong.
Thank you, I will wait for his reply.
--EDIT--
Checked my dumps, maybe I have indeed chosen wrong bin file to patch my dump?
My original NOR dump: ROS0 Version: 488.00; ROS1 Version 484.000
Patched NOR dump: ROS0 Version: 487.00; ROS1 Version 487.000
You must patch with OFW 4.88 CoreOS or nofsm Patch. Using OFW 4.87 CoreOS will fail due to syscon hash check (actually OFW 4.88 hash).
So in your case you should apply the nofsm 4.88 patch embedded in latest PS3dumpchecker or PyPS3checker (is the same patch than ps3 toolset) , then flash, then the console should boot strait to the xmb with the ability to directly install a CFW.
You must patch with OFW 4.88 CoreOS or nofsm Patch. Using OFW 4.87 CoreOS will fail due to syscon hash check (actually OFW 4.88 hash).
So in your case you should apply the nofsm 4.88 patch embedded in latest PS3dumpchecker or PyPS3checker (is the same patch than ps3 toolset) , then flash, then the console should boot strait to the xmb with the ability to directly install a CFW.
Thank you very much!
Patched using PyPS3patcher using nofsm command (more details in Patch log).
Just to be double sure checked with PS3DumpChecker and it says now: ROS0 Version: 488.00; ROS1 Version 488.000
I think its good, now just need to solder all the wires again, it will take some time for me, but I will report here if I was successful or not.
--EDIT--
Console is unbricked, it boots now, I can briefly see image, but it has other issues and shuts down (same issue before bricking). Which I will try to fix myself or look for help in forum if I get stuck.
Thank you very much again!
I have a slim that was on 4.88OFW I used PS3Xploit to install hen and all went well untill someone installed a pkg file,ok they installed several and then the console would not goto hen anymore,I tried several things to resolve but to no avail. Then thinking i could just remove and format the HDD then put it back and Use OFW update to fix and start over.But console will not turn on no,well it turns on but screen stays black with green light on.I have a backup but I think I wrote over the pre HEN backup I had,I ordered a E3 Flasher and was trying to get all files and programs I need to flash but I cant find CosOFW4.88.bin Nor have I found out how to extract it myself,I think I have the nessary tools But would be thankfull for some instructions.Than you in advance for any assistance.
I have a slim that was on 4.88OFW I used PS3Xploit to install hen and all went well untill someone installed a pkg file,ok they installed several and then the console would not goto hen anymore,I tried several things to resolve but to no avail. Then thinking i could just remove and format the HDD then put it back and Use OFW update to fix and start over.But console will not turn on no,well it turns on but screen stays black with green light on.I have a backup but I think I wrote over the pre HEN backup I had,I ordered a E3 Flasher and was trying to get all files and programs I need to flash but I cant find CosOFW4.88.bin Nor have I found out how to extract it myself,I think I have the nessary tools But would be thankfull for some instructions.Than you in advance for any assistance.
Dump the Flash memory 2 or 3 times with the E3 if you don't already have a valid dump made with software. The dumps should all validate correctly, otherwise there might be a problem with the hardware flasher setup, once you are sure all the dumps you made are good, choose one of them to work upon.
Verify the dump with pyps3checker to ensure there is no problem with it.
If the dump checks out, use pyps3patcher & the 4.88 no-fsm patch file in the project to patch it.
Apply the patched dump with E3.
If you want to verify what was written by the E3 you can dump again & verify dump with pyps3checker.
A no-fsm patch only modifies the 2 ROS regions of the Flash memory, those are the regions where system files packed into a CoreOS package in a PUP file get deployed during a PUP installation.
Factory Service Mode is not the same as recovery mode, it is a diagnostics mode that was used by s#ny staff internally, it can be launched from USB with a file called lv2diag.self.
Recovery mode is the default recovery environment for PS3 users & it is launched with a file called emer_init.self (included in CoreOS) stored on Flash memory along with the kernel & other essential files.
I got my E3 and had to do the tri state thing,then I flashed ,still comes on with no screen.To day I noticed the swap thing if dump was made with Xploit so I did that and am about to flash again.wish me luck. I was thinking about the rebuilder I think I can get a dump from another slim.But hopefuly wont need to.
I tried 6 times to get things working again with no luck ,then I noticed the nofsm patch says 4.88 CEX Patched.I want a normal one just OFW because my CECH 30001B cannot do CFW only HEN.I wish my son could tell me what pkg he installed,I know he was trying to get more shops he didnt like the one i installed.I have looked everywhere I know of to find a CosOFW4.88.bin or figure out how to extract it myself.Im pretty sure I have the tools to do so I just need a little help.Thank you anyboddy.
I tried 6 times to get things working again with no luck ,then I noticed the nofsm patch says 4.88 CEX Patched.I want a normal one just OFW because my CECH 30001B cannot do CFW only HEN.I wish my son could tell me what pkg he installed,I know he was trying to get more shops he didnt like the one i installed.I have looked everywhere I know of to find a CosOFW4.88.bin or figure out how to extract it myself.Im pretty sure I have the tools to do so I just need a little help.Thank you anyboddy.
1. You never posted any pyps3checker logs of a dump, maybe you should do that so we can get an idea of the Flash memory situation. Make a new dump, validate it with the latest pyps3checker & post the logs here.
If the 2 ROS regions in your new dumps are detected as Retail 4.88 CEX patched, the patcher did its job & the flashing procedure went well but a no-fsm patch on this console cannot work. You must repatch with OFW 4.88 CoreOS.
Note also that operating system files on /dev_flash are actually located on a small partition of the internal hdd on a slim console, those files could have been patched/swapped or whatever which could cause booting issues so I strongly recommend you set your current internal hdd aside for the time being & use a spare blank hdd instead until you can get the console to work again.
2. Installing a pkg on a 3xxx console cannot modify the Flash memory but executing an installed homebrew can.
A console is like a PC, if you run unknown apps from unknown sources, you should expect to experience some issues at some point, from system corruption to data theft & LAN penetration.
On a slim, when you change hdd, you remove all the files any homebrew installation might have deployed, even if some files were deployed in /dev_flash (which is uncommon), the only files that are not located on the hdd are the CoreOS files (lv1 hypervisor, lv2 kernel, the loaders, the recovery etc..).
3. Generally speaking, software induced bricks are quite rare & ps3 console issues are often caused by malfunctioning hardware. Having said that, it's possible to brick a system partially or fully by using software.
One of the most common software related issues is caused by using homebrews made for CFW but incompatible with a HEN console.
CCAPI is one of those homebrews, it patches some files in the Flash memory.
There are also instances of permanent patches that may lead to a system no longer booting, for instance using IDPSet to replace the idps (permanent spoofing), a DEX target id in the spoofed idps could create a number of problems.
4. I assume that what you call "shops" are those piracy sites to download pirated games. Piracy related convos are not tolerated. You are a new member so I suggest you refer to the forum rules & guidelines to avoid getting moderated and/or banned.
Thank you for a quick responce,I dont know how to add those files yet but I will send them,and I will get Newest dumps,also I have not put in a HDD since all this so My tests have been without
Thank you for a quick responce,I dont know how to add those files yet but I will send them,and I will get Newest dumps,also I have not put in a HDD since all this so My tests have been without
