Depends. It would have to be analyzed whether or not the space which it occupies can be accessed to "launch something".So is the crash that occurs when 3DS mode tries to read corrupted DS mode settings useful at all?
It's fake. Nothing plays 3DS ROMs.HOW DID YOU GET THE PASSWORD FOR THE 3DS LOADER?!?!?! PLESE REPLY.
holy shiznits! i was about to say....It's fake. Nothing plays 3DS ROMs.HOW DID YOU GET THE PASSWORD FOR THE 3DS LOADER?!?!?! PLESE REPLY.
But Rydian, you made it... you ought to know it's real.
It's not really real, Bryan162
On the 3DS there is one firmware title which handles both DSi and DS mode.DS Mode brickers have no effect whatsover on a DSi, and I doubt it would on a 3DS.Then using a DS mode bricker shouldn't be able to stop DSiWare, no?No, but that seems like it would help us dump DSiWare or something. DS st00f without the need for a flashcart..Not experienced in any form of hacking/coding, but if a bricker can write 0 over everything, why can't it write something else?
Because to the best of everyone's understanding, the DS Bios is sandboxed. So you might -potentially- be able to do something in DS mode, but that would probably be of little use in 3DS mode.
After the first time, anyway.
But IIRC, DS mode and DSi mode are sandboxed seperately, unless I'm missing something.
Still, with something like an iEvo (LOLOLOL) or a DSi-only/enhanced game... Who knows?
Is that in anyway exploitable?? Could code be run from that part of the 3DS nand??
Shame. There I thought it could be a pointer to on-cartridge data...Is that in anyway exploitable?? Could code be run from that part of the 3DS nand??
No its just info sorry
Shame. There I thought it could be a pointer to on-cartridge data...Is that in anyway exploitable?? Could code be run from that part of the 3DS nand??
No its just info sorry