[ROM][Pixel 3][10.0.0_r41] PixelDust CAF Android 10 for blueline [7 Aug 2020]
- Thread starter spezi77
- Start date
Have you flashed one of the test builds? I"d love to move to android 11, but I"m waiting for them to finish testing before I flash up again. It takes a long time to move ~100+ gbs of data back over. How's your experience with the newer builds. Please specify which you''ve tested.
I am presently on it. I have no issues at all except safety net. Runs excellent
Awesome, and great to hear. I'm going to wait as they've not posted it as ready. I appreciate your response.
I was wondering the same thing after noticing active builds for 11. The development gives me hope to extend the life of my Pixel 3 since most other devs have abandoned ship just from looking at threads here. Looking forward to supporting future development. 
If you don't need to worry about safety net at all, I'd recommend flashing imo.I was wondering the same thing after noticing active builds for 11. The development gives me hope to extend the life of my Pixel 3 since most other devs have abandoned ship just from looking at threads here. Looking forward to supporting future development.
I'm definitely tempted. I wonder if props config would work in combination with Magisk like it does for this rom. I haven't spent the time to understand the ins and outs of Magisk's limitations and such when it come to android 11 yet. Having access to google pay has been nice, though, so not sure I'm ready to jump ship just yet.
Can't you just use magisk hide props config and set to pixel 3 a fingerprint. Been using Android 11 ROMs that passed safety net on my pixel 4a and that is always worked. Currently on lineage on Pixel 3 and used it and it worked as well to pass safety net
can you please help me? I'm trying to install magisk on PixelDust 11. I'm using latest version of ROM 20201111 that was released today. I've installed ROM without any problems, after first boot installed Magisk manager 8.0.2 and patched boot.img from the same download folder as ROM, boot.img date is 2020-11-04. After flashing patched image I'm getting bootlop, and image is different size from the original, that is not patched, about 29mb. I tried several times to patch it again but getting the same result. Did you use some other approach, or maybe different ROM, boot.img and Magisk manager combination worked for you? I didn't find where to get boot.img for patching other then download folder for 11 version.
Go into magisk manager and select install
Select patch a file
Select boot.img
Copy new magisk_patched.img to adb folder
Boot into bootloader
Type in fastboot flash --slot all Boot magisk_patched.img
Select enter
Boot device
Please try magisk manager /// update channel BETA!! This is works! created image size not different.
I'm going to give the latest alpha build (20201111-2328) a whirl later. I tried searching for changelogs, news, announcements, updates, theories (you name it) on their telegram and discord or traces of GitHub that I could find. There hasn't been much in the way of activity in months at first glance. To whomever is putting in the extra effort for developing the blueline tree, if there's a place to know what changes are being implemented to have an idea what to expect, that would be nice since I really want to contribute and provide useful feedback. I don't want to state things that are still WIP nor be confused by something that wasn't intended to work yet is all. I'm sure there are others that share my same view and would love to jump at the chance to help.
+1I'm going to give the latest alpha build (20201111-2328) a whirl later. I tried searching for changelogs, news, announcements, updates, theories (you name it) on their telegram and discord or traces of GitHub that I could find. There hasn't been much in the way of activity in months at first glance. To whomever is putting in the extra effort for developing the blueline tree, if there's a place to know what changes are being implemented to have an idea what to expect, that would be nice since I really want to contribute and provide useful feedback. I don't want to state things that are still WIP nor be confused by something that wasn't intended to work yet is all. I'm sure there are others that share my same view and would love to jump at the chance to help.
okay, so I had a different problem first but now it's changed. After some difficulty I finally managed to get through the whole installation and it said it loaded pixeldust rom but when I rebooted it's just plain android. I don't understand what's going on. >.< I think it might be because when I was installing it I got the error "signature verification failed, install anyway?" and I said yes. Maybe that broke the installation? I don't know.
Last edited:
@PistolSlap you need to flash stock on both slots...and flash caf boot image....no need to rename it
Okay, thank you. Can you describe to me how to switch slots so I can flash it again?
@PistolSlap enter fastboot and simply type "fastboot --set-active=a" if you are in slot b, if you are in slot a, type "fastboot --set-active=b"
I use a very good stable, daily driver ROM. I haven't found a change log but you can notice the change
! more and more settings are added with each update. please don't use the kirisakura 3.0 kernel for this ROM because after the next update, after decrypting, the data partition will be damaged for some reason and the phone will not load. It happened 2X to me so by the time I realized this !! Before installing the ROM, it is recommended to install the latest google factory image and a factory reset "fastboot reboot fastboot".Thanks to the ROM maintainer for the excellent work!
Okay thanks. So I flashed both slots with the stock and installed the rom, but now all it's doing is infinite splash loading screen, the white boot screen with the flying coloured dots, that just happens indefinitely now. I even left it for 3 hours and still happened. I dont know maybe this rom is cursed for me (/_\) i just can't make it work after hours of trying.
Any suggestions? Thank you.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone