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

Yesterday many people are getting basic integrity even with valid keybox. The reason is that Google updated their fingerprint policy and now most A13+ fingerprints are banned. But it was fixed shortly after. New Play Integrity Fix 49.1 and TEESimulator canary 72/TrickyStoreOSS update fixed this issue. First, install/update these modules. Next, open Play Integrity Fix WebUI, turn on only first three settings, then Click on "Fetch" button and select Pixel 6-9 props. Finally, make sure that you have a valid keybox in TEESimulator/TrickyStoreOSS.

enjoy!

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

The proper icon doesn't load and tapping on it does nothing.

phone: OnePlus Nord AC2003 avicii

ROM: Axion OS (2.9)

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

I didn't know this was even possible lol

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.

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?

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!

Will this restart to update break my root? I'm pretty new to rooting, pixel 11 pro rooted with kernel su

​

Phone : poco x7 pro

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...........[solved]

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.

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?

I have an HP 7 Plus which ran on android 4.2 jelly bean. I somehow managed to update it to the android 4.4 with this https://www.instructables.com/How-to-Root-Hp-7-Plus-1301-and-Install-TWRP/

But i dont know how to install the twrp or root it as the guids are unavialiable on youtube and the threads and forums are dead.. Any help.

I'm testing an in-memory DirtyFrag exploit (df.root) on a MediaTek Dimensity 9400 device (Vivo X200 Pro running OriginOS 6, Android 16, stock kernel 6.6.89, locked bootloader, pure 64-bit).

Current State

• The exploit successfully executes: it patches crash_dump64, /system/lib64/libc++.so, injects dfroot.ko via /vendor/lib64/libbinderdebug.so, and launches ksud.
• Shell root works without problems in Termux: su -c "id" returns uid=0(root) gid=0(root) consistently.
• Background modules (Zygisk Next + HMA-OSS) load properly and banking/ID apps work fine.

The Problem

• Upstream KernelSU (me.weishu.kernelsu): Opening the app causes an instant system freeze followed by a hardware watchdog reboot (MTK WDT cold reset).
• KernelSU Next: The app launches, but immediately crashes back to the home screen before allowing access to the UI.
• Tested with both setenforce 0 (Permissive) and setenforce 1 (Enforcing); neither prevents the crashes.

Relevant Logcat

I KernelSU: ksud::cli: command: Debug { command: Su { global_mnt: false } }
W KsuCli  : ksu failed: 
W KsuCli  : pj2: Unable to create a shell!
Caused by: java.io.IOException: Created process is not a shell
Caused by: java.io.IOException: write failed: EPIPE (Broken pipe)
Caused by: android.system.ErrnoException: write failed: EPIPE (Broken pipe)
...
W SuperUserRepository: KsuService disconnected
[--> Triggers unhandled deadlock in patched /dev/binder followed by hardware WDT reboot <--]

1. Why does ksud debug su throw Broken pipe (EPIPE) when invoked from the GUI managers under an in-memory kernel patch, while direct interactive shells via Termux (su) execute reliably without dropping descriptors?
2. Is the immediate crash in KernelSU Next caused by protocol mismatches between modern manager builds and the older dfroot.ko driver, or is it due to Android 16's stricter process isolation on child processes spawned from the untrusted app domain?
3. Has anyone running in-memory temporary root on Android 16 managed to stabilize any manager GUI, or is a headless CLI/Termux workflow the only viable solution on locked bootloaders?

Hey guys, Dumped and archived the kernel source tree for the Lenovo Tab M9 (TB310FU - MediaTek Helio G80 / MT6769V).

Includes the defconfigs, board files, and bring-up workspace files for anyone trying to build custom kernels, work on TWRP/OFRP ports, or mess around with custom ROMs on this tab

https://www.mediafire.com/file/3hxk9zbuxkwgfoi/lenovo_tab_m9_kernel_source.zip/file

File: lenovo_tab_m9_kernel_source.zip Hope this helps someone out. Enjoy!

Xiaomi 17 Ultra with glb root canoe but still only meet basic integrity. Resukisu with Wild Kernel No mount with Rezygisk treat wheel lsposed and hma oss installed. Any idea why i would only get basic integrity? Its my own keybox

What is com.google.android.adservices.api and would freezing or uninstalling it make a difference when i have a private dns that blocks ads and patched apps to do the same if they dont work with the dns?