Develop Bugs

[Q] Rooted, but not rooted? Need help...

Ive searched the similar thread suggestions and my issue seems to be different...
**BACKSTORY** So I have the sgh-I317...I rooted it a while back and had JellyBEANSTALK 4.2.2 running on it for a while...phone started randomly not waking up from being locked every once in a while so I flashed back to my stock JB 4.1.2 image i had made and flashed the counter so i could take it in to ATT...since flashing back to 4.1.2 I have not had that issue so i am assuming it was something with the ROM
**PRESENT TIME** I decided I wanted to re-root and try CleanROM out...so I got all the necessary stuff I needed (correct drivers and CF Auto Root), followed directions to a T, everything passed, phone rebooted, etc. When i try and use root checker, it just 'searches'...I dont get a 'Not rooted' message or anything...tried installing titanium backup pro root; it installs but when i open it it just says its looking for root access and stays on that screen...ALSO, i do not have SuperSU in my applications but if I go into the Application Manager, SuperSU is there...I also have cwm recovery as well...so its like it partially rooted? Im at a loss right now...anyone have any ideas? Thanks!:good:

jwalck5950 said:
Ive searched the similar thread suggestions and my issue seems to be different...
**BACKSTORY** So I have the sgh-I317...I rooted it a while back and had JellyBEANSTALK 4.2.2 running on it for a while...phone started randomly not waking up from being locked every once in a while so I flashed back to my stock JB 4.1.2 image i had made and flashed the counter so i could take it in to ATT...since flashing back to 4.1.2 I have not had that issue so i am assuming it was something with the ROM
**PRESENT TIME** I decided I wanted to re-root and try CleanROM out...so I got all the necessary stuff I needed (correct drivers and CF Auto Root), followed directions to a T, everything passed, phone rebooted, etc. When i try and use root checker, it just 'searches'...I dont get a 'Not rooted' message or anything...tried installing titanium backup pro root; it installs but when i open it it just says its looking for root access and stays on that screen...ALSO, i do not have SuperSU in my applications but if I go into the Application Manager, SuperSU is there...I also have cwm recovery as well...so its like it partially rooted? Im at a loss right now...anyone have any ideas? Thanks!:good:
Click to expand...
Click to collapse
Download and flash this on cwm.
http://download.chainfire.eu/350/SuperSU/UPDATE-SuperSU-v1.60.zip?retrieve_file=1

jibust said:
Download and flash this on cwm.
Thanks man, but oddly enough, it seems i dont have cwm recovery anymore...looks like its reverted back to the Android system recovery...
Click to expand...
Click to collapse

jwalck5950 said:
jibust said:
Download and flash this on cwm.
Thanks man, but oddly enough, it seems i dont have cwm recovery anymore...looks like its reverted back to the Android system recovery...
Click to expand...
Click to collapse
Download the CWM tar and flash through ODIN, reboot to recovery and flash SuperSU
Click to expand...
Click to collapse

jibust said:
Download the CWM tar and flash through ODIN, reboot to recovery and flash SuperSU
Click to expand...
Click to collapse
Did both...worked like a charm man thanks again!!

jwalck5950 said:
Did both...worked like a charm man thanks again!!
Click to expand...
Click to collapse
Good :thumbup:

Trying like hell to root this thing...

So far ive tried superoneclick... froze on step 7
tried manually installing superuser... couldnt verify.
tried installing a root zip... couldnt verify.
the only thing that claims to have worked is clockworkmod... except that it will NOT allow me access to any of the actual rooted functions.
i was able to download superuser (which you cannot download from google play unless rooted- that worked.)
trying to keep the OS on it now while being able to delete bloatware, for a friend.
is it purely impossible to root a stock rom? why can i install programs that requre root but i cannot use them for their intended purpose (rom manager says it cant find superuser in either of 2 locations).
what the heck am i missing?? ive been googling and trying methods for hours to no avail. cant boot into cwm recovery at all, by rom manager or from powered off (it goes into stock recovery.).
what else can i do?

Pawprints1986 said:
So far ive tried superoneclick... froze on step 7
tried manually installing superuser... couldnt verify.
tried installing a root zip... couldnt verify.
the only thing that claims to have worked is clockworkmod... except that it will NOT allow me access to any of the actual rooted functions.
i was able to download superuser (which you cannot download from google play unless rooted- that worked.)
trying to keep the OS on it now while being able to delete bloatware, for a friend.
is it purely impossible to root a stock rom? why can i install programs that requre root but i cannot use them for their intended purpose (rom manager says it cant find superuser in either of 2 locations).
what the heck am i missing?? ive been googling and trying methods for hours to no avail. cant boot into cwm recovery at all, by rom manager or from powered off (it goes into stock recovery.).
what else can i do?
Click to expand...
Click to collapse
What device do you have? There a several variations of the Tab 3.

