I bought two 3ds' with issues recently. One had a broken power pin, replaced it. This other one however is completely unresponsive upon boot up. There are no icons on the screen either. The only controls that work are the power button and the wifi switch. I tried removing the battery but that didn't help. I'll be taking it apart to remove the touch panel and see if that changes anything, but I'm waiting for a screw driver to come in since mine isnt thin enough. What do you guys think it might be? It doesnt seem to be liquid damage. Have an update already. Grinded down my screw driver to fit. Disconnected the touch screen, circle pad, sd card reader, wifi, ir, and home buttons. But I still got nothing. It seems like the system is completely halted. Date is 1/1, system time stays as 0:00 Maybe this is a failed updated? Or bricked. Which i doubt since this came from a lot of other things that was mostly kids stuff.
seen a few people with this issue, i believe its a corrupt FW issue, not sure if you follow the 3ds scene, but there is something called emunand which is basically for running a copy of the nand from the SD card, i had this issue when running a emunand, and it wasn't a hardware issue, removing the emunand and replacing it with a old backup resulted in it working fine again......so im pretty sure its pretty much bricked unless you had a nand dump from the console before it went wrong you could see if you can run a update by following these steps.....got to be worth a shot Power the system off. Press the power button, then immediately press and hold down the L button, R button, A button, and Up on the +Control Pad. Keep holding down the buttons until the system update screen is displayed. Tap OK on the system update screen.
Well the update screen came up, but it says that theres a parental lock on it. And I cannot push ok or press any buttons still. I tried another touch screen just to be sure.
hmmm so its detecting you pressing the physical buttons if it lets you access the update screen i backed up my "bad" firmware, i will see if i can get that working any way, but....im not sure, maybe if you can try cleaning the motherboard up a bit see if there is any shorts that could be causing issues......just wondering if it is indeed the same issue, does the 3ds freeze on a black screen when powered on, then if you press the power button it goes to the "do you want to turn off the system" screen, then if you press home it will start to load the home screen, but freeze with the "home screen" text and never make it to the actual home screen found a few more button combo's for various things, a interesting one would be the auto boot game.....see if it will run a game and if it functions in game normally EDIT: actually it seems this one will only work before the initial setup has been run...probably only intended for shops to let people test without having to format each time The following auto-boot paths can be used by Home Menu, checked in the same order listed below(the above gamecard auto-boot is checked before this): [TABLE="class: wikitable"] [TR] [TH] Key-combo / requirements for this path[/TH] [TH] Description[/TH] [/TR] [TR] [TD] R, L, and X[/TD] [TD] This launches System Settings for touchscreen calibration.[/TD] [/TR] [TR] [TD] R, L, and Y[/TD] [TD] This launches System Settings for circlepad calibration.[/TD] [/TR] [/TABLE] The following is only checked when the low u16 from config block 0x00110000 is value zero(normally this is non-zero). Thus, the below is only handled when a system setup is required. [TABLE="class: wikitable"] [TR] [TH] Key-combo / requirements for this path[/TH] [TH] Description[/TH] [/TR] [TR] [TD] R, X, Y, A, and B, a 3DS gamecard must be inserted as well.[/TD] [TD] This launches the gamecard application. Note that pressing the HOME button in the gamecard application launched this way will only result in the system shutting down.[/TD] [/TR] [TR] [TD] This is used when the above path isn't used.[/TD] [TD] This launches System Settings for the system setup.[/TD] [/TR] [/TABLE] one more piece of info i can gather is that the 3DS must be on FW 3.x or lower, as with 4.x you can no longer set a parental lock on system updates
Try as I might the combos won't boot up into calibration menus. I'll keep giving it a go. I can tell you that in the update screen the home button does function now, but just brings up the home icon with a slash through it. It does indeed boot up to the home screen. But it acts as though I have been holding down on an empty icon, as the "create folder" option is what is shown. And the 3d slider doesn't function either. But it wouldn't surprise me if its just broken. And for entering the update menu, maybe I'm not quick enough, but unless I held down L+R+ up prior to power on it would never boot into the system update. Obviously moving quickly to hold A. Maybe just a funky r or l button.
hmmmm ok so its not the same as my issue, your seems more like a faulty touch screen (but you already tried another one so its not the digitizer) so it will likely be an issue with either the touch screen connector or possibly the touch screen controller...try giving the whole board a good clean and look around the traces where the touch screen connects to for any signs of damage or "crap" stuck in there at this point i would say its probably not a software issue...it would of been good to get the touch screen calibiration screen up though, i tested those combo's on my 3ds and they do work........could you of left the L or R button disconnected when you opened it at all, or maybe even damaged the ribbon cable ....you could try the back panel from the other 3ds on it to see if its the L or R button causing issues though
You know that's not impossible since I don't recall if I reconnected the l+r last night. I'll check once I've returned home. I probably didn't as I wanted to sleep lol I don't think its touch screen issue only because even when the touch panel is disonncected it still boots to "create folder" I'll check the traces for the touch screen. I gave a general look on the cardtidge side before and didn't see anything iffy. I have spare parts from a few 3ds that were fried so I can try replace everything except the mobo.
yeah, you could try dropping the motherboard into the other 3ds too, will at least let you 100% isolate the issue to the motherboard
They were connected =/ the other 3ds was an XL unfortunatelty. I do have my own 3ds but it's an ambassador console, so I don't want to mess it with it more than I need to.