Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.
Related
Hello there,
stupid question but Pokemon Go doesn't work with latest version (0.37). It says OS is incompatible (and ROM has been de-rooted, this was verified). I think it's due to Safeynet check that doesn't pass. I will check this tonight !
Using an old AMCHA version (Android 4.4.4), Pokemon Go works great with 0.35... but for now. When this version will be desactived, there will be no way to play anymore.
Is there a ROM, official or custom, working with Pokemon Go 0.37 and future versions ?
Thanks for your help !
seconding this!
i am on N4EliteLite_v15-Final-Note5Edition_i9305_AROMA and the game worked perfectly until the update
i already tried RootCloack with Xposed -- not working
i cannot try magisk method because it requires android 5.0 and i have not found a 5.0 rom with working gps for i9305.
any ideas?
thanks in advance!
Yep, I saw Magisk method but I didn't noticed it was only for Android 5.0+. So I will have to flash a new ROM if I want Pokemon GO + root !
Is there an official Samsung release (or an optimised ROM based on it) that works will v0.37 ?
@Girugamesh : it seems that Ressurection Remix is the best one to choose !
thanks for telling.
unfortunaly i am stuck with magisk manager root toggle turning it self off again
i flashed ressurection remix and followed the guide on androidpolice
i even tried flashing "unSU Script zip"
let me hear if you have any luck with your i9305
I will try to flash new ROM this week-end. I will tell you if I find something.
For your issue, check if all the folders associated with SuperSU are deleted : /system/xbin/su, /data/su.img, /sbin/su etc. There is probably something remaining from previous root.
i finaly made it. the real pain was to get rid of a corrupted supersu installation (es file explorer was not allowed to remove su.bin)
i did supersu unroot, deleted the files you said, also used unSu script.zip BUT since i dont need root, i just started pokemon and it works.
to clarify i am on ressurection remix android6.0 with a i9305
thanks for your help
Great news !
For my wife's phone, I will give a try on the latest official ROM (4.4.4 - I9035XXUFPB1). If it doesn't work, I will go on RRM + full unroot. More news this week-end
hoeni said:
How?
I didn't find a Superuser app, but I deleted everything su related from /system
Flashed magisk, Flashed phh Superuser, installed magisk and phh app, but the toggle keeps reverting to root. Maybe you could provide me with the steps you took
Click to expand...
Click to collapse
I thought that I'd post my solution here. I'm running CM13 right now and I can run the lastest version of Pokemon go.
1. Install Supersu from the play store and select the option full unroot.
2. Flash Magisk and phh's SuperUser.
3. Install the Magisk manager apk and install phh's SuperUser from the play store.
4. Now when you want to play PoGo open the Magisk manager and disable root. Simple as that.
JD. A said:
I thought that I'd post my solution here. I'm running CM13 right now and I can run the lastest version of Pokemon go.
1. Install Supersu from the play store and select the option full unroot.
2. Flash Magisk and phh's SuperUser.
3. Install the Magisk manager apk and install phh's SuperUser from the play store.
4. Now when you want to play PoGo open the Magisk manager and disable root. Simple as that.
Click to expand...
Click to collapse
Yep, I followed the steps provided by the dev of magisk. Seems like that thread gets so overrun by "doesn't work" that individual questions get forgotten haha
I can't think of anything I did wrong, I'm trying to get it to work on an s3 lte and a note 3.
On my main, s7 edge, it works perfectly. But only because I found a rom featuring magisk and phh root in aroma.
I'm reflash the rom right now to start over. Maybe it'll work now.
Edit:
phh's root didn't work.
the modified SU app did however
Edit 2:
Nah
Magisk is working, yes, but PoGo wont let me enter and SafetyNet wont let me pass either.
Ugh getting sick of this.
Tested with official I9305XXUFOB2 and without any root / busybox, everything is OK with Pokemon GO 0.37.1. No need to go further for my part
Lwysiwyg said:
Tested with official I9305XXUFOB2 and without any root / busybox, everything is OK with Pokemon GO 0.37.1. No need to go further for my part
Click to expand...
Click to collapse
damn, it could have been so easy.. good job mate :good:
i will remember this.
EDIT: install stock , unroot with supersu , even pokemon go v0.41.4 works now
Girugamesh said:
damn, it could have been so easy.. good job mate :good:
i will remember this.
EDIT: install stock , unroot with supersu , even pokemon go v0.41.4 works now
Click to expand...
Click to collapse
Hey man, can you help me step by step what you did to unroot and get POGO running on resurrection remix
A few days ago I posted a question about not being able to install any Xposed modules here, so far no one answered: https://forum.xda-developers.com/xposed/xposed-framework-installed-running-t3567230
I thought this problem had something to do with the modules specifically, but it turns out that on my phone, for whatever reason, installing the framework subsequently prevents ALL apps from installing, even those from Google Play itself, displaying a "-504" error.
I see people have asked this question before, but are also not getting answers: https://forum.xda-developers.com/xposed/install-apps-installing-framework-t3430922
Please, if anyone has any idea of why this can be and how to fix it, let me know. Any help will be infinitely appreciated!
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
Hey, thank you for your answer!
I am using a Sony Xperia M4 Aqua E2306, rom is 26.1.A.1.112 Latin America Generic. It is rooted and with TWRP installed accroding to this thread: https://forum.xda-developers.com/m4-aqua/general/root-e2306-m4-aqua-guide-t3270521
I also have a locked bootloader, and it cannot be unlocked, so unfortunately that shuts the door on most rooting options.
I never heard of Magisk before, but from what I'm seeing, it looks it TWRP is required to get root with Magisk, but some kind of root is already required on my phone in order to get TWRP. So I'm not sure how to go about this.
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Anova's Origin said:
If your phone is already rooted, then you can download Magisk Manager application and have it installed it's necessary frameworks through the app itself. You won't be able to use Magisk's root, but you'll still be able to install systemless Xposed and hide it from other apps.
Edit: Ignore all of that actually, I just realized that magisk requires boot image modifications so you have to have an unlocked bootloader to use it.
Click to expand...
Click to collapse
Oh well, thanks anyway. I might try it anyways, maybe it will work, you never know. Don't have much to lose at this point
Anova's Origin said:
What phone and ROM are you using?
One thing you could try is to install systemless Xposed through Magisk. Then use MagiskHide to hide both root and Xposed from all Google apps and potential sources of conflict. If it's a software limitation/conflict, this may be a workaround.
Keep in mind that you will have to root your phone with Magisk rather than SuperSU or any other form of root.
Click to expand...
Click to collapse
FIY Magisk cannot hide Xposed...
I also facing these problem on my rooted Asus zenfone 2 (ze550ml 2gb ram version, Stock ROM, bootloader unlocked) and Asus Zenpad C 7 (p01y, stock rom, bootloader unlocked). The xposed firmware (version 86) is successfully install but can't install any apps from play store and using apk...
I really hope that dev team can solve it.....
Sorry for any grammatical mistakes....
The only way is to flash the firmware
I'm getting the same problem on my LG G4 with v88.2 of Xposed :/
I don't Know if this is too late,but I also have this problem. But there is a work around, go into the xposed installer and turn the switch off so its disabled on the next boot. rebot the device and exposed and its modules are disabled, allowing you to install apps from play store and downloaded .apk files... it would still be nice to install applications while its still on.
Sent from my LG-K550 using XDA Labs
I had this issue on my LGG3. This happens when you have Lucky Patcher enabled in your xposed modules. Disabling it (Lucky Patcher) should solve the problem.
Title says it all. Im currently using using SuperSU so looking for Systemless root and looking for Xposed to work as well.
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Didgeridoohan said:
Remove SuperSU, flash Magisk. That's basically it... If you have issues on the way there's lots of info in the support read and some things to try here:
https://forum.xda-developers.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
Click to expand...
Click to collapse
Do I remove SuperSU thru it's manager and then flash Magisk?
riahc3 said:
Do I remove SuperSU thru it's manager and then flash Magisk?
Click to expand...
Click to collapse
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
jhedfors said:
Yes, choosing the full unroot option. It is also good to have the unsu zip by osm0sis handy, but the full unroot option should work.
Click to expand...
Click to collapse
This just flash Magisk? No Xposed issues?
riahc3 said:
This just flash Magisk? No Xposed issues?
Click to expand...
Click to collapse
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
jhedfors said:
I don't use Xposed, as it does not work on Nougat. You will need to install the Xposed module in the Magisk Downloads tab.
Click to expand...
Click to collapse
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
When SuperSU asked if I wanted to recover the boot image (I think it was that) I said no.
Issues with that?
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Says Ive lost root....
Magisk does say it is installed.
riahc3 said:
Checking patch status
SuperSU patched boot detected!
Adding auto patch scirpt for supersu
SuperSU image mount failed...
Will still try to complete installation
Device still does boot...which I guess is still a good sign.
Click to expand...
Click to collapse
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
riahc3 said:
Reflashed the SuperSU zip.....Opening Magisk Manager.....its currently stuck opening it. Only the logo with the background appears.
Android says "Magisk Manager is not responding".
OK! Wow, that took a while lol....
Latest version of Magisk installed....
Properly rooted
279:SUPERSU
Checking SafetlyNet Failed: CTS Profile Mismatch
Click to expand...
Click to collapse
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Didgeridoohan said:
CTS profile mismatch will happen if you're using SuperSU.
The one thing that went wrong was you saying no to restoring the boot image backup. If you want to use MagiskSU you'll need to flash it over a boot image that doesn't have the SuperSU patches.
Click to expand...
Click to collapse
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
riahc3 said:
At this point, is there is a way to fix it?
I have gotten also gotten systemless Xposed installed
Click to expand...
Click to collapse
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Didgeridoohan said:
If you're happy with your current setup, leave it be. If you need to pass SafetyNet (you'll need to disable Xposed for that) you'll have to start over.
Click to expand...
Click to collapse
Doesnt systemless Xposed pass SafetyNet?
riahc3 said:
Doesnt systemless Xposed pass SafetyNet?
Click to expand...
Click to collapse
No.
Didgeridoohan said:
No.
Click to expand...
Click to collapse
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
riahc3 said:
Oh! My mistake then
I could careless about SafetyCheck as I need Xposed modules.
Besides, that, then Magisk is working? That was pretty simple. Thank you for your help.
Reading thru your thread, I cant really see what SafetyCheck implies. Does it just affect that stupid Pokemon crap? I imagine it affects more things like banks but I dont think mines will depend on that.
Click to expand...
Click to collapse
Magisk works fine with SuperSU. It's if you'd ever want to hide root from some process or app that you might have some trouble, since Magisk Hide is developed with MagiskSU in mind.
There are some banking apps, Android Pay, Pokemon Go other apps that utilise SafetyNet. I do believe that more and more apps will use in the future and the cat and mouse game of hiding root is gonna continue...
riahc3 said:
Im on 6.0 so I do and its important.
Well, here goes nothing I guess....
Click to expand...
Click to collapse
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
anshulsingh said:
I am also on android 6.0.1 and need to install magisk to work with safetynet to install games like pokemon , supermario run etc . Why do you say Xposed is required? also, did full unroot from within superSU app worked for you or you flashed UnSu for that?
Thanks
Click to expand...
Click to collapse
I use Xposed modules in my daily life and cannot afford to be without them.
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Did it really lose root? I've found that randomly when you open Magisk it will claim that it has no root access, but when you close it (exit the app and swipe it away from the recents menu) and reopen it it will start functioning properly again.
Neo3D said:
I noticed today that I lost root. I searched and tried everything to fix it but I couldn't. So, I wiped out my entire phone and did a clean flash of Resurrection Remix 5.8.3 for the TMobile Note 3. Magisk worked after a clean flash.
Spent hours loading every app back on and now, Magisk isn't working again?
Please help?
Android version is 7.1.2.
Click to expand...
Click to collapse
Use un su zip first to remove the pre-installed root that rr has. Don't know if RR has root inbuilt now or not. But if it comes with root uninstall it and flash magisk on top of it and you are good to go
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
exodius48 said:
Me too have this problem. Magisk root sometimes gone, and i need to reboot device to make it work agan.
Tested in almost N custom roms like CM14.1, AEX, Omni, ViperOS, etc
Click to expand...
Click to collapse
Did u remove built in root
shantam3108 said:
Did u remove built in root
Click to expand...
Click to collapse
If you installed magisk it will remove built in root automatically. -_-
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
I did some more searching and someone said just flash Magisk again. I did that and it worked! But, then I lost root again several hours later, seems so random? I flashed Magisk again and it worked again.
I can only get two green on Magisk, the third green seems to run forever, I left it on for 10+ minutes and it still showed "testing".
BTW, I didn't flash the uninstall Magisk zip before re-flashing. I tried that way and my phone got into a bootloop. Luckily, I had a TWRP backup.
Kris Chen said:
Did you turn off magisk busybox ? It would help on fix that.
In another way, some of modules you installed may have potential to make you lose root. Trying to do enable/disable module to test it.
Click to expand...
Click to collapse
Thanks! I'll try this and see if it helps!
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
---------- Post added at 01:21 AM ---------- Previous post was at 01:20 AM ----------
Neo3D said:
Thanks! I'll try this and see if it helps!
Click to expand...
Click to collapse
Also keep in mind do run magisk without any modules first to check
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
Then why on AEX still loose root? It has no root prebuilt
exodius48 said:
If you installed magisk it will remove built in root automatically. -_-
Click to expand...
Click to collapse
shantam3108 said:
No magisk just overrides the root. Use Un su zip first then flash magisk and u won't lose root
Click to expand...
Click to collapse
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Didgeridoohan said:
I just want to clarify.
If systemless SuperSU is detected, Magisk will use that. If any other root is installed, the installation script will attempt to remove it and install MagiskSU instead (not sure to be successful and might lead to issues). If no root is installed, MagiskSU will be used. To avoid issues, the unSU zip is quite useful.
From v13, Magisk will no longer be compatible with SuperSU.
Click to expand...
Click to collapse
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Neo3D said:
Wow, this is very informative, thanks!
Which version of unSU.zip is the correct one to use? Is this one okay?
https://forum.xda-developers.com/showpost.php?p=63615067
Click to expand...
Click to collapse
That's the one to use. :good:
Neo3D said:
BTW, is anyone able to install Snapchat? I tried the Hide feature in Magisk and checked Snapchat, but it still knows I'm rooted and immediately closes after opening.
Also, the Sphero BB8 app? Anyone get that working? That one also closes right after opening.
Click to expand...
Click to collapse
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
[email protected] said:
It is because your device lost safety net.
You need to reflash system and gapps.
Back up data partition then wipe all then flash rom and gaps and then magisk.
After starting device first enable magisk hide.
Then restore backed up /data.
After restart enable magisk hide switches and reboot system.
Profit.
Reply it works or not.
Click to expand...
Click to collapse
I just flashed magisk again and safety passed!
Neo3D said:
I just flashed magisk again and safety passed!
Click to expand...
Click to collapse
Tell me how much time you have safety net pass?
[email protected] said:
Tell me how much time you have safety net pass?
Click to expand...
Click to collapse
Hi, what do you mean "how much time you have safety net pass?
Neo3D said:
Hi, what do you mean "how much time you have safety net pass?
Click to expand...
Click to collapse
This time after reinstalling magisk is it working till now?
Or root is gone after some time?
Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you
urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!
For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.
One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.