banner



How To Install Cfw 3ds

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Tutorial [Tutorial] Installing Luma3DS CFW (For 2DS,o3DS,N3DS - Total MenuHax+RedNAND+Autoboot Setup)

  • Thread starter Temptress Scarlet
  • Start date
  • Views 213,984
  • Replies 304
  • Likes 17
  • #one
Delight Use: https://3ds.guide/

This guide is probably pretty broken by now. And since xi.three, became the new 9.two. And with the release of B9S. Getting CFW is pretty painless and noob-proof. Just read the guide linked above, and take it tiresome.

~Opening Words & Thoughts~
This guide was originally created for people who are likewise afraid and besides scared to go the total A9LH route. (Either they read user error brick reports, or outdated bricks when A9LH was more in it'southward infancy)

Simply present, the A9LH procedure has been made shorter and safer than earlier. Then go bank check it out: https://3ds.guide/

Just if you lot're all the same reading and going on, and then this guide has been adjusted from Plailect's Old and Updated A9LH Guide, equally such it'll probably read pretty shut to it (since some stuff was copy-pasted, duh~), but has been adapted to fully stop at a functional autoboot MenuHax+RedNAND//EmuNAND setup.

Since this guide is heavily adjusted from Plailect's A9LH Guide, I want to take this time to thank Plailect for the piece of work he has put into making that wonderful guide. <3

I likewise desire to thank all the wonderful devs who have made all this possible. Y'all guys and gals rock~ <3

I nevertheless recommend people to use Plailect's A9LH Guide, however, for the people still besides scared and afraid, I have taken time to brand this for you.

I'd similar replies to this tutorial to be solely on people following this tutorial, otherwise, I can't help you well. If y'all have a question or problem and it's not related to following this tutorial, it'due south best to ask in the 3DS Noob Paradise Thread.
I'll assume any problems posted on this thread are in regards to following this tutorial.

Firmware Requirements:
USA // EUR // JPN: Firmware nine.0-9.2.
Hardware model: Shouldn't matter. N3DS//o3DS//2DS.

If you are non on 9.0-9.two, but on 9.3 to ten.seven, then use Part 1 and Office 2 of Plailect's A9LH guide to downgrade to 9.2.
You'll need to Hardmod dowgrade or a DSiWare downgrade on xi.0+

If yous are on anything below 9.0. Then use the ix.2.0 Update section of Plailect's A9LH Guide.
Link: https://github.com/Plailect/Guide_RedNAND/wiki/9.2.0-Update

At present, I'll say this here, the biggest adventure yous accept is the downgrade, so you should consider using the full A9LH guide, however, if the A9LH procedure still scares you, then go on on.

Any of the following requirements:

  • Working Web Browser on your 3DS
  • A cartridge based *hax entry point - Such as Ninjhax or Freakyhax

~♥ The Table of Contents ♥~
~Preparing our SD Menu~
~Making our first NAND Backup & Setting Up RedNAND~
~Unlinking our NANDs~
~Setting up MenuHax via BrowserHax~
~Properly Configuring Luma3DS & Updating RedNAND~
~Injecting FBI into RedNAND~
~Setting upward CtrBootManager + Useful Entries + Removing the flashing colors + Finalizing stuff~
~Making our RedNAND & SysNAND Backups~
~[Optional] Injecting FBI into SysNAND (For GBA//DSiWare Games) + Installing GBA & DSiWare Games~
~[Optional] Setup lesshax for better bootrates?~
~[Optional] Remove the blank image display at menuhax~
~[Optional] Custom Theme on SysNAND~
~[Optional] How To Dump your 3DS games & 3DS to CIA (Plus Extracting Individual Headers)~
~[Optional] Removing files nosotros don't need from our SD Card~


~Preparing our SD Bill of fare~
Files we'll need:
Homebrew Starter Pack by smealum: http://smealum.github.io/ninjhax2/starter.zip
EmuNAND9: https://github.com/d0k3/EmuNAND9/releases
Luma3DS: https://github.com/AuroraWright/Luma3DS/releases
TinyFormat: https://github.com/javimadgit/TinyFormat/releases
Decrypt9WIP: https://github.com/d0k3/Decrypt9WIP/releases/
aeskeydb.bin institute here: https://plailect.github.io/Guide/updating-a9lh)
fbi-2.four.2-injectable.zip plant here: https://plailect.github.io/Guide/installing-arm9loaderhax

1. Re-create the contents of the starter.nil onto the root of your SD Bill of fare.
2. Re-create and merge the 3DS binder from the EmuNAND9 cypher to the root of your SD Bill of fare.
3. Copy and merge the 3DS folder from the TinyFormat null to the root of your SD Card.
iv. Copy the Decrypt9WIP folder from the Decrypt9WIP cypher to the /3ds/ folder on your SD Card.
5. Create a folder named files9 on the root of your SD Carte du jour if it does not already exist.
vi. Copy aeskeydb.bin to the /files9/ folder on your SD carte.
7. Re-create the contents of fbi-2.4.2-injectable.zip to the /files9/ folder on your SD carte du jour
8. Re-create the arm9loaderhax.bin file and copy the contents inside of the hax folder from the Luma3DS null to the root of your SD menu.


~Making our first sysNAND Backup & Setting Up RedNAND~
We volition be using browserhax to make our commencement backup as well as setting up our EmuNAND//RedNAND. If you have a cartridge based *hax exploit, and so skip the first two steps.

1. Open up up the Browser.
2. Navigate to http://yls8.mtheall.com/3dsbrowserhax_auto.php or scan the QR code on your 3DS (if you get a slider, zoom all the way in on it, then tap the very right edge of it; this can take quite a few tries)

AFT9Hmn.png

3. You should at present be in the homebrew bill of fare.
4. Open EmuNAND9 (This can sometimes have a few tries)
five. Go to "EmuNAND Manager Options", then select "Fill-in SysNAND to file" - Using the arrow keys name information technology SysNAND.bin.
vi. In one case washed, press B to render to the menu.
7. Press Select to safely eject your SD Menu.
8. Put your SD Card into your calculator. Then fill-in sysNAND.bin and sysNAND.bin.sha to a safe location on your calculator; make backups in multiple locations (online storage places); this backup will salvage you lot from a brick if anything goes wrong in the futurity (Your backup should match ane of the sizes on this page; https://plailect.github.io/Guide/nand-size
if it does not, you should delete information technology and make a new i!)
9. One time yous've made sure yous've backed upwards sysNAND.bin and sysNAND.bin.sha, delete them from your SD Bill of fare.
10. Backup every file on your SD card to a folder on your computer, all files volition be deleted in the next step.
11. Reinsert your SD card into your 3DS.
12. Press B on EmuNAND9 to render to the menu. Printing B until yous are back in the main menu.
13. Select the "Complete RedNAND setup" choice. (If you plan on using a GW: And then do "Complete EmuNAND Setup")
14. Enter the push confirmation and await for it to finish.
15. Printing B to return to the menu, so press Select to safely eject your SD Card.
16. Put your SD card back into your computer, and copy all the files you backed up previously, back into your SD Menu.
17. Reinsert your SD bill of fare into your 3DS, and so press Kickoff to reboot.


~Unlinking our NANDs~
We want to unlink our NANDs, so we can later setup autoboot menuhax, this way nosotros don't have to constantly apply browserhax or a cartridge based *hax entry, simply to launch our RedNAND.
Notwithstanding, unlinking volition format SysNAND, thankfully, setting upwardly RedNAND has allowed us to create a re-create of our SysNAND onto RedNAND. So everything is now on our RedNAND.
Similar before, we will be using browserhax to perform the format via TinyFormat. If y'all have a cartridge based *hax exploit, then skip the starting time two steps.

ane. Open up the Browser.
two. Navigate to http://yls8.mtheall.com/3dsbrowserhax_auto.php or scan the QR code on your 3DS (if you get a slider, zoom all the manner in on it, then tap the very right edge of it; this can take quite a few tries)

AFT9Hmn.png

3. You lot should now be in the homebrew menu.
4. Open TinyFormat.
5. Press Y to format your SysNAND (Don't worry, everything is however saved on our RedNAND)
6. Get through initial setup without linking your Nintendo Network ID, you want it to remain linked only to RedNAND to prevent issues.


~Setting up MenuHax via BrowserHax~
1. Allow's open up the theme menu, alter your theme to anything, then switch it dorsum to the default plain normal theme. Practice this twice if y'all're paranoid or something.
2. Open up upwardly the Browser.
3. Navigate to http://yls8.mtheall.com/3dsbrowserhax_auto.php or browse the QR code on your 3DS (if you get a slider, zoom all the way in on it, then tap the very right edge of it; this tin can take quite a few tries)

AFT9Hmn.png

4. You should now be in the homebrew carte.
v. Open up menuhax_manager
six. Press the A button on Install.
7. Press the A push to go dorsum to to the main menu.
8. Select "Configure menuhax."
9. Press A to continue.
10. From here, yous'll have to determine how you want menuhax to activate. I recommend Type 2 autoboot. Where menuhax will basically trigger so long as it doesn't match the button value y'all designate.
While Type one, menuhax will only trigger when the button value you lot designate is pressed.
For this guide, we volition be using Type ii, on the Left Trigger (modify this to whatever you prefer, but there is a reason for this which I'll explain now).
Explanation for Left Trigger: For people who want to play GBA//DSiWare games, you'll want to exist able to boot into a patched SysNAND, Luma3DS can handle this job past belongings Fifty when launching information technology, but since menuhax will be on our SysNAND, we'll just end up boot-looping, and so with L as the trigger to de-activate menuhax loading, we can as well launch a patched SysNAND via Luma3DS while holding L and while too being able to disable menuhax from causing us to loop on us.
The patched sysNAND is only actually useful for people who want to play GBA//DSiWare games. The part titled "~[Optional] Injecting FBI into SysNAND (For GBA//DSiWare Games)~" covers all the steps in regards to that and goes a scrap more into detail on this.
11. Select "Blazon ii"
12. Concur down on the Left Trigger button, then tap the touch screen.
thirteen. Go back to the principal menuhax_manager menu, and so press B, followed by Start to go out back into the Homebrew Launcher.
14. Press Outset, followed by A to reboot.
15. Your console will at present reboot back into the Homebrew Launcher. This is because menuhax is fix to autoboot unless the Left Trigger button is held at boot time.


~Properly Configuring Luma3DS & Updating RedNAND~
1. Boot into the Homebrew Launcher. (If you have followed this guide, you should be autobooting into the Homebrew Launcher via menuhax)
2. Open Luma3DS (this can sometimes black screen, just endeavor again)
3. Activate "Testify NAND or user string in Organization Settings"
four. Printing Start to salve and boot into RedNAND.
5. If you boot into the home card, you take successfully launched RedNAND.
6. Open Organization Settings.
7. Make sure your DNS settings is set to Auto-Obtain. (Cyberspace Settings -> Connection Settings -> Connection 1/two/three -> Alter Settings -> DNS -> Auto-Obtain DNS set to Yes)
8. If you practice non see "Emu" in front of the version number, and so you are not on RedNAND. Practise NOT UPDATE, Observe OUT WHAT WENT Wrong.
Delight Notation: Practise Non Exit SYSTEM SETTINGS. Y'all will be kicked to SysNAND, if you have setup menuhax every bit autoboot as recommended, it should trigger menuhax and kick you back into the Homebrew Launcher. But delight just avoid exiting Arrangement Settings.
ten. Update your RedNAND to the latest version using system settings. (Other Settings -> System Update)
11. Once done, reboot back into RedNAND via HBL -> Luma3DS.
12. Open up Arrangement Settings and make sure we are on the latest system version.


~Injecting FBI into RedNAND~
So far, we have autoboot menuhax setup, equally well equally our Luma3DS configured correctly, and our RedNAND updated to the latest system version. But we don't take CIA Manager. And then for this office, we'll be properly injecting FBI into our RedNAND for utilize as our initial .CIA manager.

i. Boot into the Homebrew Launcher. (If you have followed this guide, yous should exist auto-booting into the Homebrew Launcher via menuhax)
2. Open Decrypt9 (This can sometimes have a few tries)
three. Go to "EmuNAND Options", then "Miscellaneous...", then select the "Health & Safety Dump" pick to dump Wellness & Safe to hs_emu.app (you can apply Up and Down / Left and Right to modify the name)
four. Once done, Press B to render to the menu, then select "Wellness & Condom Inject"
7. Select the FBI injectable .app for your region
8. Press A to confirm and inject.
thirteen. Shutdown as we'll need to prepare our SD card a fleck more again.


~Setting up CtrBootManager + Useful Entries + Removing the flashing colors + Finalizing stuff~
The way nosotros've setup our 3DS, we autoboot into the Homebrew Launcher via menuhax, but to get into our RedNAND, we must launch Luma3DS from the Homebrew Launcher. This isn't very platonic for some. And so in this function, we'll be using CtrBootManager to autoboot straight into our CFW+RedNAND.

Overview: In this function, nosotros'll besides be removing the annoying flashing colored screens, every bit well as optimizing our CtrBootManager with some entries nosotros'll want to use. Decrypt9WIP for our NAND backups//restores, dumping our 3DS games to .3ds, and for xorpads for use in converting .3ds to .cia, and EmuNAND9 for RedNAND management.

Files we'll demand:
-CtrBootManager: https://github.com/OperationNT414C/CtrBootManager/releases
-Decrypt9WIP: https://github.com/d0k3/Decrypt9WIP/releases/
-EmuNAND9: https://github.com/d0k3/EmuNAND9/releases
-StarUpdater-UN: https://github.com/gnmmarechal/StarUpdater-UN/releases
-hblauncher_loader: https://github.com/yellows8/hblauncher_loader/releases
-ninjhax2.7 with no debug colors or text past ihaveamac: https://ihaveamac.github.io/ninjhax2.ten/

Programs I recommend using for this part:
Notepad++: https://notepad-plus-plus.org/download/
HxD: https://mh-nexus.de/en/downloads.php?production=HxD

i. Copy the CtrBootManager.3dsx and the boot.cfg files from inside the CtrBootManager Release folder of the Release zip onto the root of your SD Carte.
two. Re-create the Decrypt9WIP binder from the Decrypt9WIP zip to the /3ds/ folder on your SD card. (Should have already been washed previously, but just in case)
iii. Copy and merge the 3DS folder from the EmuNAND9 zip to the root of your SD menu. (Should accept already been washed previously, but just in instance)
4. Copy hblauncher_loader.cia from the hblauncher_loader zip to the root of your SD card.
five. Copy the StarUpdater.cia from the higher up link to the root of your SD card.
half-dozen. Rename CtrBootManager.3dsx to auto.3dsx
7. Download the appropriate no debug colors or text ropbin (menuhax) file from the link here: https://ihaveamac.github.io/ninjhax2.ten/ it'll stop upwards existence the same proper name as the ropbin payload already on your SD Card, under the ropbin binder inside the menuhax folder.
In this example for Old3DS running 9.two.0-xx U, it'll be: "ropbinpayload_menuhax_USA12288_old3ds.bin"
8. In one case, yous've downloaded the correct ropbin (menuhax) file, re-create it to the robpin binder, inside the menuhax folder, replacing the one already on there.
9. Open HxD and navigate to and open up the file that which starts with "ropbinpayload" (root:\menuhax\ropbin\)
10. Press Ctrl+R or at the top, press "Search" and so "Replace"
11. Ensure that "Datatype" is gear up to "Text-string"
12. In the "Search for:" text box, blazon in "boot.3dsx" without the quoation marks, of course.
13. In the "Replace with:" text bot, type in "motorcar.3dsx" without the quoation marks, of course.
14. Check "Prompt on supersede" - This style we are asked if we are certain we want to supervene upon.
15. Click the "Replace all" button.
16. Ostend you desire to replace the occurrence by pressing "Yes" - Yous should be asked twice.
17. Save the file and go out HxD.
18. Open boot.cfg on the root of your SD Carte du jour with Notepad++
xix. Replace the contents of the file with the following:

                                [general] autobootfix=8; timeout=3; recovery=3; default=0;  [theme] bgTop1=000000; bgTop2=000000; bgBottom=000000; highlight=FF00004F; borders=C9FFFCBF; font1=C9FFFCBF; font2=C9FFFC; bgImgTop=/ctrbootmgr_top.bin; bgImgBot=/ctrbootmgr_bot.bin;  [animation] highlight=12:0:FF0000AF; menuFadeIn=20:10;  [entry] championship=Luma3DS; path=/3ds/Luma3DS/Luma3DS.3dsx; showtime=0; key=-1;  [entry] title=Decrypt9WIP; path=/3ds/Decrypt9WIP/Decrypt9WIP.3dsx; first=0; central=-1;  [entry] title=EmuNAND9; path=/3ds/EmuNAND9/EmuNAND9.3dsx; outset=0; primal=-ane;                              

xx. If you desire a longer time at the carte du jour, change timeout=3; to a higher number than 3 if you desire a flake more time, like x. Set to 0 for instantatnious kicking.
21. (Optional) If y'all set timeout=0; - Then I suggest irresolute recovery=three; to another key that'll interrupt automated boot. with the value at 3, information technology is the kickoff button. I practise not recommend a key that matches our menuhax type2 config, if you followed my recommendations, that would be the Left Trigger.
Wiki on the other keys: https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setup
22. (Optional) Customize CtrBootManager to even so you want using the wiki for an explanation of what every option does: https://github.com/OperationNT414C/CtrBootManager/wiki/CtrBootManager-setup
23. Save the file and exit Notepad++
24. You are nigh done, re-insert your SD Bill of fare into your 3DS, and you should now be autobooting correct into RedNAND with Luma3DS as your CFW. You'll take 3 2d window to boot other entries (If yous opted for instantaenous boot, and then yous'll have to hold the corresponding recovery key to see the CtrBootManager card).
25. Update your RedNAND to the latest version using System Settings -> Other Settings -> System Update (if you lot accept not already done then. ALWAYS brand sure information technology says Emu in front of your firmware version.)
26. Open Health and Safety (which is now FBI)
27. Select "SD"
28. Navigate to hblauncher_loader.cia and printing A to install.
29. Navigate to StarUpdater.cia and press A to install.
30. Exit with the home push button.
31. Launch the Homebrew Launcher from the home carte du jour icon at to the lowest degree once to ensure the payload for the Homebrew Launcher Loader for our RedNAND is downloaded and fully functional.
32. Reboot~! You are now washed~! (I highly recommend you make NAND backups of your setup, so please consider doing the adjacent section.)


~[Recommended]Making our RedNAND & SysNAND Backups~
Now that we're done, nosotros should make NAND backups of our setup, for recovery purposes.

1. If you lot take followed this guide completely to this point, then yous should have a short 3 second window at boot time, to load Decrypt9WIP. Do that at present.
2. Open up Decrypt9 (This can sometimes take a few tries)
three. Go to "SysNAND Options", then "SysNAND Fill-in/Restore", so "NAND Backup" - Using the pointer keys name information technology SysNAND.bin.
4. Look for it to finish, one time done, press B until you are back at the main menu.
5. Go to "EmuNAND Options", and so "EmuNAND Backup/Restore", then "NAND Backup" - Using the arrow keys proper noun it emuNAND.bin.
half dozen. Expect for information technology to finish, once done, printing B until you are back at the primary card.
7. Press Select to safely eject your SD Menu, and put your SD Card into your computer.
8. Rename the files inside the files9 folder on your SD Carte du jour equally follow:
sysNAND.bin to sysNAND_original.bin
sysNAND.bin.sha to sysNAND_original.bin.sha
emuNAND.bin to emuNAND_original.bin
emuNAND.bin.sha to emuNAND_original.bin.sha
9. Re-create over sysNAND_original.bin, emuNAND_original.bin, sysNAND_original.bin.sha, and emuNAND_original.bin.sha to a rubber location on your estimator; brand backups in multiple locations (online storage places);(Your backups should match i of the sizes on this page; https://plailect.github.io/Guide/nand-size
if it does not, you should delete them and make new ones!)
10. One time you've made sure yous've backed up sysNAND_original.bin, emuNAND_original.bin, sysNAND_original.bin.sha, and emuNAND_original.bin.sha, delete them from your SD Menu.


~[Optional] Injecting FBI into SysNAND (For GBA//DSiWare Games)~
We'll need FBI injected into SysNAND as well, and then we can install GBA and DSiWare .cia files, and so we tin can play them properly on RedNAND.

i. If you lot have followed this guide completely to this betoken, then you should take a short 3 second window at boot fourth dimension, to load Decrypt9WIP. Do that now.
2. Open Decrypt9 (This tin can sometimes take a few tries)
iii. Go to "SysNAND Options", then "Miscellaneous...", so select the "Health & Prophylactic Dump" option to dump Wellness & Prophylactic to hs.app (you tin can utilize Up and Down / Left and Right to change the proper noun)
four. In one case done, Press B to return to the menu, then select "Wellness & Safe Inject"
vii. Select the FBI injectable .app for your region
8. Press A to confirm and inject.
13. We are at present done with this part. Printing Start to reboot. Read the side by side brusk office, to get an idea of how to install your GBA//DSiWare .CIA games.

~(Continuation of previous role) ~ Installing GBA & DSiWare Games ~ (Example)~
1. If you accept followed this guide every bit well every bit the previous half of this optional function, with all my recommendations to the alphabetic character, then you should have a brusk iii second window at kicking time, where you run into the CtrBootManager bill of fare.
ii. When you get to the CtrBootManager carte du jour, we'll want to stop the autoboot, and concord L, and launch Luma3DS.
3. Since our Type2 menuhax config is set up to non trigger when L is held and when launching Luma3DS, while property Fifty, tells Luma3DS to boot into SysNAND. What this results in is allowing us to boot into a patched SysNAND, from where we tin launch the injected FBI.cia, to install our GBA//DSiWare .cias.
4. Open Health and Safe (which is at present FBI)
5. Select "SD"
6. Navigate to wherever you take your GBA & DSiWare .cia files and install them.
seven. Shutdown and Reboot into your RedNAND (This should be pretty automated if you lot take followed this guide with all my recommendations)
8. In one case in RedNAND, install your GBA & DSiWare .cia files equally you would unremarkably, via FBI (Which should be by opening Health and Safety)
nine. Enjoy your GBA & DSiWare games~


~[Optional] Setup lesshax for better bootrates?~
If you want to try lesshax and run across if your bootrate improves, so follow these instructions, it'll too take no debug colors or text, then it'll look clean.
Files nosotros'll need:
-lesshax(ninjhax2.i base) download: https://mega.nz/#!8hUVAL6a!pOLxGkFHo0YxoZZIMxsHjC-5VYxfxpXlof3zm02WVak
Release thread: https://gbatemp.net/threads/release-lesshax-cfw-optimized-ix-2-payload.415077/

one. Download the lesshax.zip
2. Inside the lesshax binder inside the lesshax zip, re-create and replace the corresponding ropbinpayload that matches the one on your SD Card, under the ropbin folder within the menuhax folder.
In this example for Old3DS running 9.2.0-xx U, it'll be: "ropbinpayload_menuhax_USA12288_old3ds.bin"
3. With the ropbinpayload replaced with the one from the lesshax, it'll now boot less.3dsx at boot time.
4. Rename the file motorcar.3dsx to less.3dsx on the root of your SD Card.
5. Reinsert your SD Card into your 3DS, and hope your bootrate has improved~!


~[Optional] Remove the bare image brandish at menuhax~
You'll probably however have a blank image display for menuhax, regardless of whether you used ihaveamac's version or the lesshax version. Both are easy to remove, and you can even customize it to however yous want.

-Black imagedisplay.png for menuhax: https://ihaveamac.github.io/ninjhax2.x/
-Or find custom ones here: https://gbatemp.net/threads/menuhax-2-0-custom-principal-screen-images.401528/
-Or make your own~! The above thread explains the dimensions the PNG has to be.

1. Download the black or a custom imagedisplay.png found in//at the links above. Or make your own.
2. Place information technology at /3ds/menuhax_manager.
3. If you accept followed this guide completely (autonomously from the optional parts) to this point, then you should have a brusk 3 second window at boot time, to load the Homebrew Menu. Do that now.
four. Yous should now exist in the Homebrew Menu
5. Open up menuhax_manager
6. Select "Configure the menuhax splash-screen."
7. Press A to continue.
8. Select "Select a custom image." Then press A.
ix. Wait for information technology to finish.
10. Printing A to get dorsum to the main menuhax_manager menu, then press B, followed past Showtime to exit.
11. Y'all should now be back at your CtrBootManager screen, and information technology'll probably autoboot into your RedNAND. Restart your 3DS to see the changes.
12. You are done~


~[Optional] Custom Theme on SysNAND~
It be nice to have a custom theme on SysNAND, and so that we tin remind ourselves, that nosotros shouldn't be messing around in information technology. For this either make folders in SysNAND and RedNAND that'll remind you lot where you are. Or you could install a custom theme via the menuhax_manager that'll remind us~!

Download a custom theme, from similar: 3dsthem.es
Suggested: https://3dsthem.es/1742

1. Copy body_LZ.bin and bgm.bcstm (bgm.bcstm is optional, ignore it if your theme doesn't have 1) to /3ds/menuhax_manager
2. If you take followed this guide completely (apart from the optional parts) to this betoken, then you should have a short 3 second window at boot time, to load the Homebrew Menu. Practise that at present.
3. Y'all should now be in the Homebrew Carte du jour.
4. Open menuhax_manager
5. Select "Install custom theme"
vi. Expect for it to finish.
7. Printing A to go dorsum to the principal menuhax_manager menu, then press B, followed by Offset to exit.
eight. You should now be back at your CtrBootManager screen, and it'll probably autoboot into your RedNAND.
ix. You'll demand to actually boot into SysNAND to run into the theme. Either boot into SysNAND by holding 50 at boot time, or past launching Luma3DS from CtrBootManager while holding Fifty. (This is assuming you lot followed my recommendations)
x. In one case you boot into SysNAND, you'll run into your custom theme! Now get the hell out of SysNAND you psycho!


~[Optional] How To Dump your 3DS games & 3DS to CIA (Plus Extracting Private Headers)~
I was originally going to write a short optional part for how to use Brahma2+Uncart, until I realized the latest release of Decrypt9WIP supports dumping games and private headers~! And so had to bit that, and so I realized the info could be useful even for A9LH users~! So I will but link to that guide here.
Link: http://gbatemp.net/threads/tutorial...o-cia-plus-extracting-private-headers.432600/

Follow the steps relevant to you lot, and you should exist fine~ ^_^


~[Optional] Removing files nosotros don't demand from our SD Menu~

kAIW4gG.png

-You'll want to basically remove annihilation non in that moving-picture show. You should only have either auto.3dsx or less.3dsx, depending on if you went ahead and setup lesshax. Both are shown in the image for reference only.

-Inside the /3ds folder, you can safely delete the TinyFormat folder.
-Do not delete the Decrypt9WIP, EmuNAND9, Luma3DS, or menuhax_manager folders within the /3ds folder.
-Everything else in the 3ds folder, is up to you to decide on whether you lot keep or delete.

Joined
Dec 7, 2022
Letters
2,848
Trophies
0
Location
ã…¤
XP
2,465
Country
United Kingdom
  • #ii
Geez this is a long tutorial... Prissy one though!
  • #3
Geez this is a long tutorial... Nice one though!
Thanks~ But information technology's hugely adapted from Plailect's A9LH Guide, just re-worked with the Menuhax+RedNAND//EmuNAND user in listen. :)
  • #4
Very good guide :P Skillful job on writing this all out, even if most of the stuff was adapted from plailects, I can tell you put a lot of try into it <iii

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

Last edited past Lia,
  • #5
I have an old3ds ix.2sys with a Luma3ds emu 11.0, fix with phailect's guide.

I but don't want to use the HBL to kick onto the tools because i take successfully installed the hbl_cia and if i ever want to utilize the tools, i just use that.

To get rid of the menuhax hbl i only renamed the luma.3dsx to boot.3dsx and this fix works, but subsequently the menuhax red colour (showing the exploit worked) information technology sometimes just crashes for no apparent reason.

To make my issue clearer, i want a coldboot enviroment directly into cfw with the highest bootrate possible (inside the menuhax enviroment, be it menuhax/lesshax/no colored screen)

I would also like to know the differences between one or another fork of menuhax-loader in detail and their consequences (similar breaking starupdater 3dsx, would it also break the cia?)

EDIT: Also, when setting up menuhax in your guide y'all said to set up it up for type 2 and configure L push button to stop menuhax from triggering and that you'd explain why later in the guide. I seem to have missed that function, didn't find it.

Last edited past Alex658,
  • #half dozen
I have an old3ds ix.2sys with a Luma3ds emu eleven.0, gear up with phailect'due south guide.

I simply don't desire to utilize the HBL to kicking onto the tools because i have successfully installed the hbl_cia and if i ever want to employ the tools, i simply use that.

To get rid of the menuhax hbl i just renamed the luma.3dsx to kick.3dsx and this gear up works, simply after the menuhax reddish color (showing the exploit worked) it sometimes simply crashes for no credible reason.

To make my outcome clearer, i want a coldboot enviroment directly into cfw with the highest bootrate possible (inside the menuhax enviroment, be it menuhax/lesshax/no colored screen)

I would also like to know the differences between one or another fork of menuhax-loader in detail and their consequences (like breaking starupdater 3dsx, would it too break the cia?)

HBL.cia volition rely on the NAND version of where it's launched. So from Emu 11.0 on an o3DS USA panel, it'll use "hblauncherloader_otherapp_payload_OLD-11-0-0-33-U.s..bin" - It'll also rely on boot.3dsx. Because of this, it's not actually recommended you rename your CFW file to kicking.3dsx, equally launching HBL.cia will just cause information technology to load the CFW kicking.3dsx file.

And so the best solution is to actually utilize HxD and make changes to the ropbinpayload.bin on the root of your SD Card. This will allow it to kicking anything y'all tell it, every bit long as it'southward 4 chars. In the example shown in the guide, we changed it to be auto,3dsx from the original boot.3dsx.

ihaveamac's version should merely be a ninjhax 2.seven payload edited to remove the debug//colors, don't think it actually improves bootrate.

While lesshax (yous don't really need to use HxD if yous decide to utilise this) is based on the 2.1 ninjhax base, with stuff removed to hopefully meliorate bootrate and stuff, besides as debug colors//text removed. lesshax should load the less.3dsx file on the root of your SD Carte du jour.

Red screen, I believe usually means it didn't observe the file. Or it could mean that it'due south trying to launch the file style too early on. Using CtrBootManager and adding Luma3DS should give y'all a chip more consistent boot into the Luma3DS.3dsx file.

  • #7
HBL.cia volition rely on the NAND version of where it's launched. So from Emu 11.0 on an o3DS Usa panel, it'll utilize "hblauncherloader_otherapp_payload_OLD-11-0-0-33-USA.bin" - Information technology'll also rely on boot.3dsx. Because of this, information technology's not actually recommended y'all rename your CFW file to boot.3dsx, every bit launching HBL.cia will just crusade it to load the CFW kicking.3dsx file.

Then the best solution is to actually utilize HxD and brand changes to the ropbinpayload.bin on the root of your SD Card. This will allow it to boot anything you tell information technology, as long as it's 4 chars. In the example shown in the guide, we inverse it to be auto,3dsx from the original boot.3dsx.

ihaveamac'due south version should simply exist a ninjhax 2.vii payload edited to remove the debug//colors, don't recall information technology really improves bootrate.

While lesshax (you don't actually need to employ HxD if you decide to use this) is based on the 2.1 ninjhax base, with stuff removed to hopefully improve bootrate and stuff, equally well as debug colors//text removed. lesshax should load the less.3dsx file on the root of your SD Card.

Red screen, I believe normally means it didn't find the file. Or it could mean that it's trying to launch the file manner too early. Using CtrBootManager and adding Luma3DS should requite you a bit more consistent boot into the Luma3DS.3dsx file.


You're right, tried to boot into the hbl.cia while having both the ropbinpayload and the hblauncher_loader it auto downloaded and it just blackness screeens (probably trying to do an inception loading luma from luma)

What is the simplest way of setting all this up for a coldboot method with an optional hbl.cia to practice the rest?

Menuhax colored screen take never bothered me so much, but if lesshax actually improves the charge per unit, then i'd need it's dedicated installer like the one in the starter kit for the normal *hax.

  • #viii
You're right, tried to kick into the hbl.cia while having both the ropbinpayload and the hblauncher_loader it automobile downloaded and information technology just blackness screeens (probably trying to do an inception loading luma from luma)

What is the simplest mode of setting all this up for a coldboot method with an optional hbl.cia to practise the residuum?

Menuhax colored screen accept never bothered me so much, but if lesshax actually improves the rate, then i'd need it'southward defended installer like the one in the starter kit for the normal *hax.

Simplest? Probably using the lesshax payloads and renaming luma.3dsx to less.3dsx. Without using lesshax, y'all'd take to use HxD to modify the robinpayload to suit your needs.

There is no lesshax installer. Yous either build information technology yourself, or use the files I linked, matching information technology with the correct one for your arrangement.
Link: https://gitlab.com/n4ru/less_hax

  • #9
Simplest? Probably using the lesshax payloads and renaming luma.3dsx to less.3dsx. Without using lesshax, you'd have to utilise HxD to alter the robinpayload to conform your needs.

There is no lesshax installer. You either build it yourself, or utilise the files I linked, matching it with the correct one for your system.
Link: https://gitlab.com/n4ru/less_hax


I'one thousand doing this correct at present, since the ropbin was replaced (and i call up this is the menuhax configuration entry) how do i know what buttons to printing in case i want to drop in sysnand?
Nevermind, menuhax managing director notwithstanding works merely equally if it was treating a vanilla menuhax.

boot.3dsx equally hbl
less.3dsx as Luma renamed for coldboot.

EDIT: This setup works wonders!! Also followed your advice to re-configure it equally type two and when i press L information technology takes me back to sysnand (Menuhax is not executed), which is exactly what i wanted. Cheers!

I also used up this custom epitome for the lulz.
https://gbatemp.net/attachments/imagedisplay-png.51611/

Last edited by Alex658,
  • #10
I'm doing this correct at present, since the ropbin was replaced (and i think this is the menuhax configuration entry) how do i know what buttons to press in instance i want to driblet in sysnand?
Nevermind, menuhax manager still works just every bit if it was treating a vanilla menuhax.

boot.3dsx as hbl
less.3dsx as Luma renamed for coldboot.

EDIT: This setup works wonders!! Besides followed your advice to re-configure it equally type 2 and when i press L it takes me back to sysnand (Menuhax is not executed), which is exactly what i wanted. Thank you!

I as well used upwards this custom epitome for the lulz.
https://gbatemp.net/attachments/imagedisplay-png.51611/

Glad it worked out for you~ ^_^

Also: Changes accept been made to the guide, removed Brahma+Uncart, as the latest release of Decrypt9WIP now supports dumping 3DS games and extracting Private Headers, a complete tutorial was written and is linked to in the optional part relating to it.

  • #11
Hello!
How do I update Decrypt9WIP in my 2DS? I take the previous version 20220607 installed in my arrangement.
Do I simply delete the previous files (Decrypt9.log+Decrypt9WIP.dat) and just drag and driblet the new Decrypt9WIP.dat from inside the zip file?
Thank you!
  • #12
Hi!
How practice I update Decrypt9WIP in my 2DS? I have the previous version 20220607 installed in my organisation.
Do I but delete the previous files (Decrypt9.log+Decrypt9WIP.dat) and just drag and drop the new Decrypt9WIP.dat from within the cipher file?
Thank you!
I guess, but not certain what it has to do with this guide, every bit following this guide, we wont be using the .dat versions. We use the .3dsx versions, and from me really using my guide, I never had any errors with not having the .dat files. The only .dat file we need is Luma3DS.dat
  • #xiv
I try to follow this guide on my 3dsxl (fw 9.2)
everything goes well except that with the lastest version of Luma I have a black screen.
Here https://github.com/AuroraWright/Luma3DS/wiki/FAQ-and-Troubleshooting I've read that it's a problem with the gw downgrade...when I first had rxtools I've downgraded to 4.5 with GW.
Tin I follow that guide besides if I didn't install A9LH and sysnand is not the lastest?
I can't undestand well the process
  • #15
I try to follow this guide on my 3dsxl (fw ix.2)
everything goes well except that with the lastest version of Luma I have a black screen.
Hither https://github.com/AuroraWright/Luma3DS/wiki/FAQ-and-Troubleshooting I've read that it's a problem with the gw downgrade...when I showtime had rxtools I've downgraded to four.5 with GW.
Tin can I follow that guide also if I didn't install A9LH and sysnand is not the lastest?
I tin't undestand well the process
Yep, yous should exist able to follow that just fine. But do as information technology tells you. Not certain how well I can help with you lot that, since the instructions are pretty straight forward for me. Step 4 is basically just telling you what option to turn on, when fixing SysNAND when not on A9LH. Y'all'll take to inject FBI into SysNAND when fixing SysNAND tho. Every bit detailed in the optional part titled "~[Optional] Injecting FBI into SysNAND (For GBA//DSiWare Games)~"
  • #16
Yeah, you lot should be able to follow that just fine. Simply do every bit it tells y'all. Not sure how well I can help with you that, since the instructions are pretty direct forward for me. Footstep iv is basically just telling you what selection to plough on, when fixing SysNAND when not on A9LH. Yous'll take to inject FBI into SysNAND when fixing SysNAND tho. Equally detailed in the optional part titled "~[Optional] Injecting FBI into SysNAND (For GBA//DSiWare Games)~"
Your guide was something perfect to me everything works fine actually!
For that problem with luma 5.4 (I recall) I just put firmware.bin in luma binder and it boot up just fine

Inviato dal mio LG-D802 utilizzando Tapatalk

  • #17
Your guide was something perfect to me everything works fine actually!
For that trouble with luma v.4 (I think) I just put firmware.bin in luma folder and it kick up just fine

Inviato dal mio LG-D802 utilizzando Tapatalk

Yeah, that was another fashion to do it likewise, as it will apply the firmware.bin in place of whatever your NAND has. I judge if the effect ever comes dorsum to bite you, you could worry and ready it then, or download the newest firmware.bin and use that.
  • #xviii
Aye, that was another manner to practice it as well, as it will use the firmware.bin in place of whatever your NAND has. I guess if the upshot e'er comes back to bite you, you could worry and set it then, or download the newest firmware.bin and use that.
So the firmware.bin is relative to the sysnand version or emunand version?
Simply to understand

Inviato dal mio LG-D802 utilizzando Tapatalk

  • #19
So the firmware.bin is relative to the sysnand version or emunand version?
Just to sympathise

Inviato dal mio LG-D802 utilizzando Tapatalk

It's used in place off your EmuNAND system version's firmware.bin. I recollect. I mean that's how I've always thought it worked.
aenoch
  • #20
im currently trying to fix my wife'due south 3dsxl. rxtools randomly stopped working via browser and ds profile. i was advised to but install menuhax with luna to supplant rxtools but keep every affair the aforementioned saves etc. i put ll the files from the guide on the sd card even tho i dont demand all the ones you lot listed. i jump to the menuhax browserhax part. i encounter the slider i zoom in i click information technology in the right spot and information technology crashes and says an error has occurred please relieve your data currently in use and restart. im completly lost here

Similar threads

The Catboy
  • No one is chatting at the moment.
    Veho @ Veho: https://i.imgur.com/nvtYFs6.jpg

    Source: https://gbatemp.net/threads/tutorial-installing-luma3ds-cfw-for-2ds-o3ds-n3ds-full-menuhax-rednand-autoboot-setup.432499/

    Posted by: freelandhictoundile1959.blogspot.com

    0 Response to "How To Install Cfw 3ds"

    Post a Comment

    Iklan Atas Artikel

    Iklan Tengah Artikel 1

    Iklan Tengah Artikel 2

    Iklan Bawah Artikel