Related
Hi Everyone,
I wanted to install custom recovery in my Sony Xperia S L26ii , So rooted it a week ago. It is rooted for sure., I installed titanium backup and backed up everything. Yesterday I did unlock my bootloader so that I can install a custom recovery and custom rom. I followed the procedure of official way of unlocking bootloader by getting the key and unlocked it using fastboot command.
Till This everything works fine.I could boot into my device.
I flashed Twrp recovery adb fastboot. After this I wanted to backup my Stock rom. While I try to perform backup i got an error "unable to mount data" and it was unsucessfull.
I tried to reboot the system and shocked that it is stuck in boot loop now. I am seeing the word "Sony " and again it is rebooting,
I tried whatever I can by browsing internet. It seems I cannot use pc companion since I unlocked bootloader and installed custom recovery.
i tried to download tft file from somewhere and tried to flash through flashtools and got an error "ERROR - Processing of loader.sin finished with errors."
Dont know what to do. Any help would be highly appreciated. All I could access is TWRP recovery . currently I powered off the phone.
Please help me in the right direction.
Regards,
Suresh
ssuresh005 said:
Hi Everyone,
I wanted to install custom recovery in my Sony Xperia S L26ii , So rooted it a week ago. It is rooted for sure., I installed titanium backup and backed up everything. Yesterday I did unlock my bootloader so that I can install a custom recovery and custom rom. I followed the procedure of official way of unlocking bootloader by getting the key and unlocked it using fastboot command.
Till This everything works fine.I could boot into my device.
I flashed Twrp recovery adb fastboot. After this I wanted to backup my Stock rom. While I try to perform backup i got an error "unable to mount data" and it was unsucessfull.
I tried to reboot the system and shocked that it is stuck in boot loop now. I am seeing the word "Sony " and again it is rebooting,
I tried whatever I can by browsing internet. It seems I cannot use pc companion since I unlocked bootloader and installed custom recovery.
i tried to download tft file from somewhere and tried to flash through flashtools and got an error "ERROR - Processing of loader.sin finished with errors."
Dont know what to do. Any help would be highly appreciated. All I could access is TWRP recovery . currently I powered off the phone.
Please help me in the right direction.
Regards,
Suresh
Click to expand...
Click to collapse
It is the "ftf" file, not "tft". Try Flashing the stock ftf file immediately again after You get the error, it will work. You get the error first time.
Mirhawk said:
It is the "ftf" file, not "tft". Try Flashing the stock ftf file immediately again after You get the error, it will work. You get the error first time.
Click to expand...
Click to collapse
Thank you bro for replying and correcting me. Yes ftf file. I am downloading stock ftf from XDA forum (thanks for the member) and Will try to flash it (by pressing volume down and connecting usb cable to it) and will let you know.
Im just wondering , yesterday when I saw the phone in bootloop , I paniked and try to perform factory reset couple of times . Though it did not help in anyway. Will it disable usb debugging? If so is there any way we can reenable it from recovery or any other way?
-Suresh
ssuresh005 said:
Thank you bro for replying and correcting me. Yes ftf file. I am downloading stock ftf from XDA forum (thanks for the member) and Will try to flash it (by pressing volume down and connecting usb cable to it) and will let you know.
Im just wondering , yesterday when I saw the phone in bootloop , I paniked and try to perform factory reset couple of times . Though it did not help in anyway. Will it disable usb debugging? If so is there any way we can reenable it from recovery or any other way?
-Suresh
Click to expand...
Click to collapse
Nah it won't affect You while flashing the ftf file. You can always flash the ftf file using flashtool by fastboot, no matter what.
Mirhawk said:
Nah it won't affect You while flashing the ftf file. You can always flash the ftf file using flashtool by fastboot, no matter what.
Click to expand...
Click to collapse
Bro, You are great. That worked. It did revoked my root and locked bootloader though. But that is fine. I could do root and unlock the bootloader again..
A quick question. It all happened when I flashed TWRP recovery in this phone using this link (http://techglen.com/2014/02/12/install-twrp-custom-recovery-on-xperia-s-lt26i-nozomi/2/). I have already flashed TWRP in another HTC but it never caused this issue.
Is there any issue in installing TWRP in xperia sl ?
Should I use only CWM recovery?
If i can use Twrp , is there any good way/post or steps you recommend.?
Many Thanks again:good:
-Suresh
ssuresh005 said:
Bro, You are great. That worked. It did revoked my root and locked bootloader though. But that is fine. I could do root and unlock the bootloader again..
A quick question. It all happened when I flashed TWRP recovery in this phone using this link (http://techglen.com/2014/02/12/install-twrp-custom-recovery-on-xperia-s-lt26i-nozomi/2/). I have already flashed TWRP in another HTC but it never caused this issue.
Is there any issue in installing TWRP in xperia sl ?
Should I use only CWM recovery?
If i can use Twrp , is there any good way/post or steps you recommend.?
Many Thanks again:good:
-Suresh
Click to expand...
Click to collapse
Weird. It should not lock Your bootloader, since locking bootloader has different procedure. Anyways, TWRP works fine with Xperia SL. Even My phone is a SL and I always use twrp. Which version where You using of twrp? Use this version. And flash it using the command by connecting Your phone in fastboot mode:
Code:
fastboot flash boot openrecovery-twrp-2.8.0.1-LT26i.img
Mirhawk said:
Weird. It should not lock Your bootloader, since locking bootloader has different procedure. Anyways, TWRP works fine with Xperia SL. Even My phone is a SL and I always use twrp. Which version where You using of twrp? Use this version. And flash it using the command by connecting Your phone in fastboot mode:
Code:
fastboot flash boot openrecovery-twrp-2.8.0.1-LT26i.img
Click to expand...
Click to collapse
Bro. I flashed this recovery and now after reboot phone is going to recovery only. I manually tried to reboot it to bootloader and it is getting to TWRP recovery only. I tried to flash a Kitkat rom which was in my internal memory as zip file it failed with error " error executing updater binary in zip" did google search on it and got to know to overcome this error I had to be on TWRP 2.8.0.1 but we are already in that code, I dont know why I was still getting that error.
So I used the ftf file again to flash . I followed the forum "http://forum.xda-developers.com/showpost.php?p=28305266&postcount=3" to get the ftf file. I could see there are ftf for ginger bread and ICS , but I could only flash Ginger bread since I am getting error when I flash ICS ftf. not sure why.
Now having stock Ginger Bread rom rooted and bootloader unlocked.
I am happy that you brought me this far. It Would be great if you could guide me to proceed further to install any custom recovery and any custom rom of Jelly bean and higher. :good:
- Suresh
I also wanted to try something before you come online . so flashed the custom recovery which you have provided and flashed cyanogenmod 9 latest nightly and current status is
Rooted, bootloader unlocked, installed custom recovery(TWRP){with your wonderful assistance} , flashed cyanogenmod 9 nightly(ICS)
All I need now is a jelly bean rom or KITKAT rom (preferable )
ssuresh005 said:
All I need now is a jelly bean rom or KITKAT rom (preferable )
Click to expand...
Click to collapse
My Bad, that procedure installs a Kernel, and since it was not compatible with the ROM You were using, it only booted to the twrp. Copy the file to Your internal sdcard and use these following commands on Terminal Emulator app from playstore:
Code:
su
dd if=/sdcard/fotakernel.img of=/dev/block/mmcblk0p11
where fotakernel.img is the name of Your .img file.
It was weird that You go that error while flashing a Kitkat ROM. Which ROM were You trying to flash? If You wan to flash a Kitkat ROM, then follow the procedure here, no matter which Android version You are on, no need to do anything else.
[Q] Need help in solving "Unfortunately, settings have stopped working" error
Problem: My unrooted SGH-I747 model AT&T GS3 recently gave me this error whenever trying to access the settings. The error shows up even after a full factory reset and I can no longer access my phone. Stuck a little after the language selection in the beginning stages of the setup.
Attempted fixes: Obviously, the initial factory reset. Then clearing the cache + factory reset.
After those failed to work, I tried to flash to a AT&T stock rom from this forum (http://forum.xda-developers.com/showthread.php?p=33570269#post33570269) using Odin. I tried to use the first row of downloads but the first row but it did not have a MD5 file, so I used the second row of downloads instead but this rom failed to install. My guess is that it may be too old of a version.
I would appreciate any help.
[SOLVED]
The problem may have arose from a critical error in the phone's software that had affected the OS system of the phone. I resolved the issue by flashing a new custom OS (cyanogenmod) to my phone. These are the steps that I took:
1. Installing Odin (http://forum.xda-developers.com/showthread.php?t=1722686)
2. Rooting my cellphone with CFAutoRoot using Odin (http://forum.xda-developers.com/showthread.php?t=1725839)
3. Installing a custom recovery TWRP -- highly recommended very user friendly (http://forum.xda-developers.com/showthread.php?t=1793224)
4. Installing a new custom rom through TWRP-- used Cyanogen (http://forum.xda-developers.com/showthread.php?t=1778270)
5. Installing gapps (http://opengapps.org/?api=5.1&variant=nano)
6. Identifying the correct bootloader by downloading and installing Samsung Phone Info by vndnguyen through the Play Store.
7. Installing the correct bootloader and modem (http://forum.xda-developers.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006)
Please refer to respective installation guides for more instructions regarding installation of any new software.
I hope this helps anyone who may have run into the same problem.
Before attempting to flash anything, confirm the bootloader on your phone. An easy way to determine if the bootloader is 4.3 or newer, boot into download mode. If you see anything about warranty bit, your phone has at least a 4.3 bootloader and no attempts should be made to flash anything from sammobile.com.
If you have a 4.3 or newer bootloader, I recommend flashing a custom recovery such as TWRP, and then flashing a stock ROM from recovery.
First off, thank you for the reply audit!
Now I have officially rooted my phone using CF-Autoroot and have installed TWRP. I have also confirmed that the bootloader is at least 4.3 because it does show the warranty bit.
Which of the stock roms are compatible with this bootloader?
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
audit13 said:
Do you want to stay on a stock ROM? If not, you could flash a custom ROM such as cm12.1 using TWRP. Once you have flashed a custom ROM, you can look under settings to determine the baseband on the phone which is another clue as to which bootloader is on your phone.
Click to expand...
Click to collapse
Just to be clear, cm12.1 is the cyanogenMod nightly?
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
audit13 said:
Yup. If you flash it, your baseband may be unknown which tells me you are probably not running a 4.4.2 bootloader and modem.
Click to expand...
Click to collapse
I'll try it out and see if I can get past the language screen this time.
Got the latest Cyanogenmod Zip file onto my phone. Tried flashing it through TWRP with the install option but it failed.
Log reads that no MDS file was found, detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system. Can't install this package on top of incompatible data.
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
5K posts.
"all i can really do , is stay out of my own way and let the will of heaven be done"
I'm pretty sure that CM de-unified the variants for CM 12.
From: https://wiki.cyanogenmod.org/w/D2lte_Info
Note: Unified device
Between the release of CM 11 M3 and CM11 M12, all Qualcomm-based variants of this device were merged into a single build: d2lte. The device information pages for the individual variants should be used to reference any device-specific unlock instructions, download recoveries, to build CM 10.2, or to install CM 12.1: d2att, d2cri, d2mtr, d2spr, d2tmo, d2usc, d2vzw.
Click to expand...
Click to collapse
I think this was just to make searching a bit harder/ more complicated.
audit13 said:
CM12.1 won't have an md5 file. You're trying to install cm12.1 for the d2att or d2lte? You're running the latest TWRP which I believe is 2.8.7.0? or 2.8.7.1?
Click to expand...
Click to collapse
For d2att and running 2.8.7.0 for TWRP.
You should be good then.
The file should be left unzipped/unrared when using it right? I'm using it as such but it keeps returning the same error message saying that it won't install it.
Yes, leave it zipped. What is the TWRP error message?
The error log:
detected filesystem ext4 for /dev/block/platform msm_sdcc.1/byname system.
Can't install this package on top of incompatible data.
Please try another package or run a factory reset
E: Error executing updater binary in zip '/sdcard/Download/cm-12.12015913-NIGHTLY-dtatt.zip
Error flashing zip '/sdcard/Download/cm-12.120150913-NIGHTLY-D2att.zip
Weird, did you do a full wipe before trying to install?
Can't believe it was that simple. I thought I had already made the wipe when I did it with the original recovery but making a second wipe through TWRP actually helped make it happen. I finally got through and have full access to my phone.
Unfortunately, the cell service doesn't seem to work but I'm guessing that I need to do more for the set up?
Edit: Not recognizing the sim card for some reason
Sounds like you need to update the bootloader and modem to the older KK version which I think is ne4.
Sorry for the late reply I've been busy the past week. I'm guessing the modem won't work without the proper bootloader? I've tried flashing the latest and original modem from the Modem list (http://forum.xda-developers.com/showthread.php?t=1831898). While they installed successfully I still don't get a signal.
I was worried which bootloader to take because it may lead to bricking. Which one are you referring to and are they in the Bootloader updates topic here? (http://forum.xda-developers.com/showthread.php?t=2321310)
After I got my nexus 5x, I unlocked bootloader and root, and finally I go back official stock 6.0.1. But the camera didn't work fine(sometimes black screen, and then phone reboot). Have to flash CM13.
Following the guide, I did those steps strictly. Yet failed.
- When I tried to install CM13.zip, the TWRP told me I had to decrypt , and need to enter the default password which I don't know/have.
- I tried another way, flash official recovery.img . Failed again: the official recovery told me "can't mount SDcard", update zip file from sd card failed.
How can I install CM13 now? Or, how can I solved the camera issue?
I feel terrible about this, could you guys help?
thank you
faytuu said:
After I got my nexus 5x, I unlocked bootloader and root, and finally I go back official stock 6.0.1. But the camera didn't work fine(sometimes black screen, and then phone reboot). Have to flash CM13.
Following the guide, I did those steps strictly. Yet failed.
- When I tried to install CM13.zip, the TWRP told me I had to decrypt , and need to enter the default password which I don't know/have.
- I tried another way, flash official recovery.img . Failed again: the official recovery told me "can't mount SDcard", update zip file from sd card failed.
How can I install CM13 now? Or, how can I solved the camera issue?
I feel terrible about this, could you guys help?
thank you
Click to expand...
Click to collapse
Update TWRP to 3.0.0-1
You can't flash anything worth flashing with stock recovery.
Make sure you are using the latest stock version "J" as it has alot of fixes for this like the camera error.
Darke5tShad0w said:
Update TWRP to 3.0.0-1
You can't flash anything worth flashing with stock recovery.
Make sure you are using the latest stock version "J" as it has a lot of fixes for this like the camera error.
Click to expand...
Click to collapse
Thanks for your reply. I will try TWRP 3.0.0.1 for bullhead
Yes, I'm using the MHC19J build. I still got the camera issue, and tired for that (this is the reason why I want flashing CM13). Do I need to format userdata while I always get the red warning at booting ?
SOLVED http://forum.xda-developers.com/nexus-5x/general/learn-using-nexus-5xwith-official-stock-t3342616
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.
Anyone on the above rom having trouble with update?? I use the rom updater on the phone and it showed a new update for 8-12-18 I've downloaded the file twice with the same outcome, pops up an error that just says install error?? Any of the updates before that installed fine..
blake .l said:
Anyone on the above rom having trouble with update?? I use the rom updater on the phone and it showed a new update for 8-12-18 I've downloaded the file twice with the same outcome, pops up an error that just says install error?? Any of the updates before that installed fine..
Click to expand...
Click to collapse
Download and install with twrp. If that build has treble and the one you're using doesn't, you need to flash with twrp for it to change OEM to vendor which the installer cannot do in boot time. It can be dirty flashed if the keys are the same. (I.E. test key to test key. If its from the same source, it is the same)
Uzephi said:
Download and install with twrp. If that build has treble and the one you're using doesn't, you need to flash with twrp for it to change OEM to vendor which the installer cannot do in boot time. It can be dirty flashed if the keys are the same. (I.E. test key to test key. If its from the same source, it is the same)
Click to expand...
Click to collapse
I got the file downloaded but when I go into TWRP and try to install I get this error.
Error applying update: 7 (ErrorCode: :
kInstallDeviceOpenError)
Update process ended with ERROR: 1
blake .l said:
I got the file downloaded but when I go into TWRP and try to install I get this error.
Error applying update: 7 (ErrorCode: :
kInstallDeviceOpenError)
Update process ended with ERROR: 1
Click to expand...
Click to collapse
Try with https://androidfilehost.com/?fid=3700668719832238233
Uzephi said:
Try with https://androidfilehost.com/?fid=3700668719832238233
Click to expand...
Click to collapse
Worked like a charm, Thanks!!
crazy question, how do i install magisk now? I've tried it with the older twrp i was using and I've tried it with the newer version twrp you suggested and i get boot loop now. I tried with the lineage recovery and it fails?