What's the best jig to get for a Switch? Links would be helpful.
some friends came over last night and we got HIGH as F**k and attempted to update my switch setup. we got the 'nogc' flag figured out booted in official mode and updated The switch OFW to the latest with success then we got lost. the last time i touched this unit it was on 8.* and I have to relearn some shit. LIKE...
why was there two versions of sigpatchs and atmosphere when I did this in the first place?
Switch is in RCM, as mentioned in my first post to this problem. libusbk 3.0.7.0 is installed and running. Not working as I said.
If I wanted to mod botw, but use a cartridge, how would I do it?
Cool, thanks! I can remember injecting 'fusee-primary' at the time it was the only way i could get my LEGIT botw backup to run. I purposely keep my CartSlot empty so it's pins stay nice and springy while my cart and its case stay unstealable in my closet. Zelda is the only game i own so i dont need some big pile of sigpatches or anything, Just point or PM me to a good tut
The patches on ITotalJustice's github are the same now (fusee.zip and hekate.zip). He changed that when Blawar removed the Hekate check in Tinfoil. See his comments here: https://github.com/ITotalJustice/patches/releases/tag/12.1.0-0.19.5-r2https://github.com/ITotalJustice/patches/releases
patches are based on bootloader you use, if you used fusee it fusee patches, if it is hekate/fss0 it is hekate patch. Chainloading fusee from hekate would make bootloader as fusee, you should understand in general what each bootloader and what each pack of signature patches do.
https://gbatemp.net/threads/guide-to-choose-which-atmosphere-patches-to-use-on-switch-fw-10.563886/
Cyan wrote a good guide explaining stuffs so it is a good idea to check it out, keep in mind fusee-primary.bin has been replace by fusee.bin and fusee secondary.bin has been replace by package3, refers to Atmosphere 1.0.0 change logs.
https://github.com/Atmosphere-NX/Atmosphere/releases/tag/1.0.0
The patches on ITotalJustice's github are the same now (fusee.zip and hekate.zip). He changed that when Blawar removed the Hekate check in Tinfoil. See his comments here: https://github.com/ITotalJustice/patches/releases/tag/12.1.0-0.19.5-r2
The only "essential" folder that is used by both CFW is the /switch folder as it contains all of your homebrew applications/I have Lite and I want to migrate from SXOS (emunand, files on the card) to Atmo. Which folders are essential on the SD card? I want to delete other files which aren't important to free up space and to have a "clean" start. I don't care about saves etc.
Is this error occurring when you try to boot your emuMMC?Incidentally, I'm attempting to migrate SX OS to Amosphere myself. I'm following this guide, latest files used, all exactly as per the guide: https://rentry.org/mys8q
I'm getting the dreaded "failed to locate warmboot" when trying to boot into Atmo. Any ideas on what I'm doing wrong here?
Have you tried using NRO2NSP?Hi, i want to convert .NRO to .NSP on my switch 12.1.0 ans atms 1.0.0.
Can anyone help me?
I've never heard of that error but it sounds like it tried to boot emuMMC, failed, and possibly fixed itself.Second question. When migrating I missed this command at the very end "Select emuMMC in the main menu, then select Migrate emuMMC and finally select emunand. Once it's done, select Close." (Guide from rentry site) and I pressed launch -> Atmosphere. The system booted up with aeroplane mode. I switched off, went into menu and selected migrate emuMMC option. I got information saying something like emunand files found and if I want to replace them. I completed the process. Did I just f**k up my sysnand or it booted into emunand?
Yes.Is this error occurring when you try to boot your emuMMC?
Does the same error occur when you try to boot CFW on sysMMC?Yes.
When I try to launch the fix I get a "failed to match warmboot with fuses" - it boots into OFW once I ignore that (and yes, sleep mode indeed does not work), but it doesn't really do or fix anything - same error crops up when I try booting to Atmosphere again.
If it matters, I can't seem to reboot and boot into OFW from Hekate when I try that, either. OFW at 10.2.0.
I'd rather avoid trying that route, frankly, so I don't know...Does the same error occur when you try to boot CFW on sysMMC?
The only "essential" folder that is used by both CFW is the /switch folder as it contains all of your homebrew applications/
Is this error occurring when you try to boot your emuMMC?
Have you tried using NRO2NSP?
I've never heard of that error but it sounds like it tried to boot emuMMC, failed, and possibly fixed itself.
Well I believe the issue stems from a lack of a cached/dumped warmboot which the CFW, Atmosphere, does automatically. But if you cannot boot emuMMC to dump it, then your only other option is to boot CFW on sysMMC to dump it. And before you ask, no that cannot be shared on this forum.I'd rather avoid trying that route, frankly, so I don't know...
If you do not have a backup of your emuMMC, then you cannot recover it. To properly update Atmosphere is the same process regardless if you are using emuMMC or sysMMC; delete the old CFW files/folders and place the new ones on the SD card. Next time, do not use the AIO Updater app. They have always been known to be buggy and many other people have had issues after using it so I would stay away from it as well as any similar applications.Surprised to see a whole number 1 update available for atmosphere through All-in-one updater homebrew app and made the mistake of updating it through the app. Once it rebooted it just gave me the panic message everytime it reboots. So I panicked and tried to fix my FU by following SD prepartion_NH Switch Guide and copy most updated files. It allowed me to boot into SYS CFW and seemed to have lost my EMUMMC. Any recommendations how to recover and update my EMUMMC? How do you properly update atmosphere on EMUMMC File Type without repeating this FU?
My mistake. It would appear someone made a new one for the higher firmware versions here.doesnt work in firmware 12.1 only 11.00 or lower
Wouldn't that be, presumably, the single bin in the warmboot_mariko dir? That got dumped, as far as I can tell.Well I believe the issue stems from a lack of a cached/dumped warmboot which the CFW, Atmosphere, does automatically.
I've never heard of that error but it sounds like it tried to boot emuMMC, failed, and possibly fixed itself.