Discussion in 'Sony PSP - Mod and firmware discussion' started by Diesel76, Mar 28, 2007.
how do I play a .CSO game on my PSP 2.6?
if u had even bothered to go to google on how to play an ISO on a PSP you would have found out that they only work on a 1.5 or custom firmware.
You will have to downgrade to 1.5fw then upgrade to custom fw. If you wand to do this I suggest you search the forum and have a good read b4 you start.
I'm not too sure about manipulating the script in my firmware
system crashes and then I'm left with a worthless piece of hardware
what game file ext should I look for that are compatible with 2.6?
If you don't want to downgrade then I'm afraid it's UMD's for you m8.
is firmware more or less the operating system of the PSP?
I keep reading about 3.03OE-C Firmware ...
I'm assuming that is some "custom" firmware code that replaces the manufactured code in order to play downloaded games with certain files extensions i.e. CSO, ISO (image files) probably ripped from legit manufactured games
will the PSP still run legitimate UMDs?
is there some sort of restoration process if it gets "bricked" (crashes)?
first Sony's orig firmware is good. and playing umd is also good
but if and only if you wanted play some homebrew games, downloadable games(iso/cso), customization of your psp that's the time you need to go to custom firmware (and yes it will replace/change the sony's firmware)
the highest firmware can be downgraded(meaning can changed) is 3.03
3.03 or lower can be downgraded to 1.5 and upgrade ----->
and 3.03oe-c and 3.10oe-a is the latest 'custom firmware' as of now
where in 3.03oe-c is better coz u can fully customized your psp
while in 3.10oe-a is just some things not fully customized
3.03oe-c has a recovery mode,,,,(oe custom firmwares has a recovery)
we should use semi-brick word, when u mess up with customization of your psp that the time you have a larger percentage of semi-bricking or totally brick
and you can use your recovery to go back down to 1.5,,
and yes you can still play umds,,you still can use the features of the original firmware
so, it's a downgrade from 2.6 to 1.5 then up to 3.03oe-c??
no way to just go from 2.6 up to the 3.03oe-c which I am understanding is the most current custom firmware version??...
the potential brick happens when downgrading and/or upgrading??
is there no way to have a restoration folder in this process with the original code, 2.6??
after a successful upgrade to 3.030e-c from 1.5 there is a "built-in" restoration folder with the custom firmware in the event of a semi-brick??
what would a restoration bring the settings back to?
if you brick while downgrading then your screwed. but if you follow the instructions right then you should be ok. if you semi-brick in 3.03OE-C and restore via downgrade. it will take you back to 1.5, if you have the 1.5 update.
these will help if you semi-brick in Custom Firmware:
Heres what you have to understand about Sony's Firmware, They write their firmware so it wont execute unsigned code. the deal with 1.5 firmware is that they're is an easy exploit that opens the system's Kernel up so you can do any modification you want to it...including firmware installation.
Each time a computer is booted, the kernel and other frequently used operating system instructions are loaded.
The kernel is the core of an OS that manages memory and devices.
no way to access the kernel in the current firmware I have?? (2.6)
so in essence I am formatting the hard disk on the PSP (removing the current OS), downgrading to a lower firmare version (1.5) accessing the kernel and modifying it?? then I am upgrading to the 3.03oe-c?? why am I modifying the kernel in 1.5, won't the upgrade change those mods?
You cant think of it as formatting the harddisk, its more likeyour formatting the BIOS on the onboard chipset.
Bascially, 1.5 Kernel is easy to bypass security. 3.03 OE-C essentially gives you 3.03 Firmware with 1.5 Kernel.
BIOS (contains startup instructions)
kernel (manages memory and devices)
OS (takes over after BIOS and kernel are loaded)
I thought BIOS was on ROM chipset (read only, cannot be modified)
the kernel loads into RAM from the hard disk (because BIOS told it to)
then the OS loads according to kernel instructions ????
Separate names with a comma.