m4xw / emummc Goto Github PK

Crash happens as soon as the first loading screen with the rolling ball fades out, before the intro movie plays. After many tests (including several different consoles / SD cards / setups), I managed to narrow the issue down to SD Files EmuMMCs.

I apologize in advance and understand this might be frowned upon as the game is not officially out yet, but since it's apparently an issue tied to the EmuMMC, I figured I'd report it anyway.

Bug Report

What's the issue you encountered?

When I am using emuMMC, the Smash Ultimate character selecting screen(known as CSS) go very slow.

How can the issue be reproduced?

Yes, just use emuMMC and open Smash Ultimate to CSS you can see it happen.

it will happen even you have only 8 characters to choose.
It will happen no matter you have mod or not.
it will happen no matter you overclock or not.
it will happen I install the game to the NS itself.
It It won't happen in the real system with atmosphere even using mod by using the same SD card with the same soft environment.

System Firmware Version

NS 13.1 and earlier.
atmosphere 1.2.2 and earlier

Environment?

not using the Official release, but as I said, it won't happen in real system with atmosphere in the very same environment.

Additional context?

This bug may seems no big deal, but you know how often people open this game worldwide, as myself is a mod maker, so my job is to test my mod time and time again and it just killing me every time i test my mod on a switch. so i just really hope this can be solved ,thanks a lot

Hi guys,

Is it possible for Nintendo to detect/scan the hidden emunand (for homebrew or similar) by mounting the hidden partition?

I tried to boot Lakka, but it wouldn't boot past the hekate splash screen. According to another user, this is fixed by deleting the emuMMC partition. I would like to use Lakka and emuMMC on the same SD card.

On crash in emummc/FS, we should handle so that e.g. stacktrace/registers are saved for debugging.

Stock emuMMC does not boot into Horizon. It results in a black screen after Nintendo Logo. Issue persists on all Firmwares, tested with OFW 4.1.0, 5.1.0, 8.0.1.
Issue is also referenced here: CTCaer/hekate#250

TF/SDcard performance and durability is far more less than USB Drive. Please consider add support for USB Drive, So we can boot from TF card, and load system from USB Drive!

Hekate: 5.9.0, Atmosphere: 1.4.0
System FW: 13.2.1

I've been using sysMMC with no issues. I just tried to setup emuMMC and it loads up to the Switch logo and it sits at a back-lit black screen.

I formatted a 128Gb sd card as FAT32 for Atmosphere and partitioned ~30Gb for the emuMMC.

Sorry, if I'm still not asking appropriately, I'm a little new to Github.

Hi,

Thanks a lot for the great project! Please forgive me if this is not the correct repo to discuss this issue described below.

Issue:

I was trying to transfer a file with Chinese and Japanese in the filename. However, the file will not show in the SD/file browser.

Environment:

Atmosphere version: 17.0.0
SD card format: FAT32

Steps to reproduce:

1. Load the file to SD card via Hekate USB tool
2. Boot into emummc
3. Get into GoldLeaf or DBI or Tinfoil
4. Navigate to the location of the file using file/SD browser
5. For Chinese and Japanese filename, the files are simply not listed. A simple filename for testing could be 你好.txt for Chinese and こんにちは.txt for Japanese.
6. For Korean filename, the file size is 0.0B and the characters are replaced with "_". A filename for testing could be 안녕하세요.zip.

Other methods to load the file into SD card have similar results. For example, transferring via DBI will drop the Chinese/Japanese characters in the filename, while scp will reject the operation.

Includes a hook for sdmmc_accessor_get_memory_capacity
TODO: Maybe also overwrite other params?

The observed behavior is an elongated black screen after b&w logo.
The specific time it needs to reach the switch logo, points to sdmmc initialization failures.

This does not happen on 10.2.0 and lower.

Tested emuMMC type was file based. Unknown if the issue exists in partition based.

Copy the bug report form Atmosphere: Atmosphere-NX/Atmosphere#1128

Bug Report

What's the issue you encountered?

Both hekete and fusee-primary failed to boot a 4.1.0 partition-based emunand emunand.
Got a black screen after Nintendo Switch Logo.
But a file-based emunand boots fine which created from the same sysnand.
And after reboot to hekete from the file-based emunand 4.1.0, the partition-based emunand 4.1.0 could be booted successfully.
After upgrade the partition-based emunand to 10.1.0, it boots ok.

How can the issue be reproduced?

Create a partition and emunand using hekate from sysnand 4.1.0.
This partition-based emunand always fail to boot.
Tested on two different brands of SD cards.

System Firmware Version

4.1.0

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate and fusee-primary
• Official release or unofficial build:
  • Atmosphère 0.14.1
• Do you have additional kips or sysmodules you're loading: No
• Homebrew software installed: ChoiDujourNX

Additional context?

RCM Exploitable Switch
Auto RCM disabled
Caffeine used to boot into RCM
incognito applied on sysnand
SD cards are fat32 formatted

-This needs some refactor, everything is already there it just got broken later in the dev cycle.

Bug Report

What's the issue you encountered?

