Hacking [RCM Payload] Hekate - CTCaer mod

[CTCaer]

It's incomplete. So try it with care. We still don't know everything about every data stored in BOOT0.

 

[Dmafra]

With 3.1 we will be able to move freely between any FW?

 

[CTCaer]

You can do that now.
But the verification is still not fixed.

 

[RAGER]

CTCaer, thx for your hard work! With 3.1 version I will finally start experimenting with my Switch!

 

[comput3rus3r]

If 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.

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

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.

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.

 

[:-infern:]

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.

Best way is to send it to Nintendo and get a repair. They'll likely update it though

 

[comput3rus3r]

Best way is to send it to Nintendo and get a repair. They'll likely update it though

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.

 

[Pittek]

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

 

[Dmafra]

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

You can restore the first backup and if it did not work you can restore the second backup withou problem!
Keep in mind that you need the rawnand.bin and boot 0/1

 

[Azel]

I did a restore with hekate 2.1 and it worked. (did a backup with 3.0 before just in case)

 

[Pittek]

Amazing, thx!

I thought it would be smart to do a backup on a "virgin" console to be safe, it seems this could pay out one day
Not that it does matter, I still have my original untouched Switch with my bought games and original account. I bought this second one just for fooling around, its offline since the initial setup and update to 5.1 and ExFat-patch. So I couldnt care less if it gets banned

Btw, you have an awesome community here, kudos!

 

[CTCaer]

As I said, before doing a restore, better wait for v3.1.

The commits are already up. So if everything goes well (the results from testers), I'll release today.

 

[Spunky247]

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?

Today i used a 64 GB exfat micro SD and the dump worked perfectly. Didnt recognise that i just could use an exfat SD. Thought i would need the exfat driver to be installed before *shame on me*

Took about 80 mins to dump and verify.

 

[Deleted_444986]

hekate 3.1 (based from last commits)

 

[CTCaer]

hekate 3.1 (based from last commits)

-.-

It's not gold yet. Not even RC.

 

[sweetlilmre]

hekate 3.1 (based from last commits)

That is a real dick move.

-(e)

 

[Deleted_444986]

-.-

It's not gold yet. Not even RC.

so it's not really 3.1 ?

 

[sirAnger]

There may be bugs in there. Even if there aren't, CTCaer may some code cleanup and documentation to do. It's open source so you can compile and distribute as you like but advertising it as 3.1 is very misleading.

 

[soaresden]

• 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.

Just some precision on bootlogo :

1- Have to be 720 x 1080 pixels and rotated
(the head of your image must be on the left and the bottom at right)
2- the file must be named as "bootlogo.bmp"
3- the file must be edited as a RVBA bmp
4 - the launch option must be on autoboot

Here I share the bootlogo i edited
Hope you enjoy

 

[tecfreak]

@soaresden
1-4: not correct. read the manual again.

 

[adrifcastr]

If we could flash hekate to that damn tx dongle, it'll be actual useful to pay for that thing, tbh I'd love to have a multifunctional bootloader like hekate being even more portable than just w/ a phone