Jio STB Unlock Guide

Research compiled 14 Nov 2026 · every claim labelled by evidence strength

Three steps: pick your box, check its firmware, compare its routes - easiest first. Easiest means least equipment and fewest steps, not safest or best-proven; every card shows its evidence so a convenient but unproven route can't look like the winner.

1 · Which box are we unlocking?

Jio set-top box unit

JMSD200A

AirFiber / JioFiber, Android 11

3 routes documented
No matching modified-device photo verified in this research, so no screenshot is shown

JHSB200

"HYBRID STB JHS B200", JioOS 2.0

no verified route found

2 · Check its firmware (Settings → About)

Open the stock Settings on the box (pen drive → My Music → Settings → Eject USB → Internal Storage → Apps → Settings gear) → About. Note the Version & Build and Security Patch Level.

JHSB200 (your photo, 14 Nov)STB-JHSB200-11.3.46 · patch 2024-06-01 · kernel 4.9.269
JMSD200Abuild still unknown - check yours. 24.1.39 and 25.1.9 both have Nov 2026 success reports

3 · Your routes, easiest first

›

JMSD200A · Route C author claim

Est. easiest · phone only, no PCTermux + free NextDNSnewest (13 Nov)

No computer at all - but single-author, tested on the base JMSD200, not confirmed on your JMSD200A. Read its dependency notes first.

›

JMSD200A · Route B author-tested on JMSD200A

Easy · PC only, no routerone scriptPC hotspot

A same-model repo automates the stack; you do 3 manual steps.

›

JMSD200A · Route A best-proven

Medium · PC + router2 independent same-model reports~1-2 h

The most equipment, and the strongest evidence: two different people report success on this exact model this month.

›

JHSB200 honest answer: nothing verified for your build

The only "supported" listing depends on a leaked certificate key - not recommended, no steps here. The only independent JHSB200 report we found is a failure (older build). What you can do today without unlocking is on the JHSB200 page.

The verdict

What the evidence says, model by model

Jio set-top box

The published Jio set-top-box unlock methods we could find, checked against your two boxes: a JMSD200A and a JHSB200. Coverage is as of 14 Nov 2026 and cannot be literally complete - new reports appear weekly. Each claim is labelled by how strong its evidence is.

Verified on that exact model Reported, not repeated Author claim only Locked / failed No public evidence

Your two boxes

›

JMSD200A 2 independent reports

ADB + sideloading reported working Nov 2026 on firmware 24.1.39 and 25.1.9 by two different people. There is also a dedicated same-model repo and a no-PC phone-only method. Root and bootloader unlock: not confirmed on this model.

›

JHSB200 no verified route found

Your exact box, identified from your About screen (build STB-JHSB200-11.3.46). One guide author lists it as supported, but that route depends on a leaked certificate key, so we don't recommend it. In the sources we searched, the only independent same-model report is a failure, and we found no leak-free unlock published for the JHSB200.

The 6 method families, ranked

›

1 · TR-069 ADB enable best current route

Redirects the box's own management check-in to a local server to switch on debugging. Sideload apps, clean launcher, no boot ads. No flashing. Factory-reset recovery.

›

2 · Root via Jio's own service model-limited

Jio ships a system daemon that runs as root and takes commands over ADB. Full root shell with no exploit on documented units.

›

3 · Bootloader unlock brick risk

CVE-based U-Boot unlock + Magisk. Confirmed only on JMSC200Av2 and JHSD200 v3. One researcher bricked his box.

›

4 · USB flashing / custom ROM old boxes only

Amlogic flash-mode tricks from 2021. Worked on pre-2022 hardware; secure boot kills it on newer boxes.

›

5 · UART / hardware research stage

Soldering-level console access. No completed unlock on current models.

›

6 · No-unlock tweaks safe, limited

Custom DNS ad-blocking, hidden settings, sleep-instead-of-off to skip boot ads. Works today on any box.

What no method gives: free access to paid Jio channels or OTT subscriptions. That lives on Jio's servers and your account, not the box. This guide covers only device control: your own apps, launcher, ads, updates.
Reality check: every unlock here may breach Jio's lease terms. The box is usually Jio's property, taken on deposit. Factory reset is the documented recovery for method 1; deeper methods can permanently brick the hardware.

JMSD200A

