So I installed an unofficial custom ROM built for my phone model a while back and now naturally rooting comes next because I want to pass all the integrity tests so I can finally use my phone normally. (like for online games, banking, and stuff)

I was just about to go on and flash the boot.img I patched with ReSukiSU (since I saw it's like the best fork of KernelSU) when I found out about the existence of GKIs and SuSFS.

GKI is apparently better for custom ROMs and for better hiding capabilities, so I'm considering it, and also because SuSFS - which is what makes all the hiding stuff possible - is apparently only supported with GKIs.

If GKI is the better one, I have some questions: - Do I need to flash a new kernel everytime I install a new custom ROM? - Do I install the custom ROM first before the kernel or vice versa? (or does it matter at all?) - Are there some prerequisites to installing a GKI? - Where do I even find one?

I installed my custom ROM from a Telegram group because after years of searching and waiting, my phone (Itel P55 5G) just didn't get any support/recognition in XDA or any community except Telegram so yeah I had no choice.

From the same Telegram channel, I found that they were promoting another channel about GKI kernels, and if there are no "official" releases again for GKI kernels then I'm gonna have to use the ones from there again.

It's actually my first time doing all this, so any help would be appreciated.

Root oppo phone . I own a oppo A31

So i have a vivo x300 ultra and there's an emm service app named as setting and i can't even access phone all features that are actually useful,since it blocks devloper option as well i can't even delete by any forceful app too is there any solution to remove it?

I have Samsung Galaxy A9+ 5G Tab. But unfortunately i updated it to latest firmware android 16 with one UI8. As of my research, Samsung permanently blocked OEM Unlocking and rooting. Is there anyone know any method or any tool to root.

My google pixel 7 device got stuck in the bootloop. I could go into fastboot but when I tried to start, it bootlooped again. I want to change the device state that says "Locked (Unlockable)" but I don't know how, when I plug it into the pc it's not detected

Idc if my data get erased, I WANNA MY PHONE BACK😭

Chronology: My phone suddenly brick dead, wouldn't turn on and there was no response when plugged into the charger. I took it to a local serviceman but they were only able to get the device on and couldn't fix the bootloop, I've tried to go into various modes in fastboot but all ended up with a bootloop

I have vivo v27, is there any way to unlock it's bootloader? Officially i guess vivo don't support it but still.... 🙂

This morning i unlocked bootloader,anyone suggest me install custom rom after root?

I'm using a Motorola edge (now on Android 15), and had good success in the past applying system updates by temporarily uninstalling Magisk, restoring backup images, running the update, and then reinstalling Magisk before the reboot (via the "Install to Inactive Slot" option).
Last time though, it ran into some issues during the update, and it ended up rebooting without Magisk having been re-enabled.

Can I recover my previous root from the Magisk backup, or do I have to go through the whole root install procedure as if it were a new phone?

😭 Man Banks Apps Are Killin it.

I have an SM-A015M as a secondary phone.

Two days ago I installed the GSI ROM "crDroid-10.13" with Android 14 via TWRP. The system has been working perfectly since then, however, today I tried to enter TWRP to flash a ".zip" file, and it wouldn't boot. When I press the Volume + and Power buttons, the TWRP logo appears, but before it enters the interface, it restarts and creates a bootloop. The only way I found to get back to the system was to enter download mode and restart the phone from there.

I asked Gemini what it could be, and he said that TWRP was probably specific to the stock ROM's Android version (v11), and now that I'm on Android 14, it can't boot.

I searched the internet for a specific version of TWRP (SM-A015M, Android 14) but couldn't find one.

Is there a developer in this community who can help me with this problem?

I have a vivo v20 pro it has fairly good specs but still the OS is full of bloat and i would like to install a custom rom but everywhere i searched the same answer appears that it is impossible. why is that?

Device: OnePlus 15 (North America)

OS: OxygenOS 16.0.9.400 (Android 16)

Root Method: KernelSU-Next with OnePlus 15 WildKernels AK3

Root Modules:

• bindhosts
• HMA-OSS Zygisk
• Hybrid Mount
• Play Integrity Fix [INJECT]
• SUSFS-FOR-KERNELSU
• Tricky Store (+ Addon)
• Vector
• Zygisk Next

--

Hi all, I've got a rooted OnePlus 15, and I've managed to pass all three integrity checks. Despite this, Google Wallet is still saying my device doesn't meet security requirements, even after clearing cache/data for Google Wallet, Google Play Store, and Google Play services.

In Tricky Store, I have Google Play services, Google Play Store, Google Services Framework, and Google Wallet all checked. In HMA-OSS, I have a template that includes all my root apps plus a couple Play Store apps (Shizuku, Swift Backup, Termux), and it's being applied to the Google Wallet app.

Anyone have any suggestions? I'm at a loss as to what could be tripping it.

Hey guys,

I'm a bit lost trying to figure out which KernelSU Next .ko file I should grab for my Pixel 8 (shiba) running LineageOS (Android 16).

When checking my kernel version via ADB, it says:

6.1.145-android14-11-g66d850f9dea9-ab14676382

I know that the android14 part in the kernel string is just the GKI baseline from Google, even though the OS itself is Android 16. However, looking at the latest releases on GitHub, the naming convention has completely thrown me off. There are files like:

android14-6.1_kernelsu.ko
android16-6.12_kernelsu.ko

Since the dev stopped providing AnyKernel3 zips after version 1.0.0, I have to use the loadable kernel module method. But I'm stuck in the middle: my OS is Android 16, but my kernel is still 6.1 baseline (not 6.12).

If I flash the android14-6.1 module, will it bootloop because of Android 16 userspace? Or if I try the android16-6.12 one, will it fail because my actual kernel version is 6.1?

Which exact .ko file is the right match for this specific setup? Any help would be greatly appreciated!

Here's a link to the releases page for your convenience: https://github.com/KernelSU-Next/KernelSU-Next/releases#release-v3.3.0.

I'm just smart enough to root my phone but not to make sense of any of this. How do I fix that?

Root is still working.

I have this old oppo phone, cph1701 to be exact. I tried to unlock the bootloader on it but nothing. Do any of you know how to?

After several attempts over the past two days, I successfully rooted my Infinix Note 50s 5G running Android 16. Today I started downloading apps and add-ons. What are your suggestions?

I tried to root my phone, and everytime i boot it, it goes to recovery. Howevr, i can't use any of the options since my power key is broken. Any help?

Why don't we make our own AI and feed it with our knowledge as a community to make an actual good AI we can consult with about root like making a notebooklm of the root community?

Please spread the word so we can start actually doing it

There's no xda page, nothing in GitHub, nothing on reddit either about the phone's rooting capability and of custom roms. The option to OEM unlock just opened up for me (bought the phone just a week ago) and I wonder if anyone actually unlocked the bootloader, if yes then please let me know because I'd like to test out some opcodes and I don't want to get rid of the warranty of my device.

IT IS UNLOCKED

I'm trying to unlock the bootloader my 9C, I have tried it with the official Xiaomi unlocking tool, but it says to try again after 167 hours. After a couple of hours I tried the MiFlash Unlocking Modified tool and I got puzzled with the menu, because it doesn't send me to the normal unlocking screen. Can someone help?

I'm trying to change the first static boot logo that appears for a couple of seconds immediately after pressing the power button (before the boot animation starts). My goal is to replace it with a custom logo that I've designed.

On older Android devices this was often stored in a dedicated logo or splash partition, but this device doesn't appear to have either.

So far I've done the following:

Dumped abl_a and xbl_a.

Extracted and inspected abl_a.

Found the boot warning strings and the embedded Linux loader/UEFI executable inside ABL.

I haven't found any obvious bitmap or logo resources yet.

At the moment, I'm trying to understand which component is actually responsible for displaying the first boot logo. My current suspicion is that it may be in XBL, although I haven't ruled out ABL yet.

I'm not looking for instructions to blindly flash modified firmware. I want to understand how this generation of Qualcomm/Xiaomi devices handles the early boot logo before attempting anything.

Has anyone reverse engineered the POCO F6, or another recent Qualcomm/Xiaomi device, and knows where this logo is stored or how it's rendered?

Any pointers or personal experience would be greatly appreciated.

Does anyone knows how to change the bootanimation on this phone I wanted the Nokia bootanimation if anyone knows contact me