Editing 1.00 Bogus Firmware

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 10: Line 10:
In order to properly install it, you will need to install the system software, and then clear out the registry after booting. You can also utilize the registry patcher application to patch the 1.0.3 registry to have it downgrade to the older settings version.
In order to properly install it, you will need to install the system software, and then clear out the registry after booting. You can also utilize the registry patcher application to patch the 1.0.3 registry to have it downgrade to the older settings version.


While it can be installed over 1.0.3, the system will need a hard reset each time it is suspended. This is due to the power method being changed in 1.0.3 and thus its' IPL will break sleeping on older firmwares. This can be fixed by either replacing '''power.prx''' from 1.0.3 or using the correct IPL. The 1.0.0 IPL (kbooti.bin) leaked on the game '''NBA Street Showdown'''. The 0.9.0 IPL also works and can be found on a few UMD games: two of these are Ridge Racers and Shutokou Battle, located in the PRX folder as '''kbooti.bin'''.
While it can be installed over 1.0.3, the system will need a hard reset each time it is suspended. This is due to the power method being changed in 1.0.3 and thus its' IPL will break sleeping on older firmwares. This can be fixed by either replacing '''power.prx''' from 1.0.3 or using the correct IPL. No 1.0.0 IPL is publicly available but the 0.9.0 IPL works and can be found on a few UMD games: two of these are Ridge Racers and Shotoku Battle, located in the PRX folder as '''kbooti.bin'''.


To make it run on retail units, you will need to remove the [[iplloader]] (first 0x1000 bytes) and make the following change to main.bin:
To make it run on retail units, you will need to remove the pre-ipl (first 0x1000 bytes) and make the following changes to main.bin:


0x04000714 -> '''0x3224007F''' (masks some check used in the Baryon leaf like in newer IPLs)
0x04000714 -> '''0x3224007F''' (fix for retail units, something related to IdStorage)


Optional, for compatibility with TA-082/86 motherboards:
0x04000730 -> '''0x1000FF47''' (clockgen fix, only needed for TA-082/86 PSPs)


0x04000730 -> '''0x1000FF47''' (clockgen fix)
You can then use ipltool to reencrypt the IPL.
 
You can then use ipltool to reencrypt the IPL. Alternatively (not recommended) you can also patch IdStorage by changing byte 0x18 in leaf 4 (Baryon) from 0x94 -> 0x14. This will allow the IPL to boot without modifying it.


= Version Differences from Release 1.0.3 =
= Version Differences from Release 1.0.3 =
Line 61: Line 59:


* GAME Category
* GAME Category
# UMD/Memory Stick Firmware Updates do not work, this is probably due to the startup information from the firmware's updates that contain more information than what the VSH is trying to read.
# UMD/MemoryStick Firmware Updates do not work, this is probably due to the startup information from the firmwares updates that contain more information than what the VSH is trying to read.
# All EBOOTs show up corrupt, as with the issue from above, this can only be mediated by using the bogus firmware PARAM.SFO since it matches the information that the XMB needs or patch the firmware's game_plugin to allow it to read the new information.
# All EBOOTs show up corrupt, as with the issue from above, this can only be mediated by using the bogus firmware PARAM.SFO since it matches the information that the XMB needs or patch the firmware's game_plugin to allow it to read the new information.
# Loading any game/application from the Memory Stick will cause a lower default memory allocation and current working directory error when the system reboots.
# Loading any game/application from the Memory Stick will cause a lower default memory allocation and current working directory error when the system reboots.


* VIDEO Category
* VIDEO Category
# While playing an hour long MPEG4 video from the Memory Stick, the video starts to desync the audio/video. The video starts slowing down but the audio continues to play in a normal speed.
# While playing an hour long MPEG4 video from the MemoryStick, the video starts to desync the audio/video. The video starts slowing down but the audio continues to play in a normal speed.
# Playing an MPEG4 video, and jumping an hour using the control panel options causes the same symptoms as above. This likely might be due to how the firmware buffers videos rather than seeking from UMD.
# Playing an MPEG4 video, and jumping an hour using the control panel options causes the same symptoms as above. This likely might be due to how the firmware buffers videos rather than seeking from UMD.


* MUSIC Category
* MUSIC Category
# Minor codec changes were made that cause specific MP3's from showing under [MUSIC].
# Minor codec changes were made that cause specific MP3s from showing under [MUSIC].


* PHOTO Category
* PHOTO Category
# If you delete the Digital Cameras folder it will cause the system to lock up immediately after exiting the category.
# If you delete the Digital Cameras folder it will cause the system to lock up immediately after exiting the category.
# Loading a large photo causes the viewer to act up, such as zooming into a photo will causing a 200% increase in size.
# Loading a large photo causing the viewer to act up, such as zooming into a photo will causing a 200% increase in size.


* SETTINGS Category
* SETTINGS Category
Please note that all contributions to PSP Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PSP Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)