Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter CTCaer
  • Start date
  • Views 1,072,636
  • Replies 3,243
  • Likes 128

LooP403

Well-Known Member
Newcomer
Joined
Apr 12, 2018
Messages
76
Trophies
0
Age
20
XP
408
Country
United States
i have did try with fat and fat32 with partition default
OK. I'll tell you what I did with my SD card to see if that works. While your switch is turned on (not in CFW) insert your micro sd. It should tell you to reboot. once it reboots, shut it off and try going into cfw again.

If this doesn't work then the only thing I can think of is the size of it being too small.
 

Dontwait00

Unknown
Member
Joined
Sep 3, 2017
Messages
272
Trophies
0
Age
31
XP
701
Country
Italy
I
OK. I'll tell you what I did with my SD card to see if that works. While your switch is turned on (not in CFW) insert your micro sd. It should tell you to reboot. once it reboots, shut it off and try going into cfw again.

If this doesn't work then the only thing I can think of is the size of it being too small.
I tryied like this now, didnt work... :/
 

Spunky247

Well-Known Member
Newcomer
Joined
Jun 20, 2018
Messages
62
Trophies
0
Age
41
XP
2,059
Country
Germany
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?
 
Last edited by Spunky247,

sirAnger

Well-Known Member
Member
Joined
Dec 4, 2002
Messages
481
Trophies
0
Age
40
Location
Michigan
XP
605
Country
United States
@CTCaer I've compiled a new .bin from the most recent master branch to test the archive bit. It doesn't seem to be working when I use the 'switch folder only' option. From what I can understand of your code, I think it might be opening the /switch folder and unsetting the archive bit for files inside it but not actually unsetting the bit for the switch folder itself. I was able to verify loading up a windows computer and unsetting the archive bit on only that folder fixed the issue for me. Homebrew works and all switch games work!
 
Last edited by sirAnger,

Naked_Snake

Constant Miscreant
Member
Joined
Oct 6, 2013
Messages
1,765
Trophies
0
Age
38
Location
Hyrule Field
XP
1,749
Country
Australia
It broke my layeredFS I do t even have the option to repair battery and I downloaded the 3.0 version I loaded up my Skyrim cart for LayeredFS and error as soon as I booted it, Atmosphere also have a purple screen lol
 
Last edited by Naked_Snake,

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
I keep getting failed to init sd card. tried exfat 200gb card and also 128gb fat32 card and same result. help!

--------------------- MERGED ---------------------------


I already tried setting the cluster from 32 to 16 but same thing happening.

--------------------- MERGED ---------------------------


does this only work on 5.1? i'm on 4.1.0 help please
As discussed a failed init is card based and before the filesystem. Changing filesystem does not help.
Anyway, this needs investigation.

i need help! the switch doesnt want to boot on CFW! (error: No FAT/FAT32/exFAT filesystem
i have a 2GB sd card (i have lost my 16gb sd card :D )
2GB, aka SDSC, are not supported.

@CTCaer I've compiled a new .bin from the most recent master branch to test the archive bit. It doesn't seem to be working when I use the 'switch folder only' option. From what I can understand of your code, I think it might be opening the /switch folder and unsetting the archive bit for files inside it but not actually unsetting the bit for the switch folder itself. I was able to verify loading up a windows computer and unsetting the archive bit on only that folder fixed the issue for me. Homebrew works and all switch games work!
I'll check this. Thanks for reporting it.

---------------------------------------------

So, status update:
* Verification for partial dump is fixed (internally) [The bug was not changing the start sector when continuing a partial backup]
* Verification for single file dump is fixed (internally) [The bug was using a 64bit value with a 32bit storage.]
* There's a probably timing bug somewhere that makes the reading or writing or verification fail if it reaches the ~69-71 minute threshold.

Additionally, don't use the current fix attributes implementation, because it may (some had a problem, other didn't) render files in atmosphere and nintendo folders unusable.

Lastly, today, I'll try to track down this obscure "timing" bug. I have already some ways to mitigate it, if it can't be fixed.
 
  • Like
Reactions: sirAnger

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
19,011
Trophies
2
Age
29
Location
New York City
XP
13,379
Country
United States
Additionally, don't use the current fix attributes implementation, because it may (some had a problem, other didn't) render files in atmosphere and nintendo folders unusable.
I know you're a busy man and everything but someone is claiming that your mod broke his license file for SX OS. Now I know you may not care much for SX OS, but if he did something like that, that might explain what happened. Anyways, here's the thread if you ever have the time and want to take a look/help out the user: https://gbatemp.net/threads/how-to-fix-sx-os-boot-dat-error.510109/
 

comput3rus3r

Well-Known Member
Member
Joined
Aug 20, 2016
Messages
3,580
Trophies
1
Age
123
XP
4,921
Country
United States
I know you're a busy man and everything but someone is claiming that your mod broke his license file for SX OS. Now I know you may not care much for SX OS, but if he did something like that, that might explain what happened. Anyways, here's the thread if you ever have the time and want to take a look/help out the user: https://gbatemp.net/threads/how-to-fix-sx-os-boot-dat-error.510109/

