Hacking Question I think i bricked my console

midstor

Well-Known Member
OP
Member
Joined
Aug 1, 2018
Messages
299
Trophies
0
Age
25
XP
797
Country
United States
So i tried installing 6.0.0 with ChiorDujorNX and all went well until i tried loading SXOS. After loading i was welcomed with a blank black screen.
I rushed to discord and users said to restore it. Is it my switch thats bricked or is it the cfw.
My fuse value is 5.1.0's fuse value i am currently transferring a nand backup to my sd card.
lets keep the un useful "you shouldn't have been messing with it" comments out.
idk what i did wrong or if its just CFW atm.

Edit:Some people are saying that its because i used the exFat option in ChoirDujorNX.

edit 2:Draxzelex says this
"So people don't follow suit, the way exFAT is enabled in 6.0 is different than other firmware and midstor updated to firmware 6.0 with exFAT. Now ChoiDujourNX has no idea how to properly add exFAT to 6.0 (thanks rajkosto) so it probably made a few unsafe assumptions and wound up semi-bricking the console. So in reality, neither SX OS nor firmware 6.0 bricked his Switch but in reality it was ChoiDujourNX. If you want to update using ChoiDujourNX, don't use exFAT until its supported officially." thank you

edit 3 I was able to recover the brick with a rawnand & boot 0/1 restore.
 
Last edited by midstor,

Scitzo

Well-Known Member
Newcomer
Joined
Sep 1, 2018
Messages
50
Trophies
0
XP
284
Country
United States
If your fuses are still at 5.1 values, then simply restore with your 5.1 backup and you're back off to the races bud.

As for 6.0, I'm not gonna -tell- you what to do, but I'd highly -recommend- not playing with fire until its understood completely. (Hint: 6.0 is fire).
 

midstor

Well-Known Member
OP
Member
Joined
Aug 1, 2018
Messages
299
Trophies
0
Age
25
XP
797
Country
United States
If your fuses are still at 5.1 values, then simply restore with your 5.1 backup and you're back off to the races bud.

As for 6.0, I'm not gonna -tell- you what to do, but I'd highly -recommend- not playing with fire until its understood completely. (Hint: 6.0 is fire).
I'm restoring atm i hope its not corrupted xD
 

midstor

Well-Known Member
OP
Member
Joined
Aug 1, 2018
Messages
299
Trophies
0
Age
25
XP
797
Country
United States
put back on boot.dat. same thing happened to me when i accidentally clicked the album during an ftp transfer
wdym, i installed 6.0.0 which messed up my sys

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

Crossing my fingers for you bud. I personally store each backup on three different mediums just to be extra safe.
I have 2 backups one of google drive one on my pc so lol i hope this fixes
 

Alex S

Creator Of WWHDM, And Metroid Fusion XER0X!
Member
Joined
May 2, 2016
Messages
695
Trophies
0
Location
Hell
Website
www.erm.wut
XP
1,002
Country
United States
so it was definitely an sx os brick. if your boot.dat size is anything other than 15kb (i.e. 32kb is what caused it for me) it will black screen and it basically disables loading the sx payload because its corrupted
 

midstor

Well-Known Member
OP
Member
Joined
Aug 1, 2018
Messages
299
Trophies
0
Age
25
XP
797
Country
United States
so it was definitely an sx os brick. if your boot.dat size is anything other than 15kb (i.e. 32kb is what caused it for me) it will black screen and it basically disables loading the sx payload because its corrupted
i get package1 errors when trying to load atmosphere via hekate or reinx so idk
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
19,006
Trophies
2
Age
29
Location
New York City
XP
13,372
Country
United States
So people don't follow suit, the way exFAT is enabled in 6.0 is different than other firmware and midstor updated to firmware 6.0 with exFAT. Now ChoiDujourNX has no idea how to properly add exFAT to 6.0 (thanks rajkosto) so it probably made a few unsafe assumptions and wound up semi-bricking the console. So in reality, neither SX OS nor firmware 6.0 bricked his Switch but in reality it was ChoiDujourNX. If you want to update using ChoiDujourNX, don't use exFAT until its supported officially.
 
  • Like
Reactions: Scitzo
D

Deleted User

Guest
If ChoiDuJourNX was open source we could fix it ourselves. Remind me again why something critical like ChoiDuJourNX is not open source?
 

midstor

Well-Known Member
OP
Member
Joined
Aug 1, 2018
Messages
299
Trophies
0
Age
25
XP
797
Country
United States
So people don't follow suit, the way exFAT is enabled in 6.0 is different than other firmware and midstor updated to firmware 6.0 with exFAT. Now ChoiDujourNX has no idea how to properly add exFAT to 6.0 (thanks rajkosto) so it probably made a few unsafe assumptions and wound up semi-bricking the console. So in reality, neither SX OS nor firmware 6.0 bricked his Switch but in reality it was ChoiDujourNX. If you want to update using ChoiDujourNX, don't use exFAT until its supported officially.
If ChoiDuJourNX was open source we could fix it ourselves. Remind me again why something critical like ChoiDuJourNX is not open source?
That is true, why isn't a firmware installer that can brick your system in 5 minutes open source?
 

ZachyCatGames

Well-Known Member
Member
Joined
Jun 19, 2018
Messages
3,398
Trophies
1
Location
Hell
XP
4,209
Country
United States
So people don't follow suit, the way exFAT is enabled in 6.0 is different than other firmware and midstor updated to firmware 6.0 with exFAT. Now ChoiDujourNX has no idea how to properly add exFAT to 6.0 (thanks rajkosto) so it probably made a few unsafe assumptions and wound up semi-bricking the console. So in reality, neither SX OS nor firmware 6.0 bricked his Switch but in reality it was ChoiDujourNX. If you want to update using ChoiDujourNX, don't use exFAT until its supported officially.
I updated to 6.0.0 exfat with ChoiDujourNX when it was first leaked and was able to start it with Hekate (with 6.0 support) and had no issues...
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • No one is chatting at the moment.
    Psionic Roshambo @ Psionic Roshambo: @SylverReZ, Indeed lol