Help, I want to Relock my Bootloader - Nexus 6 Q&A, Help & Troubleshooting

Hi All,
I want to relock my Bootloader on my Nexus 6 running Nougat N6F26U. Has anyone relocked on Nougat?

RacerXO said:
Hi All,
I want to relock my Bootloader on my Nexus 6 running Nougat N6F26U. Has anyone relocked on Nougat?
Click to expand...
Click to collapse
Hello... Why do you specifically ask about Nougat? Unlock/relock is not firmware dependant..
Something to read just in case you didn't find it when you searched: https://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Good luck...

RacerXO said:
Hi All,
I want to relock my Bootloader on my Nexus 6 running Nougat N6F26U. Has anyone relocked on Nougat?
Click to expand...
Click to collapse
And why do you want to relock? Paranoid about security? Keep your phone in your pocket.
All advice in XDA is not to relock your bootloader because it reduces the possibilities of recovering if you ever make a mess of an update.

dahawthorne said:
And why do you want to relock? Paranoid about security? Keep your phone in your pocket.
All advice in XDA is not to relock your bootloader because it reduces the possibilities of recovering if you ever make a mess of an update.
Click to expand...
Click to collapse
I want to relock my bootloader so I can use Android Pay.

5.1 said:
Hello... Why do you specifically ask about Nougat? Unlock/relock is not firmware dependant..
Something to read just in case you didn't find it when you searched: https://forum.xda-developers.com/nexus-6/general/guide-safely-lock-bootloader-android-5-1-t3067302
Good luck...
Click to expand...
Click to collapse
Thanks for the reply, I read it and didn't know if it would work on Nougat.

RacerXO said:
I want to relock my bootloader so I can use Android Pay.
Click to expand...
Click to collapse
Just install a custom Kernel that "kind of" hide your unlocked bootloader. EX Kernel, Franco and some others will be just fine. Android Pay will work... I would never lock the bootloader of mine, except for RMA purpose. If something fails, you have way more chance fixing it..! :good:
RacerXO said:
Thanks for the reply, I read it and didn't know if it would work on Nougat.
Click to expand...
Click to collapse
Yeah don't worry, it's still a Nexus

RacerXO - did you get Android Pay to work on the N6F26U Build? I also cannot get the bootloader to relock. I tried using WugFresh Nexus Root Tookit v2.1.9.
Did you install a custom Kernal? Wondering if this the answer. Thanks for the help.

I was unlocked from the first day I got the phone. Today I am locked, running nougat. Having read some of the horror stories here, I've always booted the phone after flashing updates before rooting. Did the same thing when I went back to stock to use AP. I backed everything I wanted to keep and made sure it booted, before I locked the bootloader. No issues after almost a month.

What I wound up doing was go to the T-Mobile page and established the official latest factory image was 6.0.1 MMB29K - installed that using Wugfresh. After installing and logging into WiFi and my Gmail account was prompted to install 7.0.0 NBD92G - this installed fine and then after installing a couple of security updates (thru April 2017) was able to Re-Lock my Bootloader (I wanted Android Pay to accept my credit cards). Data reception is still degraded significantly, am now thinking there is a problem with the tower.

voyageurs60 said:
RacerXO - did you get Android Pay to work on the N6F26U Build? I also cannot get the bootloader to relock. I tried using WugFresh Nexus Root Tookit v2.1.9.
Did you install a custom Kernal? Wondering if this the answer. Thanks for the help.
Click to expand...
Click to collapse
Rooting with Magisk then using Magisk manager to "hide" root should give you android pay again. This may not be the directing you want to go in, but it is an option.

I locked Bootloader but you have to flash stock recovery 1st

I was on stock 7.1.1 unlocked bootloader, rooted Nexus 6.
I relocked my bootloader by simply going into adb/fastboot and flashed the latest stock factory firmware image (not the ota) with the June 5, 2017 security update, rebooted, activated developer options and enabled usb debugging, adb/fastboot again, and entered the command "fastboot oem lock", hit okay/yes when I got the relock warning, and voila! phone relocked.
Rebooted and set up phone/reinstalled my apps, music, and files.
No issues.

Related

[Q] Can you be rooted and have a locked bootloader

