I tried to install magisk v12 zip but it always fails but says to install supersu soon after. I did that but when i installed magisk manager it said there's no MagiskSU installed and Safety net did not pass as well! Then i tried to uninstall supersu and magisk and flash magisk v12 again but same result again. I tried find how to install MagiskSU online but i can't find any thread about this issue. My aim of installing Magisk is to use MagiskHide for snapchat. Can someone help me pls.:crying:
Are you on SuperSU at the moment?
You will need to unroot using the SuperSU app (That's what I did) before flashing magisk zip.
Secondly, I had trouble with SuperSU + Magisk so I used phh superuser to get it working. I also needed magisk to hide root from snapchat and another banking app and I am able to do so easily.
So, in short,
1. Uninstall SuperSU
2. Flash magisk zip in recovery
3. Flash phh superuser in recovery (People say its optional but I do it anyway)
4. Reboot and benefit
Can you send me a link to download the phh superuser file you used please. When you say uninstall do you mean full unroot? What did you use to uninstall supersu? https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Magisk v12 will auto install root when no root is detected, so u can just clean flash ur rom and install magisk v12 after it, it will auto root
@mharis05 nowadays Phh's Superuser is not "optional": it's unsupported and replaced by the integrated MagiskSU since Magisk v10: look at the official thread, it's declared obsolete.
It would get device in trouble, even if MagiskSU is disabled.
@Bradl79 neither the clean flash is a right way, because:
1) If you're intending a system wipe, it's not resolutive because Magisk is OTA-survival.
2) If you're intending a data wipe, it's an useless waste of time... and data!
You have to run the following zip files: Magisk official uninstaller and UnSU to be sure you've not rooted device in any way.
Then to stay quiet, do a Cache and Dalvik/ART wipe.
At this point, try to reflash Magisk.
I tried that but time and time again when i try to uninstall that SUPERSU it says to flash default boot.img to complete the process. AND Installation "FAILED" Flash Supersu immediately. I did that but still no magiskSU.
At this point try to wipe system and cache/ART, then reflash OOS.
After doing that, go with Magisk.
Related
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.
Anyone know a solution to use banking apps on Rooted Android N since Xposed is not yet available?
The solution is called Magisk ?
After installing, you have at first to enable Magisk Hide, then add the banking apps to the hide list.
Magisk would also be useful for many reasons: survives to OTA (because the system partition is untouched), supports modules like in Xposed (and Xposed too for Android 5.0-6.0), provides a built-in root manager (if you're not a SuperSU user)...
I love Magisk.
To add to the above post, you can't use Magisk for root unless you completely remove SuperSU as your rooting method. You can achieve this by either flashing a cleaner zip or dirty flashing your rom, followed by flashing Magisk.
I have op3 using oos4.0.3 with super su and magisk flashed and checked can u pls guide me through the rest
---------- Post added at 05:09 AM ---------- Previous post was at 05:08 AM ----------
I had supersu before magisk don't know what to do next
BHUSHAN7988 said:
I have op3 using oos4.0.3 with super su and magisk flashed and checked can u pls guide me through the rest
---------- Post added at 05:09 AM ---------- Previous post was at 05:08 AM ----------
I had supersu before magisk don't know what to do next
Click to expand...
Click to collapse
The easiest way to ensure that you have removed SuperSU is to dirty flash your current ROM, then immediately flash Magisk without exiting TWRP. Your phone will remain rooted next time you boot up, though you'll have to re-grant root permissions to each of your root-enabled apps.
Here's what you need to flash in the following order:
1) Stock OOS 4.0.3
2) Magisk 11.1
Simply boot into TWRP, flash 1, wipe cache/dalvik, flash 2, then reboot.
Anova's Origin said:
The easiest way to ensure that you have removed SuperSU is to dirty flash your current ROM, then immediately flash Magisk without exiting TWRP. Your phone will remain rooted next time you boot up, though you'll have to re-grant root permissions to each of your root-enabled apps.
Here's what you need to flash in the following order:
1) Stock OOS 4.0.3
2) Magisk 11.1
Simply boot into TWRP, flash 1, wipe cache/dalvik, flash 2, then reboot.
Click to expand...
Click to collapse
I have SuperSU 2.79sr3 I would like to have it as my root manager
If u flash oos4.0.3 then flash magisk 11.1 then SuperSu 2.79sr3 with edited version which forces systemless mode
Will it work
BHUSHAN7988 said:
I have SuperSU 2.79sr3 I would like to have it as my root manager
If u flash oos4.0.3 then flash magisk 11.1 then SuperSu 2.79sr3 with edited version which forces systemless mode
Will it work
Click to expand...
Click to collapse
I haven't tried flashing SuperSU after Magisk, but I'm pretty sure they aren't compatible.
It will not. Use Magisk or SuperSU, not both.
What about pre-rooted roms?
How can we remove SuperSU and install Magisk?
Flash this unSu script (http://forum.xda-developers.com/attachment.php?attachmentid=3931994&d=1478779893) and Magisk afterwards.
I am running Android 7.0.0 on my P2 rooted with phh Superuser.
However, I want to switch to SuperSU, which as per my understanding (which is very limited in this matter) will happen after I properly uninstall Superuser.
I have researched quite a bit and found out that phh Superuser does not have an inbuilt unroot option unlike SuperSU.
I also flashed the SuperSU .zip file hoping it would delete the current Superuser, but in vain.
I tried to delete su and busybox from /bin and /xbin using Root Explorer but could not find those files in that location.
So I am really helpless now so as what to do in order to have SuperSU installed on my phone.
Try this:
UnSU Script
Flash in Custom Recovery
Videophile said:
Try this:
UnSU Script
Flash in Custom Recovery
Click to expand...
Click to collapse
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
aeonwiz said:
Thanks for replying.
I flashed the .zip you suggested. It deletes the phh Superuser app but does not unroot.
I can tell this because when I flash the SuperSU .zip and install the app, upon launching it says su binary occupied.
And when I reinstall phh Superuser, it works as it did before.
So I'm afraid, it has not solved my problem.
Click to expand...
Click to collapse
Correct, this will only help with removing Root successfully.
You'll then need to root via SuperSu or Magisk or phhSuperuser.
I've made a post about Magisk rooting here that you can follow, this will use Magisk Manager as your Superuser manager.
In that post I mention flashing your original boot.img which will remove any instances of SU you have previously installed if the zip I provided in my previous post does not work for you.
Thanks, I will try that.
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?
I'm on the global rom. Twrp works fine but the moment I install magisk v19.3 or v19.2 my phone bootloops to twrp
Any ideas? I can run magisk uninstaller and it resolves the bootloop.
Have you tried flashing no-verity-force-encrypt zip? It sometimes helps. I often flash it, just to be save. I have no clue what it does but sometimes it helps haha
It's caused by some Magisk module. I had the same problem when I installed ViperFX. Uninstall Magisk, install it again and then try to install modules one by one to find which one is causing the bootloops.
Don't just install uninstall. It only getting you to twrp after installing magisk. Try magisk manager recovery, you can google it and remove all modules you have after installing magisk. You can reboot and install your module again afterwards.
I havent installed any modules. It's a clean install of magisk. I get a popup asking "requires additional Setup".
If I let that run, it reboots after the Setup. And I'm left with it bootlooping.
Again, no modules installed.
How do you install Magisk to get this popup? Is it the direct install from Magisk manager?
I always install the zip in TWRP. Maybe that will solve your problem if you didn't try this method already.
The other fix could be the zip file mentioned by shisaya24. I used to install it on my previous phone to fix bootloops.
maciek90 said:
How do you install Magisk to get this popup? Is it the direct install from Magisk manager?
I always install the zip in TWRP. Maybe that will solve your problem if you didn't try this method already.
The other fix could be the zip file mentioned by shisaya24. I used to install it on my previous phone to fix bootloops.
Click to expand...
Click to collapse
I install via twrp.