PS3 [GUIDE] Unbrick a PS3 after an unfortunate PS3Xploit flash

Yugonibblit said:
So you removed the nor chip from the motherboard? Was that so you can dump your nor chip?, dump looks good only warning is you can not downgrade at all because min fw version is 4.50 from the factory or install cfw you can only use hen.maybe flash back your dump and it will work?
Click to expand...

Hi. Thx for reply. Yes i removed NOR chip for dump, because i can take dump with my universal programmer. I know few hardware issue symptoms on earlier models like RLOD, YLOD, but this one turns off after one minute without any lights. No red and green or yellow, no beep, no blinkinking red etc until i press power button again the red light on. Of course standby mode is not functional by holding power button.

The motherboard is PPX-001. May be someone knows what is wrong with it.
Thanks

Cypher_CG89 said:
I would say its got whats called "Blackout" of it just cuts out with no leds showing. That points to a power supply issue somewhere.
Click to expand...

Unfortunatly no. The power supply is working fine. Power supply issue is when no main +12V not present on power on and symptom is 3 beeps blinking red. "Blackout" turns off all lights immediatly. This one turns off after one minute, also NOT turning off at all with removed NOR chip.
 
Last edited by a moderator:
Intruder_911 said:
"Blackout" turns off all lights immediatly
Click to expand...

Sorry but unfortunately yes, what you describe is blackout.

Blackout can happen at any time, most time people experience it straight away, but it can happen after a little bit of time, possible a process drawing power through whats faulty or something along those lines... Power cuts out "all leds off" thus called blackout. then you press the power button and the red led returns...

Plenty of people have been on here describing what you are saying now and it was blackout.

Intruder_911 said:
Power supply issue is when no main +12V not present on power on and symptom is 3 beeps blinking red
Click to expand...

That's called bricked mate, not power supply issue. SYSCON is refusing to boot the CELL = FW issue not power.

Intruder_911 said:
This one turns off after one minute, also NOT turning off at all with removed NOR chip.
Click to expand...

Well that obvious, there's no FW to run it, so its just blindly powered some components. So the console isn't running properly anyways
 
Well, seems problem is in my poor English, so i can't explain my problem correctly.

I'll try again:
1. When i turn on PS3 it turns off aprox. in one minute (may be little more) - so no instant shut down.
2. While PS3 is on there is main +12V power and CELL/RSX power seems normal.
3. When i remove NOR chip and turn it on the PS3 not turns off at all.
4. My firmware check is looks fine, with no errors except SKU identification and warning about downgrade.

So is it:
a. "Blackout"
b. firmware issue
c. other hardware problem?

Thank you
 
So.. PS3 model 4xxxC super slim..(Nor)
I used e3 flasher and I successfully dumped the nor
I used the dump checker and put the file that I dumped in it(Bin)
So it said it was bad..then I checked all the settings correct and used 4.84 bin file (as I remember that the last fw I had on the PS3 was 4.84 maybe am wrong..) anyways..I take the new patched dump and put it in the sd card and flash the new dump successfully..then I cut the tristate wire..but still when I turn the PS3 on after 5 sec it goes off..what's the problem??
How can I find what the FW was before brick ?
 
Last edited:
I just found that the console had 4.82 before brick..but I overwrite the bad dump with new OK dump with 4.84 OsCore and the PS3 doesn't turns on..
Can I fix this?..
 
i fixed it...i just flashed the nor with the right dump that i patched with the right CoreOS(4.82) ..now it works..thanks for the guide..this guide is the only one that mentions unbrick on a ps3 super slim..also i asked a lot of people that are familiar with downgrading/jailbreakng and said there is no way to unbrick a full bricked console(that doesnt turn on) especially a super slim..i just proved them wrong..
 
hello I have a question whether someone can help me with my problem console at the beginning had RSOD after taking the dump got Brick I was able to upload back the original dump but I have no image nor does not respond to usb in the FSM input I have a GLOD error is in METLDR shows as false I had a different RSOD before and I did a patch on 3.55 input in FSM rogero 3.7A and LV2diag self on RSOD and the console worked normally and now I'm shocked because I used the same steps and I have GLOD
PyPS3checker v0.10.x. Check log.
Checked file : C:\Users\Administrator\Desktop\orginal RSOD\orginal\bkpps3.bin
******* Getting flash type *******
Flash type : NOR
Reversed : YES
******* Getting SKU identification datas *******
idps = 0x08
metldr0 = 0xE8D0
metldr1 = 0x0E89
metldrkey = 0x43B6EF4AE20F7400C8809E53
bootldr0 = 0x2EAB
bootldr1 = 0x2EAB
bootldrsize = 0x2EAF0
Matching SKU : OK
CECHLxx or CECHPxx (VER-001)
Minimum version 2.45
******* Getting SDK versions *******
ROS0 : 446.000
ROS1 : 485.000
******* Checking first_region_header *******
001.01 First Region Header 0x00 Filled Area 0 : OK
001.02 First Region Header Magic : OK
001.03 First Region Header 0x00 Filled Area 1 : OK
******* Checking flash_format *******
002.01 Flash Format String : OK
002.02 Flash Format Version : OK
002.03 Flash Format 0xFF Filled Area : OK
******* Checking flash_region_table *******
003.01 Flash Region Table Header : OK
003.02 asecure_loader Offset - Length : OK
003.03 asecure_loader Name : OK
003.04 eEID Offset - Length : OK
003.05 eEID Name : OK
003.06 cISD Offset - Length : OK
003.07 cISD Name : OK
003.08 cCSD Offset - Length : OK
003.09 cCSD Name : OK
003.10 trvk_prg0 Offset - Length : OK
003.11 trvk_prg0 Name : OK
003.12 trvk_prg1 Offset - Length : OK
003.13 trvk_prg1 Name : OK
003.14 trvk_pkg0 Offset - Length : OK
003.15 trvk_pkg0 Name : OK
003.16 trvk_pkg1 Offset - Length : OK
003.17 trvk_pkg1 Name : OK
003.18 ros0 Offset - Length : OK
003.19 ros0 Name : OK
003.20 ros1 Offset - Length : OK
003.21 ros1 Name : OK
003.22 cvtrm Offset - Length : OK
003.23 cvtrm Name : OK
003.24 Flash Region Table 0x00 Filled Area : OK
******* Checking asure_loader_region *******
004.01 asecure_loader Header : OK
004.02 metldr Offset : OK
004.03 metldr Length : OK
004.04 metldr Name : OK
004.05 metldr RevKey : OK
004.06 metldr Binary Size : OK
004.07 metldr Statistics : DANGER!
Any bytes from offset 0x840 to offset 0xF110 should be less than 0.52%.
0x00 is 2.74%
004.08 asecure_loader 0x00 Filled Area : OK
******* Checking eEID_region *******
005.01 eEID Header : OK
005.02 EID0 Offset - Length : OK
005.03 EID1 Offset - Length : OK
005.04 EID2 Offset - Length : OK
005.05 EID3 Offset - Length : OK
005.06 EID4 Offset - Length : OK
005.07 EID5 Offset - Length : OK
005.08 EID0 IDPS0 : OK
005.09 EID0 IDPS1 : OK
005.10 EID0 Static : OK
005.11 EID2 BlockSize/Padding : OK
005.12 EID3 Static0 : OK
005.13 EID3 Static1 : OK
005.14 EID3 Static2 : OK
005.15 EID5 IDPS0 : OK
005.16 EID5 IDPS1 : OK
005.17 EID5 Static : OK
005.18 eEID Region 0xFF Filled Area : OK
005.19 eEID Statistics0 : OK
005.20 eEID Statistics1 : OK
******* Checking cISD_region *******
006.01 cISD Header : OK
006.02 cISD0 Offset - Length : OK
006.03 cISD1 Offset - Length : OK
006.04 cISD2 Offset - Length : OK
006.05 cISD0 0xFF Filled Area : OK
006.06 cISD1 IDLog Header : OK
006.07 cISD1 Semistatic 1 : OK
006.08 cISD1 Semistatic 2 : OK
006.09 cISD1 0xFF Filled Area 0 : OK
006.10 cISD1 Static : OK
006.11 cISD1 Semistatic 3 : OK
006.12 cISD1 0xFF Filled Area 1 : OK
006.13 cISD1 Statistics : OK
006.14 cISD2 : OK
006.15 cISD 0xFF Filled Area : OK
******* Checking cCSD_region *******
007.01 cCSD Header : OK
007.02 cCSD Entry Table : OK
007.03 cCSD 0xFF Filled Area : OK
******* Checking Revokation_region *******
008.01 trvk_prg0 SCE : OK
008.02 trvk_prg0 Hash : OK
Size = 0x2E0
MD5 = E537DE954DCF25D4DE961DF44549BAF7
Version = 3.50 (from PUP)
008.02 trvk_prg0 0xFF filled area : OK
008.03 trvk_prg1 SCE : OK
008.04 trvk_prg1 Hash : OK
Size = 0x2E0
MD5 = 78629D24BD721488F3A1E846938F87DF
Version = 3.55 (from PUP)
008.04 trvk_prg1 0xFF filled area : OK
008.05 trvk_pkg0 SCE : OK
008.06 trvk_pkg0 0xFF filled area : OK
008.07 trvk_pkg1 SCE : OK
008.08 trvk_pkg1 0xFF filled area : OK
******* Checking CoreOS_region *******
009.01 ROS0 Header : OK
009.02 ROS0 Hash : OK
Size = 0x6FFFE0
MD5 = D18F9F37189627E798694B8A85434A23
Version = 4.46 CEX/SEX OFW
009.03 ROS0 unused 0xFF Filled Area : OK
009.04 ROS1 Header : OK
009.05 ROS1 Hash : OK
Size = 0x6FFFE0
MD5 = B833A708108360FC7913986E29C29B3E
Version = 4.85 CEX/SEX OFW
009.06 ROS1 unused 0xFF Filled Area : OK
******* Checking cvtrm_region *******
010.01 Pre cvtrm 0xFF Filled Area : OK
010.02 cvtrm0 Header : OK
010.03 cvtrm0 0xFF Filled Area : OK
010.04 vtrm0 Magic : OK
010.05 vtrm0 Reserved Entries : OK
010.07 cvtrm1 Header : OK
010.08 cvtrm1 0xFF Filled Area : OK
010.09 vtrm1 Magic : OK
010.10 vtrm1 Reserved Entries : OK
******* Checking Second_Region_Header *******
011.01 Second Region Header 0x00 Filled Area 0 : OK
011.02 Second Region Header Magic : OK
011.03 Second Region Header Count : OK
011.04 Second Region Header 0x00 Filled Area 1 : OK
011.05 Second Region Unknown Block 0 : OK
011.06 Second Region Header 0x00 Filled Area 2 : OK
011.07 Second Region Unknown Block 1 : OK
011.08 Second Region Header 0x00 Filled Area 3 : OK
******* Checking Unreferenced_Area *******
012.01 unreferenced area 0xFF Filled : OK
******* Checking CELL_EXTNOR_AREA_Region *******
013.01 CELL_EXTNOR_AREA Header : OK
013.02 CELL_EXTNOR_AREA 0x00 Filled Area 0 : OK
013.03 CELL_EXTNOR_AREA 0x00 Filled Area 1 : OK
013.04 CELL_EXTNOR_AREA 0x00 Filled Area 2 : OK
013.05 CELL_EXTNOR_AREA 0x00 Filled Area 3 : OK
013.06 CELL_EXTNOR_AREA 0xFF Filled Area 0 : OK
013.07 CELL_EXTNOR_AREA 0x00 Filled Area 5 : OK
013.08 CELL_EXTNOR_AREA 0x00 Filled Area 6 : OK
013.09 CELL_EXTNOR_AREA 0xFF Filled Area 1 : OK
******* Checking bootldr_region *******
014.01 bootldr0 : OK
014.02 bootldr1 : OK
014.03 bootldr Rev key : OK
014.04 bootldr Statistics : OK
014.05 bootldr 0xFF Filled Area : OK
******* Checking datamatches *******
bootldr size : OK
per console nonce : OK
CELL_EXTNOR_AREA Hash1 : OK
CELL_EXTNOR_AREA Hash2 : OK
metldr size : OK
vtrm0 : OK
vtrm1 : OK
******* Checking repetitions *******
Header Magic0 Repetitions : OK
asecure_loader Repetitions : OK
eEID Repetitions : OK
cISD Repetitions : OK
cCSD Repetitions : OK
trvk_prg0 Repetitions : OK
trvk_prg1 Repetitions : OK
trvk_pkg0 Repetitions : OK
trvk_pkg1 Repetitions : OK
ros0 Repetitions : OK
ros1 Repetitions : OK
cvtrm Repetitions : OK
******* Additional information *******
HDD : TOSHIBA MK8052GSX 98MCFD5VS
MAC address : 00:1F:A7:D1:72:3B
CID : 0x00020138667C
eCID : 01CF0132800C67180A05804000000020
board_id (part of console S/N) : 27438173
kiban_id (board barcode) : 3HFA0091242C
******* Checks completed *******
Total number of checks = 155
Number of dangers = 1
Number of warnings = 0
Following check(s) returned a DANGER!
004.07 metldr Statistics
All checks done in 14.42 seconds.
 
