Correct. Is your SD card formatted as exFAT? Its possible the SD card is corrupted which is preventing the sleep mode library from working which you can easily fix with a reformat.
Wouldn't it work like a USB install?
Also the sticky only goes up to 5.0.2 was updated last july.
Backup your boot files before you install autoRCM. AutoRCM make changes to your boot files, so there’s a warning.guys when i went to the hekate menu and looked at auto rcm it says that it will corrupt my boot0 or boot1
is autorcm safe? i mean i really want to use it else my rail would get spoilt by using that dam paper clip i bent
Also, i tried to install an update for mario odyssey and it kinda stopped at 98% making it corrupt
had to install it again twice so what did i do wrong there?
thank you for your replyBackup your boot files before you install autoRCM. AutoRCM make changes to your boot files, so there’s a warning.
Sometimes there are issues when installing .nsp files. Try it again. If it still doesn’t work, get the update from somewhere different.
Yeah i think so. Also heard that there are regions for updates.thank you for your reply
I went into the backup section and backup all 4 of the files (2 of them were like 29 gb), so i think ill try autorcm
as for the update ill try downloading from a different source. also, i read somewhere that there is a region thing for updates is that true?
EmuNAND or sysNAND on 7.0?Hello, can you guys help me with downgrade, im using nintendo switch with 7.0.0
i have a backup made with sx os but i dunno the version of firmware (i have boot0/1 and files named full00->07 bin files) i don't know how to proceed, i hope it is possible to go back to 6.2 safely
cause i dont wanna lose my switch
please help
EmuNAND or sysNAND on 7.0?
And you have backup of boot files and 6.2.0 firmware?i have sysnand on 7.0, i dont use sx os anymore =s
And you have backup of boot files and 6.2.0 firmware?
Well you could make a backup of 7.0 and restore old backup and boot files. Than boot with hekate in OFW and check which firmware it is. If you have burned fuses to 7.0 you always need to boot in OFW with an custom boot loader after you restored to lower firmware.i dont know the version of firmware i made the backup with sx os , is there a way to know wich version it is ? i dont have 6.2.0 firmware
i'am on 7.0.0 i wanna go back what is the risk ? how to do it too
Well you could make a backup of 7.0 and restore old backup and boot files. Than boot with hekate in OFW and check which firmware it is. If you have burned fuses to 7.0 you always need to boot in OFW with an custom boot loader after you restored to lower firmware.
Yeah backup and restore with hekate. But always make backup before you do anything. You can check with hekate how many fuses are burned. You can downgrade, but if you have burned fuses you always need to boot in custom bootloader (hekate, sx os, ...). You can’t boot to SysNAND over Nintendo boot loader anymore.for the 7.0.0 nand backup i use hekate right ? i think i have burned the fuses to 7.0, i can check with hekate too no ?
you think it is possible to downgrade then ?
for the 7.0.0 nand backup i use hekate right ? i think i have burned the fuses to 7.0, i can check with hekate too no ?
you think it is possible to downgrade then ?
Yeah backup and restore with hekate. But always make backup before you do anything. You can check with hekate how many fuses are burned. You can downgrade, but if you have burned fuses you always need to boot in custom bootloader (hekate, sx os, ...). You can’t boot to SysNAND over Nintendo boot loader anymore.
You can’t boot normally to SysNAND anymore. You still can boot to SysNAND but only through hekate or sx os.i can then only boot with cfw of my choice via rcm ?
You can’t boot normally to SysNAND anymore. You still can boot to SysNAND but only through hekate or sx os.