why exactly would you add emunand support to a CFW designed to only work if no SD is inserted
Because I prefer the features packed into an application rather than diseminated in fifteen. Also emunand is into the planned features list.
why exactly would you add emunand support to a CFW designed to only work if no SD is inserted
Yes it's normal, I forgot to update the version string while compiling... :|Nope nothing, I don't know what to do
EDIT: Solved! I had to swap the boot.bin (Luma) to boot.bin (ShadowNAND_Installer)
Is it normal that is says "ShadowNAND_Installer v1.1-32b7f01d" even if is the v1.2.2?
Just because it supports booting without SD doesn't mean I'M throwing away SD capabilities.why exactly would you add emunand support to a CFW designed to only work if no SD is inserted
All in due time. I'm currently waiting for @Aurora Wright to be done with reboot patches since I suck at such deep levels of programming.Because I prefer the features packed into an application rather than diseminated in fifteen. Also emunand is into the planned features list.
Weird,, it says in my notification feed that you quoted me..
Just because it supports booting without SD doesn't mean I'M throwing away SD capabilities.
It will not be supported for v1.0, maybe 1.5?.. I don't really know to be honest. I'll probably do the easy ones like splashes first. If you have a9lh on any version, you can easily install ShadowNAND without your OTP. If you boot regularly, it won't init the screen (while booting boot.bin), but if you hold DPAD_LEFT while booting, it'll init the screen (in case your boot.bin doesn't).I guess emunand is out of the scope for now. How's the installation compatibility with your old sceeninit stage2? I have that installed right now.
No, it's meant to fully get rid of silly arm9loaderhax.bin on your SD card and unshackle your 3DS from your SD.ok so eventually you plan for it to completely replace the need for a cfw file on the SD i always just assumed this was intended to act as a fallback CFW rather than a replacement
It will not be supported for v1.0, maybe 1.5?.. I don't really know to be honest. I'll probably do the easy ones like splashes first. If you have a9lh on any version, you can easily install ShadowNAND without your OTP. If you boot regularly, it won't init the screen (while booting boot.bin), but if you hold DPAD_LEFT while booting, it'll init the screen (in case your boot.bin doesn't).
Use this copy of Luma, it's the latest commit. http://luma3ds.ericchu.net/latest/homebrew/boot.binhi I installed the latest release but with luma 3ds setted as boot.bin (with paths changed ) into homebrew/3ds I cannot play gba and dsi ware anymore, everything ok if i delete shadownand and reinstall luma 3ds as primary cfw , any help?
No need for OTP.bin if you have a9lh already.I have a9lh 1.0 and no otp.bin :/ how can I install this
so do I just do thisUse this copy of Luma, it's the latest commit. http://luma3ds.ericchu.net/latest/homebrew/boot.bin
No need for OTP.bin if you have a9lh already.
Correct. Do all, except for the otp.binso do I just do this
- minus the bold bit
ok if I break my 3ds you're paying for a new oneCorrect. Do all, except for the otp.bin
Use this copy of Luma, it's the latest commit. http://luma3ds.ericchu.net/latest/homebrew/boot.bin
try this: http://luma3ds.ericchu.net/latest/homebrew/3ds/boot.binjust tried it and the problem persists though :c
this one worked flawlessy, thanks so much
Well, with such a dirty edit, there's always a chance. However, ShadowNAND comes with altstage2 that will always boot even if your stage2 doesn't work. So there will always be a way to revert to regular ShadowNAND. So try it.@Shadowhand is adapting the boot.bin path in payload_stage2.bin @ 0x3F70 viable or is this likely going to brick?
I know what you tried to achieve and I like it. However I have my own path for all application & payloads etc.Well, with such a dirty edit, there's always a chance. However, ShadowNAND comes with altstage2 that will always boot even if your stage2 doesn't work. So there will always be a way to revert to regular ShadowNAND. So try it.
However I'm not very happy with your decision simply because it is an act that will remove one of the very important things I'm trying to achieve here: Having a standardized path for all homebrew.