SELinux Permissive - Huawei P20 Pro Questions & Answers

Hello. I have question. I need permissive selinux mode. I have rooted my phone with magisk. My kernel is stock, rom also stock. Now my selinux is enforcing but I need permissive. Magisk modules and Selinuxmodechanger not working. Who can help me?
CLT-L29
Android 9.0.0.236
Kernel 4.9.97
Security patch 1 March 2019

E.Sivko said:
Hello. I have question. I need permissive selinux mode. I have rooted my phone with magisk. My kernel is stock, rom also stock. Now my selinux is enforcing but I need permissive. Magisk modules and Selinuxmodechanger not working. Who can help me?
CLT-L29
Android 9.0.0.236
Kernel 4.9.97
Security patch 1 March 2019
Click to expand...
Click to collapse
Ask @ante0, maybe he can.

kilroystyx said:
Ask @ante0, maybe he can.
Click to expand...
Click to collapse
Ok, thanks. I send a message for him.

kilroystyx said:
Ask @ante0, maybe he can.
Click to expand...
Click to collapse
E.Sivko said:
Ok, thanks. I send a message for him.
Click to expand...
Click to collapse
It's possible with a custom built kernel where this switch is enabled. But in January Huawei decided we can't use custom kernel anymore... It flashes but can't boot with it.
This "fix" was added in Mate 10 Pro, BLA-L29C432B179 (9.0.0.179). And they most likely did the same for other devices in January.
@E.Sivko for what reason do you need permissive?

ante0 said:
It's possible with a custom built kernel where this switch is enabled. But in January Huawei decided we can't use custom kernel anymore... It flashes but can't boot with it.
This "fix" was added in Mate 10 Pro, BLA-L29C432B179 (9.0.0.179). And they most likely did the same for other devices in January.
@E.Sivko for what reason do you need permissive?
Click to expand...
Click to collapse
I want to use tincore keymapper. I tried other mappers but they all have a problem with semi touch. For example i connected single handed gamepad mapped buttons and sticks, I hold left stick to run in a game and at same tame trying to look around using touchscreen in shooting game, so then i tap on screen gamepad stops working and i need press stick on gamepad again if i want to run. So I can't use touchscreen and gamepad same time because they stops each other.

ante0 said:
It's possible with a custom built kernel where this switch is enabled. But in January Huawei decided we can't use custom kernel anymore... It flashes but can't boot with it.
This "fix" was added in Mate 10 Pro, BLA-L29C432B179 (9.0.0.179). And they most likely did the same for other devices in January.
@E.Sivko for what reason do you need permissive?
Click to expand...
Click to collapse
I think that it is selinux problem or maybe old huawei input protocol, i don't know. I just want to use single handed gamepad at same time with touchscreen

Related

Why Permissive kernel?

I am very new to the nexus line as I came from a locked galaxy s5 on Verizon. However I have seen you can get the kernel to always be permissive. What benefits does this bring? I use xposed and was wondering if anything would help me there. Thanks for any help or insight!
Some xposed modules and mods may require the kernel to be permissive.
To read more, read https://source.android.com/devices/tech/security/selinux/concepts.html
It should be noted that Google wants your phone to be in enforcing to be secure.
zephiK said:
Some xposed modules and mods may require the kernel to be permissive.
To read more, read https://source.android.com/devices/tech/security/selinux/concepts.html
It should be noted that Google wants your phone to be in enforcing to be secure.
Click to expand...
Click to collapse
Are there any other benefits or uses other than xposed?
Also, are most custom kernels enforcing by default? Still trying to understand everything
zephiK said:
Some xposed modules and mods may require the kernel to be permissive.
To read more, read https://source.android.com/devices/tech/security/selinux/concepts.html
It should be noted that Google wants your phone to be in enforcing to be secure.
Click to expand...
Click to collapse
Excellent information, thank you for this. :good:
Well worth reading.
xdnax said:
Are there any other benefits or uses other than xposed?
Also, are most custom kernels enforcing by default? Still trying to understand everything
Click to expand...
Click to collapse
Viper4android needs permissive too.
Could anyone help me with a tweakable kernel for note 4 SM-N910H
ebongutibe said:
Could anyone help me with a tweakable kernel for note 4 SM-N910H
Click to expand...
Click to collapse
Try asking in the note 4 forum. This is the nexus 6 forum.

[KERNEL]Despair Kernel

