• We are moving to xdaforums.com!

    Posts made between now and when the migration is complete will not be carried over.
    You will be automatically redirected once the migration is complete.

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

Search This thread

JovialQuestion

Senior Member
Sometimes, for me anyway. I use Magisk with the fox module Hide user debug on custom Roms and it allows me to use Google pay. However you have to use the saftynet fix as well. I would just try to use root hiding techniques until you find one that works. Sometimes when your not rooted on a custom ROM it will always fail. At least this is what I've noticed on my attempts .
 
i'm using a pixel xl with lineageOS 18.1 and magisk and Google Pay/Wallet works fine.
I'm acctually using the same model as you and running the LOS 18.1 with the security patch level from dec-2022 and already works fine on this settings, but after the OTA update to Jan build, the contactless payment stop with the google wallet warning the device not meet the security levels. After this I downgraded to the this version, and not able to make works again..
 

spiff72

Senior Member
Apr 14, 2006
482
39
I can't get past an error message when flashing this. (Error Applying Update: 28 kdownloadoperationexecutionerror.)

I tried instead to use TWRP but I can't seem to get that installed (I fastboot into the twrp image, and then push the zip installer to the phone and install it, but it won't boot into recovery after this).

Any suggestions? I am able to load lineage with no issue, but really want to try pixelexperience on the Pixel XL (my backup phone).
 

JovialQuestion

Senior Member
I can't get past an error message when flashing this. (Error Applying Update: 28 kdownloadoperationexecutionerror.)

I tried instead to use TWRP but I can't seem to get that installed (I fastboot into the twrp image, and then push the zip installer to the phone and install it, but it won't boot into recovery after this).

Any suggestions? I am able to load lineage with no issue, but really want to try pixelexperience on the Pixel XL (my backup phone).
You need to flash in twrp the repartition script. Or you cannot flash this. Follow all instructions listed

Twrp doesn't flash to install recovery on Android 10 try the twrp 3.3.1 that one installed for me on Android 9 but none work on Android 10. I always boot the .img or flash the boot partition and flash the ota I want. Then if boot fails my device changes slots back to the boot slot with twrp

Pixel XL 32 gig partition script https://github.com/PixelExperience-Devices/blobs/raw/main/repartition-ogpixel-32gb.zip

Pixel XL 128 gig partition script https://github.com/PixelExperience-Devices/blobs/raw/main/repartition-ogpixel-128gb.zip


In the post you can click the link to install instructions from the website
 
Last edited:

spiff72

Senior Member
Apr 14, 2006
482
39
You need to flash in twrp the repartition script. Or you cannot flash this. Follow all instructions listed

Twrp doesn't flash to install recovery on Android 10 try the twrp 3.3.1 that one installed for me on Android 9 but none work on Android 10. I always boot the .img or flash the boot partition and flash the ota I want. Then if boot fails my device changes slots back to the boot slot with twrp

Pixel XL 32 gig partition script https://github.com/PixelExperience-Devices/blobs/raw/main/repartition-ogpixel-32gb.zip

Pixel XL 128 gig partition script https://github.com/PixelExperience-Devices/blobs/raw/main/repartition-ogpixel-128gb.zip


In the post you can click the link to install instructions from the website
I did flash the repartition zip file too (via adb), but I was still having trouble. Sorry I forgot to mention that step. I ended up reverting back to the Lineage 18.1 ROM instead last night.

If it helps, my Pixel XL was still stock and unlocked until I unlocked it last night. I flashed Lineage (using the flashed Lineage recovery) with no issues prior to attempting the PixelExperience ROM.
 

JovialQuestion

Senior Member
I know I had to flash the repartition script then reboot into twrp. Then the OTA would succeed. On another I had to flash the script a couple times. I do know that I wasn't able to install the plus ota and did the standard OTA listed.

