Database Info

[Huawei P9 Nougat info/guides]

So I've been getting lots of different questions about how to get this and that on android 7.0 nougat so to make it easier for everyone to find ill create this thread.
1. TWRP
Is twrp available for N? If so where can I find it?
http://forum.xda-developers.com/p9/how-to/twrp-3-0-2-0-n-t3506947
2. ROOT
Oh cool now I have twrp. So how can I root?
Download phh r275 version and flash
Download and install Material phh apk: Release post
Now you should be good to go. If any issues feel free to ask here or in phh official thread.
3. BUSYBOX
User friendly zip flash this and the below steps isn't needed!
Flashable zip (1.25.1) : https://mega.nz/#!zlRm3S4B!9rAtfi0wI8oFu6xjJITgF0dRwV21UPsxvZQZzMo6VXk
This one is a bit tricky. If you run root. But
Download jrummy's busybox on Gplay.
Select installation folder to /system/xbin or if u don't want to touch system folder use /sbin if available. U can replace jrummy''s busybox with stericsson version if you like it better. But you must have installed jrummys version first if you're booted into android. Else stericsson busybox might have issues installing. Or u can use zips which contains busybox Google busybox flashable.
4. VIPER
More user friendly if using this zip the below steps should only need se Linux mode changer!
Flashable zip: https://mega.nz/#!f8wlzIrB!vVCAv-xqWB8lOrcQTgIyFL0WS7MFsE9iFb08E1YKV2Y
Is quite a mess to get working. You need se Linux mode set to permissive. Flash guitarheroes version of v4a (2.5.0.5) once flashed you need to replace the audio effects in /vendor/etc/audio_effects else you'll get I/O driver installation failed. Copy the .so files to /system/lib and /system/lib64 and set correct permission. If you have wrong busybox message. Try different versions of busybox but I use latest from stericsson and it works great. Hope u get it working.
Oh and don't forget to allow sd storage access or you'll get driver I/O error as well. And se Linux changed to permissive use se Linux mode changer for it. It works great with phh!
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
6. Xposed
Not yet available. Be patient rovo needs time we can wait for him
7. comes soon.
More stuff.
Sent from my FRD-L09 using Tapatalk

how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).

paratox said:
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
Click to expand...
Click to collapse
It doesn't matter if it's aosp. Since it is for v4a it will work. As long as the audio effects works it doesn't matter.
Also I just finished my hopefully new nougat viper4android zip (i made my own for M with material designed version for my s5 neo) which worked fine until now.
Now it extract all files to its locations even to /vendor partition which all zips I used previously never had. I'll also update busybox zip which previous available is 1.24.2 which I'll bump up to 1.25.1.
I'll also going to upload my stuff to android file host. But that will be later
New files can be found https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
Tapatalk is messing with the link
Sent from my FRD-L09 using Tapatalk

Updated op with latest busybox by stericsson. More user friendly now
Sent from my FRD-L09 using Tapatalk

LastStandingDroid said:
Updated op with latest busybox by stericsson. More user friendly now
Click to expand...
Click to collapse
Nice job mate!

dodgedroid said:
Nice job mate!
Click to expand...
Click to collapse
Easy to do when you got a zip for it just update the busybox executable and replace old one
Sent from my FRD-L09 using Tapatalk

