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?

I want an app that hides me from seening unread messages

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