Hardware Dead eMMC can't make emuMMC, any advice?

[MiguelDiaz]

I've a patched V1 Switch that on OFW gives this error:

I backed up BOOT 0, BOOT 1, PRODINFO and PROD.KEYS but I wasnt able to backup RAW GPP on Hekate because it gave me an error that the eMMC is on Slower mode at 45%.

Tried to back it up using NxNandManager but it gives an error during copy, see picture:

ibb.co/WvV1wDTp

I heard that I could just stop the backup on NxNandManager at User a 500mb (already have this rawnand.bin)

I saw this tutorial: but it says that I need to backup the RAW GPP partition first.

I'll order a new eMMC but I'm not sure if I'm able to use this donor eMMC without the Raw GPP Partition.

Any thoughs will be highly appreciated.

 

[fvig2001]

I mean, it will be you following the NAND rebuilding guide.

 

[MiguelDiaz]

I mean, it will be you following the NAND rebuilding guide.

I'm kinda new to GBATEMp, This guide? suchmememanyskill.github.io/guides/unbrick/#mmc-rebuild

 

[fvig2001]

https://gbatemp.net/threads/nand-rebuilding-for-no-backup-broken-emmc.593995/

 

[l7777]

Instead of trying to backup the entire raw gpp try to backup the individual partitions in the raw gpp. If you can get the console specific ones you should be able to rebuild a donor emmc with those and the encryption keys.

 

[LuigiGad]

if you have backed up the prod.info and prod.keys you should be fine and be able to recreate a new emmc from scratch. level 3 is for those who have nothing, you have prod.info and prod.key, in my opinion level 2 is more than enough.
level 2 only because you don't have a complete raw dump, otherwise a level 1 would have been enough

 

[MiguelDiaz]

Instead of trying to backup the entire raw gpp try to backup the individual partitions in the raw gpp. If you can get the console specific ones you should be able to rebuild a donor emmc with those and the encryption keys.

Can I do that using Hekate?

if you have backed up the prod.info and prod.keys you should be fine and be able to recreate a new emmc from scratch. level 3 is for those who have nothing, you have prod.info and prod.key, in my opinion level 2 is more than enough.
level 2 only because you don't have a complete raw dump, otherwise a level 1 would have been enough

So I would still need a new eMMC, I heard that you can't use online on OFW...or something similar, or the serial would be missing.

 

[l7777]

Can I do that using Hekate?



So I would still need a new eMMC, I heard that you can't use online on OFW...or something similar, or the serial would be missing.

Yes Hekate will allow you to backup the individual partitions. I believe it is simply called partition backup instead of raw backup. If you can get the console specific ones, PRODINFO specifically, you should be able to completely rebuild and use it as normal as you will still have your console specific serial and ssl certificates.

 

[LuigiGad]

Can I do that using Hekate?



So I would still need a new eMMC, I heard that you can't use online on OFW...or something similar, or the serial would be missing.

your unique data is in prod.info and prod.keys. for the rest you can recreate your emmc. Level 3 is for those who do not have the prod.info and keys.

 

[l7777]

your unique data is in prod.info and prod.keys. for the rest you can recreate your emmc. Level 3 is for those who do not have the prod.info and keys.

Rebuild from scratch (level 3) can be used to rebuild the PRODINFO partition using the prod.keys and a donor PRODINFO but cannot rebuild the the unique ssl certificates in the PRODINFO partition for online use. A rebuilt emmc WITHOUT a backup of at least the PRODINFO partition will not be able to go online for anything but system updates. If the OP can get a valid backup of his current PRODINFO partition(s) he can rebuild the emmc and still go online. Theoretically if the OP can get all the individual partitions and ~500mb of the USER partition he can fully rebuild a donor/replacement emmc.

 

[MiguelDiaz]

Yes Hekate will allow you to backup the individual partitions. I believe it is simply called partition backup instead of raw backup. If you can get the console specific ones, PRODINFO specifically, you should be able to completely rebuild and use it as normal as you will still have your console specific serial and ssl certificates.

