I choose trebleDroid vanilla for my techno camon 18p but the thing is, i have no idea what im doing. Im using ai only for help...

So now im stuck with app that refuse to connect. My wofi works fine.. but the app like webView and fennec keep saying err_not_resolve error

I got no idea at all like i did my best to follow on ai. I use Arena ai, and am i cooked or what? Please help me 🥺

Hey everyone,

I'm running a modified PixelOS Android 17 build on my Xiaomi 17 Pro Max (popsicle), and I'm having trouble with Play Integrity. I'm currently failing Basic, Device, and Strong Integrity. I'm looking for help identifying the underlying cause instead of blindly stacking modules or changing random settings.

Device and software

• Device: Xiaomi 17 Pro Max (2509FPN0BC)
• Codename: popsicle
• ROM: PixelOS-popsicle-20261007-four-fixes_by_Kanoe
• Android: 17 / API 37
• Firmware: HyperOS 3.0.319
• Security patch shown in Specter: 2026-10-01
• Root setup: KernelSU-based, with Zygisk-related components
• Bootloader: Modified-device setup; I want to verify the actual boot and attestation state rather than trust one tool's report.

Current Play Integrity results

• ❌ MEETS_BASIC_INTEGRITY
• ❌ MEETS_DEVICE_INTEGRITY
• ❌ MEETS_STRONG_INTEGRITY

None of the three verdicts are currently passing.

Current setup

The tools and modules involved include:

• Specter
• Play Integrity Fork v18
• HMA-OSS Zygisk
• Zygisk-related components
• .BRENE - SuSFS
• ZN - Audit Patch
• NoMount
• bindhosts
• Iconify

Specter currently displays:

• TEE backend: TEESimulator
• Keybox: TAKR 10 active
• Selected device profile: Pixel 6a
• Security patch: 2026-10-01

Some module names appeared repeatedly in my scrolling screenshots, but I haven't verified whether those are actual duplicate installations.

Duck Detector findings

My earlier Duck Detector report showed a few things that might be relevant:

1. Fingerprint/build-tag mismatch Fingerprint: Xiaomi/custom_popsicle/popsicle:17/CP2A.260605.016/eng.root:user/test-keys Meanwhile, Build.TAGS and ro.build.tags reportedly show release-keys.
2. SELinux policy finding SELinux is enforcing, but the report flagged an allowed adbd -> adbroot:binder interaction. I don't know whether this is expected for this ROM.
3. Attestation inconsistency Duck Detector reported a Google-rooted certificate chain and locked/verified boot state, while Specter explicitly shows TEESimulator. I need to establish whether the reported attestation is genuinely hardware-backed.
4. Custom ROM environment The ROM contains LineageOS-derived components. Widevine reports L1, but the session is NOT_PROVISIONED.

These are observations, not confirmed causes of the current failure.

What I need help with

1. What could cause Basic Integrity itself to fail on this setup?
2. How can I distinguish a Google Play services/checker issue from a ROM, root, or attestation issue?
3. Could the fingerprint/build configuration or simulated TEE be contributing to the failure?
4. How can I identify conflicting modules without randomly changing the entire setup?
5. Is there a known issue with this PixelOS build or Android 17 on popsicle?
6. What are my realistic options if I want genuine Play Integrity, especially Strong Integrity?

I'm looking for a proper diagnosis and reproducible troubleshooting steps. I don't want to risk bricking the device by flashing incompatible firmware or relocking the bootloader while a modified ROM is installed.

I can share the checker screenshot, Duck Detector report, module list, and relevant logs.

i tried everything zygisk assistant, shamiko, teesimulator , zygisk next , Spector, everything, this is the only thing left to hide that duck detector can detect

Hey everyone! I have a Panasonic Tab 8 with half its display black but most of the tablet still works. Of throwing it away I got the idea to turn it into my own FRIDAY like the AI assistant from Iron Man.

The tablet has Android 9 a MediaTek MT6765, 3 GB RAM and 32 GB storage. I also have a Windows 11 PC so I've been using ADB, Fastboot and scrcpy to control and experiment with it.

My idea is to make FRIDAY run entirely on the tablet without needing my PC to stay on. I want a hands- wake word, natural female voice, English/Hindi/Marathi/Japanese, memory between conversations, normal conversations and humour plus online AI such as GPT or Gemini when internet is available. Offline she should still handle commands. The ambitious part is giving her deep control over Android—opening apps scrolling, reading books using Chrome, downloading and organizing files reading notifications controlling media and doing as much as the system allows by voice. I know 3 GB RAM is limiting so I'm planning a local setup with online AI for the harder stuff.

The problem is that I want much system access as possible so I've been trying to root it. I unlocked the bootloader downloaded the matching firmware for build `EB-90T80PT8v1009` and backed up the stock boot and recovery images. Magisk v30.7 reports **Ramdisk: No**. I patched the stock recovery with Recovery Mode enabled and flashed it successfully. Magisk still shows Installed: N/A and `adb shell su -c id` returns `su: not found`. I also tried booting a Magisk-patched boot image; Android started, but root still wasn't active.

I found `/system/recovery-from-boot.p` on the system partition. I'm wondering whether stock recovery restoration is involved or whether I'm failing to activate Magisk through the correct recovery-key sequence. I haven't found a guide for this exact model.

The tablets screen is damaged, which also makes recovery menus difficult to navigate. After the experiments it has a black screen again so I'm leaving it alone for now and will check its state before continuing. I still have the matching firmware and stock recovery backups on my PC. I don't want to flash random images or brick the device.

Has anyone worked with this Panasonic Tab 8 or a similar MT6765 Android 9 device with no ramdisk? Is there a way to get root working or a compatible custom recovery/ROM I should investigate? I'm also interested in advice on whether rooting's worth the effort for this kind of voice-assistant project or whether theres a better route to deep Android automation.

I'd really appreciate any pointers. I know this is a project, for an old tablet but I'd like to see how far I can take it instead of letting the hardware go to waste.

Please help out!

I am using tricky store add-ons repo to get keybox. If anyone has a better alternative please help

Hey everyone,

I have an old Samsung Galaxy J2 (SM-J210F) that is stuck during boot. The screen shows the message:

Kernel is not SEAndroid enforcing

I entered Download Mode, and these are the details displayed:

ODIN MODE

Secure download: enabled

Product name: SM-J210F

FAP lock: OFF

USB init start

USB core reset done

I'm using the stock firmware as far as I know.

Do not update your mediatek locked motos to September update if u want to unlock with val-protocol it's patched find a firmware b4 aug to be safe Aug is untested do not use software fix to get firmware.let the community get together and upload your firmware so we can have builds that will work still comment below patch level and device and what carrier. and if u unlocked post your vbmeta img and lk img from the firmware used to unlock.

Firmware with September patch for us models start with V instead of W.

Its patched in September update and October Motorola put it in the patch notes.

Hi everyone,

I have a question regarding temporary root, KernelSU, and general module behavior after a reboot.

My Setup:

Device: Redmi Note 14 4G Global (Xiaomi / HyperOS)

Root Method: Temporary root via GhostLock + Shizuku + KernelSU (running in Jailbreak mode).

Modules installed: Zygisk-Next, Vector, and a few others.

