Init eMMC Failed, no NAND backups

[StringIsNullOrEmpty]

If you followed one of the guides like this one chances are you will get a 2105-0584 error crash when you update to any firmware above and including 14.0.0, despite updating atmosphere/sigpatches.
If so, go to https://github.com/CaramelDunes/prodinfo_gen and grab the latest version of prodinfo_gen.bin.
Use hekate to place the donor_nand.bin from the guides into the /switch folder, and use RCM to inject prodinfo_gen.bin.
Follow the on screen instructions to create a PRODINFO using a donor nand (not from scratch!)
Go back to hekate and copy the generated_prodinfo_from_donor.bin file onto your computer.
Use hekate to load the eMMC that is having problems, with read-only protection OFF.
Use NxNandManager to load the drive, and click on PRODINFO (not the one with f at the end) and select restore from file.
Pick the generated_prodinfo_from_donor.bin and let it restore, this should only take a second.
Once you're done try to launch CFW again, it should work now.

 

[ewabc886]

If you followed one of the guides like this one chances are you will get a 2105-0584 error crash when you update to any firmware above and including 14.0.0, despite updating atmosphere/sigpatches.
If so, go to https://github.com/CaramelDunes/prodinfo_gen and grab the latest version of prodinfo_gen.bin.
Use hekate to place the donor_nand.bin from the guides into the /switch folder, and use RCM to inject prodinfo_gen.bin.
Follow the on screen instructions to create a PRODINFO using a donor nand (not from scratch!)
Go back to hekate and copy the generated_prodinfo_from_donor.bin file onto your computer.
Use hekate to load the eMMC that is having problems, with read-only protection OFF.
Use NxNandManager to load the drive, and click on PRODINFO (not the one with f at the end) and select restore from file.
Pick the generated_prodinfo_from_donor.bin and let it restore, this should only take a second.
Once you're done try to launch CFW again, it should work now.

In case someone like me uses file base emunand instead of partition method emuMMC.
We have our emummc system broken by 14.0+ in file 00
which should be located somewhere like
sd root/ emummc/HPE0/eMMC/00
alongside files 01, BOOT0, BOOT1

this cannot be mounted by Hekate through the USB method
instead, I read 00 with HacDiskMount
then recover the PRODINFO with "generated_prodinfo_from_donor.bin"