Root access problems on Cyanogenmod 13 - ZenFone 2 Q&A, Help & Troubleshooting

Hello to all (i have no idea if i am posting this in the right place sorry)
I have recently installed Cyanogenmod 13 on my Asus Zenfone 2 Laser/Selfie (1080p) (Asus-Z00T)
My phone works grate besides the fact that i have root access problems.
First i enabled developer options then enabled root (as now since Cyanogenmod 12 it is hidden) i installed busybox i grant it root access .So far so good nothing unusual i then install clean master then give it root access then when i try to use clean master to stop apps auto starting and i got an error no root access i then installed lucky patcher granted it root access no problem then when i tried patching a app to remove adds i got another root access error.
(I have had problems like this on Cyanogenmod 12)
Now with Cyanogenmod 11 if i get a little root bug i just go to super user app under system settings and delete the app access and then give it new root access again that solves the problem.
IT would seam that since CM12/CM13 there is no superuser app on board and no superuser settings either i have looked everywhere and i just can't find it.
I have the feeling that now root has become just a developer option it is not as good as on Cyanogenmod 11 but i could be wrong.
Could anyone help me please ?? is there a way to fix root access errors ???

The supersu type settings are in settings /privacy/privacy guard
Sent from my ASUS_Z00A using Tapatalk

Try re-rooting your device, in the worst case, flash stock rom, then flash cyanaogenmod and then root your device.
Hope this solves your problem.

Related

[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)

[Q] Root "disabled" itself!? (Rooted phone that is no longer allowing root access)
Anyone here with this phone (or any) - that is rooted - have it just seemingly act as if it is no longer rooted? or unjustly denying root access for no apparent reason....
Have been rooted since purchase and have never seen or had any issue with this..have flashed custom recovery and rom's hundreds of times...no problems...currently using Task's latest KK 4.4.4 rom and had no issues from beginning...
It comes with SuperUser...i do usually install SuperSU instead but hadn't tried yet...it was fine and apps that needed root appeared ok..even SuperUser has three or four listed apps in the "allow" section...but all of a sudden I can't seem to give root access to anything else now..
First noticed the other day when trying to sideload an apk..couldn't...tried to do it manually by just copying it to system/apps folder and that's when the first message came up saying "it appears your device may not be rooted"...quite odd I thought.. i then tried to install SuperSU and it when SuperUser popped up to give it allowable root access it would only timeout and say denied...i then tried a bunch of other apps that require root and they would all just get denied by SuperUser...
Anyone seen this before or know what causes this and/or how to fix?
THanks for any help or suggestions
ps.. i'm no noob and have been doing this a long time and have rooted/modded dozens of phones, hundreds of times...but this issue is a new one for me.. IF i have to completely wipe and even go back to stock image and then start over to re-root and re-mod... I will and can do so easily..but that would be last resort if necessary...thanks!
In SuperSU, try the clean-up for reinstallation option.
DocHoliday77 said:
In SuperSU, try the clean-up for reinstallation option.
Click to expand...
Click to collapse
when launching SuperSU it needs root access to begin with and SuperUser wont allow..this clean up for reinstall is still doable?
Get the recovery flashable SuperSU then. It'll get rid of the other one in the process. You can get it from my sig, but it'll need to be updated after.

[HELP] Cyanogenmod 12 Root Access

After months of sitting on the stock rooted rom I finally decided to install CM12 [Official] this morning.
everything is working fine but I have one issue. I've lost my root during install and can't seem to get it back.
So far I've installed SuperSU from the play store and the only thing that happens after telling me that the su binaries need to be updated is me getting the failed message when i hit update. I've also tried the secondary option of installing through TWRP but once you click that it does absolutely nothing.
Obviously there's something that i'm missing or doing wrong. does anybody have any input
Under development you have to enable Root for it to work
Sent from my LG-D851 using Tapatalk
That's the thing.... It is enabled under development.
I've restarted my phone numerous times and even did another fresh install enabled it again and the only difference this time around is that root checker is saying i have root now but supersu still wont update the binaries.
Root is now built into Privacy Guard for CM Roms, so if you need to manage anything you have to go to Privacy Guard in the settings. (In other words supersu is no longer needed)
I dont know if you should do this, but i did....
I launched odin and "re-rooted" my phone and it worked.
I already had Cyanogenmod 12 installed. I just put it in download mode and installed supersu through odin and its worked so far
SuperSU and Xposed are built in to Cyanogenmod 12. There is no need for either. Enable root access under Developer Options from the settings.
Sent from my LG-D851 using XDA Free mobile app

Why won't SuperSU update on CM13?

My Tab Pro 8.4 has been bootloader unlocked since I got it months ago. It has always run a custom ROM, usually just CM12 nightlies with root from SuperSU flashed in TWRP and no Xposed or other "fancy" stuff installed. Since the CM nightlies shifted to CM13 I can't get SuperSU to "update" (the notice that says you must update SuperSU). I've tried reflashing, I've tried wiping and doing new installation from CM13, I've tried different versions of SuperSU. Nothing works to successfully install an updated SuperSU. I've never had this problem before. I've read everything I can find and found several places where something like this is being discussed, but no path to resolution. How can I fix this?
I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.
Sicron said:
I believe SuperSU doesn't work in CM13. Just use the built-in root method. Open the developer options and use the root method in there.
Click to expand...
Click to collapse
I've tried using only the built-in root method. I set it to "both APPS and ABP" (or whatever that last option is). That's not enough for Root Explorer, not enough for PIE Control, not enough for AdAway, at least in my case. All those apps still indicate that I'm not rooted.
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Hmmm. Well, that'd be a great solution for me so I'll give it another go. Wipe wipe wipe, flash a CM13 daily, flash CM13 GAPPS, wipe Dalvic cache and cache, reboot. In Settings, enable Developer Options, set Root Access to Apps and ADB. Reboot. If that's not the recommended procedure I hope someone will let me know.
Sicron said:
Both AdAway and Rootexplorer work fine for me. Actually, I haven't seen a root app that doesn't work with the built-in root.
Click to expand...
Click to collapse
Well, maybe the problem I have is different than the one I THOUGHT I had. Wiped, installed CM13 daily, installed CM13 GAPPS, set Root Access in System/Developer Options/Root Access to Apps and ADB. I guess root access exists but I'm not sure. In Root Explorer I CAN switch folders from Read/Write to Read Only (normally a root only option) and AdAway installed and ran fine. BUT -- in PIE Control I still get "Can not, rooted only" when I try to use the "Back" command. There is often a "hashtag" (or "pound sign") symbol in the Status Bar, just as there would be if I needed to update SuperSU, but the symbol is on the far RIGHT and doesn't correspond to any message in the drop down box. Plus, I have never seen the pop up box that normally appears to ask me if I want to grant root access to an app or process. So, what am I? Partially rooted?
It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)
otyg said:
It has full root, sounds like the app needs updating for CM13 and / or other root methods. (not CM13's fault)
Click to expand...
Click to collapse
What I'm reading here makes sense but there must be another variable. My phone (Moto X Pure) is running a custom MM ROM, SuperSU DOES install and run just fine, I get all the expected root prompts and controls and the Back button (which requires root) works in PIE Control. I'm guessing, therefore, that the "problem" lies with CM13 as a specific MM ROM rather than with all MM ROMs. Time to flash a different MM ROM on my SM-T320.

Warning sign in notification telling me KingRoot is bad?

Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
joppy said:
Suddenly I get a warning telling me to uninstall king root 4.9.6. I've been running same fulmics 6 for months and I just discovered the warning sign today.
What is this? Is there any potential danger to keeping king root? If I uninstall king root I will loose root privileges, yes?
Click to expand...
Click to collapse
Fulmics has SuperSu installed as System application,there was no need to install KingRoot..
Also if you have two Root apps (same like SuperSu),then your phone isn't going to have a good time..
So delete KingRoot and stay with SuperSu.
Greetings.
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
joppy said:
Thx. I used king root to first get root access so I could install fulmics. Iirc I found the king root from a post here on the forum, so I assumed it was safe.
I disabled king root.btw it is fulmics 6.1 I got. It seems all things good now. I feel a little paranoid, as I discovered king root is from China ?
I wonder if I should do complete install from scratch or am I safe as long as king root is not longer active?
Click to expand...
Click to collapse
The best choice is to uninstall it.Because it has setted it's self as a system application.
But also i think it has an option (in-app) "Uninstall".
In addition if Kingroot is unable to uninstall by using the inapp option then try installing an app from Play store called " System app remover" and delete it from there.
If nothing works then doing a clean re-installation of the ROM would be a great option.
A Tip:Never install an other Root application while you have SuperSU.
Let's take Kingroot for an example, when you have SuperSU and install Kingroot then automatically Kingroot detects that you have an other root application and it set's it's self as system app.
System app remover did the trick. Removed the King Root app. Result is o/c that adaway is no longer working. So I get to play around with SuperSU now. As I am new to SuperSU I am not sure how to get the correct settings. Should I make SuperSU a system app? Or set permanent full root?
Btw, I never had any problems running King Root. It was even a very nice way to charge the phone because King Root made charging go faster.
I've been thinking about the warning sign I got, and could it possible be a generic warning because King Root had root access? Meaning I would get the same warning with other apps with root access?
It seems strange that King Root that is mentioned som many times here on XDA should be crapware. Surely some smart people would have noticed and made posts about it? I am thinking maybe I panic'd and removed King Root prematurely?
Darn it. SuperSU won't run or allow me to set root access to apps. So no TWRP does not work, adaway does not work, root checker confirms I don't have root anymore and to make things worse, SuperSU says I need to upgrade, so I downloaded the latest version as a zip file to install from TWRP but guess what, no more root access. I will try to boot manually into TWRP and install SuperSU. Hopefully that will work.
And reading SuperSU thread it clearly says I must have ROOT prioer to install SuperSU.
Is there are fulmics setting somewhere I have overlooked? Can I set root from within fulmics tweaks?
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
joppy said:
Well I didn't get the SuperSU working, then I discovered that there was a newer version of KingRoot, v5.0. So for the ease of it I just installed KingRoot v5.0. As of right now, I don't have any warning signs saying Kingroot is bad news.
So unless it is a known fact that kingroot is infected by crap/malware/spyware/whatever I think I just stick to that one for now. I am used to it, I know how to work it and google didn't find any indications kingroot has been compromised . I saw a few posts about earlier version sending IMEI to china, but it seems that was v3xx. v4x and5x seems to be ok.
If this is stupid behavior and I should remove king root let me know and pls add some links or something to back it. I would hate to give a compromised app gateway into my phone but at the same time I think I was in panic mode earlier today and that my reaction was uncalled for.
Click to expand...
Click to collapse
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Sotiris02 said:
Then if you are used to Kingroot just uninstall SuperSu(Install the system app remover from Play store ((the first app that appears)).
Because as i mentioned before if you have two Root applications your phone isn't going to have a good time.
(That may be the problem your phone went to Panic Mode)
If you have Kernel Panic mode problems (after unstalling SuperSU) a clean reinstall of the latest version of Fulmics ROM would be great..
PS:I don't know if Kingroot has any type of virus but I'll check if it has anything malicious.
As i checked you said that you lost root access and you took it back with Kingroot right?
Click to expand...
Click to collapse
Seems I am good after all. Turned out I messed up the fulmics 6.1 badly when trying to get adaway for youtube to work. So now I got fulmics 6.5. Yeah I know it is not the latest but I had slow internet connection and 6.5 was already downloaded but not yet installed so I just picked that and did a swipe, and twrp install of fulmics 6.5.
I did however install king root 5.01 again to get an easy way of getting everything else important installed that requires root.
If I don't see more warnings I think I will be fine. If I do I will take the plunge for superSU and read up on that before making the switch.
If I see those warning signs again I will try not to panic and try to keep calm

Lineage 14.1 Root not active

Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
DoppelM said:
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
Click to expand...
Click to collapse
Download a recovery flashable zip from here: and flash in TWRP.
http://www.supersu.com/download
Sent from my N9515 using Tapatalk
bcrichster said:
Download a recovery flashable zip from here: and flash in TWRP.
http://www.supersu.com/download
Click to expand...
Click to collapse
I would not give up so soon. At least try a clean installation of ROM and addonsu in one twrp session.
DoppelM said:
Hey, today I flashed Lionage 14.1 in my Sm-j510fn with twrp. Now i wanted to installiert Root and flashed Root in my device. In the dev settings i ticked Apps and ADB. But if i now want to open Root checker and check it, it says that my device is not rooted. In Es file Explorer i also can not tick Root mode.
Anyone help PLZ
Thanks
Click to expand...
Click to collapse
https://download.lineageos.org/extras you can download it here just choose 14.1 between the 3 arm arm64 x68 depending on your device. flashing lineageOS nightlies doesnt automatically root your device
shadow_blitz said:
you can download it here just choose 14.1 between the 3 arm arm64 x68 depending on your device. flashing lineageOS nightlies doesnt automatically root your device
Click to expand...
Click to collapse
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
wrecche said:
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
Click to expand...
Click to collapse
We are talking about an unofficial LineageOS? Maybe you should talk with the person that built it.
any solution ?
Me 2
I am having the same issue.
I installed the su extra package using TWRP 3.2 .
I now have the "root" and "manage root acesses" menus under development options.
I enabled "apps and adb" option.
When I type "su" in any terminal app (including the built in one), I get "permission denied"
With root access set to "disabled", when I type "su" I get "command not found".
With root access set to "apps and adb", if I run a root checker app or try to use any app that requires root, I do not get a prompt to allow root access, and I do not get any notifications from Privacy Guard, either.
The root checker apps all say that I do not have root.
Even after running apps that should request root, when I look in the "manage root accesses" menu, it says that no apps have requested root yet.
What gives? I am really trying to use the built in root access features, I do not want to use SuperSU. Partly because SuperSU did not work either (same behavior as above), and because I don't like SuperSU's bloated code and proprietary implementation.
I really hope we can get this working, If I can provide any other info to anyone who wants to help, let me know.
I am seeing a lot of posts about this in relation to Lineage 14.1 and 15.1 and roms based on those builds. The issue is apparent on multiple different devices, so I suspect it is an issue with the base lineage source somewhere. I havn't looked at the source, though, so I don't really know... All I do know is that this is very frustrating.
m1st3r3 said:
I am having the same issue.
I installed the su extra package using TWRP 3.2 .
I now have the "root" and "manage root acesses" menus under development options.
I enabled "apps and adb" option.
When I type "su" in any terminal app (including the built in one), I get "permission denied"
With root access set to "disabled", when I type "su" I get "command not found".
With root access set to "apps and adb", if I run a root checker app or try to use any app that requires root, I do not get a prompt to allow root access, and I do not get any notifications from Privacy Guard, either.
The root checker apps all say that I do not have root.
Even after running apps that should request root, when I look in the "manage root accesses" menu, it says that no apps have requested root yet.
What gives? I am really trying to use the built in root access features, I do not want to use SuperSU. Partly because SuperSU did not work either (same behavior as above), and because I don't like SuperSU's bloated code and proprietary implementation.
I really hope we can get this working, If I can provide any other info to anyone who wants to help, let me know.
I am seeing a lot of posts about this in relation to Lineage 14.1 and 15.1 and roms based on those builds. The issue is apparent on multiple different devices, so I suspect it is an issue with the base lineage source somewhere. I havn't looked at the source, though, so I don't really know... All I do know is that this is very frustrating.
Click to expand...
Click to collapse
I bet you have installed unofficial lineageOS. On all my officially supported devices root works as expected.
kurtn said:
I bet you have installed unofficial lineageOS. On all my officially supported devices root works as expected.
Click to expand...
Click to collapse
Essentially saying 'it works great for me, you must be doing something wrong' isn't actually a very practical troubleshooting approach. While there is definitely the possibility that I am doing something wrong, troubleshooting will reveal if I have made a mistake and will also benefit the loads of other people posting about similar or same issues. That's why we have forums, right?
You bet wrong, do I win anything?
Like I mentioned, I have experienced this issue with both Lineage 14.1, 15.1, as well as unofficial builds and ROMs based on Lineage.
It is hit or miss, in most cases I just tried flashing different ROMs on my devices until I find one that has working built-in root.
I had a lot of issues installing the official builds on my 'bacon' device, I eventually went with resurrection remix instead. That was the only Oreo build that built-in root packages worked with.
In the case of my 'klte' (g900v variant), I installed 7 different Oreo based ROMs. Since there is no official Lineage build for the 'klte' (which is sad, it's a great device), I was using all unofficial builds in the case of this device. They were all based on Lineage, or just unofficial Lineage builds focused on supporting the klte. I couldn't get the built in root functionally working on any of these builds (Lineage unofficial 14.1 & 15.1, Havoc OS, etc). If anyone thinks it will help, I can elaborate further on which packages and versions I used...
Rooted lineageos not recognized
I have exactly the same issue with my Samsung S3 I9300.
I flashed it with lineageos using CWM and thereafter I flashed with the extra armsu. I cannot see anything I could have done wrong. However, neither Titanium nor a root checker recognizes the rooted state. As far as I can see there are quite many having the same issue. Unfortunately most replies are just best guesses like flash with TRWP or add gapps (the katter didn't solve the oroblem either. I am not an expert but I successfully got rid of extremely persisting boot loops most probably caused by Magix which I avoided therefore with this try to root the lineageos.
warbexda said:
I have exactly the same issue with my Samsung S3 I9300.
I flashed it with lineageos using CWM and thereafter I flashed with the extra armsu. I cannot see anything I could have done wrong. However, neither Titanium nor a root checker recognizes the rooted state. As far as I can see there are quite many having the same issue. Unfortunately most replies are just best guesses like flash with TRWP or add gapps (the katter didn't solve the oroblem either. I am not an expert but I successfully got rid of extremely persisting boot loops most probably caused by Magix which I avoided therefore with this try to root the lineageos.
Click to expand...
Click to collapse
So what's your goal? Just moaning or asking for help? In the 2nd case you should provide more details like filenames and procedures.
And yes. Root works well on my S3.
kurtn said:
So what's your goal? Just moaning or asking for help? In the 2nd case you should provide more details like filenames and procedures.
And yes. Root works well on my S3.
Click to expand...
Click to collapse
Yes you are right. Just moaning is not an option. Here are the details:
1. Flashed with lineage-14.1-20181025-nightly-i9300-signed.zip using CWM
2. Installed Titanium (with "not rooted" as result of course)
3. Installed addonsu-15.1-arm-signed.zip using CWM and changed the setting to "apps and ADB" , an option which I didn't have before - however, with no effect on Titanium
4. Checked root status with "Root Checker" which resulted in "not rooted"
5. Installed open_gapps-arm-7.1-pico-20181120.zip using CWM (because someone suggested it as solution) - with no effect.
Now to the observed "irregularities":
1. The installation of the "addonsu" which I repeated had a "Warning: No file_contexts." but ended successfully
2. The reboot metioned: " Root access possibly lost. Fix?" which I replied with "Yes fix root (/system/xbin/su)"
Possibly worth to be mentioned: Titamium tries with command "system/bin/su". I've checked that su resides in both directories bin and xbin with identical size
In writing this I realized the version mismatch 14.1 lineageos and 15.1 addonsu. I uninstalled addonsu 15.1 and installed addonsu 14.1 instead and THIS SOLVED THE PROBLEM
Many thanks for your help.
warbexda said:
Yes you are right. Just moaning is not an option. Here are the details:
1. Flashed with lineage-14.1-20181025-nightly-i9300-signed.zip using CWM
2. Installed Titanium (with "not rooted" as result of course)
3. Installed addonsu-15.1-arm-signed.zip using CWM and changed the setting to "apps and ADB" , an option which I didn't have before - however, with no effect on Titanium
4. Checked root status with "Root Checker" which resulted in "not rooted"
5. Installed open_gapps-arm-7.1-pico-20181120.zip using CWM (because someone suggested it as solution) - with no effect.
Now to the observed "irregularities":
1. The installation of the "addonsu" which I repeated had a "Warning: No file_contexts." but ended successfully
2. The reboot metioned: " Root access possibly lost. Fix? Which I replied with "Yes fix root (/system/xbin/su)"
I hope this helps.
Click to expand...
Click to collapse
Ha! For a 14.1 Rom you need a 14.1 addonsu
For future readers:
There are two versions of lineage os root images, 32 and 64 bit. Please check that you installed correct one, this way I solved this problem!
Solution
wrecche said:
he said he already did that.
why can no one give a real answer to this issue. Installed the correct extras, says root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.
It was a lot better when it was part of the rom, why the decision to remove it? all it causes is headache and people reverting away from the rom.
Click to expand...
Click to collapse
Did you get any solution???????
Atharva C said:
Did you get any solution???????
Click to expand...
Click to collapse
Solution for what? I think lineageOS people found the best way to ship a non-pre-rooted ROM with native root solution.
NO ROOT Access
kurtn said:
Solution for what? I think lineageOS people found the best way to ship a non-pre-rooted ROM with native root solution.
Click to expand...
Click to collapse
Are u able to provide a way to Root?
Atharva C said:
Are u able to provide a way to Root?
Click to expand...
Click to collapse
Flash the su package from download/extras matching your lineageOS version. Enable root in settings/developer
NO ROOT Access yet #failed
kurtn said:
Flash the su package from download/extras matching your lineageOS version. Enable root in settings/developer
Click to expand...
Click to collapse
Root for adb and apps in developers mode, but will not give root access to apps that need root, nor can you remove/rename system apps as permission denied. No prompts, no questions, just denied. Adaway will just refuse to open saying the device needs to be rooter. SuperSU says that Su is occupied, and flashing it from TWRP causes a boot loop.

Categories

Resources