I think you just have to use them as "firmware.bin" by renaming it into that name. Correct me if I'm wrong, though.Anyone know the the NTR firm goes? I'm assuming I don't overwrite the /re/firmware.bin?
I think you just have to use them as "firmware.bin" by renaming it into that name. Correct me if I'm wrong, though.Anyone know the the NTR firm goes? I'm assuming I don't overwrite the /re/firmware.bin?
Figured that much. I'm trying to figure out where I actually put the file on my sd card.I think you just have to use them as "firmware.bin" by renaming it into that name. Correct me if I'm wrong, though.
Probably Rei folder. You just have to replace the one you're using with that one. You may also need to delete the _patched files (if you have usepatchedfw flag)Figured that much. I'm trying to figure out where I actually put the file on my sd card.
Thanks I'll give that a try!Probably Rei folder. You just have to replace the one you're using with that one. You may also need to delete the _patched files (if you have usepatchedfw flag)
Wait, what? We can boot straight to NTR now?Anyone know the the NTR firm goes? I'm assuming I don't overwrite the /re/firmware.bin?
Well a9lh combined with bootctr9 can boot in to decrypt9 even when you bricked sys and emunand as long as you didn´t also bircked a9lh. You will have to use the screen init version of a9lh because without it you would have to navigate decrypt9 blindly. But I can understand if you don´t want to use a boot manager just for decrypt9. And you should be able to install all of that and unbrick your nand when you need it as long as you have a9lh with screen init and a9lh isn´t bricked, but on the other hand lots of people will use a hardmod for this stuff and that will always work.Personally, i'd like to see implemented in Aureinand a sort of recovery like Aurora did some pages before, in other words, pressing L+R to boot into D9. I think its fast and convenient, i know it's not related to the rei cfw, but it could be usefull, and no need to install a boot manager just to have decrypt9 set.
Wait, what? We can boot straight to NTR now?
I see Plailect updated the guide with steps to install BootCtr9 to do this. But at the very end it states not to update sysNAND, only emuNAND. What if I wanted to use sysNAND only for an emuNAND-free system?Well a9lh combined with bootctr9 can boot in to decrypt9 even when you bricked sys and emunand as long as you didn´t also bircked a9lh. You will have to use the screen init version of a9lh because without it you would have to navigate decrypt9 blindly. But I can understand if you don´t want to use a boot manager just for decrypt9. And you should be able to install all of that and unbrick your nand when you need it as long as you have a9lh with screen init and a9lh isn´t bricked, but on the other hand lots of people will use a hardmod for this stuff and that will always work.
You can swap NANDs with this easy way: https://gbatemp.net/threads/tutoria...rm9loaderhax-only.415724/page-19#post-6137184 I did it this way and it worked like a charm. Though be sure to create the 2 needed files in the rei folder(updatedsysnand and installeda9lh)I see Plailect updated the guide with steps to install BootCtr9 to do this. But at the very end it states not to update sysNAND, only emuNAND. What if I wanted to use sysNAND only for an emuNAND-free system?
You can, hold L during start up to boot into 9.0-9.2 sysNAND with sigs patched then install this cia by @Columbo2811Does Gateway card work with this? I have hombrew launcher loader but I imagine that would just reboot into Rei if I select Gateway from the home brew menu.
I use my Gateway for 3ds files pretty much and still have a ton of games to finish up there.
I actually got a9lh up and running fine, but Gateway stuff is the only thing left I'm unsure about.
I used the OTP guide to set it up, so it autoboots emunand.
Pretty sure they're illegal to share.I am not sure is it appropriate to shared her files, but I will keep it on util you download.
https://drive.google.com/file/d/0B9tnSrXgLML8Ql9LbVN0WTlEVFk/view?usp=sharing
https://github.com/AuroraWright/AuReiNand/releases/tag/v3.8
Sorry for the wait, but I had issues with the chainloading breaking the .dat version.
Now everything is fixed.
It loads "arm9payload.bin", not decrypt9.bin.I take it this means if we put a decrypt9.bin file into the folder we can boot it with L&R?
(loads an "arm9payload.bin" in the rei folder when pressing L+R)