Hacking 6.2.0 released

  • Thread starter Thread starter nachuz
  • Start date Start date
  • Views Views 57,668
  • Replies Replies 222
  • Likes Likes 1
Emunand 6.0 still boots even on a 6.2 sysnand switch, so as long as emunand is not updated to 6.2, emunand will still work.
that is really weird , i figured it would be just the opposite , ut is like the total reverse as it was on the 3DS scene then?
 
According to Scires, it may be a long wait before we get homebrew on 6.2.

ZIX2757.jpg


lSOpaHu.jpg


If they don't manage to defeat TSEC (and according to him it's a considerable possibility , then they will rely on userland exploits (thus beginning the game of cat and mouse with Nintendo patching exploits every new firmware)
 
Last edited by Astoria,
According to Scires, it may be a long wait before we get homebrew on 6.2.

ZIX2757.jpg


lSOpaHu.jpg


If they don't manage to defeat TSEC (and according to him it's a considerable possibility , then they will rely on userland exploits (thus beginning the game of cat and mouse with Nintendo patching exploits every new firmware)
Sounds like a team effort is needed and not a lone wolf.
 
  • Like
Reactions: isoboy
A smart engineer under promises and over delivers. Several times things looked very dire in the 3DS scene but ingenuity and innovation always won.
 
  • Like
Reactions: peteruk
Just want to be sure, it is not possible to access CFW or downgrade at all using emunand or any other method if you have no backups and you are on 6.2.0 ? I also assume that you cannot use backups from other switches. You are basically stuck not able to use NSPs or XCIs.
 
Last edited by taggen86,
For the people on 6.2: Couldn't you restore a 6.1 backup, and boot into that using CFW with the fuse check disabled? Sure sleep mode doesn't work, but that feels like a small price to pay. Or if you're using SX OS: Couldn't you restore SysNAND back to 6.1, create a 6.1 EmuNAND, and then update back to 6.2 on SysNAND? Just trying to think of a temporary solution to your problems.
 
For the people on 6.2: Couldn't you restore a 6.1 backup, and boot into that using CFW with the fuse check disabled? Sure sleep mode doesn't work, but that feels like a small price to pay. Or if you're using SX OS: Couldn't you restore SysNAND back to 6.1, create a 6.1 EmuNAND, and then update back to 6.2 on SysNAND? Just trying to think of a temporary solution to your problems.

Is it possible to use any of these methods even if you have not created a backup? I use sx os and I am on 6.2.0. I can boot into the rcm using the dongle, but have never touched the EmuNAND options.
 
Is it possible to use any of these methods even if you have not created a backup? I use sx os and I am on 6.2.0. I can boot into the rcm using the dongle, but have never touched the EmuNAND options.
I think you might be SOL.
 
Well, it's already prooven whatever you like it or not, exfat can get fucked up if a write goes wrong
Is a Nintendo problem (confirmed by TX), so don't use emunand if you don't want to fuck up, tx fanboy that have the need to say that their $35 were worthy when you don't even need to and can't accept single wrong thing

So 6.2.0 didn't stabilize the exfat problem then?...
 
Well, it's already prooven whatever you like it or not, exfat can get fucked up if a write goes wrong
Is a Nintendo problem (confirmed by TX), so don't use emunand if you don't want to fuck up, tx fanboy that have the need to say that their $35 were worthy when you don't even need to and can't accept single wrong thing

Warning don't use exploits, it might brick your system, confirmed!!
Warning don't use exploits it might ban your system!
Warning don't use paperclips to enter recovery, it might ruin your joycon connectors!

The point is, many things currently are dangerous and can be harmful in the long run, yet we all use those or have used it without a single care in the world. People simply don't care that there is a small chance of corruption, and with the current early phase we're in, things like these are acceptable until they no less will be refined later on, as it always has in the scene. Let people use, what they want to use.
 
Last edited by Digitalcat,
Im sorry for a bit of an OT but can someone point me to the right direction as I want to ''downgrade'' my 6.2.0. I have NAND backup ready from the 6.1.0
 

Site & Scene News

Popular threads in this forum