Corrupted Cartridge Fixer Release

  • Thread starter Thread starter skawo
  • Start date Start date
  • Views Views 181,850
  • Replies Replies 709
  • Likes Likes 86
I've been waiting years to post on this thread! Finally saved up enough to buy a New 3DS to mod for the first time, and this application was a large part of the reason I wanted to buy one to mod in the first place :)

Unfortunately my Smash 3DS copy was toast, and while I was not getting many, if any, Hash Mismatches after Pass 1, I was still getting a lot of "Hash stuck"s, and the errors went to a count of around 500 to around 700, so, after booting the game and dealing with the same infinite load screens, I cut my losses, bought another copy for $10, then injected my save into the new physical copy lol.

On the bright side, after around 5 or 6 cycles, my copy of Majora's Mask verified successfully and finally runs beyond the loading screen now. Thank you very much! (Especially considering this one is the more expensive title!)

I also ran through a verification cycle for every other 3DS title I own and it's reassuring knowing there's currently no others which have any issues, and that the refresh cycle itself helps boost the cart's longevity.

Thank you for the incredible tool Skawo! As a collector and preservationist this really made me a bit more hopeful for the future of preserving my 3DS games (the only games out of every generation of Nintendo that have given me any serious trouble maintaining so far haha), and more confident buying pricier titles in the future. :)
 
Last edited by Smajora,
  • Love
  • Like
Reactions: skawo and impeeza
Can this be used to fix standard DS games as well? Noticed both my Pokemon Diamond and Platinum carts both give me the "save data could not be accessed/found" error so I was considering using this program if cleaning the bottom of the carts doesn't fix them.
 
Success! I think...

Bought a cheap Omega Ruby cartridge that was listed as "untested" - of course, didn't work, just crashed when trying to boot it from the Home Screen. Ran the verify, that failed instantly. Ran the regular mode of the cartridge fixer 5-6 times, refreshes were at around 220,000.

Decided to try with the logging, and it showed 48 unfixable blocks. Ran the SELECT mode with logging twice, and this dropped the unfixable blocks down to 24. The run finished with only 48 refreshes. The game was booting and wasn't crashing during regular gameplay, so I was happy enough with that.

Got home from work tonight, and decided to try a regular run once more with logging, the result was the same unfixable blocks:

Code:
Unfixable: 65f84000
Unfixable: 65f86000
Unfixable: 65f87000
Unfixable: 65f88000
Unfixable: 65f8a000
Unfixable: 65f8b000
Unfixable: 65f8d000
Unfixable: 65f8e000
Unfixable: 65f8f000
Unfixable: 65f90000
Unfixable: 65f91000
Unfixable: 65f92000
Unfixable: 65f93000
Unfixable: 65f94000
Unfixable: 65f96000
Unfixable: 65f98000
Unfixable: 65f9a000
Unfixable: 65f9b000
Unfixable: 65f9d000
Unfixable: 65f9e000
Unfixable: 65f9f000
Unfixable: 65fa0000
Unfixable: 65fa1000
Unfixable: 65fa2000

After it ran, I decided to try verify the cartridge again just for giggles, and to my surprise, it didn't fail immediately, and actually ran the whole verification, showing success at the end! Is there a chance this is just the part of NAND used for save data or something?

Either way, thank you for your tool, it turned a bummer cheap pick up into a nice score!

Edit: I ran the SELECT mode once more with logging after this, and now all of the unfixable blocks are gone from the logs.
Game still verifies successfully too, so I guess this truly is a 100% success.
 
Last edited by bache,
Hey I want to ask is something is normal on the fix I'm trying to do on my Omega Ruby.

I only did 1 run (where I canceled it by mistake, but I can already see some improvements on the cartridge) however the main reason it is taking a long time is that on the first block the Hash refreshes very slowly, like I see the "Current hash" update approximately once every minute. Is this normal for the first block on the cartridge? I skipped it on the first run and every other was updating fast.

The other issue I noticed is that on other blocks the Current and Expected Hash were matching, but it would still keep refreshing it.

I wanna if these 2 things are somewhat normal or if it is cause my card is just extremely corrupted and making the process take longer than normal.
 
The first block is actually just the entire EXEFS - which is a somewhat large file, and reading it back takes longer.
The later blocks are just chunks of files, so they don't take nearly as long.
So, yeah, that should be normal, although...

A minute is still quite long. Is that an exaggeration or does it genuinely take that long?
I suppose it's possible that the current hash doesn't change with every read cycle.
 
The first block is actually just the entire EXEFS - which is a somewhat large file, and reading it back takes longer.
The later blocks are just chunks of files, so they don't take nearly as long.
So, yeah, that should be normal, although...

A minute is still quite long. Is that an exaggeration or does it genuinely take that long?
I suppose it's possible that the current hash doesn't change with every read cycle.
I wish it was an exaggeration, but I just stop watched 5 and it was 51-52s every time xD
 
  • Like
Reactions: impeeza
trying to run this for my omega ruby, but as soon as i installed the payload on my console, the payload read as "corrupted". basically, i can't even run the software :/. How do i fix this?
Post automatically merged:

trying to run this for my omega ruby, but as soon as i installed the payload on my console, the payload read as "corrupted". basically, i can't even run the software :/. How do i fix this?
 
trying to run this for my omega ruby, but as soon as i installed the payload on my console, the payload read as "corrupted". basically, i can't even run the software :/. How do i fix this?
You are going to have to provide some more details about how you "installed the payload" and what, exactly, is reading it as "corrupted". Did you follow the installation instructions in the first post?
 
  • Like
Reactions: impeeza
You are going to have to provide some more details about how you "installed the payload" and what, exactly, is reading it as "corrupted". Did you follow the installation instructions in the first post
I did. I downloaded both files, and put them inside the payload's folder. Now when I start the console on godmode9, it asks me what payload to run. Both of skawo's error out when run. It says "payload is invalid of corrupted", or something along those lines. The console then boots again. I can only run the non-forked payload.
 
Thanks for your work shako!

I unearthed my old 2ds because I have to travel a lot by train for the nect two month. Sadly, my copy of Fire Emblem Echoes, which I bought new in 2016 or so, did not work anymore.
That annoyed me enough to mod my 2DS in 2026 lol.

But I still wanted to repair my cartidge; that's how I found your thread.

The refresher runs for a week now. It was at 98% when I went to sleep and when I woke up it was at 15% again.
Now in the afternoon it was 1% again, but progressing fast (already at 14%).

I ran the program while pressing "x" (because the first time I ran it without the function, it got stuck on hashes very often).

Does the program automatically repeat itselfe after each run, or are this just different data blocks (each with its own percentage)?

I am at 44.8 million refreshes now.

Thanks for your time.
 
There are a few bars, but the first couple are supposed to finish very quickly. It should say on screen which part is being fixed - EXEFS and ROMFS can take very long.

If it's taking that long, it's unfortunately likely that it's unfixable.
 
  • Like
Reactions: impeeza
hi, so i have this problem where when i'm fighting the 3rd gym leader on my alpha sapphire game and he is about to send his 2nd pokemon the game crash.
my 3ds is already modded so i'm asking just to be sure, do i have to delete on my sd godmode9.firm and replace it with the 2 files on github or is it going to brick my device ? or maybe i just have to had them all without deleting anything ?
 

Site & Scene News

Popular threads in this forum