Bootloader Mystery - Nexus 6P Q&A, Help & Troubleshooting

Welp now that safetynet checks the bootloader, I have to lock it to continue using android pay etc (non-rooted device).
I'm getting conflicting reports, so I was hoping someone here can solve this mystery.
Does relocking the bootloader automatically wipe the device?
Thanks

Yup.

It does for me when I attempted to get AP to work. Nexus 6p

seems like we're stuck in the crossroads of wipe the whole thing or go full root and say to hell with android pay :-/

arts711 said:
Welp now that safetynet checks the bootloader, I have to lock it to continue using android pay etc (non-rooted device).
I'm getting conflicting reports, so I was hoping someone here can solve this mystery.
Does relocking the bootloader automatically wipe the device?
Thanks
Click to expand...
Click to collapse
Unfortunately, I crossed this road yesterday. Yes I had to relock my bootloader and, yes, I had to wipe my phone

arts711 said:
seems like we're stuck in the crossroads of wipe the whole thing or go full root and say to hell with android pay :-/
Click to expand...
Click to collapse
I'm passing on AndroidPay.
I will not allow them to dictate what I do with my device.

tech_head said:
I'm passing on AndroidPay.
I will not allow them to dictate what I do with my device.
Click to expand...
Click to collapse
Same decision. Unless they start requiring locked bootloader for ridiculous reasons. I can sort of understand the financial/bank access concerns. If they expand the requirements for a locked boot loader beyond that, I'll return to the iPhone.

hawgguy said:
Same decision. Unless they start requiring locked bootloader for ridiculous reasons. I can sort of understand the financial/bank access concerns. If they expand the requirements for a locked boot loader beyond that, I'll return to the iPhone.
Click to expand...
Click to collapse
Love it when people "threaten" to return to iPhone lol,
Sent from my Nexus 6P using Tapatalk

Related

Tired of Waiting for 4.4 OTA

Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
badboy47 said:
Not sure what you mean about the bootloader. Yes u can unlock and lock the bootloader. After you lock it back; no there is not to tell if it was unlocked. If you want to upgrade to 4.4; follow this guide.
Click to expand...
Click to collapse
I mean People have had trouble when they have been at a Official Servicecenter.
Apparently the servicecenter said that the customer have had a open bootloader then locked it before going to repair, so the Servicecenter refused to repair the phone.
I dont know if its a myth or not?
so its 100 % secure not damaging any hardware just unlocking the bootloader with nexus toolkit.
Eastliin said:
Hi Everyone i got a Quite new Nexus 4.
Im tired of waiting for the OTA and decided to move on to flash in the Factory Images.
As ive been reading on alot of places it says it ruins my warranty. but according to the EU Directives it does not ruin my Hardware Warranty.
So what would you do? would you open the bootloader flash in 4.4 and lock the bootloader. is there anyway the Serviceman can see that only the bootloader been opened if i lock it directly afterwards?
best regards.
Click to expand...
Click to collapse
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data, again.
iowabeakster said:
I don't know a damn thing about EU Directives. But, I've never heard of google refusing to honor a warranty on a Nexus because the bootloader was unlocked. That's kind of expected on a Nexus, and that's why google makes it so easy to do. It's not like other phones that need to utilize some exploit to do it. There is very little that can go wrong. And it can almost always be fixed by flashing another factory image again.
If it was me, I would have unlocked the bootloader the day I bought it, because unlocking it will wipe your data now. There is no way around that. But if I were you, yes I would unlock it and install whatever you want to. Locking it up again is an option. But if you want to unlock again later, you will have to wipe data when you unlock in the future.
Click to expand...
Click to collapse
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Eastliin said:
here is a link to the directive im talking about.
http://matija.suklje.name/rooting-and-flashing-your-device-does-not-void-the-warranty-in-eu
I do wipes from time to time to keep the phone fresh so thats noo worries at all for me.
so for me its just getting toolkit, open bootloader, flash 4.4 then lock the bootloader no harm done?
Click to expand...
Click to collapse
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
iowabeakster said:
I also don't know anything about toolkits, I use linux and adb/fastboot (nerd).
But yes, unlock booloader, flash the new factory images, and relock it again if you want. Like I said, unlocking a Nexus is not some taboo process to google. Simply unlocking it won't void your warranty.
They only way you can void your warranty is abuse (dropping it, getting it wet, etc) , or installing BAD software that causes the hardware to malfunction. If you are installing google's factory images, you have nothing to worry about.
Click to expand...
Click to collapse
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Eastliin said:
ye i will follow a guide,
i know its ok to unlock bootloader by google, but LG that does the repair in sweden screams NONO haha
Click to expand...
Click to collapse
actualy google says to unlock,flash and then relock for"security purposes".
opssemnik said:
actualy google says to unlock,flash and then relock for"security purposes".
Click to expand...
Click to collapse
Thats fun haha, you got a link of where they state that?
Eastliin said:
Thats fun haha, you got a link of where they state that?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
opssemnik said:
https://developers.google.com/android/nexus/images?hl=pt-BR
"After restoring a factory image,lock the bootloader for security reasons." almost at bottom of page, after all the images. on instructions part.
Click to expand...
Click to collapse
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Eastliin said:
so with that link LG cant screw me at all! when it comes to repairing a phone.
Thx alot!
Click to expand...
Click to collapse
^, they tried to screw with me, but as i know lg here in brasil, i carried a book of "consumers defense code", i showed them the link,and the guy from the service center had to get my n4 and fix for no fee (my screen was broken, and no touch, but the screen broke because of overheating).

