Development [UNOFFICIAL][ROM][13][renoir] PixelExperience [AOSP] [2023-04-04] - Xiaomi Mi 11 Lite 5G

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Mi 11 Lite 5G [renoir]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Fingerprint reader
Face unlock
NFC
Lights
Sound/vibration
Known issues
You tell me
FLASH GUIDE
Note that if you can't use bluetooth audio. Try to follow here.
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download
thirteen : [ SourceForge | Selfhosted ]
thirteen_plus : [ SourceForge | Selfhosted ]
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Maintainer Channel
Maintainer Chat (CN/EN)​
Changelog:
Apr, 04, 2023 Update
Hoya~ Greetings! Here is Hana. Bring you latest PixelExperience update. Here is a berif introduction to this update.
Notice:
1. Since there are a lot of changes in kernel side. You must to flash boot, dtbo, vendor_boot manually to make sure use latest aosp recovery that can correctly flash the update package.
Improvements:
1. Improved memory performance: The available memory has been significantly improved, and the average usage has been reduced by 15-20% compared to the previous version.
2. Move to erofs: Five partitions switched to erofs, which helps to improve performance.
3. Power saving optimization: The kernel uses a series of patches to reduce power consumption
4. Overall system smoothness improvements
5. Merge March 05, Security Patch.
Fixes:
1. Bluetooth issue has been fixed.
2. Google Recorder has been fixed.
3. Alipay/WeChat fingerprint payment has been fixed.
Details:
1. Sync latest source code ( Android 13 QPR2 )
2. Initial PixelExperience Plus Edition build.
3. Move to OSS aptX audio ( Also fixed bluetooth )
4. Move { system | vendor | system_ext | product | odm } partitions to erofs
5. Backport latest erofs features from linux-6.1
6. Enable erofs per cpu decompression feature ( with high priority kthread )
7. Backport Data Access Monitor ( DAMON ) from linux mainline
8. Enable DAMON-based reclaim and lru sort.
9. Backport MutliGen LRU from Chromium Project
10.Enable MutliGen LRU support by default.
11.Kang zram driver from linux-5.15
12.Enable ZRAM WriteBack && Deduplication.
13.Port LZ4 1.9.x FAST_DEC_LOOP and enable it.
14.Set zram compression algorithm and erofs decompressor to lz4 by default.
15.Backport Lazy RCU feature and enable by default.
16.Backport a series of userfatalfd/mm changes from upstream kernel.
17.Switch to new mm locking api to ensure memory safety.
18.Fixed Google Recorder.
19.Update blobs from renoir CN V14.0.8.0.
20.Disable a series of log spam.
21.Move to power effiency workqueue.
22.Label more selinux denieds
23.Kernel components merged to CLO tag 'LA.UM.9.14.r1-21300-LAHAINA.QSSI12.0'
24.Provide both sourceforge and selfhosted mirrors
Android OS version: 13
Security patch level: March 2023
Build author/Device Maintainer: EndCredits
Device Source code: https://github.com/EndCredits/android_device_xiaomi_renoir
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09

the photos taken with any camera application show different tones than usual and in certain cases of lighting shows certain black lines only in this rom

spotify crashes instantly not working

RichyValents13 said:
spotify crashes instantly not working
Click to expand...
Click to collapse
For me it's working ( From Play Store )

RichyValents13 said:
the photos taken with any camera application show different tones than usual and in certain cases of lighting shows certain black lines only in this rom
Click to expand...
Click to collapse
Will integrate a new Camera App in the next version

Hello! Flashed the rom yesterday and so far, it's very smooth! I haven't noticed any major stutters or issues so far. The only thing that doesn't work is the Android easter egg. Whenever a cat tries to appear, the program just crashes.
You've done a great job, so keep it up!

MrDoctor175 said:
Hello! Flashed the rom yesterday and so far, it's very smooth! I haven't noticed any major stutters or issues so far. The only thing that doesn't work is the Android easter egg. Whenever a cat tries to appear, the program just crashes.
You've done a great job, so keep it up!
View attachment 5884621
View attachment 5884377
Click to expand...
Click to collapse
I recommend doing the clean installation, installing the bto vendro files and others, formatting everything

Great optimization work in the new version 04/04/2023, but if for the previous version it had something better why at least Skyline Edge opened me and ran the games wonderfully and now it crashes only when opened

Guillermo55 said:
I recommend doing the clean installation, installing the bto vendro files and others, formatting everything
Click to expand...
Click to collapse
That's what I did when I first flashed, so I don't think it's just a personal problem

I have been running on the previous version of Pixel Experience Plus for quite some time now. When I saw this, I thought to myself that it might be time to update. (Been experiencing some performance issues the last couple of days.)
I went ahead and downloaded ROM.zip, boot.img, vendor_boot.img, and dtbo.img.
Then did the following:
1. Put my phone into FastbootD mode.
2. fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (when I tried fastboot flash boot_ab boot.img I received an error, that there was no such directory.)
3. fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
4. fastboot flash dtbo dtbo.img
5. Put my phone into recovery mode
6. Apply update from ADB
7. adb sideload "PixelExperience_Plus_renoir-13.0-20230404-1454-UNOFFICIAL.zip"
It went ahead and started to install, but at 47%, I got the "Total xfer: 1.00" message and my phone said "Error in sideload/package zip (status 1).
After doing the process a few times, I went ahead and installed the previous version using the same process as listed above and that worked.
Anyone know what the problem is? Would I have to install the MIUI firmware and then start this process all over again?
Any help would be greatly appreciated.

Which firmware version is recommended for this rom & can one dirty flash from eg Banana droid rom 13/3/23 pls? I'm finding the latter doesn't fully unlock the screen on my Mi 11 5G Lite. I get a strange vigentting type effect quite often, before tapping home button again fully opens up the screen.......its like the fingerprint sensor is not always repsonding on banana droid & that was installed with a clean install with all dtbo, rom & vendor files....

Hammerlig said:
I have been running on the previous version of Pixel Experience Plus for quite some time now. When I saw this, I thought to myself that it might be time to update. (Been experiencing some performance issues the last couple of days.)
I went ahead and downloaded ROM.zip, boot.img, vendor_boot.img, and dtbo.img.
Then did the following:
1. Put my phone into FastbootD mode.
2. fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (when I tried fastboot flash boot_ab boot.img I received an error, that there was no such directory.)
3. fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
4. fastboot flash dtbo dtbo.img
5. Put my phone into recovery mode
6. Apply update from ADB
7. adb sideload "PixelExperience_Plus_renoir-13.0-20230404-1454-UNOFFICIAL.zip"
It went ahead and started to install, but at 47%, I got the "Total xfer: 1.00" message and my phone said "Error in sideload/package zip (status 1).
After doing the process a few times, I went ahead and installed the previous version using the same process as listed above and that worked.
Anyone know what the problem is? Would I have to install the MIUI firmware and then start this process all over again?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
As far as I knew & always read the adb sideload process always shows as getting to 47% but after a pause, the abd etc program goes to the next line and on rebooting the phone, the new rom is present & working...