This is the new refined home for DarkRoom Development. If you submit bug reports without a log, you may be prosecuted...or executed.
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.
Links:
Social:
Twitter - http://twitter.com/mtthwlx
Downloads:
https://drive.google.com/drive/folders/1zwaS15e4zXiSWuEU_ZOjTLBqtdzP86dL?usp=sharing
Source:
Github – https://github.com/DespairFactor/
Credits:
Essential
Google
Star Wars
Finally...
Good to see the development..
Special thanks to the members who donated f&f codes.
And @DespairFactor for quick release..
Hype.
Oof
indian84 said:
Finally...
Good to see the development..
Special thanks to the members who donated f&f codes.
And @DespairFactor for quick release..
Click to expand...
Click to collapse
ghostENVY said:
Hype.
Click to expand...
Click to collapse
LeTurntRice said:
Oof
Click to expand...
Click to collapse
There are no features yet, I am working on EAS tweaks for stock at the moment and will likely also do an HMP kernel
n00b question... What does this kernel have? Also would you be able to dive into the camera apk to help solve compression issue and color saturation since you have the phone now?
xterminater07 said:
n00b question... What does this kernel have? Also would you be able to dive into the camera apk to help solve compression issue and color saturation since you have the phone now?
Click to expand...
Click to collapse
I am about to push my changes to github, I am unaware of what the issue is or if I can help. but I can try when I have free time
Oh nice, we get to be named after Rei? Curious as to whether you intend for this to work on AOSP, LOS or stock ROMs?
ChronoReverse said:
Oh nice, we get to be named after Rei? Curious as to whether you intend for this to work on AOSP, LOS or stock ROMs?
Click to expand...
Click to collapse
Right now this is for stock oreo beta 2, will work on other stuff as I have time, but I am hoping they release stock oreo soon
OH! Does it include patches to pass Safetynet despite the unlocked bootloader as well? Would like to avoid Magisk if possible.
ChronoReverse said:
OH! Does it include patches to pass Safetynet despite the unlocked bootloader as well? Would like to avoid Magisk if possible.
Click to expand...
Click to collapse
I am adding that right now, I am testing some boot issues with one of my commits, R1 will be up for all when it is resolved
Hi,
What is the correct way to flash, boot.img then magisk. I cant remember. Blame the booze.
Thanks
R1 good to go? As its uploaded i see
Edit: Guess so as flash and passed safety net
DaveHTC200 said:
R1 good to go? As its uploaded i see
Edit: Guess so as flash and passed safety net
Click to expand...
Click to collapse
NZnewbie said:
Hi,
What is the correct way to flash, boot.img then magisk. I cant remember. Blame the booze.
Thanks
Click to expand...
Click to collapse
R2 is up now, I am working on getting AnyKernel to work and keep recovery on device if possible when flashing.
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Tried Rey2.zip nd booted back to twrp and the touch didnt work. Using the latest twrp as well
DespairFactor said:
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Click to expand...
Click to collapse
DespairFactor said:
We have confirmed that the flashable zip keeps TWRP on your phone and you get to keep the kernel and your system working fine!
To root with this, flash twrp to your boot partition using fastboot, flash the kernel zip and then flash magisk.
EDIT: also confirmed to work on nougat!
Click to expand...
Click to collapse
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
NZnewbie said:
Tried Rey2.zip nd booted back to twrp and the touch didnt work. Using the latest twrp as well
Click to expand...
Click to collapse
Looking into it, I think flashing magisk makes touch work, will see if I can fix it within the kernel side.
gk1984 said:
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
Click to expand...
Click to collapse
Yes it is, I have it on my device right now
Ive heard theres a fix coming for that as well(hope so)
gk1984 said:
Is Magisk working with this kernel on Oereo B2? Magisk 14.3 caused lots of reboots, 14.6 just doesn't work (no magisk after boot).
Click to expand...
Click to collapse
DespairFactor said:
I am about to push my changes to github, I am unaware of what the issue is or if I can help. but I can try when I have free time
Click to expand...
Click to collapse
The problem with the stock camera app was that it compresses images too much, they have lower the compression ratio but it is still not good enough. You can try it yourself to see what I mean. In broad day light outdoor, the images appears to be great but if you zoomed in, you will see it it just doesn't look right. The color is washed out as well, and you don't see any details. Looks like everything is smoothed out. File size is about 6 to 7mb or so. The low light shots are worst, it's about 3mb and there's more fuzzy stuff and lack of details/sharpness.
If you can dive deep into the apk to see what they set the compression to, and change that to possibly 0, and see what else needs to be changed. I spoke to Arnova8g2, who helped ported the gcam hdr+ to oneplus3/3t and he helped fixed the compression a bit on the older apk but I can't overwrite it no matter what. Let me know if you need any more info.

