So, the title there says New 3DS, which is is the “New 3DS” but it’s also New, in the sense that I bought it at the start of January. It’s like 3 or 4 weeks old. Then I broke it on accident. It’s taken me years to get around to saving the money to buy one of these, not so much because I don’t have the money, but because I wanted to know it was at a point in it’s console life cycle that it was worth buying. If it has been say, $50 cheaper, I’d have bought one years ago. Also, unlike all of my previous Nintendo based hand helds, I wanted to wait to get the “improved version”. I have a Game Boy, a Game Boy Advanced, a Nintendo DS, but they were all the first gen models. I didn’t care for the 3D gimmick, so I passed on the 3DS. Well now they have the horribly branded “New 3DS” and in my case, it’s the XL version, because I like having a big honking screen.
I’ve played it pretty regularly since buying it. This is kind of the problem with my argument of “waiting for the right moment”. My track record with Nintendo hand helds has always been amazing. I measure this by one real metric, how many games do I finish on them? I’m pretty sure I’ve completed every game I own for Nintendo’s handhelds since the Game Boy, and I own a lot. Contrast this with say, Steam, where I’ve beaten like 20% of my 1000+ game Steam Library.
On a side note story, that’s related here, the water out of the faucet at work is awful, there’s crap floating in it and it’s scummy and possibly not healthy (probably is for legal reasons though). So in order to make my coffee each morning, I carry a metal water bottle with water from home, usually in my lunch box.
Anyway, a week or so ago, I put my 3DS in my bag I carry and went off to work. On this particular day, I didn’t bring a lunch, so I just had my laptop bag and no lunch box. I stuck my water bottle in the side pocket of my bag and drove off to work. Upon arrival I found the bottom of my bag was wet and the top of the water bottle was not fully attached. Incidentally, the water bottle was also empty.
I headed into the office to assess the damage here. Headphones, some notes, the bottom of the bag and my 3DS were all wet. Bummer. I took everything that was damp and strung it around to dry out for a while and went about my day. Later, as things were drying I tested the 3DS. This was my fatal mistake, it turned on, but the cursor on the bottom of the screen was flipping constantly (due to water inside making an electrical contact) and when I tried to turn if off I got a cryptic message flashed up about “There is some kind of problem something something) before it turned off, for good.
I set it out to dry some more, hoping this would correct the issue. It still didn’t turn on some time later, so I set about opening it up. I’d already removed the back cover and battery, now it was time to crack open the case. It turns out it’s a pretty simple task thankfully, there’s maybe 8 small screws holding the case shut. You’ll also need to remove any SD cards.
Side not to anyone trying to do this, there are two small ribbon cables along the top edge of the system that come off with the back cover. These operate the shoulder buttons. To actually remove the cover, you must lift the top edge gently a bit, so they the whole thing can slide down and over the headphone jack, then the cover rolls/flips towards the upper side of the 3DS, minding these cables along the way. The cables can be removed and may even pop off, this is ok so long as they don’t get damaged. They ultimately need to be removed anyway, using some small pliers or a screw driver, to remove the black square from the main part of the 3DS. These connectors are designed to be removed and reinserted easily.
After removing the cover, I had a nice view of the inside of the 3DS.

On the plus side, once inside, things were not as bad as they might seem. The way the handheld sits in my bag, only one end of it got any sort of water (the left end shown above). On the minus side, there was a lot of water, like I had to get paper towels and dry it up all over inside, including removing the face buttons. To get to the underside water, I had to also remove that board on the left side, it has 5 screws, 4 in the central area, and one near the bottom ribbon cable.

Once everything was dried, I reassemble it and tried to turn it on again, with no success. So I opened it up again for a deeper inspection. This was when I found what I should have noticed originally, the painfully obvious blown out components on the board.

