I usually generate new versions using the CLI and my prefered list of patches, sometimes with the manager (at which time I usually go through the patch list again cuz the last build the manager did for me before that usually was ages ago 🤣)
I do not know if you spotted this already regarding the longer serial no, but the longer ones all start with the same string BQAAF01. The s/n will be the same length as the older s/ns once you omit this part from the s/n (namely, 16 characters)...
So if the newer revanced versions require the new GMScore (or w/e it is called), we could uninstall the old vanced MicroG package right? Or does reVanced need both of these?
Is that something like those 50-in-one "Zii" thingies you saw back in the Wii-era? 🤣
Edit: I just checked out the topic OP reffers to, and over there OP posted a whole bunch of related technical information regarding the console, this issue and...
the hell is a zeebo? Never heard of this console (or BREW, fwiw)
If all you are trying to do is access the internal filesystem, assuming it is contained in a single IC/EEPROM, couldn't you just physically dump out the chip with a programmer like...
i could fire up my save dumper and dump mine for you, but as I don't have any of the dlcs those could still be locked (idk, does buying a dlc automatically add the fighter to the roster? :P). I just got the 'unlocked all fighters' milestone :D
you know that you can revert the controller fw to the previous, correctly working, state? I experienced an Series-controller which said it had an fw update, after which I could not get it to connect to any pc or system over bluetooth anymore...