- Thread starter Zar
- Start date
Yes, there is a Evilnat is working on a 4.89.2. A beta is available in this link
I guess you are asking if ManaGunZ work on Evilnat 4.89. I haven't confirmed myself, but it should work fine on 4.89 since LV1 & LV2 of firmware 4.88 and 4.89 have the same offsets.
version 1.41 runs on Evilnat firmware 4.89.
I want to know exactly about my mistake, why it does not copy the image from the IRD.
Will version 1.39 work on firmware 4.89?
Last edited by a moderator:
sandungas
Developer
Is a little bug, the solution you should use temporally is mentioned here:
https://www.psx-place.com/threads/managunz-ps3-backup-manager-by-zar.1198/page-77#post-339972
I would not say 1.39 is better, what happened is in the last ManaGunZ versions @Zar was implementing support for encrypted dumps, IRD, and other stuff related with encryption, and while doing that he had also to improve the info given by the error logs, add some options in the interface related with the error logs, etc...
All that new features introduced a couple of little bugs, but are not critical and i guess will be fixed in the next version
I turned on the log, here's what happened:
https://ibb.co/QQkrhY4
Next, I included the DUMP log:
https://ibb.co/Dg8drbZ
Let me remind you, firmware evilnat 4.89.
Hello all,
I am very new to the PS3 cfw scene. Just flashed Evilnat 4.89 and installed Managunz 1.41. It was working for a bit and I was enjoying the UI. Seem to have hit a few bugs changing settings. First it seemed to delete all the boxart, but I could change views. Now if I try to change any of the UI settings (view or toggle on/off options) the app freezes and I have to force a power down. I have tried installing a nightly release over and deleting and reinstalling the stable package. Is this a common bug? Are there any other steps I should be taking? Thanks.
I am very new to the PS3 cfw scene. Just flashed Evilnat 4.89 and installed Managunz 1.41. It was working for a bit and I was enjoying the UI. Seem to have hit a few bugs changing settings. First it seemed to delete all the boxart, but I could change views. Now if I try to change any of the UI settings (view or toggle on/off options) the app freezes and I have to force a power down. I have tried installing a nightly release over and deleting and reinstalling the stable package. Is this a common bug? Are there any other steps I should be taking? Thanks.
@Zar the same problem for me was that the log was disabled, now that i enabled the log the dumping process of decrypted iso works fine. please enable it by default in the next release to avoid issues for other users. is there a hash database for decrypted isos to verify the images just as redump for encrypted isos?
sandungas
Developer
In PS3 the hash of the decrypted ISO cant be considered a secure check, because along all this time there was published several tools to create them, and every tool (sometimes even in between versions of the same tool) generates an ISO with small differences
The way to go is to check the hash of the files inside the ISO, for this purpose it was created the IRD format
The IRD files are like a list with the hash of every file in the disc + some more "metadata" from the original disc
In managunz there is an option to "IRD check" (in the game options at bottom, i dont remember the exact name in english), at the end of the process it should return a message telling you if all the files matches with the original disc with some kind of "success" message
Managunz can create IRD files too, if you insert an original PS3 BD game disc and you click in the game options you can make the IRD for that disc (and optionally you can use the option to send your IRD to managunz database)
This is an IRD database based on algua's backup of Jonnysps ird library (2758 ird files, 01/17/2019) + SamRohod's ird database (123 entries, 10/27/2021) + Zar's ird database (185 entries, 1/13/2022)
http://ps3.aldostools.org/ird.html
This is ManaGunZ database
http://ps3ird.free.fr/
Last edited:
Ird contains hashes of header + files + footer also hashes of regions of the iso. Why It doesn't use just 1 hash of the whole iso ? I think it's because backups were mainly dumbed as JB format (a directory). The goal was to go from JB format to original ISO, to make it working perfectly on the ODE. I used IRD format for the same reason most people use JB format, and IRD allow a check JB format.
Unfortunatly, I don't think there is hash database of decrypted ISO.
@Zar I don't see the reason why not incentivize ps3 users to drop jb format and start using decrypted iso as standard at least for playing purpose. jb is a messy container and has to rely on ird, it's even unpratical to store and could be modified in the structure cause it's stored as a folder, while decrypted iso colud be unambiguous if the community choses to use a certain creation tool such as yours from now on. now we have multiman that is almost gone even if working, and we have your fantastic homebrew that has been elevated to standard from the redump community, it's the only tool updated at the moment, it's capable to create encrypted iso (for preservation purpose, matching redump standard) and decrypted iso (for playing on console and emulators).
@aldostools @sandungas I don't understand why we have to use nowadays ird files. these irds are only a legacy of the past, nobody wants to use a mess of folders and files with metadata that tell you that all files are matching if you could do the same job with a single iso and no other junk but just his own hash. If we start our own metadata database based on a unique tool we could fight the past.
My theory obviously focuses on the fact that decrypted iso mentioned above is the actual data used from the console, not the encypted one read from the optical drive (if i understood correctly how it works)
@aldostools @sandungas I don't understand why we have to use nowadays ird files. these irds are only a legacy of the past, nobody wants to use a mess of folders and files with metadata that tell you that all files are matching if you could do the same job with a single iso and no other junk but just his own hash. If we start our own metadata database based on a unique tool we could fight the past.
My theory obviously focuses on the fact that decrypted iso mentioned above is the actual data used from the console, not the encypted one read from the optical drive (if i understood correctly how it works)
sandungas
Developer
The problem is the PS3 ISO format is not an standard, the resulting hash of the ISO depends of the tool/version you used to create it
Nowadays we can consider the most standard are the ISOs generated by "makeps3iso" because is the only 100% open source project (candidate to be fixed or updated if at some point someone realizes is needed)
As far i remember there are a few missing features from backup managers (mutltiboot discs, and some rare games that still have probems when played in ISO format), are the kind of problems where we are not sure if the root of the problem is in the payload used by the backup managers.... or in the PS3 ISO format... or both
So theoretically the PS3 ISO format could change again in the future
Nowadays we can consider the most standard are the ISOs generated by "makeps3iso" because is the only 100% open source project (candidate to be fixed or updated if at some point someone realizes is needed)
As far i remember there are a few missing features from backup managers (mutltiboot discs, and some rare games that still have probems when played in ISO format), are the kind of problems where we are not sure if the root of the problem is in the payload used by the backup managers.... or in the PS3 ISO format... or both
So theoretically the PS3 ISO format could change again in the future
Does ManaGunZ use makeps3iso or another tool? Oh maybe it's too late, but dumper community is awesome, they can cover the entire catolgue in a year or so. This must be done, and even if the dumping mode changes, tools are updated, the dumps change. Even on redump the methods changed and everything had to be redone from the start. Is it possible to create an own ManaGunZ database hardcoded in every release of the app? Or consultable online just like aldostools lsd ird and other databases?
This is what I try to do and try the md5 they are fine but when applying the config it crashes or freezes, I have cfw 4.82 and Managunz 1.41
The same game persona 3 fes (SLUS_216.21) and the Official Net config of ps2 classic
Last edited:
sandungas
Developer
If the MD5 check of the ISO matched im sure it should work, because is mentioned here:
https://www.psdevwiki.com/ps3/PS2_Classics_Emulator_Compatibility_List
Try to copy the config file manually (with a filemanager or FTP) next to the ISO, and download it from this database:
https://ps3.aldostools.org/ps2config.html
*Note the config for SLUS_216.21 appears in the database in 2 formats:
NET (decrypted for CFW)
ENC (encrypted for HEN)
Last edited:
Sorry, I did not explain the config well, I made it work manually, but when I tried to load it, the config in managunz freezes in the ps2_netemu.self option of the official config of ps2 classic, I tested with many games and with config (NET) and only with this one this happens
I think it's a managunz error, can someone check this?
Similar threads
-
PS5 Porkfolio All in One PS5 Utility (Game Library, Backporks, FTP Transfers, Cheats, Saves, Pa- Started by Red
- Replies: 0
-
-
-
PS3 [Tutorial] Update Frankenstein PS3 Firmware That is Too Low to Initialize RSX (< 3.41) (NAND Models)
- Started by byt3swap
- Replies: 0