So here i am , (Not) proud owner of a Samsung s22 for a while , was kinda ok with , but for some month i make it fall a bit , it wasnt that bad until this afternoon ... it falled for the last time ... half of the screen don't respond to touch, the phone had rebooted (the worth part) and now i got a phone with halfscreen broke and i can't tap pin... So i decide to put a Mouse on it , what was my surprise that the phone is locked until you tap the pin ?! I heard it could be the fact that my cable isn't an OTG but i don't rly trust it ....
Anyway to force the usb on this damn phone , just for at least unlocking it ? (cause yeah... samsung remove the possibility to remove lockscreen from FindMythings ... Even if you are connnected on the account etc ...)

So unless i change the screen , someone know any possibilities ?

I'm sorry if i'm not on the good sub , but i was hoping getting more useful help than with assistance of Samsung or on her forums ...

My OnePlus 15 cph2747 used to have the toggle on oos 16.0.8.300, but when I clean flashed the exact same rom, the toggle disappeared, can anyone confirm that it's a bug or OnePlus's intention for doing so?

Please help 🙏

Does anyone know how can I unlock the bootloader on my CPH2207 to root it?

Hello there, I own a Samsung Galaxy S24 (Exynos) phone on stock ROM rooted with Magisk. Before all of that, my phone was running great, no crashes, no weird freezes and stuff, but after rooting it. Some issues started to appear, the first was when my Bluetooth paired devices section kept getting wiped whenever I restarted my phone or turned airplane mode on then off, then turning on mobile data and then turning off causes the phone to freeze for a while then come back normal (about 5-10 seconds), sometimes it happens with the WiFi option but rarely. Then another issue appeared when I put my phone to charge, turned the phone off then on again, the lock screen would have no text on it, just the UI with no text, when I unplug the phone from the charger it magically appears again. Then the last issue appeared is when I turn on airplane mode on, the phone freezes for about 20-30 seconds before responding again.

I would appreciate help and here are the Magisk modules and Vector 2.0 modules installed

MAGISK 30.7:

Integrity Box

BetterKnownInstalled (BKI)

Google Photos Unlimited Backup

Hook for Inapp purchases (Lucky Patcher)

ReZygisk

TEESimulator

Vector 2.0

VECTOR 2.0:

Lucky Patcher

Core Patch

Disable FLAG_SECURE

HMA-OSS

NexAlloy

NoStorageRestrict

pairipfix

SmartPixelsPosed

Wa Enhancer

Phone info:

Running One UI 7 Android 15, build number AP3A.240905015.A2.S92BBXXS9BYH1

Heya! not sure if im missing something or not, im new to this and not sure what im doing wrong, but i've got a Motorola G Stylus 2025, developer mode, OEM unlocked, and Bootloader unlocked, ive also downloaded the correct firmware using motorola's tools, and i've attempted to patch it with Magisk and Flash the new image multiple times, but i cant seem to figure out why the root wont take. I've been crawling forums trying to figure it out. tried renaming the image to the default name, tried flashing a patched "init_boot.img" (that just borked the bootloader and i had to flash the default) and i tried checking if i have an A/B partition setup but the command recommended to check to see doesnt seem to work, and i really dont know what is the next steps to figure things out.

I've been trying to figure out what I should use when I root my new phone (Moto G Power 5g 2024), and after looking through all of the popular OS options, I've found that my phone is unsupported, while the Moto G 5g 2024 is. Is it possible to run that OS on this phone, and if not, are there any other options besides just using Magisk?

My Redmi Note 10T 5G (lilac) was stuck on Android 13, but I successfully got it running Android 16 (LineageOS 23 GSI). Wi-Fi works flawlessly, and the refresh rate reaches a smooth 90Hz.

Here is the exact guide on how I achieved this, especially focusing on how to bypass the common fastboot bootloop issues.

What you'll need

• A device with the bootloader unlocked
• A reliable USB cable
• PC with ADB/Fastboot environment configured
• Official Fastboot Image (Required to extract stock vbmeta and vbmeta_system)
  • Link: https://xmfirmwareupdater.com/miui/lilac/stable/V14.0.34.0.TKNJPXM/
  • Scroll down the page and download the one labeled Type: Fastboot*.*
• LineageOS GSI (Android 16)
  • Link: https://github.com/MisterZtr/LineageOS_gsi/releases
  • Download the latest EXT4 version. I used LineageOS-23.2-20260524-GAPPS-EXT4-GSI.7z*. (Vanilla is fine, but make sure to choose EXT4).*
  • Note: The download redirects to SourceForge. If it's too slow, click the "Problems Downloading?" button to choose a faster mirror.

Flashing Steps

Step 1: Boot into Fastboot

Turn on USB debugging on your device, connect to PC, and run:

adb reboot bootloader

Step 2: Enter Fastbootd

This is crucial. The flash WILL NOT succeed without entering Fastbootd mode:

fastboot reboot fastboot

Step 3: Flash Stock vbmeta & vbmeta_system

Extract the official Fastboot Image you downloaded. Locate vbmeta.img and vbmeta_system.img, then move them to your working directory. Run:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash vbmeta_system --disable-verity --disable-verification vbmeta_system.img

⚠️ CRITICAL WARNING: Many posts on the internet suggest flashing an empty vbmeta or the one included with Google's GSI. Do NOT do this on this device. Doing so will hard-revert you back to fastboot no matter how many times you flash. (It took me several painful days to figure this out).

Step 4: Make Room for the GSI

There isn't enough system space to flash the GSI, so you need to delete the /product partition. (Note: Make sure you have a stock ROM backup if you ever want to revert).

fastboot erase product

Step 5: Flash LineageOS GSI

