tomGER has been working with SciresM to try to find what's going on with the latest build of fs_mitm, as far as I know. I'm not sure whether it's an issue with his specific build, or with some of the newer changes SciresM made to the code.@tomGER this payload also doesn't work with your "newest commit LayeredFS" the games still say "Closed an error occurred" So perhaps this is a problem with your compilation of the Layered thing?
No reports so far, though if you're running 3.0.0 there shouldn't be any harm in tryingAny reports on 3.0.0 compatibility?
I have not been banned, but nobody can give you a definitive answer, with any modding of a console there is always a chance of getting banned. Nintendo has been the outlier in this area so far, but with their new mechanisms for detecting tinkering with the Switch, they are now on-par with the other consoles: You mod your console, you risk a ban.Hi guyz,
I want to take a full nand backup for my untouched switch using hekate through RCM mode so is this action will compromise it to be banned?
welp it worked!I have not been banned, but nobody can give you a definitive answer, with any modding of a console there is always a chance of getting banned. Nintendo has been the outlier in this area so far, but with their new mechanisms for detecting tinkering with the Switch, they are now on-par with the other consoles: You mod your console, you risk a ban.
I need some people who are on 4.0.1, who have verified that a pre-patched kernel.bin works for them, to test the following build of Hekate. It has a tweaked LayeredFS patch, based on @Falo's work in SwitchToolbox v1.0.0.2. The patch that made it in to Atmosphere looks like it was copied over wrong.
http://thedgtl.net/switch/ipl.bin
WOO! That's great to hear @Don Jon, thanks so much for testingwelp it worked!
i didnt delete the kernel patch but i did edit the hekate ini to not look for it so i think i tested correctly
ill try again later on but looks like its good
okWOO! That's great to hear @Don Jon, thanks so much for testing
It should be, this version just applied the same patch as SwitchToolbox, but in-memory as opposed to patching a kernel fileok
i deleted the kernel patch completely and its working fine
i didnt test homebrew on CFW only back ups on layerFS
but it should be fine i guess
4.01 user
Yeah, it seems that there is an actual incompatibility in the LayeredFS code with anything below 4.x A kernel patch isn't going to fix it, will require Atmosphere to fix the issue.Sadly, LayeredFS still doesn't work on 3.0.1.
You say in your pull request you had a user test this. I'm on 4.1.0 and can't seem to get it to work. What version of loader, sm, and fs_mitm were you testing with?New build with the 4.x kernel patches fixed: https://github.com/TheDgtl/hekate/releases/tag/v2.3-DMod3
This will only be useful until CTCaer gets this change into Hekate, I've already opened a pull request.
You say in your pull request you had a user test this. I'm on 4.1.0 and can't seem to get it to work. What version of loader, sm, and fs_mitm were you testing with?
I was using the kips from SDFiles v4. My fork uses "fuseepatch=1" instead of "atmosphere=1" in the hekate_ipl.ini file, so you'll need to make sure to add that line.You say in your pull request you had a user test this. I'm on 4.1.0 and can't seem to get it to work. What version of loader, sm, and fs_mitm were you testing with?
Thank you, files v4.1 are working for me. Guess I was just having bad luck of the draw. Files were either too new or too old.I was using the kips from SDFiles v4. My fork uses "fuseepatch=1" instead of "atmosphere=1" in the hekate_ipl.ini file, so you'll need to make sure to add that line.
WOO! That's great to hear @Don Jon, thanks so much for testing
Yes, CTCaer's Hekate builds now contain the same patches as this, so you can use his builds and get the same functionalityHi, thank you for your effort on this! Quick question - has this been completely integrated into Hekate v3 now? ie is LayeredFS working for 4.1.0 in Hekate?
Thanks again!