Corrupted Cartridge Fixer Release

[Emdel]

Try to redownload the update data, then - maybe it just got corrupted on the SD card, or something.
Will mark this as partial fix, in any case.

Might also be a good idea to use GodMode9 to dump your cartridge to a .cia, extract the ROMFS and compare it with a working one to see exactly what's corrupted.

I dunno, I think it's a true fix though, because before running the tool, it threw up the same ARM11 error you mentioned on my N2DS with CFW.

 

[Deer]

How long is it supposed to take? My Refresh count is at roughly 4.1 Million and 11% into the ROMFS section so I'm worried I'm fighting a losing battle. Do I just trust the process, or should I just cut my losses and figure something else out?

 

[skawo]

It takes longer the more corrupt the cartridge is, but as long as it's progressing, it should be fine. That said, if you're seeing blocks getting "skipped" a lot, then, yeah, it's probably too far gone :c

 

[DinohScene]

I haven't touched my retail 3DS carts in 11 years...
I really ought to check them all.

 

[skawo]

Incidentally, actually, for checking carts, GodMode9 has a verify function which checks all the files, a more thorough check than just trying the cartridge out. A cartridge might start but still have some random files corrupted.

 

[Deer]

It takes longer the more corrupt the cartridge is, but as long as it's progressing, it should be fine. That said, if you're seeing blocks getting "skipped" a lot, then, yeah, it's probably too far gone :c

Alright, I'll keep that in mind and keep an eye on it. It'll probably keep going for the next few days at this rate lol

 

[UltraMoonTrainer]

Hello! I just used this to fix my Pokemon Omega Ruby, it would crash everytime I entered a pokemon center and after using this tools it no longer has any issues.

 

[Deer]

Okay, good news and bad news. The good news is I'm no longer getting an immediate arm11 error. The bad news is I'm now getting a generic error 39 (quartz).

I know there are like 2 hashes at 2% that haven't been fixed yet but the tool spent the better half of 6 million cycles trying to fix it with no luck. I'm half tempted to cope and cycle it again for the next few days but maybe theres a fix for this specific error? Any advice?


Or maybe I just bite the bullet and call it dead which sounds pretty realistic actually.

 

[skawo]

Sounds like originally you had an ExeFS (code) corruption error, but now there's still a crucial ROMFS (filesystem) game file that's corrupted.

If it's just a couple hashes, I would definitely try to run it again for a while. As long as the 'Current hash' is changing while fixing one, there's a chance.

You could also dump your game (The "build cia" option), extract the ROMFS and compare to a good ROMFS to see exactly which file is corrupted. I could then build a little specialized thing to only run on that file. Or, you could use Layered FS to make a patch that redirects reads of that particular file to the SD card.

 

[Deer]

Sounds like originally you had an ExeFS (code) corruption error, but now there's still a crucial ROMFS (filesystem) game file that's corrupted.

If it's just a couple hashes, I would definitely try to run it again for a while. As long as the 'Current hash' is changing while fixing one, there's a chance.

You could also dump your game (The "build cia" option), extract the ROMFS and compare to a good ROMFS to see exactly which file is corrupted. I could then build a little specialized thing to only run on that file. Or, you could use Layered FS to make a patch that redirects reads of that particular file to the SD card

Okay, if I were to send over the game dump, where would it be best to put it? I don't know if this site allows us to through out game files

 

[skawo]

Probably best to move it from here. Sent you an invite link to my Discord.