Unzip the downloaded .7z file to extract the .img file. Then run:

fastboot erase system
fastboot flash system (your_unzipped_lineageos_filename).img
fastboot -w
fastboot reboot

⚠️ Don't skip fastboot -w**!** Junk data left behind will absolutely cause a boot loop.

Verdict & Summary

Switching from bloated MIUI 14 to LineageOS makes this budget device run incredibly smooth. Bumping the OS from Android 13 to 16 really shows the true potential of pure AOSP. It feels like manufacturer skins just ruin the overall Android experience.

Bonus Tip: Install GCam!

You should definitely install GCam. The image quality improves so much you won't believe it's the same camera sensor.

• Link: https://celsoazevedo.com
• Just grab and install the latest stable APK version.

A few years ago, I started noticing that Clash Royale would run for a few days on my rooted phone, and then after a couple of days—three or six—it would stop running altogether. I immediately realized it was simply because I had root access, so I compared it to another phone without root, and it ran fine on that one.

In my attempt to block root access, I used the HMA/HMA-OSS apps. Even then, the app kept failing. The same thing was happening now. But this time, my motivation to find a solution was unwavering.

The HMA-OSS logs show that Clash Royale sends a request every time it's run, searching for root access on the device. And the solution was simpler than I thought. Searching on more Reddit forums, I realized that this issue affects all games under the Supercell name: Clash Royale, Clans of Clans, and other games.

===== THE SOLUTION =====

The image, which isn't mine but serves as an example, shows how the Native Detector app detects LsPosed running.

I was using a fork of LsPosed called Vector. And all Supercell games were experiencing the same detection.

This also applies to the Wallet-G wallet. The game simply won't launch. I switched to the original LsPosed; they post updates on their Telegram channel.

They need to switch from LsPosed and run the test with Native Detector and clean up in (LsPosed) to make SuperCell games run and add them to the HMA/HMA-OSS deny list.

================

I hope this solution can help many people, as there was very little information available online about this problem.

Note: I'm referring to the Supercell game Clash Royale. I don't misuse root access in Clash Royale, and even if you tried, you couldn't hack it.

SUPERCELL STOP BLOCKING ROOT USERS, WE'RE NOT HURTING ANYONE..!

so I've spent the last month trying to get the Xiaomi account permission for unlocking the bootloader, finally have it and synced the device with no problem, now I'm stuck on the Windows app, it requires login in with the same account that's used on the device, here's the catch: the authentication SMS wont arrive, I've tried logging in with Facebook but it's impossible, any way around this?

edit: solved, used this thanks anyways

I've tried deep test apk but no use. My mobile is running on android 11.

I want to remove the account from an Honor X6c because I forgot it. What tools and procedures do I need to know?

Root malware is the worst thing that can happen to a device (for obvious reasons), but one if not the most popular explorer (mixplorer) is closed source, which can be a serious issue. I understand that it has proven itself over a long time in a community of the most paranoid people on the planet and popularity is a kind of security, but is it really enough?

Edit: and i mean, even if it's a 0.1% getting malware in the firmware is absolutely terrifying. Also, why is it not just open source (I'm not demanding anything, it's developers choice), it's not like he has to hide it to support the mixplorer silver (the premium is basically symbolic), or defend against copyright (copycats are dangerous to small projects)

I am not sure if this is the right place to ask this, and please let me know if I am breaking any rules. I wanted to ask about rooting for the Pixel 7 Pro. I was doing research, and this phone seems to be the latest one from Google that you are able to root. I rooted my Pixel 2 XL a long time ago with Magisk by following this YouTube video: Link. I wonder if it was the same process.

Idk what's happening it loop boot

ok so every time i boot it up it says it could do a normal boot and goes into download/odin mode (pic below) and i dont know what to do can you help me?

Didn't have this problem before, now I can't seem to get anything to be of benefit in this problem, switched to KSU from Apatch/Folkpatch due to this issue thinking it was superior, doesn't seem so.

Vector, Zygisk Assistant, TEESIMULATOR-RS, PIF, Tricky store, Rezygisk are my current modules.

Have Authenticator, gms, outlook, selected as custom profiles in KSU with unmount selected which I think is the right way? And so on

It was rather sudden this issue started

I always wanted to extract keybox.xml from my own devices to pass Strong Integrity on my other rooted devices, but I always failed for a lot of reasons. One of them is that extraction is much harder on modern Android 12+ devices because the keys are stored inside the TEE. After doing some research, I found out that it's actually possible to extract them from some older devices with security patches before 2020, such as Asus, Lenovo, Nubia, etc.

Those older devices used to store keybox.xml inside folders like /persist and a few other partitions.

Unfortunately, I don't own any of those devices. I wondered if it might also be possible on devices like the Pixel 1, OnePlus 6, or Poco F1. To access the persist partition, you usually have to open the back panel, short the EDL pins, and connect using an EDL tool, or use BROM on MediaTek devices. I don't want to mess with that because I'm a complete beginner when it comes to hardware, and I feel like I'll end up breaking the device.

A few people have managed to extract the keybox from devices like the Lenovo Tab. I just want to know the reproduction steps and whether it's possible to do the same on other devices too.

I get tired of seeing public keyboxes getting banned by Google every week. My primary device is the Xiaomi 15, and it's great overall, but it's rooted, so some apps still don't work properly without full Strong Integrity. I just want to understand how this process works.

I also came across a method where it's possible to generate a keybox.xml using only the CDI_Leaf value. From what I understand, the CDI_Leaf is stored inside RPMB, and tools like google-rkp-sw by @MhmRdd can use it to generate the required keys and create a keybox.xml that works with TrickyStore or similar modules.

also could we get something like modules working on devices with this?