We all know new google assistant is pretty cool on Pixel devices.Google kept it to Pixel only but various developers helped us to bring it to any device and now it is completely bug free.I have compiled all the steps in one thread to make it working on YU Yureka device(works on any other device too).
So let's start then.
Requirements
1. Obviously rooted android with a custom recovery.
2. Android version 6.0+
That's it.
Features
1.) Pixel Launcher along with new wallpapers app ,new dialer app from google and Pixel ringtones.
2.) Working google assistant.('Ok Google' working too.)
How To Install
( TIP* Before proceeding with installing Zips just clear your google app data to help in the process of enabling assistant successfully)
1.) Download the zip of pixel experience(for your android version) by FaserF as attached here :- https://www.androidfilehost.com/?w=files&flid=122156
2.) Furthur download these 3 zips to make assistant working :- https://www.androidfilehost.com/?w=files&flid=121914
(these will add required build.prop 'ro.opa.eligible_device=true' and 'ro.product.model=Pixel'
+ making a backup of your current build.prop and not touching your original build.prop settings.)
2.) Copy them to your device...all the zips.
3.) First flash GoogleAssistantVelvet.zip .
4.) Then flash GoogleAssistantBuildProp.zip (this will install the "tweak.prop" into your build.prop).
5.) Finally flash GooglePixelExperience-flashable-(whatever vesion of android you are on).zip and reboot.
6.) U can now flash additional zips like those of boot animation.
Google assistant may not appear on long tapping home button for a few times but eventually it will appear.
To fix 'ok Google' detection just download the chopAssistant app from play store (here is the link :- credit to @masterchop for making this app ChopAssistant https://play.google.com/store/apps/d...ssistant&hl=en)
That's all...I know its a lot to do but then just let's think about the rewards. :laugh:
Bugs
I have tested this method myself on my Yureka device(CM14.1 unofficial build) and for me everything is totally fine.
Report if u find any.
F.A.Q.
1.) Long tapping home button takes to old google now on tap
Give it about 5 minutes and try again...If still doesn't work then clear google velvet app data,then uninstall the google app completely and download google app beta from play store by registering for a beta tester. Reboot...Assistant will appear now.
2.) Dialer app crashes
Give it all permissions.
3.) Google app crashes
Give it all permissions.
Quick review:-
I want only assistant to be working fully. Do i need to flash both Pixel experience zip??
Apps that use liboemcrypto.so to play content protected by DRM, such as Netflix and My5, will fail when playback is attempted on a rooted device.
The symptoms displayed by affected devices vary by brand and Android version. Some devices may display an obscure error message when you attempt playback. Others may just appear stuck loading the requested content.
This Magisk module fixes the problem by masking liboemcrypto.so with a zero byte replacement. Whilst the same effect could be achieved by simply deleting or renaming liboemcrypto.so with a root-enabled file manager, this has the disadvantage of altering your /system partition by writing to the file-system. The advantage of the Magisk method is that no actual changes are made to the device. The problematic file is merely concealed from the apps that attempt to use it.
To use the module, flash it in the Modules section of Magisk Manager and then reboot your device.
The module works when the library in question is located at either /system/lib/liboemcrypto.so or /system/vendor/lib/liboemcrypto.so. If your library is located elsewhere (or missing), this module will have no effect (but it's harmless to try it).
The module has been verified working on a Samsung Galaxy S9+ (SM-G965F/DS) running Magisk 16.x/17.x/18.x on a variery of ROMs, on a Samsung Tab S3 (SM-T820) running stock Android 8.0 and Magisk 16.x/17.x, and on a Samsung Tab S4 (SM-T830) running stock Android 8.1 and Magisk 17.x/18.x. It was created because a similar module on XDA did not work on my devices. It is being released by popular request, because a number of other users contacted me with the same complaint.
The module was integrated into the official Magisk module repository on 2018-06-27, and can therefore be directly downloaded from within the Magisk Manager app.
Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type. Of course, without this module, you won't be able to play anything on a rooted device, so beggars can't be choosers.
Change log:
2020-12-20: v1.5
Updated for Magisk v21 template format.
2019-03-29: v1.4
Updated for Magisk v19 template format.
Issue a warning if installed on an S10e (G970F), S10 (G973F) or S10+ (G975F).
2018-12-06: v1.3
Added support for devices that have the library under either /system/lib64 or /system/vendor/lib64.
Added support for devices that have the library in multiple locations.
2018-07-22: v1.2
Added logic to install in only the appropriate library directory, rather than in both.
2018-05-29: v1.1
Added support for devices that have the library under /system/vendor/lib instead of /system/lib.
2018-04-23: v1.0
Initial release.
Work on Note 8 perfectly thx mate check with netafix,showmax thx again mate
Wysłane z mojego SM-N950F przy użyciu Tapatalka
Version 1.1 has been released with support for devices that have the library under /system/vendor/lib instead.
Hi,
Could you try to make nc+ GO usefull for rooted devices ?
Thanks for the module @ianmacd, finaly Netflix working again on my rooted and Widevine L1 patched Oneplus5.
I noticed this module actually reverts your device back to Widevine L3 when module is active, is that correct?
an0therus3r said:
Thanks for the module @ianmacd, finaly Netflix working again on my rooted and Widevine L1 patched Oneplus5.
I noticed this module actually reverts your device back to Widevine L3 when module is active, is that correct?
Click to expand...
Click to collapse
Yes, this is an unfortunate side-effect of the module. The module fakes the erasure of the DRM library, which enables playback, but not in HD.
If HD is important to you, there are patched Netflix binaries floating around, but I believe they are quite an old version. I mainly use my tablet to cast to the television, so it's not a problem for me. I should add something about this to the documentation.
Why did I have my device manually updated by ONEPLUS in order to enjoy HD content thru YouTube, prime, Netflix etc.. if it is conflicting with Netflix, the one I use the most?? This is pretty weird. This model is a great work around, but now I'm back to L3 and the whole point was to enjoy L1. What do you mean with patched Netflix libraries? Can you maybe point me in the right direction? That'd be greatly appreciated
mshinni80 said:
Why did I have my device manually updated by ONEPLUS in order to enjoy HD content thru YouTube, prime, Netflix etc.. if it is conflicting with Netflix, the one I use the most?? This is pretty weird. This model is a great work around, but now I'm back to L3 and the whole point was to enjoy L1. What do you mean with patched Netflix libraries? Can you maybe point me in the right direction? That'd be greatly appreciated
Click to expand...
Click to collapse
This article contains an introduction to the problem. Basically, you either need to patch the APK or find one pre-patched by someone else.
Most, if not all people use apktool for this kind of work, but later versions of the Netflix APK can't currently be decompiled, so if you look around for a patched APK, you'll necessarily find an old version.
ianmacd said:
Version 1.1 has been released with support for devices that have the library under /system/vendor/lib instead.
Click to expand...
Click to collapse
I didnt fix my error -9 still getting same error sorry we couldn't get Netflix service error (-9) running on Note 4 with Magisk 16.4 on MM ROM
*edit* I went into /vendor/lib/ and delete (take a backup of it) the file liboemcrypto.so, reboot and it worked! I dont know if that the right way to fix it? this Module seems like didn't change anything
zfk110 said:
I didnt fix my error -9 still getting same error sorry we couldn't get Netflix service error (-9) running on Note 4 with Magisk 16.4 on MM ROM
*edit* I went into /vendor/lib/ and delete (take a backup of it) the file liboemcrypto.so, reboot and it worked! I dont know if that the right way to fix it? this Module seems like didn't change anything
Click to expand...
Click to collapse
Thank you for the report. I will investigate the matter.
The module should have worked with that path. I have a device myself that has liboemcrypto.so in that location, and the module works fine with it. I'll look into it.
ianmacd said:
Thank you for the report. I will investigate the matter.
The module should have worked with that path. I have a device myself that has liboemcrypto.so in that location, and the module works fine with it. I'll look into it.
Click to expand...
Click to collapse
this time I download the module direct from Magisk without using the your provided zip and then installing using from TWRP
this time it worked, now I can use Netflix without any issues I download and installed the module direct from Magisk
zfk110 said:
this time I download the module direct from Magisk without using the your provided zip and then installing using from TWRP
this time it worked, now I can use Netflix without any issues I download and installed the module direct from Magisk
Click to expand...
Click to collapse
That's weird, too, because it's the same version in both cases.
I assume you returned liboemcrypto.so to your device before installing the module. If not, there wouldn't have been anything for the module to do.
I don't know if this is related to the liboemcrypto.so library or something very different: I would like to screen cast (as in mirror my display to a Chromecast) protected content such as Prime Video. If I do so now then the result is sound + captions and a black screen. No video. This module sort of fixed my problem with Prime Video but not entirely so I wonder if you have insights into fully resolving this. I can't believe Google's own screen cast feature isn't trusted by Google's own Chromecast!
Thanks
Your work is perfect. You are a genius!
Has anyone actually managed to mask the device as L1 DRM? Just curious
Hi @ianmacd, I've installed this through Magisk Manager. I don't use Netflix or My5. I expect it to work with Saavn like apps with more Indian content (songs). Regards.
Massive thank you to the O.P been trying for a very long time to get all 4 to work on a rooted device with this module it WORKS!!! Thank you so much for the time you put into Roms and this Module!!
MetalIris said:
Massive thank you to the O.P been trying for a very long time to get all 4 to work on a rooted device with this module it WORKS!!! Thank you so much for the time you put into Roms and this Module!!
Click to expand...
Click to collapse
With all regards to @ianmacd efforts, this hack will enforce falling back to Widevine L3, hence make Netflix HD a no-go.
I am now trying to fix Widevine L1 on Exynos5420 stuff, and I found out that SELinux enforcing mode restricting access from untrusted apps to read "/", and "mount", as well as restricting "toybox" system() calls effectively make up-to-date Netflix happy while debugging the mediadrmserver with gdbserver using root Of course a small SELinux policy change is required to make gdbserver work but this is out of scope.
If there is a way to assign a custom seclabel to processes or files related to package by its name, this approach can help using SELinux as an umbrella for apps like NF.
ianmacd said:
Apps that use liboemcrypto.so to play content protected by DRM, such as Netflix and My5, will fail when playback is attempted on a rooted device.
The symptoms displayed by affected devices vary by brand and Android version. Some devices may display an obscure error message when you attempt playback. Others may just appear stuck loading the requested content.
This Magisk module fixes the problem by masking liboemcrypto.so with a zero byte replacement. Whilst the same effect could be achieved by simply deleting or renaming liboemcrypto.so with a root-enabled file manager, this has the disadvantage of altering your /system partition by writing to the file-system. The advantage of the Magisk method is that no actual changes are made to the device. The problematic file is merely concealed from the apps that attempt to use it.
To use the module, flash it in the Modules section of Magisk Manager and then reboot your device.
The module works when the library in question is located at either /system/lib/liboemcrypto.so or /system/vendor/lib/liboemcrypto.so. If your library is located elsewhere (or missing), this module will have no effect (but it's harmless to try it).
The module has been verified working on a Samsung Galaxy S9+ (SM-G965F/DS) running Magisk 16.x/17.x on a variery of ROMs, on a Samsung Tab S3 (SM-T820) running stock Android 8.0 and Magisk 16.x/17.x, and on a Samsung Tab S4 (SM-T830) running stock Android 8.1 and Magisk 17.x. It was created because a similar module on XDA did not work on my devices. It is being released by popular request, because a number of other users contacted me with the same complaint.
The module was integrated into the official Magisk module repository on 2018-06-27, and can therefore be directly downloaded from within the Magisk Manager app.
Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type. Of course, without this module, you won't be able to play anything on a rooted device, so beggars can't be choosers.
Change log:
2018-07-22: v1.2
Added logic to install in only the appropriate library directory, rather than in both.
2018-05-29: v1.1
Add support for devices that have the library under /system/vendor/lib instead of /system/lib.
2018-04-23: v1.0
Initial release.
Click to expand...
Click to collapse
Ianmacd thank you 10 times for this and for the module that restores on Samsung note 9 previously paired bluetooth devices that were lost after reboot. You saved my life !! Hhh
So if I unroot my S8 will HDR and hd work?
Finally unlocked bootloader and installed HavocOS to my Xiaomi with all needed wipes: data, system, cache. However, I've faced an issue with Play Market downloads. When I try to download a large app it goes up to 100% and then starts over, stops at 2% and awaits for wi-fi connection ( though I am connected over Wi-Fi). It is the same for all apps over 1Gb in size (e.g. PUBG, Asphalt 9 and so on). Also tried to clear cache and data for Play Market, Google Play Services and no good too.
I've tried to reinstall ROM, gapps, tried Xiaomi EU Rom (stable) and got the same error there. I guess it has something to do with security, so I've tried different google account - but result was the same.
Please suggest any resolution
Just bought this phone myself. But this my guess based on my experience with other devices.
I suspect that your play store status is uncertified?
I am sure it is!
You need to fix that first, then play store function should return to normal.
The easiest way to resolve this issue without reinstallation to use the Magisk Module : Magiskhide Props Config
Next go to the main page for that module and read the instructions ( Google it)
Note, you must also install Termus and enter commands per instructions on Op page for the module. Trust me it's easy.
Essentially you are changing the fingerprints to a Play Store certified device (It only works as long as the module and Magisk stays installed)
I have attached screenshots from my other phone, where I had the same issue and resolved it.
Sent from my Xiaomi MI 8 using XDA Labs
Guys I'm in a major fix here. Any help would be appreciated.
K20 Pro Global Version - Currently on MIUI Global 11.0.1.0(QFKMIXM)
Rooted via Magisk
Everything was perfectly fine until I noticed 'microG installer Revived' on Magisk and decided to install it.
After I rebooted, Youtube Vanced wouldn't open stating that it won't run without Google Play Services. Same issue with Gmail as well. I went into the microG settings and accepted all the missing permissions. Added my Gmail account, signed in and accepted all the other permission pop-ups that came after.
Despite this everything is still messed up. Gmail and Youtube still gives the same error msg and Chrome keeps crashing.
I tried uninstalling microG but that was an even bigger mistake as the Google Play Services I installed via apk kept crashing.
If someone could pls guide me on how to get the system to how it was prior to the microG installation :crying:
So I managed to fix it somewhat. Uninstalled microG then installed the right version of Google Play services as well as the calendar and contacts sync apks.
No more crash messages but the issue I'm having now is that some app notifications don't work and others (such as Whatsapp) work only sometimes.
And for some really weird reason my Gmail no longer is (or has the option) in dark mode.
Anyway to fix these issues guys?
I've the same problem with my Huawei Mediapad M5 tablet. I've tried to reflash the original "SYSTEM.img" from fastboot mode, but nothing changed. I don't want to do a full reinstall because of this mistake, is there any solution?
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
heynando said:
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
Click to expand...
Click to collapse
It's an absolute nightmare, not sure why the devs don't just update the Magisk version, and I agree the Magisk version works perfectly fine
MicroG works only on systems that don't have GAPPS. That should have been included in the documentation.
I had the same problem (I installed the microG installer revived on a cell phone that had google play services, which caused me that error; I installed the magisk module without knowing what it was for), I solved it by doing the following:
1. Uninstall micro-g and google play services and then restart the terminal.
2. Download and Install (install as system application with lucky patcher) the latest version of the google play services apk, restart.
3. Log out or remove google account from device, reboot device.
4. Login or add google account on the device again, restart the device for the last time; and voila problem solved.
I can't remove my account for some reason, and also I can't add a new google account
Hi Guys, have the same problem. has anyone found a solution? would hate to reset it
Trying to work out what it could be for the first post. It sounds like MicroG was installed while the Google Play services were already on the device.
I have actually manually removed Google Services using the debloater magisk module and run it via terminal.
I'm currently using CrDroid Android 12 and it's working fine with MicroG revived version. I have been testing the Android 13 with MicroG and have issues with the Play Store signing in
Hya,
i have a sagit phone, with lineageos 18.1 on it, pioneer head unit capable of AA and CP. Until last weekend, it worked fine. After an error, where i had to factory default the phone and reinstall the apps again,i get the message "Phone permission needed to take calls. When it's safe, turn on the phone permission in Settings."
But all permissions are set for AA, including phone.
Any hint in how to solve this?
Thx in advance!
Did you check your Bluetooth settings if phone permission is on for your pioneer head unit Bluetooth connection?
Hi, same problem, not tried yet with bluetooth settings as suggested above. Did it work? ('m lazy to make a new attempt with LOS 18.1, I explain why below)
So if it's not working with the tip above, I give here some clues :
I recently upgraded my Sony X Compact from Android 8 to lineageos 18.1 (Android 11) with MindTheGapps installed. Everything works fine except these call permissions.
I decided, after several failures, to test LOS 17 and calls are now possible from AA.
In Android 11, AA is natively integrated. In A10, it's not, it doesn't appear in the bluetoth/NFC settings, like in Android 8. Does this make the difference? A8 and A10 seem using the same permissions process, A11 not.
About permissions, I found another thread close to my issue and could be related: https://forum.xda-developers.com/t/linageos-16-overlay-permission-denied-but-it-is-checked.3924101/ . I tried the second method (Magisk) but it gave nothing and I'm just a newbie in Android world to try the other methods.
Any suggestions ?
Update from last reply
I finally installed LOS 19.1 (Android 12) with still MindTheGapps and everything works perfectly with AA. So it doesn't seem to be an Android version issue but rather LOS 18.1 itself or MindTheGapps. Maybe by using other gapps you'll get it work (I didn't try).
Hi,
I've upgraded my 9 y.o. Galaxy Note 4 to LineageOS 18.1 recently and was very happy with it until I stumbled on the same problem.
Android Auto claimed to have phone permission in the Application settings but the permission was impossible to change (mandatory/grayed out) and the unit in my Civic 10 was showing the same error as pw44's.
Having no UI to fiddle with, I thought maybe that can be tweaked with some ADB command, and after some reading here:
How to Grant Permissions Using ADB in Android
It can be tricky to grant advanced permissions to Android apps without rooting your phone. Here's how you can use ADB to achieve it.
www.makeuseof.com
and there:
Listing permissions of Android application via adb
Using adb, how can I find out the which permissions an Android application requires? Because I want to display the permissions of multiple applications on different devices, viewing them in Google...
stackoverflow.com
I came up with a command that fixed it:
adb shell pm grant com.google.android.projection.gearhead android.permission.CALL_PHONE
Obviously, I googled that exact command and found confirmation here:
Lineage OS 18.1 Xiaomi Redmi Note 6 Pro cant phone calls in Android Auto (#5092) · Issues · LineageOS / issues / android · GitLab
Expected Behavior Realize phone calls in Android auto Current Behavior Android auto...
gitlab.com