Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[impeeza]

Hekate is a bootloader replacement, Atmosphere have his own bootloader.

Hekate have a lots of benefices and extra features than the Atmosphère bootloader.

for now use Hekate as test to the injection and preboot environment.

 

[FirM]

Hekate is a bootloader replacement, Atmosphere have his own bootloader.

Hekate have a lots of benefices and extra features than the Atmosphère bootloader.

for now use Hekate as test to the injection and preboot environment.

Ok, I started over, and Hekate won't launch. Same black screen in RCM mode, with the correct Hekate payload added the the RCMLoader.

Everything works totally fine if I revert to my previous Atmos setup, but I want to move up to OFW 15.0.0, and see zero reason why I shouldn't be able to. Why is Switch hacking so goddamn clunky and inconsistent? I have had an issue literally every single time I move up to a new version. If it's not one thing, it's something else...

 

[impeeza]

that's is weird, with bootloader on you SD card and Hekate payload on your injector, and VOL- pressed you should get in to NYX, may be you AutoRCM get disabled, put the Jig on the right rail and try again.

 

[FirM]

that's is weird, with bootloader on you SD card and Hekate payload on your injector, and VOL- pressed you should get in to NYX, may be you AutoRCM get disabled, put the Jig on the right rail and try again.

It's super weird! Oh, and I don't use AutoRCM, so I'm holding POW and VOL+ (because I always thought it was VOL+, and that's always worked for me). I tried it again with VOL-, no dice.

Why would Atmos work fine in the past, but not now all of a sudden?

 

[impeeza]

hum you need to put the jig on the right rail, pres VOL+ and power and then release and quickly press VOL-

 

[FirM]

Huh, I just tried that and got the same result. I tried the same things I've tried before a few times too, just to see if I missed something or messed up - no improvement.

Oh, and I tried booting with a card I still had the old setup on (previous atmos), and now that gets the black screen too. So whatever I did retroactively broke what used to work fine before.
Did I somehow break the RCM loader or something? Is the 1.4.0 fusee incompatible with the previous version? Because I didn't bother switching the Loader back to the old Fusee, I just grabbed the new Fusee, and replaced the Hekate I put there a few minutes ago for testing. Presumably I was using the "old" Fusee to launch before, but I doubt that matters much.

Edit - If I stock launch the system, it boots fine. It's not like, BROKEN broken.

 

[impeeza]

and if you inject tegra explorer?

Post automatically merged: Oct 26, 2022

if you have a windows computer try to inject using TegraRCM, or Rekado on a Android phone.

 

[FirM]

and if you inject tegra explorer?

Post automatically merged: Oct 26, 2022

if you have a windows computer try to inject using TegraRCM, or Rekado on a Android phone.

Ok, "solved" it! I actually happen to own more than one RCM Loader device, so I swapped to a different one, and tried everything again, and it all works perfectly now. I noticed that this Loader only lights up for like half a second before Atmos boots, while the other would stay lit up for like 3+ seconds before Atmos would come up (before it stopped working at all, apparently). Trying TegraRCM would have revealed the same result, so that was great advice, thanks! I just wish I understood why this particular Loader failed all of a sudden (despite it still lighting up). Ah well!

 

[jurai]

Ok, I started over, and Hekate won't launch. Same black screen in RCM mode, with the correct Hekate payload added the the RCMLoader.

Everything works totally fine if I revert to my previous Atmos setup, but I want to move up to OFW 15.0.0, and see zero reason why I shouldn't be able to. Why is Switch hacking so goddamn clunky and inconsistent? I have had an issue literally every single time I move up to a new version. If it's not one thing, it's something else...

Feel free to make your own update solution

 

[impeeza]

Ok, "solved" it! I actually happen to own more than one RCM Loader device, so I swapped to a different one, and tried everything again, and it all works perfectly now. I noticed that this Loader only lights up for like half a second before Atmos boots, while the other would stay lit up for like 3+ seconds before Atmos would come up (before it stopped working at all, apparently). Trying TegraRCM would have revealed the same result, so that was great advice, thanks! I just wish I understood why this particular Loader failed all of a sudden (despite it still lighting up). Ah well!

Your rcm loader has a low battery. Try to charge on any usb charger or port for about 1 hour, until white led stay on, using the micro sd cable

 

[vinson77]

There has been a couple of users who reported that dongles doesn't work anymore. But as soon as they have used the TegraRCM app... The console booted perfectly.

 

[hippy dave]

There has been a couple of users who reported that dongles doesn't work anymore. But as soon as they have used the TegraRCM app... The console booted perfectly.

Probably outdated payload on the dongles?

 

[impeeza]

Probably outdated payload on the dongles?

The RCMLoader "V2" ORIGINAL have a problem injecting Hekate 5.6.0 and newer payloads, and need the firmware 2.02 update, can be obtained from https://www.xkit.xyz/support/

But all the Chinese clones allegedly V5 what you can buy on aliexpress do not have the problem and you CAN NOT install the original firmware on it, you can brick it with the new firmware or even if you format the internal USB drive.

If the problem persist you can use ArgonNX (https://github.com/Storm21CH/ArgonNX-SE or https://gbatemp.net/threads/argonnx-se-payload-with-mariko-and-aula-oled-support.581956/) payload and setup to autoboot Hekate, the additional bonus is you will never need to update your injector dongle, only update the payload.bin file ON YOUR SD CARD and voílá!

 

[binkinator]

The RCMLoader "V2" ORIGINAL have a problem injecting Hekate 5.6.0 and newer payloads, and need the firmware 2.02 update, can be obtained from https://www.xkit.xyz/support/

But all the Chinese clones allegedly V5 what you can buy on aliexpress do not have the problem and you CAN NOT install the original firmware on it, you can brick it with the new firmware or even if you format the internal USB drive.

If the problem persist you can use ArgonNX (https://github.com/Storm21CH/ArgonNX-SE or https://gbatemp.net/threads/argonnx-se-payload-with-mariko-and-aula-oled-support.581956/) payload and setup to autoboot Hekate, the additional bonus is you will never need to update your injector dongle, only update the payload.bin file ON YOUR SD CARD and voílá!

Argon-NX is precisely what I use on mine. Dongle updates are now a thing of the past!

 

[Gep_Etto]

Oh WAIT, I always need Hekate too? I always thought it was Hekate OR Atmos, so I cut out Hekate to be efficient.

You can boot directly to Atmosphère or you can boot into Hekate and then load Atmosphère through Hekate. IMO using Hekate is better, since you can do things like set AutoRCM, choose between emuNAND and sysNAND, dump certain partitions for backup, load other payloads like LockpickRCM, etc.

 

[linuxares]

You can boot directly to Atmosphère or you can boot into Hekate and then load Atmosphère through Hekate. IMO using Hekate is better, since you can do things like set AutoRCM, choose between emuNAND and sysNAND, dump certain partitions for backup, load other payloads like LockpickRCM, etc.

That's how I boot Atmosphere. I also boot proper Atmosphere via Hekate and not fss0.

 

[ShadowOne333]

The RCMLoader "V2" ORIGINAL have a problem injecting Hekate 5.6.0 and newer payloads, and need the firmware 2.02 update, can be obtained from https://www.xkit.xyz/support/

But all the Chinese clones allegedly V5 what you can buy on aliexpress do not have the problem and you CAN NOT install the original firmware on it, you can brick it with the new firmware or even if you format the internal USB drive.

If the problem persist you can use ArgonNX (https://github.com/Storm21CH/ArgonNX-SE or https://gbatemp.net/threads/argonnx-se-payload-with-mariko-and-aula-oled-support.581956/) payload and setup to autoboot Hekate, the additional bonus is you will never need to update your injector dongle, only update the payload.bin file ON YOUR SD CARD and voílá!

I remember there were some discrepancies between the RCMLoader with white box and one with the transparent box, do we have a way to verify which one we have?
I own one and will update it, but I want to be sure I have the correct one so I don't brick it.

 

[impeeza]

I remember there were some discrepancies between the RCMLoader with white box and one with the transparent box, do we have a way to verify which one we have?
I own one and will update it, but I want to be sure I have the correct one so I don't brick it.

There is a way, when you connect the dongle to computer using micro USB cable on the windows device manager you can see:

the devices:

The name of the USB Mass Storage Device is a clue, RCMLoader One is the plastic transparent one, RCM Loader ONE Plus is the white cardboard one (and the Chinese clone)
and on the details of driver, on the Device path you can see the firmware version of the RCM Injector

 

[ShadowOne333]

There is a way, when you connect the dongle to computer using micro USB cable on the windows device manager you can see:

the devices:
View attachment 334248
View attachment 334250
The name of the USB Mass Storage Device is a clue, RCMLoader One is the plastic transparent one, RCM Loader ONE Plus is the white cardboard one (and the Chinese clone)
and on the details of driver, on the Device path you can see the firmware version of the RCM Injector
View attachment 334247

View attachment 334246

Oh man that's amazing info to have, thank you for this.
I should be able to properly update the RCMLoader firmware now once I get home in the afternoon

 

[austinshea]

thank you for your work!