[ROM][13.0][taimen] Pixel Experience [AOSP]

Search This thread

alaviss

Member
Jul 25, 2014
10
2
No root for January build so far!

I've tried flashing the latest Canary and Dev. Magisk builds v 25206. I also tried flashing a patched boot image with these Magisk builds. They all bootlooped. I gave up! Anyone found a solution that actually works?
Right now you can't enter recovery with PE due to boot loops. Until that's fixed, Magisk will never work.

This is because Magisk on this device works by booting to initramfs (recovery), then boot into the OS. However if you can't boot into built-in recovery then that will never work.
 

Alxoom33

Senior Member
May 18, 2011
5,128
1,836
New York
www.sack-ip.com
Right now you can't enter recovery with PE due to boot loops. Until that's fixed, Magisk will never work.

This is because Magisk on this device works by booting to initramfs (recovery), then boot into the OS. However if you can't boot into built-in recovery then that will never work.
I'm rooted with PE+ ! Key was to first uninstall the Magisk app!

Then you can flash the latest Magisk Canary build in TWRP and install the Magisk apk after the device is rooted!
 

Alxoom33

Senior Member
May 18, 2011
5,128
1,836
New York
www.sack-ip.com
Where we can find or make this folder? How to find him after flashing rom and formated data?
You need to be rooted, then go to #Root/Data/Unencrypted and open a new folder for flashing. It will be deleted when you format data, so back it up on your computer. You can sideload from the backed-up folder when you are not rooted.
 

Giargo

Member
May 5, 2015
23
6
Hello, I'm trying to install this ROM for the first time and i successfully installed the recovery, although, when I start sideloading the zip from ADB, all I get is "Installing update" on the screen of the phone, and no progress on the terminal (basically it gets stuck after I press enter). I also tried installing the partition table but I get the exact same result. I tried with both PE12.1 and 13, no avail.
The drivers should be fine as I then reverted to stock without issues. Any ideas?
 

runekock

Senior Member
Apr 24, 2012
989
551
Samsung Galaxy Tab S
Nexus 6
Hello, I'm trying to install this ROM for the first time and i successfully installed the recovery, although, when I start sideloading the zip from ADB, all I get is "Installing update" on the screen of the phone, and no progress on the terminal (basically it gets stuck after I press enter). I also tried installing the partition table but I get the exact same result. I tried with both PE12.1 and 13, no avail.
The drivers should be fine as I then reverted to stock without issues. Any ideas?
Windows uses a different driver when the phone is in recovery, so that is still the most likely problem
 

nitin.chobhe

Recognized Contributor
Jan 3, 2013
8,261
19,863
Pune
Google Pixel 2 XL
Hello, I'm trying to install this ROM for the first time and i successfully installed the recovery, although, when I start sideloading the zip from ADB, all I get is "Installing update" on the screen of the phone, and no progress on the terminal (basically it gets stuck after I press enter). I also tried installing the partition table but I get the exact same result. I tried with both PE12.1 and 13, no avail.
The drivers should be fine as I then reverted to stock without issues. Any ideas?
I had similar issues couple of weeks ago - installing stock image and starting it all over solved the issue.

Nitin
 
  • Like
Reactions: Alxoom33

Mags Power

Member
Jul 2, 2014
6
2
I guys, just installed the PE 13 +, runs very smooth but I noticed an issue when i wake the screen from standby, everything stop working for 1 2 second. Even spotify stop playing music and then start again. Seems like the smartphone freeze for s couple of second every time i wake the screen. The funny thing is that doesn’t happen if i enable the battery savings. Anyone have the same issue ?
 

hibariruled

New member
Feb 12, 2023
2
1
I guys, just installed the PE 13 +, runs very smooth but I noticed an issue when i wake the screen from standby, everything stop working for 1 2 second. Even spotify stop playing music and then start again. Seems like the smartphone freeze for s couple of second every time i wake the screen. The funny thing is that doesn’t happen if i enable the battery savings. Anyone have the same issue ?
I have exactly the same issue.
The music is freezing for about 2 sec right after unlocking the phone.

Also, when I used AIMP music player sometimes after unfreezing, the pitch of the song changed to a lower one (like in some pitched down song on YouTube)
When I changed music player to another one - the pitch stopped from changing, but the sound is still freezing after unlocking the phone.

