Hacking I JUST BRICKED MY SWITCH (BY TRYING RESTORE 6.20 NAND)

HadiLW

Member
OP
Newcomer
Joined
Jan 30, 2019
Messages
5
Trophies
0
Age
27
XP
67
Country
Indonesia
#SOLVEDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD

hi guys i just really confuse af right now. but first im really sorry for being scrub and didn't give a fk about "how to"
so just go to the point, yesterday my switch was upgraded to 7.00 from 6.20 *by it self (don't know how), and i'm using sxos pro as my cfw.
and i just think restore the nand to my stock nand 6.20(which i had the backup) will solve the problem.
so after the restore, my switch wont boot to ofw either cfw. only showing blank screen when i press power on, and i try going to rcm mode, where pressing volume up + power with jig and sxpro dongle , and it work i can boot to sxos rcm, but still i cant boot to my cfw and ofw.
im really a noob, doesn't know about hatake or any else,so any senpai can help me , i really hopeless right now, i need help please T-T.

#UPDATE1
I HAVE BEEN ASK FOR HELP IN FACEBOOK (SWITCH LOCAL COMMUNITY ) AND ITS FKING WORK
It just like "tidusboy21" says
what i need to do just log on to switch using hetake because it pass a blown fuze. so yes
im using hetake with atmos cfw then going update (in switch menu from 6.20 to 7.00)so im already back to v7.0 and all my switch hardware are worked so fine until now and no banned notification until now (02/02/2019).
thanks for everyone that comment and help me.

NOTE : BOOT 0/1 SO FKING IMPORTANT
 
Last edited by HadiLW,

Mthodmn101

Well-Known Member
Member
Joined
Jan 31, 2008
Messages
653
Trophies
1
XP
1,741
Country
United States
saw this on discord:

Apparently if you update and have an emunand equal or below 6.1 it works.
It's the new TSEC firmware that messes up the 6.2 support
same principle should be correct for Rawnand restoration (below or equal to 6.1 should be fine)


If you have a nand dump from 6.1 or lower, try that
 
  • Like
Reactions: OkazakiTheOtaku

HadiLW

Member
OP
Newcomer
Joined
Jan 30, 2019
Messages
5
Trophies
0
Age
27
XP
67
Country
Indonesia
saw this on discord:

Apparently if you update and have an emunand equal or below 6.1 it works.
It's the new TSEC firmware that messes up the 6.2 support
same principle should be correct for Rawnand restoration (below or equal to 6.1 should be fine)


If you have a nand dump from 6.1 or lower, try that
i dont have it what sshould i do.
 

Zumoly

GBATemp Analyst
Member
Joined
Apr 27, 2018
Messages
1,822
Trophies
0
Location
Yorosso
XP
3,157
Country
Mali
That's weird!
How did you make your NAND backup? Using Hekate or SXOS?
The Hekate backup requires you to also save the boot0/1 files (dunno if SXOS does though), so that might be your issue. Heard from @Adran_Marit that you can generate those. Hopefully this can solve your issue.
 
  • Like
Reactions: HadiLW

Adran_Marit

Walküre's Hacker
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,569
Country
Australia
hi guys i just really confuse af right now. but first im really sorry for being scrub and didn't give a fk about "how to"
so just go to the point, yesterday my switch was upgraded to 7.00 from 6.20 *by it self (don't know how), and i'm using sxos pro as my cfw.
and i just think restore the nand to my stock nand 6.20(which i had the backup) will solve the problem.
so after the restore, my switch wont boot to ofw either cfw. only showing blank screen when i press power on, and i try going to rcm mode, where pressing volume up + power with jig and sxpro dongle , and it work i can boot to sxos rcm, but still i cant boot to my cfw and ofw.
im really a noob, doesn't know about hatake or any else,so any senpai can help me , i really hopeless right now, i need
help please T-T.

That's weird!
How did you make your NAND backup? Using Hekate or SXOS?
The Hekate backup requires you to also save the boot0/1 files (dunno if SXOS does though), so that might be your issue. Heard from @Adran_Marit that you can generate those. Hopefully this can solve your issue.

You need to restore your boot 0/1 using hekate... if you don't have them then you need to generate new ones... follow this guide.. get the firmware from xbins for 6.1 then follow the instructions WORD FOR WORD until then have done step 8.3

DO NOT CLICK FORMAT WHEN IT ASKS... IF YOU DO YOU SWITCH WILL BE FULLY BRICKED
Once you have finished for 6.1 building and downgrading, then upgrade to 6.2 then restore the backup

you might need to boot sxos using hekate for now though.. dunno if they included downgrade stuff

EDIT: You might have to goto 6.1 first then upgrade back to 6.2 using choidujourNX

EDIT 2: You definitely have to do the above for 6.1 if you don't have 6.2 boot0/1 files... then downgrade to 6.1, upgrade to 6.2 using choidujourNX then restore your backup if you want
 
Last edited by Adran_Marit,

tidusboy21

Member
Newcomer
Joined
Aug 17, 2008
Messages
8
Trophies
0
XP
210
Country
I have a same your issue. It not brick it's just boot you into something like RCM and just press Power Button about 30 sec it will off. You can boot hekate to go back 7.0 and wait for next FW patched.
 
  • Like
Reactions: Subtle Demise

jscjml

Monster Hunter
Member
Joined
Jan 4, 2015
Messages
334
Trophies
0
Age
29
Location
Las Vegas
XP
256
Country
United States
Isnt that common sense though, to backup everything?

boot0/1 take like 0.2 seconds to backup anyways. My bet is people did their nand first and saw it took so long, so they got lazy and didnt want to check the other ones. Could be wrong though.
 

eldavo2090

Well-Known Member
Member
Joined
Jan 21, 2014
Messages
210
Trophies
1
Age
33
Location
Dinosaur Land, Donut Plains
XP
1,299
Country
Mexico
Isnt that common sense though, to backup everything?

boot0/1 take like 0.2 seconds to backup anyways. My bet is people did their nand first and saw it took so long, so they got lazy and didnt want to check the other ones. Could be wrong though.
Yeah probably that happened... I backed up everything just in case... it paid off!

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

Adran_Marit

Walküre's Hacker
Member
Joined
Oct 3, 2015
Messages
3,781
Trophies
1
Location
42*South
XP
4,569
Country
Australia
Isnt that common sense though, to backup everything?

boot0/1 take like 0.2 seconds to backup anyways. My bet is people did their nand first and saw it took so long, so they got lazy and didnt want to check the other ones. Could be wrong though.

If common sense was common we wouldn't need to tell people not to update lol

some people could just get told to backup nand (raw or system) and not do boot0/1 realising it is a small part of it
 
  • Like
Reactions: eldavo2090

HadiLW

Member
OP
Newcomer
Joined
Jan 30, 2019
Messages
5
Trophies
0
Age
27
XP
67
Country
Indonesia
I have a same your issue. It not brick it's just boot you into something like RCM and just press Power Button about 30 sec it will off. You can boot hekate to go back 7.0 and wait for next FW patched.
well thanks for the help , my friend already suggest the exact same solution like u said. and it worked

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

That's weird!
How did you make your NAND backup? Using Hekate or SXOS?
The Hekate backup requires you to also save the boot0/1 files (dunno if SXOS does though), so that might be your issue. Heard from @Adran_Marit that you can generate those. Hopefully this can solve your issue.
thanks for your help man, i appreciated it. maybe im using the newest boot.dat by sxos 2.5.2? it had a nandbackup option and boot backup so i dont need hetake anymore. cmiiw

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

File backup always have boot0/1 and other main file ( 29GB), like me after i backup copy file hetake to SD and run RCM to boot into CFW and it no need any boot0/1.
btw, u still stay on ofw v7.0 or back to 6.20 cfw? let me know please. i want to know a proper way to downgrade a fking v7.0
thanks
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: @BigOnYa, it was maybe funny the third or fourth time companies did it +1