Hacking My switch is dead

  • Thread starter Thread starter nico00
  • Start date Start date
  • Views Views 3,499
  • Replies Replies 16

nico00

Member
Newcomer
Joined
Dec 8, 2019
Messages
5
Reaction score
0
Trophies
0
Age
19
XP
83
Country
Italy
Hi, today i started modding my nintendo switch, i did a backup on the version 9.0.1 and, after starting atmosphere, i accidentally updated the console to the version 9.1.0.
Then i used hekate to restore the precedent backup but after trying to restart the ofw the console showed a black screen and doesn't turn up.
If i put it in the dock, it shows the light but it instantly disappears. What can i do?
 
Hi, today i started modding my nintendo switch, i did a backup on the version 9.0.1 and, after starting atmosphere, i accidentally updated the console to the version 9.1.0.
Then i used hekate to restore the precedent backup but after trying to restart the ofw the console showed a black screen and doesn't turn up.
If i put it in the dock, it shows the light but it instantly disappears. What can i do?


TRY SENDING A PAYLOAD YOU MAYBE IN AUTORCM

Did you restore the boot0 and boot1 also. ?
need to use the boot0 and boot1 that matches the backup.

Or your in autorcm if you installed or enabled auto rcm..
How did you upgrade ?
 
Last edited by Canna,
His console does not boot now, so it matters :S
I meant, why did it matter that he updated to 9.1.0 in the first place. At the time of this post Atmosphere had already been updated to support it, so he had no reason to restore his backup. But if he was using an old version of Atmosphere he should still try booting with it incase he burned fuses or something and that's what is preventing him from booting stock.
 
I meant, why did it matter that he updated to 9.1.0 in the first place. At the time of this post Atmosphere had already been updated to support it, so he had no reason to restore his backup. But if he was using an old version of Atmosphere he should still try booting with it incase he burned fuses or something and that's what is preventing him from booting stock.
agreed, but if he didn't know he didn't know, but now he is semi bricked..
And im guessing hey didnt backup the boot0/1 and restore them..
But see what happens.
 
Is it possible for this to happen to an unmodded switch because mine stopped working after the update (9.1.0) and no longer wants to boot up... kinda weird how I search up “9.1.0 update switch not working” only shows hacked switches being affected like you. I need answers :(
 
I never backed my system nand nor used emunand.

I just update my hacked system to the latest version via the homebrew app and put the latest SX OS and that is it.

Stop doing unnecessary things.
 
I never backed my system nand nor used emunand.

I just update my hacked system to the latest version via the homebrew app and put the latest SX OS and that is it.

Stop doing unnecessary things.

Making a backup of your nand is not unnecessary, it's essential. A few months ago, quite a lot of SX OS users had soft bricked their Switches, since an update caused issues with ChoiDujourNX.

The only way out for many, was to rebuild their nand with ChoiDujour, which takes about an hour and is quite complex to non technical users.

tl; dr; Backup your nand. It's the life insurance for your Switch.
 
Last edited by Taorn,
Making a backup of your nand is not unnecessary, it's essential. Not long ago quite a lot of SX OS users that had soft bricked their Switches, since an update caused errors with ChoiDujourNX.

The only way out for many, was to rebuild their nand with ChoiDujour, which takes about an hour and is quite complex to non technical users.

tl; dr; Backup your nand. It's the life insurance for your Switch.
Hmm ok I will in the future.
 
TRY SENDING A PAYLOAD YOU MAYBE IN AUTORCM

Did you restore the boot0 and boot1 also. ?
need to use the boot0 and boot1 that matches the backup.

Or your in autorcm if you installed or enabled auto rcm..
How did you upgrade ?
TRY SENDING A PAYLOAD YOU MAYBE IN AUTORCM

Did you restore the boot0 and boot1 also. ?
need to use the boot0 and boot1 that matches the backup.

Or your in autorcm if you installed or enabled auto rcm..
How did you upgrade ?

Yes. I upgraded my switch from the home
 
You should always get into RCM unless you have hardware issues..

Try another RCM method, Jig and or cable...

Rcm is built into the chip.

Rcm Doesnt need a sd card or a nand(emmc) module..

So your issue is with your rcm method. Driver or cable...


And i asked about boot0 and boot 1 above < did you restore these in hekate ?Did you back them up When you made nand backup ?
 
Last edited by Canna,
You should always get into RCM unless you have hardware issues..

Try another RCM method, Jig and or cable...

Rcm is built into the chip.

Rcm Doesnt need a sd card or a nand(emmc) module..

So your issue is with your rcm method. Driver or cable...


And i asked about boot0 and boot 1 above < did you restore these in hekate ?Did you back them up When you made nand backup ?
Yes, i restored and backupped them too.
I'll try another method to get in rcm mode

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

You should always get into RCM unless you have hardware issues..

Try another RCM method, Jig and or cable...

Rcm is built into the chip.

Rcm Doesnt need a sd card or a nand(emmc) module..

So your issue is with your rcm method. Driver or cable...


And i asked about boot0 and boot 1 above < did you restore these in hekate ?Did you back them up When you made nand backup ?
THANK YOU, I TOUGHT THAT MY SWITCH WAS COMPLETELY BROKEN.
I discovered that i just put the jig in the wrong way. THANK YOU SO MUCH!
 
Yes, i restored and backupped them too.
I'll try another method to get in rcm mode

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


THANK YOU, I TOUGHT THAT MY SWITCH WAS COMPLETELY BROKEN.
I discovered that i just put the jig in the wrong way. THANK YOU SO MUCH!

Of course man, no problem at all... as long as people explain their situation in detail what happened what they did etc, then we have a better understanding of what happened and a method to get it fixed
Always backup the boot0/1 with the nand and restore them back with it.
 

Site & Scene News

Popular threads in this forum