D
Deleted User
Guest
Fuck's sake, I was actually planning on buying a copy to play later on when I had the money.The game has been pulled in the US.
Still available in EUR. Better hurry if yous wants it.
Fuck's sake, I was actually planning on buying a copy to play later on when I had the money.The game has been pulled in the US.
Still available in EUR. Better hurry if yous wants it.
It's kinda sad how they had to take down VVVVVV just because of a secondary homebrew exploit, something that isn't even useful to us anymore unless you're having trouble using Smashhax to downgrade and need a secondary exploit too. VVVVVV is actually a really good game, one of the first I bought when I got my O3DS. And now, nobody will be able to experience it until they fix the glitch. :/
Also it's still available in Europe/Oceania.Well it is still available for download using DTK/FunKeyCia. Not to mention the usual sources.
any ways what if the maker of vvvvvv does not know how to patch exploits his game will not be on the eshop anymore i mean its kinda a bug but you need to know how it works to fix it and the maker of vvvvvv did not make the exploit
The writeup should be enough for Terry to know what to fix, I don't plan on exploiting VVVVVV twice (that'd just be mean at this point). Basically just add size-checking arguments to the XML parsing, easy as that.Maybe ShinyQuag should write a letter to Terry detailing how to patch the exploit so it can be readded to the shop (or maybe not, as they haven't taken it from the Eur eShop yet)
Ah OK cool, I hope he does fix it then, V6 is such a great game, shame for people to miss out on it! It would be interesting if all the publicity made people hear about it and then buy it after the patch (I've never seen the game advertised before, I only heard about it from friends). And then Terry deliberately puts vulnerabilities in his future games hoping for the same effect :-pThe writeup should be enough for Terry to know what to fix, I don't plan on exploiting VVVVVV twice (that'd just be mean at this point). Basically just add size-checking arguments to the XML parsing, easy as that.
Just because you don't want them to patch things doesn't mean they don't have good reasons for doing so.idk why nintedo keeps patching this its not going to make things better
Thank you so much, it worked first try after doing that!You need the salt_sploit_installer folder in your 3ds folder on your sd as well as the two vhax_installer files in the root of the 3ds folder.
You need arm9 access to get the per console sd key (movable.sed). If you actually have that kind of access, primary/secondary entrypoints are of little concern.I've been pondering if the 3DS system's own Save-Data Backup/Restore functionality could possibly be used to install an exploited gamesave.
Using two 3DS systems that both have VVVVVV installed, I tried this:
I did this and it said the save data was successfully restored, however upon loading VVVVVV on the secondary system, this just created new save data.
- Install V*Hax on primary system
- Backup VVVVVV's game save from primary system using Save-Data Backup
- Copy .sav file from primary system's SD card, located in sdmc:\Nintendo 3DS\(ID)\(ID)\backup\000\titleID\00000001.sav
- Note that 000 may be 001, 002, corresponding to the Save-Data backup slot used. You get up to 30 slots.
- For VVVVVV, the titleID is 0004000000096100
- Backup VVVVVV's game save from secondary system using Save-Data Backup
- On the secondary system's SD card, replace the .sav file located in the same Nintendo 3DS backup folder, with the exploited .sav from the primary system
- On the secondary system, open the System Settings, under Data Management perform a save data restore for VVVVVV
Chances are, the Save-Data Backup process is encrypting the save to only be restorable to the system that backed it up.
So in other words it didn't work, I couldn't back up an exploited save from one system, and restore it to another system.
This makes me wonder if you couldn't install the exploit another way.
What if you could perform the Save-Data Backup on the system to be exploited, retrieve the .sav file, decrypt it using a PC tool or at least a second homebrew enabled 3DS. Then modify the decrypted save with the exploit, re-encrypt the save file and put it in the backup folder.
Perform a Save-Data restore, and hopefully install the exploit that way.
What do you think, is there a chance this could work?
It would mean V*Hax could turn from a secondary exploit to a primary if you can manage this with just a PC.
You need arm9 access to get the per console sd key (movable.sed). If you actually have that kind of access, primary/secondary entrypoints are of little concern.
Not a new hax bro..if it was new would have been primary instead lol