Tinfoil not working on Atmosphere 15.0.1AMS 1.5.3E

[DoubleX]

I just updated to 16.0.3 and have latest Atmosphere on, but Tinfoil from latest repo installs fine, but won't start.

It says "could not start the software". Please try again from the HOME menu". Please advise what to do?

 

[Shadow#1]

I just updated to 16.0.3 and have latest Atmosphere on, but Tinfoil from latest repo installs fine, but won't start.

It says "could not start the software". Please try again from the HOME menu". Please advise what to do?

Update to 16.0.3 and sigpatches

 

[DoubleX]

Thank you, I have latest 16.0.3 and latest atmosphere and got my sigpatches. Older games work, but not newer ones, please advise?

 

[Shadow#1]

Thank you, I have latest 16.0.3 and latest atmosphere and got my sigpatches. Older games work, but not newer ones, please advise?

Newer games being?

 

[DoubleX]

Tears of Kingdom

 

[Shadow#1]

Tears of Kingdom

Then redo all cfw files there is something fucked up in there

 

[urherenow]

Do you have a file that starts with F9D7F2F90A... in /atmosphere/kip_patches/loader_patches (or a similar Loader: entry in patches.ini)? If it's not your sigpatches, then it might be that you need to run the archive bit fix...

Although like 90% of the time, Tinfoil not starting is a sigpatch problem.

 

[Phantomas77]

I just updated to 16.0.3 and have latest Atmosphere on, but Tinfoil from latest repo installs fine, but won't start.

It says "could not start the software". Please try again from the HOME menu". Please advise what to do?

Where did you get the 16.0.3 files? Can't find it on darthsternie's site.

 

[Shadow#1]

Where did you get the 16.0.3 files? Can't find it on darthsternie's site.

Easiest place to get them is your switch

 

[Phantomas77]

Easiest place to get them is your switch

Don't want to go offtopic here, but yesterday I had OFW at 16.0.2. It's a brand new console, so I wanted to test the update feature with PicoFly installed.

• Created a new SD with HATS pack (with updated Atmo, etc for the 16.0.3) while the 16.0.2 was on OFW, and setup EmuMMC from scratch.
• Then updated the OFW via settings to the latest 16.0.3 and when booted to EmuMMC, it always gave me a popup whenever I open whatever game/program that a new FW update is ready. Since I couldn't find the 16.0.3 files to update the EmuMMC via Daybreak, I pressed to update, it restarted and the EmuMMC got updated to the 16.0.3.

Don't know WTF happened here and don't know from where these update files for 16.0.3 on EmuMMC came from. It works good and I still have the serial "masked" on EmuMMC, so I presume this update didn't come from official Ninty servers. Any thoughts about this magic? Thanks

 

[DoubleX]

Thank you all for your valuable input. I will try when I get home later today.
All other old games work so hopefully this is a just a sigpatch issue

Post automatically merged: May 11, 2023

I don't see 16.0.3 on darthsternie?

I have just updated to this newer version last night.

 

[Reploid]

Thank you all for your valuable input. I will try when I get home later today.
All other old games work so hopefully this is a just a sigpatch issue

Post automatically merged: May 11, 2023

I don't see 16.0.3 on darthsternie?

I have just updated to this newer version last night.

I have same issue, tinfoil and retroarch launching from forwarders just won't run. I have latest sigpatches and everything else tho. PLS do tell if you'll solve it.

 

[DoubleX]

Do you have a file that starts with F9D7F2F90A... in /atmosphere/kip_patches/loader_patches (or a similar Loader: entry in patches.ini)? If it's not your sigpatches, then it might be that you need to run the archive bit fix...

Although like 90% of the time, Tinfoil not starting is a sigpatch problem.

I have the F9D7F2F90A ...

 

[Hayato213]

Thank you all for your valuable input. I will try when I get home later today.
All other old games work so hopefully this is a just a sigpatch issue

Post automatically merged: May 11, 2023

I don't see 16.0.3 on darthsternie?

I have just updated to this newer version last night.

I assume it is a bad dump of the game if your other games run fine and totk doesn't run.

 

[DoubleX]

I have gotten the same source from two places US converted

 

[linuxares]

I would try to re-copy over the sigpatches, make sure they overwrite.

Some times if Tinfoil won't start. Just delete it on the start page like a normal software, then go in to homebrew menu and start tinfoil there and it will reinstall tinfoil.

 

[DoubleX]

Still not working. Here is what I did

1. I updated my Switch to OFW 16.0.3
2. Get the latest Atmosphere and overwrote on SD card
3. Go Tinfoil and copied to SD as well.

Then I booted it and Tinfoil working bad, sometimes it stalls for 5 secs and I get this metadata issue on Tears of Kingdom

 

[Reploid]

Still not working. Here is what I did

1. I updated my Switch to OFW 16.0.3
2. Get the latest Atmosphere and overwrote on SD card
3. Go Tinfoil and copied to SD as well.

Then I booted it and Tinfoil working bad, sometimes it stalls for 5 secs and I get this metadata issue on Tears of Kingdom

Hey, dood. This latest FW update from nin seems to be problematic and broke some stuff for some guys, like us.
If your problem is simmiliar to mine, here is what I did.

1 Downloaded and installed latest hekate https://github.com/CTCaer/hekate/releases
2 updated this setup with latest hegakte+ams sigpatches from here https://gbatemp.net/threads/sigpatches-for-atmosphere-hekate-fss0-fusee-package3.571543/
3 booted to heakte using hekate's payload hekate_ctcaer_6.0.4.bin
4 booted into cfw via hekate like I did sometime before
Tada! Had to reinstall or run corruption check on my forwarders, but otherwise it works okay

 

[DoubleX]

I updated to 16.0.1AMS 1.5.3E and now TOTK works, but BOTW and a few old does not. Could it be sigpatches or similar that is breaking it?

Thank you all including Reploid.

 

[Reploid]

I updated to 16.0.1AMS 1.5.3E and now TOTK works, but BOTW and a few old does not. Could it be sigpatches or similar that is breaking it?

Thank you all including Reploid.

You may also try to enter recovery menu. Just enter and exit, don't touch anything.