1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Problem Signing up?

    Please use the contact us link at the bottom of the site listing the problem with your email & ip addresses & the problem will be looked into by our admin team
  3. Temporary emails are not supported for signing up accounts on 3DS Chaos, this includes 10 minute emails. All will be detected by our system & the accounts will be deleted
  4. Shared accounts, multiple accounts & inappropriate usernames not allowed on our site

    Please use a legit email account from a reliable email provider, temporary email accounts are not allowed & will be rejected by our system

CFW Get all latest cfw and info here (links provided)

NeoGamer Mar 19, 2016

  1. NeoGamer

    NeoGamer Chaos Legend Staff Member Moderator

    Joined:
    Oct 9, 2015
    Messages:
    1,019
    Likes Received:
    7,160
    Trophy Points:
    148
    :welcome: THE CUSTOM FIRMWARE THREAD :welcome:

    ITS HARD TO KEEP UP RELEASING THREADS WITH THESE AS THEY CAN KEEP UPDATING ALL THE TIME
    SO THIS IS TO HELP FIND ALL THE LATEST RELEASE'S
    INFOMATION HERE IS NOT FROM ME ITS FROM THERE OFFICIAL PAGES


    AUREINAND

    (REINAND MOD)


    Compared to the official build, this has:

    - 10.4 FIRM support.
    - O3DS support (on consoles which are on 7.x or greater).
    - SysNAND support (both with the firmware.bin on SD and the 9.0 FIRM on NAND).
    - Boot is only delayed if you place the aurei/splash.bin (top screen splash image) or aurei/splashbottom.bin
    - No ARM9 thread (in the official builds, this provides the "Ver." cosmetic patch in System Settings, which happens to patch random "Ver."s in FCRAM, and thus made me uncomfortable, and FCRAM dumping).
    - Comfy to use with A9LH: "updated sysNAND" mode to have an updated sysNAND and (optional) 9.0 emuNAND for ARM9 programs, possibility to easily load external ARM9 payloads, support for screen-init and non screen-init A9LH, noob-proof A9LH protection.

    (Please don't contact me privately if you didn't read this post from top to bottom! [​IMG])

    How to use:
    - If using Arm9LoaderHax, unpack the arm9loaderhax.bin to the root of the SD card.
    - Else copy AuReiNand.dat and the 3ds folder to the root of the SD card. If using menuhax and you don't wish to use a boot manager (such as BootCtr and CtrBootManager), you can use the boot.3dsx from the menuhax folder. Copy it to the root of the SD.
    In all cases, copy the aurei folder to the root of the SD card, and put the firmware.bin in it. New and Old 3DSes have different firmwares!
    a) You can use the latest FIRM (the 10.4 one). They are in the rei-n3ds and rei-o3ds folders in the FIRMs.7z.
    b) If, instead, you need to use NTR CFW, the 9.6 FIRM for Old3DS and the 10.2 FIRM for New3DS are needed. They are in the rei-n3ds and rei-o3ds folders inside the "NTR" folder in the FIRMs.7z.

    You can find all the FIRM files in the FIRMs.7z linked at the bottom of the GitHub page, in the ReadMe.
    Always update the AuReiNand.dat/arm9loaderhax.bin and the aurei folder when updating to a new version!

    Regular mode:
    - Normally emuNAND is autobooted. Holding B boots the second emuNAND (if present). This has no effect if you only have one emuNAND.
    - If you hold R on boot, sysNAND will be booted with the firmware.bin on the SD card.
    - You can boot SysNAND with the 9.0 FIRM. To do this hold L on boot. If you're not using A9LH and your console (O3DS) is not on 9.x, it will be detected and it will just hang on a black screen.

    "Updated sysNAND" mode:
    - For this, you need A9LH. You can toggle it by creating a "/aurei/updatedsysnand" file.
    - Normally sysNAND is autobooted.
    - If you hold L on boot, emuNAND will be booted with the 9.0 FIRM (firmware90.bin) so you can use exploits (you need to create a 9.0/9.2 emuNAND for this!). Please note that you can't have two 9.0 emuNANDs, and that the 9.0 emuNAND must be the first (or the only) one.
    - If you hold R on boot, emuNAND will be booted with the firmware.bin on the SD card. Also holding B boots the second emuNAND (if present). This has no effect if you only have one emuNAND.

    Signature checks are always patched. If you're not using the 9.0 FIRM, the FIRM reboot patch is applied, to allow games which work in the larger RAM mode (Smash Bros, MH4... on Old 3DS, still unused by official software on New 3DS) to work. This needs no user intervention in recent releases.

    Differences in Arm9LoaderHax usage:
    - If you wish to boot the 9.0 FIRM, you need the firmware90.bin for your console, you can find it in the rei-n3ds and rei-o3ds folders, inside the A9LH folder in the FIRMs.7z. Place it in the aurei folder.
    - Booting with A9LH is auto-detected, and when you load SysNAND on A9LH all FIRMs are automatically patched to prevent overwriting A9LH.
    - You can load external ARM9 programs (like Decrypt9) on boot. You need to create a payloads directory inside the aurei folder, place a default.bin inside of it, and(optionally) these other payloads: b.bin, x.bin, y.bin, select.bin, start.bin, right.bin, left.bin, up.bin, down.bin. default.bin gets launched by holding L+R, for the others you need to also hold the corresponding button. If you're using a non-screen-init A9LH, it will be done automatically before launching the payload.
    - When a soft (or "MCU") reboot happens (like exiting from System Settings), AuReiNand will remember and force the last used boot mode. This is to easily keep staying on the NAND you booted (Emu/Sys). You can override this by holding A, which will make AuReiNand behave like on a cold boot (so you can use the same buttons - or no button - as usual to choose a boot mode).
    - Finally, when you quit a GBA game, you'll be forced to SysNAND in every case. This is to prevent loss of your saves.

    Flags:
    These files can be empty and must be placed in the aurei folder.
    "/aurei/installeda9lh": If, for some reason, you want to use the non-A9LH version of the CFW (the .dat + .3dsx from HBL) after booting with the 9.0 FIRM on Arm9LoaderHax, you can force A9LH behavior by creating this file. It's not needed otherwise.
    "/aurei/usepatchedfw": If you wish to have a slightly faster boot at the expense of up to 3 MBs of SD space, you can create this file. However, remove all patched fimwares from the aurei folder if you were using this with the 9.0 exploits and then switched to A9LH, or when I say so with a new release!
    "/aurei/updatedsysnand": Switches to "updated SysNAND mode", as described above.


    FIND LATEST <<<HERE>>>
    FIND FIRMS NEEDED <<<HERE>>>
    SUPPORT <<<HERE>>>



    REINAND

    What is ReiNand?:
    ReiNand is a minimalistic custom firmware for N3DS exclusively. I didn't want tons of complex code, just something that load and patches firm basically.

    Features:

    • Ninjhax 2.5 and MSET support!
    • Sig checks disabled
    • Basic ARM9 thread capabilies (screenshot and RAM dumping)
    • Emunand up to the latest firmware! (with 'Rei' version string)
    • Autoboot
    • Custom splash screens
    • Arm9loaderhax compatible (Works best with dark_samus' fork)*
    Future plans:
    Of course I'm planning to add plenty more features and keep up with this project.
    Some ideas:
    - Config file for autoboot time settings, etc
    - Arm11 process
    ..and much more!

    Credits:
    Thanks to folks over at Cakes for there help as well as 3dbrew!
    Also I'd like to thank the community for your support!

    FIND LATEST <<<HERE>>>
    SUPPORT <<<
    HERE
    >>>


    CAKES CFW


    This is a CFW solution me and @b1l1s have been working on for a while.
    For users:

    Features right now:


    • [*=center]SPIDER 4.x-9.2, MSET 4.x and 6.x and Ninjhax 1/2 (up to firmware 9.2) support for old 3ds/xl/2ds.
      [*=center]MSET 4.x and Ninjhax 1/2 (up to firmware 9.2) support for new 3ds/xl.
      [*=center]Options to boot to sysNAND and emuNAND up to 10.6.
      [*=center]Emunand supports redNAND and GW emuNANDs.
      [*=center]Sig patches
      [*=center]Patches are contained in "cakes". The .cake format is a simple format that bundles FIRM patches, and tells the patcher what those patches need to work.
      [*=center]Autoboot.
      [*=center]Supports multiple NATIVE_FIRM versions
    Future hopeful features:


    • [*=center]Porting CakeHax to homemenuhax, to run idependently from the hax payload.
      [*=center]Loading NATIVE_FIRM from the NAND.
      [*=center]AGB/TWL FIRM patching (and trying to patch them for emuNAND, if possible).
      [*=center]CIA installing over network (b1l1s actually already has a POC for this. Check out the "dhs" branch.)
      [*=center]Region free.
      [*=center]Rainbows.

    How to install:
    Just copy all the files to the root of your SD card, and launch it with either spider, MSET or Ninjhax.
    Files and stuff are on the bottom of the post.
    Copy the firmware.bin linked at the bottom of the post to the cakes directory. Do the same with cetk.
    If you have an old 3ds with a firmware lower than 7.0, and you plan to use a emuNAND version 7.0 or higher, you need to get a file named slot0x25keyX.bin from the internet, and place it on the root of your SD card, and make sure you enable the "Load 7.x NCCH crypto key" patches.
    If you have a new 3ds with a firmware lower than 9.6, and you plan to use a emuNAND version 9.6 or higher, you need to get a file named slot0x11key96.bin from the internet, and place it on the root of your SD card.

    For MSET on 4.x or 6.x, I've modified zoogie's ROP installer to work with this. There's even a code.bin to install the rop via spider in the downloads page.
    For MSET on newer firmwares, first downgrade the MSET app to the 4.x or 6.x version (there's tutorials on this site for doing that), then use the CakesROP.nds or code.bin on the downloads page to install the correct ROP.
    For spider, see the bottom of the post for a launcher page.
    NOTE: The code.bin installs the correct ROP based on your firmware version. If you're on firmware 6.x or higher, the ROP for MSET 6.x will be installed.
    NOTE: Never rename the Cakes.dat. The arm9 payload is located there and the code expects it to be named like that.

    How to use:
    In the "Select patches" menu, you select the features you want/may not want to enable.
    In the "More options..." menu, there's two submenus:


    • [*=center]Toggleable options. This menu contains two options:
      • Autoboot: This will skip the menu when cakes starts, and automatically load the CFW (way faster than usual). Hold the "L" button while booting to enter the menu.
      • Force saving patched firmware: This option is mainly used for debugging, but may also be needed if there's a problem with autobooting/the reboot patches. Cakes tries everything possible to not to have to write firmware_patched.bin, but it may not always be right. This option forces cakes to do it (this option isn't saved in the config file).

      [*=center]Select emuNAND. This menu allows selecting which emuNAND will be booted if you enable the emuNAND patches, if you have more than one emuNAND available.
    In the "Version info" menu, you can check your CakesFW and firmware versions.
    Once done, you select "Boot CFW", and the options you've selected will be saved and the CFW will boot.

    FIND LATEST <<<HERE>>>
    SUPPORT AND FIRMS <<<HERE>>>




    RXTOOLS


    rxMode
    is probably the first free custom firmware for the Nintendo 3DS.
    Since it's part of rxTools, it is bootable from the main menu.

    How it works :
    It supports all Gateway emuNAND up to the latest version.
    It will boot in emuNAND in automatic, if it is present in your sdcard.​


    Note : To boot emuNAND 8.0 or higher, or to play newer games, you need​
    slot0x25KeyX.bin in the root of your sdcard too, if you are on a sysNAND below 7.0.

    Features :

    NATIVE FIRM:

    • Full and free EmuNAND support, up to the latest version, 10.5, also on n3ds!
    • Access to the eShop and to online playing (requires an updated emuNAND)
    • Support for 100% of the games (newer ones will require emuNAND)
    • Support for sysNAND, in case an emuNAND is not found
    • Signatures Checks disabled
    • Dynamic ram dumping (just for debug purpouses)
    • RX-E / S string patch in settings
    • PastaMode, for Signatures Check free, but clean, sysNAND
    • Reboot patch, for using SSBB and MH4 on o3ds
    • Exceptions handler (just for debug purposes)
    • AGB (GBA Virtual Console) Support, wip on n3ds
    • TWL (DSiWare/DS Cardriges) Support, wip on n3ds
    • Region free on both o3ds and n3ds
    TWL FIRM:

    • Cartridge blacklist check disabled
    • Cartridge save type check disabled
    • DSi cartridge save file exploit check disabled
    • Nintendo logo check patch
    • SHA hashes check patched, always succeeds
    • Whitelist check disabled
    • Signatures Check disabled
    AGB FIRM:

    • Signatures Check disabled

    FIND LATEST STABLE <<<HERE>>>
    SUPPORT <<<HERE>>>




    PASTA CFW
    DOWNLOAD <<<HERE>>>

    NTR CFW
    DOWNLOAD <<<HERE>>>



    :knuckles::mario::toad::mariokart::yay3ds::shadow::sonic3::tails::luigi::link::yoshirunning::sonic2::pikachu::flyingpig:

    ITS BEST TO GET SUPPORT FROM THE THREADS LISTED. ANY EXTRA FILES YOU MADE NEED NOT LISTED YOU MAY ASK IN THIS THREAD.
    ALSO THESE CAN CHANGE SO OFTEN SO INFO HERE MAY NOT BE ALWAYS CORRECT REFER TO SUPPORT PAGE FOR LATEST INFO


     
    Last edited: Mar 20, 2016
  2. Superman

    Superman Chaos Legend Staff Member Administrator

    Joined:
    Oct 3, 2015
    Messages:
    1,527
    Likes Received:
    1,361
    Trophy Points:
    485
    excellent thread, all in one place, thanks for this
     
  3. MattKimura

    MattKimura Chaos Contributor Staff Member VIP

    Joined:
    Oct 7, 2015
    Messages:
    216
    Likes Received:
    2,670
    Trophy Points:
    128
    Nice, only thing missing is miniPasta!
     
  4. lebon

    lebon Member

    Joined:
    Nov 17, 2015
    Messages:
    7
    Likes Received:
    0
    Trophy Points:
    1
    good work thank you