• PS3 Hacks, Uncategorized , 18.04.2013

    Features:

    • NOR/NAND statistics
    • NOR/NAND patching
    • NOR/NAND byte swapping
    • NOR/NAND infos
    • NOR/NAND validation
    • NOR/NAND extraction
    • DATECODE check

    This tool works different than other validators. Instead of outputing a full log, it will output an error.log, if validate is checked. But see for yourself.

    Always patching 3.55 is recommended to see if the patched statistic is right/green.

    ckp_management_ID values have to be equel as well as per_console_nonce.
    (should be stated in error.log if not)

    There is one easy rule! If the error.log contains an entry, your dump is definetly broken!

    Ros section is excluded from validation. Why? It´s easy to repair, the hole section gets patched anyway and it leads to the rule above.

    For NAND all known sections gets checked. But a big part is not or only rarely documented. So the hole part after cvtrm, cell_ext_os_area, OtherOS and unreferenced area at the end won´t be checked. It´s very important that you have look at the statistics and the “corrupt block count” of flowrebuilder when interleaving.

    It´s always recommended to check dumps manually with an hexeditor, and using other tools for validation, to be as save as possible!
    As long as it is not possible to decrypt the full dump, it`s impossible to validate it to 100%.

    Keep in mind this is only beta. 

    Download
    http://rghost.net/45369360
    http://temp-share.com/show/FHKdyGTU6

    Discuss in Forums (99)


  • 99 Comments

    1. BwE
      04-18-2013
      02:43 AM
      1

      Is this program SHOWING information or VALIDATING information?

      Also, now I have to release my NAND stuff.

    2. DEFAULTDNB
      04-18-2013
      02:47 AM
      2

      Great work [MENTION=207952]sinsizer[/MENTION], thank you

    3. sinsizer
      04-18-2013
      03:02 AM
      3

      [MENTION=114939]BwE[/MENTION]

      NOR validation is mostly complete I think. But NAND only validates till the end of cvtrm and bootldr_1 of cause. (sadly missing over 216MB, and not documented on wiki )
      Also couldn�t find informations about the ECC algo used by flowrebuilder.

      The hole validation is performed in background. I�ve choose an error.log cause most people have no idea what all these values mean. If an error is found it writes it to the log in the following structure: Offset---Value---Region/Area

      Don�t stress yourself, this is only beta. Great work on your validator btw

      Ups..to answer your question. It validates and shows infos. If validate is unchecked it will only show infos.

    4. BwE
      04-18-2013
      03:24 AM
      4

      How does one know what is validated and what isnt? One can not assume EVERYTHING is validated without any proof or documentation.

      I say what I validate and I show it, every single item has its own series of checks. Totaling 2600+ validations throughout the 370+ outputs.

      I hate to sound rude, but I doubt you have that for both NOR & NAND.

      I have validated what you have missed for NAND, its nothing amazing

      Love you <3

    5. euss
      04-18-2013
      03:31 AM
      5

      always good to see people stepping up the plate and share.

      may the best nand validator win

      in the end, with both of them improving, the whole scene wins.

    6. dafank
      04-18-2013
      03:43 AM
      6

      cool app, let's taste it!

    7. sinsizer
      04-18-2013
      03:44 AM
      7

      [MENTION=114939]BwE[/MENTION]
      All necessary checks will be done. Maybe I should write down a list. The "code behind" is important. All "errors" should be recognized. Writing down all areas and puting a hook behind, doesn�t mean it�s valid. It means maybe valid or maybe its only a hook .

      Would be nice if you can provide infos about these NAND areas.

    8. Sarah1331
      04-18-2013
      04:07 AM
      8

      Originally Posted by euss
      always good to see people stepping up the plate and share.

      may the best nand validator win

      in the end, with both of them improving, the whole scene wins.
      I have a few NAND dumps that are bad and loads that are good ill test a few


      Sent from my iPhone 5 using Tapatalk 2

    9. guerrierodipace
      04-18-2013
      04:08 AM
      9

      very nice

    10. Sarah1331
      04-18-2013
      04:19 AM
      10

      I have two Bad NAND dumps and it passes them ill upload them and post a link but the dumps give glod


      Sent from my iPhone 5 using Tapatalk 2

    11. euss
      04-18-2013
      05:10 AM
      11

      to be clear: I meant NAND checker/inspector/validator not NAND dumps!

      be cautious to who you share you dump with, as it will contain a lot of personal data and can get your console banned forever.

    12. Sarah1331
      04-18-2013
      06:38 AM
      12

      Originally Posted by euss
      to be clear: I meant NAND checker/inspector/validator not NAND dumps!

      be cautious to who you share you dump with, as it will contain a lot of personal data and can get your console banned forever.
      Doesn't quite matter if there dead bricks due to bad dumps lol


      Sent from my iPhone 5 using Tapatalk 2

    13. liomajor
      04-18-2013
      07:00 AM
      13

      Originally Posted by BwE
      How does one know what is validated and what isnt?
      Yes, there should be more details on how this works.

      As far i have tested sinsizers tool with broken dumps,
      everything i could imagine was detected and his tool
      is as far i can see solid for nor.

      [MENTION=114939]BwE[/MENTION]

      You show in your tool a lot details, but not everyone can
      understand this much information - sinsizer's rule #1 if the
      error log pops up and shows entrys is easy to understand
      not to use it for flashing

      @ both of you, there is always room for improvement
      and a win win to the scene

    14. BwE
      04-18-2013
      07:04 AM
      14

      Originally Posted by liomajor

      You show in your tool a lot details, but not everyone can
      understand this much information - sinsizer's rule #1 if the
      error log pops up and shows entrys is easy to understand
      not to use it for flashing

      @ both of you, there is always room for improvement
      and a win win to the scene


      all you need to understand is that everything is GOOD and to see WHAT is bad

    15. patastinky
      04-18-2013
      08:14 AM
      15

      Originally Posted by liomajor
      Yes, there should be more details on how this works.

      As far i have tested sinsizers tool with broken dumps,
      everything i could imagine was detected and his tool
      is as far i can see solid for nor.

      [MENTION=114939]BwE[/MENTION]

      You show in your tool a lot details, but not everyone can
      understand this much information - sinsizer's rule #1 if the
      error log pops up and shows entrys is easy to understand
      not to use it for flashing

      @ both of you, there is always room for improvement
      and a win win to the scene
      I appreciate the fact that [MENTION=114939]BwE[/MENTION] shows the entire log. The more details the better. People who don't understand it should look into it. Validating a dump is crucial and I think people who are using them should really read up on what it does. Moreover, know how to manually check the dump.

      The idea that if you have an entry in your log file then you have a bad dump is really simple and neat. However there should also be a log of what has been checked and what the ranges where. The advance user can then look over the extended log and verify for themselves. Also the curious user might want to get a better understanding of their dump and look into it.

      [MENTION=207952]sinsizer[/MENTION] like [MENTION=245343]Sarah1331[/MENTION] i have a few good/bad dumps for both nor/nand that i can use to test. I will report back shortly.
      ************* [ - Post Merged - ] *************
      [MENTION=207952]sinsizer[/MENTION] - I really like your layout. The "info" section is very easy to read. If I may make a suggestion to add a MD5 read on the input file.

    16. playerkp420
      04-18-2013
      08:23 AM
      16

      [MENTION=207952]sinsizer[/MENTION]
      Does this not validate bootldr in Nor dumps?

      I just tested with some valid dumps.

      Then I checked a dump that I know bootldr is incomplete. Size of bootldr is only "C000", when it should be "2F170"

      PS3 NOR/NAND Statistic (Beta) says

      NO ERRORS FOUND!


      BwE's NOR Validator says

      Lv0ldr/Bootldr:
      Encrypted Binary Size - 2F13
      Decrypted Binary Size - 2F13
      Calculated Bootldr Size - 2F170
      Rev Key - F5A221B5C05F214201979DAA (CECH20xx (DYN-001))
      PerConsole Nonce - 91E3EE2209F09F82950A3EAD
      Filled Area

      Lv0ldr/Bootldr Corrupt Sequence Check:
      Corruption found at offset: 0xFCBFFF - [WARNING]

      Lv0ldr/Bootldr Encrypted Statistics:
      Sum: 192880
      Mean: 753.4375
      Std Dev: 1024.74007990931 - [WARNING]
      EDIT - I just noticed BwE's NOR Validator only calculates size of bootldr? But at least it shows the corruption at offset 0xFCBFFF

    17. patastinky
      04-18-2013
      09:04 AM
      17

      [MENTION=207952]sinsizer[/MENTION] I tried loading one of my NAND dumps. I renamed it dump1.bin however when I drag it into the program it says "No valid input file!" The NOR bkkps3.bin loads just fine though. However it looks like [MENTION=211522]playerkp420[/MENTION] is doing a fine job testing that out or you.

      I am running Windows 7 Professional x64

    18. sinsizer
      04-18-2013
      09:11 AM
      18

      [MENTION=16019]patastinky[/MENTION]
      What md5�s do you want to calculate?
      It will only take FULL NAND dumps with both bootldr�s
      And of cause you have to merge the dumps before with flowrebuilder.

      [MENTION=211522]playerkp420[/MENTION]
      Hard to say without seeing the dump. The tool checks both sizes, calculates the the datasize, checks revkey, per console nonce, checks for repetitive bandings 0xFF and the unreferenced area. It�s impossible to know what the data area contains, as long it is encrypted. This makes it hard to check. Seems that I have to add back the entropie calculation.

      Maybe you can upload the dump or the extracted bootldr.

    19. patastinky
      04-18-2013
      09:12 AM
      19

      Originally Posted by sinsizer
      [MENTION=16019]patastinky[/MENTION]
      What md5�s do you want to calculate?
      Calculate the input file.

    20. BwE
      04-18-2013
      09:13 AM
      20

      Statistics is the key as well as understanding the unique corruptions.

    21. playerkp420
      04-18-2013
      09:55 AM
      21

      Originally Posted by sinsizer
      Hard to say without seeing the dump. The tool checks both sizes, calculates the the datasize, checks revkey, per console nonce, checks for repetitive bandings 0xFF and the unreferenced area. It�s impossible to know what the data area contains, as long it is encrypted. This makes it hard to check. Seems that I have to add back the entropie calculation.

      Maybe you can upload the dump or the extracted bootldr.
      I PMd u the dump.
      ************* [ - Post Merged - ] *************
      Originally Posted by BwE
      Statistics is the key as well as understanding the unique corruptions.
      Its not statistics. The bootldr is invalid size.

      I'll send it to you. I think it should of said [DANGER].

      The PS3 is a brick if you flash this dump.

    22. DANNY G
      04-18-2013
      10:02 AM
      22

      May is what the kiban_ID . is please??

    23. sinsizer
      04-18-2013
      10:21 AM
      23

      [MENTION=213286]DANNY G[/MENTION]
      It�s the barcode on the board.
      http://www.ps3devwiki.com/wiki/Flash...a_-_cISD#cISD1

    24. anaria
      04-18-2013
      02:41 PM
      24

      [MENTION=207952]sinsizer[/MENTION] nice tool well done.
      Any plan to port it to linux or osx?

    25. WalangAlam
      04-18-2013
      05:06 PM
      25

      Thanks so much. Another one to make our lives easier :D. Keep up the good work...

    26. BwE
      04-18-2013
      05:11 PM
      26

      Originally Posted by playerkp420
      I PMd u the dump.

      Its not statistics. The bootldr is invalid size.

      I'll send it to you. I think it should of said [DANGER].

      The PS3 is a brick if you flash this dump.
      Hello,

      I of Betterway Electronics Australia would like to thank you using my program to assist in your validations today.

      If you would bare witness to the output details you can see the root of the issue at offset FCBFFF. While it says it is a warning, that is correct as for the detection has detected a sequence not common with encryption. In this case that sequence is a rather extremely large set of 00.

      It will say warning because this is the only corruption sequence. This output I will deliberate on and I may adjust in the future to detect unusually or dangerously LARGE sequences.

      However if you would have a look at the statistics provided with the dump: Std Dev: 1024.74007990931 - this shows the shows how much variation or dispersion exists from the average. Commonly the standard deviation is around 24-29 - you have 1,204. This is a clear indication of danger.

      But my program says its a warning (which is true). I understand this may be confusing and thus this is a problem that will be changed in the next version. Future revisions will subsequently alert you if the statistics are WELL BEYOND the predicted ranges rather than just not matching them.

      Thank you for your participation and attribution to the success of the BwE NOR Validator


      -BwE

    27. playerkp420
      04-18-2013
      05:50 PM
      27

      Originally Posted by BwE
      Hello,

      I of Betterway Electronics Australia would like to thank you using my program to assist in your validations today.

      If you would bare witness to the output details you can see the root of the issue at offset FCBFFF. While it says it is a warning, that is correct as for the detection has detected a sequence not common with encryption. In this case that sequence is a rather extremely large set of 00.

      It will say warning because this is the only corruption sequence. This output I will deliberate on and I may adjust in the future to detect unusually or dangerously LARGE sequences.

      However if you would have a look at the statistics provided with the dump: Std Dev: 1024.74007990931 - this shows the shows how much variation or dispersion exists from the average. Commonly the standard deviation is around 24-29 - you have 1,204. This is a clear indication of danger.

      But my program says its a warning (which is true). I understand this may be confusing and thus this is a problem that will be changed in the next version. Future revisions will subsequently alert you if the statistics are WELL BEYOND the predicted ranges rather than just not matching them.

      Thank you for your participation and attribution to the success of the BwE NOR Validator


      -BwE
      Thanks for the explicit explanation. Obviously when I see a warning, I manually check the offset the warning is at.

      What my question is: Why does your validator say "Calculated Bootldr Size - 2F170 "

      When bootldr is not 2F170 in size

      The bootldr is C000 in size.

      This is blatantly obvious if you extract the dump with flowrebuilder. And see that bootldr is only 48KB, instead of 189KB.

      Is there not a way to validate the actual size of bootldr, without extracting it with flowrebuilder?

      Does your validator just make an estimated guess of the size?

      I am not knocking your validator at all. I am just curious.
      Yours is the ONLY one, that actually says something is wrong with the dump.
      Nor Inspector has all green "OK"s.
      and
      PS3 NOR/NAND Statistic (Beta) says "NO ERRORS FOUND!"

      I would highly recommend users extracting their dumps with flowrebuilder. And check the sizes of metldr and bootldr manually.

    28. BwE
      04-18-2013
      06:13 PM
      28

      Originally Posted by playerkp420
      Thanks for the explicit explanation. Obviously when I see a warning, I manually check the offset the warning is at.

      What my question is: Why does your validator say "Calculated Bootldr Size - 2F170 "

      When bootldr is not 2F170 in size

      The bootldr is C000 in size.

      This is blatantly obvious if you extract the dump with flowrebuilder. And see that bootldr is only 48KB, instead of 189KB.

      Is there not a way to validate the actual size of bootldr, without extracting it with flowrebuilder?

      Does your validator just make an estimated guess of the size?
      Its basing it on information present within the dump. If I were to put that information into a writing sequence, it would produce a 189kb file. The corruption is counted and so is the entire bootldr.

      Flowrebuilder stops writing the file when it hits the 00's - meaning its not giving you the full extracted file, hence the lower size.

      When my validator extracts, it doesn't stop.

      So technically my program does tell you the size, including the corruption.

    29. haz367
      04-18-2013
      06:23 PM
      29

      Originally Posted by playerkp420

      Is there not a way to validate the actual size of bootldr, without extracting it with flowrebuilder?
      yes we can..

      You can check metldr and bootldr sizes easily with HxD

      either after extracting flash with Flowrebuilder and opening seperate files
      or by looking in the unextracted Flash dump at the correct offset.
      http://www.ps3devwiki.com/wiki/File:Bootldr_0.png

      calculate manually it as : (header * 0x10) + 0x40 = size.

      Code:
      example: CECHL04 - size bootloader_0 = 2EAF0
      header = 2EAB * 10 + 40 = 2EAF0 = 191216 bytes

    30. BwE
      04-18-2013
      06:25 PM
      30

      Originally Posted by haz367
      yes we can..



      http://www.ps3devwiki.com/wiki/File:Bootldr_0.png

      calculate manually it as : (header * 0x10) + 0x40 = size.

      Code:
      example: CECHL04 - size bootloader_0 = 2EAF0
      header = 2EAB * 10 + 40 = 2EAF0 = 191216 bytes
      thats the way to go!

      Lv0ldr/Bootldr:
      Encrypted Binary Size - 2F13 ✔
      Decrypted Binary Size - 2F13 ✔
      Calculated Bootldr Size - 2F170 ✔
      Lv0ldr/Bootldr Encrypted Statistics:
      Sum: 192880 ✔
      I dont plaster numbers around for no reason!

      ps3devwiki ftw

    31. haz367
      04-18-2013
      06:39 PM
      31

      yup all credits to ps3devwiki, it's like a huge forest...u need to trow some peanuts arround or else u can get lost easy... great collection of tools for checking lately..keep it up guys and thx for sharing...let's not hope bwe gets bored later

    32. playerkp420
      04-18-2013
      06:41 PM
      32

      Thanks, that makes more sense now.

      Great job on the tools. I'll keep testing them.

    33. BwE
      04-18-2013
      06:46 PM
      33

      Originally Posted by haz367
      let's not hope bwe gets bored later
      I'm always bored.

      [MENTION=211522]playerkp420[/MENTION]

      You should have never doubted me

    34. sinsizer
      04-18-2013
      07:37 PM
      34

      [MENTION=41726]anaria[/MENTION]
      Linux and OSX ports are not planed. You can build Linux and OSX ports for yourself if you want. It�s an .NET app not obfuscated. You can easylie convert back the source from the IL. It�s more or less only a bunch of array copies, comparisons, loops and some small calculations.
      Or you could wait for the official release with source in a few days or weeks.

    35. anaria
      04-19-2013
      01:03 AM
      35

      Originally Posted by sinsizer
      [MENTION=41726]anaria[/MENTION]
      Linux and OSX ports are not planed. You can build Linux and OSX ports for yourself if you want. It�s an .NET app not obfuscated. You can easylie convert back the source from the IL. It�s more or less only a bunch of array copies, comparisons, loops and some small calculations.
      Or you could wait for the official release with source in a few days or weeks.
      Ah I'm not a big fan of C# but at least it's go to see an open releaseout.
      I've been very lazy working on my side so I don't know if I'll go deeper here but I'm sure many would appreciate your sharing and hopefully some may give a look.
      Again great work

      Sent from a big sh.ty samsung...

    36. pinkfloydviste
      04-29-2013
      06:34 PM
      36

      I have a similar question regarding my BwE Nor Validator Output file. Everything checks out except the part below which gives me a warning. I'm a bit new to this, so what can I do to ensure I have a good dump? I've already used PS3 NOR/NAND Statistic and NorInspector, and visually inspected it by following a few different guides on the net. I also looked at the bootldr size and that checked out. Thanks for your time.

      Lv0ldr/Bootldr Corrupt Sequence Check:
      Corruption found at offset: 0xFD08BE - [WARNING]
      Corruption found at offset: 0xFE5FC0 - [WARNING]

    37. playerkp420
      04-29-2013
      08:06 PM
      37

      Originally Posted by pinkfloydviste
      I have a similar question regarding my BwE Nor Validator Output file. Everything checks out except the part below which gives me a warning. I'm a bit new to this, so what can I do to ensure I have a good dump? I've already used PS3 NOR/NAND Statistic and NorInspector, and visually inspected it by following a few different guides on the net. I also looked at the bootldr size and that checked out. Thanks for your time.

      Lv0ldr/Bootldr Corrupt Sequence Check:
      Corruption found at offset: 0xFD08BE - [WARNING]
      Corruption found at offset: 0xFE5FC0 - [WARNING]
      Extract with flowrebuilder. Look in the folder it makes for bootloader. Open bootldr with HxD and check the size, header, compare with this chart: http://www.ps3devwiki.com/wiki/Valid...Bbootldr_sizes

      If flowrebuilder gives an error, then the dump is bad (sometimes won't give error and dump is bad also). You can also tell if bootldr is corrupt, by the size of it after you extract with flowrebuilder. If it is not around 189KB. Like if it is only 45KB or 0KB, you know the dump is bad.

    38. BwE
      04-29-2013
      08:17 PM
      38

      Originally Posted by pinkfloydviste
      I have a similar question regarding my BwE Nor Validator Output file. Everything checks out except the part below which gives me a warning. I'm a bit new to this, so what can I do to ensure I have a good dump? I've already used PS3 NOR/NAND Statistic and NorInspector, and visually inspected it by following a few different guides on the net. I also looked at the bootldr size and that checked out. Thanks for your time.

      Lv0ldr/Bootldr Corrupt Sequence Check:
      Corruption found at offset: 0xFD08BE - [WARNING]
      Corruption found at offset: 0xFE5FC0 - [WARNING]
      My program checks for corruption, this is sometimes very difficult to check with just your eyes.

      Go to the offsets and report back what's on the row.

      As you have more than 2, both far apart - I fear the worst.

      [MENTION=211522]playerkp420[/MENTION]

      what the hell?

      that has nothing to do with it, also i think i explained to you or somebody else that flowrebuilder gives out a smaller file size when it detects empty space (it will stop writing the file, thus its shorter) so technically analysing the size from within the dump is useless unless for some rare reason that specific offset is corrupt.

    39. playerkp420
      04-29-2013
      08:30 PM
      39

      Originally Posted by BwE
      My program checks for corruption, this is sometimes very difficult to check with just your eyes.

      Go to the offsets and report back what's on the row.

      As you have more than 2, both far apart - I fear the worst.

      [MENTION=211522]playerkp420[/MENTION]

      what the hell?

      that has nothing to do with it, also i think i explained to you or somebody else that flowrebuilder gives out a smaller file size when it detects empty space (it will stop writing the file, thus its shorter) so technically analysing the size from within the dump is useless unless for some rare reason that specific offset is corrupt.
      I haven't seen flowrebuilder not stop writing the the file, when it was corrupt. More than likely it will stop at the corruption and it will appear smaller in the extract.

    40. BwE
      04-29-2013
      09:21 PM
      40

      Originally Posted by playerkp420
      I haven't seen flowrebuilder not stop writing the the file, when it was corrupt. More than likely it will stop at the corruption and it will appear smaller in the extract.
      Thats what I said

    41. pinkfloydviste
      04-29-2013
      09:40 PM
      41

      [MENTION=211522]playerkp420[/MENTION]

      I double posted (I should know better.) Here's where I posted my response:

      it won't let me post a link, but it is in the dump checking thread.

    42. baileyscream
      05-25-2013
      04:46 PM
      42

      [MENTION=207952]sinsizer[/MENTION]
      with this now in the verify page of the wiki will your updates be posted there or do you have an alternative release address?
      just wanting a permanent link so people can check they have the latest version.

      also what does your tool require to run? after restoring my laptop yours nolonger runs. no errors. nothing. i dubble click it and nothing happens.

      i have the latest flash player installed as BwE's needed that updating to run without freezing. but no change to yours after it installed.
      any ideas? if not i will keep trying to find the issue.

      (oh this is win xp 32x. not tried it in win 7 yet)

    43. sinsizer
      05-25-2013
      09:30 PM
      43

      [MENTION=177623]baileyscream[/MENTION]
      I�m not expecting many updates. NAND validation is still not complete and probably won�t be in any of the tools out now. I added only a few things to NOR Validation. An updater is not needed IMO. I�m going to release it with the source, so anyone can change it to his own needs. You will find it in this thread or a new one when I got time.

      You need to install the latest .NET Framework to be able to run it.
      I think with .NET 4.5 winXP support was dropped. If so I compile it with a lower version next time.

    44. alimadhi
      07-16-2013
      03:05 AM
      44

      nice software

    45. sinsizer
      07-27-2013
      06:14 AM
      45

      UPDATE

      - added 4.46 patches
      - some small changes

      Download:
      http://rghost.net/47703650

      Source:
      http://rghost.net/47703752

      Feel free to modify or recode the tool for your own needs.

    46. playerkp420
      07-27-2013
      05:08 PM
      46

      Originally Posted by sinsizer
      UPDATE

      - added 4.46 patches
      - some small changes

      Download:
      http://rghost.net/47703650

      Source:
      http://rghost.net/47703752

      Feel free to modify or recode the tool for your own needs.
      I noticed on some phat models, it shows this:

      OFFSET: 0xF00896 --- VALUE: 0x20 --- 0x00 BLANK AREA
      OFFSET: 0xF20020 --- VALUE: 0x000002000000004000000000 --- CELL_EXTNOR_AREA
      The dumps are valid, and match the wiki flash page. IDK?

    47. Nicolas19
      07-27-2013
      05:25 PM
      47

      Originally Posted by sinsizer
      UPDATE

      - added 4.46 patches
      - some small changes

      Download:
      http://rghost.net/47703650

      Source:
      http://rghost.net/47703752

      Feel free to modify or recode the tool for your own needs.
      waiting for new version of PS3 Flash Tool

    48. sinsizer
      07-28-2013
      06:39 AM
      48

      [MENTION=211522]playerkp420[/MENTION]
      Thx.
      OFFSET: 0xF00896 --- VALUE: 0x20 --- 0x00 BLANK AREA <--this is not normal, but it doesn�t brick your console.
      OFFSET: 0xF20020 --- VALUE: 0x000002000000004000000000 --- CELL_EXTNOR_AREA <--- you can find this check in line 1522, add this value or delete the check.

      [MENTION=213427]Nicolas19[/MENTION]
      ???

      [EDIT]
      fixed:
      Binary: http://rghost.net/47726473
      Source: http://rghost.net/47726545

    49. sinsizer
      08-13-2013
      06:04 PM
      49



      Changelog
      * minor changes to the GUI (allows adding new patches to the patch folder)

      Thx to [MENTION=207545]3absiso[/MENTION] and [MENTION=256989]ChazLJ[/MENTION] for testing

      Download


      How to extract the patch file for future CFW�s (extracting/decrypting coreOS)

      Tools:
      Download

      Extract CORE_OS_PACKAGE.pkg with pupview.exe from the firmware.pup.



      unpack/decrypt the CORE_OS_PACKAGE.pkg with fwpkg.exe



      Copy the new file to the patch folder.

      IMPORTANT!
      You have to use "ros" somewhere in the name. Otherwise it doesn�t get recognized as patch.

    50. baileyscream
      09-23-2013
      04:45 AM
      50

      i still had your original release lol
      is the link in the first post of this thread updated for the latest version or is that the original one
      just going to add a link back to this thread for ppl to check there up to date.

      and 1 more little thing

      on net books with max res of 1024 x 600 the bottom of the statistics is off screen
      there is no way to see the bottom so i was wondering if you could:-
      put the option tick boxes under the first tab
      and the results under the second tab
      this way the GUI could be smaller on the smaller res net books


    51. sinsizer
      09-24-2013
      05:54 AM
      51

      [MENTION=177623]baileyscream[/MENTION]
      I wasn�t expecting someone working on low resolutions.
      I will fix this as soon I got time.

    52. baileyscream
      09-24-2013
      05:59 AM
      52

      Originally Posted by sinsizer
      [MENTION=177623]baileyscream[/MENTION]
      I wasn�t expecting someone working on low resolutions.
      I will fix this as soon I got time.
      It's the new net books there getting more common
      But have low res
      I suppose old win xp pc's may have the same issue

      But anyway cheers it will be much appreciated

    53. sinsizer
      09-24-2013
      07:49 AM
      53

      [MENTION=177623]baileyscream[/MENTION]
      Ignore the rootkey box and the more tab. It has no functionality in this version.
      I�ve removed the statistic. It causes more confusion than it helps. Maybe it�s usfull only for NAND, as long as remapping is missing.
      I think I should rename it now. lol



      Let me know how it fits.
      Download

    54. baileyscream
      09-24-2013
      08:09 AM
      54

      [MENTION=207952]sinsizer[/MENTION]
      that's a lot better thank you

      does this display normally on normal res monitors?
      if it does I will just keep this one in the guide
      if it doesn't I will put both in & let the user decide

      ps
      I don't think you should re-name it
      I quite like it

    55. sinsizer
      09-24-2013
      08:12 AM
      55

      [MENTION=177623]baileyscream[/MENTION]
      It displays the same on any PC.

    56. baileyscream
      09-24-2013
      08:26 AM
      56

      thank you

      I will change the validator images and re-upload.

      thanks for doing the changes for me
      its really appreciated

    57. baileyscream
      09-24-2013
      10:45 AM
      57

      [MENTION=207952]sinsizer[/MENTION]
      my first issue is back again
      I carnt drop a merged dump into the tool (I don't have a nor dump to check with atm just nand)
      can you check at your side please

    58. sinsizer
      09-24-2013
      10:56 AM
      58

      [MENTION=177623]baileyscream[/MENTION]
      I already did, but I can�t reproduce it. It works fine with the dump you sent me. win7 and win8.
      Make sure you drop it to the labeled field, not on the exe itself, it doesn�t take command line arguments. Also make sure you have the latest .NET Framework installed.

      The only thing I can think of, is that the machine runs out of memory and the tool stops working. I messured a peak of more than 600MB of ram usage with NAND dumps.

    59. baileyscream
      09-24-2013
      11:14 AM
      59

      When your holding the dump in the GUI you get that crossed out circle on the mouse pointer.
      That stays like that even over the box marked drag n drop dumps here

      Try n drop it n nothing happens

      Just re checked with the version before this and that one lets me

      Very strange
      Also found a nor dump and same with that.
      It's as if the box for dropping the dumps into isn't really there

      I'm going to be able to try this on another proper sized laptop in 10 min to make sure it works on that. I carnt see why not lol

    60. sinsizer
      09-24-2013
      11:27 AM
      60

      [MENTION=177623]baileyscream[/MENTION]
      Ah, now I understand.
      This is definitely OS related. There is something wrong with your user/admin privilegs.
      Make sure you have set the correct privilegs. There is no need to run the tool with admin privs.

    61. baileyscream
      09-24-2013
      11:33 AM
      61

      Originally Posted by sinsizer
      [MENTION=177623]baileyscream[/MENTION]
      Ah, now I understand.
      This is definitely OS related. There is something wrong with your user/admin privilegs.
      Make sure you have set the correct privilegs. There is no need to run the tool with admin privs.
      erm .... oops
      lol yea that was it
      cheers lol

    62. baileyscream
      09-24-2013
      02:36 PM
      62

      right this is your validator done
      just give it a check and see if you want me to mention anything else

      this one is from the NANDway guide

      [spoiler=Check your dump with sinsizer_NOR_NAND_Statistic]
      open sinsizer_NOR_NAND_Statistic



      1. put the original dump into the sinsizer_NOR_NAND_Statistic folder
      then click on dumpstatistic to open it



      2. if you want to patch the dump now then make the selection from the above box.
      once you have selected your patch then tick the Progskeet / TEENSY box.

      if you don't want to patch or you have a patched dump created from one of the other validators then just leave this as it is.



      3 Now drag and drop dump.joined.bin into the box as shown




      4 after a short moment you will be shown some basic results on this screen
      Ignore the eid root key and the more tab as these have no functionality in this build


      5 there are more results under the info tab

      if you get no errors in a pop up then you have a good dump to this point.
      if you get any errors then patch the dump if you haven't already. and see if it solves the errors
      if not then save your error log and investigate the area(s) in the next validate step.

      once you have checked everything being displayed is green you can close this tool



      6 if you ticked one of the patch options then you will now find this in the same folder.
      if you wish to use this patched dump then move it to the dumps folder.



      if you recived a bad dump then re-dump and start again.
      if you recived a good dump then carry on to the next step

      Please note this from sinsizer:-

      Originally Posted by sinsizer
      Patching and validating again is not needed with the tool. Areas which get patched are excluded from validation.
      Important infos can be found in the first post.(FOUND HERE) NAND validation is not very reliable, due to missing remapping and ECC algo. Always keep an eye on the badblock count from flowrebuilder. etc.
      I can only guarantee for NOR validation.
      It would be good to mention that eid root key and the more tab has no functionality in this build.
      I don�t want people to be confused about it

      I would also recommend installing 3.55 rogero/rebug after patching and flashing.
      Grabbing the eid root key with flatz RKdumper and updating to CFW4.46.
      This allows eid decryption, HDD recovery, c2d and setting the QAflags via toggleQA.
      The last sentence he refers to eid decription, HDD recovery, c2d is not something I have looked into.
      so if you think it may be of interest to you then please search the forums.
      please don't ask me as I cannot help with this as yet.
      [/spoiler]

    63. sinsizer
      09-24-2013
      11:59 PM
      63

      [MENTION=177623]baileyscream[/MENTION]
      Looks good so far.
      Patching and validating again is not needed with the tool. Areas witch get patched are excluded from validation.
      Important infos can be found in the first post. NAND validation is not very reliable, due to missing remapping and ECC algo. Always keep an eye on the badblock count from flowrebuilder. etc.
      I can only guarantee for NOR validation.
      It would be good to mention that eid root key and the more tab has no functionality in this build.
      I don�t want people to be confused about it

      I would also recommend installing 3.55 rogero/rebug after patching and flashing.
      Grabbing the eid root key with flatz RKdumper and updating to CFW4.46.
      This allows eid decryption, HDD recovery, c2d and setting the QAflags via toggleQA.

    64. sinsizer
      10-04-2013
      07:01 AM
      64

      Update

      The tool patches now ros and rvk if a corresponding rvk patch is placed in the patch folder.
      If no rvk patch is found, it will only patch ros.

      Naming convention for patch files:
      ros_whatever_without_extension1
      rvk_nor_whatever_without_extension1
      rvk_nand_whatever_without_extension2

      In the example you can see that it will patch ros and rvk for nor.
      For nand it will patch only ros, because the revoke patch has another name.
      All patch files have to begin with the red names.

      The tool will be released without patch files from now on.
      You can download the patchfiles here:
      http://ps3coredump.eu5.org/

      In future updates a small downloader will be integrated, as well as some other features regarding c2d and keyextraction from eid.

      PS3 NOR/NAND Statistic
      Download

    65. guerrierodipace
      10-04-2013
      07:05 AM
      65

      download link isn't good.

    66. playerkp420
      10-04-2013
      07:13 AM
      66

      The download works, but the .rar will not open. I get "The archive is either unknown format or damaged" error.

    67. sinsizer
      10-04-2013
      07:15 AM
      67

      [MENTION=13274]guerrierodipace[/MENTION] [MENTION=211522]playerkp420[/MENTION]
      Replaced the link. It�s now 7zip.

    68. guerrierodipace
      10-04-2013
      07:19 AM
      68

      with rar5 works, but probably it's better to use a more common compression version

    69. baileyscream
      10-04-2013
      02:21 PM
      69

      Originally Posted by sinsizer
      How to extract the patch file for future CFW�s (extracting/decrypting coreOS)

      Tools:
      Download

      Extract CORE_OS_PACKAGE.pkg with pupview.exe from the firmware.pup.



      unpack/decrypt the CORE_OS_PACKAGE.pkg with fwpkg.exe



      Copy the new file to the patch folder.

      IMPORTANT!
      You have to use "ros" somewhere in the name. Otherwise it doesn�t get recognized as patch.
      OK so how do you change this from 4.50
      Code:
      decrypted_core_os_package
      Metadata Key:	A6 65 83 05 64 CC BB 77 E7 0F 5E 63 C6 25 AB FC 
      Metadata IV:	45 6A 21 36 A5 7E 40 34 87 6C 31 B4 7C C7 DF E9 
      Metadata Size:	544 bytes
      Data Start:	0x00000300
      Data Size:	5898612 bytes (5.63 MB)
      PKG Key:	35 53 B4 B5 44 28 FE 09 5A 04 E5 38 E8 38 F4 A6 
      PKG IV:		5D 24 FA B1 E0 55 F4 58 15 22 C2 73 00 00 00 00 
      PKG Size:	7340000 bytes (7.00 MB)
      into the patch file i'm lost at that bit after opening the 4.46 patch file
      im sure its simple but I just don't see it
      **************************edit***************************
      never mind I figured it out
      I have 4.50 patch now

      just need to test it and see if it works or not

      btw the one I just made is the exact same size as the 3.55 patch and rogero 4.46 patch

    70. sinsizer
      10-04-2013
      03:02 PM
      70

      [MENTION=177623]baileyscream[/MENTION]
      I�ve uploaded [MENTION=272323]Smhabib[/MENTION] 4.50 coreOS already to the site.
      If you follow the tut you already have the patch file.
      Filesize is always the same.

    71. baileyscream
      10-04-2013
      03:13 PM
      71

      Originally Posted by sinsizer
      [MENTION=177623]baileyscream[/MENTION]
      I�ve uploaded [MENTION=272323]Smhabib[/MENTION] 4.50 coreOS already to the site.
      If you follow the tut you already have the patch file.
      Filesize is allways the same.
      thanks I will compare that to what I have so I can be sure I have it right

      to be honest I just wanted to figure it out.

      its one thing blindly using whats there. supplied by others.
      but its another to actually know what it actually is and how its done in the first place

      by doing this I understand now what the patch file is
      I allways thought it was just a few lines that were changed I didn't actually realise it was the whole coreos that was replaced

    72. sinsizer
      10-04-2013
      04:05 PM
      72

      [MENTION=177623]baileyscream[/MENTION]
      Yes, the hole operating system gets replaced.
      This is why I don�t validate the files.
      If you install a FW(pup), the coreOS gets written to the flash. We can�t sign cfw properly, and the console denies install. So we use the "hard way" to place the OS in the flash.

    73. baileyscream
      10-04-2013
      04:18 PM
      73

      the habib 4.50 patch is different to the ofw patch file I made
      is his from his cfw or from the ofw?

      I assumed you placed the ofw coreos as the patch but is it supposed to be from the cfw?

      also the ps3coredump site the files download as .txt not as .file

      and unfortunately the new update doesn't run for me
      it just gives me a "this program has stopped working" error

    74. sinsizer
      10-04-2013
      04:28 PM
      74

      [MENTION=177623]baileyscream[/MENTION]
      It�s the coreOS from his new CFW. It would make no sense to replace the ofw os with ofw os. The download works fine for me. Simply don�t save it as *.txt. (No extension)
      The tool works also fine for me.

    75. baileyscream
      10-04-2013
      04:52 PM
      75

      Originally Posted by sinsizer
      [MENTION=177623]baileyscream[/MENTION]
      It�s the coreOS from his new CFW. It would make no sense to replace the ofw os with ofw os. The download works fine for me. Simply don�t save it as *.txt. (No extension)
      The tool works also fine for me.
      yea It would be pointless.
      I have fixated on getting the coreos out of the 4.50ofw since it was released I didn't think twice that I actually should have been using cfw lol.

      just re-downloaded the tool again but it just wont start the prev one works just fine but for somereason the new one doesn't. tried without admin / with admin / as winxp compat mode just the same
      ************* [ - Post Merged - ] *************
      don't know if this will help
      these are the error reports
      [spoiler]WER3F21.tmp.WERInternalMetadata.xml[spoiler]<?xml version="1.0" encoding="UTF-16"?>
      -<WERReportMetadata>-<OSVersionInformation><WindowsNTVersion>6.1</WindowsNTVersion><Build>7601 Service Pack 1</Build><Product>(0xb): Windows 7 Starter</Product><Edition>Starter</Edition><BuildString>7601.18205.x86fre.win7sp1_gdr.130708-1532</BuildString><Revision>1130</Revision><Flavor>Multiprocessor Free</Flavor><Architecture>X86</Architecture><LCID>1033</LCID></OSVersionInformation>-<ParentProcessInformation><ParentProcessId>1592</ParentProcessId><ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath><ParentProcessCmdLine>"C:\Windows\Explorer.exe"</ParentProcessCmdLine></ParentProcessInformation>-<ProblemSignatures><EventType>CLR20r3</EventType><Parameter0>dumpstatistic.exe</Parameter0><Parameter1>1.0.0.0</Parameter1><Parameter2>524c3a0e</Parameter2><Parameter3>mscorlib</Parameter3><Parameter4>4.0.0.0</Parameter4><Parameter5>517a1c71</Parameter5><Parameter6>3fde</Parameter6><Parameter7>105</Parameter7><Parameter8>System.IO.DirectoryNotFound</Parameter8></ProblemSignatures>-<DynamicSignatures><Parameter1>6.1.7601.2.1.0.768.11</Parameter1><Parameter2>2057</Parameter2><Parameter22>0a9e</Parameter22><Parameter23>0a9e372d3b4ad19135b953a78882e789</Parameter23><Parameter24>0a9e</Parameter24><Parameter25>0a9e372d3b4ad19135b953a78882e789</Parameter25></DynamicSignatures>-<SystemInformation><MID>DC7F33F6-935B-4FFE-85DD-7F4E3F405743</MID><SystemManufacturer>ASUSTeK Computer INC.</SystemManufacturer><SystemProductName>1005HA</SystemProductName><BIOSVersion>1401</BIOSVersion></SystemInformation></WERReportMetadata>[/spoiler]WER58C9.tmp.appcompat.txt[spoiler]<?xml version="1.0" encoding="UTF-16"?>
      <DATABASE>
      <EXE NAME="dumpstatistic.exe" FILTER="CMI_FILTER_PRIVACY">
      <MATCHING_FILE NAME="dumpstatistic.exe" SIZE="119296" CHECKSUM="0xBE8CBDD1" BIN_FILE_VERSION="1.0.0.0" BIN_PRODUCT_VERSION="1.0.0.0" PRODUCT_VERSION="1.0.0.0" FILE_DESCRIPTION="dumpstatistic" PRODUCT_NAME="dumpstatistic" FILE_VERSION="1.0.0.0" ORIGINAL_FILENAME="dumpstatistic.exe" INTERNAL_NAME="dumpstatistic.exe" LEGAL_COPYRIGHT="Copyright � 2013" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="1.0.0.0" UPTO_BIN_PRODUCT_VERSION="1.0.0.0" LINK_DATE="10/02/2013 15:21:50" UPTO_LINK_DATE="10/02/2013 15:21:50" VER_LANGUAGE="Language Neutral [0x0]" EXE_WRAPPER="0x0" />
      </EXE>
      <EXE NAME="KERNELBASE.dll" FILTER="CMI_FILTER_THISFILEONLY">
      <MATCHING_FILE NAME="KernelBase.dll" SIZE="293376" CHECKSUM="0x85737E43" BIN_FILE_VERSION="6.1.7601.18229" BIN_PRODUCT_VERSION="6.1.7601.18229" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft� Windows� Operating System" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="Kernelbase" INTERNAL_NAME="Kernelbase" LEGAL_COPYRIGHT="� Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4A119" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.18229" UPTO_BIN_PRODUCT_VERSION="6.1.7601.18229" LINK_DATE="08/02/2013 01:52:06" UPTO_LINK_DATE="08/02/2013 01:52:06" EXPORT_NAME="KERNELBASE.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" FILE_ID="0000d9391d1f8f9c2cc785ca1e021b614c3f341f674f" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
      </EXE>
      <EXE NAME="kernel32.dll" FILTER="CMI_FILTER_THISFILEONLY">
      <MATCHING_FILE NAME="kernel32.dll" SIZE="868352" CHECKSUM="0x49E286F8" BIN_FILE_VERSION="6.1.7601.18229" BIN_PRODUCT_VERSION="6.1.7601.18229" PRODUCT_VERSION="6.1.7601.18015" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft� Windows� Operating System" FILE_VERSION="6.1.7601.18015 (win7sp1_gdr.121129-1432)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="� Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xE1B0B" LINKER_VERSION="0x60001" UPTO_BIN_FILE_VERSION="6.1.7601.18229" UPTO_BIN_PRODUCT_VERSION="6.1.7601.18229" LINK_DATE="08/02/2013 01:52:05" UPTO_LINK_DATE="08/02/2013 01:52:05" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" EXE_WRAPPER="0x0" FILE_ID="000070b8460dc96f914709b34ae76638261475e94005" PROGRAM_ID="0000f519feec486de87ed73cb92d3cac802400000000" />
      </EXE>
      </DATABASE>
      [/spoiler][/spoiler]

    76. sinsizer
      10-04-2013
      05:15 PM
      76

      [MENTION=177623]baileyscream[/MENTION]
      Place the folder named "patch" near the exe.
      I will change that, so it creates the folder on startup next time.

    77. baileyscream
      10-04-2013
      05:21 PM
      77

      Originally Posted by sinsizer
      [MENTION=177623]baileyscream[/MENTION]
      Place the folder named "patch" near the exe.
      I will change that, so it creates the folder on startup next time.
      oh it was that simple

    78. sinsizer
      10-06-2013
      07:15 AM
      78

      * empty patch folder gets now automatically created on startup

      same link
      http://www.ps3hax.net/showpost.php?p...8&postcount=65

    79. criminal5000
      12-17-2013
      02:53 PM
      79

      Hello, please can you tell me. Where is situated rvk or it real name in firmware ? Because I found coreOS in ofw 4.21, which I need to be restored, patched it and have ros421 but where is rvk, I can't find it pupview.exe in firmware. Thanks, waiting for soon reply.

    80. baileyscream
      12-17-2013
      02:57 PM
      80

      Originally Posted by criminal5000
      Hello, please can you tell me. Where is situated rvk or it real name in firmware ? Because I found coreOS in ofw 4.21, which I need to be restored, patched it and have ros421 but where is rvk, I can't find it pupview.exe in firmware. Thanks, waiting for soon reply.
      Rvk is the revoked fsm keys
      You don't enter fsm if patching for the latest cfw you just need the core os


      Sent from my iPhone using Tapatalk

    81. criminal5000
      12-17-2013
      03:14 PM
      81

      The problem is that I have not downgradeable ps3, which was bricked, friend has tried to downgrade through usb flash...It doesn't power, only with soldered trisate,I have took the dump,by e3, and it has only 2 dangers:

      OFFSET: 0x840 --- VALUE: 0x00000F8E656EC1D96595F85C1F9C6196 --- metldr BINARYSIZE/REVISIONKEY
      OFFSET: 0xFC0000 --- VALUE: 0x00002FFB63B9D98130DB7BB0F39D124F --- bootldr BINARYSIZE/REVISIONKEY

      I just want to reanimate it on Official firmware, that it could work.Is it possible? Thanks

    82. Swizzy
      12-17-2013
      04:45 PM
      82

      Originally Posted by criminal5000
      The problem is that I have not downgradeable ps3, which was bricked, friend has tried to downgrade through usb flash...It doesn't power, only with soldered trisate,I have took the dump,by e3, and it has only 2 dangers:

      OFFSET: 0x840 --- VALUE: 0x00000F8E656EC1D96595F85C1F9C6196 --- metldr BINARYSIZE/REVISIONKEY
      OFFSET: 0xFC0000 --- VALUE: 0x00002FFB63B9D98130DB7BB0F39D124F --- bootldr BINARYSIZE/REVISIONKEY

      I just want to reanimate it on Official firmware, that it could work.Is it possible? Thanks
      Only by restoring a valid dump, and seeing as both errors are within metldr/bootldr it's not likely that you can revive this console...

    83. criminal5000
      12-18-2013
      03:32 PM
      83

      The problem is that ps3 was bricked?and it is not downgradeable, by updating custom software through usb. Can anybody help me to restore dump, because I haven't got any experience in it?

    84. baileyscream
      12-18-2013
      03:40 PM
      84

      Originally Posted by criminal5000
      The problem is that ps3 was bricked?and it is not downgradeable, by updating custom software through usb. Can anybody help me to restore dump, because I haven't got any experience in it?
      [MENTION=123604]Swizzy[/MENTION] has given you your answer on this dump

      Why repeat your question?
      You have a ps3 that cannot be downgraded so no patches can help you

      You have a mtldr2 console so you will get the above error as the verifiers are trying to verify a mtldr not mtldr2 area

      You tried downgrading via USB? So is this patched for fsm rvk patches eg 3.55 patched? If so then that's why it's bricked
      You need the origional dump as a none downgradable console cannot go to 3.55 as it will brick

      What is the CECH number on the console and the date code?


      Sent from my iPhone using Tapatalk

    85. euss
      12-18-2013
      03:56 PM
      85

      Originally Posted by criminal5000
      Hello, please can you tell me. Where is situated rvk or it real name in firmware ? Because I found coreOS in ofw 4.21, which I need to be restored, patched it and have ros421 but where is rvk, I can't find it pupview.exe in firmware. Thanks, waiting for soon reply.
      The revoke you seek is most likely PRG and PKG

      http://www.psdevwiki.com/ps3/Talk:Pl..._log_breakdown "Update Package Revoke list"
      Update Package Revoke list
      read package revoke list package (576 bytes) elapsed = 6 msec
      update package revoke list elapsed = 331 msec
      Update Package Revoke list done(0x8002f000)

      ^ RL_FOR_PACKAGE.img copied from PUP to trvk_pkg


      Bul-ray Disc Player Revoke
      read bdp revoke package (1904 bytes) elapsed = 23 msec
      decrypt and verify bdp revoke package elapsed = 29 msec
      write bdp revoke package elapsed = 2240 msec
      compare bdprevoke package elapsed = 57 msec
      Bul-ray Disc Player Revoke done(0x8002f000)

      ^ dev_flash3_024.tar.aa.* files from PUP are unpkg'ed to dev_flash3


      Update Program Revoke list
      read program revoke list package (704 bytes) elapsed = 7 msec
      update program revoke list elapsed = 331 msec
      Update Program Revoke list done(0x8002f000)

      ^ RL_FOR_PROGRAM.img from PUP is copied to trvk_prg
      http://www.psdevwiki.com/ps3/Revokation
      http://www.psdevwiki.com/ps3/Flash:R...ogram#trvk_prg

    86. rablack97
      03-11-2014
      01:23 PM
      86

      Was there ever an XP compatible version done?

    87. baileyscream
      03-11-2014
      02:17 PM
      87

      Originally Posted by rablack97
      Was there ever an XP compatible version done?
      No
      10 char

    88. Swizzy
      03-11-2014
      05:29 PM
      88

      Originally Posted by rablack97
      Was there ever an XP compatible version done?
      There is one now

      You'll need to install .NET 4.0 in order for it to work tho: http://www.microsoft.com/en-us/downl....aspx?id=17851

      http://www.sendspace.com/file/ij4xrj <--- here you can grab it

      What i did was download the latest one (linked here: http://www.ps3hax.net/showthread.php...l=1#post669778) then i decompiled it and fixed a few minor decompilation errors and re-compiled it with .net 4.0 as target instead of .net 4.5 [ i tested to make sure it runs in Windows XP on one of my virtual machines, however... i didn't check that all checks etc. are ok, but they should be... ]

    89. rablack97
      03-12-2014
      10:05 PM
      89

      Originally Posted by Swizzy
      There is one now

      You'll need to install .NET 4.0 in order for it to work tho: http://www.microsoft.com/en-us/downl....aspx?id=17851

      http://www.sendspace.com/file/ij4xrj <--- here you can grab it

      What i did was download the latest one (linked here: http://www.ps3hax.net/showthread.php...l=1#post669778) then i decompiled it and fixed a few minor decompilation errors and re-compiled it with .net 4.0 as target instead of .net 4.5 [ i tested to make sure it runs in Windows XP on one of my virtual machines, however... i didn't check that all checks etc. are ok, but they should be... ]
      Hey swizzy here are the source links, they were in the thread...I knew i have seen it somewhere.

      Binary: http://rghost.net/47726473
      Source: http://rghost.net/47726545

    90. Swizzy
      03-13-2014
      03:52 AM
      90

      Originally Posted by rablack97
      Hey swizzy here are the source links, they were in the thread...I knew i have seen it somewhere.

      Binary: http://rghost.net/47726473
      Source: http://rghost.net/47726545
      Thanks, now the code makes alot more sense xD i might compile a new xp compatible one based on this code instead as it is more reliable...

      Sent from my GT-I9300 using Tapatalk

    91. rablack97
      03-13-2014
      03:53 PM
      91

      Originally Posted by Swizzy
      Thanks, now the code makes alot more sense xD i might compile a new xp compatible one based on this code instead as it is more reliable...

      Sent from my GT-I9300 using Tapatalk
      I notices your new version didn't include stats, was this intentional as this should be checked using HXD?

    92. Swizzy
      03-13-2014
      05:13 PM
      92

      Originally Posted by rablack97
      I notices your new version didn't include stats, was this intentional as this should be checked using HXD?

      You mean PS3 Dump Checker?

      If so; Yes, it's intentional, it's kinda rare that it matches due to the stats beeing checked against 3.55 ofw and each new firmware will cause the stats to change...

    93. PapaLazarou
      07-15-2014
      08:51 AM
      93

      Hi, Im a noob here.

      But can this tool extract the eid_root_key from a 3.55 dump ?

    94. baileyscream
      07-15-2014
      09:34 AM
      94

      Originally Posted by PapaLazarou
      Hi, Im a noob here.

      But can this tool extract the eid_root_key from a 3.55 dump ?
      No
      That's not in the dump
      Use flatz EID root key dumper



      Sent from my hand using Tapatalk and magic

    95. PapaLazarou
      07-15-2014
      09:37 AM
      95

      Thanks for the info.. looks like Ill have to downgrade just to get the key.

    96. 3absiso
      07-15-2014
      02:49 PM
      96

      Originally Posted by PapaLazarou
      Thanks for the info.. looks like Ill have to downgrade just to get the key.
      you need a CFW to to get it, yes,
      i think i heard a tool for ODE is released also, not sure

    97. Swizzy
      07-15-2014
      03:08 PM
      97

      Originally Posted by 3absiso
      you need a CFW to to get it, yes,
      i think i heard a tool for ODE is released also, not sure
      That'd most likely be a fake as ofw doesn't allow you access to things cfw's does, and i think you need lv1 or lv2 peek 'n' poke support (blocked by ofw)

    98. 3absiso
      07-15-2014
      03:23 PM
      98

      Originally Posted by Swizzy
      That'd most likely be a fake as ofw doesn't allow you access to things cfw's does, and i think you need lv1 or lv2 peek 'n' poke support (blocked by ofw)
      Yes, you are right, i was thinking of IDPS Dumper for the ODE

    99. Swizzy
      07-15-2014
      03:38 PM
      99

      Originally Posted by 3absiso
      Yes, you are right, i was thinking of IDPS Dumper for the ODE
      Yes, and with an ODE you can't do it because LV1/LV2 doesn't allow it...