Hi guys, I'm actually on stock rom (android 6.0.1) with Androplus kernel v40 on my Sony Z5 Compact.
I currently have SuperSU 2.78 SR3 and Xposed systemless v86.2. I also have Magisk v8 installed.
I want to get rid of Magisk (I know it's possible), but when I flash Magisk Uninstaller zip, my root is gone. If I flash supersu again (any version, even 2.76),it tries to install systemless but it's not installing su binaries (a problem with ramdisk).
I can't uninstall Xposed ; if I have Magisk installed, Uninstaller is working but after reboot, xposed is still here. If I uninstall Magisk, Uninstaller doesn't work and ask for Magisk.
I've tried to flash again Androplus, but I still need to flash Magisk in order to avoid ramdisk error.
I've tried to restore Boot from the Stock Backup (backup done just after clean flash of Android 6.0.1) with TWRP : I got stuck on Android Startup (after the app optimization), so I go back to today's Boot backup.
What can I do to uninstall Magisk and use systemless root? Use another kernel?
Thanks a lot
Bump please
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Hi, I've tried to update to Magisk v9 but if I do so, I can't install supersu (sr1 3 or 4).
What can I do to REMOVE Magisk and use systemless root alone ?
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Hi, I've tried to install v7 or v9, but when I Uninstall, v8 is still here.
Which files/folder must I remove to get rid of magisk v8?
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Hey
What can I do to remove Magisk v8? Remove files with root Explorer?
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Related
So I'm currently rooted using Systemless SuperSu 2.67 which I flashed using TWRP 3.0.0 (installed by Odin 3.11). I've been trying to install the Systemless Xposed Framework (required for me since I'm using a Samsung Galaxy S7 G930W8). Regardless of whether I use Rom Manager, Flashfire or TWRP to install the Systemless Xposed Zip, the process always completes but after my phone reboots the Xposed Framework is not installed (shown as not active or installed in the Material Design Installer) and my root no longer works aswell. Is there any way for me to install the Xposed framework on my phone without having it fail and losing my SuperSU root?
Thanks.
(posted previously in the wrong section)
Anyone using systemless root + xposed and android pay?
I was able to use systemless root with magisk v3 + phh superuser + systemless xposed without any problem however flashfire was not working since I cannot also make chainfire supersSU to work in s7 edge...
( releases after v3 up to v6 are not supporting well samsung - I verified though with the android version G935FXXU1BPH6 which also might be causing issues).
However after updating this version G935FXXU1BPH6 it seems to cause issues with TWRP and only boots to the last (twrp-3.0.2-3-hero2lte.img) and now I cannot go systemless at all because magisk v3 is not working aswell, root simply is not recognized.
SO basically now I'm using stock phone as I wanted to use android pay.... any ideas or anyone with any sucess?
im using v6 without problems. BUT you have to root with cfautoroot and unroot with superSU one time. i think that superSU changes something in boot.img that magisk needs to work ...
after that you have to use phh superuser.
pogo work
Flashfire will not
ok
inteks said:
im using v6 without problems. BUT you have to root with cfautoroot and unroot with superSU one time. i think that superSU changes something in boot.img that magisk needs to work ...
after that you have to use phh superuser.
pogo work
Flashfire will not
Click to expand...
Click to collapse
This works fine as does systemless xposed etc. Did you pick the option to restore stock boot.img when you uninstalled SuperSU?
My banking apps can still detech phh's root. Wondering if the modified boot from SuperSU is the cause. Might just need to wait for Magisk V7 which shouldn't need this workaround.
Galactus said:
This works fine as does systemless xposed etc. Did you pick the option to restore stock boot.img when you uninstalled SuperSU?
My banking apps can still detech phh's root. Wondering if the modified boot from SuperSU is the cause. Might just need to wait for Magisk V7 which shouldn't need this workaround.
Click to expand...
Click to collapse
No. Restore stock boot.img doesn't work for me
Gesendet von meinem SM-G935F mit Tapatalk
Install xposed and KoalaCoak you don't need to be unrooted
That is only for ANZ and Westpac internet banking, not Android Pay? Is that correct? Have you got it working for Android Pay?
Cheers.
playingbball20 said:
Install xposed and KoalaCoak you don't need to be unrooted
Click to expand...
Click to collapse
What bank app are you using? And can you use Android pay?
Cheers in advance
Dear,
I am new to s7 edge
I have g935FU1BPI6 installed .
I would like to install systemless root/xposed/recovery,
Is it possible?
Please guide,
Thanks in adv
earth08 said:
Dear,
I am new to s7 edge
I have g935FU1BPI6 installed .
I would like to install systemless root/xposed/recovery,
Is it possible?
Please guide,
Thanks in adv
Click to expand...
Click to collapse
Read up on Magisk. Systemless Xposed is pointless as you can't bypass safetynet
If we get update and if we update.
Is it require to wipe data after flashing twrp?
I am not able to root my Z5 E6653 running the new .160 build
I have already rooted it when Lollipop, Marshmallow and 7.0 was installed but this time it is pretty weird!
bootloader is unlocked of course!
I flashed the patched kernel and TWRP 3.1.1
then i flashed magisk v12 and as SU binaries I chose SuperSU v82...
after booting and opening the SuperSu app it wants me to grant root access for itself, it says "greant for SuperSu" and then the app freezes and keeps crashing :/ reinstalling did not help, is v82 not compatible with 7.1.1 sony rom?
What kernel do you flashed
jpl8910 said:
What kernel do you flashed
Click to expand...
Click to collapse
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
First supersu then Magisk, otherwise is wrong.
sceryavuz said:
First supersu then Magisk, otherwise is wrong.
Click to expand...
Click to collapse
Okey thanks
freaky2xd said:
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
Click to expand...
Click to collapse
sceryavuz said:
First supersu then Magisk, otherwise is wrong.
Click to expand...
Click to collapse
Magisk has root built-in, there is no reason to flash SuperSU if you've successfully flashed Magisk. You either flash Magisk OR SuperSU, not both.
Devo7v said:
Magisk has root built-in, there is no reason to flash SuperSU if you've successfully flashed Magisk. You either flash Magisk OR SuperSU, not both.
Click to expand...
Click to collapse
Not for noob. If you want to use SuperSU with Magisk Modules, then you have to flash both with this order(SuperSU, Magisk).
Already mentioned on my thread..
Magisk is a module manager like Xposed. If you dont know..
sceryavuz said:
Not for noob. If you want to use SuperSU with Magisk Modules, then you have to flash both with this order(SuperSU, Magisk).
Already mentioned on my thread..
Magisk is a module manager like Xposed. If you dont know..
Click to expand...
Click to collapse
Exactly
At the moment I am using magisk v12 only though
root fail
freaky2xd said:
the patched .160 kernel for e6653. I reflashed the 7.1.1 ftf and wiped everything except data so my system and stuf are back to normal, flashed the kernel and recovery again and this time I only flashed magisk v12 without SuperSu v82
now root is working
it seems like magisk v12 in combination with supersu v82 does not work ^^
Click to expand...
Click to collapse
hello
i have xperia z5 running version 7.1.1 i have tried alot to root it but i couldnt please help me
thanks
Hi all,
I have lost the ability to root my EMUI 5.0 v360 rom using either Magisk or SuperSU with the TWRP designed for EMUI 5.0.
I had SuperSU installed and working but I wanted to try Magisk for the Magisk Hide feature.
I uninstalled SuperSU through the app settings. It succeeded.
Then I installed Magisk. It also succeeded.
That was fine, and I noticed that Magisk has its own internal BusyBox so I figured out would uninstall BusyBox that I had installed and use that.
But from that moment I lost root.
Then I tried uninstall of Magisk using its flash able uninstall. And then reinstall it.
Root was not activated by reinstalling even though Magisk was successfully installed.
The I uninstall Magisk completely to go back to SuperSU.
The flashable SuperSU installs fine. But the app does not recognise that the binaries are installed at all.
So right now I can patch the relevant files in twrp but the system no longer recognises root.
I don't know how this could happen from uninstalling BusyBox. But that's where I am stuck at...
Sent from my Honor 6x using XDA Labs
Man with every little thing you do, you need to take a backup from TWRP. Now the only solution to your problem is to reflash your firmware.
Sent from my Honor 8 using XDA Labs
Official Xposed Working perfectly,
Root your MI A1 by following this instructions
https://forum.xda-developers.com/mi-...pdate-t3681024
Please carefully watch these steps to root..your phone...
Then we are gone for xposed..
Download the xposed installer.zip
http://dl-xda.xposed.info/framework/sdk25/arm64/
Flash the zip file using Flashfire app...then install,
XposedInstaller_3.1.2.apk
https://forum.xda-developers.com/showthread.php?t=3034811
Not working.
It's working perfectly...
Screenshot prof...
is this module works for you?
they say it works for Nougat too
https://forum.xda-developers.com/xposed/modules/mod-fingerprint-enabler-t3411066
when screen is locked by third party app (some launcher, 3rd party tile, etc) fingerprint on Mi A1 cannot unlock the phone.
that module enables that.
Tried as you wrote: flashed the xposed zip file using flashfire -> reboot -> xposed framework wasn't installed.
Then I tried to install xposed framework using the xposed app -> worked
=> Just install xposed installer apk and install xposed framework using the app.
Edit: I forgot that there was this thread: https://forum.xda-developers.com/mi-a1/how-to/install-xposed-flashfire-recovery-t3685713
https://forum.xda-developers.com/mi-...pdate-t3681024
link not working
its worked used xposed installer v3.1.2
gavitybox work fine too....
Yup gravity box works very well. Pleased with the way development is happening & being an AOSP we will get our fair share.
thanks for sharing~
AndroidAdvisor said:
Official Xposed Working perfectly,
Root your MI A1 by following this instructions
https://forum.xda-developers.com/mi-...pdate-t3681024
Please carefully watch these steps to root..your phone...
Then we are gone for xposed..
Download the xposed installer.zip
http://dl-xda.xposed.info/framework/sdk25/arm64/
Flash the zip file using Flashfire app...then install,
XposedInstaller_3.1.2.apk
https://forum.xda-developers.com/showthread.php?t=3034811
Click to expand...
Click to collapse
It does not work, when i flashed it via flashfire, i got still black screen for over 30minutes, so i gave up and forced it to reboot...
Then i've got bootloop.....
When i tried to install it via xposed app i got this error:
ves626 said:
It does not work, when i flashed it via flashfire, i got still black screen for over 30minutes, so i gave up and forced it to reboot...
Then i've got bootloop.....
When i tried to install it via xposed app i got this error:
Click to expand...
Click to collapse
i think it's was magisk that caused error.
i used supersu for root.
Sent from my Mi A1 using Tapatalk
ves626 said:
It does not work, when i flashed it via flashfire, i got still black screen for over 30minutes, so i gave up and forced it to reboot...
Then i've got bootloop.....
When i tried to install it via xposed app i got this error:
Click to expand...
Click to collapse
this is because ur have rooted ur cell with magisk
root it in supersu
Hellrazoraj said:
Yup gravity box works very well.
Click to expand...
Click to collapse
That was everything I was looking for. Thanks for the advice
AndroidAdvisor said:
Official Xposed Working perfectly,
Root your MI A1 by following this instructions
https://forum.xda-developers.com/mi-...pdate-t3681024
Click to expand...
Click to collapse
Just wanted to point out that the link you've given there comes out as "https://forum.xda-developers.com/mi-...pdate-t3681024" and leads to a 404.
guys i have flashed magdisk and it works and now im trying to flash systemless xposed via recovery and i get this:
/system could not be mounted
Error installing zip file...
faddys123 said:
guys i have flashed magdisk and it works and now im trying to flash systemless xposed via recovery and i get this:
/system could not be mounted
Error installing zip file...
Click to expand...
Click to collapse
Hey buddy, I will root my phone & share the steps(screenshots) with you by tonight
Hellrazoraj said:
Hey buddy, I will root my phone & share the steps(screenshots) with you by tonight
Click to expand...
Click to collapse
i had to flash a file called sysmount and then i flashed the systemless xposed but it told me that i need magdisk v14 or higher :/
ArchitDewari said:
this is because ur have rooted ur cell with magisk
root it in supersu
Click to expand...
Click to collapse
This is the answer to all having magisk and trying to get Xposed
I just did the following procedure:
flashed official rom with miflash,
booted to rom,
intalled second october OTA update (75mb),
booted twrp with "fastboot boot recovery.img",
and then:
installed magisk 14.4
installed magisk manager,
installed systemless xposed module from within magisk manager,
and finally installed material design xposed installer
(with reboot between each step)
and finally i have magisk root and working xposed.
If i select magisk core only mode (witch disables magisk modules) it passes safetynet and theoretically i can install OTA updates (i think xposed -systemless or not- does not pass safetynet)
ilpanos said:
I just did the following procedure:
flashed official rom with miflash,
booted to rom,
intalled second october OTA update (75mb),
booted twrp with "fastboot boot recovery.img",
and then:
installed magisk 14.4
installed magisk manager,
installed systemless xposed module from within magisk manager,
and finally installed material design xposed installer
(with reboot between each step)
and finally i have magisk root and working xposed.
If i select magisk core only mode (witch disables magisk modules) it passes safetynet and theoretically i can install OTA updates (i think xposed -systemless or not- does not pass safetynet)
Click to expand...
Click to collapse
Can you provide link all of these ?