Hacking Help my n3ds bricked
- Thread starter blackblaze
- Start date
- Views 8,880
- Replies 82
I don't really understand what actually went wrong, and why your N3ds bricked... Did you finish updating and installing 9.5 on your 3DS before you turned it off? Wouldn't the N3ds do a soft reset after updating the sys.firmware anyways? If the N3DS it was turned off before the firmware fully installed, I can understand why it bricked, otherwise it seems a bit strange that it just bricked like that... 
He should not have been trying to update to 9.5 in the first place This is just another case of someone jumping into the deep end of the pool without knowing how to swim.I don't really understand what actually went wrong, and why your N3ds bricked... Did you finish updating and installing 9.5 on your 3DS before you turned it off? Wouldn't the N3ds do a soft reset after updating the sys.firmware anyways? If the N3DS it was turned off before the firmware fully installed, I can understand why it bricked, otherwise it seems a bit strange that it just bricked like that...
Its really not that difficult to do though, I jumped into it and my 3DS is working in spectacular condition if I must say so myself.
My general rule of thumb is to ALWAYS make a backup of my NAND even if I don't intend to do anything to my system. That way, if anything happens (Such as any friends accidentally updating my system through a cartridge update), I still have an option to get a NAND mod installed and revert to 9.2/4.3.
Additionally, keep the NAND backups safe, whether it's archiving them on a hard drive (Or multiple hard drives for good measure), a cloud-based service (Dropbox, MEGA, OneDrive, Google Drive, etc etc), or any number of portable devices (USBs, SDs, cellphones) so that if anything happens, you have options.
well at this point the only recovery options are finding the file on your computer (pretty sure installing a new OS shouldn't actually delete any files unless you specifically pick to format the drive) or if recovery mode works, which im assuming it didn't in your case?
try searching your entire computer for NAND.BIN it may have just been put in a different directory unless you did choose to format the drive too......but you mention there being a "windows old" directory which suggest you didn't, so its probably still there somewhere
try searching your entire computer for NAND.BIN it may have just been put in a different directory unless you did choose to format the drive too......but you mention there being a "windows old" directory which suggest you didn't, so its probably still there somewhere
Judging from the fact that windows.old is empty and it's not anywhere on his hard drive even after doing a search with a hex editor, I think his NAND backups are permanently destroyed and will no longer have a way to revert. That is unless he has a USB or SD that has a copy of the NAND backup, but that doesn't seem to be apparent.
yeah but the fact the windows old directory is there suggests he didn't actually format (or there wouldn't even be a windows old folder), but installed windows 10 over whatever he was previously on......as to why its empty now....maybe he doesn't have hidden folders visible, or he just deleted the files manually after installing windows 10
I know it's best to stay on ~9.2 and never touch on sys.nand, but I can see someone want to upgrade nand past 9.2 for a game he really wanted, especially to play online, use eshop, etc, even if at the cost of using homebrew. I just don't understand what actually caused it to brick, even more so since he even managed to see he was on firmware 9.5 through system settings... Could it be that it's not safe to update N3ds through 3dsnus, or something?
its never been advisable to update sysnand via cia files, there is a specific route you have to go about doing so....personally if i wanted to update past 9.2, i would just update the normal route to 9.9, no point updating to 9.5 either way you loose your exploitable console
and? nobody is really bothered *why* he updated....just why he thought updating to 9.5 specifically would be a good idea, if the game he wanted needed him to update to 9.5, then he could just use the game to update....but if your going to update to a non exploitable FW, why not just do it like normal, i am just a bit confused as where the craze for trying to update sysnand via cia files came from as there is very few instances where doing so is helpful in any way yet i keep seeing threads with people bricking trying to update sysnand with cia files
Yes by using sysUpdater 0.4.1 while in Emunand or while using Pasta CFW while in Sysnand.
--------------------- MERGED ---------------------------
We have Emunand for that very reason and the only reason you should update Sysnand past 9.2 is if you have a hard mod installed to flash your previous NAND back.
Also lets say he did everything right it means he either modified a previous system title (AGB_FIRM/System Settings) or his 3DNUS downloads were corrupt OR he pulled his MicroSD out mid transfer/did not safely eject it from his PC.
LOL he updated for a puzzle game and now he cant play no type of games.
--------------------- MERGED ---------------------------
I just went through your post history and you state you have 4 copies of an EMUNAND and you are reprimanding another member for bricking his console SMH...
D
Deleted-355425
Guest
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
@
SylverReZ:
You can make a post on the DS forum about your findings, and they'll do their best to respond. They have a GBAtemp account here, you know. -
@
Materia_tofu:
oh ye i made a post i did forget they had an account i prob shouldve tagged them in the post+1
tbh -
-
-
-
-
@
BakerMan:
Update on my brother: He's home now, tired and hungry, obviously, but other than that, seems to be doing fine.+2 -
-
-
@
BakerMan:
Well, from what I've heard from my parents, he had a seizure last night, perhaps an epileptic episode, fucking died, had a near death experience, my dad called the paramedics, they showed up, took him to the hospital, and he woke up covered in tubes, and started complaining.
-
-
-
-
-
-
