Develop Bugs

Installing TWRP Fail!! Please check this out!

Ok guys Ive tried every post I can find on getting TWRP on my phone. I have the latest Odin3 v3.10.6.exe, the latest TWRP, twrp-2.8.7.0-trltespr.img.tar and tried, openrecovery-twrp-2.8.5.0-trltespr.img.tar, I have followed the posts and pulled the usb, then the battery for 30 seconds. I have unchecked the auto reboot, left it checked, tried it in the AP and BL slots and I cant get a custom recovery to stick. Here is the stats on my phone, Im at my wits end with this any help or suggestions would be much grateful. Ive already bricked it with cf autoroot and reinstalled the stock rom. Im wondering if I shouldn't of let it auto activate? Does sprint have a kill mode now for TWRP?
Software Version, N910PVPU4COG5
HARDWARE VERSION N90P.O5
ANDROID VERSION 5.1.1
BASEBAND VERSION SAME AS SOFTWARE VERSION
KERNEL VERSION
3.10.40-530320
DPI!SWHE8820 #1
BUILD NUBMER
LMY47X.N910PVPU4COG5
SECURITY SOFTWARE VERSION
MDF V2.0 RELEASE 1
VPN V1.4 RELEASE 5.2
KNOX VERSION
KNOX 2.4.1

Johniex said:
...Im wondering if I shouldn't of let it auto activate?...
Click to expand...
Click to collapse
Yes, you should. Although I can't recall it specifically said, that's what I do. I use the OB7 bootloader still and the OB7 to OG5 tar flash, reboots without warning on initial boot. Using OG5 modem on OB7, the phone would ask for permission to reboot. Once that reboot is out of the way, proceed.
@tx_dbs_tx implied (not to put words in his mouth but IMO he implies as you theorize here) the same recently when he added to get a GPS lock prior to proceeding.
The other steps you mentioned should get it done. Latest Odin, default settings, wipe everything but extSdCard (backup keep sakes) and power down prior to Odin download are recommended as well. Also, remember to uncheck auto reboot for TWRP flash in Odin, pull USB and battery. Most importantly, boot into recovery to help it stick.
Sent from my SM-N910P using Tapatalk

TWRP Fails While Trying To Write
Hello to all. I am trying to install TWRP on My Sprint note 4 . I am on software version N910PVPS4DPE2 and the Baseband is the same. Android VErsion 6.0.1
I was trying to install TWRP 3.0.2-0. Odin sees the phone and tries to install, but I notice that upon the writing process it fails. I even tried to install TWRP 2.8.5.0. I think I read something that this version must be installed first before any newer versions. Now mind you I am not rooted as of yet. I want to get a backup of the original setup before I flash a new ROM.
Any and all suggestions are welcomed to help me.
Blessings and Thank You In Advance.

ulremember said:
.. I notice that upon the writing process it fails. I even tried to install TWRP 2.8.5.0. I think I read something that this version must be installed first before any newer versions. Now mind you I am not rooted as of yet. I want to get a backup of the original setup before I flash a new ROM.
Any and all suggestions are welcomed to help me.
Blessings and Thank You In Advance.
Click to expand...
Click to collapse
Don't think you have to install an older version of TWRP first but there are 2 common overlooked steps when installing TWRP:
1) Goto Settings/Security when booted and make sure Reactivation lock is unchecked. (If it's set, you can't write in Odin and your phone displays something like blocked by R/L.)
2) You've dug up an old thread, this post may conflict with the older posts above but for clarity, it's best to open Odin options tab, uncheck only the auto reboot box and flash the img.tar, loading in AP slot. After flash is verified as successful, 0 failed (wait for it), pull USB cable and battery, wait at least 30 seconds. It's important that your first boot is directly to recovery to make TWRP stick as your default recovery. Else, you revert back to stock recovery if booting into system.
Note: There is a TWRP thread in original development forum which answers this question and others. Before rooting, you may consider OTA update to the update that matches your ROM if interest. The OTA updates are incremental so it may make more sense to Odin the stock reflecting the update of interest.
When Odin flashing stock tars, use the latest Odin, verify the md5 of downloaded zip then extract the tar.md5 to Odin folder to find easily when flashing. But on your phone, backup what you like before considering wiping; don't expect the flash to wipe for you but you may lose internal memory storage. Expect that but don't wipe your extSdCard; you can move what you want to keep there along with anything you intend to flash later. After backup and wipe, power phone down and pull battery prior to flashing stock tar. That seems to help ensure your csc gets setup properly. There is a stock tar thread in general forum with the stock tar updates, tools and instructions.
Make sure you install the right recovery or your touch screen will be out of calibration. Any trouble, refer to the TWRP thread but I think I've addressed the current issues.

