Hacking Fusee Gelee: All the payloads

  • Thread starter Thread starter Deleted-442439
  • Start date Start date
  • Views Views 195,788
  • Replies Replies 68
  • Likes Likes 37
D

Deleted-442439

Guest
Thought it would be useful to have a thread with a collection of everything that can be used on Fusee Gelee / RCM exploits

message edited by a moderator.

The payload injectors and binaries are now listed on Wikitemp.
https://wiki.gbatemp.net/wiki/List_of_Switch_payloads



If you know any missing payload or tool, you can add it or post here and someone with wiki access will update the list.


Launchers:

Fusee Launcher:
https://t.co/UGqtMeHR13


Payloads:


Sample payload: https://t.co/d5nCLNa7E5

shofEL2: https://github.com/fail0verflow/shofel2

Fuse Dump https://github.com/moriczgergo/fusedump

GRAnimated's info payload: https://github.com/GRAnimated/FG-CustomPayload/


Key dumper: https://github.com/rajkosto/biskeydump

hekate_ipl source: https://github.com/nwert/hekate (binaries: https://github.com/rajkosto/hekate/releases)

Custom Firmware (CFW)

Atmosphere: https://github.com/Atmosphere-NX/Atmosphere
Note: Only for devs


Other resources:

Linux resources: https://fail0verflow.com/blog/2018/shofel2/
Note: This is also NOT for the end user.

The thread will be updated as more payloads are released.
 
Last edited by Cyan,
The bootrom is read-only, you can't write anything to it.

Without access to NAND/eMMC drivers(with write abilities) you can't write anything to it.
 
The bootrom is read-only, you can't write anything to it.

Without access to NAND/eMMC drivers(with write abilities) you can't write anything to it.

i think on rcm we could with linux write to the consoles emmc but that would be dangerous
 
i think on rcm we could with linux write to the consoles emmc but that would be dangerous

Why do that anyways, emunand is much better and less risky, the tools we have now are to unstable, would not risk it.
 
Last edited by Crazy-S,
We need a payload to dump and restore our saves
How to do that?

  1. Place your own tsec fw as a C hex array or escaped string into the file src/hwinit/tsecfw.inl

You have to dump your TSEC (Tegra Security Co-processor) firmware with total size 3840 bytes (get it from your pkg1ldr.bin (at offset 0x00001900) or boot0.bin (at offset 0x00101900), and place it as a C hex array in src/hwinit/tsecfw.inl :unsure:
 
Great. Thank you. Keep ´em coming. All I want is to reach the end of the tunnel and, have a CFW, and a decent, great list of apps / payloads. I want one to dump / inject saves, and maybe convert the ones from Wii U games to their Switch counterpart the easy way. (Apart from emulating my favorite consoles) Waiting patiently.... Very... very insanely... but patiently...
 
You have to dump your TSEC (Tegra Security Co-processor) firmware with total size 3840 bytes (get it from your pkg1ldr.bin (at offset 0x00001900) or boot0.bin (at offset 0x00101900), and place it as a C hex array in src/hwinit/tsecfw.inl :unsure:

Who can i find pkg1ldr.bin or boot0bin?
 

Site & Scene News

Popular threads in this forum