Database Develop

[Q] Can I unroot without wiping / back to stock?

Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.

GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.

You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6

the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.

GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)

GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.

Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.

I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.

GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now

Is there a root method that doesn't require unlocking the bootloader? (LRX22C)

I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks

arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.

arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.

Can be done but not recommended.

adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6

What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.

Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.

arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market

danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.

danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up

danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).

For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?

arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery

danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.

arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.

Good to know. Thanks for the info!

[Q] First Time Rooter, Gs6 SM-G920T, need help intresting problem cant find fix.

#1-"com.tmobile.pr.adapt (10001) has been granted superuser permissions for an interactive shell" pops up on my screen every 30 seconds on the bottom of my screen in a grey box.
#2- i also noticed that i can accept and recieve calls but i can not hear, nor can the other person hear me. if i use hangouts video call, skype, etc it works fine.
#3-i also tried to get rom manager to make a recovery and it says it needs to get CWD recovery to install a new software, the first thing we need to do is install a up to date version, we will begin that process now... etc.. then it says to get started you must first sset up a custom recovery, it gives two options a samsung galaxy s3 on metro pcs or a samsung previal 2 on boost mobile, or device not listed, when i click that it says "SM-G920T does not have an officially supported CWDR yet. Have you installed a CWD based recovery manually?" so im not sure what to do from there, or if i even need that. i have been a iphone user since day one went to android after reading up a lot on it, although rooting is quite different than jailbreaking it seems, i am incredibly excited to get started if i can get past these little problems and get started and figure everything out. ANY advice, or anwsers to these problems would be Greatly appreciated! thanks!
Also i went to dev options in settings and noticed the "OEM unlocking- allow the bootloader to be unlocker" was turned off, i dont know if this is necessary to root if i did something wrong by not turning it on or what, or if it may fix any problems above if i turn it on now. thanks!
I have a samsung Galaxy S6 (SM_G920T) . i Rooted and did not trip Knox, Although i did just remember that my fingerprint sensor is not working either.
Thank you guys so much this si a incredible forum i have spent hours and hours reading and researching before making this post i appreciate it so much!

#1 Freeze that ****. Use some root tool to freeze that T-mobile apk, seems u gave it root permissions at some point. I believe there are a lot of apps that you will want to do the same.
#2 ? No idea. Stock rom/kernel?
#3 What is this I don't even. Don't do that. Go to TWRP's official web, get your zeroflte (SM-GT920T) twrp and flash it via ODIN, or else get the recovery.img and use flashify. All that assuming you want a custom recovery.
You will need to unlock the bootloader if you are on 5.1.1. I believe locked will prevent changes or wiping anything on the OS partitions, even recovery (can someone confirm?)
I believe jailbraking and rooting should be pretty much similar, if not the same, as both target to grant the user root access to do whatever he pleases on the OS.
Welcome to android btw.

How did you root? Sounds like you used the modified sboot which causes no sounds in calls and nonfunctional fingerprint scanner. If so, flash back to stock and use a different rooting method. The rest, pretty much what the above poster stated

Root
I rooted using the version that I found the only one that works it seemed like, went to Odin put my phone In download mode and then put the boot loader download in BL and the. Put a something unikernel.sbin I believe, whatever the guide said also then it was done. I thought you couldn't use the twrp or custom recovery etc on tmobile one yet but I just read a thing about xtrestolite odex pure v2 which says it's for 5.1.1 and my model of phone but in the guide it says to root using CF auto root and a link there to it but the link doesn't have my phone on the list that the guide that clearly is my phone says to use I don't know if I'm missing something but I want to use it I understand most of it but I don't know if I need to unropt first and re root then use Odin and flash twrp that's supported on my phone then use that to recover the rom. Etc. The kernel that says is used in the guide is the same one I downloaded so do I need to remove it all then let it do that or?
Sorry if this didn't make sense I'm halfway there between confused and understood I have spent the last 10 hours reading and trying to figure this out though lol. Thanks guys!

Also
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?

Just flash the 5.1.1 firmware to return to stock. To root, flash unikernel with Odin. The other method you used was to not trip knox, but as you experienced has side effects. I had to Odin back to 5.1.1 myself. Can't have those issues

thanks!
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?

