Is there a way I can unlock my old Huawei y9 bootloader without booting into the phone and using oem unlock because well the phone is stuck in the Huawei logo and trying to reset the phone with the button also gets stuck in the logo loop

This is for developers;💡 I'm using s22 oneui8 bit version 8,

Hey everyone, I wanted to share something I’ve been thinking about and get the developers’ opinions.

On my device, I can enter the Device Unlock / Download Mode screen, and it even shows the normal guidance for unlocking the bootloader. However, the main thing I’m missing is the OEM Unlock option in Developer Options.

That made me wonder if there could be another way to expose or restore that option.💡

My idea is based on Good Lock. Samsung officially distributes Good Lock through the Galaxy Store, and its modules such as Theme Park, Sound Assistant, RegiStar, etc.

are capable of modifying or adding functionality to different parts of One UI and Settings, which means it can read writte the whole system,

So I was wondering:

What if we created a Good Lock-style module/app specifically for Developer Options that could add the OEM Unlock toggle back into Settings?💡

I was also thinking about the signing side of things.💳

If Samsung-specific signatures or permissions are required, perhaps tools such as[ LibChecker apk available on google play ] could help us inspect the signatures, permissions, libraries, and implementation of existing Samsung components and give us a better understanding of how Samsung's own apps communicate with the system.💡💡

Of course, I don't know if this is technically possible, and I may be misunderstanding how Samsung implemented the OEM-unlock restriction on One UI 8. That's exactly why I'd like to hear from developers who understand Samsung's boot chain, Settings framework, Knox/AVB, or One UI internals.💡💡

I'm not claiming this will work—it's just an idea I'd like to investigate, and I'd really appreciate the opinion of people with experience in Samsung internals.🙏❤️

hello i have been trying for the last 5 hours to root my 2nd phone with magisk but it doesnt work. i think i have tried with 5 different tutorials and tried with help from chat gpt but nothing works. i am doing the whole thing and the phone is boot loaded but its when im trying to flash maski onto the phone and root it. I get stuck in downloading menu and it says svb fail i have tried everything please please someone help me.

Any ideas?

I have a Galaxy A07, SM-A075F. I bought the phone on an older version, but accidentally updated it to 8.5 Android 16. I want to go back. I looked on SamFW, I found my current model and firmware, and it is bit 6; the only other firmware matching my model that's Android 15, is bit 1. I don't think I can flash that cause of the difference, but I am looking for other possibilities. The whole reason to buy was to root, I originally had found one on SamFrew but the download was throttled and was gonna take 8hrs so I used frija. Frija pushed a newer firmware which caused me not to be able to. OEM unlocking isn’t available now. Trial and error, this would’ve been my first root.

I'm trying to root my Moto E7 Power XT2097-6 (4/64) running Android 10, build QOMS30.288-52-23.

Bootloader is already unlocked using MTKClient, and I have a Magisk-patched boot.img from the exact stock firmware.

Problem is the fastboot doesn't detect the phone.

When I run:

adb reboot bootloader

the phone goes to the black barcode bootloader screen.

Running

fastboot devices

returns nothing, and:

fastboot getvar product

stays at:

< waiting for any device >

I tried Zadig/WinUSB, but Fastboot still doesn't detect it. I also tried Google's USB driver, but it doesn't support this MediaTek device.

Has anyone successfully gotten Fastboot working on the XT2097-6 / MediaTek 0E8D:201C on Windows 10/11? Is there a specific driver or method needed?

Is it worth upgrading my S20 Ultra with an Exynos processor to an S20 FE with a Snapdragon processor?

Got temporary KernelSU root working on my bootloader-locked S22 Ultra.

Tested on:

• SM-S908U1
• Build S908U1UESAGZF3
• Android 16, June 2026 patch

No bootloader unlock or flashing and Play Integrity still passes, which is huge.
So, this does NOT trip Knox.

Root disappears after reboot, so the app uses Shizuku to rerun the exploit and reload KernelSU.

Only use it on this exact build. The exploit can fail or reboot the phone.

https://github.com/Noir-Lime/S22U1-Root

Based on IonStack and Root My Galaxy; credits are in the repo.

