Development Paranoid Android Topaz Beta 1 - Redmi Note 10

Development Paranoid Android Topaz Beta 1 - Redmi Note 10 - Redmi Note 10

{
"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"
}
We are very excited to announce Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* You tell us
Requirements
Make sure you've latest platform tools for Android.
Make sure you've MIUI Global Firmware version V14.0.3.0 flashed before flashing the ROM.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels and Custom recoveries are NOT supported and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Instructions (Firmware flashing)
Download recommended firmware zip
Extract it
Boot to bootloader
Open a terminal / command prompt in firmware-update directory and execute the following commands to flash the firmware:
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash aop_a aop.img
fastboot flash aop_b aop.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
Instructions (Recovery package)
Boot to bootloader
Download the recovery zip from here and run the following command:
fastboot update recovery-AOSPA-*.zip
Reboot to recovery with the following command:
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and select Apply update from ADB, and execute the following command:
adb sideload aospa-topaz-*.zip
After installation complete, Reboot to system.
Instructions (Fastboot package)
Boot to bootloader
Execute this to flash the ROM:
fastboot update --skip-reboot aospa-topaz-*-image.zip
Reboot to recovery with the following command:
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and reboot system.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Redmi Note 10 Community (Telegram)
Device Tree
Kernel Tree
Vendor Tree
Cheers and #StayParanoid!

Changelog for Topaz Beta 1:
- Initial beta release.
- Build kernel fully with GCC.
- Utilize most AOSPA components such as adreno, audio, av, bt, charging, display, dsprpcd, gps, init, keymaster, media, overlay, perf, telephony, usb, vibrator, wfd, wlan.
- Drop PowerOffAlarm.apk as our device has issues with the PowerOffAlarm feature.
- Transition to AOSP BT stack.
- Update GPS stack to LA.UM.9.1.r1-12900-SMxxx0.0.
- Upgrade drm to v1.4.
- Drop DisplayFeatures.
- Implement AOSP HBM (Auto-HBM that works via Auto-Brightness).
- Configure overlay for Automated DC-Dimming.
- Configure color modes overlays.
- Fixup padding.
- Fix device MAC Address handling.
- Make AoD enter doze.
- Fix ST2W/DT2W on AoD.
- Bring back CarrierConfig overlay.
- Import WFD stack from LA.UM.9.1.r1-12900-SMxxx0.0 to fix WFD.
- Import cnss-daemon from stock to fix 5GHz detection.
- Drop FM as it is mostly redundant.
- Configure QTI Bservice for optimal memory management.
- Update blobs from MIUI V14.0.3.0.SKGMIXM.
- Cleanup tree.
Kernel:
- Allow setting brightness up to 4095 for AOSP HBM.

Reserved #1

Cool

Yeah! <3

AttentionFor windows user, you could use Platform Tools r31.0.3
It doesn't matter if you would to use r33 tho
You will encounter error : ANDROID_PRODUCT_OUT not set if you use latest version of r34.0.0
Dont forget to use proper Usb Driver for Android Bootloader Interface

Waxaranai said:
Cool
Click to expand...
Click to collapse
Cool

Nice

thank you

Donpablo0271 said:
Attention:
For windows user, you could use Platform Tools r31.0.3
You will encounter some error if you use latest version of r34.0.0
Click to expand...
Click to collapse
I have to flash tomorrow (waiting to unlock the bootloader).
I have platform tools r33.0.1 and r33.0.3
Do I absolutely have to use r31.0.3?

carlos974 said:
I have to flash tomorrow (waiting to unlock the bootloader).
I have platform tools r33.0.1 and r33.0.3
Do I absolutely have to use r31.0.3?
Click to expand...
Click to collapse
No you can use r33. The problem lies with r34.

cyberknight777 said:
No you can use r33. The problem lies with r34.
Click to expand...
Click to collapse
Thank you!
By the way to flash the firmware can I copy paste the commands from OP in cmd (the firmware files will be in the platform-tools directory)

carlos974 said:
Thank you!
By the way to flash the firmware can I copy paste the commands from OP in cmd (the firmware files will be in the platform-tools directory)
Click to expand...
Click to collapse
Yeah sure you can do that

I am sorry for noob questions, but which file should I download from the website? One is name "Recovery Option" and the other is "Fastboot Option". And in the instructions, how am I supposed to replicate the steps mentioned in "Instructions (Firmware flashing)"?

@ciberknight777
I unlocked my redmi note 10 this morning.
I flashed the firmware, the rom.
All went well.
I restarted the rom works fine.
But when the phone goes to sleep, I press the power button to wake it up, the screen appears but I can't unlock by sliding my finger on the unlocked canedas (I didn't put any lock)

