https://gbatemp.net/threads/am-i-broke-format-on-mmc-chip-and-is-this-even-possible-to-fix.647844/
Probably he did this broke it.
https://gbatemp.net/threads/am-i-broke-format-on-mmc-chip-and-is-this-even-possible-to-fix.647844/
Probably he did this broke it.
Yup, so I'm stupid asf.Oooh.... now I remember... yeah he ran "This is in Tegraexplorer, when I try to use systemwipe.te" and poof nand gone
EDIT: You need to use Pika Bricker Fix guide or use that v3 guide with updated software.
Really want to try first one.Well your answer is simple
1) Use a donor nand and get it up and running again
2) Put it on a shelf and hope someone release a hack that can generate the needed keys
3) Sell it as faulty/parts only
Now I know it. But it's too late...Thats why any solid guide advices you to make a nand backup before messing with your system.
It also relies on ProdInfo_Gen. If you say i doesnt work for 17.x.x, then probably no.https://gbatemp.net/threads/switch-unbricking-guide-prodinfo-fix-pikafix.578026/ (Can't guarantee it works)
Yeah, but this one does - https://github.com/suchmememanyskill/EmmcHaccGenIt also relies on ProdInfo_Gen. If you say i doesnt work for 17.x.x, then probably no.
I mean in theory. Since Atmosphere patches the fuses requirementI wonder if you can simply generate a set of keys and then rebuild the nand from a 14.0.0 firmware. I mean the nand currently is wiped anyway so ... idk. I have never been in this situation so its all just guesswork, but it cant possibly get worse so .. its worth a try?
Hekate does that, to be the nerd here. But yeah. I dont see why it shouldnt work, as long as the generated prodinfo has all the nessesary things to allow the manual nand generation. Here is the guide i have in mindI mean in theory. Since Atmosphere patches the fuses requirement
SXOS did not in the past messed up CAL0 and BOOT0?Cal0 is basically prodinfo content. I dont know how one can detroy this other than mounting something that shouldnt be mounted and messing with it or using Incognito or something like it.
How do you know that your nand backup is broken too? I find it hard to believe, especially if you did the backup before messing with things.
It's unable. Not even recovery mode is there.so far I think console is unable to boot on OFW
Indeed, I wonder if they ever solved ithttps://github.com/suchmememanyskill/TegraExplorer/issues/45
this issue smells similar to the op having