Hacking Possibly bricked my switch. NEED HELP!

  • Thread starter Thread starter Covertrose4
  • Start date Start date
  • Views Views 14,782
  • Replies Replies 46
Alright. I’ll def see what I can do. It will probs require a lot of troubleshooting. Thanks for all the help you guys have gave btw. Hopefully I can get it working
 
So I'm stuck. I am able to load into the SXOS bootloader. I tried making an Emunand and that wouldn't work. I also tried adding the ReinX payload to my SD card and that just cause my switch to act funny so I deleted the ReinX.bin file and did some restarts and got it working. But whenever I try to load into either custom firmware or original firmware nothing works. I can't seem to get Hekate or ChoiDujour. Should I just wait for Team Xecutor to release a version of SXOS that supports firmware version 7.0.0? Because I feel totally helpless and don't know what to do.
 
Lol, update...
So I saw another thread about a supposedly "bricked" switch and installing AutoRCM made me able to get a blue screen when clicking on either the CFW or OFW button on the SXOS bootloader. So I'm getting somewhere. What it feels like is I am able to try booting into a firmware, but I feel like there is no firmware there, if that makes any sense.
 
So I'm stuck. I am able to load into the SXOS bootloader. I tried making an Emunand and that wouldn't work. I also tried adding the ReinX payload to my SD card and that just cause my switch to act funny so I deleted the ReinX.bin file and did some restarts and got it working. But whenever I try to load into either custom firmware or original firmware nothing works. I can't seem to get Hekate or ChoiDujour. Should I just wait for Team Xecutor to release a version of SXOS that supports firmware version 7.0.0? Because I feel totally helpless and don't know what to do.


Lol, update...
So I saw another thread about a supposedly "bricked" switch and installing AutoRCM made me able to get a blue screen when clicking on either the CFW or OFW button on the SXOS bootloader. So I'm getting somewhere. What it feels like is I am able to try booting into a firmware, but I feel like there is no firmware there, if that makes any sense.


Can you boot OFW normally or does it also blue screen? If you can boot OFW normally can you tell me what firmware version it is on.

If you cannot boot OFW normally (normally = no payload, no rcm) then you will need to rebuild your nand. This is a complex and long process but I'm willing to help guide you through it
 
Can you boot OFW normally or does it also blue screen? If you can boot OFW normally can you tell me what firmware version it is on.

If you cannot boot OFW normally (normally = no payload, no rcm) then you will need to rebuild your nand. This is a complex and long process but I'm willing to help guide you through it

Hi! I'm just seeing this now, but I have just started to try fixing my switch because I noticed SXOS 2.6.1 beta was released. I used Hekate to check some stuff out and I have 9/64 fuses burnt. I believe i was running 7.0.0 or 7.0.1 before this all happened. I accidentally updated it and it just fried everything. I blue screen when I load into OFW and CFW, they won't boot into anything. Its almost like I have no OS on my switch. Its as if you were on Windows 8, upgraded to Windows 10, but then ur computer just won't boot into any operating system anymore and you lost everything after updating. I feel like I definitely need to rebuild my NAND. Because I do not seem to have one. I never made a NAND backup either so there's no way I can possibly restore it.
 
Hi! I'm just seeing this now, but I have just started to try fixing my switch because I noticed SXOS 2.6.1 beta was released. I used Hekate to check some stuff out and I have 9/64 fuses burnt. I believe i was running 7.0.0 or 7.0.1 before this all happened. I accidentally updated it and it just fried everything. I blue screen when I load into OFW and CFW, they won't boot into anything. Its almost like I have no OS on my switch. Its as if you were on Windows 8, upgraded to Windows 10, but then ur computer just won't boot into any operating system anymore and you lost everything after updating. I feel like I definitely need to rebuild my NAND. Because I do not seem to have one. I never made a NAND backup either so there's no way I can possibly restore it.

okay, despite been broken, make a nand backup now, then follow the manual downgrade guide. I'm not responsible if for your actions in doing and for the love of god if you do it, do not format
 
Uhhhhhh how do I do that lol...?

--------------------- MERGED ---------------------------

Should I hit Dump NAND in the SXOS?
 
Uhhhhhh how do I do that lol...?

Follow this at your own risk. Read it all. You will be downgrading to 6.1 then need to update after if you want. You will need a way to enter RCM with this as well.

Manual Choi Downgrade

--------------------- MERGED ---------------------------

hekate, also dump boot0/1
 
Follow this at your own risk. Read it all. You will be downgrading to 6.1 then need to update after if you want. You will need a way to enter RCM with this as well.

Manual Choi Downgrade

--------------------- MERGED ---------------------------

hekate, also dump boot0/1

Well im already lost. I already backed up boot0/1 using hekate. But Idk what to do about getting a keys.txt because Biskeydump doesnt do anything. whenever I load into it it just crashes or something
 
Well im already lost. I already backed up boot0/1 using hekate. But Idk what to do about getting a keys.txt because Biskeydump doesnt do anything. whenever I load into it it just crashes or something

There are three methods for getting biskeys, one with biskeydump, one with lockpick_rcm and the other by dumping fuse info and stuff and uploading it to the guide
 
There are three methods for getting biskeys, one with biskeydump, one with lockpick_rcm and the other by dumping fuse info and stuff and uploading it to the guide
There are three methods for getting biskeys, one with biskeydump, one with lockpick_rcm and the other by dumping fuse info and stuff and uploading it to the guide

I’ve managed to get the Keys.txt file backed up but I’m working on backing up the eMMC RAW GPP. I have more than 32GB storage so I should be fine. Not sure if it’s stuck or the process takes a very long time but I’m leaving the switch on the dock overnight night and I’ll check to see if it backed up the eMMC RAW GPP. Hopefully I’m on the right path!
 

Attachments

  • image.jpg
    image.jpg
    761.3 KB · Views: 156
I’ve managed to get the Keys.txt file backed up but I’m working on backing up the eMMC RAW GPP. I have more than 32GB storage so I should be fine. Not sure if it’s stuck or the process takes a very long time but I’m leaving the switch on the dock overnight night and I’ll check to see if it backed up the eMMC RAW GPP. Hopefully I’m on the right path!

yeah it takes around an hour to do the backup normally iirc
 
There are three methods for getting biskeys, one with biskeydump, one with lockpick_rcm and the other by dumping fuse info and stuff and uploading it to the guide
So I'm not sure how to use choidujour and it didn't seem to do what it described. I have nothing in the "fw" folder. it says to put the "firmware .ZIP file to the newly created fw folder." I dont know what files i need to put in. So far ive gotten the Keys.txt file, and ive backed up the eMMC RAW GPP.

--------------------- MERGED ---------------------------

Also not sure of what to do because I use SXOS and no other types of CFW

--------------------- MERGED ---------------------------

I guess what im trying to say is im not sure what to put in the "fw" folder
 

Attachments

  • InkedCapture_LI.jpg
    InkedCapture_LI.jpg
    1.6 MB · Views: 161
Ooooooohhhhhhh... I think i mightve found what i needed from the "dark" site. For fw

--------------------- MERGED ---------------------------

Ummmm so ive tried using OFW versions 6.1.0, 6.2.0, 7.0.0, 7.0.1 and all of them don't work and they fail to match the "keys." It says failed to execute script ChoiDujour
 
Ooooooohhhhhhh... I think i mightve found what i needed from the "dark" site. For fw

--------------------- MERGED ---------------------------

Ummmm so ive tried using OFW versions 6.1.0, 6.2.0, 7.0.0, 7.0.1 and all of them don't work and they fail to match the "keys." It says failed to execute script ChoiDujour
ive also used keys.txt files from both the biskey and lockpick methods and neither work
 
So far I have created an "NX-6.1.0_exfat" folder which contains the firmware update. I kept seeing people are supposed to use their own keys.txt file but mine clearly didn't work. So I found someone online who posted their keys and "fw" folder and people on the forum said it worked. It worked for me and I was able to make a 6.1.0 firmware update with choidujour. all I had to do was replace the TSEC key with my own set of numbers. Right now I'm at STEP 5 of the guide but nothing shows up in device manager under "disk drives even after i hit ums_boot0.ini in the memloader.bin payload. This guide is very difficult
 
Last edited by Covertrose4, , Reason: Do not posts warez

Site & Scene News

Popular threads in this forum