Xiaomi.eu HyperOS 2.0.5.1 Final
Update: 2025/07/27

› Device: Mi 9T Pro / Redmi K20 Pro
› Codename: raphael / raphaelin
› Kernel: V4.14.336-Zundamon-v1.1 (KSU)
› Android: 14

•Credits
•Changelog
•Instructions
•Screenshots
•SuperWallpapers
•ROM: MEGA — PixelDrain
•ROM MD5 checksum: 5907eec79f7de99c4753a1c4b0c14907
•EFE: Download (enable encryption, optional)
•Recovery: Download
•Donate: PayPal — Revolut

WARNING!
› ROM legacy partition
› Encryption is disabled by default
› Data partition is F2FS by default
› Users who do not read the post description will be ignored!
NOTE!
› In this build, it is possible to pass integrity checks at the STRONG level with root using the TrickyStore module with valid keybox.xml

By: @FeLLzMODs
Follow: @FeLLzProjects

64 comments

Show 29 more comments
Yalçın
Which gpu driver best for this rom ?
Camilin 🇨🇴
I tried to install the rom but it doesn't go out of boot animation (I already formatted the data)
bro when new update
Yalçın
When I connect a memory stick via usb otg it transfers max 6 mb/second the first time and is very slow. When I disconnect and reconnect it returns to its normal speed of 36 mb/second. There is such a bug.
Bin Neil
Why do I have to turn my mobile data on and off repeatedly to get an internet connection?
The volume of music or calls via Bluetooth is too low.
unable to pass play integrity? any way to pass it?
How to flash it? i am currently using cr droid a 15, and F2fs parition
Imran Akhtar
How to flash it? i am currently using cr droid a 15, and F2fs parition
Flash the recommended orangefox recovery. Then flash the rom. After done, change partition type to f2fs and wipe data. Then reboot.
Themes error, I cannot grant permission to add topic from memory
sof
You have to format data?
Just read the instructions on the post already lol
sof
You have to format data?
yes. be sure that your data partition is f2fs before booting first time. or else boot will get stuck. format of data after rom install is necessary for clean rom install.
Just had the worse issue i just remove my fingerprint and pattern for lockscreen then i reboot to recovery and it turns to an endless loop to recovery that wont goes through only with orangefox logo wont even boot to system EVEN REMOVING THE BATTERY still just an endless loop to recovery🥶 my laptop just got busted need a help with my friends pc😕..i feel sorry for someone who'll be facing the same issue as me
Yalçın
Hyperos 1 fellzport and hyperos 2 fellzport roms has same theme problem. For example; winrar menu text is not readable in open theme.
@FeLLzMODs
@FeLLzProjects

The EFE (enable encryption) does not work on 2.0.5.1 anymore.

The Reason is, that the file:
/vendor/etc/fstab.qcom
in 2.0.5.1 is different as 2.0.5.0

#########################snipped from /vendor/etc/fstab.qcom OS2.0.5.0

/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,reserve_root=32768,resgid=1065,fsync_mode=nobarrier,inlinecrypt,checkpoint_merge latemount,wait,check,formattable,=ice,wrappedkey,keydirectory=/metadata/vold/metadata_encryption,quota,reservedsize=128M,sysfs_path=/sys/devices/platform/soc/1d84000.ufshc,checkpoint=fs
#########################


########################snipped from /vendor/etc/fstab.qcom OS2.0.5.1

/dev/block/bootdevice/by-name/userdata /data f2fs noatime,nosuid,nodev,discard,inlinecrypt,reserve_root=32768,resgid=1065,fsync_mode=nobarrier latemount,wait,check,formattable,=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,quota,reservedsize=128M,checkpoint=fs
########################


what worked for me, to get ForceEncryption on 2.0.5.1 was, that i copy the patched /vendor/etc/fstab.qcom from 2.0.5.0 to usb-stick, then installed 2.0.5.1 and replaced the original /vendor/etc/fstab.qcom with the patched from 2.0.5.0
## HOW-TO Update from 2.0.5.0 to 2.0.5.1

INFO: My version 2.0.5.0 is encrypted and uses Pattern + Fingerprint.

1. Open Fox Recovery and enter your pattern to decrypt the data
2. Because my phone is encrypted and I also want 2.0.5.1 to be encrypted, and the EnableForceEncryption_20240525.0135.zip does not work on 2.0.5.1:
2. a) Mount Vendor
2. b) Copy /Vendor/etc/fstab.qcom to a USB stick
3. Create a backup with Fox (not necessary, but recommended)
4. Wipe the following partitions:
- Dalvik / ART Cache
- Cache
- Cust
- System
- Vendor
5. Install ROM 2.0.5.1
6. Since my phone is encrypted and I also want 2.0.5.1 encrypted:
6. a) Mount Vendor
6. b) Copy back fstab.qcom from the USB stick to /Vendor/etc/fstab.qcom
7. Reboot phone - finish -
8. My phone booted, and all my apps with fingerprint + pattern worked perfectly :-)
Process: com.android.mms
PID: 25608
UID: 10132
Frozen: false
Flags: 0x28c9bee5
Package: com.android.mms v160002070 (16.0.2.70)
Foreground: Yes
Process-Runtime: 273
Build: Xiaomi/raphael/raphael:14/UKQ1.240624.001/OS2.0.5.1.FLZCNXM:user/release-keys
Crash-Handler: com.android.internal.os.RuntimeInit$KillApplicationHandler
Loading-Progress: 1.0
Dropped-Count: 0

java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
at android.database.DatabaseUtils.readExceptionFromParcel(Unknown Source:57)
at android.database.DatabaseUtils.readExceptionFromParcel(Unknown Source:11)
at android.content.ContentProviderProxy.call(Unknown Source:36)
at android.provider.Settings$NameValueCache.putStringForUser(Unknown Source:69)
at android.provider.Settings$System.putStringForUser(Unknown Source:73)
at android.provider.Settings$System.putStringForUser(Unknown Source:7)
at android.provider.Settings$System.putStringForUser(Unknown Source:1)
at android.provider.Settings$System.putIntForUser(Unknown Source:4)
at android.provider.Settings$System.putInt(Unknown Source:4)
at kf.o0.h(Unknown Source:12)
at kf.z0.i(Unknown Source:3)
at x2.d.run(Unknown Source:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1251)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:668)
at java.lang.Thread.run(Thread.java:1012)

Crash.how solve it? I installed several different versions and it didn't work. This error occurred after testing the installation of version 17.
How to pass integrity in this rom?
Show next 14 comments