No and probably you will never be able to hack it.there is nothing that i can do?
Only if your console's firmware is 6.2 or lower. If it is 7.0 or higher, you need Sept to boot and each CFW has their own Sept folder making it impossible to have both on one SD card unless you move the Sept folder before you boot each CFW.hey guys
can you keep both reinx and atmos (kosmos) at the same time in the same card?
There is no application designed to specifically install .NSP files on lower firmware versions. All .NSP installers (except DevMenu) have an option for ignoring firmware version when installing however this does not work for ignoring the SDK it was built with.What was that application called to install a nsp for lower firmware switch. Today I decided I wanted to install snes online and after installing it, the snes always has an error and closes. When I search for a patch for the most part, all I see are mods to add more games. My switch is 7.0.1 and I do have the latest sig patches from sd setup.
Hekate verifies NAND dumps unlike SX OS. It is not that its real but it may be corrupt and you won't know until you try restoring in which case it would be too late.hey guys i just did a nand back up with sxos menu. Im told that this isnt a 'real' backup, is this true and if so should i use hektate to create backup?
Only if your console's firmware is 6.2 or lower. If it is 7.0 or higher, you need Sept to boot and each CFW has their own Sept folder making it impossible to have both on one SD card unless you move the Sept folder before you boot each CFW.
There is no application designed to specifically install .NSP files on lower firmware versions. All .NSP installers (except DevMenu) have an option for ignoring firmware version when installing however this does not work for ignoring the SDK it was built with.
Hekate verifies NAND dumps unlike SX OS. It is not that its real but it may be corrupt and you won't know until you try restoring in which case it would be too late.
You may never see CFW in your lifetime for that console. Even if CFW does come out, the next Nintendo console may have already come out (and also be hacked). Just buy a used unpatched tablet on eBay.I bought a switch on september 20th, it is not a mariko revision, neither a switch lite, checking the serial, says it is totally patched and unintentionally updated to 9.0.0, btw I don't know which was the initial firmware since when I went to settings it just said "update downloaded"
is there any hope I can install homebrew on a not too far future? I mean, if a mariko support ever comes out
No you can still restore it but you will only be able to boot up the console through RCM because custom bootloaders bypass the fuse check. You just will not be able to boot up the console normally.Oh right thank you for the clarification, and also if I update sysnand normally I won’t be able to restore that back up because fuses will be burned right?
Its under Tools. Also AutoRCM is not tied to CFW, its actually tied to your NAND, namely BOOT0.How do i enable autorcm for the latest hekate? And if i every change to Reinx when its updated do i need to remove the hekate autorcm or can i keep it?
For Zelda you need 8.X.Do I really need to update my switch from 7.x to play games now, I haven’t touched smash since the joker update and I updated the game about two weeks ago and now the software closes when I try to play the game, Zelda a links awaken does the same thing. I get a message the softwares was closed because an error occurred. If I need to update I guess I got to go to 8.x or even 9.x.
No. You need to install them again.Hi,
Is there a way to move games installed (nsp) from the emuMMC hidden partition to the other partition of the SD card ?
Thanks.
Delte "nogc" and only keep nosigchk. Be sure that autonogc is enabled in the hekate_ipl.ini.Hey guys, followed the NG git guide and got files from sdsetup to get everything working on emuMMC from my stock 3.0.2 system. Worked without a hitch until I updated my emuMMC to 9.0.0 via Choi.
Now when I launch into emuMMC from Hekate it flashes the error "failed to apply 'nogc'" and kicks me back to Hekate.
I've read both Hekate and AMS are meant to auto apply nogc as my GC is still from 3.0.2, but I wanted to be extra sure and so added the lines "kip1patch=nogc,nosigchk" to hekate_ipl.ini, and "nogc = 1" to BCT.ini to be extra sure it would be enabled. Is one of those lines screwing it up?