Your bootloader / bootrom. Those two will check to see if that console specific info is there. If you use someone else's, it can tell that it is not from your console.What stops a faked/borrowed/generated PRODINFO from working?
That's not something that can theoretically be edited or worked around with the bootrom exploit?Your bootloader / bootrom. Those two will check to see if that console specific info is there. If you use someone else's, it can tell that it is not from your console.
What stops a faked/borrowed/generated PRODINFO from working?
I don't think so.That's not something that can theoretically be edited or worked around with the bootrom exploit?
That's not something that can theoretically be edited or worked around with the bootrom exploit?
Ah so FG isn't low enough on the boot chain then to bypass the signature check. That truly does suck, and took a bunch of exploitable consoles out of commission.Pretty sure you'd need Nintendo's signing keys to do anything there, and we obviously don't have and never will have that.
Yours.a strange file appears that's not from team X And not on their website AND you download it and now your bricked. so who's fault is this?
You could overvolt the switch, which would literally fry it. You could also burn all fuses, making it impossible to boot without hekate.That being known how it works, I have another question. Would there be any brick that a payload can do, that you can NOT fix with a full raw NAND backup?
Just for future... reference.
Man, I can already see the future shenanigans happening.You could overvolt the switch, which would literally fry it. You could also burn all fuses, making it impossible to boot without hekate.
Yeah, that would probably be the best course of action.Man, I can already see the future shenanigans happening.
Better just get the new Switch up and running, get a new SX license and forget about every other payload in existence forever.
Wow, thanks for this input that really nobody else in this thread already brought up, and that helps so much.I bet most of the people who are bricked said tx are money grabbing scoundrels and they wouldn't use their products. Yet as soon as a "cracked" version comes they try jump on the sx bandwagon. It makes me chuckle immensely that for the sake of 30dollars or so which would have saved them 100s of dollars in money saved for backups. They now have a 300 dollar paperweight. I shouldn't be smug but I really really am
This is the truth tbh ^I bet most of the people who are bricked said tx are money grabbing scoundrels and they wouldn't use their products. Yet as soon as a "cracked" version comes they try jump on the sx bandwagon. It makes me chuckle immensely that for the sake of 30dollars or so which would have saved them 100s of dollars in money saved for backups. They now have a 300 dollar paperweight. I shouldn't be smug but I really really am
Your welcomeWow, thanks for this input that really nobody else in this thread already brought up, and that helps so much.
He spake the truth to be fair.I bet most of the people who are bricked said tx are money grabbing scoundrels and they wouldn't use their products. Yet as soon as a "cracked" version comes they try jump on the sx bandwagon. It makes me chuckle immensely that for the sake of 30dollars or so which would have saved them 100s of dollars in money saved for backups. They now have a 300 dollar paperweight. I shouldn't be smug but I really really am
He spake the truth to be fair.
All the warnings to be careful what payload you’re injecting and to take nand backup are all over the place.
If you choose to ignore and get burnt then well...