[ROM][Pixel 3][10.0.0_r41] PixelDust CAF Android 10 for blueline [7 Aug 2020]

princearic

Senior Member
Aug 30, 2010
103
11
48
Highland, Utah
Just reporting back after flashing Android 11. After finally being able to download the 11-18 build after 20+ attempts, I successfully flashed the build to my phone. I added Magisk without any issues, flashed build props, and my phone passed safety net with no issue - which means I pretty much have full use of my phone. The rom feels snappy and I haven't noticed any issues with it, yet. So, I feel pretty happy with the direction the build is going. While it's currently missing a few features I've grown to love (e.g. arrows while using keyboard, squeeze customization), I have no problem using it as my daily driver for now. I'm sure it's just a matter of time until those features are implemented in future builds. As a side note, I flashed the Elementalx kernel, just for fun, and noticed it broke WiFi so I reflashed the build which returned everything back to normal. Keep up the good work! It's nice to have access to Android 11 through a custom ROM. Thank you... thank you... thank you!!!
 

PistolSlap

Senior Member
Nov 23, 2013
100
10
0
@PistolSlap hv you reset your device before flashing the rom?
Okay, well I did everything again the exact same as I did before... and this time it worked. Who knows what went wrong the first time? Even so, I wrote down everything as I did it (in case it failed again) so I kept it here in case someone else had the same issue, then this is what worked (and should have worked the first time lol)


Okay, so this is what I did, step for step. First I flashed the factory image (Android 11.0.0 (RP1A.201105.002, Nov 2020)) from here. I used the Factory Image, not the OTA, then unzipped this into the platform-tools folder. Then I installed it into the current slot (which was B) by typing
Code:
flash-all
in fastboot. Then I switched to slot A using
Code:
fastboot --set-active=a
I manually restarted fastboot, and repeated the process by again using the flash-all command.

Once the stock was flashed to both slots, I followed the instructions, like so:

Entered fastboot.
Flashed custom boot image:
Code:
fastboot flash boot boot_caf_2020_5.img
Erased Userdata:
Code:
fastboot erase userdata
Rebooted into custom fastbootb
Code:
fastboot reboot fastboot
In the custom fastboot I selected "Enter Recovery">"Apply Update">"Apply from ADB"
Code:
adb sideload pixeldust_blueline-ota-retrofit-0b6310662f.zip
Then it immediately gave error, "Signature verification failed, Install anyway?" and I selected Yes.
When it was completed I rebooted the system and this time it worked. Hooray, finally! lol.

Thanks to everyone who responded. :)
 
Last edited:

PistolSlap

Senior Member
Nov 23, 2013
100
10
0
Build props is a Magisk module you install that essentially tricks safety net into thinking your phone isn't rooted or custom using Magisk hide within the manager.
Oh cool where can I find that? I did enable the magisk hide option in the manager but you're saying there's a flash able package somewhere?
 

eliass123

Member
Feb 15, 2019
7
1
0
What does the feature "Lock screen PIN quick unlock" do?
Does it perhaps circumvent the Pixel forcing you to enter a pin ~once a day even if you're using fingerprints?

Btw, I'd love that Pixel *4a & 5 feature that mutes on-hold music in callers queue ("Hold For Me") to be included in a costum rom
 
Last edited:

droidbot1337

Senior Member
Apr 2, 2013
619
192
63
What does the feature "Lock screen PIN quick unlock" do?
Does it perhaps circumvent the Pixel forcing you to enter a pin ~once a day even if you're using fingerprints?

Btw, I'd love that Pixel 4 feature that mutes on-hold music in callers queue ("Hold For Me") to be included in a costum rom
no, all it does is eliminate the need for you to press enter after you input your pin. as for that hold thing..... i think thats built into the phone app. i dont use it but i think its there with most pixel ROMs.
 

kasperskyski

Member
Jan 25, 2016
25
2
0
Hi, nood question. What recovery did you guys used to flash Android 11 Beta? The CAF or AOSP image? Thank you! (CAF recovery flashed but failed in the end, in AOSP image I get a signature verification failed)
 

PistolSlap

Senior Member
Nov 23, 2013
100
10
0
Hey folks I'm having a weird problem with the rom. None of my app backups will restore. Titanium Backup, Rom Toolbox Pro, and MyBackupPro are all completely failing, and when I try to manually install the apps it works temporarily, but later in the day I come back and all of those apps I just installed have been deleted. The only ones that stayed were the ones it installed through the phone copying process (which were downloaded new from google play) Then I thought it was because I hadn't turned off Play Protect yet and so Android was deleting everything that was installed outside of Google Play, so I turned it off, but my backups are still broken and new apps still mysteriously disappear when I put the phone down and come back to it later. Really bizarre.
 

princearic

