If you mean rebuilding the database, yeah, you need to do it. I don't think you have to delete extdata at any moment. You can call Nintendo and all that, but I rather just unlink it and relink it in emuNAND. But if you somehow fuck up the initial installation and have to format the 3DS (or you brick), you risk locking your NNID to a sysNAND that doesn't exist. You can use both your NNID and the eShop by installing the newest NVER (file that controls the eShop), Free Multi Patcher (to apply temporary patches that "trick" Nintendo's servers, allowing you to link your NNID) and HANS (to be able to actually download things from the eShop).Ģ. You should have a section similar to this:ġ.
HOW TO ACCESS THE HOMEBREW LAUNCHER ON 9.2 PC
Once you're done, quit Themehax Manager, shut down your 3DS.īefore turning it on again, put your SD in your PC and check that you have the proper CtrBootManager config. This makes is so that Themehax boots up automatically except when you are pressing any button, which is just the opposite of what is initially set up to do (press L to boot). Once it's been installed, go to the option called "Configure/check haxx trigger buttons", choose Type 1, don't press any button and touch the bottom screen. To do so, use Browserhax to access the Homebrew Launcher and reinstall Themehax. What you need to do, first and foremost, is to boot up your sysNAND and reset Themehax. If you don't unlink your NANDs, I don't know if it's even possible to break this cycle. From what you're saying, you had it configured in such a way it entered a loop that crashed the console: Themehax in sysNAND > boot.3dsx (CtrBootManager) > rxTools > Themehax in emuNAND > boot.3dsx (CtrBootManager) > rxTools > etc.
Otherwise, you should unlink them, or this becomes a nightmare to do.
I will assume that your NANDs are unlinked. You want it to be active in the sysNAND, so it can automatically load boot.3dsx. Let's see.įirst of all, you don't want Themehax to be set up in the emuNAND.
0 kommentar(er)
