Mate 10: Can't change SELinux policy from Enforced to Permissive. - Huawei Mate 10 Questions & Answers

Hi,
First I don't know if I opened this thread in the correct subforum. I've searched for selinux in Mate 10 forum and found this thread:
https://forum.xda-developers.com/mate-10/help/update-ota-lb-t3722735
but just mentions my problem without discussing it.
Device info:
- Mate 10 ALP-L09-C432-B128 Android 8.0.0, original stock rom
- Magisk 16.0 and Magisk Manager 5.6.4.
The problem:
For an apk problem with SELinux, I need to set selinux policy to Permissive, since is Enforced by default.
I tried four apps (SELinux Toogler, SELinux Changer, SELinux Switch and Magisk SELinux module), but policy remains enforced.
I'm running getenforce command everytime and always shows Enforced.
Also tried manually with "setenforce 0" command, but I get "Invalid Argument" error code.
Any help wil be appreciated.
Best regards.

It's disabled in kernel as of Oreo by default (for some reason, security I guess). You'd need a custom kernel to get that back.
https://forum.xda-developers.com/mate-10/development/kernel-mate-10-mate-10-pro-stock-t3744501 you can use mine. I will update to April patches when they go public.

After flash the custom kernel via fastboot I can change SELinux policy.
Thanks a lot.

Hi, sorry for hijacking this thread but am curious, will this work on a P20 Pro? ?

MajinkenSword said:
Hi, sorry for hijacking this thread but am curious, will this work on a P20 Pro?
Click to expand...
Click to collapse
The kernel most likely will not, as it's for Mate 10/Pro.
Well, it should boot fine, but many things will be broken.

ante0 said:
The kernel most likely will not, as it's for Mate 10/Pro.
Well, it should boot fine, but many things will be broken.
Click to expand...
Click to collapse
The P20 Pro lacks support on this and would like to try making or modifying the kernel.
Heard that the source was available but development is sluggish for our device.
Hope you don't mind but would you happen to have a guide for us to accomplish this?
Would appreciate your feedback. Thank you! ??

Related

My phone runs 6.0.1 but can't detect root?

