just had something weird happen. my first switch said that the sd card had been removed but when i checked it, it was still there. so maybe it's a faulty sd reader after all, probably never noticed since i barelIf the problem is the same with another user's, it's possible.
The other user that had this problem, on initialization, the card was replying garbage stuff, which were out of sd association's spec.
It is possible that this could be because of the controller's init incompatibility instead of the card incompatibility.
EDIT:
Btw, don't think that TX's driver is very different than hekate's and fusee's.
I edited my thread to not blame your mod on my issues. I think what you said is possible that some switches have sdmcc controllers that are not compatible. There's another guy that had same issue as me. I'll try to find his post.Anyway, I don't care about SX OS.
But for hekate, I still want to add support for sdmmc controllers or sd cards like these. But now I only know of one user having that.
just had something weird happen. my first switch said that the sd card had been removed but when i checked it, it was still there. so maybe it's a faulty sd reader after all, probably never noticed since i barel
I edited my thread to not blame your mod on my issues. I think what you said is possible that some switches have sdmcc controllers that are not compatible. There's another guy that had same issue as me. I'll try to find his post.
--------------------- MERGED ---------------------------
@bajul did you ever fix your hekate/boot.dat? issue?
--------------------- MERGED ---------------------------
is there a way to test the sdmcc controller? I mean to isolate the problem since other than not reading the payload it seems to work just fine ie. installing games/saving screenshots/save games ect.
i updated it trying to get it working which of course it didn't. At least the new switch i bought is on 4.1. I guess i'll keep the 5.1 switch that doesn't work with sx-os for online gameplay.Best way is to send it to Nintendo and get a repair. They'll likely update it though
You can restore the first backup and if it did not work you can restore the second backup withou problem!Sorry if this is being asked before, but I didnt found anything.
I made a full nand backup with V2.3 on a brand new 5.1 switch before doing anything else.
Was someone brave enough to restore a dump with 3.0 from an older version (preferably 2.3) and did it work?
I have just made another backup today (which isnt clean anymore of hackish things) with 3.0.
Just in case the old backup will fail, will I still be able to restore todays dump? Or is the Switch totally bricked then?
Sorry for my english, I hope you got what i mean
Cheers
So, I invested some time today and was unable to dump the nand on fat 32 via hekate v3.
I get the error "fatfs 13". I am on 4.1 and have a 128 micro SD.
Now i have read the last 3 pages and If i understand it correct, there actually is a bug with firmware 4.1 and i have to wait for a new Release?
-.-hekate 3.1 (based from last commits)
That is a real dick move.hekate 3.1 (based from last commits)
- Custom boot logo
Enable the use of a custom boot logo when auto booting.
If a log is specified in the selected boot entry, it will be used
If not or the logo was not found, bootlogo.bmp will be used.
If nothing is found or custom boot logo is disabled, hekate's built in logo will be used.