Using sxos emunand with hekate

+1 hekate atm can't see it and the migrate option doesn't work either

 

Actually the migrate option was working and was pretty smooth.
After that I just launched EmuNAND CFW from Hekate 5.0.0 and took a while.
I had sd files so yea that was slow but i could wait a minute or 2.
And I could easily play game (NSP's).
Loading times are like 1-2 mins which shouldnt be much of a problem since EmuMMC is still being developed on with many bugs. (Which I havent encountered atm)

 

I have found a way for hekate to use emunand made by sxos its the same as when it was when it was in testing stage.

1. I recreated the emunand using hekate but discovered that sxos bootloader couldn't see the emunannd so you won't be able to use sxos with it. (When you think about it it make senses since sxos is looking at start of drive not the end)
2. I delete the emunand and recreated the emunand using sxos again
3. Remembering how it was config in the testing stage I change the start sector to "0x2"
4. Profit

If you want to avoid steps 1-2 i ve uploaded premade Emummc folder

Download

 

I thought hekate wasn't compatible with unallocated space?

 

I just change the starting sector in the config and it found it

 

Yeah, it worked for me to. I think pyx just can't make EmuMMC on unallocated space.

 

EDIT: wait... that's not right. Why is the Nintendo path in your .ini pointing there? It should be

Code:

[emummc]
enabled = 1
sector = 0x2
nintendo_path = Emutendo

 

Yes that's right that would make atmos use the same folder as the one created sxos

 

will this method work if sx emunand is stored in SD?

 

It'll work no matter where it is stored.