Related
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Code:
adb reboot fastboot
Temporarily boot into into TWRP
Code:
fastboot boot C:\twrp-3.0.2-0-clark.img
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
JimyKK said:
Had issues installing the latest SuperSU, turns out an old version needs to be installed then updated
Found no mention of Magisk and the x Force so gave it a try. Works beautifully and just wanted to share
This is what I did for reference
Download:
Latest Magisk zip from here
Latest Clark TWRP from here
Have a clean boot, bootloader and system image see this guide here - Also follow this guide for obtaining adb/fastboot if you don't already have it
Copy the Magisk zip to your SDcard
reboot into fastboot either by holding the power button and volume down when booting or via adb
Temporarily boot into into TWRP
Select the install option, then navigate to the Magisk zip file. Swipe to install. Wait
Reboot
Install the Magisk app from the play store - official guide said there would be a stub app but i didn't encounter
Reboot again to get Super user access - Note: you can install modules like xposed at this point through the app.
Thankfully my banking app tap to pay works when used with Magisk Hide enabled on it so I am very pleased
Click to expand...
Click to collapse
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
sam00561 said:
Hi can I ask if using magisk to root will android pay then work because I have rooted in the normal way and root is detected on android pay app.
Click to expand...
Click to collapse
Maybe™
My banking app uses google's inbuilt SafteyNet library to detect root and from my understanding that is also how android pay works as well. Magisk's hide function seams to bypass this detection even though on the main screen of Magisk management app the SafetyNet check fails.
For this procedure is necesary unlock the bootloader?
Cameronbrujah said:
For this procedure is necesary unlock the bootloader?
Click to expand...
Click to collapse
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Yemble said:
Absolutely it is !!!
You are rooting your phone.
BTW, I've been running Magisk on CrashXXLs ROMs since they first appeared last summer. There is a Magisk module available to allow the ROM to pass SafetyNET.
Click to expand...
Click to collapse
Thanks a lot for your prompt response!!!
I'll do it.
Cameronbrujah said:
Thanks a lot for your prompt response!!!
I'll do it.
Click to expand...
Click to collapse
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Yemble said:
With the very latest CrashXXL ROM from a few days ago, Magisk 14.0 passes SafetyNET without the need for any additional modules, or at least it does on my EU xt1580 :good:
If you are coming from stock MM-6.01 on the X-Force, I can strongly recommend the CrashXXL 7.0 ROM as it is rock solid, works with TWRP and has auto-updating disabled (which is a good thing if you don't want to accidentally brick your rooted phone). Moto are not really supporting the X-Force, so there is absolutely no reason to stick with stock as there will be no official Oreo update.
Your other option is (unofficial) LineageOS, however, when I tried it a few weeks ago, I found it extremely unstable, particularly when running TomTom! Therefore, I cannot recommend LineageOS for the X-Force.
Click to expand...
Click to collapse
actually I have Nougat 7.0 Official and only for the moment I will to root the phone. In a near future, of course I will change the ROM to the CrashXXL
Thanks a lot for all your help.
Regards from Mexico!
And how are we gonna unlock the bootloader?
Is there a way to do that?
Hello XDA,
As we are all aware that once again Google broke SafetyNet Passing as they have extended their property scanning | Original Article here
The temporary fix was originally mentioned on this thread by @[email protected]
However you had to do the terminal commands after every reboot, thus Me and a few friends took this idea and created an app that does the same for you in the background and thus an easy temporary fix.
All you have to do is to install the apk as usual, grant it supersu permission and click to fix :laugh:
GitHub: https://github.com/Agusyc/SafetyNetPasser | Credits @Agusyc15
Download APK
Made a Quick Video Here
Tested Working on Oneplus 5 & Pixel XL | Magisk V13.2
Development Credits: @Agusyc15 & @unknownblkman
Magisk Credits as always @topjohnwu
Original Fix & ADB Commands: @[email protected]
PS: This is a temporary fix, I am sure @topjohnwu is aware of this situation and an official fix should be out soon :fingers-crossed:
Never Settle :highfive:
Reserved
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Interceptor777 said:
You can use the module I attached, it works and does it systemlessly.
I didn't make it but I forgot who did lol
Click to expand...
Click to collapse
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Bewildered Wolf said:
What is that sharingan symbol in your quick settings.
Which rom and which SST themes.?
Click to expand...
Click to collapse
Resurrection Remix with Spectrum kernel app, running lightning kernel LOS version which supports it.
The symbol on the quick settings is a quick profile switcher for spectrum, this is what it looks like on balanced profile.
Also, theme is also called spectrum on the play store.
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
GitHub along with the Updated apk now uploaded on the OP | Credits @Agusyc15
hachamacha said:
Thanks OP! Works well. I'd tried all the recommended steps in other threads from terminal emulator and adb shell su, but they didn't work for me. Many thanks.
Click to expand...
Click to collapse
Please try the new apk uploaded on the OP :fingers-crossed:
Funk Wizard said:
Please try the new apk uploaded on the OP :fingers-crossed:
Click to expand...
Click to collapse
Just tried it and it works fine as did your first. Thanks!
@Funk Wizard you can also purpose the recovery flash solution (by noahajac) available from Github : here
Personaly i prefer flash the fix by this way instead of install a apk/service for fix SafetyNet each boot
Magisk 13.2 has been released and fixes the SafetyNet test failing.
Magisk 13.2
I can confirm that it's working for me.
Magisk 13.3 already available, and everything is fixed
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
13.3 fixed for me
Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Binary Assault said:
Anyone having issues upgrading ?
I'm using stock rom (4.5.5) with a. Custom kernel
Iupgrades to 13.3 via Magisk manager (was on Magisk 13.0 previously so whichever Magisk manager goes with that).
Rebooted and now Magisk manager force closes upon boot.
Downloaded 13.3, cleared all data from Magisk manager, uninstalled Magisk manager, went to TWRP, dirty flashed 4.5.5 to restore the stock kernel, flashed Magisk 13.3, wiped cache and dalvik then rebooted. Same issue on start. Magisk force closes.
Reinstalling Magisk 13.0 allows Magisk manager to run.
Root still works when upgrading to 13.3, but Magisk manager still force closes.
Any ideas?
Click to expand...
Click to collapse
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
crumble6 said:
I'm having this issue too.
EDIT: I just flashed Magisk uninstaller, wiped cache/dalvic and then flashed v13.3 and now all is working well. I think the issue is I flashed a 13.2 fix yesterday which probably messed with it.
Click to expand...
Click to collapse
That didn't work for me unfortunately.
ArkAngel06 said:
I kinda had that problem, but it would only crash when going to the part of the app that lets you manage apps which have been granted/denied root.
I tried clearing data and it still did it, so I completely uninstalled the app and I think that fixed it.
My guess is you are using an out of date app. The current version of the manager is 5.1.0 and can be found here.
Latest Magisk Manager
Uninstall whatever manager you have now and install that one and remember that the manager seems to get updates more often than Magisk does.
Click to expand...
Click to collapse
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Thanks guys!
Binary Assault said:
That didn't work for me unfortunately.
This seemed too do it. I assumed that the version that came with Magisk was up to date. Maybe there was another update after 13.3.
Click to expand...
Click to collapse
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
crumble6 said:
Apparently there's issues with certain modules. If I install the V4A module the same thing occurs. Lots of other people are having the same issue. So just be careful which modules you install.
Click to expand...
Click to collapse
Ya, I just discovered this. I actually noticed a few things,
My original issue was caused by a module I installed
It seems anything I flash via TWRP makes Magisk manager fail.
Most modules I installed in TWRP that fails, will properly install within Magisk manager.
For me, the culprit was doze for Google play services. Even installing it via Magisk manager froze Magisk manager.
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Binary Assault said:
Is there any way to uninstall any Magisk modules without Magisk manager? I've been going to recovery, flashing Magisk uninstall, reinstalling Magisk then manually enable each module in Magisk manager. Kind of a pain.
Click to expand...
Click to collapse
Just delete the module folder from /magisk and reboot. You will need root access for this but from what I've found, root access still works even though Magisk Manager is not responding.
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
uutsav said:
Need your help guys. I am running beta 27 with super su V2. 82 SR 5....i heard now magisk is supported in beta 27...how to I unroot supersu, install magisk 14.5(1456) and still pass safety net... I tried searching for a solution everywhere but couldn't find a solution to this..... Please help... :crying:
Click to expand...
Click to collapse
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
tropicanapure said:
It's fairly simple. You will need unsu zip (from SuperSu official thread) and the Magisk zip downloaded where you can easily find it.
Boot to recovery
** create a Backup **
Flash unsu
(Assuming no errors) Flash Magisk
Again assuming no errors, reboot system
In your list of apps you should have a new"Magisk Manager" app and your "SuperSu" should be gone.
Thats it really. Took me a whole of 10 minutes, of which 7 minutes were backup [emoji6]
Click to expand...
Click to collapse
And you passed safety net
uutsav said:
And you passed safety net
Click to expand...
Click to collapse
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
tropicanapure said:
Yes! That was my main motivation for switching. That and SuperSu no longer being run by chainfire Trust me Magisk does a far better job than Super Su.
Also worth looking at this URL
https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Forgot to mention you will need to uninstall xposed (can be reinstalled after). I don't use xposed.
Click to expand...
Click to collapse
I tried flashing unsu and it asked me to flash the stock boot image in TWRP.... Any ideas mate..
I am sorry to keep bugging.... But I am lost
Look for boot.img in the ROM zip and flash it.
I was just about to say that myself. See
https://forum.xda-developers.com/showpost.php?p=63615067
Like the previous post said, you need a pristine boot.img and your ROM zip is the ideal place to find it.
Dirty flash your Beta27 again and it should be clean, THEN reboot and then install Magisk
Now i flashed beta 28, flashed recovery and flashed magisk again... While I was able to flash it... But getting safety net error....
My life is finished...
If you were able to install magisk then you should take this to the official magisk support thread. You are more like to get a better variety of suggestions there.
Just saying.
Hey everyone, i got a new j6+ (sm-j610f) running 8.1 oreo. I rooted it via magisk patched boot.img method , also removed all the bloatware. I want ro install xposed framework but this device doesn't have a compatible twrp/cwm recovery yet, i tried using flashfire but it's not working. I'm not sure if the app isn't compatible with oreo or magisk, i granted it superuser permission but it's stuck on acquiring root access. Is there a fix for this problem, if not is there an alternative for flashfire?!
dope77 said:
Hey everyone, i got a new j6+ (sm-j610f) running 8.1 oreo. I rooted it via magisk patched boot.img method , also removed all the bloatware. I want ro install xposed framework but this device doesn't have a compatible twrp/cwm recovery yet, i tried using flashfire but it's not working. I'm not sure if the app isn't compatible with oreo or magisk, i granted it superuser permission but it's stuck on acquiring root access. Is there a fix for this problem, if not is there an alternative for flashfire?!
Click to expand...
Click to collapse
Magisk already has Xposed support. No need to install the framework separately.
Just type Xposed in the download section and install the SDK 27 version.
ashyx said:
Magisk already has Xposed support. No need to install the framework separately.
Just type Xposed in the download section and install the SDK 27 version.
Click to expand...
Click to collapse
I tried this, no success
dope77 said:
I tried this, no success
Click to expand...
Click to collapse
Are you sure you have the latest version of Magisk installed?
Also save and post the log after install.
ashyx said:
Are you sure you have the latest version of Magisk installed?
Also save and post the log after install.
Click to expand...
Click to collapse
Magisk manager says that i have the latest version
dope77 said:
Magisk manager says that i have the latest version
Click to expand...
Click to collapse
update-binary[102]: /sbin/.core/mirror/bin/magisk: not found
Have you got stuff hidden?
ashyx said:
update-binary[102]: /sbin/.core/mirror/bin/magisk: not found
Have you got stuff hidden?
Click to expand...
Click to collapse
Look, here's how i got this phone rooted, downloaded magisk manager, patched the boot.img and flashed through odin, restored phone to factory settings bcz i was stuck with integrity verification failed and there was no way to flash dm verify disabler since there is no custom recoveries for j6+ yet. After that phone booted and magisk was installed. Haven't touched any settings nor hidden any things, and there's this message i keep getting whenever i open magisk. Each time i open magisk it popups, even if i press yes it will appear the next time open magisk.
This is the log i get after installing the additional setup
- Detecting target image
- Target image: /dev/block/mmcblk0p23
- Device platform: armeabi-v7a
- Existing zip found
- Extracting files
Killed
Killed
Killed
- Unpacking boot image
Killed
Killed
Killed
- Checking ramdisk status
- Patching ramdisk
- Repacking boot image
Killed
! Unable to repack boot image!
! Installation failed
This commonly happens whe u don't have the latest MAGISK installed NOT MAGISK MANAGER.
I am on 10.3.2, rooted with Magisk Manager version 07f712a1 and Magisk 87de0e7a. These are the version numbers I can see when i open Magisk Manager. Magisk Hide is enable for banking apps mainly, systemless host module is enabled and Magisk package name is also hidden.
Most apps needing root are working fine and most Banking apps requiring root to be hidden are also working fine.
However BHIM UPI is not working, I get a message of root detected after putting the PIN and it does not open. If I uninstall or clear storage and register my mobile again, it gives the root detected error but still logs in. However as soon as I exit and open again, it does not log in. Any way to get this working?
Adaway had been working properly but now it is not able to update hosts, says Root permission not granted, even though in Magisk default permission is Grant. I have tried to uninstall and reinstall, change options in Magisk, install F-droid version but nothing works. Systemless host is enabled. I have restored a working app version and data using Titanium backup so ad-blocking is working. But unable to update with new host file. How to fix this?
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Macusercom said:
Did you try to remove root and root again? Maybe something with Magisk isn't right.
For BHIM UPI I have no idea what that app is but there are a lot of apps that use really good root detection which Magisk can't fully circumvent. It could be that this is the case here
Click to expand...
Click to collapse
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
gpz1100 said:
^^Review this thread, specifically first post
https://forum.xda-developers.com/apps/magisk/magisk-unified-hosts-adblocker-t3559019
Click to expand...
Click to collapse
Is this meant as a reply to my post? My issue with Adaway on Magisk Canary is that suddenly it is not able to get root permission.
So it worked before? I had to mess with the systemless hosts to get it working. It didn't have issues acquiring root though.
jesrani said:
BHIM UPI is a Banking App.
I am currently on Magisk Canary and also having problem with Adaway. I tried to change channel to Stable and the manager changed to version 7.5.1 but Magisk remained Canary version. When I tried to install the latest stable version the installation fails so I had to revert back to Canary version. If I clear storage the Manager comes back to Canary version and then I am able to install Canary Magisk version, it installs properly.
How do I properly uninstall Canary version Magisk and install Stable Magisk, maybe this will resolve the issues.
Click to expand...
Click to collapse
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Macusercom said:
I would advise to use the stable Magisk version. You can either flash the Magisk uninstaller via TWRP or uninstall Magisk in Magisk Manager and then flash the stable Magisk version in TWRP
Click to expand...
Click to collapse
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
jesrani said:
Is there a working TWRP for OnePlus7T, I thought there wasn't but I am not sure because I rooted it many months back.
Click to expand...
Click to collapse
Afaik only for custom ROMs. Otherwise, you can still remove Magisk in Magisk Manager and then patch the boot.img with the stable Magisk version or you remove ALL modules first, then make an OTA update to your existing version.
Then patch boot.img and flash it via "fastboot flash boot.img".
@jesrani What was the solution finally ?
Yea I'm having the same issue, tried everything i could and even using 'hide my applist' and it IS working. Its just that all apps except BHIM just won't even open now.