Installation of ARISE
paratox said:
how does your audio_effects.conf look like? i used one for aosp from "ARISE+Sound+Systems+Deuteronomy+2.3.3.zip" and got it working but don`t know if this is the right one for our device (huawei phones).
Click to expand...
Click to collapse
How did you installed ARISE in Nougat?
I've been trying all day and I'll always end with an I/O or Busybox error. I tried a lot of things, like changing /vendor/etc/audio_effect.conf to audio_effect.conf.bak or installing Busybox into system/bin, but none of them seems to work for me.
I'm on B361 btw. And sorry for answering an old post

LastStandingDroid said:
Also I just finished my hopefully new nougat viper4android zip (i made my own for M with material designed version for my s5 neo) which worked fine until now.
Now it extract all files to its locations even to /vendor partition which all zips I used previously never had...
New files can be found https://mega.nz/#F!HlpzlaZL!wGNoJinVPZL0YiBcdbLlKA
Click to expand...
Click to collapse
Do you know, is your Viper4Android installer compatible with the following rooting/Busybox configuration:
- L09 c432/b378
- TWRP 3.1.0-0
- SuperSU-v2.79-201612051815-EMUI5.0.zip
- Rummy"s BusyBox (installed to /system/xbin)
as described by @hakaz and @Atarii in the post #102 and follow-ups:
https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Also, should SELinux really be switched to Permissive mode for V4A to work on P9 with Nougat?
Thanks

zgfg said:
Do you know, is your Viper4Android installer compatible with the following rooting/Busybox configuration:
- L09 c432/b378
- TWRP 3.1.0-0
- SuperSU-v2.79-201612051815-EMUI5.0.zip
- Rummy"s BusyBox (installed to /system/xbin)
as described by @hakaz and @Atarii in the post #102 and follow-ups:
https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102
Also, should SELinux really be switched to Permissive mode for V4A to work on P9 with Nougat?
Thanks
Click to expand...
Click to collapse
Yes it should be compatible and yes u need to switch to permissive mode else it'll be asking you to install over again, or simply not start to work
Sent from my CUBOT_MANITO using Tapatalk

LastStandingDroid said:
Yes it should be compatible and yes u need to switch to permissive mode else it'll be asking you to install over again, or simply not start to work
Click to expand...
Click to collapse
Yes, thanks, I have flashed your Viper.zip through TWRP and installed vViPERFX_v2.5.0.5.apk
I have also installed SELinuxModeChanger and set SELinux mode to stay Permissive over rebooting
Viper4Android works fine - thanks

LastStandingDroid said:
5. MAGISK
As it seems to be now. Magisk won't work due to loop issues on boot. And mount seems to have losetup fail 1 on mounting a .img while booted.
Click to expand...
Click to collapse
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method

simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
Click to expand...
Click to collapse
Having Magisk, can you now also install Xposed?
PS: Please provide links to your resources and threads.
Btw, you have P9 Lite - does the method for Magisk apply also to (regular) P9 (single SIM)?

zgfg said:
Having Magisk, can you now also install Xposed?
PS: Please provide links to your resources and threads.
Btw, you have P9 Lite - does the method for Magisk apply also to (regular) P9 (single SIM)?
Click to expand...
Click to collapse
it workes because we have a modded boot.img created by @HassanMirza01, ask him what he did so as to he will do the same for p9 boot.img(or anyone else)
install selinux and set it to permissive, after that install magisk app via playstore and click on autoinstall
no xposed isnt working because there is no xposed for Nougat.

simo255 said:
it workes because we have a modded boot.img created by @HassanMirza01, ask him what he did so as to he will do the same for p9 boot.img(or anyone else)
install selinux and set it to permissive, after that install magisk app via playstore and click on autoinstall
no xposed isnt working because there is no xposed for Nougat.
Click to expand...
Click to collapse
Can you post the link to install his kernel?

Danymat said:
Can you post the link to install his kernel?
Click to expand...
Click to collapse
it won't work because it's a boot.img of p9 lite not for p9

simo255 said:
it won't work because it's a boot.img of p9 lite not for p9
Click to expand...
Click to collapse
So for p9 we don't have any solutions to install magisk?

Danymat said:
So for p9 we don't have any solutions to install magisk?
Click to expand...
Click to collapse
try to install the pre rooted boot.img (phh one) via this link https://forum.xda-developers.com/p9/development/root-pre-rooted-boot-img-p9-nougat-b378-t3574548
and follow the steps that i wrote above

simo255 said:
in my p9 lite emui 5.0 magisk is successfully installed !
it worked by flashing the modded boot.img by @HassanMirza01 and by setting selinux to permissive !!
big thanks to @Paolo83 who found this method
Click to expand...
Click to collapse
Is this using a Magisk.img in /data folder?
As said magisk can be made working since we had supersu working by chain I still doubt it uses a loop
Sent from my CUBOT_MANITO using Tapatalk

LastStandingDroid said:
Is this using a Magisk.img in /data folder?
As said magisk can be made working since we had supersu working by chain I still doubt it uses a loop
Click to expand...
Click to collapse
no there is no magisk.img folder, but there is a magisk folder which include those files (look at the screenshot

simo255 said:
no there is no magisk.img folder, but there is a magisk folder which include those files (look at the screenshot
Click to expand...
Click to collapse
Yes this is how Magisk is being made working
Sent from my CUBOT_MANITO using Tapatalk

Cant get Viper to work properly

Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help

i had the same but then i tried to use the other viper release from magisk and it worked. there is this one called hifi and fx

Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me

dgunn said:
Try exiting the viper app with the 3 dots top right hand corner. That is what worked for me
Click to expand...
Click to collapse
that works for like 10 mins and then it gets killed

byReqz said:
that works for like 10 mins and then it gets killed
Click to expand...
Click to collapse
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app

dgunn said:
Sounds to me like you need to disable the battery optimizations for Viper. It's almost as if your phone is detecting High battery drain and shuts down the app
Click to expand...
Click to collapse
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now

byReqz said:
yeah thats what i thought too, i zried whitelisting it and installing it as system app (+ magisk module) but it didnt seem to work.
I removed the one from my rom and tried the magisk repo version again and somehow its working till now
Click to expand...
Click to collapse
I was unaware that you were using the magisk module. I could not get that one to work either

dgunn said:
I was unaware that you were using the magisk module. I could not get that one to work either
Click to expand...
Click to collapse
the normal one doesnt work with viper doewsnt it?

Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.

TheNetwork said:
Try just exiting the viper app then reopening it. I had this problem before and it just randomly went away.
Click to expand...
Click to collapse
it only works for a few mins that way

I'm using the Android p beta and i don't have the problems with viper as i did with oxygen os 5. it's always processing for my headphones, either plugged in or Bluetooth. the only exception is sometimes after receiving a call while listening to music, after the call is over and my music resumes, viper is no longer processing. not every time though. i used the latest magisk and the viper module in the screenshot.
i also didn't make any changes to conf files, just installed through magisk download. rebooted, opened viper fx, gave it storage permissions and turned it on.

Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.

TuxRuffian said:
Had the same problem, but was able to resolve it by choosing the legacy (non-material) interface when installing the Magisk module. I still flashed the full module and selected the latest version, just not the material interface. It may have been something else, but I've updated my ROM (HavocOS) several times and even done a couple full fastboot stock resets and the issue is yet to resurface.
Click to expand...
Click to collapse
as i said, idk why but its working now.and im on material now

byReqz said:
Hey guys,
since i got my Oneplus 6, i couldnt get viper to work quite right. Most of the time its just shows "Processing: No" till i restart it and after like a hour or device switch it turns off.
I tried:
Copying the Audioeffects.conf from system/etc to vendor/etc
Using Magisk Audio Compability Module
Using Alternate Magisk V4A Module
Using a Magisk Rom with Build-In V4a (currently xXx 2.8)
Disabling Dirac and Services
but nothing worked
thanks for your help
Click to expand...
Click to collapse
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):

reaper000 said:
I've had this problem on an Samsung S7 Edge, S8 Plus, and now, a Oneplus 6.
Everything appears to look good on Driver Status, except "Processing:No" and it's audibly not on.
What's worked for me in this specific situation is replacing the configuration file "audio_effects.conf" in /system/vendor/etc with another configuration file that I found in another XDA thread. So here's the concrete steps:
1. Install the viper4android FX module from Magisk manager that has four devs (v1.7 as i write this) and reboot. I don't know if this method will work with other v4a modules. Note that Processing will work temporarily, but likely won't survive a reboot.
2. Download this file (files_for_v4a.zip) from here:
https://forum.xda-developers.com/ga...laxy-s8-s8-t3596933/post72049061#post72049061
3. Unzip files_for_v4a.zip and make note where it extracted. (You'll need one of its contents, audio_effects.conf, later)
4. Using a file explorer with root capability, go to the following directory:
/system/vendor/etc
5. Copy the existing "audio_effects.conf" to another directory, for example /download, to use as a backup in case this goes badly
6. Copy the file "audio_effects.conf" that you unzipped earlier to /system/vendor/etc, overwriting the existing file.
7. Reboot and test v4a.
Good luck!
Note: The Pulse feature of a custom NavBar in custom ROMS based on LOS 15.1 will not work if you do the above.
Although I'm just a hack, I modded an "audio_effects.conf" file using commits from the above to work with Pulse. I've tested it on my device (despite my lack of know-how, it seems to work for me and others!), so be aware of this if you download the following file and use it (by renaming it audio_effects.conf and placing it in /system/vendor/etc):
Click to expand...
Click to collapse
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox

byReqz said:
Thanks for your long answer, will be trying the files if this module fails again.
Also im not on a LOS Based Rom, im on OOS and GravityBox
Click to expand...
Click to collapse
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.

reaper000 said:
Just seeing if I can help! And I did the same sequence of steps on OOS as well ... But I haven't run gravity box in awhile. Hope it works out for you.
Click to expand...
Click to collapse
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?

byReqz said:
I tried everything but it still needs a restart to be working sometimes, do you know if i have to disable dirac or something?
Click to expand...
Click to collapse
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?

reaper000 said:
I haven't messed with dirac at all, and v4a still works for me.
Some clarification, please:
Did you uninstall the v4a magisk module that came with xXx and reboot?
Then go to magisk manager and install v4a fx materialized1.7 and follow the rest of the steps outlined in my post?
Click to expand...
Click to collapse
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime

byReqz said:
yeah, its 1.7 from magisk repo, disabling dirac seems to help a bit but not everytime
Click to expand...
Click to collapse
And you replaced the audio_effects.conf file in /system/vendor/etc with the one from the downloaded zip?
(Sorry to belabor the point, but it's not clear to me you tried all that)

any rom which comes with camera2api pre-enabled in it ??

i need a rom which is having camera2api pre-enabled in it ??

Aosp extended AEX Rom
Masik Miui Rom

Pixel Experience and Lineage os

Manav10799 said:
Pixel Experience and Lineage os
Click to expand...
Click to collapse
This comes as a surprise to me, as I had to manually enable camera2 two days prior in lineageos on whyred.
Anyway, OP, what is the problem with enabling it yourself via twrp? (mount system, open terminal in twrp > advanced then echo the one required line into the build.prop)

MSM Extended
https://forum.xda-developers.com/redmi-note-5-pro/development/stable-msm-xtended-x9-t3819822

v0id_walker said:
This comes as a surprise to me, as I had to manually enable camera2 two days prior in lineageos on whyred.
Anyway, OP, what is the problem with enabling it yourself via twrp? (mount system, open terminal in twrp > advanced then echo the one required line into the build.prop)
Click to expand...
Click to collapse
Or simply editing the build.prop in the system/ folder: "persist.camera.HAL3.enabled=1"
Sure you need to root the device but who doesn't in case you have already flashed a custom rom: hiding root from certain apps is not the problem (except Pokemon GO fair enough)

A R said:
i need a rom which is having camera2api pre-enabled in it ??
Click to expand...
Click to collapse
Masik

v0id_walker said:
This comes as a surprise to me, as I had to manually enable camera2 two days prior in lineageos on whyred.
Anyway, OP, what is the problem with enabling it yourself via twrp? (mount system, open terminal in twrp > advanced then echo the one required line into the build.prop)
Click to expand...
Click to collapse
yes i agree i also manually enabled camera2api on Los15.1 but it broke my front camera video calling feature in all the apps. So if anybody have any solution to this please do share here.

Surik4t4 said:
MSM Extended
https://forum.xda-developers.com/redmi-note-5-pro/development/stable-msm-xtended-x9-t3819822
Click to expand...
Click to collapse
they have just provided the option to enable or disable it from settings but what about the video calling feature which gets broken after enabling it ?? did anybody tested on any rom with enabling camera2api ???

A R said:
yes i agree i also manually enabled camera2api on Los15.1 but it broke my front camera video calling feature in all the apps. So if anybody have any solution to this please do share here.
Click to expand...
Click to collapse
There's magisk module called camera2_api+WhatsApp.zip that enable camera 2 api without conflict with any other app (in this case video calling on WhatsApp), i get it somewhere on di xda but not test it yet, i'll report back tomorrow
Bad english, sorry

Some advice: do not choose ROM just because camera2 API enabled. Enabling camera2 API is very easy. Choose ROM according to your needs and preferences first, then worry about camera2 API.

A R said:
they have just provided the option to enable or disable it from settings but what about the video calling feature which gets broken after enabling it ?? did anybody tested on any rom with enabling camera2api ???
Click to expand...
Click to collapse
Whatsapp video calling works perfectly well on Msm Xtented no issues here and in the latest build also comes with A2 ported cam

[Guild] To pass safetynet on Oxygen Android Pie open Beta

After installing Pie open beta Oxygen uploaded by @Funk Wizard many will notice that CTS profile comes FALSE in magisk manager while basicintegrity is TRUE.
to pass saferynet.
We have to change fingerprint of build in the build.prop
There are two methods currently. (Works on Hydrogen Open beta too.)
(Third one is magisk module but in android pie ro.build.fingerprint and many other props are not working. And it will not work until magisk update Resetprop)
Method 1:
Manually Edit Build.prop with text editor or other apps.
(Build.prop will be present in /system )
Replace :
Code:
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
With
Code:
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Method 2 :
Replace build.prop in /system with changed lines which is attached below. With proper permission which is " rw- r-- r-- (644) "
Source: reddit user ipha

Worked! Thanks!
OpenBeta 1 Magisk 17.1 Google Pay is working!

prins29 said:
After installing Pie open beta uploaded by @Funk Wizard many will notice that CTS profile comes FALSE in magisk manager while basicintegrity is TRUE.
to pass saferynet.
We have to change fingerprint of build in the build.prop
There are two methods currently.
(Third one is magisk module but in android pie ro.build.fingerprint and many other props are not working. And it will not work until magisk update Resetprop)
Method 1:
Manually Edit Build.prop with text editor or other apps.
(Build.prop will be present in /system )
Replace :
Code:
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:9/PKQ1.180716.001/1808301430:user/release-keys
With
Code:
ro.build.fingerprint=OnePlus/OnePlus6/OnePlus6:8.1.0/OPM1.171019.011/06140300:user/release-keys
Method 2 :
Replace build.prop in /system with changed lines which is attached below. With proper permission which is " rw- r-- r-- (644) "
Click to expand...
Click to collapse
Tested working fine :good:

Okay this is for oxygen os only, not working on H2os

nksonfire said:
Okay this is for oxygen os only, not working on H2os
Click to expand...
Click to collapse
Already mention on title that it's for Oxygen android pie.

source is from reddit user ipha
https://www.reddit.com/r/oneplus/comments/9cldzf/oxygen_os_open_beta_1_for_the_oneplus_6/e5bjo0s/

Will this have any effect on future updates?

Ankit Chahar said:
Will this have any effect on future updates?
Click to expand...
Click to collapse
will this have any effect on other things as well?

Ankit Chahar said:
Will this have any effect on future updates?
Click to expand...
Click to collapse
MultiCulti said:
will this have any effect on other things as well?
Click to expand...
Click to collapse
Don't worry.. Everything is fine..
Device Fingerprint Is system property which is registered in Google Database of Authorized Device....
When As you can see, Current Fingerprint for OOS Pie Beta 1 is not Registered in Google database so it won't pass SafetyNet..
The Fingerprint which we gone replace is Belong to the OOS based on 8.1 Oreo & registered in Google Database so SafetyNet get passed..
So, It's nothing to Do with Future updates & other things... :fingers-crossed:

Thanks for this..
Trick working fine..
But Google Pay still not working..
Anyway to get it up??

CYB3R0ID694 said:
Thanks for this..
Trick working fine..
But Google Pay still not working..
Anyway to get it up??
Click to expand...
Click to collapse
Google pay aka tez works well for me.
I'm using tezhider4magisk module which may help.
https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567

prins29 said:
Google pay aka tez works well for me.
I'm using tezhider4magisk module which may help.
https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567
Click to expand...
Click to collapse
Thanks.. Thats helpful..
Tez working fine..

cts profile dont pass in UK

asad510 said:
cts profile dont pass in UK
Click to expand...
Click to collapse
Did basicintegrity is true ? Permission set as stated above ? Read only system in twrp ? Not enabled system modification?

Works also i get google certified with this magisk mod:
https://forum.xda-developers.com/apps/magisk/module-google-playstore-services-data-t3789498

prins29 said:
Did basicintegrity is true ? Permission set as stated above ? Read only system in twrp ? Not enabled system modification?
Click to expand...
Click to collapse
Working in the UK, replaced the whole file, set the permissions and rebooted

nksonfire said:
Okay this is for oxygen os only, not working on H2os
Click to expand...
Click to collapse
It's working on hydrogen.

wwwhershcom said:
It's working on hydrogen.
Click to expand...
Click to collapse
you mean it's working on h2os P open beta? please share the screenshot.

prins29 said:
Already mention on title that it's for Oxygen android pie.
Click to expand...
Click to collapse
I was wrong, it worked for h2os pie beta 3

nksonfire said:
I was wrong, it worked for h2os pie beta 3
Click to expand...
Click to collapse
OP updated.

Problem Fixed: Failed to enabled camera2api in "build.prop" file.

for those who facing problems to enable CAMERA2API. Edit build prop still unsuccessful. please try this way. it works for me.
Go to the Magisk Manager
Please disable all magical modules. No need to delete.
Reboot phone.
Then edit build.prop file to enable camera2api.
Save and reboot phones.
Review the build prop, whether previous edits were still saved. If stored, it means you've succeeded.
Test with Camera Probe app. InshaAllah u will get Level 3.
Run gcam. You can use Gcam as desired.
Go to Magisk Manager
Re Enable all the magisk that u disable before.
Reboot phone.

You explained like ****ttt

jorgeepelos said:
You explained like ****ttt
Click to expand...
Click to collapse

Help
Brother,
I am using MiMax 3 chinese rom.
Can you please give a step by step guide how to enable camera2api?

This didnt work, My ROM has nothing to do with the camera 2 api, no app to manage the api, no script until i added it & it didnt understand it (nothing nowhere)