Build a time machine.
Stay offline until the community creates better tools to wipe traces of hacking form the NAND
It is not easy to enter RCM admittedly. Have you following the following video on how to properly use tinfoil?
No, only a clean NAND made before hacking can remove all traces of hacking so far.
hi, I have a question. Is it possible to launch hekate menu directly from Rajnx cfw? I usually go into rcm and inject the payload again, but it would be more convenient without doing it. Thank you in advance
Last edited by fallingrat,
Question as I'm a noob to the switch scene for modding and if my question can't get answered here someone could point me in the right direction to go to I baught a jig and it said it was made with 24 ag wire is that better than a paper clip by chance thanks in advance
Completely new to the switch hacking scene, been sitting on these consoles for my kids for months now..
I have 3 total.
2 are on 4.0.1
1 is on 2.1.0
Still waiting to determine which solution I will go with and possibly purchase. Was waiting for things to mature a bit more.. Was hoping for some type of cold boot jig that I could solder in the switches.
In the meanwhile, if I want to keep these as low as possible firmware wise with the hopes of some cold boot hack that is not "tethered" my questions are:
1. Is there any risk in me updating the 2 on 4.0.1 to 4.1.0? Meaning if some coldboot hack does come out in the future, is being on 4.0.1 compared to 4.1.0 really likely going to matter?
2. If not, can I update to 4.1.0 without purchasing a game? If so, how?
3. For my switch on 2.1.0, is there any value on staying at 2.1.0? If I am just as likely to get a coldboot hack being on 2.1.0 compared to 4.0.1/4.1.0, I mine as well update it to be the same as the other two.
Thanks in advance for any help.
I have 3 total.
2 are on 4.0.1
1 is on 2.1.0
Still waiting to determine which solution I will go with and possibly purchase. Was waiting for things to mature a bit more.. Was hoping for some type of cold boot jig that I could solder in the switches.
In the meanwhile, if I want to keep these as low as possible firmware wise with the hopes of some cold boot hack that is not "tethered" my questions are:
1. Is there any risk in me updating the 2 on 4.0.1 to 4.1.0? Meaning if some coldboot hack does come out in the future, is being on 4.0.1 compared to 4.1.0 really likely going to matter?
2. If not, can I update to 4.1.0 without purchasing a game? If so, how?
3. For my switch on 2.1.0, is there any value on staying at 2.1.0? If I am just as likely to get a coldboot hack being on 2.1.0 compared to 4.0.1/4.1.0, I mine as well update it to be the same as the other two.
Thanks in advance for any help.
SX OS Pro and GameCart Update? Any way around it updating Game Cart if using SX OS and does it really matter?
So it seems there is no way to use SX OS/Pro while also preventing the GameCart from updating when updating firmware (using ChoiDuJourNX or any other noburn method)? I am planning to use ChoiDuJourNX to update them fimrware from 3.0.0 to 5.1.0 without burning fuses and I see a lot of people talking about using a different CFW (Hekate, etc) with PreventGCUpdate (since SX OS doesn't have PreventGCUpdate). Is there any reason to consider doing this until SX OS adds a PreventGCUpdate? Is there any potential reason that having the GC stay at a lower firmware version could be beneficial? I've been trying to think why so many people care about that and can't figure it out. It seems having the GC working on the current FW would be more beneficial anyway (and if a new exploit comes out, we could always downgrade FW if needed, setup that method, then upgrade FW back and then GC should work fine again).
I would probably never use the Game Carts anyway since I don't use physical carts usually, but just want to make sure I'm not missing anything before doing this update and having the GC Update permanent. I'm assuming any future boot method, untethered exploit, etc most likely wouldn't be effected by the GC version and I would still be able to downgrade back to 3.0.0 if necessary since no fuses burned by FW.
So it seems there is no way to use SX OS/Pro while also preventing the GameCart from updating when updating firmware (using ChoiDuJourNX or any other noburn method)? I am planning to use ChoiDuJourNX to update them fimrware from 3.0.0 to 5.1.0 without burning fuses and I see a lot of people talking about using a different CFW (Hekate, etc) with PreventGCUpdate (since SX OS doesn't have PreventGCUpdate). Is there any reason to consider doing this until SX OS adds a PreventGCUpdate? Is there any potential reason that having the GC stay at a lower firmware version could be beneficial? I've been trying to think why so many people care about that and can't figure it out. It seems having the GC working on the current FW would be more beneficial anyway (and if a new exploit comes out, we could always downgrade FW if needed, setup that method, then upgrade FW back and then GC should work fine again).
I would probably never use the Game Carts anyway since I don't use physical carts usually, but just want to make sure I'm not missing anything before doing this update and having the GC Update permanent. I'm assuming any future boot method, untethered exploit, etc most likely wouldn't be effected by the GC version and I would still be able to downgrade back to 3.0.0 if necessary since no fuses burned by FW.
Hekate's menu is built into the payload but that payload goes away once you select launch firmware. That is because that payload exists in RCM only and we have no means of re-entering RCM without turning off the console. Although I did spot this new homebrew that can reboot the console for you but it seems like a work-in-progress: https://gbatemp.net/threads/bootmoix-a-simple-shutdown-reboot-homebrew.514467/
I...don't know unfortunately. I personally use a paperclip and its very finicky. Sometimes it boots RCM on the first try and other times it takes maybe an hour. I trust most jigs more than paperclips, but the problem with jigs is that they are harder to modify. As long as the reviews (if any) say they are good, then that should be good enough.
First of all, I'd like to preface my response that most of this information could have been found in the pinned Firmware Status thread so I am assuming you did not go there first. I have listed it below in case you are not aware of what I am talking about but for future reference, you should consult that thread first before asking a question here.
- Firmwares 3.0.1-4.1 have access to the same exploit so switching between firmwares in this set will not alter your chances of getting said exploit. Also, these firmwares have access to a warmboot not a coldboot. There is only a theoretical coldboot up to 3.0.1 but no one has achieved it thus far (and possibly no one may be interested). Sources:
https://gbatemp.net/attachments/firmware-status-chart-png.137601/
- https://gbatemp.net/threads/choiduj...ller-homebrew-for-the-nintendo-switch.513416/
- It will likely get its own warmboot exploit before firmwares 3.0.1-4.1 get theirs so I would consider it worth staying on. However, we have a means of updating without burning fuses (see #2) so you can retain your ability to load 2.1 while being on the latest firmware. If you don't know what fuses are, they are literal microscopic fuses embedded in your console to prevent downgrading. This is accomplished by burning new fuses during certain system updates. To prevent fuses from being burned when running a foreign firmware, you must boot into RCM first and use a substitute bootloader.
Another noob question 
To run payloads in RCM would a charging switch cable do the trick? Or needs to be a data cable usb c to a?
Like this one
https://www.ardistel.com/producto.asp?d=8431305027102
To run payloads in RCM would a charging switch cable do the trick? Or needs to be a data cable usb c to a?
Like this one
https://www.ardistel.com/producto.asp?d=8431305027102
What are XCI Files and how they ae used? What are NSP Files and how they are used?
--------------------- MERGED ---------------------------
i took the one frompro controller
--------------------- MERGED ---------------------------
Another noob question
To run payloads in RCM would a charging switch cable do the trick? Or needs to be a data cable usb c to a?
Like this one
https://www.ardistel.com/producto.asp?d=8431305027102
i took the one frompro controller
Any USB-C cable should be fine however I would exercise caution with third party products that claim they work with the Switch. A lot of people were bricked with 3rd party docks due to them lacking the 56k ohm resistor. As a good reference, this is the cable I use although 6.6 feet is a bit long in retrospect: https://www.amazon.com/gp/product/B00S8GU544/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1Another noob question
To run payloads in RCM would a charging switch cable do the trick? Or needs to be a data cable usb c to a?
Like this one
https://www.ardistel.com/producto.asp?d=8431305027102
.XCI files are retail Switch cartridge dumps while .NSP are (usually) retail Switch eShop dumps. .XCI files can only be used raw with an activated SX OS. .NSP files must be installed with a title installer before they can be used (e.g. Tinfoil, Rommenu, DevMenu) along with a CFW that has ES (Eticket Service) patching so the .NSP files can be launched. An activated SX OS can accomplish this as well as ReiNX, RajNX, and Atmosphere/Hekate with sig patches.
Is there any way (tools) to verify what update version an extracted (from xci) update folder is from a game?
I have been following the guide to get exfat support on the switch and the switch I am going to do this on is version 2.1.0. The guide mentions both Mario Plus Rabbids Kingdom Battle and Cars 3 as having version 2.1.0 update.
When I extract the update folder from both, they have different # of files and the size of each file varies, so I am guessing one of these I extracted is not actually 2.1.0.
I have been following the guide to get exfat support on the switch and the switch I am going to do this on is version 2.1.0. The guide mentions both Mario Plus Rabbids Kingdom Battle and Cars 3 as having version 2.1.0 update.
When I extract the update folder from both, they have different # of files and the size of each file varies, so I am guessing one of these I extracted is not actually 2.1.0.
Any charging cable can also transfer data/payloads but without the 56k ohm resistor, it might fry the Switch. In fact, this caused a console to become bricked when running the CFW RajNX.
You can use choidujourNX as I believe it analyzes the firmware packages before installation.
Plugging in the Switch to your computer doesn't allow the transfer of files. That must all be done by repeatedly removing and reinserting the SD card. Alternatively, you can use the memloader payload when the Switch is in RCM if its too much of a hassle but the speed is hard capped.
Click the link I posted. The USB Cable should have it written somewhere in its product description. If its not there, then chances are it doesn't have that resistor.
-
K3Nv2
-
DinohScene
That cat suit twink -
Veho
-
-
-
-
@
SylverReZ:
@Maximumbeans, Indeed. I've been working on getting this Infecutus chip to work on my PS2. But after soldering, I realised that a plastic piece was missing from the power ribbon cable to the power and eject buttons. -
@
SylverReZ:
Now I could go with soldering the contacts from the cable to the connector on the mobo, but doesn't sound like a good permanent solution.
-
@
Maximumbeans:
Man, that's beyond my brain I'm no good with hardware for now. I'd like to get into hardmods in future though -
@
SylverReZ:
@Maximumbeans, Maybe start practice soldering. Get a cheap-ass soldering iron and follow some good YouTube tutorials.+1
-
@
SylverReZ:
Least my experience has gotten better than over a decade ago. My iron would constantly bump into components and break them.
-
@
Maximumbeans:
Sounds good. I actually did soldering but like 16 years ago for school so uuuuh probably rusty haha
-
@
SylverReZ:
@Maximumbeans, Same here. I did soldering at school from a teacher who I honestly liked since he had plenty of good electronics experience.+1
-
-
-
-
-
@
SylverReZ:
It was like all clear and fancy. Tbf I'm not too experienced with chess, but would like to learn someday.
-
-
-
-
-
-
-
-
-
-