r/androidroot • • May 31 '25

Discussion Check my Custom Rooted Android

10 Upvotes

Hey Community,
What's new and exciting in Android Rooting?
From my initial research there is not much innovation going on android rooting. You know I'm one of the folks tried Severe times to Root a phone and didn't work properly.

And finally rooted a behemoth Samsung device. But seems like the apps are outdated and there isn't much going on. Despite all the AI , Saas Hype my rooted android sits there with pretty much an ad free device. I'm open to discussion and collaborations. Also please let me know if there is any cool projects going on here.


r/androidroot • • Aug 03 '26

Support Hi everyone, I accidentally forgot my text password on my Redmi Note 7 (lavender) running Pixel Experience (Android 13).

Post image
1 Upvotes

I have very important data on the internal storage and cannot afford a factory reset.

What I've already tried:

Google Find My Device : Only has "Mark as lost" option now, cannot set a new password.

OrangeFox Recovery: Booted via fastboot, but /data/system/ files appear encrypted (gibberish filenames).

Custom Lock Remover Zip: Sideloaded via PE Recovery, but it failed to delete lock files because filenames were encrypted on disk.


r/androidroot • • Dec 15 '24

Discussion Is rooting android without PC now impossible ?

0 Upvotes

I seen a lot tutorial videos and site teaching you how to root your android. But in the old android phones you supposed to able to root android straight from your phone without PC just only using one app called KingRoot Wich the easiest just one click and your phone is rooted . But now for newer android phones using KingRoot will no longer work . Rooting your android now requiring to unlock the bootloader first and you need to install a custom recovery to your phone or rooting by via patching the boot img of your phone updated package and patch it using magisk and flashing it using adb on pc


r/androidroot • • Mar 30 '25

Discussion Can you root with pirated Windows

1 Upvotes

I've been trying to root my samsung tab s6 lite with magisk and odin, but it hasn't been working.

I think this might be because my Windows on my PC is pirated. Can I still root my tab? If I can please help...

Everything until the Odin part, I am 99.99% sure is perfect, OEM unlocking and everything works but Odin isn't being able to flash


r/androidroot • • Jun 11 '26

Support Reddit don't log on

0 Upvotes

It's a galaxy tab A7 if that helps


r/androidroot • • Jul 28 '25

Discussion (Help, Adb) Which samsung package is responsible for the fingerprint sensor?

Post image
0 Upvotes

Hi there, my battery is poor, so tried debloating One Ui 4.1 via adb. Removed almost all samsung apps, except for the annoying game optimizing service. Anyway after debloating, I noticed the fingerprint unlock setting gives the above error. I tried reseting accessibility settings, rebooting, nothings helps. Which is why I'm asking, what samsung packages is responsible for the fingerprint sensor and biometric screen unlock service ? Thank you guys (in advance)...


r/androidroot • • Apr 18 '26

Discussion I want to root this phone without pc

Post image
0 Upvotes

Well its Samsung Galaxy J6 and I want to root it without pc and this will be my first root so im kind of confused. Any ideas?


r/androidroot • • Sep 06 '24

Support I unlocked the bootloader...

Post image
0 Upvotes

Now my banking apps aren't working. I thought they don't work when you root the device not just by unlocking the boot. Please help me revert back this. Is formatting the only option?


r/androidroot • • Sep 17 '26

Humor Sometimes I Hate Custom Roms

Post image
0 Upvotes

Due To Integrity Shit Google Doin

It boils my skin not being able to use some banking or app think that ur using some kinda hacking device.🤷


r/androidroot • • Oct 15 '26

Support Xiaomi 17 Pro Max (popsicle) + PixelOS Android 17 — All Play Integrity verdicts failing. Need help diagnosing the cause.

Thumbnail
gallery
1 Upvotes

Hey everyone,

I'm running a modified PixelOS Android 17 build on my Xiaomi 17 Pro Max (popsicle), and I'm having trouble with Play Integrity. I'm currently failing Basic, Device, and Strong Integrity. I'm looking for help identifying the underlying cause instead of blindly stacking modules or changing random settings.

Device and software

  • Device: Xiaomi 17 Pro Max (2509FPN0BC)

  • Codename: popsicle

  • ROM: PixelOS-popsicle-20261007-four-fixes_by_Kanoe

  • Android: 17 / API 37

  • Firmware: HyperOS 3.0.319

  • Security patch shown in Specter: 2026-10-01

  • Root setup: KernelSU-based, with Zygisk-related components

  • Bootloader: Modified-device setup; I want to verify the actual boot and attestation state rather than trust one tool's report.

Current Play Integrity results

  • āŒ MEETS_BASIC_INTEGRITY

  • āŒ MEETS_DEVICE_INTEGRITY

  • āŒ MEETS_STRONG_INTEGRITY

None of the three verdicts are currently passing.

Current setup

The tools and modules involved include:

  • Specter

  • Play Integrity Fork v18

  • HMA-OSS Zygisk

  • Zygisk-related components

  • .BRENE - SuSFS

  • ZN - Audit Patch

  • NoMount

  • bindhosts

  • Iconify

Specter currently displays:

  • TEE backend: TEESimulator

  • Keybox: TAKR 10 active

  • Selected device profile: Pixel 6a

  • Security patch: 2026-10-01

Some module names appeared repeatedly in my scrolling screenshots, but I haven't verified whether those are actual duplicate installations.

Duck Detector findings

My earlier Duck Detector report showed a few things that might be relevant:

  1. Fingerprint/build-tag mismatch Fingerprint: Xiaomi/custom_popsicle/popsicle:17/CP2A.260605.016/eng.root:user/test-keys Meanwhile, Build.TAGS and ro.build.tags reportedly show release-keys.

  2. SELinux policy finding SELinux is enforcing, but the report flagged an allowed adbd -> adbroot:binder interaction. I don't know whether this is expected for this ROM.

  3. Attestation inconsistency Duck Detector reported a Google-rooted certificate chain and locked/verified boot state, while Specter explicitly shows TEESimulator. I need to establish whether the reported attestation is genuinely hardware-backed.

  4. Custom ROM environment The ROM contains LineageOS-derived components. Widevine reports L1, but the session is NOT_PROVISIONED.

These are observations, not confirmed causes of the current failure.

What I need help with

  1. What could cause Basic Integrity itself to fail on this setup?

  2. How can I distinguish a Google Play services/checker issue from a ROM, root, or attestation issue?

  3. Could the fingerprint/build configuration or simulated TEE be contributing to the failure?

  4. How can I identify conflicting modules without randomly changing the entire setup?

  5. Is there a known issue with this PixelOS build or Android 17 on popsicle?

  6. What are my realistic options if I want genuine Play Integrity, especially Strong Integrity?

I'm looking for a proper diagnosis and reproducible troubleshooting steps. I don't want to risk bricking the device by flashing incompatible firmware or relocking the bootloader while a modified ROM is installed.

I can share the checker screenshot, Duck Detector report, module list, and relevant logs.


r/androidroot • • Sep 11 '24

Discussion Any real reason to root?

0 Upvotes

Don't get me wrong I have a problem with wanting control of a device I own. And I'm the first to install a custom roms and root. But in this day and age is there any real reason to root?


r/androidroot • • Jan 22 '25

Discussion Can i root my phone and then un-root it with the official samsung software?

Post image
1 Upvotes

Can i root my phone and then un-root it with the official samsung software? I just want to know if it is possible.


r/androidroot • • Jan 26 '26

Support Hack? Magisk, HuskyDG

1 Upvotes

Hey,

Over the last few months my phone (Samsung A71) has been acting really weird — constant calls to the emergency number, unlocking and locking the screen by itself, opening the camera, etc.

Following ChatGPT’s instructions, I installed ADB and started digging deeper into the system.

So far I’ve found the following:

  1. io.github.huskydg.magisk

  2. io.github.vvb2060.magisk

  3. me.garfieldhan.apatch.next

Plus some extra info from ChatGPT after I pulled part of the dumpstate:

  • The camera has been turning on in cycles for about a month

  • Spyware apps were previously removed (e.g. hidden.device.spy.camera.finder.detector)

  • Access to lockscreen / alarm / SMS

  • UID 5021 / op=26 (camera access)

  • Camera usage stats show ~27 hours of usage

  • Logs from AppOps / RequestInjectorService

Initial conclusion:
These findings CONFIRM my suspicions — the phone was most likely rooted (Magisk / APatch), which explains the persistent camera access even after removing the app.
UID 5021 (adaptivebrightnessgo) is still trying to access the CAMERA (op=26), and the queriesPackages list looks like Samsung’s built-in checker for root, spyware, or remote access tools (like AnyDesk / TeamViewer).

