every time I try installing it, the phone crashes
I'm on stock, rooted lollipop
I have installed busybox using below app
busybox on rails,
use installation method as recovery and then proceed,
play.google.com/store/apps/details?id=me.timos.busyboxonrails&hl=en
So I just updated my phone to MM, I`m using v1.6.5 of the Skydragon rom with the latest EX kernel, and SuperSu has stopped working correctly. I have to continuously grant permission to every app that needs it, SuperSu never remembers, even when changing the default setting to Grant it changes back the next time I open the app. If anyone has any ideas that would really help me out, thanks.
Which version SuperSU that you installed when running ElementalX kernel ? Is SuperSU detect the kernel as systemless mode or system mode ?
I don't use ElementalX so not sure whether it needs supolicy patch or not but I guess SuperSU 2.65 or 2.66 should work find with this kernel
ckpv5 said:
Which version SuperSU that you installed when running ElementalX kernel ? Is SuperSU detect the kernel as systemless mode or system mode ?
I don't use ElementalX so not sure whether it needs supolicy patch or not but I guess SuperSU 2.65 or 2.66 should work find with this kernel
Click to expand...
Click to collapse
Using v2.52 of SuperSu, sorry not sure how to check whether it's systemless or system mode, would you recommend updating su and can you give me a link please?, thanks.
2.52 is for system mode and need a patched kernel. ElementalX is not patched for 2.52 (if I'm not wrong).
What you can try is 2.65 or 2.66 - download here - http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
This will detect automatically whether your installed kernel is suit for system mode or system less mode.
This thread is to only inform that i could Flash surround sound mod and EX kernel without decrypting and with default recovery installed in Android N DP3. This was possible only by FLASHFIRE app by our great CHAINFIRE. So all thanks to him.
I flashed Android N DP3 clean. Then rooted with CF Autoroot 2.70 in Windows 10 without decrypting. Booted and updated with supersu 2.74 flashed through FLASHFIRE. only thing i did was enable MOUNT READ/WRITE in every flash. Then flashed the ex kernel zip and FLASHFIRE supported aroma installer too. Lastly i flashed surround sound mod. Everything is working great and my device is still ENCRYPTED
Thanks to CHAINFIRE again.:good::good::good:
So I wont say I tried everything but have been reading and trying solutions and they havent worked for me. Maybe someone can point me in a different right direction. So far I clean installed 3.2.8(twice btw), I'm fastbooting into twrp 3.0.2-1, flashed supersu 2.78 SR4 and flashed xposed framework v87.
Sometimes xposed framework v87 flashes in twrp and when I open xposed installer it says xposed framework is not installed. I attempt to then unintstall and try again and sometimes it fails in twrp with this message "cp: cant create '/system/xposed.prop':Read-only file system". I attached a screenshot. I'm also running xposed installer 3.1.1, also tried 3.0.1 by dvdandroid. Any suggestions?
Have you tried Magisk and Systemless Xposed?
mznk said:
Have you tried Magisk and Systemless Xposed?
Click to expand...
Click to collapse
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
SysAdmNj said:
Are you asking if I tried it in the past on my onplus3? I didnt see anyone trying it now with 3.2.8 so I didnt think of it.
Click to expand...
Click to collapse
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
Thanks it all worked and went green except when I tried to download the systeless arm64 sdk23 from within magisk manager. I ended using a test1 version and it went through. Now I wasnt even planning on using magisk but how are you using magisk? When I used it before it was for android pay but I thought that all broke.
Installing xposed breaks SafetyNet anyways and I have no use of Android pay or Pokemon Go etc.
But, with magisk I can install and mod system files without making changes in the system partition like dpi, Viper, SystemUI mods etc. I really like it for the ease of that.
I have installed Xposed on 3.2.8 with a success from the beginning. Steps I've taken:
1. Dirty flashing full zip OOS 3.2.8.
2. Flashing systemless SuperSU from Chainfire (you have to:
Code:
echo SYSTEMLESS=true >> /data/.supersu
for systemless).
3. Flashing Xposed v87-test version, which now disappeared from dl-xda.xposed.info/framework/sdk23/arm64/
4. Flashing ElementalX 0.28.
I was upgrading from 3.2.6.
mznk said:
I'm using it on 3.2.8 currently and all works well so far.
Here's how I did it: Clean flashed 3.2.8 using sideload with official recovery, then booted twrp-3.0.2-1 (from twrp.me), flashed Magisk v9 and flashed the phh-superuser. After booting into android, installed phh's SuperUser from Playstore, and installed Magisk Manager, then installed Xposed systemless arm64 sdk23 using the inbuilt downloader (or use the zip on the thread).
Click to expand...
Click to collapse
OxygenOS 3.2.7 with v87.1 Magisk version installed. Got stuck at boot animation when dirty flashing to oos 3.2.8. Any ideas? Is there compatibility problem with xposed modules?
I would use a newer recovery, twrp-3.0.2-23-oneplus3 is the latest and I've had zero issues with it. I uploaded it to drive vs searching for it. Next, as stated, install Xposed via the app, version 3.0.1 by dvdandroid is what I'm using and after selecting arm64 api23 , granting root, it installs, reboot and done.
Magisk has a Viper4Android Module you can download and install and reboot which you are going to use.
I have this working on my Pixel XL running 8.1:
-Installed ElementalX v3.0
-Installed Magisk v14.5
-Installed BusyBox Module found in Magisk
-Installed Viper4Android FX v2.5 (Created by ahrion ,zackptg5) This module give you option of new or old Viper.
-Installed The Magisk permissive script (Found Below)
-Restart
When you have completed the above steps, open Viper4Android and check the Driver Status. It should look like the screen below
Thanks to @TWisTeD48 for the simple instruction over at the thread [12/13/17] ViPER4Android FX 2.5.0.5 [Unity/AML][v2.5] by ahrion
Will AP still work with this if I dirty flash?
Yeah, I'd like to know if AP will pass, too.
Ya safetynet is passing with this installed.
Anyone tried this with Dolby add-on? Either Atmos or Digital?
Tx guys.
Can we uninstall super SU and suhide to flash magisk without wiping data and flashing factory image.. i see that arise amd viper mod need migisk
Rajaasim1980 said:
Can we uninstall super SU and suhide to flash magisk without wiping data and flashing factory image.. i see that arise amd viper mod need migisk
Click to expand...
Click to collapse
Try to unroot device through supersu app. This normally works on my device. If device doesn't boot after this flash factory image deletinng "-w" in flash-all.bat. In supersu thread you also find somewhere a unsu.zip to flash in recovery to totally unroot a device.