Hacking Updated to 6.2 Now I cannot boot CFW or OFW

[Philliyxx]

I used my own nand back up. It was a restore not a rebuild. I did disable RCM to boot into official but it crashes at Nintendo logo. I was able to reapply auto rcm.

So data on the user partition..is there a way to tell what fw my nand was or what fw I'm on without being able to boot. I honestly can't remember if it was 4.1 or if I did the nand back up after i updated to 5.1 now...

 

[smf]

is there a way to tell what fw my nand was or what fw I'm on without being able to boot.

You can tell what fuses are burned using briccmii, which tells you what fw your switch can boot without a dongle.

 

[Philliyxx]

You can tell what fuses are burned using briccmii, which tells you what fw your switch can boot without a dongle.

Yes I know that. I had 5 burned. In theory I could boot back to a 4.1 ofw, which is what I tried as I believe that is the fw my nand backup was which I restored. But since I can't boot into ofw now I want to verify what vofw version is on my emmc

 

[DPyro]

Yes I know that. I had 5 burned. In theory I could boot back to a 4.1 ofw, which is what I tried as I believe that is the fw my nand backup was which I restored. But since I can't boot into ofw now I want to verify what vofw version is on my emmc

Can you not view the files in hex editor to see which version?

 

[PrEtZaL]

You can look here to check the dump version https://gbatemp.net/threads/firmware-version-inspector-get-fw-version-from-nand-dump.515308/.

But if your restored a nand dump the user partition will have also been restored so it's not that.....it's going to be your boot0 and boot1 files.

Either check out the link I posted or rebuild your nand to atleast 5.1.0 using choidujour, full instructions here....

https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Just make sure you make a backup of your boot0 and boot1 files if you dont have any already. The nand backup you have contains prodinfo and prodinfof.......all of which are unique to your console

 

[Philliyxx]

Thanks. You have been very helpful and I will look I to this and try and report back

 

[benjo]

Cant you use a nand backup from another switch?

 

[Philliyxx]

NAND dump that I restored to confirmed to be 4.1, fuses still confirmed at 5 burned. Interesting though I dumped my biskeys on 5.1 before I upgraded to 6.2.

Now if I dump them I am missing crypt and tweak which are an the orginals.txt

bis_key_00 = XXXXXXXXXXXXX
bis_key_01 = XXXXXXXXXXXXX
bis_key_02 = XXXXXXXXXXXXX
bis_key_03 =XXXXXXXXXXXXX

 

[Philliyxx]

NAND dump that I restored to confirmed to be 4.1, fuses still confirmed at 5 burned. Interesting though I dumped my biskeys on 5.1 before I upgraded to 6.2.

Now if I dump them I am missing crypt and tweak which are an the orginals.txt

bis_key_00 = XXXXXXXXXXXXX
bis_key_01 = XXXXXXXXXXXXX
bis_key_02 = XXXXXXXXXXXXX
bis_key_03 =XXXXXXXXXXXXX

Before I take the long process of rebuilding my nand, should i just try to restore my boot 0/1 again ? and not the whole nand?

 

[Draxzelex]

Cant you use a nand backup from another switch?

NAND is console-specific

 

[TunaKetchup]

Why do this happen? This is not the first time i read about this and the reason why i am afraid to update.

Cheap SD cards imo

 

[Philliyxx]

Cheap SD cards imo

Don't see how the SD card caused my issue. Seems more 6.2 fw related to me

 

[PrEtZaL]

See if you can pass entropy on partitions using hacdiskmount using BISKEYS you dumped on 5.1, ie with tweak and crypto if not this will be your issue or atleast part of it.....

Since the switch will be using the tweak and crypto keys to access these partitions and if it fails, switch will not boot

If this is all good you'll need to update to 5.1.0 using choidujour as files in the SYSTEM partition will not work since you updated to 6.2.0 at some point.

Alternatively you can mount the SYSTEM partition in hacdiskmount, go into save folder and delete everything bar 8000...120, but this will be like doing a system initialise. The boot files will likely need to be written to as well if you've not restored these from the correct fw version.

Your best bet is to follow the guide to updating without burning fuses for 5.1.0 keeping your data, but this will only work if you can pass entropy using your keys in hacdiskmount

If entropy fails you'll need to encrypt the partitions using the correct keys, if you need help let me know

 

[Philliyxx]

See if you can pass entropy on partitions using hacdiskmount using BISKEYS you dumped on 5.1, ie with tweak and crypto if not this will be your issue or atleast part of it.....

Since the switch will be using the tweak and crypto keys to access these partitions and if it fails, switch will not boot

If this is all good you'll need to update to 5.1.0 using choidujour as files in the SYSTEM partition will not work since you updated to 6.2.0 at some point.

Alternatively you can mount the SYSTEM partition in hacdiskmount, go into save folder and delete everything bar 8000...120, but this will be like doing a system initialise. The boot files will likely need to be written to as well if you've not restored these from the correct fw version.

Your best bet is to follow the guide to updating without burning fuses for 5.1.0 keeping your data, but this will only work if you can pass entropy using your keys in hacdiskmount

If entropy fails you'll need to encrypt the partitions using the correct keys, if you need help let me know

Having issues at STEP 7: GENERATE the files/images to be transferred to the console via ChoiDujour

Exception: [WARN]: Failed to match key "encrypted_header_key", (value "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "eticket_rsa_kek", (value "nokey")

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

Having issues at STEP 7: GENERATE the files/images to be transferred to the console via ChoiDujour

Exception: [WARN]: Failed to match key "encrypted_header_key", (value "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx")
[WARN]: Failed to match key "eticket_rsa_kek", (value "nokey")

I have deleted these keys in the keys.txt and now it is populating the files.

 

[Mythical]

Cant you use a nand backup from another switch?

Nand backups are unique to each console (and for every system that I know of) so no and it'll always be that way
rip already said :b

 

[Philliyxx]

Nand backups are unique to each console (and for every system that I know of) so no and it'll always be that way
rip already said :b

Just finished the whole process. Launced my FS_XXX option (XXX being a firmware version) it was EX_FAT, (my card is FAT32)

Now I am hanging at Nintendo Switch screen

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

Just finished the whole process. Launced my FS_XXX option (XXX being a firmware version) it was EX_FAT, (my card is FAT32)

Now I am hanging at Nintendo Switch screen

I see you said "keep your data" I chose to do the system initialize as it was noted as the safer option.

 

[josephdin]

This is triggering my anxiety, i hope the issue gets solved,or at least figure out the cause

 

[Philliyxx]

This is triggering my anxiety, i hope the issue gets solved,or at least figure out the cause

I used windows file explorer to transfer the SYSTEM files, some people had issues, guess I will try again with TOTAL COMMANDER

 

[Philliyxx]

I used windows file explorer to transfer the SYSTEM files, some people had issues, guess I will try again with TOTAL COMMANDER

No luck with Total commander either :/

 

[PrEtZaL]

If you did it properly when you boot it should show the red nintendo logo and play the video leading into user settings.

It's possible you have a corrupted fs, the data on the sd card may have been corrupted and not written to the nand correctly.

But all should be able to be resolved, run gptrestore from rajkosto then do as before but also try mounting the USER and SYSTEM partitions WITH BISKEYS entered (so you can access the files) in hacdiskmount and formatting in guiformat....MUST format in 16k then transfer files you extracted as before in choidujour to each partition.

You will only ever need the boot0, boot1, prodinfo and prodinfof partitions with your BISKEYS to recover from anything.