Hacking Switch possible Bricked. Doesnt work after NAND restore.

  • Thread starter Thread starter Emeraldman94
  • Start date Start date
  • Views Views 20,270
  • Replies Replies 25

Emeraldman94

Well-Known Member
Member
Joined
Dec 22, 2008
Messages
386
Reaction score
10
Trophies
1
XP
778
Country
United States
Help. I have 6.1 sysNAND and 6.1 emNAND. Never use sysNAND.

the Switch boots up into RCM mode. Then I click emunand or custom firmware. Then the Nintendo screen flashes. Then Black screen. Then Nintendo Switch screen. IT then freezes on this screen and never moves on. Did I brick my switch????

I turn off my switch my holding the power for 15 seconds. Charge the SX pro. Then try again and always get the same results.

Auto RCM was on. I turned it off just in case.

I dont think Booting into Original firmware even works anymore EITHER!!!! I never used original firmware

I used Hekate to restore my eMMC BOOT0/1 and eMMC RAW GPP (Exfat only) from my original backup. It still doesnt work.

RCM is uninstalled. Booting the system with no SD card, No SXPro dongle, and No Jig results in No boot. booting into CFW from SXpro still has same Nintendo Switch logo hang. HELP
 
did you restore a nand backup that is older than the firmware you were using? if you have too many fuses blown, the switch wont boot older firmwares.
 
did you restore a nand backup that is older than the firmware you were using? if you have too many fuses blown, the switch wont boot older firmwares.

That is what I did. I just cant figure out how to get to 6.1 now from the 4.1 I am on since I cannot load CFW
 
That is what I did. I just cant figure out how to get to 6.1 now from the 4.1 I am on since I cannot load CFW

Have you tried Nintendo Recovery Mode? That can be used to update to the latest version, officially, which will burn your fuses. Additionally, if you have emuNAND on sysNAND it will be gone. Still, it's better than a brick. If you are using emuNAND on microSD card with SX Pro that will work when the next Beta comes out, but until then going to 6.2 will ALSO lead to a black screen if try to use emuNAND.

It would be nice if we had a tool to update the NAND dump with a PC tool. That would totally solve problems like this.

Anyway, the good news here is that if your Switch was never banned and if the NAND dump you used that screwed things up was from before you went to CFW, you will PROBABLY be good playing officially for a while. Better at least than if you tried running a recovery while mods were in place. Either way, I'd be curious to know how it goes.
 
Last edited by Elliander,
You don't need to make several threads about this. Maybe if you answered people's questions and followed directions in the other thread you might have it fixed by now.
 
Have you tried Nintendo Recovery Mode? That can be used to update to the latest version, officially, which will burn your fuses. Additionally, if you have emuNAND on sysNAND it will be gone. Still, it's better than a brick. If you are using emuNAND on microSD card with SX Pro that will work when the next Beta comes out, but until then going to 6.2 will ALSO lead to a black screen if try to use emuNAND.

It would be nice if we had a tool to update the NAND dump with a PC tool. That would totally solve problems like this.

Anyway, the good news here is that if your Switch was never banned and if the NAND dump you used that screwed things up was from before you went to CFW, you will PROBABLY be good playing officially for a while. Better at least than if you tried running a recovery while mods were in place. Either way, I'd be curious to know how it goes.


It doesnt load for me. Ive tried doing that when loading CFW and Horizon. It just goes to black room
 
It doesnt load for me. Ive tried doing that when loading CFW and Horizon. It just goes to black room

Different kind of recovery mode. You don't use the dongle, nor do you use a jig. It's this:

nintendo-switch-recovery-mode-640x480.jpg

  • Turn off the console by pressing the power button on top of the console for five seconds.
  • Press POWER button + Volume Up + Volume down at the same time.
  • Release all buttons when the Switch logo appears on the screen.
  • The console should now be in recovery mode with the option to update.
This SHOULD allow you to officially install the latest update, which will then allow the console to boot.
 
Different kind of recovery mode. You don't use the dongle, nor do you use a jig. It's this:

nintendo-switch-recovery-mode-640x480.jpg

  • Turn off the console by pressing the power button on top of the console for five seconds.
  • Press POWER button + Volume Up + Volume down at the same time.
  • Release all buttons when the Switch logo appears on the screen.
  • The console should now be in recovery mode with the option to update.
