Hekate don't boot OFW 6.0.1

[UdoChudo]

So, next problem. When try boot to OFW 6.0.1 through Hekate 5.0 it just return me on RCM mode OFW 6.0.1 Hekate 5.0 EmuMMC 6.0.1 SD Card Fat32 partition for games

Hekate_ipl.ini

[config] autoboot=1 autoboot_list=0 bootwait=3 customlogo=1 verification=2 backlight=40 autohosoff=0 logopath=bootloader/bootlogo.bmp { } [Atmosphere] payload=bootloader/payloads/fusee-primary.bin { } [Stock 6.2.0 and lower] stock=1 emummc_force_disable=1 { }

[CTCaer]

Hmm I'll need to investigate that. Did it work in 4.10.1?

[Slluxx]

Same for me with a completly clean 6.1 system

[bbatod]

Yeah, I encountered an issue with 6.2 as well. Switch FW 6.2 + Atmosphere 0.9.2 + Hekate 5.0 and just gets stuck on boot for me.

[ultra-azu]

For me, if I use fusee-primary.bin(while pretty slow due to me using File-based EmuMMC) it boots into EmuMMC(6.2 btw), so you guys can use that as a workaround.

[bbatod]

For me, if I use fusee-primary.bin(while pretty slow due to me using File-based EmuMMC) it boots into EmuMMC(6.2 btw), so you guys can use that as a workaround.

I did not even setup emuMMC, I was just trying to boot into CFW on 6.2 with Atmosphere 0.9.2 and Hekate 5.0. Reverting back everything to Atmosphere 0.8.9 and Hekate 4.10.1. fixed it.

[ultra-azu]

For me it looks like, EmuMMC or no EmuMMC, 6.*(and potentially lower) doesn't work.

In my case my SysMMC is on 8.0.1 so I'll stick with hekate 5.0.0 until then.

[UdoChudo]

For me it looks like, EmuMMC or no EmuMMC, 6.*(and potentially lower) doesn't work.

In my case my SysMMC is on 8.0.1 so I'll stick with hekate 5.0.0 until then.

on SysNand 4.1.0 emuMMC with Hekate 5.0 and Atmo 9.2 working good. Don't tested 5.0.1 FW but i think it will work too. Problem in 6.X only but not sure

[CTCaer]

So hekate 4.10.1 + atmo 0.9.2 (or lower) works with 6.x?

[ultra-azu]

Yep, and latest fusee-primary works fine too.

[CTCaer]

Good, I might pinpoint it then.

[CTCaer]

Various stuff were fixed. I have a build in retronx discord. Please check.

BTW, Atmosphere 0.9.2 removed 6.2.0 keygen from exosphere. So I had to add it to hekate.

[ultra-azu]

Will try it ASAP.

[ultra-azu]

It may be me only, but while I don't get stuck on splash screen now, when I boot with Hekate in Stock to 6.2.0, after the splash I get a black screen. The system is rebooting to RCM(I proved it by connecting my phone while it rebooted. It booted back to hekate).

For curiosity, I decided to try CFW to see if it would boot, and it got past the Nintendo Switch logo, but after that Atmosphere gave me an error with code 2002-4686. The title points to the ns module, according to SwitchBrew.

[CTCaer]

That error is probably the NS patching for emuMMC.

Do you by any chance run stock with emuMMC? This is not supported, as it needs a fix on m4's emuMMC

[ultra-azu]

I used to, but I switched to OFW SysMMC(6.2.0 for now) and CFW emuMMC(8.0.1). I don't have any problems with emuMMC, this is in sysMMC. I ran Atmosphere in 6.2 because I thought it could give us a clue. Sorry if I didn't make it clear(English isn't my primary language).

[CTCaer]

6.2.0 was fixed internally.

But I'm quite curious about 6.1.0/6.0.x. I wonder if the problem is the debug fix patches.

To test that, I'll need someone that really is on 6.x that is not 6.2 and want's to test stock with no emuMMC. (As I said before emuMMC with stock doesn't work and will be removed until fixed. It will throw an error for that purpose.)

[ultra-azu]

I know you want people lower than 6.2, but it may not be working at all. Like I mentioned in one of my comments, booting 6.2 on Stock in sysMMC redirects to RCM. Doing the same, but with CFW goes fine until the ns error(the same goes to fusee-primary). Sorry if I'm being stubborn, it's just that it may not be fixed yet(and at the same time I'm worried that my backup may be corrupted). Although it would be great to see if someone else has the same issues as me.

[CTCaer]

Can you show me your ini which boots to Stock 6.2?

[ultra-azu]

Sure(I renamed it to a .txt file since Github doesn't accept inis. hekate_ipl.ini.txt

[ultra-azu]

Well crap, I accidentally disabled autoRCM and now I don't have hekate.

Good news though, it isn't hekate. My switch threw the same error it threw with Atmosphere. Any ideas on what should I do?

[CTCaer]

Your stock option run emuMMC. Which is not working. You need to use

[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

[ultra-azu]

Well, I'll try once my jig arrives(which according to Ebay, in 10 days).

Still, I know this isn't related to hekate, but why does booting without hekate to Stock throw the same error as with Atmosphere? Is my backup screwed up?

[CTCaer]

dunno what error is that (you didn't provide the whole error code. or how you upgraded to there)

[ultra-azu]

I meant the error that pointed to the ns module. It's the same error code(2002-4686), although I don't know if it's the same module from last error, due to Stock's limited error message. This is now happening on Stock without hekate(because I accidentally disabled autoRCM).

[CTCaer]

FS: Invalid FAT format for BIS User partition.

It's not NS

[ultra-azu]

Well, that's a start. Do you know how I can fix this?

[CTCaer]

It has to do with your USER partition. You probably did sth that you shouldn't have.

The reason emuMMC also has that, is that you used the same problematic sysnand to make it. So that's why both have it

[ultra-azu]

I don't care if I lose my saves in sysMMC since I already backed them up. I should boot into Recovery Mode and there I should reinitialize the console, correct? I think it happened because for EmuMMC I cloned my 8.0.1 installation to it, and then restored 6.2 in sysMMC. AFAIK if the downgrade is too low sometimes the saves won't work, which I think it's what happened here.

Also, when I had a way to access RCM(autoRCM) my emuMMC worked completely, and probably will once my jig arrives. Just wanted to clarify that.

Anyway, thanks for everything(and btw thanks for your work for emuMMC)!

[ultra-azu]

Well, the initializing provides the same error. I'm gonna ask on reddit in order to keep this more on-topic

[CTCaer]

https://github.com/CTCaer/hekate/commit/0862cb1e7e7b9d9a46edebd55436762ac45c8801