Hacking [RCM] hekate-ipl for 5.0.x + working hb menu

  • Thread starter Thread starter Deleted User
  • Start date Start date
  • Views Views 139,797
  • Replies Replies 359
  • Likes Likes 65
It is amazing what this Payload does. They could replace the file of "hbmenu.nro" for any .nro they want to try and execute it from the Photo Channel. There they will say if it is more compatible than launching it directly from the Homebrew.
 
It is amazing what this Payload does. They could replace the file of "hbmenu.nro" for any .nro they want to try and execute it from the Photo Channel. There they will say if it is more compatible than launching it directly from the Homebrew.
I know this won't work but for the sake of science why the hell not. I'll report back in five minutes.
edit: no it didn't work didn't think it would. It's the source code itself for the homebrew apps.
 
Last edited by Haztel,
@Jan4V
Upstream hekate already supports launching 5.x, along with the 1-4.x.
https://github.com/nwert/hekate/commit/8b9e65e76fc46ad1e56f01f1a8bda1dacd4de133

Can you rebase your repo to latest hekate and also upstream your extra differences/changes (e.g. patchset6)?

Please consider this, because having countless unlinked forks is not the best.
For example rajkosto, I and others upstream our fixes. And that means that everyone can enjoy and build on the version that has better sd card, partial dumping, raw dumpin, etc support.

By the way, upstream hekate included clearing of boot reason.
This is important to have, otherwise, Switch OS will know that you booted from RCM.
And because I believe most users here will use it on their online console, it may create problems/blacklisting from nintendo in the future.

Anyway, thanks for the release.
 
Thanks for the release.

But i'll wait for emunand support.

I'm quite sure that running HBL will leave some (detectable) traces in nand.
Therefore i prefer using (offline)emunand and leave sysnand untouched/stock.
 
By the way, upstream hekate included clearing of boot reason.
This is important to have, otherwise, Switch OS will know that you booted from RCM.
And because I believe most users here will use it on their online console, it may create problems/blacklisting from nintendo in the future.
This seems kinda important. Is there a log kept of multiple boot reasons or is it just a single value?
 
Incredible work. I am tempted to do this with my 4.1 but i will choose to wait patiently. I really like this as opposed to what i do on 3.0. A glimpse into the future of switch hacks def.
 
@Jan4V
Upstream hekate already supports launching 5.x, along with the 1-4.x.
https://github.com/nwert/hekate/commit/8b9e65e76fc46ad1e56f01f1a8bda1dacd4de133

Can you rebase your repo to latest hekate and also upstream your extra differences/changes (e.g. patchset6)?

Please consider this, because having countless unlinked forks is not the best.
For example rajkosto, I and others upstream our fixes. And that means that everyone can enjoy and build on the version that has better sd card, partial dumping, raw dumpin, etc support.

By the way, upstream hekate included clearing of boot reason.
This is important to have, otherwise, Switch OS will know that you booted from RCM.
And because I believe most users here will use it on their online console, it may create problems/blacklisting from nintendo in the future.

Anyway, thanks for the release.

There is no secmon patches for stuff other than 1.0/2.x in there + the keygen is wrong, atleast for 5.0.x.
But yes, I will definitely consider upstreaming these changes, especially after I make it work on 4.x.
 
I have a question about the rawnand dump. I'm using a 120 gb sd card but why stopped the dump at 89% with a text with "Done"? I have enough space and I got 12 parts (part 12 has 0 bytes) and together I got around 24 gb. Something went wrong I think. What can I do now?
 
I got this on 4.1.0

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

is not yet updated, when modified I will tutorial again
Sounds great. Is that something you are working on at the moment?
 

Attachments

  • 20180509_110015.jpg
    20180509_110015.jpg
    1 MB · Views: 521
I wonder what happens if we modify SciresM loader to relink rom:/ to sdmc:/ too and not only code:/ (which boots HBC main exe instead of Photo album main exe). Could we boot legit games that way ? (after extracting romfs and exefs obviously)
 
I wonder what happens if we modify SciresM loader to relink rom:/ to sdmc:/ too and not only code:/ (which boots HBC main exe instead of Photo album main exe). Could we boot legit games that way ? (after extracting romfs and exefs obviously)
Close but no cigar. Someone I know already does this but don't ask me who and how.
 

Site & Scene News

Popular threads in this forum