Search results
Jump to navigation
Jump to search
- Aligns version on 12 bits then compares to the hardcoded current firmware version (example: 0x03600000 on FW 3.60).7 KB (780 words) - 22:25, 16 July 2023
- ...are relative to the start of the image, for <code>vnzimg.skprx</code> from firmware ???.5 KB (845 words) - 21:40, 1 May 2023
- ! Firmware !! Changes since previous version !! Notes By abusing the way resume works, we can reboot the device into a custom firmware by patching the non-secure kernel bootloader. The general framework to do t12 KB (1,871 words) - 04:36, 19 June 2022
- ...d of word-sized operands. The "new" filter algorithm is used instead since firmware 1.50.7 KB (924 words) - 07:50, 13 January 2024
- ...(by seed encryption) SMI keys in second_loader, which are used for minimum firmware version decryption. | 0x50F || 0x18000001 || 0x18000003 || Y || second_loader || Minimum firmware version. 4 bytes. Comes from IdStorage SMI leaf (eMMC).15 KB (2,128 words) - 09:51, 18 March 2024
- ...ame/application/system application is hacked, Sony can easily distribute a firmware update to block the hack. They can also ask a game update and depending on6 KB (1,004 words) - 08:27, 4 August 2023
- ...is chip (seemingly mapped to SDIC, physical address 0x50090000) and the CP firmware is stored on it. Cyan : CP firmware updating12 KB (1,872 words) - 18:32, 8 January 2024
- ...module_suspend(void);</code> Supported in FW 0.990.030, unsupported as of firmware 3.65. Present in FW 0.990.030 [[SceKernelModulemgr]]. ...d* pCommon);</code> Supported in FW 0.931.010-0.990.030, unsupported as of firmware 3.65. Seemingly never used.38 KB (5,257 words) - 14:21, 25 December 2023
- ...ows encryption, leaving Update Manager SM add personalization layer during firmware update without having to derive the keys itself.8 KB (1,251 words) - 23:45, 16 July 2023
- ! Firmware !! Address ! Firmware !! Address34 KB (5,112 words) - 18:25, 17 September 2023
- Gets version of the current installed Ernie firmware. Can also be seen in the packet header in [[Syscon Update]]. Also sent at k Gets Ernie firmware timestamp. Also sent at kernel boot.40 KB (5,023 words) - 22:21, 5 January 2024
- This bug exists since at least firmware 0.920 and has never been fixed. It is plausible it exists since an earlier Present in firmware 3.60.23 KB (3,419 words) - 11:41, 8 February 2024
- | 0x4 || 0x4 || second_loader || Current Firmware Version | 0x8 || 0x4 || second_loader || Minimum Firmware Version. Comes from SMI IdStorage leaf.33 KB (4,849 words) - 19:57, 30 March 2024
- This sort of exploit works in theory on any firmware (not patchable, or hardly). ...bKit exploit, it is using a gamesave exploit. The reason for that is after firmware 3.30 or so, Sony introduced [[SceKernelModulemgr#sceKernelInhibitLoadingMod59 KB (8,666 words) - 18:39, 13 October 2023
- ...<br /> - blacklisted offsets 0x8-0x1000 in release syscon firmware20 KB (3,211 words) - 12:22, 9 January 2024
- ...ed as <code>YYYYMMDDhhmm</code>. This comes from a string stored in Syscon firmware under another format: <code>$Date:: YYYY-MM-DD hh:mm:ss +0900#$</code> Example: <code>$Date:: 2013-12-13 15:52:05 +0900#$</code> in Syscon firmware becomes <code>201312131552</code> in Syscon command 2.110 KB (12,775 words) - 21:59, 4 April 2024
- On 7/29/2017, all hacked Vitas on 3.60 spoofing the latest firmware (3.65) were blocked from console activation. This is particularly odd becau27 KB (3,421 words) - 21:04, 21 January 2024
- These system usermode modules can be decrypted on any firmware version and are identified by kprx_auth_sm.self by their program-authority-37 KB (4,005 words) - 15:48, 8 December 2023
- In firmware 3.60, the TTBCR has the following value: 0x00000002, which means that TTBCR37 KB (4,938 words) - 05:51, 2 September 2023
- Private key 0 is only used for signing __sceebootpbp files for firmware versions before 1.8X, otherwise private key 1 is used for signing __sceeboo53 KB (7,975 words) - 21:55, 10 January 2024