I had someone suggest I leave my bootloader unlocked. I usually relock it. Does leaving it unlocked stop Google Pay and banking apps from working. Or Games like Pokemon Go?
That was me, but other more knowledgeable folks should feel free to chime in as we all could learn something here.
As I said in the other thread, I don't know. What I do know is that Google's safetynet is more likely to prevent you from using banking apps, Pokémon Go, or Google Pay than the bootloader. Case in point, I have my bootloader completely unlocked yet I still pass safetynet. Now, if an app actively checks for an unlocked bootloader then you may have an issue, but I'm not aware of apps that check for bootloader unlock status.
acheney1990 said:
I had someone suggest I leave my bootloader unlocked. I usually relock it. Does leaving it unlocked stop Google Pay and banking apps from working. Or Games like Pokemon Go?
Click to expand...
Click to collapse
It will certainly stop Google Pay from working, as the phone will report it is insecure.
Banking apps may or may not depending on what they check for.
acheney1990 said:
I had someone suggest I leave my bootloader unlocked. I usually relock it. Does leaving it unlocked stop Google Pay and banking apps from working. Or Games like Pokemon Go?
Click to expand...
Click to collapse
Unlocked breaks Pay. I don't recall any other apps that care.
Leave it unlocked. The forums here are littered with posts that say.... help, I relocked and now it is bricked......and those phones are still bricked.
Don't do it, it's Russian Roulette.
Flash a custom kernel that hides the unlock. Most all of them do, or root it with Magisk and that will hide it.
uicnren said:
It will certainly stop Google Pay from working, as the phone will report it is insecure.
Banking apps may or may not depending on what they check for.
Click to expand...
Click to collapse
This is incorrect.
I have an unlocked bootloader (and am rooted) and use Google Pay without issue.
mitchdickson said:
This is incorrect.
I have an unlocked bootloader (and am rooted) and use Google Pay without issue.
Click to expand...
Click to collapse
its not incorrect, an unlocked bootloader on stock Android will cause Google Pay to not work.
Your root hides the unlocked bootloader (which is why it passes safetynet)
uicnren said:
its not incorrect, an unlocked bootloader on stock Android will cause Google Pay to not work.
Your root hides the unlocked bootloader (which is why it passes safetynet)
Click to expand...
Click to collapse
So you probably shouldn't be saying an unlocked bootloader will definitely stop Google pay from working.
mitchdickson said:
So you probably shouldn't be saying an unlocked bootloader will definitely stop Google pay from working.
Click to expand...
Click to collapse
Except is does, nowhere did the OP mention root, I answered his question 100% correct.
uicnren said:
Except is does, nowhere did the OP mention root, I answered his question 100% correct.
Click to expand...
Click to collapse
You made a blanket statement that an unlocked bootloader definitely stops Google Pay from working. We both know this isn't true.
You aren't just answering the question for OP, but also for any other user who might search for a topic like this.
You should probably edit your post to say that it will definitely stop Google Pay from working if you do not take further steps to protect safety net integrity.
mitchdickson said:
Yes u made a blank t statement that an unlocked bootloader definitely stops Google Pay from working. We both know this isn't true.
You aren't just answering the question for OP, but also for any other user who might search for a topic like this.
You should probably edit your post to say that it will definitely stop Google Pay from working if you do not take further steps to protect safety net integrity.
Click to expand...
Click to collapse
I shouldnt edit anything because its 100% accurate as answered, and as asked.
uicnren said:
I shouldnt edit anything because its 100% accurate as answered, and as asked.
Click to expand...
Click to collapse
Except that it's not.
mitchdickson said:
Except that it's not.
Click to expand...
Click to collapse
It is.
uicnren said:
It is.
Click to expand...
Click to collapse
It's an answer that fails to take any nuance into account, and instead chooses to declare that any unlocked bootloader will cause Google Pay to not work.
mitchdickson said:
It's an answer that fails to take any nuance into account, and instead chooses to declare that any unlocked bootloader will cause Google Pay to not work.
Click to expand...
Click to collapse
I dont go by 'nuance' only by what the OP asked in his question, and in that regard, the answer is 100% correct.
I dont assume anything, had they asked the question differently, then maybe they would get a different answer.
Now people will go unlock their bootloader, without root and wonder why the hell Google pay isn't working, because someone said it would.
uicnren said:
I dont go by 'nuance' only by what the OP asked in his question, and in that regard, the answer is 100% correct.
I dont assume anything, had they asked the question differently, then maybe they would get a different answer.
Now people will go unlock their bootloader, without root and wonder why the hell Google pay isn't working, because someone said it would.
Click to expand...
Click to collapse
Here's the thing: you can have an unlocked bootloader, without root, and still pass Safety Net by flashing a kernel which incorporates this patch: https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
You are continuing to ignore that you are not only answering a question for OP, but for anyone who may come across this thread.
mitchdickson said:
Here's the thing: you can have an unlocked bootloader, without root, and still pass Safety Net by flashing a kernel which incorporates this patch: https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
You are continuing to ignore that you are not only answering a question for OP, but for anyone who may come across this thread.
Click to expand...
Click to collapse
Nope, I only answered for the OP, with the information provided. Im not answering to anyone else.
If they are already going through all the other stuff, they wouldnt be asking the question, since you're stuck on 'nuance' and assumptions.
uicnren said:
Nope, I only answered for the OP, with the information provided. Im not answering to anyone else.
If they are already going through all the other stuff, they wouldnt be asking the question, since you're stuck on 'nuance' and assumptions.
Click to expand...
Click to collapse
You're assuming the OP wouldn't root and would not flash a kernel.
My whole point is that you shouldn't make that assumption.
mitchdickson said:
You're assuming the OP wouldn't root and would not flash a kernel.
My whole point is that you shouldn't make that assumption.
Click to expand...
Click to collapse
I didnt assume anything.
The answer was based on the information provided (or lack thereof).
uicnren said:
I didnt assume anything.
The answer was based on the information provided (or lack thereof).
Click to expand...
Click to collapse
Did I miss where the OP said he wouldn't root and wouldn't flash a kernel?
mitchdickson said:
Did I miss where the OP said he wouldn't root and wouldn't flash a kernel?
Click to expand...
Click to collapse
No, you missed where he said he would.
Related
Hi all,
Just got a OP3 and was thinking about unlocking the bootloader. Having read OnePlus' policy on warranty and root, there should be no problem.
However, I have read about the "Tampered flag" that is set when unlocking the bootloader and which doesn't get reset even after relocking it. Could this affect my ability to run Android Pay or any other similarly secure software? I've read that Knox will start doing that, so better to be safe than sorry
Thanks!
You can use Android Pay with an unlocked bootloader fine even when you've re-locked it. it'd just root that will stop Android Pay from working.
Roxas598 said:
You can use Android Pay with an unlocked bootloader fine even when you've re-locked it. it'd just root that will stop Android Pay from working.
Click to expand...
Click to collapse
Thank you!
I guess there's no way to reset the tampered flag?
vagaerg said:
Thank you!
I guess there's no way to reset the tampered flag?
Click to expand...
Click to collapse
I don't think there even is one, if there is i've never noticed it or it causing issues to anything.
Roxas598 said:
I don't think there even is one, if there is i've never noticed it or it causing issues to anything.
Click to expand...
Click to collapse
Awesome. Thanks a lot again!
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.
jhs39 said:
If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.
Click to expand...
Click to collapse
You don't need root. Just need an unlocked bootloader.
toknitup420 said:
You don't need root. Just need an unlocked bootloader.
Click to expand...
Click to collapse
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.
jhs39 said:
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.
Click to expand...
Click to collapse
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.
rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
Did you find the phone somewhere or is it yours legitimately? Are you trying to break into another device to get information off it? If you're honest about your intentions you really should explain accurately.
If it's a startup pin you can't bypass that. I hope for owner's sake the bootloader is locked including you if it's yours.
Sent from my Pixel using XDA-Developers Legacy app
toknitup420 said:
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.
Click to expand...
Click to collapse
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.
jhs39 said:
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.
Click to expand...
Click to collapse
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.
toknitup420 said:
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.
Click to expand...
Click to collapse
I misinterpreted your comment then but a lot of people on XDA obviously like to flash their phones and on the Nexus 6P thread you were told by the person who wrote the flashing guides that the absolute first thing you should do with that phone when you got it was to unlock the bootloader. As for getting TWRP to work on the Pixel a lot of experienced flashers including myself have found it challenging to get TWRP to work on this particular phone. Google didn't make Pixels easy to flash on--particularly compared with their earlier Nexus devices. That said I honestly had no idea unlocking the bootloader made the phone that insecure so I sincerely thank you for the heads up.
huh
toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Don't you need the pin to even get into TWRP to delete the file?
Raegoul said:
Don't you need the pin to even get into TWRP to delete the file?
Click to expand...
Click to collapse
Ah yes I forgot about this. This trick only works on decrypted devices. Decrypted devices don't require a password or pattern to enter twrp. Pixel is encrypted by default so yes you would need the password in order to access twrp. GLO. I completely forgot about that.
toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Won't it ask for the password when op starts twrp. And if op doesn't have it it cannot decrypt the file system to delete the file you mentioned.
Edit:
NVM saw someone mentioned it
No offense to the OP, but I'm going to call it and say we probably shouldn't be saying anymore. I have never heard of someone setting up their device and then not knowing what their password is. Not saying it's not possible, but if you're on XDA, with a Pixel device on Android O, that means; a) you flashed it and should know your way around some key things on Android, b) you stole the phone, or c) you're trying to break into your significant other's device, and last but not least d) you bought it on Swappa or Cracklist or wherever and the seller didn't wipe it.
People forget their passwords ALL the time... ask my lady if you want!
Erikbronx said:
People forget their passwords ALL the time... ask my lady if you want!
Click to expand...
Click to collapse
Buy her a pen and a pad. No excuses in this day and age.
Sent from my Pixel using XDA-Developers Legacy app
Can't you just go to google.com/android/devicemanager and log in with your google account and unlock it there?
Sorry if this is naive, but the s9 (g960U) is the first phone I've had with a locked bootloader
I'm wondering if anyone with this model has tried to flash a magisk boot image with odin, and had any luck?
Seems like the most likely way to get some semblance of root without being able to flash TWRP.
Any one tried it/is it worth trying, and if i do try it, is there a special version of Odin that would be necessary?
Nye-uhls said:
Sorry if this is naive, but the s9 (g960U) is the first phone I've had with a locked bootloader
I'm wondering if anyone with this model has tried to flash a magisk boot image with odin, and had any luck?
Seems like the most likely way to get some semblance of root without being able to flash TWRP.
Any one tried it/is it worth trying, and if i do try it, is there a special version of Odin that would be necessary?
Click to expand...
Click to collapse
You can't. My understanding of "locked bootloader" is that the device simply won't allow you to flash anything that isn't signed by Samsung.
nelsyv said:
You can't. My understanding of "locked bootloader" is that the device simply won't allow you to flash anything that isn't signed by Samsung.
Click to expand...
Click to collapse
That's my understanding too, that's why i haven't taken the time to just try it.
I've read things about a modified version of odin that lets you flash unsigned images, but i don't know if that's still a thing and if it would apply here
Nye-uhls said:
That's my understanding too, that's why i haven't taken the time to just try it.
I've read things about a modified version of odin that lets you flash unsigned images, but i don't know if that's still a thing and if it would apply here
Click to expand...
Click to collapse
You can't flash anything custom with a locked bootloader. modified ODIN or not
I am just freaking amazed at the folks that attempt to modify their devices without thorough research and at least searching for answers that have been posted over and over again.
Tel864 said:
I am just freaking amazed at the folks that attempt to modify their devices without thorough research and at least searching for answers that have been posted over and over again.
Click to expand...
Click to collapse
The best one is when they've rooted / custom, but have no idea how to return to stock
Tel864 said:
I am just freaking amazed at the folks that attempt to modify their devices without thorough research and at least searching for answers that have been posted over and over again.
Click to expand...
Click to collapse
Do you mean me? Because i haven't attempted to modify, this is my research. And i haven't seen this asked since magisk just added support for the s9, so I'm curious to know if that changed anything for locked bootloaders, since topjohnwu didn't say much about what kind of support was added.
And I'm just desperately clinging onto hope for returning to a rooted device.
If it's snapdragon it's locked.
Tel864 said:
If it's snapdragon it's locked.
Click to expand...
Click to collapse
False. There are unlockable snapdragons. The s9 is the SM-G9600 and the s9+ is the SM-G9650.
Please help stop spreading this misconception. Thanks
partcyborg said:
False. There are unlockable snapdragons. The s9 is the SM-G9600 and the s9+ is the SM-G9650.
Please help stop spreading this misconception. Thanks
Click to expand...
Click to collapse
As OP has a US flag set as their country, and even states "G960U" in their post, their snapdragon is locked, as most of them are locked, only two that are not and are not US models, as has been the case since at least the S7, I can't speak for previous
*Detection* said:
As OP has a US flag set as their country, and even states "G960U" in their post, their snapdragon is locked, as most of them are locked, only two that are not and are not US models, as has been the case since at least the S7, I can't speak for previous
Click to expand...
Click to collapse
All true, but does not change the fact that "if it's a snapdragon it's locked" is not a true statement. I live in the us, and have a snapdragon, but my bootloader is unlocked.
partcyborg said:
False. There are unlockable snapdragons. The s9 is the SM-G9600 and the s9+ is the SM-G9650.
Please help stop spreading this misconception. Thanks
Click to expand...
Click to collapse
Hmm, hopefully you can read and if not please stop spreading that misconception.
Tel864 said:
Hmm, hopefully you can read and if not please stop spreading that misconception.
Click to expand...
Click to collapse
I can, but can you? Trying to parse this sentence makes me not so sure...
Thats not true. You dudes shouldn't answer questions you don't know the answer to.
Not sure if it has anything to do with unlocking bootloader, but it seems that I can't install Netflix because my device is not certified in the Play Store. Anyone else come across this issue?
It is caused by the unlocked bootloader. It has been that way with Pixels since the originals. The solutions are to root with Magisk (do not know if Magisk works with the Pixel 3 or not) or use a custom kernel when one becomes available provided the P3 works like the P and P2.
Sideload it, done.
krabman said:
Sideload it, done.
Click to expand...
Click to collapse
what level is your widevine since you have unlocked your bootloader, did it change?
Actually I need to backtrack here, Netflix wont install on a rooted device and while some say it works I've never had it work with Magisk either. On the other hand you can just sideload and it will work fine rooted. I don't actually know what happens if the device is unlocked but not rooted because I've never done that. lol My bad. I would try sideloading though, it's got a good shot at working and nothing lost if it doesn't.
Just download apk file from apk mirror
Works fine
https://www.apkmirror.com/apk/netfl...flix-6-13-0-build-29940-android-apk-download/
Figured, it's been this way for a fair while now and thats been the fix from the start.
Just open play store in settings\apps, clear data. Reopen the play store and see if it still says it. Might have to do it more than once. I unlocked my bootloader, and I saw that. I had to clear data twice. Now mine shows as certified.
gettinwicked said:
Just open play store in settings\apps, clear data. Reopen the play store and see if it still says it. Might have to do it more than once. I unlocked my bootloader, and I saw that. I had to clear data twice. Now mine shows as certified.
Click to expand...
Click to collapse
No dice for me Google Pay won't work either... strange
virtyx said:
what level is your widevine since you have unlocked your bootloader, did it change?
Click to expand...
Click to collapse
How do I check widevine?
JeromeLeung said:
No dice for me Google Pay won't work either... strange
Click to expand...
Click to collapse
Weird, mine went back to not certified. I did the clear data again and it's good, again. Hrmm
gettinwicked said:
Weird, mine went back to not certified. I did the clear data again and it's good, again. Hrmm
Click to expand...
Click to collapse
Will Google Pay allow you to add a card?
JeromeLeung said:
Will Google Pay allow you to add a card?
Click to expand...
Click to collapse
Nope. Says it cannot complete setup because the device has been rooted or modified. And play store keeps jumping back to uncertified. Guess it won't stick. Have to wait for root. No biggie, I haven't fully jumped on the GPay train yet.
gettinwicked said:
Nope. Says it cannot complete setup because the device has been rooted or modified. And play store keeps jumping back to uncertified. Guess it won't stick. Have to wait for root. No biggie, I haven't fully jumped on the GPay train yet.
Click to expand...
Click to collapse
Okay, I thought something was wrong with my device. Good to know we're all in the same boat
I'm kiinda wondering if the much talked about Titan chip is going to make it harder to hide root. Some of the stuff out there is making that claim. Something related is that I followed a link to a google blog about it and the said that one of it's (Titian's) features is the ability to block unlocking. Not that it did block it, that it had that ability, so presumably it will depend on the OEM whether or not that feature is active. Was wondering where that will put the Verizon guys... Not trying to scare anyone because I haven't run into anything specific that comes from google and says exactly what it does but I know it's got my attention.
JeromeLeung said:
How do I check widevine?
Click to expand...
Click to collapse
you can download an app to check, just search widevine
virtyx said:
you can download an app to check, just search widevine
Click to expand...
Click to collapse
Widevine Security Level: L1
JeromeLeung said:
Widevine Security Level: L1
Click to expand...
Click to collapse
with unlocked bootloader?
Hi
It happens to me on samsung s8 device not certified. I have tried some things( saw in youtube and foruns) and nothing.
So try this...
Open setting/apps/ and look if any app of google is disabled( chrome/gmail/play movies...) activate all from google and voila
My s8 is now certified
virtyx said:
with unlocked bootloader?
Click to expand...
Click to collapse
That's correct
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
upperbladez said:
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
Click to expand...
Click to collapse
I had the same issue and someone replied and said that the newest version of Google play services can detect unlocked bootloader. It works if you rollback to an older version but it may just be easier to wait until they update Magisk.
Here is a link with more info.
https://forum.xda-developers.com/ap...magisk-discussion-t3906703/page2#post79044917
upperbladez said:
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
Click to expand...
Click to collapse
This was an issue on the stable release, so I switch to canary. As far as I know now, it should be resolved on stable with a wipe of data from google Pay but see this thread for more info - https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703
upperbladez said:
Magisk says that my device is secure, but Google pay is not working. The payment method works when I am ordering from the Google play store. It is just my debit card. Any ideas?
Click to expand...
Click to collapse
Custom or stock rom? What kernel?
I am on HavocOS with Kirisakura kernel. Google pay working fine with latest update for me. I have seen other people discussing non-working google pay, and switching to a different kernel solved it for them.
suhridkhan said:
Custom or stock rom? What kernel?
I am on HavocOS with Kirisakura kernel. Google pay working fine with latest update for me. I have seen other people discussing non-working google pay, and switching to a different kernel solved it for them.
Click to expand...
Click to collapse
Havoc as well, am and was on the same Kirishakura kernal as well so I dont think its kernel related.
Remove all cards. Clear storage for Google pay and Google services. Then add cards again.
shortyboy said:
Remove all cards. Clear storage for Google pay and Google services. Then add cards again.
Click to expand...
Click to collapse
What happens if you don't remove your cards and just clear storage for Google Pay and Google Services? It said it can't remove my card because it's associated with a service or subscription, likely from financing my p2xl through Google. Any other work around to get Google pay working?
fortillian said:
What happens if you don't remove your cards and just clear storage for Google Pay and Google Services? It said it can't remove my card because it's associated with a service or subscription, likely from financing my p2xl through Google. Any other work around to get Google pay working?
Click to expand...
Click to collapse
This happens to me too.
I updated magisk. Still isn't working. Anyone else?
Ehm I have advice because I had this problem either. Just lock bootloader and it will work. But be carefull, if you have custom recovery than there is chance to brick device.
Still ongoing with no permanent solution yet. Its likely going to take an update to Magisk to fix.
All of the workarounds are temporary for a few days before things are detected again.
Relostyt said:
Ehm I have advice because I had this problem either. Just lock bootloader and it will work. But be carefull, if you have custom recovery than there is chance to brick device.
Click to expand...
Click to collapse
thats what google wants you to do when they soft brick your phone with an update and you cant reflash it and you have to pay $$$$$$$$ to fix something you could do for free the allow unlocking option was the worst thing that has happened to android at least before this was around you could recover phone but lose data but now os bricked and cant read state of toggle rip your phone!!! so no im not re locking my bootloader to have android pay work i want it to work but not bad enough to risk my phones safety
billycar11 said:
thats what google wants you to do when they soft brick your phone with an update and you cant reflash it and you have to pay $$$$$$$$ to fix something you could do for free the allow unlocking option was the worst thing that has happened to android at least before this was around you could recover phone but lose data but now os bricked and cant read state of toggle rip your phone!!! so no im not re locking my bootloader to have android pay work i want it to work but not bad enough to risk my phones safety
Click to expand...
Click to collapse
Yeah...I don't think I'd do this one.
Itachisasuke said:
Still ongoing with no permanent solution yet. Its likely going to take an update to Magisk to fix.
All of the workarounds are temporary for a few days before things are detected again.
Click to expand...
Click to collapse
Is that the thread to watch where the fix will be announced?
billycar11 said:
thats what google wants you to do when they soft brick your phone with an update and you cant reflash it and you have to pay $$$$$$$$ to fix something you could do for free the allow unlocking option was the worst thing that has happened to android at least before this was around you could recover phone but lose data but now os bricked and cant read state of toggle rip your phone!!! so no im not re locking my bootloader to have android pay work i want it to work but not bad enough to risk my phones safety
Click to expand...
Click to collapse
upperbladez said:
Yeah...I don't think I'd do this one.
Click to expand...
Click to collapse
Just a heads up guys I've actually relocked and locked my bootloader multiple times maybe 4/5 times in the past month and never experienced no hard it soft bricks always went smoothly as long as you follow the instructions. Now I'm thinking of relocking again because Google pay is actually more important to me than root but if there's an update coming to fix Google pay them I'll wait.
sharpz811 said:
Just a heads up guys I've actually relocked and locked my bootloader multiple times maybe 4/5 times in the past month and never experienced no hard it soft bricks always went smoothly as long as you follow the instructions. Now I'm thinking of relocking again because Google pay is actually more important to me than root but if there's an update coming to fix Google pay them I'll wait.
Click to expand...
Click to collapse
yes your phone wont brick from re locking the problem comes down the line for an update or something like that i have unlocked and relocked bootloaders many times too but what happens when your phone soft bricks months later after an update and it can only get to fastboot and it cant be unlocked because the phone can read the state of the togggle in the os if unlocking is allowed rip phone
billycar11 said:
yes your phone wont brick from re locking the problem comes down the line for an update or something like that i have unlocked and relocked bootloaders many times too but what happens when your phone soft bricks months later after an update and it can only get to fastboot and it cant be unlocked because the phone can read the state of the togggle in the os if unlocking is allowed rip phone
Click to expand...
Click to collapse
Bruh just when i thought i was finally getting the hang of understanding this pixel. My 6p was so much easier to work with lol. So basically what you saying is that it's best to keep bootloader unlocked to prevent any possible bricks later down the road?
sharpz811 said:
Bruh just when i thought i was finally getting the hang of understanding this pixel. My 6p was so much easier to work with lol. So basically what you saying is that it's best to keep bootloader unlocked to prevent any possible bricks later down the road?
Click to expand...
Click to collapse
yup
shortyboy said:
Remove all cards. Clear storage for Google pay and Google services. Then add cards again.
Click to expand...
Click to collapse
Is this fix still working for you after April update? Root is more important to me than Google Pay but it's a convenience.
is this working for anyone else?