gr8nole said:
What device do you have? There a several variations of the Tab 3.
Click to expand...
Click to collapse
in the model number it says sm-t210R
running android 4.1.2
build number jzo54k.t210euwamk1
she needs it back by sunday night so any help would be greatly appreciated

Pawprints1986 said:
in the model number it says sm-t210R
running android 4.1.2
build number jzo54k.t210euwamk1
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2433853

gr8nole said:
http://forum.xda-developers.com/showthread.php?t=2433853
Click to expand...
Click to collapse
saw that but cant use it as i cant get my system to boot in to CWM recovery, to flash a root zip, although it is installed.
cant flash zips with odin.
so im basically stuck.

Pawprints1986 said:
saw that but cant use it as i cant get my system to boot in to CWM recovery, to flash a root zip, although it is installed.
cant flash zips with odin.
so im basically stuck.
Click to expand...
Click to collapse
Did you watch the video in the CWM thread?
Tell me your steps EXACTLY and we'll figure it out.

Finally got it to work. i guess the magic step is not letting odin auto reboot. I was afraid not to let it because its not even mine. But, i followed the video in that thread exactly and that let my root zip install correctly.
phew!

Pawprints1986 said:
Finally got it to work. i guess the magic step is not letting odin auto reboot. I was afraid not to let it because its not even mine. But, i followed the video in that thread exactly and that let my root zip install correctly.
phew!
Click to expand...
Click to collapse
Well actually the guide say rem8ve the check mark of reboot. You most do it by your own.
Send from my SM-T210R (Rocket Tab Rom) using XDA HD Premium

How can i create a back up on my s4 mini

Hi all. I have rooted my s4 mini using kingroot. I have installed adaway and xmod because they were my main reasons for rooting. But i'd like to go a bit deeper now and learn a bit more about rooting as im a novice. But before i can do that ive read that i should create a back up, am i right in thinking a nandroid and a back up are the same thing? Well anyway my problem is ive tried to create a back up using cwm rom recovery but my device is not supported. Ive also read something aboit phils cwm recovery 6 ( at least i think it was called that) but from my understanding i need access to a laptop or a pc to be able to take that route. I dont have access to a pc or laptop at the moment so im just here to ask if anybody can advise me on how i can create a back up for my device. My plan is to learn the ropes using this device as its an old device and when im more comfortable im going to root my galaxy alpha. Any help and answers will be appreciated, im not so great with tech and the lingo but im wanting to learn. Thanks

Unrooted
Well i have unrooted to be safe. My son plays with my phone and i dont feel safe without out a back up or nandroid. I would still like info so i can reroot n get adaway back and xmod for the unlimited lives on candy crush, and sandbox mode on clash of clans. If anybody has any info that could be of any use to me, even just a link to point me in the right direction it would be great.

Try installing TWRP for backups. i am also a beginner but i tried backing up the stock rom, flashing custome roms, And restoring the backups. Done this almost five times a week.
Here are files.
http://forum.xda-developers.com/showthread.php?t=2678420
Some important steps from here
http://techbeasts.com/2014/05/08/install-twrp-2-7-recovery-on-samsung-galaxy-s4-mini-how-to-guide/
Forgot to mention that my stock rom is 4.2.2 Jelly bean. I had flashed cm12.1 rom before, which triggered my knox to 0x1.

Thanks il check those out now

Yes twrp is a good recovery...i am using it too and it can be installed without a pc

Davidich could you direct me to a link or explain how i can install it without using a pc. Do i need root to install it or can i create recovery then reroot? Is it as simple as finding file and installing it by checking unknown sources. Then opening up twrp app and applying recovery? Or do i need to go into download mode to apply it? Any answers will be appreciated. Thanks

Well ive rooted again and installed twrp because i needed root access to enter twrp. When i open twrp it asks me to install busy box, i accept the request but it doesnt download. What is busybox? Do i need it to back up? Ive just read something about mounting system using terminal emulator and then that should allow busybox to download. Am i going in the right direction?

Please Anyone give me a backup of stock rom for Samsung galaxy s4 m919
Sent from my SGH-M919 using xda app-developers app

R1C3Y said:
Well ive rooted again and installed twrp because i needed root access to enter twrp. When i open twrp it asks me to install busy box, i accept the request but it doesnt download. What is busybox? Do i need it to back up? Ive just read something about mounting system using terminal emulator and then that should allow busybox to download. Am i going in the right direction?
Click to expand...
Click to collapse
Busy box can be downloaded directly from play store. As for installing a recovery without a computer well that's RISKY. There are apps that can help like Flashfire, Rashr and Flashify. These can flash various things without a custom recovery. BUT they are not guaranteed to work. My experience is with Flashfire by Chainfire. With this I was able to flash a stock ROM without a computer. But the app when I last looked was in beta stage. Also if something goes wrong you will need a computer to fix... If it hasn't bricked your phone. Sooo much safer thru Odin on a computer.

