Which Switch Firmware are you on specifically?game launch error, help!!!!
when a game is detected, an error occurs: the program is closed because an error occurred, I started the game through the firmware and license. You can go into some games for a couple of minutes, then it throws it out again. I have the first revision. All the firmware is the latest. Sorry for the broken English
Using N64 NSO, is it possible to have true widescreen like you can with Mupen64Plus? Using the widescreen patch just seems to stretch it out.
Thanks for the help, but remodding my console would just wipe my emummc and i dont wanna lose what i have left. After gathering my thoughts, i pulled out an OLD backup of some key stuff like my hekate_ipl.ini to at least boot and see what i have left, my console seems to be running a little slower than usual, which is concerning, but what's worse is that all my sd card games seem to be gone. Their icons are there but they ask for a redownload, right now im trying to recover what i can, sys memory games, save files and such. Also, there seems to be trouble booting homebrew sometimes, but that should be fine.
Post automatically merged:
I just checked SD card contents with goldleaf and it's blank, i think it completely wiped the location wheregames are stored, or severly damaged it.
Is the latest atmosphere version stable with no issues now?
There used to be a thread for the latest sigpatches and all that too, is that thread not used as much now?
I guess in that case ill wait a bit. thxStill in pre-release state.

Deleting your serial number on emuMMC will not affect sysMMC. Either you didn't actually make emuMMC or you deleted your serial number on sysMMC at some point. At any rate, all you do is use Hekate to restore your eMMC backup to sysMMC. Also, this is why you shouldn't use that title installer. I highly recommend switching to TinWoo Installer instead. Its what I personally use and I never have any issues while using it.I used tinfoil on my enunand and deleted the serial number. I had no idea it would do it to the sysnand as well, so my sysnand is now blank. Im trying to restore it i have a nand backup and i have prod.keys. (not sure if they're needed in the process.) im just unsure on how to actually process with restoring my sysnand serial number
Ah okay if i use hekate to restore the backup how can i select it to restore the backup to the sysnand and not to the emunand by mistake?Deleting your serial number on emuMMC will not affect sysMMC. Either you didn't actually make emuMMC or you deleted your serial number on sysMMC at some point. At any rate, all you do is use Hekate to restore your eMMC backup to sysMMC. Also, this is why you shouldn't use that title installer. I highly recommend switching to TinWoo Installer instead. Its what I personally use and I never have any issues while using it.

Hekate will ask you where to restore it to.Ah okay if i use hekate to restore the backup how can i select it to restore the backup to the sysnand and not to the emunand by mistake?
Which Switch Firmware are you on specifically?
What version of Atmosphere and Hekate?
Where Did you get your Sigpatches?
Did you update fusee.bin when you updated Atmosphere?
Post automatically merged:
I don’t know a whole lot about widescreen on Mupen64Plus.
Does this help any?
https://gbatemp.net/threads/n64-online-widescreen-cheats.615714/
Anybody else know more about this?
Post automatically merged:
Agreed. I was only suggesting you replace anything that was missing in order to get back up and running. Recreating a new emummc would destroy things you want to keep. If it knows about your games but can’t run them then it means your emunand still has your game saves so reinstalling the games will get you right back to where you were. You may or may not have to delete the game using System-> Data Management.
How to run:
Put your Gameshark codes into “gameshark_code.txt”
Copy a ROM into this directory and name it “rom.z64″
Open a terminal and type the following…
python gameshark_code_injector.py
It will generate a rom called “rom_patched.z64″
Open your newly patched rom in your favorite emulator or copy to a flash drive for console and enjoy playing!


Sounds like your card is dying. But i'm not really sure. Check it via h2testw.What could be the problem?
Hi,
I've tried to upgrade the firmware and atmosphere to the latest patch, but the switch gives me a blue screen (attached).
I've done the steps I always do, that is:
1) Get the zip from sdsetup
2) Delete the atmosphere, bootloader, config and switch folders in the sd card
3) Upload the sd files from the sdsetup package
4) Upload the sigmapatches to the sd card
5) Upload the firmware files to the sd card
6) Inject the fusee.bin file using TegraRcmGUI
7) Update the firmware then shutdown the console
8) Inject the fusee.bin file using TegraRcmGUI
I've done this sequence many times before and it's the first time it doesn't work, did I miss something?
Thanks in advance
I think I solved it on my own!Hi,
I've tried to upgrade the firmware and atmosphere to the latest patch, but the switch gives me a blue screen (attached).
I've done the steps I always do, that is:
1) Get the zip from sdsetup
2) Delete the atmosphere, bootloader, config and switch folders in the sd card
3) Upload the sd files from the sdsetup package
4) Upload the sigmapatches to the sd card
5) Upload the firmware files to the sd card
6) Inject the fusee.bin file using TegraRcmGUI
7) Update the firmware then shutdown the console
8) Inject the fusee.bin file using TegraRcmGUI
I've done this sequence many times before and it's the first time it doesn't work, did I miss something?
Thanks in advance
According to the link below, what I posted is a valid way to get widescreen:Those are listings for some Gameshark codes. I'm not sure how those could be used with NSO.
Does anyone know how to have true widescreen with N64 NSO, not just stretched screen like the Cave mod does?

Paper Mario NTSC-U:
8102D574 2407
8102D576 018A


It has its own thread where you have already posted.Any updates on pikofly ? , someone was talking about functional firmware on thread