I'm interested in rooting my nexus 6. I know that you have to unlock the bootloader in order to root the phone and install a custom recovery. But after all of that is done is it ok for me to re-lock the bootloader for security reasons or will it have any issues?
Thanks in advance.
nfremd said:
I'm interested in rooting my nexus 6. I know that you have to unlock the bootloader in order to root the phone and install a custom recovery. But after all of that is done is it ok for me to re-lock the bootloader for security reasons or will it have any issues?
Thanks in advance.
Click to expand...
Click to collapse
Not on 5.1
nfremd said:
I'm interested in rooting my nexus 6. I know that you have to unlock the bootloader in order to root the phone and install a custom recovery. But after all of that is done is it ok for me to re-lock the bootloader for security reasons or will it have any issues?
Thanks in advance.
Click to expand...
Click to collapse
Please click the top link in my signature for more information about locking the bootloader.
cam30era said:
Not on 5.1
Click to expand...
Click to collapse
Why is that the case? I was able to unlock flash 5.0, relock and side load 5.1. Did Google change something in 5.1?
nfremd said:
Why is that the case? I was able to unlock flash 5.0, relock and side load 5.1. Did Google change something in 5.1?
Click to expand...
Click to collapse
Yes. Very much so.
problem is.. you now have to enable oem unlocking, to unlock the bootloader. technically, you can still be rooted and lock your bootloader. but the problem is that some have gone back and relocked their bootloader(not with root i dont think so) only to find that they cant boot up, that they end up with a boot loop. and then they cant unlock their bootloaders to flash the factory.img, because you need to check that setting first, to unlock the bootloader. honestly, i think someone with root, and twrp, would be able to. if not, you can fix it by formatting a few things(if you have twrp).
nfremd said:
I'm interested in rooting my nexus 6. I know that you have to unlock the bootloader in order to root the phone and install a custom recovery. But after all of that is done is it ok for me to re-lock the bootloader for security reasons or will it have any issues?
Thanks in advance.
Click to expand...
Click to collapse
If you have a custom recovery installed, then having a locked bootloader is no more secure than having an unlocked one...
Sent from my Nexus 6 using Tapatalk

[Q] Android M flash

hello guys ) i just wanna ask if its possible to flash android m with nexus root toolkit or no ??
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
jj14 said:
Apparently, yes. https://plus.google.com/113329792100896065459/posts/ZFUJD6Yn4hm
Click to expand...
Click to collapse
thank you for the fast reply
Yes I followed those steps and flashed it perfectly.
BossJ said:
Yes I followed those steps and flashed it perfectly.
Click to expand...
Click to collapse
yeah same here, everything went more then well.
Should I relock the bootloader after flashing M ?
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
NOOO!!!!
To many folks have encountered an issue that soft-bricked their device afterwards.
You will still receive OTA with an unlocked bootloader.
M5Rahul said:
Should I relock the bootloader after flashing M ?
Click to expand...
Click to collapse
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
stricker said:
you can relock it (safer) but if you want to flash any new rom later you will loose all your data. cause everytime you flash you need to unlock the bootloader. its up to you
Click to expand...
Click to collapse
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
danarama said:
Hang on now, lets be clear about the advice that we're giving here.
Yes, a locked bootloader is safer if a thief were to get his hands on your device. However, locking the bootloader has a whole host of other problems linked to it. For example, if you end up in a boot loop with a locked bootloader because something breaks in the rom or kernel, if you have stock recovery, you can never unlock the bootloader again, without sending it for repair.
I would suggest people using experimental ROMs should keep their bootloader unlcoked to avoid this
Click to expand...
Click to collapse
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
If I did lock the boot loader, can it not be unlocked again using NRT ? I'm wondering since this (Android M) is an official release from Google, there should be a way to unlock the Boot loader if someone wants to roll back to lollipop ... Am I wrong in this assumption ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
danarama said:
It's a security feature whereby if you do not have "enable OEM unlocking" set in the rom, you cannot unlock the bootloader. If you don't have it set, have stock recovery then have a rom that will not boot, you cannot set that, ergo cannot unlock the bootloader. If you're going to mess with exxperiemental previews, I would suggest not re-locking the bootloader.
Click to expand...
Click to collapse
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
M5Rahul said:
I just checked and the 'OEM unlocking' option is turned on under Dev Options.
So, can I unlock the bootloader and flash back to 5.1.1 ?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you like.

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.
H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.
-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.
Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.
Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.

Nexus 6 Cyanogenmod carrier ROM ?

I looked on Cyanogenmod's website below:
https://download.cyanogenmod.org/?device=shamu
and it just has 1 ROM for Nexus 6. I have Nexus 6 for Sprint. Is there only 1 version of the ROM that works for all carriers ?
My old Galaxy S4 has many different builds for Sprint, ATT, Verizon, etc.... wasn't sure if Nexus has the same set up.
Yes, applies to all N6 variants.
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
simms22 said:
thats because every sgs4 has a different setup for different carriers. we only have one nexus 6, and its the same for every carrier.
Click to expand...
Click to collapse
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
mikeprius said:
I didn't have a locked bootloader with Sprint Galaxy S4. If I were to restore the Nexus 6 back to stock to do an OTA update to update everything, then re-root and put a new custom ROM does the bootloader need to be re-locked, or can the factory .img be suffice to do an OTA ?
I'm still trying to learn how to do this as it is much different than the Samsung GS4. I saw there is a Nexus Toolkit by wug fresh. Is there any benefit to doing these processes by adb vs just using this progra which seems easier ?
Click to expand...
Click to collapse
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
simms22 said:
you dont use adb for it, you use fastboot. and doung it right vs a toolkit.. toolkits dont teach you anything, and can mess things up.
Click to expand...
Click to collapse
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
mikeprius said:
Does the bootloader need to be locked to do OTAs or does the stock ROM with leaving the bootloader unlock suffice for an OTA ?
Click to expand...
Click to collapse
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
simms22 said:
bootloader can be locked or unlocked, it doesnt matter. but i recommend that you keep it unlocked forever, as it can save your phone in certain situations. and having it locked can be the end of your device, in the same situations.
Click to expand...
Click to collapse
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
mikeprius said:
Ok. That's what I was planning on doing once it becomes unlocked. I was going to have it set like my previous GS4 and just toggle custom ROMs from there. When you mention having it locked, are you referring to when people have re-locked the bootloader then had an error flashing the stock custom ROM thus bricking the phone ? That's what worries me. Looks like the security is more stringent on the new Nexus vs. older versions.
Click to expand...
Click to collapse
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
simms22 said:
i was actually refering to it because of the unlock setting that has to be ticked to unlock. some stock users got caught in a bootloop, then cant boot up to tick the setting, to fix their bootloop. since it cant get unlocked, their phones are a "brick".
Click to expand...
Click to collapse
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
mikeprius said:
Is this what happened to this person below ?:
http://forum.xda-developers.com/nexus-6/help/help-nexus-6-brick-t3227126
Since the stock rom did not have developer options "checked" then the bootloader can't be unlocked ? How can you tick the OEM unlock if it is in a bootloop ?
Click to expand...
Click to collapse
you cant, thats why i said that you should keep it unlocked.
simms22 said:
you cant, thats why i said that you should keep it unlocked.
Click to expand...
Click to collapse
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
mikeprius said:
Ok that makes sense. What is the purpose of having the bootloader come locked in a stock phone then ? What does it actually do ? Prevents root ? I probably took it for granted mine was always unlocked before so all I had to do was worry about flashing the proper carrier ROM
Click to expand...
Click to collapse
Security.
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
scryan said:
Security in that if stolen your phone cannot be made to work for someone else...
Someone can (and likely will [emoji14]) correct me if I am wrong... But does little to secure your data...ESPECIALLY if you stay encrypted.
Click to expand...
Click to collapse
It does nothing to secure data from remote access, but it will protect data (if set with a password) from physical access, providing they do not know the password. The bootloader being unlocked, with no password on encryption would allow them to flash a custom recovery and pull the data off. This will be decrypted on the fly. So it works in conjunction with Encryption. To secure data from physical access, you need both.
IF your bootloader is unlocked and you have no password, you may aswell not be encrypted

Android Pay on rooted Mi Mix? Possible?

