My ability to do Computer construction & Deconstruction:
I Fully Deconstructed a Computer has you can see in the photos. Showing Every part of it and that. I took everything out of the computer. And then Put it all back in the correct spot with every screw and Everything still worked and functioned Properly with Zero problems.
One of my more significant technical accomplishments involved repairing a Lenovo ThinkBook and successfully installing macOS Tahoe. This process required compiling an EFI bootloader with the correct drivers to boot without errors. I used the device for approximately one month without encountering any stability issues; the system remained reliable, with features like AirDrop and AirPlay/casting to Roku and other TVs functioning correctly.
I have hosted and maintained a Minecraft server for a solid four months with no issues, using a service called AMP ($20 one-time fee). Before this, I operated another server that ran perfectly for about five months and still is. I also bought the domain "dennisdanil.com" to streamline the connection process for players.
The server runs smoothly on the hardware I’ve built and configured. Through this process, I have learned how to port forward, keep the server up to date, and manage modded environments. I have also gained extensive experience configuring routers, servers, and computers to optimize them for hosting.
Another big accomplishment of mine is building a "Home Lab." Basically, I turned my house into a mini data center where I run my own private servers for games like Minecraft and other projects.
I also built my own custom computer bot from scratch using a programming language called Python, & C++, HTML, Ect. As of April 23, 2026, the bot has been running for over two years! I even made a simple webpage that I can open to change the bot's settings or just check on how it's doing.
Everything I’ve built is completely self-hosted, meaning I own and control all the equipment myself. My equipment lives in my closet, which makes it easy to manage while keeping everything quiet and cool. To make sure the connection is perfect, I ran Ethernet cables (Also making the cables myself) to all my devices so I don’t have to deal with the lag or drops you sometimes get with Wi-Fi.
I’ve come a long way since I started. My "first server" was actually an old Galaxy S10e that had a broken, blacked-out screen. Since I couldn't see anything on the phone, I used a program called scrcpy to see the phone's screen on my PC and learned how to use ADB (Android Debug Bridge) to control it. Through that, I learned how to use special commands to install apps, change the screen resolution, and take screenshots directly from my computer. The bot lived on that phone for a year before I moved it over to a small Raspberry Pi computer.
Here, I show that I know how to set up a Business network with network-attached storage, a Printer over Wi-Fi, and a scanner, all managed from a Wi-Fi router and multiple computers, with everything printed or scanned to/from the network-attached storage.
Here I'm demonstrating. I know how to set up a LAN party game on Minecraft. It is being hosted via my laptop, and we are all playing via LAN Only (IP to IP). I show that I know how to host and set up Local Area Networking without the need for the internet.
In this photo, you can see that I am capable of managing many laptops/devices at once, installing Windows, updating drivers, ect and I am capable of installing Windows on 15 laptops in one day with only 3 Windows installation media.
On May 21, 2026, I was given a water-damaged phone that wouldn't turn on, with the person hoping to recover their photos one last time. Drawing on visual clues and my knowledge of similar issues with devices like the S23 Ultra, I diagnosed a daughterboard failure caused by water corrosion on the contacts, which led to a kernel boot failure. By unplugging the damaged board, I stopped the kernel panics and allowed the phone to boot successfully into Android One UI, making it possible to transfer all their data to a new device. While we got lucky this time, it serves as a reminder of why everyone should back up their photos regularly, whether by using a personal NAS, paying for a cloud backup subscription, or storing files on an external drive. Unfortunately, I didn't take detailed photos during the repair process, so I have very few visuals to document the exact steps I took to recover the data.
On June 12, 2026, I received over 10 Samsung Galaxy Tab A (2016) tablets that had been retired from a workplace. The company no longer needed them and was giving them away. Before I worked on them, I was given explicit permission to reset the tablets and remove the security locks so they could be used again.
Most of the tablets were either locked by Google Factory Reset Protection (FRP) or were stuck on an enrollment screen. I used this as a chance to learn more about how Android security works and how to restore retired devices.
I used SamFW to download the correct firmware for Odin and also experimented with some of the tools it includes while trying different ways to get past the setup screens. After flashing the firmware with Odin and using different methods I had learned, I was able to remove the FRP lock and finish setting up every tablet.
At first, it took me about 1 to 3 hours to figure out the process by researching, testing different methods, and learning what worked. Once I had it figured out, I was able to reset each additional tablet in about 5 to 25 minutes, depending on how the tablet acted and whether I ran into any problems during the process.
In the end, I successfully reset every single Galaxy Tab A (2016). All of the tablets are now fully working and can be be used like normal Android tablets again instead of being thrown away.
I also worked on a Samsung Galaxy Tab S 10.5 (SM-T850) that had a different problem. It was still enrolled in ScaleFusion MDM, so it couldn't be factory reset because the MDM policy blocked it. Recovery Mode said that factory reset was disabled by MDM, and Download Mode showed it was running official Samsung firmware with FRP Lock: ON.
After spending time researching the problem and trying different approaches, I was able to remove the MDM restrictions with the organization's permission and restore the tablet to normal use. It now works like a regular Android tablet again.
This project taught me a lot about Android recovery tools, Samsung firmware, FRP, MDM enrollment, troubleshooting, and solving problems through research and testing.
Unfortunately, I didn't think to take any pictures besides two while I was working on the tablets, so I don't have any photos of the process.