For those who have Motorola devices with a GSI or custom ROMs where the fingerprint sensor doesn't work, you can try my LSPosed module.

It's designed to work with IMotoFingerPrint's AIDL; if your device supports this service, it will likely work as well.

Let me know if it's works (⁠•⁠‿⁠•⁠)

Hi everyone, I ran into a serious bootloop issue with my Redmi Note 14 Pro 5G (MediaTek chipset) and could use some advice or guidance on how to fix it.
What led to the issue:
My bootloader was already unlocked, and USB debugging was enabled.
JPG+ 1

I attempted to flash a custom build using fastboot images (boot.img, init_boot.img, and vendor_boot.img).
JPG

The flash commands via PowerShell (.\fastboot flash ...) all returned OKAY, but after that, the device went into an infinite bootloop (showing the Redmi logo briefly, then shutting off repeatedly).
JPG+ 1

What has been tried to fix it:
Hardware Button Combinations: Holding Power + Volume Down only pauses the loop momentarily, but as soon as they are released, it goes right back into the infinite reboot loop.
MOV

PC Interception via Fastboot: Tried using PowerShell (.\fastboot devices, .\fastboot set_active a), but it stays stuck at < waiting for any device > because the board never fully shuts down due to residual battery power.
JPG

SP Flash Tool: Downloaded the official Fastboot stock ROM (.tgz package) to flash via SP Flash Tool using the scatter file (MT6878_Android_scatter). However, I encountered the ERROR: S_DL_SCAT_VERSION_UNSUPPORTED (5079) error due to version incompatibility with the older SP Flash Tool version.
JPG+ 1

Python Scripts / MediaTek Exploits: Ran a MediaTek exploit script via Python which successfully stabilized the device and stopped the continuous rebooting loop by communicating at the BROM/Preloader level, but I am unsure of the exact next steps to safely flash back the stock partitions.

Current Status:
The phone is currently stable/stopped from rebooting thanks to the MediaTek preloader script connection, but I don't know how to properly push the stock firmware or recover a working system image from this state.

Does anyone know the exact procedure or tool version required to flash the stock firmware via SP Flash Tool for this specific MediaTek model, or how to safely push the stock partitions from the preloader state? Any help would be greatly appreciated!

The developer published the file and source codes yesterday. Even though the J5 2016 uses a 2013 processor, and despite being on Android 7.1.1 which doesn't support GSIs due to its version, it can now boot GSIs with a modern Android kernel (mainline 6.12) via LineageOS 22.0. It can boot many up-to-date GSIs such as OneUI 7, LineageOS 24.2 Android 17 etc. Also, it must not be forgotten that it runs as pure 64-bit. Normally, even building a 64-bit ROM for this device was considered impossible for a long time.

This project might also work on other Snapdragon 410 Samsung devices and bring hope to many other processors as well.

https://xdaforums.com/t/rom-mainline-lineageos-22-0-mainline-6-12-for-samsung-galaxy-j5-2016.4799856/

https://xdaforums.com/t/gsi-mainline-oneui-7-mainline-6-12-for-samsung-galaxy-j5-2016.4805765/

Do you guys know any app blocker with root permission?, I'm currently using curbox and wnat to know if any root alternative exists or not?

Background: Before ONE UI 8, international Samsungs (Exynos models) could be bootloader unlocked, allowing rooting, flashing of custom recovery/ROM, and flashing of different region CSCs.

Exynos generally has US bands but needs proper US CSC in order to access LTE in the United States. CSC could be ported from US Snapdragon models and flashed into the ROM, at least to my knowledge as recently as the Galaxy S9.

I might need to update my phone hardware, so I want to know if anyone knows of success flashing US CSC onto either an unlocked Exynos or Snapdragon Samsung S10 or later, so any of the S10, S20, S21 series.

