- #HOW TO USE PRO PSP FIRMWARE 6.60 PATCH#
- #HOW TO USE PRO PSP FIRMWARE 6.60 FULL#
- #HOW TO USE PRO PSP FIRMWARE 6.60 SOFTWARE#
- #HOW TO USE PRO PSP FIRMWARE 6.60 PSP#
#HOW TO USE PRO PSP FIRMWARE 6.60 PSP#
While I’ve talked a lot about the different hardware models of the PSP, their restrictions, their current best possible software, and a lot of other stuff, lets head back to Davees surprise and a potentional ‘permanent patch’ for the latest PSP firmware, version 6.60 – Which would enable any PSP device, old or (too) new, to run a cIPL or permanent CFW, respectively.
#HOW TO USE PRO PSP FIRMWARE 6.60 PATCH#
The third category contains only (2 devices), depending on personal opinions and technicalities, 3 devices, the PSP E1000 (due to its inability to run a firmware other than 6.50 or 6.60), the PSP 3000 09g (while being capable to perform an enforced downgrade to firmware 6.20, which is below its intended lowest firmware limit of firmware 6.30) which should stay on firmwares 6.30 to 6.60, due to firmware stability and IDstorage reasons, and the 09g’s similar twin sister, the PSP 3000 07g (a very rare model of the PSP, which shares the same motherboard characteristics as the 09g), a PSP so rare, that we were unable to properly investigate it (this is also the reason why the 09g supports the enforced downgrade and the 07g does not).ĭevices of this third category are unable to use the current version of the permanent patch, since they lack the ability to natively support the PSP firmware 6.20, which is (as of now) required to use a permanent patch CFW.
The current version of the permanent patch works up to firmware 6.20 and has been (randomly) patched as of firmware 6.30, due to new security checks.
#HOW TO USE PRO PSP FIRMWARE 6.60 FULL#
The permanent patch loads the modules of the custom firmware very early in the boot chain (not as early as & good as cIPL, but get what you can), which will slightly lengthen the initial boot time of your PSP, but will automatically load the CFW on the startup and provides you a method to recover your device, if you (only) semi-bricked it.Ī full brick will still be fatal and unrepairable on these new devices. Those devices are fully capable of using a permanent CFW, a CFW that uses the current version of the permanent patch. The PSP 2000 with the TA-088v3 motherboard, the PSP 3000 03g, the PSP 3000 04g, the PSP 3000 09g (only as forced downgrade, though) and any PSP Go. The second category contains most of the newer PSPs. Those are also the only devices that can use (and create, depending on the motherboard) a Pandora battery. The first category contains the PSP 1000s and PSP 2000s (except for the ‘doomed TA-088v3’ series), that are fully capable of using a full CFW, a CFW that uses a cIPL to load the custom firmware modules. This currently leaves us with 3 categories: Old devices, new devices and too new (or rare) devices. While the enforced downgrade method for the PSP 3000 09g is not the cleanest and most secure thing to do, all other recommendations are safe to follow and should work without problems. This is the current state of the most recommended things you can do with your PSPs (made by myself – You can see this on the emphasis of the ME/LME CFW recommendations, hehe).
#HOW TO USE PRO PSP FIRMWARE 6.60 SOFTWARE#
Hardware & Software talk – Different PSP models
If this interests you, then keep reading! Davee has a surprise up his sleeves! How about this would be available for the latest PSP firmware, version 6.60? How about this would now natively support the previously ‘unsupported devices’ – 3000 07g*, 3000 09g (no enforced downgrades anymore) and the PSP E1000? Something (similar enough) that has only existed (while being far superior, by the way) in the form of a custom IPL for the older PSP devices exclusively. The current permanent patch is, as of now, the number one thing to install, if you have one of the newer PSP devices, since it enables you to automatically boot into a CFW, no (manual) launcher required. Some of you might remember the first betas of the permanent patch, which worked surprisingly well (for most of us, at least).
0 kommentar(er)