Nothing else inside seemed to be damaged at all and all of the moisture was on this end of the console. So I figured I’d look into replacing this power board (the batter connects to this board). I figure spending $50 on a new board would be better than $200 on a new 3DS. Fortunately, these boards can be found all over online, and even more fortunately, it only cost me around $15 to order one, a real deal non knockoff one too.
A week later, I had the new power board, time to swap. It’s pretty straight forward as well, I removed all of the screws first. Next there are two small ribbon cables that attach to the board, the one broad orange one and another smaller one at the top for the secondary nubbin that is on the New 3DS models. The large orange one was simple, since the new board came with a new ribbon cable, potentially damaging the old one wasn’t a problem. I was still careful to slide it out of the end on the main part of the 3DS. After removing it, the gray bar is able to flip up so the new cable can be slid in and aligned, then the gray bar snaps back down to secure it.
The second smaller cable was a bit trickier, but due to it’s small size, I was able to flip the bar piece holding it down up using a small screw driver. Once these cables were swapped, the new board gets screwed in. Carefully reattach the two cables on the case cover for the ribbon cables, there is a natural orientation to these when the cover is attached, though it’s slightly twisted around with it removed. Once everything was reassembled and screwed down, I reinserted the battery for the moment of truth of powering the system back on.
Which was successful!
I’m not saying this will fix any broken 3DS, there’s all sorts of other issues that could come up, especially with water. This is more just how I was troubleshooting and fixed mine.
A Myriad of Little Projects
I’ve neglected posting much lately, not so much because I haven’t been doing anything but more because I’ve been busy and not really with anything deserving of it’s own post. I hope to remedy this a bit next year but for now I just wanted to run through some recent projects I’ve been working on.
The All New All the Same Lameazoid.com
Probably the biggest monopolizer of my time has been my other blog at Lameazoid.com. There isn’t a lot there now, but my intention is to do a relaunch of sorts in 2017. I’ve managed to keep up with my current regular posting, which amounts to roughly two posts per week, one Weekly Haul post and a recap of Agents of SHIELD. I want to do much more next year. I even made up a spreadsheet to plan everything for the year.
I have regular content set up for every day of the week. The idea right now, is to build up a long runway. I have the time now to crank out reviews and take photos as needed. If all goes to plan, I will have content scheduled out through roughly May in every category. The idea is that this content, while good is a buffer that can be shuffled as needed for NEW content to be inserted on demand.
I’ve also taken steps to try to line up content with related new content. For example, Logan, comes out on 3/3. So in the weeks before, for the Marvel Movie Review of those weeks, I’ll do Wolverine and The Wolverine (yeah those names are similar and dumb). I could also pair this with some Wolverine related Marvel Legends reviews, or maybe some other Hugh Jackman reviews.
I’ve been up to a few new tech related projects lately as well.
Mail-In-A-Box
I’ll probably do a post just on Mail-in-a-Box and my set up experience. Mail-In-A-Box is a simple install Mailserver for hosting your own email. I’ve spun up a second VPS and attached this domain to it, since I previously didn’t have any email for this domain. It was a little tricky but I worked things out. The hardest bit is that Mail-In-A-Box wants to handle the DNS and core domain, but I’m hosting these things on two separate servers.
I’ve gotten a little extra cozy with DNS lately, but I also had an issue come up because Mail-In-A-Box seemed to be pushing the SSL https domain for BloggingIntensifies.
Encryption Everywhere
You might notice, I’ve enabled HTTPS on this blog. This came out of necessity since after setting up Mail-In-A-Box, Firefox kept forcing the site to the HTTPS version, which nothing was set up for so it didn’t load. This is a change I’ve been meaning to make anyway since the launch of LetsEncrypt! Google is supposed to start penalizing non HTTPS sites at some point plus it’s good practice anyway. I set up HTTPS for this blog, Lameazoid.com and Joshmiller.net. Once I am confident in things I’ll set it up for TreasuredTidbits,.com and TheZippyZebra.com as well.
I had some issues with Joshmiller.net though because of the way Cloudflare works.
Cloudflare Integration
I also recently added Cloudflare to all of my sites. Cloudflare is essentially a DNS provider but it also lets you mask and reroute traffic to help protect your server. I had to pull BI off of it though to get Mail-In-A-Box to work and apparently Lameazoid.com wasn’t set up for rerouting. I ended up having trouble with Joshmiller.net when I tried to enable SSL encryption. Basically, as near as I can tell, the set up was looking at the Cloudflare IP and not the server IP, so things weren’t meshing or hooking up properly. Everything corrected itself once I removed the Cloudflare rerouting. I still need to play with this a bit before I set things up on my wife’s two blogs.
Part of why I experiment with my blogs vs hers is that I get way less traffic and I don’t like to irritate her.
Cloud At Cost VPS
I did a post on Cloud At Cost, but I wanted to mention it again as a recent project. I have two VPSs from them, plus some. I’m still having issues with the Windows VPS but the Linux one has been running pretty well since I got it up and running.
PLEX Server
My Synology NAS has the ability to act as a PLEX server. I recently cleaned up a bunch of space on the NAS by throwing some spare drives into an older machine and creating a “Deep Archive” for things that I never need to access that take up a lot of space (read: My 500GB of raw video from ten years of my bi annual DVD making projects). I also shoved some things like old ISOs and Game Install files onto the Deep Archive. I then proceeded to start filling this new space with rips of my DVD collection. I’m still working on the long and arduous ripping process as time allows but the idea is to run everything through PLEX to the two Firesticks I’ve set up on each TV. This means my family doesn’t have to drag out a huge binder of DVDs to find a movie and it means I can stop worrying about discs getting scratched up and ruined.
It also gives me a nice way to watch all of the home video footage I’ve recorded over the past 10+ years. This whole project met a bit of a roadblock when I found that I need to pre transcode all of the video in PLEX before it becomes watchable. The NAS isn’t powerful enough to transcode it in real time.