How I Started Learning Cybersecurity With Just an Android Phone

This is a submission for the 2026 WeCoded Challenge: Echoes of Experience

When I first got interested in cybersecurity, I didn’t have a laptop.

I didn’t have a powerful computer, multiple screens, or any kind of advanced setup.

All I had was an Android phone, limited data, and curiosity.

At the time, that felt like a problem.

Most of the tutorials I found online were built for people with laptops. They would say things like “open your terminal” or “run this on Kali Linux,” and I would just sit there thinking… how?

It felt like I was locked out before I even started.

But something about cybersecurity kept pulling me back. I didn’t fully understand it yet, but I knew I wanted to learn.

So instead of waiting until I had better tools, I decided to start with what I had.

The Moment Everything Changed

One day, while searching for ways to learn hacking on a phone, I came across something called Termux.

At first, it looked confusing.

It wasn’t like a normal app. There were no buttons, no menus, just a black screen and a blinking cursor.

I remember thinking, “What am I even supposed to do here?”

But I followed a tutorial anyway.

I copied commands line by line, not really understanding what they meant. Sometimes it worked, sometimes it didn’t. When it failed, I had no idea why.

Still, that moment was important.

For the first time, I wasn’t just using a phone. I was interacting with a system.

Learning Without a Clear Path

The early days were not easy.

There was no structured plan. No step-by-step roadmap. Just random tutorials, trial and error, and a lot of confusion.

I had to figure things out slowly:

• What basic Linux commands do
• Why installations fail
• How package managers work
• What different tools are actually used for

Sometimes a simple error would take hours to fix. Other times, I would follow a tutorial perfectly, and it still wouldn’t work on my device.

That was frustrating.

There were days when I felt like giving up, especially when progress felt too slow.

But then something small would happen.

A command would finally run successfully. A tool would install without errors. A scan would actually return results.

Those small wins mattered more than they seemed.

They gave me a reason to keep going.

The Hidden Challenge No One Talks About

The technical part was hard, but it wasn’t the hardest thing.

The hardest part was feeling like I didn’t belong.

When I looked at people in the tech space, they all seemed ahead. They had better setups, more experience, and a clear understanding of what they were doing.

Meanwhile, I was trying to learn cybersecurity on a phone.

It made me question myself.

• Was I wasting time?
• Was this even a real way to learn?
• Was I doing things the wrong way?

But over time, something started to change.

I realized that everyone starts somewhere.

Some people start with laptops. Some start with courses. Some start with mentors.

I started with a phone.

And that was okay.

Turning Confusion Into Understanding

As I kept going, things slowly started to make sense.

Commands were no longer random text. I began to understand what they actually do.

Errors stopped being scary. They became part of the learning process.

Instead of just copying tutorials, I started experimenting.

I would try different commands, break things, fix them, and learn from that process.

That’s when I noticed real progress.

Not because I had better tools, but because I started thinking differently.

From Learning to Sharing

At some point, I realized something important.

If I was struggling to understand these things, there were probably many others in the same situation.

Especially people using phones, or people who are completely new to tech.

So I started writing.

Not as an expert, but as someone who remembers what it feels like to be stuck.

I focused on explaining things in a simple way:

• No complicated language
• No assumptions about prior knowledge
• Just clear steps and honest explanations

I wrote the kind of content I wish I had when I started.

Slowly, people began to find it.

Some were beginners like me. Some were also using Termux. Others just wanted simple explanations without all the noise.

That’s when I realized something powerful.

You don’t need to know everything to help someone.

You just need to be a few steps ahead and willing to share.

What Starting With a Phone Taught Me

Looking back now, starting with just an Android phone didn’t hold me back.

It actually helped me build a strong foundation.

1. It taught me patience. When things are slow and limited, you learn to take your time.
2. It taught me problem-solving. Without a proper setup, you’re forced to think differently and find alternative solutions.
3. It taught me how systems work. Because nothing is automated, you see what happens behind the scenes.
4. It taught me consistency. I didn’t learn everything at once. I just kept showing up, even when things didn’t make sense.

A Message to Anyone Who Feels Stuck

If you’re starting out and feel like you don’t have the right tools, you’re not alone.

It’s easy to think you need a perfect setup before you begin.

But that’s not true.

Start with what you have.

• Even if it’s just a phone.
• Even if things feel slow.
• Even if you don’t understand everything yet.

What matters is that you start.

Progress in tech doesn’t come from having the best device.

It comes from staying consistent, learning step by step, and not giving up when things get difficult.

Conclusion

Everyone’s journey in tech is different.

Some start with everything they need. Others start with almost nothing.

This is my journey.

It wasn’t perfect. It wasn’t fast. But it was real.

And it all started with a simple Android phone, a blank terminal screen, and a decision to keep going.