The issue has been going on for about a month because root access allows hidden code injection. This doesn’t look like a bug — it looks like malware or an exploit.

According to ChatGPT, this couldn’t have been installed remotely.
I’ve never connected this phone to a computer. I got it from a friend, who bought it brand new and claims he never installed anything like this.

What do you think?
Did someone install malware on this phone or not?
How can I verify this further?
If you need more system info or logs, let me know and I’ll dump them.


r/androidroot • • Sep 28 '26

Discussion did Google restrict sideloading right now?

Post image
0 Upvotes

I was checking developer options in HyperOS and then I found an option that I've never seen before, "Allow Apps from unverified developers" so i clicked on it and this popped up.


r/androidroot • • May 07 '25

Support Does anyone know what this is tool? Spoiler

Post image
0 Upvotes

Does anyone know what this is tool?


r/androidroot • • Aug 25 '25

Discussion How to fix this

Post image
0 Upvotes

Hello, I'm new to this stuff. Please anyone can help me to fix this?


r/androidroot • • 22d ago

Support I cannot flash my Jelly Star to Android 16.

Post image
0 Upvotes

I could not get this working. The only way to update to ansroid 16 is flashing the 13 build and I need to then download the firmware again from there. Its hell and takes hours.


r/androidroot • • Oct 05 '26

Humor Did Android just add root in the permission manager???

Thumbnail
gallery
0 Upvotes

r/androidroot • • Sep 28 '25

Meta FRP bypass requests/assistance is now a bannable offence

28 Upvotes

Hi all,

As you all should know, we do not tolerate discussion of FRP (Factory Reset Protection) bypassing on r/androidroot. While there are potential good reasons for one to want to bypass FRP, there are far more negative ones.

To avoid unintentionally being of benefit to any potential thieves, we have chosen to outright ban discussion of it outright. This includes asking how to do it, providing information on how to do it, and so on.

The first offence will carry a 7 day ban.

The second offence will carry a permanent ban.

These stricter punishments are being put into place as a result of a sharp increase in FRP bypassing posts. We appreciate those who have been reporting them to us, by the way. We have no tolerance for this, and these new punishments will come into play effective immediately.

Thanks.

Edit: In the interest of fairness to users, posts made prior to this announcement will not be subject to a ban. Due to the confusing way Reddit handles rules, Mods were under the impression that it was already designated as a rule. It was actually just a ban reason.


r/androidroot • • Mar 05 '26

Discussion now that google's gonna restrict sideloading, would it be a bad idea to root?

4 Upvotes

What the title says.


r/androidroot • • Jun 27 '25

Discussion HELP AGAIN WITH MY BRICKED TABLET

5 Upvotes

I recently added a post where my Samsung Galaxy tab a7 2020 (south america, qualcomm) got bricked trying to install TWRP. Now I have an issue with another screen that is download mode but some strange text, and it doesn't let me flash (I TRIED BOTH OFON AND EROS)


r/androidroot • • May 31 '26

Humor D.I.Y Wallpaper, Android os is built on top Linux kernel...

Thumbnail
gallery
8 Upvotes

r/androidroot • • Dec 25 '24

Support [HELP]Guys help someone send me a python file and he said execute the file using termux and after that my device shutdown

Post image
0 Upvotes

r/androidroot • • Apr 14 '25

Discussion My discontent with the discrimination towards low-end products and how I resolved it

1 Upvotes

How I transformed my Redmi 14C: A technological customization manifesto

1. Why did I decide to root and modify my cell phone?

I decided to root and mod my phone because it is a low-end device, and I can't stand the limitations imposed by manufacturers based solely on price range. I feel that, by labeling a cell phone as "low-end," they are discriminating against me just because I don't have enough money to pay for their flagships that cost four hundred thousand pesos. This motivated me to prove that an affordable phone doesn't have to be left behind. So I got to work and started by unlocking the bootloader as the first step to unlocking its true potential.


2. What tools and steps did I use to unlock the bootloader and root?

The process of unlocking the bootloader was quite a challenge. My phone is a Redmi 14C, with the codename Pond. Unfortunately for me, almost all devices of this model share the Lake codename, and to date (April 13, 2025), there is still no specific support for the Pond codename. Xiaomi's official tools were not of much help; It seemed that, since it was a low-end phone, they simply didn't want to provide anything.

