Hacking Why is my RCM Jig not working?!

Status
Not open for further replies.
At least give him the safest directions to go along with it. Here CVFireDragon, a guide to using tin foil as safely as possible. Note: there will always be risks with using tin foil.

The instructions can easily be found on this site or a simple google search.
Apparently the Switch has internal short protection from what I've read, I mashed my foil in there good and no harm came of it. The major concern people have is foil flakes getting inside the unit but I didn't have that problem and have seen no proof of it either.
 
Last edited by Mr. Wizard,
If you used foil you'd be done by now...

Maybe. I haven't tried it because it just seems kinda ghetto. Also the joy con rail pins are seperated and slightly recessed. It's not guaranteed to make good contact. Also I'd worry about the foil ripping. Personally I just bent a paperclip in a way where I could touch pin 10 and the center screw of the joy con rail. It was kind of fiddly but I could do it consistently.

Edit: Before I got my jig of course.
 
Last edited by DocAmes1980,
Maybe. I haven't tried it because it just seems kinda ghetto. Also the joy con rail pins are seperated and slightly recessed. It's not guaranteed to make good contact. Also I'd worry about the foil ripping. Personally I just bent a paperclip in a way where I could touch pin 10 and the center screw of the joy con rail. It was kind of fiddly but I could do it consistently.
I only had to do it once. AutoRCM.
 
True. It's still nice to have a reliable jig because FW updates will remove AutoRCM.
And potential reports you to Nintendo when updating . Since a thing such as auto rcm can't be archived my normal means. Buts that's just my guess.
 
True. It's still nice to have a reliable jig because FW updates will remove AutoRCM.
How often do you update your FW to need to jig it? Why would you update the normal way and burn fuses?
The only safe way (for the moment) of updating FW without burning fuses also handles the AutoRCM issue.

And potential reports you to Nintendo when updating . Since a thing such as auto rcm can't be archived my normal means. Buts that's just my guess.
Do you have any proof?
This is fake news based on your opinion.
 
And potential reports you to Nintendo when updating . Since a thing such as auto rcm can't be archived my normal means. Buts that's just my guess.

It's possible that they could look for a corrupted boot0. If you were worried you could uninstall AutoRCM prior to updating. I'm not worried but I'm not too concerned about being banned anyways.
 
How often do you update your FW to need to jig it? Why would you update the normal way and burn fuses?
The only safe way (for the moment) of updating FW without burning fuses also handles the AutoRCM issue.


Do you have any proof?
This is fake news based on your opinion.
Don't you know what the word guess means?
 
  • Like
Reactions: Draxzelex
-snip-
if you think so then so be it...
Fact is nintendo is going to find ways to detetect hacks and will add more ways to so. A corrupted boot 0 is a sure way to tell so.
Since it isn't archivable by normal use and even if it happens by normal use it would result in a situation in which the normal user can't even begin the update process or boot the device to begin with . Hence they may could use this as a potential flag of they don't do so already.

But once again this is a guess based on what I would do if I where a software developer at Nintendo that needs to find ways to detect hackers.
 
Last edited by Quantumcat, , Reason: Remove deleted post quote
How often do you update your FW to need to jig it? Why would you update the normal way and burn fuses?
The only safe way (for the moment) of updating FW without burning fuses also handles the AutoRCM issue.

I don't care about burning fuses. I have no intention of downgrading. A warmboot exploit isn't worth all the hassle to me. When I need to reboot I just connect my phone, PC, or HTPC. All are setup to push the payload automatically. It would be neat to have the option, but pushing a payload via RCM is quicker and easier for my purposes.
 
I don't care about burning fuses. I have no intention of downgrading. A warmboot exploit isn't worth all the hassle to me. When I need to reboot I just connect my phone, PC, or HTPC. All are setup to push the payload automatically. It would be neat to have the option, but pushing a payload via RCM is quicker and easier for my purposes.

whats A warmboot exploit
 
An exploit that is triggered while the system is already running. A coldboot exploit on the other hand refers to an exploit that is triggered before the system turns on.
and what would happen if an exploit was triggered thank you already for your answer
 
and what would happen if an exploit was triggered thank you already for your answer
I don't understand the question. There are only 2 possibilities; either the exploit is triggered before the system is on (coldboot) or after the system is on (warmboot).
 
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum