Absolutely. We’re you able to get the temp card sorted? Was the emunand created as files based instead of partition based?Hey mate, any chance if you could help me further? I think we were on the right track, thank you!
Absolutely. We’re you able to get the temp card sorted? Was the emunand created as files based instead of partition based?Hey mate, any chance if you could help me further? I think we were on the right track, thank you!
Some new games not working
I did latest firmware update and atmosphere and latest sigpatches from here. but few newer games dont run just crash other games work. i tried other source to get game but same thing. can someone lead to right direction. Youropa is one game that doesnt work just released few days ago. thanks
Absolutely. We’re you able to get the temp card sorted? Was the emunand created as files based instead of partition based?
I guess files-based, chose some 00 file and it opened. I've restored my emuNand to temporary SD and the problem replicated - black screen after second Atmosphere logo, what does it mean and what can I do now?
I can see the saves saved like this - is it correct? Didn't see your fancy saves screen with colored icons though, just a table of saves with game names.Yuck. That means your emunand is bad.
Best approach at this point is to back up your original game saves with NXNandManager by going to the Explorer (requires keys to do this) under :USER/Saves and then creating a brand new Emunand from your stock Sysnand on your old SDCard. Just use Hekate to overwrite the original partition with a new Emunand. You will need to reinstall your games and then import your game saves using JKSV. You won’t need your temp card any longer. It has served its purpose.
any chance there's some emuNand repair tool?Yuck. That means your emunand is bad.
Best approach at this point is to back up your original game saves with NXNandManager by going to the Explorer (requires keys to do this) under :USER/Saves and then creating a brand new Emunand from your stock Sysnand on your old SDCard. Just use Hekate to overwrite the original partition with a new Emunand. You will need to reinstall your games and then import your game saves using JKSV. You won’t need your temp card any longer. It has served its purpose.
here’s a thread about it:I can see the saves saved like this - is it correct? Didn't see your fancy saves screen with colored icons though, just a table of saves with game names.
Post automatically merged:
I’m not aware of any emunand repair tool. Doesn’t mean one doesn’t exist…just that I’m ignorant of its existence.any chance there's some emuNand repair tool?
Thanks - found this one, will give it a try, not sure if it's legithere’s a thread about it:
You should be able to click and get a Save option.
NXNandmanager is the most common method used.
Here’s an alternative method just for completeness:
https://gbatemp.net/threads/extract-save-from-nand-backup.514261/#post-8299285
I’ve not used this but it looks interesting.
I’m not aware of any emunand repair tool. Doesn’t mean one doesn’t exist…just that I’m ignorant of its existence.
Anyone else know of an Emunand repair tool? Am I missing something?
Does it show that it’s on after you reboot with the toggle set to on? If not, then something is missing. Probably the emuiibo system module. I typically install all the emuiibo stuff via the HB App Stoe and they come out correct and start with no issues.Anyone got experience with emuiibo I've got it installed but the sysmodule for it won't start with my switch I can see it in hekate toolbox but it's toggled to off and when I toggle it to on and restart it still doesn't work
Both are legit people in the scene…I’m just not sure it’s going to do anything more than give you a default emunand (I.e. if it rescues your saves I will be impressed.)Thanks - found this one, will give it a try, not sure if it's legit
https://www.sthetix.info/fixing-the-sysnand-the-emunand-with-the-emmchaccgen/
try those steps i found game at 3 different sources but all are same file info and name. no luck
There are approximately a dozen different possible solutions. None of them worked?try those steps i found game at 3 different sources but all are same file info and name. no luck
Mission Control allows the addition of 3rd part controllers. Does that help?Hey guys theres any homebrew to increase the amount of controllers connected up to 10?
apparently no lol. when i load with fusee it freezing on loading screen and crashes. i tried with hekate it loads little further but also crashes.There are approximately a dozen different possible solutions. None of them worked?
Post automatically merged:
Mission Control allows the addition of 3rd part controllers. Does that help?
https://gbatemp.net/threads/mission...other-consoles-natively-via-bluetooth.572645/
Does it show that it’s on after you reboot with the toggle set to on? If not, then something is missing. Probably the emuiibo system module. I typically install all the emuiibo stuff via the HB App Stoe and they come out correct and start with no issues.
What we’re the results of each thing you tried?apparently no lol. when i load with fusee it freezing on loading screen and crashes. i tried with hekate it loads little further but also crashes.
please double check You followed everything here: https://github.com/XorTroll/emuiibo/blob/master/Usage.mdExactly what happens, I have removed it all and tried the version from HB store still the same issue and when I go into oil menu it says 'emuiibo appear to not be present'
What we’re the results of each thing you tried?
They are the most common issues and we’ll need to eliminate the easy ones before we can jump into anything more esoteric.
We can walk through them one by one if you’d like
Post automatically merged:
please double check You followed everything here: https://github.com/XorTroll/emuiibo/blob/master/Usage.md
For example did you create this: sd:/emuiibo/amiibo
I just double checked mine and it looks exactly like the readme.
Maybe remove all other sysmodules except these:
0100000000000352
420000000007E51A
(the ones we’re working with)
Hi, I am getting the infamous
A Fatal Error Ocurred when running Fusee Unable to identify Package1
error after accidentally updating firmware to the latest.
I tried updating atmosphere as per https://rentry.org/MigrateToAtmosphere1_0_0. But I am still out of luck. This error still persists.
Is it safe to delete Atmosphere and Bootloader folder and then try again copying these files? Or is there a better solution?
yes. New fusee.bin was downloaded from latest 1.3.2 atmoshphere. The same fusee.bin was renamed and moved to the rcm loader ATMOSPHERER folder.Are you injecting an old fusee.bin?
Did you update your hekate_ipl.ini file? (please post contents of your file here)
You downloaded a new fusee.bin from the Atmosphere GitHub?
If you want to try out a new atmosphere and Hekate, temporarily move/rename your current ones to /atmosphere.bk and /bootloader.bk respectively and then unzip a new set of files at the top level of yiur SDCard to see if that fixes you.
[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0
[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp
[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp