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

[l7777]

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

Yes, it will restore the partitions for any files it finds. You'll also want to restore boot0 and boot1

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?

Right, you'll need to put them under a restore folder under the new id folder

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 is rebuilding the OS in this step. I'm assuming that since you were able to get a proper backup it won't need rebuilding. You also have your PRODINFO things so those shouldn't need rebuilding either.

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.

You could completely rebuild everything but I'm going off the assumption that your system data is good. That could still end up a false assumption but you won't know until you try.

Just trying to find the easiest way

Right, my steps above were essentially an if 1 doesn't work go to 2, if 2 doesn't work go to 3. If 1 works, then no need to do any more steps. There's no harm in trying an option and it failing since you have backups and are restoring to a new EMMC.

 

[MiguelDiaz]

Yes, it will restore the partitions for any files it finds. You'll also want to restore boot0 and boot1

Right, you'll need to put them under a restore folder under the new id folder

He is rebuilding the OS in this step. I'm assuming that since you were able to get a proper backup it won't need rebuilding. You also have your PRODINFO things so those shouldn't need rebuilding either.

You could completely rebuild everything but I'm going off the assumption that your system data is good. That could still end up a false assumption but you won't know until you try.

Right, my steps above were essentially an if 1 doesn't work go to 2, if 2 doesn't work go to 3. If 1 works, then no need to do any more steps. There's no harm in trying an option and it failing since you have backups and are restoring to a new EMMC.

Just got the replacement chip today, but sadly it doesn't work.

Picofly gives me these error messages, from the eye they both look the same to me, I ordered as 32gb.

Not sure If I'm missing something

 

[l7777]

Probably worth asking in the picofly thread. My guess is retrain the chip as the new emmc might have a different glitch timing. I've only done this with a V1 unpatched. They can boot Hekate even without an emmc attached.

 

[MiguelDiaz]

Probably worth asking in the picofly thread. My guess is retrain the chip as the new emmc might have a different glitch timing. I've only done this with a V1 unpatched. They can boot Hekate even without an emmc attached.

Well I tried to boot mine without an eMMC and it doesn't boot, mine is a V1 patched

 

[l7777]

Well I tried to boot mine without an eMMC and it doesn't boot, mine is a V1 patched

Oh yeah only unpatched units can do that, the mod chips monitor communication between the EMMC and SOC to determine when to glitch. Thus why a retrain might work. The picofly folks will know the best though.

 

[MiguelDiaz]

It seems that the eMMC doesn't work or doesn't have the 4mb boot partition to get Hekate to work.

I just found this on AliExpress:
5,17€ | EMMC to USD Board EMMC to USB (MicroSD) Adapter Board MicroSD EMMC Modules for ROCK PI 4A/4B
https://a.aliexpress.com/_EzTVk

You think this could work to write any partitions to it?

Can you please put the link of the picofly thread?

 

[impeeza]

It seems that the eMMC doesn't work or doesn't have the 4mb boot partition to get Hekate to work.

I just found this on AliExpress:
5,17€ | EMMC to USD Board EMMC to USB (MicroSD) Adapter Board MicroSD EMMC Modules for ROCK PI 4A/4B
https://a.aliexpress.com/_EzTVk

You think this could work to write any partitions to it?

Can you please put the link of the picofly thread?

you should format and restore a NAND on the EMMC BEFORE try to boot the pico fly, AND THAT CAN BE ONLY ACHIEVE WITH LINUX AND THE RIGHT ADAPTER.

 

[MiguelDiaz]

Yes, it will restore the partitions for any files it finds. You'll also want to restore boot0 and boot1

Right, you'll need to put them under a restore folder under the new id folder

He is rebuilding the OS in this step. I'm assuming that since you were able to get a proper backup it won't need rebuilding. You also have your PRODINFO things so those shouldn't need rebuilding either.

You could completely rebuild everything but I'm going off the assumption that your system data is good. That could still end up a false assumption but you won't know until you try.

Right, my steps above were essentially an if 1 doesn't work go to 2, if 2 doesn't work go to 3. If 1 works, then no need to do any more steps. There's no harm in trying an option and it failing since you have backups and are restoring to a new EMMC.

Got the new eMMC, Hekate works fine.

