The payloads are the same on every version. The difference in installation is the difference in version.Maybe because the OPT less installation has nothing to do with the payloads themselves. It's just a "different" way to install them.
The payloads are the same on every version. The difference in installation is the difference in version.Maybe because the OPT less installation has nothing to do with the payloads themselves. It's just a "different" way to install them.
These are the one's you need if you don't know what the other's mean/do:how do I configure Luma3DS v.6.3.1 correctly? I always used the "basic" settings (in older versions of Luma) listed on AuroraWrights page and I have no clue what I am supposed to check off anymore hope someone might be able to help me
- Use the (A) button and the D-Pad to turn on the following:
- "Autoboot SysNAND"
- "Use SysNAND FIRM if booting with R (A9LH)"
- "Show NAND or user string in System Settings"
- "Show GBA boot screen in patched AGB_FIRM"
- This may cause crashes for some injected GBA Virtual Consoles
- If some games do not work properly, disable this option and try again
- If you are using a New 3DS, you should also enable the following:
- "New 3DS CPU" to "Clock+L2(x)"
- This will increase the framerate of many games, but may cause instability in others
- If some games do not work properly, disable this option and try again
thank you, thank you, thank you!These are the one's you need if you don't know what the other's mean/do:
So I checked and the payloads are different. At least for the v1 and v2 used in Plailect guide.The payloads are the same on every version. The difference in installation is the difference in version.
Its on the guide -_-thank you, thank you, thank you!
20 minutes of Google-ing - nothing, ask here - less than five minutes
where specifically can you see the exact settings I needed to apply to my device in the guide? I could not find it, and I was sitting there with my device, stuck on the customization page, so I asked for help. why did you feel the need to reply to my post just to say that? I got the answer I needed and moved on. you might claim that I spam the thread with questions already asked, but you spam the thread with "Its on the guide -_-", but oh, well. each to their own, I suppose.Its on the guide -_-
Ignore it and don't replywhere specifically can you see the exact settings I needed to apply to my device in the guide? I could not find it, and I was sitting there with my device, stuck on the customization page, so I asked for help. why did you feel the need to reply to my post just to say that? I got the answer I needed and moved on. you might claim that I spam the thread with questions already asked, but you spam the thread with "Its on the guide -_-", but oh, well. each to their own, I suppose.
where specifically can you see the exact settings I needed to apply to my device in the guide? I could not find it, and I was sitting there with my device, stuck on the customization page, so I asked for help. why did you feel the need to reply to my post just to say that? I got the answer I needed and moved on. you might claim that I spam the thread with questions already asked, but you spam the thread with "Its on the guide -_-", but oh, well. each to their own, I suppose.
Ignore it and don't reply
--------------------- MERGED ---------------------------
Its two posts merged in one ans just linked you to you to the guideno, but all of this is
thank you, but I already customized/set up, and my problem is solved. I know where to look next time I might get stuck, though.Its two posts merged in one ans just linked you to you to the guide
U don't need firmware.binThis semi falls into this category I gotten the custom themes to work but now ntr cfw won't work with luma cfw I have both firmware.bin & ntr.bin even rebooting no luck plz help c: ?
This is what i get now even after putting on root and luma folderU don't need firmware.bin
Use thisThis is what i get now even after putting on root and luma folder
UPDATE:
Nvm I managed to fix it
I am also interested. I manually removed emunand when switching to a9lh but a friend of mine kept his out of laziness. How does one remove emunand from Luma now?So there is one thing from 6.3 which never really was explained anywhere and which seemed to have sliped without much notice.
It interests me how to do it since I want to remove mine and also why it works, since it wasnt really possible before. I guess it has not anything to do with Emunand9, since it has its last commit nearly a month prior to lumas 6.3 release.
- A full format of the SD card is no longer necessary to remove an EmuNAND (also fixes crashes when trying to boot EmuNAND with an SD which used to have one and wasn't fully formatted).
I am also interested. I manually removed emunand when switching to a9lh but a friend of mine kept his out of laziness. How does one remove emunand from Luma now?
I know, and I have done so. I only inquire as to the meaning of that precise line on Luma changelog.Removing Emunand? Just format your SDcard. (classic method but very easy way)