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.
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.