Database Info

OEM Unlocking issue [SOLVED]

I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.

Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170

depii said:
Do you use "fastboot flashing unlock_bootloader"? Do you have actual platform-tools?
# fastboot --version
fastboot version 27.0.0-4455170
Click to expand...
Click to collapse
Once it boots into fastboot, I enter "fastboot flashing unlock"
I have that same version of fastboot.

Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?

depii said:
Is "Device State" locked or unlocked on bootloader screen? In Developer Options > OEM Unlocking for me is a second line with text: "bootloader already unlocked". What is yours?
Edit: Did you enable OEM Unlocking before fastboot flashing unlock?
Click to expand...
Click to collapse
Device state is locked
There's nothing under OEM unlocking saying that the bootloader is already unlocked.
Yes, I have enabled unlocking before booting into fastboot. I've done it five times now.
What's odd is if I use the unlock_critical command, I get "FAILED (remote: Device already : unlocked!)"

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?

rohanhole said:
Facing the same issue in INDIA. Are you sure RMA is the only option ? I was hoping for Jan 2018 Security patch ! Worth to wait or RMA ?
Click to expand...
Click to collapse
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.

geicogecko said:
Nothing I did fixed the problem. You can keep fighting with it and hope it eventually works, and possibly end up with a permanently locked bootloader.
Click to expand...
Click to collapse
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.

rohanhole said:
Could you tell me 2nd RMA'd device which one you able to unlock was on 8.0 or did you update OTA and then unlocked ?
Click to expand...
Click to collapse
I first updated to 8.1 OTA, then unlocked.
rohanhole said:
Hello All ,
I have succefully unlocked the bootloader with following command !!!!!! Pixel 2 128 GB
C:\platform-tools>fastboot flashing lock_critical
...
OKAY [ 9.054s]
finished. total time: 9.056s
I dont know but after reading latest post on XDA and other Android related tech sites ,
I performed the above command and it worked for me ! I was about to RMA but this is what i wanted ! so no need to RMA now.
Again not to confuse with VERIZON variant , as my device was Google store unlocked In INDIA ! Strange but worked.
Click to expand...
Click to collapse
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
Read the other threads or check the xda news portal. This command actually unlocks the pixel 2 not XL variant.

geicogecko said:
I first updated to 8.1 OTA, then unlocked.
That command locks the bootloader, not unlocks. The unlock command is "fastboot flashing unlock". Critical is only needed for the Pixel 2 XL.
Click to expand...
Click to collapse
I really don't have any clue why it worked ! After reading latest post I executed the above command in leap of faith and it really worked ! Finally unlocked bootloader on pixel 2 128 Gb. But its strange as I don't have Verizon model , as I purchased the device from official google store in India ( flipkart.com )
Here is the XDA post : https://www.xda-developers.com/verizon-google-pixel-2-bootloader-unlock/

geicogecko said:
I'm trying to unlock my bootloader to root the phone. I can enable OEM Unlocking in the dev options. Then, once I connect the phone in fastboot mode and enter the unlocking command, I get the not allowed message. When I reboot the phone, the OEM Unlocking option is now disabled and greyed out.
I've factory reset at least three times, as well as updating to 8.1.
Edit: I tried every which way to unlock it. I tried a factory reset with a SIM. I tried doing the reset in recovery mode. I tried running the cmd prompt as administrator. I tried restarting after the factory reset. About the only thing I didn't try is a different cable since I have no adapters yet, but that shouldn't matter since it's correctly receiving the commands.
I contacted Google and am RMA'ing this phone and have ordered a new one. Hopefully the new one works.
2nd edit: The new phone works. Bootloader unlocked on the first try and am now rooted. One thing I noticed with the first phone is that the bootloader unlock permission toggle was set to on whenever I wiped or rebooted.
If you are having this problem, the only solution is to RMA for a new phone.
Click to expand...
Click to collapse
SkipSoft Download Page | SkipSoft.net
skipsoft.net

Newest Global Stable Rom: V9.5.18.0.ODGMIFA

The global stable which is floating around is very old, so here's a newer one.
http://bigota.d.miui.com/V9.5.18.0.ODGMIFA/miui_MIMIX2SGlobal_V9.5.18.0.ODGMIFA_a9e31fa04c_8.0.zip
It might be possible to update to this if you are on older global stable.
Nightly builds are also updated at:
https://funkyhuawei.club/mimix2builds
We have up to May 8 builds now.
I will add stable builds there in the future as well.

Thanks a lot. Is it a fastboot rom?

underlines said:
Thanks a lot. Is it a fastboot rom?
Click to expand...
Click to collapse
Not a fastboot rom. Regular OTA zip.

Cool thx!
Could you please provide fastboot ROM version as well?

duraaraa said:
Not a fastboot rom. Regular OTA zip.
Click to expand...
Click to collapse
Hmm do you know if this is flashable within the updater when we have a locked bootloader on the chinese stable (8gb variant)?

underlines said:
Hmm do you know if this is flashable within the updater when we have a locked bootloader on the chinese stable (8gb variant)?
Click to expand...
Click to collapse
It's not. It fails due to region mismatch. It might work if you have an original global phone, but not on Chinese.
For Chinese, only hope of switching to global is unlocking the bootloader.

Just FYI, you can't install it through Updater app as this update is a beta update. Flash it manually with TWRP.
Edit. At least that's what Updater app tells me, I'm on v9.5.4.0 Global.

duraaraa said:
It's not. It fails due to region mismatch. It might work if you have an original global phone, but not on Chinese.
For Chinese, only hope of switching to global is unlocking the bootloader.
Click to expand...
Click to collapse
Thanks for that insight.
I am really pissed at Xiaomi: I am a 5 year Gold user in their forum and once even was a beta tester and admin there, in the Galaxy Note 1 + MIUI days.
When I bought the Mi Mix 2S 8GB variant last Sunday, I logged in with my MI Account, which has unlock permissions since 2 years and I was able to unlock any new Xiaomi phone I ever bought immediately without waiting for confirmation SMS anymore (as the Unlocking permission is on account level, not device level).
Then I enabled Developer Mode and went into "Mi Unlock status" to press "Add account and device". After that I started the unlocker application as usual and tried to unlock, which failed. with the message "Wait 360 hours" which is over 10 days! Damn...
Later I checked the developer settings again and saw another thing "OEM unlocking" which is set to OFF.
TLDR; Do you know if we have to set this to ON as well, before starting the unlocking process?

underlines said:
Thanks for that insight.
I am really pissed at Xiaomi: I am a 5 year Gold user in their forum and once even was a beta tester and admin there, in the Galaxy Note 1 + MIUI days.
When I bought the Mi Mix 2S 8GB variant last Sunday, I logged in with my MI Account, which has unlock permissions since 2 years and I was able to unlock any new Xiaomi phone I ever bought immediately without waiting for confirmation SMS anymore (as the Unlocking permission is on account level, not device level).
Then I enabled Developer Mode and went into "Mi Unlock status" to press "Add account and device". After that I started the unlocker application as usual and tried to unlock, which failed. with the message "Wait 360 hours" which is over 10 days! Damn...
Later I checked the developer settings again and saw another thing "OEM unlocking" which is set to OFF.
TLDR; Do you know if we have to set this to ON as well, before starting the unlocking process?
Click to expand...
Click to collapse
I set it to on before trying to unlock and my device was unlocked immediately. I'm a Diamond member and was a beta tester in 2017 though so I'm not sure if that makes any difference

underlines said:
Thanks for that insight.
I am really pissed at Xiaomi: I am a 5 year Gold user in their forum and once even was a beta tester and admin there, in the Galaxy Note 1 + MIUI days.
When I bought the Mi Mix 2S 8GB variant last Sunday, I logged in with my MI Account, which has unlock permissions since 2 years and I was able to unlock any new Xiaomi phone I ever bought immediately without waiting for confirmation SMS anymore (as the Unlocking permission is on account level, not device level).
Then I enabled Developer Mode and went into "Mi Unlock status" to press "Add account and device". After that I started the unlocker application as usual and tried to unlock, which failed. with the message "Wait 360 hours" which is over 10 days! Damn...
Later I checked the developer settings again and saw another thing "OEM unlocking" which is set to OFF.
TLDR; Do you know if we have to set this to ON as well, before starting the unlocking process?
Click to expand...
Click to collapse
From my experience yes, you have to switch it on. I'm pissed off as well, got the device mid-April and got it usable only a week ago on the 3rd of May, as 360h is a heckin' 15 days. Gotta think twice before buying anything Xiaomi again, though Mix 2S is beyond amazing thus far <3

skw5115 said:
I set it to on before trying to unlock and my device was unlocked immediately. I'm a Diamond member and was a beta tester in 2017 though so I'm not sure if that makes any difference
Click to expand...
Click to collapse
Can I borrow your account and unlock mine? I've still got to wait 10 days

duraaraa said:
Can I borrow your account and unlock mine? I've still got to wait 10 days
Click to expand...
Click to collapse
I think that would be theoretically possible:
Set your device's MI Account to an account that already has unlock permissions.
In developer options add the device for unlock permissions.
In developer options turn on OEM unlock.
Unlock.
But never tried. I'm sure xiaomi is banning accounts that unlock too many devices, because thats how they prevent resellers from buying chinese devices and flashing the global rom in big quantities.

underlines said:
I think that would be theoretically possible:
Set your device's MI Account to an account that already has unlock permissions.
In developer options add the device for unlock permissions.
In developer options turn on OEM unlock.
Unlock.
But never tried. I'm sure xiaomi is banning accounts that unlock too many devices, because thats how they prevent resellers from buying chinese devices and flashing the global rom in big quantities.
Click to expand...
Click to collapse
Chinese resellers, generally, have been using EDL to flash the global rom without touching the bootloader. But it seems not possible with Mi Mix 2S. I think they're trying to prevent resellers from installing compromised custom ROMs, which is fine, but 15 days is still a long wait.
My account also allows unlocking, but not instantly it would seem, as I got the 15 day wait. I don't have any kind of special account, but I've had it for a long time.
On the Mi Mix 2, I had a 72 hour wait, which I didn't really mind. But 360 hours is a long time!
Anyway, theoretically, if someone offered me their account which can unlock the phone instantly, it would be a gamble. If it turns out it doesn't work to unlock the phone instantly, I think my wait would get reset to 360 hours again.

any news about root?it's working correctly by flash magisk from polaris recovery?

underlines said:
Thanks for that insight.
I am really pissed at Xiaomi: I am a 5 year Gold user in their forum and once even was a beta tester and admin there, in the Galaxy Note 1 + MIUI days.
When I bought the Mi Mix 2S 8GB variant last Sunday, I logged in with my MI Account, which has unlock permissions since 2 years and I was able to unlock any new Xiaomi phone I ever bought immediately without waiting for confirmation SMS anymore (as the Unlocking permission is on account level, not device level).
Then I enabled Developer Mode and went into "Mi Unlock status" to press "Add account and device". After that I started the unlocker application as usual and tried to unlock, which failed. with the message "Wait 360 hours" which is over 10 days! Damn...
Later I checked the developer settings again and saw another thing "OEM unlocking" which is set to OFF.
TLDR; Do you know if we have to set this to ON as well, before starting the unlocking process?
Click to expand...
Click to collapse
I can confirm to you, that having that option set to ON, in developer options, the result is the same...i got an "WAIT 360 Hours" too.
Got my message text last Sunday, granted me to unlock the device, then when i logged into my Mi Account to unlock it, gave me that message...so, got to wait 360 hours.

When i flash a global rom, is the bootloader still unlocked? Have the china version with unlocked bootloader and xiaomi.eu rom at the moment.

tasar said:
When i flash a global rom, is the bootloader still unlocked? Have the china version with unlocked bootloader and xiaomi.eu rom at the moment.
Click to expand...
Click to collapse
Yes, your bootloader won't relock again and if you relock it you can unlock it instantly again without waiting the 360h.

@duraaraa
Can you find fastboot ROM version of it? That would be highly appreciated.

graw2 said:
@duraaraa
Can you find fastboot ROM version of it? That would be highly appreciated.
Click to expand...
Click to collapse
I'm impressed with the difficulty to release a fastboot version for the Global Rom.

For every build has fastboot version on bigota servers but more difficult to find them than the recovery version
Sent from my MI 5 using Tapatalk

Google Pixel 2 (July Update non Verizon) OEM unlocking issues.

The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.

After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?

Jomama22 said:
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
Try: fastboot oem unlock
Definitely a weird issue. Are you on Verizon’s network?
Edit: were you connected to the internet when you did the oem unlock in the developers options?
Edit 2: you have usb debugging enabled yeah?
Click to expand...
Click to collapse
After factory image, did you reinstall the update? Maybe make sure the update has been completed in total (takes 2 reboots sometimes).
I did not, I assumed that since it is the latest factory image, I did not needed to update, will try this ASAP.
USB Debugging is enabled.
I was connected to the internet when I did the OEM Unlock under developer options, I tried both connected and not connected to the internet. I tried to change the boot partition using fastboot and it does not allow to do so when in "locked" mode.
oem unlock returns that it is unable to be unlocked. (Sorry, not home now, but will post the actual error when I get back)

I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.

keanon said:
I am experiencing this issue also. I'm on my 2nd RMA device. The specific error I get after typing
Code:
fastboot flashing unlock
is
Code:
FAILED (remote: Flashing Unlock is not allowed)
Any help is appreciated.
Click to expand...
Click to collapse
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.

plgonzalezrx8 said:
That is in fact the error I'm getting. I had the OG Pixel and the Pixel 2 rooted since the day they came out and never had a problem, and now with this RMA replacement, I'm having problems, but IDK what could be the cause because with a fresh factory reset, I can at least see the "OEM Unlock" under developer options, so I'm so confused.
Click to expand...
Click to collapse
My OEM Unlock option will "take" when I click it, but it's disabled again when I reboot.

If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.

lightningdude said:
If they're RMA replacements, there's a possibility you got a Verizon Pixel 2 instead of a Google. This happened to me as well, I just traded for my wife's Pixel 2, because she has no interest in BL Unlocking and all that goes with it. There have been others who kept returning phones until they got one that allowed BL Unlocking. If you purchased from Google originally, just tell them the problem and they should send you another RMA replacement, from what I've seen elsewhere.
Edit for clarification: Supposedly, they've been getting Verizon and Google Pixel 2s mixed up when they get refurbished.
Click to expand...
Click to collapse
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.

MrKillroy said:
I ordered a new open OEM Pixel 2 XL 64gb in Just Black arriving from eBay in 48hrs. I am now concerned.
Click to expand...
Click to collapse
I am too. I'm still paying mine off and I've been without a well-functioning phone since June 15.

So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again

Jomama22 said:
So op, is this the first time you have tried unlocking this rma? If so, sounds like you know the problem and probably have to rma again
Click to expand...
Click to collapse
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.

plgonzalezrx8 said:
Yes. This is the first time I tried to unlock this RMA, just got it a couple days ago. I have rooted all my android phones for the past 4-5 years and never had a problem similar to this show up before. The thing is that I really want to know what is happening at at deeper level, why is this happening, it doesn't make any sense at all because why would that option change if the fasboot flashing command is returning an error, also when I use "fastboot flashing get_unlock_ability" it returns a (1) and not a (0), which means that it can be unlocked.
We'll see, I started the RMA process lets see what they say.
Click to expand...
Click to collapse
I don't remember where exactly I saw it, but in one of the commands, it tells you whether it's allowed to be unlocked. That's a firm 0 in that spot. Like I said, you likely ended up with a refurbished Verizon version. The only difference, to my knowledge, is that Verizon doesn't want you to unlock your bootloader.

There's already a whole thread about this. Please post there
https://forum.xda-developers.com/pixel-2/help/oem-unlocking-grayed-vzw-pixel-2-t3776763/page5
Bottom line. Google pixel 2s refurbished RMAs are botched for OEM unlocking. There's a problem with their refurbishment procedures that makes it behave exactly like show here
Only solution is trying to convince them to send you a new RMA, but good luck with that.

plgonzalezrx8 said:
The issue that I'm having is that I am unable to unlock the bootloader even though I should be able to. Here are the steps i'm taking and where the issue happens.
Factory/Wipe reset
Tap about Pixel 2 7 times to get developer options
Go to developer options and enable USB Debugging and OEM Unlocking.
(I Can see that OEM unlocking is enabled).
Then I do "adb reboot bootloader"
and once in the bootloader, I do "fastboot flashing unlock"
Then it tellsme that Flashing Unlock is not allowed and when I go back to the developer options, the OEM Unlocking is greyed out and in the off position and I cannot re enable it no matter what. I have not being able to find anyone with this problem or a solution, any help would be appreciated.
I have tried the above steps many times with no luck, and every time the results are the same. It gives me the OEM Unlock option right after the factory reset, but one I do the "fastboot flashing unlock" it doesn't unlock the bootloader and then it locks the option in developer options.
I updated both ADB and fastboot to the latest version.
Edit #2: running the "fastboot flashing get-unlock-ability" command, returns a (1), which means that it should be able to be unlocked.
Edit #3: Tried to sideload OTA update using ADB and it does not solve the issue.
Click to expand...
Click to collapse
Please visit this thread for more info. Though I need to mention there is no actual fix as of yet.

Mi unlock status shows wrong info..

I'm using latest global stable 10.0.5.0 rom.
I unlocked bootloader, installed DM verity patch and installed Pitchblack recovery.
Installed Camera2Api zip and magisk 18.
After these, I looked at the device unlock status at developer settings page.
But, what I see, It shows my device is locked. I can bind account, and I can enable the option gives permission to unlock. It seems my device locked as previous.
But, I checked the status with fastboot commands. And it writes unlock status : true. And I can install everything, root works, Uninstall any program etc. I know the device is unlocked. But, why it shows wrong info (locked) in developer settings?
Did I anything wrong, or is it normal?

I'm having the same problem.

I was also having this problem. but when placing the device in the miunlock, it was unlocked normally.

My device is unlocked too. I can install any rom/update with TWRP without problem. But it shows wrong info (locked) in developeroptions/mi unlock status.

edu_pozzolini said:
I was also having this problem. but when placing the device in the miunlock, it was unlocked normally.
Click to expand...
Click to collapse
Did it wipe the data again ? I mean it just unlocked the device without wiping internal storage OR you've to go through the whole process of rooting again?
Sent from my Redmi Note 6 Pro using Tapatalk

live4speed said:
Did it wipe the data again ? I mean it just unlocked the device without wiping internal storage OR you've to go through the whole process of rooting again?
Click to expand...
Click to collapse
I did not wipe the date again and also did not do the root process again. only checked if the bootloader was still unlocked.

edu_pozzolini said:
I did not wipe the date again and also did not do the root process again. only checked if the bootloader was still unlocked.
Click to expand...
Click to collapse
So miui system started showing the correct status after that ? What's your device status now?
Sent from my Redmi Note 6 Pro using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:06 PM ----------
live4speed said:
So miui system started showing the correct status after that ? What's your device status now?
Sent from my Redmi Note 6 Pro using Tapatalk
Click to expand...
Click to collapse
I just checked my device with mi unlock. It see it as a locked device. I saw a warning that unlocking my device will ERASE DATA. so I didn't go further & disconnected my device.

live4speed said:
So miui system started showing the correct status after that ? What's your device status now?
Sent from my Redmi Note 6 Pro using Tapatalk
---------- Post added at 09:22 PM ---------- Previous post was at 09:06 PM ----------
I just checked my device with mi unlock. It see it as a locked device. I saw a warning that unlocking my device will ERASE DATA. so I didn't go further & disconnected my device.
Click to expand...
Click to collapse
my status remains unlocked when I put it in mi unlock toll. but in developer settings it shows device locked.

edu_pozzolini said:
my status remains unlocked when I put it in mi unlock toll. but in developer settings it shows device locked.
Click to expand...
Click to collapse
Wish someone could tell how to fix that problem without wiping data & start from the scratch again.

live4speed said:
Wish someone could tell how to fix that problem without wiping data & start from the scratch again.
Click to expand...
Click to collapse
if your device is locked as on the miunlock tool I think you'll have to do it again anyway. mine is unlocked according to the tool. this occurred to me with Redmi Note 3 that in the developer options also showed for some time that the device was locked. it must be a system error because then the correct information appeared.

edu_pozzolini said:
if your device is locked as on the miunlock tool I think you'll have to do it again anyway. mine is unlocked according to the tool. this occurred to me with Redmi Note 3 that in the developer options also showed for some time that the device was locked. it must be a system error because then the correct information appeared.
Click to expand...
Click to collapse
But I've checked with fastboot method & it showed my device bootloader as unlocked.
BTW Did u get that "your device is unlocked" on the miunlock tool as soon as you connected the device in fastboot ? Or did you also see that "unlock will erase data" warning first ?

I can't wait anymore, and flashed global beta rom 8.12.27 with Miflash tool. But I didn't notice the option "clean all and lock" selected at the bottom. Flashing process finished without any problems.
But my device is now locked again. It shows locked when I checked with fastboot commands.
I can bind account in developer options. I tried to unlock again, but mi unlock tool gives me error: "The phone has not been used for the specified time and cannot be unlocked. Wait for 7 days and try again."
Now I'm waiting for 7 days, after that will try again...

live4speed said:
But I've checked with fastboot method & it showed my device bootloader as unlocked.
BTW Did u get that "your device is unlocked" on the miunlock tool as soon as you connected the device in fastboot ? Or did you also see that "unlock will erase data" warning first ?
Click to expand...
Click to collapse
I think it showed "unlock will erase your data". but I'll check it when I get home and tell you.

netlogger said:
I can't wait anymore, and flashed global beta rom 8.12.27 with Miflash tool. But I didn't notice the option "clean all and lock" selected at the bottom. Flashing process finished without any problems.
But my device is now locked again. It shows locked when I checked with fastboot commands.
I can bind account in developer options. I tried to unlock again, but mi unlock tool gives me error: "The phone has not been used for the specified time and cannot be unlocked. Wait for 7 days and try again."
Now I'm waiting for 7 days, after that will try again...
Click to expand...
Click to collapse
That's why I'm not flashing stock rom again. I don't want to start from the scratch again.
---------- Post added at 02:15 AM ---------- Previous post was at 02:13 AM ----------
edu_pozzolini said:
I think it showed "unlock will erase your data". but I'll check it when I get home and tell you.
Click to expand...
Click to collapse
Ok mate that'll be very helpful. Post screenshots of miunlock tool as well if possible. It may help many people who are having the same problem .

live4speed said:
That's why I'm not flashing stock rom again. I don't want to start from the scratch again.
I didin't notice the option. If I were only selected "clean all", there was no problem, then I will not have to start from scratch..
Click to expand...
Click to collapse

live4speed said:
That's why I'm not flashing stock rom again. I don't want to start from the scratch again.
---------- Post added at 02:15 AM ---------- Previous post was at 02:13 AM ----------
Ok mate that'll be very helpful. Post screenshots of miunlock tool as well if possible. It may help many people who are having the same problem .
Click to expand...
Click to collapse
I am trying to unlock the bootloader
But it shows an error every single time
Sometimes at 50 percent saying that device can't be verified
Sometimes at 99 percent saying that it can't be unlocked.
Please help me.

shaharyan93 said:
I am trying to unlock the bootloader
But it shows an error every single time
Sometimes at 50 percent saying that device can't be verified
Sometimes at 99 percent saying that it can't be unlocked.
Please help me.
Click to expand...
Click to collapse
first you have to associate your mi account with the device in the developer options. done that, wait 15 days to use the miunlock toll with device in fastboot mode.

Reference to original issue ..."Mi unlock status shows wrong info.."
i too have same issue on Redmi Note 9S Global version. Perhaps Magisk is trying to hide that the phone is actually unlocked.

Xiaomi redmi note 6 pro unbrick
Xiaomi redmi note 6 pro unbrick without authorized mi account! No need bootloader unlock

Today I realized the same thing on my Poco F2 Pro. Device seems locked. Today I turned to stock ROM from Xiaomi.eu with Mi flash but I didn't choose lock option. I chose clean all and then flashed.
I think it is because of the checkpoint configuration on Mi Flash program. I removed Bootloader -s lock" kind of something before flashing since the previous flash finished a bootloader unlocked kind of error.
Device may see itself as locked since Mi Flash finishes without checking the lock status. It should be try and see result. But I can't do that since I all restored my apps, settings etc.

Question How to unlock new Tmo variant with OEM unlock greyed out?

Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?

TimmyP said:
Title pretty much asks it all.
In developer options, OEM unlocking is greyed out. Is there a way to unlock and if so how?
Click to expand...
Click to collapse
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?

Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.

TimmyP said:
Yes Internet. Oos 11. I tried the T-Mobile app for permanent unlock it failed. Doesn't say anything but "allows the bl to be unlocked" but it's greyed.
Click to expand...
Click to collapse
Permanent unlock is sim unlocking, has nothing to do with OEM unlocking

Thats great thanks

I got it. Set to midi connection so ADB detects phone.
adb shell
pm disable-user com.qualcomm.qti.uim
Now OEM unlocking is ungreyed

Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.

TimmyP said:
Its a no go. It reveals the option, but fastboot commands ask for a token.
Going to the Oneplus token generator with the correct info (because get oem info worked in fastboot) results in a window that says
"api router invoker request error"
It seems these phones are no longer rootable. Maybe when its paid off tmobile will give me a token.
Any ideas?
"fastboot flashing unlock" asks for token.
Click to expand...
Click to collapse
Maybe the site down, probably wait a bit, got the same error too

Thanks Ill get all prudent info in a text file. What a pita. I loathe having a new phone and not knowing whether I can root it. So much setting up already.

I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.

TimmyP said:
I tried it again for the heck of it, and now it says "IMEI number has been applied" ...so I guess I wait for the email?
Never got a confirmation or anything, but searches tell me I should get it in a few days to weeks.
Click to expand...
Click to collapse
i got mine around an hour later after applying mine, maybe check hourly to see if you gotten it or not?

Nothing. Tbh I think Im gonna return this. Its only 128gb version and I was much happier with rooted A32 5G.
Sucks cant even use tasker for fun stuff.

Look through the OP9 forums for the OnePlus Tool..... it helps you get the number you write down to request the unlock code from OnePlus, also it can ungrey the OEM switch

Thanks but I already got that stuff requested. Still no token :-( Been talking to support tho they said they are on it!

underworld737 said:
Have you connected to internet? What version of oxygen os are you on? And does it say "connect to the internet or contact your carrier" by the OEM unlocking toggle?
Click to expand...
Click to collapse
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')

barguybrady said:
OMG !
I have spent 7 hours attempting to unlock my Boot-Loader, and in the desire to prevent any unintended updates, I did not connect my OP9 to the network.
I Think That This Advice Should be Stickied to the front page:
"Unable to toggle OEM unlocking in <Developer Settings> ?"
"Connect to Internet first to see if it's already done !!"
HOWEVER, I still cannot :
Code:
flashboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
Click to expand...
Click to collapse
Try ,,,,,,fastboot oem unlock,,,,

Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.

TimmyP said:
Its fastboot flashing unlock and I wouldnt recommend anything but using a token, because the rooting information here is fragmented and outdated.
Request one from oneplus and check back on that page you requested it on. Mine took about 3 days.
Click to expand...
Click to collapse
I already have that... Hence my confusion.
I'm thinking that there's Just One Little Thing I'm doing wrong here... Can't figure it out..!
Aha. I had been doing it in the wrong order.
Bash:
fastboot devices
fastboot flash cust-unlock unlock_code.bin
fastboot oem unlock