> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reconnect-tool.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Termux Cookie Login & Save: Roblox Cookie Tools Guide

> Inject .ROBLOSECURITY cookies into Roblox packages or export saved cookies to file using the Reconnect Termux client's root-powered Cookie menu on Android.

The Cookie menu provides two root-powered tools for managing Roblox account cookies directly on your device. You can inject a `.ROBLOSECURITY` cookie into one or all Roblox packages to log in instantly, or export every package's active cookie to a file for backup or bulk use.

<Warning>
  Both items in this menu require root access. If root is not granted, the client shows an error and asks you to grant root and retry.
</Warning>

***

## Menu Items

<CardGroup cols={2}>
  <Card title="Login via Cookie" icon="right-to-bracket" href="/termux/cookie">
    Injects a `.ROBLOSECURITY` cookie into one or all Roblox packages, then relaunches them already logged in.
  </Card>

  <Card title="Save Cookie" icon="floppy-disk" href="/termux/cookie">
    Extracts and verifies cookies from every detected package and exports them to a file in your Downloads folder.
  </Card>
</CardGroup>

***

## Login via Cookie

<Note>
  At least one Roblox package must be installed and detected on your device. If none are found, install and open Roblox first, then retry.
</Note>

<Steps>
  <Step title="Pick a target package">
    Choose a single detected Roblox package to inject into, or select **All Packages (cookies.txt)** for bulk injection across all packages at once.
  </Step>

  <Step title="Provide the cookie(s)">
    <Tabs>
      <Tab title="Single Package">
        Paste your `.ROBLOSECURITY` cookie directly into the prompt. The client validates the cookie format before proceeding — malformed cookies are rejected immediately.
      </Tab>

      <Tab title="All Packages (Bulk)">
        The client reads `/storage/emulated/0/Download/cookies.txt` — place one cookie per line in any of these accepted formats:

        * Raw cookie string
        * `username:cookie`
        * `_|WARNING::cookie`

        After reading the file, you can check off which packages to inject into. All packages are checked by default.
      </Tab>
    </Tabs>
  </Step>

  <Step title="Verify and inject">
    Each cookie is verified against the Roblox API before injection. Invalid cookies are rejected with an error message — only verified cookies are written to their target packages.
  </Step>

  <Step title="Relaunch packages">
    All targeted packages are killed and re-launched already logged in to the injected accounts. In bulk mode, relaunches are staggered by 2 seconds per package to avoid conflicts.

    <Info>
      If **Auto Arrange Windows** is enabled in your settings, the client rearranges app windows after relaunching.
    </Info>
  </Step>
</Steps>

***

## Save Cookie

Save Cookie extracts the active `.ROBLOSECURITY` cookie from every detected Roblox package on your device, verifies each one against the Roblox API to capture the associated username, and writes the results to:

```
/storage/emulated/0/Download/saved_cookies.txt
```

Each line in the output file uses the format:

```
username:cookie
```

<Tip>
  The **Phantom API** rejoin method uses `saved_cookies.txt` as a fallback. If it cannot extract a cookie directly from a package's database, it reads from this file automatically — so keeping it up to date improves Phantom API reliability.
</Tip>