Hacking [Release] NTRBoot for R4igoldcc,ARDS(EZ),ARDSI

[Wantija]

Ok so I managed to get my ARDS fat working, the problem was the ntrboot.firm file. When setting it up in order for it to boot luma 3ds's .firm file needs to be ntrboot.firm, is there any way to have it so it will use boot.firm instead? Also my original slim ARDS works and turns out the last official update it supports is 1.55 and wont update to 1.71 or the flashed firmware file under the regular exe or the patched one. Is there any hope for the slim one to get support?

 

[RattletraPM]

Ok so I managed to get my ARDS fat working, the problem was the ntrboot.firm file. When setting it up in order for it to boot luma 3ds's .firm file needs to be ntrboot.firm, is there any way to have it so it will use boot.firm instead? Also my original slim ARDS works and turns out the last official update it supports is 1.55 and wont update to 1.71 or the flashed firmware file under the regular exe or the patched one. Is there any hope for the slim one to get support?

1)At the moment there's no way to boot from boot.firm, but this will change soon. I'm making a tool to modify, fix and extract ARDS firmware files (which is almost complete, by the way) that will also support the official Boot9Strap release, so you'll be able to boot from boot.firm instead of ntrboot.firm.
2)Some slim ARDSes require a different header in order to update their firmware via code manager and yours might be one of those. If you want to flash the modded firmware file, open it in your HEX editor and change the first four bytes from AR2M to FIRM (and if you want to use it on an unpatched code manager you'll need to fix the CRC too, otherwise use the patched code manager exe). I know it's a bit of a shameless plug at this point but again, if you're willing to wait, my tool will be able to do this automatically.

EDIT: A small tip, if your ARDS slim needs the header mod, DO NOT use it to flash the official 1.71 firmware to it, chances are that it won't get recognized by Code Manager anymore and you won't be able to flash anything to it without first restoring it with a flashcart.

 

[al3x_10m]

ntrboot.firm was just a personal choice of mine as to not interfere with the normal boot.firm used in the guide

--------------------- MERGED ---------------------------

1)At the moment there's no way to boot from boot.firm, but this will change soon. I'm making a tool to modify, fix and extract ARDS firmware files (which is almost complete, by the way) that will also support the official Boot9Strap release, so you'll be able to boot from boot.firm instead of ntrboot.firm.
2)Some slim ARDSes require a different header in order to update their firmware via code manager and yours might be one of those. If you want to flash the modded firmware file, open it in your HEX editor and change the first four bytes from AR2M to FIRM (and if you want to use it on an unpatched code manager you'll need to fix the CRC too, otherwise use the patched code manager exe). I know it's a bit of a shameless plug at this point but again, if you're willing to wait, my tool will be able to do this automatically.

EDIT: A small tip, if your ARDS slim needs the header mod, DO NOT use it to flash the official 1.71 firmware to it, chances are that it won't get recognized by Code Manager anymore and you won't be able to flash anything to it without first restoring it with a flashcart.

waiting for your tool

 

[RattletraPM]

ntrboot.firm was just a personal choice of mine as to not interfere with the normal boot.firm used in the guide

--------------------- MERGED ---------------------------



waiting for your tool

I can understand that, it was pretty hard to understand if NTRBoot worked correctly before Luma implemented a function to see what method was used to boot it. At the time I didn't know about that B9S fork and I've compiled my own version of B9S just to change the file name

Anyways, my tool is probably going to be ready tomorrow (I don't have too much time to work on it today, but the core functions are pretty much done.) I've already created a repo for it on my github (it's empty atm) but I'll post a link and make its own thread when it's ready!

 

[Deleted User]

Well, that's not entirely true. The question should be: "Can you update your AR's firmware via Code Manager or Code Manager DSi? And does it work on a 3DS?" If you can answer yes to the first question and no to the second, then there's a good chance it's supported, otherwise it's most probably NOT supported.

Anyways, for anyone wondering, here's a quick list of all the ARs that are confirmed working and not working for NTRBoot.

WORKING:
Action Replay DS (no card slot, aka "slim". Might require a firmware mod in order to work.)

Spoiler

Action Replay DS ("fat", aka the one with a card slot)

Spoiler

Action Replay DS EZ

Spoiler

Action Replay DS Media Edition (requires a different installation method than other ARs)

Spoiler

Action Replay DSi (the original one that WON'T boot on a stock 3DS and is updateable via Code Manager DSi)

Spoiler

NOT WORKING:

Action Replay DS/DSi Updates (there seems do be different variants for those, check your ARDS's label if it says "Updates". Also, those are able to boot on a stock 3DS.)
Anything that doesn't come with an USB port or is not updateable, such as Action Replay Ultimate Cheats for Pokémon.
Action Replay Powersaves

I don't own all of these, but I've been able to find out which ones do and don't work by looking at their firmwares (if available). If I'm wrong on anything, let me know and I'll fix this post.

It says on your list that ARDSi has worked... I tried over a couple hours and I haven't been able to do it.

 

[RattletraPM]

It says on your list that ARDSi has worked... I tried over a couple hours and I haven't been able to do it.

By checking out the firmware (I don't own an ARDSi so I can't actually test if it works) I saw that the ARDSi has an identical firmware structure to the other ARDSes, the only thing that change is the content of the firmware itself - so it should work. Howerer, there are a ton of different ARDSi models out there, so you might've got one that is simply not compatible. To double check that, see if you can update to the latest ARDSi firmware with Code Manager DSi.

 

[Deleted User]

By checking out the firmware (I don't own an ARDSi so I can't actually test if it works) I saw that the ARDSi has an identical firmware structure to the other ARDSes, the only thing that change is the content of the firmware itself - so it should work. Howerer, there are a ton of different ARDSi models out there, so you might've got one that is simply not compatible. To double check that, see if you can update to the latest ARDSi firmware with Code Manager DSi.

Code Manager DSi doesn't do firmware updates. ARDSi firmware updates are separate programs.

 

[RattletraPM]

Code Manager DSi doesn't do firmware updates. ARDSi firmware updates are separate programs.

Code Manager DSi does do firmware updates:
http://uk.codejunkies.com/support/article.aspx?article_id=433
http://uk.codejunkies.com/support/article.aspx?article_id=433
Whether you can update your own Action Replay DSi with it depends on which ARDSi model you have. NTRBoot will ONLY work with the original, MicroSD-capable, non 3DS compatible ARDSi.

 

[aarti]

Why isn't 3ds.guide updating when it's released for a long time now?

 

[Deleted User]

Code Manager DSi does do firmware updates:
http://uk.codejunkies.com/support/article.aspx?article_id=433
Whether you can update your own Action Replay DSi with it depends on which ARDSi model you have. NTRBoot will ONLY work with the original, MicroSD-capable, non 3DS compatible ARDSi.

Oh, shit. Never mind, then. There's not a dedicated button for it like in the ARDS Code Manager. I assumed the separate updaters were the only way.

 

[al3x_10m]

ok...there's fpga code updates and nand image updates...i think @YukiSnowmew meant the fpga fw update and @RattletraPM the image fw update

--------------------- MERGED ---------------------------

btw...my ardsi was originally without the microsd slot...i added one just because the pads and the traces for the power regulator and the passives were there...and worked

 

[RattletraPM]

ok...there's fpga code updates and nand image updates...i think @YukiSnowmew meant the fpga fw update and @RattletraPM the image fw update

--------------------- MERGED ---------------------------

btw...my ardsi was originally without the microsd slot...i added one just because the pads and the traces for the power regulator and the passives were there...and worked

I actually think he meant the 3DS compatible ARDSi updates, those are shipped in a completely different format and don't use Code Manager at all... Anyways, the thing's still simple - you need to be able to flash that firmware if you want NTRBoot. If not, your ARDSi is not going to be compatible.

Anyways, yeah - I noticed those pads in a picture posted in this thread by another user... free ARDSi upgrade?

Why isn't 3ds.guide updating when it's released for a long time now?

Maybe because, as it is right now, it's a bit more involved than the other NTRBoot installation methods. Plailect might be waiting until someone ports this to ntrboot_flasher so no USB cable will be needed.

 

[al3x_10m]

I actually think he meant the 3DS compatible ARDSi updates, those are shipped in a completely different format and don't use Code Manager at all...

that's the fpga update for ar3ds...it doesn't restore the image

 

[Deleted User]

Code Manager DSi does do firmware updates:
http://uk.codejunkies.com/support/article.aspx?article_id=433
Whether you can update your own Action Replay DSi with it depends on which ARDSi model you have. NTRBoot will ONLY work with the original, MicroSD-capable, non 3DS compatible ARDSi.

So I just attempted to apply this to my 3DS compatible ARDSi and it worked. That's not a good method for determining whether an ARDSi is compatible. After applying the patch, my ARDSi would run, but would black screen.

After that, I used Code Manager DSi's "reset hardware". My ARDSi now functions as it did before that patch.

--------------------- MERGED ---------------------------

I actually think he meant the 3DS compatible ARDSi updates, those are shipped in a completely different format and don't use Code Manager at all...

Yes, that is what I was talking about. There's also updates like that for the old ARDSi.

 

[RattletraPM]

that's the fpga update for ar3ds...it doesn't restore the image

Oh, alright then. I don't own an ARDSi so I didn't know, but it makes sense.

Yes, that is what I was talking about. There's also updates like that for the old ARDSi.

al3x_10m pointed out that those are fpga updates. They have nothing to do with NTRBoot, so you can ignore them.

 

[zaide_chris]

@RattletraPM the tool that your making, will it be possible to flash any firm directly to the ARDS? or will it only support the official Boot9Strap release? I'm interested in flashing a custom GodMode9.firm complied with an autorun.gm9 file.

 

[RattletraPM]

@RattletraPM the tool that your making, will it be possible to flash any firm directly to the ARDS? or will it only support the official Boot9Strap release? I'm interested in flashing a custom GodMode9.firm complied with an autorun.gm9 file.

The tool will still require Code Manager and a USB cable but will support both the official B9S release and any other NTRBoot compatible FIRM. It will also have an easy mode (just specify which AR model you have, then the tool will download the latest available B9S version directly from the Github repo and pack it up for you in a firmware file) and an advanced mode (specify your own FIRM, AR model and console type - aka whether you want to make NTRBoot work on a retail console or a devkit - and generate a firmware based on those settings).

One of the reasons why I'm making this tool in the first place is because I want to install GodMode9 directly on my ARDS ME, so you bet it'll be supported!

 

[patrizl001]

could there be a way to flash this using something like a DS and a flash card if you don't have the cable? My flash card can't run ntrboot, but from what I see about how it works it looks like you could take out the flash card and replace it with the ARDS. Might be wrong about that though.

 

[Deleted User]

Hmm... I have the one pictured on the OP... maybe @RattletraPM 's tool will help.

 

[zaide_chris]

Some extra info that may help people at least with the black label Action Replay DS.
One way you can restore the firmware is by using two different DS consoles during the process.

1. Put the card in one DS and turn it on
2. Leaving it ON take out the card
3. Put the card in the second DS then flash it with the ards_ntrboot.bin @RattletraPM shared after modifying AR2M to FIRM in the header.
4. Second DS will be rebooted and useless
5. Use the card in the 3DS for ntrboot
6. Put the card back in the first DS that has been left on the whole time
7. Flash ARDS.firmware.1.55.bin back to it

As codejunkies no longer has it on their page here is ARDS.firmware.1.55.bin: mega.nz/#!EGxRxJiR!a4Wfsg9TJVJNZROVluY3-YWCK4MwN4P1i_dPqx-1gEM