As we have now a lot of different possible hack attempts, I though it would be nice to reference somewhere all things that doesn't work (to avoid other people having the same ideas loose some time).
In this attempt, I had in mind the following thing:
- Copy every files of PSM Assistant for Unity directly at the root of "ux0"
- Change pathes of PCSI00009 inside "app.db" from "ux0:app/PCSI00009" to "ux0" (table "tbl_appinfo", key 2593862978) and "ux0:app/PCSI00009/eboot.bin" to "ux0:eboot.bin" (key 3022202214)
- Start the homebrew "FTPVita-app0-readonly" to be able to browse all the "ux0" content (app0 would become ux0)
Well, before trying directly on "ux0" (where I couldn't control easily all the files), I started doing it on "ux0:/pspemu".
Unfortunatly, as the title of this topic says, it fails. It seems that it is not possible to have a "eboot.bin" somewhere else than in "drive0:/app/TITLEID". On the start of the application, it results in a "C1-6761-0" error (error from application NPXS19999).
Another interesting point is that the error is not exactly the same if the key 3022202214 targets a path where there is no "eboot.bin" file: it results in a "C0-13006-0" error (also error from application NPXS19999).
Finally, it seems that the path in the key 2593862978 (folder path without "eboot.bin") has absolutly no incidence on the application behavior (only the path with "eboot.bin" matters).
All those errors cannot be found on this page:
http://vitadevwiki.com/index.php?title=Error_Codes
Is there any "official" documentation about those 2 different error codes ?
What is the application "NPXS19999" ?
Thank you for your attention, hope to see some other hack attempts (even if it fails, it could leads to some interesting information and avoid time loss)
Advertising