Hacking Official ShadowNAND

[Ghassen-ga]

I already have v.82 installed , can someone guide me how to update shadowNand properly ? thank you.

 

[Halvorsen]

I already have v.82 installed , can someone guide me how to update shadowNand properly ? thank you.

The exact same way you installed it in the first place.

 

[Ghassen-ga]

The exact same way you installed it in the first place.

Let's just say that it wasn't me who installed it, and don't worry i got it figured , thanks for your help (:

 

[Aletron9000]

is there a way to remove shadowNAND without and NAND backup like a9lh v2? or is a backup needed?

 

[Billy Acuña]

is there a way to remove shadowNAND without and NAND backup like a9lh v2? or is a backup needed?

Install another a9lh with SA9LHI.

 

[Shadowhand]

So, I will be releasing new versions of ShadowNAND and SaltFW soon, but I need input on which paths to use.

As everyone knows I used to prefer /homebrew/, however the scene's lack of enthusiasm and disorderliness tired me. So now I simply don't care. There's a big chance I'll make it use SD root, but I still wanted to ask the users before I went ahead and did it.

 

[annson24]

So, I will be releasing new versions of ShadowNAND and SaltFW soon, but I need input on which paths to use.

As everyone knows I used to prefer /homebrew/, however the scene's lack of enthusiasm and disorderliness tired me. So now I simply don't care. There's a big chance I'll make it use SD root, but I still wanted to ask the users before I went ahead and did it.

Actually the homebrew folder was such a good idea, however, you're right. Seems like nobody bothers to use it (or maybe it's just not advertised well). Anyway, I would like to suggest to use the Luma folder since I think luma3ds is the base firmware everybody is using but I see you're not using it. Maybe the root folder will be best (although messy *sigh*)

 

[shawn_]

So, I will be releasing new versions of ShadowNAND and SaltFW soon, but I need input on which paths to use.

As everyone knows I used to prefer /homebrew/, however the scene's lack of enthusiasm and disorderliness tired me. So now I simply don't care. There's a big chance I'll make it use SD root, but I still wanted to ask the users before I went ahead and did it.

The root if not homebrew/
I still like the idea of keeping it off the root if possible, less messy
Thanks [emoji1303]


Sent from my iPhone using Tapatalk

 

[Shadowhand]

Actually the homebrew folder was such a good idea, however, you're right. Seems like nobody bothers to use it (or maybe it's just not advertised well). Anyway, I would like to suggest to use the Luma folder since I think luma3ds is the base firmware everybody is using but I see you're not using it. Maybe the root folder will be best (although messy *sigh*)

I have brought the topic up to lots of people, including profi2000, but they were less than happy about the change. So I give up.

 

[Urbanshadow]

I have brought the topic up to lots of people, including profi2000, but they were less than happy about the change. So I give up.

Heh. Whatever change you finally implement i'll carry with it, as always. There's no point on complaining. It's a shame devs in general haven't complied to a standard (specially now that d0k3 centralized fs usage to a files9 folder).

If you actually need a suggestion, change the path from /homebrew/3ds/ to /ShadowNAND as everyone is doing this days and let it be.

 

[Shadowhand]

Heh. Whatever change you finally implement i'll carry with it, as always. There's no point on complaining. It's a shame devs in general haven't complied to a standard (specially now that d0k3 centralized fs usage to a files9 folder).

If you actually need a suggestion, change the path from /homebrew/3ds/ to /ShadowNAND as everyone is doing this days and let it be.

Thank you for the support. About the path; it'd cause more issues than it solves, actually. When the time comes for ShadowNAND to do splashes, of course it will use /ShadowNAND, but until then, I think I will stick to SD root.

 

[Aletron9000]

Just a suggestion, could you add a ShadowNAND uninstaller to the installer? It is easier access and faster.

 

[Urbanshadow]

Just a suggestion, could you add a ShadowNAND uninstaller to the installer? It is easier access and faster.

SafeA9LHInstaller is able to update shadownand to aurora's a9lhv2. I asume it can uninstall it too.

 

[astronautlevel]

Just a suggestion, could you add a ShadowNAND uninstaller to the installer? It is easier access and faster.

Normal safea9lhinstaller can do this, since it's just a manner of resetting the keystore on the n3ds and then rewriting FIRM0 and FIRM1 with the stock data.

 

[laharl22]

Any news shadowhand ?i always on shadownand since the beginning i love the boot.bin for luma and safeboot for ctrmultibootmanager thankssss

 

[The Catboy]

So, I will be releasing new versions of ShadowNAND and SaltFW soon, but I need input on which paths to use.

As everyone knows I used to prefer /homebrew/, however the scene's lack of enthusiasm and disorderliness tired me. So now I simply don't care. There's a big chance I'll make it use SD root, but I still wanted to ask the users before I went ahead and did it.

I actually like /homebrew/ path. Mostly because I find it cleans up the root of my SD card a bit more.

 

[ThunderbInazuma]

I don't know if this is possible, but since there are 50% of people which like the /homebrew/ path and another 50% which like the root/arm9loaderhax.bin , wouldn't be possible, make two releases, for each path? I'm saying this, but I don't know if this is simple or not.

 

[metroid maniac]

The problem is that the standard has already been established to keep the payload in the SD card root. Trying to change things at this point makes things more complicated, not more simple.

Well in any case, I don't think it's a major issue. Moving a single file to a different directory is something anyone can do.

I don't know if this is possible, but since there are 50% of people which like the /homebrew/ path and another 50% which like the root/arm9loaderhax.bin , wouldn't be possible, make two releases, for each path? I'm saying this, but I don't know if this is simple or not.

Maybe it could try different paths? i.e. try path 1, if there's no file there then try path 2, if there's no file there try path 3 etc. until it either locates a payload or falls back on the built in miniCFW. Overcomplicating things with multiple releases isn't much of a solution.

 

[Thunder Kai]

What is screeninit?

 

[ThunderbInazuma]

The problem is that the standard has already been established to keep the payload in the SD card root. Trying to change things at this point makes things more complicated, not more simple.

Well in any case, I don't think it's a major issue. Moving a single file to a different directory is something anyone can do.



Maybe it could try different paths? i.e. try path 1, if there's no file there then try path 2, if there's no file there try path 3 etc. until it either locates a payload or falls back on the built in miniCFW. Overcomplicating things with multiple releases isn't much of a solution.

Yeah, your option is also good,