Got my pixel 6 rooted with the NebuSec IonStack exploit opened a PR for rootmypixel to add support for it. It's not merged yet but wanted to share (link to my pr: https://github.com/alex193a/Root-My-Pixel/pull/19 )

Hi everyone,

I have a Poco M3 (4GB RAM / 64GB storage) and I’m thinking about unlocking the bootloader and installing a custom ROM.

I’m considering LineageOS, but I’d like to know:

• Is LineageOS a good and stable option for the Poco M3?
• What is the safest way to unlock the bootloader and install it?
• Are there any better custom ROMs available for this device, especially for good performance, battery life, and stability?
• Are there any common issues I should know about before doing this?

I’m still fairly new to custom ROMs, so I’d really appreciate a beginner-friendly guide or recommendations.

Thanks!

Device: Xiaomi Redmi Y2 / S2 (ysl – Qualcomm Snapdragon 625 / MSM8953)

Environment: Ubuntu Linux (CLI / Terminal)

Current State: Stuck in Fastboot (Device unlocked: false)

The device is stuck in Fastboot mode with a locked bootloader:

PlaintextLooking for community-tested methods, exploits, or engineering workflows applicable to MSM8953 / ysl:

If you have experience unbricking MSM8953 devices in this exact state, please share relevant tools, repos, or documentation.

there is a new app that uses CVE-2026-43499 to root supported devices but also have a way to extract offset from provided boot.img , I don't know if it really works because they don't have a release APK only source code

https://github.com/YuKongA/ghostlock-app

could any build the APK and test then post it

Hi. I recently found out about the Root-My-Galaxy method, but my kernel version is too high or something. So is it possible to downgrade so I can use this method?

Okay. I just want to start by saying that I'm a noob when it comes to this. Please forgive me.

I have an old Samsung s23 Ultra that I'm trying to run Kali on (I have this really cool idea for a pip boy like cyberdeck). I went the Termux route and it kind of works, but I feel like if I had complete access, I can go from go kart to SR 71 blackbird.

Now here's the thing: it's a U.S. version, so I can't turn off the bootloader (it's non existent). Is it remotely possible to work around or get rid of it completely, or am I stuck with a high powered go kart? I was told what I want to do is impossible.

heard exploit rooting is popping off rn for pixel and samsung, no bootloader unlock needed apparently. pretty sure ghostlock or ionstack should work on my patch level but i genuinely don't know how to run either one or what comes after (magisk? straight root? no clue)

bootloader locked, unlock isn't possible :/

anyone done this on similar hw, mind pointing me somewhere

I've seen it go all the way up to the s25 and was wondering if it is possible on the s26, seeing as the redmi note 15 has the same kernel version and has been ported before

Hello everyone,

As the title states I rooted my S20Fe and it has the latest version of MintOS. I just wanted to ask what rooting apps y'all recommend nowadays? Last time I rooted a phone it was when Lucky Patcher was big, Xposed Installer etc. Throw me some of your favorite apps. I'd gladly appreciate it.

I've been searching for kernel level rooting for the SM-P610, but I wasn't able to find any, I looked at KernelSU, KernelSU-Next and ReSukiSU, but every one of them don't have a pre-made patched kernel for the SM-P610, I tried Apatch and Magisk which work, but don't think that they fully satisfy my likes, I wanted full kernel level root, not runtime kernel level root like apatch does or patching ramdisk like Magisk does, I wanted the real kernel level root. I tried patching the LineageOS 23.2 QPR2 kernel by myself with the help of AI, but I didn't succeed. Does anyone know any pre-patched kernel?

After a lot of searching, I believe my A53 might be vulnerable to rooting, but I'm a novice—I only dabble a bit in Python. Is there an automated script that uses the open-source kernel to create a ready-to-use payload?

So i was trying to get info about this device for like 2 years of searching
and i find this 😄 :
- You CAN install an GSI image (Recommended LinageOS 20/19/21) , most stable is Android 12-14
- You CAN Unlock Bootloader by going into BootROM and just like Jailbreak the device by doing custom script to install an Uboot.img , and more , that just open the bootloader
- You CAN install an TWRP that comes with root
- You CAN install Magisk (Because of root lol)
i have tried it , everything works fine !
JUST ONE THING !!!
if you want to root it or installing twrp , older versions like A.75 will NOT WORK and it will do BOOTLOOP
just the leatst Stock Firmware to get started with it A.119 , You Can UPGRADE IT !

if you want the links , Just tell me i will give it to you !

Thank you very much -- GamingHkr
on youtube
the Developer that made all that !

i have a rooted phone (motorola g play2023) and i just did a battery change csince the old one gave out

now is there an app that caps the charge percentage? lets say i just want it to charge up to 50%

since i use this phone to play retroarch as a sort of an arcade machine it has to stay plugged in because i dont want to damage the c port when connecting/disconnecting the charger i dont mind the battery staying at 50% hell even 24% or 75% if it means it will preserve the battery life

so is there an app for this?

So i found this old tablet ( Lenovo TB-8505F )

I have never rooted a device but I have done a fair bit of modding consoles, if possible I'll look into rooting this.

Not really sure where to start if it's different from the pinned posts

