It worked! It was the adapter! I tried it with a usb a to c cable.
So... I would now only recommend usb a to c cables.
So... I would now only recommend usb a to c cables.
I got a question. I did a partial NAND backup with the latest version, and everything seemed fine. My SD card is barely under 32 GB thanks to some files, so it dumped almost all 2GB parts alright. Once it tells me to make some space, I take the SD card out, put it on my PC, take the dumps out, then put it back in, and it continues dumping.
Now here's where the problems happens. The last file seems to be dumping alright, but upon finishing, it gives me that "SD Card and eMMC data do not match!" I was told to check the SD card with h2testw, which I did and it showed no problem. What could be happening?
Now here's where the problems happens. The last file seems to be dumping alright, but upon finishing, it gives me that "SD Card and eMMC data do not match!" I was told to check the SD card with h2testw, which I did and it showed no problem. What could be happening?
Guys, there's someone converted hekate_ctcaer_4.0.bin to hekate_ctcaer_4.0.h to download to the dongle, and then I can not run the script binConverter.py? Thnx
Hey I just want to confirm this is correct. I just updated from 3.2 to 4.0.
In the ini file I've added.
As i've been using stock firmware trying not to burn any fuses.
In the ini file I've added.
[Stock]
kip1=modules/newfirm/FS510-exfat_nocmac.kip1
{ }
kip1=modules/newfirm/FS510-exfat_nocmac.kip1
{ }
As i've been using stock firmware trying not to burn any fuses.
You can open hekate bin with HxD and select "file" at the top bar, and go to "export" and export it as "c" then just rename it to the .h instead of .c
Not sure, but you also need to consider the game cart fuse.
- Q: I've never run firmware 4.0.0 or higher on my switch, so my gamecard controller firmware is still not updated. How do i make sure my gamecard controller works after i downgrade back to < 4.0.0 ?
- A: When flashing the firmware image for any 4.0.0 or later firmware, ChoiDujourNX will generate a protective hekate_ipl.ini on your microsd, with a "PreventGCUpdate" launch target. You must ALWAYS boot using this launch target (or add kip1patch=nogc to any launch target you wish to use in the future) and use a Hekate that supports the kip1patch option (releases here do: https://github.com/rajkosto/hekate/releases) if you want to prevent use and updating of your GC controller firmware on firmware versions 4.0.0 and up.
Only if you burned fuses when you updated from 3.0.2 to 5.0.1. Otherwise, it is highly recommended.
- Joined
- Mar 29, 2018
- Messages
- 41
- Trophies
- 0
- Age
- 26
- Location
- Australia
- Website
- www.youtube.com
- XP
- 190
- Country
i updated using ChoidujourNX so i didnt burn fuses. so ur saying if i updated normally i can use my 3.0.2 backup? (burned fuses)
edit:
just to clarify what i'm trying to understand: if i used choidujournx to update to 5.1.0 and sumthing happened to my switch, can i use my 3.0.2 backup or do i have to backup on 5.1.0 as well?
Last edited by r6tro,
So just learning about this and trying to understand: So this requires a JIG, and and runs off SD card. And using this i can back up my original boot 0/1 emmc or whatever before i hack with SX os for instance or do other homebrew? and if i ever want to go back to legit original switch to play legit online and connect to nintendo servers, i would just restore the original backup using HEKATE?
Yup, right on the money. You can use your 3.0.2 backup to return to 3.0.2 firmware without using ChoiDujourNX.
Just to be sure.... I know the switch writes to boot0 and/or boot1 each boot, hencw why you should always backup everything in one boot. But does it also write something to the nand or not?
Similar threads
