Related
Android Pay use after rooting has been discussed in a few other threads, here on XDA, notably the 6P and 5X Nexi:
http://forum.xda-developers.com/nexus-6p/general/android-pay-root-t3309072
http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659
With our newly rooted H830s (courtesy of http://forum.xda-developers.com/tmobile-lg-g5/development/root-h830-t3384526), it'd be nice to collect our information here.
I am very interested in how Android Pay may or may not work after our TOT flash. Here's a quick tutorial:
SuperSU must install via a 'systemless' root method due to security changes with Marshmallow. Thus, when SuperSU is flashed in TWRP as described in the TOT root thread, it can only install this way. It should not affect the /system partition.
Android Pay uses the "Safetynet API" to detect for tampering/root. What they classify as tampering is not entirely clear. But they do check /system among other things. It looks like apps that have altered the /system partition in some way are detected via this method.
(more boring info here http://www.howtogeek.com/241012/saf...y-and-other-apps-dont-work-on-rooted-devices/ )
It must also check the permissions of the /su/bin folder, as it should have a 751 permission profile (which is the described fix in the TOT root original post).
That is:
-Run "adb shell"
-From the shell run "su"
-On the # prompt run "chmod 751 /su/bin/"
Or, you can use root explorer to change the permissions octal to 751 for that folder.
It is set to this permission state in the rooted TOT upon first install. Obviously other root alterations you do may change it.
There are apps, such as Safetynet Helper sample (https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample), which can utilize the API to see if the API is tripped.
Right after installing the TOT and getting everything to boot properly, the app shows everything is still kosher. I was able to run Android Pay, add credit cards, and have confirmed with a payment transaction.
I believe any root app that doesn't make permanent changes to /system in and of itself will probably keep Android Pay working. Obviously, for instance, if you have a terminal program app with root, and run some commands that alter your system partition/files, it may trip SafetyNet, though just having the app installed does not.
EDIT1: As of 7/25/16, a change was made to the SafetyNet API and it now detects systemless root. Android Pay no longer works on rooted devices, regardless of method. A new method will need to be developed.
EDIT2: As of 8/22/16, a workaround has been developed and tested!​Developer @topjohnwu has created Magisk (http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382). This is a new way of integrating systemless changes into Android devices. This includes root, xposed, etc. The unique thing with Magisk is that you can instantly un-root your device, run Android Pay, and then reactivate root, all without rebooting. It is pretty seamless.
See the referenced thread for the latest information. It does take some work to install but it's fairly straightforward.
If you want to start from a clean install, @Gungrave223 has detailed the steps here:
http://forum.xda-developers.com/showpost.php?p=68353051&postcount=22
If you want to keep your data, it's just slightly more work. Assuming you are starting with a rooted install, here is a quick summary on how to do this:
0. You may want to first un-register the cards you have in Android Pay. Some banks apparently only allow a set # of installs before they block additional installs, thus requiring you to call the bank directly to have them reset that number. If Android Pay resets (unsure what security changes trigger this), it will forget your cards, thus leaving those cards registered on a phantom install. Un-registering first may prevent this.
1. Get the Magisk flashable zip, the Magisk-altered phh-superuser.zip, and the Magisk manager apk from the referenced thread.
2. Go to SuperSU and select full unroot. DO NOT restore the stock boot.img. DO NOT restore the default recovery. The phone should reboot and your root will be lost.
3. You should now restore the stock boot.img. This can be done without losing your data or re-encrypting your data. There are 2 ways.
Flash autoprime's stock boot.img zip file through TWRP (recommended), OR
Flash the TWRP-ed TOT file through LGUP, using the UPGRADE (not refurbish) setting
Why not just allow SuperSU to restore the stock boot.img in step 2? Because it will reboot instantly into system and start encrypting your data, with no way for you to intervene and boot into TWRP first!
4. You likely did not have data encryption on your initial rooted installation. If you want to keep yourself un-encrypted, you MUST immediately boot into TWRP before the next power on. If you do not, it will re-encrypt your data. This is the default behavior of the stock boot partition, which you just restored in the step above. You can make this easy for yourself by TWRP flashing autoprime's stock boot.zip and then immediately doing the next steps. Note: Magisk can be installed just fine on a phone with an encrypted data partition if you don't care about data encryption.
Flash the magisk.zip from the Magisk thread. This installs Magisk and also disables the forced encryption (just like the dm-verity zip)
Re-establish root by then flashing the special modified phh-superuser.zip
Note: Chainfire's SuperSU is NOT compatible if you want to use Android Pay
5. Reboot into system. You need to then install from the Playstore phh's superuser app. You also need to install the Magisk manager apk. Grant all your usual apps root permission in the superuser app.
6. Run Magisk Manager and grant it superuser access. You'll find a simple toggle to mount/unmount root. Unmount! Check that SafetyNet will pass. If you've done everything right, it will!
7. Run Android Pay. Add your card(s) back. Mount root back and go about your business.
8. When you want to use Android Pay, unmount root and run the app. Here's a tricky part (and currently a work in progress). We do not know how often or when Android Pay checks for root. We DO know that it does this when you initiate adding a new card. So you can try an Android Pay transaction. If it fails (they often do, even if you are unmounted root at that time), pretend to add a card, cancel it, and then do the transaction again. It should work now!
pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.
fatapia said:
pay was not working after I installed the Fluence patch, uninstalled xposed and Android Pay is working with no issues with root.
Click to expand...
Click to collapse
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?
waylo said:
The Fluence patch has a huge # of system changes. I would totally expect xposed to break the SafetyNet.
So do you have Fluence still installed, with only xposed removed?
Click to expand...
Click to collapse
Yup you got it, I had been running Xposed off Fluence for a while until I left my wallet at home and didn't feel like starving. So I downloaded the Xposed uninstaller only, ran it in recovery and then let it reboot and Pay was working again.
I followed the instructions for rooting in this thread, http://forum.xda-developers.com/tmo...p-step-guides-rooting-t-mobile-lg-g5-t3388272 and then the instructions here to change the permissions but an still having problems. The only app root app I installed after rooting was an app to export google play music with track names intact.
What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.
waylo said:
What problems specifically are you having?
Did you install the safetynet helper app? What happens when you run it?
What root app did you install? Was it this one? http://forum.xda-developers.com/showthread.php?t=2620331 (play music exporter) aka https://www.david-schulte.de/en/play-music-exporter/
Looks like that app doesn't work in MM regardless, per the developer's page.
Click to expand...
Click to collapse
Yes, that is the app. I noticed MM was not supported after I had it installed
I have installed and run the safetynet app and it shows it gets tripped on the CTS profile
---------- Post added at 02:03 PM ---------- Previous post was at 01:40 PM ----------
I just realized I also had Adguard installed. I have uninstalled it and turned off suppersu and restarted but the phone still does not pass the CTS profile check
Wondering if any of those apps made some changes to /system that were not completely reversed.
Doesn't look like that music app does any permanent changes anyway, rather just copies cache not normally accessible into another folder.
Can you check the permission profile of your /su/bin folder?
Briefly looking at the Adguard website I can't make out how its root version works exactly.
What other apps are listed under your SuperSU app list? You're not running xposed, right?
Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly
eremeya said:
Apps listed in supersu are adb shell, root checker basic, and Titanium backup.
Titanium backup was installed after safetynet app test failed.
I'm not 100% sure what the permissions are but I followed your instructions above to change the permissions and it appeared to run correctly
Click to expand...
Click to collapse
SafetyNet still failing after the permissions change?
It was today. I can try changing them again tonight when I'm at my computer and report back.
I have confirmed that the folder permissions are set to 751
eremeya said:
I have confirmed that the folder permissions are set to 751
Click to expand...
Click to collapse
Well if we can't track down the actual changes made, and you're interested in getting Android pay to work, you could try reflashing the system partition.
It looks like from reports on other threads (Nexus mostly), that something has changed with the SafetyNet check. Phones that were working just fine yesterday now fail. Most likely something server-side was patched so now Android Pay will not work with systemless root.
Details updated as I find them.
For those interested in this topic, a pretty major development has occurred at this thread:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Essentially, this is a brand new way to implement root systemless, which can be toggled via an app, without rebooting. This does allow the SafetyNet api to remain untripped. The steps involved include flashing back to stock kernel/system, flashing the application .zips, and flashing special SuperSU or SuperUser .zips. I have not done any of this yet as it is still very early.
There are some reports, unfortunately, such as this post:
http://forum.xda-developers.com/showpost.php?p=68045722&postcount=121
which reports that despite SafetyNet passing, Android Pay still does not work (user is on Nexus 6P).
I have read of no G5 users doing this yet, but there is a V10 user who has. Stay tuned.
I've been watching the Magisk threads for the past week and decided to take the plunge today. Many Nexus phones seem to have a lot of trouble with Android Pay, but other makes seem to do better. There were confirmations from LG G4 owners. As of this writing Magisk is on v3.
The install steps from the Magisk thread are this:
1. Reflash a stock boot.img to reset your systemless root
2. Flash Magisk.zip
3. Flash modified phh-superuser.zip (not the official one). Chainfire's SuperSU does not currently have as much support, but there is a modified supersu zip as well.
4. Boot and install phh's superuser app from the App store.
5. A 'magisk manager' app is installed via the flashed .zips. This allows you to turn off root for a set # of minutes, without rebooting.
Given the unique way the G5 is rooted, with automatic encryption, I figured it might not be so simple to install this if I wanted to keep my data without a full wipe. It quickly became much more complicated than what I wanted. Here's exactly what happened.
First, I made a full boot+system+data backup.
Then, these were my thoughts/concerns:
I have Adaway installed with the systemless addon zip and SuperSU installed. Magisk installation requests flashing back the stock boot.img. What would this do to the supersu install and Adaway?
The adaway systemless zip makes a script file which is kept in the /su/su.d/ folder. I removed this.
The SuperSU has a complete uninstall feature. As part of this uninstall process, it asks if you want to restore the boot.img (yes--this stock one is backed-up after the initial supersu.zip flash during our initial root/TOT process) and/or the recovery (no, don't do this, but it probably would not have done anything as there is no stock recovery backup). I thought this would accomplish our goal. It does warn you that you may have re-encrypting of the data partition if you go this route.
And unfortunately, after rebooting, it automatically and immediately encrypted the data partition.
Well shoot. Correct me if I'm wrong, but an encrypted data partition cannot be worked on. It booted just fine, but without root.
I started having some doubts at this time so I decided to try to restore back to my initial setup. Through TWRP, I wiped the data partition and flashed the no-verity.zip, to hopefully stop any re-encryption.
Then, after figuring out how to mount system properly (TWRP defaulted to mount system as r/o), I restored my nandroid backup in its entirety.
But upon reboot, it went immediately into bootloader mode. And it continued to do this after every battery pull and power on. I had never heard of this before! Finally, I realized I could still boot into TWRP. I flashed the 10Dcomplete.zip made by autoprime, restoring the boot and system partitions to stock. And then I flashed the magisk v3.zip and the modified phh-superuser zip.
It finally rebooted into Android, with data intact! Oddly, my unlock pattern had changed without my knowledge, but the backup PIN worked. I installed the market phh Superuser. Magisk is installed properly and it passes SafetyNet, and I can add cards to the app. I'll test out Android Pay next opportunity I have.
If I had to do it all again and wanted to keep data intact, this is what I would do.
1. Autoprime did make a 10D boot flashable zip. So this would restore the stock boot.img as intended. There are some files to clean up, such as data/su.img, but that can be dealt with later.
2. I do not know if just flashing the stock boot.img would result in re-encrypting. It probably would. So, immediately after flashing the boot.img in TWRP I would flash magisk and the phh-superuser.
Alternatively, they say you should not dirty flash for things this complex. So consider starting completely new from a 10Dcomplete flash with wiped data.
I've learned that Magisk will work fine with an encrypted data partition, so if you are set on having that, it won't be a problem.
waylo said:
I have a thread here discussing Android Pay while rooted on our G5s:
http://forum.xda-developers.com/tmob...le-g5-t3395036
I thought I was the only one who cared about this kind of stuff!
Which version Magisk did you install?
I just did this 2 days ago but haven't had the opportunity to test AP yet.
What rooted apps are you running? AdAway?
Click to expand...
Click to collapse
To answer your question... I'm using v3 with his v2 of his modified phh superuser.
As for rooted apps...yes AdAways still works perfectly....TB...my one time use of System App Remover etc...
I haven't been able to test Android util tomorrow....but SafetyNet did pass when Magisk was disabled and failed when enabled.
I'll report back tomorrow after I go buy my weekly chicken at my local Fresh Mart.
I'm using the same install as you.
I tried it this AM for the first time and it failed.
On the Magisk-AP thread, someone has posited that maybe the AP app caches any root inquires during that boot. So if you test out AP and it fails while the root is active, it will remember that failure until the next reboot.
That could explain how so many people are getting weird inconsistent results. I'm testing out that theory later today.
Bah, still doesn't work, even if done immediately after a reboot =(
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
saleenman95 said:
Hey guys,
I've done some searching around on this issue, and it looks like Snapchat is not allowing me to login as my device is rooted. However, I had the factory OxygenOS ROM (rooted as well) installed before and never had this issue. Now that I have installed Sultanxda's "Unofficial CyanogenMod 13.0 with custom kernel", I can no longer get Snapchat to login. Like I said, from the searching that I've done it look like it is root related, so I went into SuperSU and did a complete unroot. This still hasn't solved the issue yet, so now I'm stuck and not sure what to do. Is there something I'm missing or is there a way to solve this without having to reflash a different ROM and loose all the time spent setting this one up?
Thanks for the help!
Click to expand...
Click to collapse
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
NevaX1 said:
Hi, the searching can be useful sometimes
http://forum.xda-developers.com/search/forum/5476?query=snapchat
You need an fully unrooted rom to login into snapchat, after that you can flash supersu.
Click to expand...
Click to collapse
Ah, looks like I just didn't search enough. This seems to have done the trick, thanks!
I think you just need to uninstall Xposed Framework for Snapchat to login and then after login you can install Xposed again.
This sounds weird but what worked for me was to download superkiwi via xposed installer, it's supposed to bypass root detection for banking apps in New Zealand but works with snapchat [emoji14]
I found this workaround in a thread somewhere and thought that it wouldn't hurt to try but actually works mighty fine!
Sent from my ONEPLUS A3003 using Tapatalk
Leaving this here in the hopes it helps someone else, took me a bit to find the correct steps.
Currently running the last official CM 13 build for the Droid Turbo (will be moving to LOS soon), rooted with SuperSU Pro, Xposed framework v87, on the newest TWRP.
Nothing worked, not Xposed Switch, Root Switch, nothing. In fact I had to reinstall Xposed Switch to be able to turn root back on, while Root Switch simply uninstalled the SuperSU binary, I had to reflash it. Finally I put it all together and in the following order I got Snapchat to work.
Make sure any OS root (my case CMroot) was turned off.
Download the correct version of Xposed framework Installer, Xposed Uninstaller, and the SuperSU binary (all flashable zip files) for your device to a location on your system that you can easily access from recovery. For me its my TWRP folder.
Uninstall Snapchat. Open a File Explorer and delete the entire Snapchat folder left over.
Select the uninstall "permanently unroot" option from SuperSU, but DON'T let it install the original... Whatever it is, the name escapes me. But don't let it!
Phone will reboot automatically after taking out root, boot to recovery, run Xposed Uninstaller, wipe Cache & Dalvik, reboot phone.
When the phone boots, confirm it is unrooted and Xposed Framework is uninstalled. A root checker app and opening the Xposed App worked for me here.
Install Snapchat, sign into Snapchat. It will accept your login if you did everything correctly.
*This step I did to save myself work in the future, but you can do it later. Turned on CMroot and took a TiBackup of logged in Snapchat in case I ever have to login again, I can just reload the data.*
Boot to recovery. Flash the Xposed framework and the SuperSU binary (in that order), wipe Cache and Dalvik, reboot system.
Open Snapchat to confirm its still logged in. If so grab a TiBack of it for use as needed later.
I hope this helps!
Sent from my DROID Turbo using XDA-Developers Legacy app
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
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
eleazar123 said:
I've spent way too long trying to get this working without any success.
If I flash a custom ROM (ie. Pure Nexus), I can flash the ARISE zip (ARISE+Deuteronomy+2.94+Modular+AROMA+Installer.zip) and it works perfectly. No driver issues, or anything.
When running stock, rooted, after flashing the above zip file, it appears to flash successfully, but when I open the app after rebooting, it always says that the drivers are missing and offers to install them. If I choose the option to install the drivers, it always fails.
I learned that if you're on stock, you have to flash a custom kernel before it'll actually flash (and auto install the apk), so I tried with franco and elemental kernels.
Does anyone know the steps I'm missing? I'm wondering if maybe it's because I need busybox, but I'm not sure where to install busybox (or the best method).
I know there has to be a way to get this working. I'm sure I'm missing something simple.
Thanks in advance!
Click to expand...
Click to collapse
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
rename/remove /vendor/etc/audio_effects.conf
grifforama said:
I think not only do you need Busybox (you should just be able to download this from the play store now you're rooted) you will also need a way of setting SELinux to permissive. Try The SELinux toggler.
Click to expand...
Click to collapse
Shawn haz root said:
rename/remove /vendor/etc/audio_effects.conf
Click to expand...
Click to collapse
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
eleazar123 said:
Thank you both! I will try all of those solutions right now.
When I tried to install busybox via the play store installer to /system/xbin/, it says "It looks like the installation of BusyBox was not successful. Try installing to a different location, that may resolve the issue".
My understanding is that I need to put it in /system/xbin. Do you guys have any ideas? The busybox installer was granted root when I first opened it, so I know it has root access. :\
Click to expand...
Click to collapse
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
grifforama said:
I'd be interested to hear how you get on.
I have Viper4Arise installed, Busybox installed, and it appears to be working (sometimes it just doesn't) but when it does, I don't hear any difference when I apply my convolver irs .
Click to expand...
Click to collapse
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
eleazar123 said:
When I was running custom roms, it worked perfectly and I could tell a major difference in the music.
How did you get busybox installed? I can't figure out why the play store installer is failing. It's also failing for my friend on his Pixel XL (also rooted)
Click to expand...
Click to collapse
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Shawn haz root said:
If you install an app called "root browser classic", the second you open it, it requests to install an add on which is busy box. Then close and open it again and it asks to update which takes you to the Google play store then installed the busy box app. Not exactly a conventional way but I just tried and it installed. Not sure if that will help you or not.
Root browser
https://play.google.com/store/apps/details?id=com.jrummyapps.rootbrowser.classic
Busy box
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
I also installed this with no issues
https://play.google.com/store/apps/details?id=stericson.busybox
Click to expand...
Click to collapse
Thank you! That jrummy busy box installer worked perfectly the first time. I confirmed in the stericson version that busy box is really installed.
I went ahead and flashed the arise zip file, and it has an option to set SELinux to permissive. Unfortunately upon reboot, it was the same drivers not installed error
I'm now thinking my issue might be the audio_effect.conf file. I've tried Solid Explorer (my go to file explorer) and Root Browser that you linked above. Both explorers have been granted root, but neither can actually rename the file (or delete it). Jrummy's app just says operation denied, while solid explorer shows the file gone, but if you refresh, it's right back where it was. I'm struggling to find a way to mount system r/w in either app. Do you have any ideas? :\
I tried to find a tool to set SELinux to permissive and i found lots of kernel tuning apps, but none that actually allowed setting permissive. Even Franco's own app for his kernel doesn't have that option (he said it's something about trying to keep it more secure). Hopefully the arise zip is really setting it properly, it's just the audio_effects issue causing my problem.
Thanks again for your help, guys!
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.