It doesn't have to do with the payload dongle if you inject from a computer and still blank screen, then problem is your NAND.
It doesn't have to do with the payload dongle if you inject from a computer and still blank screen, then problem is your NAND.
I can confirm working with RCM Loader ONE.
Atmosphere 1.0.0
HOS 12.1.0
copied fusee.bin to payload.bin in ATMOSPHERE_HEKATE dir
Atmosphere 1.0.0
HOS 12.1.0
copied fusee.bin to payload.bin in ATMOSPHERE_HEKATE dir
I think he's trying to use Fusee Primary directly.
Hekate works, did you try to chainload fusee-primary from it?
You can set up a boot entry to autoboot fusee-primary when you load Hekate later but for now you can use the "Payloads" menu to manually select fuee-primary.
Edit: Oh, I see the problem was fixed. My fault for not bothering to read the second page.
I am owner of a RCMLoader One first version, and can load either Hekate 5.5.6, Atomosphère 1.0.0 (latest) injecting Hekate and FUSE.BIN payloads respectively, you must be careful to rename payload.bin and put on a folder on the RCMLoader, and pressing the button change the corresponding color-folder. I also use the RCMLoader to inject TegraExplorer 4.0.0 and LOCKPICK_RCM_1_9_4 with no problem at all.
you should try to update all your homebrew by hand an download the latests releases from his repository. As I note your problem was a outdated injector/SD Files combination.
the same goes to the sigpatches if you use it, update it manually.
I am not against the prepacked setups but sometimes they aren't updated to latest files and the result is only works with exactly the combination of CWF and Homebrew they was created, and if you update only a component can get inconsistencies for others pieces of software.
you should try to update all your homebrew by hand an download the latests releases from his repository. As I note your problem was a outdated injector/SD Files combination.
the same goes to the sigpatches if you use it, update it manually.
I am not against the prepacked setups but sometimes they aren't updated to latest files and the result is only works with exactly the combination of CWF and Homebrew they was created, and if you update only a component can get inconsistencies for others pieces of software.
AIO Switch Updater, generally is capable to download the latest version of sigpatches from the repository, it hast been safe for updating the sigpatches.
Still piecing the puzzle together here. So after I use Hekate to create an emunand, how do you use the fusee payload to boot into the emunand? I would prefer (per mikefor20's recommendation) to use fusee as its paired with Atmosphere but since 1.0, they changed some things. (There are no more bins in the atmos folder other than reboot_payload.bin)
I still have to set up my emunand still but the switch is STRICTLY offline.
I still have to set up my emunand still but the switch is STRICTLY offline.
Last edited by viper3344,
Similar threads
- Solved
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer". -
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Mame should be two sets one for preservation of everything and one set for people who just want to play and enjoy the old old ganes -
-
-
-
@
SylverReZ:
@Psionic Roshambo, Believe Japan was going to make it legal at some point, according to a Kotaku story.+1
-
@
Psionic Roshambo:
I swear like 99% of arcade games wouldn't even exist these days outside of MAME the arcade machines are old and busted very few ever saw any sort of home conversion
-
-
@
SylverReZ:
@Psionic Roshambo, There's a lot of obscure Japanese arcade titles that are either lost to time or dumped.+1
-
-
@
Psionic Roshambo:
I mean if a company could use AI to do the work of a home conversion for essentially free why not? The rights for some games are completely lost though
-
-
-
-
-
-
