Yellow screen after using AIO updater

[Noctosphere]

Hello everyone

I haven't used my Switch in a couple of months, and havent updated it for an even longer while.
Today, i wanted to play totk on it, but everything in it was very outdated, ofw and cfw.
So i used the All in one switch updater and updated everything there was to update.
At the end, it asked me to reboot the console. After that, i ran in the menu to choose the fw i wanted to run, cfw or ofw. I went for the cfw of course, and everything went yellow

Dont be fooled, it really is yellow, it's not white.

So yea, is there anything to do? My computer is out of service for now, so i cannot edit anything on the microsd (gonna check my other cellphone to see if they have a microsd slot)
Thanks everyone

 

[jkm81]

Does it boot in stock firmware?

 

[Noctosphere]

Does it boot in stock firmware?

Yes and no
If i boot it from hekate, i get the yellow screen
If i boot it the regular way, everything is normal

 

[linuxares]

https://github.com/CTCaer/hekate/issues/660

 

[Noctosphere]

https://github.com/CTCaer/hekate/issues/660

Alright thanks
So my switch is out of service for good until i get my computer back

 

[twins333]

Alright thanks
So my switch is out of service for good until i get my computer back

There are usb card readers for cheap, coupled with an otg adapter (type c or microusb) you can edit/delete/download/unpack anything on your phone and change it that way.
pro tip: use total commander on the phone for easy unpack/edit/transfer of files.

 

[Hayato213]

@Noctosphere I was going to say to do a manual update but since you don't have a working computer that is hard to say, typically replacing the CFW files would fix AIO problem.

 

[jkyoho]

C to C cable + file explorer on android phone should do most work for PC

 

[Noctosphere]

Ok, i received my sd reader, but...
Here is what i got in my ini file

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

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

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


I didn't change anything, yet, it seems to be the way it should be to not be bugged, according to @linuxares link

 

[Hayato213]

Ok, i received my sd reader, but...
Here is what i got in my ini file

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

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

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


I didn't change anything, yet, it seems to be the way it should be to not be bugged, according to @linuxares link

If you have an emunand use the CFW-emuMMC one if not use the CFW sysMMC

 

[Noctosphere]

If you have an emunand use the CFW-emuMMC one if not use the CFW sysMMC

I get yellow screen on all three options of hekate.

 

[jkyoho]

HEKATE & ATM up to date?

 

[linuxares]

Hmm you always boot via FFS0.
Can we do a test and boot Atmosphere instantly without using FFS0?
You need to have fusee.bin in the payloads folder (latest version from Atmosphere!)

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


EDIT:
I honestly think that you need to delete Atmosphere folder and copy a fresh over. AIO updater maybe didn't update something correct for you.
EDIT2: And for good measure, do an Hekate fresh Hekate install as well.

 

[Noctosphere]

Hmm you always boot via FFS0.
Can we do a test and boot Atmosphere instantly without using FFS0?
You need to have fusee.bin in the payloads folder (latest version from Atmosphere!)

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

Can you give me a proper tutorial for this? Just so i dont screw this up even more

HEKATE & ATM up to date?

Last week, i updated everything there was to update in AIO updater

 

[linuxares]

Can you give me a proper tutorial for this? Just so i dont screw this up even more


Last week, i updated everything there was to update in AIO updater

1) That thing I gave you, just put it in hekate_ipl.ini. Safe copy that file to your Computer.

2) https://github.com/Atmosphere-NX/Atmosphere/releases - download atmosphere and fusee.bin. Put fusee.bin in /bootloader/payloads/

3) Delete atmosphere on your SD Card, extract the new Atmosphere and all the related files to your SD Card. Overwrite anything it asks.

4) Download Hekate - https://github.com/CTCaer/hekate/releases extract the Hekate files to you SD Card (ignore the joiner and nyx reg file on the download page)

5) Copy back the hekate_ipl.ini and overwrite it.

6) Reinsert your SD Card and see if you still get yellow.
----------
If successful boot?

Download Signature patches so you can run unsigned stuff again!

 

[Hayato213]

I get yellow screen on all three options of hekate.

What happens if you replace your files with fresh files?

 

[Noctosphere]

1) That thing I gave you, just put it in hekate_ipl.ini. Safe copy that file to your Computer.

2) https://github.com/Atmosphere-NX/Atmosphere/releases - download atmosphere and fusee.bin. Put fusee.bin in /bootloader/payloads/

3) Delete atmosphere on your SD Card, extract the new Atmosphere and all the related files to your SD Card. Overwrite anything it asks.

4) Download Hekate - https://github.com/CTCaer/hekate/releases extract the Hekate files to you SD Card (ignore the joiner and nyx reg file on the download page)

5) Copy back the hekate_ipl.ini and overwrite it.

6) Reinsert your SD Card and see if you still get yellow.
----------
If successful boot?

Download Signature patches so you can run unsigned stuff again!

Seems like everything works again

Thanks a lot

For future concerns, if i have similar problems after updating atmosphere and co, would you suggest me as first "common solution" to do a clean update? Like the common solution everyone should try with a buggy computer is to just restart it, is a clean install a common solution in the cfw area?
Thanks again

 

[Hayato213]

Seems like everything works again

Thanks a lot

For future concerns, if i have similar problems after updating atmosphere and co, would you suggest me as first "common solution" to do a clean update? Like the common solution everyone should try with a buggy computer is to just restart it, is a clean install a common solution in the cfw area?
Thanks again

Don't use AIO, just manually update your files then update the firmware, AIO is known for having problems.

 

[linuxares]

Possibily, I've stopped using AIO Updater to update. I always use Hekate's USB tool, connect my PC via it.
Then copy over Atmosphere and Hekate and overwrites the files.

 

[Noctosphere]

Seems like ive got another problem
I'm unable to launch tinfoil at all. I found solutions online which apparently worked for those who had the same problem as i have, but they dont work for me.
I get that "unable to launch software" error.

But maybe i'm looking at the wrong place, because i think i saw somewhere that tinfoil was like the freeshop for 3ds. Is that right? If not, can you guys point me to the homebrew name?

Thanks again