forums.ps2dev.org

the 1.50 updater fails to run on psp-1007 because the scechkuppkg module doesn't think the psp is a legit retail model (it performs a idstoragelookup() on the model key but it gets an unknown keys as an answer so it believes the hardware you are trying to run the updater on is not a retail hardware ...

yes but if some is banned and want to share something with the scene he can't because some mods presume they possess sony's sdk... or some others because they shared something as a proof of concept and mods define it as illegal, I do understand how important is the issue between you and sony I do kn...

As yoshihiro's changes weren't put into the pspsdk, its not surprising someone else may come along and eventually fix the same thing while unaware of it already being done elsewhere. They weren't in the pspsdk because you banned him... What I can't also get is why Yoshihiro was banned from ps2dev b...

jonny what do you think of using the atrac3 codec into the next PMP format ? It would save up cpu processing as we have the atrac3plus lib reverse engeneered that uses the ME.

It could allow people to use AVC+AT3 pmp files which would be a great improvement.

That was me, I think Drakonite removed the post for an unknown reason, it was talking about how to write to the flash in game mode. I think he deleted it because it was containing some plain text of one of the updater's modules. Although it would be as legal as posting a version.txt content. I was s...

Well from my point of view I don't think that fw 1.00 was what I'd call secured. You could run any decrypted elfs as long as it was packed within a pbp and reverse engeneering the how the pbp is done isn't rocket science. I wonder what LoadExecForKernel_28D0D249 in newer firmwares need to actually e...

so, vshAvcResumeDebugGetVTimerBase cannot actually be used to run homebrews on 2.00 because LoadExecForKernel_28D0D249 wont run decrypted elfs ?

Great finding ! :) I think Mathieulh spoke somewhere on this forum of some hidden debug functions within vshbridge (without giving further details) it seems to be one of them. I am no expert but I presume that it is just a forgotten debug function forgotten in the retail firmwares that doesn't do wh...

The index.dat encryption simply changed, that's all. All the firmware revisions from 1.00 to 2.01 can load decrypted index.dat (aka version.txt) and share the very same index.dat decryption keys while 2.50+ cannot load decrypted index.dat and cannot load old index.dat (featuring another encryption) ...

you could try replacing the prx files in the data.psp, although if it relies on new 2.7 syscalls it most likely won't boot still. You cannot actually decrypt a prx unless you can run kernel mode code, and as far as I am aware, the 1.00/1.50 firmwares do not possess the required keys to decrypt this...