PS3 PLAYERKP420 4.78 CFW v1.00

Discussion in 'PS3 News' started by STLcardsWS, Jan 21, 2016.

By STLcardsWS on Jan 21, 2016 at 8:45 PM
  1. 8,636
    8,318
    1,022
    STLcardsWS

    STLcardsWS Administrator

    Joined:
    Sep 18, 2014
    Messages:
    8,636
    Likes Received:
    8,318
    Trophy Points:
    1,022
    The first 4.78 CFW (Custom Firmware) has appeared following the Official Firmware Update of 4.78, that we have just seen come alongside the PS Vita (& PSTV) v3.57 System Update. playerkp420 who is known for his various MFW releases (which are essentially CFW, but created with a tool called MFW builder) has been working on creating his own CFW from scratch.He delivers a simple CFW that's a Standard CEX based firmware with the release of PLAYERKP420 4.78 v1.00 CFW. [break]ss[/break] Also, playerkp420 has provided a Video Tutorial to show user's how to setup the MAMBA payload which gives those non-cobra cfw's cobra like features, in this link you can view some of the features MAMBA adds (such as ISO Support, Plugin Support, Network Loading and more). View the details of this 4.78 Custom Firmware release and if you are looking for all the latest 4.78 Releases and other CFW options be sure to view this link in our forums as we will be updating the list as things get updated and released over the next weeks.



    playerkp420.jpg
    CFW
    Firmware Version
    Type
    Developer4.78 Homebrew / CFW


    • 4.78





    USE ANY CFW AT YOUR OWN RISK
    Download: Playerkp420 4.78 v1.00
    • md5 = 18F6F0D562DE5AB9E7419D0058F9F333

    Source: ps3hax.net / (2)
     

Comments

Discussion in 'PS3 News' started by STLcardsWS, Jan 21, 2016.

    1. xiaoyang
      xiaoyang
      Thank you very much
    2. lokuelo
      lokuelo
      thanks, for your job
      regards
    3. Sdw100
      Sdw100
      Nice going [MENTION=1879]playerkp420[/MENTION], how did u patch core os? Can i extract core os and use with swizzy patch tool?
    4. sheaushyong
      sheaushyong
      MM report it's 4.75 , BD EMU is usable ... strange..
    5. playerkp420
      playerkp420
      I used MFW Builder to apply some patches, and did some patches in hex. You can use it with patch tool. But usually what he uses only has the minimum patches like from dual boot OFW coreos. I will have a DB in a little while.
    6. Sdw100
      Sdw100
      when mfw patches are used filesize is incorrect and can cause issues I think editing the .txt file can fix ill have a play when I get this ps3 in
    7. johtaja
      johtaja
      Has anyone tried this on CECHL? Does multiMAN 4.76 work without mamba?
    8. pinky
      pinky
      might be due to mm not being updated. I just decrypted the pup file for hex comparisons to 4.76/4.75, and the vsh.self header shows 4.78 like it should. :)
    9. playerkp420
      playerkp420
      That is why I took it apart and used the list.txt from OFW.

      I have made a DB OFW, that should be better for making coreos patch. The file size is exactly the same as OFW. Even if you unpack it, lv0 and spu_pkg_rvk_verifier.self, they are the same size. (The only 2 files that are patched to allow reinstall of CFW)

      [​IMG]

      Download: Playerkp420_DB.OFW_4.78
      md5 = 98808D251DA71AA56626D6011137F265
    10. STLcardsWS
      STLcardsWS

      [MENTION=673]sheaushyong[/MENTION] BD EMU will not work without an update by deank .. (multiMAN v4.78.00 will be needed as mM follow OFW version numbering)

      So since the latest version is v4.76.00 we need an update. There has not been many changes to the firmware in the last several releases of OFW, so 4.75, 4.76, 4.78 are nearly identical. Also since mM is not updated it will not display newer firmwares correctly.

      mmCM mode can be used on 4.78 CFW without update, which that requires COBRA or you can use MAMBA and i believe mmCM can be used. Which in mmCM BD EMU is not needed.
    11. littlebalup
      littlebalup
      patch for qa in addition to the basics LV0 and spu_pkg_rvk_verifier patchs is better for a no-fsm patch. This way you can downgrade right after the flash (if console has already been jailbroken with qa token created of course).

      Edit; and maybe patch Core OS hash check as well
      Last edited: Jan 22, 2016
    12. STLcardsWS
      STLcardsWS
      I think your username needs a new color ..
    13. atreyu187
      atreyu187
      Agreed MFW or not!!
    14. xiaoyang
      xiaoyang
      Can publish a cobra 7.20 4.78 CFW
    15. bitsbubba
      bitsbubba
      technically all CFWs are MFW, and so seems this is not completely a MFW Builder production as stated some patches were done manually :p
    16. pinky
      pinky
      I think it's semantics mostly. for example, most people use the coldboot creator by twizzy (is that the right name?) with the purple wave in the background, but others, such as myself, hex in the images/script. it's really the same thing whether it's automated or not. u can get most, if not all, information u need for creating cfw from ps3devwiki along with patches. u can learn a lot through hexing or IDA to debug the files, both of which, r in the patches section of ps3devwiki. ...just make sure u have an e3 or a similar device on hand in case something goes wrong.
    17. sheaushyong
      sheaushyong
      BD EMU is really work fine on this 4.78 CFW , that's why so strange...
    18. kozarovv
      kozarovv
      This mean that changes between 4.75-4.78 are really small. Also this confirm that $ony released this fw ONLY because rebug release, just to make 4.76 "outdated". Is funny that big company like to play cat and mouse game.
    19. arcadekidflo
      arcadekidflo
      This fw has Install Package Files and app_home upside down , they are first in the column instead of being last . What is the correct procedure to enable Mamba ? I installed Mamba Autoloader , launched it and kept X pressed , then installed Webman 1.43.25 but after a restart i cant acces the Game column at all , no items appear . I needed to to a firmware reinstall , re-enable Mamba then it worked . Also , is app_home still needed with Mamba/Cobra ? Maybe it can be removed from the xml

Share This Page