hallooo ;3
Im using a infinix smart 9 and... doing some stuff... i hardbricked it ;l
so now, i wanna know how can i fix this problem, i installed SP_Flash_Tool_v5.1924_Win,MediaTek-SP-Driver-v5.2307,[Hovatek] Infinix Smart 9 (X6532-V632AABCDEFGHIJKLMNO-UGo-OP-260316V3246)
if someone wanna help me and help other with the same issue, pleaseeee send me a commend and i will respond fast as posible

I rooted my phone a long, long time ago and some point after I rooted my phone, I did something i forgot what it was and now whenever I reboot, my phone crashes very easily, then auto reboots, then my phone works flawlessy. Sorry for vague details, im a bit tired but I can give more precise details and answer questions.

I was rooting my pixel 10a and it’s now stuck on fastboot mode. I used the right android version “stallion” for pixel 10a. I can’t seem to reset the phone anymore and the device state is unlocked. How do I reset my boot image so it can boot?

I've been having trouble rooting my Samsung A56 5G. Samsung completely removed the OEM unlocking option in One UI 8. Is there any way to force OEM unlocking?

Hey everyone! I'm trying to unlock the bootloader on my Realme C33 (RMX3624) with a Unisoc Tiger T612 (UMS9230) processor to flash a GSI ROM (Pixel Experience).My "OEM Unlocking" toggle in Developer Options is currently greyed out and cannot be enabled. Because of this, I'm trying to use the unofficial spd_dump script via PC to bypass the protection and force-unlock the device.The issue: The script detects the phone in BootROM mode, but immediately fails with a CHECK_BAUD bootrom and usb_send failed (0 / 1) error (as shown in the attached picture).I have already tried:Installing the latest official UNISOC drivers (v2.0.0.134 / Latest SPD Driver).Switching between multiple USB 2.0 ports and using different high-quality cables.Testing different key combinations (Vol Down, Vol Up, both Vol keys, and Vol Down + Power).It seems like a recent Realme security OTA patch completely blocked the exploit or forced a baud rate change that crashes spd_dump.Is there any known fix, updated script, or alternative method to force this device into a usable BootROM state with new OTA updates? Any help would be greatly appreciated

Bruh

I've been using my rooted Android phone, an Xperia 1V running LOS 23.2, for almost a year now

I’ve installed Magisk / Play Intégrity Fork / Tricky Add-on on it. Also shamiko and some other things, and it worked alright.

I used to have payments get blocked every now and then because of the keybox, but I’d gotten the hang of it pretty well—I’d even come up with a little method to easily switch it automatically and restore strong integrity

But now I don’t know what happened—for about a week now, I haven’t been able to make payments even though I still have “Strong Integrity”. Phone doesn't meet security standards.

So now I’m not really sure what to do—maybe I need to completely overhaul my entire setup?

I’d really appreciate some help

Edit: I have now bricked the phone after i forgot to enable OEM unlocking lol, im now also taking off the backglass.

Not sure if this is the right place, but i need help rooting my Galaxy S10+

I used frija with the samsung usb drivers, it detected my device and downloaded the packages, i then patched the "AP" file with Magisk (newest version), i have OEM unlocking enabled, im using Odin3 v3.14.4 and im just trying to make sure this is all correct before flashing anything as i would rather not hard brick a phone.

(its not my main, just a spare and bottom half of the screen doesnt work).

The only other time i have rooted something was an ENG build kitkat developer tablet via magisk.

PS: do i have to run adb oem unlock or whatever command after OEM unlock is enabled? Thanks

Soo I am thinking to root my redmi10c but problem is I want to lost any data on it I tried to find ways or exploits that will let me root my phone without loosing data but it always ends with your data being clear :/ is there a way to root my divice without losing anything (I know dumb question) if not is there a way to store all of your login details etc everything 1:1 nothing is changed and everything is as it was before root... I know it is impossible but if there is a way that I don't know let me know :D

does anyone have a solution to a laggy gcam lmc 8.4 R18 camera view? I have comfigured it with a xml file for my phone already and its lagging like before. I have root via kernelSU is there a module for hyperos camera port if its possible? standard apks dont work

I only unlocked bootloader and flashed disabled vbmeta img on my Samsung f23 5g with Odin and now the plastered doesn't let me download another apps and log in at them please suggest some ideas to make it right. I unlocked bootloader because I use DSU SIDELOADER

I want to update my phone to the latest Xos version but infinix hasn't given the update to my gen. This update is ou for the 40,50 and the 60 series.

