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 didn't know this was even possible lol

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

Woah

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

Soo, Google released a new update recently absolutely destroying integrity, they check for more than integrity and (spoofed) locked bootloader so it's become WAY more tricky, yes it shows strong for you but don't fret on it one clear app data and it's gone,

What's the solution? I don't know.. for now it's just like that until devs come up with an idea

Hey everyone! Since the community for the Lenovo Tab M11 is mostly dead and many people get stuck in bootloops or get the dreaded "dm-verity corrupted" red screen, I wanted to share the exact hardware-level method I found to successfully bypass Lenovo's lock and boot custom GSIs flawlessly. This guide template works for flashing stable GSIs (like AndyYan's Android 15 LineageOS) or experimental ones (like risingOS Android 16 Vanilla) using either a PC or another tablet via Bugjaeger.

(You need mtkclient (bkerler), adb platform tools and your desired gsi (Android 15/16 I suggest)

🛑 CRITICAL STEP 1: The Smart Backup (Skip Userdata!)

Do not dump everything blindly. userdata will take 5+ hours and fill your hard drive. • Connect your tablet in BROM Mode to your PC using mtkclient (GUI). • Manually deselect userdata in the GUI partitions list. • Dump the rest of the firmware. Your super partition will be around 11 GB, but it reads reliably. This is your ultimate 100% safety net.

🔓 CRITICAL STEP 2: The Hardware Shield (Bypassing dm-verity)

Lenovo hides an army of security tables (vbmeta_a/b, vbmeta_system_a/b, vbmeta_vendor_a/b). If you flash a GSI without patching them, it's an instant brick. • Use the mtkclient GUI to click Unlock Bootloader (this handles your seccfg). • Immediately open your terminal/command prompt inside mtkclient and execute this global chipset command directly: mtk da vbmeta 3 • Why this works: This command automatically scans the partition table, finds all 6 instances of vbmeta, and patches their headers globally to disable verification entirely. Even if you see a brief warning on boot (If it says Dm verity corrupted it s just a false warning, i also got that warning it s there to trick you so simply press the power button and it will change to your device will boot in 5 secs), just click the power button and it will bypass it safely!

⚡ CRITICAL STEP 3: The Safe Charging Pause

• Do not flash with low battery! BROM mode drains the cell massively. • Unplug from the PC, connect the tablet to a wall charger for 15 minutes until it hits at least 35-40%. A power drop during system flashing will cause a hard-brick.

🛸 CRITICAL STEP 4: Flashing the GSI (PC or Bugjaeger OTG)

You can do this via standard PC terminal or directly from another device using Bugjaeger via an OTG cable connection.

1. Boot the tablet directly into FASTBOOTD mode (run adb reboot fastboot or hold Vol Down + Power). Make sure the screen says fastbootd.
2. Free up logical partition blocks by running: fastboot delete-logical-partition product_a (optional, if needed)
3. Wipe the laggy stock Lenovo system partition: fastboot erase system
4. Flash your custom GSI image (rename your .img file to system.img): fastboot flash system system.img
5. Wipe old stock structural encryption data completely and reboot:fastboot reboot recovery

Wipe Data from recovery (It might look like it's stuck, just give it 30 secs-1min)

fastboot reboot 💡 Developer Notes & Troubleshooting:

• Android 15 (AndyYan LineageOS arm64_vn_light): Absolute peak performance. Wi-Fi, audio, camera work flawlessly out of the box. Highly recommended for daily use. • Android 16 (risingOS VANILLA): It boots! Wi-Fi, audio, and camera are fully functional despite the older VNDK 33 framework. • Note on Vanilla builds: If you flash a Vanilla GSI, it does not include GApps package out of the box. The system will boot but you won't see the basic google apps.

The Android 16 menu will load up instantly! Even if you don't have Gapps.

Enjoy!

Help! I was installing TWRP, and now my phone is stuck in a boot loop at the Android Bootloader Unlock Warning screen. Pressing the power button does nothing. Instead, the phone keeps restarting, showing the Samsung logo, and then returning to the warning screen repeatedly. I aloo tried to forcely turned it off then power it on .but it does nothing

I need help recovering my Clovertek G12 tablet, which is stuck in a bootloop and always returns to Android Recovery. I’m using a Windows PC and am willing to try unofficial repair methods.
Device information
Brand: CLOVERTEK
Model: Clovertek G12
FCC ID: 2BCQA-G12
Android version: 12
Build: CLOVERTEK / Clovertek_G12
Reported chipset: MediaTek MT8766
Bootloader: Locked (unlocked: no)
Secure boot: Enabled (secure: yes)
Fastbootd: Supported (is-userspace: yes)
Current slot: A
Product: clovertek_g12

Problem
The tablet displays the Clovertek logo, then returns to Recovery instead of booting Android.
I already performed a factory reset, but it didn’t fix the problem.

Hey everyone! Pixel Suite 2.0.0 is out. After 45 preview updates, a lot of testing and small adjustments, this brings the launcher, drawer and module settings together into one release.

🏠 Open Pixel Suite straight from your home screen

Long-press an empty area on the home screen to access the module settings.

📁 Drawer folders and separate folder grids

Create folders in the app drawer, rename them, add apps, sort their contents or remove the folder and return its apps to the drawer. Choose 3×3, 4×4 or 5×5 grids independently for home-screen and drawer folders. The drawer stays alphabetically sorted.

↗️ Smoother drawer dragging

Move apps around inside the drawer and drag toward the “Add to home screen” target when you want to place one on the home screen. Folder animations, menus and spacing have also had a lot of attention.

🎨 Rename apps and change their icons

Pick an image from Photos or Files, or give an app a different name. Changes apply immediately across the home screen, folders, drawer and both searches, including the Google search bar. Original icons can be restored.

🔤 Labels and shortcuts

An optional five-level label-size control changes only the text, leaving icon sizes alone. It is off by default. You can also hide app-provided drawer shortcuts while keeping the usual launcher and Pixel Suite actions.

✂️ Screenshot tools in Pixel Studio

Free cropping and Doodles: draw shapes, change color, thickness and fill, move or resize markup, and use Undo/Redo while editing. These tools depend on a supported Pixel Studio version.

🧹 Recents and Files

Clear all stays visible alongside Select and Screenshot instead of being tucked away at the far left. Newest-first sorting also covers the system file picker, keeping folders first.

⚙️ A redesigned settings app

All Pixel Suite controls now live inside the module, with light/dark themes, animated feature previews and an in-app changelog. The flashlight, camera, three-finger screenshot, sleep and wake options are still there with their own settings.

Compatibility and updating

This is a free, open-source LSPosed module for rooted Pixels using API 102. Tested on a Pixel 11 Pro running Android 17; it should also work on other Pixel devices, though I would appreciate reports from other models. System and Google app versions can affect compatibility.

Install the new APK over the existing version, check the recommended LSPosed scope in the README and reboot. Enable Google for search customization and Pixel Studio for the screenshot tools.

Downloads and full changelog

GitHub — v2.0.0: Download APK

Xposed repository — v2.0.0: Download APK

Source code (GPL-3.0): View on GitHub · Bug reports: Report an issue

If you try it on another Pixel, let me know your model, Android version and how it goes.

Made by RovianDev

Your Pixel. Your Way.

I rooted my friend's phone and it was going okay for a few weeks. She said last night her phone was died (no battery) so she just charged it as usual but when she turned on her phone suddenly it doesnt connect to the internet, simcard cant be read, and status bar doesnt load as well, and the phone also got flickering screen too.

How to fix this?

The phone is Redmi Note 10s.

this probably has been asked a million times here but i just need a little help from people who understand it better than me. i have a Samsung Tab S9 FE+ and i was planning on rooting it, but OEM Unlock is unavailable and i can’t downgrade to One UI 7 (or any other One UI version) because my bit number is G. is there ANY help for this or am i just cooked?

Got the Z Fold 8 Ultra so it shipped with A17.

Was looking to de-google and run MicroG, but the signature spoofing module needed (FakeGapps) only supports up to Android 16.

Any way to get signature spoofing working with root/Lsposed on A17?

Looks like you no longer have to compile your own kernel at all to get a KSUN + SuSFS setup on GKI 2.0 devices, I have not tested it since I already have SuSFS built in but this is awesome!

The update also brings fixes and a security feature to restrict shell root to adb sessions, you can read the full release notes here:

https://github.com/KernelSU-Next/KernelSU-Next/releases/tag/v3.4.2

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.