They may be mixing up coldboot with softmod. Coldboot is theoretically possible up to 3.0.2 but no one is working on it at the moment.Where is all this coldboot info coming from? I can't find anything beyond random posts from people with no real info.
The softmod that people are most likely referring to is Deja Vu as seen below
I intend to be fully transparent about this shit, especially going forwards. At present, I'm not aware of any non-RCM means of getting code execution from coldboot. To the best of my knowledge, nobody else is, either.
Got some good news (sorry that it takes over a minute for the lennies): https://t.co/hGdPOchTVo
— Michael (@SciresM) February 16, 2018
Anyway, I would strongly recommend not updating when new firmwares release.
Although autorcm is a little bit yikes, what makes people still wait for a coldbit exploit? It has the same usage
Some people are holding onto the hope that an untethered softmod coldboot becomes available. Not all users wish to use a jig and USB cable to use hacks. Jigs aren't 100% guaranteed to work and may not be entirely safe on the Switch's pins either. The only known alternative to loading hacks is via the warmboot softmods that have been confirmed and shown to work up to 4.1. However, their release date has not been specified yet.Thats the point I'm getting at. There isn't a cooldboot hack. I see it all over these forums and it doesn't actually exist.
Edit: The only really difference I can find is older firmwares wont need a jig to enter RCM while newer firmwares do. To me it doesn't seem like a good reason to not update. I'm always open to being proven wrong though.
Well for me it's a good reason to stay lower firmware, since it would really annoy me to always use a jig. But that's just my personal opinion.Thats the point I'm getting at. There isn't a cooldboot hack. I see it all over these forums and it doesn't actually exist.
Edit: The only really difference I can find is older firmwares wont need a jig to enter RCM while newer firmwares do. To me it doesn't seem like a good reason to not update. I'm always open to being proven wrong though.
I get that. What made me update from 4.1 was that exfat update, couldnt really be arsed to follow that one guide and just pressed the button.Well for me it's a good reason to stay lower firmware, since it would really annoy me to always use a jig. But that's just my personal opinion.
You only update if you don't mind having to use a jig and a USB cable for possibly the rest of the Switch's life. Some people mind and others don't. Its down to personal preference.
The only difference is not using a jig. You will still need a USB C cable and a PC or phone to load a payload.You only update if you don't mind having to use a jig and a USB cable for possibly the rest of the Switch's life. Some people mind and others don't. Its down to personal preference.
No the USB cable is needed only if you are using an RCM based exploit. Deja Vu is a webpage-based exploit meaning you will not need a jig nor USB cable, you will only need an Internet connection. The only situation where you don't need a jig is if you are using AutoRCM.The only difference is not using a jig. You will still need a USB C cable and a PC or phone to load a payload.
Hacks are loaded differently depending on what you are using. PegaSwitch for example was purely script based. It did not involve payloads. Payloads are used in the current exploit because of how the RCM is configured within the Switch. We first cause a stack smash and after that, some code is sent that is treated as properly signed due to the error we just created. It also must be sent via USB because in RCM, it can accept code from there. For Deja Vu, the closest thing would be the PS4 exploit where you navigate to a webpage and click on the appropriate links to boot hacks.I've been searching, and I can't find anything about loading payloads using Deja Vu. If I'm wrong I'll have no problems admitting it, but I just can't find anything.
I've been searching, and I can't find anything about loading payloads using Deja Vu. If I'm wrong I'll have no problems admitting it, but I just can't find anything.
not actual downgrade.
autorcm bypass stock fw and no efuse check
What made me update from 4.1 was that exfat update
Although autorcm is a little bit yikes, what makes people still wait for a coldbit exploit? It has the same usage
So how would one "downgrade" from 5.1.0 to 4.1.0 and have it permanent? AFAIK, the guide isn't super user friendly.
Title
I have a 128 gb sd card.Sounds like you didn't use an external card over 32GB on 4.1.0.
https://gbatemp.net/threads/update-to-use-sd-card-4-1-0.501327/
https://gbatemp.net/threads/switch-update-for-sdxc-exfat.498191/
Has there been a dev confirming Atmosphere or even Hekate will be ported to use this, or is it just speculation that this will be usable for more than just entering RCM without a jig?Hacks are loaded differently depending on what you are using. PegaSwitch for example was purely script based. It did not involve payloads. Payloads are used in the current exploit because of how the RCM is configured within the Switch. We first cause a stack smash and after that, some code is sent that is treated as properly signed due to the error we just created. It also must be sent via USB because in RCM, it can accept code from there. For Deja Vu, the closest thing would be the PS4 exploit where you navigate to a webpage and click on the appropriate links to boot hacks.