Hacking [Release] rxTools - Roxas75 3DS Toolkit [fw 2.0 - 9.2]

[Apache Thunder]

Yeah if you attempt to update 8.1 to 9.2 directly using game roms/CIAs, you'll get a brick. Create an emunand of 8.1, update it from emunand, then get a 9.2 firm0/firm1.bin files (add the "emu_" part to them so rxTools knows they are for emunand) and inject them into emunand. Then extract emunand with emunand tool and rename it to NAND.BIN. Put on your SD card and flash it to sysnand using Gateway menu.

It's actually not that complicated once you figure out how to do it.

Since you're on 8.x sysnand firmware, you don't have to worry about the slot 25 keyX file.

 

[Slushie3DS]

Yeah if you attempt to update 8.1 to 9.2 directly using game roms/CIAs, you'll get a brick. Create an emunand of 8.1, update it from emunand, then get a 9.2 firm0/firm1.bin files (add the "emu_" part to them so rxTools knows they are for emunand) and inject them into emunand. It's actually not that complicated once you figure out how to do it.

Since you're on 8.x sysnand firmware, you don't have to worry about the slot 25 key file.

Do you have to use the specifically picked through files or just the general files downloaded from the Nintendo CDN? I remembered you said your friend caught a brick trying to use all of the files that were downloaded. If you could PM me a tut, I'd owe you a solid.

 

[Apache Thunder]

Ahh yes, the CIA preparation part is the complicated part. Just use UpdateCDN (use 3DNUS to build the eShop CIA, as for some reason UpdateCDN built one that DevMan refused to install) to download all CIAs for 9.2.0-20U. You can just not install the eShop CIA if you don't want to bother with 3DNUS though. I don't think you'll be using it much anyways.

Then delete/move the 9.0.0-20-Stage2 folder. That contains all the n3DS stuff and installing those will result in bricked emunand when you go to install them. This is assuming you told UpdateCDN to keep things organized in folders. Other region firmwares have additional stage folders, so those could also contain n3DS firmware. But for USA region like what yours likely is, that one stage 2 folder is the only one that has n3DS stuff for a 9.2 update.

Then take all the cias and put them in one folder on your SD card. Remove TWL_FIRM and DS Cart White list CIAs if you want to maintain older DS flashcart compatiblity. Otherwise it's ready to be installed to emunand. Just make sure you are using DevMan 6.2 or BigBlueMenu. BigRedMenu and older versions of DevMan will NOT work!

You can also update emunand using a rom. (though one user on the forum bricked doing that, but not sure how. I've updated emunand a couple times using a rom and didn't brick sysnand. Maybe he accidentally ran the update while in sysnand?)

If in doubt about that, stick to CIAs then as I have not had issues installing those to emunand.

EDIT: Oh and when I had mentioned a friend catching a brick, it was when he attempted to use that emunand on sysnand. He had a NAND mod so it wasn't a problem. But note this was before I knew about the firm0/firm1 issue.

 

[Slushie3DS]

Ahh yes, the CIA preparation part is the complicated part. Just use UpdateCDN (use 3DNUS to build the eShop CIA, as for some reason UpdateCDN built one that DevMan refused to install) to download all CIAs for 9.2.0-20U. You can just not install the eShop CIA if you don't want to bother with 3DNUS though. I don't think you'll be using it much anyways.

Then delete/move the 9.0.0-20-Stage2 folder. That contains all the n3DS stuff and installing those will result in bricked emunand when you go to install them. This is assuming you told UpdateCDN to keep things organized in folders. Other region firmwares have additional stage folders, so those could also contain n3DS firmware. But for USA region like what yours likely is, that one stage 2 folder is the only one that has n3DS stuff for a 9.2 update.

Then take all the cias and put them in one folder on your SD card. Remove TWL_FIRM and DS Cart White list CIAs if you want to maintain older DS flashcart compatiblity. Otherwise it's ready to be installed to emunand. Just make sure you are using DevMan 6.2 or BigBlueMenu. BigRedMenu and older versions of DevMan will NOT work!

