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.
Last edited by PRAGMA,