Hacking Need help with switch that wont boot

rubyred

Member
OP
Newcomer
Joined
Feb 10, 2019
Messages
5
Trophies
0
Age
36
XP
57
Country
United States
I am in a bit of a pickle. Recently I was attempting to link a Nintendo account to my switch using the methods discussed in a thread on here. Before making any changes to my nand I made sure to back it up. When I made this backup I was on firmware 6.1.0. I made a number of changes but was never able to get the linked account working. So, after getting frustrated, I instead decided to create my own Nintendo account and go online for a minute to link it. I did so and immediately went offline after linking the account. After this I decided to update a bunch of homebrew apps as well. Now keep in mind this was a while ago so I do not fully remember all of the changes I made. Once I finished my updates I attempted to launch a game and it wouldn't launch due to corrupt save data (likely due to modifying my nand earlier). At this point I had been working on this for a day and decided to take a much needed break.



Cut to today. I decided to work on this again and thought back to the last day I was working on this. I figured I could just restore the nand backup and everything should be back to how it was before the changes. So I tried that, but unfortunately after the update the system no longer powers on. I can still boot into rcm and load hekate, but the system will not boot normally. I started to think back to the last day I worked on it and I cant remember if I updated firmware (I always use ChoiDujour to update) to 6.2.0. So I checked my fuses and sure enough I have 8 burnt fuses. Now I am not sure what to do, I figured I should attempt to downgrade and found some threads saying that was not possible. Then I found a website showing how to downgrade manually with choidjuour, but I am not sure if that will even work now that I have restored. Just looking for some guidance on whether or not its possible to resurrect this thing.



In short I have a nand backup from 6.1.0. I have 8 burnt fuses. My switch will only boot into RCM after restoring said nand backup. At this point I am unsure what to do and am looking for some guidance.



Thanks in advance for any help that you can provide.
 

Kubas_inko

"Something funny goes here."
Member
Joined
Feb 3, 2017
Messages
6,324
Trophies
1
Age
24
Location
I gues on earth.
XP
5,180
Country
Czech Republic
1. You probably found this site and that method does work.
2. What files you have in that backup (boot0/1 and rawnand.bin?)
3. 8 fuses = 6.2.0. So if you restored 6.1.0, you have to boot through RCM and bootloader which skips fuse check (any bootloader you can find).

So if you have restored full 6.1.0 backup, you probably really just need to boot through RCM and then update to 6.2.0 again.
 
Last edited by Kubas_inko,
  • Like
Reactions: rubyred

rubyred

Member
OP
Newcomer
Joined
Feb 10, 2019
Messages
5
Trophies
0
Age
36
XP
57
Country
United States
I backed everything up that I could using hekate 4.6. Here are the contents of the backup folder.

FILES
BOOT0
BOOT1
rawnand.bin

DIRECTORIES
dumps:
01/01/2018 12:00 AM 764 fuses.bin
01/01/2018 12:00 AM 576 kfuses.bin
01/01/2018 12:00 AM 48 tsec_keys.bin
partitions:
01/01/2018 12:00 AM 8,388,608 BCPKG2-1-Normal-Main
01/01/2018 12:00 AM 8,388,608 BCPKG2-2-Normal-Sub
01/01/2018 12:00 AM 8,388,608 BCPKG2-3-SafeMode-Main
01/01/2018 12:00 AM 8,388,608 BCPKG2-4-SafeMode-Sub
01/01/2018 12:00 AM 8,388,608 BCPKG2-5-Repair-Main
01/01/2018 12:00 AM 8,388,608 BCPKG2-6-Repair-Sub
01/01/2018 12:00 AM 4,176,896 PRODINFO
01/01/2018 12:00 AM 4,194,304 PRODINFOF
01/01/2018 12:00 AM 67,108,864 SAFE
01/01/2018 12:00 AM 2,684,354,560 SYSTEM
01/01/2018 12:00 AM 27,917,287,424 USER
pkg1:
01/01/2018 12:00 AM 94,176 nxloader.bin
01/01/2018 12:00 AM 262,144 pkg1_decr.bin
01/01/2018 12:00 AM 75,776 secmon.bin
01/01/2018 12:00 AM 4,960 warmboot.bin
pkg2:
01/01/2018 12:00 AM 2,425,556 ini1.bin
01/01/2018 12:00 AM 465,688 kernel.bin
01/01/2018 12:00 AM 2,891,244 pkg2_decr.bin


I also have biskey dumps. How can I boot via hekate? Is there a way to boot into OFW from hekate?
 

rubyred

Member
OP
Newcomer
Joined
Feb 10, 2019
Messages
5
Trophies
0
Age
36
XP
57
Country
United States
Not sure why I hadnt tried booting CFW. It works when booting the newest reinx. If I update to 6.2 will it boot normally again? Really appreciate the help, was getting to the point where I was scared and just needed someone to verify everything I was doing was correct.
 

rubyred

Member
OP
Newcomer
Joined
Feb 10, 2019
Messages
5
Trophies
0
Age
36
XP
57
Country
United States
Ok so I ran into the same corrupted save problem after updating to 6.2. Since I first loaded CFW sometime last year I was under the impression I could just turn off autorcm and it would boot into ofw and everything would work fine. Now I am starting to wonder if I had the wrong impression.

Here was my process this time.
Restore 6.1.0 nand backup.
Boot reinx.
Load 6.2 with ChoiDujour
Shut off autorcm.
Boot normally.
This is where all of my games say that the saves are corrupt.

At this point I know I messed up by shutting off autorcm the first time as it burned my fuses (not really sure if that matters too much). I only did it so that I could boot without cfw to connect to the network and link a nintendo account.

Unfortunately I didn't try loading reinx first to see if the corrupt save issue persisted. I am restoring nand again and will load reinx first after 6.2 update to check.
 

Adran_Marit

Walküre's Hacker
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,551
Country
Australia
Ok so I ran into the same corrupted save problem after updating to 6.2. Since I first loaded CFW sometime last year I was under the impression I could just turn off autorcm and it would boot into ofw and everything would work fine. Now I am starting to wonder if I had the wrong impression.

Here was my process this time.
Restore 6.1.0 nand backup.
Boot reinx.
Load 6.2 with ChoiDujour
Shut off autorcm.
Boot normally.
This is where all of my games say that the saves are corrupt.

At this point I know I messed up by shutting off autorcm the first time as it burned my fuses (not really sure if that matters too much). I only did it so that I could boot without cfw to connect to the network and link a nintendo account.

Unfortunately I didn't try loading reinx first to see if the corrupt save issue persisted. I am restoring nand again and will load reinx first after 6.2 update to check.

If it didn't work or you need a hand feel free to comment over here
https://gbatemp.net/threads/switch-7-0-downgrade-to-6-2-tutorial.530135/
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Xdqwerty @ Xdqwerty: