Develop Bugs

MT7-TL10 Bootloader Unlocked BUT STILL LOCKED

Calling all the Huawei Experts to help me out on this!!
Short Summary of problem
On my Ascend Mate 7 MT7-TL10 (running Android 5.1.1 version B326) -The bootloader shows as unlocked but I still can't flash a custom recovery - It gives error 'FAILED (remote: image verification error)'. I am using the lastest version of ADB/Fastboot, I have USB drivers installed and I also have the Bootloader Unlock code from Huawei, which works and shows 'Done'
Please read the details below first and kindly see all attachments
Click to expand...
Click to collapse
Little bit more information
- On the Bootloader screen of my MT7-TL10 (Gold 32 GB, 3 GB RAM version), I see "Phone Unlocked" in red, which means that my bootloader is unlocked. (refer to attachment)
- When I run the command 'Fastboot OEM get-bootinfo', it returns 'UNLOCKED'.
- However, whenever I try to flash a custom recovery, it gives me an error 'FAILED: (remote: image verification error).
- At the same time, if I flash stock recovery, it is successful.
Detailed Information
- When I run the command 'fastboot oem get-bootinfo' it returns 'UNLOCKED'.
- However, when I run the command 'fastboot oem get-lockstate', it returns 'Locked'
- I rolled back to KitKat 4.4.2 - But the process of roll-back to KitKat 4.4.2 was not as simple as it was described in many forums and I first ended up soft-bricking the device
- I followed the restore process described on Huawei's website and ended up flashing a chinese ROM (JAZZ) on my MT7-TL10 and there were plethora of chinese apps
- Then, I unlocked the bootloader using (fastboot oem unlock <unlock code>) and on KitKat, both commands 'fastboot oem get-bootinfo' and 'fastboot oem get-lockstate' returned 'UNLOCKED' (Hurray!, That's what I thought but...)
- Realizing that the bootloader was finally unlocked, with the help of @acbka, I was finally able to restore Lollipop (version 5.1.1 - B326) and to my utter disgust, after upgrading, I found out that I was again not able to flash a custom ROM - On Lollipop, the command 'fastboot oem get-lockstate' again returned 'LOCKED' and the command 'fastboot oem get-bootinfo' returned 'UNLOCKED'
- As you can see, I was back to square 1 and I still can't unlock the bootloader and therefore, I cannot root my phone
Final statement
- When I rolled back to KitKat, the Bootloader showed as Unlocked and I was able to flash custom recovery TWRP
- After upgrading to Lollipop (5.1.1 B324 and B326), I am unable to flash custom recovery (somehow, the bootloader shows as 'Locked' when I run 'fastboot oem get-lockstate')
- If I flash stock recovery, it is successful
- The error 'FAILED (remote: image verification error)' implies that the bootloader is locked and that's why it forbids flashing of custom recovery BUT it allows flashing stock recovery
Please see the attached pictures, which will show what I mean.
I will really appreciate any help to enable me to flash a custom recovery!! Please help!

i also face the same problem any one can help us ?

try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984

Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk

prahastaabenk said:
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Click to expand...
Click to collapse
kingrk said:
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Edit: The link that you posted is not dead - it didn't open on my smartphone. The author of that post ACBKA helped me and we both tried it but could not beat the bootloader. While it shows that it is unlocked, it is still restrictive and doesn't allow flashing of custom recovery.

awzx_77 said:
i also face the same problem any one can help us ?
Click to expand...
Click to collapse
I have an idea!
I remember that when I was troubleshooting the problem (my smartphone was soft-bricked when I tried to rollback to KitKat and I ended up flashing Chinese 'Jazz' version on my TL10), I had realized that the bootloader was FULLY UNLOCKED on the chinese Jazz ROM and I could actually install a custom recovery. So, here is the idea:
a) First roll back to KitKat 4.4.2 --> I believe that there is a procedure on XDA to roll-back to KitKat
b) Change the phone's location to China
c) Install custom recovery and root phone by flashing superuser
d) Upgrade to Lollipop 5.1.1 (Chinese version)
e) Upgrade to Marshmallow beta (Chinese version)
f) Install custom recovery and root phone

same problem
just unlock the bootloader again using unlock code!
it worked for me

+1 for @xAghilx. Same here.

Bricked Pixel C?

Hi all,
I recently picked up a new Pixel and was wanting to flash it. I ended up enabling USB debugging and set OEM unlock within Android settings.
Yet when I use fastboot flashing unlock, it keeps telling me that OEM unlock isn't set. In my haste, I ran flash-all with a new Google build and this overwrote the existing ROM, but left the bootloader intact it seems. Now when I boot, it says I have a damaged OS and I should use recovery. The problem is that even recovery is damaged and it keeps rebooting to the bootloader. So adb won't work either. The only thing that works is fastboot.
Is there anything I can do to fix this or is it completely bricked? I can't seem to use fastboot to flash any ROM to the device - keeps erroring. I tried to match a ROM with the bootloader but that didn't work either.
Any ideas?

I used Nexus Root Toolkit when I got semi-bricked.

Use erase Command on flashboot for data and system then do flash_all again

As was mentioned, if you have fastboot you are ok. You can flash as mentioned above or use this -
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78

NRT is good for people like me who barely know what they're doing, enough to get bricked in the first place like I did. What i like is that it takes away a little of the uncertainty about whether I'm using the right files.
I hadn't rooted and unlocked and done all the setup in about a year so I forgot everything.
Save yourself some trouble and look at the "TWRP bootloops" thread. It's easy to avoid if you follow some specific steps, frustrating otherwise.

Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)

hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...

hamazoza said:
Thanks all, but will this even work, given that the bootloader is still locked? I have no way of unlocking it via any fastboot commands. That's why I am completely stuck.
Will NRT do that somehow in a way that fastboot can't? If so, I'll go find a windows machine from somewhere (who still uses Windows!?)
Click to expand...
Click to collapse
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!

d j a said:
Yes, you can unlock bootloader from fastboot.
Um...
fastboot oem unlock
Learn fastboot. It's your friend!
btw, you don't need it unlocked to flash the stock image!
Click to expand...
Click to collapse
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.

cam30era said:
Won't work IF bootloader is still locked. Try this command > fastboot continue
That will work with locked bootloader, but not sure if it'll solve your problem. Nothing to loose by trying...
Click to expand...
Click to collapse
Yeah didn't think NRT would work because of the locked bootloader! Fastboot continue just gets out of fastboot - what is that gonna solve? I have a damaged set of partitions it seems - going from bootloader -> recovery boots back to the bootloader so it's clear that partition is damaged.
Is there any way I can just push some build to rebuild the partitions or can I do absolutely nothing until the bootloader is unlocked. And if so, how on earth can i unlock it if the only thing that works is fastboot?

hamazoza said:
Um...no You missed what I wrote in the first post - oem unlock (actually flashing unlock) doesn't work.
So how on earth do i flash the original image - I've tried to do that multiple times and it always fails.
Click to expand...
Click to collapse
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip

d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
I'll try that tonight. FWIW, I know I copied the line from flash-all to just flash recovery.img and even the system image, and both failed.
The only difference I see between that and yours is you have '-w update'. Maybe that's the trick.

d j a said:
Try this.
https://forum.xda-developers.com/showpost.php?p=70611434&postcount=78
You'll need to extract the system image and flash that.
fastboot -w update image-ryu-n4f26i.zip
Click to expand...
Click to collapse
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"

hamazoza said:
So I tried that...no luck...it created the partitions and at the end, I get this error:
"erasing 'boot'...
FAILED (remote: unsupported command)
"
Click to expand...
Click to collapse
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106

d j a said:
Try the SkipSoft tool. You can download and flash the entire stock image using that and FASTBOOT.
https://forum.xda-developers.com/pi...tool-skipsoft-android-toolkit-google-t3277106
Click to expand...
Click to collapse
I don't think that'll work. OEM unlock wasn't set in developer settings.

hamazoza said:
I don't think that'll work. OEM unlock wasn't set in developer settings.
Click to expand...
Click to collapse
You don't need that. I actually unlocked mine without it. The tool also has a unlock feature. Its worth a try.

Look for this forum post: flashing to stock android npd90g twrp t3424863
This helped me too. Only difference is I had TWRP installed.
Try unlocking bootloader via termjnal, then use the fastboot command via terminal (pc) fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable fastboot, then erase the partitions manually as mentioned in the tutorial and reflash them either manually or together using skipsoft / nrt or manual commands and a factory image.
Normally there should not be anything wrong with your bootloader image since modifying it is disabled for bootloader locked devices. Let us know about your progress.
Oh, also never flash an older system image than your current one.

Your device is corrupt. It can't be trusted and will not boot

Hi friends
Please give me suggestion or guide how to solve problem about handset booting after mistakenly handset OEM locked through fastboot
It enter to fastboot mode but not going to recovery mode or restart in system mode
Is there any solution
If yes then please help me

fastboot oem unlock ?

Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed

This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Edit: Just noticed the part about your device will not boot. You need to find the system image and flash it. I read somewhere today that OnePlus just released the system image for 4.7.4.

Can you unlock again?

@op, IMHO the best possible solution will be to flash stock rom image and stock recovery if required but I think when you flash stock image it will also flash stock recovery.

When you turn off the phone and boot it with VOLUME UP plus POWER, this should send you straight away to Fastboot. Try if you can unlock again, otherwise... bad luck - you'll need a restore session with 1+.

the Doctor said:
This happens because your bootloader has been unlocked at one time. There is no going back, even if you use "fastboot oem lock" later.
Click to expand...
Click to collapse
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!

jonsat said:
Not to be unrespectful, but you're wrong, it is absolutely possible to relock bootloader without problems.
IMHO, trouble happened because he had a custom rom onboard... and a locked bootloader does exactly its purpose... to not boot insecure firmware!
Click to expand...
Click to collapse
After looking into it further, I agree with you. That's what I get for having a bootloader-locked Samsung device for two years. I must be getting rusty!
Yes, the bootloader can be re-locked. There may still be a tamper flag as with previous OnePlus devices. But having a locked bootloader with non-OEM software would likely cause the problem he is describing. So, he needs to flash the factory image from bootloader.

I've requested to 1+support for restore remote session
Support send me file link and l2 will assist me in within 2 days

DO NOT RELOCK BOOTLOADER UNLESS U READ UP FIRST!!!!!, its worth just waiting the few seconds after reboot, then to go and try to relock the bootloader

I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.

kaihansen2001 said:
Can you unlock again?
Click to expand...
Click to collapse
Yes ive unlock Bootloader

Rdxsammm said:
I've restored oneplus 5t through remote session
it become as company new mobile
After that OEM also unlock
Thanks oneplus supports.
Click to expand...
Click to collapse
How did you do it? can you guide me too?

sam razzy said:
How did you do it? can you guide me too?
Click to expand...
Click to collapse
Have you dumpling files and MSM download tools for oneplus 5t
If you have then restore op5t after success it work as new mobile.
But you can get basic dumpling file from oneplus support remote session.
You have to create ticket and chat with oneplus support

oneplus 5 device corrupt and it cant be trusted and will not bootr

hrushi0130 said:
oneplus 5 device corrupt and it cant be trusted and will not bootr
Click to expand...
Click to collapse
Did you by any chance re-lock the bootloader with a custom recovery and custom ROM flashed?

It's because of custom recovery.
Just flash stock recovery image before locking the bootloader.
This fixed for me.

Rdxsammm said:
Actually ive unlocked OEM and install twrp recovery and installed freedom os
Then while checking OEM status ive enter command fastboot OEM lock
It ask me I've pressed yes after that the massage is came after restart as your device is corrupt it can't be trusted and will not boot
After that it enter to fastboot but not going to recovery mode or system
While type command in fastboot OEM unlock massege come failed
Click to expand...
Click to collapse
You unlocked bootloader, flashed rom (custom) and relocked bootloader? Never lock your bootloader on a custom rom! Just enter fastboot again flash twrp (manual/force reboot recovery), copy internal storage to pc then wipe/format everything. Format data. Factory reset then flash latest official rom and reboot

OEM Locked, and Device is corrupt. Unfixable?

So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.

kschmitz4 said:
So, long story short I recently decided to try and root my oneplus7t I unfortunately made some mistakes and somehow corrupted some files. I read elsewhere in the forum that I could download the stock rom which I did and then use flash-all and that would allow me to go back to the factory settings so I could lock the oem and just go back to normal because I was tired of the headache. Unfortunately, after using flash-all I locked the oem thinking everything should be stock and it would work properly. But it says device is corrupt and trying to unlock the oem says oem unlocking is disabled.
So did I just completely brick my phone? I don't know of anyway to fix it at this point :/.
Click to expand...
Click to collapse
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.

Josh McGrath said:
Can you still boot into bootloader via the hardware keys, whatever that combo is on the 7t?
Boot to bootloader or recovery and factory reset it or so.
Click to expand...
Click to collapse
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.

kschmitz4 said:
I can get to the bootloader but it's Device State -locked and when I tell it to boot into recovery it says the device is corrupt. When I use fastboot to oem unlock it says I cannot, and I can't flash when oem is locked either.
Click to expand...
Click to collapse
Try
fastboot erase userdata and
Fastboot erase cache
Let me know if that works or not we will move on. Probably won't work since it's bootloader locked
You may have to contact OP and while you're at it, get the MSM tool for us all :good:

It says erase is not allowed in locked state . I think this is probably all she wrote for this one. I think I'm just going to send it back tbh, the whole reason I was trying to root it was because it didn't work with Sprint like they said it would. and I was wondering if I could find a way too make it work with custom software. Thanks for trying

Are you able to flash one of these Fastboot ROMs?

Maybe Sideload can work!
https://support.oneplus.com/app/answers/detail/a_id/4583/kw/7t here is official stock file.
https://forums.oneplus.com/threads/how-to-do-flash-through-adb-sideload.509377/
https://www.the***********.com/sideload-ota-update-stock-recovery-adb/
Please refer above links for your knowledge purpose maybe it can help.....

I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.

kschmitz4 said:
I unfortunately no longer have Twrp installed as I did a flash-all with a stock rom already . If I try and flash recovery it says "flashing is not alllowed in lock state". Sideloading wasn't functional back when I had twrp either as the functionality for it is still in progress. I'll probably try contacting support one more time and see if I can get a T2 who can unbrick it, otherwise I'm just going to send it back. Thanks for the attempts guys!
Edit: As to the flashboot roms I flash-all'ed one of them and that's how I got into this mess :/.
Click to expand...
Click to collapse
I ended up needing to flash the fastboot 10.0.3 firmware and was able to do a local upgrade to 10.0.4 that way, then flashing a patched boot.img via fastboot

I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?

kschmitz4 said:
I can't run any flash commands as my oem is locked. I don't suppose there's anyway around that?
Click to expand...
Click to collapse
How did you flash twrp with it oem locked??That doesnt make sense

I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.

kschmitz4 said:
I had twrp on it when the oem was unlocked, I was trying to reset the device to stock, so I did a flash-all and then oem locked it. But for some reason the repair was unsuccessful, and now it says my device is corrupted and I forgot to turn on oem unlocking in the settings on my phone after the flash-all before I did the oem-lock.
Click to expand...
Click to collapse
You should have no issues reflashing the stock images

I cannot flash anything. Because my OEM state is locked.

Boot to Stock Recovery ?
Holding for a long time Volume Down + Power Buttons while booting your phone ?

Volume down plus power button takes me to "Your device is corrupt and will not boot"

kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Looks like you will need the MSM tool to fix this issue. You'll have to contact OP support and they will remote in your PC, load their software and flash it 100pct back to stock.
Also, disconnect them before they can delete the MSM tool so we can have it here in the community

kschmitz4 said:
Volume down plus power button takes me to "Your device is corrupt and will not boot"
Click to expand...
Click to collapse
Press volume up/down and power, reboot to fastboot. Unlock bootloader again. Install update from settings, reboot and install it again. (local install)
Factory reset in setting, reboot fastboot, lock bootloader. Reboot and untick unlock bootloader in developer settings.

Don't know if it's too late but I believe there's a working MSM tool now

Question Unable to lock the bootloader

Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?

If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.

wrkadung said:
If your phone was rooted, then do a factory reset. Download and install the Google Platform tools, or if adb and fastboot drivers are installed system-wide, that's fine.
Connect phone to PC in fastboot mode
Enter the first command "fastboot devices"
Then type, "fastboot flashing unlock"
Confirm on your device to lock the bootloader
That's it. If you want a detailed guide, here are the instructions on how to unlock/relock the bootloader on a Pixel phone.
Click to expand...
Click to collapse
Locking with adb will erase all my data?

max_134 said:
Locking with adb will erase all my data?
Click to expand...
Click to collapse
Yes, of course! Unlocking and relocking will erase and factory reset your phone, I use Google One to take backups.

Alternatively, you can also use the Android flash tool, and it will automatically do it for you. You just have to follow the on-screen instructions, and it will ask for your confirmation to lock the bootloader, and you also get the option to wipe data (never tried unchecking the wipe data option).
Here is the video tutorial, if you need it.

EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...

max_134 said:
Week ago I flashed the android 14 dev, don't liked it and yesterday flashed A13 (TQ1A.230205.002) with Android Flash Tool. Today I saw that I can't add my credit card to the Google Pay. I checked in settings and found out that my bootloader unlocked but the button is unavailable.
What can I do?
Click to expand...
Click to collapse
Google pay will work with an unlocked bootloader.

simplepinoi177 said:
EDIT: apologies for covering much of what has already been discussed by @wrkadung, got ninja'd a bit there...
I wouldn't risk locking the bootloader via platform-tools....so many instances from all the way back from the original Pixel has had countless members hard-brick their Pixel's relocking the bootloader.
The safest way to go about it is to use the Android Flash Tool to flash both slots and relock bootloader; most hard bricks happen when it's not flashed to both slots and/or the improper factory image is used...
But the OEM unlocking being greyed out is sometimes SOP after unlocking the bootloader. It's not really anything to be concerned about. If Wallet isn't working properly, it is doubtful it is simply having the unlocked bootloader; Wallet usually doesn't work when rooted than it is the fact of an unlocked bootloader. You should try Force Stop-ing and Clear Data Wallet first. Then even "uninstall updates" and/or revert to an older version before locking the bootloader. ESPECIALLY if you don't wish to wipe the device by relocking the bootloader...
Click to expand...
Click to collapse
Yes, definitely, a stock factory image is required. Most people directly lock the bootloader on a rooted phone using adb & fastboot commands, which results in bricking the phone.
On stock firmware, it is working perfectly. Right now I am working on a video tutorial for Pixel 7 and it worked fine without any issues, it was just bootloader unlocked device (not rooted).