Related
Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.
First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7
Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app
The tool kit is windows only, correct?
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.
Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?
Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.
Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.
I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)
I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
You'll need adb/fastboot + the appropriate drivers.
-unlock BL via fastboot,
-flash recovery via fastboot,
-flash SU zip via recovery,
-leave BL unlocked, no reason to relock it.
That's it. Don't remove, or rename any system apps if you want the OTA to apply. You can even flash OTA's via a custom recovery, this will likely be available here prior to you getting a notification.
Good info here: http://forum.xda-developers.com/showthread.php?t=2010312
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You know when you are on other phones, you are actually unlocking the bootloader via a exploit or through the manufacturers developer center.
You need a custom recovery in order to obtain root. It is a must need, without it you cannot be rooted.
Only way to change your recovery is to unlock the bootloader. Having a locked bootloader locks it so your recovery can't be changed. So.... You get the idea
Sent from my Nexus 4 using xda premium
mseebass said:
So there is no way to root the device without unlocking the bootloader and flashing the custom recovery?
I'm basically in the same boat. I'm developing android apps and want to use log reading apps but I don't want to have any custom rom/recovery on the phone.
Click to expand...
Click to collapse
You can do it via adb with an insecure boot image, outlined here below the CWM method: http://forum.xda-developers.com/showthread.php?t=1993331&highlight=insecure
If you do it the CWM, or TWRP way you can flash the stock recovery again. You absolutely have to unlock the bootloader however, no way around that.
CF Root is another option: http://forum.xda-developers.com/showthread.php?t=2025274
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
threeclaws said:
Convenience? With CWM it even patches on first boot so you don't lose root or anything so I like being able to do OTA (well the one update so far) vs. having to connect to my desktop.
Click to expand...
Click to collapse
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
phermey said:
no reason to connect to desktop if you have recovery. you can come here on your phone or 'chrome to phone' it over. find the thread. click the download link. then reboot in recovery and flash.
Click to expand...
Click to collapse
I also could drop it into dropbox but that is all more work than just hitting "install" on my phone, it isn't like updates are released with enough frequency that the amount of work matters but like I said OTA is more convenient for me and CWM made it even more convenient. The OP may have completely different reasons for wanting OTA.
phermey said:
i just want to make sure you know that if by some circumstance you lose ota that you can always just download the zip of the update here and flash in recovery. there really is no reason for ota that i can see on a nexus device. its here as soon as its released pretty much.
Click to expand...
Click to collapse
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
ORStoner said:
Hi,
I'm expecting my Nexus 4 some time this week and I'd like a little help.
I have a htc one x at the moment. A while after I got it, I decided to unlock it and use custom rom etc.
With the nexus 4, I just want to root it without disrupting anything if possible. The one thing I don't want to mess up is getting the Ota updates as I couldn't get that to work again on my one x.
So to summarise, I want to root my Nexus 4 whilst retaining the ability to get Ota updates and full functionality as normal. Can anyone help?
Click to expand...
Click to collapse
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
phermey said:
i think you must have missed that part in bold. no reason to be a smart a$$ either when you are the one who didnt know there is no reason to connect to desktop.
remember... the whole reason for this thread in the first place is because the op lost ota on his last phone by rooting it. all i did was try to let him feel at ease.
Click to expand...
Click to collapse
I wasn't being a smart ass nor was I unaware of other ways to get an OTA update, you said there was no reason for OTA on a nexus device and I responded why someone would want it.
clockcycle said:
Just use the nexus 4 toolkit, follow it's directions/steps - Can't get any easier or less impact than that. Install Drivers, unlock bootloader and root. Done. OTA still work, install busybox from the play store if needed.
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
Don't use toolkits take the time and learn how to do it yourself so if you get into situations where you messed something up you know how to fix it as you know how adb and fast boot will work.
Toolkits are not worth the short cut
Sent from my Nexus 4 using xda premium
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
ORStoner said:
Can I just unlock the bootloader, fastboot boot not flash cwn and install root from there.
Also, how does unlocking bootloader affect warranty?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is the best way to do it. Yes you can fastboot boot cwm so it'll be temp and just install supersu zip. Regarding warranty for bootloader, it originally came locked so should you need to return it, warranty will be voided if you unlock it. However, it would really be just fastboot oem lock if you need to relock it. The state won't show relocked if you do it. It'll be plain locked
Sent from my Nexus 7 using Tapatalk 2
Noob for tablets. Got the nexus 10 for the family for christmas. Want to get it all setup before I turn it over to the wolves.
I love using TBpro on my Droid Bionic. I thought it would be good to have a solid backup program on the tablet, and since I have it on my smartphone I thought I would hang with what I've sorta know already.
Dont really understand what unlocked/locked means for a bootloader, and why the N10 needs that why many smartphone can be rooted without being unlocked.
I would love to hear some views on the purposes of apps like ClockWorkMod and TWRP and what they do and provide. Seems like they do perform backups and more. Why TBpro is likely just a backup app. What functions do these recovery apps have the make them "must have".
thanks for the time answering the tablet noob
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
bg1906 said:
TBPro requires Root access and to acquire root access you have to be able to modify the operating system. You can't do that until the bootloader is unlocked. Once unlocked, you then need to flash Custom Recovery (either CMW or TWRP) in order to to flash/install the the files required to install the root binaries. Other uses of recovery include making NAND/System Backups and installing custom roms. They are essential if you are into modding your device. I have an LG G2x that is rooted and has a custom rom (CM7.2) and a Custom Kernel (Faux123 v54), as well as Beats Audio for Gingerbread. I installed all of those via ClockworkMod. I followed ZedoMax's instructions to root my Nexus 10 and had only the initial bootloop issue after unlocking the bootloader. That was easy to fix but I couldn't get ClockWorkMod to stay installed so I flashed TWRP instead. Works great. Just follow this thread and watch the vids. Hope I helped some.
http://forum.xda-developers.com/showthread.php?t=1997227
Click to expand...
Click to collapse
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
jetguat said:
Thanks!
After unlocking, and using CMW or TWRP. I can then "root" my device. ok. After rooting, I can use TBpro.
At this point, do I need to remain "unlocked" Does it matter? For the N10 will I receive OTA after being unlocked/rooted,
or do I need to be in another state?
Click to expand...
Click to collapse
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
bg1906 said:
Yes to all. Another option for you if you are not comfortable typing in the various commands is to use the Wufresh method. Watch the video by qbking777 here: http://forum.xda-developers.com/showthread.php?t=2015467
Click to expand...
Click to collapse
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
The wugfresh version automates what the zedomax version does by hand. I did mine via the zedomax way.
Sent from my Nexus 10 using xda app-developers app
jetguat said:
Thanks again. I did stumble across that site and was trying to compare that to the mskip Nexus root tool kit. That was had so many options and I didnt (yet) find the cliff note's version on what they all do and why you'd need to.
The GUI for Wufresh is simple. Do you use it? I read a little about the root and the root+custom recovery choices. Not entirely clear which is preferred, at least for me needs. And I've not got a warm fuzzy feeling about what state the N10 should be in, such that OTA updates still happen. Can they happen when unlocked+rooted+custom recovery but still stock ROM (without system mods)
Click to expand...
Click to collapse
I would suggest using the Wugfresh method, definitely the simplest to use. And a great recovery is TWRP, it is very clear and easy to understand what it is that each menu contains.
Also with the OTA updates, it really depends on the size and type of update. If it is a fairly major one, like JB 4.1 to JB 4.2 then you will have to use the option in Wugfresh toolkit to 'unroot', then update. After the update you can simply reuse the toolkit to root again. Sometimes if the OTA is small it will simply install over the rooted device, but I wouldn't count on it. It definitely shouldn't discourage you from rooting though, its relatively simple to fix
hi all i want to root my nexus 4 but i can't risk data loss is there an easy way to root the phone anything not too technical, I'm not good with this, i used easy root toolkit for my sony and samsung, i haven't seen anything similar yet for nexus 4. thanks in advance guys cheers
is it helps I'm on a mac running mavericks the latest version, i forgot the password for my windows pc lol
no_username_available said:
is it helps I'm on a mac running mavericks the latest version, i forgot the password for my windows pc lol
Click to expand...
Click to collapse
If you really dont know anything please use Toolkit. I recommend you to learn commands,usefull for long run.
Can you tell us more about your phone? Bootloader unlocked?
Anyway, here you go
forum.xda-developers.com/nexus-4/general/tutorial-how-to-root-access-unlocking-t2341103
Towel Root
Sent from my Nexus 7 using XDA Free mobile app
If you have a custom recovery like CWM or TWRP, you just need to download the SuperSU zip from their website and flash the zip in recovery
i haven't done anything to the phone yet, its as it would be out of the box just with my apps and settings on. Would towel root work on 4.4.4? and how would i check if my boot loader is locked or unlocked? thanks
Just check my guide on how to root the nexus 4 without wiping data. It explains how to use Towelroot to root the device and how to unlock the bootloader then (if desired). You may find it in the stickies
I'm wondering why you root your phone or choose not to. My reasoning for both is below.
On the root side:
*I'm coming from a rooted 5x. With the introduction of Nougat, I lost any way to a power menu (via Xposed) screenshot. So my preferred method without that option was using a home button remapping app (Homebot https://play.google.com/store/apps/details?id=com.abast.homebot ) that opened up my screencap app ( Screencap https://play.google.com/store/apps/details?id=com.symcoding.app.screenshots ) but there screencap app requires root. It's clunky, but it works. I've tried every other screencapping app I can find and nothing works as easy as power menu>screenshot. I could use power+power down, but my case makes that difficult. It's not worth downgrading the OS to use Xposed for this. But I'm on the fence if it's worth rooting my 6p.
* I like Xposed mods that allow me to modify things like going to text only battery percentage. Still not worth downgrading to Marshmallow though.
On the no rooting side:
*I won't be forever chasing a way to use or being without the ability to use Android pay.
Your thoughts/reasoning?
Sent from my Nexus 6P using Tapatalk
I mean, you don't have to root.
You can unlock the bootloader and flash a custom ROM (such as Pure Nexus). With Pure Nexus, you don't have to flash SuperSU, which gives you root access, or you can flash SuperSU, up to you.
Either way, there is an option in the ROM to add screenshot to the power button menu, and there is no need for Xposed (which doesn't have support for N yet anyways).
Going between root access and no root only takes 30 seconds, and you can switch between the two anytime you want. To add root, simply flash the SuperSU. To unroot, go into SuperSU menu and click the unroot button.
The only benefit I see without root is the ability to use Android Pay. Android Pay will still work on the Pure Nexus ROM, as long as you don't flash SuperSU.
Sent from my Nexus 6P using XDA-Developers mobile app
Because even factory images are bugged to no end. That's why I root...
Sent from my Pixel using Tapatalk
I root so I can use Adaway and High Brightness Mode Widget
Well, if you're not sure, don't root. It is a security risk. Also if you ever want to pay with your phone, then you don't root.
Me, I always had rooted phones, because
- I like to be in total control of all my computers, no matter if stationary or mobile.
- Also when I develop my rom, it helps if I can remove all traces of a system app from the phone itself.
- Also, because I develop my rom, I regularly make TitaniumBackups when trying out a bigger change in the os.
- Makes me all powerful and grownup
I just rooted my 6P yesterday. My main driver was to be able to edit the build.prop file to get the Google Assistant on my 6P, which is supposed to be a Google Pixel exclusive feature. That worked for me, and I'm enjoying the Google Assistant, although I'd say it's still very much in its infancy. However, I did lose the ability to use Android Pay though , but I've been trying to find a workaround for using Android Pay on my rooted 6P. I believe it can be done on a systemless root (like SuperSU 2.76+ IIRC). I've seen some data points on that on another 6P thread. My Android Pay is still being very finicky though.
---------- Post added at 07:00 PM ---------- Previous post was at 06:51 PM ----------
vikramjatt11 said:
I mean, you don't have to root.
You can unlock the bootloader and flash a custom ROM (such as Pure Nexus). With Pure Nexus, you don't have to flash SuperSU, which gives you root access, or you can flash SuperSU, up to you.
Either way, there is an option in the ROM to add screenshot to the power button menu, and there is no need for Xposed (which doesn't have support for N yet anyways).
Going between root access and no root only takes 30 seconds, and you can switch between the two anytime you want. To add root, simply flash the SuperSU. To unroot, go into SuperSU menu and click the unroot button.
The only benefit I see without root is the ability to use Android Pay. Android Pay will still work on the Pure Nexus ROM, as long as you don't flash SuperSU.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Are you sure that the custom TWRP recovery will remain if you unroot using the button within SuperSU? In the Nexus 6P rooting guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928), step 2, dealing with installation of custom recovery TWRP, says that TWRP "won't stick" if you don't immediately flash SuperSU after booting into TWRP recovery the very first time. I can attest to that, because it happened to me. I had to reflash the TWRP img file, reboot into TWRP recovery, and immediately flash the SuperSU on the phone to make TWRP stick. Do you think unrooting thru SuperSU will allow the TWRP to remain, so that you can use Android Pay? Otherwise, you need to do another step of flashing the TWRP before rerooting.
Secondly, do you know if you just need to be unrooted to add cards to Android Pay? Or do you need to be unrooted for even regularly paying with your app? I've not had success adding cards (except for one) to my Android Pay app after rooting. I haven't yet had a chance to test whether I am able to pay while rooted.
One does not need to root.
If it works for you stock, go for it.
I would say though that unlocking the bootloader is a must.
It allows freedom if anything ever gets corrupt.
Do it ASAP because it wipes the device..
istperson said:
Well, if you're not sure, don't root. It is a security risk. Also if you ever want to pay with your phone, then you don't root.
Me, I always had rooted phones, because
- I like to be in total control of all my computers, no matter if stationary or mobile.
- Also when I develop my rom, it helps if I can remove all traces of a system app from the phone itself.
- Also, because I develop my rom, I regularly make TitaniumBackups when trying out a bigger change in the os.
- Makes me all powerful and grownup
Click to expand...
Click to collapse
Magisk takes care of the rooting non rooting Android Pay fiasco.
Sent from my Nexus 6P using Tapatalk
inprince said:
I just rooted my 6P yesterday. My main driver was to be able to edit the build.prop file to get the Google Assistant on my 6P, which is supposed to be a Google Pixel exclusive feature. That worked for me, and I'm enjoying the Google Assistant, although I'd say it's still very much in its infancy. However, I did lose the ability to use Android Pay though , but I've been trying to find a workaround for using Android Pay on my rooted 6P. I believe it can be done on a systemless root (like SuperSU 2.76+ IIRC). I've seen some data points on that on another 6P thread. My Android Pay is still being very finicky though.
---------- Post added at 07:00 PM ---------- Previous post was at 06:51 PM ----------
Are you sure that the custom TWRP recovery will remain if you unroot using the button within SuperSU? In the Nexus 6P rooting guide (http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928), step 2, dealing with installation of custom recovery TWRP, says that TWRP "won't stick" if you don't immediately flash SuperSU after booting into TWRP recovery the very first time. I can attest to that, because it happened to me. I had to reflash the TWRP img file, reboot into TWRP recovery, and immediately flash the SuperSU on the phone to make TWRP stick. Do you think unrooting thru SuperSU will allow the TWRP to remain, so that you can use Android Pay? Otherwise, you need to do another step of flashing the TWRP before rerooting.
Secondly, do you know if you just need to be unrooted to add cards to Android Pay? Or do you need to be unrooted for even regularly paying with your app? I've not had success adding cards (except for one) to my Android Pay app after rooting. I haven't yet had a chance to test whether I am able to pay while rooted.
Click to expand...
Click to collapse
Yes, when you flash the Pure Nexus ROM, it will not have root by default. So if you flash the ROM, google apps, and vendor image and then reboot, the ROM will work as needed, but will not have root. In order to get root, you have to flash the SuperSU file in TWRP.
In Android Pay, you will need to be on the Pure Nexus ROM with no SuperSU flashed in order to add cards or use Android Pay regularly when paying. But you can simply flash the SuperSU file when you need root, and then remove root by going to the SuperSU app.