When you download an update with the Network Update function, it doesn't write the file to the memory stick until the very end. For example, if you start a Network Update, rip the MS out ater it has started downloading (I did this when it was at 0%), all you get is a file that says "Corrupted Data" and supposedly 16KB big under the Game -> Memory Stick place in the XMB. I run Network update again, let it d/l 99% of the update, and I rip the MS out. Again, I get a 16 KB "Corrupted Data" file. Basically, if someone was able to use the Network Update function to send it a homebrew update with a large file size, you would be able to overrun the memory (which seems to be the place where the update file is stored until it's 100% downloaded).
Also, if you have an update (100%, non-corrupted) on the MS, and re-download the update, if you let it d/l 100% of the way, it will overwrite the update on the MS.
My guess is that the Network Update sends some 16KB file to reserve space (or maybe act as some kind of header or container) for the update. The update downloads, but not to the Memory Stick, despite the fact that the Memory Stick access light flashes constantly. Perhaps some small bit of data is being while the update is being d/l'd. Anyway, after all files have been downloaded, the PSP checks if there has been another update on the MS (or perhaps it does this when it first creates the 16KB file, I don't know) and then overwrites any existing update with the one stored in memory.
I don't know if a memory overflow is useful, but this is one way to do it, or so it seems.
*I haven't connected the PSP to a PC to see what the real size of the "Corrupted Data" files are; they may be smaller/larger than 16KB in reality.
Overflow Memory with Network Update??
Moved to the new Exploit forum.
Dude, news for you, it is writing to the memory stick, that's why the light is constantly flashing. But because you eject it while it's writing, it never gets the chance to close the file, resulting in corrupted data.
You can end up trashing your memory stick this way, I wouldn't advise doing it anymore. I think Herben mentioned this in another thread, but folks, please don't yank out your memory stick as it's being accessed, that's just being dumb.
Dude, news for you, it is writing to the memory stick, that's why the light is constantly flashing. But because you eject it while it's writing, it never gets the chance to close the file, resulting in corrupted data.
You can end up trashing your memory stick this way, I wouldn't advise doing it anymore. I think Herben mentioned this in another thread, but folks, please don't yank out your memory stick as it's being accessed, that's just being dumb.
-
- Posts: 24
- Joined: Fri May 06, 2005 5:59 pm
-
- Posts: 24
- Joined: Fri May 06, 2005 5:59 pm