Installing game from eShop, then goes to settings and moving game to NAND with internal HOS method.
File-based EmuNAND, on Samsung EVO 128Gb microSD, formatted with hekate 5.5.3. Booted from hekate =- payloads =- fuse-primary.bin
Using atmosphere-0.17.1-master-49f07b06+hbl-2.4.0+hbmenu-3.4.0 from github. I have unpacked hekate_ctcaer_5.5.3_Nyx_0.9.9.zip to the root of sd, then unpacked atmosphere-0.17.1-master-49f07b06+hbl-2.4.0+hbmenu-3.4.0.zip, renamed hekate_ctcaer_5.5.3.bin to payload.bin and put fuse-primary.bin too bootloader =- payloads

My modchip works on Spacecraft-NX.

How can the issue be reproduced?

1. Format SВ with hekate
2. Remove all files from SD
3. Unpack hekate_ctcaer_5.5.3_Nyx_0.9.9.zip to the root of sd
4. Unpack atmosphere-0.17.1-master-49f07b06+hbl-2.4.0+hbmenu-3.4.0.zip to the root of sd
5. Renam hekate_ctcaer_5.5.3.bin to payload.bin
6. Put fuse-primary.bin too bootloader =- payloads
7. Launch console
8. Payloads =- fuse-primary.bin
9. Install game from eshop
10. Go to Settings =- Data Management =- Move Data Between Console/microSD Card =- Move to System Memory =- Choose game =- Move Data =- Move
11. After approximately 1 minute system will crash with error provided on screenshot below

With fss0 (fss0=atmosphere/fusee-secondary.bin) I got this error:

Crash Report

fuse-primary:
atmosphere.zip

fss0:
fatal_reports.zip

System Firmware Version

11.0.1

Environment?

Using atmosphere-0.17.1-master-49f07b06+hbl-2.4.0+hbmenu-3.4.0 from github. I have unpacked hekate_ctcaer_5.5.3_Nyx_0.9.9.zip to the root of sd, then unpacked atmosphere-0.17.1-master-49f07b06+hbl-2.4.0+hbmenu-3.4.0.zip, renamed hekate_ctcaer_5.5.3.bin to payload.bin and put fuse-primary.bin too bootloader =- payloads without additional homebrew, patches or other

Tested on Switch Light and big Switch on Mariko

Additional info

It seems that FW 9.0.0 is not supportet on file based emuMMC running under ATM 0.9.4 (a750e55f). Repeated updates with ChoiDujourNX that passed successfully resulted in a black screen after a subsequent reboot. The last working FW version was 8.1.0.

Switch is on sysNand 5.1.0

Methods employed:

• DBI "Install to NAND"
• "HOS" Move software to internal storage"
• Game Card Installer "Nand Install"

A crash stack appears a few gigabytes into transfer pretty consistently. Hekate and Atmo people keep telling me that's an emuMMC issue. Can I help as an engineer?

add code pls June 15 uwu

I was updating my firmware and I clicked on 17.0.1 without thinking about it. But when rebooting I started to get tons of errors. Is there any way to downgrade or should I wait for an update?

Access to album path on 1.0.0 is swapped resulting in an Album folder at the root of the sd card and an emuMMC path on the USER partition.

Mounting the folder via OpenImageDirectoryFileSystem will allow you to mount those exact paths and OFW will write to those.

Hello,

I am sorry it is probably not in the correct category but I was trying to find a way to contact you.
I don't know exactly what to do with theses issues. I already tried so many things in order to solve this but I really don't know what to do now. I am even thinking of selling my unpatched switch as I am so frustrated now...

I have an unpatched Switch: XAJ7001373 OFW: 9.1
I installed Atmosphere 10.1 and Hekate 5.1.1 with the patches from Joonie86.
I managed to partition my SD card with Tegra Explorer and I managed to create en EMUNAND.
I also managed to launch Hekate without any issue or to launch directly Atmosphere with fusee-primary.bin. So I managed to run the switch with the emunand 9.1/ATM10.1/E
However my system appears to be unstable. Randomly I have some frozen screens when I am playing, or some crashes with 2002-2002 error code and 2002-3502 code.
SciresM wrote to me that he didn't think it was a problem within Atmosphere but maybe you would have some thoughts about these Nand issues...

I tried the tool Archive Bit of Hekate and I always have some archive bit fixed (typically 60 in the Nintendo folder) even if I use the tool several times in a row as if it wasn't correcting the archive bits (don't know if it is normal)
I tried different SD cards (SANDISK ULTRA and SAMSUNG EVO+) that appear to be genuine, I checked them with h2testw...
I am kind of desperate. If someone could help me in order to get a stable system, I would really appreciate. (For one of my friend, it works really well and it is stable)
One of my thought is that my sysnand is dirty. I used a RCM loader and I had a very weird message (like a virus message when it loaded the payload the very first time)
Is it possible that with a dirty sysnand it could create some issues like that.
I know that I should have made a clean copy of my sysnand from the beginning but it appears that the copy I made at the very beginning is not good because when I tried to restore it, I had an error message.
I used Haku33 once in order to clean my sysnand but I am wondering if it is enough to clean it completely. I was able to connect to the eshop and to download demo games from it without being banned but still when I am running the CFW on EMUMMC, it is not stable.
Please, if anyone has an idea on what to do in order to get a stable system working, I would really appreciate. Thanks a lot