Hacking Atmosphere-NX - Custom Firmware in development by SciresM

[izy]

Edit: Nevermind

What you do to fix that error

 

[Mister_X]

This isn't the place to ask for sigpatches, as Atmosphere does not (and will never) include them.
But you can always find them here:
https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-secondary-only.571543/

Thanks for the link, but this is for secundary, not primary (i think)...

 

[Dothackjhe]

Any link for primary sigpatches? Thanks

Google "exhumer patches".

 

[Adran_Marit]

Thanks for the link, but this is for secundary, not primary (i think)...

Those patches are for if you are using hekate - I just use the sigpatch updater from totaljustice to get the latest for my chosen version /shrug but a search of the forums should find both fusee-primary patches and hekate patches were the ones linked

 

[Mister_X]

Those patches are for if you are using hekate - I just use the sigpatch updater from totaljustice to get the latest for my chosen version /shrug but a search of the forums should find both fusee-primary patches and hekate patches were the ones linked

No, those patches are for hekate + secondary, im using hekate with primary.

 

[mattyxarope]

What you do to fix that error

Ok so I figured out what was wrong.

I have SX Lite hidden partition emunand and used Choi to update my emunand partition. This corrupts the BOOT0/1 on emunand. So in order for Atmo to boot properly (which as of now requires using SX Gear), you have to backup the BOOT0/1 paritions from your sysnand (with the same firmware version) and then restore those to the emunand partition.

The problem is that I have no idea how to do that, lol.

 

[Helidwarf]

Ok so I figured out what was wrong.

I have SX Lite hidden partition emunand and used Choi to update my emunand partition. This corrupts the BOOT0/1 on emunand. So in order for Atmo to boot properly (which as of now requires using SX Gear), you have to backup the BOOT0/1 paritions from your sysnand (with the same firmware version) and then restore those to the emunand partition.

The problem is that I have no idea how to do that, lol.

If you used choi to upgrade a mariko system before then you will have erista code in your boot0 and will get a nxboot not enough storage error when using atmosphere, luckily all mariko consoles running the same firmware have the exact same boot0, so ideally if you cant fix your boot0 you can just get someone to share their boot0 (as long as you are on the same fw i.e. both consoles needs to be 11.0.0)

 

[mattyxarope]

If you used choi to upgrade a mariko system before then you will have erista code in your boot0 and will get a nxboot not enough storage error when using atmosphere, luckily all mariko consoles running the same firmware have the exact same boot0, so ideally if you cant fix your boot0 you can just get someone to share their boot0 (as long as you are on the same fw i.e. both consoles needs to be 11.0.0)

Well I tried to backup my sysnand's boot0/1 sectors with the SX tool, then use Hekate to restore those to the Emunand partitions, and then migrate the emunand to Hekate. That didn't work, still Boot0: Not enough space error.

 

[Helidwarf]

Well I tried to backup my sysnand's boot0/1 sectors with the SX tool, then use Hekate to restore those to the Emunand partitions, and then migrate the emunand to Hekate. That didn't work, still Boot0: Not enough space error.

did you use choi to upgrade your sysnand? also have you tried using the cleanup option in sx firmware?

 

[mattyxarope]

did you use choi to upgrade your sysnand? also have you tried using the cleanup option in sx firmware?

I've used Choi before, yes.

And no, I haven't used the cleanup option. What does that do? Full disclosure, I've also migrated the emunand using Hekate after trying to get it to work. Should I rename the Nintendo folder and change it back to Emunand (and restore its location) before doing the cleanup option?

 

[Helidwarf]

I've used Choi before, yes.

And no, I haven't used the cleanup option. What does that do? Full disclosure, I've also migrated the emunand using Hekate after trying to get it to work. Should I rename the Nintendo folder and change it back to Emunand (and restore its location) before doing the cleanup option?

if you have used choi before then your sysnand boot0 also has erista code thus same error, you need a clean donor boot0 from a system with the same fw

The cleanup option "supposedly" removes tx code from your boot0, but who knows, tx is full of shit you dont know if they are bullshitting you...

