Development [ROM][13][UNOFFICIAL][alioth] PixelExperience for Redmi K40/Poco F3/Mi 11X [AOSP]

[lukasz_m]

Hello,

After a lot of work done by lzgmc, jayanthk and after some tests, I have built an unofficial continuation of PE for alioth.

Motivation:
- I have the device and wanted to have last security patches
- I want to have Netflix, Google Wallet, McDonald app working

Changes:
- Updated binaries from the most recent global alioth image
- All updates from PixelExperience, including security updates
- Share the same kernel as munch
- Publish differential OTA images

Changelog:

PixelExperience_Plus_alioth-13.0-20230926-0859
- Based on 2023.09 PE update
- Update kernel to the most recent version (4.19.295)
- Use drivers from MIUI Global 14.0.8.0
- Performance fixes
- Enabled OTA

Older releases deleted, but maintaned since 2023.04.

Image (initial, flash next by Updater app)):

https://gitlab.com/lukasz1992-pe/al...-13.0-20230926-0859-OFFICIAL.zip?inline=false

Sources:

https://gitlab.com/lukasz1992-pe/

Instruction:
- you have to flash 2023.09 image first
- use updater app to get next updates

FAQ:

Q: Do you have the device?
A: Yes, I use my ROM on my device

Q: How to report bugs?
A: Write about them here

Q: I do not trust your builds
A: No problem, build image yourself from source or do not use this rom

Q: What about official support?
A: My ROM is not official (depsite OFFICIAL in name of images). There is already an official maintaner, but has not released images yet.

Q: Are there automatic updates?
A: Yes, you will receive notification when update is ready. Install it from updater app.

Q: Why do you publish incremental updates
A: I wanted to test this mechanism - they take less space and I like them

Q: Incremental update does not work
A: Do not flash other kernel, do not modify files. If you did it - go back to the 2023.05 release and start again

Q: Is this a vendor-boot ROM?
A: No

Q: Is there any guarantee?
A: xD

 

[cyanGalaxy]

You accidentally used the Question-tag for this thread

 

[cobolatrix]

Hi, I'm on the 20230420-1753 build but when I try to adb sideload the from-20230420-1753-to-20230516-2127 update I'm getting this error, I'm using the provided recovery image:

Supported API: 3
Finding update package...
Installing update...
Step 1/2
Error applying update: 20 (ErrorCode::kDownloadStateInitializationError)
ERROR:    recovery: Error in /sideload/package.zip (status 1)

Install completed with status 1.
Installation aborted.

I also tried with OrangeFox Recovery, I didn't get this error there but upon reboot I noticed that my version number didn't change.

Also, thanks a lot for keeping PE on the Poco F3 alive, I briefly tried MIU14 but I found it too bloated for my taste.

 

[lukasz_m]

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?

Please also confirm you do not have magisk etc.?

 

[cobolatrix]

Could you enable ADB, dump the log from /tmp/ and paste it to pastebin?

Please also confirm you do not have magisk etc.?

Sure, here they are: https://pastebin.com/M5kvav40 https://pastebin.com/VRkbgbvh

I also don't have magisk or anything like that installed.

 

[lukasz_m]

[DELETED]

 

[lukasz_m]

Okay, released a new, fixed update - I tested it, it should work

 

[cobolatrix]

I flashed the new update and its been working fine, thanks for you work!

 

[tdw197]

I flashed the full image on GDrive linked above - thanks very much, works really well. But I think I'm being a blind and can't see the May update? Where do I find that...

 

[lukasz_m]

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

 

[tdw197]

Everything okay with your eys. We have some defects with may update again Currently not repaired yet, will publish it when I am sure everything works.

Ah great, thought I was asking a stupid question

Thanks for all your work - had semi-retired my F3 and just bumped it from 12 to 13, its really fast and smooth.

 

[lukasz_m]

Update - 2023.05 image was reuploaded

 

[nnoca]

Sorry if this is a noob question. Is it possible to dirty flash to this 2023.05 from the latest official build?

And thx for keeping this device updated, really appreciate what you're doing here.

 

[lukasz_m]

hi, yes - you can do it

 

[ciottaciotta]

Hey Lukasz,
thanks for this work you are doing for all of us.
I I'm on last OFFICIAL PE build from lzgmc and I'm tying to dirty flash with ADB your ROM.
I receive this error whenever I run the ADB sideload comand but Maybe I did something wrong...can you help me ?
Thanks in advance

My version is:
PixelExperience_alioth-13.0-20230119-0644-OFFICIAL

Enabled ADB.
Now send the package you want to apply to the device with "adb sideload <filename Supported API: 3
Finding update package...
Installing update... Step 1/2
Error applying update: 7 (ErrorCode::kInstallDeviceOpenError ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1. Installation aborted.
@lukasz_m

 

[lukasz_m]

It happens when update was interrupted. I do not remember exact names, but please do from ADB:
mount /dev/block/by-name/metadata /metadata rm -rf /metadata/ota*
reboot to recovery and try again

 

[ciottaciotta]

mount /dev/block/by-name/metadata /metadata

rm -rf /metadata/ota*

Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.

I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device

Than what I have to do ?
thanks in advance for your time.

 

[blonderulez]

Sry Lukasz but I don't understand how to run these commands.
I'm surely missing somethig, so it's my ingorance.

I boot the phone and connect it to my pc. I run the "adb devices" command from the platform-tools folder using "command prompt" as administrator.
I get this so ADB is running properly:
List of devices attached
506a3bf9 device

Than what I have to do ?
thanks in advance for your time.

First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

 

[ciottaciotta]

First open a shell on your device by entering on your PC: adb shell
Then then you can give shell commands like in the posting above

OK thnaks for the explanation...
After giving "mount /dev/block/by-name/metadata /metadata" command i get:
"mount: bad /etc/fstab: No such file or directory"

When I try to browse it with "cd" and "ls" commands i can browse till /dev/block/by-name/ and I see metadata folder with "ls" than when i go for "cd metadata" i get this "/dev/block/by-name/metadata: Not a directory"

 

[lukasz_m]

Does this work?

mkdir /tmp/metadata
mount /dev/block/by-name/metadata /tmp/metadata
rm -rf /tmp/metadata/ota*