You can also update emunand using a rom. (though one user on the forum bricked doing that, but not sure how. I've updated emunand a couple times using a rom and didn't brick sysnand. Maybe he accidentally ran the update while in sysnand?)

If in doubt about that, stick to CIAs then as I have not had issues installing those to emunand.

So, how exactly would I launch DevMan or BBM from rxMode?

 

[Apache Thunder]

lol. You don't. You need a Gateway or MT-Card. rxMode won't boot DevMan/BBM because they aren't signed correctly. BigRedMenu won't install system titles correctly, so don't use that. (though that also won't boot in rxMode. )

You can however use Palantine CFW's emunand to do the update. But converting Palantine's emunand to a usuable NAND image for flashing to sysnand will be a pain in the ass. (not to mention you'd have to reinject it back as a normal emunand first so rxTools will see it and let you inject the firm0/firm1 files into it. You'll likely have to completely wipe the SD card as Palantine CFW changes the partition size for emunand and emunand tool will no longer recognize it)

You don't have very good options right now if you don't own a Gateway/MT-Card. Your best bet is to just wait for Karl3DS to get released. From what I hear they plan to allow installation of system titles.

 

[Slushie3DS]

lol. You don't. You need a Gateway or MT-Card. rxMode won't boot DevMan/BBM because they aren't signed correctly. BigRedMenu won't install system titles correctly, so don't use that. (though that also won't boot in rxMode. )

You can however use Palantine CFW's emunand to do the update. But converting Palantine's emunand to a usuable NAND image for flashing to sysnand will be a pain in the ass. (not to mention you'd have to reinject it back as a normal emunand first so rxTools will see it and let you inject the firm0/firm1 files into it. You'll likely have to completely wipe the SD card as Palantine CFW changes the partition size for emunand and emunand tool will no longer recognize it)

You don't have very good options right now if you don't own a Gateway/MT-Card. Your best bet is to just wait for Karl3DS to get released. From what I hear they plan to allow installation of system titles.

Aha, I knew today wasn't my lucky day! Thank you for clearing that up.

 

[Xelnok]

Yes to all, I did the same and it works now .

Just to make sure i don't corrupt my eshop Y save, can i load it on the latest emunand 9.5 and also load it on sysnand 9.2 (for browser exploit) without having any save data errors? I know nintendo can be finnicky sometimes with saves and i don't want to kill my save by trying it.

Anyone know if it would work?

Thanks

 

[DSoryu]

Just to make sure i don't corrupt my eshop Y save, can i load it on the latest emunand 9.5 and also load it on sysnand 9.2 (for browser exploit) without having any save data errors? I know nintendo can be finnicky sometimes with saves and i don't want to kill my save by trying it.

Anyone know if it would work?

Thanks

eShop saves aren't affected by system version or emuNAND, you should be fine.

 

[Xelnok]

eShop saves aren't affected by system version or emuNAND, you should be fine.

Just tried to open the save on 9.2 after having it work on 9.5 and it said the save wasn't compatibile with the version i was running. It might not be working because my pokemon game is update 1.2 on 9.2 and 1.3 on 9.5, i was hoping installing the update on emunand would allow it to work on sysnand, i guess until we get a way to copy over updates to sysnand i might not be able to use it.

Anyone know of any other solutions for an issue like this?

Thanks

 

[bbmax]

lol. You don't. You need a Gateway or MT-Card. rxMode won't boot DevMan/BBM because they aren't signed correctly. BigRedMenu won't install system titles correctly, so don't use that. (though that also won't boot in rxMode. )

You can however use Palantine CFW's emunand to do the update. But converting Palantine's emunand to a usuable NAND image for flashing to sysnand will be a pain in the ass. (not to mention you'd have to reinject it back as a normal emunand first so rxTools will see it and let you inject the firm0/firm1 files into it. You'll likely have to completely wipe the SD card as Palantine CFW changes the partition size for emunand and emunand tool will no longer recognize it)

You don't have very good options right now if you don't own a Gateway/MT-Card. Your best bet is to just wait for Karl3DS to get released. From what I hear they plan to allow installation of system titles.

Palantine form plain EMUNAND is difrent only with first 512bytes 0x0 to 0x1F0 so cutting this region and save in hexeditor give us plain EMUNAND

 