CjetOKC said:
so how do i flash back to 5.1.1? find the ling to completely stock 5.1.1 and flash through odin in the same spot and same way i flashed the kernel to root? also.. i rooted with " s6_UniKernel_v2-0003-ODIN.tar" is that not the one you were talking about?
Click to expand...
Click to collapse
Yes, flashing to 5.1.1 works exactly like that. You need to get the version for your model (very important on this one) and then simply place that file in the AP field of ODIN while the device is in recovery mode. It is normal for ODIN to freeze for 2 minutes while verifying. Make sure to use a MD5 checker tool on the firmware before flashing.

Rooting has historically required more technical savvy and balls than jailbreaking, but PingPong made rooting the S6 brain-dead simple. CF-Auto root is still pretty painless, but you must make sure you have the right zip for your device.
Anyhoo, the quickest & easiest way to restore phone calls & fingerprint scan is to use Odin to get back to bone stock.
Next, use PingPong to root. After rooting, "com.tmobile.pr.adapt" will ask for root access. That is T-Mobile's "phone home" app and sends info about your device (probably including root status). Deny it root access and make sure you check "Remember my choice", and it won't bother you again. You will not lose any functionality by denying it root, so terminate that crap.
Don't bother with rom manager. CWM is archaic. If you want a custom recovery, use TWRP. You can install TWRP either using Odin or TWRP Manager app (it's free).
Good luck and have fun with your S6

CjetOKC said:
Sorry for adding more but also how do I flash back to stock? Search for the download to the stock image of my phone? Also I could only find one way of rooting everything else said it wasn't working yet or am I missing a big portion of something here?
Click to expand...
Click to collapse
Are you still rooted? If so, and if you are experiencing the call audio issue, go flash AOU's kernel. He has made a kernel for the tmo s6. that should eliminate your call audio issue. The finger print scanner is the only issue with flashing his kernel. Also, I rooted with the modded sboot, his TWRP and kernel, and I didn't trip knox
http://forum.xda-developers.com/tmo...recovery-twrp2-8-6-0-g925t-5-1-1-of6-t3143002

Persistent root without installing TWRP

I used this method after I unlocked with sunshine to remove king-root and replace it with SuperSU. It worked great for me. Kingroot is gone and i have a permanent root and SuperSU installed. I was wondering if there is someone else who has unlocked their boot-loader and not yet installed TWRP who can give it a shot to see if my expereince was a fluke or the norm. It would be a nice addition for people who want root but don't want TWRP installed for one reason or another.
I used the second link in his post.
Replace_Kinguser_with_SuperSU-v2.4.zip
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Thank you

HT123 said:
I used this method after I unlocked with sunshine to remove king-root and replace it with SuperSU. It worked great for me. Kingroot is gone and i have a permanent root and SuperSU installed. I was wondering if there is someone else who has unlocked their boot-loader and not yet installed TWRP who can give it a shot to see if my expereince was a fluke or the norm. It would be a nice addition for people who want root but don't want TWRP installed for one reason or another.
I used the second link in his post.
Replace_Kinguser_with_SuperSU-v2.4.zip
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html
Thank you
Click to expand...
Click to collapse
I previously used the above method you posted to permanent root an LG Transpyre on 5.1.1 that did not have the bootloader unlocked. Glad to see someone else knows about it. :good:
Maybe it will work on a locked bootloader Turbo for those who don't want to unlock their phones but just want root.

classic757 said:
I previously used the above method you posted to permanent root an LG Transpyre on 5.1.1 that did not have the bootloader unlocked. Glad to see someone else knows about it. :good:
Maybe it will work on a locked bootloader Turbo for those who don't want to unlock their phones but just want root.
Click to expand...
Click to collapse
Can not unlock booloader root? I do not have a visa. $ 25 is a huge amount to me

Thành67890 said:
Can not unlock booloader root? I do not have a visa. $ 25 is a huge amount to me
Click to expand...
Click to collapse
I don't think that is the case.
What I said was you don't need to install a custom recovery.
Give it a shot report back though. Worst that can happen is it does not work.

HT123 said:
I don't think that is the case.
What I said was you don't need to install a custom recovery.
Give it a shot report back though. Worst that can happen is it does not work.
Click to expand...
Click to collapse
Agreed. I was just pointing out that I was able to use kingroot and wolfdroid's method to permanent root a phone (albeit an lg phone) that had a locked bootloader. Other people also had success doing that as well on other brands of phones. Will it work on a Turbo with a locked bootloader? IDK. However I would not be surprised if it does. I had a Turbo with a locked bootloader but sold mine else I would try it myself.

