-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to dump flashcard #153
Comments
Try it again in GodMode9 (check the cart drive, C:), then report back. |
it is reported as 0 Byte |
I need more information. Is the only entry you see in there the virtual ".." entry? The one that on A returns to the containing folder? Or do you see any filenames? |
Only the virtual ".." is visible and there are no other files or folders And to be clear, the home menu shows the icon/banner of the cart. |
Well... I have my doubts the problem is in D9 or GM9. It is very much possible that flashcard is simply defective. I'd suggest you try dumping it in Woodumper (if you can get a hold of a compatible console), or otherwise simply ask around elsewhere. |
If it displays the icon on the home menu and can be launched isn't it safe to conclude something is with d9 and gm9? There clearly is something wrong with the cart because it no longer completely boots without the reset slot 1 thing. But the parts that do work should show up in gm9 |
I fixed my cart, but gm9 still does not see it |
Well... what do you mean by fixed your cart? Does it work in D9 now? Also, don't make such assumptions, even if they work most of the time, flashcards are special. They use exploits etc when the dumping code in D9 / GM9 is made for regular retail cartridges. |
By fixing the cart i mean flashing the original firmware to it. Restoring its fuctionality in the sense that it now works normally from the home menu. I am assuming D9 / GM9 are capable of dumping everything and have feature parity or even exceeding that of older apps like wooddumper. I understand now that this assumption is incorrect. As for D9, it still shows the same error as my first post and GM9 still shows an empty directory. |
Well... the code in D9 / GM9 is completely rewritten. Woodumper is closed source, too, so it's not like we can take too much out of it. It is possible that there are carts out there for which Woodumper works and D9 / GM9 does not. This is why I'm asking you to try it in Woodumper. Con you do this and let me know the result? Btw, I'm assuming something in that cart makes the cart type (3DS or DS?) check fail. |
Okay, one more thing to try... Could you try this test build? |
Unfortunately that test file still shows and empty folder. In the mean time i am trying to figure out how to use wooddumper on a 3ds :) |
I tried various version of wooddumper on a 3ds and a dsi and they all hung indefinately on "reading secure header" i hear "NDS Backup Tool wifi" has a higher successrate but it takes a lot of work to configure and i already solved the issue that started this quest. (being the ability to boot the cart from the home menu) What i did discover however is that wooddumper can dump the m3 ds simply, this card also cannot be read by GM9 or be dumped by D9. I guess this issue can be closed then unless you want to further troubleshoot the m3 ds simply and see if that brings gm9 any closer to displaying its contents |
Tbh, I'm unsure about how to proceed with this. Improving the cart dumper is a bit like stumbling in the dark, pushing switches until one works (and maybe amkes something else no more work). I'm still closing this now, but I added these two flashcarts to the list here: Can you tell me the output when trying to dump the M3 DS Simply in D9? Maybe provide the log? But, please, continue in the other issue. |
I am trying to dump my flashcard to figure out what, if anything, is wrong with the header of it.
When i try do so however i get the following screen
Dump cart [full]
Cartridge id FFFFFFFF
cartridge type CTR
error reading cart NCCH header
the cart is an r4i from r4.ndsi.in which should not be detected as CTR
The text was updated successfully, but these errors were encountered: