> For the complete documentation index, see [llms.txt](https://alham-rizvi.gitbook.io/alhamrizvi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alham-rizvi.gitbook.io/alhamrizvi/picoctf-writeups/picoctf/reverse-engineering/droids0.md).

# droids0

First, I opened the APK file using JADX to reverse the code.

In the main activity, I saw that the app has:

* 2 TextViews
* 1 EditText
* 1 Button

When the button is clicked, it shows “Not Today..”. So clearly, the flag is not directly displayed on the screen.

Looking at the code, the button calls a function named `getFlag()` from another class called `FlagstaffHill`.

In the `FlagstaffHill` class, the function always returns “Not Today…”, but there is something interesting. It logs a value using a tag named `PICO`.

This matches the hint: “where else can output go? \[PICO]”

This suggests that the output is being sent to Logcat instead of the app screen.

So instead of interacting with the UI, I checked the logs.

#### Steps

1. Connect to the device:

```bash
adb shell
```

2. View logs:

```bash
logcat
```

3. Click the button multiple times to generate logs.
4. Search for logs with tag `PICO`.

In Logcat, the flag appears in the logs.

#### Final Flag

picoCTF{a.moose.once.bit.my.sister}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://alham-rizvi.gitbook.io/alhamrizvi/picoctf-writeups/picoctf/reverse-engineering/droids0.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.