Hacking [RCM Payload] Hekate - CTCaer mod

  • Thread starter Thread starter CTCaer
  • Start date Start date
  • Views Views 1,197,567
  • Replies Replies 3,331
  • Likes Likes 128
What is left todo for 3.0.1/3.0.2 support?

You misunderstood.

To develop the patches, I need to reverse engineer nintendo's code first. It's the opposite of compiling. And then I can compile a new hekate version.
Anyway, I can't do that with damn IDA pro crashing on me.


On the other hand, I've implemented a 16px font (original text is 8px).
But it breaks all long text, because now the limit is 45 characters (from 90).
It will take a while because I have to fix:
2b0hw8.jpg



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



That's absolutely correct.

Maybe, I'll do a new installation in a VM. But still, I don't want to find the correct variables all over again..
 
  • Like
Reactions: :-infern:
Why do we need a fork for this (as far as i understand only parting was added) ? A PR would have done the job or am i missing something?
 
CTCaer has been actively developing more functions and has been doing the PR upstream.
I don't see a problem having a fork for new/testing features

That is the reason why i am asking. I saw his activity in the Ipl repo. Just affraid of the countless endusers getting confused and making Threads asking which Tool to use. + imho more forks = more overhead = less Output.

I wouldn‘t call it Problem though
 
Last edited by Digital_0xFF,
As @Dread_Pirate_PJ said.

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

Need 2-3 ppl with 3.0.1 or 3.0.2 to test.
You need to know what to do and have the sd card ready with the files from the sdfiles.zip.

The first 2-3 that will reply will get a PM.
 
Last edited by CTCaer,
So we have our first success with 3.0.1/3.0.2.

If everything goes well and there are more successes, a release that supports firmware launching in every firmware will be imminent.
You're doing God's work, my friend.
 
So we have our first success with 3.0.1/3.0.2.

If everything goes well and there are more successes, a release that supports firmware launching in every firmware will be imminent.

you are a god.
I will look forward to on 3.0.1.
 
While my other SD is still "at the shop", I've got another 32gb card and dump is underway. Thanks for your work!

EDIT: Failed afer 77% (2329 sec.) with:

[FatFS] Error: Write - Low level disk I/O!
Fatal Error (1) when writing to SD Card​

On a fresh, unused card (formatted to exFat on Windows 10). Man, I just keep being out of luck.. :sad:
 
Last edited by Ohex4455,
While my other SD is still "at the shop", I've got another 32gb card and dump is underway. Thanks for your work!
...
On a fresh, unused card (formatted to exFat on Windows 10). Man, I just keep being out of luck.. :sad:

Same here.
I have solved formatting my 128gb sdcard in exfat slowly (not quick format, this take a lot of time) and then dumped all successfully. When finished and moved the dumps on PC I have reformatted in fat32 with a tool founded here (quick format at this time).
 
  • Like
Reactions: Ohex4455
Same here.
I have solved formatting my 128gb sdcard in exfat slowly (not quick format, this take a lot of time) and then dumped all successfully. When finished and moved the dumps on PC I have reformatted in fat32 with a tool founded here (quick format at this time).
Thanks for your input. I've reformatted it, did an error-check and literally a minute ago the second run went through perfectly :).
 
  • Like
Reactions: cicciopas
If you want to be sure, you should dump the NAND at least twice WITHOUT BOOTING THE OS, and then compare the hashes. It takes a lot of time, but it's better to be safe than sorry
 
  • Like
Reactions: Ohex4455
If you want to be sure, you should dump the NAND at least twice WITHOUT BOOTING THE OS, and then compare the hashes. It takes a lot of time, but it's better to be safe than sorry
Already happening, thanks ;) Read it somewhere else (5-6 actually :huh:... don't know if that's neccessary).
 
Last edited by Ohex4455,

Site & Scene News

Popular threads in this forum