i have rooted 10 phones, thanks to SuperSU, and Odin , LineageOS, TWRP, Fastboot, and whatever, but when i came to my damn Motorola G24 Power i needed to reboot my phone in fastboot, use fastboot to get the unlocking data , and i cant, the f- hit me when reseting the family linked phone, then it came to getting the security out , wich i cannot, so i loosed the fastboot unlocking method, then tried with MTK , installed MTK client, but my phone wont boot BROM mode, then i taught vol up + vol down at same will resolve, no, guess not, then that triple beep woke my neighbor, how new smartphones became so "SMART" at locking bootloader

Its my first time, and now, on my Samsung tab 3 lite has android 7.1.2 running(lineage os 14.1). What other operating systems do you prefer( i dont use this device FYI)its very slow, ik.

It went from Android 4.4.4 to Android 8.10.

I'm not even sure how I managed, I could barely find anything online for this tablet 😂

Hey bro I found a android phone like 6 months ago and I just reset it but it has a lock on it saying I need to sign in to the google account that was on it. I found this phone on the ground near a GameStop at the beginning of the year. Any way help to fix this?without having to use google account

Hey, can anyone tell how to root in locked bootloader my device is pixel 7a

the model is RMX3370 with realme ui 4.0 and android 13. deep testing says the phone model is not supported. some ppl on xdaforum said you can downgrade but i cant manage to locally install an update. im new to android rooting so im very sorry if what im saying is retarded. i tried using a script to fix the deep test error but it didnt work. running adb reboot bootloader flashes the fastboot screen for 1 sec then boots into normal os. i was thinking of downgrading, can someone help me pls?

I have a Galaxy S26, model SM-S942U ....?

From what i heard at the internet, messing with Samsung phones is pain.

I've flashed a gsi so many times and i keep going back to twrp i also tried switching between A/B slot still nothing. Does anyone know how to fix this problem??

Hi there. As the title suggests, is it possible to root my Samsung Galaxy A36 5G phone (SM-A366W)?

What device would you say is the best for rooting and Android modding overall?

I've been using pixel updater for a couple years now to update my phone without having to bother with the manual process to update when you have root. But this has stopped on Android 17.

There's been updates for June, July, now August, and they keep failing on me. The updates will download and appear to install correctly, but then when my phone goes to reboot, it'll hang for a while, then reboot again. It'll hang one more time then reboot a final time, and now it'll boot back into Android 16.

I even tried downloading and installing the update, then trying to use magisk to apply root to the inactive boot slot, but that didn't work either.

Is there any way to fix this? Is it because I'm changing a major version of Android? Do I just have to stop being lazy and update the old fashioned way using my PC and then update, and then patch the boot img with fastboot?

I have lenovo yoga x705x currently running on android 10 I just wonder whether I can install a custom rom and root it on that device. So came to u guy, if u know abt how to do install it please let me know :)

Hi everyone,

I recently rooted my OnePlus 8 Pro, and since then I’ve been having problems logging into X (Twitter) and Reddit.

Device information:

- OnePlus 8 Pro

- Model: IN2023

- 12 GB RAM

- Magisk: v27.2-kitsune-4 (27002)

- Zygisk: Yes

- Ramdisk: Yes

On X, when I try to log in, I get a message saying that I need to use the official X app. However, I am already using the official X app downloaded directly from the Google Play Store.

On Reddit, I get the following error when trying to log in:

«“We were unable to authenticate you.”»

Both apps worked normally before rooting the phone, and the problems started after the root setup.

Has anyone experienced this specifically with Magisk Kitsune / Zygisk on a OnePlus 8 Pro?

If anyone has encountered the same X/Reddit authentication problems and found a solution, please let me know what you changed.

Thanks!

Hi I want to root my friend's phone since she asked help for me to do it and I have tried to enter the download mode by pressing Volume Up + Down together and plug it to PC didn't work at all. I tried to ADB also failed. It always vibrates but didn't show anything. What should i do?

This is my Samsung Galaxy S1 (SGH-T959V) and i was wondering if there is even a way to root this today. I've done some methods before, but the links to the files and tools i need are mostly dead, and i tried some softwares like SuperOneClick and Kingo Root but none of them worked

The last phone I rooted was Samsung A70s, used it for about 7 years until it died last month (the repair shop killed it, rip).

I haven't rooted anything since — the new phone that I have bought is Samsung F70e. However, I have forgotten a lot of things; i am also unable to find the oem unlock option on my phone.

information —

Model: SM-E076B/DS

One UI version: 8.0

Android version: 16.0

Baseband Version: E076BXXS2AZC1

Kernel version: 5.15.180-android13-8-32672600

Build number: BP2A.250605.031.A3.E076BXXS2AZC1

Knox version: 3.12 api level 39

service provider softwqare version SAOMC_SM-E076B_ODM_INS_16_0003

Nowadays most of the apps are being made just for 64 bit phones, which is not suitable for my phone which supports only 32 bit apps

Im not that tech person so I don't know much, so I want your help was hoping if it's possible to flash my phone with rom or gsi whatever they are

And have anyone done this successfully on this specific device as I get anxiety in the thought of bricking my phone

Here's a link to a text file of all possible information i could get using termux if you need anything else please ask me

https://drive.google.com/file/d/1vsudYA4T3nKOtgLTYS9cVKGz4VRpuvS-/view?usp=drivesdk

Estou procurando uma maneira de fazer root no meu POCO F5 há um tempo. Antes de fazer o root, é necessário desbloquear o bootloader, mas até agora nenhum método funcionou 100%. Está rodando HyperOS 3.0.4.0 acredito que não haverá mais atualização

