Database Develop

FoxFi to work with Cricket Wireless ??

I have a none rooted Moto X and don't want to root it. Just curious if anyone here has got Foxfi to work with their Moto X on Cricket, I have a neighbor that has the same phone and asked me to help him set it up, and I was not able to get it working. So I figured I'd post here to see if anyone else has had success, if yes, please post your settings. :good:

DonB. said:
I have a none rooted Moto X and don't want to root it. Just curious if anyone here has got Foxfi to work with their Moto X on Cricket, I have a neighbor that has the same phone and asked me to help him set it up, and I was not able to get it working. So I figured I'd post here to see if anyone else has had success, if yes, please post your settings. :good:
Click to expand...
Click to collapse
its not carrier dependent. it has to do the version of Android. last i checked, FoxFi isn't compatible with any 4.4.x version.

640k said:
its not carrier dependent. it has to do the version of Android. last i checked, FoxFi isn't compatible with any 4.4.x version.
Click to expand...
Click to collapse
Thanks, Thus the reason why I couldn't get it to works, I'll relay the message. :crying:
Any other app that does work ??

root.

640k said:
root.
Click to expand...
Click to collapse
Yep, I told him that but he also doesn't want to root, but thanks, any other suggestions, please advise if not then he'll be SOL, LOL

Figured I'd check in to see if anything has changed. Has anyone been able to edit their build prop without ROOT to allow Tethering on Cricket wireless ?? Or figured out how to Tether without ROOTING, I've tried all I can find on the net but no luck.
If ROOTING is my only option, what suggestions are a simple ROOT process, to keep stock Rom and be able to Tether.

