Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,197,886
  • Replies Replies 3,331
  • Likes Likes 128
I for one, am very thankful for 3.0.1 support ! just did a nand dump, then added exfat drivers, now playing Mother 3 :D
some emu do work, but other don't tought (FBA, VBA next, Laines, DSMume work, the rest doesn't)

guess the libs or the way those are compiled are different.
 
Nah, exosphere produces a pink panic screen (SE).
And ofcourse the latest sm.kip and loader.kip halt at a black screen.

Well, at least I updated hbmenu to the latest commit.


EDIT:
I for one, am very thankful for 3.0.1 support ! just did a nand dump, then added exfat drivers, now playing Mother 3 :D
some emu do work, but other don't tought (FBA, VBA next, Laines, DSMume work, the rest doesn't)

guess the libs or the way those are compiled are different.
Some of them need the latest libnx, others must fix more stuff.
 
  • Like
Reactions: Azel and Zumoly
Nah, exosphere produces a pink panic screen (SE).
And ofcourse the latest sm.kip and loader.kip halt at a black screen.

Well, at least I updated hbmenu to the latest commit.


EDIT:

Some of them need the latest libnx, others must fix more stuff.
Too bad...
Thanks for trying though.

Sent from my SM-N9200 using Tapatalk
 
@CTCaer thanks for this v2.0 now i finally dumped my NAND. With the older versions the 128gb fat32 sd card dropped an error.
Thank you for dropping by and informing me for this specific thing.
It means that most of the write errors users had, were because of sd card being busy.
I hope that we finally tackled another problem. x)

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

Btw, the first test on the algorithm for verification of written data to sd card is going pretty well.
I believe we are going to have on site verification in the next version at last!

EDIT:
The verification is extremely fast, even in a class 6 card. So I'll probably make it always on.
 
Last edited by CTCaer,
I have a problem with the latest version. when booting cfw on 5.0.2 with payolad v.2.0 it halts on cfw bootup for a little and then brings me to a black screen. this does not happen on older versions of the payload.
 
I have a problem with the latest version. when booting cfw on 5.0.2 with payolad v.2.0 it halts on cfw bootup for a little and then brings me to a black screen. this does not happen on older versions of the payload.
Hmm strange, it works on my 5.0.2 switch. And I tested it before hours again today.
Can you check your sd card and that the "sdfiles" are OK?
 
yea i used the same files as always and i just tested it with v.1.6 of the payload
and it works fine.

EDIT: i retryed launching with v.2.0 of the payload and it just worked
 
Last edited by SekateSwitch,
Just tested it again.
Any other changes or info you can provide (any additional mods to the eMMC, sd card filesystem and cluster size, etc)?
It is still strange that it boots fine with v1.6 though.

EDIT:
I just tested my 128GB exFAT with 128KB cluster and it also works.
Even though hbmenu shows nothing, it still loads into CFW and launches hbmenu through album icon.
 
Last edited by CTCaer,
  • Like
Reactions: Azel
Hi there, I have a 256GB card which works fine on my Switch, I have a couple of games installed which play fine, saves work etc, so I know the card works in my Switch. However when trying to use the "launch firmware" feature it's saying it failed to mount SD card with a FATFS error 13. My Switch then boots into the OS and clicking on the album button just brings up my pictures. I'm on 3.0.1 and I have copied the files from the sdcard.zip to the root of my SD card.
 
This is "There is no valid FAT volume". No other error in yellow or red letters?
What fs your sd card has? FAT32 or exFAT and also what cluster size?

(Make sure that a valid FAT type partition exists) - that's the only other text, then it does a bunch of white text which goes by too quick to read and boots into unmodified OS. SD card is exFAT, cluster size is reported as 131072 in Drive Genuis, I assume that's bytes.
 
(Make sure that a valid FAT type partition exists) - that's the only other text, then it does a bunch of white text which goes by too quick to read and boots into unmodified OS. SD card is exFAT, cluster size is reported as 131072 in Drive Genuis, I assume that's bytes.
Try to use the Console info -> Print Sd card info
It will probably show the yellow error. If not, tell me.

---------

Btw, you are still not gonna be able to see any homebrew in hbmenu with a 128GB cluster sized sd card.
But you can still launch homebrew by replacing hbmenu.nro with another file.
 
Try to use the Console info -> Print Sd card info
It will probably show the yellow error. If not, tell me.

---------

Btw, you are still not gonna be able to see any homebrew in hbmenu with a 128GB cluster sized sd card.
But you can still launch homebrew by replacing hbmenu.nro with another file.

Print SD Card info just shows the same red error message I get when trying to launch firmware, no further text. What cluster size should the card be?
 
Print SD Card info just shows the same red error message I get when trying to launch firmware, no further text. What cluster size should the card be?
OK, I found 2 places that return this error but do not print a relevant yellow error info.
Try the attached payload, and do the print sd card info again.
 
sector! Error: exFAT - Bitmap allocation at 2
I don't quite understand this error. And in the FatFS code it seems that neither the creator does.
For now I commented this check until I find out what is actually happening.
Try the new payload.


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


For users that have problems with the old hbmenu that is provided in sdfiles.zip, you can get the latest one from OP.
 

Site & Scene News

Popular threads in this forum