Hacking Console won't boot after disabling AutoRCM?

Last_colossi

New Member
Newbie
Joined
Mar 10, 2020
Messages
2
Reaction score
0
Trophies
0
Age
35
XP
62
Country
Australia
Hi everyone,

This is my first post here but recently I've been repairing a switch (had to replace right joycon socket) and I found out it was in AutoRCM mode, so I ran TegraRCMGUI and got the console to boot to the hekate boot menu I think?, and it said "LP0 and Missing or No Minerva" even though I had all the files on the SD card it was formatted in exfat from another switch (so maybe it was in the wrong format), anyway I just wanted to boot the console normally so I disabled AutoRCM and chose "reboot (normal)" and it just turned off and now it won't boot and obviously AutoRCM can't be detected by TegraRCMGUI.

I don't know what to do, should I buy an RCMLoader dongle and try to boot it into RCM again with a Fat32 SD format or something?, because I've tried holding down the power button for 15 second, 30 seconds and volume up but nothing's working and now it won't turn on.

(the boot menu said the battery was at 100%)
 
If you turned off AutoRCM, you need a Jig or something like that, to get into RCM-Mode. You don't need the RCMLoader as long as you can send the payloads with TegraRCMGui, for example. Search for a guide for entering the RCM Mode.
You wrote, that you replaced the right joycon socket. Could that be the cause of the problem?
 
  • Like
Reactions: MrMcTiller
If you turned off AutoRCM, you need a Jig or something like that, to get into RCM-Mode. You don't need the RCMLoader as long as you can send the payloads with TegraRCMGui, for example. Search for a guide for entering the RCM Mode.
You wrote, that you replaced the right joycon socket. Could that be the cause of the problem?

Thanks for the reply, I just ordered a jig. I bought the console used and the previous owner had basically destroyed the socket on the MB that the Joy-con rail connects to, I replaced it with a new one and reassembled the console. It wouldn't turn on so I charged it over night and read up about autoRCM and dead batteries, I then formatted a micro SD card with my main switch and copied over all the Kosmos files, then ran TegraRCMGui and thankfully it recognised it perfectly and I was able to load the Hekate payload and boot the console into the RCM? boot menu, but yeah after I rebooted in "normal" mode it won't turn on at all. Even if the socket is still non-functional it should still boot right? I don't know why it would boot into the RCM/Hekate menu and yet not reboot after...

Is there something to do with fuses that won't let the console boot or something?
 
Burned fuses can be the cause of OFW not booting, but for this scenario you have to first start the OFW with a newer firmware, so the fuses would burn and then you would have to restore a NAND backup with an older firmware. So then you only could start the switch with a CFW. To be able to start the OFW again, you would have to update the firmware to a version which correponds to the number of burned fuses. So as you bought the console used, it could be possible, that more fuses were burned in the past and the last owner went back to an older firmware. That would explain, why you cannot boot into OFW.

Nevertheless you have to get back into RCM mode to do anything right now. So I think, you have to wait for the jig.
On the other hand you can look here: https://gbatemp.net/threads/the-ultimate-list-of-mods-to-enter-rcm.502145/
I used a paperclip to get into RCM mode: https://gbatemp.net/threads/paperclip-rcm-jig.502087/
 
Last edited by Calahan,

Site & Scene News

Popular threads in this forum