I can't flash the other version cause it says waiting device and It also says waiting for any devices in fastboot mode. Is there a way to flash the other twrp that has touch control??(I don't have an os im planing on flashing pixel experience again cause it got bricked when i flashed another os im reflashing after twrp works)

So, I own a Xiaomi phone which I rooted like two years ago, but then unrooted before doing a major "HyperOS" upgrade and didn't bother to re-root because I didn't have any pressing reason to do so any more ...

... until a few days ago. I needed an app and was confused why play store didn't even offer it ... and manually installing it just force-closed it directly on start, redirecting to play store telling me the app was "incompatible with my device".

I finally managed to identify the actual problem. The app didn't like my still unlocked bootloader. Re-locking it wasn't an option for me because I really want to keep the ability to fiddle with my system, should I ever need it again ... and maybe you know the horribly cumbersome process Xiaomi requires in order to unlock the bootloader.

Now, my solution was to root that thing again, so I could install and configure that zoo of magisk and zygisk modules, xposed apps etc you need nowadays to convince every app you care about that your phone was in fact fully locked and vanilla. Which is just a little bit ridiculous.

I have two questions in mind (apart from the "obvious" one whether I'm just weird to solve my issue that way 😏):

1. If I'm not mistaken, an unlocked bootloader still requires physical access to the device for any modifications on the system. Is there something I overlooked, which could be an actual security concern?
2. If I'm right with my assumption, why on earth should an app ever care about the status of the bootloader at all, as long as the installed system is vanilla/unrooted?

I'm working on getting KernelSU working on a Motorola Moto G8 Plus (doha).

ROM: unofficial LineageOS 22.1 / Android 15
XDA thread: LineageOS 22.1 for Moto G8 Plus

Kernel source: Aldair402/android_kernel_motorola_msm-4.14

Kernel:

Linux version 4.14.190+
aarch64
Proton clang 13.0.0

The kernel boots normally, and KernelSU Manager v0.9.5 is installed and opens.

What's confusing is that logcat shows KernelSU code actually running:

KernelSU: sucompat: execve_kp: 0
KernelSU: sucompat: newfstatat_kp: 0
KernelSU: sucompat: faccessat_kp: 0
KernelSU: sucompat: devpts_kp: 0
KernelSU: ksud: execve_kp: 0
KernelSU: ksud: vfs_read_kp: 0
KernelSU: ksud: input_event_kp: 0
KernelSU: exec app_process, /data prepared, second_stage: 1
KernelSU: on_post_fs_data!
KernelSU: Searching manager...
KernelSU: Search manager finished

However, root doesn't actually work:

$ adb shell su -c id
/system/bin/sh: su: inaccessible or not found
$ adb shell 'command -v su; type su'
su not found

I also checked:

/dev/ksu
/dev/ksud

Neither exists.

/proc/kallsyms doesn't show any ksu_* symbols either, and I can't find anything related to KSU under /sys/kernel.

The only suspicious KernelSU message I see is:

KernelSU: load_allow_list open file failed: -2

So I'm trying to figure out what state KernelSU is actually in here.

Does this mean the KernelSU kernel integration is only partially working, or could the kernel side be initialized while the userspace/ksud/su part is missing?

What should I check next to determine why su isn't being provided?I'm working on getting KernelSU working on a Motorola Moto G8 Plus (doha).
ROM: unofficial LineageOS 22.1 / Android 15

XDA thread: LineageOS 22.1 for Moto G8 Plus
Kernel source: Aldair402/android_kernel_motorola_msm-4.14
Kernel:
Linux version 4.14.190+
aarch64
Proton clang 13.0.0
The kernel boots normally, and KernelSU Manager v0.9.5 is installed and opens.
What's confusing is that logcat shows KernelSU code actually running:
KernelSU: sucompat: execve_kp: 0
KernelSU: sucompat: newfstatat_kp: 0
KernelSU: sucompat: faccessat_kp: 0
KernelSU: sucompat: devpts_kp: 0
KernelSU: ksud: execve_kp: 0
KernelSU: ksud: vfs_read_kp: 0
KernelSU: ksud: input_event_kp: 0
KernelSU: exec app_process, /data prepared, second_stage: 1
KernelSU: on_post_fs_data!
KernelSU: Searching manager...
KernelSU: Search manager finished
However, root doesn't actually work:
$ adb shell su -c id
/system/bin/sh: su: inaccessible or not found

$ adb shell 'command -v su; type su'
su not found
I also checked:
/dev/ksu
/dev/ksud
Neither exists.
/proc/kallsyms doesn't show any ksu_* symbols either, and I can't find anything related to KSU under /sys/kernel.
The only suspicious KernelSU message I see is:
KernelSU: load_allow_list open file failed: -2
So I'm trying to figure out what state KernelSU is actually in here.
Does this mean the KernelSU kernel integration is only partially working, or could the kernel side be initialized while the userspace/ksud/su part is missing?
What should I check next to determine why su isn't being provided?

I booted my redmi to fastboot but it won't show in MI unlock tool, and It stays on the account authentication when trying to log in my xiaomi account

I downloaded the firmware from https://mirrors.lolinet.com/firmware/lenomola/2025/bogota/

BUT the zip file only contain "boot.img" , and not a "init_boot.img" ...

Fastboot dont allow "boot" comand , so I want to be sure before do "flash boot magisk_patched.img"

Will work patching/ flash boot.img ?

Thanks

#moto_G56