Database Develop

Lineage OS 04.04.17 wifi won't connect

Hello there
I finally completed installing Lineage OS to my Mi5 today, following all the official instructions on the Lineage os page.
Everything installed without error - however I can't connect to wifi!
When choosing the wifi network it says "Connecting" quickly followed by "Saved". Occasionally it will say "Authentication failed" or "Disabled".
I can't get it to connect to either 2.4ghz or 5ghz, and both of these were working fine in Miui Global stable rom.
Any insight would be wonderful.
Cheers!
Edit: solution down the thread.

Hi!
Have you tried to reflash rom?
Are you using stock LOS kernel ou another kernel?

Yes I did reflash the ROM once. I assume I'm using the default kernel, I haven't gone to any efforts to use another (I'm a noob )

Solution
Follow up - after much pulling out of hair and freaking out, this solution finally did the job:
https://forum.xda-developers.com/mi-5/help/wifi-connectivity-problem-t3517777/post70408866
All hail Pekkuky!
"This is what I did to fix my WiFi:
First prepare an new MAC-address. I personally don't know when a MAC-address is considered valid, so I just took one from an other device. I used the mac address of my previous mobile phone, which could connect to my router.
1. Disable WiFi.
3. Enable debugger settings (Setting>about Phone>Press build number repeatedly).
2. Enable root (Develepor settings>root access set to "Apps and ADB").
3. Open the file manager app.
4. Give the file manager app root access (menu>Settings(cog in lower left corner)>General settings>Access mode set this on "Root Access mode").
5. Now find the file root/etc/firmware/wlan/qca_cld/ and open wlan_mac.bin.
You should see something similar to:
Code:
Intf0MacAddress=XXXXXXXXXXXX
Intf1MacAddress=XXXXXXXXXXXX
END
6. Change the first to your new MAC-address, but first write down the old one, so you can change it back if this method doesn't work for you.
The last X of the next line should be a digit higher than the previous line. E.g:
Code:
Intf0MacAddress=957FDC328BF4
Intf1MacAddress=957FDC328BF5
END
(This MAC-address most likely won't work).
7. Save the file. You might need to press the save button a few times.
8. Check if the file has changed.
9. Check if you MAC-address has changed (Settings>WiFI>Configure-WIFI(cog in right upper corner)).
10. Enable WiFi.
I hope this works for everyone that has the same problem. "

LG Urbane 2 LTE (Nemo) TWRP , systemless root and APN editing BOOTLOADER unlocked

TWRP 3.0.2 and systemless supersu 2.79
You must unlock bootloader first
From bootloader menu
*- To permanently install
fastboot flash recovery (TWRP files name)
*- Running TWRP without installing
Fastboot boot (twrp files name)
download
TWRP 3.0.2 android M
TWRP 3.0.2 Android N (Android wear 2.0)
systemless Wear SU 2.79 from
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
To CHANGE (ADDING or EDITING) APN
edit or add apn on two files (APN-Name and value MUST MATCH between these two files)
The watch select and display APN selection based on MCC and MNC value that stored under the SIM card
(you can see the sim card value under telephony.db under siminfo data)
*- apns-conf.xml
/system/etc/apns-conf.xml
*- telephony.db
/data/data/com.android.providers.telephony/databases/telephony.db
You can push and pull these files from recovery menu main screen
1- Boot into TWRP
2- Mount System as RW (from mount menu)
3- connect the watch into computer and install ADB drivers.
4- Than run adb pull to get the files
Edit the files (by adding APN or edit existing carriers APN)
apns-conf.xml with any text or xml editor
telephony.db (under data and carriers) with Db browser for sqllite or any sql editor
APN name and data value on both files MUST BE THE SAME/MATCH otherwise the watch wont load the selection
5- ADB push to push the files back to the watch
6. Run shell command to change permission, ownership and group
apns-conf.xml - chmod 644 (rw r r), chown and chgrp root
telephony.db - chmod 660, chown and chgrp radio

Wanting to try this, but it isn't letting me mount /system. TWRP log says "Failed to mount '/system' (No such device)". The "Mount system RO" checkbox checks, but doesn't actually mount RO either.
I also looked for the telephony.db and it didn't exist at /data/data/com.android.providers.telephony/databases/telephony.db. The "databases" folder doesn't exist. Couldn't check for the one in /system
Running wear 2.0, so I DL'd the correct TWRP. I did boot-only, not flash.
Any ideas?

Concur.
Rayfen Windspear said:
Wanting to try this, but it isn't letting me mount /system. TWRP log says "Failed to mount '/system' (No such device)". The "Mount system RO" checkbox checks, but doesn't actually mount RO either.
I also looked for the telephony.db and it didn't exist at /data/data/com.android.providers.telephony/databases/telephony.db. The "databases" folder doesn't exist. Couldn't check for the one in /system
Running wear 2.0, so I DL'd the correct TWRP. I did boot-only, not flash.
Any ideas?
Click to expand...
Click to collapse
I have the same problem with TWRP and System RO. I did it in the same manner for booting from bootloader, because the flashing of recovery does not work correctly. I flash the TWRP using fastboot flash recovery, but every time I attempt to boot into recovery I get the same android icon with a red triangle over the top and an exclamation inside. I did not check the apn, because if I cannot go into recovery or flash SU I know that would be useless to even try. Same here device name nemo from bootloader screen using wear 2.0 (Android 7.1.1). Unlocked using fastboot oem unlock.

My Nexus 5 is rooted with custom Nougat ROM and it does NOT have the .db in the data directory. Given that they use a lot of the same AOSP code, it's probably safe to say that Wear 2.0 (nougat 7.1.1) doesn't need this here either. My conclusion then, is that they have consolidated these settings to the XML in the /system directory, which we cannot mount.
In the thread linked for the systemless su, it mentions that system is read only as it is squashfs. I can only assume that this applies to /system/etc/apns-conf.xml, so I'm not sure how OP was able to push the modified file back to /system in the first place without taking this into account.

Got it working with my FreedomPop SIM. Should work to add any APN. So I combined this with another guy's guide. There are two main differences.
First off, use twrp-3.1.1.0.img from this guy's thread. https://forum.xda-developers.com/lg-urbane-2/how-to/root-twrp-squashfs-3-1-1-lg-urbane-2nd-t3661569
Then it works to mount /system as READ ONLY, which allows you to use the systemless-su from this thread. WARNING: This may not modify the system, but it does modify and reflash another partition (I didn't catch which). I do not know if this will prevent your device from receiving OTAs afterward (It updates, see edit below). ALSO, because there isn't a SuperSU app, there is no management of what can use su privileges. Any app could discover root and do whatever without your knowledge. I plan to remove su from my watch when I get around to it now that my APN has been added. I will post how when I do.
EDIT: I just received an update through the Play Store that updated my AW version, build number, the works. Security patch August 1st. The APN I added persists after the update, though it showed the "no sim" icon until I went and manually enabled cell and selected the APN again.
After getting that done, follow these instructions for adding the APN starting from the header "Add the APN via the ADB shell". https://michaeltroger.github.io/blog/2017/08/12/add-apn-in-android-wear-2
Adding FreedomPop's data APN went as follows:
adb shell
su
content insert --uri content://telephony/carriers --bind name:s:"FreedomPop" --bind numeric:s:"310170" --bind type:s:"default,supl" --bind mcc:i:310 --bind mnc:i:170 --bind apn:s:"fp.com.attz"
If you happen to mess up, or have to add it with trial and error as I did, you can use the following two commands to fix things.
content query
content delete
Using the where clause as exampled in the above link.
NOTE: I just found out that as these changes are systemless, they DO NOT survive an unpair/reset.

Use this TWRP instead for Android wear 2
I modified from Android wear 2 stock recovery
TWRP 3.1.1
https://drive.google.com/open?id=0B4W0KuzRjVvGNkF1UnFkQkFBcU0
Systemless root
https://drive.google.com/open?id=0B4W0KuzRjVvGMzJka1dGRFM2dGc
Dont flash TWRP instead run fastboot boot (TWRP image name)
You wont be able to flash any OTA update with TWRP.
Your watch will keep rebooting to TWRP if you try to download and install any OTA.

Rayfen Windspear said:
Got it working with my FreedomPop SIM. Should work to add any APN. So I combined this with another guy's guide. There are two main differences.
First off, use twrp-3.1.1.0.img from this guy's thread. https://forum.xda-developers.com/lg-urbane-2/how-to/root-twrp-squashfs-3-1-1-lg-urbane-2nd-t3661569
Then it works to mount /system as READ ONLY, which allows you to use the systemless-su from this thread. WARNING: This may not modify the system, but it does modify and reflash another partition (I didn't catch which). I do not know if this will prevent your device from receiving OTAs afterward (It updates, see edit below). ALSO, because there isn't a SuperSU app, there is no management of what can use su privileges. Any app could discover root and do whatever without your knowledge. I plan to remove su from my watch when I get around to it now that my APN has been added. I will post how when I do.
EDIT: I just received an update through the Play Store that updated my AW version, build number, the works. Security patch August 1st. The APN I added persists after the update, though it showed the "no sim" icon until I went and manually enabled cell and selected the APN again.
After getting that done, follow these instructions for adding the APN starting from the header "Add the APN via the ADB shell". https://michaeltroger.github.io/blog/2017/08/12/add-apn-in-android-wear-2
Adding FreedomPop's data APN went as follows:
adb shell
su
content insert --uri content://telephony/carriers --bind name:s:"FreedomPop" --bind numeric:s:"310170" --bind type:s:"default,supl" --bind mcc:i:310 --bind mnc:i:170 --bind apn:s:"fp.com.attz"
If you happen to mess up, or have to add it with trial and error as I did, you can use the following two commands to fix things.
content query
content delete
Using the where clause as exampled in the above link.
NOTE: I just found out that as these changes are systemless, they DO NOT survive an unpair/reset.
Click to expand...
Click to collapse
Is Safetynet working after removing root? I presume you can still sideload updates or that there is a method to return to stock if SafetyNet is tripped?

sjavvaji said:
Is Safetynet working after removing root?
Click to expand...
Click to collapse
I never got around to forcefully disabling/removing it. Nor have I gotten around to redoing it after unpaid/reset wiped it all. How would I test that? I'll get it back on and working then remove root this time sometime this week and give it a go. I don't use Android pay, so I'm not sure how I would test it. Perhaps I could adb push one of the checker apps for phone and hope it works?

Rayfen Windspear said:
I never got around to forcefully disabling/removing it. Nor have I gotten around to redoing it after unpaid/reset wiped it all. How would I test that? I'll get it back on and working then remove root this time sometime this week and give it a go. I don't use Android pay, so I'm not sure how I would test it. Perhaps I could adb push one of the checker apps for phone and hope it works?
Click to expand...
Click to collapse
That would be one way to do it. I have my watch coming in tomorrow and a Freedompop sim on the way. I would prefer Android Pay working over data but having both working is optimal.

sjavvaji said:
That would be one way to do it. I have my watch coming in tomorrow and a Freedompop sim on the way. I would prefer Android Pay working over data but having both working is optimal.
Click to expand...
Click to collapse
Just getting around to tinkering today. Did a bit of research and found that installing the systemless SU modifies the kernel. I'm going to dig a little deeper and hopefully come up with a zip to flash that will completely undo everything that is done by the SU zip (if there isn't one already) to make sure that safetynet not only passes, but that the kernel is stock and secure too. The recent update they pushed for Aug security patch possibly updated the kernel too, yet the APN survived, so once set, APNs definitely live in the userdata and should be fine.

Rayfen Windspear said:
Just getting around to tinkering today. Did a bit of research and found that installing the systemless SU modifies the kernel. I'm going to dig a little deeper and hopefully come up with a zip to flash that will completely undo everything that is done by the SU zip (if there isn't one already) to make sure that safetynet not only passes, but that the kernel is stock and secure too. The recent update they pushed for Aug security patch possibly updated the kernel too, yet the APN survived, so once set, APNs definitely live in the userdata and should be fine.
Click to expand...
Click to collapse
Let me know how it goes! I would honestly just like to get the APN working and return to stock. So assuming it works, the process would go, unlock bootloader, run TWRP w/o install, install systemless SU, edit APN, run TWRP w/o install, uninstall systemless SU, and bootloader relock. Am I missing anything?

sjavvaji said:
Let me know how it goes! I would honestly just like to get the APN working and return to stock. So assuming it works, the process would go, unlock bootloader, run TWRP w/o install, install systemless SU, edit APN, run TWRP w/o install, uninstall systemless SU, and bootloader relock. Am I missing anything?
Click to expand...
Click to collapse
Ooooh... does SafetyNet check for an unlocked bootloader? Does relocking it force a data wipe? I can't remember, because once I unlock, I've never gone back

Rayfen Windspear said:
Ooooh... does SafetyNet check for an unlocked bootloader? Does relocking it force a data wipe? I can't remember, because once I unlock, I've never gone back
Click to expand...
Click to collapse
Yeah. I forgot it required a data wipe. That might be an issue lol.

So is there a way to install Magisk? Or any way to bypass the SafetyNet check and a way to reverse the systemless SU check?
Edit:
I did some more research and it seems like we might be able to install Magisk in place if the systemless root uses SuperSU. Other LG watches in the past and android wear devices in general have been rooted using Magisk in place of SuperSU and it seems to pass safetynet.

hoodred said:
TWRP 3.0.2 and systemless supersu 2.79
You must unlock bootloader first
From bootloader menu
*- To permanently install
fastboot flash recovery (TWRP files name)
*- Running TWRP without installing
Fastboot boot (twrp files name)
download
TWRP 3.0.2 android M
TWRP 3.0.2 Android N (Android wear 2.0)
systemless Wear SU 2.79 from
https://forum.xda-developers.com/apps/supersu/android-wear-6-0-1-root-squashfs-t3319097
To CHANGE (ADDING or EDITING) APN
edit or add apn on two files (APN-Name and value MUST MATCH between these two files)
The watch select and display APN selection based on MCC and MNC value that stored under the SIM card
(you can see the sim card value under telephony.db under siminfo data)
*- apns-conf.xml
/system/etc/apns-conf.xml
*- telephony.db
/data/data/com.android.providers.telephony/databases/telephony.db
You can push and pull these files from recovery menu main screen
1- Boot into TWRP
2- Mount System as RW (from mount menu)
3- connect the watch into computer and install ADB drivers.
4- Than run adb pull to get the files
Edit the files (by adding APN or edit existing carriers APN)
apns-conf.xml with any text or xml editor
telephony.db (under data and carriers) with Db browser for sqllite or any sql editor
APN name and data value on both files MUST BE THE SAME/MATCH otherwise the watch wont load the selection
5- ADB push to push the files back to the watch
6. Run shell command to change permission, ownership and group
apns-conf.xml - chmod 644 (rw r r), chown and chgrp root
telephony.db - chmod 660, chown and chgrp radio
Click to expand...
Click to collapse
Is there a way to flash back to stock AW 1.5?
Sent from my SM-G965U using Tapatalk

The exact framework for note 4 marshmallows

Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.

Hgt45 said:
Hello, i had read many things at the forum but i still very confused. .please in a simple answer, which one is the correct and the download link. .please i can damage my cel.
Click to expand...
Click to collapse
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?

Rom said:
Hello,
first i am not sure that u are in the right forum section.
About your demand, you haven't mention the CPU arch of your phone and have you reboot in custom recovery to flash the downloaded zip ?
Click to expand...
Click to collapse
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.

Hgt45 said:
Hello Lyon, hope everything happy... well, i don't know if its the right fórum,, here the info:
SYSTEM: SDK versión 6.0.1 ID:MMB29M OS name: Linux OS versión:3.10.40-9120850 Dalvik VM versión: 2.1.0
DEVICE: Model: SM-N910P Product: trltespr Board:APQ8084 Brand: Samsung Fingerprint: Samsung/trltespr/trltespr:6.0.1/MMB29M/N910PVPS4DQD1:user/reléase-keys
CPU: Name: ? Current freq.: 1958.4MHz Max freq.: 2649.6MHz Min freq.: 300MHz Cores: 4
Architecture: 7 BogoMIPS:38.40 Hardware: Qualcomm APQ8084 Revisión: 1
Serial #:0000000000000000
Memory
Total:2845492kbB Free:97792kB Inactive:896648kB
I haven't reboot in custom recovery to flash the downloaded zip XposedInstaller_by_dvdandroid.apk because of the warning its shows ( i send the pictures ).. i don't want to damage my note 4.. its the righ one ?
If you or anyone can help me to easy way to do it..
1- is,, XposedInstaller_by_dvdandroid.apk ? safe to run in custon recovery ? i Yes, how to, if No, which one to download it.
Regards.
H.
Click to expand...
Click to collapse
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.

Rom said:
I don't see your CPU arch in your details, you are in the wrong forum section and on Android 5.0+ you must flash your zip in custom recovery.
Click to expand...
Click to collapse
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.

Hgt45 said:
Thank you ROM,,for answer me, sorry I'm not an experienced tech... . and I'm afraid to flash zip in custom recovery mode if is not the right one,, in other words, I haven't did before, I just install framework in my S4 with no problems before. ..
I find out CPU arch: ARMv7-A Qualcomm APQ8084 ,,etc,, see attachment.
Please could you please tell me and help me ?....
If someone move these Thread to the right place. .
Sorry if I'm bothering
Regards
H.
Click to expand...
Click to collapse
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.

Rom said:
Hello,
Apparently your CPU is an arm32 bits processor, so dl the last zip from this page:
http://dl-xda.xposed.info/framework/sdk23/arm/
And flash it via custom recovery.
After flash the zip, reboot in classic mode and check again by opening XPosed Installer app.
Click to expand...
Click to collapse
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.

Hgt45 said:
Hello Rom, wishing your are very happy...
look the picture and see what is happening..
Overall Status: Congratulations! This device has root access!
Feedback
Stage 1 - Superuser App: Installed
Installed: SuperSU by Chainfire - version 2.82
Stage 2 - Superuser Binary Files: Installed
Standard System-less Location
Command: ls -l /su/bin/su
Result: -rwxr-xr-x root root 75352 2017-09-22 16:39 su
Version: 2.82:SUPERSU
Analysis: Root access IS correctly configured for this file! Executing this file can grant root access! Root user ownership is present and setuid attribute is not present.
Standard System Location
Command: ls -l /system/bin/su
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard System Location
Command: ls -l /system/xbin/su
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Command: ls -l /sbin/su
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Command: ls -l /system/sbin/su
Result: /system/sbin/su: No such file or directory
Analysis: File /system/sbin/su does not exist.
Alternative Location
Command: ls -l /system/xbin/sudo
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Alternative Location
Command: ls -l /magisk/.core/bin/su
Result: /magisk/.core/bin/su: No such file or directory
Analysis: File /magisk/.core/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /vendor/bin/su
Result: /vendor/bin/su: No such file or directory
Analysis: File /vendor/bin/su does not exist.
Alternative System Environment Location
Command: ls -l /su/xbin/su
Result: /su/xbin/su: No such file or directory
Analysis: File /su/xbin/su does not exist.
Stage 3 - Root User Account: Success
Root user id: uid=0(root)
Root group id: gid=0(root) groups=0(root)
Root SELinux context: context=u:r:init:s0
Optional - ADB Shell User
Status: Non-Root Shell User
Setting stored in /default.prop and configured as: ro.secure=1
Additional - Google SafetyNet Status
SafetyNet Status: False
Google evaluates hardware and software against Android specifications
Additional - System Environment PATH
System Environment PATH: /su/bin /sbin /vendor/bin /system/sbin /system/bin /su/xbin /system/xbin
Results provided for your SM-N910P - Android 6.0.1 device by Root Checker Pro version 6.1.5 from joeykrim in Google Play - http://goo.gl/NcnHn
thanks..
h.
Click to expand...
Click to collapse
Hello,, any sugestion. ?
Have a great day.
H.

: (
Sent from my SM-N910P using Xposed Modules

Hgt45 said:
: (
Sent from my SM-N910P using Xposed Modules
Click to expand...
Click to collapse
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk

samep said:
Read fully, gather resources, install prerequisites on PC and study before proceeding AND only with confidence, considering all risks. Steps are generally in order but start with verifying reactivation lock is not enabled at Settings/Security while phone is booted.
I'd also recommend that you begin with fingerprints removed and no encryption. Make backups frequently in TWRP recovery beginning with suggested stock backup on ext sdcard as explained along the way.
Note: remember, before making any backups that fingerprints should be removed. Fingerprints do not restore from custom backups and don't work as expected even restored in a backup. Problematic!
Steps may contain redundant reminders and links because I've reiterated important things more than once.
Begin here when prerequisites, explained, are installed and gathered. The SuperSU zip and Wanam unofficial Xposed can be downloaded to phone's internal memory or retained for safe keeping on your micro sdcard. Just remember where downloaded to find when flashing in recovery. Always verify md5 of zips before extracting or flashing (as applies) where available. Sanity check to be safe.
USB driver will be installed on PC as executable; Odin will be extracted to Odin folder; your user files are good location to place this folder with extracted files; the exe file is an Odin application launcher executable with dependencies. The TWRP img.tar file will be downloaded to PC to install with Odin as explained along the way.
You can use the 3.1.1 Xposed Installer apk but your Xposed framework is going to be an unofficial one from Wanam for touchwiz lollipop and marshmallow.
Wanam also has an Xposed module suggested for touchwiz marshmallow: XTouchWiz (found with download search in Xposed Installer application when successful in installing all that I've given guidance for) . You might try that one first for SM-N910P; (other likened Xposed modification modules may not be as compatible as this Wanam module-- not too be confused with Wanam unofficial framework zip for recovery flashing to install Xposed framework). Note the differences.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
The file you'll eventually find is Wanam unofficial Xposed framework for SDK 23 arm.
https://www.androidfilehost.com/?fid=529152257862685344
I don't believe you're rooted. It also appears you're trying to flash custom zips with stock recovery? Are you familiar with TWRP recovery by Team Win? You'll need that to backup your ROM and flash custom zips like SuperSU zip and unofficial Xposed framework by Wanam. (Bootloader is already unlocked on SM-N910P; please make sure that is your model number because that's what I'm recommending files for).
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
The file above is latest custom recovery for SM-N910P or any Qualcomm Note 4. Recently, the TWRP recovery became unified by processor but common mistakes users of Qualcomm Note 4 make is not knowing which to flash and what's required for Odin install and how to properly flash in Odin. What's Odin? It's a utility made for flashing custom tar files and stock tar updates for rooted users. There are many updates and untrusted sources (beware of adware or malware!) but basically it's installed on a PC as an executable file. But you'll also need the official USB driver to help the PC discover your phone when placed in download mode to flashed with Odin. What will you flash? The tar.img file above.
To get started download USB driver and Odin. Install USB on PC with its exe file.
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
Latest Odin trusted download is below. Unzip or extract contents in a folder named Odin
https://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
If you have Samsung Smart Switch or Samsung KIES installed on PC, you need to ensure all process and apps sessions are closed before using Odin. Also note that launching Odin exe on Windows 8 and below requires to launch with administrative permission (right click the executable file and select launch with administrative permission). Windows 10 does not require administrative mode at launch.
Are you familiar with launching download mode? Power Off, pull battery after charging to at least 80% (general rules for flashing in Odin download mode- never use a "boot to download mode" shortcut from system booted state; actually, that necessity applies to flashing full stock tar but remember that; make it a practice is my suggestion to avoid catheter csc errors with full stock tar flashes with Odin-- that's how rooted users update). Reinstall battery and press hold volume down, home and power button until it vibrates or launches. Read the prompt on phone* this is important because flashes are always a risk. Launch Odin on PC and goto options tab and uncheck auto restart and return to to log tab. While watching "COM" field with USB cable connected (must be data USB type cable- original Samsung Note 4 is recommended), follow prompt* I believe it's volume up to continue. Read your phone's state and see that COM field populated with your device (likely a port or device number unique to your PC where phone USB cable is connected or your phone* it only populates when you accept/commit download mode with phone and PC connected via USB with data support). Do not proceed until verifying your phone display shows Odin fast mode and that reactivation lock is disabled or inactive. If that is a go, load the img.tar in AP slot. You still see the file name fill that slot when you navigate to it on your PC and select it. The install button will be at bottom of Odin screen, I believe. Begin when all is verified.
If all above is a go, just remember that you're looking for a green field that fills and says SUCCESS! Happens quickly and stops (if you setup as directed). Wait until you see Odin log file state that "1 passed, 0 failed". Give it a minute to declare "disconnected" or just wait one minute before proceeding. Since auto reboot was unchecked, you'll have to remove USB and pull battery manually (wait at least 30 seconds after pulling battery before reinstalling). And close Odin after each flash session; you're actually done with the PC for this directive. IMPORTANT: If you fail to go directly to recovery mode after reinstalling the battery, stock recovery will restore itself and you'll have to do the Odin flash of TWRP again. To do this, press and hold volume up, home and power simultaneously until it vibrates; TWRP recovery should launch. You're now ready to backup your stock un-rooted ROM. I recommend backing up to ext SD Card (micro sdcard).
To familiar yourself with TWRP install and use, there's a support thread for that. There's also an official TWRP recovery application in Google Play. Search it there. Note the thread hasn't reflected latest update or developer notes since the official TWRP recovery app launched in Google Play but many unique questions are answered there. Ignore any suggestions to use an older TWRP version or any specific update or Android version. Suggestions like this change over time and may not be relevant at present.
https://forum.xda-developers.com/no...ility-twrp-2-8-1-0-teamwin-t2915591?nocache=1
After backup, I'd recommend installing SuperSU zip with TWRP recovery.
https://forum.xda-developers.com/showpost.php?p=68475511&postcount=1
Make a rooted TWRP backup before applying Xposed and label accordingly, saving to ext sdcard. You can edit the generalized title of backup as you prefer. Rather than the extended fine stamp, shorten to include your description.
Then you can install the Xposed Installer apk (install by sideload method not recovery- you may have already done this) and Wanam unofficial Xposed zip. Follow this thread; I've already linked the zip above but usually you're looking for the highlighted download link and browse to marshmallow SDK 23 arm.
https://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
All threads referenced are your support threads for files referenced. Understand before flashing that there risks you assume yourself. Never a guarantee that you'll be successful or the inevitable happens from followed instructions offered by me or anyone else I've linked you to.
Again, make sure you haven't set reactivation lock in phone's Settings/Security tab before beginning and verify the phone display and Odin states before flashing. Not following could result in phone activating a factory reset protection mode. Not sharing to warning while flashing TWRP recovery may only refuse to flash due to reactivation lock enabled and may state such when using recent Odin releases. But that message may be only abbreviated and cause question of its intent.
Only flash when familiar and confident with instructions. Better to ask than risk misunderstood direction. There may recent demo videos to follow but avoid using suggested older files, noting date of your video; they're not necessarily scripture to live by. Best to use recent files and direction because unlike a certain BOOK, updates and time changes with Samsung, touchwiz and Note 4 development.
There's also some custom ROMs to consider if you follow the road map of XDA links for Sprint Note 4 at top of thread: Note 4 development, rather than Note 4 original development where TWRP support thread. Updates for TWRP can be found in the official TWRP recovery app but I've linked you latest recommended release for flashing in Odin.
Questions? Ask away or read the support threads to familiarize yourself. Many questions are answered there.
Sent from my SM-N920P using Tapatalk
---------- Post added at 10:28 PM ---------- Previous post was at 09:59 PM ----------
Final result on my SM-N910P Note 4. See screenshots.
I'm using a couple of non Xposed modules to compliment modification outside of Xposed. Since compatible modules and applications are sometimes limited, I'll include those for clarification. Both linked below by Google Play link. Strictly optional. Both contain back to kill foreground app shortcuts but may be premium only features- I'm not sure on both or whether one or the other would be ideal. I sort of discovered these apps by recommendation and haven't tried eliminating one or the other.
https://play.google.com/store/apps/details?id=flar2.homebutton
https://play.google.com/store/apps/details?id=com.goodmooddroid.gesturecontrol
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Hello Samep, I'm impressed and thankful on how you describe everything, I know its takes lon time and dedication to write,, THANKS A LOT, I know these will be the most comprehensive for many many users... I will try to do what you explained. ..
Also thanks to Rom and others for your suggestions and help.
Have a great weekend.. all the best wishes for all.
Regards
Herm.

slm note 4
note 4 I am using n910c 6.0.1. I have installed the device rooted twrp but I do not know which xposed i will install. I write armv7l in the kernel.
I do not know how many sdk I have to help you rejoice

[MODULE] Debugging modules: ADB Root, SELinux Permissive, Enable Eng

These modules are not meant for everyday use. They are intended for debugging and modification of a firmware. They significantly lower security of your device while active and even could softbrick it. You've been warned.
ADB Root
Magisk Module that allows you to run "adb root". adb root is not an ordinary root (su), it's adbd daemon running on your phone with root rights. adb root allows you to "adb push/pull" to system directories and run such commands as "adb remount" or "adb disable-verify".
Download v1.0: https://github.com/evdenis/adb_root/releases/download/v1.0/adb_root.zip
Source code: https://github.com/evdenis/adb_root
Support: Telegram
SELinux Permissive
This module switches SELinux to permissive mode during boot process. This module intentionally lowers security settings of your phone. Please don't use it if there is a better solution to your problem, e.g., magiskpolicy. The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels.
Download v2.0: https://github.com/evdenis/selinux_permissive/releases/download/v2.0/selinux_permissive_v2.0.zip
Source code: https://github.com/evdenis/selinux_permissive
Support: Telegram
Enable Eng
This Magisk Module enables engineering build props. It allows to activate debugging parts of a firmware. Please, disable Magisk Hide for this module. If you don't know what you are doing, don't use this module. It can easily softbrick your device.
Troubleshooting
If your device doesn't boot then you need to reboot to TWRP recovery and
Code:
$ adb shell rm -fr /data/adb/modules/enable_eng
If ADB doesn't work that means adbd in your firmware is build without ALLOW_ADBD_ROOT. You can fix adb autostart either by installing "ADB Root" magisk module or by disabling this module.
Download v1.0: https://github.com/evdenis/enable_eng/releases/download/v1.0/enable_eng.zip
Source code: https://github.com/evdenis/enable_eng
Support: Telegram
Kexec tools for Android
This module adds statically linked kexec binary to your system. Aarch64 only. Kexec is a system call that enables you to load and boot into another kernel from the currently running kernel. Your kernel should support kexec.
Download v1.0: https://github.com/evdenis/kexec/releases/download/v1.0/kexec.zip
Source code: https://github.com/evdenis/kexec
Support: Telegram
GDISK/Parted for Android
The module adds statically linked parted/sfdisk/fdisk/gdisk binaries to your system. Aarch64 only. These utils are standard linux tools to edit the partitions tables on disks.
Download v2.0: https://github.com/evdenis/disk/releases/download/v2.0/disk-v2.0.zip
Source code: https://github.com/evdenis/disk
Support: Telegram

Is also valid for One Plus 5 ?
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

tmviet said:
Is also valid for One Plus 5 ?
Click to expand...
Click to collapse
Hi, these magisk modules are device independent. Yes, you can use them on One Plus 5.

evdenis said:
Hi, these magisk modules are device independent. Yes, you can use them on One Plus 5.
Click to expand...
Click to collapse
Tks. A lot [emoji6]
Inviato dal mio ONEPLUS A5000 utilizzando Tapatalk

Thanks @evdenis, this module is great! I haven't gotten the 100% desired behavior (getting adbd with actual root perms) because I'm running a 32-bit architecture (armeabi-v7a) and you've supplied only the 64-bit version of adbd, but I've been using your module to swap out 32-bit versions of different versions of adbd I have lying around (older devices). I'm a n00b when it comes to building adbd from scratch using the latest sources with your patch so I'm planning on using the adbd that came with the device and using a disassembler and a hexeditor to NOP out some calls, such as the call to minijail_enter() and see if I have any success. The original device version of adbd doesn't seem to have the functions in it that you built with the patch, but instead appears to use a bunch of minijail library functions. The device is a rooted android 8.1.0 OS, but it is only rooted systemlessly so many of the ro.* build properties affecting adb are changed well after the OS-essential portion boots rendering my efforts thus-far using the original adbd ineffective I'm guessing. I can now issue the "adb root" command from my machine, but adbd on the device is always being launched with the following command line arg "--root_seclabel=u:r:su:s0" and never gains root permissions by default (the behavior I'm trying to achieve). I can manually use "su" but this doesn't help me with push/pull requests to protected parts of the OS and chainfire's "ADB Insecure" patches adbd successfully, but I still don't get the root perms.
Do you know if the system is starting the process with reduced permissions (i.e. adbd will never be able to gain root access on its own no matter what I modify) and I should go a different route like modifying something else in the system rather than adbd? Again, I've already modified the ro.* properties affecting adbd so it does attempt to re-launch itself as root, it just doesn't end up getting the root perms. Manually launching adbd after killing it from within a shell on the device doesn't seem to affect the permissions in ultimately gets.
If you are anyone has any insight as to what I need to do so that adbd gains root permission, that would be much appreciated.

bpaxda said:
I'm planning on using the adbd that came with the device and using a disassembler and a hexeditor to NOP out some calls, such as the call to minijail_enter() and see if I have any success.
Click to expand...
Click to collapse
It was my initial attempt to gain "adb root" on samsung s10. And noping a couple of calls is not enough on the phone. adbd binary on your device could be compiled without "adb root" branch. This is the case on samsung s10. If "adb root" branch exists one need to force should_drop_privileges() function to return false (https://android.googlesource.com/platform/system/core/+/refs/heads/master/adb/daemon/main.cpp#65) in order to get into the "adb root" branch of code (https://android.googlesource.com/platform/system/core/+/refs/heads/master/adb/daemon/main.cpp#151).
bpaxda said:
ro.* build properties affecting adb are changed well after the OS-essential portion boots rendering my efforts thus-far using the original adbd ineffective I'm guessing.
Click to expand...
Click to collapse
You could try enable_eng magisk module (https://github.com/evdenis/enable_eng). The module changes ro.* props to engineering build props. Depending on a firmware this could help to get "adb root". However, no guaranties that the module will not softbrick your device. In case of softbrick you will need to reboot to TWRP and delete the module, instruction is in the README.md.
bpaxda said:
I can now issue the "adb root" command from my machine, but adbd on the device is always being launched with the following command line arg "--root_seclabel=u:r:su:s0" and never gains root permissions by default (the behavior I'm trying to achieve).
Click to expand...
Click to collapse
Try to disable SELinux either with the magisk module or with a script.

Thanks for your response.
I think you're right. Despite having adjusted the ro properties post-boot, there was nothing in ADB that would change the privileges as if it has been compiled out. By sheer luck, I managed to grab adbd from an identical device that had a recent forced firmware update, but the "improved adbd" actually let me get closer. The updated adbd had code changes to its adbd_main function so that it at least looks at the properties "ro.secure" and "service.adb.root" not to mention new calls to minijail_capbset_drop(), minijail_change_gid() and minijail_change_uid(). Using magisk to dynamically replace my original adbd binary with this updated one actually worked in getting adbd to start root shells without needing to invoke "su"!
However its a weird type of root that can't read certain files like /verity_key but I can see some things I should be able to see as root. I'm no SELinux expert, but my guess is that if everything is functioning correctly, I may be getting an SELinux "restricted" root. In this case, it might be the most I can expect from an SELinux enabled kernel launching adbd as root. Let me explain: since I'm using Magisk, post-boot systemlessly, (the system boots restricted and then I use the mtk_su exploit, to gain root and disable permissive SELinux mode), I'm getting permissive root on a session by session basis. I think the nature of this type of root means the kernel is probably still locked down and thus whatever daemon may be responsible for launching adbd remains locked down. Does this sound correct to you? If so, I can live with that
I'd love to get TWRP on this device, but I'm not sure its possible since TWRP doesn't list my device as supported on their website nor can I get into fastboot mode (I didn't try that hard because I wanted to exhaust other options before flashing anything). Do you think enable_eng would work *after* the ACTION_BOOT_COMPLETE event is processed? I.e. my device is rooted after bootup by a script which runs the exploit, but it is well after the system is fully running and locked-down. Luckily Magisk has a utility to change ro properties, but some of those properties are not looked-at by the system this late in the boot stage. Do you think in this case "enable_eng" would work for me? Thanks again!

bpaxda said:
Let me explain: since I'm using Magisk, post-boot systemlessly, (the system boots restricted and then I use the mtk_su exploit, to gain root and disable permissive SELinux mode), I'm getting permissive root on a session by session basis.
Click to expand...
Click to collapse
I'm not sure that my modules will work with this rooting scenario. As far as I could understand, magisk by default replaces the init process, patches selinux policy before it is loaded and next, calls the original init binary. I don't think that it will be possible to alter selinux policy with different boot scenario for magisk.
bpaxda said:
Do you think enable_eng would work *after* the ACTION_BOOT_COMPLETE event is processed? I.e. my device is rooted after bootup by a script which runs the exploit, but it is well after the system is fully running and locked-down. Luckily Magisk has a utility to change ro properties, but some of those properties are not looked-at by the system this late in the boot stage. Do you think in this case "enable_eng" would work for me?
Click to expand...
Click to collapse
I'm not sure that enable_eng will work. adbd daemon check some properties such as ro.secure dynamically, but they could be cached after the boot. I don't know the ways to drop the cache and re-read these properties (altered with magisk) after the boot. Here are the main properties the modules changes https://github.com/evdenis/enable_eng/blob/master/system.prop

Thanks for making this tool! I'm just wondering if I need to modify my adb to use the module - I run "adb root" normally and get "adbd cannot run as root in production builds" still

Anyone know why when i install SELinux Permissive version 2.0 of the module it still states version 1 in Magisk?

I flashed this in Magisk and rebooted. Now my phone is stuck in a boot loop. Any ideas? I'm using Sony Xperia XZ1 compact.

cheeklitched said:
I flashed this in Magisk and rebooted. Now my phone is stuck in a boot loop. Any ideas? I'm using Sony Xperia XZ1 compact.
Click to expand...
Click to collapse
If you have twrp installed just uninstall and reinstall magisk.
Otherwise,
Boot to bootloader and flash your boot.img file
Code:
fastboot flash boot boot.img
Then let phone boot. Reboot to bootloader again. Flash magisk_patched.img
Code:
fastboot flash boot magisk_patched.img
During startup, as soon as you get to the Google logo, hold the volume button down. This should start the phone in safe mode. See if it loads. If not, reboot phone, and execute this in terminal/command prompt:
Code:
adb wait-for-device shell magisk --remove-modules
This should allow the phone to start up all the way. Enable whatever modules you want. You may need to flash magisk_patched.img again.
This has fixed multiple problems for me. It's redundant, but it tends to work.

I installed the Magisk selinux script, but after installing it no longer shows in Magisk, so how do I dissable/undo/uninstall the script? I installed a Selinux checker and it says it is on permissive, so the scrip must have installed, but I want to remove it. Is there an undo script, or can I manually delete the script in my root filesystem? THX

Hello guys
I used Redmi K20 pro with Eu rom 10.4, android 10.
I used the lastest version of this module but my devices was not found on ADB system on my computer.
So what I do now? I tried to fix it but I cannot find anything about it.

Recently, setting SElinux to permissive is not advised. I had a issue with V4A setting my SElinux to permissive permenantly, but editing the magisk module to set SElinux to enforcing instead of permissive also works.
This is probs the only module that actually sets SElinux properly.
Here's the modded magisk module with the same credited creator, but just sets SElinux to Enforcing instead of permissive

OMFG I THINK THIS IS WHAT IVE BEEN LOOKING FOR. TEH HOLY GRAILLLLL OMGOMGOMG THANK YOU THANK YOU THANK YOUUUUU

Will ADB Root work for Android 8.1?

evdenis said:
These modules are not meant for everyday use. They are intended for debugging and modification of a firmware. They significantly lower security of your device while active and even could softbrick it. You've been warned.
ADB Root
Magisk Module that allows you to run "adb root". adb root is not an ordinary root (su), it's adbd daemon running on your phone with root rights. adb root allows you to "adb push/pull" to system directories and run such commands as "adb remount" or "adb disable-verify".
Download v1.0: https://github.com/evdenis/adb_root/releases/download/v1.0/adb_root.zip
Source code: https://github.com/evdenis/adb_root
Support: Telegram
SELinux Permissive
This module switches SELinux to permissive mode during boot process. This module intentionally lowers security settings of your phone. Please don't use it if there is a better solution to your problem, e.g., magiskpolicy. The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels.
Download v2.0: https://github.com/evdenis/selinux_permissive/releases/download/v2.0/selinux_permissive_v2.0.zip
Source code: https://github.com/evdenis/selinux_permissive
Support: Telegram
Enable Eng
This Magisk Module enables engineering build props. It allows to activate debugging parts of a firmware. Please, disable Magisk Hide for this module. If you don't know what you are doing, don't use this module. It can easily softbrick your device.
Troubleshooting
If your device doesn't boot then you need to reboot to TWRP recovery and
Code:
$ adb shell rm -fr /data/adb/modules/enable_eng
If ADB doesn't work that means adbd in your firmware is build without ALLOW_ADBD_ROOT. You can fix adb autostart either by installing "ADB Root" magisk module or by disabling this module.
Download v1.0: https://github.com/evdenis/enable_eng/releases/download/v1.0/enable_eng.zip
Source code: https://github.com/evdenis/enable_eng
Support: Telegram
Kexec tools for Android
This module adds statically linked kexec binary to your system. Aarch64 only. Kexec is a system call that enables you to load and boot into another kernel from the currently running kernel. Your kernel should support kexec.
Download v1.0: https://github.com/evdenis/kexec/releases/download/v1.0/kexec.zip
Source code: https://github.com/evdenis/kexec
Support: Telegram
GDISK/Parted for Android
The module adds statically linked parted/sfdisk/fdisk/gdisk binaries to your system. Aarch64 only. These utils are standard linux tools to edit the partitions tables on disks.
Download v2.0: https://github.com/evdenis/disk/releases/download/v2.0/disk-v2.0.zip
Source code: https://github.com/evdenis/disk
Support: Telegram
Click to expand...
Click to collapse
how can i make permissive enfocing because in 2022 i heard thats a BIG security risk and my custom ROM (havoc os) if selinux permissive

Phone permission needed to take calls.

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