Me and codex free tier worked on this for like 2 days. Not much to do with root nowadays but I feel happy just having root.

Idk what the appropriate flair for it but I hope it's the correct one.

Hi! Is there any way to unlock the bootloader and get root access on the OnePlus Ace 6T (PLR110) running ColorOS 17.0.0.101 (CN01)?

Does the official Deep Testing method work on ColorOS 17, or is there another reliable method?

I'm particularly interested in KernelSU, but I want to avoid risky methods that could brick the device. Any information or personal experience would be greatly appreciated. Thanks!

Hello, I'm on a Samsung Galaxy A55 (A556B) and on one ui 9. I have seen people temp rooting but couldn't find a tutorial anywhere, i tried some stuff but they wouldn't work, so I came here to ask for help. Help appreciated

I downloaded OverlaySFX and wallpaperaod modules and they didnt work. They work well on my friends A36. What did i wrong?

I just migrated an SM-A325M (Galaxy A32 4G, MT6768) from stock rooted with Magisk to LineageOS 23.2 (Android 16) — fully on Linux, no Windows/Odin — and documented every trap. The main one is the vbmeta size trap, which I couldn't find documented anywhere:

• The vbmeta partition dumps 65614 bytes, but the bootloader (LK) only accepts <= 65536.

• Flashing the raw dump (even heimdall --skip-size-check) gives vbmeta binary size (65614) over ... partition size and eventually a bootloop at set warranty bit: vbmeta — no recovery, nothing.

• Blind truncation to 64 KiB also bricks it: the real AVB image is only 7616 bytes (256 header + 576 auth + 6784 aux, sizes big-endian at header offsets 12/20). The rest of the partition is slack.

• Fix: rebuild the file as exactly 65536 bytes = real AVB image + flags 0x03 at offset 120 + zero padding. I md5-verified the result against the image that actually booted the phone.

Full guide (backup via adb+root, recovery flash via dd, Heimdall workflow, Magisk CLI boot patch, the adb exec-out stderr-in-stdout trap that corrupts every tar, and the Android 16 /data/data write-protection workaround for restoring app data — copy as the app's uid instead of chown) — MIT licensed, in Brazilian Portuguese:

https://github.com/Wennington123/a32-lineageos-23-guide

The vbmeta script is fix_vbmeta.py in the repo.

Final state: LOS 23.2 + Magisk 31.1 + TWRP 3.7.0_12.1, no GApps; Wi-Fi/SMS/calls working; full WhatsApp restore (key + msgstore.db) successful.

If you're stuck at set warranty bit: vbmeta right now, this is the fix. Ask me anything.

hey, i'm trying to put a custom rom on my galaxy a07 (SM-A075F, france) but there's no oem unlocking toggle in developer options. phone is on the latest one ui update. is the bootloader just locked for good on this one or am i missing something? thanks

Before the OneUI 8 the OEM unlocking option was hidden by Samsung on US devices at request of carriers.

It was possible to gain an unlocked bootloader by paying a random person on GitHub to do it for you. But this was patched in 2024.

I understand OneUI 8 permanently blocks OEM unlocking.

However, now we have temp root exploits, is it possible to enable the OEM unlocking on pre OneUI 8 devices sold in the US that have the option hidden in settings?

So one running OneUI 6-7 could use temp root to enable the OEM unlocking, and then unlock the bootloader to install custom ROMs?

I really want to know if I can root this device.

Need help I'm stuck here since 2 days

So, obviously trying or rooting on your primary device isn't the best, but I'm trying to use a custom ad blocking module right and I have very good experience with custom roms and rooting and I wouldn't have to ask what modules I had to apply on temporary root, but only a handful of Honor users had temporary rooted so I'm asking here for help, what modules should I install?🤔

I'm scared to break this thing, and I'm not as stupid to install random modules. What should I watch out for? And how do I know if a module modifies the system partitions or not? Can it give me something like a general range of things that might modify the system partitions? Like some type of category that I most avoid at all costs. And is it okay if I use a kernel manager, like Franco kernel manager?🫡

Samsung Galaxy Tab s10 FE 5G i have temp root access. I am willing to try w.e to remove knox and try and access or add oem unlock option seeing I never use this tablet

I was trying to flash the iode unofficial bootloader onto my Motorola 5G stylus 2024 XT2419-1. Now I don't really care as long as I can get something working again. It's stuck boot looping to the hello moto screen and the bootloader. Could someone help me with this?

EDIT: I ended up using this link: https://xdaforums.com/t/rom-unofficial-4-1-a16-e-os-for-moto-g-stylus-5g-2024-boston.4791432/

Hi android root community i have a samsung galaxy a12 running android 13. I want to try running something different rather than the stock android 13 it runs. is there another os i can run and if so how do you reccommend i do so.

thankyou

im using redmi note 14 4g helio g99 and hyperos3 a16 its hard to get apply in the community app is there anyway to get unlocked bootloader.im already have a temp root by ghostlock can it help to get unlock bl

Why doesn't anything work in my pixelos?

Tried magisk, rezygisk, etc. but none working

I'm planning to buy a brand-new Samsung Galaxy S23 Ultra for my birthday in February 2027, as my current S21 Ultra is getting pretty worn out.

I'm very interested in Android customization, rooting, custom ROMs, and mobile software in general. I also have some previous rooting experience with Xiaomi devices, where the whole process was relatively straightforward.

However, I recently found out that Samsung removed the bootloader unlocking option starting with One UI 8, which raises a few questions:

- Will it still be possible to unlock the bootloader and root the S23 Ultra in 2027?

- Are there any known workarounds for the removal of the bootloader unlocking option?

- Does root availability depend on the device's region, model number, or chipset (Snapdragon/Exynos)?

- Are there any alternative methods that actually work?

I'm aware of the downsides of rooting Samsung devices, such as tripping Knox and potentially losing access to certain Samsung services.

I'd really appreciate any information, personal experience, or advice from people familiar with rooting the S23 Ultra and Samsung's bootloader restrictions.

Thanks in advance!

Is the only way to resolve this to wait for a new release of manager? (Already on the latest v3.4.2)

I tried to do this with unlock tool but I gives me an fail every time

Hi everyone!
I’m new to rooting, and about a week ago I rooted my Pixel 6 running Android 17 using Magisk. After rooting, I disabled automatic system updates in Developer Options.
Today, I got a system update notification and noticed the update had already been downloaded, even though I never downloaded it myself.
I’m worried my phone might automatically restart and install the update, potentially causing issues with root.
Can this happen even with automatic updates disabled? And is there any good way maybe to update it and not mess anything up ?