MTP is a protocol. It gives a presentation of the SDCard. This actually mounts it like an SDCard reader so you can use regular Windows tools to fix your issue. You can reboot to payload, so no need for jig and injector.
Bottom Line: Trying to get you around “can’t” and get you to where you “can” do what @Hayato213 is suggesting.
How is this different from using MTP responder to check? And loading up Hekate would mean I have to use the jig and RCM loader,no ? Wouldn't that be more inconvenient?
So how do I remove the backup on micro SD if I have it ?
While in CFW, if you open the power menu and select "restart", your switch will actually reboot back to Hekate. Hold VOL- at the splash screen to enter Hekate's menu, and bam! No need for a jig or host to inject once you've already entered CFW.
you can use a homebrew for that, I personally use Studios Pancake overlay which allows me select which payload reboot to, and even can reboot to hekate with parameters
you can use a homebrew for that, I personally use Studios Pancake overlay which allows me select which payload reboot to, and even can reboot to hekate with parameters
you can use a homebrew for that, I personally use Studios Pancake overlay which allows me select which payload reboot to, and even can reboot to hekate with parameters
DIRECTLY TO UMS?? I mean, that's cool and all, but with DBI I have no real use for that considering DBI has similar UMS functionality. (also. uh. what the hell is Nyx anyway, other than a component of hekate?)
I think if you pass a Hekate ID that doesn’t exist it will stop in Hekate main page and not execute your autoboot=1. Super helpful when you don’t want to wait around to press Vol(-) and miss it…and have to do it all again.
DIRECTLY TO UMS?? I mean, that's cool and all, but with DBI I have no real use for that considering DBI has similar UMS functionality. (also. uh. what the hell is Nyx anyway, other than a component of hekate?)
Yes sir but you shouldn't update Atmosphère or hekate files from homebrew. Even there is a hekate config to avoid access to bootloader folder from homebrew
Yes sir but you shouldn't update Atmosphère or hekate files from homebre. Even there are a hekate config to avoid acces to bootloader folder to homebrew
Well yeah, if I'm updating those I either reboot to hekate or, more quickly and (honestly not THAT) risky, just yank out the SD card and plug it into my PC, then put it back after the update.
I think if you pass a Hekate ID that doesn’t exist it will stop in Hekate main page and not execute your autoboot=1. Super helpful when you don’t want to wait around to press Vol(-) and miss it…and have to do it all again.
I've never missed it so far, at least after memorizing that it's VOL-. My splash has been pretty helpful with that.
Post automatically merged:
Anyway, OP, one thing I recommend you do is to backup everything on your SD card, then format the SD card, and then run h2testw (or F3 if you're a linux user, but I doubt it) on the card to see if it's fake/partially broken.
One advantage for Pancake is it builds the list of options dynamically. Less to think about when making boot option changes and it’s always just there.
Being a noob and scaredy cat that I am I decided to inspect every folders size one by one before taking any further action.
I found a 29 GB size folder named sxos located in : Switch/External SD card/sxos It has :
emunand folder with full.00 -full.07.bin , each totalling about 4 GB each
nsp folder with desktop.ini
title folder with many TID subfolders in it but only is about 400kb
and desktop.ini
Another big folder in External SD card is called Switch with all my homebrew stuff in it totalling 600+ MB. What I don't understand is that looking with DBI there's already a partition called Homebrew that has the exact same stuff in Switch folder.
My question is that since I'm running on latest atmos, would I be able to safely delete the sxos folder with no repercussions or should I keep it? And should I delete Switch folder in Switch/External SD card? Thank you to every suggestion here !