[MOD][MAGISK][ANDROID 11] Addon Features for Pixel Devices - Pixel 4a Thread

Search This thread

mindyabiznis

Senior Member
Oct 16, 2011
363
51
I notice you say this may or may not work with AOSP, I understand I can't flash the systemUI on LOS but the other mods are they compatible with latest official LOS?
 

Mike808James

Member
Feb 13, 2016
16
2
@ Typhus_ I would like to ask you why SafetyNet is no longer passable on May update? I followed the steps you outlined and updated to Android_11_SystemUI_for_Addon_Features_V8.zip along with Android_11_Addon_Features_For_Pixel_V12.zip and checked with the latest Magisk on my Pixel 4a, and it fails SafetyNet completely now. It used to pass before (a couple of months back.) Now it states SafetyNet API Error basicIntegrity - failed ctsProfile - failed. What can I do? Please help me fix this.
 

Typhus_

Senior Member
  • Jan 9, 2013
    1,236
    1,458
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    @ Typhus_ I would like to ask you why SafetyNet is no longer passable on May update? I followed the steps you outlined and updated to Android_11_SystemUI_for_Addon_Features_V8.zip along with Android_11_Addon_Features_For_Pixel_V12.zip and checked with the latest Magisk on my Pixel 4a, and it fails SafetyNet completely now. It used to pass before (a couple of months back.) Now it states SafetyNet API Error basicIntegrity - failed ctsProfile - failed. What can I do? Please help me fix this.
    Did you enable Magisk Hide option on Magisk Manager options?

    it's working fine at my end...
     

    Attachments

    • Screenshot_20210506-105027.png
      Screenshot_20210506-105027.png
      71.6 KB · Views: 17

    mindyabiznis

    Senior Member
    Oct 16, 2011
    363
    51
    Does this mod come with some static wallpapers?

    I had a few added into my themes and wallpaper section on the phone but then I flashed latest LOS build, lost root but kept the wallpaper I set as active before I updated, but lost all the others.

    This is the one I kept, just wondering if it's part of this mod because I have no idea where those wallpapers came from if not:ROFLMAO:
     

    Attachments

    • Screenshot_20210507-075648_Trebuchet.png
      Screenshot_20210507-075648_Trebuchet.png
      2 MB · Views: 26

    Mike808James

    Member
    Feb 13, 2016
    16
    2
    Did you enable Magisk Hide option on Magisk Manager options?

    it's working fine at my end...
    Yes, I did enable Magisk Hide in the settings, and I also clicked on the shield icon on the bottom of Magisk and made sure to check every single app in my Pixel 4a to "hide" Magisk completely and am still unable to pass SafetyNet. However, I only have your two modules enabled in Magisk, System_UI_V8, and Addon_Features_For_Pixel_V12. Is there something I'm missing or did wrong? My Pixel 4a is still failing SafetyNet completely. Bummer. I've attached pics. Any help or advice is greatly appreciated. p.s. I did have a problem when updating with step 5. Completely uninstall Magisk, when I clicked on the red uninstall Magisk, then on COMPLETE UNINSTALL (in blue) it did nothing. So, not having TWRP I had to just continue with the steps to update. Steps 6, 7, 8, went as planned, but on step 9 I'm not sure if it worked as intended, because of step 5 problem, however I lost no data, and the Magisk patched boot image was written to A partition with the flash-all.bat file, but not B partition. Then followed through steps 10 through 15. Tried to pass SafetyNet and completely failed. Sorry for the long message, but better to include any important data than leave it out. Thank you so much for your help.
     

    Attachments

    • Screenshot_1.png
      Screenshot_1.png
      162.1 KB · Views: 18
    • Screenshot_2.png
      Screenshot_2.png
      179.4 KB · Views: 18
    • Screenshot_3.png
      Screenshot_3.png
      70.1 KB · Views: 18

    mindyabiznis

    Senior Member
    Oct 16, 2011
    363
    51
    Yes, I did enable Magisk Hide in the settings, and I also clicked on the shield icon on the bottom of Magisk and made sure to check every single app in my Pixel 4a to "hide" Magisk completely and am still unable to pass SafetyNet. However, I only have your two modules enabled in Magisk, System_UI_V8, and Addon_Features_For_Pixel_V12. Is there something I'm missing or did wrong? My Pixel 4a is still failing SafetyNet completely. Bummer. I've attached pics. Any help or advice is greatly appreciated. p.s. I did have a problem when updating with step 5. Completely uninstall Magisk, when I clicked on the red uninstall Magisk, then on COMPLETE UNINSTALL (in blue) it did nothing. So, not having TWRP I had to just continue with the steps to update. Steps 6, 7, 8, went as planned, but on step 9 I'm not sure if it worked as intended, because of step 5 problem, however I lost no data, and the Magisk patched boot image was written to A partition with the flash-all.bat file, but not B partition. Then followed through steps 10 through 15. Tried to pass SafetyNet and completely failed. Sorry for the long message, but better to include any important data than leave it out. Thank you so much for your help.
    You need to magisk hide Google play services as well.

    If that alone doesn't work you'll need to clear cache of Google play services
     

    GoldElocks

    Senior Member
    Jul 1, 2012
    232
    122
    Chicago
    Google Pixel 4a 5G
    Could you please tell me how to completely uninstall Magisk through adb or fastboot commands with the uninstall .zip file. Thank you.
    If you're using *Stable branch of Magisk manager to check if safetynet passes that's your issue. It's not working and the dev is aware and working on a fix. You can use a safetynet check app from the app store to check if safetynet passes. (It should)
     
    Last edited:
    • Like
    Reactions: kurt.gomez

    mindyabiznis

    Senior Member
    Oct 16, 2011
    363
    51
    If you're using Magisk manager to check if safetynet passes that's your issue. It's not working in MM and the dev is aware and working on a fix. You can use a safetynet check app from the app store to check if safetynet passes. (It should)
    If that's the case why does my magisk validate as safetynet pass?

    Running latest canary magisk, latest LOS and blu.spark
     

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,236
    1,458
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    Does this mod come with some static wallpapers?

    I had a few added into my themes and wallpaper section on the phone but then I flashed latest LOS build, lost root but kept the wallpaper I set as active before I updated, but lost all the others.

    This is the one I kept, just wondering if it's part of this mod because I have no idea where those wallpapers came from if not:ROFLMAO:

    No, the MOD doesn't include any static wallpapers. Don't know from where that image came from, as well.

    Yes, I did enable Magisk Hide in the settings, and I also clicked on the shield icon on the bottom of Magisk and made sure to check every single app in my Pixel 4a to "hide" Magisk completely and am still unable to pass SafetyNet. However, I only have your two modules enabled in Magisk, System_UI_V8, and Addon_Features_For_Pixel_V12. Is there something I'm missing or did wrong? My Pixel 4a is still failing SafetyNet completely. Bummer. I've attached pics. Any help or advice is greatly appreciated. p.s. I did have a problem when updating with step 5. Completely uninstall Magisk, when I clicked on the red uninstall Magisk, then on COMPLETE UNINSTALL (in blue) it did nothing. So, not having TWRP I had to just continue with the steps to update. Steps 6, 7, 8, went as planned, but on step 9 I'm not sure if it worked as intended, because of step 5 problem, however I lost no data, and the Magisk patched boot image was written to A partition with the flash-all.bat file, but not B partition. Then followed through steps 10 through 15. Tried to pass SafetyNet and completely failed. Sorry for the long message, but better to include any important data than leave it out. Thank you so much for your help.

    If you check your print screen, the evalType states "N/A". That's an issue with your current Magisk Manager app version. SafteyNet is indeed passing, Magisk Manager just isn't able to check it correctly.

    You're not running latest Magisk Canary version. If you were, the update channel wouldn't be "stable" as you may see on your prints.

    Download latest Magisk Manager Canary apk version from HERE and install it.


    Cheers!
     
    • Like
    Reactions: mindyabiznis

    mindyabiznis

    Senior Member
    Oct 16, 2011
    363
    51
    No, the MOD doesn't include any static wallpapers. Don't know from where that image came from, as well.



    If you check your print screen, the evalType states "N/A". That's an issue with your current Magisk Manager app version. SafteyNet is indeed passing, Magisk Manager just isn't able to check it correctly.

    You're not running latest Magisk Canary version. If you were, the update channel wouldn't be "stable" as you may see on your prints.

    Download latest Magisk Manager Canary apk version from HERE and install it.


    Cheers!
    Ah that's a shame some of them were nice wallpapers, maybe they're just LOS wallpapers but I can't imagine losing them when updating, strange
     

    Mike808James

    Member
    Feb 13, 2016
    16
    2
    Wow, I did not realize I had to still use Canary build of Magisk! if I'm not mistaken, I'm pretty sure that it was passing SafetyNet check with your Magisk Mod using regular Magisk (Non Canary) just a couple of months back! Oh well. Thank you for clearing this up for me. I would like to ask you, Typhus_, how I can uninstall the regular version of Magisk 22 that I had installed using a Magisk patched boot image on my pixel 4a? The reason I ask isbecause when I try to completely uninstall through Magisk, nothing happens. Also there is no TWRP for the Pixel 4a, so I am unable to flash the uninstall .zip to my knowledge. Is there any way to do it through ADB or fastboot with commands? Do I just have to suck it up and completely loose all my data through a complete factory stock update and take hours and hours replacing all of the smartphone apps (some modded & not stock from Google Play.) ?
     

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,236
    1,458
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    Wow, I did not realize I had to still use Canary build of Magisk! if I'm not mistaken, I'm pretty sure that it was passing SafetyNet check with your Magisk Mod using regular Magisk (Non Canary) just a couple of months back! Oh well. Thank you for clearing this up for me. I would like to ask you, Typhus_, how I can uninstall the regular version of Magisk 22 that I had installed using a Magisk patched boot image on my pixel 4a? The reason I ask isbecause when I try to completely uninstall through Magisk, nothing happens. Also there is no TWRP for the Pixel 4a, so I am unable to flash the uninstall .zip to my knowledge. Is there any way to do it through ADB or fastboot with commands? Do I just have to suck it up and completely loose all my data through a complete factory stock update and take hours and hours replacing all of the smartphone apps (some modded & not stock from Google Play.) ?
    Just flash stock boot.img through fastboot.
     

    Top Liked Posts

    • There are no posts matching your filters.
    • 6
      Hello!

      Addon Features V13 and SystemUI V9 modules have been added on the OP.

      These MODs are now working with June build update.

      No other features were added, only make them compatible with June update (sorry, I don't have much free time lately).


      Cheers and enjoy!
      5
      I still haven't tried June update. I'll try to do it later today.

      It's quite possible that the MOD needs to be updated, as I've explained on the OP.

      Rest assured that, if it really is, I'll update it.

      Cheers!
      5
      Well, SystemUI MOD is really not compatible with June update.

      Google introduced some changes that requires some lame edition (mainly the IDs are different...which sucks).

      It's going to be a dull procedure but I'll try to do it as fast as possible.

      Please wait for a new update. As soon as I do it, I'll share.


      Cheers!
      3
      Does this work on the Pixel 4a??
      What kind of question is that!?

      Did you read the OP?

      C'mon...please...geez....
      1
      I know this is probably a dumb question, but are there any plans to bring this to the Android 12 beta? I've been using this for a few weeks, but those beta features seem amazing.
      I won't do anything to 12 until a stable build is released. I mean, anything that requires SystemUI modding. The "addon features" module works on 12, since it's just overlays and stuff...
    • 27
      Addon_Features_For_Pixel_Devices.png


      So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11:

      • Forces Google Sans font system wide
      • 63 Accent colors
      • 12 Icon shapes
      • 22 Fonts
      • Wallpapers Breel 2019; 2020 & 2020a
      • 9 different Dark Styles
      • Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
      • Background Blur options
      • Blur Intensity options
      • Adaptive sound options
      • Navigation bar options (hide pill, reduce keyboard bottom space size, hide assist handles)
      • SystemUI Tuner options
      • Rounded corner options
      • QS Rows x Columns options
      • QS Footer Drag Handle options (Default, Accent based, Hidden)
      • Option to show more icon notifications on staus bar
      • Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide
      • Rom Control app (to setup all options available that you cannot using just Styles & Wallpapers)

      Everything can be controlled using Styles & Wallpapers and also Rom Control app.

      This MOD will probably work on any AOSP, or close to it, ROMs.


      Get it here: Android_11_Addon_Features_for_Pixel_V8.zip


      Just a note, this module already includes a SafetyNet fix, so if you're using another module for SafetyNet, please remove it since I don't know if that couldn't cause issues.


      For users that may be testing Android S developer preview I've made a module that, not only, adds all above features, but also, adds the hidden Android S features that you can choose to test. That module is shared HERE. I've also shared, on that post, a PDF with all features explained as well as instructions. Feel free to try it.



      Addon Features EXCLUSIVE for Pixel Devices running on STOCK Android 11 ROM:

      These exclusive and specific for Pixel Devices running on STOCK Android 11 ROM Magisk modules that you'll see next adds all of the features stated above but with extra goodies!

      "Exclusive features" included:

      • Battery Bar
      • Battery Styles
      • Clock Customization
      • Corrected lock screen icons not changing after applying different theme
      • "Disco Dingo" the QS (just a funny name for the option to apply random colors on QS toggles)
      • Hide QS Labels
      • Lock screen album art customization
      • Lock screen camera shortcut (enable/disable)
      • Lock screen custom clock faces
      • Network Traffic Indicators (unfortunately, on redfin, it only works on QS Header and not on status bar)
      • QS Battery percentage independent options
      • QS Header opacity level control
      • QS Headers styles
      • QS Panel opacity level control
      • QS Tiles styles
      • QS Data usage info
      • QS Rows x Columns options (both on portrait and landscape modes)
      • Reduce Status bar height (and correct left padding on devices with the notch on the left)
      • Removed side assist handles from lock screen
      • Status bar Quick Pulldown (Never, Right pulldown, Left pulldown, Always)
      • Switch styles
      • Touch QS Labels to add or remove on QS customize panel (just didn't bothered to translate "Tap or Drag Tiles..." strings, so you'll continue to see "Drag Tiles..." but the feature is there, try it.)

      Exclusive features downloads:

      Android_11_Addon_Features_For_Pixel_V13.zip
      -> "Harmless" module that works on any Pixel device running on STOCK ROM, much like the "universal mod" shared above, but with a Rom Control app version that has more options. The "exclusive features" options won't do anything if the SystemUI module, shared next, isn't installed. If your going to try these exclusive features module, install this one and not the one shared above. The SaftetyNet is also included on this module, so once again, don't try to use any other SafetyNet module since it could break things.

      Android_11_SystemUI_for_Addon_Features_V9.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI. Without this module the "exclusive features" won't work. Also, this module could be responsible for breaking boot if it fails to work at your end. I've ran several tests on my device (a Pixel 4a) and didn't face any issues but, since this module replaces stock SystemUI for a modded SystemUI, you could run into problems if some other module tries to do the same or it's simply incompatible with it.

      Android_11_SystemUI_for_Addon_Features_V8.zip -> Use this version ONLY if you're still running May Android 11 build update!


      Notes regarding the "exclusive version" for Pixel devices:

      • DO NOT, I'll repeat, DO NOT flash "SystemUI module" zip on any other ROM besides stock. It won't work! If you want those extra features on your current ROM you will have to port them yourself. I explain how to later on this post.

      • Make sure that you're able to run adb shell as root before rebooting your device.

      • If something goes wrong after flashing "SystemUI module", like if your device doesn't boot or something stupid, connect your phone to your PC during boot and run this:

      Code:
      adb shell
      Code:
      su
      Code:
      rm -rf /data/adb/modules/Modded_SystemUI && reboot

      • If you forgot to enable the ability to run adb shell as root, and if your device is on a "non-boot" state, the only way you can fix that is to remove all Magisk modules you have installed. That can be achieved by running the following commands during boot:

      Code:
      adb shell
      Code:
      magisk --remove-modules
      • If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).

      • The "SystemUI module" requires that your device is already updated to March build!

      • When a new OTA update comes please don't flash the "SystemUI module" until I say it's ok to do so. I mean, me or any other member who may have tested it. Why? Because Google may change things on stock SystemUI between builds. When that happens, I have to recreate the module again to adapt those changes. For instance, March build was not compatible with the module that was built on top of February build SystemUI. Rest assured that I'll always test the module with new builds and update as necessary.

      • In case your device gets caught in a bootloop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:

        Code:
        adb logcat > log.txt

      Requirements:

      • Unlocked bootloader
      • Magisk Root | Magisk Manager

      Suggestion:

      • Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.

      • If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.

      How to install? (If you're running a Pixel 5, just install the module...you don't need all these next steps)

      1. Uninstall Device Personalization Services updates
      2. Clear Google Play Store app data and cache
      3. Flash the Magisk Module(s)
      4. Reboot device
      5. Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
      6. Profit!


      Video:

      Check all Rom Control (with exclusive features) options HERE.



      How's these "exclusive features" even possible?

      All (well, not all but almost...) features that you see on Pixel Devices "SystemUI module" were reverse engineered from Evolution X ROM source code. The source code is available on the link bellow shown on the credits. This means that I've been practicing some hard core "old school" Android smali edition in order to get this working. So, yes, I have some credits about this but, if it weren't for the original developers and it's public source code, none of this would be possible. Thank them for this!

      Smali, and xml, edition wasn't enough to get this working. After decompiling, changing/adapt the code and recompiling everything again, I had to find a way to make it bootable without messing with the original apk signature. And here is where VR Theme logic came in handy. So thanks for the original dev who brought us this feature.

      As for ROM Control app....this was/is a project created by daxgirl and wubydax back in 2015! So yeah, I'm not bringing anything new here, I just followed their instructions in order to get the features working after editing smali/xml with the source code taken from Evolution X. The original app source code is also available on the link shared on the credits.

      I've just combined all of the above into a Magisk Module and shared here so that we can get the best of both worlds....a stock ROM with custom features included.


      Rom Control with "exclusive features" source code:

      https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a



      Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:


      https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a/app/src/mods



      Credits:

      EvolutionX ROM team, specially @joeyhuab
      @daxgirl
      and @Wuby986 for ROM Control project and source code.
      @Tulsadiver for showing me how to adapt VR Theme logic originally used on 3Minit Battery Mod by @gharrington.
      @Ticklefish
      for Tickle My Android
      @topjohnwu for Magisk
      @kdrag0n for Safetynet-fix.
      @Freak07 for Adaptive Audio



      Cheers and enjoy!
      7
      Hello!

      SystemUI V8 module has been added on the OP.

      It's already working with May build update.

      Please do not get confused with "Addon features V8", it's SYSTEMUI V8!


      Cheers and enjoy!
      6
      OP has been updated!


      New "exclusive features" added:

      • Bring back status bar footer drag handle (and it's options | Default; Accent based; Hidden)
      • Added option to completely remove the nav bar (it gets removed on any navigation mode but stock gestures will continue to work)
      • Center clock position fix option (it's needed for devices with a left notch using default status bar height)
      • Added Switch styles

      Hope you may enjoy these new features.


      Remember, these features needs both "Addon features V12" and "SystemUI V7" modules to be flashed.


      Notes:

      • The "center clock position fix" is somewhat related to the status bar height and "fix left side padding" options. You may encounter a few weird behaviors if you try to enable/disable/change those 3 features several times on Rom Control. I ran into a weird situation when testing all possible combo options....at the end I choose default status bar height and left clock. To my surprise, the clock ended up behind the notch...WTF!? So, if that, by any chance, happens to you, just try to set on/off all to default values, close ROM Control, open it again and choose your desired combo.

      • The "completely remove navigation bar" option has a warning dialog. I've added a "warning" so that people read it and understand what that option does. Since the text is somewhat long, I've added a timer that only enables the overlay, that removes the nav bar, after 10 secs (so that people have time to read the warning). And so, if you see the warning and just decide to immediately touch OK, you'll notice that the nav bar will only disappear after 10 secs... Having this said, the first a**hole that comes here stating something like "hey man I touch the remove nav bar option and it doesn't disappear...wtf!?...plzzz, halp. I've tried to enable disable several times...it dasn't wark!!!"... will be rewarded with a very nice "F**K *ff!" answer.


      Cheers!
      6
      Hello!

      Addon Features V13 and SystemUI V9 modules have been added on the OP.

      These MODs are now working with June build update.

      No other features were added, only make them compatible with June update (sorry, I don't have much free time lately).


      Cheers and enjoy!
      6
      The current SystemUI V7 module isn't compatible with May update.

      The phone boots but SystemUI just gets FC.

      I'll have to fix the module and upload a new version.

      Please be patient.


      Cheers!