Auto RCM got me stuck in fatal error.

[kklaite]

Howdy. I just followed the rentry org tutorial for unlocking my switch. It said to turn On Auto-RCM in the Hekate menu. I just followed the tutorial and got to test the Atmosphere. As i entered the EmuNand, it gave me ''Unable to identify package1!''. I tried to turn off and reset the switch, but it keeps stuck in this screen as i have the Auto Rcm turned on.

Is there any way to get out of this?

 

[Hayato213]

What firmware is the emunand on?

 

[kklaite]

What firmware is the emunand on?

16.1.0

 

[linuxares]

hekate_ipl.ini - what does this include? Can you post what it say?

 

[kklaite]

hekate_ipl.ini - what does this include? Can you post what it say?

It Says:
''A fatal error occurred when running Fusee.
Unable to identify package1!

Press POWER to reboot.''

When i press the power button, it gets on the same screen, as i have the auto RCM On.

 

[linuxares]

hekate_ipl.ini on the sd card... it's in bootloader

 

[kklaite]

hekate_ipl.ini on the sd card... it's in bootloader

BRUH, i'll try getting it out.

 

[jeffyTheHomebrewer]

AutoRCM just makes your switch always boot into RCM, ready to accept an inject from a secondary device (PC, rooted Android device, etc) so I don't think this is a brick, but a misconfiguration.

 

[kklaite]

AutoRCM just makes your switch always boot into RCM, ready to accept an inject from a secondary device (PC, rooted Android device, etc) so I don't think this is a brick, but a misconfiguration.

Oh. Do you think is there any way of getting it out?

 

[linuxares]

Oh. Do you think is there any way of getting it out?

Depends on how it's configed or injected.


Why I asked for hekate_ipl.ini

 

[kklaite]

Depends on how it's configed or injected.


Why I asked for hekate_ipl.ini

Okay. This is the settings i used in hekate_ipl.ini


[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

 

[linuxares]

Okey so. It autoboot 0, which is [Atmosphere CFW]

It wait 3 seconds to do it.


I would download fusee.bin here - https://github.com/Atmosphere-NX/Atmosphere/releases (latest version of course)
and put it inside bootloader/payloads/



EDIT: You do boot Hekate first right?

 

[kklaite]

Okey so. It autoboot 0, which is [Atmosphere CFW]

It wait 3 seconds to do it.


I would download fusee.bin here - https://github.com/Atmosphere-NX/Atmosphere/releases (latest version of course)
and put it inside bootloader/payloads/



EDIT: You do boot Hekate first right?

I just did it, and it is stuck at the same error.

And yes, i did boot Hekate first.

 

[linuxares]

What happens if you try to boot the [Stock SysNAND]

 

[kklaite]

What happens if you try to boot the [Stock SysNAND]

I can't. When i press power to reboot, it gets back into the Atmosphere, getting stuck in a loop.

 

[linuxares]

hold down the power button for 15 sec, inject Hekate again.

 

[kklaite]

hold down the power button for 15 sec, inject Hekate again.

Got it. It did work.

Edit: Now i just have to make the Atmosphere to work lol

 

[linuxares]

to me it sounds like something is broken with the atmosphere files.

Normally fusee.bin should boot atmosphere.

Maybe try copy them over again?

 

[seith_typhon]

just in case you accidentally updated your switch. its 17.0 now and atmosphere is not updated yet.

 

[kklaite]

just in case you accidentally updated your switch. its 17.0 now and atmosphere is not updated yet.

Oh. Understood.