Originally posted by BrewAgent: I'd probably be best if you gave us more information. What you did before this started to happen, the firmware you were on, etc.
I didn't do anything really. All I did was pop in the game "TMNT" and it just went black.
Originally posted by BrewAgent: I'd probably be best if you gave us more information. What you did before this started to happen, the firmware you were on, etc.
Originally posted by BrewAgent: I'd probably be best if you gave us more information. What you did before this started to happen, the firmware you were on, etc.
I didn't do anything really. All I did was pop in the game "TMNT" and it just went black.
Regardless of custom Firmware or Official, it makes no difference. Your PSP system files are stored locally on the integrated flash. After the PSP boots up, it is then passed off from flash0 to flash1, which is sort of like your RAM in a computer. Once booted, the system files have been loaded and the flash0 does not have to remain open. Even if, by some odd way, an official UMD had some type of bug or security device inbedded, it simply could not access your flash once booted. It would reqiure a program built off of homebrew or an app run in Recovery Mode, before the system critical files take over. An official UMD can not gain access to the flash. If you claim that if it worked before TMNT was played and not afterwards, I'd call you a liar. You must have done something else. The only way you could get a brick like that would be from a program specifically designed to modify the flash. These programs do NOT EXIST on any official UMD!
Originally posted by BrewAgent: I'd probably be best if you gave us more information. What you did before this started to happen, the firmware you were on, etc.
I didn't do anything really. All I did was pop in the game "TMNT" and it just went black.
Regardless of custom Firmware or Official, it makes no difference. Your PSP system files are stored locally on the integrated flash. After the PSP boots up, it is then passed off from flash0 to flash1, which is sort of like your RAM in a computer. Once booted, the system files have been loaded and the flash0 does not have to remain open. Even if, by some odd way, an official UMD had some type of bug or security device inbedded, it simply could not access your flash once booted. It would reqiure a program built off of homebrew or an app run in Recovery Mode, before the system critical files take over. An official UMD can not gain access to the flash. If you claim that if it worked before TMNT was played and not afterwards, I'd call you a liar. You must have done something else. The only way you could get a brick like that would be from a program specifically designed to modify the flash. These programs do NOT EXIST on any official UMD!
If he's on CFW he could have played with his settings and killed it no?
