Hardware My Switch is a 2019 v6.2.0 XAJ4008278 UNPATCHED unit!

[PRAGMA]

Edition: Gray + £30 eShop Included with Sticker advertising this on the corner.
Revision: Original Launch Edition (White Box)
Original Firmware Version: Probably 6.2.0, I can't remember, but definitely 8.1.1 or older.
Shell: Original Launch Edition, not the glittery and more metallic shells you typically see on 2019+ units.
Merchant: Scan.co.uk
Purchase Date: 23rd of August, 2019

This was purchased just around the time that the merchant was struggling to get Nintendo Switch's, especially as the new V2 Red Box versions were just around the corner.

---

I bought this brand new a couple of days ago and it arrived today. I checked the serial on ismyswitchpatched.com and based on its result it should be "definitely patched".

However, I tried to send a payload anyway and it worked! At first, I thought this is a shell swap but it isn't. I matched the serial number on the shell's sticker with the serial numbers inside the settings.

---

Interestingly enough, BIS Key generation for this unit failed on Atmosphere, Lockpick_RCM, and biskeydump. It seems to have revised BIS key generation. SciresM who created Atmosphere said my console needs a fix that he will help with in ~6 hours.

Because of this, I cannot safely use this Switch as I cannot get valid BIS keys to keep with my eMMC backup. BIS keys are required for decrypting eMMC backups and without them, the backup is more or less useless.

---

On the 29th of August, 2019, SciresM pushed a fix for BIS Key generation to Atmosphere: https://github.com/Atmosphere-NX/Atmosphere/commit/600d68bd1aa6f13b47b1482e48110b2e3c2684ed and then 15 days later released Atmosphere v0.9.4 with this fix.

On the 16th of September, 2019, Shchmue pushed a similar fix to Lockpick_RCM: https://github.com/shchmue/Lockpick_RCM/commit/6540ddc24ba65fdf4863c78b0119869f8dfd0ed8 and then a day later released Lockpick_RCM v1.5.0 with this fix.

All that needs updating is rajkosto's biskeydump project.

I can confirm the fixes made on both projects work and dump the correct BIS Keys on my unit. I managed to decrypt SYSTEM.bin, and mount it with HacDiskMount and the BIS Key's entropy was Valid.

---

Just in case there was anything interesting about my specific system, or if anything of interest was left on my eMMC, SciresM took a look at the NCA headers of my decrypted SYSTEM.bin and found nothing of interest.

---

Take from this thread what you will, but just know that you cannot take the Serial number or the Serial checker websites at face value. It may be worth taking the time to try and send a Payload even if the websites say it's "definitely patched". You can't blame these websites either as they only have limited data to work on and can only go by what seems to be the common path for serials. After all, this unit can be considered a bit of a weird one.

 

[Loko4]

I see this as absolute win

 

[guitarheroknight]

What? More attention seeking you say?!

 

[PRAGMA]

What? More attention seeking you say?!

?
Im just showing this to notify people to not take serial number as face value on if your switch is patched or not, clearly it could be a case like mine, shell swap, e.t.c

 

[DeoNaught]

Maybe just old boards finally getting shipped out in new housings?

 

[PRAGMA]

Maybe just old boards finally getting shipped out in new housings?

I wouldn't see why Nintendo would do that to be honest. It wouldn't make any sense from an anti-piracy perspective.

 

[antiNT]

This is absolutely remarkable to say the least. I would've never guessed that could be possible. I hope the opposite isn't though (i.e switch that's definitely supposed to be vulnerable but isn't)

 

[uyjulian]

Possible that they forgot to apply the ipatches, or ran the wrong factory firmware?

 

[Deleted-452294]

The OS prints the serial on PRODINFO. I will be interested in knowing whether the Device ID in eFuses matches the Device ID in PRODINFO.
Feel free to DM me if you want me to calculate your BIS keys. This will require a FUSE+KFUSE dump for your console, though.

 

[x65943]

Wow this could be big

 

[Nerdtendo]

At first I thought this was one of those "I got a patched switch, can I hack?" Threads.

Can it actually boot CFW or is it unable to with what's available

 

[PRAGMA]

At first I thought this was one of those "I got a patched switch, can I hack?" Threads.

Can it actually boot CFW or is it unable to with what's available

It can actually boot CFW.

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

The OS prints the serial on PRODINFO. I will be interested in knowing whether the Device ID in eFuses matches the Device ID in PRODINFO.
Feel free to DM me if you want me to calculate your BIS keys. This will require a FUSE+KFUSE dump for your console, though.

I would check that but I don't have BIS keys to read PRODINFO. Id rather wait for the fix from sciresm though.

 

[Deleted-452294]

I would check that but I don't have BIS keys to read PRODINFO. Id rather wait for the fix from sciresm though.

Alright, well, that's up to you anyway.

 

[Dave_Chad]

Pragma winning at life right now...

What made you try anyway?

 

[PRAGMA]

Pragma winning at life right now...

What made you try anyway?

Takes like 2 seconds to try, so I said why not.

 

[M7L7NK7]

So basically everyone with a patched switch needs to try it, and even buying a patched switch could be actually unpatched?

 

[The Real Jdbye]

So basically everyone with a patched switch needs to try it, and even buying a patched switch could be actually unpatched?

Yeah it seems like they sometimes have old stock that are shipped with new serial numbers. Not the first report I've heard of this.

I bought this new a couple of days ago and it arrived today, checked serial and based on it, assumptions was that it was "definitely patched".

However I tried anyway and it worked.
At first I thought this is a shell swap but it isn't. I matched the serial numbers with the serial numbers inside the OS against the shell's sticker.
And interestingly enough, BIS Key generation isn't working properly, apparently according to SciresM my console needs a "fix" that he will help with in "~6 hours".

This also means that it isnt a first revision unit due to it having revised BIS key generation.
Because of this, as of right now I cannot safely use the switch as I cannot get a proper backup as the BIS keys currently gotten from Lockpick_RCM/biskeydump isn't working, it's entropy doesn't match the NAND.

Pretty odd stuff.

Which edition Switch is it? Neon, gray, etc.

 

[Essometer]

Guys, chill out. Comparing Serials was never an accurate science. To make predictions, we need data, the less data we have the less good are the predictions.
This is the reason why we can pretty accurately tell if a Switch is unpatched. Since this is a hacking community, people bought the unpatched Switches and
the potential patched Switches stayed mostly in the shelf. Since we had to establish a boarder somewhere, the cutoff point to "patches" was more or less
arbitrarily. It just means that where was never a Switch with this high of a firmware reported to be unpatched. Your find means that the boarders for potential
unpatched units will be moved.

That it doesn't support the BIS Key Generation is intersting however.

 

[Budsixz]

Takes like 2 seconds to try, so I said why not.

yours isnt the latest version right? the one with better battery?

 

[PRAGMA]

Yeah it seems like they sometimes have old stock that are shipped with new serial numbers. Not the first report I've heard of this.

Which edition Switch is it? Neon, gray, etc.

Gray

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

yours isnt the latest version right? the one with better battery?

No its the original