- Thread starter Reisyukaku
- Start date
- Views 811,853
- Replies 6,480
- Likes 115
This setup a 3rd folder under Nintendo 3DS, but emunand is still getting stuck on the one theme lol.
So it's not to do with linked NANDs? I mean both nands are on seperate themes, it's just the emunand one seemingly cannot be changed (at least not permanently).
Last edited by Audioboxer,
I'm sorry if this question has already been asked, but there are a lot of posts in this thread and I can't find what I'm looking for. I have dumped my OTP and restored my sysnand backup so I am back on 9.2, running Reinand with a 10.5 emunand. I have also built the arm9loaderhax installer. Is there a guide anywhere to explain how I use the installer to boot Reinand from cold boot? I don't mind whether it boots the emunand on the SD card, or if it clones the emunand to sysnand and boots that. Thanks in advance!
Personally my advice is just to hold off for now till more work is done with payloads. If you really want to then grab the arm9loaderhax.bin Rei posted some pages back (think it's post 19x) and put that on the root of your sd card. With official Rei 3.2 this will boot you into emunand. That's it. Obviously after installing arm9loaderhax.3dsx, but put the .bin file on your sdcard first.
It's only a bit more complicated if you were like me and started all of this with no emunand (to boot into sysnand Shadow's .bin payload is needed as well as the Rei unofficial mod). No need to do this if you have an emunand.
Last edited by Audioboxer,
Installation reinand as usual (copy the zip contents),
copy your arm9loaderhax.3dsx (and probably all the other "output" files, wont hurt) onto your SD card and grab the file Reisyukaku posted a few pages back (arm9loaderhax.bin, page 193) and place it in the root of your SD card
Now boot into homebrewlauncher in sysNAND and start the loaderhax 3dsx file.
It should start installing, and after that your 3ds should auto coldboot into your emuNAND
One note: after that there is no way to boot sysNAND (or even power on without SD card) as the arm9loaderhax.bin is required.
To boot into something else, you need to swap out the *hax.bin
First thing to do would be sysNAND backup for easy restore later on if you want to get rid of the modified bootloader, but for now Decrypt9 won't work inside emuNAND hbl Launcher because wrong FIRM probably
Last edited by Sylthos,
I have a question : with the a9lh's and rei's CFW cold boot, do you still have to close/open lids to fix the 3D ?
- Joined
- Oct 7, 2007
- Messages
- 4,312
- Trophies
- 3
- Age
- 35
- Location
- Levelland, Texas
- Website
- www.mariopc.co.nr
- XP
- 6,335
- Country
-
I've got the output files and the armloaderhax.bin Rei posted back on page 193 but I'm getting a red screen when I open armloaderhax.3dsx. Just to make sure, what are the paths to the files?
Currently I've got arm9loaderhax.bin at the root of the sd card along with the other output files and arm9loaderhax.3dsx in the 3ds folder.
Currently I've got arm9loaderhax.bin at the root of the sd card along with the other output files and arm9loaderhax.3dsx in the 3ds folder.
the other output files need to be in the same folder as arm9loaderhax.3dsx
I think you have to put the other files (not the payload arm9loaderhax.bin) to the folder where the 3dsx is
no, only the 3dsx is needed. don't know why the other files end up in data_output.
Thanks for confirming. I haven't seen a full guide only bits and pieces. Is there a full guide from start to finish? I've read the otp guide. I might try this out. I have a mate that can hardmod if anything goes wrong
Similar threads
-
- Article