So I have rooted my i9100 on May 2013 so I can flash CM KitKat, and the SuperSU was working just fine, same thing when I flashed Lollipop. But since I flashed Marshmallow (In which I encountered some issues as my phone was bricked because I didn't do the repartition thing, but the XDA team solved it :good: ) it's as if my phone isn't rooted at all! SuperSU doesn't pop up anymore asking me to grant root access, apps who require root don't work, but I still can flash ROMs and updates with no problems at all, I'm so confused
Now, I was thinking about rooting it again, but I don't know whether that would be safe or not, so I decided that it's better to ask about it here before I brick my phone for 16,520,735th time
What should I do!?
Android version: 6.0.1
CyanogenMod version: 13.0-20160930-NIGHTLY-i9100
Kernel version: 3.0.101-CM-g43c083a
zedex39zeo said:
So I have rooted my i9100 on May 2013 so I can flash CM KitKat, and the SuperSU was working just fine, same thing when I flashed Lollipop. But since I flashed Marshmallow (In which I encountered some issues as my phone was bricked because I didn't do the repartition thing, but the XDA team solved it :good: ) it's as if my phone isn't rooted at all! SuperSU doesn't pop up anymore asking me to grant root access, apps who require root don't work, but I still can flash ROMs and updates with no problems at all, I'm so confused
Now, I was thinking about rooting it again, but I don't know whether that would be safe or not, so I decided that it's better to ask about it here before I brick my phone for 16,520,735th time
What should I do!?
Android version: 6.0.1
CyanogenMod version: 13.0-20160930-NIGHTLY-i9100
Kernel version: 3.0.101-CM-g43c083a
Click to expand...
Click to collapse
In CM13, did you enable root for apps in the developer menu (tap the build number a few times)?
SuperSU doesn't work on our device with CM13.
Saber
Saber said:
In CM13, did you enable root for apps in the developer menu (tap the build number a few times)?
SuperSU doesn't work on our device with CM13.
Saber
Click to expand...
Click to collapse
I feel stupid for never checking the Developer Menu :silly:
Thank you so much, worked like a charm
Yes it does, open terminal type:
setenforce 0 this changes selinux to permissive now you can run supersu.

Max 2 fails SafetyNet, does it have malware?

So I got a Max 2 x829 which came with a case. It's running Android 6.0.1. It fails SafetyNet CTS and Basic Integrity, so does not run Pokemon Go. Is this expected, or did a reseller add malware on the device?
Mine suffers from the same problem. Where did you buy yours?
I wouldn't put much stock in safety net.
castuis said:
I wouldn't put much stock in safety net.
Click to expand...
Click to collapse
What do you mean? Not passing SafetyNet means not being able to play/download some of the best games on the PlayStore. I think it's relevant.
Same here. I'm using cuoco92 ROM. I tried safety net that comes with magisk manager, but it doesn't work. I really doubt that there is malware installed, but I've no idea why it fails...maybe because ROM is rooted?!
Let me think about this... Most people have buy this device from a international reseller shop instead of the official Leeco store or online shop. Makes sense cause I'm pretty sure that most of the users here on the board are not living in China or India.
Every online shop is installing a custom ROM to make sure that as many languages as possible are supported. The most installed "Shop-Rom" is couco92...
As far as we know every Android device that is able to run a custom ROM needs an opened bootloader and especially couco92 comes with the ability to run SuperSU and Root!
If you just search Google for "SafetyNet" you find an official statement why it's not possible to run Banking or
Pay-Apps and why there's no possibility to run games like Pokemon go on rooted devices!!!
So let me think again about this...
Sorry guys but I also don't understand why the hell this device isn't able to pass the SafteyNet check! It must be because of malware or something like this!!!
Sorry for being so damn ironic! Hopefully it's self explaining why I wrote a post like this and you are able to get the informations you are looking for from the text...
Thanks for the answer, albeit the unnecessary sarcasm. Assuming that's true (which sounds quite reasonable) would the original ROM fix the problem? is the original ROM maybe supporting english language? And could anyone confirm such ROM does indeed pass SafetyNet checks? Thanks!
So ended up flashing the last Indian stock ROM. That solved the "basic integrity" check and now I can download from Play Store apps not previously visible. However, still does not pass the CTS check.
I believe such checks are over exaggerated, hackers can hack strongly locked iPhones or anything similar, so it doesn't matter CTS pass or fail as long as you keep your phone fully scanned with reasonable antivirus/security apps.
I think thats because your phone has bootloader unlocked.
This is the reason:
Devices that ship with Google's Play Store and other apps installed must pass Google's Android “Compatibility Test Suite”. Rooting a device or installing a custom ROM prevents a device from being “CTS Compatible”. This is how the SafetyNet API can tell if you're rooted–it merely checks for CTS compatibility. Similarly, if you get an Android device that never came with Google's apps–like one of those $20 tablets shipped direct from a factory in China–it won't be considered “CTS compatible” at all, even if you haven't rooted it.
Click to expand...
Click to collapse
Source
Heyyo, use the official LineageOS MM ROM. It passes safety net. There's some other ROMs but I'm not sure. I'll try it on Mokee MM build and report back.
RR N fails Safety Net as it is pre rooted and some other tweaks that cause it to fail.
Oh, another reason why it can fail safety net is modem firmware. You might have to revert to a Chinese or Indian or international modem firmware. I don't think developer firmware works for SafetyNet
ThE_MarD said:
Heyyo, use the official LineageOS MM ROM. It passes safety net. There's some other ROMs but I'm not sure. I'll try it on Mokee MM build and report back.
RR N fails Safety Net as it is pre rooted and some other tweaks that cause it to fail.
Oh, another reason why it can fail safety net is modem firmware. You might have to revert to a Chinese or Indian or international modem firmware. I don't think developer firmware works for SafetyNet
Click to expand...
Click to collapse
I can't pass SafetyNet with latest (04/29) LineageOS 13 nightly. I tried with Chinese 23S modem, wipe everything except Internal Storage, and install Open GApps Pico. I still get CTS Profile Mismatch. I tried with it as my Internal ROM under MultiROM, which I believe should be OK. I think it's expected to fail if installed as a Secondary. In any case, I have no particular reason I need to pass SafetyNet, I just thought I'd try. I've read that on newer Android devices, an unlocked bootloader can cause SafetyNet to fail (unless kernel is patched). I didn't try re-locking my bootloader so that could be it.
Heyyo, hmm well I tried ASOP based DU rom but it failed too but then again I'm using MultiRom as well so I'm unsure if that messes with it since it's a custom boot.img which I think is part of the SafetyNet check...

[Magisk/Module] Enable NFC-SIM Function On OnePlus 8 Pro [2020/06/12]

Hi All, just share an easy module to enable nfc-sim on 8 pro, hope can help someone NEED IT.
I will not answer about "what is NFC-SIM" question, PLEASE DO SOME RESEARCH!
Requirements
NFC-SIM (already activated)
Oneplus 8 Pro
OxygenOS 10
Magisk 19+
※May work on another ONEPLUS devices, you can try it and leave a comment ((I'm not responsible for bricked devices)) !! ※
Instruction
Flash The Module via Magisk and Reboot.
Re-Enable NFC Toggle. (make sure system reload the config)
Already Tested
Stock Stable OOS 10.5.10
CHT NFC-SIM Card
EasyCard
Bus、MRT、Train
Convenience Store POS and Kiosk
Issue
- None
Daily Use (2020/06/12)
Changelog
v0.3
-> First Release
Source Code
Github Repo
Credits
@topjohnwu Awesome Magisk !
@steven71508 Helping me to test the module
very thanks and how about it use for oneplus 7 pro?
very thanks and how about it use for oneplus 7 pro?
i really really want it so much
yyuuping said:
very thanks and how about it use for oneplus 7 pro?
i really really want it so much
Click to expand...
Click to collapse
Hi,
First of all, 8 Pro has been use new NXP NFC Chip SN100 different as 7 Pro PN533.
Second, 7 Pro、7T、7T Pro have different design otherwise my 6T module it should work and I don't have those phone so development progress slowly, please understand thx.
Very thanks your reply and i hope u can help me
If can ,i also can pay .
Pls and very thank you.
I just really want this function for my life city hongkong.
Thanks again.
hi may i ask how about now?
i really teally want it pls
yyuuping said:
i really teally want it pls
Click to expand...
Click to collapse
Hey, If you really want to help just don't keep asking about the progress
According to my research and surmise, the API that triggered NFC-SIM was moved to the app they call "公交卡" (app package name: cn.oneplus.wallet), so if you want to try you can download my "6T NFC-SIM Magisk Module" and "APP", the APP need to set default as your payment settings, maybe it will work.
Hi,
It uses Magisk so the phone needs to be rooted, or at least BL Unlocked right?
I need it for ViaNAVIGO (Ticket purchase for Parisian transports) but I’m afraid that rooting/BL unlocking disables Google Pay and banking apps...
TheBledard said:
Hi,
It uses Magisk so the phone needs to be rooted, or at least BL Unlocked right?
I need it for ViaNAVIGO (Ticket purchase for Parisian transports) but I’m afraid that rooting/BL unlocking disables Google Pay and banking apps...
Click to expand...
Click to collapse
Maybe you can use Magisk Hide Props or simply Magisk Hide if you have troubles with some apps
I am very envious. It seems that I will never have an NFC-SIM on my OnePlus 5 Android 10.
Tian Ya Feng Hao Da said:
I am very envious. It seems that I will never have an NFC-SIM on my OnePlus 5 Android 10.
Click to expand...
Click to collapse
even on Android 10 !?
hmm I will take a look about 5T A10 system
That's great, thank you very much, no matter whether it succeeds in the end or not!NFC-SIM can be used in Android 8.1 and below before, but it will not be available after upgrading to Android 9.0 and above
真的希望能在5T 10 系统上使用
oneplus 8, didn't work form me (. Who could make it work, please help
Anyone test in OOS11 ?
Kris Chen said:
Anyone test in OOS11 ?
Click to expand...
Click to collapse
Well, OOS11 EU version has supported for NFC-SIM.
But this module seems to work at A11 AOSP ROM as well after testing it.

[Curtana] Does flashing a custom ROM compel disabling force encryption?

First of all, I'm really sorry if this thread would turn out to be a dumb enquiry. I am new to intrinsically customising my phone and only have been using this device (Redmi Note 9S EEA Curtana, MIUI Global V11.0.4.0. QJWEUXM 4/64 GB) for 10 days. I've successfully installed root and TWRP on my phone after having thoroughly researched relevant information. The only thing is all my efforts regarding the removal of force encryption have so far failed. I'm inclined to install a custom ROM, e. g. LineageOs or Evolution X.
1. Is it a necessity to have encryption permanently disabled so that the flashing process proves viable? Currently, I'm only aware of a method which has its effect limited to the the period the phone is in recovery. It involves formatting data and then installing Magisk and thus I need to go through the set-up again. At the end of the operation, encryption is enabled again. I have no clue why. I've tested loads of no verity opt files, none of them worked in a proper way either.
2.Will installing a custom ROM eliminate root acces (since it performs a reinstallation targeting the entire system, let alone the patched boot image)?
3. In case something goes wrong, what's the correct procedure to return to the factory ROM? Is re-locking the bootloader a prerequisite? (See this guide https://c.mi.com/uk/miuidownload/detail?guide=2, for example. Notice how each of the stable MIUI releases there are marked with ★ next to them, meaning they're locked. I didn't quite grasp the message they were trying to convey with that explanation though.)
I'm conscious that's a lot to ask in a single thread, however, unlike myself, the majority of users here are supposedly tech enthusiast and probably have encountered similar difficulties on several occasions.
I hope that I've provided enough information and the thread has been named reasonably.
(Priority: detailed answers within a month would be great.)
Cheers,
Hsjaai
Just format data: twrp->wipe->format data write yes->reboot twrp and flash rom.
If you got error(red lignes reboot twrp and format again).
or
delete all your lockscreen security before flashing but to install a new rom you must format the data before.
Thanks for your quick response, honestly I didn't expect anyone to be this early to react.
As I've already mentioned, in TWRP there's a workaround for temporarily disabling encryption using the first method, the latter one doesn't seem to function as intended - that may be the case on newer devices, according to an article I've come across.
One last request. Could you please (briefly) answer my two other questions as well? How do I reinstall MIUI if something breaks down? Is the flashing apparatus provided by Xiaomi reliable?
I'll keep you updated on my progress,
Hsjaai
Hsjaai said:
Thanks for your quick response, honestly I didn't expect anyone to be this early to react.
As I've already mentioned, in TWRP there's a workaround for temporarily disabling encryption using the first method, the latter one doesn't seem to function as intended - that may be the case on newer devices, according to an article I've come across.
One last request. Could you please (briefly) answer my two other questions as well? How do I reinstall MIUI if something breaks down? Is the flashing apparatus provided by Xiaomi reliable?
I'll keep you updated on my progress,
Hsjaai
Click to expand...
Click to collapse
Use this tool who is reliable(if you follow the instructions). In all cases unroot before and reboot (if necessary).
NOSS8 said:
Use this tool who is reliable(if you follow the instructions). In all cases unroot before and reboot (if necessary).
Click to expand...
Click to collapse
Thank you so much once again for the help. What should I do if the worst-case scenario arised -essential parts of the file system got corrupted so that the phone wouldn't be capable of booting into system? Uninstall magisk via zip and then make use of the fastboot tool?
Hsjaai said:
Thank you so much once again for the help. What should I do if the worst-case scenario arised -essential parts of the file system got corrupted so that the phone wouldn't be capable of booting into system? Uninstall magisk via zip and then make use of the fastboot tool?
Click to expand...
Click to collapse
1)Normaly yes
2)Or with app(i prefer)
NOSS8 said:
2)Or with app(i prefer)
Click to expand...
Click to collapse
What did you mean by that exactly?
Besides, sorry for bothering you, it's just that I'm genuinely curious and don't want to mess up the process.
Hsjaai said:
What did you mean by that exactly?
Besides, sorry for bothering you, it's just that I'm genuinely curious and don't want to mess up the process.
Click to expand...
Click to collapse
With Magisk app
I'm still unsure about something. Will the custom ROM be installed without hassle if I unroot Magisk at the beginning (meanwhile leaving the custom recovery intact, of course)? No guide seems to deem having root installed as a prerequisite. If you answer that, I'm really embarking on the flashing process.
Hsjaai said:
I'm still unsure about something. Will the custom ROM be installed without hassle if I unroot Magisk at the beginning (meanwhile leaving the custom recovery intact, of course)? No guide seems to deem having root installed as a prerequisite. If you answer that, I'm really embarking on the flashing process.
Click to expand...
Click to collapse
Installing a custom rom (aosp or Miui) requires a data format (erases all data and creates a new partitions if necessary) which will remove root anyway, but sometimes root + twrp creates problems (can't mout the partitions) it is therefore to avoid this that I recommend you to unroot before.
In all cases (Aosp or custom Miui) magisk is installed last.
Which ROM do you want to install?
I'd like to install LineageOS first and see how compatible it is.
[ROM][UNOFFICIAL] LineageOS 17.1 for Redmi Note 9S
THERE IS AN OFFICIAL BUILD NOW, USE THAT INSTEAD! Note: this ROM is derived from LeddaZ's build. I will continue to update it until my 9s is on its last legs. Do not expect any features to be added. LineageOS is a free, community built...
forum.xda-developers.com
LineageOS With Android 11 For Redmi Note 9s/9 Pro/9 Pro Max/Poco M2 Pro (Miatoll) | The Custom Rom
November 20, 2021 Lineage OS 18.1 | OFFICIAL ~ Miatoll Android: 11 Build Date: 19.11.2021 Maintainer: @dereference
thecustomrom.com
The latter is relatively new, although I doubt that site would be credible.
Hsjaai said:
I'd like to install LineageOS first and see how compatible it is.
[ROM][UNOFFICIAL] LineageOS 17.1 for Redmi Note 9S
THERE IS AN OFFICIAL BUILD NOW, USE THAT INSTEAD! Note: this ROM is derived from LeddaZ's build. I will continue to update it until my 9s is on its last legs. Do not expect any features to be added. LineageOS is a free, community built...
forum.xda-developers.com
LineageOS With Android 11 For Redmi Note 9s/9 Pro/9 Pro Max/Poco M2 Pro (Miatoll) | The Custom Rom
November 20, 2021 Lineage OS 18.1 | OFFICIAL ~ Miatoll Android: 11 Build Date: 19.11.2021 Maintainer: @dereference
thecustomrom.com
The latter is relatively new, although I doubt that site would be credible.
Click to expand...
Click to collapse
Umm... I've taken my word back, they're XDA developers, not just some random dudes in the internet. Still, you can't be too careful.
Deleted
Hsjaai said:
Umm... I've taken my word back, they're XDA developers, not just some random dudes in the internet. Still, you can't be too careful.
Click to expand...
Click to collapse
Lineage 17 for Curtana
Lineage 18 for Miatoll
CherishOS https://sourceforge.net/projects/cherish-os/files/device/curtana/
More options than lineage.
NOSS8 said:
Lineage 17 for Curtana
Lineage 18 for Miatoll
CherishOS https://sourceforge.net/projects/cherish-os/files/device/curtana/
More options than lineage.
Click to expand...
Click to collapse
What device is Miatoll ?
Hello guys ! For some days or weeks, I see a new codename : Miatoll. I looked and search but I don't find what device is it. Can you helo me ? I wonder if I can flash my phone with a Miatoll Rom
forum.xda-developers.com
Miatoll ROMs are supposed to be compatible with Curtana if I haven't got something wrong... What's the deal with that?
I may consider flashing CherishOS instead, seems neat and the monthly updates appeal to me.
Hsjaai said:
What device is Miatoll ?
Hello guys ! For some days or weeks, I see a new codename : Miatoll. I looked and search but I don't find what device is it. Can you helo me ? I wonder if I can flash my phone with a Miatoll Rom
forum.xda-developers.com
Miatoll ROMs are supposed to be compatible with Curtana if I haven't got something wrong... What's the deal with that?
I may consider flashing CherishOS instead, seems neat and the monthly updates appeal to me.
Click to expand...
Click to collapse
Indeed it is the same.
Others great roms
https://sourceforge.net/projects/blissroms/files/R/miatoll/***
https://downloads.msmxtended.org/?dir=miatoll***
Don't flash magisk right away, check if the playstore is certified.
If not delele your google account and root with the Magisk app.
Of course, if you absolutely want to root your device for other reasons, ignore that.
***certified on redmi note 7
The installation of these should only differ (on a particular device) in the ROM that's being flashed az a zip, right?
For instance, see this guide. Could that be deemed to be applicable to any custom ROM?
https://www.getdroidtips.com/lineage-os-18-1-xiaomi-mi-a2-lite/
Hsjaai said:
The installation of these should only differ (on a particular device) in the ROM that's being flashed az a zip, right?
For instance, see this guide. Could that be deemed to be applicable to any custom ROM?
https://www.getdroidtips.com/lineage-os-18-1-xiaomi-mi-a2-lite/
Click to expand...
Click to collapse
Install the right TWRP
Be sure you have the right firmware.
If not flash it.
1)Twrp wipe format data write yes reboot twrp(if error reboot twrp and format again).
2)flash rom
3)reboot system
v11.0.4.0. QJWEUXM is a turkish rom(android 10)
V12.0.2.0.RJWMIXM is a global rom(android 11)Firmware base for AOSP
It is better to use Miflash and install TWrp after.(dont relock the bootloader).
Are you sure v11.0.4.0. QJWEUXM is the Turkish version? I thought it was EEA (the one tweaked for European countries). Installing the Global version seems alright, but why does the MIUI version has such a great effect on the outcome of the flashing?
Is that because both Cherish OS and the Global version are AOSP-based?
Hsjaai said:
Are you sure v11.0.4.0. QJWEUXM is the Turkish version? I thought it was EEA (the one tweaked for European countries). Installing the Global version seems alright, but why does the MIUI version has such a great effect on the outcome of the flashing?
Is that because both Cherish OS and the Global version are AOSP-based?
Click to expand...
Click to collapse
My bad EEA
AOSP use global firmware .RJWMIXM android 11
and sometime CN firmware.
https://xiaomifirmwareupdater.com/miui/curtana/