TheDon13 said:
Which firmware version is recommended for this rom & can one dirty flash from eg Banana droid rom 13/3/23 pls? I'm finding the latter doesn't fully unlock the screen on my Mi 11 5G Lite. I get a strange vigentting type effect quite often, before tapping home button again fully opens up the screen.......its like the fingerprint sensor is not always repsonding on banana droid & that was installed with a clean install with all dtbo, rom & vendor files....
Click to expand...
Click to collapse
I have the 14.0.6.0 firmware and I have no problems with the rom. Also it's the best if you always clean flash if you're moving from another rom

TheDon13 said:
As far as I knew & always read the adb sideload process always shows as getting to 47% but after a pause, the abd etc program goes to the next line and on rebooting the phone, the new rom is present & working...
Click to expand...
Click to collapse
But as far I could see, the transfer just stopped? My phone said there was an error, and when I tried to reboot the phone, it came up with the MIUI logo and then went into Fastboot.
MrDoctor175 said:
I have the 14.0.6.0 firmware and I have no problems with the rom. Also it's the best if you always clean flash if you're moving from another rom
Click to expand...
Click to collapse
Isn't a clean flash just booting the boot.img, vendor_boot.img and dtbo.img?
Would it be better to flash the MIUI rom and then follow this process once again? I must have done something wrong, since it's working for everyone else.

Hammerlig said:
But as far I could see, the transfer just stopped? My phone said there was an error, and when I tried to reboot the phone, it came up with the MIUI logo and then went into Fastboot.
Isn't a clean flash just booting the boot.img, vendor_boot.img and dtbo.img?
Would it be better to flash the MIUI rom and then follow this process once again? I must have done something wrong, since it's working for everyone else.
Click to expand...
Click to collapse
As long as I know, a clean flash is flashing the mandatory files, format data and then flash the rom. How I did it is flash boot_ab "boot.img", flash vendor_boot_ab "vendor_boot.img", flash dtbo "dtbo.img", boot to recovery, format data, flash from adb, adb sideload the package, wait and then reboot.

will this rom be continued after Xiaomi abandones the beta/dev rom's after the 21st of april ?

my bluetooth isnt working... do i need to update firmware?

Does this rom have call recording built in?

Hammerlig said:
I have been running on the previous version of Pixel Experience Plus for quite some time now. When I saw this, I thought to myself that it might be time to update. (Been experiencing some performance issues the last couple of days.)
I went ahead and downloaded ROM.zip, boot.img, vendor_boot.img, and dtbo.img.
Then did the following:
1. Put my phone into FastbootD mode.
2. fastboot flash boot_a boot.img
fastboot flash boot_b boot.img (when I tried fastboot flash boot_ab boot.img I received an error, that there was no such directory.)
3. fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
4. fastboot flash dtbo dtbo.img
5. Put my phone into recovery mode
6. Apply update from ADB
7. adb sideload "PixelExperience_Plus_renoir-13.0-20230404-1454-UNOFFICIAL.zip"
It went ahead and started to install, but at 47%, I got the "Total xfer: 1.00" message and my phone said "Error in sideload/package zip (status 1).
After doing the process a few times, I went ahead and installed the previous version using the same process as listed above and that worked.
Anyone know what the problem is? Would I have to install the MIUI firmware and then start this process all over again?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I tried to install Pixel Experience Plus, which is also what I tried to install last time. After the same thing happened again, I tried installing the normal Pixel Experience and that was successful. Don't know if it was just me having issues installing the Plus version.
j0k1n9 said:
my bluetooth isnt working... do i need to update firmware?
Click to expand...
Click to collapse
My Bluetooth isn't working either. I turn it on and then it just turns off right away. I flashed boot.img, vendor_boot.img and dtbo when installing. Happens for me on the regular version of PE.

Hammerlig said:
I tried to install Pixel Experience Plus, which is also what I tried to install last time. After the same thing happened again, I tried installing the normal Pixel Experience and that was successful. Don't know if it was just me having issues installing the Plus version.
My Bluetooth isn't working either. I turn it on and then it just turns off right away. I flashed boot.img, vendor_boot.img and dtbo when installing. Happens for me on the regular version of PE.
Click to expand...
Click to collapse
I installed MIUI 14.0.6 EEA, and then went over the process with this version of PE Plus. Flashed succesfully and seems to be working. Nice!

Related

