i remember there being a few posts about New3DS keyslot problems and that the new3ds would not have firmware 9.5 and up. i have updated to 9.5-23u so maybe they got around it?
i remember there being a few posts about New3DS keyslot problems and that the new3ds would not have firmware 9.5 and up. i have updated to 9.5-23u so maybe they got around it?
i remember there being a few posts about New3DS keyslot problems and that the new3ds would not have firmware 9.5 and up. i have updated to 9.5-23u so maybe they got around it?
I'm assuming you update your sysnand and I have not back up the nand if that's the case no there's nothing that can be done and this has nothing to do with it being a new3ds what you're referring to have to do with the emunand and yes that was fixed.
I'm assuming you update your sysnand and I have not back up the nand if that's the case no there's nothing that can be done and this has nothing to do with it being a new3ds what you're referring to have to do with the emunand and yes that was fixed.
Yeah that was fixed the key decoding was cracked the post you are referring to is almost 2 months old it's one of the main reasons Gatewait was so long.
Maybe, maybe not, we don't know tbh. For what it's worth though, NATIVE_FIRM is fairly forwards and backwards compatible, I've managed to run a 9.5 updated firmware from a 9.0 NATIVE_FIRM just fine.
The arm9 encryption added in 9.5 was both unnecessary and redundant from a hacking perspective, as Shiny said. It didn't contribute one way or another to their release being delayed.