Development PIXEL EXPERIENCE-PLUS FOR PIXEL 5A ANDROID 12 - AUG. 13, 2022

Search This thread

TheSayaMan

Senior Member
Sep 12, 2016
453
204
August security patch.

You MUST be on Android 12 to use this!!!!!

If your not, you must flash any Google factory image for Android 12 barbet.

Your bootloader must also be unlocked to install custom firmware.

To do this, reboot to bootloader and type the following: fastboot flashing unlock

The custom kernel of this ROM hides the unlocked bootloader. The device will pass Safetynet and the Play Store will report the device as certified. Based on this, root, magisk and the modules are not needed to pass device certification.

This is based on the Android Open Source Project. It includes various proprietary hardware-specific code.

All the source code is available in the Github repo here.

Basic requirements​

  1. Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
  2. Make sure your computer has adb and fastboot. Setup instructions can be found here.
  3. Enable USB debugging on your device.

Thanks go to Github and Pixel Experience for their source code and device specific code. I couldn't have built this without it!!!

The ROM uses the Pixel Experience source code, device specific code. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated every week with minor changes.

GAPPS ARE ALSO INCLUDED WITH THIS ROM

DO NOT DOWNLOAD OR FLASH GAPPS ON THIS ROM!!!!!

DOWNLOAD BOOT, VENDOR_BOOT & ROM HERE

#1 REBOOT TO BOOTLOADER

#2 FACTORY RESET: fastboot -w

#3 FLASH VENDOR_BOOT & BOOT:
fastboot flash --slot all vendor_boot vendor_boot.img
fastboot flash --slot all boot boot.img


#4 REBOOT TO RECOVERY THEN ADB SIDELOAD
adb sideload PE-Plus-barbet-12.1-20220813-UNOFFICIAL.zip

#5 REBOOT TO SYSTEM

#6 REBOOT TO RECOVERY AGAIN IF YOU WISH TO ROOT AND ADB SIDELOAD
adb sideload magisk.apk

#7 REBOOT TO SYSTEM

Screen call and Google assistant works.

If you are already on this ROM, you can dirty flash updates without wiping data. Simply set to inactive slot in bootloader. Reboot to bootloader and see what active slot is and set to opposite. Example: fastboot --set-active=a

Then repeat all steps except #2

DO NOT DIRTY FLASH THIS ROM WITH THE OFFICIAL ONE LOCATED ELSEWHERE. I USE DIFFERENT SECURITY KEYS AND YOU WILL BOOTLOOP. YOU MUST WIPE WHEN COMING TO THIS ROM THE FIRST TIME!!!
 
Last edited:

[email protected]

Senior Member
Feb 6, 2017
120
11
Hello, thanks for for new custom rom. Can you please post screenshots with which customizations available in this ROM? For example double tap on status bar to go sleep, etc?
 

TheSayaMan

Senior Member
Sep 12, 2016
453
204

Attachments

  • Screenshot_20220503-221251_Trebuchet.png
    Screenshot_20220503-221251_Trebuchet.png
    283.1 KB · Views: 191

TheSayaMan

Senior Member
Sep 12, 2016
453
204
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set-active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
 
Last edited:

[email protected]

Senior Member
Feb 6, 2017
120
11
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
 
Last edited:

TheSayaMan

Senior Member
Sep 12, 2016
453
204
Hello, if there some critical updates, or fixes? I think everything working fine on current ROM.
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
 
  • Like
Reactions: [email protected]

[email protected]

Senior Member
Feb 6, 2017
120
11
Ok thank you. Someone sent me a personal PM saying that phone calls were dropping for no reason and all text messages were not being received to their phone. I can't seem to see any issue from the logcat they sent me. Any truth to this from you or anyone else? I am using this myself and don't have such issues. Maybe it's carrier related. I have Verizon. I will check with him and see what carrier he is using. I will give him the benefit of doubt.
Hello, I haven't such issues. I use 2 sims, 1 esim and 1 sim, everything working fine with SMS and calls.
 

[email protected]

Senior Member
Feb 6, 2017
120
11
I'm having a issue right now getting the updates pushed through the updater. For now you can manually update without wiping by the following method until I get it fixed. Reboot to bootloader and check what your active slot is. Switch to opposite slot by the following. Example, active slot is b. fastboot --set active=a Reboot to recovery and sideload update file. Reboot to recovery and sideload Gapps file. Reboot to system. You will then have to reboot to recovery to sideload magisk and root again. Updates are always installed in opposite slot or you will be stuck at bootanimation. This will hopefully be temporary until I get the issue resolved.
Hello, do you plan to release Android 12.1, as I understand this linage is Android 12
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    August security patch.

    You MUST be on Android 12 to use this!!!!!

    If your not, you must flash any Google factory image for Android 12 barbet.

    Your bootloader must also be unlocked to install custom firmware.

    To do this, reboot to bootloader and type the following: fastboot flashing unlock

    The custom kernel of this ROM hides the unlocked bootloader. The device will pass Safetynet and the Play Store will report the device as certified. Based on this, root, magisk and the modules are not needed to pass device certification.

    This is based on the Android Open Source Project. It includes various proprietary hardware-specific code.

    All the source code is available in the Github repo here.

    Basic requirements​

    1. Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
    2. Make sure your computer has adb and fastboot. Setup instructions can be found here.
    3. Enable USB debugging on your device.

    Thanks go to Github and Pixel Experience for their source code and device specific code. I couldn't have built this without it!!!

    The ROM uses the Pixel Experience source code, device specific code. I made other minor changes and used compression to lower the file size of the ROM, creating more space in the internal storage with minor reduction in performance. Updated every week with minor changes.

    GAPPS ARE ALSO INCLUDED WITH THIS ROM

    DO NOT DOWNLOAD OR FLASH GAPPS ON THIS ROM!!!!!

    DOWNLOAD BOOT, VENDOR_BOOT & ROM HERE

    #1 REBOOT TO BOOTLOADER

    #2 FACTORY RESET: fastboot -w

    #3 FLASH VENDOR_BOOT & BOOT:
    fastboot flash --slot all vendor_boot vendor_boot.img
    fastboot flash --slot all boot boot.img


    #4 REBOOT TO RECOVERY THEN ADB SIDELOAD
    adb sideload PE-Plus-barbet-12.1-20220813-UNOFFICIAL.zip

    #5 REBOOT TO SYSTEM

    #6 REBOOT TO RECOVERY AGAIN IF YOU WISH TO ROOT AND ADB SIDELOAD
    adb sideload magisk.apk

    #7 REBOOT TO SYSTEM

    Screen call and Google assistant works.

    If you are already on this ROM, you can dirty flash updates without wiping data. Simply set to inactive slot in bootloader. Reboot to bootloader and see what active slot is and set to opposite. Example: fastboot --set-active=a

    Then repeat all steps except #2

    DO NOT DIRTY FLASH THIS ROM WITH THE OFFICIAL ONE LOCATED ELSEWHERE. I USE DIFFERENT SECURITY KEYS AND YOU WILL BOOTLOOP. YOU MUST WIPE WHEN COMING TO THIS ROM THE FIRST TIME!!!
    2
    I saw that for other roms it is in requirements, and generally for every ROM flashing. And I was like if you invented some magic that would be nice :D
    Unfortunately not but I do hide the unlocked bootloader with this, so it still acts as a unmodified device. Banking apps and Google pay works without root. The only thing I noticed that doesn't work is sports gambling apps if anyone even cares.
    2
    Twrp removed as part of install process. vendor_boot and boot supplied as part of install process. August security update patch will be in next update.
    2
    is your build based off 12.1.0_r8 ?
    I use the same repository located on GitHub. The security patches are still from last month, May. They haven't been updated yet. I will update them myself if not updated soon. I'll have to pull it from stock and it requires more work. Since I work a lot, I'll do it when I get a chance. It's not extensive, so I should be able to apply it on next full update Thursday.
    2
    After some reading about it here is a hint that you probably already now :)
    Newer Android devices' bootloaders pass a verified boot flag to the kernel. This means that if the bootloader is unlocked, it sends that flag, and the kernel listens to it then SafetyNet will fail. And solution is to patch your kernel to ignore the flag :)
    I am working on it. Hopefully the next update. Thanks.