Domi42 said:
:(
sorry my english not GOOD im not continue proces downgrade Not video Not audio Not light working HDD
Click to expand...

Is it the dump you sent me? I think I missed to answer you... sorry for that.
So, your metldr is corrupted with a lot of consecutive 0x00 bytes (you have 2.74% of the metldr data that is 0x00 and that is a lot too much).
That's not fixable if you dont have a dump, from your console, with a good metldr.
 
uploaded it to the server and how should I send you Pw because I wrote you from my email dominikkoc ... @ gmail.com
 
Last edited:
Domi42 said:
92/5000
I don't have a good dump because the metldr is broken and I'm looking for someone to help me fix it the one I shared
Click to expand...
The data in your dump, your console needs is specific to that console only. If that data is corrupted. You probably have a permanent bricked console. Unless someone knows how to recover that data. As far as I know only sony can recover that data or address a new console id to it. Unless @littlebalup has an idea .:D
 
Domi42 said:
I have other discharges where metldr is good from the same model
Click to expand...
Is that a dump from the same console you're trying to fix? You'll have to work with it then, and not the other that has that "danger" warning. You have no other choice. Also, I don't understand, you took a good dumpe using what? And why after you made a dump the console bricked? That's not possible, unless you damage something in the process.
 
ElGris said:
Is that a dump from the same console you're trying to fix? You'll have to work with it then, and not the other that has that "danger" warning. You have no other choice. Also, I don't understand, you took a good dumpe using what? And why after you made a dump the console bricked? That's not possible, unless you damage something in the process.
Click to expand...
Consoles I bought with Damage red screen early death and thanks to E3 flasher it was possible to fix this error by performing a full downgrade on ofw 3.55 and using LV2diag on RSOD and here after the freeze
 
Domi42 said:
Consoles I bought with Damage red screen early death and thanks to E3 flasher it was possible to fix this error by performing a full downgrade on ofw 3.55 and using LV2diag on RSOD and here after the freeze
Click to expand...
So you got it working? RSOD is sometimes an indication that the nor chip is failing,each time u flash a dump the nor can wear out causing bad blocks in the nor chip, if metdlr area in your dump is bad than it's like @littlebalup said earlier it is not fixable, if you didn't make a backup of a good dump first.
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top