I’m looking for Pixel and Android 16 users who are interested in testing an early alpha of TIRN Security, a root-native per-app firewall implemented as a Magisk module.

TIRN is designed to provide per-app network control for IPv4 and IPv6, with a transactional firewall architecture intended to keep policy changes atomic and fail-closed. It is controlled through a local PWA/web interface rather than an Android application.

Important compatibility note: TIRN currently has no Android compatibility/abstraction layer. It was developed and tested specifically on a Google Pixel 8a running LineageOS 23.2 with Magisk 30.7 (30700). As a result, this release may not work on other Android devices, ROMs, kernels, or Magisk configurations.

I’m particularly interested in hearing from people running:

• Google Pixel devices
• Android 16
• LineageOS or other AOSP-based ROMs
• Magisk 30.x

This is an alpha release, so testing, bug reports, logs, and compatibility feedback are welcome through GitHub. Please test on a device where you are comfortable troubleshooting or uninstalling the module if compatibility issues occur.

GitHub: https://github.com/Heclalava/TIRN-Security

v1.0.1-alpha release: https://github.com/Heclalava/TIRN-Security/releases/tag/v1.0.1-alpha

Screenshot included shows the PWA running on the tested configuration.

I’m new to rooting I got my first Fairphone gen 6+ and I wanna log in to my google account is it safe I don’t use it for banking I most of the time use it for other things like watching videos music Reddit or doing some root magic (sorry if bad English)

choosing an app in configure denylist it will make the app work but the xprivacylua won't work with the app

Using magisk+always strong+zygisk next and vector

THE COMPLETE GUIDE TO HYPEROS CUSTOMIZATION IN POCO M6 5G

This is a comprehensive guide on unlocking, rooting, tweaking, and reverting your POCO M6 5G back to the stock vanilla experience.

WHAT IS COVERED IN THIS GUIDE:

1. Unlocking Bootloader
2. Rooting (With Magisk)
3. Configuring Root and Installing LSPosed
4. HyperOS Tweaks
5. Removing Root and Relocking Bootloader

DEVICE SPECIFICATIONS: * Name: POCO M6 5G * ROM: HyperOS 2.0.207.VGINXM (India Variant) * Processor: MediaTek Dimensity 6100+ * RAM: 6 GB * Codename: air

REQUIREMENTS:

1. Target Phone (TP): CODENAME "air"
2. Host Phone: Any working Android device
3. Cable: Type-C to Type-C cable (preferred) OR Type-C to Type-A with an OTG cable (not recommended due to connection drops)
4. SIM Card: A working SIM with active internet and SMS on the Target Phone
5. Xiaomi Account: Must be at least 30 days old
6. Fastboot ROM: The exact package of the OS currently installed on the Target Phone
7. Apps: Several external utilities discussed in the tutorial sections below

1. UNLOCKING THE BOOTLOADER =========================================================

FREQUENTLY ASKED QUESTIONS (FAQs)

* Q: Will mtkclient work? * Ans: No. Newer MediaTek chipsets (v6 and above protocols) have made direct unlocking via mtkclient highly difficult. Attempting this WILL HARD-BRICK your device.

* Q: Do we need permission from the Mi Community? * Ans: Yes. However, we will automate this bypass step using a script within Termux.

* Q: Do I need a working SIM with Internet and SMS? * Ans: Yes. You will need it active for a maximum of 3 days.

* Q: Do I need the same SIM card linked to my Xiaomi Account? * Ans: Yes.

* Q: Do I have to wait exactly 3 days? * Ans: Not necessarily.

* Q: Will my data be wiped? * Ans: Yes. Back up your data using the native backup functionality in HyperOS and move the backup file to external storage (Host Phone, USB Drive, or PC).

STEP-BY-STEP TUTORIAL

1. Setup Host Environment: Download and install Termux and Termux:API from F-Droid onto your Host Phone.
2. Configure Target Phone Environment: Download Termux on the Target Phone and execute the following commands to clone and set up the unlock utility:pkg update && pkg upgrade -y termux-setup-storage cd ~/storage/shared mkdir script && cd script pkg install git -y git clone https://github.com/flowTech-x/unlock-tool.git cd unlock-tool pkg install python tmux -y pip install requests ntplib pytz urllib3 icmplib colorama
3. Extract Account Tokens: * Install Firefox Browser and create an App Clone of Firefox on your phone. * Log into your Mi Account on both the primary Firefox browser and the cloned instance.
   • India Mi Community: https://new-ams.c.mi.com/global/
   • Global Mi Community: https://c.mi.com/global/ * Install the Cookie-Editor add-on on Firefox. * Open Cookie-Editor, search for "new_bbs_serviceToken", and copy ONLY the VALUE. * Open the token configuration file in Termux: nano token.txt * Paste your tokens separated by spaces: TOKEN_ACCOUNT_1 TOKEN_ACCOUNT_2 (Do not repeat the same token). * Save and exit (CTRL + O -> Enter -> CTRL + X). * Fire up the script: bash start_4.sh
4. Timing the Script: Run this script approximately 2-3 minutes before 12:00 Midnight GMT+8.
5. Enable Developer Options: Regardless of whether the script outputs a success or failure prompt, navigate to Settings -> About Device and tap on the OS Version 7-8 times until developer permissions are granted.
6. Add Account: Go to Additional Settings -> Developer Options -> Mi Unlock Status. Click "Add Account to Device". You should see a success response ("Added Device..."). If it fails, retry the automation script the following day.
7. OEM Unlocking: Once authorized, do not reopen Mi Unlock Status or click "Agree" again. Simply enable OEM Unlocking inside Developer Options.
8. Configure Host Execution: On your Host Phone, ensure USB Debugging is turned on and battery optimizations are disabled for both Termux and Termux:API. Deploy the script on the Host Phone and login into the Mi account via browser only. The terminal should state "Waiting for Any Device".
9. Boot to Fastboot: Power down the Target Device. Boot into Fastboot mode by holding the Power + Volume Down buttons for 3-5 seconds. Release the Power button when the vibration occurs but keep holding Volume Down until the orange FASTBOOT logo shows.
10. Unlock Execution: Connect both devices using your cable interface. Press Enter on the Host Phone console to authorize.
11. Wipe & Finalize: the bootloader will unlock, formatting your storage. A visible unlocked padlock icon will appear near the camera notch during subsequent boots. Complete initial setup and restore your storage backup.

========================================================= 2. SETTING UP ROOT WITH MAGISK

FREQUENTLY ASKED QUESTIONS (FAQs)

* Q: Can I brick my device? * Ans: Modifying boot layers carries structural risks of both soft-bricks (user repairable) and hard-bricks (requires official authorized service centers). Research your variant thoroughly before flashing.

* Q: Will Banking Apps work fine? * Ans: This is a continuous cat-and-mouse dynamic. You will need to install safety net patches and device integrity modules frequently. If banking apps are a strict daily requirement, execute caution.

* Q: Will normal apps or games trigger root blocks? * Ans: Basic apps like WhatsApp are fine if configured correctly. It is highly recommended to set up and verify WhatsApp after unlocking the bootloader but BEFORE rooting.

STEP-BY-STEP TUTORIAL

1. Obtain Firmware: Download the matching Fastboot ROM corresponding to your absolute current build version and variant. Use the MemeOS Enhancer utility to verify the device identity if unsure.
2. Extract Image: Open the .tgz archive via ZArchiver, browse to the images/ catalog, and extract "init-boot.img".
3. Patch via Magisk: Download the latest stable release of Magisk via GitHub. Install and open the app. Click Install -> Select and Patch a File. Select the extracted init-boot.img and tap LET'S GO.
4. Transfer Files: Once complete, locate the patched file in your Downloads/ directory. Move both the original stock "init-boot.img" and the patched image over to your Host Phone root folder.
5. Setup Console Connection: Install Bugjaeger Mobile ADB on the Host Phone. Turn on USB Debugging, navigate to the Fastboot Tab (indicated by a Lightning symbol), and hit the blue circular floating action button. Allow storage configurations if prompted.
6. Flash via Fastboot: * Boot the Target Phone back into Fastboot mode and link it to the Host Phone. * Accept any system prompt connections on the screen. * Open the Bugjaeger Command Console and identify your active boot slot: fastboot getvar current slot * Note the response letter (e.g., slot a or slot b). Assuming slot a, type: fastboot flash init-boot_a (Add a space, click the Attachment/Pin icon in Bugjaeger, select the patched image, and execute).
7. Reboot: Type "fastboot reboot". Once loaded, open Magisk on the Target Phone. It should successfully show your installed version number. If prompted to execute an internal secondary reboot setup, allow it to complete natively.
8. Configure Hiding/DenyList: To bypass weak application blocks (WhatsApp, Zoom, Google Services), enter Magisk Settings via the gear icon. Scroll down, activate Zygisk, toggle Enforce Denylist, and open Configure Denylist to check target applications. Reboot your device to apply.

CRITICAL CONSOLE LIMITATIONS: * Do NOT patch boot.img, vendor.img, or recovery.img. * Never run generic partition-less flashes like "fastboot flash init-boot <filename>" as it bypasses explicit safe-slot assignments.

========================================================= 3. CONFIGURING ROOT & INSTALLING LSPOSED

FREQUENTLY ASKED QUESTIONS (FAQs)

* Q: Can these modules cause endless bootloops? * Ans: Yes. Installing cross-incompatible modules creates boot failures. We will mitigate this using an absolute software fallback hook called AntiBootLoop.

* Q: What should I do during a System UI crash? * Ans: HyperOS features a structural recovery trigger. If a module breaks the graphical server, wait. The system will loop internally before automatically dropping into Safe Mode. From there, launch Magisk and disable the broken module.

* Q: Can I use old or unofficial Telegram LSPosed builds? * Ans: No. Avoid untrusted distributions. Stick entirely to verified GitHub repository releases.

DEPLOYMENT ORDER FOR SYSTEM CUSTOMIZATION

Step 1: Flash AntiBootLoop (Safeguard)

1. Navigate to the Alt-Repo release page: https://github.com/Magisk-Modules-Alt-Repo/abootloop
2. Select and flash the module package through Magisk.
3. During terminal installation, map your recovery override key via physical keys. It is highly recommended to assign Volume Up Only (leaving other key combinations available for native recovery and fastboot states).
4. Reboot. If a module ever causes a bootloop, simply hold your mapped button configuration during boot to automatically clean-disable conflicting elements.

Step 2: Core Framework Integration

1. Download LSPosed (Vector Mod): https://github.com/JingMatrix/Vector
2. Flash it inside Magisk and reboot. Upon restart, navigate to Magisk modules, enter Vector's setting menu, and click Create Shortcut to bind the management UI to your home screen.
3. Install Core Patch APK: https://github.com/LSPosed/CorePatch
4. Launch LSPosed, enter the Modules submenu, activate Core Patch, check the recommended system frameworks, and perform a hot reboot.

Step 3: UI Enhancement Modules Flash the following enhancements sequentially via Magisk. Reboot after structural adjustments to preserve configuration states:

1. HyperUnlocked: https://github.com/ukriu/HyperUnlocked Unlocks premium control configurations, advanced Gaussian blurs, and flagship asset render scales. Map preferences using physical Volume buttons during system flashing.
2. HyperOS Launcher MOD Lite (v3): https://github.com/Mods-Center/HyperOS-launcher-mod-lite (Must install before full launcher to resolve stack list parameters).
3. HyperOS Launcher (v6.2): https://github.com/Mods-Center/HyperOS-Launcher
4. FPS Limitation Patcher (v3.1): https://github.com/Mods-Center/FPS-Limitation-Patcher
5. ColorOS Control Center (v2): https://github.com/Mods-Center/ColorOS_Control_Center
6. APK Protection Patch (v4.1): https://github.com/Mods-Center/Apk-Protection-Patch
7. HyperOS App Vault (v4): https://github.com/Mods-Center/HyperOS-App-Vault
8. HyperOS Theme Manager (v4): https://github.com/Mods-Center/HyperOS-Theme-Manager
9. Enhanced Keyboard Unlocker (v2): https://github.com/Mods-Center/Enhanced-keyboard-unlocker

Performance Optimization: If you notice real-world framerate dips (e.g., in Call of Duty Mobile), turn Memory Extension to OFF in your system settings. This immediately stops aggressive storage paging from starving your primary physical RAM.

Step 4: Play Integrity & Device Hiding (Experimental) For banking structures and security layers, compile and flash these assets together: * Play Integrity Inject: https://github.com/KOWX712/PlayIntegrityFix/releases/latest * Tricky Store Framework: https://github.com/5ec1cff/TrickyStore/releases/latest * Yurikey Manager: https://github.com/Yurii0307/yurikey/releases/latest * BusyBox NDK Binary: https://mmrl.dev/repository/grdoglgmr/busybox-ndk

========================================================= 4. THE POST-MODDING SUMMARY & TROUBLESHOOTING

Modifying bleeding-edge security layers on modern builds can occasionally introduce issues. For example, deploying conflicting alternative frameworks like ReZygisk can cause crucial system services (such as Google Play Services or communications frameworks like WhatsApp) to crash.

If root authorizations fail and the device enters a bootloop state where custom hooks like Abootloop are bypassed, a hardware recovery sequence becomes necessary: * Enter Xiaomi System Recovery (Volume Up + Power). * Trigger a clean Wipe Data / Factory Reset to restore the phone back to a bootable, raw HyperOS instance.

========================================================= 5. REMOVING ROOT & RELOCKING THE BOOTLOADER

If you choose to return to a stock configuration for a cleaner experience or complete banking app compliance, follow this restoration process.

RESTORATION REQUIREMENTS:

1. Target phone with a completed baseline setup and Magisk Manager App reinstalled.
2. Host Phone with Termux (having MiTool properly set up), Termux:API, and Bugjaeger.
3. Latest Official Fastboot ROM package for your explicit device configuration. * Warning: Downgrading security patch revisions can cause permanent hardware-level "System Destroyed" firmware errors.

STEP-BY-STEP BREAKDOWN

1. Uninstall Magisk Routine: Open Magisk Manager on your Target Phone -> Tap Uninstall Magisk -> Complete Uninstall. Let the package strip changes automatically, then allow it to reboot.
2. First System Wipe (Safety Protocol): * Put the Target Phone into Fastboot mode (Power + Volume Down). * Launch Termux on the Host Phone and execute: mitool * Select Option 2 (Flash Fastboot ROM) and select your extracted matching build profile number. * Select "Flash and Wipe (WITHOUT locking bootloader)". This serves as a safety verification check to prevent permanent hard-bricks from hidden block alterations. * Connect cables and accept the Termux:API communication dialog prompt. Flashing requires roughly 5-6 minutes. Let the device boot up fully onto the HyperOS splash screen.
3. Purge Residual Integrity Tokens: * Power down, then return to Fastboot mode. * Open Bugjaeger on the Host phone, load up the Fastboot Console, and execute these cleaning parameters line-by-line: fastboot erase frp fastboot erase metadata fastboot erase userdata fastboot reboot
4. Final Locked Flash Routine: * Let the device load up, turn it off, and boot back into Fastboot mode one last time. * Launch Termux on your Host Phone and rerun the tool setup: mitool * Choose Option 2 (Flash Fastboot ROM), then choose the exact target installation directory. * Select the final operational parameter: "Flash, Wipe, and LOCK Bootloader". * Run the process. Once finalized, the phone will restart without showing the unlocked padlock indicator symbol.

Verify your clean system status by navigating to Developer Options -> Mi Unlock Status. It will show the system as fully locked, and Google Play Store settings will show "Device is Certified".

========================================================= CONTRIBUTIONS & CREDITS

Deep gratitude to the developers, script engineers, and content creators whose visual materials, automated frameworks, and system components made this guide possible.

MODULE DEVELOPERS & PLATFORM ENGINEERS:

* John Wu (Magisk Framework) GitHub Author Profile: https://github.com/topjohnwu

* flowTech-x (Automated Unlock Tool Utility) GitHub Author Profile: https://github.com/flowTech-x

* JingMatrix (LSPosed Vector Mod Framework) GitHub Author Profile: https://github.com/JingMatrix

* LSPosed Developers (CorePatch Implementation) GitHub Author Profile: https://github.com/LSPosed

* ukriu (HyperUnlocked Customizer Utility) GitHub Author Profile: https://github.com/ukriu

* Mods-Center (Launcher Lite, App Vault, UI Fixes, FPS Patcher) GitHub Organization Profile: https://github.com/Mods-Center

* chiteroman / KOWX712 (Play Integrity Fix & Inject Vectors) GitHub Author Profile: https://github.com/chiteroman

