Hacking Restored 5.1.0 NAND to 6.1.0, Switch does not boot anymore, Hekate stuck on Launch

[caller]

I restored a NAND Backup from 5.1.0 to my Switch which was on 6.1.0. I can see that the Switch wouldnt boot normally due to burnt fuses count. However Hekate doesnt boot either, it tells me that package1 version is from 6.1.0 ('20180802162753'), keyblob version 5, and is stuck after printing "Loaded package1 and keyblob".
Am I missing something? Or is this expected behavior?

 

[PrEtZaL]

It's expected since your boot files relate to fw 6.1. If you have boot files for 5.1 restore those.

If not you'll need to rebuild them

 

[caller]

If you mean BOOT0/1, I did restore these too. Do I need some special files for Hekate to boot into Horizon?

 

[PrEtZaL]

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

Concentrate on steps 7,8.2,8.3 and 9

Yes you need files on your sd card, hekate is just a payload....you'll need files on your sd card as well. Have you not booted using hekate before?

 

[caller]

I followed Steps 7,8.2,8.3 and 9. It does not boot either, but it does behave different. The Switch now turns off after a while being stuck again in hekate after launching the "FS_XX..." option. It shows package1 ('20180220163747') and keyblob version 4. After that a black screen and nothing (seemingly) happens.
I did use hekate for booting into atmosphere, but I havent used it to boot after restoring a lower firmware NAND.

 

[PrEtZaL]

Where did you get your boot0 and boot1 files from?

Used choidujour I hope

 

[caller]

Yes, I used Choidujour to generate the files to write to the Switch when in memloader emmc mode. I followed the steps, but nothing changed.
I also tried to write the 6.1.0 update to the Switch, which ends up in the same situation as in the first post, being stuck when booting "FS_XX..." option. I feel like somehow the Switch does not want to boot up anymore, at least not into Horizon OS

 

[sunflower1978]

Maybe a bad DUMP?

 

[caller]

There seems to be no way of checking if the dump is valid, but I can open it in HacDiskMount and after entering the bis keys, mount and browse the partitions, so it seems to me that the backup may be valid.
I have also tried the manual downgrade to 5.1.0 using HacDiskMoun deleting all SYSTEM and USER files on the Switch emmc, so the Switch is essentially factory reset, but booting in Hekate does not work after that either. Also after upgrading to 6.1.0 again as described in the Tutorial, also deleting any SYSTEM and USER files, yields the same result, always stuck in Hekate after selecting the appropriate Launch option.

 

[Flocka]

There seems to be no way of checking if the dump is valid, but I can open it in HacDiskMount and after entering the bis keys, mount and browse the partitions, so it seems to me that the backup may be valid.
I have also tried the manual downgrade to 5.1.0 using HacDiskMoun deleting all SYSTEM and USER files on the Switch emmc, so the Switch is essentially factory reset, but booting in Hekate does not work after that either. Also after upgrading to 6.1.0 again as described in the Tutorial, also deleting any SYSTEM and USER files, yields the same result, always stuck in Hekate after selecting the appropriate Launch option.

Did you ever figure anything out?

 

[subcon959]

I've never done a nand restore so can't help, but I would like to know what is going on here that these types of threads pop up on such a regular basis. Surely, it's not just user error every single time?

If you restore boot0/1 and rawnand from 5.1 onto 6.1 shouldn't you be able to boot straight into hekate again? Why do some people have to resort to using hacdiskmount after the hekate restore failed to let them boot?