OnePlus 7T Pro with TWRP and Magisk

Hello, i've looked through many Forums and Threads but i couldn't find an answer.
The Problem: I have an OnePlus 7T Pro (Regular) (HD1910) running on OOS 11.0.6.1.HD01AA and i want to install TWRP Recovery with Magisk, but i dont have the necessary files and i maybe need a guide. The Guides i found where from 2021 and the Files i found where for OOS with Android 10. I want to stay on the Stock OS but as i said with TWRP and Magisk. Can someone help me?
PS: It's not the first time that im Rooting a Smartphone but i only have experience with Samsung and Huawei Devices.
Delorean12DMC said:
Hello, i've looked through many Forums and Threads but i couldn't find an answer.
The Problem: I have an OnePlus 7T Pro (Regular) (HD1910) running on OOS 11.0.6.1.HD01AA and i want to install TWRP Recovery with Magisk, but i dont have the necessary files and i maybe need a guide. The Guides i found where from 2021 and the Files i found where for OOS with Android 10. I want to stay on the Stock OS but as i said with TWRP and Magisk. Can someone help me?
PS: It's not the first time that im Rooting a Smartphone but i only have experience with Samsung and Huawei Devices.
Click to expand...
Click to collapse
1. Unlock phone
2. Flash TWRP(FBEv1 for oos) - https://twrp.me/oneplus/oneplus7tpro.html
3. Flash anything if you want
You want to also pass the safety net checks?
Timka-1 said:
You want to also pass the safety net checks?
Click to expand...
Click to collapse
If that is possible, yes.
Take a look at this guide. Perhaps it can help you too:
GitHub - poti1/oneplus7tpro
Contribute to poti1/oneplus7tpro development by creating an account on GitHub.
github.com

Categories

Resources