Related
Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do
mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
If I do a ROM update do I need to unSU and flash Magisk again?
Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.
aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?
guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.
Would using the wrong unSU version affect safetynet detection?
Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?
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?
Is anyone using magisk and have Android pay working with root on the 5x ? I've been looking for a thread and can't find how to do it.
Unlock bootloader
Flash stock image
Flash TWRP
Reboot
Download magisk Manager and zip
Reboot ?
Will root apps work now with Android pay?
mikeprius said:
Is anyone using magisk and have Android pay working with root on the 5x ? I've been looking for a thread and can't find how to do it.
Unlock bootloader
Flash stock image
Flash TWRP
Reboot
Download magisk Manager and zip
Reboot ?
Will root apps work now with Android pay?
Click to expand...
Click to collapse
Make sure Magisk hide is on in magisk manager and that it passes the safety net check.
Keithn said:
Make sure Magisk hide is on in magisk manager and that it passes the safety net check.
Click to expand...
Click to collapse
Do I need to flash SU or just magisk
Got it working. Shows Superuser PHH's not the SU by chainfire. Some apps are not working as well with superuser vs SU, but at least everything seems to be working. Every now and then Magisk Manager bug and it shows loss of root. I'll try Android pay sometime today if I can
Could you make a quick guide on how you got magisk installed correctly?
I had some trouble when i tried it after updating to 7.1.2 yesterday and ended up flashing supersu instead. thx
mikeprius said:
Got it working. Shows Superuser PHH's not the SU by chainfire. Some apps are not working as well with superuser vs SU, but at least everything seems to be working. Every now and then Magisk Manager bug and it shows loss of root. I'll try Android pay sometime today if I can
Click to expand...
Click to collapse
mikeprius said:
Do I need to flash SU or just magisk
Click to expand...
Click to collapse
Magisk zip include SU binary (MagiskSU)
---------- Post added at 02:12 PM ---------- Previous post was at 02:09 PM ----------
robotzki said:
Could you make a quick guide on how you got magisk installed correctly?
I had some trouble when i tried it after updating to 7.1.2 yesterday and ended up flashing supersu instead. thx
Click to expand...
Click to collapse
If you have custom kernel, flash the stock one or that came with the Rom from recovery. Then flash Magisk 12 zip file from Magisk Thread and flash it via recovery. Then reboot and download Magisk manager ....
Is there any reason why Magisk wouldn't work with a custom jkernel? I've installed Magisk on top of pure nexus ROM with ElementalX kernel without issues before.
I'm running SAOSP with Magisk and Franco Kernel and I have root and Android Pay works. That's all I flashed. It had a hard time passing Safety Net when SuperSU was installed. So just flash Magisk without SuperSU. And I guess Android Pay can detect if you have an unlocked bootloader so Franco Kernel is used because it hides that.
I tried Android Pay twice. First time didn't go through, said on the vending machine failed. Second time worked. I checked Android Pay and see 2 charges, does the one that didn't go through just drop off eventually ? Also both charges are much higher than what the actual price was, but I assume this is just a temp charge.
I have elemental X kernel. Works fine. I decided not to mess with SU. My other apps work, plus I've tried asking Chainfire before questions about his apps he's made and he never responded. Not cool, I did buy his apps too, not just freebies.
mikeprius said:
I tried Android Pay twice. First time didn't go through, said on the vending machine failed. Second time worked. I checked Android Pay and see 2 charges, does the one that didn't go through just drop off eventually ? Also both charges are much higher than what the actual price was, but I assume this is just a temp charge.
I have elemental X kernel. Works fine. I decided not to mess with SU. My other apps work, plus I've tried asking Chainfire before questions about his apps he's made and he never responded. Not cool, I did buy his apps too, not just freebies.
Click to expand...
Click to collapse
All of my Android Pay charges initially show up as a $1.00 pending charge. After a while, they post as transactions for the full value of the purchase.
Can't install SuperSU on Huawei Watch 1 "Patching sepolicy ---Failure, aborting"
I apologize if this is a noob question. I'm no stranger to modding Android devices; only new to modding Wear devices, and unfortunately information about rooting this watch is so sparse (understandably) and I couldn't find anyone with the same issue when searching. So like the title says, I can't get SuperSU installed on my Hwatch running AW 2.0. When I try to install SuperSU via TWRP, it gets stuck when trying to patch sepolicy.
Do I need a custom kernel for this? Is there one with no modifications other than the sepolicy? Or is there a way to change the sepolicy on the stock kernel. Between the guides I've read and WinDroid Toolkit, nothing has mentioned needing to do anything else to allow flashing SuperSU, but I can't think of what else would be the cause of the issue and I suppose things could have changed since those guides and Windroid were written.
I kind of want to avoid custom kernels as they almost always have issues in my experience with running them on phones (no offense to any kernel devs out there) and I can't deal with that on something simple as a watch. I just want this rooted mostly so I can test out underclocking and powersave governor when needing some extra battery time and so the next time I flash or upgrade my phone, I don't have to wipe the watch.
Any help will be greatly appreciated. And if I must install a custom kernel, I would love recommendations on the most reliable and/or closest to stock one.
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an every time I try to flash the latest SuperSU zip.
Tristan Phan said:
For me, WinDroid Toolkit doesn't work for rooting Android Wear 2.0. I am on AW2.0 with the stock kernel and I have rooted the device using Magisk v13.2. Magisk Manager works on Android Wear (even though it may be hard to use on a round screen), but SuperSU (app) crashes when I launch the app. All you have to do to install Magisk is to flash the latest Magisk installer in TWRP and sideload the latest Magisk Manager using adb. You can download Magisk here. I have tried SuperSU, but I would get an error every time I try to flash the latest SuperSU zip.
Click to expand...
Click to collapse
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
neonixxx said:
Thank you! Sounds like we encountered the same issue when flashing SuperSU. I had thought about trying Magisk, but wasn't sure if it would cause some issues on Wear. Thanks to your positive report, though, I'm going to try it out when I get home later. :good:
Click to expand...
Click to collapse
I'd like to know if it works for you. ?
Tristan Phan said:
I'd like to know if it works for you.
Click to expand...
Click to collapse
It worked! I was unable to sideload Magisk Manager, though, but that's fine. I'm just stuck on v5.0.5 which works just fine for handling root requests.
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Tristan Phan said:
That's great! The only real difference between Magisk Manager v5.0.6 and v5.0.5 is that v5.0.6 fixes a crash when downloading modules from the repo, so you shouldn't be that affected. If you want any modules, you can just download them from XDA or something and flash it in TWRP.
Click to expand...
Click to collapse
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
neonixxx said:
Yeah, that's why I'm not bothering with it. I don't feel a need for any modules on my watch at the moment Thanks again for tipping me off that Magisk would work.
Click to expand...
Click to collapse
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Tristan Phan said:
Just saying (sorry to bother), but Magisk v13.3 came out and fixed SafetyNet bypass. If you want, you can update by flashing Magisk-v13.3 by flashing it in TWRP without needing to uninstall the previous version. Installing this should also update Magisk Manager to v5.1.0.
Click to expand...
Click to collapse
No worries, haha. Yeah I already updated on my phone. Thought about updating the watch, but too lazy at the moment :silly: since I don't really need to pass SafetyNet on my watch for anything. Probably will do it later on.
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Tristan Phan said:
I'm thinking that the reason that you couldn't install Magisk Manager v5.0.6 was that it was already installed by the Magisk-v13.2 zip and ADB wasn't able to install over the existing APK, but I'm still a noob so I have no idea.
Click to expand...
Click to collapse
Check the adb install switches in adb help to solve that. Use the -r or -d switch.
Code:
adb install [-lrtsd] <file>
- push this package file to the device and install it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
Format data with the FORMAT DATA button first in TWRP then immediately flash Magisk (preferred) or latest Supersu.
Reboot.
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
Just wondering how you flashed TWRP (which version) and how? I'm having the same issue trying to get root on this phone and will probably just flash a custom
jermzii said:
Just wondering how you flashed TWRP (which version) and how? I'm having the same issue trying to get root on this phone and will probably just flash a custom
Click to expand...
Click to collapse
I have done it! Had the same problem and yes i have the Canadian a520w. I had to use Odin and then install superuser
Step one: Is to download Odin on pc mac or linux.
Step two: download superuser on your phone then move the file from your phone to
you computer.
Step three: open Odin and select the superuser zip file and it should say pass.
Step four: install root checker off Google play
This is not a full tutorial on how to install it but all you need to search is how to use Odin.
I got it!!
jermzii said:
I got it!!
Click to expand...
Click to collapse
Glad you got it to work did you use my method?
ashyx said:
Format data with the FORMAT DATA button first in TWRP then immediately flash Magisk (preferred) or latest Supersu.
Reboot.
Click to expand...
Click to collapse
Can you please provide a link to an appropriate TWRP version for SM-A520W?
Many thanks!
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
SlickSneeker said:
I have done it! Had the same problem and yes i have the Canadian a520w. I had to use Odin and then install superuser
Step one: Is to download Odin on pc mac or linux.
Step two: download superuser on your phone then move the file from your phone to
you computer.
Step three: open Odin and select the superuser zip file and it should say pass.
Step four: install root checker off Google play
This is not a full tutorial on how to install it but all you need to search is how to use Odin.
Click to expand...
Click to collapse
Please excuse my being a layman in this matter. I tried tot flash superuser.zip using ODIN but ODIN does not even see zip files (it only recognizes some other formats like .tar, .img etc). Could you please give a little more details on how you flashed superuser.zip using ODIN?
Thanks a lot in advance.
jermzii said:
I got it!!
Click to expand...
Click to collapse
Hi jermzii,
I apologize for my questions - I am not very experienced in all these. I would like to ask you a few questions:
Where did you get an appropriate TWRP version for SM-A520W?
Also, ODIN, does not "see" zip files. How did you flash the supersu.zip using ODIN?
Many thanks for your help in advance.
I just bought a Canadian A520W with with stock Nougat (Telus firmware A520WVLS2BRD2). I tried to root it using CF autoroot and TWRP and I had the exact experience as the OP dan.tjones. There is no TWRP specifically for A520W. After trying several versions I found one which is successfully flashed with ODIN (TWRP 3.2.1.0 for A520F). TWRP appears to install Magisk (latest version 16) successfully but it shows no root or su binary. TWRP also appears to install SuperSU zip (there is a specific version for A520W nougat) successfully, but when I open SuperSU app, it says the SU binary is occupied. Google shows two "fixes" ((1) clean uninstall using an option within SuperSU, then reinstall, and (2) uninstall SuperSU + install an earlier version of SuperSU then updating the binary (hangs). Both fixes do not work. Someone mention wiping DATA in TWRP would fix the problem, but it did not work for me.
The major problem seems to be KNOX keep saying "failed verification". At one point it was so screwed up that it just boot-loop / hang and the only thing that work was download mode. I install TWRP again and it sticks. Then I wiped everything (cache/ Dalvik, data, system, internal storage). I probably could try to flash the stock nougat firmware using ODIN, but it was still downloading (snail speed free download).
Since there is no more OS in the phone, I manage to install a 6.0.1 pre-rooted custom ROM using TWRP (I originally intended to downgrade from 7 to 6.0.1 anyway because of reports of poor battery life), and installation was successfully, giving me root. BTW I originally tried to downgrade from stock nougat to stock marshmellow using ODIN, but it does not work ("failed" message).
The TWRP version that I flashed with ODIN:
TWRP 3.2.1.0 for A520F ("recovery_a5y17lte-080318.img.tar")
https://androidfilehost.com/?fid=890129502657588962
The 6.0.1 custom ROM I installed with TWRP:
AXES ROM v.1 (they did say it is compatible with A520W)
https://forum.xda-developers.com/samsung-a-series-2017/development/rom-t3606231
I did not find any nougat custom ROM suitable for A520W. I am happy that I can find a rooted ROM and it does not matter to me whether it is marshmellow or nougat.
slim_thumb said:
I just bought a Canadian A520W with with stock Nougat (Telus firmware A520WVLS2BRD2). I tried to root it using CF autoroot and TWRP and I had the exact experience as the OP dan.tjones. There is no TWRP specifically for A520W. After trying several versions I found one which is successfully flashed with ODIN (TWRP 3.2.1.0 for A520F). TWRP appears to install Magisk (latest version 16) successfully but it shows no root or su binary. TWRP also appears to install SuperSU zip (there is a specific version for A520W nougat) successfully, but when I open SuperSU app, it says the SU binary is occupied. Google shows two "fixes" ((1) clean uninstall using an option within SuperSU, then reinstall, and (2) uninstall SuperSU + install an earlier version of SuperSU then updating the binary (hangs). Both fixes do not work. Someone mention wiping DATA in TWRP would fix the problem, but it did not work for me.
The major problem seems to be KNOX keep saying "failed verification". At one point it was so screwed up that it just boot-loop / hang and the only thing that work was download mode. I install TWRP again and it sticks. Then I wiped everything (cache/ Dalvik, data, system, internal storage). I probably could try to flash the stock nougat firmware using ODIN, but it was still downloading (snail speed free download).
Since there is no more OS in the phone, I manage to install a 6.0.1 pre-rooted custom ROM using TWRP (I originally intended to downgrade from 7 to 6.0.1 anyway because of reports of poor battery life), and installation was successfully, giving me root. BTW I originally tried to downgrade from stock nougat to stock marshmellow using ODIN, but it does not work ("failed" message).
The TWRP version that I flashed with ODIN:
TWRP 3.2.1.0 for A520F ("recovery_a5y17lte-080318.img.tar")
https://androidfilehost.com/?fid=890129502657588962
Before flashing custom ROM (in zip format), I use TWRP to wipe everything on the phone (cache / Dalvik, data, system, internal storage).
The 6.0.1 custom ROM I installed with TWRP:
AXES ROM v.1 (they did say it is compatible with A520W)
https://forum.xda-developers.com/samsung-a-series-2017/development/rom-t3606231
I did not find any nougat custom ROM suitable for A520W. I am happy that I can find a rooted ROM and it does not matter to me whether it is marshmellow or nougat.
Click to expand...
Click to collapse
You have rooted the device successfully the first time when you flashed magisk.Just root manager app was not installed.
If you have screwed up your device, do a clean flash of OS...then flash twrp and after flashing magisk the binary would be flashed but the app would
not be installed.To do that extract the app from the magisk zip that you flashed.It must be in common folder inside the zip.
Dont flash binaries on top of binaries.
Hope it helps
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
hey...im novice at this as well but I did get my a520w rooted with su on oreo with twrp...I flashed the latest su on twrp....twrp was hard to get on but there is somewhere that shows how...good luck
A Very Possible and Precise Solution
dan.tjones said:
Hey everyone,
I have been trying to root my new Samsung A5 (A520W - Canadian variant) but nothing seems to be working.
My first method was to flash CF AUTO ROOT with Odin, but this just rebooted the device without any sign of changing anything - no superSU installed and RootChecker returning negative results
I then flashed TWRP, and from there tried installing both SuperSU and Magisk v16.0, both of these options made the phone unusable (verification error on boot) so I flashed back to stock firmware and now I'm out of ideas.
I've tried looking for guides on the SM-A520F (non-Canadian variant) but most of these are out of date with respect to the recent OTA upgrade to nougat and/or mention the CF AUTO ROOT method which I know doesn't work
has anyone here managed to root this device? Am I missing a step, like formatting/wiping data beforehand or something? is it worth downgrading to an earlier android version?
Cheers!
Click to expand...
Click to collapse
Hey Sir!
Soooooo I've been messing around with this all night and I figured it out somehow after nearly frying my new A5 (2017) lol
I'd recommend that you follow the directions as best you can and as fully to help you not have to redo all your software settings and stuff like I did haha. I think if all this is done in this order you shouldn't have to lose your data. I can't guarantee anything but figured I could share what worked for me. BONUS: I actually don't have an unlocked phone and I'm still locked to my carrier actually! So I don't think all these warnings are necessarily valid. Anyhow, hope it helps. :laugh:
NOTE: I'm not allowed to post website links here for some reason haha so sorry for the inconvenience! All the sites began with the https colon double slash btw! So MAKE SURE to add that to the addresses below (links are in italics)!
FIRST: Completely backup phone using Android Studio as can be found at Tech Republic website /article/how-to-create-a-full-backup-of-your-android-device-without-root/ . Also I'd recommend you do a Smart Switch full backup. Smart Switch will work to some extent and I personally restored from there pretty intact as I didn't have the Android Studio backup option before my phone got wrecked by the Verification error after I attempted to flash SuperSU onto the phone using TWRP.
1. BEFORE ANYTHING ELSE: Enable Developer Mode (by tapping on the Build Number several times), Turn OEM unlock on, enable USB debugging, and make sure all the "factory reset block" is off (or Allow factory reset option is on) and encrypted data features are off, I unlocked any Notes and disabled Secure Folder and Knox and Samsung Pass
2. Turn phone off
3. Boot phone into Custom OS install mode by holding Power+Volume Up+Home
4. I downloaded a TWRP installer file from tx5.androidfilehost.com/dl/TLLV1I5jSqS9Zg68RNh1hA/1538776061/890129502657588962/recovery_a5y17lte-080318.img.tar
5. Download the Odin software to flash TWRP onto your device, I got mine from drive.google.com/file/d/0B-2yp-J_x0LPaGJrSUlUcHE1a2s/view
6. Used Odin 3.1 to flash TWRP onto Recovery using the AP function, also turned Auto Reboot and F.Restart off (unchecked boxes)
7. Downloaded (newest file that's a zip) such as no-verity-opt-encrypt-6.0.zip from build.nethunter.com/android-tools/no-verity-opt-encrypt/ and put it on the SD card in the phone
8. Turned phone off and booted it into Recovery Mode by holding Power+Volume Down+Home
9. Used TWRP recovery to flash the no-verity-opt-encrypt-6.0.zip which sort of disables all the security things on Samsung (such as Health and Pass and Auto Updates) that would block your work, and this actually lets you reboot your phone instead of getting the Verification Integrity Check failed error and having to reset your phone every time.
10. After rebooting my phone, everything was running fine. I then downloaded SuperSU file SR5-SuperSU-v2.82-SR5-20171001224502.zip from download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip?retrieve_file=1
11. Used TWRP in Recovery Mode to flash SuperSU onto phone from SD card and hit Reboot. Slight boot loop was visible and then the phone restarted normally with SuperSU installed and full root access. Thanks be to God.
Again, I can't guarantee this will work BUT it is the first walkthrough that I know of on the web. Hope it helps at all!
Edit:
Originally gave up on this, but recently managed to flash TWRP.
Now in Verification Error on boot, and trying to flash the no-verity to get around that.
Success (almost rooted, but shouldn't be much harder)
Just flashed a custom OS using Odin_3.12.3, twrp-3.2.3-1-a5y17lte.img.tar, lineage-14.1-20181117-nightly-a5y17lte-signed.zip, and open_gapps-arm64-7.1-pico-20181204.zip.
With help from this discussion, the LineageOS wiki "Install LineageOS on a5y17lte", r/LineageOS "Heimdall Failed to send data" (a post by noahajac was very helpful. You'll find it soon after OP), and the Odin install guide.
Some problems I encountered was that heimdall isn't favoured for this, and that if you try to wipe your partition through TWRP and it says it couldn't mount /data, you need to format the partition before wiping it.
Edit: so upon using the phone for a bit, it became evident that the SIM card was not being detected. From what I've read so far, this is because the phone had Android Oreo and the LineageOS was for Nougat. So I will have to restore and then revert to a Nougat version of Android and try again from there...
Not gonna be finished tonight. As long as I can get the restore and cell service working...
Two Questions re: rooting the SM-A520W
1. How can I make a proper Nandroid Backup. Everytime I go into TWRP the /data partition is unavailable. Yes I formated it and flashed no-verity-opt-encrypt-6.0.zip but it still is Zero bytes.
2. After rooting, the Fingerprint scanner becomes non operational and the lock screen password/pin does not work (keeps asking for the same password/pin over and over even though they are correct.)
Thanks for the Help.
ethan_hines said:
1. How can I make a proper Nandroid Backup. Everytime I go into TWRP the /data partition is unavailable. Yes I formated it and flashed no-verity-opt-encrypt-6.0.zip but it still is Zero bytes.
2. After rooting, the Fingerprint scanner becomes non operational and the lock screen password/pin does not work (keeps asking for the same password/pin over and over even though they are correct.)
Thanks for the Help.
Click to expand...
Click to collapse
Which firmware are you running.
ashyx said:
Which firmware are you running.
Click to expand...
Click to collapse
I'm on Stock 8.0
I managed to fix problem 1 by flashing a modded Version of TWRP (3.2.3-TwrpBuilder) I am rooted with Magisk and now have access to the /data partition and can make a proper Nandroid Backup.
Problem 2 Is still there I seem to remember I have to replace Samsung Pass and Samsung Account, but I don't know where they are located I think I am supposed to create a directory in /prv-app I don't remember
I have that phone. I installed a custom recovery and used super SU.
SonicFan66 said:
I have that phone. I installed a custom recovery and used super SU.
Click to expand...
Click to collapse
I didn't want Super SU because it can't be hidden from apps that disable if root is detected esp. Snapchat
@ethan_hines did you figure it out? I am looking to do what you did.