Yes, you can update to 4.83 CFW from 4.82 CFW. If you choose to install it, make sure you set the QA Flag to enabled in Rebug Toolbox; that way you can go back to 4.82 or earlier CFW if you choose to.
When I do that ? When i'm updating or at any time coz it will be always enabled ?

Sent from my CAM-L21 using Tapatalk
 
When I do that ? When i'm updating or at any time coz it will be always enabled ?

Sent from my CAM-L21 using Tapatalk
At any time. Once you enable the QA flag it will remain active, even when you install other firmware over the current one. It's good practice to enable it, as it allows you to move up and down freely between firmware versions. It also removes the option to update via internet on the System Update menu, preventing accidental installation of OFW from Sony.
 
Well, as it seems peoples have some issues to make a working 4.83 Dualboot firmware, I made one based on @haxxxen PS3MFW mod task (https://github.com/haxxxen/ps3mfw-builder-0.2.1-mod/blob/master/tasks/23_patch_db.tcl).

So "littlebalup's" Dualboot 4.83: http://www.mediafire.com/file/nohp1m422o35ld2/DB_4.83_littlebalup.PS3UPDAT.PUP
MD5 : 4CF60DAE7DA5071A5AD21803C9376E97

Patched isoldr and spu_pkg_rvk_verifier to disable ecdsa protections and allows to install CFW4.83+ over it (tested!).
Core OS patched files (lv0 and spu_pkg_rvk_verifier.self) have exact same size than the original ones.
Code:
isoldr.elf
FileSize: 0x1453b bytes
Search Pattern:  3FE1128518014206
Mask Pattern:    FFFF00FFFFFFFFFF
Replace Pattern: 40800003
Replace Offset:  0x08
----PATCHED AT:000036C0
----PATCHED AT:00003EA8
Code:
spu_pkg_rvk_verifier.elf
FileSize: 0xf7d7 bytes
Search Pattern:  2100030304002A03
Mask Pattern:    FFFFFFFFFFFFFFFF
Replace Pattern: 40800003
Replace Offset:  0x08
----PATCHED AT:00003154

Tested on both NOR (CECH-2004B) and NAND (CECHC04).
 
Last edited:
Hey Guys

Having a slight problem.
Updating from 8.42 to 8.43. Not 100% sure on what version its running but after trying different optipns (FERROX AND COBRA) Im met with an 8002F997 error! If I try and update through the service menu it tells me data is Currupt with another 800 code. Anyone else had this or know why Im getting it?
 
I believe QA means quality assurance, which is a production stage in manufacturing. @bguerville has covered the rest.
Yes, but i think the "Quality Assurance" includes the official repair services
The procedures used in the repair services are made by following a very strict sequence of actions, some of that actions involves using a "JIG USB" and a "JIG PIN MACHINE"
With the JIG USB they can run code at boot time with high privileges, i guess they can enable QA there
And the JIG PIN MACHINE is big, it connects with a lot of service connectors and testpads of the motherboard and it can replace all the software and can generate new IDs for evertyhing. Also, the JIG PIN MACHINE is conected online with sony servers (to update the databases with the info from the repaired PS3) in the same way is made at manufacturing time
 
Well, as it seems peoples have some issues to make a working 4.83 Dualboot firmware, I made one based on @haxxxen PS3MFW mod task (https://github.com/haxxxen/ps3mfw-builder-0.2.1-mod/blob/master/tasks/23_patch_db.tcl).

So "littlebalup's" Dualboot 4.83: http://www.mediafire.com/file/nohp1m422o35ld2/DB_4.83_littlebalup.PS3UPDAT.PUP
MD5 : 4CF60DAE7DA5071A5AD21803C9376E97

Patched isoldr and spu_pkg_rvk_verifier to disable ecdsa protections and allows to install CFW4.83+ over it (tested!).
Core OS patched files (lv0 and spu_pkg_rvk_verifier.self) have exact same size than the original ones.
Code:
isoldr.elf
FileSize: 0x1453b bytes
Search Pattern:  3FE1128518014206
Mask Pattern:    FFFF00FFFFFFFFFF
Replace Pattern: 40800003
Replace Offset:  0x08
----PATCHED AT:000036C0
----PATCHED AT:00003EA8
Code:
spu_pkg_rvk_verifier.elf
FileSize: 0xf7d7 bytes
Search Pattern:  2100030304002A03
Mask Pattern:    FFFFFFFFFFFFFFFF
Replace Pattern: 40800003
Replace Offset:  0x08
----PATCHED AT:00003154

Tested on NOR ONLY.
I'll test it on NAND later next week but there is no reasons it will not work. However, use it at your own risk.

@STLcardsWS, please add it to the main post ;)


Will add after NAND test, since there was already an issue on one, want to be sure there is no issues here as well.

Thanks for supplying.

(Edit: added with a note and warning about NOR not being tested)
 
Last edited:
i am on creating 9 CFW Cobra,
  • Cobra(noBD) 7.55,
  • Cobra (noBT) 7.55,
  • Cobra(noBD, noBT),
  • normal,
  • normal(noBD),
  • normal(noBT),
  • normal(noBD, noBT),
  • dualboot (some onemust test it cuz my teensy is borken)

those 9 firmware with :
  • noBD-noBT Patches
  • Cobra 7.55
  • Better System Stability
  • Disable searching for update packages in GAME disc
  • (Prevent accidental OFW update while on Recovery mode)
  • LV0-isoldr to disable ECDSA Protection to allows installation of CFW over OFW (DualBoot FW)
  • LV0 appldr to enable fself
  • LV0 disable LV0 descrambling of LV1LDR
  • LV0 disable ECDSA checks in ALL LV0-loaders
  • LV0 appldr to disable sig check
  • LV0 appldr to disable lv2 memory protection
  • LV1 Disable integrity check in System Manage
  • LV1 peek/poke Syscalls 182 and 183
  • LV1 allow mapping of any memory area
  • LV1 to remove LV2 protection
  • LV1 mmap function 114
  • LV1 disable CoreOS Hash check
  • LV2 Peek&Poke Syscalls (Syscall 6 and 7)
  • LV2 LV1 Peek&Poke Syscalls (LV2 Syscall 8 and 9)
  • LV2 LV1 Call Syscall to LV2 3.55 (LV2 Syscall 10)
  • LV2 allow execution of any LV2 internal function (LV2 Syscall 15)
  • LV2 disable NPDRM ECDSA check
  • LV2 Syscall 36
  • LV2 QA Flag
  • Disable ECDSA check for spkg files
  • Disable ECDSA check (spp_verifier.self)
  • Disable ECDSA check (spu_token_processor.self)
  • SPU_PKG_RVK_VERIFIER to disable ECDSA Protection to allows installation of CFW over OFW (DualBoot FW)
  • VSH:
  • FSelf (Fake Signed ELFs)
  • Allow runnig of unsigned applications
  • ReactPSN v2.0 into VSH
  • Auto unlocks c00 demo contents
  • Disable Unlinking/Deleting of act.dat (Fix missing act.dat after reboot)
  • Allow unsigned act.dat & rif files
  • Disable Cinavia Protection Completly (Disc&HDD)
  • allow installation of packages(CEX,DEX,CEX-DEX,HAN)
  • Disable PSP drm Check
  • Enable ingame screenshot
  • Disable ECDSA Check in vsh.self
  • Disable flag check in PARAM for Remote Play (REMOTE PLAY SFO FLAG OBSOLETE)
  • XMB CFW setting
 

Attachments

  • cobra noBD & noBT.png
    cobra noBD & noBT.png
    1.2 MB · Views: 568
  • cobra noBD.png
    cobra noBD.png
    1.2 MB · Views: 551
  • cobra noBT.png
    cobra noBT.png
    1.2 MB · Views: 292
  • cobra normal.png
    cobra normal.png
    1.2 MB · Views: 477
  • dualboot.png
    dualboot.png
    1.2 MB · Views: 545
  • standard noBD & noBT.png
    standard noBD & noBT.png
    1.2 MB · Views: 287
  • standard noBD.png
    standard noBD.png
    1.2 MB · Views: 470
  • standard noBT.png
    standard noBT.png
    1.2 MB · Views: 463
  • standard normal.png
    standard normal.png
    1.2 MB · Views: 539
  • screenshot_2018_10_20_18_22_08.png
    screenshot_2018_10_20_18_22_08.png
    954.1 KB · Views: 475
  • screenshot_2018_10_20_18_22_25.png
    screenshot_2018_10_20_18_22_25.png
    1.3 MB · Views: 335
  • screenshot_2018_10_20_18_22_37.png
    screenshot_2018_10_20_18_22_37.png
    1.3 MB · Views: 410
  • screenshot_2018_10_20_18_22_47.png
    screenshot_2018_10_20_18_22_47.png
    518.9 KB · Views: 406
  • screenshot_2018_10_20_18_22_57.png
    screenshot_2018_10_20_18_22_57.png
    1.3 MB · Views: 395
Last edited by a moderator:
i am on creating 9 CFW Cobra,
  • Cobra(noBD) 7.55,
  • Cobra (noBT) 7.55,
  • Cobra(noBD, noBT),
  • normal,
  • normal(noBD),
  • normal(noBT),
  • normal(noBD, noBT),
  • dualboot (some onemust test it cuz my teensy is borken)

those 9 firmware with :
  • noBD-noBT Patches
  • Cobra 7.55
  • Better System Stability
  • Disable searching for update packages in GAME disc
  • (Prevent accidental OFW update while on Recovery mode)
  • LV0-isoldr to disable ECDSA Protection to allows installation of CFW over OFW (DualBoot FW)
  • LV0 appldr to enable fself
  • LV0 disable LV0 descrambling of LV1LDR
  • LV0 disable ECDSA checks in ALL LV0-loaders
  • LV0 appldr to disable sig check
  • LV0 appldr to disable lv2 memory protection
  • LV1 Disable integrity check in System Manage
  • LV1 peek/poke Syscalls 182 and 183
  • LV1 allow mapping of any memory area
  • LV1 to remove LV2 protection
  • LV1 mmap function 114
  • LV1 disable CoreOS Hash check
  • LV2 Peek&Poke Syscalls (Syscall 6 and 7)
  • LV2 LV1 Peek&Poke Syscalls (LV2 Syscall 8 and 9)
  • LV2 LV1 Call Syscall to LV2 3.55 (LV2 Syscall 10)
  • LV2 allow execution of any LV2 internal function (LV2 Syscall 15)
  • LV2 disable NPDRM ECDSA check
  • LV2 Syscall 36
  • LV2 QA Flag
  • Disable ECDSA check for spkg files
  • Disable ECDSA check (spp_verifier.self)
  • Disable ECDSA check (spu_token_processor.self)
  • SPU_PKG_RVK_VERIFIER to disable ECDSA Protection to allows installation of CFW over OFW (DualBoot FW)
  • VSH:
  • FSelf (Fake Signed ELFs)
  • Allow runnig of unsigned applications
  • ReactPSN v2.0 into VSH
  • Auto unlocks c00 demo contents
  • Disable Unlinking/Deleting of act.dat (Fix missing act.dat after reboot)
  • Allow unsigned act.dat & rif files
  • Disable Cinavia Protection Completly (Disc&HDD)
  • allow installation of packages(CEX,DEX,CEX-DEX,HAN)
  • Disable PSP drm Check
  • Enable ingame screenshot
  • Disable ECDSA Check in vsh.self
  • Disable flag check in PARAM for Remote Play (REMOTE PLAY SFO FLAG OBSOLETE)
  • XMB CFW setting

I am going to apply a warning (if pups appear) to this until more eye's have seen it.

Just because we have not seen any CFW releases from you in the past and well we have 9 variants of the firmware.
 
Last edited:
I am going to apply a warning to this until more eye's have seen it.

Just because we have not seen any CFW releases from you in the past and well we have 9 variants of the firmware.
yes your right i will upload youtube videos on each cfw and i will upload the cfw on mediafire or mega and make thread and you can see files vsh elfs...........
 
i have 4.82 and 4.83 cfw but i've got the idea of creating variant firmware from bobby_downgraders :)
 
yes your right i will upload youtube videos on each cfw and i will upload the cfw on mediafire or mega and make thread and you can see files vsh elfs...........

its all about protecting user's the best we can, so many will create and release and its flawed and since we have not seen your work we will play a cautious role (of course once proved be great releases), but its an expected thing and nothing personal

Most of the well known CFW devs will tell you i treated their initial releases the same way when they start doing CFW releases.
@habib @Alexander @playerkp420 and various others ..
 
yes i know that some people make fw that harmes other console for that reason i say to you can see the files in the fw and what patches i applied to it to make people confortamble and secure
 
Last edited:
Back
Top