My bad it wasn't letting me reply to your post but I figured it out I had to remove your hyperlinkCan you try tegrarcmsmash with biskeydump ?
And run this command when you connect your RCM switch to your pc.
TegraRcmSmash.exe -w biskeydump.bin BOOT:0x0
Then capture the output on the command line windows and post it here please.
I think you are the first in US who reported a patched unit.My bad it wasn't letting me reply to your post but I figured it out I had to remove your hyperlink
Here's the output:
View attachment 135507
Lucky me.I think you are the first in US who reported a patched unit.
Welcome to the club
I purchased a Switch with the serial number XAW700183***** and I can confirm that payload injection doesn't work.
Steps to recreate:
1. Copied the Switch Starterkit root files to the root of my FAT32 SDcard from my PC
2. Inserted SDcard into Switch, then booted into RCM mode with paperclip jig
3. Plugged Switch into PC, used Zandig to install the libusbK drivers, confirmed APX came up as a device in device manager
4. Tried to run the NX bootkit 64-bit executable, the Switch screen remains black and the cmd prompt window displayed some code then counted down from 5 seconds to close the window
Is it possible that my USB-C cable (came with my phone) is the culprit here or is it likely that I have a patched Switch?
So it appears these units have been smuggled into the US but we have another problem: we don't know the serial number cut-off for un-patched units...I think. Need to double check that spreadsheet...My bad it wasn't letting me reply to your post but I figured it out I had to remove your hyperlink
Here's the output:
View attachment 135507
starts with xaw40012 came with 4.1
i got in to the sx payload bootscreen.
i guess im fine
That's right, it also looked identical to the screen that came up when I ran Hekate. I know for a fact it said "Smashed with 0x0000 stack" as wellJust to explain.
This is from a working console.
View attachment 135511
I asked you to run the biskeydump because you were not sure about your cable.
But from the command line output, it can send data using your cable.
Next, see the different 0x0000(not working) and 0x7000(working) output?
First time posting, but wanted to include info on my switch I bought on June 29 through Newegg. Its very close to the serial bitteorca posted, but mine does work im running SX Pro and been playing backups and even updated to 5.1. Hope this helps in figuring out where the line is between patched and unpatched.
Serial: XAW700119XXX
Serial on device matches serial on box: Yes
Region: US
Firmware: 4.1.0
Color option: Blue / Red
Store: Newegg
Was a bundle (if yes, which): No
Purchase date: June 29 2018
Fusée Gelée works: Yes
Please also post your serial and model information here, https://gbatemp.net/threads/switch-firmware-by-serial-number.481215/page-59That's right, it also looked identical to the screen that came up when I ran Hekate. I know for a fact it said "Smashed with 0x0000 stack" as well
The girl at the counter even offered me a used unit, damn. Does anyone have any news on the webkit exploit Deja vu?
Got some good news (sorry that it takes over a minute for the lennies): https://t.co/hGdPOchTVo
— Michael (@SciresM) February 16, 2018
Anyway, I would strongly recommend not updating when new firmwares release.
XAW700183 is actually a really high serial number. It is just that assembly line XAW7 is pretty slow in producing switches. According to myseems to be a low serial, whats the date code on the switch?
might be worth trying a different USB port/pc, unfortunately I feel like anyone having troubles with setup at this point are going to be "arrrgh its a patched switch!!!!"
XAW700119XXX = not patched
XAW700183XXXXX = patched
So 11 is still safe, but 18 isn't. That leaves like 7 more possible Switch serial numbers, at least. And while there is no word yet on when Deja Vu will be released, this is what it looks like in action: https://twitter.com/SciresM/status/964619151913336833
An XAW700119XX doesn't have it patched so its a little more specific. Similar to the Japanese ones, the cutoff point is not XAJX004, butXAJX0043 since there were people who could still do the exploit on the former serial number.XAW700183 is actually a really high serial number. It is just that assembly line XAW7 is pretty slow in producing switches. According to
serial list, it is very possible that this serial is another cutoff point for patched switches.
oh, no I know that, I meant the previous patched systems were 7004, but his was 7001 with others with 7003 being ok, but with it being a US console the "patched/no-patched" serials are going to be differentXAW700183 is actually a really high serial number. It is just that assembly line XAW7 is pretty slow in producing switches. According to
serial list, it is very possible that this serial is another cutoff point for patched switches.
Yes, this is what I think as well that the cutoff point for the XAJ7 line is more specific as for XAW7. We definitely need more serials to get a cutoff point for all assembly lines.An XAW700119XX doesn't have it patched so its a little more specific. Similar to the Japanese ones, the cutoff point is not XAJX004, butXAJX0043 since there were people who could still do the exploit on the former serial number.
When we talk about serials, it doesn't make sense to compare a XAW7 serial to a XAJ7 serial, since they are completely different form each other.oh, no I know that, I meant the previous patched systems were 7004, but his was 7001 with others with 7003 being ok, but with it being a US console the "patched/no-patched" serials are going to be different
Give TX a call, they are shitting them selfs right now.Someone buy my Switch? If you live in Northeast Ohio I'll drop it off
Give TX a call, they are shitting them selfs right now.