Corrupted Cartridge Fixer Release

  • Thread starter Thread starter skawo
  • Start date Start date
  • Views Views 199,275
  • Replies Replies 749
  • Likes Likes 91
Made an account to reply to this - I have a bit of good news, some bad news, and also some VERY interesting news. My Pokémon Y cartridge was corrupted, so I ran this fixer many times.

Good news: Before I ran it at all, it simply would refuse to launch. After running it once and it doing a shitton of hash refreshes, it now boots and loads into the game!

Bad news: Some chunks still seem permanently unfixable. I’ve run it probably around 10 times, and with a total of around ~1,400 unfixable chunks, I am always running into them at the same percentage with around the same amount of chunks each time. I haven’t been able to do extensive testing, but it crashes at the start of the Lysandre battle in Geosenge Town about 99% of the time.

INTERESTING news: Despite this, dumping the cartridge as is into a CIA and running the game digitally from microSD card does not crash at the Lysandre battle at all. This suggests that some corrupted cartridges might still functionally work for dumping digitally, which is honestly a textbook case of a perfectly legal and valid reason to dump one’s cartridge for use on a modded 3DS.
EDIT: Forgot to add, cartridge fails verifications instantly, but the dumped CIA passes verification successfully.
Post automatically merged:

Update to my post above, this got… weirder and I no longer have a clean story. What I’ve confirmed since:
- Cart fails GM9 verification instantly, every single time.
- I dumped the cart, extracted it with 3dstool, and hash-compared every file against an extracted dump of a known-good copy (same game, same region). All 690 RomFS files identical. ExeFS identical, including code.bin. So the game data on my cart reads back intact.
- That first CIA passed GM9 verification and played through the Lysandre battle in Geosenge many times with no crash.

A few days later (just now) it stops making sense:
- Did a fresh dump and fresh install tonight. That second CIA also passes verification, buuuut it crashed at Lysandre twice.
- Went straight back to the cart expecting a crash, and the battle started fine for once…
So the crash doesn’t track with verification status, and doesn’t track with cart vs. digital. A verification-passing CIA crashed; the verification-failing cart didn’t. The cart still fails the large majority of the time, but not always. Crash is 0xd900458b (invalid RomFS or savedata hash), process 39. One constant I haven’t isolated is that the same ~40 hour save file is used in every test. I don’t have a pre-Lysandre save to compare against, and a statically damaged save would presumably(?) fail deterministically rather than ~95% of the time, so I’m not confident that’s it either.

No idea what to make of this tbh.
 

Attachments

  • IMG_9549.jpeg
    IMG_9549.jpeg
    507.2 KB · Views: 1
Last edited by Pokebert,
What do you get when you run the fixer with logging?

crashes at the start of the Lysandre battle in Geosenge Town about 99% of the time.
That kind of sounds like it might be some physical connection-based issue, or that chunk is in the process of stabilizing.

You should also try to delete the update data for the game and redownload it. Could have an issue there.
 
Oh, I see. I'm an idiot.
Posted new version with fixed chunk counter.
New version returns 128 unfixable chunks. Game still boots. No idea where it will crash. I’ve bought a new cart from eBay that passes verification. I will now move my save over and recreate digital copies from this clean cart (the other cart made them in around 2018, so probably not corrupted, but who knows).
 
Hello! You’ve really saved my cartridges, my Pokemon Y, Smash Bros and my Omega Ruby! Thank you very much!! Im trying to fix my Pokemon X this time but it fails to verify.
When I end the fix process it always shows that there are 0 unfixable chunks but still doesnt verify. What can I do?
I just created my account here since I wanted to thank you in this thread and let you know this stuff its amazing!!
 

Attachments

  • IMG_6987.jpeg
    IMG_6987.jpeg
    2 MB · Views: 1
Which version of the program is that?
I recently updated it because there was an issue with the chunk counter.
If it's the latest (1.6) then try running the fixer with logging and tell me what appears in the logs in gm9/out/
 
Hi! First of all thank you for this tool, hacky or not. Neat work!

Secondly, I have a feeling this OR is cooked. Save is still accessible thru PKSM/Checkpoint. Says Game card cannot be used when booted.

Put this on last night, (it had been running for about 12 hours) and I've cancelled it a few times because it gets stuck. It got into the 10 millions of refreshes and only barely moved into the 1% on the load bar, the clock never changed and the ETA never updates. I don't know what to do here, or if I should just call in the towel.
20260821_160952.jpg
 
Yeah, probably dead unfortunately :(
Well at least the save file's recoverable, I guess. It was a launch copy of OR too, so I suspect it's got issues like a lot of them and the PQ copies. If it's totally cooked after tomorrow, I'll try to split the casing and give it a reflow, just to see. I'm not holding out hope but if it's working again after that, I'll update y'all.

I did just run all my other carts through it, (Ultra Sun, X, Y, Sun, Moon, Animal Crossing New Leaf) and they all had a variety of verification fails to begin with, so set them through a fix cycle and it only took one and now they all verify flawlessly. I'll be more vigilant this time on playing them occasionally! Mark 1 as failed and 6 as fixed!

Once again, thanks SO much for this tool. It's incredibly cool! :yay3ds:
 
So, I ran all my cartridges through verify just in case.
All of them ran fine, except for Xenoblade Chronicles 3D (European).

This one, works good in game (At least for what I tested), but I cannot verify integrity nor fix cartridge.

When I verify, at 0%:

"C:/000400000F700200_v00.3ds
Content0 (EAF76000@00004000):
Verification failed"

When I try to fix, fails at 0% also:

"C:/000400000F700200_v00.3ds
Content0 (EAF76000@00004000):
Fixing failed"

I already uninstalled updates through the settings app, and it's the same.

Any clue?

Thanks

Edit: I just saw on github this is a know issue. but even on the latest godmode9 (2.2.3), fails
 
Last edited by SnakeGS,
I'm not sure. Since it fails on actual godmode, then I suppose there must be some bug upstream in the base program.
I don't have any n3DS cartridges to test with :c
 

Site & Scene News

Popular threads in this forum