Toggle sidebar

Corrupted Cartridge Fixer Release

  • Thread starter Thread starter skawo
  • Start date Start date
  • Views Views 213,807
  • Replies Replies 826
  • Likes Likes 95
skawo said:
Well, I did not add this since you're supposed to look at the chunks report at the end. I suppose I could do that, though, and just save the report to a file...
Click to expand...
Well, that’s what I mean: I could not see the result because the console turned itself off at some point well past after it finished verifying, several times, and I do not know what makes it turn off.
 
Curious if someone could help. When attempting repair it just gets stuck the first time it hits something it can’t fix. I have to hit y to skip. Does it not do that automatically so I can see the total number of errors? I didn’t want to sit for hours hitting y every time it gets stuck.

For reference this is a copy of Omega Ruby that will not boot.
 
glauberlima said:
Thanks a lot for testing this and for the detailed notes — this is genuinely useful.

The important detail is that the refresh counter stopped completely and B/Y did nothing. That's not the "it's just retrying" behavior — it means the tool is stuck waiting on the cartridge itself and can't even poll the buttons.

The 82M-refresh run was one failure mode; the frozen-at-277 (and 193/73/19) hangs are a different one, and the decreasing numbers across reseats suggest the cartridge is progressively failing to respond.

To answer your question directly: if the refresh count doesn't change for ~60 seconds, it is hung and waiting longer won't help. You can stop it.

We're working on a timeout for the cartridge read path so it can't sit there forever, and so it reports a bad cartridge instead of freezing.

Before that, a few things would really help us:
1. Can GodMode9 read this cartridge at all through other paths? E.g. browse the gamecart drive, or try dumping any file from it. Does it also hang, or does a dump complete?
2. Do you have a known-good cartridge (or another game) to test with? Does the fixer / verify complete normally on it? We want to be sure a timeout won't hurt normal reads.
3. When it's stuck, is the refresh counter completely frozen (unchanged for 60s+)? Does the screen still redraw anything, or is everything frozen? And does the POWER button still shut it down normally?
4. How fast does it hang now — seconds after starting? Is it always on the first file in the EXEFS step?

Thank you very much for your feedback!
Click to expand...
My cartridge also does the game thing. I thought the version shared here the other day worked fine, but that did crash after a couple hours.
1. It doesn't crash at a consistent refresh count, sometimes it will crash after 15 mins, sometimes only 1 min.
My cartridge also tends to do the game thing.
2. It doesn't crash at a consistent refresh count, sometimes it will crash after 15 mins, sometimes only 1 min.
It is fully stuck, nothing happens when holding B, pressing the power button. Nothing else is drawn on the screen.
3. Fixer and verify does work on the working cartridges I have with no issue.
4. It always crashes on the same file, at the first chunk.

I have checked the md5 checksum of the 3ds file after each run and the data has not changed.
I also kept the cartridge in the 3ds whilst in sleep mode and have checked the md5 checksum after a while. It does seem to change after a while.
 
Vegeta77 said:
Curious if someone could help. When attempting repair it just gets stuck the first time it hits something it can’t fix. I have to hit y to skip. Does it not do that automatically so I can see the total number of errors? I didn’t want to sit for hours hitting y every time it gets stuck.

For reference this is a copy of Omega Ruby that will not boot.
Click to expand...
Hold X when starting to enable autoskip.

@Philippo
Click to expand...
It's weird these hangs only started getting reported now. Can you try version 1.4? That one to be stable for a very long time...

@Vegeta77
Click to expand...
Oh, sorry, I misread. Weird, I'll have to look and see if godmode turns the console off when it's idle for a while. Meanwhile you can enable the logging with Y to get a report every time, I guess.
 
Last edited by skawo,
skawo said:
Hold X when starting to enable autoskip.


It's weird these hangs only started getting reported now. Can you try version 1.4? That one to be stable for a very long time...


Oh, sorry, I misread. Weird, I'll have to look and see if godmode turns the console off when it's idle for a while. Meanwhile you can enable the logging with Y to get a report every time, I guess.
Click to expand...
Unfortunately 1.4 seems to also hang. Current hash doesn't even seem to change on that version before crashing.
 

Site & Scene News

Go to forum More news

Popular threads in this forum