I'm a student who likes figuring out how things actually work — especially when a device, OS, or piece of software says "you can't do that."

I'm heavily interested in Android internals, system modification, rooting, bootloader unlocking, ADB, Magisk, reverse engineering, and finding ways to squeeze more capability out of hardware and software.

I don't really like treating technology as a black box. If something is locked down, restricted, inefficient, or behaving strangely, my first instinct is usually:

"Okay, but why?"

And then I start digging. 🔧

• 🤖 Android internals & system modification
• 🔓 Rooting, bootloader unlocking & device customization
• 🧩 ADB / shell / system debugging
• 🪄 Magisk & systemless modifications
• 🔬 Reverse engineering & understanding undocumented behaviour
• ⚙️ Performance tuning and optimization
• 🖥️ PC hardware & GPU/CPU performance
• 🧠 Exploring exploits, loopholes, and unintended system behaviour
• 🎮 Game modification, configuration & optimization
• 📱 Making hardware do things it was never really meant to do

I like experimenting rather than blindly following instructions.

I'll usually start with a hypothesis, test it, break something, figure out why it broke, and then try again with a better understanding.

Sometimes the best way to understand a system is to push it until it tells you where the boundary actually is.

I'm especially interested in the gap between:

what a system is designed to do → what it technically can do.

I'm also into gaming, PC hardware, performance comparisons, and generally overthinking how things work.

I enjoy taking quick observations and turning them into hypotheses — then going deeper when something is actually worth investigating.

Currently learning, breaking, rebuilding, and figuring things out.

adb • android • linux • magisk • reverse-engineering • root • optimization • hardware