Your box · AirFiber/JioFiber Android 11 unit · evidence as of 14 Nov 2026

The sideload/ADB method has two independent first-hand success reports on this exact model this month, plus one second-hand forum report and a dedicated same-model repo. Deeper mods (root, bootloader) are unconfirmed here.

Evidence log

WhenWhoResult
28 Oct 2026TechEnclave user, quoting a friendsecond-hand
stage1 completed on JMSD200A V2, apps installable
2 Nov 2026MrBlack16 (GitHub)first-hand
works on firmware 24.1.39, "no change required in script", used the standard JMSC/JMSB option
8 Nov 2026RajendranDinesh (GitHub)first-hand
works on firmware 25.1.9 (Android 11, 32-bit)
7 Nov 20264sudosu (repo author)author claim
dedicated JMSD200A repo; tested on Android 11, security patch 2024-06-05; PC-hotspot variant verified
13 Nov 2026MuthamizhanR (repo author)author claim
no-PC method (Android phone + Termux) for JMSD200/JMSD200A, including recovery from "Set-Top Box Blocked" screen
Honest limits: none of these are our own test of your unit. The two first-hand reports are the strongest signal. One earlier teardown (21 Oct) of a JMSD200A V2 found every simple software route closed — the TR-069 method below is the one that later reports say works.

What you get after the unlock

Network ADB (debugging)On, valid to 2037
Install any Android TV appVia PC or on-box stores
Clean launcher (Monet etc.)Replaces ad home screen
Boot adsDisabled
Auto firmware updatesDisabled (see tradeoff)
Jio services (JioTV+ etc.)Keep working
Root / custom ROMNot included
Jio STB running sideloaded apps
A Jio STB running sideloaded apps (XDA, 2021 guide)
Sorted by estimated ease (least equipment first), as requested - these are estimates, not measured. Easiest is not the best-proven: Route A has the strongest evidence (two independent same-model reports), Route C the least (one author, base model). All three are the same underlying TR-069 method with different equipment.

Route C — no PC at all (phone + Termux) est. easiest · author claim

Difficulty: Easy-Medium, estimated - real effort depends on your hotspot, Wi-Fi, NextDNS and Termux setupEquipment: Android phone/tablet onlyEvidence: author claim, tested on the base JMSD200 - not your exact JMSD200ARecovery: factory reset + documented blocked-screen fix

Model caveat first: this route was tested by its author on the base JMSD200, not on the JMSD200A - treat it as unverified for your exact box until someone confirms it. Published 13 Nov 2026. Replaces the PC/Docker stack with a 90-line Python server in Termux on an unrooted Android phone/tablet, plus a free NextDNS profile that rewrites Jio's management hostname to the phone's hotspot IP. Also documents recovery from the "Set-Top Box Blocked" screen. Two technical findings worth knowing: this model's management flags use the Device.JioSTB. prefix (not Device.JSTB.), and the debugging flag must be sent alone in its own session or the box rejects the batch.

Read before using - provenance and dependencies:
· Provenance: the author tested it on a JMSD200 (the base model, per the repo's own story) and extends the claim to JMSD200A. Repo created 13 Nov 2026, single author, zero third-party confirmations so far.
· Third-party DNS: it routes the box's Jio lookups through a NextDNS account you create, rewritten to your phone. That is an outside service in the middle; you can delete the rewrites afterwards, and the guide says to.
· No leaked keys: unlike the JHS route, this uses no stolen certificate key.
· Downloaded software: its post-unlock script fetches and installs third-party apps (Shevery/Shizuku, Glassio launcher, SmartTube) and disables Jio's update + management client. Review the script before running; disabling updates means missing security patches.
· Risk the author hit himself: his box was blocked mid-process ("Set-Top Box Blocked" screen) during development. He recovered it, but expect friction, not a smooth ride.

jiostb-zero-pc-unlock 0★, single author

Route B — PC hotspot, no router easy · author-tested on JMSD200A

Difficulty: Easy-Medium, estimatedEquipment: Windows PC onlyEvidence: author-tested on JMSD200A, no independent confirmationsRecovery: factory reset

A same-model repo automates the whole thing with one script; the PC's own mobile hotspot replaces the router. You do 3 manual things: turn the PC hotspot on, connect the STB to it, reboot the STB.

Install prerequisites: Docker Desktop, Python 3, Git, ADB platform-tools on PATH.
Clone the repo and run its unlock script. It raises the local server stack, spoofs DNS on the hotspot subnet, queues the payload and watches for the box.
Turn the PC's Mobile Hotspot on (phone hotspot off, so the box doesn't escape to the internet).
Connect the STB to the PC hotspot via its hidden settings (USB-trick path above), DHCP automatic.
Reboot the STB and accept the debugging prompt on the TV when it appears.
Optional: run its restore/setup script to install the bundled app set (launcher, stores, players).

