seems 2 users have had their 3ds "semi-bricked" by updating sysnand whilst in gateway mode on 2.4b, despite this being mistakes on both users parts, i think we can agree that it seems there is a issue there, so word of warning just make 100% sure you have emunand set up and follow the guides to the letter......as if you enter gateway mode while on sysnand and run a update your console will likely end up with the good old black screen of death(not to be confused with the brick code blue screen of death)
im thinking there must be some sort of bug here as the worst that should happen is sysnand would be updated
im pretty sure this will this can be fixed by just re-flashing a nand backup via a hardmod....but again make 100% sure you have a nand backup and make 100% sure you have picked format emunand before running a system update on 2.4b
Just to clarify as long as you see GW3D#.# and not Ver.#.# in system setting you should be fine it only appears to happen to people who haven't set emunand up and where already well on their way to a updated system nand anyway
im kinda guessing gateway might actually be apply some sort of patch or something to the nand as its updated, (which is why its not booting when applied to the sysnand) but works in emunand....this is the most logical explanation to me
im thinking there must be some sort of bug here as the worst that should happen is sysnand would be updated
Just to clarify as long as you see GW3D#.# and not Ver.#.# in system setting you should be fine it only appears to happen to people who haven't set emunand up and where already well on their way to a updated system nand anyway
im kinda guessing gateway might actually be apply some sort of patch or something to the nand as its updated, (which is why its not booting when applied to the sysnand) but works in emunand....this is the most logical explanation to me