Hacking Does nintendo actively blocks emunand in each update?

  • Thread starter Thread starter simonhwsn
  • Start date Start date
  • Views Views 1,844
  • Replies Replies 4

simonhwsn

Well-Known Member
Newcomer
Joined
Nov 23, 2011
Messages
47
Reaction score
2
Trophies
0
XP
146
Country
United States
It may be a very silly question but in the case of DS flashcarts nintendo blocks (or used to block?) them actively by changing the whitelist, is it kind of the same situation with emunand? or it gets blocked inherently due the firmware version change?
 
They have been intentionally trying to block it since 8.0, so updating to a non-currently supported FW by GW is a bad idea.
 
For DS (not 3DS) there is one file as whitelist inside updates.

Starting emuNAND and loading launcher.dat, it needs memory hooks and the offset might change in updates for region fix/breaking sign and so on.

The result after Nintendo updates Firmware might be blackscreen oder missing functions until Gateway udpates the launcher.dat.
 
I don't think they block anything tho... The way emunand works is 4.5 is still running at the base , along with the exploit. This shouldn't let the 3ds know that it's running an emulated nand... I think the emunand breaks when new features are present ( 7.x keys , themes , theme shuffle) and neither the gateway launcher or the 3ds 4.5 firmware know how to handle them
 
Emunand breaks when Nintendo touches Home menu portion of firmware. GW uses hardcoded patch offsets it seems.
 

Site & Scene News

Popular threads in this forum