Does Luarmor work on mobile?
The licence check runs wherever the loader can run. What Android and iOS clients need, and why a phone reports a different HWID.
Yes, if the executor on your phone can run the loader. Luarmor is a licence
service, not an app: the loader is the same kind of Lua file on Android, iOS or a
desktop, and the check depends on what your client can do with HTTP, files and
loadstring. Where the client cannot do those things, the check never
starts.
What the loader needs from the client
The loader begins with game:HttpGet and loadstring, then
calls readfile, writefile and makefolder
further down. None of those functions belong to a normal Roblox client. They exist
because the executor added them, and a client that lacks one of them fails at that
line.
| Call in the loader | What it does | What happens on a client without it |
|---|---|---|
game:HttpGet |
Fetches the loader, then the second stage | The first line errors before any licence check |
loadstring |
Compiles the text into a function | Nothing runs, whatever the key says |
readfile |
Reads the cached init file |
The cache branch is skipped inside a pcall, so the loader goes
to the network
|
writefile |
Stores the second stage on disk | The download succeeds, then the branch stops before the script runs |
makefolder |
Creates static_content_170926 |
The error is swallowed by pcall, and a later write can fail
|
The table describes the 1,245-byte loader we downloaded on 19 Oct 2026. No
documentation lists those calls as requirements. Another seller runs another
loader, but the shape holds: a small file that needs network,
loadstring and file access before it needs your key. The full chain
is in
the loader anatomy.
Android
Clients that inject Lua on Android exist, and some of them expose those functions.
Whether Luarmor accepts one is a separate question. The
cdn.luarmor.net endpoint answers according to the client that asks, and
our unauthenticated request received a 327-byte placeholder that kicks the player
with Your executor is not supported by Luarmor.
That message arrives before the key is read. If you see it on a phone, the client was not recognised, so check the client before you retype the key. The second stage we read is the rejection branch, so it says nothing about what a recognised client receives. The rejection itself is described in what the second stage does.
iOS
iOS has less tooling than Android, and the rule does not change. If the client can fetch, compile and write, the loader reaches the licence check. If it cannot, the first line fails and you never see a Luarmor code.
Luarmor's documentation does not publish a list of supported clients for either platform. A compatibility table would be a snapshot, so the answer comes from the response.
The key page on a phone
The key page is a website the seller configures, and a phone browser can open it. That part of the flow works the same on a phone: you copy the key, then paste it where the seller tells you.
The friction sits in the steps around it. Threads in r/robloxhackers describe key pages with checkpoints, ad links and captchas, and one user showed a key panel that would not scroll on a phone. You visit the flow in a browser; there is no program to install for the key itself.
What the HWID does on a phone
A key is bound to a hardware identifier. A phone reports a different one from a
desktop, so a key that works on your PC returns KEY_HWID_LOCKED on your
phone even when the key is valid and the client is recognised.
The fix is a reset by the seller, normally through /resethwid on the
seller's Discord bot. The documentation does not list which hardware values feed
the fingerprint, so do not expect to compute it yourself. Moving a key to a phone is
the same operation as moving it to a PC, covered in
the HWID reset page.
The check order on a phone
The order of the check is the same on every platform: the client is recognised, then the key is read, then the HWID is compared, then the expiry and the ban list.
The cache works the same way. The loader writes the second stage to
static_content_170926/init-<short-id>-ocmid.lua inside the
executor workspace and reuses it only if the text is longer than 2,000 characters.
purge_cache() is the documented way to clear the cached build. On a
phone, the folder lives wherever your client keeps its workspace, and the same size
rule applies.
Trying it in five steps
- Get the key from the seller's page in your phone browser. Complete the flow the seller set, then copy the key.
-
Open the executor and check that it exposes
HttpGet,loadstring,readfileandwritefile. Most clients list their API or print it in a console. - Paste the loader as one line. Do not split the URL or add line breaks.
-
Run it once and read what comes back. A kick message points to the client. A
KEY_code points to the key. -
Act on the code: reset for
KEY_HWID_LOCKED, renew forKEY_EXPIRED, recheck the copy forKEY_INCORRECT.
If step 2 fails, stop. A second key will not add the missing function, and a reset will not either.
Where the licence stops
Luarmor decides who may run a script. It neither hides the client from Roblox nor checks what the script does once the licence passes. The licence layer sits above the executor, and the executor is what touches the game, on a phone as on a desktop.
That matters when a loader fails and someone offers a fix built on a different client. Swapping the layer below the licence changes which code runs, not whether you are authorised. For where the licence layer ends, see Is Luarmor safe.
FAQ
Does Luarmor have a mobile app?
No. The documentation describes a web service with projects, keys and a loader file, and it does not describe an app for Android or iOS. What you install on a phone is the executor, which is a separate program. Luarmor is reached over HTTPS by the loader and by the key page in a browser.
Can I get a Luarmor key on my phone?
Yes, in the browser. The key page belongs to the seller and is a normal website. The steps around it depend on how the seller configured the flow, and nothing in the documentation requires a desktop. If a step opens an app store instead of a page, that is the ad link, not the licence check.
Why did I get kicked with "executor not supported" on Android?
The second stage served to your client was the rejection branch. That happens before the key is read, so neither the key nor the HWID is involved. Either the client is not recognised, or the request arrived without the fingerprint the service expects. A new key does not change the answer.
Can I use one key on my PC and my phone?
Only if the seller allows it, and the usual case is one device per key. The key is tied to a hardware identifier, and a phone reports a different one from a desktop. Moving it means a reset by the seller, the same operation used when you change computers.
Which mobile clients work with Luarmor?
The documentation does not publish a list per platform, and any list we wrote would go stale. The endpoint decides per request: a recognised client receives an init, and an unrecognised one receives the kick message. That is why threads asking for a compatible client get different answers over time.
Does reinstalling the app change my HWID?
It can. A reinstall, an operating system update or a reset of the device can change the values the client uses to build its fingerprint. When that happens the key reports KEY_HWID_LOCKED and the seller resets it. The documentation does not list the inputs, so the result is observed rather than predicted.
Does Luarmor work on a Chromebook?
If the Chromebook runs the client in an Android container or a Linux environment, the question is the same as on any other machine: can the client fetch, compile and write? Luarmor does not target Chromebooks as a category. A key that works there is a key the seller has reset onto that machine.
Is a mobile key cheaper?
The seller sets the price and the flow. Luarmor sells access to sellers through invite codes, and the documentation does not publish a price for keys. If a key costs nothing on a phone, it costs nothing because the seller chose an ad flow or a free tier. The device does not set the price.