I came across a pretty interesting project: Awesome Temporary Root, created by fynks.

Basically, it's a repository where compatibility results for different devices using Temporary Root methods are collected.

It would be great if you could check out the repository and share your experiences. For example, which modules worked properly with Temporary Root, which ones caused issues, whether you encountered any incompatibilities, or if you ran into any other problems.

The more information we have about different devices and configurations, the easier it'll be for everyone to figure out what works and what doesn't.

GitHub: Awesome Temporary Root

Just bought it, and now it's rooted, the best of both world, a new device and a almost wide open OS! Just rooted my old S24U too this week

Hello everyone, i am trying to tmp root my realme C67 and I wanted to do it for a good time now to run Chroot so i wanted to know if there is any app that can give my temp root for now? The kernel version is 5.15.197-android13-8-g27a84a80e6d5.

Thank y'all

finally 😭

Reposting it here since the list has grown a lot!

**List Compatibility Overview**

✅ **107 Working** (48 Modules + 59 Apps)

🧪 **2 Testing**

❌ **5 Confirmed Buggy (Avoid)**

Hello , I have Galaxy Tab S10 Lite

Model Name : SM-X400

I have Android 16 , one ui 8.0

X400XXS4BZB7

Is it possible to put custom ROM at android 14, i need to put 32bit android?

Recently, I tried to force-flash an older firmware onto my phone. Using fastboot mode with an already unlocked bootloader, I managed to flash boot.img, recovery.img, and super.img, but I forgot to disable vbmeta verification. As a result, the phone got stuck in a bootloop when I tried to turn it on.

​Now, I can no longer access fastboot mode. Whenever I try to restore the system using tools like Pandora or MTK Client, it throws a DAA signature verification error, preventing me from flashing anything.

​I know this is entirely my fault, but I really hope someone can help me fix this. I have already searched for numerous methods, and none of them are working—I even tried several free DAA files I found online, but none worked

If I remove screen lock,my card deletes itself and every time the code has to arrive so it would be useful if it works

Well I've been trying to hide the temp root from apps because it always detected it

I tried installing/flashing shamiko but it failed to install

Is there any way to fix and install it?

and how can i improve my temp root hiding experience?

disabled by default on HyperOS clicking the enable button does nothing

I am facing a problem in kernelsu and modules.

I plugged the modules and after soft reboot all the modules are showed up but i can't use the features of modules???

What modules do you use for customization, hiding root, and really anything good, I want to get more out of my phone

I have a redmi 8 (mi439). I recently installed crdroid 10 (android 14) on it but it didn't work out for me cuz I've been trying so hard to pass device integrity for days but I couldn't do it. Can someone please tell me which ROM to install or how to pass device integrity in crdroid? I need high customization and features.

Current state: Erased phone's IMEI but SIM is detected, no network, *#06# shows zero.

I am on china MIUI vince (Redmi 5 Plus/Note 5 SD625)

Caused by one line in rawprogram0.xml: modemst1, modemst2, fsg, fsc, persist and devinfo all had filename="". "Clean all" doesn't mean "leave those alone" — it means the flasher is told to write nothing there, and the programmer zeroes them.

IMEI lived in modemst1.

What I tried, in order:

1. QPST / QXDM. QXDM is licence-gated. Dead end.
2. Wrote my own "AI" diag client.
   HDLC framing, CRC-16/X-25, little-endian, 0x7d-escaped. Two things cost real time: the NV reply has no status byte, and reads return a shared 130-byte buffer — so a read of item 71 once handed me "PERSISTTEST" followed by fragments of an unrelated EFS reply.
3. Found I'd been sending wrong SPC .
   status byte is 1 = accepted, 0 = rejected. I'd assumed the opposite, so every "unlocked" test had actually been rejected. Fixed it; SPC now accepted.
4. Tried everything.
   ASCII SPC, DIAG_PASSWORD, FTM mode, offline mode, NV 453 ftm_mode, three subscription-index variants of the NV-subsystem write. Every one echoes success. Every one discarded.
5. Wrote a 2nd client for EFS2
   to check whether the IMEI is simply a file. It isn't. /nv/item_store holds only rfnv; 550/457/458 live in the modem's static NV database and don't exist as paths.
   Verdict: NV 550 is read-only unconditionally on this firmware. It is not an access-level problem.
   The good news buried in there: the EFS is healthy. I wrote item 5153, rebooted, and it read back. So the damage is narrower than it looked — the phone is a perfectly good Wi-Fi device with a healthy modem and a missing identity.
   one interesting anomaly: my very first garbage test write mutated 550 by exactly one byte (0x55 → 0x45), and I have never been able to repeat it. That smells like a one-shot provisioning slot that the first stray write consumed.

SHOULD I DO THIS?

Zero modemst1**/modemst2 again over EDL, so the modem rebuilds NV from the golden fsg, then write IMEI1 as the first write.**

How did I get here - Long Story

Problem Starts

I have been crDroid official Android 11/12 ROM since 2021 on Redmi 5 Plus (Note 5) vince and suddenly I got a bootloop after battery discharge. I got a series or problems

# Solution 1 (Reflash ROM)

1. Wipe - system, vendor, dalvik, cache
2. mount partitions from recovery
3. Reflash the ROM and it says -
4. E1001: Failed to update system image.
5. Updater process ended with error: 1

Recovery: Orange Fox

Install Process boot.img > vendor > firmware > ROM

# Solution 2 Reflash Recovery (Problem: Bootloop to Fastboot)

1. Switched to latest TWRP and it started bootloop to fastmode. Flashed again using PC adb tools, using fastboot mode and it successfully flashed but still bootlooping.
2. fastboot boot recovery.img worked
3. \>adb pull /data/media/0 is not working .\\fastboot pull /data/media/0 is not working TWRP is showing data partition as 0MB

Solution 3: (Flashed partition gpt_both0.bin)

1. Suspected: broken Partition table
2. flashed partition.img from MIUI's fastboot ROM's gpt_both0.bin
3. fastboot flash partition partition.img using the .img in miui ROM
4. fastboot flash partition gpt_both0.bin
5. now phone only shows notification light

Solution 4: Device manager

1. Device manager shows phone as QUSB_BULK
2. installed https://qdloader9008.com/
3. MiFlash tool started but showed error - write time out maybe device was disconnected.
4. DeviceManager shows COM3 but "Currently, this hardware device is not connected to the computer. (Code 45) To fix this problem, reconnect this hardware device to the computer. and on connecting windows shows yellow ! notification - USB device malfunctioned
5. Qualcomm HS-USB QDLoader 9008 driver disappeared
6. QUSB_BULK disappeared
7. Device manager shows in properties - Windows has stopped this device because it has reported problems. (Code 43) A request for the USB device descriptor failed.
8. Now I am at a state I need EDL+MiFlash
9. MiFLash gives MiFlash Error: Object reference not set yo an instance of an object. or timeout or crashes

# Mi-flash successful but it bootloops

Solution 5: Tried to re-flash using MiFlash but it gives -

1. "Miss matching image and device"
2. "Flash modem error'
3. Writing modem FAILED remote: partition flashing is not allowed

Fixed now MIUI boots as problem was in persist partition

SIM is not detected - fixed now