Hey guys, this morning i wanted to switch my 32GB microSD to a new 128GB one, first i booted back to hekate and turned off the switch and took out the 32GBm then first mistake i formatted the 128GB exfat and copied everything in it, when i put it back and tried to boot into RCM with the jig my switch would not go into RCM and neither boot, i tried the whole 12 seconds power button, i tried for 30 seconds, i tried plugging it in but nothing, i of course tried everything with both SD cards but it seems like my switch is dead... do i have any options or am i screwed?
Thanks in advance
Thanks in advance
Okay! That's the info I was missing.
I though the bypass was universal, but it also needs an update.
--------------------- MERGED ---------------------------
So, I was advised to just boot up vanilla Atmosphere with fusee primary to update SYSNAND here: https://gbatemp.net/threads/an-easy...-burning-any-fuses.511847/page-9#post-8803793
I want to add that option to hekate, is this how it should look like in hekate_ipl.ini?
Code:
[UPDATE SYSNAND (CFW)]
emummc_force_disable=1
fss0=atmosphere/fusee-primary.bin
atmosphere=1
icon=bootloader/res/icon_switch.bmp
{}
Last edited by DrDoctor,
Thanks that worked, I'm back in AMS. How can I check my GC fuse count just to make sure? I saw the main fuse info in Hekate but don't think GC was there.
Idk if there is a better way than mine. I have eMMC on 2.1.0 and emuMMC on 8.1.0. I simply checked by booting to 2.1.0 and inserting a game card. If it still works on lower firmware, your gc reader is fine. I haven't heard of a homebrew app to check the gc reader firmware.
Hah! Good thinking, booted into system 3.0.2 and yeah GC works. Thanks mate.
Hey I have a question after update Hekake it gave me the CFW Sysnand option back and like a dumbass I clicked it but turned off the console on the Atmosphere screen
Should I restore my clean nand or not?
Should I restore my clean nand or not?
Can I backup my SMO save, then download the SMO nsp from the Internet and restore the backup to the nsp ?
Yeah I could dump the game card but I don´t want to lose the key/ticket (whatever code will be removed)
Sorry for my English speech
Yeah I could dump the game card but I don´t want to lose the key/ticket (whatever code will be removed)
Sorry for my English speech
Last edited by TheSpearGuy,
@KiiWii there are some problem with 9.0.0, that part of the reason I haven't updated yet, not 100% sure if there is any wrong with 9.0.0 sig patches, as for games corruption if the system can't fix it themself you have to reinstall them yourself. As for blocking Nintendo server I recommend using blawar's Incognito over 90DNS, for the sysmodule remove it when you are done with it.
https://gbatemp.net/threads/incognito.531924/
https://gbatemp.net/threads/a-custo...phere-that-allows-writing-to-prodinfo.541609/
Last edited by Hayato213,
Did you try formatting one of the SD cards as FAT32?
To be specific, Hekate or any other bootloader/CFW does not need to support a new firmware in order to prevent a fuse from being burnt. Updating without burning fuses is merely a process of having AutoRCM enabled after updating the system firmware whether that involves using ChoiDujourNX or updating officially while in CFW and having AutoRCM enabled. If Hekate or any other bootloader/CFW does not support a new firmware but you update to that firmware without burning fuses, then you will not be able to boot into that firmware without burning fuses until Hekate or another bootloader/CFW supports that firmware.Okay! That's the info I was missing.
I though the bypass was universal, but it also needs an update.
Just boot up fusee_primary instead of Hekate. Its much easier and leaves less room for error.
Sure why not?
If you want to be as safe as possible, then yes.
Yes i just put back the old one that was working perfectly but my system seems dead, it doesn't even turn on or show any signs of life!
Okay thanks, I need to check how that process goes because I've always used Hekate.
But is it truly safe to update like this? I've kept my SYSNAND clean since the beginning and would honestly risk burning fuses than getting banned in the future from just updating the console...
Try other USB ports on your computer or USB cables if you have any.
It is as safe as Nintendo determines it to be which is so far safe but that can change in the future. Not to mention updating without burning fuses is an abnormal process therefore it will always carry a ban risk because of its nature. There is no way to update without burning fuses and not risk a ban at the same time. There is one method of updating without burning fuses that does not require CFW or homebrew but it is extremely risky as it relies on your jig booting you manually into RCM after installing the system update. The reason it is risky is because if your jig fails to boot you into RCM even once, then you will irreversibly burn fuses.
Tried all of them and different computers, what worries me is that windows doesn't even makes the sound of "device connecting", it seems like it's completely dead, i'm wondering how is that possible!
That's the one I was going to attempt before being suggested to use the fusee primary method.
I'll check how that one is done and then decide which is the better risk to me.
Thanks.
not sure if this is the right place to ask, but is it possible to have a icon for a gba game on the homescreen and that it then boots up via retroarch?
-
The Real Jdbye
*is birb* -
Veho
-
-
-
-
-
-
-
-
-
-
-
-
@
realtimesave:
Nintendo needs to release a new console, switch is getting such shitty little games lately lol it's pathetic -
-
-
-
@
The Real Jdbye:
well actually
a new console won't do anything right now, because the games are still in development, that's why there are few games being released -
-
-
-
-
-
-
-
-
