[UNOFFICIAL BUILD] Xiaomi Mi Pad 4 (clover) for /e/OS T

Xiaomi Mi Pad 4 for /e/OS T-1.15


Please see sources and install instructions including recovery here:

Use it at you own risk! I do not own this device so its untested.
Please support the developer(s)!

Just to clarify, is the kernel not 4.19?

in the sources its stated:
ROM Kernel: Linux 4.4

any plans to upgrade to 4.19?

For this you would need to ask the respective developer:


My Xiaomi Mi Pad 4 / 4 Plus (clover) runs excellently with PixelExperience (PE) 13.0 OFFICIAL - but is fully googled as usual with PE. Can you please build a new /e/OS-T ROM? My feedback is self-evident!



10.1" Xiaomi Mi Pad 4 plus

:white_check_mark: 4G LTE (Cat12)
:white_check_mark: Wi-Fi 802.11 a/b/g/n/ac,
:white_check_mark: Bluetooth 5.0
:white_check_mark: GPS, GLONASS, BDS (LTE model only)
:white_check_mark: Accelerometer, gyro, proximity, compass (LTE model only)
:white_check_mark: Charging* 10W wired + Quick Charge 3.0 + PD 2.0

*The original scope of delivery of the Mi Pad 4 only includes a modular charging adapter (5.0 V ~ 2.0 A) and a USB cable (Type A to Type C).

Since the Qualcomm SDM660 Snapdragon 660 (14 nm) chipset supports up to Quick Charge 4.0 via USB-C 3.1, I was able to connect a quick charge adapter with Quick Charge 3.0 and PD 3.0 via the built-in USB-C interface without any problems and thus achieve quick charging of the large Li-Po 8620 mAh.

I have already run various custom ROMs on my Mi Pad 4: CarbonROM (A10)+ MinMicroG, PixelExperience (A13) LineageOS 20.0 (A13) and LineageOS 21.0 (A14). I finally ended up with /eOS-T thanks to :sunglasses:@ronnz98.

I was able to install the e-Recovery and @ronnz98’s e-1.18-t-20231214-UNOFFICIAL-clover without incident. A future manual update can be started without PC and without data loss via e-Recovery from internal memory or USC-C stick via adb sideload.

Hi there, could you please explain where you found E-recovery for the miPad4 (clover)?

Hi there, e-recovery.img is included file e-1.18-t-20231214-UNOFFICIAL-clover.zip by @ronnz98.

You simply have to unzip the *.zip file, for example with 7-Zip, WinZip, etc. under Windows.

Or in Ubuntu/Linux: Open your terminal, use the Linux command unzip. Extract the file to your preferred location. For example:

unzip e-1.18-t-20231214-UNOFFICIAL-clover.zip -d <destination>

1 Like

Ah wow, thanks, I never thought to look there. Are there any advantages to E-recovery over TWRP?

I see the advantage of using e-Recovery in the fact that with e-Recovery a manual update can be made directly on the device using adb sideload - without data loss - i.e. without a PC, for example:

adb sideload *.zip [ from USC-C Stick]

It has interest only IF you have problems with OTA update using TWRP.
In the present case no, as this unofficial build don’t provide OTA updates.

Both can adb sideload from the Computer to the device via USB cable.

Both can work localy on the device without Computer but regarding recovery-e only from internal storage, SDcard or USB stick, when TWRP can explore the entire device tree (old downloaded OTA for exemple).

recovery-e don’t manage .IMG files, only .ZIP
so it can’t update itself or install TWRP, when TWRP can update itself or install recovery-e

recovery-e don’t include file-manager to access to the entire device tree

recovery-e don’t provide MTP file transfert with the file-manager of the computer
so you can’t use it to easily access to internal storage from the PC when Phone screen is broken

recovery-e cannot backup and restore /partitions

… … …

1 Like

This is a basic function of custom coveries.

Please show me how to do a manual update with TWRP Recovery on the smartphone - without data loss + without a host machine (PC). I am not omniscient, so I am happy to learn.

if you already download the zip to the device “internal storage” or “additionnal SDcard”
you can skip the (B) paragraph (that can be done in normal mode or in TWRP mode).

note that in the device tree,

“internal storage” is called “/sdcard” when “physical SDcard” is called “/external_sd” the old OTA are under “/data/lineageos_updates


clic here to see detailled instructions


@piero, thank you for your detailed explanation. Well, how /e/OS is installed via TWRP is generally known to me.

But I wasn’t talking about installing, but about updating without data loss. That is a difference. Hence my question again:


Installing or updating simply replace the /system partition content (and sometime other needed partitions only on devices still maintened by the vendor)
But don’t touch the /data partition (only when upgrading, you may need to wipe or format the /data partition if device tree has change)

Okay, that’s news to me. I will try it out.


I am ashamed that I did not know this TWRP update method before. Until this moment, I assumed that TWRP INSTALL eliminates personal data and additionally installed apps. My recent test on a Galaxy A5 2017 (a5y17lte) proved me wrong. @piero, thanks for the tip.

You may also try OrangeFox, as some TWRP fails to decrypt with recent (12+ ?) Android.
It works exactly the same way.

I am a friend of e-Recovery because it does its work completely in the background. For the ‘normal user’ I see this as an advantage, because he does not have to deal with the numerous options of TWRP or OrangeFox Recovery. It is undisputed that TWRP or OrangeFox Recovery offers the advanced user and enthusiast far more possibilities. But more does not always mean better. It always depends on the user’s requirements.

1 Like