WalinAhmed said:
I am sorry for noob questions, but which file should I download from the website? One is name "Recovery Option" and the other is "Fastboot Option". And in the instructions, how am I supposed to replicate the steps mentioned in "Instructions (Firmware flashing)"?
Click to expand...
Click to collapse
The choice is yours, you can choose whether to follow recovery option or fastboot option. Instructions are provided respectively.
As for firmware flashing, do what it says? You obviously need windows/Linux with cmd prompt / linux terminal to do so.

carlos974 said:
@ciberknight777
I unlocked my redmi note 10 this morning.
I flashed the firmware, the rom.
All went well.
I restarted the rom works fine.
But when the phone goes to sleep, I press the power button to wake it up, the screen appears but I can't unlock by sliding my finger on the unlocked canedas (I didn't put any lock)
Click to expand...
Click to collapse
What is "canedas" and I can't reprod this nor have I seen such issues being reported. I'd take it this is probably some rare AOSP meme. If you can reprod, provide logs for it. That said it's highly possible that it isn't device specific so yeah.

cyberknight777 said:
What is "canedas" and I can't reprod this nor have I seen such issues being reported. I'd take it this is probably some rare AOSP meme. If you can reprod, provide logs for it. That said it's highly possible that it isn't device specific so yeah.
Click to expand...
Click to collapse
Typo "padlock"
I changed a year ago already the broken screen by another screen not amoled but TFT

carlos974 said:
Typo "padlock"
I changed a year ago already the broken screen by another screen not amoled but TFT
Click to expand...
Click to collapse
Then it's your screen issue

Related

[UNOFFICIAL] AOSiP 9.0 Pizza (by Dark98)

i installed this rom its been pretty solid phone boots up fast is what i like the most I don't think the battery drain is as bad as the OP made it sound. I had a little trouble installing with his installing rules cause you have to erase user data before you boot up the rom for it to boot right. I suggest installing with no sd card in the phone (sd cards have giving many issues if not compatible and set up to you phone.) so i used sideload to install any rom on this phone not just this one.
HERE IS WHAT I DO
Extract stock ROM to ADB folder and follow these steps from the command prompt
restart phone to bootloader and type these commands on your computer must have ADB AND FASTBOOT INSTALLED i suggest using linux
fastboot set_active a
fastboot reboot-bootloader
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Let phone bootup into the set up screen then restart the phone in to bootloader again
now you want to boot in twrp by typing this in the bootloader and i renamed my twrp file to twrp.img
fastboot boot twrp.img
then i sideloaded the partition ab file ( partition-ab.zip must be in adb folder)
adb sideload copy-partitions.zip
make sure you reboot to the b partition before you reboot to bootloader
restarted bootloader
fastboot boot twrp.img
adb sideload (name of ROM) (ROM must be in ADB folder)
restart to bootloader then type these commands other wise the phone will be stuck on the loading screen
fastboot erase userdata
fastboot reboot
start phone
if you want to install twrp or orangefox now is the time
you can install open gapps and magisk if you like

Bump for AOSiP! I've been using this February pie build now for a few days and it has ran great. When I initially installed I formatted data then flashed copy partitions AB zip then reboot bootloader, booted orange via fastboot, wiped then flashed rom, rebooted bootloader, booted orange fox recovery via fastboot, flashed gapps, rebooted system. I believe I ended up doing a erase userdata with fastboot afterwards and it booted fine and I went and flashed magisk for root a bit later after I was all setup.. I haven't yet tweaked doze how I normally do in a more aggressive way and I haven't made any other adjustments that i normally do but I will now so I'll be able to compare more on how battery is for me on my device after I do some of my usual tweaks but haven't noticed any abnormal drainage thus far but haven't been studying it much either... I say that in reference to the op known issues battery drain.. AOSiP has always been a favorite of mine. I hope this rom stays and/or it's cousin Derpfest becomes a thing at some point. ? Would definitely be awesome! I appreciate you building this rom and sharing with us all!! :good::good:
Everyone stay safe where ever you are located. I hope nobody gets this crud going around. I may attempt to compile some things from Gcloud. Going to look more into that..

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.

[10] [GSI] crDroid [ARM64-A/AB] [Experimental]