12-19 - ViperExperience Beta 14 | Android 13 | November 2022 Security Patch |GSI

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ViperExperience 12L GSI for U12+
"Choose your flavor! - The next Generation Viper ROM"
Dear Community,
Venom ROMs takes the next big step for your HTC, as well as other Treble A/B devices out there! You want Android 11, but don't want to miss out on the hardware benefits of your HTC U12+? Or you want to enjoy all of your beloved HTC Apps on another OEM? Then we have the best of both worlds for you today (or very soon)! Decide for yourself between an Android Stock Experience, or an HTC Sense Experience by choosing between Pixel Launcher and HTC Sense 10 UI Launcher. On your HTC U12+ you can in addition continue to use your popular HTC features like HTC Edge Sense, HTC FaceUnlock and the HTC Camera!
We at Venom ROMs are using the AOSP GSI based on Android 11 to bring you the best HTC features paired with the latest Android AND Pixel experience from Android 10.
Thanks to @phhusson for his Treble experimentations repos, @JEANFRIVERA, @5m4r7ph0n36uru, @Captain_Throwback, @MassStash, @donmarkoni for all tests you did for me to make this ROM.
mikalovtch
Must have unlocked bootloader from htcdev.com or factory S-OFF
Download Viper Experience 11 GSI from Androidfilehost.com
Download „vbmeta_noverity.zip“ from Androidfilehost.com
Download latest TWRP from #2 post or Download latest PBRP from here: PBRP
Boot your Device in Bootloader Mode
Boot to TWRP or PBRP, using the following command:
Code:
fastboot boot nameoftwrpimage.img
Rename „vbmeta_noverity.zip“ to „update.zip“ and place it inside your adb/fastboot folder
Push „update.zip“ to your device, using the following command:
Code:
adb push update.zip /update.zip
Make sure you are on slot A on reboot page of TWRP or PBRP if not switch to slot A and fasboot boot twrp.img again
Flash „update.zip“ from recovery UI
Reboot to Download from recovery UI
Erase userdata and system using the following commands: (THIS WILL FORMAT INTERNAL STORAGE!)
Code:
fastboot erase userdata
and:
Code:
fastboot erase system
Flash Viper Experience 10 GSI, using the command:
Code:
fastboot flash system nameofimage.img
Rebootyour device, using the command
Code:
fastboot reboot
Setup and enjoy an mew ROM on your HTC U12+!
​
XDA:DevDB Information
12-04 - ViperExperience Beta 12 | Android 12L | April 2022 Security Patch |GSI , ROM for the HTC U12+
Contributors
mikalovtch, JEANRIVERA
Source Code: https://github.com/phhusson/treble_experimentations
ROM OS Version: Android 12L
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 9 Pie
Based On: AOSP HTC Sense
Version Information
Status: Beta
Beta Release Date: 2020-12-22
Created 2020-03-07
Last Updated 2020-12-22
​
Prerequisites
PIE_noverity_vbmeta_both_slots-TWP.zip: This zip patches the stock vbmeta for BOTH slots to ensure the device will boot after flashing the GSI. The zip in the OP only patches slot A, so you would have to ensure you are on slot A when flashing the system image. This zip allows either slot to be used. Thanks @The_Walking_Playground for posting the updated zip!
Fixes
UPDATE-BeyondStock™_U12+_Exodus_Vendor_Fixes-CPTB-signed.zip: This zip patches the vendor partition on U12+ and Exodus devices to fix Bluetooth streaming/headset compatibility, and enables exFAT support with the stock and BeyondStock™ kernels (NOTE: The exFAT portion of this fix is no longer needed, but has no negative side effects).
Patches
UPDATE-BeyondStock™_Header_Patch_U12+_Exodus-CPTB-signed.zip: This zip patches the boot.img header of the installed kernel so that decryption will work in permanently installed TWRP. This zip should be used if you're using a custom kernel that doesn't require patching for touch.
UPDATE_BeyondStock™_U12+_Exodus_Remove_Forced_Encryption_CPTB_signed.zip: This zip disables forced encryption on the device so that it doesn't automatically get encrypted after Formatting Data in TWRP.
Custom Recovery
Official TWRP for U12+: This is the recommended TWRP version to use with the ROM, with full Android 11/12 decryption support.
Kernels
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus-signed.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP older than 3.4.0, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
UPDATE-BeyondStock™-Kernel-Pie-v0.02-U12+_Exodus_TWRP_3_4_0_CPTB.zip: This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP 3.4.0 (and higher), and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
[MANUAL] Fix CTS Profile Mismatch
Initial situation: most GSIs are rooted to a certain extent. This also applies to the AOSP GSI, which is the basis of our ViperExerience ROM.
Precondition: To correct the CTS mismatch, it is necessary that Magisk is installed.
If the precondition is fulfilled, proceed as follows:
Install the Magisk modules "Busybox" from Osmosis, and "MagiskHide Propst Config" from Didgeridoohan
After a device restart, open a Terminal App on your HTC U12+ and go through the following steps
Request root privileges by typing
Code:
su
Start the Props module by typing
Code:
props
Type
Code:
1
to set a new fingerprint for the device
Follow the instructions in order by selecting
Code:
f
and
Code:
7
(for HTC).
finally type
Code:
4
(for U12+ Pie).
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from here: https://github.com/CaptainThrowback/android_device_htc_ime/releases
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either
4. Download BeyondStock™-Kernel This zip installs the BeyondStock™ kernel which has patched touch for permanently installed TWRP, and patches the boot.img header so that decryption will work. It also supports the stock exFAT implementation.
5a. If you want to be rooted flash the magisk.zip
5b. If you don't want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
Thanks to @JEANRIVERA
reserved
reserved3
reserved4
reserved5
reserved6
Support
Hi users, I was a noob once too, believe it or not I had questions & stupid questions too but I was never afraid to ask, in my way to be part of this amazing team I have known all kind of Devs, with different levels of friendliness , but being honest in some way or another I have learned from all of them a little something, Now I want to give back to the community as much as I can, I am no Dev, but I do know a trick or two, if I don't know the answer to your questions, I will try my best to get an answer for you from the Team.
The instructions in the OP have been updated for better understanding and corrected some points, if anyone has tried unsuccessfully to flash this ROM please follow the updated instructions, if anyone have trouble or not booting device please feel free to ask, I will try to guide anyone as much as I can and as friendly as possible. I see there is 73 downloads on AFH of the ROM but only few users reported their experience here, maybe if you are afraid to ask, don't be, if you navigate through the thread you will see only friendly responses, and I will try my best to keep it that way, don't be afraid to tag me for support
And I'll take this one, just for the kicks.
I am running android 8 with viper 2.0 and i tried to update to this but ADB says that my file system is read-only. What is the recommended course of action?
Code:
adb: error: failed to copy 'update.zip' to '/update.zip': couldn't create file: Read-only file system
I read elsewhere that 'adb root' would be needed but i figured it would be better to ask here instead of following some random post about a somewhat similar situation.
First off: don't install this ROM on Android 8 firmware. It's an Android 10 GSI and all development an testing has been done on the latest EMEA firmware.
So the way to go from ViperU12+ would be to go back to full stock unsung a RUU and upgrade to Android Pie. This is to make sure you start from the correct base and environment. Then boot the device and copy the vbmeta zip onto /sdcard. Then reboot to bootloader and boot to TWRP, and follow the instructions from post #1 to the point.
Use the latest TWRP from @Captain_Throwback, found here: https://github.com/CaptainThrowback/android_device_htc_ime/releases/tag/3.3.1-2
Sent from my Pixel 4 XL using XDA Labs
it should be: 9 Reboot to Download from TWRP UI not
9 Reboot to bootloader from TWRP UI
on Production Units in Bootloader you get an error:
FAILED (remote: Erase is not allowed on PRODUCTION device)
This ROM is been running quite fantastic for me, I am so excited to help test and get this released for everybody to use! Can't believe we have Android 10 on this u12 plus Beast, it's so amazing! LOL thank you so much @mikalovtch, @JEANRIVERA, @Captain_Throwback, &
Sent from my HTC U12+ using Tapatalk
Oh man, you`ve done brilliant work:highfive::good:
it is almost perfect, butter smooth and fully functional except few bugs.
some issues are:
1. time and date automatically reset to 2020.03.07 4:47 after reboot, which can be quite annoying.
2. edgesense squeeze gesture feedback is weird. it`s not like the feedback of power btn but vibrating.
3. edgesense setting does not show in the settings.
some Pro tips:
1. flash system.img via twrp or via usb under DOWNLOAD mode. you can not flash it under BOOTLOADER mode.
2. you can access edgesense settings by this method:
goto Setting.Apps, show all system Apps and find out edgesense service app. In the detail screen(where you can clear the cache and force stop, idk the exact term), tap Advanced, Additional settings in the app.
3.kirisakura kernel tested, all good.
btw i use China version u12+, hope this will help you.
Thanks you bro!
issue has been fixed
JEANRIVERA said:
without the vbmeta.zip the ROM will not boot at all, the instructions fail to specify you must be on slot A to flash the vbmeta.zip and ROM, instructions will be updated soon, if you are on slot B another vbmeta zip should be used.
Click to expand...
Click to collapse
thank you! but i still boot without flashing vbmeta.
neoncloud4399 said:
thank you! but i still boot without flashing vbmeta.
Click to expand...
Click to collapse
is your device S-OFF? that would be the only possible reason it boots
JEANRIVERA said:
is your device S-OFF? that would be the only possible reason it boots
Click to expand...
Click to collapse
no, it still s-on.
i followed this procedure:
clear system, flash system, clear userdata under twrp
flash vbmeta.zip under twrp By sideload
reboot, failed to boot, show warning messages.
run fastboot oem rebootRUU to ruu flash mode and downgrade to 1.21
fastboot erase persist
boot to 1.21 China then upgrade to PIE.
boot to DOWNLOAD, erase system, userdata, flash system both system_a and system_b and it boots.

