Related
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.
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Badger50 said:
You won't lock the bootloader unless you manually enter the commands in fastboot.
You can update to July by either: fastbooting the factory image with the -w removed to preserve data. Flashing the OTA.zip in twrp. Or side load the OTA :good:
Click to expand...
Click to collapse
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Badger50 said:
You made no mention that it was a Verizon phone in your post. Therefore, I'm not sure now. Have you run the IMEI checker to see if it's truly a Verizon phone.
Sorry, my bad, you did mention it.
Click to expand...
Click to collapse
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
ryanispd said:
I've read that the only way to lock the bootloader once its unlocked is to manually do so via the commands, this should be the same regardless of if being Verizon I would assume but not sure and don't want to go through with updating without knowing.
What's a good IMEI checker to check which network, imei.info doesn't seem to show
Click to expand...
Click to collapse
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Badger50 said:
This is the only one I know of.
http://www.imeipro.info/check_lg.html
Click to expand...
Click to collapse
I checked via verizon's imei checker (https://www.verizonwireless.com/prospect/bring-your-own-device#/checkDevice)
looks like it isn't actually a verizon model, I'm in luck I guess.
ryanispd said:
My device is a Verizon phone, I was in luck when getting the phone for it being on an older security update just really worried that I will lock it if I try to update it.
Are you 100% sure this won't do so?
Is this guide fine to follow: https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535
or do I need to leave anything out while doing it? I thought I'd need to leave the bootloader-taimen-tmz12g-.img out or something to prevent it.
Apologizes if I sound dumb, I'm new to all this and only recently moved from Samsung to Pixel so I appreciate the help.
Click to expand...
Click to collapse
It will not relock. I am 100 percent sure. There are several reasons it wont. One is that relock will wipe your data, can you imagine the lawsuits if Google and Verizon send an update that they knew would wipe your data.
The second reason is that it is technologically impossible. You are thinking of when a VZ update breaks root o other phones. This phone is way different. It won't happen.
Relax, update.
You will lose root when you update. Easy enough to restore though.
ryanispd said:
I unlocked the bootloader on my Pixel 2 XL and rooted, while being on security patch May 2018, I'm wanting to update to July 2018's security patch but don't want to risk locking the bootloader.
It's a Verizon phone.
Anyone know if I can go about it and how exactly? Really nervous and don't really like my device without being rooted.
Any help is appreciated
Click to expand...
Click to collapse
I also have a Verizon phone that randomly let me unlock the bootloader. I was running DU and just flashed the OTA in TWRP. Booted right up. No issues with it relocking the bootloader or any other nonsense.
hi guys please help me i get this error on the screen ". The device will not start." and i can't use my phone, i can't enter the recovery mode (i get the same error) and the device state locked ! please help me
19 views no reply ! Up
Chouiyekh said:
19 views no reply ! Up
Click to expand...
Click to collapse
Tried reflashing stock?
djcrystals said:
Tried reflashing stock?
Click to expand...
Click to collapse
i can't because the bootloader is locked, please help to find a way to revive my mobile (i don't know i there is a box or something else to install the os even the bootloader locked)
the problem happened when i tried to relock the bootloader, unfortunately i don't know the place of purchase because i'm a second hand and i don't know the person who sold me the phone where to live we just met through the internet and we don't have google support in Morocco
Chouiyekh said:
i can't because the bootloader is locked, please help to find a way to revive my mobile (i don't know i there is a box or something else to install the os even the bootloader locked)
the problem happened when i tried to relock the bootloader, unfortunately i don't know the place of purchase because i'm a second hand and i don't know the person who sold me the phone where to live we just met through the internet and we don't have google support in Morocco
Click to expand...
Click to collapse
If you were not on full stock rom without root, or anything custom, and you turned off OEM unlocking and USB debugging, then locked the bootloader, you are basically hosed my friend
Look at this point it just needs to be said... PEOPLE STOP RE-LOCKING THE DARN BOOTLOADER!!
PERIOD!!
There are literally a half dozen posts this week with probably bricked phones and a good amount of them are this same root cause.
CyberpodS2 said:
Look at this point it just needs to be said... PEOPLE STOP RE-LOCKING THE DARN BOOTLOADER!!
PERIOD!!
There are literally a half dozen posts this week with probably bricked phones and a good amount of them are this same root cause.
Click to expand...
Click to collapse
Your preaching to the choir ol friend! While I agree with you 100%, some things are best learned the hard, and expensive way! I've done it twice myself.
The carpenters rule should apply to these phones as well...."measure twice, cut once" :good:
I remember and I'm sure that i left USB debugging enabled, and the bootloader locked, so is there any hope ?
Chouiyekh said:
I remember and I'm sure that i left USB debugging enabled, and the bootloader locked, so is there any hope ?
Click to expand...
Click to collapse
Did you leave OEM unlocking on as well? And, were you on full stock, non rooted rom?
Badger50 said:
Did you leave OEM unlocking on as well? And, were you on full stock, non rooted rom?
Click to expand...
Click to collapse
i left it in this case, OEM unlocking OFF and USB debugging ON, and i was on full stock, rooted rom , the problem happened when i tried to unroot and relock the bootloader
any hopes please please guys, i'm ready to donate for the one who will help i promise
Chouiyekh said:
any hopes please please guys, i'm ready to donate for the one who will help i promise
Click to expand...
Click to collapse
My friend.....you could give me or anybody else 10 thousand bucks, and it's still not going to solve your problem I'm sorry to say. You should have unrooted the phone first, then fastbooted the factory image, or do a factory reset, and made sure that OEM unlocking & USB debugging were left on until you were done locking the bootloader. Sorry man, but there's not much you can do without at least a stock recovery, so....accept the loss, learn from your mistake, and move on. Many of us here, including myself, have been there as well. What you choose to learn from it is up to you
Badger50 said:
My friend.....you could give me or anybody else 10 thousand bucks, and it's still not going to solve your problem I'm sorry to say. You should have unrooted the phone first, then fastbooted the factory image, or do a factory reset, and made sure that OEM unlocking & USB debugging were left on until you were done locking the bootloader. Sorry man, but there's not much you can do without at least a stock recovery, so....accept the loss, learn from your mistake, and move on. Many of us here, including myself, have been there as well. What you choose to learn from it is up to you
Click to expand...
Click to collapse
Thank you so much, i will accept this loss as you said and absolutely i will learn from it. Tupac was right " that which does not kill me can only make me stronger "
Chouiyekh said:
Thank you so much, i will accept this loss as you said and absolutely i will learn from it. Tupac was right " that which does not kill me can only make me stronger "
Click to expand...
Click to collapse
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Badger50 said:
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Click to expand...
Click to collapse
Easy to mistake the two...
Badger50 said:
No problem my friend. As they say "s#*t happens"
And your quote isn't from Tupac, it's from the philosopher Frederick Nietzsche in 1888. :laugh:
Click to expand...
Click to collapse
hahaha, what a big mustache he has
CyberpodS2 said:
Easy to mistake the two...
Click to expand...
Click to collapse
Oh absolutely it is! Almost like twins! ???
Badger50 said:
Oh absolutely it is! Almost like twins!
Click to expand...
Click to collapse
:laugh::laugh::laugh:
Chouiyekh said:
:laugh::laugh::laugh:
Click to expand...
Click to collapse
have you tried flashing the official ota image as that doesnt require an unlocked bootloader so it coud be worth a shot
kevtrysmoddin said:
have you tried flashing the official ota image as that doesnt require an unlocked bootloader so it coud be worth a shot
Click to expand...
Click to collapse
You are correct. Unfortunately, he has no stock recovery anymore
So a little while ago i tried to root my S9, it did not go well so i flashed stock firmware in Odin and everything started working fine again.
Yesterday my bank finally started supporting Google pay so i went to add my card but it said i was still rooted. After some searching i found out the my CTS Profile Match was failing because i unlocked the bootloader, is there anyway to relock the bootloader to pass safetynet?
on developer options you can disable bootloader unlock but its gonna factory reset your device.
dimitrispas22 said:
on developer options you can disable bootloader unlock but its gonna factory reset your device.
Click to expand...
Click to collapse
ok, are you sure that it will work. I have heard some theorys that once you trip Knox you can't relock the bootloader
thewoolysheep08 said:
ok, are you sure that it will work. I have heard some theorys that once you trip Knox you can't relock the bootloader
Click to expand...
Click to collapse
that knox how much i HATE it....
anyway i have the same device and i did that...
your knox is already 0x1 samsung pay and some other features for example s health you can not access it anymore via the original apk and firmware if you don't have root..
google pay will work just fine after you gonna lock the bootloader.
and if you want to use gpay with custom rom you must delete google play services and install a version that starts from 14. something and hide magisk but it works just fine
aparently
dimitrispas22 said:
that knox how much i HATE it....
anyway i have the same device and i did that...
your knox is already 0x1 samsung pay and some other features for example s health you can not access it anymore via the original apk and firmware if you don't have root..
google pay will work just fine after you gonna lock the bootloader.
and if you want to use gpay with custom rom you must delete google play services and install a version that starts from 14. something and hide magisk but it works just fine
aparently
Click to expand...
Click to collapse
I don't really care about the Samsung pay and that stuff. but will locking the bootloader even work with Knox tripped? all I want to do is pass safetynet
thewoolysheep08 said:
I don't really care about the Samsung pay and that stuff. but will locking the bootloader even work with Knox tripped? all I want to do is pass safetynet
Click to expand...
Click to collapse
after locking the bootloader you gonna pass safetynet yes
dimitrispas22 said:
after locking the bootloader you gonna pass safetynet yes
Click to expand...
Click to collapse
yeah I know that, but doesn't having Knox tripped make it unable to lock? have you done this exact thing before?
thewoolysheep08 said:
I don't really care about the Samsung pay and that stuff. but will locking the bootloader even work with Knox tripped? all I want to do is pass safetynet
Click to expand...
Click to collapse
https://photos.app.goo.gl/FVWPKofhji5EQKvq7
dont worry this is a google photo link which contains a proof that gpay works when you gonna lock the bootloader..
you can use smart switch to backup your data
dimitrispas22 said:
https://photos.app.goo.gl/FVWPKofhji5EQKvq7
dont worry this is a google photo link which contains a proof that gpay works when you gonna lock the bootloader..
you can use smart switch to backup your data
Click to expand...
Click to collapse
have you done this exact same thing before?
thewoolysheep08 said:
have you done this exact same thing before?
Click to expand...
Click to collapse
yes
dimitrispas22 said:
yes
Click to expand...
Click to collapse
alright, thanks so much for your help. I'll try this tomorrow and let you know how it went
dimitrispas22 said:
yes
Click to expand...
Click to collapse
ok, thanks so much for your help. I'll try it tomorrow and let you know how it goes
dimitrispas22 said:
yes
Click to expand...
Click to collapse
Thanks so much for your help, just did it today and it worked great!
I have a custom rom. If I block the bootloader, can I have google play certified?
I've a Samsung Galaxy S9 Plus
I have only experience of Rooting Google Phone actually. Now I have the first Samsung phone in my Hand that I want to root. But when I resell it, I want to lock the Bootloader again like I do with the original Google Phones. Is that possible with the A71 too?
XJSKFJHFKH23 said:
I have only experience of Rooting Google Phone actually. Now I have the first Samsung phone in my Hand that I want to root. But when I resell it, I want to lock the Bootloader again like I do with the original Google Phones. Is that possible with the A71 too?
Click to expand...
Click to collapse
locking the bootloader is possible. but re-knox your phone isn't possible. once trippin will be tripped forever.
faizauthar12 said:
locking the bootloader is possible. but re-knox your phone isn't possible. once trippin will be tripped forever.
Click to expand...
Click to collapse
Good to know that! So I need to read further before I begin to root. Thanks a lot for your quick response!
They use e-fuse which can only be turned from 0X0 to 0X1. That makes sense to me