Hacking Use Prodinfo from another switch.

[I_AM_L_FORCE]

Hey there, I've bought a switch that seems to have have it's serial and certs completely wiped for unknown reasons, as well as not coming with any sort of nand or Prodinfo backups.

However, I do have backups from another switch that for all intents and purposes is junk now (many, many issues)

Would it be possible to use the Prodinfo from my junk switch to restore to my good switch?

 

[Lacius]

Hey there, I've bought a switch that seems to have have it's serial and certs completely wiped for unknown reasons, as well as not coming with any sort of nand or Prodinfo backups.

However, I do have backups from another switch that for all intents and purposes is junk now (many, many issues)

Would it be possible to use the Prodinfo from my junk switch to restore to my good switch?

No, the prodinfo is device specific. You might be able to find something here that can help you, depending on the details of your issue:
https://gbatemp.net/threads/switch-unbricking-guide-prodinfo-fix-pikafix.578026/

 

[I_AM_L_FORCE]

No, the prodinfo is device specific. You might be able to find something here that can help you, depending on the details of your issue:
https://gbatemp.net/threads/switch-unbricking-guide-prodinfo-fix-pikafix.578026/

The switch itself can boot sysnand just fine with/without CFW. The only issue appears to be the wiping of the serial and certs. HoS is not actually bricked itself. Could I skip all the Boot0/1 in this tutorial?

 

[Lacius]

The switch itself can boot sysnand just fine with/without CFW. The only issue appears to be the wiping of the serial and certs. HoS is not actually bricked itself. Could I skip all the Boot0/1 in this tutorial?

If the Switch can boot and isn't bricked, then you will not benefit from the above guide. Are you saying that the new switch has the prodinfo blanked, and you want to be able to go online with it? Without a prodinfo backup, this Switch will never go online to connect to Nintendo's services.

 

[I_AM_L_FORCE]

If the Switch can boot and isn't bricked, then you will not benefit from the above guide. Are you saying that the new switch has the prodinfo blanked, and you want to be able to go online with it? Without a prodinfo backup, this Switch will never go online to connect to Nintendo's services.

Precisely. Thank you, so just to be clear I cannot use the Prodinfo from the other switch at this time?

 

[Lacius]

Precisely. Thank you, so just to be clear I cannot use the Prodinfo from the other switch at this time?

It is currently impossible to get your Switch online without a prodinfo backup from that Switch. A prodinfo backup from another Switch will not help you.

 

[Draxzelex]

Precisely. Thank you, so just to be clear I cannot use the Prodinfo from the other switch at this time?

It will most likely never be possible so your only solution is to buy another console.

 

[Tamalulu]

You could do it with https://github.com/PabloZaiden/deviceid-exosphere-builder

 

[I_AM_L_FORCE]

You could do it with https://github.com/PabloZaiden/deviceid-exosphere-builder

Care to elaborate?

 

[Draxzelex]

You could do it with https://github.com/PabloZaiden/deviceid-exosphere-builder

Care to elaborate?

This is moreso for recovering a bricked console without an eMMC backup. This is NOT to restore online functionality.

 

[Tamalulu]

Care to elaborate?

You would write the prodinfo from your junk console to your functional one and use a custom exosphere to spoof the device id to match the prodinfo so that the console boots.

This is moreso for recovering a bricked console without an eMMC backup. This is NOT to restore online functionality.

It should work though. It's a bit more complicated if the prodinfo is personalized (roughly, ipatched or Mariko devices).

 

[I_AM_L_FORCE]

This is moreso for recovering a bricked console without an eMMC backup. This is NOT to restore online functionality.

Wooooo online time

You would write the prodinfo from your junk console to your functional one and use a custom exosphere to spoof the device id to match the prodinfo so that the console boots.



It should work though. It's a bit more complicated if the prodinfo is personalized (roughly, ipatched or Mariko devices).

Does the Prodinfo have to be re-encrypted with the recipient consoles keys? And does the whole nand need to be donor's or just the Prodinfo

 

[Tamalulu]

Wooooo online time

Does the Prodinfo have to be re-encrypted with the recipient consoles keys? And does the whole nand need to be donor's or just the Prodinfo

Well you still have to use the console's own BIS keys, but the prodinfo in itself shouldn't need reencrypting if it comes from a Erista unpatched. Haven't tested but, I would guess only the prodinfo needs to come from the donor console. Your best bet is to follow the instructions at https://github.com/PabloZaiden/deviceid-exosphere-builder

 

[Draxzelex]

Its been over a week so something tells me it didn't work.

 

[I_AM_L_FORCE]

Its been over a week so something tells me it didn't work.

To be honest, I built the exosphere and injected the unencrypted Prodinfo from the other switch only, but it refused to boot.

 

[Maupiti]

Well you still have to use the console's own BIS keys, but the prodinfo in itself shouldn't need reencrypting if it comes from a Erista unpatched. Haven't tested but, I would guess only the prodinfo needs to come from the donor console. Your best bet is to follow the instructions at https://github.com/PabloZaiden/deviceid-exosphere-builder

what about the serial number ? To be able to go online ?

 

[Tamalulu]

To be honest, I built the exosphere and injected the unencrypted Prodinfo from the other switch only, but it refused to boot.

Are the two Switch the same kind (Lite, Erista, Mariko...)? Have you followed all the steps at https://github.com/PabloZaiden/deviceid-exosphere-builder ?

what about the serial number ? To be able to go online ?

What do you mean? The serial number actually has little to do with going online AFAIK.

 

[I_AM_L_FORCE]

Are the two Switch the same kind (Lite, Erista, Mariko...)? Have you followed all the steps at https://github.com/PabloZaiden/deviceid-exosphere-builder ?


What do you mean? The serial number actually has little to do with going online AFAIK.

Yes, to both.

 

[Maupiti]

If the Switch can boot and isn't bricked, then you will not benefit from the above guide. Are you saying that the new switch has the prodinfo blanked, and you want to be able to go online with it? Without a prodinfo backup, this Switch will never go online to connect to Nintendo's services.

Thanks for confirming what I posted ( And also @Draxzelex of course) and just went “kicked off” by @Tamalulu. There’s no way to connect to Nintendo servers for online without the unique Id/serial number linked to the hardware .
@Tamalulu How do you think banning works...?, If it was so “simple”, unbanning units will be possible, which is not the case. I pointed the unit, not the account.
That’s also why, you can’t use a license Sxos from one switch to another, saying that, saying “nothing”.

 

[Tamalulu]

Yes, to both.

Well, if it is not even booting, you probably did it something wrong as the whole purpose of https://github.com/PabloZaiden/deviceid-exosphere-builder is to make your console boot. Is it stuck on the Nintendo Switch logo? Are you using the atmosphère version matching the one of your custom exosphère?

Thanks for confirming what I posted and just went “kicked off” by @Tamalulu. There’s no way to connect to Nintendo servers for online without the unique Id/serial number linked to the hardware .
@Tamalulu How do you think banning works...?, If it was so “simple”, unbanning units will be possible, which is not the case. I pointed the unit, not the account.

The prodinfo is what makes a console unique. When Nintendo decides to ban someone, they probably revoke some, or all, of the certificates that are contained in that prodinfo. The console verifies that the device id of the prodinfo matches the one from fuses at boot. Once you spoof that device id and it's booted, you could theoretically use the prodinfo as-is and connect to online services.

I never said unbanning was easy as this requires another, not banned, prodinfo. Nobody's gonna buy a new console to unban a previous one.