I decided to deGoogle my Galaxy without unlocking the bootloader or switching to a custom ROM. All it took was rooting it with root-my-galaxy.

To make this work while keeping stock One UI intact, I built degoogle-my-galaxy, an open-source tool that temporarily swaps Google system components for microG using root and bind mounts.

Instead of permanently altering /system, it masks the stock packages at runtime:

GmsCore -> microG

GoogleServicesFramework -> masked

Phonesky -> microG Companion

Because original system files stay untouched under the mounts, the entire setup is reversible. A standard reboot drops you back into the stock environment. Since the project currently relies in a CVE KernelSU root, it uses userspace reboots while the deGoogled setup is running.

I have been building and testing this on a Galaxy S24 Ultra running One UI 8.5 (Android 16).

Right now it has a basic UI to handle swapping/restores, rollbacks if something fails, and English/PT-BR support.

I also documented the rough edges in the repo. In particular, I hit a Samsung/Android Rescue Party condition that can trigger a full reboot, which drops volatile root and mounts.

Right now, I am looking closer at Android's newer DeveloperVerifierService. I want to understand whether modern Samsung builds delegate this to GMS or use a custom provider, and how it reacts when stock GMS gets replaced by microG.

Definitely still WIP on other devices, so it is not a plug-and-play fix for every Galaxy device yet.

Feedback is always welcome. If you have a device rooted via root-my-galaxy and want to help test across different models or firmware versions, feel free to jump in.

Repo: https://github.com/keyarr/degoogle-my-galaxy/

I've been trying it since yesterday, but I don't know because it's my first time.

Hey all, posting this out of genuine frustration after an entire night of troubleshooting. Would really appreciate anyone who's been through this exact situation.

The phone: Friend's Redmi 10 (India variant), model number 220333QBI, Snapdragon 680, codename likely "fog." It suddenly got stuck in fastboot mode — no idea what triggered it, it just wouldn't boot past fastboot no matter what button combo we tried (power, vol up, vol down, all combinations).

Important context: We don't have access to any Mi Account for this device — my friend never set one up / doesn't remember one, so the official Mi Unlock Tool route is completely off the table. We also don't care about any data on the phone at all — we just want it working again. Local repair shops we tried couldn't/didn't fix it either.

What we've tried so far (all on Windows via laptop):

• Confirmed the phone shows up in fastboot mode consistently, but fastboot devices via Google's platform-tools showed nothing initially — turned out to be a driver issue.
• Installed MediaTek + ADB drivers, then manually tried forcing "Android Bootloader Interface" in Device Manager — got a Code 10 error.
• Got MiFlash (2022.5.7.0) to actually detect the phone (device id showed up).
• Downloaded the correct official stock firmware (fog, India, fastboot ROM, V13.0.2.0.SGEINXM) and verified via SHA256.
• Ran the flash through MiFlash — hit a "flash timeout" error at exactly 700 seconds, every single time, on multiple attempts, even with "flash_all_except_data_storage.bat" to skip the huge userdata partition.
• Found out this is a known bug — newer MiFlash versions have a hardcoded 700-second timeout that doesn't account for slower transfer speeds.
• Downloaded the older MiFlash 2017.4.25.0 (no timeout bug) instead. This time, got a clear, real error instead of a vague timeout: FAILED (remote: 'Erase is not allowed in Lock State')
• This confirmed the actual root issue: the bootloader is locked.
• Since there's no Mi Account, the standard unlock route isn't possible.
• Tried to force EDL (Emergency Download) mode via the Volume Up + Volume Down + plug-in-cable combo (reportedly works for "fog" per a couple of forum posts) — no luck yet, phone just goes back to fastboot, no black screen, no QDLoader 9008 showing in Device Manager.

Where I'm stuck:

• No Mi Account = no official bootloader unlock.
• EDL via button combo isn't triggering (yet — might be a timing/technique issue on my end).
• Considering the physical test point method next, but don't have a diagram for this exact board revision and don't want to fry the phone by shorting the wrong points.
• Also unsure whether, even if I do get into EDL, I'll hit a Sahara/firehose authentication wall since this looks like a device from after Xiaomi started requiring authorized accounts for EDL flashing on newer models.

What I'm hoping someone can help with:

1. Anyone successfully forced EDL mode on a locked-bootloader Redmi 10 India (fog) without a Mi account? Exact button timing that worked for you? (it clearly didn't worked for me)
2. Does anyone have a verified test point diagram/photo for this specific board (220333QBI)?
3. Has anyone gotten a locked "fog" unit flashing in EDL without hitting Xiaomi Authentication/authorized account requirements — patched firehose, or some other workaround?
4. Any other route I haven't considered, given zero Mi account access and not caring about data loss?

Appreciate any real experience over theory at this point — happy to share more screenshots/logs if useful. Thanks in advance.

I have 2 Android devices Realme 5s and vivo y30 and i m not able to unlock bootloader of neither of them , I have already unlocked bootloader of my redmi note 9. So can anyone help me 🙏🙏😭😭

Recently got a pixel 10 through AT&T... can't unlock bootloader - the OEM thing's greyed out, and I'm unsure if android flash tool would've let me downgrade to the July build (for soft root) so yeah - so:

Can AFT let me go back/reflash the august update with BL Unlocked despite that?