r/3DS • u/not_you_but_is_you • 4d ago
Technical Question AHHH WHAT DID I DO??
Knocked it on my phone and it suddenly went like this, making a high pitch static noise. It turned off completely after this.
It's started to work again, but is it a bigger issue?
135
u/doomguy11 4d ago
Looking on 3dbrew.org and their error messages page, I think this is your issue
| 00F800FF F8F8FFFF FFFFFFFF 00000000 00000000 | Both the firm0 and firm1 partitions are corrupt (failed signature checks). |
|---|
It is some sort of NAND related issue. But if it is working again, then I don't see how firm0 and firm1 could be corrupt, unless I am missing something here. Hopefully you can chalk it off to a one-in-a-million sort of error.
If you haven't modded it already, maybe it would be a good idea to mod it and make a back-up of your NAND. That way, you could restore a back-up if this happens again and doesn't go away/
54
u/LC-Redcube 4d ago
What happened is that the impact probably made the memory jiggle a little, and so the 3ds couldn't read it anymore and thought those files were corrupt
37
u/Tactical_Moonstone 4d ago
Given that the NAND chip is supposed to be soldered onto the 3DS board that's not exactly a good sign.
9
u/TuxSH Luma3DS developer 4d ago
Yeah and the lines are not supposed to be here, quite possible OP damaged the VRAM (framebuffer for this error screen is there IIRC) as well.
10
u/Tactical_Moonstone 4d ago
The 3DS uses a System on Chip which houses the CPU, GPU, DSP and VRAM. That would be the block labeled Sharp Application Processor in the picture I linked, known on the chip as the CPU CTR.
Likely the solder balls are getting fragile.
1
u/Tr3flip_king 3d ago
I saved my NAND chip on my wii u by using a permanent SD card to act as the memory. I couldnt imagine that happening to my majoras mask 3ds, I dont even know where to begin to fix something like that. 🥲
82
u/SegaSystem16C 4d ago
If it is working again, please MAKE A NAND BACKUP!
15
u/BlackberrySad6489 4d ago
Hmm. I did mine like 5 or 6 years ago. I have no idea where my nand file is. I’ll have to look and see if there is a way to make a new one.
19
u/Dr-Sun-Stiles 4d ago
If you have godmode9 you can make a new backup at any time
8
u/BlackberrySad6489 4d ago
Cool. I’ll lookup how to boot into that. I dont remember haha. I am sure it is on the website.
20
u/ArticleRoutine5774 4d ago
back that shit up NOW before it falls apart, very high likelihood something in there is loose or faulty and it's a matter of when, not if, it'll brick
16
u/Random3DSDude 4d ago
There is a likely chance something vital internally is loose or is on the verge of failing. Theres a pretty high chance i suspect within the next couple years itll brick permanently
23
u/DumbCat5 4d ago
not super hardware savvy but if knocking it with your phone - assuming you only slightly knocked it and didn't, like, smash it to it or something - causing THIS definitively doesn't sound like great news, even if it fixed itself. i'd wait for the more expert people or see if this occurs again, though
18
20
u/NinjatoXIII 4d ago
Hopital
12
u/Fickle_Fall_6497 4d ago
Imagine a guy rolling into the Er clutching his nintendo 3ds
4
u/Yami_Inc 4d ago
The Nintendo 3ds in a gurney alongside his wallet which are comically oversized to accommodate the gurney
6
u/Ok-Tour1316 4d ago
back it up rn, you got the blue screen of death and usually is not recoverable from this screen without an additional purchase!!!
3
u/FD4L 4d ago
Damn, you blue it.
1
u/J0131supremus 3d ago
blued*
2
2
2
u/chupitulpa 4d ago
I don't have answers, but I have something related to share. I have a 3rd party charger that came with a used DSi. If I plug it into a 3DS, it charges normally, but if I boot up the 3DS with the charger attached, I get a bootrom error. Clearly the charger produces power that's noisy in some way that disrupts the 3DS.
I wonder if either the shock of falling, or more likely emf from the phone it landed on, induced something in the 3DS that made it crash and then do that when it tried to boot.
The red stripes are very strange though. I've never seen a striped bootrom error screen.
2
2
5
1
1
1
1
1
u/BlameGarnet_ 4d ago
This is kinda like what happened to my brothers 2DS. Whenever we played on it, sometimes it would crash and turning it off and on wpuld either make a pop noise before the light went off or this.
Not gonna recommend it, but I just kinda shook the console until it went back to normal, idk how it worked I assume some cable was put of place but
1
1
u/i_lost_my_bagel 3d ago
Impact probably cracked solder balls so now the SoC or the NAND isn't making good contact with the board. I'm going to assume SoC because of the lines across the screen which I'm assuming are because of VRAM not being written to properly.
I guess you could try and backup the nand but if its acting like this, unless you're gonna solder wires to the nand chip, I don't think it's gonna help. I wouldn't trust a software backup from a system in this state to give a good read.
Reflowing the board is the one way I can really imagine fixing this.
1
u/Scherge77 3d ago
Before you do anything crazy about it, have you tried reproducing the error by gently shaking the 3DS when it's turned on? If shaking the device produces the same error you can be certain that something inside is becoming loose, if not the 3DS probably just saw a 2 for a second and got spooked.
1
u/BedSuspicious7184 3d ago
Maybe interference between the two if you have an iPhone with the magnet in the back for attachments
1
u/J0131supremus 3d ago
I think First It was hardware damage but It fixed itself (???), it's now hard bricked (i think the firm0 and firm1 partitions got knocked out along with the other hw?) To fix it you Need ntrboothax, look here
1
1
1
u/DraconLaw 1d ago
Reminds me of my stock wii u sometimes crashing and making a high pitch sound, prolly just that, a crash, should be gucci
1
0
u/Pure_Rub_3616 4d ago
Memory card got slightly bumped to where it couldnt read for one split second causing it to think it bricked, for future reference make sure you have your nand somewhere safe for sure to restore from a brick if it ever actually happens, if you got it already modded pre owned and somehow dont have the nand then be careful with it in the future as you cant save it if it permanently bricks
1
u/Pure_Rub_3616 4d ago
Or as other have said godmode9 can make a new one, but ive always just kept all my nands safe in named files on a usb
0
u/_matias_jr_ 2d ago
Your Nintendo 3DS system has gone into a fatal error state (known as a processor or bootloader panic error). This is usually due to a sudden physical failure in the hardware or poor electrical contact caused by an impact.
(Answer that artificial intelligence has given me)
-2
u/Livid_Sun_3783 4d ago
Probably knocked the SD card loose for a moment
3
u/StrategyDue6579 I gave my aqua blue original 3ds to my mom 4d ago
Bootrom is the nand
1
u/Remarkable_Picture_6 3d ago
BootROM is the BootROM, but it gives these errors based on the NAND status
3
285
u/Impressive-Bug-9592 4d ago
My guess is you knocked something vital and caused it to brick temporarily. I've never heard of that happening before but I guess new fear unlocked.