Corrupted Cartridge Fixer Release

  • Thread starter Thread starter skawo
  • Start date Start date
  • Views Views 201,883
  • Replies Replies 761
  • Likes Likes 91
Some hashes can take a very long time. 1000+ retries isn't actually uncommon.
If it is really every hash though then, yeah, probably too far gone, though...
 
Hello, I'm currently going through my 3DS collection to verify them and I got to Omega Ruby and, of course, it didn't pass verification.

I've run the fixer 4 times total, and it found 0 unfixable chunks every time it finished, yet it still didn't pass verification.

So earlier in the thread I ran across the following post:

You're correct, the tool only goes over actual files so the padding area is not touched.

You can attempt to stabilise the padding area by holding SELECT while going to calculate SHA-1 of the entire cartridge (without dumping it).

I personally wouldn't, though; straining the cart further really doesn't seem like a good idea.

As for what the padding should be, it appears it's usually 0xFFs.

After doing this, it passed verification multiple times.

I just have a few questions regarding this feature.

Is this feature specific to your version of GodMode9 or is it also in the base version?

And how exactly do I ensure it calculates hashes for the entire cartridge?

I just clicked on the .3ds file, held SELECT and clicked on Calculate SHA-1.

Is that correct or do I need to somehow select all the files from the cartridge?
 

Site & Scene News

Popular threads in this forum