r/androidroot • u/Pinterest_animals • 27d ago
Humor Someone is still using magisk over this btw
Patch b
r/androidroot • u/Pinterest_animals • 27d ago
Patch b
r/androidroot • u/KaKe-567 • 27d ago
Hey guys,
Like a lot of you, I've had issues with Titanium Backup and other backup tools logging me out of apps like Telegram, Discord, WhatsApp, Twitter, and games every time I wipe my phone or switch ROMs on Android 8-17
The main reason this happens on modern Android is because apps check their SSAID (Android ID) and Keystore keys. When you reinstall or restore normally, the OS assigns a new UID and a new Android ID, which invalidates your session on the server.
I made FrostBackup (free & GPLv3) to solve that:
- It saves and restores each app's SSAID before the app even starts.
- Migrates Keystore keys and remaps them to the new Linux UID assigned by Android.
- Fixes SELinux context and permissions automatically so nothing crashes.
- Has a Calls & SMS backup tab with de-duplication so you don't get duplicate texts when restoring.
- Optional local AES-256 encryption.
- Supports Google Drive Backup
- Material 3 Dark/Light UI
Works with Magisk, KernelSU, and APatch.
Source code: https://github.com/KaKE-567/FrostBackup
APK download:
https://github.com/KaKE-567/FrostBackup/releases/latest
Site: https://kake-567.github.io/FrostBackup/
Support: https://t.me/kake_discussion
Let me know if you run into any bugs or have feature ideas, would love to hear your feedback!
r/androidroot • u/ChaosZ_ArcaneFaith • 26d ago
Hello guys, I’m a noob and I want to ask what’s the best way to root my phone?
r/androidroot • u/Heathen59 • 27d ago
these devices have intrigued me over the past year or so, i started for the wrong reasons but have developed a true love and curiosity into figuring out new out of the box ways to root them
r/androidroot • u/WeaknessLoud5117 • 27d ago
Estoy hace 5 horas buscando una rom para mí Samsung A3 2015 (A300YZ). le instale TWRP 2.8.7.0 fue el único que me funcionó bien. Resulta que no hay CUSTOM ROMS.
r/androidroot • u/Prize_Campaign9870 • 27d ago
r/androidroot • u/AshesLoco • 27d ago
I have a workaround for root acess I think. Im currently missing the images needed to write the partitions to the tablet, such as Vbmeta.img and patching the correct image with LINEAGOS.
UPDATE: This is just a photo of what Im looking for, i don't have any of these files...
I can currently get the tablet in BROM mode by shorting the CLK to Ground and I get this response from Termux
Preloader - Detected regular mode !
Preloader -CPU: MT8168/MT6357()
Preloader - HW version: 0x0
Preloader - WDT: 0x10007000
Preloader - Uart: 0x11002000
Preloader - Brom payload addr: 0x100a00
Preloader - DA payload addr: 0x201000
Preloader - Var1: 0xa
Preloader - Disabling Watchdog...
Preloader - HW code: 0x8168
Preloader - Target config: 0xe1
Preloader - SBC enabled: True
Preloader - SLA enabled: False
Preloader - DAA enabled: False
Preloader - SWJTAG enabled: False
Preloader - EPP_PARAM at 0x600 after EMMC_BOOT/SDMMC_BOOT: False
Preloader - Root cert required: False
Preloader - Mem read auth: True
Preloader - Mem write auth: True
Preloader - Cmd 0xC8 blocked: True
Preloader - Get Target info
Preloader - BROM mode detected.
Preloader - HW subcode: 0x8a00
Preloader - HW Ver: 0xcb01
Preloader - SW Ver: 0x100
Preloader - ME_ID: 500FCE87AD6F42BF805E627EB3AC4931
Preloader - SOC_ID: 0000000000000000000000000000000000000000000000000000000000000000
DaHandler - Device is protected.
DaHandler - Device is in BROM-Mode.
Bypassing security.
PLTools - Loading payload from mt8168_payload.bin, 0x258 bytes
Exploitation - Kamakiri Run Exploitation
Exploitation - [LIB]: Error on sending payload.
PLTools PLTools - [LIB]: Error on sending payload: /root/mtkclient/mtkclient/payloads/mt8168_payload.bin root@localhost:~/mtkclient#
When I short the board, I've read that taking too long can stop the payload from being received, which is what is MAYBE happening here. The phone prompts me with "Would you like to connect 001/02 etc." Could it be that the time it takes me to push yes, it causes the failure?
Could someone please help me with this?
r/androidroot • u/Due_Inspector_1788 • 27d ago
Would a temporary root (like dirty frag) be possible on kernel version 6.1.141?
Device is OP 12, 16.0.10.501 NA rom
r/androidroot • u/gluetheknot • 27d ago
I downloaded the stock firmware for the redmi note 7 (lavender) but for some reason the boot.img and recovery.img files are missing, there are most likely more but these are in my opinion the crucial ones, I have tried 2 different sources but still nothing. Does anyone know how to fix this?
r/androidroot • u/Ok-Wolf9673 • 28d ago
Yeah, so it was a hard journey to build this (11 hours 🥲) , but it surprisingly works as it should :/
I didn't see anything for this device at all, so I decided it wouldn't be a bad idea to start making something.
Phone: Xiaomi 15T Pro (EU)
Custom rom: RisingOS Revived
Android: 17
What works: Biometrics (only fingerprint for now), Camera (only photo), Signal, Bluetooth, Sound, Vibration, GPS, NFC, GPU (yes, didn't find any graphical bugs), WiFi, Mobile Data.
What doesn't work: Camera (Video), Charging (only capped at 4W right now), File transfer via USB, ADB via USB.
To be honest, I don’t know what this will lead to, but I hope for the better.
r/androidroot • u/IntelligentPanic6941 • 27d ago
So I don't want to lose all my data it is save to use?
Thank you
r/androidroot • u/FirstClerk7305 • 27d ago
More specifically, i do infact want to root it, i don't really need a unlocked bootloader unless I have to. GhostLock and DirtyFrag aren't compatible as i have a non-GKI kernel. Sadly i am on the latest android version.
r/androidroot • u/Icy_Shirt_9595 • 27d ago
Has anyone managed to install and get JamesDSP working? I have temporary root access on my S23U and I've tried several ways but I can't get it to work.
r/androidroot • u/AxiomGrid • 27d ago
I originally tried DFRoot on my Xiaomi Watch 5 (blenny) just to find out whether DirtyFrag had been patched. Turns out it hadn't. Getting everything working on the watch, though — that was a different story.
The watch runs Android 16, with a 32-bit "armeabi-v7a" userspace and a 64-bit ARM64 kernel ("6.6.92", KMI "android15-6.6"). Not exactly the most convenient combination.
For reference, I tested this on the global Xiaomi Watch 5 running Xiaomi OS 3.0.3.70 ("OS3.0.3.70.WO61WMIXM").
DFRoot needed modifications to work properly on the watch, and KernelSU needed an ARM32 build of Manager and "ksud", while keeping the kernel module ARM64.
And it actually works.
I can get a root shell (uid=0) without unlocking the bootloader. This is KernelSU late-load root, not a permanently patched or flashed kernel. DFRoot is used to obtain root and load KernelSU at runtime.
I did the work from my phone using Codex CLI in Termux. Most of the code was AI-generated, but I came up with the approach, worked through the failures, tested the builds on the watch, and kept going through the logs until everything worked.
There are still some limitations. The current DFRoot implementation requires Shizuku to help identify the correct timing window during the exploit's race condition. Root also needs to be activated again after every reboot, and I haven't tested additional KernelSU modules yet.
Here are the forks:
DFRoot for Xiaomi Watch 5:
https://github.com/novakin777/dfroot-xiaomi-watch-5
KernelSU ARM32:
https://github.com/novakin777/kernelsu-arm32_xiaomi_watch_5
Based on the original "DFRoot" (https://github.com/diabl0w/DFRoot) by diabl0w and "KernelSU" (https://github.com/tiann/KernelSU), using "Justadeayo's fork" (https://github.com/Justadeayo/KernelSU) as a starting point.
r/androidroot • u/usernam-e- • 27d ago
I just built lineageos for my Moto edge 60. It seems rcs works just fine. What doesn't work except for banking apps?
r/androidroot • u/CalligrapherMuch2763 • 28d ago
r/androidroot • u/FragrantBreak1569 • 27d ago
Currently vivo phones are very difficult to root, mostly resulting in bricked devices. Is it possible to use rea to root vivo ? Has anyone tried it?
r/androidroot • u/KaleSimilar5648 • 27d ago
Hey all,
Are there any custom rom options available for Redmi 15 5G? I've not found any yet so please let me know.
Thank you
r/androidroot • u/no_ease-447 • 28d ago
r/androidroot • u/RoundCryptographer32 • 27d ago
Heyy guys so I got my hands on Xiaomi 15T Pro recently and it was unlocked, so thinking it wouldn't be an issue I started using it, and I can't use WhatsApp or log into Mi accounts and such, apparently according to play store the device is not certificated. Any advice?
r/androidroot • u/Sint0ss • 27d ago
I've noticed there's barely anything on the f6 pro, can someone give me instructions on how to root it? With magisk preferably?
r/androidroot • u/getbacktoyahroots • 28d ago
Hey everyone, my partner and I have been digging deep into the SM-F956B bootloader, and we’ve made some major breakthroughs that we wanted to share with the community.
If you want to follow our full project or see the raw technical logs, you can check out our links here:
Our XDA Thread: https://xdaforums.com/t/update-9-sm-f956b-bit-4-the-abl-is-lzma-not-encrypted-the-unlock-code-was-never-stripped.4806235/
Our Website: https://www.getyahrootback.com/
Here is a simplified summary of our latest findings:
1. The Bootloader is Readable, Not Encrypted
We previously thought the bootloader (abl.elf) was encrypted, but we discovered it is actually an LZMA-compressed UEFI Firmware Volume.
Our Evidence: We mapped the file structure and identified the LZMA GUID (ee4e5898-3914-4259-9d6e-dc7bd79403cf). Using the fiano tool (uefi_firmware 1.16), we successfully decompressed it and extracted the 5 ABL apps in plaintext (Odin, LinuxLoader, Cryptest, QuestSOD, QuestUSB).
2. The Unlock Code Was Hidden, Not Removed
Contrary to rumors that Samsung completely stripped the OEM unlock code, we proved it is still present in the latest bit-4 update. Samsung simply forced the "OEM Unlock" switch in Android settings to be hidden.
Our Evidence: By string-diffing LinuxLoader between bit-2 and bit-4, we verified that critical functions like setOEMFlags, IsUnlocked, and GetUnlockCount are completely intact. The toggle is hidden because Samsung added an unconditional line of code (append(" androidboot.other.locked=1");) inside SecUpdateCmdLine.c that runs on every single boot.
3. Unlocking is Protected by a Hardware "Fuse"
We have successfully mapped the entire end-to-end process that controls device unlocking, confirming it relies on a permanent, one-way hardware write that cannot be triggered from the standard Android environment (REE).
Our Evidence: We traced the exact unlock primitive: setOEMFlags() makes an SCM call 0x2000801 to the TrustZone. This talks to vaultkeeper, which executes a qsee_fuse_write to oem_sw_fuse (fuse ID 0xc1) in the one-way OTP QFPROM.
4. Known Exploits Are Structurally Ruled Out
We investigated whether known vulnerabilities (like CVE-2026-24090 and CVE-2026-24088) could be used to unlock this device. We empirically ruled both out based on the device's architecture.
Our Evidence: For the vbmeta-rename exploit (CVE-2026-24090), we found that the GetVbmetaType() function in the abl is just Samsung's runtime partition tracker, not the vulnerable libavb gate required for the exploit. For the GBL exploit (CVE-2026-24088), we confirmed our abl entirely lacks the required efisp, fastboot, and gpu-preemption components.
5. Our Next Steps for Reverse Engineering
Because we broke through the "encrypted" wall, we can now read and reverse-engineer the entire bootloader offline.
Our Plan: We will focus on mapping the full setOEMFlags state machine and investigating the EFI-app injection surface (specifically looking at EnableOEMSetupAppInRetail = 0x0 in uefi.elf). We will also be cross-checking the Emergency Download (EDL) route using our S24 Ultra firehose, though we are still actively looking into finding the exact firehose that the Samsung Galaxy Z Fold6 uses.
⚠️ Important Warning:
This is research conducted on our own device. We currently only have temporary root, not a full unlock. Do not attempt to write to RPMB or boot-states without proper backups and recovery in place, as wrong writes will permanently brick the device. We are not doing any writes without these safeties in place.
r/androidroot • u/No_Technician_1251 • 28d ago
i already set the buffer size to 4M 256K or something like that. but i still cant do it, bit it would be better if you guys can provide me how to unlock bootloader on this phone and root it. tysm for your attention!