Hacking 6.2.0 Confusion, explained.

  • Thread starter Deleted User
  • Start date
  • Views 17,769
  • Replies 46
  • Likes 8
D

Deleted User

Guest
OP
So there seems to be alot of puzzlement over the new 6.2.0 update and CFW. So I'm making this post to try and explain everything as clearly as possible.

So the new 6.2.0 update changed alot of things. Files strewn about the place, new key generation method, etc etc.
Because of this, all current CFW solutions are incompatibale with 6.2.0.

So here's whats happening.
People are updating, whether on purpose or by accident to the latest firmware, and because of the new changes, their current cfw solution is not working, causing issues such as booting and crashing instantly. You see, you can still access RCM (Tegra Recovery Mode) because that's something that is unfixable.

So booting an incomatible firmware with an incompatible cfw solution is crashing your switch.
This means means ONLY 6.2.0 is affected.

However, we can bypass fusechecks in order to downgrade to older firmwares..... and EmuNand.
We can boot EVERYTHING below 6.2.0 with CFW, both on SysNand and EmuNand.

What's the best solution then?

If you're only wanting 6.2.0 with CFW, then you may wait until a 6.2.0 compatible CFW solution is released.
If you're wanting CFW RIGHT NOW, then be on ANY other firmware, and use a compatible CFW solution.

Now, the big confusion occurs with the newly released EmuNand by TX. And that they said don't update.

So to be clear:
6.2.0 is NOT available with a CFW yet. Whether on SysNand or EmuNand.
You CAN have 6.2.0 on SysNand, stock without CFW & still boot 6.1.0 and below through EmuNand.

6.2.0 CFW?
SysNand? NOT YET
EmuNand? NOT YET

6.2.0 OFW?
SysNand? YES
EmuNand? UNSURE (Why would you be using OFW on EmuNand anyways?)

6.2.0 OFW on SysNand & ANY lower CFW on EmuNand? YES!

I hope this helps try and clear up the confusion that's ongoing.
 

sergux

Well-Known Member
Member
Joined
Jul 14, 2018
Messages
125
Trophies
0
Age
101
XP
1,057
Country
Afghanistan
im on 6.2 cuz i want to play online my legit games, i have old emunand on 6.1. i use to boot both using autorcm but when im on TX volume + menu i press boot original firmware and he didnt boot as allways, something is wrong with this but i dont know how to fix this, i tested and unisntalling autorcm OFW boots normally but i dont want damage right joycon bay with the jig, please help
frown.png
 

XorTroll

Switching between my 2DS and my Switch
Developer
Joined
Dec 28, 2017
Messages
641
Trophies
1
Location
Nowhere
Website
github.com
XP
4,209
Country
Spain
This can be resumed like this:

If you want to keep using CFW, DON'T UPDATE for the moment, until 6.2.0 gets patched. If you update, no CFW will work. People are working on it now, but it's not as easy as it was with other updates, this one requires much hard work. Please, be patient!
 
D

Deleted User

Guest
OP
So basically same old advise, NEVER UPDATE xD
Yup, just trying to make the solutions clean and clear.

Personally, I don't mind EmuNand being behind a little, and I'm gonna get a dongle too, so considering updating SysNand to latest and setting up EmuNand as 6.1.0

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

Im wondering, how longg will we be able to play online with 6.1.0?
As long as Nintendo allows. Hours? Days? Maybe a week or 2?

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

This can be resumed like this:

If you want to keep using CFW, DON'T UPDATE for the moment, until 6.2.0 gets patched. If you update, no CFW will work. People are working on it now, but it's not as easy as it was with other updates, this one requires much hard work. Please, be patient!
Exactly.
 

huma_dawii

Well-Known Member
Member
Joined
Apr 3, 2014
Messages
3,879
Trophies
1
Age
33
Location
Planet Earth
XP
4,244
Country
United States
Yup, just trying to make the solutions clean and clear.

Personally, I don't mind EmuNand being behind a little, and I'm gonna get a dongle too, so considering updating SysNand to latest and setting up EmuNand as 6.1.0

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


As long as Nintendo allows. Hours? Days? Maybe a week or 2?

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


Exactly.
Wait im confused now, can I have emunand on 6.2 OFW? xD

EDIT: never mind, that defeats the purpose since 6.2 is not compatible with homebrew xD
 

XorTroll

Switching between my 2DS and my Switch
Developer
Joined
Dec 28, 2017
Messages
641
Trophies
1
Location
Nowhere
Website
github.com
XP
4,209
Country
Spain
And people, those scared or confused, READ BEFORE DOING ANYTHING, or you'll regret updating, and it's always better to avoid drama in servers or in threads here!
 

radicalwookie

Well-Known Member
Member
Joined
Sep 15, 2018
Messages
528
Trophies
0
Age
46
XP
1,210
Country
United States
Yup, just trying to make the solutions clean and clear.

Personally, I don't mind EmuNand being behind a little, and I'm gonna get a dongle too, so considering updating SysNand to latest and setting up EmuNand as 6.1.0

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


As long as Nintendo allows. Hours? Days? Maybe a week or 2?

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


Exactly.
Yes im aware of that its theor decision but how long did they allow in the past?
 
D

Deleted User

Guest
OP
Okay... so I have a clean 6.1.0 sysnand backup ..... I am currently on 6.2.0 , I have no emunand or SX OS set up yet , could I some how manually create an emunand on the sd cArd using my 6.1.0 back up so that I can boot sx os loader and boot cfw using emunand 6.1.0,if someone knows the exact steps on how to create an emunand could they explain thanks
Backup sysnand 6.2.0, Restore sysnand to 6.1.0, use sxos to set up emunand. Check emunand boots up into 6.1.0, then restore sysnand to 6.2.0. Sorted. Use latest hekate to restore nands.
 

Apache Thunder

I have cameras in your head!
Member
Joined
Oct 7, 2007
Messages
4,398
Trophies
3
Age
36
Location
Levelland, Texas
Website
www.mariopc.co.nr
XP
6,731
Country
United States
Pretty sure that due to 6.2 TSEC verifying Package1Loader means that you can't have AutoRCM installed and still be able to boot 6.2 (not even booting via "stock" option in Hekate will help you here, because that requires you patch out the checks that PK1LDR does on the things AutoRCM corrupts so even minimal patching that is required can't be done).

You also can't modify Package1Loader and bypass fuse checks. Thus you can't use 6.2 if you want to avoid burning fuses. So yeah...don't even attempt to use a stock 6.2 sysnand and old emunand because if you burn fuses to make 6.2 usable, you loose ability to use sleep mode on older firmwares. (and also ability to boot old fw's without using RCM jig)
 
Last edited by Apache Thunder,
  • Like
Reactions: Full Metal

Jordan9716

Active Member
Newcomer
Joined
Nov 9, 2015
Messages
31
Trophies
0
Age
33
XP
118
Country
United States
Yup, just trying to make the solutions clean and clear.

Personally, I don't mind EmuNand being behind a little, and I'm gonna get a dongle too, so considering updating SysNand to latest and setting up EmuNand as 6.1.0

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


As long as Nintendo allows. Hours? Days? Maybe a week or 2?

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


Exactly.

As a major word of warning OP, your sleep mode won't work at all. That's a huge huge con. It's not possible to get sleep mode on 6.2.0 with 6.1.0 emunand.

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

Pretty sure that due to 6.2 TSEC verifying Package1Loader means that you can't have AutoRCM installed and still be able to boot 6.2 (not even booting via "stock" option in Hekate will help you here, because that requires you patch out the checks that PK1LDR does on the things AutoRCM corrupts so even minimal patching that is required can't be done).

You also can't modify Package1Loader and bypass fuse checks. Thus you can't use 6.2 if you want to avoid burning fuses. So yeah...don't even attempt to use a stock 6.2 sysnand and old emunand because if you burn fuses to make 6.2 usable, you loose ability to use sleep mode on older firmwares. (and also ability to boot old fw's without using RCM jig)

Oh also this happened to me. Autorcm still works for me on 6.2.0 sysnand with 6.1.0 emunand. The only issue is sleep mode not working. At this point it seems if I wanna use my switch I better be prepared to use it for at least an hour.
 
  • Like