For that you can simply root with magisk using stock ROM. Also magisk have a module to enable tethering if you phone have locked (can't try because I have unlocked non American version).
Also after this time you don't have any warranty so root is not a problem in that way.
However you can't touch system file like build prop without accessing the system (root) afik.
If you are on stock 5.1 follow this link to root:
https://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
Change SuperSu in the guide with magisk zip (and install magisk manager after that) and TWRP 2.8.6.0 with TWRP 3.0.2/3.0.3/3.1.1
---------- Post added at 03:03 AM ---------- Previous post was at 02:55 AM ----------
If you already see the message I updated with guide link

Question is this, by simply rooting, will it allow for editing the build prop for tethering, or do I also have to unlock the bootloader as well ??

DJB628 said:
Question is this, by simply rooting, will it allow for editing the build prop for tethering, or do I also have to unlock the bootloader as well ??
Click to expand...
Click to collapse
I don't think you can rooting with bootloader locked.
Do it, it's easy and the warranty is already expired.
The only problem is with bank app or some app like Netflix or Pokemon go.

Thanks for the info, cheers, Sorry I've been out of action for awhile.

root, lollipop, xposed questions

first, sorry if this has been asked b4, xda/google saeearch didn't find anything.
I need xposed, and I also need root. ( both, root for other things besides xposed.)
just got my moto g2, 4.4.4., and I wanted to know, should I root now, or wait till the 5.0 update and then root? or should I root now and install xposed and not update to 5.0 when it comes out? I read online that there probably will not be xposed fully working on lollipop.
advice anyone?

Root it now, you can aways install the update on your phone, rooted or not.

Hakkinan said:
Root it now, you can aways install the update on your phone, rooted or not.
Click to expand...
Click to collapse
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?

Kobro said:
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Click to expand...
Click to collapse
You can be rooted and still be fully stock.

Kobro said:
most of the updfate threads say to make sure the phone is fully stock, wont it mess it up?
Click to expand...
Click to collapse
Only if you want to receive it by OTA, besides that, it doesn't matter if you are fully stock or not.

There are some known issues relocking bootloader and returning to stock at all. In most of all cases it works without problems but not in all. If you can´t get back to stock there still will be future options to get lollipop,by sideloading as a zip though recovery for example,ota is not the only way.
I am still on stock 4.4.4 and will wait for the ota,then relock bootloader and root.The Moto G is the first phone I didn´t root at once because it works really good and has farly not as much crapware as others, so I´m able to wait. But I don´t need xposed desperatly, I badly need Adway,Titanium and some others more.
It´s still not clear if xposed will work under lollipop.
So it´s your choice, it´s up to you. You can stay on Kitkat,root and install xposed. And you can update to lollipop later,when/if xposed is running.
Or you can stay stock,wait for ota and root later wich is my way.

Coming from 2 nexus devices, i can't imagine to have a phone without unlocked bootloader, root, custom rom and kernel, that's the point of android for me, customization

Thanks all for your responses! Much appreciated! Now all i have to do is find some way of rooting the thing, vroot failed- first time ever for me

To root Moto G 4.4.4 you have to unlock the bootloader,install custom recovery and flash superSU.zip.
Just follow this guide: http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245
But use the CWM-recovery from here: http://forum.xda-developers.com/moto-g-2014/development/recovery-cwm-philz-touch-6-moto-g-2014-t2896586
or TWRP from here: http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165

xposed not working
Kobro said:
first, sorry if this has been asked b4, xda/google saeearch didn't find anything.
I need xposed, and I also need root. ( both, root for other things besides xposed.)
just got my moto g2, 4.4.4., and I wanted to know, should I root now, or wait till the 5.0 update and then root? or should I root now and install xposed and not update to 5.0 when it comes out? I read online that there probably will not be xposed fully working on lollipop.
advice anyone?
Click to expand...
Click to collapse
plz send a link where i can download xposed for moto g 2014 tx

najm555 said:
plz send a link where i can download xposed for moto g 2014 tx
Click to expand...
Click to collapse
One post above yours.......
http://forum.xda-developers.com/showpost.php?p=58828974&postcount=1

lollipop root on G900A discussion

On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.

wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app

miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
How does this affect our device when it gets the lollipop update?
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/

wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.

Since I am running dynamic Kat on stock slot right now, I should be safe from updates for now right?
Waiting to see what happens with all this. I did back up my stock rom to an SD card, so I can restore and unroot etc... to get an update if I choose to later.

muniz_ri said:
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Click to expand...
Click to collapse
was looking for a post like this. well maybe we might get 5.1 in the next few weeks or sooner so i am sure you will give it a try and a good look and hopefully you will have success in attaining root and a good SS. seems like u da man for this...:good::good:
as for 5.1 or a custom rom...well whose to say what that will bring...
will be waiting to see what happens. will check back here when it comes out. i watch for it everyday and as usual, thank you for all your great work!

miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily, just because (if) the S5 gets 5.0 does not mean the ability to root will be lost just go check out the Verizon S5 forums you'll see they have a method for rooting with 5.0 that in theory should work for us as well. again it is recomended to remain on a 4.4.x rom until this has been fully evaluated.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
My suggestion would be not to take any updates until the root capabilities have been evaluated.
As always, research goes a long way towards alleviating fears and stopping panic attacks before they happen. be patient there are great devs here give them time to work

Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now

the att gs5 doesn't seem like it's getting any updates..

wmunn said:
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
Click to expand...
Click to collapse
How are you liking it? I'm seriously thinking about doing the same thing.

I have a coworker that just got the Lollipop update for his Note 3 so that means it will be coming to the S5 very soon!

There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.

silentscreamz said:
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
Click to expand...
Click to collapse
I used that method as well. Sure, it worked for me, but I came from Dynamic Kat, a well debloated stock rom. Due to this, after installing the update using this method, the built-in apps restore function could not complete due to having all of the useless bloatware back, taking up the extra space I was free to use in Dynamic Kat. Even removing the apps that are safe to remove via Titanium Backup doesn't help because the space is reserved for them. I've also already moved every app that it will allow to move to SD card. I've removed unneeded apps. I've gone through my internal storage to remove any unneeded files.
I've removed most of the apps listed here
This doesn't give me the Bluetooth tether that I used to us for my Gear 1(Running Null Rom). I'd look for an app to cover this but... I can't install anything because I've got no space to do so... I hope a good debloat method comes along soon. I still have root, so I'm hopeful.

Yea, bloatware is ridiculous for this phone. Have you tried the Alliance rom, that is what I run and it's not to bad for bloatware but I have only managed to get 5.6 running. Going to try version 8 today sometime. If you like to customize that is an awesome rom.

Hi folks, new to the S5 forums on here as I just upgraded from my trusty S3 on AT&T. I'm still on the stock 4.4.2 firmware, NG3 build, and I'm wondering if I should just root from here using TowelRoot method or take the 4.4.4 OTA and root from there.

Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.

SoCalHTCFuze said:
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
Click to expand...
Click to collapse
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.

MetalHead66 said:
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
Click to expand...
Click to collapse
You gotta downgrade theres a post on here just type it in the search bar. Pretty easy process

Yes. Follow the 4.4.2 how to root thread, it says that bit still works.

OK thanks a bunch. Getting ready to do that now.
---------- Post added at 03:27 AM ---------- Previous post was at 02:53 AM ----------
Well that was quite easy and I'm a happy camper now! Just had to flash nd3 kernel with odin in order for TR to work then flash my ng3 kernel. So nice to be able to use TiBu. Helium wouldnt install all my apps. Now I can start freezing and uninstalling all the bloatware!

Could I just sideload 5.1.1 without using TWRP?

Could I boot into ADB sideload and use an 5.1.1 image from Amazon? And then root?
Sent from my KFFOWI using Tapatalk

Distinct feeling that will just make it have the same effect as using the OTA upgrade, but I'm not sure.
Is there a problem with using twrp?

AntDeek said:
Could I boot into ADB sideload and use an 5.1.1 image from Amazon? And then root?
Click to expand...
Click to collapse
Indeed, you might as well just turn on OTA, and wait for it
You have to be able to root somehow, and the best way is through TWRP since otherwise 5.1.1 is currently impenetrable.

So if I wanted to do a fresh install I would just have to wait for the 5.1.1 root?
Sent from my KFFOWI using Tapatalk

Why on earth would you want to install 5.1.1?
Have you read what 5.1.1 does? See [PSA] Information Regarding Firmware Version 5.1.1.
Only safe way to install 5.1.1 is detailed here: HOWTO] Install FireOS 5.1.1, ROOT, GAPPS and keep TWRP access and even then you will be worse off on 5.1.1. I believe you can't remove any bloatware or the lockscreen ads.