classic757 said:
Agreed. I was just pointing out that I was able to use kingroot and wolfdroid's method to permanent root a phone (albeit an lg phone) that had a locked bootloader. Other people also had success doing that as well on other brands of phones. Will it work on a Turbo with a locked bootloader? IDK. However I would not be surprised if it does. I had a Turbo with a locked bootloader but sold mine else I would try it myself.
Click to expand...
Click to collapse
I agree, i apologize if it it came off otherwise. I think the question is if the sunshine process removes the protection and allow writing to the system partition. I unlocked prior to making my root permanent so i cant test again but am very interested to see if it works with a locked boot loader

HT123 said:
I agree, i apologize if it it came off otherwise. I think the question is if the sunshine process removes the protection and allow writing to the system partition. I unlocked prior to making my root permanent so i cant test again but am very interested to see if it works with a locked boot loader
Click to expand...
Click to collapse
My thinking it that it probably will work because temp root can be obtained on a locked bootloader Turbo with kingroot. It's just that kingroot is unstable and often times does not survive reboot. However, wolfdroid's method is similar to using SuperSu Me(or SuperSume). It removes kingroot and replaces it with SuperSu, which of course is more stable and survives reboot.

classic757 said:
My thinking it that it probably will work because temp root can be obtained on a locked bootloader Turbo with kingroot. It's just that kingroot is unstable and often times does not survive reboot. However, wolfdroid's method is similar to using SuperSu Me(or SuperSume). It removes kingroot and replaces it with SuperSu, which of course is more stable and survives reboot.
Click to expand...
Click to collapse
If security is disabled and the system can write to the system partition it will work, if not, then I assume Sunshine disables it in the process of unlocking the boot-loader. Hopefully someone with a stock Turbo who was going to unlock anyway can verify.

Not sure why you wouldn't want a custom recovery. With custom recovery you can make backups of your entire phone image in case you screw something up. Many times in the past I've flashed something that didn't work as I expected. And with ROOT, if you flash something you can screw up something system-related. Very easy to boot back into TWRP recovery and restore the previous day's backup I had made. Like a time machine to erase your mistake.
And it's FREE. Doesn't cost anything.
Yes, with Titanium Backup (a powerful app) you can restore previous versions of an another app. (I choose to save 3 days worth of apps in Titanium Backup.) But with a TWRP custom recovery backup (also called a "nandroid"), you can save and restore the ENTIRE phone, including all system apps, all settings, everything. Very powerful, useful tool.
I wouldn't have a rooted phone without custom recovery. That's one of the main reasons I always buy phones where I can unlock the bootloader -- to install custom recovery (like TWRP or CW) and root.
If you screw something up and come asking for help, the first thing someone is going to ask is, "Did you make a backup?" And they are talking about a custom recovery backup.

ChazzMatt said:
Not sure why you wouldn't want a custom recovery. With custom recovery you can make backups of your entire phone image in case you screw something up. Many times in the past I've flashed something that didn't work as I expected. And with ROOT, if you flash something you can screw up something system-related. Very easy to boot back into TWRP recovery and restore the previous day's backup I had made. Like a time machine to erase your mistake.
And it's FREE. Doesn't cost anything.
Yes, with Titanium Backup (a powerful app) you can restore previous versions of an another app. (I choose to save 3 days worth of apps in Titanium Backup.) But with a TWRP custom recovery backup (also called a "nandroid"), you can save and restore the ENTIRE phone, including all system apps, all settings, everything. Very powerful, useful tool.
I wouldn't have a rooted phone without custom recovery. That's one of the main reasons I always buy phones where I can unlock the bootloader -- to install custom recovery (like TWRP or CW) and root.
If you screw something up and come asking for help, the first thing someone is going to ask is, "Did you make a backup?" And they are talking about a custom recovery backup.
Click to expand...
Click to collapse
As far as why... some people like chocolate... some people like vanilla. The question is not the merits of a custom recovery, it is if one is required to have persistent root on the phone.
I personally don't care about a custom recovery. I prefer the stock rom at this point because without fail most custom roms have some minor bug that inevitably annoys the sh*t out of me. I want root because i want an ad blocker. I want an ad blocker because I use my phone as a proxy for web traffic on a computer with network monitoring software and i would prefer my internet traffic not be visible to my employer. There is zero reason for a custom recovery to do what i want to do.

Android Pay

Has anyone been able to get android pay working after flashing 8.0 firmware and rooting? If so could you talk through how you did it?

bot_rosco said:
Has anyone been able to get android pay working after flashing 8.0 firmware and rooting? If so could you talk through how you did it?
Click to expand...
Click to collapse
I have working Android Pay with Android One stock rooted firmware. I'm running the XT1900-1 Retail Edition. What have you done so far?
Sent from my moto x4 using Tapatalk

@jiggyman - Are you on Nougat or Oreo?

Neffy27 said:
@jiggyman - Are you on Nougat or Oreo?
Click to expand...
Click to collapse
I'm running the Android One Oreo firmware.
Sent from my moto x4 using Tapatalk

Just today a new magisk update was released which has allowed me to use Google pay . Anyone else who has been having issues and is using root (magisk) ensure you are using version 16

I OTA'd to 8.0 (I have the X4 Retail/Non-Fi version) and Android Pay is broken. It was working just fine on Nougat. Any pointers? TIA.

smmankad said:
I OTA'd to 8.0 (I have the X4 Retail/Non-Fi version) and Android Pay is broken. It was working just fine on Nougat. Any pointers? TIA.
Click to expand...
Click to collapse
Are you using Magisk for your root? If not, that's what you need. So remove your other root method like SUPERSU or whatever, then use the systemless root like magisk.
It is working for me.

edufur said:
Are you using Magisk for your root? If not, that's what you need. So remove your other root method like SUPERSU or whatever, then use the systemless root like magisk.
It is working for me.
Click to expand...
Click to collapse
Thank you - I was considering Magisk, but I'm not rooted at all (I'm on stock, re-locked bootloader - I re-flashed stock after playing around with unlocking the bootloader, TWRP, etc.). Is it because of the re-flash? I am able to OTA successfully, but Root Checker says "CTS Profile Match: Failed" for Safety Net. I suspect that's the issue, but have no clue about solving it. Googling isn't much help either (all answers point to Magisk - I'm okay with that, if that's a guaranteed solution, as I'm dreading having to lose data when I unlock the bootloader to install TWRP and Magisk). I'm pretty certain I'm missing something as it looks as though I am one of the few whose Pay isn't working. I even tried the Fi ROM, with same problem (OTA works, but Pay doesn't. Same CTS Profile Match error). This issue is driving me insane (Everything else works great and I love this device!)

smmankad said:
Thank you - I was considering Magisk, but I'm not rooted at all (I'm on stock, re-locked bootloader - I re-flashed stock after playing around with unlocking the bootloader, TWRP, etc.). Is it because of the re-flash? I am able to OTA successfully, but Root Checker says "CTS Profile Match: Failed" for Safety Net. I suspect that's the issue, but have no clue about solving it. Googling isn't much help either (all answers point to Magisk - I'm okay with that, if that's a guaranteed solution, as I'm dreading having to lose data when I unlock the bootloader to install TWRP and Magisk). I'm pretty certain I'm missing something as it looks as though I am one of the few whose Pay isn't working. I even tried the Fi ROM, with same problem (OTA works, but Pay doesn't. Same CTS Profile Match error). This issue is driving me insane (Everything else works great and I love this device!)
Click to expand...
Click to collapse
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.

edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
The funny thing is that the re-flash was done using 7.1.1 stock ROM found here - https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/ (I used the 26.83-34-0-1 and then OTA'd up to 8.0/March 2017 from there). Pay was working on 7.1.1. Right after the last 8.0 OTA, it broke. I used the standard fastboot flash and flashed all files in the right order. What stumps me is that there was no issue in 7.1.1... Only after OTA did it break. Can you point me to the ROM I should use just to make sure I didn't pick a bad one? (I tried so many in my attempt to solve this that I really need a second set of eyes to tell me if I'm going wrong somewhere).
---------- Post added at 03:32 AM ---------- Previous post was at 03:17 AM ----------
edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
PS: Also, is there a way I can start from a clean slate, I mean, phone ? Some way I can do a hard wipe and then flash stock? I'm sure something is mucked up currently, so a clean flash would be best.

edufur said:
Going back to stock and relocking the bootloader should have google pay back up and running with no issues. If you are having issues, I would be concerned that the return to stock did not work. In any case, if you want to return to a rooted rom, you obviously need to unlock the bootloader and then just make sure you choose Magisk as your option for root. But for me personally, I would not go this route until you can get a factory rom with locked bootloader working again. Otherwise, even if you go the magisk route, it might not work due to your current situation.
Click to expand...
Click to collapse
My investigation here: https://forum.xda-developers.com/mo...ware-stock-7-1-1-t3693145/page13#post76610643