This SHOULD allow you to officially install the latest update, which will then allow the console to boot.

Right but the problem is nothing boots if the dongle isnt in. Screen doesnt even light up or anything unless I use jig and RCM
 
So, to be clear, you HAVE tried to do that? because the dongle is just an exploit on the recovery mode, but the recovery mode is it's own thing that is supposed to happen when nothing boots. That is to say, if you get to a point to decide what to boot into, you aren't in that mode. If RCM works, this should as well.
 
So, to be clear, you HAVE tried to do that? because the dongle is just an exploit on the recovery mode, but the recovery mode is it's own thing that is supposed to happen when nothing boots. That is to say, if you get to a point to decide what to boot into, you aren't in that mode. If RCM works, this should as well.

Right I did try. When I have No hib. no dongle no SD card. my switch wont even turn on or light up or anything

It only turns on when RCM mode is activated. Then when I boot original FW I hold down voluem up and down. Thats when it flashes at the switch screen but then goes to black screen
 
That's curious... and unfortunately, to the best of my knowledge, Hekate doesn't have a built in Homebrew launcher and SXOS has to load CFW to launch Homebrew. Now I'm curious to know if anyone knows how to run Choidujournx without being able to boot.

See, if you can get to the SX menu, recovery mode should work for you as well.

The good news, at least, is that if anyone ever does develop a way to install a firmware update manually from RCM your Switch should be recoverable so if nothing else I suggest holding onto it. Maybe request it as a feature from Hekate or Team Xecutor?

In the mean time, this is a valuable lesson: Always make a new NAND dump before and after making any kind of change, and keep detailed track of those backups. If space is a concern, both NAND dumps and emuNAND backups compress very well. My 15.0 GB emuNAND backup compresses to 1.54 GB with 7-zip (set to Ultra). Meanwhile a 29.1 GB NAND and/or emuNAND compresses to 2.12 GB. It's very easy to make multiple copies, and even though I wouldn't be able to install an old NAND after the fuses burn, I'd still be able to maintain them just in case some part of them is ever needed or useful.
 
You will need to perform the manual downgrade process, I own a repair/mod shop on my country and thats the process that I follow to install SX OS on 6.2 switches. Downgrade manually to 6.1, re do all partitions in balena/hacdiskmount as the guide says and you will hace CFW back and running. PM me if you need some help.
 
You will need to perform the manual downgrade process, I own a repair/mod shop on my country and thats the process that I follow to install SX OS on 6.2 switches. Downgrade manually to 6.1, re do all partitions in balena/hacdiskmount as the guide says and you will hace CFW back and running. PM me if you need some help.

What guide are you talking about? Why would I downgrade more if Im on 4.1? Im not on 6.2
 
https://guide.sdsetup.com/#/manualchoidowngrade this one, do the whole process, you are not doing it with the purpose of downgrading more but to repair your partitions and boot.

I do follow this but without much luck, it doesnt fix my issue. I do wonder if Im messing up at a step though. My hactools never dumps my keys in the appropriate format. I have to move them around. Not sure i thats the issue or if this is some harware issue.

Wat
 
I do follow this but without much luck, it doesnt fix my issue. I do wonder if Im messing up at a step though. My hactools never dumps my keys in the appropriate format. I have to move them around. Not sure i thats the issue or if this is some harware issue.

Wat
Reading this thread, use ReiNX, atmosphere or different payload(not tx)... flash boot0 see if boots, flash boot1 see if boots!!
My self not had to restore nand but sounds like boot0 or 1 if nothing on boot..
 
Reading this thread, use ReiNX, atmosphere or different payload(not tx)... flash boot0 see if boots, flash boot1 see if boots!!
My self not had to restore nand but sounds like boot0 or 1 if nothing on boot..

Ive done that. FLashing using Balena Etcher using the BOOT choi provides me. No luck. I try REINX Hekate atmosphere. No luck. Then I turn off ato RCM and retry all. Then try maintainence mode on all. No luck. Tried repairing GPT. no luck
 

Site & Scene News

Popular threads in this forum