search

Atmosphere-NX / Atmosphere

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.
GNU General Public License v2.0
14.29k stars 1.21k forks source link

Cannot use fs.mitm on overlayDisp #1972

Open Ereza opened 1 year ago

Ereza commented 1 year ago

Bug Report

What's the issue you encountered?

When an attempt is made to use fs.mitm on overlayDisp (title id 010000000000100C), the system hangs at startup.

I use fs.mitm to provide a Catalan language translation to the Switch interface (https://github.com/Ereza/switch-cat). This is done by replacing some .szs files on each system title via fs.mitm. I was using firmware 13.0.0 and Atmosphère 1.1.1 until now, but now I upgraded to firmware 15.0.0 and Atmosphère 1.4.0.

When on firmware 13.0.0 and Atmosphère 1.1.1 it was possible to use fs.mitm on overlayDisp with no problems. However, under the current versions, adding any file to atmosphere/contents/010000000000100C/romfs/ completely hangs the system at startup. Just a guess, but could this be related to the optimizations made to fs.mitm in 1.2.4?

How can the issue be reproduced?

If you place no files inside the atmosphere/contents/010000000000100C/romfs/ directory, the console boots just fine.

Crash Report

N/A

System Firmware Version

15.0.0

Environment?

Additional context?

SciresM commented 1 year ago

You report the issue doesn't occur on 1.1.1/13.0.0, and that it does occur on 1.4.0/15.0.0.

Does it occur on 1.4.0/13.0.0?

Ereza commented 1 year ago

Unfortunately I did not try it on 1.4.0/13.0.0, I updated the firmware and Atmosphère at the same time...

SciresM commented 1 year ago

Could you make an emummc, downgrade it to 13.0.0, and test it? If not, it is not the end of the world, but it may take me longer to test and reproduce locally.

Ereza commented 1 year ago

Hmm, I have never done anything with emuMMC and never downgraded either, so I don't feel very confident on doing that. I'm sorry...

SciresM commented 1 year ago

No worries, I will investigate myself.

Ereza commented 1 year ago

Oh, I didn't mention that, but just in case: other system titles work as expected when using fs.mitm on them. It seems to happen only with overlayDisp.

Also, possible related issue with what could be the same problem: #1698.

JarleSoelie commented 1 year ago

Hi, I believe I'm getting the same error message after updating atomsphere, hekate, and then the firmware to 15.0. Everything was working great before, and I have also updated everything several times before without any problems. I never installed any themes, and I don't have the 010000000000100C folder in my atmosphere/contents folder.

I am using emummc, (that I have left be on the sd card since I really don't want to delete 350 gb of data), but I tried to delete absolutely everything else regarding atmosphere and hekate and do as fresh of an install as possible, but I still get the exact same error message no matter what I do... I have attached the fatal error log below. Is there something inside the emummc that can cause this? Is there anything that can be done you think, or is perhaps the SD card itself on the fritz? 01640995215_010000000000100c.log

JarleSoelie commented 1 year ago

Hi, I believe I'm getting the same error message after updating atomsphere, hekate, and then the firmware to 15.0. Everything was working great before, and I have also updated everything several times before without any problems. I never installed any themes, and I don't have the 010000000000100C folder in my atmosphere/contents folder.

I am using emummc, (that I have left be on the sd card since I really don't want to delete 350 gb of data), but I tried to delete absolutely everything else regarding atmosphere and hekate and do as fresh of an install as possible, but I still get the exact same error message no matter what I do... I have attached the fatal error log below. Is there something inside the emummc that can cause this? Is there anything that can be done you think, or is perhaps the SD card itself on the fritz? 01640995215_010000000000100c.log

Wait! I fixed it, but I'm not entirely sure how. I made sure no overlays were active, I reinstalled atmosphere and hekate (making sure I extracted them from their archives before copying the files to the SD card). Then I used the latest TegraRCMgui instead of my phone to load the hekate payload. And suddenly I was in! I apologize for posting this here, I was at my wits end last night trying to figure this error out. Thanks for everything

Ereza commented 1 year ago

I just wanted to confirm that this still happens in Atmosphère 1.5.3 with firmware 16.0.3. Creating any file inside the romfs directory for title id 010000000000100C hangs the system on startup.

sodasoba1 commented 1 year ago

Just to note I tried a similar mitm but patching a szs the switch black screens but Tesla will still work.