Thank you soooo much!!!! That worked.
God bless you!!!!
Have a great weekend!!!

[Guidance] SGH-T989 UPDATING ISSUE!

Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.

Did you follow the instructions to flash TWRP using Odin?

olafo73 said:
Did you follow the instructions to flash TWRP using Odin?
Click to expand...
Click to collapse
I'm pretty sure I did everything I was intended to do. I installed Samsung Kies so I could install the drivers on my mobile, and then TWRP through Odin properly with the blue light showing up. After flashing it, it turned green and said PASS or PASSED. So I think I did everything right on that end, I can even access TWRP with no real problems.
I even tried to do a ROOT on my system, but again, I couldn't use ZIP or any other files on the TWRP installation option because they simply do not appear

bump

Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1

aguycalled80 said:
Watching this thread as I have the same problem.
I can boot to TWRP 2.8.7, but if I try to install, there's no file to install from.
I can go back to TWRP 2.6.0, and then mount the card and see the ROM, but every ROM I try fails. Something about non-virtual partitions if I try 4.4 or better, and error executing updater binary if i try 4.1
Click to expand...
Click to collapse
How did you go back to TWRP 2.6.0?

N1ZUW said:
How did you go back to TWRP 2.6.0?
Click to expand...
Click to collapse
With Odin.
I can boot in download mode no problem.

N1ZUW said:
Good evening everyone!
I've recently wanted to update my Hercules from 4.1 (I know it's reeealy outdated) to version 6.0 Marshmallow.
So I did a few steps and now I cant' seem to go any further, and I need your help.
So far, I've done the following:
-Installed TWRP 2.8.7.0
-Used Odin to flash the TWRP mentioned above
Now, I know there are a few problems regarding this version of the TWRP on the Hercules, so I tried fixing it by using Odin again and flashing the updated 2.8.7.1 and even the 3.0 version that I found on some threads, but with no sucess.
I haven't even had the chance to install Marshmallow on my phone in the first chance, because I couldn't find any .ZIP folders on the TWRP instalation menu.
I really appreciate your help guys, I'm a noob at this and I'm just starting to figure what is what, I just need my phone updated. It's running so far atleast, so it's not hard bricked I guess.
Click to expand...
Click to collapse
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.

markusrow said:
I don't know of any problems with any of the recoveries. However there are different recoveries for different roms which need to be used in a specific order and in a specific way, the first time that you virtually repartition your phone.
Have you gone through the process of applying the "virtual partition" and installing the modified "virtual partition" recovery? This is required for most of the MM roms on this phone (Hercules). The process is very well documented here http://forum.xda-developers.com/galaxy-s2-tmobile/help/guidance-sgh-t989-updating-issue-t3414641 in the #2nd post.
Click to expand...
Click to collapse
Hi, thanks for replying
No, I dont' take I have taken that step actually. I'm pretty new to this and I tried following every step correctly, but I know that I failed or skipped something at some extent and I've been trying to figure out what exactly, so I can fix it. I guess I need to Virtual Partition my phone then, could you post me the link do to so? Because I think you posted one that would take back to this post

aguycalled80 said:
With Odin.
I can boot in download mode no problem.
Click to expand...
Click to collapse
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!

N1ZUW said:
How do you go in download mode if you have TWRP installed? Does TWRP work as download mode aswell? Thanks for your help man, hope you can fix your phone too!
Click to expand...
Click to collapse
I shut it down in TWRP then hold volume down and power to go into download mode.
My phone has gone backwards now though - it doesn't matter what I load in Odin now, it won't boot up. The SAMSUNG screen is on, with a progress bar, but it never gets to the end. It stops right near the end and it sits there until I reboot it again.

My device is pretty much bricked

