So is Devmenu literally required to downgrade MSET, or is it used just for the purpose of making this guide "newb-friendly?" Doesn't ReiNand permit the installation of unsigned CIAs as well? Why is firmlaunch a bad thing? If our objective is to downgrade MSET on the sysNAND, why do we bother injecting it's backup into emuNAND in step 3 in the first place?
Hacking [Tutorial] Setting up Reinand CFW from scratch
- Thread starter usernametaken
- Start date
- Views 94,041
- Replies 537
- Likes 15
So is Devmenu literally required to downgrade MSET, or is it used just for the purpose of making this guide "newb-friendly?" Doesn't ReiNand permit the installation of unsigned CIAs as well? Why is firmlaunch a bad thing? If our objective is to downgrade MSET on the sysNAND, why do we bother injecting it's backup into emuNAND in step 3 in the first place?
Do I need Cubic ninja for this? I have N3DS + Gateway + OOT.
Please answer
No, you don't. If you already have the gateway save file on your OOT, then just replace the With Gateway cubic ninja option with the OOT boot method to get into gateway menu.
If you don't have the save file on your OOT already, you'll need someone with access to gateway menu - save dongle - or cubic ninja.
If you originally setup gateway with cubic ninja, you'll either need to rescan the gateway qr code or install the gateway ROP replacing Reinands.
To get back to your gateway emunand, you need to reinstall the gateway ROP. Using either the unofficial FBI or a your DSTwo.
My understanding is you'd need to manually uninstall a system files from the Sysnand with FBI before being able to write the 4.5 Mset in its place. So if this were done incorrectly, the person trying to install Mset would have a bricked system.
Yes - Others have reported not being able to install certain files while firmlaunch is active.
In step 3 you're making a backup prior to installing the Mset. Rather than shutting the system down and injecting the Devmenu backup of Sysnand into Emunand, then starting back up > Launching Cubic Ninja > Homebrew > Pasta > Cubic Ninja > Homebrew > FBI to install the Mset exploit, it's much quicker to just make a backup right after installing Devmenu, then installing the Mset exploit which won't be in the backup you're going to inject into emunand.
basically this is a guide that if followed exactly will result in people having reinand setup with the MSET entry point......can you go about it all differently? sure thing, there's probably at least 6 different deviations you can make to get to the same position, but some are more complicated or have more potential pitfalls, when choosing what route to take for a guide its usually best to choose the option with the least potential issues for people to fall into, as it stands this guide have very little room for error which imo is as good as it gets for a guide
if you want to use a different route and you know what your doing then this guide isnt really for you anyway, this is for people who simply want a A-> B guide and have zero/minimal experience with how to hack 3DS consoles
if you want to use a different route and you know what your doing then this guide isnt really for you anyway, this is for people who simply want a A-> B guide and have zero/minimal experience with how to hack 3DS consoles
I don't get this part: "emuNAND tool > Inject NAND to emuNAND > Select the NAND.BIN you placed in folder "Sysnand MSet installed"
Where is this Sysnand Mset installed folder? It's not in the included zip. What do i do with the NAND.BIN after i patched it, the guide doesn't tell me.
Where is this Sysnand Mset installed folder? It's not in the included zip. What do i do with the NAND.BIN after i patched it, the guide doesn't tell me.
When i load up the DS profile i see the Reinand splash screen, but after i click start it just turns black. Using the no ds flashcard method.
Step 2:
Hold [L] start Pasta cfw > select Backup SysNAND
Then later on once you shut down your system
Copy the NAND.BIN from the root of your mSD to "Sysnand MSet installed" folder on your computer. *You create your own folder, you don't have to, just place the NAND.BIN from that step somewhere you can get to it"
With Emunand tool, you'll flash that NAND.BIN over your Emunand partition.
Re-drop all the files from Root of mSD - region to your internal SD card. Then try booting again.
If you're getting the start screen for Reinand, you probably just missed a necessary file while copying stuff.
My understanding is you'd need to manually uninstall a system files from the Sysnand with FBI before being able to write the 4.5 Mset in its place. So if this were done incorrectly, the person trying to install Mset would have a bricked system.
Yes - Others have reported not being able to install certain files while firmlaunch is active.
In step 3 you're making a backup prior to installing the Mset. Rather than shutting the system down and injecting the Devmenu backup of Sysnand into Emunand, then starting back up > Launching Cubic Ninja > Homebrew > Pasta > Cubic Ninja > Homebrew > FBI to install the Mset exploit, it's much quicker to just make a backup right after installing Devmenu, then installing the Mset exploit which won't be in the backup you're going to inject into emunand.
Thanks for the help! One last question: will my Acekard 2i work with the MSET exploit? It seems like bluecardfix.cia didn't work for the person I quoted below below, which leads me to believe that the only way to make it work is to downgrade TWL_FIRM. Is that even possible on the New 3DS?
Yes the emunand tool detects the drive with an emunand partition. I assume station is drive letter. ;D
Just wanted to make sure I wasn't missing something.
My Reinand is working after i create an emunand. But everytime i patch the nand.bin it seems to break reinand. I get the splashscreen but after that nothing, just a black screen. I have no idea what i'm doing wrong..
(did everything in the guide with reinand still working when i boot it with cubic ninja up to the backup nand.bin part.)
1. i create the nand.bin with pastaCFW.
2. i put the sd card in my computer. copy and paste the nand.bin on my pc.
3. use the nand tool and point it to the nand.bin on my computer (with the sd card still in my card reader)
4. put sd back in n3ds.
5. boot fbi through pastacfw, set it to sysnand, press select and install "Reinand N3DS 4.x MSET"
6. ds profile exploit is working, goes to reinand splash screen, when i press start nothing. When i load reinand with cubic ninja instead of ds exploit same error.
Try redropping these files onto your internal SD. Second image is the contents of the 3ds folder from the first.
Well everything is the same as in your screenshots. I'm going to redo the whole tutorial again for the third time. I'm formatting my microsd now and going to restore the n3ds (9.0) back to factory settings.
I really think something goes wrong when i patch nand.bin with emunandtool. But i have no idea what.. What can i do wrong lol, point it to nand.bin and press inject nand to emunand and wait.. xD Should i install "mset_(region).cia " to sysnand or sd?
Just to clarify things. I'm using the "Installing ReiROP to Sysnand for Profile exploit" method, without a gateway setup and without a nds flashcard, just cubic ninja and a 9.0 n3ds. This should work to boot into reinand right?
I'm a fulltime developer and i can't even do this right, i feel so stupid lol. XD
When your format the N3DS the installed mset_region.cia will persist, the only thing that'll be wiped is the installed ROP.
Mset is installed to the System.
Yes, you're getting the start screen for Reinand, so you're installing the correct ROP, it's either the Reinand files on the SD card or the NAND.BIN injection.
You can try injecting the original NAND.BIN backup to your emunand & see if it'll boot. (Though if it does, it won't have a title manager installed (Devmenu)
Since Mset is now on your Sysnand, if you create a new NAND.bin and inject it, your emunand will have downgraded settings as well. Once you're all up and running, updating the firmware to 9.5.0-23 will fix this though.
Being removed from the Sysnand yeah. From the Emunand, it shouldn't.
You could try reinstalling Devmenu to the Sysnand then copying the dbs folder from your mSDs Nintendo 3DS > Sysnand code > dbs to your Emunands code folder. I don't know if this would solve your problem though. Just a guess.
Well different approach with succes (for anyone facing with the same emunandtool problem):
1. Format nand in gateway launcher.
2. Boot PastaCFW, boot Homebrew Channel, boot FBI. install fbi.cia (SD) and mset (nand).
3. Turn off n3ds, remove sd, turn on and format n3ds.
4. Setup your n3ds, turn it off, insert sd, turn it on again. (You have unlinked sysnand from emunand now)
5. Boot PastaCFW, boot Homebrew Channel, boot FBI. Install Reinand N3DS 4.x MSET. Turn it off.
6. You can enter Reinand with the DS profile exploit now.
Thanks usernametaken for the guide! I've only had this exploitable n3ds for a week so i didn't know much.
1. Format nand in gateway launcher.
2. Boot PastaCFW, boot Homebrew Channel, boot FBI. install fbi.cia (SD) and mset (nand).
3. Turn off n3ds, remove sd, turn on and format n3ds.
4. Setup your n3ds, turn it off, insert sd, turn it on again. (You have unlinked sysnand from emunand now)
5. Boot PastaCFW, boot Homebrew Channel, boot FBI. Install Reinand N3DS 4.x MSET. Turn it off.
6. You can enter Reinand with the DS profile exploit now.
Thanks usernametaken for the guide! I've only had this exploitable n3ds for a week so i didn't know much.
Similar threads
-
-
-
-
-
-
@
BakerMan:
fellas, would you rather have a scouter from dragon ball irl or a pip boy from fall out irl? -
-
-
-
-
-
-
-
-
-
-
-
-
S @ StealthD0g99:I am trying to hack Fire Emblem Warriors on my 2DS XL, I have been trying to get it to work, but I need some extra help figuring it out. I have HEX codes, and a possibly outdated plugin, but I dont know how to implement them
-
-
-
-
-
-
