Hacking RCM loader not booting latest atmosphere

[Hayato213]

Tried a few different SD cards. Anyone have the latest atmosphere working with and RCMloader?

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.

 

[proconsule54]

i am planning to update update the switch to last atmo and so i'll try it and let you know

 

[proconsule54]

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

 

[viper3344]

GOT IT WORKING!!! Ok it was outdated files from sdsetup.com.....

Sorry for the long thread guys. I can now boot into Atmosphere just fine. Thanks!

 

[The Real Jdbye]

Atmosphere 1.0 doesn't use Fusee Secondary anymore. That's probably the issue.

I think he's trying to use Fusee Primary directly.

JUST tried it!

Hekate works just fine! But I cant get any fusee payload to work. The TegraRcmGUI says its injected but the switch only has a black screen.

Looks like its an RCMloader issue.... Either way, still cant get atmosphere to work. SXOS was so easy.... Atmosphere not so much...

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.

 

[impeeza]

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.

 

[viper3344]

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.

Exactly! All good advise! Now for my sigpatches... can I just use the AIO switch updator?

 

[impeeza]

AIO Switch Updater, generally is capable to download the latest version of sigpatches from the repository, it hast been safe for updating the sigpatches.

 

[Hayato213]

Minor issue with AIO would be you might ran into the case atmosphere won't boot after updating, so you end up doing it manually. Beside that I don't think there are problem with it.

 

[viper3344]

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.

 

[Draxzelex]

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.

Just use Hekate to boot Atmosphere instead.