Senior Member
Aug 30, 2010
103
11
48
Highland, Utah
I've had strange deal-breaking issues with the alpha 11 as well. (E.g. Youtube crashing, sound being broken (silenced) anytime after "hey google", etc). I personally can't recommend it in its current state.

I also had the titanium backup issue where it would restore one app but not another without any rhyme or reason. It seemed fine for a day until I really started using my phone. It was cool having a new look, and I was really excited to have 11 for about... 6 hours. In the end, I just couldn't get ahead of the bugs and decided to return to 10 for the foreseeable future to avoid the headache of troubleshooting on my own.

Others may be having a different experience with their phones, though - for better or worse.
 

Zehlek

Senior Member
Jul 17, 2010
6,508
2,000
253
Niagara Falls
I've had strange deal-breaking issues with the alpha 11 as well. (E.g. Youtube crashing, sound being broken (silenced) anytime after "hey google", etc). I personally can't recommend it in its current state.

I also had the titanium backup issue where it would restore one app but not another without any rhyme or reason. It seemed fine for a day until I really started using my phone. It was cool having a new look, and I was really excited to have 11 for about... 6 hours. In the end, I just couldn't get ahead of the bugs and decided to return to 10 for the foreseeable future to avoid the headache of troubleshooting on my own.

Others may be having a different experience with their phones, though - for better or worse.
I'm on the latest A11 version and I have no issues. Maybe try a clean install?
 

kkjb

Senior Member
May 3, 2017
329
111
26
I also did clean flash of latest. Device to device transfer of data, working great. I don't use a lot of Google apps besides phone stuffs. Extreme battery saver works good with this old battery of mine too. Nicely done A11. !!!
 

princearic

Senior Member
Aug 30, 2010
103
11
48
Highland, Utah
I'm on the latest A11 version and I have no issues. Maybe try a clean install?
It's a pain sometimes, but I always clean flash. Did it twice and suspect something with the interaction of Magisk is likely to blame. I can live without a lot of features, but my music and ad blocking are two things I can't. I'll probably try again in a few builds, but it takes a good solid hour to set up my phone each time on top of signing into everything again since titanium backup is spotty.

If I knew what was supposed to work or where to submit logs for insights, I would.
 

Zehlek

Senior Member
Jul 17, 2010
6,508
2,000
253
Niagara Falls
It's a pain sometimes, but I always clean flash. Did it twice and suspect something with the interaction of Magisk is likely to blame. I can live without a lot of features, but my music and ad blocking are two things I can't. I'll probably try again in a few builds, but it takes a good solid hour to set up my phone each time on top of signing into everything again since titanium backup is spotty.

If I knew what was supposed to work or where to submit logs for insights, I would.
Any logs and questions can be in here https://t.me/joinchat/ErsPsFe1_CRG6eXUDynOUA
 

appye

Senior Member
Jun 20, 2006
252
23
38
Hello. I am new to this phone. I my new used phone should show up in a few days. I am a little confused about TWRP and this ROM. Why can't we use it? At least, why does the OP mention that we don't have TWRP and instructs us to use sideloading to get this ROM installed? Is it because this is a CAF ROM, and compiled differently or something? Is the OP just outdated? Thanks for your time. I did search, but the forum seems to be a bit broken at the moment ...

EDIT: Ah I get it. I think. TWRP also needs to be made CAF, right?
 
Last edited:

appye

Senior Member
Jun 20, 2006
252
23
38
Okay, so some other questions before I dive in. My phone is still several days off, but I just want to be prepared for this when it does arrive.

  1. The OP states I need to have a recent factory image on "both slots" before installing for the first time. Does this mean that I should be okay, assuming my phone arrives with with the stock image? If it is at Android 10, should I upgrade to 11 first? Should I downgrade if it is at 11? I don't understand the "both slots" thing.
  2. If I do need to flash a factory install, the OP provides a link to "instructions" on how to do so. Clicking on the link provides a list of available downloads, each with a "Flash" and a "Download" link. When I go to one of the Flash links, it presents me with what seems to be a web based tool to flash an image with. Will this work with Linux? I am running Chrome on Debian Buster, and am familiar with at least the terminal versions of adb, fastboot, etc. I am hoping this isn't some Windows software I have to install, though I can probably make that happen if I really need to.
  3. I will likely be installing the Android 10 version, as 11 is still in alpha. Judging by discussion in is thread over the last couple months, future builds will likely be 11. When I eventually upgrade to 11, it will be with a full wipe beforehand, but after that, is it going to be feasible to treat future 11 builds as OTA/security updates? Meaning, is it going to be okay to dirty flash? I don't want to have to rebuild my phone (and my wife's, we are getting two of these) every time I want a new build, but I do want the security updates.
... I am really looking forward to this! It has been a while since I have run a phone I am able to root and flash a custom ROM to. My first google devices since I had my Nexus 1 phone and Nexus 7 tablet.