Tried to turn off Lock Sound - nothing changed.
So currently I don't know how to fix it.

(I'm using PE plus 2022.11.19)

Upd. Tried enabling battery savings mode - the issue really disappears.
 
  • Like
Reactions: あなたの

runekock

Senior Member
Apr 24, 2012
989
551
Samsung Galaxy Tab S
Nexus 6
I guys, just installed the PE 13 +, runs very smooth but I noticed an issue when i wake the screen from standby, everything stop working for 1 2 second. Even spotify stop playing music and then start again. Seems like the smartphone freeze for s couple of second every time i wake the screen. The funny thing is that doesn’t happen if i enable the battery savings. Anyone have the same issue ?
This seems to be a problem on all roms if "now playing" is enabled. Maybe the battery saver disables now playing.
 
  • Like
Reactions: hibariruled

あなたの

New member
Nov 17, 2020
3
3
Very bad. It works very poorly compared to the last release. I installed the PE 01.10 update, the first thing that did not please me: installing the update on a clean one. Further, after OOBE, the biggest problem was revealed: system animations that are getting stuck (they can slow down at any moment, and this is not dying RAM, because everything is fine in applications and there were no problems with this on the last build). Broken song names on AOD (they are not shown, and the date and weather are always shown instead) as well as non-working Bluetooth conversations (Google phone sees that the headset is connected and even selects it as the main audio output/input, but it still goes through the speaker and microphone of the phone. And now what they can't fix since the release: the lack of multimedia sound when the screen is locked / unlocked (disappears for about 1-2 seconds, but sometimes the sound is not interrupted, I wanted to record the screen with this problem, but on the record it doesn't look like in real life). So far, that's all I've noticed and most likely won't notice anymore, I'm rolling back to the previous build. I'm waiting for ctf to be fixed, because of the new verification method from Google, NFC payment does not work.
 
  • Like
Reactions: Alxoom33

Alxoom33

Senior Member
May 18, 2011
5,128
1,836
New York
www.sack-ip.com
Very bad. It works very poorly compared to the last release. I installed the PE 01.10 update, the first thing that did not please me: installing the update on a clean one. Further, after OOBE, the biggest problem was revealed: system animations that are getting stuck (they can slow down at any moment, and this is not dying RAM, because everything is fine in applications and there were no problems with this on the last build). Broken song names on AOD (they are not shown, and the date and weather are always shown instead) as well as non-working Bluetooth conversations (Google phone sees that the headset is connected and even selects it as the main audio output/input, but it still goes through the speaker and microphone of the phone. And now what they can't fix since the release: the lack of multimedia sound when the screen is locked / unlocked (disappears for about 1-2 seconds, but sometimes the sound is not interrupted, I wanted to record the screen with this problem, but on the record it doesn't look like in real life). So far, that's all I've noticed and most likely won't notice anymore, I'm rolling back to the previous build. I'm waiting for ctf to be fixed, because of the new verification method from Google, NFC payment does not work.
You are correct, the 1/10/23 update is practically unusable. But and A13 Rom is a work in progress, and I expect that the next iteration of PE and PE+ to be much better.
 

あなたの

New member
Nov 17, 2020
3
3
You are correct, the 1/10/23 update is practically unusable. But and A13 Rom is a work in progress, and I expect that the next iteration of PE and PE+ to be much better.
I have a suspicion that the A13 itself has become more demanding since the update in which the progressbar in the player was changed, because it was from this update that Google outgrew sending updates to the Pixel 4/4Xl (except for security updates, they still come).
I really hope that the next PE updates will be better.
 
  • Like
Reactions: Alxoom33

Osaxely

Member
Mar 22, 2022
6
1
Google Pixel 2 XL
When I try to flash this rom (Pixel Experience 13 Plus Edition, last February build), I keep getting the error:
Code:
Error applying update: 28 (kDownloadOperationExecutionError)

I have followed carefully the guide on the Wiki (flashed the right recovery and partition table. I'm not sure on what to do, if someone could help me, it'd be good.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    I have followed carefully the guide on the Wiki (flashed the right recovery and partition table. I'm not sure on what to do, if someone could help me, it'd be good.

    Had the same issue. Resizing the partition wasn't quite working for me on my Pixel2XL. I flashed TWRP on boot_a and set that to active and then ran the extended partition zip via TWRP, formatted, then set it back to boot_b and once in recovery was able to sideload correctly.

    Essentially...

    Flash recoveries
    Bash:
    fastboot flash boot_a [TWRP]
    fastboot flash boot_b [PE-recovery-image]
    fastboot --set-active=a
    fastboot reboot recovery

    Fix Partitions via TWRP

    In TWRP => Advanced > ADB Sideload
    Bash:
    adb sideload productpartition-pixel2xl-extended.zip
    Wipe Data etc
    Reboot to bootloader
    Bash:
    fastboot --set-active=b
    Reboot to recovery

    Updated PE
    Factory Reset
    Bash:
    adb sideload [PixelExperience.zip]
    Reboot

    I may have missed a couple of reset steps, I do reset before and after flashing - just to be shure, to be shure.
    3
    As mentioned in an earlier post, I tried the latest version of Lineage. Same problem with connectivity. No connectivity whatsoever with the AT&T SIM card, text+data but no calls with the H2O card. So it appears this is an issue with Android itself, something common to the custom ROMs based on it and not specific to PE.

    What I do think is egregious about PE is that you can't load the damned thing because of the problem with the partitioner vs the recovery they provide. And there is no mention of this problem that goes back at least a year in their instructions. I realize this is free software, but if you are going to do it, do it right!! I posted an issue about this on github a few days ago and have gotten no response. Similarly, I posted a pull request on github to update the wiki about the partitioner issue. Again, no response. Feels like a black hole.
    2
    yes correct zip
    failed in twrp
    Try flashing the product zip to both slots by changing them in TWRP or manually via command prompt
    Ensure you reboot to fastboot and then reboot back into TWRP each time.
    Then factory reset in TWRP and adb push rom.zip and install it from there.
    Good luck!
    2
    (THESE INSTRUCTIONS NO LONGER WORK)

    Hi there, Make sure you are connected to a USB 2.0 Port, If so try these steps.
    1. Download TWRP.
    2. Download PE recovery.
    3. Download Pixel Experience.
    4. Download the repartition script from the install instructions.
    5. Reboot into bootloader.
    6. fastboot flash boot_a [TWRP recovery path]
    7. fastboot flash boot_b [PE recovery path]
    8. fastboot --set-active=a
    9. fastboot reboot recovery
    TWRP should open. Click on Advanced, then on ADB Sideload. Swipe to start.

    1. Plug your phone.
    2. Run on the PC adb sideload [Repartition ZIP path].
    3. Back in TWRP, go back, click Reboot, and Bootloader. Accept the warning.
    4. Run on PC fastboot --set-active=b
    5. On phone reboot to recovery mode
    PE recovery should open.

    1. Run a factory reset from there.
    2. Go back.
    3. Apply update -> Apply from ADB.
    4. adb sideload [PE ZIP path]
    5. Run a factory reset.
    6. Reboot to system.
    So I just had to follow these again when trying to update to PE 13 from PE 13 beta. Still works :)
    2
    I too had trouble with the same error when trying to sideload the ROM

    I followed your advice and was able to successfully boot up

    For some reason flashing the repartition zip under twrp instead of pixel experience recovery did the trick

    After using twrp to flash the repartition zip I changed slots and went back to pixel experience recovery to sideload the ROM with no trouble
    I also had the experience of following the PE instructions to the letter and getting Error 7. Sideloading the partitioner with TWRP instead of their supplied recovery fixes that problem.

    I did this install having first installed the stock rom and had it up and running. Verified that cellular calling worked. Then installed PE 13 as above. No cellular service: "Emergency calls only". I noticed when the system first came up that the signal strength icon briefly showed that it had a signal. Then nothing, with the exclamation point. It does see the SIM card and gets the phone number from it correctly. Signal strength = 0. Unknown voice and data network type. The SIM card is AT&T.

    Unless I can fix this, my choice with this phone is to go back to the stock ROM and take a chance on being without 2.5 years of security updates, or have a cell phone that can't make cellular calls. Too bad, because the 2XL is still excellent hardware with really good antennas. I've tried newer Android phones, e.g., OnePlus, and had serious signal-strength issues. I did comparative measurements between the 2XL and the OnePlus, and saw a factor of as much as 1000 greater signal strength (in milliwatts) on the 2XL vs the OnePlus at exactly the same place within my house.

    Any suggestions on the lack of cellular connectivity would be appreciated.
  • 21
    GtwTyCR.png

    PixelExperience for Google Pixel 2 XL [taimen]

    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.0

    Whats working?
    Wi-Fi
    RIL
    Mobile data
    GPS
    Camera
    Flashlight
    Camcorder
    Bluetooth
    FM radio
    Sound/vibration

    Known issues
    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
    Hate to ask but how did you install? I am following the instructions that i posted for previous version of Pixel Expeirnece but they arent working now...How did you do it? Tia!
    This is how I installed the Pixel Experience 13 (January 10, 2023) update:

    *Please read the steps before performing them*

    - In Bootloader (Fastboot) mode, I entered the command ' fastboot -w ' (to factory reset the device)
    - Then, I booted (did not flash) TWRP recovery IMG with the command ' fastboot boot twrp-3.6.0_9-0-taimen.img '
    - Then, in TWRP, I clicked on ' Advanced ' and then ' ADB sideload ' and then I sideloaded the 'productpartition-pixel2xl-extended.zip' from the Pixel Experience Website. I entered the command ' adb sideload productpartition-pixel2xl-extended.zip '
    - Then, I rebooted to Bootloader from TWRP by clicking on ' back ' then I clicked on ' reboot ' and clicked on ' Bootloader ', and in Bootloader (Fastboot mode), I entered the command ' fastboot -w ' again, to factory reset.
    - Then again, I booted (did not flash) TWRP recovery IMG with the command ' fastboot boot twrp-3.6.0_9-0-taimen.img '
    - In TWRP, I clicked on ' Advanced ' and then ' ADB sideload ' and then I sideloaded the Pixel Experience 13 (January 10, 2023) update, with the command ' adb sideload PixelExperience_taimen-13.0-20230110-0731-OFFICIAL.zip '
    - Then again, I rebooted to Bootloader from TWRP by clicking on ' back ' then I clicked on ' reboot ' and clicked on ' Bootloader ', and in Bootloader (Fastboot mode), I entered the command ' fastboot -w ' again, to factory reset.
    - Finally after ' fastboot -w ' in Bootloader (Fastboot mode), I entered the command ' fastboot reboot '

    And after a moment, I successfully booted into Pixel Experience 13 (January 10, 2023) update.

    Hope this helps.

    Cheers!
    6
    I have followed carefully the guide on the Wiki (flashed the right recovery and partition table. I'm not sure on what to do, if someone could help me, it'd be good.

    Had the same issue. Resizing the partition wasn't quite working for me on my Pixel2XL. I flashed TWRP on boot_a and set that to active and then ran the extended partition zip via TWRP, formatted, then set it back to boot_b and once in recovery was able to sideload correctly.

    Essentially...

    Flash recoveries
    Bash:
    fastboot flash boot_a [TWRP]
    fastboot flash boot_b [PE-recovery-image]
    fastboot --set-active=a
    fastboot reboot recovery

    Fix Partitions via TWRP

    In TWRP => Advanced > ADB Sideload
    Bash:
    adb sideload productpartition-pixel2xl-extended.zip
    Wipe Data etc
    Reboot to bootloader
    Bash:
    fastboot --set-active=b
    Reboot to recovery

    Updated PE
    Factory Reset
    Bash:
    adb sideload [PixelExperience.zip]
    Reboot

    I may have missed a couple of reset steps, I do reset before and after flashing - just to be shure, to be shure.
    6
    PixelExperience 13.0 January Update

    Disclaimer
    :
    • This build of PixelExperience requires the new partition table to be set up before flashing.
    • As a consequence of this, it is suggested that any data present on older builds of PixelExperience are backed up before updating.
    • Given either a stock partition table, or a previously defined partition table given from the PixelExperience wiki, Product Partition (Extended) will adapt accordingly.
    • Kindly follow the necessary procedure from the following:
    https://wiki.pixelexperience.org/devices/taimen/install/
    3
    Can't boot into recovery after flash recovery in fastboot mode, just show a "G" logo with a progress indicator.
    Device now on Pixel Experience 13 plus edition (20221119).
    Any one else has the same problem?