Hacking 6.2.0 Key Generation could (POSSIBLY) be UNCRACKABLE.

  • Thread starter Thread starter Essasetic
  • Start date Start date
  • Views Views 66,972
  • Replies Replies 253
  • Likes Likes 3
Status
Not open for further replies.
Roms of both old and recent games. And not just having them on his site but having that littered with ads and selling premium access too. At 12-17 million users per month.
Stop being an idiot and so the math, that couple massively profited from their copyright infringement which is why they settled for millions.
Whatever was destroyed, they never would've had in the first place. So losing it all in bankrupsy is more than deserved.

Ok sometimes a person can not know all the facts of something and that doesn't make them an idiot. The question is, are you smart enough to understand the difference? I didn't know all of those details so no need for insults. Nintendo is not your momma I didn't insult you personally like you did me.

In fact I know how this goes with angry people like you that can't provide information without adding insults, so I'll save myself the trouble and put you on ignore.

Nintendo is not just going after that one rom site either.
 
Last edited by ,
Besides after Nintendo ruined a man with a family's life recently by suing him for 12 million dollars just for having roms of their old games on his site I have no hurry to want to support them.
LMFAOOOOOOOOOOOOOOOOO

Out of all the retarded self-excuses for pirating, this takes the cake. Good job buddy.


LMFAOOOOOOOOOOOOOOOO
 
What exactly does this mean? Can sx os menu be booted? Can emunand of pre 6.2 be booted? (When real nand is 6.2)
 
how many fuses are burned on 6.1 and 6.2???
7 for 6.1 8 for 6.2

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

Didn't read all the thread, is this just a clickbait ?
Well yes and no.

Yes: Because it probably will get cracked eventually.

No: Because it's been proven harder than thought to crack 6.2.0 (and a cat and mouse game may begin because of it.)
 
  • Like
Reactions: aerios169
7 for 6.1 8 for 6.2

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


Well yes and no.

Yes: Because it probably will get cracked eventually.

No: Because it's been proven harder than thought to crack 6.2.0 (and a cat and mouse game may begin because of it.)
well i am fucked, i tried to updapte not burning fuses through rcm mode and sx, now i have 8 fuses burrned =/
 
well i am fucked, i tried to updapte not burning fuses through rcm mode and sx, now i have 8 fuses burrned =/
Why did you try to update without burning fuses? You do realise if you can't access CFW on 6.2 then you can't access Choir on 6.2! Which basically means you've fucked yourself over.
 
Why did you try to update without burning fuses? You do realise if you can't access CFW on 6.2 then you can't access Choir on 6.2! Which basically means you've fucked yourself over.
not yet i have emunand, and is working but it gets stuck when i use sleep mode
 
meanwhile pirate pc games till the switch scene comes back.....theres many things in life to enjoy. lol
 
well i am fucked, i tried to updapte not burning fuses through rcm mode and sx, now i have 8 fuses burrned =/
Just wondering, how did you "update while not burning fuses"?
Did you update in OFW, then insert an RCM jig and hold vol+ while booting?

I usually do this at EVERY firmware update, then do a NAND backup.
Only just because I like having NAND backups for each FW version.
Then I just restore my old 5.1 backup to play.

But I've seemingly been reading reports of problems with this method now... like AutoRCM doesn't work now supposedly(?) (did N modify the new BOOT0/1 so that the old "AutoRCM bricking methods" don't work on it?), or it seems even just booting once into 6.2 burns your fuses (even if you try to enable AutoRCM, which seemingly fails)? I have to boot once into the new FW version though to delete the wifi settings before making the backup... but I'm scared now due to some of these reports.

So yeah... how exactly did you "update while not burning fuses"?

Also tagging @Draxzelex because I know he knows this method that I am talking about, maybe you know something about these reports Drax?
 
  • Like
Reactions: Essasetic
Just wondering, how did you "update while not burning fuses"?
Did you update in OFW, then insert an RCM jig and hold vol+ while booting?

I usually do this at EVERY firmware update, then do a NAND backup.
Only just because I like having NAND backups for each FW version.
Then I just restore my old 5.1 backup to play.

But I've seemingly been reading reports of problems with this method now... like AutoRCM doesn't work now supposedly(?) (did N modify the new BOOT0/1 so that the old "AutoRCM bricking methods" don't work on it?), or it seems even just booting once into 6.2 burns your fuses (even if you try to enable AutoRCM, which seemingly fails)? I have to boot once into the new FW version though to delete the wifi settings before making the backup... but I'm scared now due to some of these reports.

So yeah... how exactly did you "update while not burning fuses"?

Also tagging @Draxzelex because I know he knows this method that I am talking about, maybe you know something about these reports Drax?
i enter to rcm mode on sx menu then i booted OFW, it supposed that on the updapte the fuses wouldn´t be burned, then i check with hekate and i got 8 fuses burned
 
i enter to rcm mode on sx menu then i booted OFW, it supposed that on the updapte the fuses wouldn´t be burned, then i check with hekate and i got 8 fuses burned
Wait, you didn't do anything else?
Like hold vol+ and stick in an RCM jig exactly as it restarted?
You do know that updating in OFW removes AutoRCM, right?
 
Last edited by bundat,
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum