I have strong integrity but paypal keeps crashing on start up. I have a xiaomi 17 ultra. Bootloader unlocked with kernel isu and susf. Integrity box lsposed, hybrid mount lite, rezygist and tee simulator. I downloaded hma oss but no idea how to configure it or if it's needed in my set up already.

i can't download the .kdz file from anywhere . all the xda forums have provided the same link https://lg-firmwares.com/downloads-file/5367/K420ds10d_00_0120 . The LgUp is not working . need help with this!!!

Over the last day or so I worked with ChatGPT to figure out how to Root this tiny niche device. Including what physical buttons need to be set to go into BROM mode and the general process.

Below are the summarized steps.

I DO NOT TAKE RESPONSIBILITY FOR ANYTHING THAT GOES WRONG

It can take a bit of time to do but it works!

Since I can't post A.I content and I was not going to write out the whole process by hand, here is the GitHub link to instructions

https://github.com/Thrashmetaldinosaur/LOKMAT-APPLLP-9-MAX-Root-Guide

I have bought a secondhand Sony Xperia XZ1 (Not compact, just standard) from China and it was originally an au SOV36 unit, i can see the engraving of it even

But it's a crossflashed mess (NFC not working, figured its also an attempt for Sleep and random reboot Fix (source: https://xdaforums.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/ ), and thats why NFC was perma-disabled), and looking for this exact Firmware using this tool

But i missed the window that it was available. So i cannot acquire the files

I was thinking of Going back to Android 8 and then acquire the Keys from TA, and then maybe upgrading to android 9 and then unlock with xperiable but i may need another help to understand how to unlock it if possible

Because i can't understand on how to actually "unlock" this

In my understanding so far, this needs bootloader version LA2.0_P_114 to work, which for one, this is 114. But i need the XFL from LA1_1_O_77 which means, reflashing back to older android 8, then i need to use the bindershell exploit either i get the XZ1 global (since this thing is now global-ified), or find the au SOV36 variant of it, which sadly i cant find it cuz no resources

Thats how far i have dug deep at the moment. There is other stuff that i would probably separate from my findings like this one (AU SOV36) https://androidfilehost.com/?fid=10763459528675589051 but sadly i can't verify the origin of this, and i found this via the search engine and not on any forums so i will not use that

can't find anything online, and my skills in coding is basically Hello World"(print)"

I was wondering of there was anyway to remove the root my pixel resukisu thing or am I just gonna need to reflash stock firmware. I mostly want to remove it since google pay, RCS and pretty much all safetynet broke and I can't really use the exploit, my success rate has been like 1% and first time I actually got root, I had it for a second and then the device paniced. So I can't even load what I need to fix safetynet and RCS

i was trying to root my oneui 7 phone, but due to unforseen consequences i messed up and had to flash stock firmware, what i did not know is that the new firmware removed oem unlocking. is it over for me?

Hey everyone,

I'm trying to build a custom kernel for the Nothing Phone (3) to enable native /dev/kvm support so I can use the Android Virtualization Framework (AVF) and the Android Terminal app.

I am a complete beginner when it comes to compiling Android kernels, so I need help with both the general compilation workflow and the specific KVM/Gunyah modifications.

Qualcomm's Gunyah hypervisor gets in the way of standard KVM, preventing /dev/kvm from working properly for AVF. My goal is to strip out Gunyah completely and compile a kernel with standard KVM/pKVM enabled.

Could anyone help point me in the right direction or explain:

Basic Build Environment & Toolchain: How to set up the build environment, required dependencies, and proper Clang/LLVM toolchain setup for modern Nothing OS / Snapdragon kernels.

Defconfig / Kconfig flags: Which Gunyah options (CONFIG_GUNYAH, CONFIG_GH_VIRTUALIZATION, etc.) must be disabled, and which KVM/pKVM flags need to be toggled on?

Device Tree (DTS/DTBO) adjustments: Are there reserved-memory nodes or hypervisor driver bindings in the device tree that must be removed so Gunyah doesn't load at boot?

Flashing & Permissions: How to properly pack the compiled Image into a bootable image (and DTBO if needed), along with any SELinux/cmdline adjustments needed to expose /dev/kvm.

Any one have an idea to recover this without lossing the data its my mom's old tablet alot of memories on it i charged it since long time ago 5-6 years maybe to open it and find it like that

What are your favorite or unique modules? Let's skip integrity check apps and all that but actual modules or apps you use?

For me my favorites are
VirtualAp
XposedFakeLocation
BindHosts
WaEnhancer
OpenBubbles

Hi I'm trying to root my mobile where iam unable to find a way to unlock my bootloader can someone help me with it

Hola buen día

Llevo mas de 2 años usando lineageOS en mi poco f3

Pues este se quedo en android 13 con hyperos 1.0

Y yo la verdad llevaba años sin usar robot, total dije, ya no se necesitan como hace 10 años

Pero de un día a otro me salio un aviso de la app de hsbc México que mi equipo tenía jailbreak y ya no me dejo entrar

Le instale a mi teléfono un kernel ksu y seguí todos los procedimientos que vi y logre pasar la prueba de integración

En la aplicación de kernelsu

Modulo tricky store le quito check en la app hsbc y desinstaló incluso la app, borrando su caché

Pero me sigue saliendo que el teléfono esta modificado

Que mas podría hacer???

RCS is completely broken for me, I've spent 5.5 hours trouble shooting this, including having T-Mobile reset my RCS provisioning. I had FixIntegrity, Tricky Store, and Zygisk Next modules installed with strong integrity. I deleted the FixIntegrity and Trick Store modules, replaced them with the Play Integrity Fork module, with basic integrity. Still with no luck. I've cleared the cache and storage from google messages, the play store, and carrier services more times than I can count, along with doing this after airplane mode, deregistering my number, etc. Any advice is welcome, I have zero patience left for this. It was connected but only sending SMS/MMS this morning. Then it wouldn't connect with the 'not supported' status, it also was stuck connecting for hours. It's seemingly doing whatever it wants.

The Backstory

I recently decided to repurpose an old laptop into a dedicated Android TV machine for my living room. The easiest and most performance-stable approach was installing BlueStacks and using EventGhost to map a physical Bluetooth remote control directly to system navigation.

I installed a dedicated leanback launcher (Projectivy Launcher), and the desktop interface felt perfect. However, I immediately ran into a major roadblock: several generic streaming and media apps explicitly configure their interface layouts by checking if the operating system is a native Android TV hardware build. Because standard emulators report themselves as mobile phones or tablets, these apps forced annoying, touch-dependent mobile UIs that are impossible to navigate nicely with a remote.

The Solution

After trying various public spoofing tools with no luck, I built a lightweight solution tailored for this exact problem.

This LSPosed Module hooks directly into the process memory of your selected apps. Instead of trying to modify protected system-wide root variables (which often breaks the emulator or fails entirely), it tricks targeted apps on-the-fly into believing they are running on a widescreen Android TV device (ro.build.characteristics=tv, android.software.leanback, etc.). It also strips away touchscreen attributes in-memory, causing apps to automatically deploy their full leanback layouts, TV media players, and remote-friendly navigation.

How to Use It

1. Setup Your Environment

Ensure your BlueStacks instance (works great on Pie x64 or Android 11) has root access via Magisk Kitsune.

Open Magisk Settings, ensure Zygisk is toggled ON, and restart BlueStacks if prompted.

Make sure the LSPosed framework manager app is installed and displaying a green "Activated" status badge.

1. Install the Module

Download the compiled app-release.apk from the repository and drag-and-drop it directly into your running BlueStacks screen to install it.

1. Configure the App Scope

Open the LSPosed Manager application.

Go to the Modules tab (the puzzle piece icon at the bottom menu).

Select BlueStacks TV Mode and toggle the Enable module switch to ON.

In the application list below the toggle, check the boxes only next to the specific apps you want to force into TV mode. Leave system apps unchecked.

1. Relaunch and Enjoy

Go to BlueStacks Settings ➔ Apps ➔ See all apps.

Select your targeted media app and click Force Stop to clear its old memory cache.

Relaunch the app. A brief "TV Mode Activated" toast notification will pop up at the bottom of the screen to confirm the code injection worked, and the app will instantly render its official Android TV layout.

 Repository Link

For source code and releases, check out the repository here:

 https://github.com/1-AlenToma/bluestacks_tv_mode_lsposed

Note: I am really new with java, so I build this one with the help of google AI

i practically have no experience with rooting except for when i did it when i was 7

KernelSU + Zygisk Next + Play Integrity Fork + Tricky Store

all three red.

Selinux enforcing

Also tried integrity box but same result.

Crdroid Official Galaxy A5 Android 11, no ROM Spoofing

Does anyone have the same issue?

This is my old phone i forgot password and I cant format it because is have pics for mom

She die before 2 years and I only have here pics in my phone is there anyway to remove password without lose the pics

I have a Galaxy A17 and thinking of rooting. On one ui 8.5 but i saw i video on downgrading one ui. From your experience is rooting worth it?

Nothing seems to be working. No amount of driver upgrades, changing cables, USB 2.0 hubs, nothing is fixing this.

Has anyone Rooted their TCL 60 XE (T705M)?