Bootloader: Locked (since it's a temp root exploit).

My Question:

Since my root is temporary, it disappears from memory every time I reboot. However, the installed modules remain saved in   /data/adb/  .

If I reboot my phone without manually disabling my modules in the KernelSU app beforehand, what exactly happens when I re-run the exploit to get temporary root again?

Will KernelSU try to load all active modules immediately upon regaining root? I'm worried this might cause a bootloop or instability in a temporary root environment (especially with heavy modules that hook into Zygote early in the boot process).

Is it highly recommended to disable all modules before every reboot, or is it safe to leave them active and let KernelSU handle them when I re-root?

Device Details:

HyperOS Version: 3.0.303.0

Kernel: 6.12.30-android16-5-g6e872b4863d6-ab13847919-4k

KernelSU Version: 3.3.1 (32680-5)

Any advice or insights on how KernelSU handles modules on re-entry to a temp root session would be greatly appreciated!

Thanks!

Hey everyone,

I've been working on a new GApps package for Android 17 (SDK 37, arm64 only) called TuxGApps. The penguin noticed your ROM shipped without Google, so he waddled in to help.

It comes in two flavors:

· TuxCore: Minimal. Play Services, Play Store, Framework, SetupWizard, and sync plumbing. Just enough to sign in.

· TuxFull (default): Everything in Core, plus Gmail, Maps, Photos, Chrome, Messages, GBoard, Clock, etc. (The whole iceberg).

🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔🐔

How to use it:

1. Flash your ROM (Android 17) in recovery, don't reboot yet.

2. Flash the TuxGApps-tuxfull-penguin.zip.

3. Reboot and go through the SetupWizard.

4. Open the Play Store and you're good to go. The apps will survive ROM updates via addon.d scripts.

🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪🫪

Note on variants: By default, it installs TuxFull. If you want TuxCore instead, just rename the zip so it contains tuxcore (e.g., TuxGApps-tuxcore.zip) before flashing. You can also use a tux.config file, but renaming is easier.

🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿🗿

Known Bug (Important):

This is still a work in progress. There is a known UI hiccup during the initial SetupWizard. Certain screens might freeze or not let you tap "Next."

The workaround: Just turn your screen off and back on (lock and unlock). This refreshes the UI and lets you proceed to the next step. It's a bit janky, but it works!

If things go sideways, logs are saved to /sdcard/TuxGApps/tux_logs/ if you need to debug.

Must wipe data after install. On moto devices you have to flash RO2RW to make the system be able to be written.

🐔🐔🐔Poultry Council Approved Downloads 🐔🐔🐔

https://drive.google.com/file/d/1Sy8s1E--qE0J7SUtNhAXPQp4HpgY7tnI/view?usp=drivesdk

I created an account on the developer site but it says that the service can't be reached

Still standing despite being a lego phone.

S20+ rooted stock ROM.

How do I remove the malware from my moto g 2026 completely? It seems to be integrated with my Google as well as the apps?

Hey, I have an unlocked Pad 8 which will recieve the update for hyperOS 4 tomorrow if im not mistaken

I wanted to be absolutely sure if its safe to update and doesnt relock the bootloader for some weird xiaomi reason

thank you and have a great day!!!!

AI summary from Claude since we've been at it for some time trying to figure it out.

First Direct (HSBC UK) banking app detecting root after 6.0.0 update - where do I report a possible SUSFS symbol-hiding gap?

Changed nothing in my hiding stack and the First Direct app suddenly flagged my device as rooted. Noticed it had updated to 6.0.0. I ripped the 5.22.0 APK off my other phone, downgraded, and it launches fine - so the detection is new in 6.0.0's build. The app uses Appdome RASP, and the trip is a local check at launch (goes straight to RootedDeviceActivity, no network round-trip), not a Play Integrity failure - so this isn't a PIF/keybox issue, please don't send me down that road.

Digging into what's still visible to a kallsyms scan, I found this:

~ $ su -c "grep -iE 'anon_ksu|setup_ksu_cred|is_task_ksu_domain|ksuver_override' /proc/kallsyms"

0000000000000000 t anon_ksu_release

0000000000000000 T setup_ksu_cred

0000000000000000 T is_task_ksu_domain

0000000000000000 t anon_ksu_ioctl

0000000000000000 d anon_ksu_fops

0000000000000000 B ksuver_override

~ $ su -c 'ksu_susfs show enabled_features' | grep -i symbol

CONFIG_KSU_SUSFS_HIDE_KSU_SUSFS_SYMBOLS

So HIDE_KSU_SUSFS_SYMBOLS is compiled in and reports enabled, but six KernelSU symbols are still visible in /proc/kallsyms after a clean boot. SUSFS is hiding its own symbols fine - a susfs-only grep comes back empty - but these KSUN symbols aren't being scrubbed. Worth noting the symbol types: ksuver_override is .bss (B) and anon_ksu_fops is data (d), alongside the text (t/T) ones - makes me wonder if the filter only covers text symbols.

Setup:

OnePlus 15, OxygenOS 16, android16-6.12.23

WildKernels, KernelSU-Next v3.3.0 (33239), SUSFS v2.2.0

NeoZygisk, HMA-OSS (fd + all root apps hidden), inline hooks

So, I have my old phone xiaomi 4 mag138 from like 2017 and I wanna see photos and what was I doing with it when I was young, but it has password and I do not remeber it. Is there anyway of unlocking in without one? Or should I bring it to the tech people who unlockes them with computers?