Hi Mi Mix fans!
Does anybody know how to run Android Pay on rooted Mi Mix?
I have tried Xposed + Rootcloak and it doesn't work...
Is there anybody who run Android Pay on Mi Mix with unlocked bootloader and root installed?
Even restore an app with the configured data doesn't work. After the app is started Android Pay clear the settings and want me to set up the payments cards again. Then after click on "Add card" it displays the message "You cannot run Andoid Pay on this device, because root...." etc. etc.
Any help will be very appreciated!
zencooler said:
Hi Mi Mix fans!
Does anybody know how to run Android Pay on rooted Mi Mix?
I have tried Xposed + Rootcloak and it doesn't work...
Is there anybody who run Android Pay on Mi Mix with unlocked bootloader and root installed?
Even restore an app with the configured data doesn't work. After the app is started Android Pay clear the settings and want me to set up the payments cards again. Then after click on "Add card" it displays the message "You cannot run Andoid Pay on this device, because root...." etc. etc.
Any help will be very appreciated!
Click to expand...
Click to collapse
until we get kernel sources and are able to patch the bootloader with SultanXDA's safetynet patch, no android pay on root
mlkemac said:
until we get kernel sources and are able to patch the bootloader with SultanXDA's safetynet patch, no android pay on root
Click to expand...
Click to collapse
Does SultanXDA also remove the other security requirements of android pay? Last I tried android pay it says, either I have unlocked bootloader, custom firmware or device is rooted.
Also, my company requires me to use MobileIron's suite of apps for email and such. It won't activate w/ Root and also usb debugging (WTF). If any of you guys are in IT and have the ability to recommend software, stay away from that POS.
Thorin78 said:
Does SultanXDA also remove the other security requirements of android pay? Last I tried android pay it says, either I have unlocked bootloader, custom firmware or device is rooted.
Also, my company requires me to use MobileIron's suite of apps for email and such. It won't activate w/ Root and also usb debugging (WTF). If any of you guys are in IT and have the ability to recommend software, stay away from that POS.
Click to expand...
Click to collapse
I think you would need to hide root as well with suhide or an equivalent.
the unlocked bootloader is the most important piece here, once that's done the rest is easy.
mlkemac said:
I think you would need to hide root as well with suhide or an equivalent.
the unlocked bootloader is the most important piece here, once that's done the rest is easy.
Click to expand...
Click to collapse
I'm hoping AOSP would come out sooner or later and then I would "relock" my bootloader if necessary.
mlkemac said:
until we get kernel sources and are able to patch the bootloader with SultanXDA's safetynet patch, no android pay on root
Click to expand...
Click to collapse
Thanks for the info. Seems it a bit long way ahead.
I come from Galaxy S7 where it wasn't an issue and I had unlocked bootloader with root, xposed etc. and fully working Android Pay...
Regards.
I have not unlocked or rooted yet and Android Pay is not available. Did it work before you unlocked?
gary.lavin said:
I have not unlocked or rooted yet and Android Pay is not available. Did it work before you unlocked?
Click to expand...
Click to collapse
Sure I read will on work on stable China ROM,
Not always though Google signed the stable ROM but not Dev.
I'm on China stable just tried it and said bootloader unlocked, which is true.
gary.lavin said:
I have not unlocked or rooted yet and Android Pay is not available. Did it work before you unlocked?
Click to expand...
Click to collapse
Unfortunately I didn't try before unlock and root so I'm not sure it worked before...
Can anybody confirm it was or wasn't working on locked bootloader, please?
Sent from my MIX using XDA Free mobile app
It doesn't even work on stock stable rom with locked bootloader lol
Leechoonhwee said:
It doesn't even work on stock stable rom with locked bootloader lol
Click to expand...
Click to collapse
Really??? How come???
zencooler said:
Really??? How come???
Click to expand...
Click to collapse
I dunno. Ask Google. It says either my phone is unlocked or rooted which is false. After that, I sort of gave up and just unlocked the bootloader and root the phone
Leechoonhwee said:
It doesn't even work on stock stable rom with locked bootloader lol
Click to expand...
Click to collapse
Did you check wasn't already unlocked. Even TWRP will stop it working, although I did read the last 2 stable ROM s it didn't work.
Leechoonhwee said:
I dunno. Ask Google. It says either my phone is unlocked or rooted which is false. After that, I sort of gave up and just unlocked the bootloader and root the phone
Click to expand...
Click to collapse
I had the exact same problem. it wasn't just google play. any NFC payment app would have the same or similar message
I got the phone with China stable rom, no root nor bootloader unlock. Android pay works fine.
Leechoonhwee said:
It doesn't even work on stock stable rom with locked bootloader lol
Click to expand...
Click to collapse
shinji21 said:
I got the phone with China stable rom, no root nor bootloader unlock. Android pay works fine.
Click to expand...
Click to collapse
Over on reddit, I was chatting with someone who was using Android Pay on his Mi Mix straight out the box but it was a vendor ROM. He flashed one of the official ROMs and it stopped working but that was because he'd unlocked his bootloader in the process.
After trial and error (and nearly bricking his phone), the conclusion was that it will work on the China Stable ROM, provided your bootloader is locked and you're not rooted.
I'm going to switch back to stable and re-lock my bootloader this weekend to see if it works for me.
Step666 said:
Over on reddit, I was chatting with someone who was using Android Pay on his Mi Mix straight out the box but it was a vendor ROM. He flashed one of the official ROMs and it stopped working but that was because he'd unlocked his bootloader in the process.
After trial and error (and nearly bricking his phone), the conclusion was that it will work on the China Stable ROM, provided your bootloader is locked and you're not rooted.
I'm going to switch back to stable and re-lock my bootloader this weekend to see if it works for me.
Click to expand...
Click to collapse
Thanks for a quick summary. Let us know if this check to relock bootloader and installation China ROM works.
Regards!
Sent from my MIX using XDA Free mobile app
I got a feeling that it works only when Google had approved of the rom. When I flash the china stable when I got my phone, it was newly updated and hence not approved by Google yet.
zencooler said:
Thanks for a quick summary. Let us know if this check to relock bootloader and installation China ROM works.
Click to expand...
Click to collapse
Seems to have worked - at least it let me set up a card etc.
Just need to use it to pay for something for 100% confirmation but I doubt it'll be an issue.
Downside is, I'd forgotten how China-y the Stable firmware is after using the Xiaomi.eu ROM.
OK, final update.
The app works on China Stable up to the point when you try to make a payment, that has never worked for me - it simply doesn't interact with the POS system.
Android Pay was about the only reason to go stock, IMO. Given it doesn't work, I'll probably switch back to Xiaomi.eu.

Categories

Resources