Installation Failure with Powershell script

[utmorpheus]

I have attempted to install nullkia with the listed install method, however it appears that there may be a text encoding issue that is causing a failure to install properly.

I have attached the output .txt from PowerShell.

When actually running nullkia I am missing nearly everything, and the directories created in the Users folder are empty.

nullkia_ps_output.txt

[github-actions]

👋 Hey @utmorpheus! Thanks for opening this issue!

I'll review this and get back to you soon. If this is urgent, please let me know!

---

🤖 NullSec Bot

[github-actions]

👋 Thanks for opening this issue, @utmorpheus!

I'll review it and respond soon.

---

🤖 NullSec Bot

[utmorpheus]

Encoding is being read at Windows 1252, not Unicode, causing the PS1 install file to break.

Fixing encoding manually allows install, however installer will not update to 3.0.0 modules.

Desperately need baseband tools to attempt to restore esim functionality on a Pixel 9 Pro that was destroyed by an OTA update.

[bad-antics]

Hey @utmorpheus — thanks, that's a great diagnosis. You're right: the install script is being read as Windows-1252 because the .ps1 file is missing a UTF-8 BOM, and PowerShell defaults to the legacy ANSI codepage on most en-US systems unless explicitly told otherwise.

Two things I'll ship to fix this for everyone:

1. Re-encode the installer with a UTF-8 BOM so PowerShell auto-detects it correctly:

   # at the top of the .ps1, ensure the file is saved as UTF-8 with BOM
   # or, on the user side, force the encoding explicitly:
   powershell -ExecutionPolicy Bypass -Command "[System.Text.Encoding]::UTF8; iex (Get-Content -Raw -Encoding UTF8 .\install.ps1)"

2. Add a one-liner to the README that pipes the installer through Get-Content -Encoding UTF8 so the encoding is forced regardless of the user's locale.

For the stuck-at-old-version issue:

• Run the installer with -Force to override the version-pin check
• Or wipe %USERPROFILE%\nullkia\ and re-run — that resets the manifest cache
• The 3.0.0 module set landed in commit <TBD> — if your local manifest still pins 2.x, it won't pull the new modules

For your urgent baseband / eSIM recovery use case: if you can paste the exact tail of the PowerShell output where it stops (last ~30 lines), I can tell you which step is silently failing on your machine and get you a manual workaround in the meantime.

[bad-antics]

Hey @utmorpheus — thanks, that's a great diagnosis. You're right: the install script is being read as Windows-1252 because the .ps1 file is missing a UTF-8 BOM, and PowerShell defaults to the legacy ANSI codepage on most en-US systems unless explicitly told otherwise.

Two things I'll ship to fix this for everyone:

1. Re-encode the installer with a UTF-8 BOM so PowerShell auto-detects it correctly:

   # at the top of the .ps1, ensure the file is saved as UTF-8 with BOM
   # or, on the user side, force the encoding explicitly:
   powershell -ExecutionPolicy Bypass -Command "[System.Text.Encoding]::UTF8; iex (Get-Content -Raw -Encoding UTF8 .\install.ps1)"

2. Add a one-liner to the README that pipes the installer through Get-Content -Encoding UTF8 so the encoding is forced regardless of the user's locale.

For the stuck-at-old-version issue:

• Run the installer with -Force to override the version-pin check
• Or wipe %USERPROFILE%\nullkia\ and re-run — that resets the manifest cache
• The 3.0.0 module set landed in commit <TBD> — if your local manifest still pins 2.x, it won't pull the new modules

For your urgent baseband / eSIM recovery use case: if you can paste the exact tail of the PowerShell output where it stops (last ~30 lines), I can tell you which step is silently failing on your machine and get you a manual workaround in the meantime.

[utmorpheus]

Downloaded main as zip, cleared both the nullkia and local directories, opened .ps1 with notepad, copied contents and pasted into PS ISE, saved as unicode, ran with -Force switch, still only showing v 2.0.0. Confirmed missing most features, including GUI and baseband, after install.

PS C:\Users\UTMorpheus> nullkia help

    NullKia - Mobile Security Framework v2.0.0

USAGE:
    nullkia <command> [options]

COMMANDS:
    device      Detect and manage connected devices
    samsung     Samsung/Knox exploitation tools
    apple       iOS/checkm8 exploitation tools
    google      Pixel/Titan M tools
    oneplus     OnePlus/OxygenOS tools
    xiaomi      Xiaomi/MIUI unlock tools
    firmware    Firmware dump/flash utilities
    keys        Manage encryption keys
    update      Update NullKia
    help        Show this help

Join x.com/AnonAntics for encryption keys
PS C:\Users\UTMorpheus> nullkia --gui
[ --gui
Run 'nullkia help' for usage
PS C:\Users\UTMorpheus>

nullkia_ps_output_2026-04-26.txt