You sure you are using the correct bootloader and patches, if you are using the wrong patches with the wrong bootloader that why your games doesn't work, Also is your CFW on an emuNAND?
You sure you are using the correct bootloader and patches, if you are using the wrong patches with the wrong bootloader that why your games doesn't work, Also is your CFW on an emuNAND?
yes my cfw is on a emunand i made sure i set one up both times I installed the software
--------------------- MERGED ---------------------------
and I downloaded the latest hekate zip so and the hekate sigpatch zip from both websites. Idk whats going on
Pretty sure you need to dump the game or find nsp copy to be install on your emunand.
I've been putting off updating my Switch (it's on 10.2 with AMS 15 using emunand) but finally want to update. So I have a few questions:
1. From what I understand, I should update atmosphere, then hekate (in this order). The update process is essentially just merging new files/folder with the existing ones. Does it matter if I just back up my old files/folders, then delete them on my SD card, and extract fresh copies from the updates?
2. When updating the actual firmware itself, it is recommended that I make a BOOT0/1 eMMC backup. That part seems simple. After this, I should be updating my sysMMC first. So my question is: do I update sysMMC by booting the existing stock firmware (i.e. retail mode with no payloads) and then update the firmware? The reason I ask is that I vaguely remember hekate having non-EmuMMC boot options, making me wonder if these are the ones I should be booting instead.
1. From what I understand, I should update atmosphere, then hekate (in this order). The update process is essentially just merging new files/folder with the existing ones. Does it matter if I just back up my old files/folders, then delete them on my SD card, and extract fresh copies from the updates?
2. When updating the actual firmware itself, it is recommended that I make a BOOT0/1 eMMC backup. That part seems simple. After this, I should be updating my sysMMC first. So my question is: do I update sysMMC by booting the existing stock firmware (i.e. retail mode with no payloads) and then update the firmware? The reason I ask is that I vaguely remember hekate having non-EmuMMC boot options, making me wonder if these are the ones I should be booting instead.
How is the SD card formatted? And have you checked to see if the SD card is fake or not?
Have you tried using other USB ports and/or cables?
Based on what your goal is, you should create an emuMMC now then restore the clean eMMC backup you made way back when. If you create an emuMMC now, it will be a copy of everything that you have done so far on your sysMMC. Restoring a clean backup before making emuMMC will result in you making a clean emuMMC which doesn't line up with your goal unless you wish to go online with emuMMC (which is more safe than you might think).
Fuses are only relevant if your trying to boot the console without Fusee Gelee which you will need in your case. Since Fusee Gelee is triggered before the fuse check, it allows us to technically boot any firmware we want regardless of the fuse count. Do not mistake this for being able to freely downgrade because you would need the exploit Fusee Gelee to boot up the console if too many fuses are burnt when downgrading. Downgrading for the sake of another exploit such as untethered coldboot is pointless if fuses are burnt but downgrading for the sake of a clean eMMC is useful.
Lastly, emuMMC/CFW is realistically the same speed as OFW/sysMMC. Theoretically, it is slower but the different is hardly noticeable.
- While the order of Atmosphere and Hekate does not largely matter, what does matter is how you update the files. It is incorrect to simply merge the existing files/folders because old files/folders will remain with the new ones. Better practice is to delete the old CFW files/folders before placing the new ones on the SD card. You can back them up though before you delete the old CFW files/folders
- You do not need to make an additional BOOT0/BOOT1 and eMMC backup if you already have those backed up. While these are updated when the firmware changes, you can still restore older versions of them. As for how to update the firmware, it depends if you want to burn fuses or not. Fuses only matter in case you ever wish to downgrade to a firmware that has a better exploit than the current one such as a hypothetical untethered coldboot. If you don't care about fuses or downgrading for the sake of a more convenient exploit, then you can just do what you suggested and boot Stock mode via Hekate to update your firmware online. If you do care about burning fuses, which I should mention has no downsides, then you can either update via a homebrew application such as Daybreak or install the firmware update while Atmosphere is running and AutoRCM is enabled. Normally AutoRCM is used to prevent fuses from being burnt but is disabled during firmware updates; Atmosphere circumvents this. Whichever method you choose is ultimately up to you
Thank you for the reply. Just a few follow-ups if you don't mind. Since there are two nands (sys and emu), and fuses can be kept un-burned, is it possible to keep my sys firmware at the lower 10.2 revision, and have my emunand run the latest 12.0.3? Or does updating the firmware on the emu side require updating the sys side as a pre-requisite? I.e. must firmware versions match on both sys and emu sides once everything is said and done? (My reading so far leads me to think that firmware versions must match, and that one has to at least update the sys side before one can proceed to update the emu side.)
The primary purpose of emuMMC is to have separate firmware versions on both sysMMC and emuMMC. That was the way it was used when on the 3DS and Gateway was the only method of hacking it but Gateway required a specific firmware version so emuMMC was developed to allow users to be on later firmware versions without losing the exploit/
I understand it now. Part of my confusion was thinking that the only way to get the firmware update was to update sysnand via Nintendo's online servers. Thus I had this incorrect notion that one necessarily had to update sysnand through official channels before one could update emunand. However, that clearly is not the case after reading your replay, and some googling. Thanks for your help!
Hi All,
I was checking my available memory on my modded switch. I've installed all games and the emuNAND to my SD card but the system memory only shows 8 GB left. I think there may be a game or two that I had installed before modding. Is there any way to figure out where a game is actually installed? I went through the file explorer in Tinfoil but couldn't really figure out what folder would contain those games and they just appear to be a series of letters and numbers rather than folders with game names.
Also, the free 8 GB is around 1 GB less than what I had a week ago. Is there anything about installing new games to the SD card that would also cause me to use up space on the system memory?
Thanks for any help.
I was checking my available memory on my modded switch. I've installed all games and the emuNAND to my SD card but the system memory only shows 8 GB left. I think there may be a game or two that I had installed before modding. Is there any way to figure out where a game is actually installed? I went through the file explorer in Tinfoil but couldn't really figure out what folder would contain those games and they just appear to be a series of letters and numbers rather than folders with game names.
Also, the free 8 GB is around 1 GB less than what I had a week ago. Is there anything about installing new games to the SD card that would also cause me to use up space on the system memory?
Thanks for any help.
Check if you move games into your system internal memory, go to settings, data management then Move Data Between System / microSD Card.
Thanks, I did find around 20 GB of games were actually installed to the system memory. Any idea how that could have happened? Did I just forget to choose SD card in Tinfoil when installing them?
Last edited by Gumdoc,
Well you need to see if you accidentally moved one of your installed game to your internal memory, if you did you can move it back to the SD card, the previous post tell you where to check.
I can only downgrade to the earliest Firmware installed WHILE using auto rcm ? I mean. When i made my clean backup file back in 2019, i've updated my switch sometimes using the official method, only mid 2020 i've started using autoRCm (not entering official nand anymore, so no burnt fusees).
Being so, some fusees were burn AFTER my clean backup, so I must presume that the switch will expect firmware above the one I have backed up.
Effectively, the answer is yes. There is no reason not to be using AutoRCM nowadays. People haven't been banned for using it by itself and it saves wear & tear on your Joy-Con rails.
https://switchbrew.org/wiki/Fuses#Anti-downgrade
you can check this table, there is the expected fuse count and firmware, sometime you might be able to get away with 1-2 firmware over the expected firmware and get it to boot with hekate, if you burn too many fusee and try to boot a lower firmware the system might panic.
Last edited by Hayato213,
Thanks. How to count how many fuses are burn? i triyng to see in hekate screen, but its confusing.
Attachments
it says
9-0 (HOS 7.0.0-8.0.1) so 9 burn fuse, expected firmware is 7.0.0 to 8.0.1,
https://github.com/eliboa/NxNandManager
you can try using this to check the firmware the NAND backup was made from, to get a general idea, if you do restore the old NAND backup make a NAND backup of your current firmware along with the correct boot0/boot1 before restoring.
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
@
Xdqwerty:
@BakerMan, iirc it was about a news article about princess peach showtime using the word "sus" unironically -
-
-
-
-
-
-
-
-
-
-
-
-
@
realtimesave:
Nintendo needs to release a new console, switch is getting such shitty little games lately lol it's pathetic -
-
-