Install TWRP and backup
Sent from my SM-N910G using Tapatalk

Yes,i used flashify.First i flashed a recovery.img(downloaded from xda) and when i got a custom recovery,i flashed the last version of twrp.at first yes i get a soft brick because flashed a recovery for i9195L but then i re flashed another for i9195 and that's ok.if you want to try: from here download recovery.img ----> http://forum.xda-developers.com/showthread.php?t=2589011 ,when you flashed the recovery...flash this one https://www.androidfilehost.com/?fid=24052804347763032 from recovery

How To Root Latest QE1 Update

How-To Root and Remove Bloatware on the new QE1 Update:
1 ) Via ODIN/OTA/Smart Switch, install the new QE1 update (Firmware links available on SamMobile)
2) ODIN install the TWRP recovery 3.1.1 (TWRP link: https://dl.twrp.me/zenltetmo/)
3) Download the SuperSU zip onto your phone(SU link in this post: https://forum.xda-developers.com/showpost.php?p=72187304&postcount=5)
4) Enter recovery mode and install the SuperSU zip.
You will only get one boot with this zip. If you reboot while still rooted, you will get stuck in boot.
When your phone boots for the first time, you can install Titanium Backup and remove all the bloatware. DO NOT uninstall the Samsung Music app. the stock ROM cannot load without it!!!
When finished removing your apps, open the SuperSU app, go to settings and select Full Unroot. Your phone will reboot and should load normally.
If you ever need root again, repeat step 4 and use your initial boot for your root modifications.

alexknop said:
How-To Root and Remove Bloatware on the new QE1 Update:
1 ) Via ODIN/OTA/Smart Switch, install the new QE1 update (Firmware links available on SamMobile)
2) ODIN install the TWRP recovery 3.1.1 (TWRP link: https://dl.twrp.me/zenltetmo/)
3) Download the SuperSU zip onto your phone(SU link in this post: https://forum.xda-developers.com/showpost.php?p=72187304&postcount=5)
4) Enter recovery mode and install the SuperSU zip.
You will only get one boot with this zip. If you reboot while still rooted, you will get stuck in boot.
When your phone boots for the first time, you can install Titanium Backup and remove all the bloatware. DO NOT uninstall the Samsung Music app. the stock ROM cannot load without it!!!
When finished removing your apps, open the SuperSU app, go to settings and select Full Unroot. Your phone will reboot and should load normally.
If you ever need root again, repeat step 4 and use your initial boot for your root modifications.
Click to expand...
Click to collapse
I can't seem to Odin TWRP correctly. After the reboot, my phone just sits at the T-Mobile screen .... any suggestions?? I keep having to flash QA1 stock rom to get my phone back.

I did this yesterday and after I did the full unroot I got stuck in boot loop at the Galaxy s6 edge + screen. So I just used Odin to get back to normal.

Kidlat917 said:
I can't seem to Odin TWRP correctly. After the reboot, my phone just sits at the T-Mobile screen .... any suggestions?? I keep having to flash QA1 stock rom to get my phone back.
Click to expand...
Click to collapse
I suggest using a different odin version. Try 3.07.
And it might sit on the TMobile screen longer than usual so I would give it at least 5 minutes.

darthmalus said:
I did this yesterday and after I did the full unroot I got stuck in boot loop at the Galaxy s6 edge + screen. So I just used Odin to get back to normal.
Click to expand...
Click to collapse
Why would you unroot ?
Sent from my SM-N900T using XDA-Developers Legacy app

tupirujp said:
Why would you unroot ?
Sent from my SM-N900T using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'd also like to know why this would be necessary. Removing the bloat would make it not possible to receive ota updates anyway, would it not?

Is this phone still rootable?

Markyzz said:
Is this phone still rootable?
Click to expand...
Click to collapse
Why would it not be? All the tools and resources necessary are here, so unless you physically changed hardware in your device, you can still root it. Granted, you may not be rooted with the latest Android OS. But the point is, once the puzzle of root on a given device is solved, root is always available.

bobpantsspongesquare said:
Why would it not be? All the tools and resources necessary are here, so unless you physically changed hardware in your device, you can still root it. Granted, you may not be rooted with the latest Android OS. But the point is, once the puzzle of root on a given device is solved, root is always available.
Click to expand...
Click to collapse
I asked because sometimes a new update will make a device unrootable

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.