JioSTB-JMSD200A-Unlock 1★, author-tested only

Route A — PC + your router best-proven · matches both Nov reports

Difficulty: Medium, estimatedEquipment: PC + router + pen driveEvidence: 2 independent same-model reports (Nov 2026)Recovery: factory reset, documented

Needs: Windows PC, Docker Desktop, Python 3, Git, a USB pen drive (any, empty), and your phone's hotspot or tethering if you want internet on the PC mid-setup.

Install the tools. Docker Desktop (restart after), Python 3 (tick "Add to PATH"), Git for Windows, Technitium DNS.
Run the one-time prep script from the guide repo as Administrator while the PC is online. It pulls the Docker images, adds the local DNS record for Jio's management hostname and opens the needed firewall ports.
Stock settings on the box
The stock settings screen you reach through the USB-pen-drive trick (TeleOS screen, digit.in)
Point the box's DNS at your PC. Plug the pen drive into the STB → My Music → Settings → Eject USB → Internal Storage → Apps → stock Settings (gear) → Network → your active Wi-Fi → switch DHCP to Static, keep all values, set DNS 1 to your PC's IP.
Isolate the network. Unplug the incoming fiber/WAN cable from the router (router stays on). Temporarily turn off Windows Defender Firewall.
Start the local services: Docker Desktop, the Technitium zone, the TLS containers, and the proxy listener — for JMSD200A use the JMSC/JMSB option (option 1), per MrBlack16's same-model note.
Queue the payload with the stage-1 script and pick your box from the device list.
Cold power-cycle the box: unplug its power adapter from the wall, wait 5 seconds, plug back in. The box only contacts the management server during boot.
Accept "Allow USB debugging" on the TV (tick "Always allow"). Verify on the PC: adb devices should show the box as device.
Restore everything: reconnect the WAN cable, turn the firewall back on, stop the containers and listener.
Monet launcher
The Monet launcher running after a successful unlock (IBF user ackr8, 2021 - same method family, older box)
Recovery: a factory reset (pinhole button while powering on) is documented by the guides as restoring stock behaviour. No flashing is involved, and no brick reports exist for this stage in any tracker we read — that is reassuring, not a guarantee.
Update tradeoff: the setup disables Jio's auto-updates so the unlock isn't overwritten. That also stops security patches. You can re-enable updates later (and likely lose the unlock).

sideload-jiostb — main guide 381★ Issue #6 — the two JMSD200A success reports Jio-Datsugoku — beginner version of the same method 22★

Deeper mods on JMSD200A — status

Root shell via Jio SDK daemonplausible, unverified
Bootloader unlock (CVE-2024-31317)untested here
Custom ROMsecure boot on
UART consoleread-only log only

The documented root shell targets a unit called "JioSTB C200A (ohm)" on the same chip family; a third-party teardown labels the JMSD200A V2 with the same "ohm" codename. Nobody has published the root shell working on a JMSD200A, so treat it as a lead, not a feature. The bootloader-unlock CVE is tied to the box's security-patch date and is documented only for JMSC200Av2.

JHSB200

Your second box · JioOS 2.0 · build STB-JHSB200-11.3.46 · security patch 2024-06-01 · kernel 4.9.269 (from your About screen)

Verdict for this exact box: we have not verified a recommendable route for this exact build. The one guide that lists the JHSB200 as supported gets there through a leaked certificate-signing key, which we will not walk you through. In the sources we searched, the only independent report from a JHSB200 owner is a failure - on an older build than yours. Details and sources below.

Evidence log - JHSB200 specifically

