Can I ask if this is a problem - ie that it might affect my use of SYSNAND in any way? What are my options if so? Or are BOOT0/1 unchanging - ie there is no problem as long as I have restored my backups?
Accidentally restored BOOT0/1 to SYS instead of EMUMMC
- Thread starter grcd
- Start date
- Views 1,254
- Replies 4
Its only an issue if your sysMMC and emuMMC firmware don't match as BOOT0/BOOT1 are firmware specific.
Okay to answer everyone's Qs:
Yes the system was 'soft-bricked' as there was a version mismatch. But I found the relevant BOOT0/1 backups and restored it and got it working again. So everything was solved - and I was glad I had my backup files handy.
Yes the system was 'soft-bricked' as there was a version mismatch. But I found the relevant BOOT0/1 backups and restored it and got it working again. So everything was solved - and I was glad I had my backup files handy.
Similar threads
-
@
Sicklyboy:
@SylverReZ, Oh yeah, arguably doing better than ever. They're releasing new sets constantly for it+1 -
-
-
@
SylverReZ:
Nice. I wish they bought back collectable figurines in blind bags, which I had as a kid. -
@
Sicklyboy:
I like buying the Halo Megablox blind bags every once in a while when I see them. Scratches that itch
-
-
-
@
hitorikuroi:
i have a question currently my atmos switch isnt picked up by pc on HOS but the cable and port do work with apx and tegra so i know the hardware is good, any clue? -
-
-
-
-
-
-
@
Psionic Roshambo:
Well on a good day life does suck... lol on a bad day it just sucks differently lol+3 -
-
-
-
-
-
@
BakerMan:
it's just in an empty open space, like outside at night or the backrooms, depending on the branch of the hypothetical you either feel unsafe, but you actually are safe, or you feel safe, but are unsafe, also you don't actually know the truth about your safety either way -
-
-
-