I took my 5.1.1 VZW Note 4, and rooted it with King Root. I proceeded to follow the instructions to change my CID here. I used adb, performed the commands, and everything seemed golden. I used odin to flash TWRP, but something went wrong. I booted into the recovery, and tried to "update from external storage". I soon recieved a "dm-verity verification failed in recovery" messaged. It did not occur to me that I was still in the stock recovery; I did not bother to check it's initial look and feel, and assumed the TRWP programmers were just lazy. After reading up on this "dm-verity" error, xda posters said I should flash it with Kies. Thinking nothing wrong could happen, I gave it a shot. It updated to 6.0.1. This is where the problems start happening.
Since then, I can't reflash to 5.1.1. I've tried every version I could get my hands on, including the 5.1.1/6.0.1 hybrid posted here. I have 3 total verions of 5.1.1. I then tried to downgrade to 5.0.1. The first version of 5.0.1 started artifacting the screen, but booted and stopped promptly. It only artifacted the "Samsung" loading screen. I couldn't, however, root the device. Feeling desperate, I tried the only other version of 5.0.1. Success! I rooted and reran the adb commands and the script provided to change CID. This time, it skipped the first half of the script. It went directly to "backup up loader to external card". This tells me something about my CID will forever be changed, and is probably the reason my phone is boot looping. This time, I was able to flash TWRP. I installed CM 13 only to find out my sim wasn't recognized (when I used it to download King Root in 5.0.1 before). I figured it was because I was usig a 5.0.1 bootloader/modem. I tried reflashing to 5.1.1, the 5.1.1/6.0.1 hybrid, and 5.0.1 again. 5.11 boot loops and 5.0.1 hangs. Advice please... Thanks
Versions flashed:
"N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.tar" - 5.1.1, boot loops at Verizon screen
"N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar" - 5.1.1/6.0.1 hybrid, boot loops
"N910VVRU2BOG5_N910VVZW2BOG5_N910VVRU2BOG5_HOME.tar" -5.0.1, boots but artifacts and cannot root
"N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.tar" - 5.0.1, booted and rooted/flashed to TWRP, caused hiccups in MM custom roms, cannot get to boot again after a reflash
"N910VVRU2BPA1_StockRestore.tar" -5.1.1 unincremented stock restore, fails on ~90% of odin flash
"N910VVRU2BPA1_StockRestore_Incremented.tar" - 5.1.1 incremented stock restore, flashes, boot loops
Edit: Success!! I flashed the Incremented Stock Restore for 5.1.1 to no avail. It keep boot looping. I cleared the cache and data twice in a last ditch effort, and pulled the USB cord. It booted! Can anyone instruct me on how to proceed to flash only the modem/required portion of 6.0.1 after flashing TWRP? Do I just flash the 6.0.1 modem or modem and kernel?
Edit 2: I flashed the 6.0.1 modem over top of my 5.1.1 full firmware. I have TWRP and CM 13 loaded and working perfectly. From previous experiences, I've noticed CM 13 is more forgiving than some other 6.0.1 custom ROMs. Should I attempt to reflash the Lollipop on MM Stock Rom to obtain the MM bootloader, and then unlock it? This is working fine at the moment.
Edit 3: I reflashed to the hybrid rom and everything's okay. I had to wipe the cache..

mods, you can delete this thread. I solved my issue

av00va said:
mods, you can delete this thread. I solved my issue
Click to expand...
Click to collapse
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk

mwebb34 said:
Hey bud I'm on 6.0.1 can you give me the link to downgrade to 5.1.1 So I can root and unlock
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-verizon/general/note-4-verizon-bootloader-unlock-t3358913 and http://forum.xda-developers.com/not...t/howto-bootloader-unlock-upgrade-to-t3398144 Use the 2nd link 1st to downgrade to 5.1
I had to use Kingoroot(Google it) to root. It was a pain but once you root you have to be patient and leave the phone until it stabilizes after rooting. It took me a few attempts but in the end I'm golden. Part of my problem is a bad battery too but that's another story....

[ROM] MOAR MM Rom v4.1 - Toasted Edition - 07/22/2016

Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1

what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?

FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues

and if I'm on note 5 moar rom with patch.... no issue flashing right?

Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!

Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.

MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.

i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?

FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/

yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?

bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated

fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel

FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?

yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?

FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?

I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?

FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.

Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.

heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding

FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.

Anyone successfully rooted SM-A520W?

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.