Hello,
About two years ago with the help of this page I was able to ROOT and load a Cyanogenmod ROM on my former Motorola Xoom Tablet. I don't remember how I did it. I just remembered it worked.
I now have a Samsung Galaxy Tab pro 8.4 (SM-T320). Samsung said on its ROM related pages that Android 5 was coming for the SM-T320 in Q3 or Q4 of 2015. Well I am tired of waiting. So I remembered this page and here I am. I do see that a new (non-nightly build) of Lollipop will soon be available. My present Tablet has Android 4.4.2. So you can see why having Android 6 would be nice. My SM-T320 has never been rooted.
I have hunted this page and few others and I have found various threads on how to load a Cyanogenmod ROM. But, they all offer various paths and steps and are not the same. My hope is that some more experienced user can point me to a guide or video that is written like 'How to do XXX for dummies.' Thank you in advance for your help.
6 is Marshmallow not Lollipop. Everything else should be scattered around the forum (especially the CM13 thread) for you to see.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
Though no official word (outside a UK Twitter Feed), was ever given. It would seem that the Qualcomm Tab Pro's:
8.4
SM-T320 (Wi-Fi)
SM-T321 (3G)
SM-T325 (LTE)
10.2
SM-T520 (Wi-Fi)
SM-T521 (3G)
SM-T525 (LTE)
Will never be updated past its stock 4.4.2 (KitKat) ROM.
Rooting these Devices is simple enough with Towelroot. But, if you go 'round messing with Custom ROMs, and are Recoveries. Your gonna tripnthe Knox Flag, meaning that you'll never be able to use, or access such Data you might have had there from that Device ever again.
That said it's a fair comp that you probably could care less. But, just note that the Knox Flag will trip if you go though with it, and that you’ll be greeted by such warnings when you cold boot then Device. To the effect of "Kernel is not SELinux enforcing".
bigfootnmd said:
I have hunted this page and few others and I have found various threads on how to load a Cyanogenmod ROM. But, they all offer various paths and steps and are not the same.
Click to expand...
Click to collapse
There are always going to be slightly different ways to skin a cat. With some differences depending on your personal preferences.
In general, you need to:
1) Root by towelroot or CF Auto-root
2) Install custom recovery. That can be TWRP or CM recovery (or even CWM, but I don't think our device is officially supported). Custom recovery can be installed by Odin, or by app (such as TWRP Manager or Flashify)
3) Put the ROM on the phone (whether you download to the device, or transfer it using a computer) either on internal storage or removable SD card
4) Boot into custom recovery, full wipe (data, Dalvik and cache) then flash the ROM
5) Reboot and drink beer, because you are now on Marshmallow
A more detailed guide is here: http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/qa-how-to-root-install-custom-recovery-t3087451
Personally, I rooted using CF Auto-Root by process similar to that described in the guide. But I then installed TWRP by Odin as described here (with TWRP downloads): https://twrp.me/devices/samsunggalaxytabpro8.4exynoswifi.html
Rooted and used TWRP app to load TWRP
Hello,
I successfully rooted my Samsung Galaxy Tab PRo 8.4 WIFI. I downloaded the TWP app from the Google Playstore. I downloaded the latest TWRP image. Tablet reboots and the TWRP version 3.0.0-2 loads.
However, GEE where did this APP put the recovery image? I cannot find it. I can't seem to find it on the SD card or Internal storage. Where might this app have put it? If I don't know where it is then how can I install it? YES I did look in the Download folder on the SD card. It is not there. It isn't in the download folder on the internal storage. So, Tablet on boots into recovery mode.
Any help or insight will be appreciated.
redpoint73 said:
There are always going to be slightly different ways to skin a cat. With some differences depending on your personal preferences.
In general, you need to:
1) Root by towelroot or CF Auto-root
2) Install custom recovery. That can be TWRP or CM recovery (or even CWM, but I don't think our device is officially supported). Custom recovery can be installed by Odin, or by app (such as TWRP Manager or Flashify)
3) Put the ROM on the phone (whether you download to the device, or transfer it using a computer) either on internal storage or removable SD card
4) Boot into custom recovery, full wipe (data, Dalvik and cache) then flash the ROM
5) Reboot and drink beer, because you are now on Marshmallow
A more detailed guide is here: http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/general/qa-how-to-root-install-custom-recovery-t3087451
Personally, I rooted using CF Auto-Root by process similar to that described in the guide. But I then installed TWRP by Odin as described here (with TWRP downloads): https://twrp.me/devices/samsunggalaxytabpro8.4exynoswifi.html
Click to expand...
Click to collapse
redpoint73 said:
In general, you need to:
1) Root by towelroot or CF Auto-root
2) Install custom recovery. That can be TWRP or CM recovery (or even CWM, but I don't think our device is officially supported). Custom recovery can be installed by Odin, or by app (such as TWRP Manager or Flashify)
3) Put the ROM on the phone (whether you download to the device, or transfer it using a computer) either on internal storage or removable SD card
4) Boot into custom recovery, full wipe (data, Dalvik and cache) then flash the ROM
5) Reboot and drink beer, because you are now on Marshmallow
Click to expand...
Click to collapse
1) is unnecessary - flashing TWRP with PC via Odin does not require root.
bigfootnmd said:
However, GEE where did this APP put the recovery image? I cannot find it. I can't seem to find it on the SD card or Internal storage. Where might this app have put it? If I don't know where it is then how can I install it? YES I did look in the Download folder on the SD card. It is not there. It isn't in the download folder on the internal storage. So, Tablet on boots into recovery mode.
Any help or insight will be appreciated.
Click to expand...
Click to collapse
I don't really get what you want to know, but recovery is a separate partition on the device you can't access normally. After flashing a recovery it gets written into that partition for permanent access. You won't find the recovery image anywhere on your storage.
Sent from Google Nexus 6P @ CM13
[WARNING: XDA One have not implemented "mark forum as read" - do not use]
My quest is for Android 6 on my tablet. I downloaded one of the file twrp-3.0.0-0-mondrianwifiue because it is about 8 megs and because the later files when I tried to use ODIN I was told they were too big. The 3.0.0-0 img was loaded successfully. NOw when my tablet boots it freezes on the Samsung Galaxy Tab Pro SM-T320 screen. At the very top in RED it says KERNEL IS NOT SEANDROID ENFORCING. Second line reads Set Warranty Bit Kernel.
So, what now? Maybe if I can just figure out how to RESET it to factory I will be back where I started. Any help will be appreciated.
bigfootnmd said:
My quest is for Android 6 on my tablet. I downloaded one of the file twrp-3.0.0-0-mondrianwifiue because it is about 8 megs and because the later files when I tried to use ODIN I was told they were too big. The 3.0.0-0 img was loaded successfully. NOw when my tablet boots it freezes on the Samsung Galaxy Tab Pro SM-T320 screen. At the very top in RED it says KERNEL IS NOT SEANDROID ENFORCING. Second line reads Set Warranty Bit Kernel.
Click to expand...
Click to collapse
Try booting into recovery, and see if it boots into TWRP: hold power button until the phone reboots. Once the screen goes dark, and before the Samsung logo screen comes up, hold the vol up (you may have followed a similar process to boot into Download mode and use Odin - except vol down).
bigfootnmd said:
Maybe if I can just figure out how to RESET it to factory I will be back where I started. Any help will be appreciated.
Click to expand...
Click to collapse
"Factory reset" is a bit of a misnomer, all it does is wipe the user data partition. I don't think it will help in this case. Flashing TWRP by Odin should not have put you in a "no boot into OS" condition, and I don't know why that would have happened. But if you can get into TWRP, you can flash a ROM (put the ROM zip on the phone by adb push or copy to removable SD card) and get the phone back up and running.
Need help
Hello,
My friend rooted my samsung galaxy tab pro 10.1 SM-T520 using kingo root.
Would i be able to update to lollipop?
If yes then how?
If no then why?
Please reply as soon as possible.
Please also guide me on [email protected] by mailing me.
Thanks.
Related
Hi everyone.
I recently got a used Note 2. I've been doing a bit of reading in this section and just wanted to confirm a couple of things.
First off my phone's description:
Carrier: Sprint
Model Number: SPH-L900
Android Version: 4.3
Baseband Version: L900VPUBMK4
Kernel Version: 3.0.31-2106854 [email protected] #1 Mon Nov 11 20:33:03 KST 2013
Build Number: JSS15J.L900VPUBMK4
SE for Android Status: Enforcing SEPF_SPH-L900_4.3_0010
Hardware Version: L900.09
(1) Even though the phone came wiped of all previous data I would like to do a factory reset. Billard412's guide is mentioned several times. Is this the option to go with for my phone?
(2) The phone is not rooted at the moment. Should I use the CF-Auto Root method by Chainfire first and then proceed to install TWRP and then restore back to stock using Billard412's guide?
Thanks for your help in advance.
To start with you have the 100% KNOX on your phone so Billard412's back to stock will be the option you want to use.
You will need to download
TWRP recovery (recommended because billards zip works best with it)
Billards back to stock mc2 with counter reset
The root file located in billards thread
Prep steps
Backup everything you want from your internal sdcard (this will get wiped)
place billards rom and root files on your external sdcard
1. boot phone into download mode
2. use odin to flash twrp recovery (any version but 2.7) make sure you uncheck the reboot option in odin
3. once finished remove cable and battery
4. hold the recovery boot key sequence (vol up, home, and power keys) then insert battery (while holding keys)
5. once in recovery wipe everything
6. flash billards rom (do not wipe anything else after this step)
7. flash the root file
8. reboot and dont get worry when things get funky this is normal
9. the phone will take a bit to boot
10. now you have stock mc2 with root
11. install your recovery of choice (if flashing touchwiz 4.3 or aosp 4.4 roms use Philz 6.07.9) this can be done with odin or an image flashing app
12. now you can flash whatever rom you want
FYI -- when going from touchwiz 4.1x to 4.3 or aosp 4.4 you should format your internal sdcard. The newer roms use a different location for your internal sdcard and without proper formatting you will end up with issues (mostly random reboots and apps force closing) -- Same goes if you go from 4.3 TW/aosp 4.4 to 4.1x TW/4.3 or lower aosp
jlmancuso, thanks for the reply. Couple of things to clarify from your post:
- Regarding the Prep steps.
- I don't have anything on this phone yet so I don't think I need to back anything up. Even if if did the "Android system recovery <3e>" recovery menu does not have an option to back anything up
- Regarding using Odin to flash TWRP
- The 2.7 version to avoid is for TWRP correct? I went to TWRP's Sprint Note 2 page and I cannot seem to find a different version. Where should I get the version of TWRP that actually works?
- From the XDA page on Odin, which version should I use 3.09 or 1.85?
- All of the boxes must be unchecked including the reboot option? If not which ones need to be checked?
- I click on the "PDA" button to load the TWRP zip file correct?
- Regarding step 8:
- What do you mean "dont get worry when things get funky"? Funky as in the phone takes long to reboot or the screen flashes weird colors/patterns?
- Also, I came across Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread. That one seems pretty easy to follow through. Would that option work for me given that I have the KNOX update?
Thanks again for your help.
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
roofus1218 said:
Well, I've done a bit more reading into the Galaxy Note2 TOOLKIT V5.0.0 SPRINT thread and it seems that might be the way to go. Mark mentions the KNOX update in his changelog. I don't have the necessary posts to post a question in that thread so hopefully someone sees this that's familiar with that method. Does this method apply to a phone that has already undergone the KNOX update?
From what I can understand, Mark has made a recovery as well as a root tool. I bought this phone second hand so any warranty issues (e.g. flash counts, etc.) don't really apply to me. I'm just looking to get the phone to a clean state where I can start fresh and then add TWRP and Root. As far as the version of TWRP, Billard412 says (in post #604) that "Version of twrp doesn't matter as far as I know."
My second question is, using the Unified Toolkit, will i be able to restore my phone to stock and then root it with the least amount of problems?
Click to expand...
Click to collapse
I belive your best option is billard412s thread. You are correct with your Odin steps. Flash TWRP and follow thread you should be golden
Awesome thanks a bunch!
Hi guys, much thanks for your help.
I had the unofficial CM11 nightly installed on my GTab 3 8.0 but it got corrupted. I used PhilZ Touch to wipe the storage but I can't find a guide to help me re-install CM on this device.
I tried to use Odin to install CM11, but it won't take .zip files. I converted the file to .tar so I could try and flash it, but Odin immediately crashed.
Please help me fix this device.
To add - There is no ROM installed on this device. It has only the philz touch recovery installed.
I can't turn the tablet off - The device just constantly displays the battery icon. When I try to turn it on, it boots and endlessly displays the galaxy tab 3 boot splash screen.
Hoodahottie said:
To add - There is no ROM installed on this device. It has only the philz touch recovery installed.
I can't turn the tablet off - The device just constantly displays the battery icon. When I try to turn it on, it boots and endlessly displays the galaxy tab 3 boot splash screen.
Click to expand...
Click to collapse
I'm not familiar with philz, I'm using TWRP, but I used TWRP to install CM11. I'm assuming philz is similar.
lloydsw said:
I'm not familiar with philz, I'm using TWRP, but I used TWRP to install CM11. I'm assuming philz is similar.
Click to expand...
Click to collapse
Yes lloydsw, PhilZ is ClockWorkMod based. PhilZ has similar functionality to TWRP.
My problem is that I don't know how to get the ROM zip file onto the tablet. If I can get it on the tablet, I'll have no trouble installing with PhilZ.
I tried to adb a little bit, but I keep getting Access is denied errors. For some reason, I have been getting these errors recently whenever the Console is involved, even if I launch it with admin rights. I think Microsoft changed Console functionality with a recent update. So, I didn't try too hard.
So, how do I get this rom file into the tablet?
Hoodahottie said:
Yes lloydsw, PhilZ is ClockWorkMod based. PhilZ has similar functionality to TWRP.
My problem is that I don't know how to get the ROM zip file onto the tablet. If I can get it on the tablet, I'll have no trouble installing with PhilZ.
I tried to adb a little bit, but I keep getting Access is denied errors. For some reason, I have been getting these errors recently whenever the Console is involved, even if I launch it with admin rights. I think Microsoft changed Console functionality with a recent update. So, I didn't try too hard.
So, how do I get this rom file into the tablet?
Click to expand...
Click to collapse
Put the zip on an external sdcard and use that.
Sent from my SM-N900V using Tapatalk
gr8nole said:
Put the zip on an external sdcard and use that.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Hi gr8nole,
I don't think I have an microSD. I have an old SD card but I don't think the Tab 3 will take that.
Is there some kind of GUI tool, like the nexus root toolkit that let me flash .zip files on this thing? I don't why odin doesn't take the most common kind of compressed file. I'm kind of stuck here.
Hoodahottie said:
Hi gr8nole,
I don't think I have an microSD. I have an old SD card but I don't think the Tab 3 will take that.
Click to expand...
Click to collapse
You have a couple options.
Download the full firmware from sammobile.com and flash it with odin. Then re-flash custom recovery.
Or, continue trying to get the rom zip onto your device. Either get a micro sdcard or get adb to work.
If you get adb working, remember you have to mount the data partition before you can send anything to the internal sdcard (internal sdcard is simply a link to /data/media).
Sent from my SM-N900V using Tapatalk
Hey everybody.
I searched my house for microSD cards, and I found one in an old dumb phone. And I recovered some pictures and info that I thought was lost. I found sd card adapters in another box. I put them together and installed the rom easily.
My tablet is working fine, thanks to everyone. Not only is my device working again, I found my lost data. yes!
gr8nole, special thanks to you. Have a great day!
I was previously on cm12.0 but wanted to get back to stock for 6.0.1. Got back to stock but now I can't stand the bloat. Has anyone rooted the stock 6.0.1 yet?
jawz101 said:
I was previously on cm12.0 but wanted to get back to stock for 6.0.1. Got back to stock but now I can't stand the bloat. Has anyone rooted the stock 6.0.1 yet?
Click to expand...
Click to collapse
Just flash TWRP with Odin then flash the supersu zip through TWRP.
Thanks. I got through it all. It's been a while since I've rooted this tablet. My Linux laptop and Virtualbox eventually played nice. Also, apparently any old cord doesn't work. I had to use the original Samsung USB cable for Download Mode to work.
Root SM-T800 6.0.1 with TWRP
paulshriner said:
Just flash TWRP with Odin then flash the supersu zip through TWRP.
Click to expand...
Click to collapse
Thanks for the heads-up..
As I've never used TWRP before (always rooted with Chainefire''s CF-Auto-Root still not available for SM-T800 6.0.1), could you please post a quick step-by-step on how to root the new Marshmallow 6.0.1 on a SM-T800.
Much appreciated..
terrord8158 said:
Thanks for the heads-up..
As I've never used TWRP before (always rooted with Chainefire''s CF-Auto-Root still not available for SM-T800 6.0.1), could you please post a quick step-by-step on how to root the new Marshmallow 6.0.1 on a SM-T800.
Much appreciated..
Click to expand...
Click to collapse
This link is not for our tablets but is the same process. Just make sure you find the correct TWRP version for the T800. Once you have TWRP installed find Supersu and copy it to your tablet's SD card. Use TWRP to install Supersu. http://www.cyanogenmods.org/forums/topic/install-twrp-recovery-samsung-android-using-odin/
Sent from my SM-T800 using XDA-Developers mobile app
I'm also on MM 6.0.1 having just bought this device. I'd like to install this rom:
https://forum.xda-developers.com/galaxy-tab-s/development/rom-android-6-marshmallow-tab-s-10-5-lte-t3219759
So how do I go about it please? Do I need to unlock the bootloader?
:edit: Followed the guide and got TWRP installed. Downloaded the Gapps (very slow download), SuperSu zip and Nougat rom from here. Did a wipe of dalvik, cache, data and system. Sorted. Only problem is I bought the tablet for reading comics and for some reason my comic reading apps can't "see" the cbr files on the micro SD.
So I have tried re downloading Odin and Twrp and flashing it. It passes Everytime. But when I boot to recovery with power home and vol up. It goes to Android recovery. Any tips solutions you could help me with? Thanks very much in advance
After flashing twrp in odin did you reboot to recovery ? Pretty sure u need to reboot to recovery to get it to "stick",
Otherwise I believe your tab will change it back to origanal recovery
DOWNLOAD:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
I had the same problem and I solved it by chance by finding a post online. It seems that after you flash TWRP with Odin it is indeed properly installed but you can't access it because when you boot into recovery it boots into Samsung's recovery. To get to TWRP you need to do the following:
1. Power off your Galaxy Tab S 10.5. Wait 6-7 seconds after screen goes off.
2. Press and hold the three buttons Power + Home + Volume down together until you see warning screen.
3. Press Volume Up to continue to download mode.
4. Reboot again pressing POWER + HOME +VOL DOWN but as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons and wait.
5. Voila TWRP!
I hope it worked for you as it did for me.
Yes
paulshriner said:
Just flash TWRP with Odin then flash the supersu zip through TWRP.
Click to expand...
Click to collapse
I did root the. samsung galaxy sm-t800. watch my vldeo.
https://youtu.be/Ih2IifEUq84
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.
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
doctadocta said:
Hello Friends!
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first.
Then it got all messed up -- you can read about the issues I was having at the end of this post.
Fortunately, the phone works again with the stock ROM after reflashing the BL/AP/CP/CSC files using Odin!
Now I am trying to figure out the best method for rooting with Magisk and installing TWRP or CWM. (if that is needed)
Any suggestions? Any recommendations for posts I can read, videos, or other tutorials?
I don't want to screw this up again!
I *really* appreciate any tips, directions or help of any kind!
And I apologize for being pretty inept at this stuff
BACKGROUND ====================================================
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
I deleted some modules in Magisk that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I decided to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it would reboot within 30 seconds of android starting - I could not get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-...0-with-magisk/)
Now I cannot access recovery.
The phone is just stuck on the Samsung Galaxy A50 screen.
I am able to get into download mode using volume +/- & USB-C. But reflashing the patched ROM or trying to install TWRP using the methods that I know are not working.
I am really not sure what to do now.
===> I am currently reflashing the BL/AP/CP/CSC files using Odin.
The place that I am at is at the top of this post.
Thanks for your help!!
Click to expand...
Click to collapse
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Spaceminer said:
Uncheck auto reboot in Odin. Flash twrp, then hold your hard key combo to boot straight into recovery. You have to go from fastboot (odin mode) straight to recovery after you first flash it, or the stock recovery will replace twrp with itself. Once you get it to stick you won't have to worry about how you boot up.
Click to expand...
Click to collapse
Thanks for the response, Spaceminer!
When I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folders/1brK12SaoQ4gRbhuqLm7k0ZaW_iiaqfde
I get stuck on the Samsung Galaxy A50 screen.
I am basically trying to follow the directions here:
https://forum.xda-developers.com/galaxy-a50/development/recovery-twrp-galaxy-a50-t3916199
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
doctadocta said:
after trying to flash TWRP, I am now stuck on the Samsung screen.
I am now going back to the download screen (volume up, vol down + usc-c) and reloading the stock ROM stuff.
I can't seem to get TWRP to work - I think I may be using the wrong file.
Any suggestions on what TWRP file I should flash for a Samsung A50?
Like I mentioned above, I get stuck on the Samsung Galaxy A50 screen when I try to flash TWRP_A50_Magisk_Prepatched.tar
from here: https://drive.google.com/drive/folde...7k0ZaW_iiaqfde
any help is deeply appreciated!
Click to expand...
Click to collapse
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Spaceminer said:
Do you have a copy of your stock boot.img and stock recovery? I'll take a look at that tar file in the mean time. You might need an updated package.
Click to expand...
Click to collapse
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
doctadocta said:
Hello Spaceminer! Thanks for the support.
I ended up going back to the stock ROM using Odin ===> installing magisk patched ROM
so now I have everything up and running with root access.
Do you recommend that I do anything from here?
Should I install TWRP or CWM on the Samsung A50 even though I have root access using the patched magisk ROM method using Odin?
Thank you for the support!!
be well.
Click to expand...
Click to collapse
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
As I just spent like 8~hours getting my device out of bootloop.. (after trying to root + twrp...) I might as well take the time to post how I got it working.
DISCLAIMER: Only do this if you are desperate - I have no idea why this worked for me to be honest..
Here is how I managed to get my phone(A505FN btw) to boot again it:
download currently used firmware
extract boot.img + place it on external sd
Flash TWRP.tar (see roms&kernels forum section)
hold up + power while flashing until you are in TWRP
now flash boot.img for bootloader
reboot to system
IT BOOTS (I never got it passed samsung logo + text complaining about non offical firmware)
//edit
RIP it installed on SD card, anyone got any tips on how I move it onto internal?
It doesn't show internal storage anymore..
Shout outs to all the non english youtube videos about flashing android phones lmao
Im having kind of same issue but i only tried to install twrp via odin but then it got stuck on samsung logo boot loop. Later i tried creating recovery tar file and tried flashing it in odin but it wont go to the recovery mode although it came as Pass in odin and now im stuck on downloding screen fml any help is appreciated. can some please suggest my next course of action? is my phone gone>?
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Spaceminer said:
Me personally, I would just for sake of making a backup. If you don't plan on modifying system files, then skipping it isn't going to hurt anything.
Click to expand...
Click to collapse
The twrp gives problems but since I rooted with just the patched bootloader in magisk and flash it with Odin. It works stable and I don't have issue's.
ebayusuff said:
As far as I understand no one could manage to root sm-a505f.
Still no solution?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
i tried but stucked at modem_debug.log. can't proceed further. go back to SC to restore the default rom.
Thinking on having magisk but not TWRP. as TWRP may cause many malfunctioning.