Reactions: Full Metal

Apache Thunder

I have cameras in your head!
Member
Joined
Oct 7, 2007
Messages
4,398
Trophies
3
Age
36
Location
Levelland, Texas
Website
www.mariopc.co.nr
XP
6,731
Country
United States
Oh also this happened to me. Autorcm still works for me on 6.2.0 sysnand with 6.1.0 emunand. The only issue is sleep mode not working. At this point it seems if I wanna use my switch I better be prepared to use it for at least an hour.

You can boot into the 6.2 sysnand with AutoRCM installed? I was under the impression that you couldn't. Would that mean you can also avoid burning fuses? But I assumed not because you can't CFW things at all with 6.2 and still boot into 6.2. Sure you can boot a 6.1 emunand, but that's not thing I was talking about. :P
 

urherenow

Well-Known Member
Member
Joined
Mar 8, 2009
Messages
4,701
Trophies
2
Age
48
Location
Japan
XP
3,570
Country
United States
But I assumed not because you can't CFW things at all with 6.2 and still boot into 6.2. Sure you can boot a 6.1 emunand, but that's not thing I was talking about. :P
You lost me. No CFW on 6.2 sysnand is correct, but emunand has zero to do with sysnand. With RCM, your sysnand user and system partitions could be toast and you could still boot 6.1 emunand...
 

Apache Thunder

I have cameras in your head!
Member
Joined
Oct 7, 2007
Messages
4,398
Trophies
3
Age
36
Location
Levelland, Texas
Website
www.mariopc.co.nr
XP
6,731
Country
United States
You lost me. No CFW on 6.2 sysnand is correct, but emunand has zero to do with sysnand. With RCM, your sysnand user and system partitions could be toast and you could still boot 6.1 emunand...


Well yeah, but there's no point in installing 6.2 on sysnand because you can't boot into it without burning fuses since you can't boot into it with AutoRCM or modified PK1LDR to skip fuse check.
 

urherenow

Well-Known Member
Member
Joined
Mar 8, 2009
Messages
4,701
Trophies
2
Age
48
Location
Japan
XP
3,570
Country
United States
Well yeah, but there's no point in installing 6.2 on sysnand because you can't boot into it without burning fuses since you can't boot into it with AutoRCM or modified PK1LDR to skip fuse check.
There still isn't a good reason to worry about fuses though. Even if a solution was released that made use of a lower firmware, that makes it worthwhile to downgrade, there is still no way to avoid fuse checks in sleep mode. So what? Never let the console sleep?

zero. reason.

Reason for 6.2 would be new games and online play, if you're not banned already. From the looks of it, new games will require the update even when the new encryption is figured out.
 
Last edited by urherenow,

Apache Thunder

I have cameras in your head!
Member
Joined
Oct 7, 2007
Messages
4,398
Trophies
3
Age
36
Location
Levelland, Texas
Website
www.mariopc.co.nr
XP
6,731
Country
United States
There still isn't a good reason to worry about fuses though. Even if a solution was released that made use of a lower firmware, that makes it worthwhile to downgrade, there is still no way to avoid fuse checks in sleep mode. So what? Never let the console sleep?

zero. reason.

There could be a soft mod method of booting into RCM mode from older FWs. So in my opinion staying on 4.x FW is still relevant. Plus it's nice not needing a dongle/Smartphone/PC to boot the console from cold boot. :P
 

chrisrlink

Has a PhD in dueling
Member
Joined
Aug 27, 2009
Messages
5,528
Trophies
2
Location
duel acadamia
XP
5,666
Country
United States
Yup, just trying to make the solutions clean and clear.

Personally, I don't mind EmuNand being behind a little, and I'm gonna get a dongle too, so considering updating SysNand to latest and setting up EmuNand as 6.1.0

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


As long as Nintendo allows. Hours? Days? Maybe a week or 2?


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


Exactly.

which is why i do't bother with there onlne (still wouldn't if i wasn't super banned
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Sicklyboy @ Sicklyboy: *teleports behind you* "Nothing personnel, kiddo" +1