[ROM][Pixel 4 XL][11.0] [Clang 13] PixelDust Android 11 for coral

Search This thread

GROOVYJOSHCLARK

Senior Member
  • Again I thought I was pretty clear the first time when I stated I ran stock android with this pdust boot linked in the thread. I can give you a step by step process if that helps.
    I was running STOCK Android 11 April factory build straight from Google. I thought about flashing this ROM so I downloaded the boot from the op and patched it with magisk. After unlocking the bootloader I then immediately flashed the PD boot image. Rebooted my phone and went through the setup process again as the unlocking wiped it. At this point I'm still running fully stock android 11 April factory build WITH the PD boot image. Never got around to flashing the PD ROM so up until the May factory google update was released I ran the factory ROM with the PD boot without any issues other than missing apps as I previously stated.
    Before updating to the May build I had to flash the stock boot image. After it updated I patched the stock boot and reflshed it gaining root. Immediately after booting back up those missing apps were now present and available in the playstore. No magisk hide, no relocking the bootloader no safety net patches. Having used ElementalX for years I did then use the app to flash Ex. Still no issues with missing apps. (I'm fully aware of how any kernel zips work and they don't effect the symbolically linked default.prop located inside the boot images ramdisk.)
    To summarize , for 1 month ran completely stock aside from the PD boot ran fine but had those missing apps, back to stock boot upon may update. Apps present and available. Never had PixelDust on this phone. Only the boot image.
    I also don't mean to be argumentative or sound condescending. I don't think we were on the same page and things were getting more complicated than necessary. I do respect you looking out for "newbs" , but having built plenty of ROMs for several devices I would never bring up something that I hadn't tried or tested myself. That would be irresponsible.
    OK so basically it was a wording issue. No prob, all good.

    A few things to clarify. When you say "for one month completely stock", were you also running a custom kernel? Also you probably were running stock/stock on the separate partition.
     

    blueyes

    Senior Member
    OK so basically it was a wording issue. No prob, all good.

    A few things to clarify. When you say "for one month completely stock", were you also running a custom kernel? Also you probably were running stock/stock on the separate partition.
    During the month in question I ran completely stock (factory ROM) and the PD boot for a week or so then using the ElementalX app flashed his kernel on top of it for a couple weeks. Had the missing apps for the entirety.
    Apps showed back up following my updating to the May factory build, stock boot , rooted etc. After a few days , yes I did reflash Ex. Apps remain present.
    Are you asking about the inactive partition while running the stock ROM and PD boot on the active partition? In April I was actively on slot_b (stock ROM and PD boot). And actually was also stock with PD boot on the inactive slot_a. The reason being when I flashed the PD boot initially I flashed it to both slots. (Im aware it's not necessary but between continuity and maybe a little OCD I've been in the habit of flashing both slots since they introduce AB)
     

    GROOVYJOSHCLARK

    Senior Member
  • During the month in question I ran completely stock (factory ROM) and the PD boot for a week or so then using the ElementalX app flashed his kernel on top of it for a couple weeks. Had the missing apps for the entirety.
    Apps showed back up following my updating to the May factory build, stock boot , rooted etc. After a few days , yes I did reflash Ex. Apps remain present.
    Are you asking about the inactive partition while running the stock ROM and PD boot on the active partition? In April I was actively on slot_b (stock ROM and PD boot). And actually was also stock with PD boot on the inactive slot_a. The reason being when I flashed the PD boot initially I flashed it to both slots. (Im aware it's not necessary but between continuity and maybe a little OCD I've been in the habit of flashing both slots since they introduce AB)
    OK so you answered the question. You ran EX (custom kernel) which is why you lasted a month and it worked. I've beaten this to death so I'll leave with this final thought, flashing the stock boot will not magically make your device certified and pass safteynet so don't do it and expect it to work. That's my main take away and what I've been pulling out from the convo.

    No I'm not asking about the inactive partition (slot). I'm trying to get you to understand what you actually are doing verses what you feel is happening.
     

    blueyes

    Senior Member
    OK so you answered the question. You ran EX (custom kernel) which is why you lasted a month and it worked. I've beaten this to death so I'll leave with this final thought, flashing the stock boot will not magically make your device certified and pass safteynet so don't do it and expect it to work. That's my main take away and what I've been pulling out from the convo.

    No I'm not asking about the inactive partition (slot). I'm trying to get you to understand what you actually are doing verses what you feel is happening.
    Ok I guess we'll just have to agree to disagree. I appreciate it but I don't need you to help me understand what I did. I know exactly what I did. EX has zero to do with it, just extra information. Phone ran fine with stock ROM and PD boot for 2 weeks before flashing ElementalX. Saying flashing ElementalX is the reason why I lasted a month makes no sense as it ran 14 days beforehand and could of ran 14 more if I had chosen not to flash it.
    I never said flashing the stock boot will make it magically pass safetynet. Never mentioned passing it. In fact I clearly stated earlier I never activated magisk hide. For some reason last month the apps were hidden and now they're not. The ONLY DIFFERENCE between the two is the base boot image. Something between the 2 changed allowing those apps to be available. I know what I did just can't say why, but at this point I don't care anymore.
     

    GROOVYJOSHCLARK

    Senior Member
  • Ok I guess we'll just have to agree to disagree. I appreciate it but I don't need you to help me understand what I did. I know exactly what I did. EX has zero to do with it, just extra information. Phone ran fine with stock ROM and PD boot for 2 weeks before flashing ElementalX. Saying flashing ElementalX is the reason why I lasted a month makes no sense as it ran 14 days beforehand and could of ran 14 more if I had chosen not to flash it.
    I never said flashing the stock boot will make it magically pass safetynet. Never mentioned passing it. In fact I clearly stated earlier I never activated magisk hide. For some reason last month the apps were hidden and now they're not. The ONLY DIFFERENCE between the two is the base boot image. Something between the 2 changed allowing those apps to be available. I know what I did just can't say why, but at this point I don't care anymore.
    Okie dokie, I'm not arguing. I don't care what happens but I am trying to keep it accurate for others and it's not. I could also pour milk in my gas tank and it will work, until it doesn't.

    It's all built from Google code, so sure, some things will work, but that doesn't mean it's correct. Others should not read this and assume you can flash another OSs boot and run it. You also cannot flash the boot.img and fix safteynet and playstore certifications (which started this with the "possible solution"), it's not.

    NF not showing in playstore is very well documented, and certification/safteynet related, so that's the issue. That issue cannot be solved by flashing that months boot.img.

    We can agree to disagree, but I don't think that's the issue. I think the issue is we're focussing on different aspects of what's being said.
     
    Last edited:

    blueyes

    Senior Member
    Okie dokie, I'm not arguing. I don't care what happens but I am trying to keep it accurate for others and it's not. I could also pour milk in my gas tank and it will work, until it doesn't.
    Stock/PD boot missing apps
    Stock/stock boot apps available. Pretty simple until you disected it and browbeat it to death. Ridiculous analogy, my phone started up, rebooted, ran fine with stock/PD boot. If there was an issues it wouldn't of booted and ran fine for 2 weeks. You're logic is off.
    Your engine requires combustion, milk wont turn it over much less last 2 weeks. What do I know, just an engineer at an oil refinery.
     

    GROOVYJOSHCLARK

    Senior Member
  • Stock/PD boot missing apps
    Stock/stock boot apps available. Pretty simple until you disected it and browbeat it to death. Ridiculous analogy, my phone started up, rebooted, ran fine with stock/PD boot. If there was an issues it wouldn't of booted and ran fine for 2 weeks. You're logic is off.
    Your engine requires combustion, milk wont turn it over much less last 2 weeks. What do I know, just an engineer at an oil refinery.
    LOL ok. I could chime in with who I really am and my multiple certifications in senior sys engineeing/architect, or the ROMs I have developed and supported for users, but why waste the energy.

    We do agree on one thing, I did beat it to death so the accurate information was there.
     

    blueyes

    Senior Member
    LOL ok. I could chime in with who I really am and my multiple certifications in senior sys engineeing/architect, or the ROMs I have developed and supported for users, but why waste the energy.
    If I made some stupid ridiculous analogy about something you had expertise in I'd expect nothing less. Let me know how that milk in your tank works for you. I tried to keep it peaceful, but you just couldn't stop browbeating. I'm sorry but I can only take so much. I'm done.
     

    GROOVYJOSHCLARK

    Senior Member
  • If I made some stupid ridiculous analogy about something you had expertise in I'd expect nothing less. Let me know how that milk in your tank works for you. I tried to keep it peaceful, but you just couldn't stop browbeating. I'm sorry but I can only take so much. I'm done.
    Sorry if I rubbed you wrong, I did say early on that I wasn't personally attacking you or for you to take NOT it personally. I was not attacking you, so if I came off that way, I am sorry.

    I do repeat myself on purpose to point something out that is not sound advice (so its seen over and over again to catch the newbs eye). I do this so it's in the thread and seen over and over to protect others. Sometimes this comes off wrong and the user feels attacked, so I am sorry if I made you feel that way. You are not the first user I have offended or upset with this type of repetitive actions but it was not intended hurtfully. My only intention is safety for others and their personal data. Using the wrong boot.img can (and usually will) cause either a soft brick, or bootloops.

    You really shouldn't run another boot image, than the OS you're on. Being certified for the PlayStore is important for the apps to appear (when the BL is unlocked). Those were my only two points I was trying to clarify, the rest was wasted energy.

    Goodnight
     
    Last edited:

    fKm

    Senior Member
  • Jan 7, 2011
    1,118
    1,645
    Schuettorf
    Stock/PD boot missing apps
    Stock/stock boot apps available. Pretty simple until you disected it and browbeat it to death. Ridiculous analogy, my phone started up, rebooted, ran fine with stock/PD boot. If there was an issues it wouldn't of booted and ran fine for 2 weeks. You're logic is off.
    Your engine requires combustion, milk wont turn it over much less last 2 weeks. What do I know, just an engineer at an oil refinery.
    Why the hell one uses Stock with PD boot.img? Makes no sense for me, sorry.
     
    • Like
    Reactions: GROOVYJOSHCLARK

    blueyes

    Senior Member
    Why the hell one uses Stock with PD boot.img? Makes no sense for me, sorry.
    It wasn't my intention to run stock with PD boot. I downloaded both the ROM and boot with the intention on flashing both. After flashing the boot and before flashing the ROM I received a call on my landline with a work emergency that required I leave immediately. Ended up working nearly a month straight 7 days a week 12 hours a day so never got around to flashing the ROM nor the energy to. By the time May came around I just reflashed stock boot and manually updated. I never said to myself "Hey lets just flash this boot".
     

    dragynbane222

    Senior Member
  • Jul 2, 2012
    170
    58
    Google Pixel 4 XL
    It wasn't my intention to run stock with PD boot. I downloaded both the ROM and boot with the intention on flashing both. After flashing the boot and before flashing the ROM I received a call on my landline with a work emergency that required I leave immediately. Ended up working nearly a month straight 7 days a week 12 hours a day so never got around to flashing the ROM nor the energy to. By the time May came around I just reflashed stock boot and manually updated. I never said to myself "Hey lets just flash this boot".
    I still say you should get around to finishing the process, PD is a good rom, after all.
     
    • Like
    Reactions: GROOVYJOSHCLARK

    Mr. Blanco

    Senior Member
    Dec 17, 2017
    126
    29
    Vancouver
    Just wondering if anyone else is having issues launching the stock camera via double pressing the power button , i have double tap power button in gestures enabled but for some reason it is not launching , it was also like this on the previous version of this rom , im running this rom stock with no mods or root
     

    KingMike67

    Senior Member
    Jun 6, 2009
    68
    35
    Mississauga
    I have had it happen a few times but I can't always reproduce it. Does it happen mainly from the lock screen? I usually happens to me when I'm at the dog park and I take my phone out to take some pictures. I have Snapchat, Tasker and PicsArt that all want to use the camera double-tap shortcut, so after I set the Google Camera to be the default the problem only happens every so often
     

    Mr. Blanco

    Senior Member
    Dec 17, 2017
    126
    29
    Vancouver
    It's actually not working at all for me(double tap ) power button for camera . I've resorted to using the active edge squeeze function to use camera , I miss the double tap function Badly ..lol
     

    Mizta_Rshn

    Member
    Jul 14, 2016
    27
    3
    26
    ipoh perak
    Google Pixel 4 XL
    Hello there . Im new here :)

    I have installed PD ROM yesterday .
    How do i root it ? Should i use Stable or Canary version ?
    I have tried using root method from link below using both stable and canary version . My touch screen not respond on first boot after flash the .img file that created by Magisk .

    Not sure if my step are wrong or the boot.img file are wrong ? Should i use boot.img from factory image or from this thread ?


    Link : https://forum.xda-developers.com/t/guide-root-pixel-4-xl-android-11-r.4160441/
     

    GROOVYJOSHCLARK

    Senior Member
  • Hello there . Im new here :)

    I have installed PD ROM yesterday .
    How do i root it ? Should i use Stable or Canary version ?
    I have tried using root method from link below using both stable and canary version . My touch screen not respond on first boot after flash the .img file that created by Magisk .

    Not sure if my step are wrong or the boot.img file are wrong ? Should i use boot.img from factory image or from this thread ?


    Link : https://forum.xda-developers.com/t/guide-root-pixel-4-xl-android-11-r.4160441/
    Stable (MAGISK v23.0):


    Install the APK you download from that link (or here Magisk-v23.0.apk), open it, click install, then select patch (top option), choose the BOOT.img from the ROM (download it along with the ROM zip and make sure its the right monthly version), the name will resemble the ROM name (and date) but comes from the ROM not stock, once its patched, it will be in the download folder. Copy it out to your PC, then FASTBOOT it to your boot, then boot (reboot to system), enable MAGISKHIDE in the MAGISK options and you will pass safetynet (you should if you did everything right):

    fastboot flash boot magisk_patched.img

    The name wil be random but resemble something like this "magisk_patched-23000_XXXX.img".

    Easy Peasy but I dont know whats going on with your touch, I have had issues like this when using 3rd party kernel, so I would only use the stock kernel and patch it but not a 3rd party kernel.
     
    Last edited:

    xFaultx

    Senior Member
    Jun 18, 2010
    186
    25
    Any suggestions for face lock and wearing a face mask? With the default face unlock you can trick it by wearing a mask on half your face. With this one it's just your face straight on, so it can't be tricked. Any help would be awesome, really annoying to have it lock me out just cause i have my mask on
     

    Curiousn00b

    Senior Member
    Dec 3, 2011
    3,146
    998
    Delaware
    LG G7 ThinQ
    Google Pixel 4 XL
    Any suggestions for face lock and wearing a face mask? With the default face unlock you can trick it by wearing a mask on half your face. With this one it's just your face straight on, so it can't be tricked. Any help would be awesome, really annoying to have it lock me out just cause i have my mask on
    Why not just distance yourself a little and pull it down for a quick second?

    In some situations, I've seen my face unlock work with my mask on, but other than that, I just pull it down for a quick sec to unlock if I really need my phone.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 5
      New build with latest security patches was pushed. Changelog is also updated. Have fun!
      1
      Same on my phone. Anyone ever have pulse stop processing? Seem like I remember a solution being Android compatibility patch magisk module but there's quite a few options now when selecting that module. I guess I need to read up.. I use YouTube Vanced (rooted) for music and that's what I'm referring to when I say pulse stopped working.
      (Edit)
      Unfortunately using a mod'd app (youtube vanced) or MAGISK module to overcome an incompatibility moves you into an unsupported territory. That would be 3rd party to the ROM (vanced YouTube) so its not really a ROM issue. I am only mentioning as you might not find the right support here in the ROM forum (is what I mean). You may find better support in the vanced/YouTube forum.

      I cannot reproduce it myself as I do not use it, so maybe others do and can help, but I would also reply in that forum's support.
      1
      When update Jun 2021 @fKm ???
      When it is ready. Feel free to do it yourself, sources are there for you to compile...
    • 16
      banner11spjzm.png

      PixelDust ROM is an Android 11 ROM especially built for the current Google Pixel devices and aimed for stability at its core with themes and customizations.

      Our philosophy is to offer all the features known from the Google Pixel Factory Images paired with a useful selection of the coolest custom ROM features.

      Our project is based off directly from AOSP. We attach great importance to aesthetics, themeability and personalization. For this we have integrated a great selection of space wallpapers and a special theme app (many thanks to Dirty Unicorns for their code base) in the settings of the Android OS.

      The PixelDust Crew would highly appreciate if you would take a little of your time and leave your valuable feedback, your honest opinion or just say hello. If you should encounter a bug, or some kind of glitch that seems to be abnormal and you are pretty sure that it is related to the ROM (and not related to any special apps or mods you flashed on top), then please give as many details as possible.

      Special shoutouts to Roger.T for his amazingly designed wallpapers, logos and the best bootanimation I ever had on my Pixel!!! If you like our work, please consider to buy Roger the first beer, and a few more for the other team members and spezi77. Cheers!


      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.


      listingoffeaturesnuj5z.png


      * Periodic AOSP security updates
      * Vendor image and Pixel GApps included (Please do not flash any third party GApps)
      * Pixel wallpapers
      * PixelDust wallpapers
      * PixelDust Launcher

      Theming
      * Additional dark/black themes, Accent colors, Fonts, Icon shapes, Navbar and QS tile styles

      Additional QS tiles
      * Always On Display
      * Caffeine
      * Language
      * NFC
      * PixelDust Settings
      * Screenshot (Partial/Full)
      * and many more

      Lock screen display
      * Ambient wake gestures
      * Pixel style Ambient music ticker
      * Now Playing support (only Pixel 2 and higher)

      Security
      * Lock screen PIN quick unlock
      * Face Unlock

      System Gestures
      * Active Edge
      * Swipe fingerprint for notifications
      * Swipe fingerprint left or right to dismiss notifications
      * Volume rocker skips music tracks
      * Three-fingers-swipe to screenshot
      * Advanced Gestural navigation settings

      Status bar
      * Status bar items
      * Network activity
      * Clock & date settings
      * Battery settings

      Quick settings
      * Secure tiles require unlocking
      * Battery percentage
      * Battery estimate
      * Quick QS pulldown
      * QS columns/rows customizations
      * and many more

      Buttons
      * Screen off power button torch
      * Volume Settings: Playback control, Volume wake, Volume key cursor

      Navigation bar
      * Navbar visibility toggle
      * 3-button navigation options:
      * Layout (normal, compact, left-leaning, right-leaning)
      * Invert layout of Navbar buttons
      * Pixel animation

      Gestures
      * Status bar dt2s
      * Lock screen dt2s

      Lock screen
      * Battery info
      * Charging animation
      * Lockscreen shortcuts
      * Show/hide quick settings
      * Show/hide status bar
      * Media cover art
      * Media artwork blur level
      * Lock screen charging animation

      Power menu
      * Additional Power Menu options incl. advanced Restart

      Notifications
      * Less boring heads up
      * Notification sound if active

      Misc
      * Pulse for NavBar, LockScreen and Ambient Screen
      * Wake up on charge
      * Rounded corners



      Not working:

      * Motion Sense


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

      Downloads:
      * Pixel Dust ROM Android 11 incl. GApps
      * Boot image (must be flashed before each installation process)

      socialmedia5ljkh.png

      Telegram Discussion Channel: https://t.me/pixeldustcommunity
      Telegram Announcements Channel: https://t.me/pixeldustproject
      Telegram Build Support Channel: https://t.me/compile_pixeldust
      Discord Server: https://discord.gg/ANtVnW8



      installationguidemmkme.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
      * Bootloader unlocked
      * You have created a backup of your ROM & data

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

      YOU MUST HAVE JUNE FACTORY IMAGE!
      1. Flashing stock ROM: Follow these instructions: https://developers.google.com/android/images#coral
      2. Flashing PixelDust ROM:
        • Download the ROM and boot image
        • Flash the boot image (this allows stock recovery to flash unsigned rom zip since we dont have TWRP):
          Code:
          fastboot flash boot boot.img
        • Wipe userdata (required for first PixelDust/Android 11 install):
          Code:
          fastboot erase userdata
        • Reboot into fastbootd:
          Code:
          fastboot reboot fastboot
        • Use volume keys and power button to select "Enter Recovery"
        • Use Power button + volume up to enter Recovery
        • Select "Apply Update from ADB"
        • Sideload the ROM zip:
          Code:
          adb sideload PixelDust-Eleven-aosp-coral-***.zip
        • Reboot
      Dirty flashing PixelDust ROM:

      Just skip the step "Wipe userdata"



      creditsi9kfj.png


      Thanks to all development teams, e.g. ABC ROM, AICP, AOKP, AOSPA, AOSP Extended, BenzoROM, Bootleggers, CarbonROM, crDroid, DirtyUnicorns, Havoc OS, HentaiOS, LOS, MSM-Xtended Project, OmniROM, Potatoes Project, PureNexus, ProtonAOSP and YAAP, we borrowed a few features and tweaks from.


      kernelsourceemjy3.png

      Source code:
      * Unicornblood kernel (by Dirty Unicorns)
      5
      I recompiled with the latest blobs and stuff and flashed it on my coral. Zero issues.
      I pushed a new build.

      If you have any problems atleast try a clean flash after flashing stock before. That worked flawless for me.
      5
      New build with latest security patches was pushed. Changelog is also updated. Have fun!
      5
      New build with march security update was pushed. No FCs or other problems after a short testing by me. Have fun.
      4
      New build with april security update was pushed. Have fun!