didn't break my license file. I feel like it did something to the way the switch reads my memory card. OFW reads the card perfectly ie. installs demos,save games, screenshots. all working fine but when I try to boot into sx-os using the boot.dat file it's like it's not reading it or doesn't see it. I had to go buy a new switch to get my sx-os to work. I used the same memory card and booted up first try. So I don't know what's going on. just seems odd.
 

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
@CTCaer which romfs do I use on 5.1 I loaded the standard one and my Skyrim cart gave me an instant error I might have to go back to my old hekate ini instead of the 3.0 one
I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.

(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)

I know you're a busy man and everything but someone is claiming that your mod broke his license file for SX OS. Now I know you may not care much for SX OS, but if he did something like that, that might explain what happened. Anyways, here's the thread if you ever have the time and want to take a look/help out the user: https://gbatemp.net/threads/how-to-fix-sx-os-boot-dat-error.510109/
That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.

Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)

He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...

EDIT:
didn't break my license file. I feel like it did something to the way the switch reads my memory card. OFW reads the card perfectly ie. installs demos,save games, screenshots. all working fine but when I try to boot into sx-os using the boot.dat file it's like it's not reading it or doesn't see it. I had to go buy a new switch to get my sx-os to work. I used the same memory card and booted up first try. So I don't know what's going on. just seems odd.
So have you thought that the switch you had, may had a sdmmc controller incompatible with the driver hekate (or SX os) uses?
No..
 
Last edited by CTCaer,

Naked_Snake

Constant Miscreant
Member
Joined
Oct 6, 2013
Messages
1,765
Trophies
0
Age
38
Location
Hyrule Field
XP
1,749
Country
Australia
I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.

(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)


That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.

Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)

He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...

EDIT:

So have you thought that the switch you had, may had a sdmmc controller incompatible with the driver hekate (or SX os) uses?
No..
I do t use backup loaders I never said I did, I use my cart only, also what breath of the wild mods are out for switch?
 

comput3rus3r

Well-Known Member
Member
Joined
Aug 20, 2016
Messages
3,580
Trophies
1
Age
123
XP
4,921
Country
United States
I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.

(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)


That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.

Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)

He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...
you're right I didn't try sx-os before I tried to dump nand. Like I stated I found it very odd that i had "fail to init sd" errors on a switch that's 3 months old and literally not being used just waiting for sx-pro to arrive. then I gave up on the nand dump and it won't read the boot.dat file.. then I get a new switch and just boots sx-os boot.dat file perfectly with same sd card.
 

Bakugo

Active Member
Newcomer
Joined
Dec 28, 2016
Messages
33
Trophies
0
Website
steamid.ml
XP
572
Country
United States
So what exactly are the risks of restoring a full unmodified NAND backup? I'm interested in using this to avoid bans before emunand is available.
 

comput3rus3r

Well-Known Member
Member
Joined
Aug 20, 2016
Messages
3,580
Trophies
1
Age
123
XP
4,921
Country
United States
I don't know actually. I don't use any backup loaders.
My mods for BotW and Odyssey still work though.
You can try on other threads.

(The only sure thing, is that in v3.0 the fusee patches are broken for switch 4.X)


That thread does not talk about fix sd card files attributes. With init not done, you can't do any changes on files.

Also he states that he just got sx os. He does not say that it worked before. I hate when assumptions and claims like that are made.
So, false information spreading. Hekate can't break a card. And if it has problem with hekate, he's bound to have problems with sx os payload that loads boot.dat.
(sx os payload uses a similar driver as hekate. It does not uses the switch's driver like the boot.dat code)

He also asked help through PM and I told him I had testing payloads for his case, so we can track down the incompatibility (because these sd work in Horizon and PC, so it must be a case we don't support), but I don't know if I'm willing to help now...

EDIT:

So have you thought that the switch you had, may had a sdmmc controller incompatible with the driver hekate (or SX os) uses?
No..
would that controller change depending on the firmware version? cuz i started out on 4.1 and after 1 hour all i could think of was maybe i need to be on 5.1 and it didnt' work either.
edit: new switch is on 4.1 but I'm afraid to try out hekate now that i have sx-os working on it.
 
Last edited by comput3rus3r,

CTCaer

Developer
OP
Developer
Joined
Mar 22, 2008
Messages
1,154
Trophies
0
XP
3,008
Country
Greece
I do t use backup loaders I never said I did, I use my cart only, also what breath of the wild mods are out for switch?
Then what romFS?
I used latest atmosphere commits and files extracted from my carts and their update files.
I made some simple mods, like changing text and I tried some made for WiiU after converting them.

you're right I didn't try sx-os before I tried to dump nand. Like I stated I found it very odd that i had "fail to init sd" errors on a switch that's 3 months old and literally not being used just waiting for sx-pro to arrive. then I gave up on the nand dump and it won't read the boot.dat file.. then I get a new switch and just boots sx-os boot.dat file perfectly with same sd card.
would that controller change depending on the firmware version? cuz i started out on 4.1 and after 1 hour all i could think of was maybe i need to be on 5.1 and it didnt' work either.
Not firmware version. But based on manufacturer's demands (volume produced) and supplier not able to meat these demands.

So what exactly are the risks of restoring a full unmodified NAND backup? I'm interested in using this to avoid bans before emunand is available.
If you use your switch completely offline, none.
Otherwise inconsistencies may be found by Nintendo.

Before doing that though, wait for v3.1.
 
  • Like
Reactions: Naked_Snake

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    K3Nv2 @ K3Nv2: Nut on the hill