Background
I'm one of the lucky ones that has the data mount issues with the SELinux versions of TWRP. I've tried every method I can find in the forums here including:
Hashcode's original instructions for Kitkat using either "zip-otter-twrp-2.6.3.0-selinux-recovery.zip" or "openrecovery-twrp-2.6.3.1-otter.img"
Using Kindle Fire Utility to install either version of TWRP
this technique explained here: http://forum.xda-developers.com/showthread.php?t=2537579
And finally using Flashify
I end up with data mount error every time and I couldn't install any of the 3 KitKat versions found here http://forum.xda-developers.com/showthread.php?t=1859851 from within native TWRP (not the app) because I would get errors and the install would fail.
Convoluted Workaround
Here's what I finally did to get kitkat installed and fair warning, it's very convoluted. I installed TWRP 2.6.3.0 with KFU and used that to install CM 10.2 M1 snapshot with the appropriate "gapps-jb-20130813-signed.zip". Then I installed the Goo.im and Flashify apps. I ran both to make sure they had superuser rights. Closed them and rebooted. I then went into Goo.im and tried to upgrade to latest TWRP 2.6.3.1 which downloaded the file but failed to flash it. Close Goo.im and use file manager to find the downloaded file and when I clicked on it Flashify automatically asked if I wanted to install it. I said yes and let it do its thing and then rebooted.
Next I installed KitKat "CyanogenMod version 11-20131210-NIGHTLY-otter" by going into settings, about tablet, update cyanogenmod. Change search criteria so it sees the CM11 nightlies and then use it to download and install CM11
After rebooting, Kitkat installed and I had to run through the normal new ROM setup.
After that google play didn’t work so I uninstalled google play services & google play store with clean master app and reinstalled the gapps-kk-20131119.zip version. I think I used Flashify but I don’t remember to be honest. I also “might” have had to go back to TWRP 2.6.3.0 first to install gapps but again, I’m not sure. I know I sound like a ditz but I spent a day trying all kinds of things and should have taken notes.
Result is that my Kindle Fire 1st gen is running KitKat very well and so far this is the best version I have found and I’ve tried most of the 10.1 & 10.2 versions out there. The down side is the TWRP 2.6.3.1 backup is broken now. I’ve also tried going back to TWRP 2.6.3.0 (with & w/out SELinux) and none of them will complete a backup.
Sorry for the convoluted post. I wanted to recreate/clean up my process but since I can’t run a backup, I’m scared to hose my Kitkat install and not be able to get back. You are probably at extreme risk to try to follow my madness but maybe one of the smart people on here can use this to create a cleaner method for those of us stuck with the data mount issue related to the SELinux versions of TWRP.
Question
Is there any risk to my Kitkat installation by running a TWRP that has data mount issues as long as I don’t use TWRP? I read the KF guide here in the forum and I don’t believe there are any dependencies of the Android ROM (kitkat in my case) on TWRP. I do realize that any version of TWRP is basically useless for me unless I go back to version 2.6.3.0, wipe and start over.
No, no threat to your os
Sent from my air powered ceiling fan
Thank you
Sent from my Amazon Kindle Fire using Tapatalk
Have you tried the flashable zip version of TWRP? it works within twrp so that you can get the right one on your kindle
I think I've tried them all.
Laquox said:
Have you tried the flashable zip version of TWRP? it works within twrp so that you can get the right one on your kindle
Click to expand...
Click to collapse
Yes, both the zip and img versions with flashify, goo.im app, TWRP app and within TWRP native.
Okay i've removed the fire OS off my kindle and am running cyanogenmod 10.1, but would like to update to cyanogenmod 11 kitkat. But everytime I try to flash the rom through TWRP 2.6.0.0 I get a failed error. I understand it's recommended to use the most updated version of TWRP(2.6.3.1) but I HAVE NO IDEA HOW TO UPDATE TO THAT VERSION now that I've erased the original OS and am running strictly android OS! (after I successfully erased the fire OS I deleted all the files i downloaded to save space) So now I can't remember how to get my device into bootloader mode to enable fastboot to install the updated version of TWRP.
BUT MY REAL QUESTION is do I even need an updated version of TWRP to move from CM 10 to CM 11???? My drivers are all correct for my current version and can add and move files fine through the USB connection it just fails every time I try to install CM 11.
I am performing a factory reset wipe before I attempt to flash the new ROM, but is there something else I'm missing or is the only way to flash CM 11 with TWRP 2.6.3.1?
Any help I can get on this is appreciated, I've searched for a hot minute and have found some posts saying updated versions of TWRP are preferred but nothing explaining how to install an updated version of TWRP after fire OS has been deleted. I'm sure it's something small and stupid I've been overlooking but after several hours I just need a fresh pair of eyes for help. Please and thank you to all that respond.
Simple really, download the twrp zip from here, and flash it from in twrp, and I believed after reading the changelog yes you will need it because it has full selinux support and I don't believe your version does, selinux is used on cm11.
Edit: also should mention after flashing the new recovery zip file to reboot the device into recovery again to load the new recovery up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
you're a gentleman and a scholar!
stunts513 said:
Simple really, download the twrp zip from here, and flash it from in twrp, and I believed after reading the changelog yes you will need it because it has full selinux support and I don't believe your version does, selinux is used on cm11.
Edit: also should mention after flashing the new recovery zip file to reboot the device into recovery again to load the new recovery up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Ha I can't believe it was that simple, here I thought I had to re-run ADB and SDK on a previous version to make everything communicate but all I had to do was install the update through the current version. Thank you, I am currently running the set up on CM 11, you deserve a vacation, or at least a cuddle.
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.
So i sideload the Oreo on Nougat. Everything was fine. Then i rooted with magisk and it is no stuck in bootloop. The only way to boot up the device is to go to bootloader screen and hit start. I flashed an image found on this forum and nothing changed. I believe i need a new image ?
Thank you
There is an Oreo .xml.zip, but I don't know for which versions it is:
https://firmware.center/firmware/Motorola/Moto Z Play/Stock/
Gigahyperprime1 said:
So i sideload the Oreo on Nougat. Everything was fine. Then i rooted with magisk and it is no stuck in bootloop. The only way to boot up the device is to go to bootloader screen and hit start. I flashed an image found on this forum and nothing changed. I believe i need a new image ?
Thank you
Click to expand...
Click to collapse
The solution is in this post -- https://forum.xda-developers.com/moto-z-play/how-to/guide-how-to-magisk-root-xposed-oreo-8-t3743273
The user Rafikowi give the solution in that post. - "Good Luck" :good:
UPDATE 20.04.2018
If you flashed everything as described in OP and noticed that you got stuck in boot, go to TWRP again and:
1. Uninstall Magisk using latest Magisk uninstaller.
2. Flash Magisk 16.0 or 16.2 (does not matter) AGAIN (yes.).
3. Flash f2fs-loopback-bug-workaround-2018.1.31.zip
4. Enjoy rooted phone.
PS. I do not know why device does not start after first flashing to be honest, but these four steps above are confirmed by several users (and by me last night).
I've been away for about a year so I'm behind on everything right now. I just flashed a factory image to get back to Android 8.1 and set my phone up from scratch. I would like to install TWRP and Magisk but have some questions..
TWRP. Do I just find the latest TWRP for this phone and the process is the same as before? Fastboot flash twrp img and then install TWRP zip?
Magisk: I have never used it before so I'm not to familiar at all. From what I can tell I just download the zip and install via twrp? Is there a specific version I should be looking for for the Pixel on 8.1 or will the latest from the Magisk forum work?
I've searched around and keep seeing random issues so I'm wondering if it's as straight forward as mentioned above. I see posts about people trying to install TWRP and Magisk and bootlooping and stuff like that. Thanks!!
aholeinthewor1d said:
I've been away for about a year so I'm behind on everything right now. I just flashed a factory image to get back to Android 8.1 and set my phone up from scratch. I would like to install TWRP and Magisk but have some questions..
TWRP. Do I just find the latest TWRP for this phone and the process is the same as before? Fastboot flash twrp img and then install TWRP zip?
Magisk: I have never used it before so I'm not to familiar at all. From what I can tell I just download the zip and install via twrp? Is there a specific version I should be looking for for the Pixel on 8.1 or will the latest from the Magisk forum work?
I've searched around and keep seeing random issues so I'm wondering if it's as straight forward as mentioned above. I see posts about people trying to install TWRP and Magisk and bootlooping and stuff like that. Thanks!!
Click to expand...
Click to collapse
Yes.
Why Android 8.1.0?
Android 9.0 (Pie) is the current version of android.
this guide will help you: [Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + November 2018 Security Patch
If you want to stick with the outdated version of Android, 8.1 (Oreo), scroll down to other section in the guide above and click on the Android 8.1.0 (Oreo) link.
aholeinthewor1d said:
I've been away for about a year so I'm behind on everything right now. I just flashed a factory image to get back to Android 8.1 and set my phone up from scratch. I would like to install TWRP and Magisk but have some questions..
TWRP. Do I just find the latest TWRP for this phone and the process is the same as before? Fastboot flash twrp img and then install TWRP zip?
Magisk: I have never used it before so I'm not to familiar at all. From what I can tell I just download the zip and install via twrp? Is there a specific version I should be looking for for the Pixel on 8.1 or will the latest from the Magisk forum work?
I've searched around and keep seeing random issues so I'm wondering if it's as straight forward as mentioned above. I see posts about people trying to install TWRP and Magisk and bootlooping and stuff like that. Thanks!!
Click to expand...
Click to collapse
Hey, I recently got my Pixel XL (27th, new for only £200!). I am telling you from what I had experienced. I believe I was shipped a Verizon phone, as I cannot unlock the bootloader and make calls as I am with Vodafone in the UK. I followed a guide on XDA and you should to if you have the greyed out "OEM Unlock" Setting in Developer Options: https://www.xda-developers.com/unlock-bootloader-verizon-google-pixel-xl/
So, if you have had any experience flashing and unlocking boot loaders with the Nexus devices, you will feel mostly at home. TWRP is very easy to flash, but with extra steps. However, remember that not all goes well for everyone, so I am not responsible if anything goes wrong, that doesn't mean that I wouldn't help you though. lol Any links that you may need are listed at the bottom.
Installing TWRP:
Firstly, download the twrp-pixel-installer zip file on your Pixel:
-Pixel devices: https://dl.twrp.me/sailfish/
-Pixel XL devices: https://dl.twrp.me/marlin/
You would want the latest zip file on your Pixel. Why Pixel? I have tried to flash the recovery from the PC, but I get a partition error, I believe this is normal and I think I was doing everything incorrectly at my first try. Instead of flashing the recovery the traditional way, we will temporarily boot into the recovery though fastboot.
On your computer, download the IMG file of twrp: "twrp-3.2.x.x-devicename.img". This is the image file we are going to use to boot into TWRP. Make sure you have the correct adb drivers from Google and the platform-tools itself and go into the bootloader screen on the Pixel. Then connect your Pixel and start CMD within the directory of which your platform-tools is in.
Type:
Code:
fastboot devices
to check if your device is recognised by the computer. If not, try reinstalling the Android Drivers, or try a different PC (which helped me sometimes).
After that, type
Code:
fastboot boot "directory-of-twrp-img"
Just drag-and-drop the img file in CMD. It will fill in the directory for you with the speech marks.
Your Pixel will boot into recovery, just swipe to allow modifications or set your language first if you desire. Then go into the install section and flash the twrp-pixel-installer zip file that you have downloaded for the first step of this guide. It will run the installer in both slot partitions (a & b) of the Pixel to make sure that all goes smoothly (i think).
TWRP is now installed on your system.
Installing Magisk:
Magisk is a universal systemless root that is designed to work on Android 5.0 and higher. This works on any phone and you do not need any specific zip file. Just download the Magisk Manager apk from XDA and install. Then go into the app and it should ask you if you want to download the latest Magisk zip file. Just download it and download as a zip file only. Then reboot into TWRP and install the zip file in the Downloads folder.
I hope my long reply has helped you here and if you have any questions, or issues, feel free to ask. Contact me on my Telegram if you wish: t.me/yomarshmellow
Links:
platform-tools: https://developer.android.com/studio/releases/platform-tools
Google USB Driver: https://developer.android.com/studio/run/win-usb
Max Lee's video guide on this: https://www.youtube.com/watch?v=Hg5986wL-3k