/!\ WARNING /!\ Do NOT relock your bootloader around the time of updating to 5.1!

Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app
ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.
:thumbup:
I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...
daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota
doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.
y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.
rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry

Root without bootloader unlock?

Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT

PSA: Android Pay and SafetyNet no longer work with unlocked bootloaders.

It seems that Google has turned it's back on devs a bit more. Tons of people are having this issue, as I was finally tweaking around and could never get safetynet working. Turns out I got an early taste of Google's rollout yesterday.
Happening to me as well. Both on my 5x and N6 that used to work. Locking the bootloader (I'm not rooted) will now wipe the phone, right?
I have a completely stock 5X. The only modification is an unlocked bootloader. When I installed the 7.1.1 DP update yesterday, Android Pay quit working. I tried to pay for an Uber ride using Android Pay and it failed. I assume the same is true for trying to use Android Pay via NFC in stores.
---------- Post added at 02:43 PM ---------- Previous post was at 02:40 PM ----------
Minker17 said:
Happening to me as well. Both on my 5x and N6 that used to work. Locking the bootloader (I'm not rooted) will now wipe the phone, right?
Click to expand...
Click to collapse
Unlocking the bootloader wipes the device. Locking does not.
http://www.androidcentral.com/how-unlock-nexus-5x-bootloader
I've seen reports that it started wiping a few versions ago. This is for a 6p, but have seen others. Does it just not apply to the 5x?
https://plus.google.com/+ArtemRussakovskii/posts/49VyN48ixDp
I relocked my bootloader yesterday, it does now cause a factory reset. It will also cause bricking to happen if you have a modified system, recovery or boot partition, recommend practice would be to flash a factory image before relocking if you have rooted or used twrp etc.
If you do go ahead also remember to back up anything you have on your storage first.
It was only a matter of time before they started doing stuff like this... I didn't know they were really that worried about nfc payments yet.
Minker17 said:
I've seen reports that it started wiping a few versions ago. This is for a 6p, but have seen others. Does it just not apply to the 5x?
https://plus.google.com/+ArtemRussakovskii/posts/49VyN48ixDp
Click to expand...
Click to collapse
I think the previous guy is confused. On 5x, t has been forcing a factory reset during lock since at least MHC19J if not since the beginning.
On older phones it didn't force factory reset during lock, only unlock, so I think many people are just going by memory and probably never relocked on 5x.
sfhub said:
I think the previous guy is confused. On 5x, t has been forcing a factory reset during lock since at least MHC19J if not since the beginning.
On older phones it didn't force factory reset during lock, only unlock, so I think many people are just going by memory and probably never relocked on 5x.
Click to expand...
Click to collapse
That's correct. I just relocked mine last night and I had to do a factory reset.
So, I installed the 7.1 preview a few days back without rooting or anything else, can I safely just relock bootloader to get android pay working again?
I was on the 7.0 factory image before hand, again, unrooted and stock recovery
Mikey F said:
So, I installed the 7.1 preview a few days back without rooting or anything else, can I safely just relock bootloader to get android pay working again?
I was on the 7.0 factory image before hand, again, unrooted and stock recovery
Click to expand...
Click to collapse
Yes, but be aware locking or unlocking your bootloader will wipe your device.
yochananmarqos said:
Yes, but be aware locking or unlocking your bootloader will wipe your device.
Click to expand...
Click to collapse
OK cool, yes I'm aware it will wipe the phone, I'm prepared for that.
The Flash's kernel now had a fix for that bootloader check.
Try it and see if it works for you before locking the bootloader. It is easier to flash a boot.img than it is to format.
odunke01 said:
The Flash's kernel now had a fix for that bootloader check.
Try it and see if it works for you before locking the bootloader. It is easier to flash a boot.img than it is to format.
Click to expand...
Click to collapse
So flashing the flash's kernel means android pay should work with unlocked bootloader?
With flash or Franco kernel I pass safetynet helper. So I am assuming it will work with pay, I don't have any cards at up atm to try.
Edit. Just enrolled a card and all good.
https://www.engadget.com/2016/10/24/android-pay-is-coming-to-hundreds-of-thousands-more-websites/
It's a losing battle imo. Either root or use banking and ap. No reason to try both. It's just frustrating.
Sent from my Nexus 5X using XDA-Developers mobile app
Wait. Just so I'm clear, unlocking the bootloader alone will break Android Pay? I typically unlock my bootloader as soon as I get a new phone, mainly so I can manually flash images, but I don't root or flash custom recovery. It's be really annoying to lose that option.
Sent from my Nexus 5X using Tapatalk
Yeah I think I'm going to just back up and relock my bootloader, android pay, once I'd started using it, became really handy
Don't use Android pay! Don't use any of those features. It's the only way to let Google know this is too far!
Same for SafetyNet.
It's MY device, so I want to decide how to use it. Therefor I won't use any app that forces me to lock bootloader, unroot, or whatsoever.
Bright.Light said:
Don't use Android pay! Don't use any of those features. It's the only way to let Google know this is too far!
Same for SafetyNet.
It's MY device, so I want to decide how to use it. Therefor I won't use any app that forces me to lock bootloader, unroot, or whatsoever.
Click to expand...
Click to collapse
That's fine and your decision, but AP is Google's service and they can operate how they want with what security features they want. And with lots of banks & lots of money on the line, you better believe it Google needs to ensure as much security as they can with it.
Bright.Light said:
Don't use Android pay! Don't use any of those features. It's the only way to let Google know this is too far!
Same for SafetyNet.
It's MY device, so I want to decide how to use it. Therefor I won't use any app that forces me to lock bootloader, unroot, or whatsoever.
Click to expand...
Click to collapse
Entirely your call, but working in the computer repair business, I deal with a lot of end users that have been done over by malware and ransomware, so any efforts to stop that are welcome. I'm happy to be able to use android pay at the cost of a more secure phone, so I'll be relocking my boot loader when I'm home from holiday

relocking bootloader

I can't remember if relocking the bootloader wipes the device or not. I know unlocking it does, but I want to relocking for android pay and don't want to be shocked if it wipes the data.
318sugarhill said:
I can't remember if relocking the bootloader wipes the device or not. I know unlocking it does, but I want to relocking for android pay and don't want to be shocked if it wipes the data.
Click to expand...
Click to collapse
It shouldn't wipe your data, but I think you would want a stock recovery if you do lock it.
Fe Mike said:
It shouldn't wipe your data, but I think you would want a stock recovery if you do lock it.
Click to expand...
Click to collapse
Everything is stock, I just unlocked it to flash factory images. I'm not rooted or anything on this device. Just want to use Android pay again. With the Android beta program, u never know what things might not work so I keep it unlocked to be able to roll back to whatever I liked best. But darn android pay and bootloader anymore.....
Fe Mike said:
It shouldn't wipe your data, but I think you would want a stock recovery if you do lock it.
Click to expand...
Click to collapse
I actually went to relocking it today, and it gives me a warning that it WILL wipe the device upon relocking the bootloader. I'm leaving it alone as I just got my pixel and unlocked that. I'll relocking it when I'm ready to sell this.
318sugarhill said:
I actually went to relocking it today, and it gives me a warning that it WILL wipe the device upon relocking the bootloader. I'm leaving it alone as I just got my pixel and unlocked that. I'll relocking it when I'm ready to sell this.
Click to expand...
Click to collapse
Really? I was under the impression it didn't, that's bad info on my part. Sorry, Thank you

Categories

Resources