I'm using sx emunand with atmosphere by creating a ini file in sd:emummc/emummc.ini
with the following:

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

no need to emigrate with hekate

 

[mattyxarope]

if you have used choi before then your sysnand boot0 also has erista code thus same error, you need a clean donor boot0 from a system with the same fw

The cleanup option "supposedly" removes tx code from your boot0, but who knows, tx is full of shit you dont know if they are bullshitting you...

I'm using sx emunand with atmosphere by creating a ini file in sd:emummc/emummc.ini
with the following:

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

no need to emigrate with hekate

Is backing up my sysnand now and restoring that not good enough? I'm confused about that...

And I've already migrated the emunand, I can move it back though.

 

[Helidwarf]

Is backing up my sysnand now and restoring that not good enough? I'm confused about that...

And I've already migrated the emunand, I can move it back though.

you said you've used choi on your sysnand before so no its not good enough (choi was never intended to be used with mariko systems so it always assumes the console it's running on is an erista. When you use it it will ALWAYS corrupt your boot0 with erista code). You need to find a clean donor boot0 running the same FW.

 

[mattyxarope]

you said you've used choi on your sysnand before so no its not good enough (choi was never intended to be used with mariko systems so it always assumes the console it's running on is an erista. When you use it it will ALWAYS corrupt your boot0 with erista code). You need to find a clean donor boot0 running the same FW.

No, I used Choi only on SX hidden partition emunand, never on sysnand. I've only ever updated using the online updated on sysnand.

I tried using SX cleanup but that didn't do anything.

Still Boot0 error.

 

[Helidwarf]

are your sysnand and emunand on the same FW then? as I said the boot0 is FW specific, you can't use a 10.2.0 sysnand boot0 with a 11.0.0 FW emunand

--------------------- MERGED ---------------------------

Spoiler

I'm just gonna leave here what SciresM had to say about this nxboot issue.

 

[mattyxarope]

are your sysnand and emunand on the same FW then? as I said the boot0 is FW specific, you can't use a 10.2.0 sysnand boot0 with a 11.0.0 FW emunand

Both my sys and emu nands are on the same firmware.

I:

1. Backed up the boot0 and boot1 sectors of my sysnand using SX's tool.

2. Booted Hekate, used it to create an emunand backup of boot0 and boot1.

3. Deleted the backups made by Hekate, then replaced them (in the restore folder) with the ones made by SX.

4. Booted Hekate using SX Gear, then Atmo, which did not work.

 

[SciresM]

gateway's "cleanup" just copies the backup bootloader/BCT on top of the normal one.

Choi overwrites both the normal and backup with garbage erista contents.

You need to flash a valid Mariko BOOT0, to fix that kind of error. If you can't figure out how to do it, I imagine somebody will make a tool, given how common it seems like people bricking themselves with choi is.

 

[mattyxarope]

gateway's "cleanup" just copies the backup bootloader/BCT on top of the normal one.

Choi overwrites both the normal and backup with garbage erista contents.

You need to flash a valid Mariko BOOT0, to fix that kind of error. If you can't figure out how to do it, I imagine somebody will make a tool, given how common it seems like people bricking themselves with choi is.

I think I know how it is done, just trying to figure out why it didn't work.

I've used the Hekate restore feature for a BOOT0/1 backup from my sysnand, but perhaps that isn't enough?

Unfortunately I don't have my card reader so I can't use the NX tool that is around to restore.

 

[SciresM]

I think I know how it is done, just trying to figure out why it didn't work.

I've used the Hekate restore feature for a BOOT0/1 backup from my sysnand, but perhaps that isn't enough?

Unfortunately I don't have my card reader so I can't use the NX tool that is around to restore.

"backup from my sysnand" I would guess that your sysnand is also corrupted by choi.

 

[mattyxarope]

"backup from my sysnand" I would guess that your sysnand is also corrupted by choi.

Despite not using Choi to update it? I've only ever used Choi on emunand...that's what I'm confused about...