Homebrew ARM9Loader -- Technical Details and Discussion

  • Thread starter Thread starter Selver
  • Start date Start date
  • Views Views 581,501
  • Replies Replies 4,025
  • Likes Likes 42
You need the appropriate custom firmware files, and the arm9haxloader.bin that comes with the cfw. Either cakes or rei or aurei. Then look at maybe a boot manager after
 
Thanks for the fast answer, but I don't understand what you mean. Can you elaborate?
For example if you're using AuReiNAND, you'll need to download the latest release from: https://github.com/AuroraWright/AuReiNand/releases

Then, you'll need to copy to the root of your 3DS SD card the arm9loader.bin file, the rei folder, and place the appropriate firmware.bin file in the rei folder.
 
Last edited by NekoMichi,
For example if your using AuReiNAND, you'll need to download the latest release from: https://github.com/AuroraWright/AuReiNand/releases

Then, you'll need to copy to the root of your 3DS SD card the arm9loader.bin file, the rei folder, and place the appropriate firmware.bin file in the rei folder.
You need the appropriate custom firmware files, and the arm9haxloader.bin that comes with the cfw. Either cakes or rei or aurei. Then look at maybe a boot manager after
Thanks guys, I'm looking into AuReiNand now.
EDIT: Got up to the ReiNand splash screen, and then both screens went black again. I think it's because of the firmware.bin file. I used the one I was originally using from before. Am I allowed to ask where to get a firmware.bin file? It wasn't in the files with AuReiNand.
 
Last edited by Boogieboo6,
Thanks guys, I'm looking into AuReiNand now.
EDIT: Got up to the ReiNand splash screen, and then both screens went black again. I think it's because of the firmware.bin file. I used the one I was originally using from before. Am I allowed to ask where to get a firmware.bin file? It wasn't in the files with AuReiNand.
The firmware files from before won't work, you'll need to read https://github.com/AuroraWright/AuReiNand/
There's a section on where to obtain the firmware files for your 3DS model.
 
The firmware files from before won't work, you'll need to read https://github.com/AuroraWright/AuReiNand/
There's a section on where to obtain the firmware files for your 3DS model.
Did this, got the proper file. I tried it 3 different ways. I threw it in next to the other firmware.bin because it was named firmware90.bin. Then I deleted firmware.bin and left the other as firmware90.bin. Then I renamed firmware90.bin to firmware.bin. It freezes on the Reinand splash screen.
 
Did this, got the proper file. I tried it 3 different ways. I threw it in next to the other firmware.bin because it was named firmware90.bin. Then I deleted firmware.bin and left the other as firmware90.bin. Then I renamed firmware90.bin to firmware.bin. It freezes on the Reinand splash screen.
You need both firmware.bin and firmware90.bin in the /rei/ folder.
 
Did this, got the proper file. I tried it 3 different ways. I threw it in next to the other firmware.bin because it was named firmware90.bin. Then I deleted firmware.bin and left the other as firmware90.bin. Then I renamed firmware90.bin to firmware.bin. It freezes on the Reinand splash screen.
If you have an original 3DS/3DSXL/2DS:
From the FIRMs folder, copy firmware.bin from rei-o3ds to the rei folder on your SD card.

If you have a new 3DS/3DSXL (released 2015 or later):
From the FIRMs folder, copy firmware.bin from rei-n3ds to the rei folder on your SD card.
 
If you have an original 3DS/3DSXL/2DS:
From the FIRMs folder, copy firmware.bin from rei-o3ds to the rei folder on your SD card.

If you have a new 3DS/3DSXL (released 2015 or later):
From the FIRMs folder, copy firmware.bin from rei-n3ds to the rei folder on your SD card.
I've made sure that I'm using the proper files and I even switched to o3ds files just to be sure. I forgot to mention that the orange light doesn't turn on for wireless. Isn't that a brick sign? What if it's actually working fine but it's trying to throw me into a broken sysnand which freezes the console?
 
I've made sure that I'm using the proper files and I even switched to o3ds files just to be sure. I forgot to mention that the orange light doesn't turn on for wireless. Isn't that a brick sign? What if it's actually working fine but it's trying to throw me into a broken sysnand which freezes the console?
Did you delete any rei folders before copying across the new rei folder from AuReiNAND? Also, there shouldn't be a ReiNand.dat on the root of the card.
Could you please upload a screenshot of the SD root contents and the rei folder contents?
 
Last edited by NekoMichi,
Did you delete any rei folders before copying across the new rei folder from AuReiNAND? Also, there shouldn't be a ReiNand.dat on the root of the card.
I didn't at first, I used the old Rei folder. Then I deleted it and tried again. Currently I'm using a new downloaded Rei folder and inserted the AuReiNand files. I deleted a ReiNand.dat from the card and tried again. It didn't work.
 
Did you delete any rei folders before copying across the new rei folder from AuReiNAND? Also, there shouldn't be a ReiNand.dat on the root of the card.
Could you please upload a screenshot of the SD root contents and the rei folder contents?
I didn't notice you edited your post, sorry about that. I learned that AuReiNand autoboots into emunand when it starts, by holding R, I got into sysnand. I never restored my emunand after I bricked it by a 2.1 downgrade. That's why it kept going to a black screen. When loading Sysnand, I got menuhax and then ctrbootmanager, this was my old setup. Currently, I'm trying to get Decrypt9 to work. It just kicks me back to the boot manager. If you can help me get Homebrew back to working order, I can restore my emunand backup and fix it. Then I'll be perfect!
 
  • Like
Reactions: NekoMichi
I didn't notice you edited your post, sorry about that. I learned that AuReiNand autoboots into emunand when it starts, by holding R, I got into sysnand. I never restored my emunand after I bricked it by a 2.1 downgrade. That's why it kept going to a black screen. When loading Sysnand, I got menuhax and then ctrbootmanager, this was my old setup. Currently, I'm trying to get Decrypt9 to work. It just kicks me back to the boot manager. If you can help me get Homebrew back to working order, I can restore my emunand backup and fix it. Then I'll be perfect!
Ah, that would explain a lot then. Decrypt9 seems to have a poor startup rate for me too. I was able to get it to run by going into the boot manager menu, then selecting the Decrypt9 .3dsx from the file browser. This avoids using the homebrew menu altogether, although it took several attempts.
 
Ah, that would explain a lot then. Decrypt9 seems to have a poor startup rate for me too. I was able to get it to run by going into the boot manager menu, then selecting the Decrypt9 .3dsx from the file browser. This avoids using the homebrew menu altogether, although it took several attempts.
I'll start trying it your way then. In the event that it just won't boot Decrypt9 at all, what should I do from there? I'm actually having it work all by itself now. It's autobooting Decrypt9WIP.3dsx. It's not working at all. Other homebrew works, but not Decrypt9. I even tried Emunand9 and that doesn't work either. I also updated Decrypt9 and it STILL didn't work. Are there other tools besides Decrypt9?
 
Last edited by Boogieboo6,
I didn't notice you edited your post, sorry about that. I learned that AuReiNand autoboots into emunand when it starts, by holding R, I got into sysnand. I never restored my emunand after I bricked it by a 2.1 downgrade. That's why it kept going to a black screen. When loading Sysnand, I got menuhax and then ctrbootmanager, this was my old setup. Currently, I'm trying to get Decrypt9 to work. It just kicks me back to the boot manager. If you can help me get Homebrew back to working order, I can restore my emunand backup and fix it. Then I'll be perfect!
I believe that when holding R in aureinand, it boots sysnand with a newer firmware - making Decrypt9 fail. You can boot sysnand with the 9.0 firmware by holding L instead.
Alternately, you can use the arm9loaderhax version of Decrypt9.
 
I believe that when holding R in aureinand, it boots sysnand with a newer firmware - making Decrypt9 fail. You can boot sysnand with the 9.0 firmware by holding L instead.
Alternately, you can use the arm9loaderhax version of Decrypt9.
Why did this message not load until now?! Anyways, I managed to use emuNAND Tool V1.0.1 (A PC tool) to restore my emunand backup. It now works 100% of the time and boots flawlessly into emunand. Thank you Trinitro and a big thanks to NekoMichi for all of your help!
 
  • Like
Reactions: NekoMichi
Just reporting I have pulled Arm9 from Dark_Samus's github today and have installed on n3dsxl via .3dsx without a nand restore before hand. Do files get left over when flashing like this?

All is working okay. Is their a chance of it later corrupting through normal use?
 
Last edited by democracy,

Site & Scene News

Popular threads in this forum