Ah, we just send them a new ID, make a new account, will be fineGood chance we will all be banned from online, should expect it.
(Not that I actually want to go online with a CFW)
Ah, we just send them a new ID, make a new account, will be fineGood chance we will all be banned from online, should expect it.
They will probably system ban, not account ban....Ah, we just send them a new ID, make a new account, will be fine
(Not that I actually want to go online with a CFW)
I expect them to do bothThey will probably system ban, not account ban....
One more distinction - playing online might be possible with emunand. If the emulation is low level enough, maybe there is no way to build in detection.
Two issues:
- That part of the system would work "as a retail unit" (no modifications)
- Not sure, if installation can be done without decrypting at least the container. (Probably wrong use of that figurative concept..) meaning, not sure, If we would have to "own" all prior firmwares, to be able to install the next one as emunand
Good to know.Also - seems logical, ATM.
![]()
Yea more chance Nintendo just won't care, but starting with 3ds seems they do.well yea its 100% possible. It's also possible we could be invaded by aliens tomorrow and they share tech with us that lets us go unnoticed when playing pirated games online.
Yea more chance Nintendo just won't care, but starting with 3ds seems they do.
The nice part of owning the trustzone hypervisor
Potentially put the OFW on internal NAND to avoid timing issues and sdcard need all together? Put cfw on sdcard? (Custome TZ on internal NAND o.c.)![]()
