Hacked Switch not powering on at all after initialization after downgrade

  • Thread starter Thread starter jasper7474
  • Start date Start date
  • Views Views 2,339
  • Replies Replies 17

jasper7474

Member
Newcomer
Joined
Mar 16, 2025
Messages
6
Reaction score
2
Trophies
0
Age
18
XP
22
Country
United States
Problem: Nothing happens when I try to power the console on or enter RCM.

Background:
About two months ago I bought a V1 Switch from a friend with the intention to hack it. I did so successfully, and even successfully replaced the connector on the motherboard for the SD card reader when it broke. At one point, my games that I had on both my emuMMC and sysMMC were found to have corrupt data, and I wanted to start over and reinstall everything from a clean slate, so I restored the sysMMC backup I'd made. Turns out, that was a backup from when I had initially gotten the Switch, complete with all my friend's data and an older version of the OS (version 17.0.0, if I remember correctly). I was aware of e-fuses and the issue with burning them due to downgrades, but I wasn't too concerned since I knew that RCM would always work. It wasn't connected to the internet, so it didn't force me to update the system before initializing (factory resetting) it. As soon as it finished, the screen went black like it does normally, but it didn't come back on. I figured it was in RCM, but TegraRCMGUI didn't recognize it. I held the power button for 20 seconds for good measure, put in a paperclip, held volume up and pressed power, and nothing. No RCM. No backlight on the screen. Nothing.

Troubleshooting I've done so far:
As of writing, this happened about a month ago and it hasn't shown any signs of life since. I've since taken it apart and tested it with a multimeter and the pins on the right rail are excellent, ribbon cable on it is fine, etc. The battery, however, was at 2.4 volts, the cutoff voltage for charging the battery. I plugged in the official charger and it immediately began charging. After about 20 minutes it was holding the charge steadily, so the battery does not appear bad. I had also tried keeping the console on the official charger for 2+ days straight and then held the power button for over a minute and tried putting it in RCM and still nothing. I'm at my wits' end. Perhaps someone knows the solution.
 
Have you tried accessing maintenence mode i think you can update from there if your switch is connected to WiFi hold + and - while booting your switch.
 