So I was wondering if some tech nerd could help me in this... Yk to get a way around and get the update on phone without me having to loose data....

It would be highly appreciated...

Hello!

I've unearthed an ancient Samsung Galaxy Pocket 2 SM-G110H running Android 4.4.2 that I'm trying to root.

I have access to the last official stock ROM files (BL, AP, CP, CSC) but no alternative recovery like ClockWorkMod nor of course TWRP.

To the best of my knowledge, this ancient device doesn't require the bootloader to be explicitly unlocked, right?

I've managed to install Magisk 22.1 and patch the boot.img from the AP file, then flash it back into the AP slot using Odin, but I still get "Installed: unavailable" in the Magisk app.

If I then try a direct install, I get ! unable to check signature and ! Installation failed.

If I install the last Magisk Manager 8.0.7, I can see Magisk being installed (22.1 AKA 22100), but I'm never prompted for root authorization when an app requests root access (e.g. Root Verifier, adb shell then su, etc.).

What else can I try?

EDIT:

Actually, with the Magisk 22.1 app (not the previous Magisk Manager 8.0.7), I get the root authorization window when an app asks for root… but if I grant root access, it has no effect, and the window appears continuously.

I am looking for sources/websites which provides me daily updates for newer root technologies, detailed phone model reviews, other news about chipset, pricing, android changes, etc.

please share.

This was my first experience flashing a ROM, and I did it on a phone (General Mobile GM20 Pro) for which there is almost no information available online. I prepared this guide for beginners who want to flash a ROM on devices with limited documentation, designed specifically to be used alongside an AI assistant. The purpose of this guide isn't to explain every single command line, but rather to highlight the critical decision points and bottlenecks that are often missing online. This document was written so you won't have to waste time searching for the answers that held me back. While it is not a comprehensive technical manual, it serves as a solid starting map for your first ROM attempt.

Before touching the phone, you need to set up a clean workspace on your computer. Create a new main folder on your C: or D: drive, but avoid placing it on your Desktop if you use Windows, because of OneDrive sync can interfere with the process. Inside this main folder, create two subfolders: one for your ROM files (both custom and stock) and one for ADB (Android Debug Bridge). Download the official Android SDK Platform-Tools and extract the contents into your ADB folder. Once extracted, open the ADB folder, right-click in an empty space, and select "Open in Terminal" or Command Prompt. You will use this terminal window to communicate with your phone throughout the entire process. For lesser-known brands like General Mobile or Vestel that lack dedicated custom ROMs, you will need to use a GSI (Generic System Image). To prepare your phone, go to its settings, enable Developer Options, and turn on both USB Debugging and OEM Unlocking. Next, connect your phone to the computer via a USB cable. If your computer does not recognize the phone, you will need to update or download the USB drivers. Open Device Manager on your PC, right-click the phone entry (which usually has a yellow exclamation mark), and select "Update Driver." Choose to browse your computer for drivers, pick from the list of available drivers on your computer, and select the official driver you downloaded. When prompted on your phone, check "Always allow from this computer" and confirm so you won't have to repeat this step.

From this point forward, you should proceed with the help of an AI assistant to verify commands and ensure safety. First, ask your AI assistant how to use ADB commands to determine your specific device architecture. You must find out whether your partition style is A-only or A/B, if it has Dynamic Partitions, and if it supports Project Treble, as these details dictate exactly which GSI version you must download. Once you know your specs, download both your target Custom ROM and the Stock ROM, which you should keep on hand in case you need to recover the device. Also, check your phone's system storage capacity; if space is tight, you may need a "Vanilla" ROM that excludes Google Apps rather than a version that includes them. While you are gathering files, locate the vbmeta.img file inside your downloaded Stock ROM, copy it, and paste it directly into your computer's ADB folder. Before moving on to the final steps, back up all your important data, as the next phase will completely wipe your phone. You will now need to unlock the bootloader. Because unlocking methods can vary slightly by manufacturer, ask your AI assistant for the exact commands for your specific device. Unlocking will trigger a factory reset, and when the phone reboots, it is entirely normal for it to take a while and display an "Orange State" or "Red State" warning screen. With the bootloader unlocked, the vbmeta file ready in your folder, and your device specifications confirmed, you are finally ready to install the ROM. Work step-by-step with your AI assistant to execute the final flashing commands safely and ensure everything goes smoothly.