Related
I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
I just got my unlocked G5 Plus (XT1687) today and I've unlocked the bootloader and installed TWRP and SuperSU.
However, SuperSU seems to be randomly losing root access. It works for a little while, but then I'll get an error in SuperSU about root undetected and I have to reboot back into TWRP and reflash SuperSU. This has happened 3 times so far today.
Has anyone seen this issue in the stock rom? Is there some security process stealthily running in the background that deletes the su binary on a regular basis? I'm running build number NPN25.137-33.
Edit: SuperSU is running in systemless mode
I rooted mine using the Toolkit here yesterday and that afternoon it acted like i lost root. Root checker would say i didn't have root and just constantly flash that it was trying to get permission. I restarted it and it's been fine ever since.
I tried rebooting and it restores root temporarily, but I'm still losing it constantly (no set time interval, but I've seen it lost within a few minutes of a restart). Getting really annoying.
Would flashing one of the modified stock kernels potentially help this?
Hi,
I've the same problem. XT1685
Already done:
- reflash stock
- reflash updated stock
- reflash SuperSu 2.82 SR3 and SR4
Ever the same, after some (short) time the root is lost.
Unrooted from SuperSu app and installed Magisk 14.0: loses root after some moments!
Edit: after some reboots now its working. The root is maintained from 2 days. So Magisk 14.0 works.
Hi.
Here another confirmation. My XT1687 loses root rights once in a while. I’d say it’s about every 3rd day or so.. Simple reboot brings root rights back.
Config:
Build: NPN25.137-83
Kernel: 3.18.31-ElementalX
Root: Magigk 14.0
EDIT: When checking Magisk App I found out that Magisk crashed each time I started Superuser. So, I deinstalled Magisk and re-installed again. No problem ever since.
Always remember to un-optimize Magisk- (or SuperU-) App in battery options! "Boeffla-Doze-Control" also helps to avoid apps from falling asleep.
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
No root losses anymore
Just_a_fan said:
Hello there.
I actually rooted my Moto G5 Plus according to this instructions. I flashed TWRP 3.2.1.0 and the last stabel SuperSU.
I also uninstalled SuperSU over "apps" on Stock Rom and tried to flash Magisk, but this causes in an error while flashing (It says something about "Error 1" and about the path, where the magisk.zip is, for further information I would try to flash again and tell you the whole error).
The latest thing I tried was running the command from highwaystar2699 over the terminal from TWRP, but still I loose root randomly.
Can anybody help? =(
Thanks in advance
FlatD
Click to expand...
Click to collapse
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
G5 Plus Mate said:
Well, I can say, that after some updates of Magisk I don't experience the problem anymore. Neither me nor a friend who has the G5 (not Plus) have ever lost our root since being on Magisk Version 16.0
Maybe you should give Magisk a try...
Click to expand...
Click to collapse
Like I said, installing Magisk returns an error.
Nevertheless, after I ran the command from @highwaystar2699 and canceled the battery-optimization of SuperSU I've got still root after already 5 days of using the phone.
So, thanks for your help, for now =)
I have no ideas that you can solve your problem ...
What I got interested in your post(#8) is "I also uninstalled SuperSU over apps on Stock Rom".
If there is no mistake in my memory, SuperSU have an "unroot" menu, which should be used to uninstall SuperSU.
Did you uninstall by using "unroot" menu?
In any case, I am not sure how to recover the state of your g5plus.
I will not be able to help you. sorry.
highwaystar2699 said:
On StokROM + SuperSU 2.82SR5, I also experienced the same situation.
Running the following command no longer causes problems.
Code:
ln -s /su/bin/su /system/bin/su
Click to expand...
Click to collapse
How and where to run this code? Fastboot or adb terminal?
sudiptoc19 said:
How and where to run this code? Fastboot or adb terminal?
Click to expand...
Click to collapse
Just boot into TWRP and open the terminal (you can find it under "advanced" or "tools", not completely sure right now) and run that command. Maybe you should check where the mentioned su-folder is located right now on your phone, 'cause in my case it was at a different location.
@highwaystar2699: Yeah, afterwards I also realized that unroot-option
So maybe I have to unroot with that option and retry to install magisk. I will try that maybe, if I should loose root again. Or when the next update comes. (I'm a little afraid about that. Sounds difficult to OTA-update after rooting your G5 Plus...)
Either way: Thanks for your help! If I try something, I will report about it here
Super SU working for G5 plus. I don't think so. It has some problems. Bootloops are frequent.
Sooooo, hello again all! @highwaystar2699: I lost root again after one hour when I had to reboot the phone so I just thought about: "Why don't give it a try now?"
So I flashed the superSU again in TWRP to get root, startet the SuperSU app and choose "Unroot". I was asked if I want to unroot because of an OTA update, which I answered with "no". The app closed and root was gone.
I rebooted into recovery and tried to install the magisk 16.0 zip aaaaaaannnnd...
...got Error 1 again.
At the point "Unmounting partitions", TWRP says
"Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v16.0.zip'"
Now I'm back to superSU again. Damn, I don't know whats wrong here =(
Short edit for @Yeshu_bablu: Yes, after installing superSU, you've got 2 to 3 bootloops. But only the first time. After it's installed, the phone boots normal.
So, according to you... Which is better? SuperSU or Magisk?
SuperSU is obsolete, twrp you need latest version 3.2.1.0 or higher number if updated.
Once twrp installed you can install the rom of your choice with or without gapps package of your choice.
Then you can install magisk 16.3 for root and modules if wanted.
Yeshu_bablu said:
So, according to you... Which is better? SuperSU or TWRP?
Click to expand...
Click to collapse
SuperSu is root, TWRP is recovery, 2 different things.
[email protected] said:
SuperSu is root, TWRP is recovery, 2 different things.
Click to expand...
Click to collapse
I'm sorry, SuperSu or Magisk?
Short update and big thanks to @highwaystar2699 and @Wolfcity.
After I completely lost root with SuperSU, I tried to install Magisk but failed everytime with already known Error 1.
But finally, after I got a stock boot.img and flashed it and instantly (!) installed Magisk after flashing the boot.img, the phone startet normal and now I've got root without problems.
FIY: When I only flash the boot.img and don't root it in TWRP, the phone keeps bootlooping.
So, to give @Yeshu_bablu an answer: Magisk is better. SuperSu only make problems with Moto G5 Plus. Magisk works like a charm.
After a long time using SuperSU, I switched to Magisk yesterday, for it's modules and of course Magisk Hide. So, starting with a full stock B414 rom, I unlocked my BL, installed OldDroid's TWRP and flashed Magisk 16.0 .
Everything went fine, I'm able to give root access to my apps. What I'm trying to do now is passing SafetyNet check.
I downloaded SafetyNet "attest" from the store and ran a test -> Basic integrity : false and CTS profile match -> false :crying:
Reading various tutorials, I enabled magisk hide, selected a few google apps to hide (store, services framework) , enabled Host systemless and magisk Core (rebooted my phone between these changes), cleared Store data. Regardless of what I've done, I keep failing at SafetyNet check. Did I miss something basic ? Did someone manage to pass safetynet on a P9 Lite with Nougat ?
EinderJam said:
After a long time using SuperSU, I switched to Magisk yesterday, for it's modules and of course Magisk Hide. So, starting with a full stock B414 rom, I unlocked my BL, installed OldDroid's TWRP and flashed Magisk 16.0 .
Everything went fine, I'm able to give root access to my apps. What I'm trying to do now is passing SafetyNet check.
I downloaded SafetyNet "attest" from the store and ran a test -> Basic integrity : false and CTS profile match -> false :crying:
Reading various tutorials, I enabled magisk hide, selected a few google apps to hide (store, services framework) , enabled Host systemless and magisk Core (rebooted my phone between these changes), cleared Store data. Regardless of what I've done, I keep failing at SafetyNet check. Did I miss something basic ? Did someone manage to pass safetynet on a P9 Lite with Nougat ?
Click to expand...
Click to collapse
Hello,
i used it some times ago...
Try to enable usb-debugging together with magisk/hide,
then reboot and see what happen.. ( this is what i done )
All the best
Thanks for your answer ! However, it didn't changed anything, safetynet check failed. Interesting fact, after rebooting, both magisk hide and usb debugging are disabled... Is this normal ?
EDIT : It's more than that, usb debugging gets disabled as soon as I quit settings
managed to fix this using another xda thread, but safetynet keeps failing and magisk hide is always disabled on startup
https://twitter.com/topjohnwu/status/1029239685338419200
Hi. I have a safety net issue after following the rooting tutorial on this post. (to be precise, safety net was fine, i got the issue when i tried to install edexposed)
I've got a "cts profile mismatch".
I tried to get rid of it, uninstall magisk, wipe system, but it's still there.
I would like to try to make a factory reset using an ota file, but i can't find my version of the system.
I was on SKYW1907110OS00MP3 and i updated to SKYW1911010OS00MP5. Does someone have a factory ota update.zip for one of this two version ?
There is the MagiskHide Props Config module ( https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228 ) for fixing this kind of issue, but there is no build-in fingerprint for the blackshark 2.
I tried to get one within an OTA file, but i can't find it.
I really don't know if i can do a << adb push stock_boot_b.img /dev/block/bootdevice/by-name/boot_b >> to restore the unpatched version of my rom or if that will brick my phone (or maybe do nothing to solve my issue)
If anyone have an idea, it would be great. Thanks.
Flashing the stock boot image of the ROM currently installed in your device will not cause bootloop. Tried and tested.
To pass Safetynet, you don't need to flash MagiskHide Props Config module. It doesn't really make your device pass Safetynet at all.
To pass Safetynet with EdXposed, follow these steps:
1. Make sure you enable Magisk Hide in the Magisk app.
2. Rename your Magisk package (optional - for banking apps).
3. Flash the latest EdXposed module from this repo: https://ci.appveyor.com/project/ElderDrivers/edxposed/history (the EdXposed in the Magisk app is outdated, and it breaks Safetynet), and the latest EdXposed Manager here: https://github.com/ElderDrivers/EdXposedManager
4. Go to EdXposed Manager's settings and enable App List mode and Pass SafetyNet options, then reboot your device.
Now, the trickiest part (sort of):
5. Clear Google Services Framework, Google Play services, and Google Play Store's data, then check for Safetynet. Sometimes, it still fails after your first attempt so just repeat this step until it passes Safetynet.
That's all. All of these worked 100% on my CN-converted-to-Global Black Shark 2 device. Hope it will work on yours, too.
Woot, thanks a lot, i will try that right away.