Related
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Root works with supersu version 2.62-3. Thanks
sam298 said:
From rooted 6.0, I took the OTA and was stuck. Finally wiped everything and installed 6.0.1 fresh. flashed TWRP and supersu 2.60. But after boot, Supersu says binary needs to be updated - but fails to update.
TWRP works fine. Just can't root 6.0.1 with unlocked bootloader. Can anyone share the supersu that worked for 6.0.1? TIA
Click to expand...
Click to collapse
That wasn't my experience. I took the 6.0.1 update and it failed. So I ran
Code:
fastboot flash system system.img
fastboot flash boot boot.img
using the system and boot images from the 6.0 update. And then I waited for the OTA again. It installed ok.
Using TWRP I installed SuperSU 2.60 for a systemless root of the boot image. Everything is fine.
i can't even get pass installing twrp. every time i flash twrp in fastboot mode it works but it wipes my entire device. booting into twrp shows "NO OS INSTALLED' and even the sd card storage is wiped. the only way to get it to boot is to flash back 6.0.1 full stock rom. any help???
Try nexus root toolkit.
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
WugFresh did not work for me, after booting into TWRP and looking for the SuperSU and BusyBox they don not show up. Below is a post I have over on WugFresh Forum.
I’m having the same problem as everyone else. I’m using 6.0.1 MMB29K. It goes through the motions but when TWRP launches the /sdcard directory is empty. However, when I reboot and look at the files using an app called File Manager, I see them in /storage/emulated/0/!ReadyToFlash/Root_Files/. However, if I use a app called Root Browser I see a directory called sdcard and in there is !ReadyToFlash/Root_Files/ so they are being copied to the tablet but when you go into TWRP to install them they can’t be found. I tried to use the app Root Browser and make a directory called kiledl, this failed, probably because I do not have root access. Kind of a catch 22 here. I was just going to copy the files in sdcard to my directory and then try again. NO go!!! Anyone else have any ideas? I seems like this is some sort of permissions issue with the files but only from TWRP. I sure hope someone comes up with an answer, WugFresh and ideas?
tomxass said:
Try nexus root toolkit.
Click to expand...
Click to collapse
same result. twrp installed but can't detect my sd card or any files on the device
Download latest SuperSU 2.62-3.
Root via Nexus root toolkit.
Then copy SuperSu to nexus and flash, supersu not from NRT but downloaded latest 2.62-3, busybox and last rar.
Sorry for my English.
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
dlkile said:
Found a solution, the version of TWRP that WugFresh NRT is using is not compatible with this version of the N7 seems as though these were made with a different MMC memory. Check you this link and download this modified version of TWRP. You can use the NRT Advance Utilities > fastboot flash > recovery > other and then point to this modified version of TWRP and install it. Then you can proceed with the install of SuperSU and BusyBox. They will show up in the !ReadyToFlash/Root_Files/ folder to install.
Check this link **UPDATE** Mounting Errors in Custom Recovery
**UPDATE** Mounting Errors in Custom Recover… | Nexus 7 (2013)
Click to expand...
Click to collapse
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
aiiee said:
noooo. That's not true. I just used NRT yesterday to upgrade to rooted 6.01.
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
aiiee said:
EDIT: I think I misundersstood your post. This is only a problem if you try to install TWRP when upgrading right? If you just want to upgrade to 6.01 and keep stock recovery there is no issue.
Click to expand...
Click to collapse
Correct only when using TWRP. However, I was using WugFresh NRT and it does a temporary install of TWRP then you install the SuperSU and BusyBox files. However, with the wrong version of TWRP you would not see the files in the SDCard folder, it would be empty. However, booting back to Android and using File Explorer the files where there. Using the modified version of TWRP would correct this.
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
r.sorujlall said:
interesting. i was wondering why some persons say it work and when i tried it, it wouldn't show anything in twp. can you point me to the link of the modified/correct version of twrp to use or help me by saying what to search. i don't want to sound lazy bu asking you for the link but i'm not sure as to what to google exactly to find the correct twrp to use. obviously i've been google wrong the pass few days because that hasn't come up for me in any of my past searches
Update: i found it and it works. thanks guys. now i can flash some custom roms. gonna try cm 13 tonight. thanks again
Click to expand...
Click to collapse
Yes, here is the link you need to select the LTE or WiFi version depending on you device. I do not have enough post to be able post links, so try removing the "*" from the link below.
forum*.xda-developers*.com/nexus*-7-2013/nexus*-7-2013-qa/mount*-recovery*-t3064562
dlkile said:
Yes it is true, it depends on what kind of eMMC chip is in it. I have a very new device and NRT would not root it. When it booted in TWRP it could not see the !ReadyToFlash/Root_Files/ folder to install the files. There was no files on SDCard at all unless you booted to Android to verify they were in fact there. I had to install the modified Recovery TWRP file first. Saying "noooo. That's not true." is a little harsh, kinda make me a liar, I think NOT. Just because the method worked for you does not mean it worked for me. Not all devices are the same. If you read other post here you will see lots of others are having the same problem.
Click to expand...
Click to collapse
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
aiiee said:
I sit corrected, sir. :good:
Just for my own edumacation, how old is your N7? I just bought two from Groupon and I wonder if they are affecteed? How can one tell ?
Click to expand...
Click to collapse
You most have the same unit as I do. I just got mine a week ago from GroupOn as well.
i bought mine about a week ago off amazon. i had a gift card and had nothing to buy so i decided to get the N7 and give it a try
Hello everyone.
I am newbie here.
I own t-mobiles lg g3 and updraded to marshmallow as the ota updates became available. But due to certain reasons, i wanted to install custom rom. The primary hurdle was rooting the device. Through trial and error method i have now successfully installed the fulmics 5.3.
I want to share my experience in this regard.
Device : d851 ( t-mobile lg g3)
Software veesion : 6.0 official marshmallow.
Root :-
Through mobile's browser, google for kingsroot. Download and install. ( donot reboot as this is temporary root, one the cell is rebooted the device will regain its previous status).
download twrp.image for d851 and save in sd card.
Now download flashify from play store and open the app. It will give three options. Select the first option ( browse image file or some thing like this) and select the twrp file you have recently downloaded. The flash will b completed in few seconds.
Congratulations, you have installed twrp.
Download a copy of custom rom ( fulmics 5.1 recommended) and save in sd card.
Now reboot the device in recovery mood ( either by turning off the cell, and then pressing simultaneously volume down+ power button, as the lg logo appears, release the power key and again press it. You will see two options, select the YES twice.
In recovery mode, first select wipe, advance wipe, system and then slide to wipe. Once done, go back and install the custom rom. After the successful installation, dont select the reboot option. Instead go back and again select wipe, factory reset.
congratulations, rom has been installed.
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
Enjoy the new custom rom.
Thanx.
Sorry for poor presentation and, offcourse, my weak english.
Man! Thanks for this! I have been looking everywhere for a way to do this and you are all the help I needed! Thank you!!!
If i may ask you, where can we get the modem and which one do you recommend? I have tried this and always i get the imei, baseband and number unknown
Enviado desde mi LG-D851 mediante Tapatalk
imrock666 said:
If i may ask you, where can we get the modem and which one do you recommend? I have tried this and always i get the imei, baseband and number unknown
Enviado desde mi LG-D851 mediante Tapatalk
Click to expand...
Click to collapse
google for this
downloads.codefi.re/autoprime/LG/LG_G3/D851/stock_partitions/30D/LG-D85130D-Flashable.Modem.zip
Sure could have saved a lot of time if I had found this first.
I did install TWRP using a kingroot temporary root, got lost in a boot loop installing Fulmics 5.1 lost my data connection and imei information and finally downgraded back to stock Marshmallow feeling blessed to have restored my data connection. Had just finished transferring the flashable modem zip over to the SD card with an idea that I would try to move the mountain once more when I stumbled across your post which is priceless with the wealth of solutions to the problems I've had to overcome with the install. Flashify was the route to go. Lost TWRP on last flash and was just about to go through my torturous route of installing Fulmics 5.1 from scratch (root/adb/twrp/rom/bootable modem/etc.. Instead in the time it took to sign up so I could thank you for the easiest directions to this LG G3 D851 nightmare, I'm up an running on Fulmics 5.1 with full data connection. Your method eliminated a lot of the problems introduced by going the other route. Also you highlighted the main things. The factory reset is crucial and with the tricky temp root of Kingroot, it's easy to get stuck. Same with SuperSU flash/WRP and the modem flash. This should be a sticky on most sites related to LG G3 because it is the simplest way to go.
Jesus christ! Is this the only way to root my t-mobile D851? Seems like this is a dangerous way to live! Lol. But Really...
thank you, i will try it could you please give me fulmatic 5.3 room link for (d851)
Thanks for sharing
I am a newbie and do not have much experience with rooting or installing flash. But I followed your instruction and installed the fulmics.. I am struggling to flash the modem file. Can you please provide step by step instruction to do that pls. I am using flashify app
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
I am no expert either, but I believe you need to flash it in TWRP. Boot in to TWRP recovery and flash the modem zip. TWRP recovery-> Install-> modem zip-> reboot when finished
KingoRoot just seems shady to me, I wouldn't touch it personally. Here's what I did (just yesterday), from Stock MM Unrooted:
Downgrade back to original factory stock image: http://www.androidexplained.com/downgrade-lg-g3/
Root (used PurpleDrake "manual" method as auto script didn't work): http://lgg3root.com/lg-g3-root/how-to-root-lg-g3/
Once rooted, install SuperSU & TWRP Manager from Play Store
From TWRP Manager install latest version of TWRP
Boot into TRWP and do a factory reset/clear cache; flash ROM (Blisspop for me, but same general steps should apply for any ROM) and Gapps from TWRP; factory reset/clear cache again for good measure
Edit: Data works with 20B modem.
How to prevent apps from being unistalled in stock rom? In other roms u can lock the package installer .
In stock simply u just hold and drag the app to unistall button . installation of an app can be locked but unistallation cant be locked . is there anyone to solve the issue . sorry for bad english
i flashed another kernel and it is not that good... is it possible to find the kernel and just flash it ? without reflashing the rom?
KingRoot is not working for me, says Root Failed, somebody know why? What can i do?
Shady282 said:
i flashed another kernel and it is not that good... is it possible to find the kernel and just flash it ? without reflashing the rom?
Click to expand...
Click to collapse
You should be able to get the stock kernel back by "dirty flashing":
-boot into recovery (twrp)
-flash ROM *without* wiping anything.
Not to lecture, but this can all be prevented by following this simply advice:
-ALWAYS take a backup before flashing anything/customizing this or that.
-ALWAYS double and triple check that the ROM/Kernel/Whatever you're flashing is for your SPECIFIC MODEL and CARRIER.
Happy modding
Semi Fahid said:
Hello everyone.
I am newbie here.
I own t-mobiles lg g3 and updraded to marshmallow as the ota updates became available. But due to certain reasons, i wanted to install custom rom. The primary hurdle was rooting the device. Through trial and error method i have now successfully installed the fulmics 5.3.
I want to share my experience in this regard.
Device : d851 ( t-mobile lg g3)
Software veesion : 6.0 official marshmallow.
Root :-
Through mobile's browser, google for kingsroot. Download and install. ( donot reboot as this is temporary root, one the cell is rebooted the device will regain its previous status).
download twrp.image for d851 and save in sd card.
Now download flashify from play store and open the app. It will give three options. Select the first option ( browse image file or some thing like this) and select the twrp file you have recently downloaded. The flash will b completed in few seconds.
Congratulations, you have installed twrp.
Download a copy of custom rom ( fulmics 5.1 recommended) and save in sd card.
Now reboot the device in recovery mood ( either by turning off the cell, and then pressing simultaneously volume down+ power button, as the lg logo appears, release the power key and again press it. You will see two options, select the YES twice.
In recovery mode, first select wipe, advance wipe, system and then slide to wipe. Once done, go back and install the custom rom. After the successful installation, dont select the reboot option. Instead go back and again select wipe, factory reset.
congratulations, rom has been installed.
But you will observe sim card is not read by device. This is because cell was not properly rooted. To tackle this problem, download the modem file for D851 and flash it.
Enjoy the new custom rom.
Thanx.
Sorry for poor presentation and, offcourse, my weak english.
Click to expand...
Click to collapse
I did this but got stuck on the LG logo boot screen. What am I doing wrong?
Hi guys, I did the safe upgrade on my DevEd from 5.1.1 to 6.0.1. TWRP 3.0.2-0 starts up correctly. Then I try to choose any zip file to flash and TWRP immediately restarts itself instead of flashing it. Did I do something wrong with this upgrade, and why can't I flash anything using TWRP?
Well for anyone who reads this, I found the solution. By default, I can't use my external SD card for anything. Once I copied the files to the internal SD I was able to flash things.
Also it seems that I had to root the device first by forcing SuperSU to flash using FlashFire before it was going to accept any flashes, I don't think TWRP specifically requires you to have Android rooted but probably it set up directories or permissions or something by doing that.
FMXP said:
Well for anyone who reads this, I found the solution. By default, I can't use my external SD card for anything. Once I copied the files to the internal SD I was able to flash things.
Also it seems that I had to root the device first by forcing SuperSU to flash using FlashFire before it was going to accept any flashes, I don't think TWRP specifically requires you to have Android rooted but probably it set up directories or permissions or something by doing that.
Click to expand...
Click to collapse
wow 2 days messing around with this. man oh man thank you for the find.
works great!
I am rooted and unlocked still on 5.1.1 I updated to MM bootloader was unlocked after I updated but couldn't get root with the NewKingRoot app. It didn't give me the option to root. I also tried KingOroot and it failed also. When I was on MM when I rebooted my device I didn't see the custom lock icon on the splash screen but when I booted to download mode it said Mode developer. I work so much I can only spend a few hrs a day working on this. I would however rather go back to 4.4.4 I really miss kitkat.
Sent from my SM-N920F using Tapatalk
Having the same problem. I finished Bootloader Unlock and Upgrade to Marshmallow and now sitting on unrooted with recovery 3.0.2-0. I was rooted but one of the things I tried is a factory reset, Just throwing anything at it to see if it sticks.
ANYWAY If I try to flash supersu it starts listing activity. Gets to "creating space" phone immediately crashes when that displays with a vibration and can't turn phone back on without a battery pull. I have reflashed twrp via odin. I've tried flashing supersu from both internal and external card. No joy. I also tried checking mount system. It will crash with setting default off. Anyone have any ideas on what could be the problem?
My guess is it's something I'm not thinking and if I get a fix before anyone post I post it.
edit:
Well I could never get it to flash supersu but I did restore the Jasmine 7.0 backup. So that worked.
Hi there,
I have a Huawei Rio L02, Australian Vodafone version.
I wanted to root my phone so I could use the gyroscope feature.
I was following a guide and managed to unlock the bootloader and install TWRP and SuperSU ok, upon trying to install cyanogenmod I got error 7 and it said to wipe the system which i did and still got error 7. (I did not realise at this time the stock firmware needed to be updated to marshmallow before installation) so I wiped the files again and didn't realise until it was too late I had system checked. Now I can access TWRP, but I can not figure out how to install any firmware on the device.
- I have tried multiple stock firmwares
- I have tried the forced update and fastbootloader methods
- I have tried manually installing the files using TWRP
I had a backup file, but unfortunately did not back it up to my pc before wiping my system, stupid and a noob mistake I know.
If anyone has a Nandroid backup of the stock system that would be fantastic (If you can use a same model, but different devices backup)
Any Ideas? Is there an old version of cyanogenmod i could install without any O.S. on the device and would this allow me to update to the newer cyanogenmod?
Would really appreciate any assistance.
Thank you
Easiest way IMO would be to download stock firmware, put it on sdcard in dload folder.
Turn off the phone. Press and hold Vol_ & Vol+, press power button. Huawei firmware update will start. You'll have stock firmawer without root and twrp.
That's why I always keep, stock firmware on sd card in dload folder so can quickly flash stock firmware if something goes wrong
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.