Hacking Unable to run emuMMC on a freshly jailbroken 18.0.1 switch

[Logenter]

I installed an Instinct-NX modchip on a switch OLED and it works fine, I've jailbroken many switches before, but this one can only run Semi-stock (SYSMMC) and CFW (SYSMMC) but it just won't run emuMMC, I've tried with an original Sandisk 512GB SD and an original Adata 128GB SD. so It's not the SD either. If I try running atmosphere with the fusee.bin it says that the GPT signature is invalid. I've tried many cfw packages from different people including the latest HATS pack but nothing seems to work, has anyone ever had to deal with this?? I'm starting to go insane.

 

[MoeXzl]

@Logenter You don't need fusee.bin, it works fine without it. Have you tried making a backup? Format your SD to FAT32 and download the latest HATS package to test it. Make the EmuNand first and then the backup, otherwise you will be missing files on the SD, which is what happened in your case.

 

[Logenter]

@Logenter You don't need fusee.bin, it works fine without it. Have you tried making a backup? Format your SD to FAT32 and download the latest HATS package to test it. Make the EmuNand first and then the backup, otherwise you will be missing files on the SD, which is what happened in your case.

I tried with and without fusee.bin for troubleshooting sake, after creating the emuMMC with hekate I use UMS to insert again all the folders once again (atmosphere, bootloader, config etc) just in case i'm missing a file or something an then run the emuMMC but same outcome.

Also if at the moment of creating the emuMMC I use SD file instead of SD partition it actually works and enters atmosphere, but the contents of the Nintendo folder at emummc\Nintendo\ always get corrupted, prompting the console to throw the error code 2016-0247 "The MicroSD card cannot be read by the system." Please reinsert the MicroSD card[...]".

What baffles me is that it just won't work at all if a use SD partition when creating the emuMMC, just goes straight to a black screen with red letters.

 

[MoeXzl]

But you can start the OFW normally? Is your Emmc partition table error-free or is something missing?

 

[Logenter]

But you can start the OFW normally? Is your Emmc partition table error-free or is something missing?

Yeah, OFW works fine, even CFW using Sysnand, only emuMMC doesn't work. I would assume the Emmc partition table should be error free since the switch is pretty new and it works with OFW but how do I check it? I'm gonna do it tomorrow.

As for things missing I don't think so, I format de SD card, partition it with Hekate and then create the emuMMC as a SD partition, and at that point nothing looks missing but it doesn't work either. Things start going crazy and corrupting when I create a emuMMC as a SD file though, but that's the only way I've made the emuMMC work so I'm against the wall here.

 

[TheStonedModder]

Yeah, OFW works fine, even CFW using Sysnand, only emuMMC doesn't work. I would assume the Emmc partition table should be error free since the switch is pretty new and it works with OFW but how do I check it? I'm gonna do it tomorrow.

As for things missing I don't think so, I format de SD card, partition it with Hekate and then create the emuMMC as a SD partition, and at that point nothing looks missing but it doesn't work either. Things start going crazy and corrupting when I create a emuMMC as a SD file though, but that's the only way I've made the emuMMC work so I'm against the wall here.

Did you replace the HAT files after creating the partition ? Hekate says it’s going to backup the files prior but this has never been the case for me. I always lose files or they get corrupted

 

[Hayato213]

Your problem is that your card is under gpt instead of mbr

 

[Logenter]

Did you replace the HAT files after creating the partition ? Hekate says it’s going to backup the files prior but this has never been the case for me. I always lose files or they get corrupted

I do replace the files after partitioning the SD card, I've heard that's been a problem for some people so I do it now.

Post automatically merged: May 28, 2024

Your problem is that your card is under gpt instead of mbr

I don't think that's the problem.

Post automatically merged: May 28, 2024

Guys I checked the Vendor Id for the eMMC of the console and it's a Toshiba (11). Could y'all do me a big favor and check if your switch have a toshiba eMMC? my personal switch has a Samsung (15) and works perfectly.
To check the vendor id go into hekate - console info - eMMC
My theory is that maybe It's the toshiba eMMC the one that's creating problems.

 

[MoeXzl]

In this case, the NAND is not the problem. Toshiba is said to be causing problems with glitching - and you can use OFW and CFW (Sysnand) that access the NAND without any problems. The error lies elsewhere.

 

[Logenter]

In this case, the NAND is not the problem. Toshiba is said to be causing problems with glitching - and you can use OFW and CFW (Sysnand) that access the NAND without any problems. The error lies elsewhere.

I see, makes sense, I'll have to keep digging then.

Post automatically merged: May 28, 2024

Ok guys remember when I said that if I create the emuMMC using SD File it actually boots into atmosphere but everything gets corrupted and messed up? I turned on the logs while booting and there are interesting differences when booting the emuMMC with SD partition and SD file.

Red letters and black background is SD partition
White letters black backgroud is SD file
unfortunately I'm no expert and can't make a guess on what all that means, maybe someone else can have an idea?

 

[Logenter]

Figured it out, it was the SD, I ordered brand new ones and everything went smoothly, I feel super dumb.