I have a mod Japanese Dsi ( 1.3J, twilight 21.1.0 , Unlaunch 2.0 ) and i dont know what would happen if i update it , and should i update it to latest version
There is literally nothing to gain unless you want to re-download purchased DSiWare. Most of these updates were attempts to block flashcarts.I have a mod Japanese Dsi ( 1.3J, twilight 21.1.0 , Unlaunch 2.0 ) and i dont know what would happen if i update it , and should i update it to latest version
Do you have a source for that? Would have caused a lot of warranty claims since the updates came out when the DSi was new and the shop was actually usable.Not to mention updating has been known to brick even stock DSis
I've no idea where this idea comes from. This gets repeated over and over again, but I never saw any proof for this. Furthermore I can't confirm this from own testing. The NAND seems to be a standard Samsung chip and I couldn't get one to fail by overwriting the complete chip multiple times with a hardmod (not that I would have expected a NAND to fail after a few cycles; but this is what is told all the time about DSi NAND chips: "Bad quality, dead after a few write cycles!").because the NAND died a natural death (Nintendo put some shitty one in and expected it to last.)
iirc at least two people have come to the DS⁽ⁱ⁾ Mode Hacking! Discord server with DSi's that bricked after doing System Updates and I've seen at least one more on r/NDSHacks or somewhere, I know I've seen it happen at least three times. Unfortunately I'm not able to find the messages though as there's 211,530 message in the Discord help channel and Discord's search is kinda awful... This all in the past 2 or so years, dunno if it ever happened back when the DSi was actually new.Do you have a source for that? Would have caused a lot of warranty claims since the updates came out when the DSi was new and the shop was actually usable.
I've no idea where this idea comes from. This gets repeated over and over again, but I never saw any proof for this. Furthermore I can't confirm this from own testing. The NAND seems to be a standard Samsung chip and I couldn't get one to fail by overwriting the complete chip multiple times with a hardmod (not that I would have expected a NAND to fail after a few cycles; but this is what is told all the time about DSi NAND chips: "Bad quality, dead after a few write cycles!").
Discord server. Well… what should I say to that? Unfair prior conditions. My searches on that topic only included the freely available sources on the internet. Things that can be found with a general search engine without signing up on some closed place. (To go even further off-topic: That is one of the reasons, why I dislike Discord. Locking important pieces information behind a login is not a good idea)iirc at least two people have come to the DS⁽ⁱ⁾ Mode Hacking! Discord server with DSi's that bricked after doing System Updates and I've seen at least one more on r/NDSHacks or somewhere, I know I've seen it happen at least three times. Unfortunately I'm not able to find the messages though as there's 211,530 message in the Discord help channel and Discord's search is kinda awful... This all in the past 2 or so years, dunno if it ever happened back when the DSi was actually new.
So it's not a common occurrence by any means, but it's definitely a (small) possibility. It seems to be about likely to happen as a brick when installing Unlaunch, which makes sense as both are writing to files that would cause a brick if the write somehow failed. And neither have a reason for a brick to make sense besides just the NAND dying of overuse, I have no confirmation but it's possible the ones that are bricking are ones where people took a lot of photos or played a lot of DSiWare or such, would make sense but no way to prove it unless someone bricks, knows their DSi's history, and shares about it...