Hacking Can someone with a banned switch help me repair mine?

[guyman70718]

Maybe use the --fix-hashes option.
I would suggest flashing boot0, boot1 and bcpkg2 and running lockpick_rcm to get more of your own keys (assuming you started from internet keys).

Maybe use the --fix-hashes option.
I would suggest flashing boot0, boot1 and bcpkg2 and running lockpick_rcm to get more of your own keys (assuming you started from internet keys).

--fix-hashes did nothing. I'll flash those three files now and dump my own keys and try it again

 

[guyman70718]

Maybe use the --fix-hashes option.
I would suggest flashing boot0, boot1 and bcpkg2 and running lockpick_rcm to get more of your own keys (assuming you started from internet keys).

I keep failing here. I tried flashing the prodinfo that your tool generated but it still says that the BIS keys are bad

 

[Tamalulu]

First, you don't need the prodinfo to run lockpick_rcm. Second, this is normal: your nand contains the prodinfo from the original console it was attached to, encrypted with different bis keys; decrypting it with your own bis keys outputs high entropy data (basically random).
You'll see the test turn green after you've written the generated prodinfo with your own bis keys.

 

[guyman70718]

First, you don't need the prodinfo to run lockpick_rcm. Second, this is normal: your nand contains the prodinfo from the original console it was attached to, encrypted with different bis keys; decrypting it with your own bis keys outputs high entropy data (basically random).
You'll see the test turn green after you've written the generated prodinfo with your own bis keys.

I wrote generated_prodinfo_from_scratch.bin to the PRODINFO (partition?) in HacDiskMount and the test still fails. I generated a new prod.keys after writing boot0,1 and bcpkg2 and generated prodinfo using those prod.keys

 

[Tamalulu]

When I say "written the generated prodinfo", I mean restored it from file using HacDiskMount (actually pressing the "Start" button despite the test failing).

The truth is, you could even restore a blank file with HacDiskMount, the test will turn green as long as you are using the same BIS keys.

 

[guyman70718]

When I say "written the generated prodinfo", I mean restored it from file using HacDiskMount (actually pressing the "Start" button despite the test failing).

The truth is, you could even restore a blank file with HacDiskMount, the test will turn green as long as you are using the same BIS keys.

I selected the file your tool generated using my prod.keys and clicked start, then put the BIS keys generated from https://www.sdsetup.com/biskeygen in the boxes and it fails the test

 

[Tamalulu]

View attachment 234256
I selected the file your tool generated using my prod.keys and clicked start, then put the BIS keys generated from https://www.sdsetup.com/biskeygen in the boxes and it fails the test

Are you using the same BIS keys every time? Derived from your console's TSEC and SBK keys? As said earlier, the test failing is unrelated to the generated prodinfo (unless it is garbage data).

Steps:
- Fill in your bis keys.
- Restore prodinfo from file (press "Start")
- Test the bis keys again, it has to be green

 

[guyman70718]

Are you using the same BIS keys every time? Derived from your console's TSEC and SBK keys? As said earlier, the test failing is unrelated to the generated prodinfo (unless it is garbage data).

Steps:
- Fill in your bis keys.
- Restore prodinfo from file (press "Start")
- Test the bis keys again, it has to be green

Ahh, i got it now. I was writing the prodinfo while the BIS keys area was blank still. Yes I am using the bis keys derived from my specific console

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

Are you using the same BIS keys every time? Derived from your console's TSEC and SBK keys? As said earlier, the test failing is unrelated to the generated prodinfo (unless it is garbage data).

Steps:
- Fill in your bis keys.
- Restore prodinfo from file (press "Start")
- Test the bis keys again, it has to be green

So now prodinfo checks out fine, what do I write to PRODINFOF? I assume a different BIN file is required for PRODINFOF to be written?

 

[Tamalulu]

Ahh, i got it now. I was writing the prodinfo while the BIS keys area was blank still. Yes I am using the bis keys derived from my specific console

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


So now prodinfo checks out fine, what do I write to PRODINFOF? I assume a different BIN file is required for PRODINFOF to be written?

