Related
I am a proud owner of OP One and SuperSu Pro. Currently i am using http://forum.xda-developers.com/oneplus-one/development/daily-stock-unofficial-cm12-builds-t2948099 ROM (as of today 15-12 build).
I installed SuperSU through TWRP 2.8 and used to work fine, untill i updated to a new CM12 build. Then i was promted to grand permissions to an app, but i could not press "grant", later opened the SuperSU app and got a message that there is no binary installed, so i tried to reflash the zip noumerous times, but it seems that TWRP is unable to flash the zip.I can flash other zips like new versions of the ROM, GAPPS etc.
It seems like TWRP is not able to flash the SuperSu zip, even though i get a "succesful" message while flashing. I tried cleaning Cache and Dalvik. Also i can't find the log created by TWRP which is suposedly created in data/media/0 so i can't post detailed info about it.
Super Su
There is no Su binary installed and SuperSu cannot install it. This is a problem.
...
Click to expand...
Click to collapse
/system/addon.d/ is a folder in CM roms where the user (and sometimes apps) can put scripts that will be run when you flash a new version of the rom.
Tipically those scripts are used to backup system apps, and their files, so that they can survive a format and reflash.
For example, this is how you would keep SuperSU (root), Avast Agent,...
I made the script below so that @rovo89's Xposed for Lollipop will survive (that is keep it installed) when I flash a new CM12 nightly.
Tested on my phone (32bits), just flashed latest CM12 nightly, wiped cache and dalvik-cache and the phone rebooted fine (and Xposed was still working). Tested on TWRP 2.8.5.1, might not work with other recovery.
Warning: It's for Xposed for Lollipop only. It work as of today. It might not work later with new future versions of Xposed. Also not sure it would work for 64bits.
Download script only:
If you use SuperSu:
81-Xposed.sh
Or flashable zip, see post attachment below:
If you don't use SuperSu, see and flash this other version by DualJoe, see http://forum.xda-developers.com/showthread.php?p=59199445.
So to clarify, this works when you dirty flash? But if you clean flash you need to set everything up again?
click here for my device info:
~~~~~~~~~~~~~~~~~~
DEVICE: SM-N900W8
ROM: Temasek's CM12 v7.7
BASEBAND: N900W8VLUCNI1
KERNEL: 3.4.106-f2fs-temasek-cm12-hlte-v0.66+
RECOVERY: TWRP 2.8.5.0 hlte
XPOSED? YEAH BABY!
vanisleguy1976 said:
So to clarify, this works when you dirty flash? But if you clean flash you need to set everything up again?
click here for my device info:
~~~~~~~~~~~~~~~~~~
DEVICE: SM-N900W8
ROM: Temasek's CM12 v7.7
BASEBAND: N900W8VLUCNI1
KERNEL: 3.4.106-f2fs-temasek-cm12-hlte-v0.66+
RECOVERY: TWRP 2.8.5.0 hlte
XPOSED? YEAH BABY!
Click to expand...
Click to collapse
That's indeed a very good question ?.
Yes, I use it when dirty flashing, primarily to save time and streamline the process, that is, I avoid having to flash the Xposed zip over again.
If you do a clean flash (ie. with a wipe data) I think it should keep all the stuff in place (all the stuff installed by the Xposed zip). In that case thought, you'll need to reinstall the Xposed Installer, as well as all the modules you add. In that case you wouldn't really save much time I believe.
Sent from my OnePlus One using Tapatalk
And if real clean flash as like wipe system, it won't survive..
But for dirty it's great, going into recovery as writing it, thanks you..
reemar said:
And if real clean flash as like wipe system, it won't survive..
But for dirty it's great, going into recovery as writing it, thanks you..
Click to expand...
Click to collapse
Yeah, true, if you wipe system you remove that whole addon.d folder, which is good (might be needed).
Yes, it's basically for those who flash Nightlies every now and then (which don't require wiping more than cache and dalvik).
Sent from my OnePlus One using Tapatalk
adlx.xda said:
That's indeed a very good question ?.
Yes, I use it when dirty flashing, primarily to save time and streamline the process, that is, I avoid having to flash the Xposed zip over again.
If you do a clean flash (ie. with a wipe data) I think it should keep all the stuff in place (all the stuff installed by the Xposed zip). In that case thought, you'll need to reinstall the Xposed Installer, as well as all the modules you add. In that case you wouldn't really save much time I believe.
Sent from my OnePlus One using Tapatalk
Click to expand...
Click to collapse
I'll have to wait till Temasek comes back from holidays before I can test this
adlx.xda said:
/system/addon.d/ is a folder in CM roms where the user (and sometimes apps) can put scripts that will be run when you flash a new version of the rom.
Tipically those scripts are used to backup system apps, and their files, so that they can survive a format and reflash.
For example, this is how you would keep SuperSU (root), Avast Agent,...
I made the script below so that @rovo89's Xposed for Lollipop will survive (that is keep it installed) when I flash a new CM12 nightly.
Tested on my phone (32bits), just flashed latest CM12 nightly, wiped cache and dalvik-cache and the phone rebooted fine (and Xposed was still working). Tested on TWRP 2.8.5.1, might not work with other recovery.
Warning: It's for Xposed for Lollipop only. It work as of today. It might not work later with new future versions of Xposed. Also not sure it would work for 64bits.
Download script only: 81-Xposed.sh
Or flashable zip, see post attachment below:
Click to expand...
Click to collapse
I have some questions, please forgive my lack of knowledge.
How do you get the script into the addon folder in the CM nightly?
Also, do you know if it can be used in conjunction with Cyandelta updater?
Thnx, Alex
alexdpaul said:
I have some questions, please forgive my lack of knowledge.
How do you get the script into the addon folder in the CM nightly?
Also, do you know if it can be used in conjunction with Cyandelta updater?
Thnx, Alex
Click to expand...
Click to collapse
Just flash the zip in the fist post. This will install the script in the right place in your phone. After that you can flash Nightlies like you always do, manually or with Cyandelta (I use Cyandelta myself too).
You just have to flash the script once, it will also survive future flashes.
Sent from my OnePlus One using Tapatalk
adlx.xda said:
Just flash the zip in the fist post. This will install the script in the right place in your phone. After that you can flash Nightlies like you always do, manually or with Cyandelta (I use Cyandelta myself too).
You just have to flash the script once, it will also survive future flashes.
Sent from my OnePlus One using Tapatalk
Click to expand...
Click to collapse
Thanks, flashed the zip, just need to wait for the next nightly to see if it works for me.
Thanks for your quick reply!
You're missing at least one file (app_process32):
Code:
localhost bin # ls -l |grep app_
lrwxr-xr-x 1 root shell 13 Feb 23 20:53 app_process -> app_process32
lrwxrwxrwx 1 root root 32 Feb 24 17:36 app_process32 -> /system/bin/app_process32_xposed
-rwxr-xr-x 1 root shell 13664 Feb 23 20:53 app_process32_original
-rwxr-xr-x 1 root shell 72757 Feb 24 17:36 app_process32_xposed
DualJoe said:
You're missing at least one file (app_process32):
Code:
localhost bin # ls -l |grep app_
lrwxr-xr-x 1 root shell 13 Feb 23 20:53 app_process -> app_process32
lrwxrwxrwx 1 root root 32 Feb 24 17:36 app_process32 -> /system/bin/app_process32_xposed
-rwxr-xr-x 1 root shell 13664 Feb 23 20:53 app_process32_original
-rwxr-xr-x 1 root shell 72757 Feb 24 17:36 app_process32_xposed
Click to expand...
Click to collapse
I've been flashing various nightly and Xposed has survived all of them, so it works for me, no file missing as far as I can tell.
On my phone app_process32 is modified by SuperSu, and flash survival is handled by SuperSu script in addon.d (99-supersu.sh).
Sent from my OnePlus One using Tapatalk
adlx.xda said:
/system/addon.d/ is a folder in CM roms where the user (and sometimes apps) can put scripts that will be run when you flash a new version of the rom.
Tipically those scripts are used to backup system apps, and their files, so that they can survive a format and reflash.
For example, this is how you would keep SuperSU (root), Avast Agent,...
I made the script below so that @rovo89's Xposed for Lollipop will survive (that is keep it installed) when I flash a new CM12 nightly.
Tested on my phone (32bits), just flashed latest CM12 nightly, wiped cache and dalvik-cache and the phone rebooted fine (and Xposed was still working). Tested on TWRP 2.8.5.1, might not work with other recovery.
Warning: It's for Xposed for Lollipop only. It work as of today. It might not work later with new future versions of Xposed. Also not sure it would work for 64bits.
Download script only: 81-Xposed.sh
Or flashable zip, see post attachment below:
Click to expand...
Click to collapse
Work for me cm12(32bit) thx
Nice, it's work on my Xperia Z1 with CM12.
Not working for me on Oneplus One CM12, the XposedBridge.jar survives but not app_process, the OnePlus One has an ARM v7, so what do I need to modify in the config file?
card13 said:
Not working for me on Oneplus One CM12, the XposedBridge.jar survives but not app_process, the OnePlus One has an ARM v7, so what do I need to modify in the config file?
Click to expand...
Click to collapse
I also have a Oneplus One.
Do you have SuperSu? Go in SuperSu settings and check if you have installed the script to survive flashes.
Sent from my OnePlus One using Tapatalk
I don't have SuperSu, haven't used that since the nightlies became official and builtin su was working properly.
card13 said:
I don't have SuperSu, haven't used that since the nightlies became official and builtin su was working properly.
Click to expand...
Click to collapse
Ok, that's the reason why it fails for you then... I'll have to work that our then.
Sent from my OnePlus One using Tapatalk
How unistall this?
Rygiel98 said:
How unistall this?
Click to expand...
Click to collapse
Uninstall? Remove the file /system/addon.d/81-xposed.sh from your system.
Sent from my OnePlus One using Tapatalk
card13 said:
Not working for me on Oneplus One CM12, the XposedBridge.jar survives but not app_process, the OnePlus One has an ARM v7, so what do I need to modify in the config file?
Click to expand...
Click to collapse
Here is a fixed version.
Added entry:
[...]
list_files() {
cat <<EOF
bin/app_process32
bin/app_process32_xposed
bin/dex2oat
bin/oatdump
[...]
Click to expand...
Click to collapse
Special thanks to @funkyboy1281, @lentm, @macboy3000 for helping getting this work. As far as I can tell, this is the easiest and most straight forward instruction set for getting Android Pay to work on the latest version of Pure Nexus, Chroma, or OMNI Rom
Clean Flashing
Download the appropriate Rom.
Pure Nexus DiscussionChroma DiscussionOMNI (no link available, sorry)
Download Pure Nexus Dynamic Gapps 2-3-16 (Very important, you cannot use 15-3-16 or later). Yes, even if you use Chroma or OMNI, these Gapps should work for you. Link
Download the unSU script for completely unrooting before installing systemless root. Link
Download SuperSU 2.68 (or higher) Link || Discussion
Advance wipe in recovery all but internal storage
Install the ROM, gapps, and unSU
Optional: Install custom kernel
In TWRP, under advanced, go to terminal and type the following:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Note: You may also do this using ADB in recovery (adb shell, and then enter the same commands. This is much easier in my opinion, and is the method I used.
Flash 2.68 beta in TWRP
Fully reboot, go through initial device setup
Verify in SuperSU that you cannot install SU to the system. This will verify that we are using the systemless root option
Download SafetyNet Helper and make sure it passes
Install Android Pay and profit!
Dirty Flashing
Verify that SafetyNet still passes in Android.
Verify in Android that /data/.supersu is still present and contains the appropriate options (see clean flashing). You may also verify in recovery by going to terminal commands and entering in:
Code:
cat /data/.supersu
Install the updated ROM (do not reinstall gapps unless your ROM builder specifically tells you to do so. Pure nexus does not require a reflash)
Optional: Install unSU. This was not necessary on PureNexus, but I cannot be sure for other roms. It shouldn't hurt anything to flash.
Optional: Install custom kernel
Install SuperSu 2.68 (or higher)
Check SafetyNet Helper and make sure it still passes
FAQ
Q. Can I still install and use AdAway?
A. Yes. You must first install something in recovery before installing AdAway. See the discussion Thread. You should be installing v3.1 of the app after you install the recovery zip.
Q. Can I still use V4A?
A. Yes. I do not use this however, but it has been reported that nothing special needs to be done.
Q. Can I change the screen density?
A. We have not found a way to do this without tripping Safety Net
..
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
MrBrady said:
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
Click to expand...
Click to collapse
Noted, thank you! Still hoping some of the lucky folks that have it working can help us out here.
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
MrBrady said:
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
Click to expand...
Click to collapse
You (should) be able to change the density through adb using
Code:
adb shell wm density DPI
with dpi being what you want, or if you have root you can do that from a terminal emulator, just remove the adb shell part.
I tried the 2nd method without formating data in different combos to no avail, still hesitant to wipe my internal sdcard, it shouldn't be that hard man, will follow this thread
anyone know other aosp ROMs that have AP working outside of pure nexus?
Sent from my Nexus 6 using Tapatalk
Following the steps in the top most instructions in the OP...
1) Pure Nexus 3/8 does not have root out of the box, so the Unroot step was not needed.
2) TWRP did not show any files/folders in the /su directory, so the Terminal command didn't work. I booted up the device and did it through the Terminal there instead and then rebooted.
After that, loaded up Android Pay and it says "Android Pay can't be used".
Running SafetyNet reports....
SafteyNet request: success
Response validation: success
CTS profile match: false
Tried different methods, not working for me.
1. Download Pure Nexus 1/03/16 or newer (Layers), the latest PN GApps, UnSU, the latest SuperSU.
2. Backup any important data.
3. Boot into TWRP and wipe everything including internal storage
4. Format data.
5. reboot TWRP with USB-OTG that has fines necessary.
6. Flash Pure Nexus.
7. Flash GApps.
8. Flash UnSU.
9. In terminal I saw I still had a folder /supersu so I deleted that.
reboot. Setup phone with google account. Did not have it restore apps, but did have it restore basic setup from google.
Install Safetynet helper
Still fail CTS Profile Match
Don't know what the people are doing different, but not working for me.
Are you using the PN-Gapps or others?
The updated-unsu is what date?
Thanks!
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
macboy3000 said:
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
Click to expand...
Click to collapse
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
sgloki77 said:
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I formatted everything except internal storage before installing.
macboy3000 said:
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
Click to expand...
Click to collapse
Well I tried this and still no luck
I even tried flashing the modified ROM, gapps, and never flashing SuperSU at all (so my rom wasn't rooted at all), and SafetyNet still gives me a red screen. I really wish I knew what was triggering this for some and how others can make it work.
I tried again using 2.57 SuperSU and Elemental X and still fails. Would someone that got it working be able to post a more detailed log of exactly what steps you're using and exactly what files you're flashing.
MrBrady said:
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
Click to expand...
Click to collapse
This has been my experience as well !
jcrompton said:
This has been my experience as well !
Click to expand...
Click to collapse
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
lentm said:
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
Click to expand...
Click to collapse
Not that I have found, unfortunately. Even via just ADB commands.
Hello
Im going to wipe my entire Marshmallow ROM and go to Nougat.
I used Xposed modules a lot.
But Im intrested in some Magisk things as well so Id like to use both.
First thing after wiping is going to install Snapchat and log on. After that, I need Titanium Backup to freeze and make a backup copy which is where root and/or MagiskSU come in. I want to do it correctly and right so what is the correct way to go upon this in this scenario?
Thank you
riahc3 said:
Hello
Im going to wipe my entire Marshmallow ROM and go to Nougat.
I used Xposed modules a lot.
But Im intrested in some Magisk things as well so Id like to use both.
First thing after wiping is going to install Snapchat and log on. After that, I need Titanium Backup to freeze and make a backup copy which is where root and/or MagiskSU come in. I want to do it correctly and right so what is the correct way to go upon this in this scenario?
Thank you
Click to expand...
Click to collapse
The below order has worked fine for me in the past:
Wipe all partitions (I personally wipe internal storage as well) and format data
Reboot to recovery and copy the zips to the internal storage
Flash ROM
Flash GApps
Flash Magisk/SuperSU
Flash custom kernel
Wipe cache and dalvik-cache
Reboot and setup the phone
Setup Snapchat and backup it's app+data using Titanium Backup once logged in
Reboot to recovery
Flash Xposed
Wipe cache and dalvik-cache
Reboot
shadowstep said:
The below order has worked fine for me in the past:
Wipe all partitions (I personally wipe internal storage as well) and format data
Reboot to recovery and copy the zips to the internal storage
Flash ROM
Flash GApps
Flash Magisk/SuperSU
Flash custom kernel
Wipe cache and dalvik-cache
Reboot and setup the phone
Setup Snapchat and backup it's app+data using Titanium Backup once logged in
Reboot to recovery
Flash Xposed
Wipe cache and dalvik-cache
Reboot
Click to expand...
Click to collapse
Looks like a good solid order to get both Magisk and Xposed working on Nougat. Ill try to do that.
riahc3 said:
Looks like a good solid order to get both Magisk and Xposed working on Nougat. Ill try to do that.
Click to expand...
Click to collapse
You can also install systemless Xposed through magisk manager. It's a magisk module. Then you can easily turn off Xposed if you need to pass safetynet.
You can do it after setting everything else up. Then go into magisk manager and install Xposed (for your correct API) and the systemless Xposed installer APK (it's in the description in magisk manager for Xposed magisk module) then reboot, wipe cache and dalvik, and boot system. Some have said they had to install Xposed APK after first boot after installing framework in magisk.
madbat99 said:
You can also install systemless Xposed through magisk manager. It's a magisk module. Then you can easily turn off Xposed if you need to pass safetynet.
You can do it after setting everything else up. Then go into magisk manager and install Xposed (for your correct API) and the systemless Xposed installer APK (it's in the description in magisk manager for Xposed magisk module) then reboot, wipe cache and dalvik, and boot system. Some have said they had to install Xposed APK after first boot after installing framework in magisk.
Click to expand...
Click to collapse
So:
Wipe all partitions and data
Reboot to recovery and copy the zips to the internal storage
Flash ROM
Flash GApps
Flash Magisk/SuperSU
Flash custom kernel
Wipe cache and dalvik-cache
Reboot and setup the phone
Setup Snapchat and backup it's app+data using Titanium Backup once logged in
Open Magisk Manager
Install Systemless Xposed
Reboot to recovery
Wipe cache and dalvik-cache
Reboot
Install my Xposed modules
Thats your recommendation?
riahc3 said:
So:
Wipe all partitions and data
Reboot to recovery and copy the zips to the internal storage
Flash ROM
Flash GApps
Flash Magisk/SuperSU
Flash custom kernel
Wipe cache and dalvik-cache
Reboot and setup the phone
Setup Snapchat and backup it's app+data using Titanium Backup once logged in
Open Magisk Manager
Install Systemless Xposed
Reboot to recovery
Wipe cache and dalvik-cache
Reboot
Install my Xposed modules
Thats your recommendation?
Click to expand...
Click to collapse
To make an very full clean flash to get:
- SU access
- Custom kernel
- GApps
- Magisk
- Xposed
- Snapchat
Yeah :good:
riahc3 said:
So:
Wipe all partitions and data
Reboot to recovery and copy the zips to the internal storage
Flash ROM
Flash GApps
Flash Magisk/SuperSU
Flash custom kernel
Wipe cache and dalvik-cache
Reboot and setup the phone
Setup Snapchat and backup it's app+data using Titanium Backup once logged in
Open Magisk Manager
Install Systemless Xposed
Reboot to recovery
Wipe cache and dalvik-cache
Reboot
Install my Xposed modules
Thats your recommendation?
Click to expand...
Click to collapse
Don't forget the modified Xposed installer/manager APK. When you click on Xposed in magisk to get description the link for it is there. And I think you flash magisk zip after your custom kernel (because it modifies boot.img). And setup all your other stuff before Xposed (like opening magisk and make sure it's good). First boot after installing Xposed can take a while, it has to optimize pretty much everything. But everything else looks good.
Im just flashing a ROM (which I believe already has the custom kernel)
Very good list, but I have doubt about this order:
madbat99 said:
And I think you flash magisk zip after your custom kernel (because it modifies boot.img).
Click to expand...
Click to collapse
Because in first post in Magisk thread is stated:
Magisk said:
If you plan to flash a custom kernel, flash it AFTER installing Magisk.
Click to expand...
Click to collapse
thanks
I've installed AOSP Extended 8.1.0 Oreo on the Axon 7. I'm also using @Chainfire's Aroma SuperSU Config zip to configure systemless mode. I've set it to sbin mode, with dm-verity disabled, encryption and forced encryption disabled for the data partition, factory reset protection enabled, xbin su binary binding disabled, and SELinux set to permissive. /system, /data, and /cache are formatted as ext4. I'm not using any custom kernels, just what was included with the ROM. When I try to boot, my device momentarily sits on the "Your device is unlocked and can't be trusted" screen. Afterwards it reboots to the bootloader menu and then into TWRP. No matter how many times I try booting this cycle repeats. I think that maybe SuperSU needs an update to address Oreo compatibility issues. I really don't want to use Magisk.
AnonVendetta said:
..... I really don't want to use Magisk.
Click to expand...
Click to collapse
Did you try to get it working with Magisk?
@NLBeev: Magisk does work, and I'm using it, but I would rather use SuperSU. I will ditch Magisk for SuperSU in a hot minute if someone can help me get it working.
On a side note, the ROM won't boot with Phh's Superuser installed either. I get exactly the same behavior. It seems Oreo has changed a lot of stuff.
AnonVendetta said:
[MENTION=528201]...Magisk does work, and I'm using it, but I would rather use SuperSU. I will ditch Magisk for SuperSU ...
Click to expand...
Click to collapse
There are many changes in Oreo that affect kernel and system files.
In Nougat SuperSU works great and also with rootswitch.
Unfortunately SuperSU is not updated since sr5.
I've been able to get SuperSU fully working on Oreo by:
1. Flashing SuperSU Aroma zip and configuring it for system mode installation
2. Then I flashed the SuperSU v2.82 SR5 zip
Afterwards the ROM boots up with no issues and root seems to be working as expected. I know system mode doesn't work with all ROMs, maybe I'm just lucky. Magisk is slow on my ROM and makes everything laggy. With SuperSU everything is smooth now.
AnonVendetta said:
1. Flashing SuperSU Aroma zip and configuring it for system mode installation
2. Then I flashed the SuperSU v2.82 SR5 zip
Click to expand...
Click to collapse
This worked for me and I didn't even know what the hell I was doing.