(shadow)banned on socials, games or banking apps???
your device might be failing integrity checks
i built ukeystore, a native attestation component compiled directly into the ROM
no Magisk
no additional runtime injection module
Rust and C++ changes inside keystore2, handling attestation certificate chains with a configured profile and a separately provisioned keybox
the difference vs TrickyStore is where the implementation lives
the code is built into the system service, so there is no extra module to install or inject at boot and none of the module-specific artifacts that come with that layer
on my custom Samsung ROM with an unlocked bootloader, i saw BASIC, DEVICE and STRONG in Play Integrity diagnostics
pretty wild seeing all three on that setup
the source is now public
no keybox included
you're solely responsible for how you use it
drop a star github.com/antiyro/ukeystore…
here’s the explain it like im 5 version of ukeystore
a stock android phone usually gives apps a green light 🟢
but some advanced automation setups involve changing parts of android
those changes can trigger an orange light 🟠 basically telling apps this phone might have been modified
some apps then refuse access to certain features or bans
one approach is to use tools like magisk and trickystore to try to get that green light back 🟢
but apps can also look for signs that those tools are installed
with ukeystore the attestation changes are compiled directly into the android rom
no magisk dependency
no extra module to inject at boot
with the right configuration and keys a modified phone can get a green light again 🟢!
drop a star github.com/antiyro/ukeystore
(shadow)banned on socials, games or banking apps???
your device might be failing integrity checks
i built ukeystore, a native attestation component compiled directly into the ROM
no Magisk
no additional runtime injection module
Rust and C++ changes inside keystore2, handling attestation certificate chains with a configured profile and a separately provisioned keybox
the difference vs TrickyStore is where the implementation lives
the code is built into the system service, so there is no extra module to install or inject at boot and none of the module-specific artifacts that come with that layer
on my custom Samsung ROM with an unlocked bootloader, i saw BASIC, DEVICE and STRONG in Play Integrity diagnostics
pretty wild seeing all three on that setup
the source is now public
no keybox included
you're solely responsible for how you use it
drop a star github.com/antiyro/ukeystore…
TIL that @Tailscale always tries to find the shortest path to devices on my network
if they're right next to me, it'll route traffic directly over my local network
wait waaaaat
no bootloader unlock, no Knox fuse blown
in theory, this opens the door to rooting stock Samsung devices while keeping the hardware trust chain intact
good for apps spoofing
doing some research rn
Galaxy S26 Ultra: untrusted_app → root.
Introducing "Infinity Core": 6 vulns in the Linux kernel's core subsystems.
Their impact spans Linux server LPE, container escape, and Android LPE.
Details: github.com/V4bel/InfinityCor…
I’m currently trying to trace the vulnerability chain that could lead to a similar jailbreak
got the right abliterated models running blind, let’s see what they find
especially interested in how they achieved persistence across reboots without breaking the secure boot chain
going to shenzhen for the third time this year
everything in low- evel mobile engineering happens there
I'll be visiting factories across guangdong and documenting everything here and on tiktok
people are hyping up phone control like it's some crazy breakthrough
since Opus 4.6, frontier models have been perfectly capable of dumping screen states and interacting with apps using traditional libraries
but everyone is missing the actual problem 👇
the real bottleneck is the cost of running vision models at every step
decision models changed the game, but they're still not accurate enough
I think the future of app automation is deterministic execution powered by AI exploration
let frontier models explore an app, map its screens, elements and transitions, then use that map to generate deterministic workflows
say you want to send an announcement to all your LinkedIn contacts
the model generates a workflow from the map, tests it under human supervision, fixes what fails, then makes it reusable long term
no expensive model running at execution time
the best part? the entire system improves as vision models get better, without rebuilding existing workflows
I'm building this right now and will prob open source it
HERMES CAN NOW CONTROL YOUR PHONE. 🤯📱🔥
A new Phone Harness plugin gives Hermes the ability to actually operate an iPhone or Android.
We're talking real phone control:
• See what's on the screen
• Open apps and navigate menus
• Tap, swipe, scroll, and type
• Read the results and continue working
• Handle multi-step tasks inside mobile apps
And here's what makes this so interesting...
Hermes doesn't need a dedicated API integration for every app. It can interact with the same interface you use.
Supports iPhone through Mac mirroring, Android through ADB, and cloud phones.
Think about how many new workflows this opens up for Hermes.
Repo + setup in the first reply. 🔥
@phone_harness
this is great but it means carrying an esp32 dongle in your pocket
plus for security reasons you don’t want this running on your main device
I’d rather leave it plugged in at home and access it remotely through a small app on my main phone
终于搞懂大家为什么都在折腾 ESP32 了。花 50 块钱买块小板子,不用越狱也不用 Mac,直接接管 iPhone 自动点屏幕。这种低成本硬核玩法,难怪全在玩
github.com/onehumanbeing/esp…
but wtf is Play Integrity???
Play Integrity lets apps ask Google whether they can trust your Android device and the app running on it
it checks app authenticity, Google Play licensing and device integrity
there are 3 main device integrity levels:
BASIC: basic system checks, can pass with an unlocked bootloader
DEVICE: genuine, certified device. on Android 13+, hardware-backed proof of a locked bootloader and certified OS (socials don't seem to require above this one)
STRONG: on Android 13+, DEVICE requirements + recent security patches for both OS and vendor partitions (this level is for banking, auth etc apps)
the app receives a signed, encrypted token. its backend gets it verified by Google and decides what you can access
but Samsung adds another layer: the Knox warranty bit
STOP your phone farm slop #2
do you remember @ManusAI???
they went viral back in 2024 with this single video that supposedly showed their engine, which at the time was basically a LangGraph wrapper with tool access
the funny part: the video wasn't Manus at all, @peakji confirmed it
it's pretty clear this is one of the Chinese phone farm engines like genfarmer, laixi, some3c, xiaowei, etc
these engines are basically adb wrappers selling automations
today it's not that hard to build this kind of engine with claude or codex
but none of these engines handle the integrity of your devices
those devices are mostly second hand market devices, potentially stolen or refurbished
their actions will have a very low trust score with social platforms like TikTok, Instagram, Twitter, or YouTube
and spoofing is basically impossible... (or not ?)


















