[ROM][Pixel 3 XL][13.0.0_r8] PixelDust Android 13 for crosshatch [5 October 2022]

Search This thread

Ashwin Kale

Senior Member
Jun 26, 2016
184
36
@spezi77 hi, how can I root the phone without using any other recovery? On pixel dust recovery the verification is failed everytime I try to install magisk... So What I did is I flash Pixel Experience recovery for A13... But my kernel got changed to Neko Miya instead of Kirisakura...
Have a look please...
What is the solution for this?

Edit :
My bad, It's been a while since I have patched boot.img file from magisk manager that I forget that option even exist, LOL !
Now I am on kirisakura again with root and freeze free kernel...
 

Attachments

  • Screenshot_20221008-051746.png
    Screenshot_20221008-051746.png
    165.8 KB · Views: 73
Last edited:
  • Like
Reactions: spezi77

lingarajug

Senior Member
Apr 6, 2010
484
77
Roanoke, VA
SO i have the june 2022 stock update on my phone, have been using stock since i got this on release date, do i have to flash back to march update and then unlock bootloader, then follow the steps or am i good to go with oem unlock, also how do i know if i have both slots flashed(is there a way to check it), also is it possible to restore a backup from google one that is in my phone on A12 to A13 ( i faintly remember that backups dont crossover to newer android versions), sorry it has been about 3 years since i have done any of this stuff and i am out of shape for this, any help appreciated.
 
Last edited:
SO i have the june 2022 stock update on my phone, have been using stock since i got this on release date, do i have to flash back to march update and then unlock bootloader, then follow the steps or am i good to go with oem unlock, also how do i know if i have both slots flashed(is there a way to check it), also is it possible to restore a backup from google one that is in my phone on A12 to A13 ( i faintly remember that backups dont crossover to newer android versions), sorry it has been about 3 years since i have done any of this stuff and i am out of shape for this, any help appreciated.
You can go ahead and unlock your bootloader as you are. It will wipe your phone. I suggest getting swift backup to restore your data. But before restoring your data, i would from here flash the latest stock to both slots (search on here for how to) and then go through the process of rooting and setting up/restoring data. My opinion. That's how I would do it. The only caveat being I would use the pixel flasher to do it (again search on here for how to).
Hope this helps.
 
  • Like
Reactions: lingarajug

rubnduardo

Member
Nov 23, 2012
37
11
Maracaibio
I've searched for some way to change the bootanimation to no avail. I know system is supposed to be read only but i don't know if we can make this by flashing or else.

Do you guys can give me some help?

It's the only think i don't like about the rom, otherwise it's perfect. Great job OP.
 

lingarajug

Senior Member
Apr 6, 2010
484
77
Roanoke, VA
I've searched for some way to change the bootanimation to no avail. I know system is supposed to be read only but i don't know if we can make this by flashing or else.

Do you guys can give me some help?

It's the only think i don't like about the rom, otherwise it's perfect. Great job OP.
I remember when I was using lg g2 back in the day it was rooted and copy pasted the boot animation file and set permissions for it, but since then Android folder structure changed a lot so idk anything now.
 

lingarajug

Senior Member
Apr 6, 2010
484
77
Roanoke, VA
You can go ahead and unlock your bootloader as you are. It will wipe your phone. I suggest getting swift backup to restore your data. But before restoring your data, i would from here flash the latest stock to both slots (search on here for how to) and then go through the process of rooting and setting up/restoring data. My opinion. That's how I would do it. The only caveat being I would use the pixel flasher to do it (again search on here for how to).
Hope this helps.
thank you, everything went fine and i am booted into rom, i believe i am currently on slot a and should i switch slots and flash this again in slot b, and how do i restore data from google ONE of this old phone to this new phone.
 

tkacer

Senior Member
Oct 25, 2012
552
216
BF, MI
www.wmcc.org
Google Pixel 3 XL
Please try again. Follow the instructions. I hope it works for you on the second attempt. 🙏
I know this post pertains to A11, but the same thing is happening to me with this A13 version even tho I did flash stock to both slots prior. I finally tried to flash the custom boot.img to both slots and even side loaded this rom to both slots to no avail. I'm perplexed , what am I missing or screwing up???!
 

spezi77

Recognized Developer / Contributor
Jan 27, 2013
3,519
7,845
/home/less
You can go ahead and unlock your bootloader as you are. It will wipe your phone. I suggest getting swift backup to restore your data. But before restoring your data, i would from here flash the latest stock to both slots (search on here for how to) and then go through the process of rooting and setting up/restoring data. My opinion. That's how I would do it. The only caveat being I would use the pixel flasher to do it (again search on here for how to).
Hope this helps.
Thanks for your reply. Highly appreciated!
However, it is also possible to use Google One for the backup to migrate to a13. At least for me it worked fine.
I know this post pertains to A11, but the same thing is happening to me with this A13 version even tho I did flash stock to both slots prior. I finally tried to flash the custom boot.img to both slots and even side loaded this rom to both slots to no avail. I'm perplexed , what am I missing or screwing up???!
So if you reboot after the flash process and the custom ROM you installed does not appear as expected, but the stock ROM, then something went wrong with the installation that caused the installation process to be aborted. I recommend you take a look next time to see if you get an error message. Then please post it here. Have a nice day!
 

