If you downloaded the files from the Mega link on the tutorial in the OP, and run setup as normal, then you should've have a directory, C:\Program Files (x86)\Datel\Action Replay DSi Code Manager, and it should look like this.
I saw. Did you even open the exe "setup"? Or did you download from the MEGA link in the OP, https://mega.nz/#F!H0kVjYjQ!aamHbp5TDL-4Uidut6tO4A? Because in there is a zip that has ActionReplayDsiCodeManagerSetup-2018.exe, and you run that and go through all the default settings.
Off the back of the messing around with my non-worky ARDSi, I can now get the code manager to treat a few custom files as firmware files (I don't get the "Not a firmware file" error any more) but it won't apply it because the checksum is incorrect this time (So it thinks they are corrupt firmware files now). Progress? Probably not, but at least I haven't horribly bricked the thing with all this blatantly-incorrect firmware writing 
I'm probably barking up the wrong tree with this, but it's pretty interesting nevertheless, I'm also happy to help out with my rather limited programming knowledge if anyone else wants to work on/is working on a solution for the 3ds compatible ones
I'm probably barking up the wrong tree with this, but it's pretty interesting nevertheless, I'm also happy to help out with my rather limited programming knowledge if anyone else wants to work on/is working on a solution for the 3ds compatible ones
If you followed everything in the tutorial and it still doesn't work, then either it's not actually supported, or you have the magnet is not placed in a more precise spot.
Just a quick update, I've been able to restore my ARDS Media Edition by rebuilding a firmware file from a ROM I dumped a while ago, which proved to be way easier than I expected. I also checked if a regular ARDS firmware could be booted from the ARDS ME's Media Player function and it works, so a flashcart won't be needed anymore to install NTRBoot on an ARDS ME.
I've got an exam in a couple of days so I really don't have a whole lot of spare time but I'll write an ARDS firmware toolkit and an easier guide on how to flash NTRBoot on one as soon as possible.
I've got an exam in a couple of days so I really don't have a whole lot of spare time but I'll write an ARDS firmware toolkit and an easier guide on how to flash NTRBoot on one as soon as possible.
I've two of this one but i need Windows XP the driver doesn't install into W10
And i've a DSI with SD card with driver working into W10
I too as well would like to know.
I have one of these and tried hooking it up, although it seems like Windows 10 didn't recognise the device properly.
I might have to run it through a Virtual Machine to flash it
Not a big deal if not though, I have other means of installing b9s on 3DS systems, I'm getting the SNES edition N3DSXL next month and am looking forward to transferring my system to it, hacks and all.
I don't own one of these but if you can flash ARDS firmware 1.71 via Code Manager to it, then it means it's supported. If you really don't want to brick it keep in mind that you can use a flashcart to unbrick an ARDS.
(EDIT: Grammar.)
Last edited by RattletraPM,
So, I was able to find someone with a hacked 2DS, we put the R4i gold.cc and we were able enter in the menu with the 7.0 version, but when we select the update already patched nothings happened, just a black screen with white text "firware update" it didn't show me any option to inject the hax... Please I'm really trying hard but nothings happen.
Yeah, that behaviour seemed extremely suspicious and reminiscent of when B9s or A9lh can't find something to boot off of. What threw me off was that I had everything named correctly except for ntrboot.firm, i had missed that line and went with boot.firm, as that what the guide said that normal ntrboothax was looking for. Renaming it properly allowed it to fire off without a hitch.
Yeah, I found that alternate .nds file too. Problem is that TWL loader doesn't seem to support it properly, and my only flashcart (R4 DS Upgrade Revolution for DS by R4i-sdhc), errors out upon loading either .nds file, so no go there until we can either force write the stock firmware back from PC, or have TWL loaders bootstrap properly support it.
Either way, I'm happy I have a properly ntr'd ARDS for the time being.
Last edited by Joelgp83,
hello everybody, I have an older r4igold.cc, not the ¨yellow with sprites..¨ this one: http://www.r4igold.cc/download.asp
is this card compatible? should I ask for it here ..
thanks in advance.
I have the other one too the one from this thread but I think is bricked.(no icon on the menu and not respond to the flash proceess)
is this card compatible? should I ask for it here ..
thanks in advance.
I have the other one too the one from this thread but I think is bricked.(no icon on the menu and not respond to the flash proceess)
There's gonna need to be qualifiers on that flashcart-can-unbrick (or revert to stock)-an-ARDS idea. The .nds files given so far to do so simply don't boot on R4 cards such as mine.
Instead of using the ROM file posted in the MEGA link, take the ARDS 1.71 firmware file, remove the first 8 bytes (41 52 32 4D CC CD 00 00) and rename it to .nds, then run it on your flashcart. This way you'll basically get something more similiar to a NAND image than a ROM (some stuff isn't where it should normally be, such as the Secure Value) but most flashcarts don't care and it'll boot anyways - plus, as it contains only what's needed for an ARDS to function properly and nothing else (no cheat codes, extra ROM/NAND pages or anything else really) so it should be compatible with more flashcarts.
I've got a R4DS (non SDHC, original) with WoodR4 as a kernel and it boots just fine. If you're having trouble, try to see if there's a wood kernel available for your card.
- No one is chatting at the moment.
