[ROM][Pixel 3 XL][13.0.0_r8] PixelDust Android 13 for crosshatch [5 October 2022]
- Thread starter spezi77
- Start date
Okay cool, The developer of kirisakura hasn't uploaded latest build so that is why I asked.
Thanks for the headsup.
This is probably due to the fact that there are no longer any official kernel updates from the AOSP because our device is end of life.Okay cool, The developer of kirisakura hasn't uploaded latest build so that is why I asked.
Thanks for the headsup.
Do u know if esim will work I have a pixel 3 and the SIM card tray won't recognise simcard so using esim
@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...
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
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.
Last edited:
Slim2none4u
Senior Member
- Oct 28, 2011
- 833
- 497
- 49
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.
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.
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.
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.
Has Google made the pixel launcher mandatory, I am trying to use my old Evie launcher but it's not sticking.
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???!Please try again. Follow the instructions. I hope it works for you on the second attempt.
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!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
16
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.
* VoWifi not working
* You tell me
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.
- Download PixelDust ROM: https://download.pixeldust-project.com/PixelDust-Tiramisu-aosp-crosshatch-user-20221005-0744.zip
- Download boot.img: https://download.pixeldust-project.com/boot_aosp_crosshatch_10_22.img
- Download TWRP (twrp-3.6.2.11-0) : https://twrp.me/google/googlepixel3xl.html
Telegram Discussion Channel: https://t.me/pixeldustcommunity
Telegram Announcements Channel: https://t.me/pixeldustproject
Telegram Build Support Channel: https://t.me/compile_pixeldust
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
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.
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
