Thanks, I managed to get android up and running no problem. I'll do more research next time lol
@CTCaer , Could you show the "nyx_ver + expected_nyx_ver" value for the error message?
I always get that error and I don't know which part should I update.
I don't know I need to update my payload.bin or update the "bootloader" folder?
If you can show the version, It would be more clear.
(For the normal usage, I can update both to solve this problem, I just want to know the version differences in the error message.
)if (nyx_ver < expected_nyx_ver)
{
h_cfg.errors |= ERR_SYSOLD_NYX;
gfx_con_setpos(0, 0);
WPRINTF("Old Nyx GUI found! There will be dragons!\n");
WPRINTF("\nUpdate the bootloader folder!\n\n");
WPRINTF("Press any key...");
msleep(1000);
btn_wait();
}
@CTCaer, any thoughts how I can get rawnand.bin.05 to dump and complete my nand backup?
I am trying to make nand backup, but when I dump eMMC raw using hekate 5.5.3 I get an error. I have partial nand dump with all rawnand.bin.xx files except rawnand.bin.05. When I set partial.idx file to 0x05 to resume the dump, only rawnand.bin.05 fails with this error every time:
error reading 8192 blocks @ LBA 01478000, from eMMC (try 1). Retrying...
error reading 8192 blocks @ LBA 01478000, from eMMC (try 2). Retrying...
error reading 8192 blocks @ LBA 01478000, from eMMC (try 3). Aborting...
please try again...
Failed!
I am trying to make nand backup, but when I dump eMMC raw using hekate 5.5.3 I get an error. I have partial nand dump with all rawnand.bin.xx files except rawnand.bin.05. When I set partial.idx file to 0x05 to resume the dump, only rawnand.bin.05 fails with this error every time:
error reading 8192 blocks @ LBA 01478000, from eMMC (try 1). Retrying...
error reading 8192 blocks @ LBA 01478000, from eMMC (try 2). Retrying...
error reading 8192 blocks @ LBA 01478000, from eMMC (try 3). Aborting...
please try again...
Failed!
I have been at this for a few days and not really having much luck. I want to dual boot both atmosphere and SXOS but use the same emunand from SXOS. THIS IS FILE BASED. Sorry, but every discussion I have seen reverts to partition based and this is NOT what I m looking for. I have tried using emummc.ini that looks like this:
[emummc]
enabled=1
path=sxos/emunand
id=0x0000
nintendo_path=emutendo
and many variations of this with leading / in the paths,, changing id=, removing id=, just about everything I can think of. Hekate doesn't ever recognize it.
I can choose the migrate emunand option which then moves all of the files from /sxos/emunand to emummc\EF00\eMMC and renames them and creates emummc.ini like this:
[emummc]
enabled=1
sector=0x0
path=emuMMC/EF00
id=0x0000
nintendo_path=emuMMC/EF00/Nintendo
and it boots CFW emunand but this breaks SXOS since the files have moved. Afterwords, the previous things that were installed in SXOS do look like they are all still there but nothing will launch so there appears to be something else I am missing with the migrate method. What do I need to do to get hekate to be able to boot atmoshere using the emunand from sxos and it's Emutendo folder WITHOUT altering the SXOS setup so it will still boot, thus sharing the same files between both? Remember, file based, NOT partition based.
[emummc]
enabled=1
path=sxos/emunand
id=0x0000
nintendo_path=emutendo
and many variations of this with leading / in the paths,, changing id=, removing id=, just about everything I can think of. Hekate doesn't ever recognize it.
I can choose the migrate emunand option which then moves all of the files from /sxos/emunand to emummc\EF00\eMMC and renames them and creates emummc.ini like this:
[emummc]
enabled=1
sector=0x0
path=emuMMC/EF00
id=0x0000
nintendo_path=emuMMC/EF00/Nintendo
and it boots CFW emunand but this breaks SXOS since the files have moved. Afterwords, the previous things that were installed in SXOS do look like they are all still there but nothing will launch so there appears to be something else I am missing with the migrate method. What do I need to do to get hekate to be able to boot atmoshere using the emunand from sxos and it's Emutendo folder WITHOUT altering the SXOS setup so it will still boot, thus sharing the same files between both? Remember, file based, NOT partition based.
Mostly because it is easier to make backups of the sdcard in case something goes wrong. Also easier to transfer to another card or similar functions. With a good sdcard, I haven't had performance issues at all.
Last edited by swspjcd,
NxNand Manager is a very good tool that allows you to easily do backup/restore (and more) , that’s the one I use and never had issues, and therefore very easy to have dual boot using Atmosphere and Sxos.
I’ve been using dual boot for over 3 years, and never felt more difficult to backup my sd card (or transfer to another sd card) with Partition based emunand. The other good thing about Partition based emunand is that you can have more than 1 emunand or rezise it to suit your wills.
Last edited by Maupiti,
After days and days of trying to get file based sharing to work dual booting between sxos and atmosphere, I just don't think it is possible. Everytime I bring it up, everyone starts talking about how they are doing it via partition but not file based. I have asked for examples from different forums where several people say they are doing it, but noone can actually share their emummc.ini from a working system where they dual boot file based emunands. I have tried about every combination of options in emummc.ini that I can think of and found from others examples. You would think it should be as simple as this:
[emummc]
enabled=1
id=0x0000
path=sxos/emunand
nintendo_path=Emutendo
but this still wont boot. I have edited and redited the emummc.ini over and over. Nothing works. I can successfully use the migrate option in Hekate but it moves and renames the files from sxos/emunand which breaks sxos. I am very skeptical anyone is actually successfully doing file based dual boot between atmosphere and sxos where the share the same emunand and emutendo files/folders.
[emummc]
enabled=1
id=0x0000
path=sxos/emunand
nintendo_path=Emutendo
but this still wont boot. I have edited and redited the emummc.ini over and over. Nothing works. I can successfully use the migrate option in Hekate but it moves and renames the files from sxos/emunand which breaks sxos. I am very skeptical anyone is actually successfully doing file based dual boot between atmosphere and sxos where the share the same emunand and emutendo files/folders.
Well, sorry, I can’t help you with that..So.., maybe you should give a try to Partition based emunand and NxNand manager
haven't used sxos emunand but have you tried setting the atmo location to the exact patch like below?
Code:
[emummc]
enabled=1
id=0x0000
path=sxos/emunand
nintendo_path=sxos/Emutendo
Since Android 10 is officially out now I just came here to ask the very same thing.
Due to the fact that a filebased emuMMC would make things so much easier for having Android and emuMMC (usable by both custom firmwares!) I was really hoping there was already a way to create one that is usable in Atmosphère and SX OS at the same time like it's the case for the partition based one.
@CTCaer (and anyone else here):
Since a filebased emuMMC that is usable for both CFWs seems to be impossible, is there a way to install Android on the SD card while still having the emuMMC partition at the start of the card so at least the partition based emuMMC is usable by both CFWs?
Ah yeah, forgot that TX was such a big fan of MBR unfortunately.
Guess a MBR/GPT hybrid solution would be needed somehow?
Would be great if you could look into it if u're a bit into the topic since I'm not tbh. :/
Yes, the Hybrid Mbr is unfortunately necessary. But what is still possible would be to write Android to the emmc When you are not using nintendo services.
Or you buy a 64gb emmc and then have Horizon and Android on the emmc. Then you need a new Sx license because the license is tied to the emmc.
Or you buy a 64gb emmc and then have Horizon and Android on the emmc. Then you need a new Sx license because the license is tied to the emmc.
That might work out but that would be a bit too much of a hassle for me "only" to have Android on the Switch.
Also I'm still using my sysNAND to play online.
Not sure how many other people noticed but Hekate was just updated to version 5.5.4. It includes a lot of quality of life bugfixes and niche edgecases that make it worth the upgrade. Although he also posted it on his Twitter, I learned of this update funnily enough from Wololo which is notoriously slow on the uptake 
(no offense to Wololo)
(no offense to Wololo)
I know that Hekate can turn Power off during autoRCM and battery will not drain at all just like an original Nintendo Switch.. Correct me if I am wrong.
Does Daybreak for atmosphere do the same thing ? I dont want to keep it in sleep mode for months because I haven't played it for a few months now.
Does Daybreak for atmosphere do the same thing ? I dont want to keep it in sleep mode for months because I haven't played it for a few months now.
Similar threads
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Veho:
Illinois is working to ban toxic food additives that have been banned for decades in other countries; additives that can be replaced and all those countries still have Skittles and Mountain Dew. Title of the piece: GUBMINT WANTS TO TAKE AWAY YOUR CANDY -
-
@
SylverReZ:
@Veho, Sounds and smells like bullshit. They don't give you cancer, and California should know that. I don't get why they stick labels that say "may or may not cause reproductive harm or cancer". -