But I'm not able to restore the partitions to it.

When I mount it has a raw gpp partition, NxNandManager comes with "input file/drive is not a valid nx storage"

Sometimes I get purple screen and have to reboot a few times to get to Hekate.

I tried to restore the individual partitions from the old eMMC to the new one, using the new eMMC, but it won't boot, I just get Nintendo screen but never the switch logo.


Any thoughts? Thanks!

 

[l7777]

Got the new eMMC, Hekate works fine.

But I'm not able to restore the partitions to it.

When I mount it has a raw gpp partition, NxNandManager comes with "input file/drive is not a valid nx storage"

Sometimes I get purple screen and have to reboot a few times to get to Hekate.

I tried to restore the individual partitions from the old eMMC to the new one, using the new eMMC, but it won't boot, I just get Nintendo screen but never the switch logo.


Any thoughts? Thanks!

Did you restore Boot0/1 as well?
Will it go into maintenance mode? Select stock firmware from Hekate and hold Vol + and - together.

 

[MiguelDiaz]

Did you restore Boot0/1 as well?
Will it go into maintenance mode? Select stock firmware from Hekate and hold Vol + and - together.

Yeah I did boot0/boot1 first, then raw gpp all, and it does all the individual partitions separately.

Since I have partial user partition (only 4 files), it doesn't restore it, user stucks to 0% and finishes .

Also tried to do the level 2/3 guide from shtetix guide on YouTube with no avail.

Could be a bad capacitor around the eMMC? Or something else I could try?

Already tried with different picofly chip and still.

 

[impeeza]

Yeah I did boot0/boot1 first, then raw gpp all, and it does all the individual partitions separately.

Since I have partial user partition (only 4 files), it doesn't restore it, user stucks to 0% and finishes .

Also tried to do the level 2/3 guide from shtetix guide on YouTube with no avail.

Could be a bad capacitor around the eMMC? Or something else I could try?

Already tried with different picofly chip and still.

OR WRONG DAT0 RESISTORS.

 

[MiguelDiaz]

Did you restore Boot0/1 as well?
Will it go into maintenance mode? Select stock firmware from Hekate and hold Vol + and - together.

Finally got it working again

I did a boot0/boot1 and rawnand on the new eMMC just in case, but using my separate partitions broke the eMMC.

Also sthetix on his video mentions that we can to stop the backup/restore process at certain point when doing the user partition, but it broke the partition in my case.

I just restore the original rawnand.bin from the donor board using Hekate, and followed the level 2 guide process let to fully restore the user partition.

It booted!

Edit: now I just did a boot0/boot1 on rawnand backup, since now it's working fine.

Tried to restore this on the old eMMC to see if it was corrupted by the old owner or if it was physically damage and it works too.

Could possibly fail later? Now sure

 

[l7777]

Finally got it working again

I did a boot0/boot1 and rawnand on the new eMMC just in case, but using my separate partitions broke the eMMC.

Also sthetix on his video mentions that we can to stop the backup/restore process at certain point when doing the user partition, but it broke the partition in my case.

I just restore the original rawnand.bin from the donor board using Hekate, and followed the level 2 guide process let to fully restore the user partition.

It booted!

Edit: now I just did a boot0/boot1 on rawnand backup, since now it's working fine.

Tried to restore this on the old eMMC to see if it was corrupted by the old owner or if it was physically damage and it works too.

Could possibly fail later? Now sure

Great to hear you got it going! Hard to say what initially caused the issue. At some level electronics are all black magic. Now that you have a good backup save that somewhere good and if you ever have a problem again you have a known good backup. Based on your solution it sounds like you arrived where I would have ended up, take a donor rawnand and replace everything but the user partition with the backups you had. The original emmc probably doesn't have a hardware fault but Nintendo doesn't give us any good way to rebuild the software side of things. Fortunately we have Hekate and CFW to claw back some manner of control over the software. If you're concerned about future failures, just keep your saves backed up and if it fails again in the future you can simply restore the backup you have and then restore the saves.

 

[jkyoho]

I just restore the original rawnand.bin from the donor board using Hekate, and followed the level 2 guide process let to fully restore the user partition.

Have you tested serial number or going to e-shop?