Hacking Official ShadowNAND

[Billy Acuña]

AGB_Firm patched GBA games are GBA games that patched then made into a CIA format, even after using the AGB_firm patch CIA you need a CFW capable of using it, I had a patched AGB_firm and reinand or Luma3DS couldn't run them , just a black screen, but after using Alex's Luma3DS nightlies it started working.

Well, it is more a reboot issue than a AGB one, afaik Shadownand itself doesn't need reboot patches like others CFWs because the system itself reboots and since Shadownand has a miniCFW into the nand, it simply reboots the console without the need of a redirection.

 

[TariqSoftDev]

Well, it is more a reboot issue than a AGB one, afaik Shadownand itself doesn't need reboot patches like others CFWs because the system itself reboots and since Shadownand has a miniCFW into the nand, it simply reboots the console without the need of a redirection.

Jesus you just bitch slapped some realisation into me hahaha, well I guess i'll still wait for those other to do features

 

[alex61194]

Use my fork of CtrBootManager9 for that. YOu can find it here: https://github.com/RShadowhand/CtrBootManager/releases/latest
Put it in /homebrew/3ds/, edit the config file, then simply press DPAD_DOWN to get to the menu.

i edit the bootmgr.cfg and did as you said the same route and when i use dpad_down i get black screen if i dont push nothing i get the normal boot anyhelp pls? i only want to use decript9 and luma3DS

 

[annson24]

i edit the bootmgr.cfg and did as you said the same route and when i use dpad_down i get black screen if i dont push nothing i get the normal boot anyhelp pls? i only want to use decript9 and luma3DS

Are you certain you put bootmgr.bin on /homebrew/3ds folder together with the boot.bin and bootmgr.cfg?

 

[alex61194]

Are you certain you put bootmgr.bin on /homebrew/3ds folder together with the boot.bin and bootmgr.cfg?

yep the only way i found to make it work is to name it boot.bin btw i cant play nds or gba games since i updated to luma 6.0 maybe have something to do with shadownand?

 

[vhaines]

i can't switch back to a9lh v2, how do i uninstall this?

 

[The Catboy]

i can't switch back to a9lh v2, how do i uninstall this?

Just follow this guide
https://github.com/Plailect/Guide/wiki/Updating-arm9loaderhax
Simply rename the "arm9loaderhax.bin" to "boot.bin" and it should auto-boot like your CFW. Then upgrade and it will remove ShadowNAND and replace it with A9LHv2.

 

[alex61194]

i changed the path to run boot.bin i put back in the root of the sd so i dont have to use pathchanger anymore

 

[Halvorsen]

I bricked after installing this onto a fourth 3DS.
My OTP is correct, and I made sure to follow the directions on the site. So this is just a run-off-the-mill brick?

 

[The Catboy]

I bricked after installing this onto a fourth 3DS.
My OTP is correct, and I made sure to follow the directions on the site. So this is just a run-off-the-mill brick?

Are you sure you used your own OTP? You didn't mess with any of the files? I've installed like at lease 20 times in one night when trying to get bootanim 9 (turns out I was dyngus and forgot a step, not related to the thread.) Still, I would think if there was chance of bricking, I would have run into it.
Can you still boot into recovery mod or anything like that?

 

[Halvorsen]

Are you sure you used your own OTP? You didn't mess with any of the files? I've installed like at lease 20 times in one night when trying to get bootanim 9 (turns out I was dyngus and forgot a step, not related to the thread.) Still, I would think if there was chance of bricking, I would have run into it.
Can you still boot into recovery mod or anything like that?

Yeah, of course it's the right OTP, I triple checked.

Got data_input.zip, the ShadowNAND files themselves, and my OTP in the homebrew/3ds/shadowNAND_installer folder. Started the payload, and it said all checks: SUCCESS. Restart, permanent black screen, SD Card in or otherwise. All the files are the right size.

The backlight never turns on, so it's frozen before I can get to recovery mode. It doesn't work regardless. I even used some crazy methods like "maybe the screen isn't initialized, so I'll just find my way to restore a NAND by using another 3DS as a guide so I can see what's onscreen".

I'll get a hardmod eventually.

 

[The Catboy]

Yeah, of course it's the right OTP, I triple checked.

Got data_input.zip, the ShadowNAND files themselves, and my OTP in the homebrew/3ds/shadowNAND_installer folder. Started the payload, and it said all checks: SUCCESS. Restart, permanent black screen, SD Card in or otherwise. All the files are the right size.

The backlight never turns on, so it's frozen before I can get to recovery mode. It doesn't work regardless. I even used some crazy methods like "maybe the screen isn't initialized, so I'll just find my way to restore a NAND by using another 3DS as a guide so I can see what's onscreen".

I'll get a hardmod eventually.

There has to be something missing

 

[Shadowhand]

This is the second brick I've ever encountered.

1) Ever used GW to downgrade the console?
2) Is it region-swapped?
3) Did it already have A9LH installed, or did you try to skip A9LH and install ShadowNAND directly?

 

[Halvorsen]

This is the second brick I've ever encountered.

1) Ever used GW to downgrade the console?
2) Is it region-swapped?
3) Did it already have A9LH installed, or did you try to skip A9LH and install ShadowNAND directly?

Nope, nope, and I was upgrading from Aurora's first build.

 

[annson24]

Nope, nope, and I was upgrading from Aurora's first build.

Maybe the otp file is corrupted? IDK, I'm just guessing. Anyway, you can install shadownand without the otp.bin file if you're already on A9LH. Just sayin'

Sent from my SM-G930F using Tapatalk

 

[Halvorsen]

Maybe the otp file is corrupted? IDK, I'm just guessing. Anyway, you can install shadownand without the otp.bin file if you're already on A9LH. Just sayin'

Sent from my SM-G930F using Tapatalk

That's only for updating standard a9lh. You still need OTP for ShadowNAND.

 

[annson24]

That's only for updating standard a9lh. You still need OTP for ShadowNAND.

No you don't. I've installed shadownand to several 3ds'es with a9lh installed and I didn't used any otp.bin with them.

 

[Shadowhand]

That's only for updating standard a9lh. You still need OTP for ShadowNAND.

He's right, you don't need OTP.bin while switching from regular A9LH.

Anyway, I'm sure it was just a random thing, because as I said, this is literally the second device that bricked, and the first one tried to install ShadowNAND directly. No idea why would that cause anything, but it happened.

 

[Halvorsen]

He's right, you don't need OTP.bin while switching from regular A9LH.

Anyway, I'm sure it was just a random thing, because as I said, this is literally the second device that bricked, and the first one tried to install ShadowNAND directly. No idea why would that cause anything, but it happened.

No you don't. I've installed shadownand to several 3ds'es with a9lh installed and I didn't used any otp.bin with them.

Well, eh, maybe it was an earlier version, but I definitely remember otp being a requirement and there being slight backlash over it.
Good to see that it isn't anymore, but if that was the case, then the otp should definitely not be the cause of the brick. Right?

At least it wasn't my main system. I'm still enjoying ShadowNAND on my others perfectly fine.

 

[Urbanshadow]

He's right, you don't need OTP.bin while switching from regular A9LH.

Anyway, I'm sure it was just a random thing, because as I said, this is literally the second device that bricked, and the first one tried to install ShadowNAND directly. No idea why would that cause anything, but it happened.

The two bricks have a solid resemblance for being random (Success screen then brick). Just saying.

Oh and the device is dandy fine and kicking around with a cool hardmod.