this is a v2 correct ? i think v2's can't be downgraded if you burnt fuses (unlike fusee-geele which bypasses it entirely the only time you can dg on a v2 is if you upgraded via atmos/daybreak because that preserves the efuse count which you can only downgrade to the fw you upgraded from (ex you upgraded from 18.0.0 to 19.0.1 through daybreak you can only revert back to 18.0.0 basicly if the efuse count mismatches it'll kernel panic and fail to boot
 
this is a v2 correct ? i think v2's can't be downgraded if you burnt fuses (unlike fusee-geele which bypasses it entirely the only time you can dg on a v2 is if you upgraded via atmos/daybreak because that preserves the efuse count which you can only downgrade to the fw you upgraded from (ex you upgraded from 18.0.0 to 19.0.1 through daybreak you can only revert back to 18.0.0 basicly if the efuse count mismatches it'll kernel panic and fail to boot
This is a V1 unpatched Erista unit. As far as I know, RCM is something that always works regardless of the state of the e-fuses.
worm28:
Have you tried accessing maintenence mode i think you can update from there if your switch is connected to WiFi hold + and - while booting your switch.
I hadn't until you suggested it. I just tested that and nothing. I'm going to leave it on the charger for a while and try maintenance mode again later. Although it's unlikely, it very well may be a simple issue with the battery, although when I tested it yesterday night it seemed fine aside from being low voltage.
 
This is a V1 unpatched Erista unit. As far as I know, RCM is something that always works regardless of the state of the e-fuses.

I hadn't until you suggested it. I just tested that and nothing. I'm going to leave it on the charger for a while and try maintenance mode again later. Although it's unlikely, it very well may be a simple issue with the battery, although when I tested it yesterday night it seemed fine aside from being low voltage.
DO NOT USE PAPERCLIPS THEY WILL DAMAGE YOUR RAIL AND YOU WILL BE UNABLE TO ENTER RCM UNTIL YOU REPLACE IT, Use a jig, they are inexpensive
Post automatically merged:

And by the way, corrupt data is you missed the patches or the sys-patch sysmodule
 
DO NOT USE PAPERCLIPS THEY WILL DAMAGE YOUR RAIL AND YOU WILL BE UNABLE TO ENTER RCM UNTIL YOU REPLACE IT, Use a jig, they are inexpensive
Post automatically merged:

And by the way, corrupt data is you missed the patches or the sys-patch sysmodule
I do use a paperclip, used it quite a bit. I made sure that the pins were undamaged yesterday and confirmed that everything on the right joy-con rail is working properly. I'll look at buying a jig soon.
And yeah, I likely forgot to reinstall the sys-patches after reformatting my SD card and that's what caused the corrupt data. To be clear, the corrupt data thing was only a small part of why I wished to just start over.
 
after pressing the power button for 20 secs and try to enter on RCM mode what showns you on the injection program?
Miraculously, it worked this time, it is successfully in RCM. Nothing on the screen, but that can probably be solved by plugging its ribbon cable back in. Just yesterday, it wasn't doing anything at all even when I followed those exact steps.
1742163832129.png
 
  • Like
Reactions: impeeza and 6adget
Miraculously, it worked this time, it is successfully in RCM. Nothing on the screen, but that can probably be solved by plugging its ribbon cable back in. Just yesterday, it wasn't doing anything at all even when I followed those exact steps.View attachment 491348
Isn't that a great feeling? After hours of going over shit you know you've gone over multiple times before, just to have it work. You rack your brain trying to remember what you did differently this time. I'm happy you were able to get it working. I have truly lost count how many times kind, knowledgeable people on this website have helped me. Sure, there will always be those who will be negative and put you down for asking a question they believe the answer to be too obvious to ask. But for the most part it's a friendly home. I've been here since modding my original Xbox, and GBA. Ok, I'm done being cringe.
 
  • Like
Reactions: impeeza
Isn't that a great feeling? After hours of going over shit you know you've gone over multiple times before, just to have it work. You rack your brain trying to remember what you did differently this time. I'm happy you were able to get it working. I have truly lost count how many times kind, knowledgeable people on this website have helped me. Sure, there will always be those who will be negative and put you down for asking a question they believe the answer to be too obvious to ask. But for the most part it's a friendly home. I've been here since modding my original Xbox, and GBA. Ok, I'm done being cringe.
Yup, absolutely agree. With a little more poking and prodding, the screen still doesn't seem to be working. Not sure what to do at this point since the ribbon cable doesn't appear damaged and I've ensured it's inserted fully.
 
Yup, absolutely agree. With a little more poking and prodding, the screen still doesn't seem to be working. Not sure what to do at this point since the ribbon cable doesn't appear damaged and I've ensured it's inserted fully.
or the connector damaged, as all the connectors on the SOC of the console THEY ARE VERY LOW QUALITY and connecting and disconnecting will damage them, look inside the connector for bent or missing pins. also check the retro-illumination ribbon
 
sounds like the paperclip jig just wasnt actually making contact correctly

it booting to black screen on ofw makes sense if you had higher fuses, and being unable to enter rcm makes sense if you're using an unreliable method

you can get a proper jig if you want but you could just enable auto rcm instead

and if the screen is not working anymore after plugging it back in, make sure it's properly plugged in and that you didn't bend pins in the ribbon connector when trying to reconnect the screen... ask me how I know
 
  • Like
Reactions: impeeza
Yup, absolutely agree. With a little more poking and prodding, the screen still doesn't seem to be working. Not sure what to do at this point since the ribbon cable doesn't appear damaged and I've ensured it's inserted fully.
Even after you upload a payload to it?
 
In 2019 I downgraded my v1 switch fw and that's bricked my switch, I found a thread here that explained how to fix it (u need to manual boot the switch) it was a long process , it took me 4 hrs to do it , I wonder if someone can link us to that thread , I can't find it
 
In 2019 I downgraded my v1 switch fw and that's bricked my switch, I found a thread here that explained how to fix it (u need to manual boot the switch) it was a long process , it took me 4 hrs to do it , I wonder if someone can link us to that thread , I can't find it
You can search that tutorial here use the search bar at top of site, indeed they're two threads about that issue
 
  • Like
Reactions: KiiWii

Site & Scene News