Issues and workarounds:
1. Check your phone compatibility with Treble before following these instructions.
2. Generally, smart charging feature (Settings > Battery > Smart Charging) does not work on Treble. You can have the same functionality using Battery Charge Limit app.
3. Can't flash Gapps due to error 70 (insufficient storage space available in System partition)? In TWRP, just go to Wipe menu > Advanced Wipe > check System partition > Partition options > Resize FS. Then flash Gapps again. In other recoveries, the steps are similar.
4. To get Viper4Android working on GSI ROMs, please, thank here or the Magisk modules.
5. For RAW support on cameras: Settings > Phh Treble Settings > Misc features > and select Expose Aux cameras (Qualcomm) if possible.
6. You may need to flash the vbmeta.img file specific for your device (firmware) before you first boot the GSI. Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
7. If you lose Wi-Fi and/or Bluetooth, you should flash the dtbo.img file specific for your device (firmware). Discover your actual slot: check in TWRP reboot options or in fastboot mode: fastboot getvar current-slot. Then run in the same slot you're flashing the GSI image:
For A/B devices, run:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
For A-only devices, run:
fastboot flash dtbo dtbo.img
8. Additional files as Permissiver v5 and DM-verity, forced encryption, and disc quota disabler must be needed to boot.

Bugs?

vytska69 said:
Bugs?
Click to expand...
Click to collapse
You tell me. I've tested on just one phone.

Does not see the sim card. No 3g / 4g. Redmi Note 8 pro.

Technical said:
You tell me. I've tested on just one phone.
Click to expand...
Click to collapse
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks

numser said:
Does not see the sim card. No 3g / 4g. Redmi Note 8 pro.
Click to expand...
Click to collapse
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.

HueyT said:
Perfect on top of LOS171 base on Moto g7 River xt1962-1 and VZW (CDMA). Great job, thanks
Click to expand...
Click to collapse
Thank you for testing. Please, let me know if something goes wrong with sensors (the most delicate part of building gsi's imho).

Brightness and auto brightness dont work in Samsung J7 Pro (J730)

Gheartxz2017 said:
Brightness and auto brightness dont work in Samsung J7 Pro (J730)
Click to expand...
Click to collapse
Thank you for testing and reporting. I was expecting this due to failure to apply 0043-Add-samsung-light-2.patch from phh...
Is there any app that can help you by-passing it? Like https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite or https://play.google.com/store/apps/details?id=com.velis.auto.brightness

Technical said:
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
Click to expand...
Click to collapse
Temporarily CFW. I will definitely check it out. Thank. :good:

Technical said:
Issues and workarounds:
6. On A/B devices, you may need to flash a vbmeta.img file specific for your device before you first boot the GSI.
must be needed to boot.
Click to expand...
Click to collapse
Hello.
how to flash vbmeta.img please ? thanks

skeeter92 said:
Hello.
how to flash vbmeta.img please ? thanks
Click to expand...
Click to collapse
1. Open bootloader and custom recovery are mandatory (see OP).
2. Download the latest (official) firmware for your device. Extract the vbmeta.img file and put into your adb/fastboot folder.
3. Go to fastboot mode and from command line, flash vbmeta.img:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Technical said:
Thanks for testing it.
Probably you need to flash dtbo.img that comes with your firmware package in your active slot:
fastboot flash dtbo_a dtbo.img
or
fastboot flash dtbo_b dtbo.img
Please, let me know and I'll update post 2.
Click to expand...
Click to collapse
fastboot flash dtbo dtbo.img if so?

perfect and all is well on Moto G7 plus XT-1965-2...... I flashed gsi over stock 10....then flashed permissiver 4, then my device specific Twrp installer..... reboot repaired file system in advanced wipe to add space for gapps no issue... booted canary magisk....

numser said:
fastboot flash dtbo dtbo.img if so?
Click to expand...
Click to collapse
Yeah, if your device is A-only (not A/B partition).

Technical said:
Thank you for testing and reporting. I was expecting this due to failure to apply 0043-Add-samsung-light-2.patch from phh...
Is there any app that can help you by-passing it? Like https://play.google.com/store/apps/details?id=com.vitocassisi.luxlite or https://play.google.com/store/apps/details?id=com.velis.auto.brightness
Click to expand...
Click to collapse
Thanks brightness works fine ..... but now camera and flashlight isn't available in last build

numser said:
fastboot flash dtbo dtbo.img if so?
Click to expand...
Click to collapse
I think so.

May i know for samsung note10 plus the vbmeta.img is flash on which partition?? Tks

orbital_71 said:
May i know for samsung note10 plus the vbmeta.img is flash on which partition?? Tks
Click to expand...
Click to collapse
The same partition you're flashing the GSI (system.img). You can check in TWRP which is the actual slot you're using.
Also in bootloader, you can run:
fastboot getvar current-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?

Development [UNOFFICIAL][ROM][13][renoir] PixelExperience [AOSP] [2023-04-04]

{
"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!

Better Mobile App

welcome