[ROM][13][OFFICIAL][DynamicPartition][Kernel 4.19] PixelExperience (Plus) for Mi Pad 4 (Plus)[5.19 Updated][Check #2 for FAQ and changelog]

[williamfeng99]

It's been a long time since I've touched my Mi Pad 4, and I just recently noticed there is now a A13 Pixel Experience (Plus) rom the device.

Questions:

1. Can I flash this straight from Official China 10.3.2.0 firmware or should I flash from Xiaomi.eu 10.3.2.0?

2. Would TWRP-3.7.0_12-0-clover-4.4 work well with this rom as recovery (after rom has been flashed)?

3. Is there a A13 recovery available for Clover?

4. Is Play Store Certified with this rom and Magisk?

5. Is overclocking the screen to 90Hz recommended (I have one of the very first batches of Clover bought in the summer of 2018)?

Thank you,

1. Flash this R.O.M. from official 10.3.2 CN firmware will do.
从MIUI 10.3.2中国版底包刷这个系统就行。

2. You can't use T.W.R.P. with the R.O.M. as it uses retrofit dynamic partitions, you have to use the provided PixelExperience Recovery along with the R.O.M. instead.
T.W.R.P.不能用，这个系统用的是虚拟动态分区，必须和PixelExperience的恢复程序一起用。

3. You can find the PixelExperience Recovery from the install guide for Mi Pad 4 on the PixelExperience official website.
恢复程序从官网上小米平板4系统安装教程里下载。

4. Yes SafetyNet works, and yes Magisk also works and it can be sideloaded via the PixelExperience Recovery if that's what you're looking for.
设备认证没问题，Magisk能用，也能从PixelExperience恢复程序里安装。

5. You can overclock the screen but it's not recommended, do so at your own risk.
可以自己超频屏幕刷新率，但是不建议这么做，风险自担。

 

[Ravel7774]

Thank you for this ROM. It has given this old device a new lease of life

 

[Nemix77]

Installed rom and root. So far, everything working very good!

How do I install the boot_75hz.img?

 

[Piccolo1]

I would like to know if you too notice some micro lag

 

[Nemix77]

Been trying this out for the past day. Scrolling smoothness and performance is not there yet. There's lots of micro lag when scrolling and the performance is not as smooth as other roms on Android 13 like LineageOS 20.

On top on all that, there are many bugs and UI inconsistencies with this rom. One of the most annoying bugs for me is when the screen does not turn off sometimes.

Finally, Magisk is very buggy with this rom. Sometimes apps do not detect root prompt, and other times apps that have been given root permission loose root permission.

For the time being I've had to revert back to Pixel Experience Plus 11, which has been working really good for me.

 

[Alcatraz323]

Been trying this out for the past day. Scrolling smoothness and performance is not there yet. There's lots of micro lag when scrolling and the performance is not as smooth as other roms on Android 13 like LineageOS 20.

On top on all that, there are many bugs and UI inconsistencies with this rom. One of the most annoying bugs for me is when the screen does not turn off sometimes.

Finally, Magisk is very buggy with this rom. Sometimes apps do not detect root prompt, and other times apps that have been given root permission loose root permission.

For the time being I've had to revert back to Pixel Experience Plus 11, which has been working really good for me.

1. Scrolling/Installing/transitioning is not maximum boosted with Qti perf service(Los20 using, pix106/sabar_op rom not using) which is conflicted with current more battery saving pixel power manager(EAS kernel). This ROM is battery life preferred
2. If your screen not off, check if you enabled "Screen attention" function previously, it still needs a reboot even you turn it off to work. Blame google if it's not good for it's a pixel phone's function. They have no pixel tablet now.
3. Magisk related SHOULD NOT be considered as a bug for the ROM

 

[Alcatraz323]

Been trying this out for the past day. Scrolling smoothness and performance is not there yet. There's lots of micro lag when scrolling and the performance is not as smooth as other roms on Android 13 like LineageOS 20.

On top on all that, there are many bugs and UI inconsistencies with this rom. One of the most annoying bugs for me is when the screen does not turn off sometimes.

Finally, Magisk is very buggy with this rom. Sometimes apps do not detect root prompt, and other times apps that have been given root permission loose root permission.

For the time being I've had to revert back to Pixel Experience Plus 11, which has been working really good for me.

Also as per FAQ#2 on #2 said
The refresh rate will lock as laggy during the first minutes of starting if you are overclocking

 

[AntoRei]

guys i have problem with persist partition, i tried to install twrp but data is encrypted. What can i do to install persist.img? Thanks

Edit: here solution, thanks Alcatraz
In pe recovery:
Advanced - enable adb
Then On PC:
adb push persist.img /tmp
adb shell
dd if=/tmp/persist.img of=/dev/block/by-name/persist16:09

 

[Dumet]

I have encountered the above error, how to solve it

 

[Alcatraz323]

QPR2 with march security released, lots of updates, check #2 for new FAQ and detailed CHANGELOG

Overclock image NOT uploaded since computer is not aside today, will upload recently about 1-2 days, pay attention if you need that

 

[rchoi999]

Thank you for the update.

 

[Alcatraz323]

QPR2 with march security released, lots of updates, check #2 for new FAQ and detailed CHANGELOG

Overclock image NOT uploaded since computer is not aside today, will upload recently about 1-2 days, pay attention if you need that

Uploaded

 

[djmok]

Thanks for this amazing ROM, really bring a new lease of life to this device.
Also thanks for all the frequent updates.

 

[MRKQATIF]

Thanks for the great ROM.
I installed the January version. It kept giving me errors that Pixel Launcher needs to close. Then, a couple of weeks ago, it hanged and when I pressed the power button for a few seconds: hoping to reboot the tablet, it booted into TWRP.
Now, I can only boot into TWRP or fastboot.
When I am in TWRP, I cannot install a new ROM because of errors with the data partition, which TWRP cannot wipe.

I tried to perform factory reset using the methods here: https://android.stackexchange.com/questions/175885/factory-reset-android-using-adb

Nothing works.

Would someone give me guidance, preferably a step-by-step method to fix the problem and reinstall PE13+?

Thanks in advance.

 

[amityg]

connect to PC and use adb fastboot format userdata and system update TWRP and sideload

 

[Alcatraz323]

Thanks for the great ROM.
I installed the January version. It kept giving me errors that Pixel Launcher needs to close. Then, a couple of weeks ago, it hanged and when I pressed the power button for a few seconds: hoping to reboot the tablet, it booted into TWRP.
Now, I can only boot into TWRP or fastboot.
When I am in TWRP, I cannot install a new ROM because of errors with the data partition, which TWRP cannot wipe.

I tried to perform factory reset using the methods here: https://android.stackexchange.com/questions/175885/factory-reset-android-using-adb

Nothing works.

Would someone give me guidance, preferably a step-by-step method to fix the problem and reinstall PE13+?

Thanks in advance.

There is a BIG "How to flash" on #1

 

[MRKQATIF]

connect to PC and use adb fastboot format userdata and system update TWRP and sideload

Latest rom PixelExperience_clover-13.0-20221110-2311-UNOFFICIAL.zip :
- Android 13.0.0_r23
- January security patch
- 4.19 Nyx Kernel
- OSS cam HAL
- Migrate to Xiaomi power AIDL HAL and common sdm660 powerhint

Download

Installation instructions :
- Perform a backup of your current ROM (optional)
- Use latest 4.19 TWRP created by pix106: (TWRP)
- Perform clean install from TWRP (factory reset, format data and wipe system)
- Flash ROM

What's working:
- All hardware
- Safetynet pass / device certified

What's not working:
Let me know.

Source : https://github.com/PixelExperience
Kernel : clover
Device tree : sdm660

I had no problem to flash the PE ROM

As for the Magisk, I downloaded the latest magisk apk from their website, then changed the file format to .zip, and copied it to my MiPad4Plus

I then rebooted to the recovery, TWRP, installed the magisk.zip, I also did a cache clean, not sure if this helps.

I then rebooted into android, then tapped the magisk that just installed, it gave the update papup stating something like "this is not the lastest blah blah, will update blah blah", I then tapped yes.

After few seconds, magisk finished the update, I install the overlay fix over the module function in magisk

Hope this helps

Thanks for the response; I've tried this option but it does not work; always comes up with "waiting for device" or on other occasions: press any button to turn it off.
The latter seems to come now in response to any action I take via adb.

 

[MRKQATIF]

I followed that guide and it worked with the constant problem that Pixel Launcher needs to close.

At this point, I want to unbrick my device, format everything, and install the latest PE+ on it.

 

[Alcatraz323]

Thanks for the great ROM.
I installed the January version. It kept giving me errors that Pixel Launcher needs to close. Then, a couple of weeks ago, it hanged and when I pressed the power button for a few seconds: hoping to reboot the tablet, it booted into TWRP.
Now, I can only boot into TWRP or fastboot.
When I am in TWRP, I cannot install a new ROM because of errors with the data partition, which TWRP cannot wipe.

I tried to perform factory reset using the methods here: https://android.stackexchange.com/questions/175885/factory-reset-android-using-adb

Nothing works.

Would someone give me guidance, preferably a step-by-step method to fix the problem and reinstall PE13+?

Thanks in advance.

I need to clarify that I'm not in before Feb, and I have fixed the Pixellauncher on pe source for all devices after Feb.

Thanks for the response; I've tried this option but it does not work; always comes up with "waiting for device" or on other occasions: press any button to turn it off.
The latter seems to come now in response to any action I take via adb.

Fastboot instantly shutdown with "press any key" on screen means you are using mismatching connection,like PC is usb3.0 cable is usb2.0 pad is usb2.0

 

[MRKQATIF]

Thanks for the note; I will find another cable and try.