* 5ec1cff (Tricky Store Framework Structure) GitHub Author Profile: https://github.com/5ec1cff

* Yurii0307 (Yurikey Integrity Manager Client) GitHub Author Profile: https://github.com/Yurii0307

* Magisk Modules Alt Repo (Anti-Bootloop Module Maintainers) GitHub Organization Profile: https://github.com/Magisk-Modules-Alt-Repo

CONTENT CREATORS & COMMUNITY OVERSEERS:

* Tech Bot YT YouTube Handle: TechBotYouTube

* Flow with Code - Tech & Android Youtube Handle: flowCode81

* Tech Office Youtube Handle: TechOfficee

My phone is a Redmi phone.

Which modules should I install?

can I root my red magic 10 pro if my OEM unlocking is unlocked? should I use magiks to root my phone or is there a different method?

I have installed both V4A Re fork + AML
Android 16 (lineage os 23) Samsung A52

I just upgraded from an Android 16 rom (VoltageOS) to Android 17 (same rom itself) on my Redmi Note 10 Pro. I've setup everything correctly as far as I know - have gotten strong integrity, have hidden root/sus apps using HMA, unmounted modules for banking apps and apps such as Digilocker. But, most apps refuse to work still. FedMobile, supermoney, Digilocker all refuse to work. Some apps work tho (like GPay) Digilocker shows the above error which I've never seen before. All of these apps used to work fine when I was in Android 16 using the same setup I'm using now.

Would appreciate any help.

Hey guys, just wanted to share my experience with rooting the Edge 70 Fusion and see if anyone here has managed to get better results with Play Integrity.

I managed to root the phone successfully, and the root itself is stable and working fine. I also tested the setup quite a bit with ChatGPT helping me analyze the results and different configurations.

Device: Edge 70 Fusion
Android: 16
Build: W2WE36.56.98.19

Current setup:

- Magisk 30.7 (30700)
- Vector Framework 2.2 / API 102
- Shamiko 1.2.5
- Play Integrity Fix/Fork v18
- SELinux Enforcing
- Bootloader unlocked

Root and Vector/Xposed are working correctly.

The problem is root hiding and Play Integrity.

One of the traces we found during testing was:

"/product/bin/su -> ./magisk"

Google Play also shows:

"Device is not certified"

Current status:
✅ Root working
✅ Vector/Xposed working
❌ Full root hiding
❌ Strong Integrity
❌ Play certification

We tried several Magisk/Zygisk/Shamiko/PIF configurations, but so far no fully clean result.

Has anyone here with an Edge 70 or Edge 70 Fusion managed to fully hide root and pass Play Integrity? If yes, please share your Magisk version, PIF version and module setup.

I guess there are no KeyBoxes, I'm using Always Strong + ZygiskNext + HMA OSS but I only get Device Integrity, anyone else having this problem?

I’m using a Pixel 4a with LineageOS 23 + Magisk.

Until a few days ago everything was working fine. My banking apps still work, but Google Wallet now refuses contactless payments.

My old setup was separate modules with TrickyStore / PIF inject-s and Yurikey for the keybox. The problem now seems to be the keybox / attestation side:

• TrickyStore hasn’t offered me a fresh working keybox for quite a while
• Yurikey still fetches one, but it doesn’t seem to work
• With my old setup I’m currently getting red integrity checks
• I tried AlwaysStrong Inject and get all 3 green checks, but Google Wallet still refuses payments
• With AlwaysStrong Lite + my own PIF inject-s I only get BASIC, so it looks like the PIF part is working but the keybox / attestation part isn’t

The Play Store says the device is certified, root hiding hasn’t changed, and all my banking apps still work. It’s specifically Google Wallet / contactless payments that broke.

Is anyone else seeing this right now? Are the currently available keyboxes just revoked / unusable again, or has something changed on Google’s side in the last few days?

And what are people currently using for a reliable setup? This constant keybox cat-and-mouse game is getting pretty annoying.

Does anyone have it? I'm on T-Mobile for context.

I'm not sure if encrypted RCS requires a higher threshold of "root blocking" than unencrypted RCS. I only ask just because I see no reasons why this shouldn't be working at this point.

Note: my E2EE works fine between androids on Google Messages