Hacking Official ShadowNAND

[Urbanshadow]

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.

 

[Shadowhand]

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?

Yes it's normal, I forgot to update the version string while compiling... :|

why exactly would you add emunand support to a CFW designed to only work if no SD is inserted

Just because it supports booting without SD doesn't mean I'M throwing away SD capabilities.

--------------------- MERGED ---------------------------

Because I prefer the features packed into an application rather than diseminated in fifteen. Also emunand is into the planned features list.

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.

 

[Aletron9000]

Weird,, it says in my notification feed that you quoted me..

there was a post error that i corrected that had you quoted. sry

 

[Urbanshadow]

Just because it supports booting without SD doesn't mean I'M throwing away SD capabilities.

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.

 

[Deleted member 381889]

I see the appeal of it, as I would like one cfw, not on my sd card, but on my nand, which has all the patches/features I want

 

[gamesquest1]

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

 

[Shadowhand]

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.

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).

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

No, it's meant to fully get rid of silly arm9loaderhax.bin on your SD card and unshackle your 3DS from your SD.

 

[Urbanshadow]

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).

It's ok, I understand. I'll give it a try tomorrow then.

 

[Shajk00]

hi 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?

 

[Nyap]

I have a9lh 1.0 and no otp.bin :/ how can I install this

 

[Shadowhand]

hi 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?

Use this copy of Luma, it's the latest commit. http://luma3ds.ericchu.net/latest/homebrew/boot.bin

I have a9lh 1.0 and no otp.bin :/ how can I install this

No need for OTP.bin if you have a9lh already.

 

[Nyap]

Use 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.

so do I just do this

• Download ShadowNAND Installer from here
• Download ShadowNAND itself from here
• Download other required files from here
• Put ShadowNAND files, other required files, and your otp.bin to SD:\homebrew\3ds\ShadowNAND_Installer
• Boot from ShadowNAND_Installer.bin or other entry points.
• Press SELECT
• Done.

• minus the bold bit

 

[Shadowhand]

so do I just do this

• minus the bold bit

Correct. Do all, except for the otp.bin

 

[Nyap]

Correct. Do all, except for the otp.bin

ok if I break my 3ds you're paying for a new one
brb

--------------------- MERGED ---------------------------

do I put the a9lh folder in /homebrew\3ds\ShadowNAND_Installer or the things in it (data_input_v2.zip)

 

[Shajk00]

Use this copy of Luma, it's the latest commit. http://luma3ds.ericchu.net/latest/homebrew/boot.bin

just tried it and the problem persists though :c

 

[Shadowhand]

just tried it and the problem persists though :c

try this: http://luma3ds.ericchu.net/latest/homebrew/3ds/boot.bin

 

[Shajk00]

try this: http://luma3ds.ericchu.net/latest/homebrew/3ds/boot.bin

this one worked flawlessy, thanks so much

 

[Zan']

@Shadowhand is adapting the boot.bin path in payload_stage2.bin @ 0x3F70 viable or is this likely going to brick?

 

[Shadowhand]

@Shadowhand is adapting the boot.bin path in payload_stage2.bin @ 0x3F70 viable or is this likely going to brick?

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.

 

[Zan']

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.

I know what you tried to achieve and I like it. However I have my own path for all application & payloads etc.
I don't like calling it homebrew, so I simply have a folder "3ds_launch" which includes everything that would usually lay around on the root of the SD Card.
And I don't want 2 folders (3ds_launch AND homebrew) if I can prevent it.