Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,195,819
  • Replies Replies 3,331
  • Likes Likes 128
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.
I'm on 3.0.2 so I can't report on older versions but my 256gb samsung sdcard worked perfectly fine on 1st try for full nand dumping :)
 
I'm on 3.0.2 so I can't report on older versions but my 256gb samsung sdcard worked perfectly fine on 1st try for full nand dumping :)
exFAT or FAT32?

EDIT:
This is a FatFS error, so it doesn't matter the version you are in. And it actually helps to find out that other 256GB work.
 
Last edited by CTCaer,
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.

This shows info on my SD card, huzzah! It only has the console info and power options though, no firmware launching.
 
This shows info on my SD card, huzzah! It only has the console info and power options though, no firmware launching.
Ofcourse, because I will not allow you to use a debug version with some random (maybe important) check commented out.
It shows info on your partition btw? Down below, it should say that it found XXXXXX filesystem, size of partition and cluster size.
 
Ofcourse, because I will not allow you to use a debug version with some random (maybe important) check commented out.
It shows info on your partition btw? Down below, it should say that it found XXXXXX filesystem, size of partition and cluster size.

Fair point! Better safe than sorry. Yeah it says "Found exFAT volume" and then "Free: 243797 MiB" and "Cluster: 128 KiB"
 
did one dump on fat 32, will try one on exfat
Edit ; started the dump, seems to be working

did a SD Card info before doing it :
VID 1B
OEM ID SM
HWr 3
FWr 0
SN xxxxxxxx
M/Y 10 2017
Cmd Cl 5B5
Cap 244224MiB
Bus W 4
SClass 10
UHS U3
Vid Class V0
AppPref Class A0
w protector 0

free xxxxx MiB
Cluster 128KiB

My SD Card works flawlessly with HBL too btw^^ (sorry I said before that I was on 3.0.2, I'm on 3.0.1)
 
Last edited by Azel,
How the sd card was formatted? Factory or switch?

There's a way to fix it by formatting it in windows (or linux).
If you use windows, when you restore the files back, make sure to select the Nintendo folder and any other file or folder and right click to untick "folder/file is ready for archiving".

But I'll read the exFAT datasheet, so if you can wait 1 day, we may end up fixing a bug on the FatFS exFAT driver.

EDIT:
did one dump on fat 32, will try one on exfat
Edit ; started the dump, seems to be working
Yeah if you formatted it normally it should not have this problem.
The actual problem if I understand it, is that it can't find the first bitmap allocation. It starts with the 2nd sector.
We'll see
 
Last edited by CTCaer,
sonds like it, yeah.
from factory, was exfat, I formatted it to fat32, then used windows 10 to format in exfat
 
@cherryduck
Please try the attached payload.
I added a print that shows a number in the format: "i: #"

EDIT:
Do you have big games installed into your sd card?

i: 1024

I only have Fast RMX and Snake Pass installed on the SD card atm, neither of which are huge.
 
i: 1024

I only have Fast RMX and Snake Pass installed on the SD card atm, neither of which are huge.
They are not huge but enough to draw out my conclusions:

Your exFAT partition was formatted wrongly and out of spec.
It misses the allocation bitmap entry (has info about which clusters are in use).
You can also see that from the "Free: 243797 MiB".

So better make a backup of your files and reformat it. And then copy back the nintendo folder and make sure that the "folder/file is ready for archiving" is not enabled.
Btw, currently homebrew has a limitation with the sd cards filesystems and cluster size. So before you copy your backed up files back check to see that hbmenu can show the contents of the switch folder.
 
They are not huge but enough to draw out my conclusions:

Your exFAT partition was formatted wrongly and out of spec.
It misses the allocation bitmap entry (has info about which clusters are in use).
You can also see that from the "Free: 243797 MiB".

So better make a backup of your files and reformat it. And then copy back the nintendo folder and make sure that the "folder/file is ready for archiving" is not enabled.
Btw, currently homebrew has a limitation with the sd cards filesystems and cluster size. So before you copy your backed up files back check to see that hbmenu can show the contents of the switch folder.

Will give that a shot, thanks. what cluster size should I be using?
 
Will give that a shot, thanks. what cluster size should I be using?
Users say that 32KB is fully compatible with homebrew, currently.
I can't say for sure though, because I have 100GB data in my sdxc sd card and I'm bored to try it.
So the options are:

  • exFAT with 32KB cluster size
  • FAT32 with 32KB cluster size
My recommendation though, is to try formatting it to exFAT through windows, with cluster size set to default allocation size (this will use 128KB probably).
Copy the switch folder, the sdfiles and the new hbmenu.nro back (as always disable the archive bit) and check if it shows your homebrews.
If not, format it in exFAT with 32KB cluster size and try again.


EDIT:
Never mind, I tripled checked with colleague's 128GB and 256GB sd cards formated with exFAT and 128KB cluster sizes. They worked perfectly (after disabling the archive bit).

So in the end the best formats are:
with exFAT switch micro update
less than 32GB:
  • FAT32 /w 32KB cluster size
32GB:
  • FAT32 /w 32KB cluster size
  • exFAT /w 128KB cluster size (this greatly improves performance)
64GB and up:
  • exFAT /w 128KB cluster size (this greatly improves performance)

without exFAT switch micro update
All sizes:
  • FAT32 /w 32KB cluster size
 
Last edited by CTCaer,
Users say that 32KB is fully compatible with homebrew, currently.
I can't say for sure though, because I have 100GB data in my sdxc sd card and I'm bored to try it.
So the options are:

  • exFAT with 32KB cluster size
  • FAT32 with 32KB cluster size
My recommendation though, is to try formatting it to exFAT through windows, with cluster size set to default allocation size (this will use 128KB probably).
Copy the switch folder, the sdfiles and the new hbmenu.nro back (as always disable the archive bit) and check if it shows your homebrews.
If not, format it in exFAT with 32KB cluster size and try again.


EDIT:
Never mind, I tripled checked with colleague's 128GB and 256GB sd cards formated with exFAT and 128KB cluster sizes. They worked perfectly (after disabling the archive bit).

So in the end the best formats are:
with exFAT switch micro update
less than 32GB:
  • FAT32 /w 32KB cluster size
32GB:
  • FAT32 /w 32KB cluster size
  • exFAT /w 128KB cluster size (this greatly improves performance)
64GB and up:
  • exFAT /w 128KB cluster size (this greatly improves performance)

without exFAT switch micro update
All sizes:
  • FAT32 /w 32KB cluster size

Yeah after a reformat with cluster size set to 128KB it worked perfectly, hbmenu shows my apps :) thanks for your time!
 
anyone know why i keep getting stuck at 8% ? Waited allmost an hour it just sits there ? 32gb class 10 real sandisk im pretty sure exfat
 

Site & Scene News

Popular threads in this forum