[ROM][11.0][marlin] PixelExperience [AOSP][OFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PixelExperience for Google Pixel XL [marlin]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 11.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Lights
Sound/vibration
Known issues
Nothing yet
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 11.0.0_r46
Security patch level: December 2021
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_marlin
https://github.com/PixelExperience-Devices/kernel_google_marlin
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_marlin
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Reserved
Niceeeeee!!! I have been waiting too long for this <3
Awesome! Thanks alot for this! Couple of questions before flashing. Does it include stock google camera? Does it retain unlimited photos storage and also is it possible to flash over stock without losing all data? I know the last isn't recommended, but would be nice.
BoboBrazil said:
Awesome! Thanks alot for this! Couple of questions before flashing. Does it include stock google camera? Does it retain unlimited photos storage and also is it possible to flash over stock without losing all data? I know the last isn't recommended, but would be nice.
Click to expand...
Click to collapse
1. The camera included is one provided by cstark. It is a modded version of Google Camera which includes features from later Pixels, but should still hold the original features.
2. Yes, you can still upload unlimited photos in original quality.
3. Unfortunately, it is not possible to directly flash PixelExperience over stock. In fact, 11 requires a full device repartition. It's easy as flashing a .zip file before the ROM to do so.
If you have any more queries, make sure to let me know!
PixelExperience - OFFICIAL | Android 11
Updated: 14/03/'21
Links:
Sailfish [1.06GB]
Marlin [1.06GB]
️Telegram Group
Disclaimer:
This build requires you to re-partition your device in order to flash.
Kindly read the Pre-install instructions before flashing.
Changelog:
Initial stable release for Google Pixel/XL
PixelExperience (Plus Edition) - OFFICIAL | Android 11
Updated: 14/03/'21
Links:
Sailfish [1.06GB]
Marlin [1.06GB]
️Telegram Group
Disclaimer:
This build requires you to re-partition your device in order to flash.
Kindly read the Pre-install instructions before flashing.
Changelog:
Initial stable release for Google Pixel/XL
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
kartikb said:
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
Click to expand...
Click to collapse
Hey dude! (or dudette), would you please walk me throught the installation process? I'm a noob on flashing custom roms, and i'm facing some difficulties flashing this rom. I downloaded the repartition zip form the link, and I'm flashing it throught twrp recovery and then the rom zip file but it gets stuck on a bootloop. What am I missing? (Please forgive any misspellings, I'm also a noob at english)
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Great great work! Will surely be trying this at the first available free time!
kartikb said:
Flashed and working fine. Thanks a lot for your hard work, still going through the setup but so far so good. Will report if I come across anything funny.
Click to expand...
Click to collapse
Hi. Are you able to download Google Camera from playstore and does it work fine?
Is selinux enforced? Tks
Going through Pixelexperience site, came across two versions for Pixel XL- Stable android 11 and Stable Android 11 (plus edition).
What's the difference between the two? Apologies if this is common knowledge, but this is the first time for me using Pixelexperience.
pantsaregood said:
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Click to expand...
Click to collapse
I'm facing with this issue too. Have done repartitioning successfully. :'(
lmvuong1997 said:
I'm facing with this issue too. Have done repartitioning successfully. :'(
Click to expand...
Click to collapse
I have solved the issue, this is what i have done:
- Boot into twrp from fastboot, using the latest twrp 3.5.0
- Advanced Wipe (system, dalvik, data), change active slot and then repeat (just to be sure)
- adb sideload the repartitioning zip
- Format data (where you type 'yes') then reboot into twrp
- (From Kartik Billimoria on Telegram)Push rom zip file to /sdcard via adb push command then flashed the rom
- Change to inactive slot (the slot you flashed the rom), reboot to fastboot to make sure the active slot has changed (for me it has not), if not change it by 'fastboot set_active a' (or b). Reboot.
josegarfer01 said:
Hey dude! (or dudette), would you please walk me throught the installation process? I'm a noob on flashing custom roms, and i'm facing some difficulties flashing this rom. I downloaded the repartition zip form the link, and I'm flashing it throught twrp recovery and then the rom zip file but it gets stuck on a bootloop. What am I missing? (Please forgive any misspellings, I'm also a noob at english)
Click to expand...
Click to collapse
It will not work via TWRP recovery.
1. Kindly go on the downloads page and install the PE recovery.
Code:
fastboot flash boot recovery.img
(It may bootloop once or twice, but then it will show up in PE recovery)
2. Go into Apply update via ADB.
Code:
adb sideload repartition-ogpixel-**gb.zip
3. Factory Reset/Wipe Data.
4. Apply update via ADB and sideload the ROM.
Code:
adb sideload PixelExperience-**.zip
5. Reboot and wait patiently.
Hope this helps.
pantsaregood said:
Flashing both the regular and plus versions doesn't seem to work for me. They both get to 35%, then I get:
28 (ErrorCode::kDownloadOperationExecutionError)
Error in /sideload/package.zip (status 1)
Click to expand...
Click to collapse
lmvuong1997 said:
I'm facing with this issue too. Have done repartitioning successfully. :'(
Click to expand...
Click to collapse
If you are still in difficulty, follow the mentioned post below:
PixelBoot said:
It will not work via TWRP recovery.
1. Kindly go on the downloads page and install the PE recovery.
Code:
fastboot flash boot recovery.img
(It may bootloop once or twice, but then it will show up in PE recovery)
2. Go into Apply update via ADB.
Code:
adb sideload repartition-ogpixel-**gb.zip
3. Factory Reset/Wipe Data.
4. Apply update via ADB and sideload the ROM.
Code:
adb sideload PixelExperience-**.zip
5. Reboot and wait patiently.
Hope this helps.
Click to expand...
Click to collapse
gverma1 said:
Going through Pixelexperience site, came across two versions for Pixel XL- Stable android 11 and Stable Android 11 (plus edition).
What's the difference between the two? Apologies if this is common knowledge, but this is the first time for me using Pixelexperience.
Click to expand...
Click to collapse
PixelExperience Plus Edition provides extra tweaks that you can apply.
One that comes to mind is further customization to the notifcation bar to include network stats.
If you're up for extra customization from ROMs like LineageOS, consider flashing Plus instead.
gverma1 said:
Hi. Are you able to download Google Camera from playstore and does it work fine?
Is selinux enforced? Tks
Click to expand...
Click to collapse
By default, the ROM includes Google Camera PX by cstark27, which is more up to date than the stock (marlin/sailfish) Google Camera app. It includes newer features such as Portrait mode and Timelapse.
However, from the Google Play Store, you are still free to install the stock one.
As for SELinux, yes. It is enforced.
For stable releases from PixelExperience, it is required that builds are on Enforcing.
lmvuong1997 said:
- Change to inactive slot (the slot you flashed the rom), reboot to fastboot to make sure the active slot has changed (for me it has not), if not change it by 'fastboot set_active a' (or b). Reboot.
Click to expand...
Click to collapse
No need for this last part. If on TWRP, after flashing the ROM, you just need to reboot back to recovery and it will automatically set to the inactive slot.

[ROM] [OFFICIAL] [STABLE] [R] DotOS 5.2.1 [MOTO X4 - PAYTON] [23/11/2021]

View attachment 5438975
" #DroidOnTime "
ROM Version: 5.2.1
Device: PAYTON
Maintainer: AADITYAZEO
Build Status: OFFICIAL
View attachment 5438991​
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.​
Click to expand...
Click to collapse
"This is a user-friendly thread, all your suggestions are important to us and will be taken into consideration."
View attachment 5438997
dotOS is an Android ROM that focuses on performance, stability, and User Experience. We focus on making our rom look and feel great without struggling on Performance and Battery! So that one can get the most out of your device.....
View attachment 5438999
CLEAN FLASH/First Time Installation :
01. Download the ROM, Firmware and GApps from the links above.
02. If you're coming from Oreo Flash the PIE Firmware (Factory Image or Firmware ONLY) for your device.
03. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
04. Create backup. i.e. EFS
## YOU ONLY NEED THIS STEP ONCE.. When updating Firmware's ##
05.At this point Flash "Copy Partitions Zip" In TWRP "SLOT A"
06. Flash the ROM and TWRP installer.
07. Choose Reboot -> Recovery
08. Install GApps & Magisk.
09. Reboot -> Bootloader
10. fastboot -w
11. Reboot and Enjoy.
*Note-1: Slots, ROMS install to opposite (inactive) slot
If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"
*Note-2: Firmware's
* Recommended to install to "Slot A" unless you have PIE firmware fully installed on "Slot B" (you can achieve this with Firmware ONLY Links or copypartitions.zip ran from Slot A after a full stock update)
DIRTY FLASH :
1.Download the latest build.
2.Reboot to recovery.
3.Flash the latest build along with the twrp.
4.reboot to recovery. (very Important)*
5.flash optional packages like gapps and magisk.
6.Wipe Cache.
7.Reboot.
Note: If upgrading from 5.0.* to 5.1.* a clean flash is required.
Note: GApps only has to be flashed once whereas Magisk/Su is to be flashed every time you Dirty Flash the OTA Update.
View attachment 5439003
CLICK ME
View attachment 5439005
COMPLETE CHANGELOG : https://changelogs.droidontime.com/
View attachment 5439007
AOSP
Lineage OS
Pixel Experience
Dirty Unicorns
Project Lighthouse
And all other open-source Devs/Teams.
View attachment 5439009
Mohan CM - Founder/Core Developer
Iacob Ionut - UI, UX Developer/ Core Developer
Sipun Kumar - Developer/Maintainer
Special thanks:
Manish Bajpai - Web Developer
Important Links
If you liked our Project, please consider supporting us. - Donate - https://www.paypal.me/MOHANCM
Donate to device maintainer. - Donate - https://www.paypal.me/jackvortexhd
dot OS source
dotOS-Device Sources
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Telegram Group
Telegram Channel
Website
Downloads page
REPORTING BUGS !
As soon as the problem occurs, take a LOGCAT!
for more READ THIS
and do not forget to send it to us
View attachment 5439011
Contributors: AadityaZeo
Source Code: https://github.com/DotOS
GitHub : - https://github.com/aadityazeo
ROM OS Version: 11.x Android R
Version Information
Status: STABLE
Current Stable Version: v5.2.1
Stable Release Date: 23-11-2021​
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Same problem be my.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Which Verison of twrp you're using?
Aaditya ZeO said:
Which Verison of twrp you're using?
Click to expand...
Click to collapse
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, booting to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Randy Power said:
twrp-3.6.0_9-0-payton
I've also tried installing dot without installing twrp. When I do this, boring to system gives me the booting animation (3 colored circles that look like two planets circling the sun). But it gets stuck there. One time, I waited for several hours, enjoying the planets animation.
Click to expand...
Click to collapse
There're quite few things which you need to remember.
1st
2nd
If you were stuck on boot logo, you should perform fastboot - w in bootloader.
3rd - as per your comment u want vanilla edition. So i suggest u to stick with two 3.5xxx (latest prior to version 3.6xx) and follow the steps as stated below
a) completely wipe the phone
b) rom + twrp
c) reboot to recovery
d) wipe data in twrp
e) reboot to system.
This should work as I've also installed vanilla Verison with same process.
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Randy Power said:
Thank you very much, @Aaditya ZeO. I will try again with those steps when I get back to my x4 today.
If i want to install the gapps version, should I use twrp 3.6 instead of 3.5?
Click to expand...
Click to collapse
I don't think it matters, I've use twrp 3.2 and 3.6 to install gapps and had no issues in either case.
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Randy Power said:
I appreciate the suggestions. I think I've tried everything, including installing twrp 3.5.xxx, but I still get the same result.
If I clean install dot and fastwipe -w , I still get the spinning planets.
If I clean install dot, install twrp 3.5 or 3.6, and fastwipe -w, a "reboot system" always brings up twrp again.
In case it matters, my device is payton XT1900-1 32GB P4.
Click to expand...
Click to collapse
Can you try to install gapps version for once?
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
After the above, I formatted data from twrp. It completed without errors, so I rebooted to system.
Result: Still stuck on spinning planets.
Randy Power said:
I just did this:
fastboot boot twrp
completely wipe the phone
install rom 5.2.1 (dotOS-R-v5.2.1-payton-GAPPS-20211123-1226.zip)
install twrp (twrp-installer-3.5.2_9-0-payton.zip)
reboot to bootloader
fastboot boot twrp (in retrospect, I could have rebooted to twrp without fastboot)
wipe data in twrp
format data in twrp
reboot to bootloader; fastwipe -w
reboot to system.
Result: Spinning planets (boot animation).
I'll try again with the above, except step 5-6 reboot directly to twrp.
By the way, is this the expected result of "fastboot -w" on the x4?
Code:
>fastboot -w
Erasing 'userdata' OKAY [ 0.322s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
nope this shouldn't be the output after the fastboot -w.
Aaditya ZeO said:
nope this shouldn't be the output after the fastboot -w.
Click to expand...
Click to collapse
I appreciate that. I've tried many combinations of formatting data in TWRP, which seems to work. Resizing the partition and fsck on the partition work fine, all in TWRP. I can even copy files from /externalsd to /sdcard, and the fs survives a reboot.
However, fastboot -w always fails (error shown above), and booting the system gives spinning planets animation forever.
I'd be grateful for pointers on fixing the fastboot -w problem, if that is what's needed.
Hello
I installed dotOS 5.2.1 and when it's time to enter the PIN code it says that the sim card is locked. Tried both PIN and PUK, but none works. What should I do?
OK, so I solved it by basically following these instructions:
However, I now have a new problem. If I power off the phone while the USB charger is connected, it restarts the phone instead. And if it's powered off and I connect the charger, it turns itself on. This didn't happen with Android 9. How can I fix it? I do not want my phone to switch itself on when charging.
Randy Power said:
Hi there. First time trying Dot. Despite trying lots of different combinations of flashing, and trying to ensure I followed the instructions above exactly (with the exception that I do not want Gapps or Magisk), rebooting to System always reboots into Recovery instead.
For grins, I tried the latest unofficial lineage (lineage-18.1-20211112-UNOFFICIAL-payton), which installed and booted up just fine.
Suggestions appreciated.
Click to expand...
Click to collapse
Are you flashing to the appropriate slot?
For those having problems with the phone rebooting after a few seconds after upgrading from an Android 9 rom:
You might need to upgrade the modem firmware. That happened to me while upgrading from Lineage 16.0 to Lineage 18.1. After investigating a bit, I figured out the problem happened when connecting to the mobile network or (sometimes) wifi.
This is (roughly) how I solved the problem:
- flash your choice of recovery/system (not needed if already done - if you do this later your updated firmware might be overwritten)
- download the latest payton stock rom from lolinet's obsolete phones archive
- unzip and cd to unzipped folder
- connect phone and reboot to bootloader
- make sure you have fastboot and run the following commands (adapt to your OS as needed):
mfastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot erase carrier
fastboot erase userdata (I did it after backing up my data, but I think it was not necessary)
fastboot erase ddr
fastboot reboot
- have fun!
Notes:
- you might just flash a subset of the binaries above, I flashed what I thought was needed. The original reddit thread mentioned only NON-HLOS.bin and fsg.bin
- after having tried many things I ended up with dotOS 5.2.1 and will try it for a while
References
- this reddit comment
- Method 2 at rootmygalaxy
rodrigopitanga said:
Are you flashing to the appropriate slot?
Click to expand...
Click to collapse
I think yes. It's been a few weeks now, so my memory on the details is fuzzy. But I'm familiar with the A/B monkey business, copy partitions, etc. And flashing lineage worked out successfully. Thank you for the reply.
Does adoptable storage work?

General [SHARED] LineageOS 19.1 | OFFICIAL | MicroG + MIUI Camera [23/04/16]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First I'm not the developper of this rom and just share it here
credits go to @NeoArian
Be aware that it's a provisory thread and the dev will create his own when he decide ....
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
​@NeoArian made a flashable zip for having MIUI camera on LOS​Here is the camera..I repeat Im not the creator of this file, you must thank @NeoArian for this and his perfect rom​
LineageOS 19.1 for Xiaomi M2101K9G (renoir)
Build date: 2022-11-01
Security patch: 2022-10-05
Variant: GMS
Changelog (https://www.lineageoslog.com/19.1/renoir)
Download
lineage-19.1 (https://download.lineageos.org/devices/renoir/builds)
lineage-19.1 MicroG (https://download.lineage.microg.org/renoir/renoir/)
⛭ GitHub release / additional files
Build date: 2022-09-27
Spoiler
Security patch: 2022-09-05
Variant: VANILLA
changelog
Download
lineage-19.1 (https://github.com/arian-ota/ota/re...f/lineage-19.1-20220927-UNOFFICIAL-renoir.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/19.1-renoir-3746432f)
SHA-256 checksum
3746432fe6134e94aabfb1efad645aec882da1ddba48b39c70b5548a0abd3120
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++===========================================================================================
Build date: 2022-09-25
Security patch: 2022-09-05
Variant: GMS
changelog
Download
lineage-19.1 (https://github.com/arian-ota/ota/re...neage-19.1-20220925-UNOFFICIAL-GMS-renoir.zip)
⛭ GitHub release / additional files (https://github.com/arian-ota/ota/releases/tag/19.1-renoir_gms-4eab216d)
SHA-256 checksum
4eab216d294330b851005b8166d3e356e41e72729831b696d915f026027133e6
Spoiler: Earlier versions
Build date: 2022-08-29
Security patch: 2022-08-05
Variant: GMS
Changelog
Download
Lineage 19.1
⛭ Github release/additional files
SHA-256 checksum
b5b38148be07ed66d614dfada0acc2587420f2a763c36fd6d8647db6eb0c903f
Credits and thanks to @NeoArian
Installation Instructions:
Lineage Os Installation:
1- Install LOS Recovery: With the phone in FASTBOOT mode in the Platform-tool folder and the necessary files, open the CMD
2- Next we place in the window: fastboot flash boot_ab boot.img and then fastboot flash vendor_boot_ab vendor_boot.img to finish fastboot reboot recovery
3- The cell phone will restart in recovery mode with LOS recovery already installed (it is managed with the volume and power keys)
4- Perform Format Data (do not restart again)
5- Give Apply Update and then Apply Update from SDcard1 and look for the ROM
6- Then Reboot System Now (WILL INITIATE THE ROM)
7- Force restart in recovery to install Gapps (PICO Recommended)
8- Apply Update, Apply update from SDcard1 choose the gapps
9 Reboot System Now and enjoy XD
ALTERNATIVE WAY OF FLASHING THE ROM see post 2
ALTERNATIVE WAY OF FLASHING THE ROM
For those like me who have issue with flashing this rom here i what I do to bypass recovery issue..
after flash boot+vendor and start on LOS recovery and format data, I click update but I haven' apply update from sdcard1 but justapply from ADB..in advanced settings, there isn't such option....so I installed with ADB sideload
that what I do, and after 1 error I tried again and got error when I command adb reboot that system was not installed but I'm now on your rom....only issue is with my sdcard not recognized...have to backup on pc, format and recopy back, but certainly error on my side when I flash back miui rom.......
Install Custom ROM with ADB sideload
What is Android Debug Bridge?
ADB is a command-line tool included in the Android SDK development kit. It is used to communicate with any device that runs the Android operating system. You can use the ADB commands to perform various operations on your Android device.
With the help of the Android Debug bridge, you can install custom ROMs, mods, GApps, backup Android, flash official stock firmware, and install Android apps. Besides, you can also use ADB to uninstall bloatware without Root, downgrade an app, etc.
What is ADB Sideload?
ADB sideload, a command that transfer and install a zip file on an Android device from the PC. This command is handy for a custom ROM developer to push and install any installation zip file directly on a device.
The sideload feature was introduced with the Android Jelly bean recovery. Most importantly, this sideload mode requires a TWRP recovery version 2.3 or higher. Besides, it is also essential to install the latest ADB binaries on your PC.
How to Flash Custom ROM using ADB and Fastboot
Are you ready to use ADB and Fastboot for flashing custom firmware on your Android phone? Then let’s get started.
Warning
Ensure to install the right custom ROM on your Android phone. Do NOT proceed if the firmware is incompatible with your phone model number.
Requirements
A Windows PC and a standard USB cable.
Charge your device to a minimum of 50%.
Install mobile USB drivers on your computer.
Enable USB Debugging mode from your device settings.
Also, enable the OEM unlocking and Advance reboot mode.
Moreover, unlock your device bootloader.
Install TWRP 2.3 or higher on your Android device.
(Optional) Temporarily disable antivirus and firewall on your PC.
Steps to Install Custom ROM using ADB Sideload
Follow these step-by-step instructions to sideload the zip file on your Android phone.
1. Download Custom ROM
At first, download the mobile-specific Android custom ROM on your PC.
Ensure that the ROM file is in zip format.
Also, download the correct firmware that is compatible with your device’s model number.
2. Install ADB and Fastboot drivers
Download and install the latest ADB drivers on your computer.
Make sure that the ADB version is 1.0.29 or higher.
3. Transfer Custom ROM to ADB folder
Copy the downloaded custom ROM and paste it into the ADB folder.
The folder default location will be C:\Program Files\Minimal ADB and Fastboot.
4. Boot Android phone into Recovery mode
Switch off your Android phone.
Now, restart it into recovery mode.
Every device has different methods to boot into recovery.
You can either Google it or use the Recovery reboot app from Play Store.
5. Set the device into ADB sideload mode
As soon as you enter the recovery mode, click on the Advanced button.
On the next screen, click on the ADB sideload option.
6. Connect Android phone to PC
Now, connect your Android device to the computer using a USB cable.
Keep the device as it is in sideload mode.
After a successful connection, tick the Wipe Davik Cache and Wipe Cache options.
Then, swipe right on your device to start sideload.
7. Launch CMD window
Open the ADB folder, hold your keyboard’s Shift button, and right-click.
From the list of options, tap on the Open command window here option.
This will open the command prompt window on your PC.
8. Confirm the ADB connection
Furthermore, type the below command in the cmd window and press the enter key:
adb devices
You’ll see some random numbers with a ‘List of devices attached’ message.
This will confirm that your Android device is successfully connected to the PC.
9. Flash Custom ROM with ADB sideload command
To flash the custom ROM zip package file, enter the below command in the CMD:
adb sideload LineageOS18.zip
Make sure to type the exact name of the custom ROM file.
Also, don’t forget to add the zip extension at the end.
Here, I’m flashing LineageOS18 custom ROM.
Finally, hit the enter key to begin the ROM flashing process.
10. Reboot Android phone
On the installation finishes, your device will show a message saying, ‘ADB sideload complete.’
Tap on the Reboot System option to restart your device.
or those who don't know how to use ADB sideload here is a tuto you can read
How to Flash Custom ROM using ADB sideload [Easy Steps] ​
Flash Custom ROM zip file with ADB and Fastboot commands on any Android phone. Install Custom Firmware without TWRP recovery using CMD.
How to use adb
Attachments​
Mind sharing the device, kernel and vendor trees used to build this ROM? I want to build and try it out myself. Thank you and @NeoArian for the hard work btw.
calputer said:
Mind sharing the device, kernel and vendor trees used to build this ROM? I want to build and try it out myself. Thank you and @NeoArian for the hard work btw.
Click to expand...
Click to collapse
The trees and kernel are available on GitHub.com/renoir-development
The vendor repository can be extracted with extract-files.sh from the renoir tree. To do so, download the lineage zip, then cd to device/xiaomi/renoir and run "./extract-files.sh /path/to/lineage.zip".
I don't see a vendor_boot.img in the github release page but there's a dtbo.img file. What do we do with this file? Also I don't think TWRP for renoir is working with Android 12 am I right?
Sa
calputer said:
I don't see a vendor_boot.img in the github release page but there's a dtbo.img file. What do we do with this file? Also I don't think TWRP for renoir is working with Android 12 am I right?
Click to expand...
Click to collapse
Same here. Where can i download boot_ab boot.img and vendor_boot_ab vendor_boot.img ?
I tested the rom and managed to install. attached image with the command needed. It work after I tried to puzzle the correct way to install. PS (if don't work try install LineageOS 18 as base to start, this is how I done). [after <<fastboot reboot recovery>> command, your smartphone will go in recovery mode from that -reset data- and -apply update-].
source of files used <<github.com/ arian-ota/ota/releases/tag/19.1-renoir_gms-b5b38148>>
wanna ask to dev or expert: if this change about use of -dtbo- instead -vendor_boot- is android 12 new design fault (google)?
PS: the devs have some grudge against users for lacking info about rom installation? This is my first LineageOS custom rom, kinda hard to install.
So I flashed the rom using files from the git release and vendor_boot.img from MIUI13. And one problem is that the wallpaper preference in setting is not working. So I just decided to go back to MIUI 13 global and somehow twitter and reddit scrolling is smooth and does not stutter anymore. Interesting cause it was stuttering on every AOSP I've tried.
calputer said:
So I flashed the rom using files from the git release and vendor_boot.img from MIUI13. And one problem is that the wallpaper preference in setting is not working. So I just decided to go back to MIUI 13 global and somehow twitter and reddit scrolling is smooth and does not stutter anymore. Interesting cause it was stuttering on every AOSP I've tried.
Click to expand...
Click to collapse
vendor_boot from MIUI13 OTA or FASTBOOT? for odd reason my LIneage os 19 work even without installing it
Testing the ROM, it cannot read sd card in exfat, ntfs or ext3 file system, it always ask me to format in fat32. there's a workaroud? fat32 limit is annoying, and pretty sure original MIUI have support for exfat.
Ranball said:
vendor_boot from MIUI13 OTA or FASTBOOT? for odd reason my LIneage os 19 work even without installing it
Click to expand...
Click to collapse
From Fastboot zip. And the vendor_boot.img from Pixel Experience site also has the same size (98,304 KB), so I figured I could use it without any modifications.
Any news about update??
jellybean 4.1 said:
Any news about update??
Click to expand...
Click to collapse
no, not yet
I bought my mom a new Xiaomi Redmi Note 11 lite 5G. Before she has used the Xiaomi Redmi Note 8T, which now will be dedicated for banking apps or as Navigation device.
The Xiaomi RN 8T had some issues on a custom Rom, especially with the microphone on some Apps.
Now i consider to let the Xiaomi RN 11L on Stock ROM, to not disturb her phone experience. I'm a fan of the work of all the Custom ROM Creators and use it on all my own devices. But which one of the Custom ROMs does work properly and would you prefer, for daily use and a bigger amount of Gapps?
MonoPro9 said:
I bought my mom a new Xiaomi Redmi Note 11 lite 5G. Before she has used the Xiaomi Redmi Note 8T, which now will be dedicated for banking apps or as Navigation device.
The Xiaomi RN 8T had some issues on a custom Rom, especially with the microphone on some Apps.
Now i consider to let the Xiaomi RN 11L on Stock ROM, to not disturb her phone experience. I'm a fan of the work of all the Custom ROM Creators and use it on all my own devices. But which one of the Custom ROMs does work properly and would you prefer, for daily use and a bigger amount of Gapps?
Click to expand...
Click to collapse
Pixel Experience best stability for now, then this Lineage 19.1.
razor_1911 said:
Pixel Experience best stability for now, then this Lineage 19.1.
Click to expand...
Click to collapse
Thank you for the conclusion.
She want to stay with MIUI at least till the guarantee.
The Redmi Note 8T will be my next Toy
razor_1911 said:
Pixel Experience best stability for now, then this Lineage 19.1.
Click to expand...
Click to collapse
For renoir is the rom discontinued =(
@NeoArian made an update of his LOS with Gapps and Vanilla version.....I have flashed both and its working great....
thanks to him

[ROM][OFFICIAL] LineageOS 20 weeklies for Xiaomi Poco F1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13 (T), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
GPL compliance:
​
Device tree source code: LineageOS/android_device_xiaomi_beryllium
Kernel source code: LineageOS/android_kernel_xiaomi_sdm845
Working:
Camera (and flashlight)
WiFi
Bluetooth
Telephony (Calls and Data)
IMS (RCS, VoLTE and WiFi Calling)
Audio (Record and Playback)
Video Playback
Sensors
GPS
Encryption (FBE)
WiFi Display
Broken:
Nothing (?)
Compatibility:
Compatible with all Xiaomi Poco F1 variants.​Builds are based off the Xiaomi's Android 10 firmware with proprietary blobs from MIUI v12.0.3.0 global stable package.​
Device wiki:
Official wiki link
Downloads:
Official download links
Installation:
Follow instructions found in the respective wiki page
Is this a System-Ext-Rom?
Chris_Kaos79 said:
Is this a System-Ext-Rom?
Click to expand...
Click to collapse
Yes
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
I updated to LOS 20 via dirty flash from LOS 19.1 (following the official procedure: https://wiki.lineageos.org/devices/beryllium/upgrade)
It worked flawlessly!
AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
NGK has some problems for now, wait for update or use orange fox...
AtomicStryker said:
Read the upgrade instructions, had to sadly ignore them because i no longer have a cable/port/adb combo that allows adb to sideload successfully (i just get errors when he starts to transmit).
EDIT [i am lying, adb works but fastboot does not]
So i remained on the Reignz TWRP, and from a recent LOS 19.1:
- flash LOS 20
- flash MindTheGapps 13
- flash Magisk
- flash NGK kernel
- Wipe dalvik/cache
- reboot system
-> Bootloop. Well theoretically this must work, so maybe try less at once? I did see that Magisk re-flashed itself automatically in TWRP, so attempt 2:
- flash LOS 20
[Magisk automatically reflashes itself]
- flash MindTheGapps 13
- reboot system
Works now.. but i am always eager to ruin myself so i will try to reflash NGK now.
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
EDIT3: Working good with stock kernel. Magisk works, camera works, banking and auth apps work. Thank you
Another oddity: The updater app immediatly came up and recommended i upgrade to the LOS20 i just flashed. Uh huh?
Click to expand...
Click to collapse
I know this is off-topic, but I guess you used Reignz V3.6.2 that he tested for A13 support?
Interesting that apparently A13 again uses other encryption than A12? I though now with A13 FBE would be the new standard but there is something new again?
So official 3.7.0 TWRP will not work with A13 I guess.
Looking forward to jump to A13 this weekend based on all the positive feedback so far - thank you bgcngm for your hard work!
hello there,
I've just dirty flashed LOS20, and I'm having problems connecting anything via bluetooth, any idea how to fix this without clean installing?
Another question, I'm using MindTheGapps 13 as recommended here, but I was looking for something the minimum google services, do you think I can use NikGapps?
Thanks
alright, I couldn't fix it, I had it reinstalled clean. Everything is working nicely and the new camera is a very welcome improvement.
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
AtomicStryker said:
EDIT: Yup NGK+TWRP causes bootloop. I will reflash LOS20 again ... and try LOS recovery with NGK maybe.
EDIT2: LOS recovery with NGK bootloops also. Stock kernel it is.
Click to expand...
Click to collapse
This problem is a known issue since the day before yesterday. Several people are experiencing this with the upgrade from 19.1 to 20. For now, running the stock kernel should be fine.
Installation Guides​Official way of installation can be found at OP.
Installation Guides:
Clean Install via TWRP:
Backup your data to PC or SDCard if you have.
Downland:
Spoiler: These files
- TWRP by REIGNZ v2 [twrp-beryllium-v3.7.0-A12-V2.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Boot, flash and reboot to TWRP. [Check Install Custom Recovery Guide]
Select Wipe > Advanced Wipe -> Select Dalvik / ART Cache, System, System_EXT, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe.
Reboot to recovery once again (needed due to a current issue with TWRP by REGINZ) and then Format data > type yes.
Transfer the files you previously downloaded into Internal Storage, while you are connected and into TWRP from PC to your Device. If you have SDcard or USB OTG you can also use that.
[TWRP by REIGNZ have an issue, if PC doesn't recognize the device, press in twrp menu, Advanced > File Manager > and find and select sdcard folder aka Internal Storage > go back and now your pc should be able to recognize the device]
Flash ROM > GApps. NOTE: ROM IS FORCE ENCRYPTED
[Optional] Flash LineageOS recovery by pressing "Install Image > Navigate and Select the LineageOS Recovery > Flash it to recovery partition.
Reboot and Enjoy!
[Optional] In case you want to change Kernel to NGK or SC [SE version - aka System_Ext], flash it after the first boot of the ROM.
[Optional] In you case you want Root, flash Magisk after the first boot of the ROM.
SafetyNet & Certified Play Store:
Official LineageOS doesn't pass SafetyNet or have certified Play Store by default. [Read here why]
Root your device with Magisk and Follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
OTA Upgrade/Update:
Warning
Only use OTA if you are encrypted. Simply go to updater and press install, everything will be automatic.
Dirty Installation via TWRP:
{Manually Upgrade/Update the ROM}
Download:
Spoiler: These files
- TWRP by REIGNZ [twrp-beryllium-v3.7.0-A12.img] - [Current Bugs/Issues & Workarounds]
- Latest build of Official LineageOS ROM and optional LineageOS Recovery from the same link, if you want to flash that later.
- Optional A13 GApps of your choice.
Wipe System, System_Ext, Dalvik ART/ Cache, Cache, Vendor.
Flash ROM > GApps > [Optional]Magisk.
Reboot and Enjoy!
Notes:
If you want to flash DFE use TWRP by REIGNZ based on A9. (not A12) [Not recommended be decrypted]
If you encounter Fastboot issues read the guide/fix in my thread.
You can translate the ROM in Crowdin.
Check my threads:
Spoiler: My threads
- POCO F1 Ultimate Collection & Guides
- Android Ultimate Collection & Guides
- ReVanced & ReVanced Extended - Guides & Useful Links
- Windows Ultimate Collection & Guides
pmcmm said:
I'm still facing issues with bluetooth though. I'm able to use it and connect normally, but when listening to audio, it seems that the connection is weak, and I can often hear cuts in the connection, or noise. Anyone having the same?
Click to expand...
Click to collapse
I had to unpair my existing bluetooth devices and re-pair them, (presumably because the upgrade changed the phones bluetooth ID) but it seems to work perfectly for me.
- I am on this ROM since 01.01, no major issues so far.
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
- One small glitch I found: If I lit up the screen (press power button) while charging, the phone stays on the lockscreen with the display on, never turning off by itself. Of course if I press power button or double tap I can turn it off. Also if I just disconnect power cable, display turns off in few seconds like it should. But if I just press power once and leave it, it will stay on the lockscreen forever.
- Bluetooth is fully working for me. I am using 2 different BT headsets for few hours every day. Not a single issue so far.
marsa47 said:
- Just FYI, DFE zip (Disable Force Encryption) from Retrial collection doesn't seem to work on this ROM. For the sake of testing, I tried both A13 DFE and the older zip (which worked on LOS19.1) with clean installations. When I check in the settings, the phone was encrypted every time, no matter what I do.
- On the other hand, I can report that unofficial TWRP A12 by Reignz (twrp-beryllium-v3.7.0-A12.img) can decrypt storage on LOS20.
Click to expand...
Click to collapse
The DFE not seem to working with the TWRP by REIGNZ based on A12. Instead you should try to flash DFE via TWRP by REIGNZ but based on A9.
The purpose of A12 based twrp is to decrypt A12+ encrypted ROMs. If you don't need encryption (which I recommend everyone to use encryption), then use TWRP by REIGNZ A9 and flash DFE.
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
MagnesG said:
Is it important to fastboot the required xiaomi firmware first? Coming from 19.1.
Click to expand...
Click to collapse
I assume u already have it. No need.
noah001 said:
any way to get F2FS working ? With flashed fstab i get recovery reboot and without i get a bootloop
Click to expand...
Click to collapse
Flash a kernel with with f2fs support,
Do "long loading while taking picture from whatsapp-bug" still occurred????
123r4ka456 said:
Do "long loading while taking picture from whatsapp-bug" still occurred????
Click to expand...
Click to collapse
I get the following behavior:
1st try: click on photo button: nothing happens (but no hang)
2nd try: click on photo button: photo is immediately taken and can be sent, no hang
So: not really running without issues, but no hang
Maybe this is helpful

Categories

Resources