Hacking is my switch patched for fusee gelee?

[jamezfat]

i recentlly got another switch this month, and finally got around to testing fusee gelee. i can inject payloads no problem, but my screen stays blank. even though the injector says sucess. it was on 4.1 when i got it, but i updated to 5.1...

am i out of luck?

(
also, just dropped my switch while typing this. now have a chip on the top that i will hate myself for forever.)

 

[linuxares]

You can change shell on it, so don't fuss to much about it. What's the serial number?

 

[jamezfat]

You can change shell on it, so don't fuss to much about it. What's the serial number?

The serial is XAW10080979240

 

[Paulsar99]

Tx has future support for patched switches so might as well wait for that.

 

[linuxares]

Might be one then, since the ones I know are patched began with XAJ1007+

 

[V-Temp]

Tx has future support for patched switches so might as well wait for that.

Don't sell people on empty promises with zero evidence of veracity.

 

[thekarter104]

Don't sell people on empty promises with zero evidence of veracity.

Yeah, I wonder how TX claims it's possible on unhackable units, especially on 5.0+... lol

 

[iriez]

Take a look at this post

Does your output show 0x0000 or 0x7000 when smashing? 7000 is a vulnerable switch, 0000 is a patched switch.

 

[jamezfat]

I think I might just need to replace my switch then... Again ; ^ ;​

 

[4get9]

Might be one then, since the ones I know are patched began with XAJ1007+

There are no patched XAW1007, but some XAW1008... I don't think about a link between J and W serials.
But I'm surprised to see a patched XAW10080X

And maybe a little bit stressed with my 100800 waiting for its jig... But I'm keeping hope....

Sent from my LG-H872 using Tapatalk

 

[V-Temp]

Yeah, I wonder how TX claims it's possible on unhackable units, especially on 5.0+... lol

Their post claiming their success is riddled with factual inaccuracies so pardon me if I think it's all just bullshit.

 

[Paulsar99]

Don't sell people on empty promises with zero evidence of veracity.

Yeah we get it bro, you hate tx like the plague.

 

[V-Temp]

Yeah we get it bro, you hate tx like the plague.

You're free to believe a statement with verifiably false information in it all you'd like.

 

[jamezfat]

Take a look at this post

Does your output show 0x0000 or 0x7000 when smashing? 7000 is a vulnerable switch, 0000 is a patched switch.

I presume this shows what you're looking for?

 

[krazykanuck]

Was there any other info after that as the picture you have and the one he showed are a little different

 

[iriez]

View attachment 137956I presume this shows what you're looking for?

In this picture you have not successfully delivered the payload. Perhaps usb complications. I would suggest trying different usb ports, if you are currently using a blue 3.0 port, try switching to a black 2.0 port. If you are using the front usb, try switching it to the back.

But for whatever reason, your device has not received the payload because the final status message has not been received. Look at the post I showed you earlier and you'll see what yours is missing.

 

[jamezfat]

In this picture you have not successfully delivered the payload. Perhaps usb complications. I would suggest trying different usb ports, if you are currently using a blue 3.0 port, try switching to a black 2.0 port. If you are using the front usb, try switching it to the back.

But for whatever reason, your device has not received the payload because the final status message has not been received. Look at the post I showed you earlier and you'll see what yours is missing.

I've tried multiple usb ports, yet to no avail. By using tegra rcm gui, it fully injects the payload. But tegra gui doesn't display any of the things that we're looking for...

 

[TheCyberQuake]

Tx has future support for patched switches so might as well wait for that.

As far as I've seen they haven't said they actually have anything for patched systems, just a "we are working on it" and trying to find a way into patched systems. We know there is more than the one bootrom exploit, so if only the one was patched there could be others that they use, so I'm not saying they don't have one. But I would just wait until they prove that they have one rather than going around saying they have one and then possibly later they end up not having one.

 

[iriez]

I've tried multiple usb ports, yet to no avail. By using tegra rcm gui, it fully injects the payload. But tegra gui doesn't display any of the things that we're looking for...

No, according to the image you've provided it definitely did not inject the payload. If it did, there would be a status return. I've had this happen to me with a switch that had a trinket install where the usb connections were bridged or reversed. Im not saying thats your situation, im just saying it has to do with your usb chipset, adapter or cable. If it did, you would have gotten either 0x0000 or 0x7000 as a status return in the cmd window.

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

As far as I've seen they haven't said they actually have anything for patched systems, just a "we are working on it" and trying to find a way into patched systems. We know there is more than the one bootrom exploit, so if only the one was patched there could be others that they use, so I'm not saying they don't have one. But I would just wait until they prove that they have one rather than going around saying they have one and then possibly later they end up not having one.

Not only that, but hexkyz confirmed you can display the info they got through a privsec exploit. So it could be a PR campaign, or perhaps they have a different bootloader exploit. I sure hope they don't burn a new exploit before a big hardware revision.

There's 16 million switches that are vuln. We have no reason to rush. Plenty of them in the wild.

https://twitter.com/hexkyz/status/1023588626611884033

 

[Paulsar99]

As far as I've seen they haven't said they actually have anything for patched systems, just a "we are working on it" and trying to find a way into patched systems. We know there is more than the one bootrom exploit, so if only the one was patched there could be others that they use, so I'm not saying they don't have one. But I would just wait until they prove that they have one rather than going around saying they have one and then possibly later they end up not having one.

True. Only time will tell though.