tkacer

Senior Member
Oct 25, 2012
552
216
BF, MI
www.wmcc.org
Google Pixel 3 XL
Thanks for your reply. Highly appreciated!
However, it is also possible to use Google One for the backup to migrate to a13. At least for me it worked fine.

So if you reboot after the flash process and the custom ROM you installed does not appear as expected, but the stock ROM, then something went wrong with the installation that caused the installation process to be aborted. I recommend you take a look next time to see if you get an error message. Then please post it here. Have a nice day!
I will definately do that, but I have gotten a successful looking "pixeldust" completion msg each time I have flashed it......stay tuned and thanks for the prompt reply!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    The opposite happened to me. I had this same issue running stock. Out of nowhere, I got the persistent USB charging message, and could only charge my phone with the USB plugged in one direction. I know USB C works in both directions but when I had this message it would only charge in one direction, and not at all with some chargers/cords. After flashing this ROM the message went away and has not come back, and I'm able to charge normally.
    It's not the ROM.
    Thanks for answering me! You are correct once install new rom, no problem for a while.. but after few day back to same issues again!!! I will try to change charging port but I don't thinks so!! Anyway thanks a lot!!
    1
    Great ROM, smooth as silk so far. It has been awhile since I have done custom ROM's, but any updates will be in the first post correct?
    1
    I installed the image today. So far everything works except VoWIFI
    I have the feeling that it runs more smoothly than the last Android 12 stock version.
    It's just something funny that in the menu backup a Pixel 6 Pro appears and in the Google account a Huawei Nexus 6P is shown.
    Additionally I have locked the bootloader again. To do this, I extracted the public key from the image and deposited as custrom key in the AVB. Now the device runs with Secureboot: Production and Device state: locked
    Only the note " Your Device is loading a different operationg system" is shown.

    I am curious how the next updates look like. Also with reference to AVB.
  • 15
    XDA_banner_2022.png

    PixelDust ROM is an Android 13 ROM based on the source code of the AOSP with all the official Pixel features.

    Furthermore we're adding a minimal selection of the coolest custom ROM features that might have been missing if they weren't included.

    Special shoutouts to Roger.T for his amazingly designed wallpapers, logos and an amazing bootanimation! If you like our work, please consider to buy Roger the first beer, and a few cups of coffee for spezi77. Cheers!

    Help us help you!

    If you find a bug in one of our builds, please report it here or in our Telegram Group. You MUST include the following when posting a bug report:
    1. A logcat or last_kmsg
    2. Kernel and mods used
    3. Useful information (which build, steps for reproduction, screenshots, etc.)

    If you fail to report something adequately, DO NOT expect things to be fixed.

    Disclaimer:
    If your device fails to comply with your standards of what you consider functioning, I am not liable. This is provided free of charge and does not come with a warranty. Although, if you provide a log, I can provide some sort of assurance that I will look into your issue.


    Listing%20of%20Features.png


    * Periodic AOSP security updates
    * Pixel GApps included (no need to flash any third party GApps)
    * Safety net / banking and payment apps work out of the box (no need to root)

    Pixel 3 features
    * Smartspace/weather info on lockscreen
    * Now playing support
    * Gaming Dashboard
    * Quick tap
    * Adaptive connectivity
    * 24h battery usage stats / Battery estimates
    * Onehanded mode
    * Battery level on bottom
    * Show bluetooth battery level

    Enhanced Pixel features
    * Free and unlimited Google photo storage (in original quality)!
    * ActiveEdge customization (powered by kdrag0n's Elmyra service)
    * Allow recording of system audio when screen recording
    * Allow to switch usage stats from last full charge & for past 24h hours

    UI customisation
    * First-class Repainter support without root

    Lock screen
    * Show Ambient instead of lock screen on wake gestures
    * Double tap to sleep on lock screen

    Security
    * Lock screen quick unlock
    * Lock screen option to scramble PIN

    PixelDust wallpapers
    * A set of 22 breathtaking space themed Wallpapers




    Known%20issues.png

    * VoWifi not working
    * You tell me

    Links.png

    Terms & conditions:
    By downloading this custom ROM you agree that I, the developer of PixelDust ROM, am not liable in any way, shape or form for any damage done to your device. The PixelDust ROM is provided free of charge and does not come with a warranty.


    Social%20Media.png


    Telegram%20Group.png

    Telegram Discussion Channel: https://t.me/pixeldustcommunity
    Telegram Announcements Channel: https://t.me/pixeldustproject
    Telegram Build Support Channel: https://t.me/compile_pixeldust

    Donators.png

    If you like our work then please consider donating.
    PayPal: https://www.paypal.me/RogerTruttmann | https://www.paypal.me/spezi77

    Who last donated:
    Tengku Azwan Bin Mamat
    Dominik Laignel
    Simone Scanzoni
    Elizabeth Laughlin

    Installation%20guide.png


    Pre-requisites:
    * You are familiar with helping yourself out of awkward situations. You won't defame or complain at the developer of this ROM for your misfortunes.
    * You are familiar with using fastboot
    * Before you are ready to flash this custom ROM, you have to install the latest factory image from October 2021
    * Bootloader unlocked
    * You have created a backup of your ROM & data

    First time installing PixelDust ROM, or coming from another ROM:

    YOU MUST HAVE an Android 12 FACTORY IMAGE FLASHED TO BOTH SLOTS BEFORE YOUR FIRST TIME INSTALLING ROM.

    1. Flashing stock ROM / unlock bootloader (If applicable):
    1. Follow these instructions: https://developers.google.com/android/images#crosshatch
    2. Boot the stock ROM.
    3. Don't setup any google account, don't add a screen lock. Just go to Settings > System > Developer options. Enable OEM unlocking.
    4. You need to follow this guide to unlock your bootloader.
    2. There are now two options for the installation. Either via TWRP or via Sideload (for advanced users).

    A. Flashing PixelDust ROM via TWRP:

    1. Download the ROM and both TWRP files (img + zip) (for download links see above).
    2. Boot fastboot mode.
    3. Connect the phone to the Computer with USB cord.
    4. Copy twrp-3.6.2_11-0-crosshatch.img to the platform-tools folder or folder that has fastboot in it and rename it twrp.img.
    5. Open a Command Prompt.
    6. At the Command Prompt type and press enter.
      Code:
       fastboot boot twrp.img
    7. If requested, swipe to allow modifications.
    8. Tap "Wipe", then tap "Format data" and type yes to continue.
    9. Copy the rom zip and twrp-installer-3.6.2_11-0-crosshatch.zip to your device.
    10. Tap "Install", select the rom zip, tap "Add more Zips", select the twrp-installer.zip and Swipe Slider to install.
    11. When install is successful tap on "Reboot", then tap on the first list item "System".


    B. Flashing PixelDust ROM via sideload:

    1. Download the ROM and boot image (for download links see above)
    2. Boot fastboot mode
    3. Connect the phone to the Computer with USB cord.
    4. Flash the boot image (this allows stock recovery to flash unsigned rom zip)
      Code:
      fastboot flash boot boot_aosp_xxx.img
    5. Wipe userdata (required for first PixelDust/Android 13 install)
      Code:
      fastboot erase userdata
    6. Reboot into fastbootd
      Code:
      fastboot reboot fastboot
    7. Use volume keys and power button to select "Enter Recovery"
    8. Select "Apply Update from ADB"
    9. Sideload the ROM zip
      Code:
      adb sideload PixelDust-Tiramisu-aosp-crosshatch-user-xxx.zip
    10. Reboot


    Dirty flashing PixelDust ROM (coming from a previous PixelDust A13 ROM):
    Just skip the step "Format data" / "Wipe userdata"



    Credits.png

    AOSPA (https://github.com/aospa)
    AOSP Extended (https://github.com/AospExtended)
    ABC ROM (https://github.com/ezio84?tab=repositories)
    CAF Extended (https://github.com/CAF-Extended)
    CarbonROM (https://github.com/Carbonrom)
    LineageOS (https://github.com/LineageOS)
    crDroid (https://github.com/crdroidandroid)
    DirtyUnicorns (https://github.com/dirtyunicorns)
    Havoc OS (https://github.com/havoc-os)
    Nitrogen Project (https://github.com/nitrogen-project)
    OmniROM (https://github.com/omnirom)
    Pixel Experience (https://github.com/PixelExperience)
    Potato Open Sauce Project (https://github.com/PotatoProject)
    ProtonAOSP (https://github.com/ProtonAOSP)
    MSM-Xtended Team (https://github.com/Project-Xtended)
    Superior OS (https://github.com/SuperiorOS)
    Syberia Project (https://github.com/syberia-project)
    And all the other Developers, Testers, Donators and Users.


    Kernel%20source.png


    XDA:DevDB Information
    [ROM][Pixel 3 XL][13.0] PixelDust Android 13 for crosshatch, ROM for the Google Pixel 3 XL

    Contributors
    spezi77

    Source Code: https://github.com/pixeldust-project-caf

    ROM OS Version: Android 13
    ROM Kernel: Linux 4.x
    Based On: AOSP

    Version Information
    Status:
    Stable

    Created 2021-02-02
    Last Updated 2022-10-05
    15
    12
    Changelog

    2022-10-05

    * Initial build
    * Security patch level: 2022-10-05
    * Based on AOSP tag: android-13.0.0_r8 (TP1A.221005.003)

    Caution:
    If coming from a previous A12 build or other ROM a clean flash is always recommended.
    11
    Hello folks, I've updated the links now to point to the latest & greatest build. You can use the boot.img from September. It will work just fine.

    This is very likely the last A11 based build.. we'll now jump straight to A12...
    6
    The new build (1.6GB) is here now.