![]() |
| Forums | Gaming News | Videos | Downloads | Today's Posts | Mark Forums Read | Chat | FAQ | Members List | Contact |
| ||||||
This is a discussion on PSP EEPROM and Boot block within the PSP Homebrew and Hacks Discussion forums, part of the PSP Development, Hacks, and Homebrew category; Here is a feeling : With all the recent fakers, we still don't know how to downgrade a PSP, but ...
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 |
![]() |
Here is a feeling :
With all the recent fakers, we still don't know how to downgrade a PSP, but we know how to brick a PSP. A PSP is bricked when the firmware is corruped. This may happen if you shut it off while flashing the firmware. I use to work on many PC BIOS. All recent EEPROM (where the BIOS is located) have a "boot block". A boot block is a small write-protected part of the EEPROM. At boot stage, if the unit finds the BIOS code corrupted, it will skip the part and load this small boot-block. Usually, the boot block is only able to reflash the main BIOS using only very simple access to device (no video, no keyboard, only floppy, for exemple). You just need a specially formatted floppy with a single file with a specific name. I'm working on many firmware like ADSL Router or DVD drive. They all have a boot-block in order to revert a hand-user flash error. If you brick the PSP and send it back to Sony, i'm sure they will not rework the EEPROM BGA and they have a way to reflash the main firmware with a kind of boot-block build into the main EEPROM. To be sure, we need to check 3 things on a bricked PSP : 1/ Check if the boot-block try to read from USB 2/ Check if the boot-block try to read from MS 3/ Check if the boot-block try to read from UMD I think there is more chance to find a read form the MS, that's easier with a small size of code like on a boot-block. With an MS Emulator, you will be able to see WHICH file it searchs. More, there is no enough space on a boot block to implement security check... PS : Check about boot-block on google to know more http://www.pcguide.com/ref/mbsys/bios/compBoot-c.html |
|
|
|
|
|
#3 | |
![]() |
Quote:
If this is the case, that's even better. |
|
|
|
|
|
|
#4 |
![]() |
http://nil.rpc1.org/psp/remote.html
Really easy hardware to build. Did anyone tryed to check what is sent to this port on a bricked psp ? The handshake between client and host should be simple and that may be a solution to send a firmware. |
|
|
|
|
|
#5 |
![]() |
Sony reflashing through the serial port was conjecture only on the PS2dev forum - based on how Sony reflash other pieces of equipment. It has never been confirmed.
PSP has an IPL file in the 2.0 firmware update that appears to patch some kind of "boot block" and give it the ability to decrypt the latest PRX files in the firmware. The only way PSP has ever been reflashed out of Sony HQ was by reverse engineering the two Samsung chips and manually reflashing them with working images. This too has been discussed on PS2dev. |
|
|
|
|
|
#8 |
![]() |
Hmm...in that case, sorry that I stated it as fact.
I guess I just accepted it as fact a while ago... Seems probable though. Sony are able to reflash the firmware to 'unbrick' a PSP that bricked during update. There are other ways they do this, but the serial port seemed a safe definate. But maybe it could be USB? Such information should have been leaked by now, surely? ![]() Well, carry on your research about the PSP's most basic boot...good luck! EDIT - another thing, the headphone connector (serial) is not a standard plug...look on that remote analysis link (http://nil.rpc1.org/psp/remote.html - thanks xsecret!) to see how to make the connector for PC-PSP via serial connections. |
|
|
|
![]() |
| Tags |
| block , boot , eeprom , psp |
| Thread Tools | |
|
|