In what way is installing it through twrp not a fresh install if (after backing up) you wipe it all? (assuming install files and backups made to an external sd)

AntDeek said:
So if I wanted to do a fresh install I would just have to wait for the 5.1.1 root?
Click to expand...
Click to collapse
Couldn't one factory reset in TWRP and then use bibikalka's upgrade/root method? (I'm asking.)

If you want a completely fresh install then you can just reinstall 5.0.1
No reason to go anywhere near 5.1.1
HOWTO How to restore frimware on your device + Amazon Frimware

Would it be possible to do a side load restore to 5.0.1 and then upgrade to 5.1.1 and wait for a root script and the google apps?

So long as you realise that they might never come.
If your tablet is functional atm I can't understand why you want to do something that might never work rather than something that does easily.
If you are on anything other than 5.1.1 atm see if you can swap with someone desperate to get rid of a Fire stuck on it.

So really I should just keep it on 5.0.1 rooted with Google launcher and see if 5.1.1 gets rooted
Sent from my KFFOWI using Tapatalk

Or just...
I don't know...
use twrp...

Some people (myself included at a certain point of time) just HAD to have the latest updated version, even though it sometimes is a downgrade really. Case in point is the current es file explorer.

That's how I am lol I feel the need to have the latest version
Sent from my KFFOWI using Tapatalk

julianpaul said:
Some people (myself included at a certain point of time) just HAD to have the latest updated version, even though it sometimes is a downgrade really. Case in point is the current es file explorer.
Click to expand...
Click to collapse
What's wrong with ES?

AntDeek said:
So really I should just keep it on 5.0.1 rooted with Google launcher and see if 5.1.1 gets rooted
Click to expand...
Click to collapse
5.1.1 can already be rooted (if installed through the proper procedure). See the link I posted.
blueberry.sky said:
Only safe way to install 5.1.1 is detailed here: HOWTO Install FireOS 5.1.1, ROOT, GAPPS and keep TWRP access and even then you will be worse off on 5.1.1. I believe you can't remove any bloatware or the lockscreen ads.
Click to expand...
Click to collapse
You are in root & custom Rom land now. There will be so called "upgrades" to the amazon OS that provide zero upgrade, only serve to disable root, roms, debloating & adblocking.
Pond-life said:
What's wrong with ES?
Click to expand...
Click to collapse
http://www.xda-developers.com/es-file-explorer-a-short-story-of-a-fallen-king/
---------- Post added at 05:00 PM ---------- Previous post was at 04:43 PM ----------
AntDeek said:
Would it be possible to do a side load restore to 5.0.1 and then upgrade to 5.1.1 and wait for a root script and the google apps?
Click to expand...
Click to collapse
Pond-life said:
If you are on anything other than 5.1.1 atm see if you can swap with someone desperate to get rid of a Fire stuck on it.
Click to expand...
Click to collapse
I will buy your 5.0.1 Fire / trade. I am entirely serious.
If you want 5.1.1 and don't mind taking a chance, waiting for a new 5.1.1 root exploit to come out, I have another Fire on it's way to me from Amazon. It may very well come preloaded with 5.1.1. I will seriously trade. I need a custom rom, root doesn't do what I need.

I am not looking to sell my device I'm sorry friend!
So I am better off leaving 5.0.1 rooted in my Fire since it does everything I need it to.

Pond-life said:
What's wrong with ES?
Click to expand...
Click to collapse
Unless you're on the pro version, you cannot disable the homepage, and the stupid cleaner function is a major annoyance. My opinion; others' may vary.
@blueberry.sky cheers for the link, reading now...
AntDeek said:
So I am better off leaving 5.0.1 rooted in my Fire since it does everything I need it to.
Click to expand...
Click to collapse
Finally ! you got it !

Is there any downside to using 5.0.1 until 5.1.1 can be easily rooted?

AntDeek said:
Is there any downside to using 5.0.1 until 5.1.1 can be easily rooted?
Click to expand...
Click to collapse
5.1.1 cannot be downgraded
Sent from my KFFOWI using Tapatalk

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