[Chaldron]

Palantine form plain EMUNAND is difrent only with first 512bytes 0x0 to 0x1F0 so cutting this region and save in hexeditor give us plain EMUNAND

So making this edit would allow rxTools to boot CFW? Unlikely because it''s so unstable, but if that's the only difference between a CFW and "regular" emuNAND I can't see why not.

 

[zero2exe]

Just tried to open the save on 9.2 after having it work on 9.5 and it said the save wasn't compatibile with the version i was running. It might not be working because my pokemon game is update 1.2 on 9.2 and 1.3 on 9.5, i was hoping installing the update on emunand would allow it to work on sysnand, i guess until we get a way to copy over updates to sysnand i might not be able to use it.

Anyone know of any other solutions for an issue like this?

Thanks

If your sysnand and emunand are linked then game updates should be applied to sysnand as well so you'd have 1.3 on both nands.

 

[Fishaman P]

If your sysnand and emunand are linked then game updates should be applied to sysnand as well so you'd have 1.3 on both nands.

Only if sysNAND already has a ticket for a previous update (which would be the case here). But a sysNAND that hasn't downloaded any patches won't see the emuNAND patches.

 

[zero2exe]

Only if sysNAND already has a ticket for a previous update (which would be the case here). But a sysNAND that hasn't downloaded any patches won't see the emuNAND patches.

Indeed I have just tested the second case with Steeldiver Sub Wars and it only applies the latest update while on Emunand, that's interesting considering the game was already in my ticket from months ago (which is why it also shows on sysnand without trouble) but it was from back when the game had no updates available.

 

[Xelnok]

If your sysnand and emunand are linked then game updates should be applied to sysnand as well so you'd have 1.3 on both nands.

It looks like it is showing up as version 1.3 but still states "The saved data is not compatible with this version, so it can't be used"

I think that is the message that pops up if you mess around with your digital save to avoid people from reverting to an older saved game, but its wierd it works on 9.5 but not on 9.2 even with a linked nand.

Not sure how to go about fixing it either.

Xel

 

[piratesephiroth]

It looks like it is showing up as version 1.3 but still states "The saved data is not compatible with this version, so it can't be used"

I think that is the message that pops up if you mess around with your digital save to avoid people from reverting to an older saved game, but its wierd it works on 9.5 but not on 9.2 even with a linked nand.

Not sure how to go about fixing it either.

Xel

Then the rollback prevention won't let you play the same game on both nands.
Saving it on one will make the save data invalid for the other one.

 

[WateredFire19]

I put slot0x25keyx.bin, firmware.bin, and rxtools.dat on the root of my sd card. I have 7.1.0-9U system nand and GW3D 7.1.0-9U EmuNAND. But when i scan the QR code it takes me to the rxtools.dat loading web page but it just crashes the browser! Can someone tell me what im doing wrong?

 

[SMVB64]

I wouldn't unlink it at least until the actual fix for Smash/MH4 is released. The only issue I've seen so far is with newly downloaded software is that they appear wrapped up again every time I start emunand, but the saves are fine so I don't really mind right now.

OK, that's good to hear! So nothing too funky will happen when they are linked together like that. Though, to unlink them would that require a sysnanad format? Would it be possible to format emunand instead?

But when i scan the QR code it takes me to the rxtools.dat loading web page but it just crashes the browser! Can someone tell me what im doing wrong?

Make sure that you cleared your cookies and cache before starting the exploit. I had that issue to where it would crash to the main menu.

 

[SMVB64]

Ah crap, sorry double post. Please delete

 

[Slushie3DS]

I put slot0x25keyx.bin, firmware.bin, and rxtools.dat on the root of my sd card. I have 7.1.0-9U system nand and GW3D 7.1.0-9U EmuNAND. But when i scan the QR code it takes me to the rxtools.dat loading web page but it just crashes the browser! Can someone tell me what im doing wrong?

>Turn of wifi.
>Scan QR.
>Allow it to open.
>Bookmark the page.
>Go into browser settings and clear your caches.
>Turn back in your wifi.
>Reload the page.

May help.