Sorry to burst your bubble, but all this video shows is Hekate with a custom boot bmp, autorcm, and likely a trinket m0Video of the exploit: https://i.4cdn.org/vg/src/1530654137669.webm
Last edited by YigglyPoof,
Sorry to burst your bubble, but all this video shows is Hekate with a custom boot bmp, autorcm, and likely a trinket m0Video of the exploit: https://i.4cdn.org/vg/src/1530654137669.webm
this is like standing in a fireworks shop saying "boy, son, bet you can't wait until new year's to see fireworks"Check the Twitter responses. All the transphobes are crawling out of the woodwork.
keyword likely. we all know bog is very trustworthSorry to burst your bubble, but all this video is is Hekate with a custom boot bmp, autorcm, and likely a trinket m0
Except that this puts more pressure on keeping Deja Vu under wraps until Mariko rears its ugly head. In the event that the exploit does reach Nvidia's ears and they do patch it out in the Mariko Units, Deja Vu is now the only confirmed exploit to work on those units. Given that TX took down their video of their exploit working on a supposedly patched unit, that either means they realized they weren't running a patched unit and/or they don't have a way to exploit the new units as of yet.Ok, I know I'm playing Devil's Advocate here, and I'm probably gonna get flamed... but maybe ktemkin just did us a big favor?
We've seen these new "unhackable" Switches hit the shelves. This "new exploit" is probably applicable to them, and ReSwitched will probably end up releasing it soon now that there's no point in keeping it hidden. Now we will be able to hack these new Switches, and there's probably a decent amount of time between now and when the first Mariko units hit shelves, hopefully enough time to find yet another exploit. Or maybe she had doubts that this exploit would have ever worked on Mariko to begin with.
And instead of waiting forever before it gets released, we can benefit from this exploit now (or at least very soon).
I could be wrong, it's just an idea. Apparently she left the original author's name in the disclosure, and if I've heard correctly, she didn't receive any money from the hack. If she was really trying to steal credit for it, I think she would have been smart enough to remove all traces of the original author first, that kinda seems like a common sense thing to do.
Off course they wouldn't as they are in the market for more than a decade and as long as they can keep hacking some future consoles, they can keep making profit...at least TX didn't sold us
this is way way worse for us the community
Except that this puts more pressure on keeping Deja Vu under wraps until Mariko rears its ugly head. In the event that the exploit does reach Nvidia's ears and they do patch it out in the Mariko Units, Deja Vu is now the only confirmed exploit to work on those units. Given that TX took down their video of their exploit working on a supposedly patched unit, that either means they realized they weren't running a patched unit and/or they don't have a way to exploit the new units as of yet.
No one knows, 4chan post good chance its fake.So did he get a money or not? Can someone make a summ?
If you are referring to K (and me and everyone else should just use K going forward), K submitted an exploit for a bounty of 200k. Meaning K has not collected said bounty yet; only submitted it. Its up to the company that set the bounty on whether they believe K deserves the money or not. My money is on no after seeing this massive fallout but you never know.So did he get a money or not? Can someone make a summ?
Depends on how fast the ReSwitched Discord can recover from its "slight turbulence"So, can we get the FULL story? Not the cliff note?
Unlikely. As far as can be pieced together;So, can we get the FULL story? Not the cliff note?
"I haven't sold out any Switch bugs to Nintendo..."
"I haven't sold out any Switch bugs to Nintendo..."
But what about Nvidia?!
It's a shame this was posted after over 250 posts of solid, seething hatred have already been made. Even if no wrongdoing truly was done, the damage has already been inflicted, nobody will believe anything she has to say. Peoples' minds have already been made up.
I mean, that's kinda the point I was making. I can't tell if she's being vague on purpose or by accident. Its like asking TX whether they had brick code in SX OS. They didn't answer the question, they just dodged it then conveniently remove it in a later firmware -_-Pixel C uses the Tegra X1. So, basically the same thing.
Yeah and worse is Kate reporting like if she knows nothing when she exactly know how similar Pixel C is too the Switch, like if she was excusing for a 5 years old kid, just like if SciresM would fall 4 that.Pixel C uses the Tegra X1. So, basically the same thing.
But, what do transphobes have to do with bootrom bugs?I don’t think it has been disclosed exactly which bug was reported, it is presumably one we don’t know about.
The silver lining is that this bug may be released once it is patched, but it would be a waste given F-G already exists.
--------------------- MERGED ---------------------------
Check the Twitter responses. All the transphobes are crawling out of the woodwork.