Printable View
Now what if someone used the MPH downgrader but added the attribute "read-only" to the index.dat file? The PSP wouldn't be able to overwrite it, right? This would mean that even after updating or downgrading, the version would still appear to be 1.00, right? Does someone want to try that?
hehe, no way, not me, i dont wanna loose my PSP like you, heh!
*kidding*
Well, please, anyone answer his question?
Highly unlikely to work for several reasons:
First, assuming the updater use a naive file-based updating procedure and does in fact even respect the read-only attribute, the result would most likely be that the updating process aborts and that usually goes really well...
The versioning information has apparently been changed, so even if the scheme would work as prescribed (and I seriously doubt it), it would not help with higher firmwares.
seriously... if an updater can constantly read wether the memory stick is in or not, im sure it would be able to tell if a file wasnt written.... especially the index.dat.... now, there isnt any way to use usb to directly access the flash, is there?
Well, there is a way to access the UMD via FTP, but that uses homebrew technology, which, of course, is not runnable on 2.01>.
INDEX.DAT is read-only by default. The most complex part of the MPH (and riskiest part of SXT) downgrader code is the bit that tries to remove that read-only attribute.Quote:
Originally Posted by IndianCheese
You can be certain that the official upgrader has no problems whatsoever if that file is read-only.
why don't you just make a "2.70" update? it would be disguised as a 1.0 update or somthing so it would force you to upgrade to 1.5!!
im probably wrong :(
Done already about 8 trillion times. It doesn't work.