1.00 Bogus Firmware
System Version Information
[ 1.00 Bogus ]
release:1.00: build:106,1:root@psp-vsh system:16214,0x00100000: vsh:2004_1104_s16214_p3883_v8335:
[ 1.00 Release ]
release:1.00: build:228,0,3,1,0:root@psp-vsh system:17919@release_103a,0x01000300: vsh:p4029@special_day1,v9972@special_day1,20041201:
Description
This is an official firmware update that was released on the Network Update servers in early January 2005. Sony did this to make sure that a full system software update can be received and installed on the PSP hardware before the US launch.
Due to the design of the network update feature, they did not use update test servers and used the production servers. This allowed people to go into the 'Network Update', download and install the software causing a soft-brick.
At the time, this was considered a brick due to the symptoms causing the hardware to no longer boot. There were several theories to why it happened such as the bootloader (IPL) being deleted due to missing a IPL driver in the updater. What actually happened was that the registry/user settings were not downgraded from the Release 1.00 (1.0.3) and the older system software (1.0.0) was not able to read it.
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.
Version Differences from Release 1.0.3
This firmware is known to most as 1.00 "bogus" also known as 1.0.0 bogus, this was a Pre-release 1.00 with some development/debug modules mixed in to specifically assist in the development of VSH modules.
The few modules that were left in for development purposes was 'loadcorei', 'rebooti', and 'dlgsample_plugin'. There are some modules that were modified for development purposes to provide more debug information. Most of the firmware contains kernel messages that would not normally be seen by the typical user.
It does not contain a DECI2P debugging module so its not certain how these messages would be seen, possibly through another active host file system receiving the TTY information.
The firmware uses loadcorei by default to allow plain modules to be loaded during runtime, and 'dlgsample_plugin' was a development sample for the dialog utility. It's uncertain what rebooti.prx did differently than the rebooti.prx.
XMB Menu Differences
TODO: Screenshots/sounds.
Due to the early revision of the firmware, there are some major differences with the firmware compared to the launch 1.00. Early assets such as XMB navigation sounds/icons were present in the firmware but later removed or changed around.
Probably the most notable difference is the boot up sound:
XMB Menu Bugs
As with any in-development software, the XMB kernel comes with several bugs that are not found under normal conditions.
- VIDEO Category
- 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.