But as they say, "he who seeks finds." After a lot of digging, I found on GitHub a tool called miunlock-termux, designed to run on Termux, an app that creates a Linux environment on Android. I installed this tool on an old LG Power 2 (model LM320) that I had at home. Following the instructions and with all the requirements ready, surprise! The tool unlocked the bootloader without asking me for anything: no Xiaomi account, no authorization, no connection to its servers. An unexpected success!

The next challenge was rooting the phone, which required the boot.img firmware file. However, I did not find a firmware for my codename Pond. Tired, I decided to try the Lake firmware. I downloaded it, extracted the boot.img, transferred it to the cell phone, and patched it using Magisk. Then, I transferred the patched file to my PC, placed it in the Minimal Fastboot and ADB folder, and connected the phone in bootloader (fastboot) mode.

I ran the magic command:

fastboot flash boot_ab bootloader.img

The tool did its magic, and with a simple:

fastboot reboot

Goodbye locks! The bootloader was unlocked, and the phone was ready to unleash its full potential.


3. Modifications made

Once I had my Redmi 14C rooted, I couldn't wait any longer to use Magisk and start adapting. My first module installed was Antibootloop, which has been an essential tool to avoid the dreaded bootloops when I make a mistake or install a module that is incompatible with the cell phone.

Afterwards, I jumped straight into Hyperceiler, the magical and holy module of radical modifications. This module was one of my main reasons for rooting my cell phone, since my big challenge was to activate Xiaomi's Super Wallpapers, which according to the company, my model could not install due to "range restrictions". Ha! Restrictions for me and my cell phone, please. I activated Super Wallpapers and, to my surprise, they work wonderfully, proving that the limitations imposed by manufacturers are more political than technical.

Among the additional modules I installed to complement Hyperceiler were:

  • LSPosed: Very useful, although it does not achieve the same level of customization as Hyperceiler.

  • Cemiuler: Similar to LSPosed, but I decided not to keep it because it did not offer significant advantages.

There are many other modules that could be mentioned, but I want to leave the space open for everyone to explore and discover for themselves the wonders they can achieve on phones that, unfairly, are discriminated against and underestimated just for being cheap.


4. Results obtained

Once my Redmi 14C was completely modified, the results were surprising, taking the user experience to another level:

  • Custom Bootanimation: Although the initial Xiaomi logo still appears (for now), I managed to change the annoying Telcel animation for something much more motivating: a video of my favorite player, Dennis Rodman. I made this change with the Vid2Boot tool, executed in Termux as root. Now every time I turn on my phone, the startup has personality and style.

  • Super Wallpapers activated: I was finally able to enjoy Xiaomi's impressive Super Wallpapers, something that was blocked for devices like mine because it was "low-end". Currently, I have the Earth wallpaper, but all the ones available (Moon, Mars, Geometry) are incredible. They really transform the appearance of the cell phone.

  • Improved sound: With EXTREM Music, the device's audio had a total change, taking the sound quality to another level, perfect for music and videos.

  • Custom fonts and themes: Thanks to Dafont, I was able to modify the system fonts, and now I have a completely unique style. Plus, I can choose any theme without the annoying global restrictions imposed by Xiaomi. It's like having a completely different cell phone.

  • Beware of bootloops: Not everything has been perfect; I've had to deal with four bootloops so far. Luckily, I always managed to recover with tools, adjustments and a little help from my good friend, a "wey" I know who calls himself Copilot (who, I must admit, is a good beast at this).

In short, the telephone is now another world. Despite its initial limitations, I have taken it to a level comparable to, or even superior to, many high-end models.


5. Recommendations and final message

I could give them recommendations on the tools I mentioned or warn them about what can happen if they make mistakes when rooting their phones. You might even tell them not to try if they don't feel safe. Do you know how many times they told me that? As many as you can imagine. And do you think I listened? Ha! Not at all. I have gone through at least 15 phones: some bricked, others broken, and some open that I no longer knew how to put together. But you know what? Thanks to those mistakes and not listening to repetitive warnings, sometimes even perverse ones, today I have my cell phone just the way I want it.

And how do I have it? Just the way I feel like it! Not how the manufacturers want me to use it. Since when does someone tell me how to use what I bought with my money, whether expensive or cheap. If I paid for it, it's mine, and I'll use it however I want. Does anyone tell me how I should use my bike after I buy it? Well no.

So no, I'm not going to give you warnings. There are already enough out there. My only hope is that my experience with the Redmi 14C inspires you and helps you make your way. Down with technological discrimination!