WhenWhoResult
22★ guideRookieEnough (Jio-Datsugoku)author claim
compatibility table lists "JHSB200 - Verified - all builds". But the JHS route in that guide mints a forged eMudhra certificate chain (its own file names say so), so the claim doesn't translate into a route we can recommend.
9 Nov 2026tekimanish09 (GitHub issue #24)question
JHSB200 owner ("HYBRID STB JHS B200", build STB-JHSB200-11.0.20, patch 2023-12-05) asked whether the JHSC200 method works on this model.
13 Nov 2026PROBOTFREE (same issue)failed
"No i tried and didn't work may be it is just for jhsb200a" - hints a JHSB200A variant exists; yours is JHSB200.
13 Nov 2026tekimanish09 (same issue)failed
"I tried many exploits and same no leads whatsoever."
About your exact build: your box runs build STB-JHSB200-11.3.46 (patch 2024-06-01). The failure reports above are on the older 11.0.20 build, and we found no public test of 11.3.46 on a JHSB200 - so your build is simply untested in public, not proven locked. Note the JHSC200 v1 was verified on a same-numbered build (stb-jhcs200-11.3.46), but that is a different model and proves nothing for yours.

Other JHS boxes, for context

Suffix by suffix

ModelStatusEvidence
JHSC200 v1sideload verified*jadedFella repo: verified end-to-end on build stb-jhcs200-11.3.46
JHSC200 v2guide-listedJio-Datsugoku table lists v1 & v2 verified, build 11.3.46+
JHSD200 v3root confirmedMassacre80 root toolkit: end-to-end test 2 Nov 2026, build 11.3.46, Magisk + bootloader unlock
JHSC200 v5lockedXDA thread: no ADB, signed-only recovery, USB Burning Tool can't detect it
JHSB300, JHSD202unknownno public reports either way
The asterisk on JHS sideloading: JHS boxes validate TLS certificates properly, so the published JHS sideload method mints a fake certificate chain using a leaked eMudhra CA signing key (the repos call it "forged_chain.pem" themselves). The method itself, its evidence and its risks stay documented here - but: Censored: leaked private key and instructions for its use. The JMS-family method (your JMSD200A) does not need it. We found no leak-free JHS sideload alternative in the sources we searched (14 Nov 2026).

Not your box: JHSD200 v3 — the one fully-rootable JHS

Massacre80/jio-stb-root-tools verified 2 Nov 2026

Root, bootloader unlock, backup/restore and Magisk tooling confirmed end-to-end on exactly the JHSD200 v3 ("franklin"), JioOS 2.0 / Android 11, build 11.3.46. It works through the box's own TR-069 native command channel after ADB is enabled, then patches the boot image with Magisk.

Verified build11.3.46 / 20260917
ChipAmlogic S905X2-class
Writes toenv + boot partitions
USB burn-mode recoveryDisabled (eFuse password lock)
Read this before touching it: the author's own warnings: bricking is possible; fastboot is not a reliable recovery route on these boxes; Amlogic USB Download mode is disabled, so there is no guaranteed unbrick path. One wrong flash and the box may be permanent e-waste. A factory reset does not undo boot-partition changes.

jio-stb-root-tools TWRP device tree for JHSD200 (franklin)

Not your box: JHSC200 v5 — current picture

Everything checked is closed: developer options and USB debugging hidden, package installer disabled ("No apps found to open this file"), USB stick detected but not mountable for apps, recovery stripped to reboot + factory reset, fastboot stripped, USB Burning Tool doesn't detect the board, eMMC-short tricks unsolved. One XDA member reached "worldcup mode" on a jhs200v3 but flashing failed at the USB status stage.

XDA: Jio jhsc200 v5 unable to flash ROM

Official recovery reference

Jio's own factory-reset instructions explicitly cover the JHSB200 (alongside JHSC200/JHSD200) - useful if anything ever goes wrong.

Jio official: factory reset, JHSD200 / JHSC200 / JHSB200 (PDF)

Image honesty: no verified photos of a JHSB200 unlock exist (there is no verified unlock). We deliberately do not show other models' unlocked screens as if they were your box.

What works on any JHS box today (no unlock)

Skip boot ads without any mod: use sleep mode from the remote instead of powering off — the box returns straight to the home screen (r/Jio workaround, Jul 2026).
Block most in-app ads: set a filtering DNS (NextDNS/AdGuard) in the hidden network settings via the USB-trick path, or at router level for every device.
Open hidden settings: pen drive → My Music → Settings → Eject USB → Internal Storage → Apps → Settings gear. On the newest TeleOS builds the developer-options menu opens but Jio has removed the ADB toggles from it.

All 6 methods

What each one actually is, enables and risks

Easiest first Strongest evidence Original order
Method 1 · TR-069 / ACS spoof

Fake management server → ADB current best

How: the box asks Jio's TR-069 server at boot whether debugging is allowed. A local server (GenieACS + TLS proxy + DNS rewrite on your own network) answers instead and flips the flags: USB debugging on, updates off.

Enables: sideloading, third-party launcher, boot-ad removal, debloat, on-box app stores. Not: root, bootloader, ROM.

Risk: no flashing; guides document factory-reset recovery. Models: JMSC200Av2, JMSB200A, JMSK200A (verified); JMSD200A (2 independent reports); JHSC200 v1 (verified but via leaked-key certs — not recommended); JHSB200 (reported failing, issue #24); base JMSC200A + JMSB200A v1 on firmware 25.1.9 (reported failing — hardcoded server).

Difficulty: MediumEquipment: PC + router (or phone-only variant)Recovery: factory reset, documented

sideload-jiostb 381★ Housekeeping-PoC (origin research) 271★ STB-Comprehensive-Guide (direct-Ethernet variant) 70★ Technical writeup, 4 Nov 2026

Method 2 · sdknativeservice root shell

Jio's own daemon gives root post-ADB

How: Jio's SDK native service runs as uid 0 (root), accepts binder calls from the ADB shell with no caller check, and passes a parameter straight to a shell. No CVE, no exploit — documented on a "JioSTB C200A" S905X4 unit, Nov 2026.

Enables: any root command, boot-image extraction for Magisk. Requires: method 1 first. Model coverage: not established beyond the documented unit; same-codename lead for JMSD200A is unverified.

Difficulty: Easy once ADB is onEquipment: same PC/phoneRecovery: reset restores

Housekeeping-SDK.md — full security analysis

Method 3 · Bootloader unlock + Magisk

CVE-2024-31317 → U-Boot unlock can brick

How: an Android zygote injection (fixed in Google's June 2024 bulletin) escalates to write the U-Boot environment: unlock flag + SELinux permissive. Then Magisk via a patched boot image.

Limits (from the authors): one attempt per boot; patch date decides eligibility; U-Boot fastboot is heavily restricted; the lead author bricked his own box. Confirmed: JMSC200Av2 (Housekeeping-PoC) and JHSD200 v3 (Massacre80 toolkit, via a different tr069native path). Nothing else.

Difficulty: ExpertEquipment: PCRecovery: none guaranteed - author bricked his box

Housekeeping-PoC jio-stb-root-tools (JHSD200 v3) CVE-2024-31317 reference

Method 4 · Amlogic USB flashing / custom ROM

2021-era flash-mode trick old hardware only

How: exploit the Amlogic chip's USB flashing protocol to write a ported Mi Box Android TV system image. Worked on: 2021 C200/D200 (XDA), and pre-2022 JHSD200 v2 / JHSC200 v1 per a TechEnclave flash guide.

Today: newer boxes ship secure boot, stripped fastboot, signed-only recovery and eFuse password locks ("Need Password: 1" on S905X2). A JHSD200 got LineageOS 20 flashed and hung at the boot logo — signed-vbmeta problem, box effectively bricked. Custom-ROM attempts also risk permanent Widevine L1 → L3 loss (480p streaming cap).

Difficulty: ExpertEquipment: USB tools + PCRecovery: none - closed on current boxes

XDA, Sep 2021 TechEnclave: generic Android TV on pre-2022 boxes TechEnclave p2: LineageOS attempt + eFuse lock

Method 5 · UART / hardware

Console pins + USB-UART adapter research stage

How: open the case, find TX/RX/GND pads, attach a CH340 adapter, interrupt boot for a U-Boot console. Reached on JMC20211 (Jun 2025) — a custom image was flashed but never booted ("transaction failed" binder errors). On JMSD200A the exposed UART only prints a co-processor log and accepts no input. eMMC pin-shorting to force flash mode: timing unsolved.

Jio STB motherboard
Jio AirFiber STB (JMSC200A2_J) board — community teardown
Difficulty: ExpertEquipment: soldering + USB-UARTRecovery: n/a - research stage

XDA: JIO STB ROM Change (JMC20211) Full hardware teardown gallery

Method 6 · No-unlock tweaks

Hidden settings & DNS documented on several models

Includes: hidden stock settings via the USB trick; custom DNS (NextDNS/AdGuard) for ad-blocking; hotspot mode; sleep-instead-of-shutdown to skip boot ads; router-level DNS for the whole home. On the newest TeleOS builds the developer menu opens but ADB toggles are removed from it.

Difficulty: EasyEquipment: pen drive onlyRecovery: settings-level changes; full reversibility not verified on every firmware

India Broadband Forum: hidden options guide r/Jio: startup-ads workarounds

TeleOS sideload note: on Jio TeleOS televisions (e.g. Thomson Jio TV), ADB can be switched on from a hidden factory menu and apps sideload directly — digit.in's guide claims the same steps work on the JioFiber STB, but no STB confirmation exists; treat as TV-verified only.

Model matrix

Every Jio STB model with public modding evidence

V = verified working · R = reported (not repeated) · C = author/repo claim · X = failed/locked · ? = no evidence

ModelADB sideloadRootBL unlockCustom ROM
JMSC200Av2VVV?
JMSB200AV?C?
JMSD200A yoursR×2lead?X
JMSK200AV???
JMSC200A (base)25.1.9 fails???
JMSC200A2_J????
JHSC200 v1V*CXpre-22
JHSC200 v2C*???
JHSC200 v5XXXX
JHSB200F*???
JHSB300????
JHSD200 v1oldoldoldpre-22
JHSD200 v2old??pre-22
JHSD200 v3V*VVboot fail
JMC20211??UARTboot fail
C200 / D200 (2021)V?oldV (MiBox port)

* published JHS sideload route depends on a leaked CA certificate key — not recommended, no steps provided. "F*" = one same-model failure report (build 11.0.20, Nov 13) plus one guide-author support claim that relies on the leaked-key route. "old/pre-22" = 2021-2023 era methods on early hardware, mostly closed by secure boot now. "boot fail" = a custom image was flashed but never booted successfully.

Revision matters as much as model: firmware 25.1.9 broke the DNS-spoof method on the base JMSC200A and JMSB200A v1 (the box ignores the spoofed DNS entirely), while JMSC200Av2 and JMSD200A on the same firmware still have success reports. Check both the exact label and the build number in Settings → About.

Sources

Everything this guide is built from · checked 14 Nov 2026

GitHub, by stars

XDA

Forums

Videos

How to sideload apps and APK bundles on Jio Tele OS TVs Mar 2025 · Jio TVs, not STBs - method overlaps the hidden-settings path Install Mi-Box firmware in Jio Fiber STB 2022 · the old flash method - closed on current boxes, shown for context Jio 4K Set Top Box Unlock (Shorts) short-form · unverified claims, treat as a lead only Install GenieACS (TR-069 server) 2023 · background tooling for Route A, not Jio-specific

Checked 14 Nov 2026: we found no quality video walkthrough of the current TR-069 method for these exact models. Most "Jio STB unlock" videos are the dead 2021-22 flash trick or unrelated hardware (e.g. Indonesian B860H boxes). The written guides below are more current and more honest.

Reddit

Articles & people

abhishek.log: Reclaiming the Jio STB 4 Nov 2026 technical writeup digit.in: sideload on Jio Tele OS Mar 2025, TV-verified AirFiber STB teardown site high-res board photos CVE-2024-31317 reference patched June 2024

Named researchers: Bihaan Sen, ak_0o7, Otus9051 (original PoC); Vishal Beniwal (u/ilikechocopies, Windows guide); Pavit Chhabra (@mesosan16 on X, JHS certificate research); Sandip Bhardwaj (ACS tooling); RealEngineer + aidanmacgregor (2021 XDA method).

Image credits

Box + sideload photos: XDA (2021). Hero illustration: abhishek.log. Board photos: nav9v/jio-airfiber-stb-teardown. Launcher screenshot: India Broadband Forum user ackr8 (2021). TeleOS screens: digit.in. All used for research documentation with source links.

Methodology: compiled 14 Nov 2026 from the sources above. Evidence labels: Verified = tested on that exact model and revision, by the author or two-plus independent reporters. Reported = first-hand but single/unconfirmed. Claim = repo table or author statement only. Nothing here was tested on your physical units. Corrections belong upstream in the linked repos and threads.