If you were on stock 10 when you attempted to flash the twrp-installer.zip did it result in a boot loop? Or a white flashing screen? Sometimes I also got the blue TWRP screen flash then black. Or did it just trigger a reboot? If the screen is black. Does adb recognize the device. You can still use some TWRP features using "adb shell twrp sideload Will enable adb sideload to adb shell sideload /path/to/ota.zip ECT"

Did you try to install the newest TWRP? Or any other versions? I know I originally used OrangeFox recovery. I always just boot the recovery.

As for the failure. That's the failure you get unless the partition script is flashed.

Try to download the Pixel experience Boot.img on the download page and then fastboot reboot-recovery and use the Roms recovery instead.

Make sure to reboot recovery after the partition script
 

spiff72

Senior Member
Apr 14, 2006
482
39
I went from stock 10 (whatever is current on Marlin) to unlocking bootloader, and then flashing the Lineage recovery (which flashed fine and functioned as it should). I didn't see any bootlooping.

When I try to install TWRP (either the latest 3.7.something, or 3.5.0, I would boot from the temporary recovery image, then adb push the zip installer across, and then install that via recovery. When I would then reboot into recovery again, it seemed like it didn't "take" and it would bootloop.

I ended up fastboot flashing the lineage recovery and that one allows me to flash Lineage 18.1 without any issues.

I will give it another try here later if i have some time. I dug through more of this thread and found some detailed instructions on how to repartition manually - which looks complicated, but might be worth trying.
 

JovialQuestion

Senior Member
I know I had to flash the repartition script then reboot into twrp. Then the OTA would succeed. On another I had to flash the script a couple times. I do know that I wasn't able to install the plus ota and did the standard OTA listed.

If you were on stock 10 when you attempted to flash the twrp-installer.zip did it result in a boot loop? Or a white flashing screen? Sometimes I also got the blue TWRP screen flash then black. Or did it just trigger a reboot? If the screen is black. Does adb recognize the device. You can still use some TWRP features using "adb shell twrp sideload Will enable adb sideload to adb shell sideload /path/to/ota.zip ECT"

Did you try to install the newest TWRP? Or any other versions? I know I originally used OrangeFox recovery. I always just boot the recovery.

As for the failure. That's the failure you get unless the partition script is flashed.

Try to download the Pixel experience Boot.img on the download page and then fastboot reboot-recovery and use the Roms recovery instead.

Make sure to reboot recovery after the partition script

I went from stock 10 (whatever is current on Marlin) to unlocking bootloader, and then flashing the Lineage recovery (which flashed fine and functioned as it should). I didn't see any bootlooping.

When I try to install TWRP (either the latest 3.7.something, or 3.5.0, I would boot from the temporary recovery image, then adb push the zip installer across, and then install that via recovery. When I would then reboot into recovery again, it seemed like it didn't "take" and it would bootloop.

I ended up fastboot flashing the lineage recovery and that one allows me to flash Lineage 18.1 without any issues.

I will give it another try here later if i have some time. I dug through more of this thread and found some detailed instructions on how to repartition manually - which looks complicated, but might be worth trying.
If you flash the intended Pixel Experience Boot.img then use the volume keys to navagate to reboot recovery you will end up in the pixel experience recover intended for the install. This should allow repartition script to be sideloaded then reboot recovery again and flash the ota. Just flash the boot.img to both slots make sure to use the factory reset option first In the PE recovery and reboot recovery

So

Fastboot flash boot_a
Fastboot flash boot_b

Key boot recovery

Factory reset

Reboot-recovery
Adb sideload repartition script

Reboot recovery

Adb sideload OTA.zip


Normal boot

This is how I just installed it on a pixel XL 128gig with all stock 10
_______

I wouldn't partition manually unless you are 100% you can recover the Partition Tables. I believe the script listed is specific for this OTA to work.
_______

I will look check on a few things and if I can come up with anything else I'll post here.


If you run into anything else let me know. I'll do what I can.
 

JovialQuestion

Senior Member

This looks promising. Just be careful repartitioning.
 

spiff72

Senior Member
Apr 14, 2006
482
39
If you flash the intended Pixel Experience Boot.img then use the volume keys to navagate to reboot recovery you will end up in the pixel experience recover intended for the install. This should allow repartition script to be sideloaded then reboot recovery again and flash the ota. Just flash the boot.img to both slots make sure to use the factory reset option first In the PE recovery and reboot recovery

So

Fastboot flash boot_a
Fastboot flash boot_b

Key boot recovery

Factory reset

Reboot-recovery
Adb sideload repartition script

Reboot recovery

Adb sideload OTA.zip


Normal boot

This is how I just installed it on a pixel XL 128gig with all stock 10
_______

I wouldn't partition manually unless you are 100% you can recover the Partition Tables. I believe the script listed is specific for this OTA to work.
_______

I will look check on a few things and if I can come up with anything else I'll post here.


If you run into anything else let me know. I'll do what I can.
Just so I am clear on the commands before trying this again...

Flash the recovery to both slots (I didn't do this before with the PE recovery image - just did it without any _a or _b suffix):

fastboot flash boot_a <recovery_filename.img>
fastboot flash boot_b <recovery_filename.img>

adb reboot recovery

run factory reset inside recovery

reboot into recovery
adb sideload repartition script

reboot into recovery

adb sideload the rom zip

reboot
 

spiff72

Senior Member
Apr 14, 2006
482
39
Still no luck here. Got the same error message when flashing. one thing I noticed, there is an error message shown in recovery (see attached).

The other strange thing is that the adb sideload for the rom takes WAY longer than it does for the lineage rom.

Going to try again on different computer (I was using windows 11 pc last night, and when I tried the last process above I was using my mac, and I couldn't even get the rom zip adb to do anything - never went beyond ~0%). Going back to the PC again next.

Also, I see that the recovery shows the active slot is "b" in the photos attached. Is that correct? Is there a way to change this? I don't understand these new "slots" in newer android devices/OS's!
 

Attachments

  • IMG_3637.JPG
    IMG_3637.JPG
    1.2 MB · Views: 13
  • IMG_3636.JPG
    IMG_3636.JPG
    1.1 MB · Views: 14

spiff72

Senior Member
Apr 14, 2006
482
39
OMG - I got it to work!

I ended up following the instructions from this post:

It still went super-slow, but it made it past the 35% mark and got to the 47% completion point. I rebooted, and after a nerve-wracking period of time, it came up at the initial setup screen.
 

JovialQuestion

Senior Member
OMG - I got it to work!

I ended up following the instructions from this post:

It still went super-slow, but it made it past the 35% mark and got to the 47% completion point. I rebooted, and after a nerve-wracking period of time, it came up at the initial setup screen.
I'm glad you were able to get the rom loaded.
 

rodken

Senior Member
Jan 11, 2010
1,977
905
OMG - I got it to work!

I ended up following the instructions from this post:

It still went super-slow, but it made it past the 35% mark and got to the 47% completion point. I rebooted, and after a nerve-wracking period of time, it came up at the initial setup screen.
There are other methods to flashing ROMs besides sideloading.
-- That is another topic for another day.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 20
    NFjZzFl.png

    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
    9
    Hello, I have followed the guide until the ROM flashing step and I am stuck with the next error message:

    "Error applying update: 28 (ErrorCode::kDownloadOperationExecutionError)
    E:Error in /sideload/package.zip (status 1)"

    I have tried flashing either the Plus and the normal versions of Android 11 for marlin device.

    Can you help me, please?
    I have the same issue.

    Background: I went through the installation process successfully once. I had problems post-install however, it said no SIM inserted and I suspected a botched restore from Titanium Backup (didn't realize until too late that it's an abandoned app). So I decided to try to re-install the zip, which failed. I looked through the recovery logs and saw "no space left on device", so I perfomed a new factory reset. Still the same. So I repartitioned, then factory reset, then install zip. Still the same. So I go to step 1 and flash boot, reboot recovery, repartition, factory reset, install zip. Still the same.

    So at this point the phone is un-bootable, and I can't see how I can get it back to a working state. Any suggestions?

    EDIT: Sorry, just saw this https://forum.xda-developers.com/t/...xperience-aosp-official.4247199/post-84661869
    Going to try that!

    EDIT2: YES! It worked! So for anyone else experiencing the "kDownloadOperationExecutionError" (like @ogossorio), this is what I did:

    1. Download TWRP (twrp-3.5.1_9-0-marlin.img) from https://dl.twrp.me/marlin/
    2. Boot phone into bootloader mode
    3. Temporarily boot TWRP: fastboot boot twrp-3.5.1_9-0-marlin.img
      1. If you can't reach your phone with adb while in TWRP, try disabling MTP under "Mount"
    4. Start adb shell and perform the steps described for your phone from PixelBoot's post
    5. Power off your phone
    6. Boot into bootloader mode
    7. Flash PE recovery: fastboot flash boot PixelExperience_Plus_marlin-11.0-20210317-1910-OFFICIAL.img
    8. Boot into recovery
    9. Factory reset
    10. Flash PE: adb sideload PixelExperience_Plus_marlin-11.0-20210317-1910-OFFICIAL.zip
    11. Reboot into OS
    7
    Today's PixelExperience (16/09/2021) brings a lot of the most requested bug fixes for both Google Pixel and Google Pixel XL.
    Here's the changelog, one of which being the highly anticipated APN bug fix:

    • Fixed APN issue
    • Fixed network related issues
    • Fixed SELinux denials
    • Performance improvements
    • Other fixes

    Thanks to however contributed and made me aware about this issue, and sorry for taking so long to resolve such a bug.
    I hope that in the past days, each one of your Google Pixel devices has been performing smoother and more efficiently thanks to all the related bug fixes.
    If you run into any more bugs, kindly do let me know, even though I'm not as active on XDA, I still frequently stay up to date.
    7
    PixelExperience - UNOFFICIAL | Android 11
    Updated
    : 18/01/2022

    ▪️ Marlin [960MB]

    Changelog:
    • Revert back to original partition table.

    Notes:
    • After further analyzing the performance of the device, it was noted that UFS degradation was present during the use of the new repartitioned table, so therefore this build removes some of the system packages in order to satisfy the stock partition table found on the Pixel.
    • If you currently find yourself on a ROM which required repartition, kindly flash the stock images (https://developers.google.com/android/images) for your respective device to revert to the original partition table.
    7
    No luck. Fails after 2/2.

    Error applying update: 5 (ErrorCode::kPostInstallRunnerError)


    This is exactly what I have been doing. Doing it multiple times does not appear to make it more successful. I was following the install guide on the PIxelExperience website precisely.
    Then your last resort is going to TWRP and using the shell to input the following commands:
    Google Pixel/XL (32GB):

    sgdisk --delete=33 /dev/block/sda
    sgdisk --delete=34 /dev/block/sda
    sgdisk --delete=35 /dev/block/sda

    sgdisk --new=33:227142:1275716 --change-name=33:system_a --typecode=33:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
    sgdisk --new=34:1275717:2324291 --change-name=34:system_b --typecode=34:77036CD4-03D5-42BB-8ED1-37E5A88BAA34 /dev/block/sda
    sgdisk --new=35:2324292:7785285 --change-name=35:userdata --typecode=35:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda

    Google Pixel/XL (128GB):

    sgdisk --delete=33 /dev/block/sda
    sgdisk --delete=34 /dev/block/sda
    sgdisk --delete=35 /dev/block/sda

    sgdisk --new=33:227142:1537862 --change-name=33:system_a --typecode=33:77036CD4-03D5-42BB-8ED1-37E5A88BAA34 /dev/block/sda
    sgdisk --new=34:1537863:2848582 --change-name=34:system_b --typecode=34:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
    sgdisk --new=35:2848583:31215429 --change-name=35:userdata --typecode=35:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda