Develop Bugs

Android pay has stopped working

I had a Nexus 5X with stock Android 6 software. Android Pay was working fine.
I was having a few lag issues and noticed the final Nexus factory image was available for Android 7 so I decided to unlock my bootloader and install the factory image. After I installed it, Android Pay was still working fine.
Then I received an OTA update for the monthly security hotfixes which I installed. Since doing this, Android Pay doesn't work. It says something about my phone being rooted/unlocked and that Android Pay does not support this.
Can anyone tell me why this is happening? I don't need to keep my bootloader unlocked so if locking will allow me to resolve the issue without losing data then I can do this. Can anyone guide me please?

Try flashing a kernel from The Flash or Franco.
Both have a line of code that should stop the bootloader error in safetynet

Thank you but I don't want to put on any custom stuff. I just want to go back to a stock Android 7.0 ROM that works with Android Pay. I don't need root, or an unlocked bootloader. How can I go back to stock?

You can use something like wugs nexus tool.
Although some have mentioned you can brick your device trying to lock the bootloader.
Personally I have never done it. Others might have more experience.
It may or may not be easier to lock than to use a custom kernel. YMMV.
One benefit of the kernel is increased performance on your phone.
Oh and if you lock your bootloader it will completely wipe your phone. E.g. You will lose your data.
Edit.. Root isn't needed for a kernel either

Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Source: https://developers.google.com/android/nexus/images

Ah okay, thanks for the info. What I should have done originally was re-lock the bootloader straight after I flashed the ROM. Unfortunately, I setup the device after flashing the ROM and kept the bootloader unlocked which is why I'm stuck right now. Okay, time to backup my stuff up and re-lock the bootloader. Thanks everyone.

Phone formated and its asking for google account.

