Develop Bugs

Installed full 3.2.8, help with xposed?

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.

HTC One M9 Nougat Update 4.14.401.7 + Magisk v11.1

Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??

phen0m2016 said:
Hi,
I currently have my HTC One M9 with the following installed:
TWRP v3.0.2-0
Magisk v10.2
Magisk Manager v4.1
phh's SuperUser 2.0 [Beta 11]
And it's running: Android 6.0 (Marshmallow)
Now, I've received the OTA update notification for Android 7.0 (Nougat) - 4.14.401.7. I'm assuming that if I do the update, it will overwrite both my boot and recovery partitions, and therefore my phone will return to a stock status.
My question now is: Has anyone tried installing TWRP + Magisk v11.1 on this phone, running Android 7.0 (Nougat) - 4.14.401.7 (Stock)?? And, has it worked fine??
Click to expand...
Click to collapse
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.

computerslayer said:
I have the developer edition (4.23.617.1) but Nougat works fine with TWRP (3.0.3-0_unofficial) and Magisk 11.1. The new MagiskSU has worked fine as a root solution and within Magisk Hide - but some users have reported that it is necessary to disable/enable Magisk Hide, or even reboot to pass a SafetyNet check. For me, disabling & re-enabling after install worked fine - and was necessary only immediately after install.
Click to expand...
Click to collapse
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??

phen0m2016 said:
Hey computerslayer. Thanks for the reply!
So in order to do a clean install of the Nougat Update (4.14.401.7) + Magisk v11.1, I should do the following:
1.- Uninstall phh's SuperUser using Magisk Manager > Modules
2.- Unistall Magisk Manager using TWRP > Magisk Uninstaller
*.- (Unistalling TWRP wouldn't be necessary as the Update rewrites the Recovery Partition)
3.- Apply the Nougat Update
4.- Reinstall TWRP
5.- Reinstall Magisk
6.- Finished
Is this procedure OK??
Click to expand...
Click to collapse
Honestly, I'm not sure. I don't know if it is possible to upgrade between Android versions via OTA with TWRP installed - I vaguely remember some limitations on OTAs and TWRP. Best to check the official TWRP thread and the readme thread to be sure.
Similarly, I'm not sure about a clean install of Magisk. I've only been using it for about a month so I'm not confident in offering advice about uninstalling - especially since giving bad advice could end up with you not passing SafetyNet because I missed some basic step. I recommend checking out the Magisk forums.
I'm sorry I can't be of more help.

How to install Magisk & Xposed? I keep getting bootloops.. "no digest file found"

How to install Magisk & Xposed? I keep getting bootloops.. "no digest file found"
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.

smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
I'm not sure about Oreo I think you can but you can't get certain modules or things like Xposed but double check that cuz I'm not sure
Secondly if you wanna flash 14.2 or 14.3 at the bottom of the magisk post where you download it will have the different versions to choose from any version after 14.0 supports the pixel
try flashing magisk by itself and see if that helps I know when I flash it with anything else it just doesn't show up and doesn't work but if you want when it bootloops flash the uninstaller and flash your boot image and that will fix the bootloop but do it again copy the log from twrp and put it on your computer and upload it here it will say exactly where it fails and what's wrong with it so we can help better

smithilberry said:
So I have a Pixel XL, stock, nougat 7.1.2 (Aug NHGE47Q).
I have tried the following steps:
Boot TWRP 3.1.1-1
Flash TWRP 3.1.1-1
Flash Elemental 7.1.2 kernel
Flash newest Magisk 14.5 beta (since 14.0 doesn't support pixel, right?)
Flash TWRP 3.1.1-1
What am I doing wrong?
I tried it a few times and no good. I did notice it says something about "no digest file found", which I assume is the problem.. ? I tried a combination of things like with and without wiping cache/dalvik. Or not flashing TWRP at the end. I search around and couldn't find updated instructions on this process. Help will be appreciated!
P.S. Also, if I update to Oreo, I can't get Xposed, right? (as in the systemless version via Magisk) because that's the only reason why I haven't updated yet.
Click to expand...
Click to collapse
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.

blanken_ship said:
According to elementalx.org/devices/pixel/ the right elemental kernel is 1.15.
I've done this exact process too and ran into many issues, I would recommend as follows, I've had a lot of success with this. I got Magisk working under 14.2 , twrp 3.1.1-1 , and elemental 1.15. I could not get any of them working correctly with any other versions or in any other order - this worked for me.
reflash stock with flash_all and factory reset
fastboot boot twrp 3.1.1-1
check "never show" and swipe
adb sideload twrp-3.1.1-1.zip
adb sideload VerifiedBootSigner-v8.zip
reboot recovery
sideload again
adb sideload your new ROM here if you want that
adb sideload twrp-3.1.1-1 again, had to do this for PureNexus, cause recovery was overwritten
adb sideload VerifiedBootSigner-v8.zip again
reboot recovery
adb sideload ElementalX-P-1.15.zip
reboot recovery (might not be necessary)
adb sideload Magisk-v14.2(1420).zip - I got this from the Arise Aroma installer package in another thread
adb sideload VerifiedBootSigner-v8.zip again
reboot system, enable systemless hosts and magisk hide on google services framework and play store. magisk hide only works with a kernel that supports it so if your elemental is working you should be fine.
reboot again, then install busybox, I used stericsons from play store. I also installed the selinux switcher for permissive mode. I installed these to get Arise / Viper to work and I think they are required for xposed too.
Magisk modules should work from there, including the xposed installer, but xposed will cause safetynet to fail. I could not get magisk modules to work with 14.3, have not tested other versions, but 14.2 worked.
I did not let twrp install it's apk from recovery mode, or let magisk download it's update, I downloaded both APKs separately.
I remember having many issues with the order of install for magisk versus elemental. I'm pretty sure what worked for me is elemental, then magisk as I put here. but if you run into issues it might have to be magisk then elemental.
Click to expand...
Click to collapse
Thanks for the directions!
However, before I try this, I have one question... what is "VerifiedBootSigner-v8.zip"?
After searching, I see a bunch of information on the May security patch, but nothing talking about the August security patch (which is what I'm on). That being said, does it still apply?

You don't need Xposed, magisk has plenty of modules, but after rooting, flash the verified boot signer to allow for stock boot. It patches the boot image. Android 8 methods fixed this issue

Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.

Mikkey81 said:
Here is how you flash a kernel with the stupid 2 slots LOL...
Rom installed and ALREADY BOOTED INTO the OS That rom.
Reboot to TWRP 3.2.1-0
Flash Kernel and Flash TWRP 3.2.1-0.ZIP followed by rebooting recovery (i usually hit reboot system hold volume down until i get to bootloader and then choose recovery (reboot recovery doesnt always work))
Flash Magisk 15.0 or 15.1 on Oreo and i believe 14.3 and down will work better for Nougat.
Reboot buddy!!! All is good in the world.
Click to expand...
Click to collapse
WAAAAAAIIIIIT!!!! you need to be on Magisk 15.0 just failed multiple times and realized that was the last thing I Updated to 15.1..
Make sure you're flashing 15.0.

Can we get Xposed yet on Oreo with Magisk? I see it says there are 4 different options available in the module section of Magisk. One is labeled "Xposed framework". All the others are labeled "Xposed Framework SDK 25" down to 19. Which one should be used for Oreo?

[How-to] Viper4Android on Pixel XL running Android 8.1

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.

Flashing SuperSU doesn't root my device

Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.

Shakti Panda said:
Hello everyone,
I have the Xiaomi Redmi 5A.
Currently I am running Official Pixel Experience ROM (8.1.0, oreo) https://forum.xda-developers.com/xiaomi-redmi-5a/development/rom-pixel-experience-t3801702 on it. It so happens that when I try to flash SuperSU latest zip, the flashing goes fine but the device doesn't get rooted on checking in a root checker app and also no SuperSU app comes in the app drawer after flashing. I am not sure why this happens. But flashing magisk roots the device. Why not SuperSU?
In the Pixel Experience ROM thread they told to use vendor TWRP and not the Official TWRP but even on vendor TWRP I don't get root access after flashing SuperSU...
Previously I was using Unofficial Lineage OS (14.1, nougat) https://forum.xda-developers.com/xi.../unofficial-lineage-os-14-1-redmi-5a-t3773985 on my device. In Lineage OS when I flash SuperSU I get root access and also the SuperSU app comes in the app drawer. Why not in Pixel Experience?
Is the kernel responsible for this?
Is it something related to "mount"?
I come across this "mount" word in TWRP but I'm not sure what does this mean...
In TWRP while flashing SuperSU I saw "ramdisk restore failed, aborting". What does that mean?
Also is it related to SuperSU being a system-less root software and magisk being a system-based one?
Please help me... It's driving me nuts!:crying:
P.S. I know magisk is better but I want SuperSU, so don't suggest me to use magisk and forget SuperSU.:laugh:
Thanks.
Click to expand...
Click to collapse
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...

Growtopia Jaw said:
Hello,
I don't know exactly what you are encountering but SuperSU should work on this ROM and run fine. I ran this ROM before and SuperSU works fine. I now switched to Magisk because I need ViPER4Android to work on Oreo.
Unless you are running a Treble based ROM, that is a different story. If you are running a Treble based ROM, please refer to this https://forum.xda-developers.com/showpost.php?p=76937637&postcount=24 thread to get root working.
CONTINUE TO READ IF YOU ARE NOT RUNNING A TREBLE BASED ROM,
I need to get some things straight. Android with version 6.0 (Marshmallow) and above (should) and (only) run systemless mode (including SuperSU). I came across a thread and read that root with Marshmallow and above would not work without patching bootloader and make system unmodified.
SuperSU and Magisk are almost the same. Magisk just offers extra module repository and SuperSU just offers root. SuperSU works both in system mode and systemless mode but Magisk only works in systemless mode.
This might help you:
- Do a clean flash (Wipe System, Data and Cache)
- Try using this latest version of SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 (SuperSU v2.82 SR5 released by Chainfire himself)
- If it doesn't work then something might be wrong with the boot partition.
- If you really need root and SuperSU REALLY DOESN'T WORK, (spoiler) try Magisk...
Click to expand...
Click to collapse
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:

Shakti Panda said:
Thanks man.
I'll try that for sure but later i.e., doing a clean flash and trying to flash SuperSU again...
I'll let you know once I've done that.
Thanks again man!!!:angel:
Click to expand...
Click to collapse
Sure, no problem