project treble support???

will Honor 9 Lite support project treble???
gds06 said:
will Honor 9 Lite support project treble???
Click to expand...
Click to collapse
It comes loaded with oreo, so it must.
I can confirm that it supports project treble ??
Have you tried the "getprop ro.treble.enabled" command in the terminal ? If no, could you please confirm whether the value was "true" or "false".
I used treble check app & it says there is support for treble but no A/B partition so no seamless updates.
khanjunaid said:
I used treble check app & it says there is support for treble but no A/B partition so no seamless updates.
Click to expand...
Click to collapse
I'm a little confused. How come it supports Treble if it doesn't have a separate 'vendor partition' which is supposed to bring seamless updates?
I don't think the app you're using is reliable.
Well, either that or I'm missing something BIG about Project Treble!
He didn't say that! The phone does indeed have a vendor partition, it just doesn't have the A/B scheme (that's what he said at least).
Xhah said:
I'm a little confused. How come it supports Treble if it doesn't have a separate 'vendor partition' which is supposed to bring seamless updates?
I don't think the app you're using is reliable.
Well, either that or I'm missing something BIG about Project Treble!
Click to expand...
Click to collapse
gds06 said:
will Honor 9 Lite support project treble???
Click to expand...
Click to collapse
When I do a hard reset, will project treble stay intact? I'd do a hard reset to get rid of the installed bloatware before I setup the phone.
Dio-Genes said:
When I do a hard reset, will project treble stay intact? I'd do a hard reset to get rid of the installed bloatware before I setup the phone.
Click to expand...
Click to collapse
Okay, got my device today, did a factory reset before starting. All worked fine. Yes, for sure Project Treble support, but only A-Partition. But after the reset and setup all that Bloatware was there again. Well, not to nice, but you can uninstall some of them. The device is really nice and you really get a lot of SP for the money. So, now wait for the first updates to come
?
faizk123485 said:
Is this device got project treble and support and custom rom support in future becoz i m thinking buy it or i buy xiaomi redmi note 5
Click to expand...
Click to collapse
Did you read the thread???
Dio-Genes said:
Did you read the thread???
Click to expand...
Click to collapse
Srry ?
Yesterday the first Update came in OTA. LLD-L31 8.0.0.127(C432)
Enhancement for VoLTE an VoWiFi and Security Patch for February 2018. Size: 314 MB.
Didn't install on the first time, but second time it all worked fine.
Just FYI...
Dio-Genes said:
Yesterday the first Update came in OTA. LLD-L31 8.0.0.127(C432)
Enhancement for VoLTE an VoWiFi and Security Patch for February 2018. Size: 314 MB.
Didn't install on the first time, but second time it all worked fine.
Just FYI...
Click to expand...
Click to collapse
Was this through normal phone OTA ? our some other way? Haven't got anything on same model yet in the uk.
xzyk said:
Was this through normal phone OTA ? our some other way? Haven't got anything on same model yet in the uk.
Click to expand...
Click to collapse
OTA. Checked for updates and there it was. I'm in Germany.
Dio-Genes said:
OTA. Checked for updates and there it was. I'm in Germany.
Click to expand...
Click to collapse
Thanks, just tried using VPN via Germany, but still got nothing. I have 3 huawei/honor devices and none of them have ever worked via the phone updater, always have to use FF. On the H9L however not even the stock firmware is available yet let alone any updates. Thanks for replying anyway.:good:
xzyk said:
Thanks, just tried using VPN via Germany... On the H9L however not even the stock firmware is available yet let alone any updates. Thanks for replying anyway.:good:
Click to expand...
Click to collapse
Yes, the Stock Firmware is not available yet. Hope it is coming soon. Want to try this LOS thing, I don't like the EMUI too much.
I bought my H9L on 06.02.2018 from Amazon.de, well and yesterday the update appeared. One month after purchasing. Don't know if this is important...
Dio-Genes said:
Yes, the Stock Firmware is not available yet. Hope it is coming soon. Want to try this LOS thing, I don't like the EMUI too much.
I bought my H9L on 06.02.2018 from Amazon.de, well and yesterday the update appeared. One month after purchasing. Don't know if this is important...
Click to expand...
Click to collapse
why not just install LOS ? the one for honor view 10 works without problems. running it for over a week now without issues. there cant go much wrong. i didnt backup stock before it either.
Sent from my Honor 9 Lite using XDA Labs
4RK4N said:
why not just install LOS ? the one for honor view 10 works without problems. running it for over a week now without issues. there cant go much wrong. i didnt backup stock before it either.
Click to expand...
Click to collapse
The reason i haven't done that, as i explained in the other thread, is because i need android pay, or Google pay as it's called now. I know i can pass Safetynet with some fiddling with magdisk, but as you know magdisk vs Google is a cat and mouse story, Google closes one hole resulting with magdisk failing safetynet, then magdisk updates and safetynet passes again, then Google closes that hole and so on and on. Android pay is too important for me to have to keep doing that. Without magdisk as soon as BL is unlocked, which is required for LOS, safetynet fails. If GPay wasn't so important to me i would have loaded LOS , or phh AOSP, some time ago as EMUI is just bloatware in my opinion. Why OEMs, and it's not just Honor, think their skins are better than stock is strange. If they truly believe their skin is that great then make it an apk and let users decide, don't force it down people's throat and then not even give them the option to disable it...rant over..
4RK4N said:
why not just install LOS ? the one for honor view 10 works without problems. running it for over a week now without issues. there cant go much wrong. i didnt backup stock before it either.
Click to expand...
Click to collapse
True, but even without the chance to go back to Stock if I want, is just too risky for me at the moment. Sure will try later...

[HowTO] Treble for S9

Hello everyone,
After seeing the news that Treble images were properly working on the S9, I decided to give it a go and see for myself how good/bad was it working.
The from my findings, the only thing that is NOT working is the auto-brightness.
Here are the installation steps :
Make sure you got TWRP installed properly, with DM-Verity and Encryption disabled.
Download this : https://www.androidfilehost.com/?fid=817906626617958348
Place it in the root of your device, then navigate to TWRP, click install, click install Image, select the transfered system.img, and select system image.
Make sure to full wipe after that, and reboot, and you are good to go.
This is awesome. As soon as I'm able to get my hands on an Exynos variant S9, I'm buying one for Treble support alone.
Auto-brightness doesn't work because the framework doesn't define any brightness levels for each lux level. You can make an overlay to fix that or modify the framework at source.
MishaalRahman said:
Auto-brightness doesn't work because the framework doesn't define any brightness levels for each lux level. You can make an overlay to fix that or modify the framework at source.
Click to expand...
Click to collapse
I'll pass onto phh, see if he can include a fix in his builds.
Works Samsung câmera app?
how about camera's aperture (switch between 1.5 and 2.4) , slow motion too ?
Paradoxxx said:
Hello everyone,
After seeing the news that Treble images were properly working on the S9, I decided to give it a go and see for myself how good/bad was it working.
The from my findings, the only thing that is NOT working is the auto-brightness.
Here are the installation steps :
Make sure you got TWRP installed properly, with DM-Verity and Encryption disabled.
Download this : https://www.androidfilehost.com/?fid=817906626617958348
Place it in the root of your device, then navigate to TWRP, click install, click install Image, select the transfered system.img, and select system image.
Make sure to full wipe after that, and reboot, and you are good to go.
Click to expand...
Click to collapse
Any idea how to build a treble image?
I know how to build for a specific device but treble... bohh. Maybe you can help me.
Astrubale said:
Any idea how to build a treble image?
I know how to build for a specific device but treble... bohh. Maybe you can help me.
Click to expand...
Click to collapse
phh is sharing his build script : https://github.com/phhusson/treble_experimentations/blob/master/build.sh
That should get you started
Paradoxxx said:
Hello everyone,
After seeing the news that Treble images were properly working on the S9, I decided to give it a go and see for myself how good/bad was it working.
The from my findings, the only thing that is NOT working is the auto-brightness.
Here are the installation steps :
Make sure you got TWRP installed properly, with DM-Verity and Encryption disabled.
Download this : https://www.androidfilehost.com/?fid=817906626617958348
Place it in the root of your device, then navigate to TWRP, click install, click install Image, select the transfered system.img, and select system image.
Make sure to full wipe after that, and reboot, and you are good to go.
Click to expand...
Click to collapse
owsome guide thanks
---------- Post added at 11:23 AM ---------- Previous post was at 11:22 AM ----------
hoangtu2410 said:
how about camera's aperture (switch between 1.5 and 2.4) , slow motion too ?
Click to expand...
Click to collapse
on aosp u loose some tw features
matheus_sc said:
Works Samsung câmera app?
Click to expand...
Click to collapse
Nope
hoangtu2410 said:
how about camera's aperture (switch between 1.5 and 2.4) , slow motion too ?
Click to expand...
Click to collapse
Stays at 1.5, and not sure about slow motion.
Paradoxxx said:
Nope
Stays at 1.5, and not sure about slow motion.
Click to expand...
Click to collapse
damn... maybe it is possible to collect the camera.apk and all needed libs to get the samsung app to work on aosp rom ??
inteks said:
damn... maybe it is possible to collect the camera.apk and all needed libs to get the samsung app to work on aosp rom ??
Click to expand...
Click to collapse
It's also framework related so very much unlikely to happen.
have you guys also tested if the telephoto lens activates when you zoom in?
iamnotkurtcobain said:
It's also framework related so very much unlikely to happen.
Click to expand...
Click to collapse
Porting the frameworks has recently happened for Huawei and Sony. Unless Samsung are deliberately obfuscating things, it should be possible to do the same for the Exynos versions of the S9 and S9+.
Can someone post screenshots
Im so excited .. this is one of the biggest reasons why I will switch to s9+
Hi sorry for a noob question I am new here, after flashing the image will I get stock android ? Like lineage os ?
Thanks
pavneet10174 said:
Hi sorry for a noob question I am new here, after flashing the image will I get stock android ? Like lineage os ?
Thanks
Click to expand...
Click to collapse
Yes
Griffiths_Anna said:
Yes
Click to expand...
Click to collapse
Hey thanks a lot for helping,
I have one more question, when I flashed aosp ROM it worked fine but with the brightness glitch, however when I flashed lineage os it just bootlooped so any suggestions ?
Thanks
26th builds of 8.1 are okay for brightness but fingerprint is broken for some and causes touch to stop but reboot, unlock then a few lock/unlock cycles it's good temp fix til next reboot

[KERNEL][SOLUTION] Magisk 17 and higher for Stock ROMs

This kernel fixes continuesly reboots when you install magisk v17 or higher on lastest oreo stock rom.
Requirements
A2017U_V2.1.0B20 Firmware
TWRP
Instructions
Install a fresh Stock ROM.
Boot it once.
Install TWRP.
Install the boot image over TWRP by choosing install image option.
Flash Magisk v17 or higher.
Flash custom signed kernel modules magisk module over TWRP.
Reboot phone.
Download
BOOT_A2017U_V2.1.0B20_for_magisk_signed.img
Custom_Signed_Modules_A2017U_V2.1.0B20.zip
XDA:DevDB Information
[KERNEL][SOLUTION] Magisk 17 and higher for Stock ROMs, Kernel for the ZTE Axon 7
Contributors
asderdd
Source Code: https://github.com/Asderdd/android_kernel_zte_axon7/tree/zte-8.0.0
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: A2017U_V2.1.0B20
Created 2018-10-21
Last Updated 2018-10-21
Thanks ihsan awesoma work :good: :highfive:
Any idea if this can also be used on nougat roms? Or perhaps the same modification used to boot those with Magisk?
Dodgexander said:
Any idea if this can also be used on nougat roms? Or perhaps the same modification used to boot those with Magisk?
Click to expand...
Click to collapse
I can do it again for nougat but I recommend you to use oreo b20. It's better than all others about sound quality, camera and more stuff.
asderdd said:
I can do it again for nougat but I recommend you to use oreo b20. It's better than all others about sound quality, camera and more stuff.
Click to expand...
Click to collapse
It is possible doing this for the A2017V3.0.0B17 ?
for all axon 7 phones running oreo b20 stock?
Thanks for your job, I've seen your source under github, can you confirm that to avoid bootloops on Magkisk > 17 is enough to set to "n" the SeLinux policy?
Teşekkürler.
foggydew88 said:
Thanks for your job, I've seen your source under github, can you confirm that to avoid bootloops on Magkisk > 17 is enough to set to "n" the SeLinux policy?
Teşekkürler.
Click to expand...
Click to collapse
Yes, if you want use a custom init binary you need to disable zte's policyproc.
Aviver said:
It is possible doing this for the A2017V3.0.0B17 ?
Click to expand...
Click to collapse
If you send me pm that includes the stock boot.img and /system/lib/modules /system/vendor/lib modules folders it's possible.
Predatorhaze said:
for all axon 7 phones running oreo b20 stock?
Click to expand...
Click to collapse
Absolutely.
great work!
Hi, thanks for your work but after this i have no wifi on G model.
ppllpp said:
Hi, thanks for your work but after this i have no wifi on G model.
Click to expand...
Click to collapse
Don't forget to install Magisk module that I gave.
asderdd said:
Don't forget to install Magisk module that I gave.
Click to expand...
Click to collapse
Ok, solved using directly Magisk to flash custom module. Thanks.
Thanks for this @asderdd works well. Do you know if it will still work with v17.2 or v17.3? I tried but it doesn't seem too although I know they are beta and dev versions.
ppllpp said:
Hi, thanks for your work but after this i have no wifi on G model.
Click to expand...
Click to collapse
This is probably because you didn't boot first. I had this too. Make sure you install stock rom first, install recovery and then after the first boot make sure to restart, go to recovery and then flash it according to the steps.
Dodgexander said:
Thanks for this @asderdd works well. Do you know if it will still work with v17.2 or v17.3? I tried but it doesn't seem too although I know they are beta and dev versions.
Click to expand...
Click to collapse
Sure, it works with all sub versions of magisk 17. I'm using magisk 17.4 canary build at this moment.
Dodgexander said:
Thanks for this @asderdd works well. Do you know if it will still work with v17.2 or v17.3? I tried but it doesn't seem too although I know they are beta and dev versions.
This is probably because you didn't boot first. I had this too. Make sure you install stock rom first, install recovery and then after the first boot make sure to restart, go to recovery and then flash it according to the steps.
Click to expand...
Click to collapse
Yes i know i should have followed exactly the instruction but i flashed recovery and modem with miflash all at once then twrp and encryption is not the best...anyway problem solved. Even if custom module in twrp give me error and i don t know why, maybe encryption.
I have tried Oreo yet, but I'm very eager to do so. I've seen some comments that system is now only ro, does this fix this? And can i assume safetynet passes on this? Thank you!
Sent from my ZTE A2017U using Tapatalk
@asderdd On stock latest nougat A2017U Magisk 17.x also bootloops to recovery, is this a separate problem? I'm interested in reporting whatever you had to do to topjohnwu so he can make a fix in Magisk if possible. Or better yet if you're not to busy maybe you can advise him?
thanks
bluenote73 said:
I have tried Oreo yet, but I'm very eager to do so. I've seen some comments that system is now only ro, does this fix this? And can i assume safetynet passes on this? Thank you!
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Nope it doesn't effect mount status of system. I recommend you to make a magisk module that can adds, modifies or removes files systemlessly. Unfortunately b20 rom can't pass safetynet.
bluenote73 said:
@asderdd On stock latest nougat A2017U Magisk 17.x also bootloops to recovery, is this a separate problem? I'm interested in reporting whatever you had to do to topjohnwu so he can make a fix in Magisk if possible. Or better yet if you're not to busy maybe you can advise him?
thanks
Click to expand...
Click to collapse
The solution is disabling zte's selinux policyproc feature. Lookup the commits at github for details. I don't know what had changed on magisk v17 to cause conflict with our policyproc.
asderdd said:
Unfortunately b20 rom can't pass safetynet
Click to expand...
Click to collapse
I am pretty sure I had safetynet passing fine with your solution before + MagiskHide props config module but I kept losing it after some time. I thought it was something I did wrong but today after a fresh reinstall I still can't pass safetynet with the MagiskHide props config module spoofing the Nougat ZTE Axon fingerprint.
Have google done something which means we can't pass safetynet on b20?
only twrp from nfound works on this rom?
---------- Post added at 12:24 PM ---------- Previous post was at 12:00 PM ----------
doesnt work for me,G version.Magisk is shown in app list,but not in drawer and no root is detected
---------- Post added at 12:29 PM ---------- Previous post was at 12:24 PM ----------
i rebooted again,works now.Magisk 17.3

Categories

Resources