Do you have a hekate_ipl.ini file inside the bootloader folder?I formated it to fat32... did the back up... and when I go to Launch I still dont see anything?? it just says
Payloads
More Configs
No Main Config found.
I did everything on the text based guide
( When I launch the payloads on tegra this is the message I see)
ploading payload
Smashing the stack!
Smashed the stack with a 0x7000 byte SETUP request!
Payload successfully injected
The files on my Sd card are: hbmenu.nro,atmosphere,bootloader,edizon,nintendo and switch
Yes but whether or not you will need to boot through RCM will depend if you burnt fuses or not as firmware is irrelevant on the Switch. You can check the list of fuses with their respective firmwares here. Know that you cannot boot the console normally if the fuse count exceeds the firmware. If it does, you can only turn on the console via RCM meaning you will need AutoRCM enabled if you downgrade to a firmware that is less than the fuse count.Is it possible to restore a sysNand backup from an older firmware (let's say 6.0) to a newer firmware (let's say 7.0.1) ?
If it's not possible we have to do a sysNand backup at every firmware ?
Thanks
Use something else like aluminum foil, a paperclip, or thin screwdrivers.I believe so long as you made the backup yourself and it's your switch, it ought to work.
Meanwhile, I ended up upgrading to 8.0.0 in an attempt to get FF10 for Switch having already pre-purchased it, it made me download the update and now my console won't go into RCM mode no matter what I do (tinfoil, or jig) the jig looks like this:
And as you can see the pins are significantly smaller than other jigs. Any way to get this jig to work?
Well either way, you cannot link a Nintendo Account for use with CFW since firmware 8.0 doesn't support CFW yet so you can either downgrade or stay and link the Nintendo Account now. You can just use EmuNAND for CFW and homebrew until TX updates SX OS to work with 8.0.Ok so i was playing around last night creating an emunand which was fine, restored sysnand back to my original which was 4.1 i think it was, went online and updated. Proper $hit myself when i checked the settings and it said fw 8.0. Bad timing or what? Well it doesn't seem to have broken anything, i can still boot into my 6.2 emunand.
Can i reinstall my sysnand back with my backup? is there any point? Am i right in thinking to wait until tx have sorted the sxos with fw 8.0, go online with my emunand and link a nintendo account which was my original requirement, or should i update the emunand with ChoiDujourNX to fw 8 when its available?
Sorry for all the questions....
Its impossible to quantify the chances of a ban since they are random. Just assume you will get banned for taking a hacked console online. And while there are multiple types of ban, the most common block eShop access, online play, and online game updates.Hi,
quick question
I read the tutorials on how to reset a switch, dump nand etc... And it seems super complicated and i WILL mess it up..
I'm on 6.0 and sx os pro on, i haven't done any nand, so my question is :
If i remove SD card, i remove all the games installed on the desktop (xci only) and i reboot the switch, what are my chances to get ban ? I know it's not an exact science but can you give me an approx. ?
If ban, what type of ban would it be (ban from accessing online ?)