Just checked, a 100% blank PRODINFOF works fine as it seems to only be accessed in Settings -> System -> Additional Information menu.
You can probably leave it as it is now.

 

[guyman70718]

Just checked, a 100% blank PRODINFOF works fine as it seems to only be accessed in Settings -> System -> Additional Information menu.
You can probably leave it as it is now.

Should I overwrite it with a blank file or just leave it with the old console's PRODINFOF

 

[Tamalulu]

I expect the old console's PRODINFOF to work just fine, here's a blank:
(not a bmp image)

 

[guyman70718]

I expect the old console's PRODINFOF to work just fine, here's a blank:
(not a bmp image)

OK, done. PRODINFO and PRODINFOF both are clear with BISKeys. Now for SAFE, SYSTEM, and USER, how do I go about restoring them? In the guide it says to check if the BIS keys check out, then mount them and drag the files ChoiDuJour (or EmmcHaccGen) generated for each of those partitions into the partition. Can I do that even though the BIS key check fails, or do I have to overwrite them with a blank file too?

 

[Tamalulu]

First, have you regenerated the firmware files with your very own prod.keys?
Then, you'll do like for the PRODINFO: put your BIS keys and mount despite the test failing. Windows will probably complain and you'll have to format SAFE, SYSTEM and USER in FAT32.

 

[guyman70718]

First, have you regenerated the firmware files with your very own prod.keys?
Then, you'll do like for the PRODINFO: put your BIS keys and mount despite the test failing. Windows will probably complain and you'll have to format SAFE, SYSTEM and USER in FAT32.

You mean did I rerun EmmcHaccGen with my own prod.keys? I didn’t, should I? If so should I rewrite boot0, 1, and bcpk2 files after regenerating them?

 

[Tamalulu]

You mean did I rerun EmmcHaccGen with my own prod.keys? I didn’t, should I? If so should I rewrite boot0, 1, and bcpk2 files after regenerating them?

Yes, you have to rerun it. No, you shouldn't need to rewrite boot0, 1, and bcpk2 files.

Actually, maybe rerunning is not mandatory but I'd do it anyway :-^

 

[guyman70718]

Yes, you have to rerun it. No, you shouldn't need to rewrite boot0, 1, and bcpk2 files.

Actually, maybe rerunning is not mandatory but I'd do it anyway :-^

I reran it and the md5 hashes are the same, so I wont bother reflashing them.

 

[guyman70718]

Yes, you have to rerun it. No, you shouldn't need to rewrite boot0, 1, and bcpk2 files.

Actually, maybe rerunning is not mandatory but I'd do it anyway :-^

Ok, USER, SYSTEM, and SAFE all have their files copied and now pass BIS key check

 

[guyman70718]

Yes, you have to rerun it. No, you shouldn't need to rewrite boot0, 1, and bcpk2 files.

Actually, maybe rerunning is not mandatory but I'd do it anyway :-^

Yes, you have to rerun it. No, you shouldn't need to rewrite boot0, 1, and bcpk2 files.

Actually, maybe rerunning is not mandatory but I'd do it anyway :-^

Console still wont boot into atmosphere, any ideas? Someone is telling me that it has to do with boot0 missing encrypted keyblobs?

 

[Tamalulu]

What happens, do you get to the Switch logo? Keyblobs shouldn't matter for 6.2.0 but you could get them with linkle and try running a lower version with ChoiDuJour.

 

[guyman70718]

What happens, do you get to the Switch logo? Keyblobs shouldn't matter for 6.2.0 but you could get them with linkle and try running a lower version with ChoiDuJour.

Wait, should it be able to boot without fusee-primary? I was told that even when this is repaired, it will only boot from rcm, will never boot normally again. I was trying fusee-primary and was getting an error, hold on i forgot what it was and I am backing up my current progress

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

What happens, do you get to the Switch logo? Keyblobs shouldn't matter for 6.2.0 but you could get them with linkle and try running a lower version with ChoiDuJour.

Nope, I don't even get a nintendo logo when I click restart>OFW in hekate.