[GUIDE] Unbrick a PS3 after an unfortunate PS3Xploit flash

Discussion in 'Tutorials & Guides' started by littlebalup, Dec 16, 2018.

  1. 884
    755
    147
    littlebalup

    littlebalup Developer PSX-Place Supporter

    Joined:
    Oct 16, 2014
    Messages:
    884
    Likes Received:
    755
    Trophy Points:
    147
    Location:
    43°36'16.0"N 1°26'36.1"E
    That guide is a traduction of my french topic here : http://www.logic-sunrise.com/forums...ne-ps3-suite-a-un-flash-ps3xploit-malheureux/

    That guide is for technicians and advanced users having an hardware flasher. It intended to restore a NOR console under "metldr2" having been accidentally flashed via PS3Xploit (v1 or v2), causing a perma-brick. So for some CECH-25xxx, the CECH-3xxxx and CECH-4xxxx NOR (for the 12GB CECH-4xxxx equipped with EMMC, no public tools are available yet to unbrick them.)

    Note : for consoles under "metldr" (jailbreak compatible) bricked using PS3Xploit flash writer over a CFW4.82, dump and flash your NOR or NAND applying regular NO-FSM jailbreak method.




    Case if you previously made a backup with PS3Xploit Dumper:

    Simply flash the NOR with your "dump.hex" backup file and your hardware flasher. (I will not describe the procedure here. There are a lot of tutorials to use E3 flasher, Teensy or Progskeet for those who don't know yet).

    !!WARNING!! If you are using an E3 flasher, you must do a byte swap of your dump before to rename it "bkpps3.bin" and to fash it.

    For that, you can use either FlowRebuilder (http://www.psx-place.com/resources/flow-rebuilder.524/) with the "Byte reverse a dump" operation, or PyPS3patcher (https://github.com/littlebalup/PyPS3tools/tree/master/PyPS3patcher) with the "swap" command.




    Case if you have not previously done a backup with PS3Xploit Dumper:


    1- Dump the NOR with your hardware flasher (I will not describe the dump/flash procedure here. There are a lot of tutorials to use E3 flasher, Teensy or Progskeet for those who don't know yet). In that guide I assume the dumps have been done correctly.
    I highly recommend to use PyPS3checker (https://github.com/littlebalup/PyPS3tools) to check your dump before before going further. Your dump should be good exept a warning on the SKU and maybe one on ROS hash. Ask if you have any doubt.


    2- Download that *.bin file: https://www.dropbox.com/s/ph0gvbh8jljgwk2/CosOFW482.BIN?dl=1
    MD5: DBCE1CCF7E8A64DC2A6C7019E1C03749
    It's the Core OS of the OFW4.82 we will use as ROS patch to overwrite wrongly applied PS3Xploit patches.


    3- Overwrite both ROS of your dump with OFW4.82 CoreOS as patch:

    Using PS3DumpChecker (https://github.com/Swizzy/PS3DumpChecker) :
    - Load your dump. It may be BAD with one bad ROS hash, and maybe also the SKU and or semistatic data (PS3DumpChecker is not fully compatible with 3k and 4k dumps). Don't care as long as you are 100% confident your dump has been done correctly and checked with PyPS3checker.
    - In the PS3DumpChecker options (the small wrench icon at the top left) check the options as shown below. Select the custom patch file "CosOFW482.BIN" you downloaded previously then save.
    [​IMG]

    - Click on "Force Patch" button
    [​IMG]

    - You obtain a new patched dump ready to flash in your NOR.


    Or using PyPS3patcher (https://github.com/littlebalup/PyPS3tools/tree/master/PyPS3patcher) :
    - Paste the file "CosOFW482.BIN" and your dump in the script folder.
    - Rename "CosOFW482.BIN" as "patch.bin".
    - Run the script with the command: patcher.py cust yourdump
    [​IMG]
    - You obtain a new patched dump ready to flash in your NOR.
     
    DeViL303, esc0rtd3w, Algol and 14 others like this.
  2. 84
    11
    12
    Khabibov

    Khabibov Forum Noob

    Joined:
    Nov 7, 2018
    Messages:
    84
    Likes Received:
    11
    Trophy Points:
    12
    Gender:
    Male
    Great job buddy, many thanks :biggrin:
     
    Last edited by a moderator: Dec 17, 2018
  3. 3,403
    2,849
    372
    sandungas

    sandungas Moderator Developer

    Joined:
    Dec 31, 2014
    Messages:
    3,403
    Likes Received:
    2,849
    Trophy Points:
    372
    Location:
    Babylon 20xxE series
    Thread moved to "tutorials & guides" subforum, leaving a permanent (and sticked) redirect
    Now the thread is located here: http://www.psx-place.com/forums/tutorials-guides.60/
    And the permanent sticked redirect is here: http://www.psx-place.com/forums/PS3Xploit/

    Hope you like the changes @littlebalup if you dont we can revert them or modify it again
    @Khabibov i edited your post to remove the part where you was "quoting" the whole tutorial, because this looks like the kind of tutorial that could be improved along time if some people gives some feedback (about things that needs to be explained in a different way, to add more details, etc...)




    Edit:
    Im not telling the tutorial is bad explained... is just im guessing this thread is going to generate lot of posts where you are going to have people with very different skill levels asking for clarifications and details
    All that questions can be considered feedback. The point is if there is someone that doesnt understands "how to do "X" then it means that is a good idea to add more details in the tutorial where is explained "how to do X", even if he original explain was fine, if you find a way to explain the things in a monkey proof way then your tutorial will be much better and probably there will be no more questions about "how to do "X" :)

    Also, i think this thread is important because we (moderators, and frequent forum users) should indicate newcomers with this problem to read and post here, and also eventually the forum mods will move/merge here some posts from other threads
     
    Last edited: Dec 17, 2018
  4. 7
    0
    5
    Davidsu

    Davidsu Forum Noob

    Joined:
    Dec 16, 2018
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    HeyLittlebalup , I have a big problem with my PS3 Slim cech 3001A because I tried to install the 4.82 jailbreak on it and I got a perma brick and the biggest problem I didn't had a clean dump file so, I bought a E3 flasher made a dump of the perma bricked console and I used everything you wrote in your guide it still says bad dump and I can't use the pyps3 patcher, it gives me errors, can you please take a look at my dump file and tell me whats wrong with it? Or what should I do to make it work? Thanks in advance
     

    Attached Files:

  5. 884
    755
    147
    littlebalup

    littlebalup Developer PSX-Place Supporter

    Joined:
    Oct 16, 2014
    Messages:
    884
    Likes Received:
    755
    Trophy Points:
    147
    Location:
    43°36'16.0"N 1°26'36.1"E
    If it's the only semistatic error, your dump seems ok. As said in the guide, PS3DumpChecker is not optimized for 3k and 4k dumps.
     
    Yugonibblit likes this.
  6. 7
    0
    5
    Davidsu

    Davidsu Forum Noob

    Joined:
    Dec 16, 2018
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    Do you have any suggestions why the flashing didn’t work? I left the first switch up on the e3 flasher and down the rest, when I turn on shuts off 1second later.
     
  7. 884
    755
    147
    littlebalup

    littlebalup Developer PSX-Place Supporter

    Joined:
    Oct 16, 2014
    Messages:
    884
    Likes Received:
    755
    Trophy Points:
    147
    Location:
    43°36'16.0"N 1°26'36.1"E
    With the first switch up (flashfun mode), tristate is set to ground. Console should stay turned on unless you missed to connect the SBE point of the E3 clip or linker to the tristate point of the mainboard.
    So, check those connections. If still no success, maybe your E3 is faulty. So you can directly solder a wire between the tristate point and the ground of the mainboard. If no success... it's probably a mainboard component failure.
     
    Yugonibblit likes this.
  8. 7
    0
    5
    Davidsu

    Davidsu Forum Noob

    Joined:
    Dec 16, 2018
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    5
    I flashed the BIN file successfully, I mean first I got an error code for the flasher not sitting on the chip but for the second attempt I managed to flash it and when I tried to turn on see if the system works. It turned off instantly, did I missed a step? installing the OFW while the tristate is connected?
     
  9. 884
    755
    147
    littlebalup

    littlebalup Developer PSX-Place Supporter

    Joined:
    Oct 16, 2014
    Messages:
    884
    Likes Received:
    755
    Trophy Points:
    147
    Location:
    43°36'16.0"N 1°26'36.1"E
    Well I would say the flash is not successfull, even if no error code. Dump again and check new dump. It should be exacty the same as the dump file you flashed. If it's not the case... it's a clip issue.
     
    DeViL303 and Yugonibblit like this.
  10. 2
    0
    5
    michiel edward endraws

    michiel edward endraws Forum Noob

    Joined:
    Dec 20, 2018
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    Gender:
    Male
    thanks for the Tutorial :)
    i have a same problem and have bricked my console
    i have e3 flasher and downloaded all programs except bin file .....link is broken
    so please from where can i download the file CosOFW482.BIN
     
  11. 7,837
    6,458
    647
    bguerville

    bguerville Moderator

    Joined:
    Feb 25, 2015
    Messages:
    7,837
    Likes Received:
    6,458
    Trophy Points:
    647
    Location:
    Earth
    The link is not broken, I just downloaded the file from this URL in 3 different ways to make sure:
    1. from Mobile Firefox
    2. from Mobile Chrome
    3. from the Dropbox Android App.
    I can confirm that all 3 worked perfectly fine.

    Anyway here is an alternate mirror on Mediafire if you have issues with Dropbox.
    https://www.mediafire.com/download/rj3id74dj3rjaly
    MD5: DBCE1CCF7E8A64DC2A6C7019E1C03749
    Remember to check the md5 hash of the file after download, for this kind of job, it's very important to be sure that you are working with clean files. Use a small freeware md5 hash calculator utility on your PC like winmd5 (wwww.winmd5.com).
    Or Google "md5 checksum calculator windows 10" to get more options.
    You can also get md5 calculator apps on smartphone.
     
    Last edited: Dec 21, 2018
    Yugonibblit likes this.
  12. 25
    4
    7
    floky

    floky Forum Noob

    Joined:
    Dec 9, 2018
    Messages:
    25
    Likes Received:
    4
    Trophy Points:
    7
    Gender:
    Male
    and this is a log while I did the backup for the second time

    Code:
    PyPS3checker v0.9.x. Check log.
    Checked file : C:\Users\Floky\Desktop\backup new\bkpps3.bin
    ******* Getting flash type *******
      Flash type : NOR
      Reversed : YES
    ******* Getting SKU identification datas *******
      idps = 0x0C
      metldr0 = 0xF920
      metldr1 = 0x0F8E
      metldrkey = 0x39ECF2D2ACC0E0752248A9F8
      bootldr0 = 0x2EAB
      bootldr1 = 0x2EAB
      bootldrsize = 0x2EAF0
      Matching SKU : WARNING!
       No matching SKU found!
    ******* Getting SDK versions *******
      ROS0 : (unknown)
      ROS1 : (unknown)
    WARNING! : unable to get all versions.
    ******* 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 0x10160 should be less than 0.52%.
        0x00 is 0.93%
    004.08   asecure_loader 0x00 Filled Area : WARNING!
      All bytes from offset 0x10160 to offset 0x2F000 should be 0x00.
      Byte at offset 0x20000 has value : 0xF5
      Subsequent bytes in the range may be wrong as well.
    ******* 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 = C6E142FFF29F5DACDBBF56779C0F32C7
      Version = 3.66 (from factory)
    008.02   trvk_prg0 0xFF filled area : OK
    008.03   trvk_prg1 SCE : OK
    008.04   trvk_prg1 Hash : OK
      Size = 0x2E0
      MD5 = C6E142FFF29F5DACDBBF56779C0F32C7
      Version = 3.66 (from factory)
    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 : WARNING!
      All bytes from offset 0xA0FF0 to offset 0xC0000 should be 0xFF.
      Byte at offset 0xB0000 has value : 0x00
      Subsequent bytes in the range may be wrong as well.
    ******* Checking CoreOS_region *******
    009.01   ROS0 Header : WARNING!
      At offset : 0xC0000
      Actual data (reversed from original) :
       > FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
      Expected data :
       > 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0
    009.02   ROS0 Hash : WARNING!
      Size = 0xFFFFFF
      MD5 = DD0BCBAAC2DBA3224E7DE8595A17E9FF
      Version = (unknown)
    009.03   ROS0 unused 0xFF Filled Area : OK
    009.04   ROS1 Header : WARNING!
      At offset : 0x7C0000
      Actual data (reversed from original) :
       > 00 00 2E AB B1 94 34 A3 3C F1 C8 66 DF 42 0E 50
      Expected data :
       > 00 00 00 00 00 00 00 00 00 00 00 00 00 6F FF E0
    009.05   ROS1 Hash : WARNING!
      Size = 0xC8829C
      MD5 = 5831CD73B3FDB2DABE8A066CD3C2A305
      Version = (unknown)
    009.06   ROS1 unused 0xFF Filled Area : WARNING!
      All bytes from offset 0xEBFFF0 to offset 0xEC0000 should be 0xFF.
      Byte at offset 0xEBFFF0 has value : 0x00
      Subsequent bytes in the range may be wrong as well.
    ******* Checking cvtrm_region *******
    010.01   Pre cvtrm 0xFF Filled Area : WARNING!
      All bytes from offset 0xEBFFF0 to offset 0xEC0000 should be 0xFF.
      Byte at offset 0xEBFFF0 has value : 0x00
      Subsequent bytes in the range may be wrong as well.
    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 : WARNING!
      All bytes from offset 0xF01000 to offset 0xF20000 should be 0xFF.
      Byte at offset 0xF10000 has value : 0x00
      Subsequent bytes in the range may be wrong as well.
    ******* 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 : WARNING!
      All bytes from offset 0xF69C00 to offset 0xF80000 should be 0xFF.
      Byte at offset 0xF70000 has value : 0x00
      Subsequent bytes in the range may be wrong as well.
    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 : WARNING!
      All bytes from offset 0xFA9C00 to offset 0xFC0000 should be 0xFF.
      Byte at offset 0xFB0000 has value : 0x10
      Subsequent bytes in the range may be wrong as well.
    ******* Checking bootldr_region *******
    014.01   bootldr0 : OK
    014.02   bootldr1 : OK
    014.03   bootldr Rev key : OK
    014.04   bootldr Statistics : DANGER!
      Any bytes from offset 0xFC0000 to offset 0xFEEAF0 should be less than 0.5%.
        0xFF is 3.23%
    014.05   bootldr 0xFF Filled Area : DANGER!
      All bytes from offset 0xFEEAF0 to offset 0x1000000 should be 0xFF.
      Byte at offset 0xFF0000 has value : 0x36
      Subsequent bytes in the range may be wrong as well.
    ******* Checking datamatches *******
    bootldr size : OK
    per console nonce : DANGER!
      Following datas should be the same :
      metldr at offset 0x854 length 0xC
       > 0B 42 99 F6 E5 F2 B7 CD 34 8B 7B F1
      eid0 at offset 0x2F084 length 0xC
       > 0B 42 99 F6 E5 F2 B7 CD 34 8B 7B F1
      eid3 at offset 0x302B4 length 0xC
       > 0B 42 99 F6 E5 F2 B7 CD 34 8B 7B F1
      eid5 at offset 0x303E4 length 0xC
       > 0B 42 99 F6 E5 F2 B7 CD 34 8B 7B F1
      bootldr at offset 0xFC0014 length 0xC
       > 8E E1 C8 15 45 89 5A F6 DB C8 82 9C
    CELL_EXTNOR_AREA Hash1 : DANGER!
      Following datas should be the same :
      CELL_EXTNOR_AREA F40000 Hash at offset 0xF40000 length 0x30
       > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
         00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
      CELL_EXTNOR_AREA F80000 Hash at offset 0xF80000 length 0x30
       > 00 00 00 01 00 00 00 2C 6E 47 15 E8 38 9B C8 16
         65 6E 0C 37 54 25 FE 7B 22 9A 31 75 72 22 63 2B
         31 DD 15 AA 60 7D EB F5 F7 A3 74 0B 9D DD 3B 3A
    CELL_EXTNOR_AREA Hash2 : OK
    metldr size : OK
    vtrm0 : OK
    vtrm1 : OK
    ******* Checking repetitions *******
    Header Magic0 Repetitions : OK
    Header Magic1 Repetitions : DANGER!
      Following data (reversed) expected at offset 0xF00010 :
       > 00 00 00 00 0F AC E0 FF 00 00 00 00 DE AD FA CE
      Repetition(s) found at offset(s) :
        0x700010, 0xF10010
    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 : FUJITSU MHZ2160BH G1 K65XT8A2JELK
    MAC address : 28:0D:FC:15:A6:AB
    CID : 0x000202F2085E
    eCID : 01CA04E7811877180C0DB64200000010
    board_id (part of console S/N) : 27459522
    kiban_id (board barcode) : 402008657636
    ******* Checks completed *******
    Total number of checks = 156
    Number of dangers = 6
    Number of warnings = 13
    Following check(s) returned a DANGER!
      004.07   metldr Statistics
      014.04   bootldr Statistics
      014.05   bootldr 0xFF Filled Area
      datamatches : per console nonce
      datamatches : CELL_EXTNOR_AREA Hash1
      repcheck : Header Magic1 Repetitions
    Following check(s) returned a WARNING!
      SKU identification
      SDK versions
      004.08   asecure_loader 0x00 Filled Area
      008.08   trvk_pkg1 0xFF filled area
      009.01   ROS0 Header
      009.02   ROS0 Hash
      009.04   ROS1 Header
      009.05   ROS1 Hash
      009.06   ROS1 unused 0xFF Filled Area
      010.01   Pre cvtrm 0xFF Filled Area
      012.01   unreferenced area 0xFF Filled
      013.06   CELL_EXTNOR_AREA 0xFF Filled Area 0
      013.09   CELL_EXTNOR_AREA 0xFF Filled Area 1
    All checks done in 11.15 seconds.
    IMPORTANT NOTICE:
    Checks of late CECH-25xxx, CECH-3xxxx and CECH-4xxxx consoles dumps still under development! It could return both false positive and false negative results. Please, send me your checklog.txt via my github repository (https://github.com/littlebalup/PyPS3tools/issues) or by mail at [email protected] It will help me a lot to improve checks ;)
     
    Last edited by a moderator: Dec 30, 2018
    Yugonibblit likes this.
  13. 884
    755
    147
    littlebalup

    littlebalup Developer PSX-Place Supporter

    Joined:
    Oct 16, 2014
    Messages:
    884
    Likes Received:
    755
    Trophy Points:
    147
    Location:
    43°36'16.0"N 1°26'36.1"E
    Dump totally bad. metldr and bootldr corrupted (per console data). Can't be fixed as is.
    If you already attempted to flash the NOR like that and if you didn't made a better dump before, your PS3 is dead.
    If you didn't already attempted to flash, you must make a better dump with your E3 before going further. Did you tried the E3 linker instead of the clip?
     
    Yugonibblit and bguerville like this.
  14. 25
    4
    7
    floky

    floky Forum Noob

    Joined:
    Dec 9, 2018
    Messages:
    25
    Likes Received:
    4
    Trophy Points:
    7
    Gender:
    Male
    no..ay not try.. but ay flash that ps3 with another dump.. that is now problem?
     
    Yugonibblit likes this.
  15. 884
    755
    147
    littlebalup

    littlebalup Developer PSX-Place Supporter

    Joined:
    Oct 16, 2014
    Messages:
    884
    Likes Received:
    755
    Trophy Points:
    147
    Location:
    43°36'16.0"N 1°26'36.1"E
    Yes, you lost your per conlole data. Your PS3 is dead...
     
    Yugonibblit and Khabibov like this.
  16. 25
    4
    7
    floky

    floky Forum Noob

    Joined:
    Dec 9, 2018
    Messages:
    25
    Likes Received:
    4
    Trophy Points:
    7
    Gender:
    Male
    :(
     
    Yugonibblit likes this.
  17. 3,403
    2,849
    372
    sandungas

    sandungas Moderator Developer

    Joined:
    Dec 31, 2014
    Messages:
    3,403
    Likes Received:
    2,849
    Trophy Points:
    372
    Location:
    Babylon 20xxE series
    He means the dump is completly corrupted, the most critical areas are the bootldr and metldr because are encrypted using a key that is stored inside CELL processor (and is imposible to know that key), so if you lose bootldr and metldr is completly imposible to regenerate them

    But maybe you misunderstood his answer... what you need to do is to re-attach the flasher and make more dumps until you get a dump with the correct data (that passes the checks of PyPS3checker successfully)
    And... DONT WRITE IN FLASH until you get this dump correctly made


    Edit:
    Now i just realized your has been spreading info about your problem along the forum, and you have made me lost time in trying to help you here while i was not aware of your complete adventure that started here
    www.psx-place.com/threads/bricked-ps3-3004a-please-help.21799
    Im posting this link for other people that are curious, but is something you should have made, not me
    Is too late... but please dont do that, if you want help post all the info together (or add links to everything) but dont post a bit of info here, and another bit there, and another bit somewhere else... etc...
     
    Last edited: Dec 22, 2018
    Yugonibblit likes this.
  18. 25
    4
    7
    floky

    floky Forum Noob

    Joined:
    Dec 9, 2018
    Messages:
    25
    Likes Received:
    4
    Trophy Points:
    7
    Gender:
    Male
    :) ok sorry
     
    Yugonibblit likes this.
  19. 259
    92
    57
    Yugonibblit

    Yugonibblit PSX-Place Supporter

    Joined:
    Jan 25, 2017
    Messages:
    259
    Likes Received:
    92
    Trophy Points:
    57
    Gender:
    Male
    Occupation:
    Mechanic
    Location:
    Uranus
    is this garbage?
     

    Attached Files:

  20. 822
    372
    97
    psykosis

    psykosis Developer Developer

    Joined:
    Dec 7, 2014
    Messages:
    822
    Likes Received:
    372
    Trophy Points:
    97
    To recap the situation:
    1. Minver.pup was never ran (this would have given you the info that you could only use HAN)
    2. The unit was a superslim that was NOT meant for jailbreak (Only HAN)
    3. The unit was never dumped prior to patching
    4. The wrong patch was applied (JB vs HAN)

    After unit was patched, unit no longer worked (BRICK)

    5. The unit was dumped after brick
    6. The dump was known bad from app
    7. Bad dump was again flashed to bricked ps3
    8. Dump was taken again, and came out with errors again
    Was it even checked that the two dumps taken were the same? Console is dead, but clip might be suspect also.

    After this, unit still bricked. littlebaleup verifies dump is not fixable.

    Sorry for your loss, but you kind of walked right into it. These points i'm giving here aren't to bash you, but to clarify points of safety for your next possible endeavor should you so choose. These are things to remember. It is better to learn from the loss.

    I would get a different console, and read as much as you possibly can. Look up every guide you can, and know what they are talking about. Read the comments below the guides for what people run into as problems and make sure you know not only how to avoid it, but how they resolved it. We have a fantastic set of knowledge in this community, and a lot of these guys are super helpful. I've known them to be good people for YEARS.

    We can really only do so much in the end, though. There's always a brick risk, and the more safety steps you skip, the higher that brick risk becomes. Unfortunately, your choices raised your brick risk to 100%. I wouldn't let that discourage you, but rather, use this as a pivotal learning point to never let that happen again.

    This should also be a learning point for other users as well. FOLLOW THE DAMN GUIDES, OR PERIL AWAITS. If you read something, and don't understand it, GOOGLE IS YOUR FRIEND. Keep reading for context, start thinking about what you've read. Apply it, understand what you're reading to the point that you know what's going on. You don't have to be a programmer, or an engineer or an electrical genius. You just have to be careful, meticulous, and perceptive. Have a good day :)
     
Tags:

Share This Page