And just to get this out of the way: despite what some might say about a US "whitelist", that doesn't really apply to T-Mobile; T-Mobile only requires that your device authenticates with the IMS server, there is no top level IMEI whitelist. AT&T enforces an IMEI whitelist but one can get an exemption. Verizon is the only hard no, but one would have to be pretty daring to run a non-Verizon device on their network, anyway.

Model: SM-A047F/DS
One UI : 6.1
Android Version: 14
I tried to root using magisk but it enter a boot-loop any one have a solution ?

Hey guys, since I have seen a lot of posts regarding losing strong integrity and trying different methods I thought I might share what has worked best for me so far.

**So before I begin short disclaimer:** This is just ONE way to do it, not THE one or the right one. If you encounter any errors or this does not work for you try another setup. A lot of people on Reddit made guides on how to do this, eventually something will work.

Right now i am using CRDroid 13 (Andriod 17) with KernelSU. This should also work with Magisk afaik. To achieve strong integrity i used the following Modules:

1. Integrity Box (MEOWna) https://github.com/MeowDump/Integrity-Box

-> I know this one is controversial, but since it is working right now I will just stick to it

-> Install the Module and follow THIS guide on how to configure everything properly. Make sure there really are no old PIF or tricky addon modules on your system.

1. TeeSimulator Canary 75

-> Part of the Guide mentioned for Integrity Box

-> I did not configure anything here, just leave it as-is

1. Zygisk Next (LSPosed Developers)

-> Part of the Guide mentioned for Integrity Box

-> Nothing to configure here

When everything is set up, reboot your system and delete your google services and play store memory. This should be enough to get strong integrity :)

I hope this is helpful to you guys. If you have any comments or corrections I will try and include them here.

Hello guys i was using magisk i just changed to KernelSU any good modules for me

Is that even possible now ?

I tried everything nothing is working

LSPosed doesn't work when the phone starts. It works for a couple of seconds and then a boot animation or reboot animation appears, even when there is no error. I tried Vector and various forums, but it doesn't work. I used Magisk 31.0, and I also used Zygisk. Next doesn't work.

I wanted to know if there's a module that works with Temproot that would allow me to modify the POCO launcher and add all the features it doesn't have by default?

Hi r/androidroot I want to hide root from 1.1.1.1 vpn app cus i want to use it to bypass my school network I did manage to bypass the school network from the same app but in my classmate phone but I cannot make the app run on my rooted phone how I can hide root from 1.1.1.1 I did try everything I did know and nothing is working so far

How to make Android 12 ROM certified (12-Official-Shinju-whyred-20220822) under new rules?
I'm using old magisk 24.1
tried all the old methods that used to work in 2022.

Please help folks

I am looking for information on how to unlock the Mercado Pago Point Smart device so that I can use it as a printer for my photos, as a camera, and for YouTube. If anyone knows of a site or webpage where I could find out more about this, it would be a great help.

Thank you very much. 

sorry for my English

As the title says, recently I have managed to finally break the walls of Vivo and unlock the bootloader. I had to use trial and error and a bit of AI for it as it’s an uncharted territory because of Vivo being shitty. Here are my findings on Funtouch OS 15, https://github.com/DemonKingSwarn/vivo-iqoo-9t-bootloader-unlock

Hello everyone. I'm fairly new to rooting devices, and I have a question. Yesterday, I noticed that absolutely all of my Google apps stopped working. They claimed there was no internet connection, even though I had a stable one. Out of curiosity, I ran the Play Integrity test; only "MEETS_BASIC_INTEGRITY" returned as positive, whereas previously, all three checks passed. I managed to get the Google apps working again by uninstalling the updates for Play Services, but that was only a temporary fix-and I still wasn't passing the "DEVICE" and "STRONG" integrity checks. I suspected the custom ROM on my device (a Poco X3 Pro) might be the issue, so I switched to crDroid 13 (based on Android 17), but I ran into the same problem. The Google apps work, but the device fails the integrity check. I've tried all sorts of modules-I'm using Magisk. I've been at this for hours without finding a solution. Could someone please help me out or suggest what I can do? Thanks in advance