Do you have a guide for that? I'm searching everywhere.

I'm able to backup the partitions individually.

I'm waiting for the eMMC donor that i bought from AliExpress

 

[LuigiGad]

Rebuild from scratch (level 3) can be used to rebuild the PRODINFO partition using the prod.keys and a donor PRODINFO but cannot rebuild the the unique ssl certificates in the PRODINFO partition for online use. A rebuilt emmc WITHOUT a backup of at least the PRODINFO partition will not be able to go online for anything but system updates. If the OP can get a valid backup of his current PRODINFO partition(s) he can rebuild the emmc and still go online. Theoretically if the OP can get all the individual partitions and ~500mb of the USER partition he can fully rebuild a donor/replacement emmc.

Exactly, he says he has a backup of both the product.info and the keys, so he doesn't need level 3 and should be able to come back online easily. As long as the eMMC is operational, but it can be easily replaced.

 

[l7777]

Do you have a guide for that? I'm searching everywhere.

I'm able to backup the partitions individually.

I'm waiting for the eMMC donor that i bought from AliExpress

No guide, but it's pretty strait forward if you understand the backup folder structure. It should look something like:

• backup
  • numerical_id for old emmc
    • partition
    • restore
      • partition
      • emummc
        • partition
    • emummc
      • partition
      • restore
  • numerical_id for new emmc
    • partition
    • restore
      
      • partition
      • emummc
        • partition
    • emummc
      • partition
      • restore

Some folders may or may not exist. If they do not, you can create them. You'll need hekate to create the numerical_id for the emmc though.

1. Save a copy of your backups if you haven't already.
2. Install new emmc
3. Boot hekate
4. Attempt to make a backup of boot1. This will create the numeric folder for the new emmc in the sdcard's backup folder.
5. Mount the sdcard in hakate
6. Copy/move the boot0, boot1, and partition backup files from the old emmc id to the corresponding location under the new emmc id/restore partition
7. Eject the mounted card
8. Restore boot0, 1, and partitions with hekate's restore functions.
9. Reboot and see if it worked.

 

[MiguelDiaz]

No guide, but it's pretty strait forward if you understand the backup folder structure. It should look something like:

• backup
  • numerical_id for old emmc
    • partition
    • restore
      • partition
      • emummc
        • partition
    • emummc
      • partition
      • restore
  • numerical_id for new emmc
    • partition
    • restore
      
      • partition
      • emummc
        • partition
    • emummc
      • partition
      • restore

Some folders may or may not exist. If they do not, you can create them. You'll need hekate to create the numerical_id for the emmc though.

1. Save a copy of your backups if you haven't already.
2. Install new emmc
3. Boot hekate
4. Attempt to make a backup of boot1. This will create the numeric folder for the new emmc in the sdcard's backup folder.
5. Mount the sdcard in hakate
6. Copy/move the boot0, boot1, and partition backup files from the old emmc id to the corresponding location under the new emmc id/restore partition
7. Eject the mounted card
8. Restore boot0, 1, and partitions with hekate's restore functions.
9. Reboot and see if it worked.

Oh!, so I don't need to rebuild anything or install a new firmware or something like that? or use NXNandManager.... I don't even need Raw GPP Backup then?

Thanks for your reply and your explanation!, it helped alot!.

 

[l7777]

Oh!, so I don't need to rebuild anything or install a new firmware or something like that? or use NXNandManager.... I don't even need Raw GPP Backup then?

Thanks for your reply and your explanation!, it helped alot!.

No nothing special needed. You're just restoring a backup. The Raw backup simply combines all the partitions into one file. The partition backup breaks them into individual files. In the end you have the same result, a complete backup of the emmc. In your case it sounds like the raw backup wasn't completing but the partition backup did. This should still allow you to effectively make the replacement emmc look just like the old one.

 

[MiguelDiaz]

No nothing special needed. You're just restoring a backup. The Raw backup simply combines all the partitions into one file. The partition backup breaks them into individual files. In the end you have the same result, a complete backup of the emmc. In your case it sounds like the raw backup wasn't completing but the partition backup did. This should still allow you to effectively make the replacement emmc look just like the old one.