Hi,
My roommate has HTC 10 which was formatted by him last week. He don't remember the name/password of google account he used. Now, the phone is asking for google account when its started and he don't know what to do.
I though, I would flash it with new firmware and see how it goes, but I don't think it will work. I assume even after flashing new firmware, google account detail will be ask on phone start up.
so,
1. Is there anyway we could recover phone to normal operation? He has phone number he was using with but he is stupid enough not to remember other details of his google account on his phone.
2. Regarding flashing, the phone I believe is unlock (bought in Dubai), but I don't know if the phone is bootloader unlock or not. How can I check if the boot loader is lock or not? Is there anyway to unlock bootloder using fastboot/ADB?
3. what will happen if I flash custom rom on existing phone(which i'm sure is carrier unlock but not sure of bootloader status)? I want to install twrp first and try other ROM.
and lastly, for argument sake, if phone is locked(bootloader lock) and there is no way to unlock without login to google account in phone first and enabling bootloader unlock in developer option, can HTC support reflash the phone to unlock as new phone, so that he can continue using it?
I'd really appreciate help and suggestion on the topic

If it's full stock, boot to bootloader, then recovery and performance factory reset. Everything g will be deleted from the phone. It should work then, otherwise just unlock bootloader and flash TWRP and a custom rom
Also you can find everything In HTC 10 general forum. Like what to do and what is what and and and.
Sent from my HTC 10 using XDA Labs

I think that is the android "factory reset protection" which after reset it need to use the same account using before for verify ownership, I know samsung and LG have some bypass method but dunno about the HTC, may be flash a RUU may help.
anyway, here is a page to find the google account if you had phone number link to it: h**ps://accounts.google.com/signin/usernamerecovery?hl=en

DummyPLUG said:
I think that is the android "factory reset protection" which after reset it need to use the same account using before for verify ownership, I know samsung and LG have some bypass method but dunno about the HTC, may be flash a RUU may help.
anyway, here is a page to find the google account if you had phone number link to it: h**ps://accounts.google.com/signin/usernamerecovery?hl=en
Click to expand...
Click to collapse
yes i think it is the case. Its asking for google account after factory reset.
a n00biesh question, what exactly RUU is. Is it windows based tool like odin or some files to flash in fastboot.
My major concern is if it is possible to unlock the bootloader directly via fastboot without enabling "oem unlock" enable option in developer mode. I'm not familiar with HTC. I'm been using MI phones for past 4 years and i know how to handle MI phones.

naifdamudi said:
yes i think it is the case. Its asking for google account after factory reset.
a n00biesh question, what exactly RUU is. Is it windows based tool like odin or some files to flash in fastboot.
My major concern is if it is possible to unlock the bootloader directly via fastboot without enabling "oem unlock" enable option in developer mode. I'm not familiar with HTC. I'm been using MI phones for past 4 years and i know how to handle MI phones.
Click to expand...
Click to collapse
RUU is the rom update utility by HTC. unlocking without oem unlock from dev options won't work afaik. please check CID with fastboot getvar all and post it here, but don't post your IMEI. just the CID . if you have a compatible CID, for example WWE one then you can use the RUU for WWE to flash the phone completely new. maybe then you can bypass that protection.

Accidentally locked bootloader

Alright guys, I was trying to fix my fingerprint (which I ended up doing) by flashing the global dev ROM 7.8.31 via fastboot with the miflash tool but I accidentally locked the bootloader while doing so. My phone came with the bootloader unlocked and now I can no longer unlock the bootloader. in developper options, the OEM unlocking option is enabled but no matter what I do in fastboot, the process simply does not work. I get the remote token verification has failed message. I have tried every freakin guide out there but my phone now refuses to get unlocked. I can't flash anything with miflash tool anymore, it just says failed, even when trying to flash the global dev 7.8.31 ROM. Anyone can help me here? Xiaomi says my device is unsupported for unlocking yet it was unlocked from the start........

What i did was the official unlock guide from xiaomi where you will get the code from them. Sadly you have to wait for 3days to be able to unlock them again.

Well check this thread...
en.miui.com/thread-781303-1-1.html
You can reapply if you got rejected

blaspheme000 said:
What i did was the official unlock guide from xiaomi where you will get the code from them. Sadly you have to wait for 3days to be able to unlock them again.
Click to expand...
Click to collapse
Well I did that but it kept on saying I had too many IP requests of sorts but I used TunnelBear and set my location to Hong Kong and that allowed me to bypass that and the request was passed through. Surprisingly, I got a message 4 hours later that said I was able to unlock it instead of the 2-7 days it took for most people to get theirs

Same happened to me. I re-lock bootloader to install android pay, and bricked my phone.
Have to reboot in EDL mode (after >50 tries) and flash again.
But... Flashed a locked bootloader version, so i have to request for official unlock (phone came unlocked)
Now I have unlocked bootloader, with Magisk and Safety Net module with Android Pay working fine.
PS: i also had the IP problem. Used a Chinese proxy to override restriction.

Confused About Bootloader And Unlocking? Is mine outdated?

Ok so I was reading an article and now I'm confused. I see there are two ways to unlock a phone...the regular unlock command and an unlock critical command. From what I understand the unlock critical command is for updating the bootloader? When would I want to do this? I was on the Android P final beta and because official Pie release was delayed here in Canada I decided to just unlock and flash Pie manually. I did this and then relocked the bootloader. But is my bootloader outdated now? Confused. ?

If you keep the bootloader unlocked your bootloader will never go out of date, otherwise the bootloader will not be updated on subsequent stock ROM updates. I personally recommend unlocking the bootloader using both commands and keeping it unlocked. You'll have a minor annoyance in that you'll have a warning pop up prior to boot about the bootloader being unlocked, but I believe avoid a major annoyance in Factory Reset Protection being disabled with the bootloader unlock.

Ok. So just unlock using both commands? Do I just enter in right after the other? How does the bootloader get updated?

Also does leaving the bootloader unlocked stop Google Pay and some banking apps from working?

Enter both commands, one after the other. The bootloader, even if it has no updates, is included with every copy of the stock ROM you download from Google. It will also be included with any OTAs that come directly to the device. You'll have to discover for yourself whether Google Pay and your banking app are affected, because I simply do not know. I don't use my device for banking.

Question Carrier ROM not updating since miui 12.5.5. Is there anything I can do to fix this?

Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks

rockyrobin said:
Hi, my carrier purchased 'Lisa' came with its ROM showing as version RKOEUBY.
My carrier isn't keeping up with updates so was wondering if I can just flash the ROM RKOEUXM without unlocking the bootloader?
I have my banking apps etc on this phone so am reluctant to unlock the bootloader unless absolutely necessary.
If anyone else has found an easy way to solve this would be grateful for your feedback.
Many thanks
Click to expand...
Click to collapse
Hi !
The best way is to download the zip of your European ROM from the Xiaomi site and try to install it from the update utility in your phone's settings. If that doesn't work, you'll have to unlock your bootloader, install the ROM you want with the flash utility, and choose the relock option before the install starts. Then you will be on an official Xiaomi ROM, with your bootloader locked and you will have updates from Xiaomi and no longer from your operator.
Bill

Hi,
I confirm that manually flashing the European ROM does not work (in my case at least), so I am stuck on MIUI 12.5.6 with RKOEUSF ROM.
If anyone finds a way to upgrade to the official version without unlocking the bootloader, and therefore not breaking the warranty, I would be grateful if you could share it.
Thanks

Hi !
From the moment you want to install a new ROM, you have no choice but to unlock your bootloader. You can then reblock it. Afterwards, I don't know if the warranty is impacted because you go through the official unlocking from Xiaomi.
Bill

Thanks Bill,
I've just tried flashing the zip of my ROM and the phone just quits the update after a long pause, saying that it cannot verify update.
Guess I'll have to unlock the bootloader. There's plenty of info about how to do this, but I've noticed a number of people complaining about the flash process.
When they apply the update, at the end they get an error message. The only way they get round this is with an edit of the settings of miflash.
Is this something I need to worry about?

Just been reading about these errors and it appears that they are caused by the path to the ROM file having too many characters.
Placing the ROM file in your C: folder solves this.