After trying to backup the individual partitions, I can only do eMMC SYS.

I can't do eMMC USER.

However with NxNandManager I can stop the backup when is backing up the user at 1gb before crashing.

Can I use this rawnand.bin to restore it to my donor nand?

 

[l7777]

After trying to backup the individual partitions, I can only do eMMC SYS.

I can't do eMMC USER.

However with NxNandManager I can stop the backup when is backing up the user at 1gb before crashing.

Can I use this rawnand.bin to restore it to my donor nand?

Ok, so in that case you are likely going to have to so some kind of rebuild. If you can get Boot0, Boot1, and the eMMC SYS partitions you have a good start. The rebuild guides mostly walk through the process of decrypting the individual partitions from a donor NAND backup, re-encrypting them with the key from your console (prod.keys), and repacking them into a rawnand.bin file. Since you have most of the partitions, you can try restoring the partitions you have, and then beat the user partition into submission.

Given what you've described, below would be my attempts to get it going again:

1. Try to use NxNandMangaer and backup as much of the user partition as it will allow restore it to the new NAND and see what happens. If you're lucky you'll just have to re-install games.
2. Try would be to use the built in Switch Maintenance mode (Power on with Volume + & - held) to reset the console to factory settings.
3. Decrypt & re-encrypt a donor User partition and then the tegra explorer system wipe option.

 

[MiguelDiaz]

Ok, so in that case you are likely going to have to so some kind of rebuild. If you can get Boot0, Boot1, and the eMMC SYS partitions you have a good start. The rebuild guides mostly walk through the process of decrypting the individual partitions from a donor NAND backup, re-encrypting them with the key from your console (prod.keys), and repacking them into a rawnand.bin file. Since you have most of the partitions, you can try restoring the partitions you have, and then beat the user partition into submission.

Given what you've described, below would be my attempts to get it going again:

1. Try to use NxNandMangaer and backup as much of the user partition as it will allow restore it to the new NAND and see what happens. If you're lucky you'll just have to re-install games.
2. Try would be to use the built in Switch Maintenance mode (Power on with Volume + & - held) to reset the console to factory settings.
3. Decrypt & re-encrypt a donor User partition and then the tegra explorer system wipe option.

I saw a guide that by just doing the ~500mb user partition and using the rawnand.bin from NxNandManager, and using it as an Image with Rufus, I can format the nand and reinstall the system software.

You think this is possible?

 

[l7777]

I saw a guide that by just doing the ~500mb user partition and using the rawnand.bin from NxNandManager, and using it as an Image with Rufus, I can format the nand and reinstall the system software.

You think this is possible?

Right, I would try to get NxNandManager to backup something like that from your current emmc, but don't get confused between the individual partitions and a full Raw GPP (rawnand.bin) backup. Your goal is to restore from the individual partition files, not a rawnand.bin. Based on your previous post, it sounds like the only partition you couldn't successfully backup is the user partition. The rest should be able to restore directly to your replacement EMMC.

 

[MiguelDiaz]

Right, I would try to get NxNandManager to backup something like that from your current emmc, but don't get confused between the individual partitions and a full Raw GPP (rawnand.bin) backup. Your goal is to restore from the individual partition files, not a rawnand.bin. Based on your previous post, it sounds like the only partition you couldn't successfully backup is the user partition. The rest should be able to restore directly to your replacement EMMC.

Yes I have the individual partitions that I got from Hekate.

Just one question though, I'll be using these individuals partitions to restore them into my new eMMC

But I'll be using this option instead? Under restore GPP Partitions eMMC All

I'll have to backup first the replacement nand to get the numbers from it, then just add my files there and do a restore?

Then use tegra explorer to system restore?

Because sthetix on his unbricking level 1, he just use emmcHaccGen GUI with prod.keys, the firmware.

He uses SYSTEM and boot.bis on tegra explorer.

I guess this is something I can try?

I mean, I have prod.keys prodinfo, boot0 and boot1.

Just trying to find the easiest way