Hi, what exactly does this mean?
I get this message when booting the device into recovery, or "download mode"
I just picked up a used htc u11 from ebay, and I intend to run totally stock and would like to receive OTA updates.
I would guess this phone has been rooted in the past, although I am not entirely sure.
I would like to know what exactly this message means, what is going on.
It's a Sprint phone, I recently flashed the device with stock RUU firmware package (bundled with installer) obtained directly from htc, though this did not remove the failed security check.
Also, would it be possible to return this phone to 100% stock? Thanks.
It seems the security check is part of the htc security feature (S-ON) primarily intended to protect the radio and sim. Though any more information here would greatly be appreciated.
Not exactly sure what cause any security check to fail, or what part of the phone would need to be changed to where a stock rom flash would not revert any changes.
Further information -
Device state is locked,
Secure state is on (S-ON)
Secure boot reads as "PRODUCTION"
Software status reads as "OFFICIAL"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The specific message I get says "Security checking failed DENY"
Then followed by a basic warning about flashing custom firmware,
Then it lists, what I assume are things it has denied,
It lists -
"SD NOT MOUNTED"
"OTG NOT MOUNTED"
"File NOT FOUND"
I don't want to pass this off as a generic warning, or a bug, perhaps as something which has stuck from a previous root attempt, and is harmless.
I am definitely concerned that the phone may have been tampered with by some other means for "S-ON" feature to be complaining this way.
Once again, I have already flashed the phone with stock htc firmware, I don't see a reason for any of this.
Please excuse my lack of knowledge on this subject. I even tried searching for "htc download mode" which in itself I am also unaware of, and any information is hardly available online for even this. "download mode" seems to be a part of some firmware which comes before the bootloader, or is a different part of the bootloader itself, and needs SD/OTG/file access for some kind of update purpose, which in itself is different from the one already provided by the default recovery mode.
This is getting rather silly.
It would seem normal to "DENY" SD/OTG access, because download mode should not be open or ready this way by default, but perhaps it's something which is designed to recover the phone in case even the bootloader becomes corrupt? I'm really not sure.
Seems normal to deny this, but once again I really don't know.
This "security check failed DENY" message is rather confusing. Do you perhaps need some kind of key to activate download mode?
and00r said:
It seems the security check is part of the htc security feature (S-ON) primarily intended to protect the radio and sim. Though any more information here would greatly be appreciated.
Not exactly sure what cause any security check to fail, or what part of the phone would need to be changed to where a stock rom flash would not revert any changes.
Further information -
Device state is locked,
Secure state is on (S-ON)
Secure boot reads as "PRODUCTION"
Software status reads as "OFFICIAL"
Click to expand...
Click to collapse
Id say its because your bootloader is unlocked...
miffymiffy said:
Id say its because your bootloader is unlocked...
Click to expand...
Click to collapse
As I already stated, the device is locked. Thanks for your input though.
It really seems like the S-ON feature is reporting a failed signature check, that is obviously my biggest concern.
And I don't know what the stock htc firmware actually replaces, so please, if anyone can help, that would be especially appreciated.
These phones are actually solid in quality and build, and no other devices are priced this low on the used market, so there is really no other option , as I don't wish to overpay several hundred more dollars for used previous gen hardware. I am definitely content with the Snapdragon 835 and especially the Adreno 540.
anyone?
Did not expect this thread to go completely ignored this way... come on guys
I'm with miffymiffy on this one. I have the same warning. Afaik there's no way to remove it, even if you're successful in relocking it. Just read all the threads pertaining to S-ON/OFF.
and00r said:
As I already stated, the device is locked. Thanks for your input though.
Click to expand...
Click to collapse
@cynikZA is correct:
Once the bootloader has been unlocked that warning is there forever.
Relocking won't get rid of it.
jhill110 said:
@cynikZA is correct:
Once the bootloader has been unlocked that warning is there forever.
Relocking won't get rid of it.
Click to expand...
Click to collapse
Yes it seems that way, but what about the functionality of download mode?
Seems like file access is denied. Does this mean that download mode is no longer functional?
and00r said:
Yes it seems that way, but what about the functionality of download mode?
Seems like file access is denied. Does this mean that download mode is no longer functional?
Click to expand...
Click to collapse
Everything will work as it should.
miffymiffy said:
Everything will work as it should.
Click to expand...
Click to collapse
Alright, thanks.
Related
First of all sory formy english
I did update two days ago,but I have problem with my phone,it is locking and loose signal telephone and 3g,also battery finishing quickly.What is the problem I tried to enter 3g options but *#*#4636#*#* not working,how can I back 4.1.2 version
thanks you all
You cant go back so dont bother trying unless you wish to brick your phone....did you try an fdr
cmh714 said:
You cant go back so dont bother trying unless you wish to brick your phone....did you try an fdr
Click to expand...
Click to collapse
yes I did but still same
trapper66 said:
yes I did but still same
Click to expand...
Click to collapse
Since you're up to 4.2.2, (assuming locked bootloader?) then there is not much outside of a factory reset to fix your phone's problems.
You might just have to get a warranty replacement.
jewbydoo said:
Since you're up to 4.2.2, (assuming locked bootloader?) then there is not much outside of a factory reset to fix your phone's problems.
You might just have to get a warranty replacement.
Click to expand...
Click to collapse
thank you for answer my friend,what does it mean locked bootloader,how can fix this,ı made just download 4.2.2,nothing else,what should I do
trapper66 said:
thank you for answer my friend,what does it mean locked bootloader,how can fix this,ı made just download 4.2.2,nothing else,what should I do
Click to expand...
Click to collapse
If you have a locked bootloader, it means the phone is locked down to where you cannot use custom recoveries (like CWM or TWRP) and you cannot flash ROMs that have a different kernel than what is currently on your phone. There's a whole host of other things, but that's the main issue.
Unless your phone is on JB version 9.16.9 or earlier (AND no one has flashed a later version and then flashed back to the previous version), then you cannot unlock the bootloader on this phone anymore.
iBolski said:
If you have a locked bootloader, it means the phone is locked down to where you cannot use custom recoveries (like CWM or TWRP) and you cannot flash ROMs that have a different kernel than what is currently on your phone. There's a whole host of other things, but that's the main issue.
Unless your phone is on JB version 9.16.9 or earlier (AND no one has flashed a later version and then flashed back to the previous version), then you cannot unlock the bootloader on this phone anymore.
Click to expand...
Click to collapse
Now,I have problem like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't my phone unlock,I tried this way (motorola offical bootlader way) the and I saw message like this,your phone cannot be unlock
is it normal ?
trapper66 said:
Now,I have problem like this
View attachment 2781977
I can't my phone unlock,I tried this way (motorola offical bootlader way) the and I saw message like this,your phone cannot be unlock
is it normal ?
Click to expand...
Click to collapse
you cannot unlock the XT926 with the official unlocker from Motorola unless it's the dev edition. Only the XT925 can be unlocked via the Motorola unlocker (at least for the RAZR HD phones).
But, you are already on Kit Kat. You even quoted where I said if you are apply an OTA greater than 9.16.9 version, you CANNOT unlock your bootloader ever. Once you do that on an XT926, you've patched the exploit that allowed unlocking the bootloader and nothing will ever put it back because it's in a protected area that you cannot flash back to a previous version to put the exploit back in.
Sorry, once you took the KitKat upgrade, you've lost any chance of unlocking the bootloader. Don't even try to flash back to a previous version. You'll brick your device. This has been stated over and over and over again since the KitKat ota has been released.
iBolski said:
you cannot unlock the XT926 with the official unlocker from Motorola unless it's the dev edition. Only the XT925 can be unlocked via the Motorola unlocker (at least for the RAZR HD phones).
But, you are already on Kit Kat. You even quoted where I said if you are apply an OTA greater than 9.16.9 version, you CANNOT unlock your bootloader ever. Once you do that on an XT926, you've patched the exploit that allowed unlocking the bootloader and nothing will ever put it back because it's in a protected area that you cannot flash back to a previous version to put the exploit back in.
Sorry, once you took the KitKat upgrade, you've lost any chance of unlocking the bootloader. Don't even try to flash back to a previous version. You'll brick your device. This has been stated over and over and over again since the KitKat ota has been released.
Click to expand...
Click to collapse
thanks my friend,I totaly understand I must wait to fix or new update, I suppose
you any idea about my problem ? why it's happening,especially phone is on lockscreen,when ı using the phone,tapatalk whatsapp facebook,there is no problem ,when I locked my screen it will be block and restarting,two or three times a day
trapper66 said:
thanks my friend,I totaly understand I must wait to fix or new update, I suppose
you any idea about my problem ? why it's happening,especially phone is on lockscreen,when ı using the phone,tapatalk whatsapp facebook,there is no problem ,when I locked my screen it will be block and restarting,two or three times a day
Click to expand...
Click to collapse
There is no way to unlock it, ever. Don't wait for a fix, as there is no fix to unlock the bootloader. It was never meant to be unlocked. It was unlocked via a security exploit and that exploit was patched after 9.16.9. There is no way to "fix" it.
As for your phone restarting, I would say a factory data reset is probably your only cure. It wipes everything (including your internal SD card), so be sure to back up what you can, especially pictures, etc.
The Nokia 7.2, surprisingly, comes with an unlockable bootloader. The information is shared by TechMesto and I am just re-using it to create this guide.
Notes:
Unlocking the bootloader may void the device's warranty.
All existing data on the device will be erased.
To unlock:
Update: Nokia has disabled the unlock ability with the December MR. You can only unlock if you downgrade your phone to an old release first. You can get it at Nokia Care or by buying remote flashing services.
Before you start: Make sure that you have platform-tools downloaded on your PC. You need to open a CMD or Terminal window in the folder where you have saved the platform-tools, unless you have installed them system-wide.
• First of all, enable Developer Options by tapping 7 times on BuildID in "About phone".
• Then go to developer options and enable OEM Unlocking option.
• Now reboot the phone into bootloader/fastboot mode. You can use the adb command:
Code:
adb reboot-bootloader
or else use hardware keys to reboot to bootloader mode.
• Make sure the phone is detected in fastboot mode. Then send the OEM unlocking command:
Code:
fastboot flashing unlock
• Confirm the unlock on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• That's it!
You can also do the unlock_critical if you plan to flash the bootloader.
Reserved for future use.
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
KohGeek said:
I am on a Nokia 7.2, a dual-sim variant with 6GB RAM and 128 GB ROM. The model name is TA-1196.
I am currently having issues with this method, whenever I try to flash unlock, prior to the V1.160 update, the fastboot will report back saying "Write to device failed (unknown error)".
If anyone would enlighten me I would be happy to hear.
Edit: Currently on build number 00WW_1_060
Edit 2.0: Works after updating to build 00WW_1_160. Seems Nokia enabled this method by mistake. Who knows?
Click to expand...
Click to collapse
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
singhnsk said:
Hi, looks like you were initially doing flash unlock instead of flashing unlock? And since there was nothing to flash, it failed.
Click to expand...
Click to collapse
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
KohGeek said:
I was using flashing, and as my edit has said, it seems the option to unlock the bootloader was only enabled after version 160.
Click to expand...
Click to collapse
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
singhnsk said:
That's okay, but the output you got wasn't appropriate for that command. If the unlock support isn't allowed it will say "flashing unlock is not allowed". Or in case the bootloader isn't including that command at all, it will say "Unknown command".
I might be wrong too, but your output isn't something i've seen on any of the phones i've owned, whether unlockable or non-unlockable. That output is what I usually get when the command is not proper, or the drivers aren't properly installed or the fastboot device isn't properly responding. Rebooting to bootloader should usually fix it. At least it does on other Nokia and Sharp phones.
Click to expand...
Click to collapse
I was curious too, it kicked me off the bootloader screen when I was doing that on version 060, but it seems all is well now
https://nokiamob.net/2019/11/02/off...nlock-the-nokia-7-2-and-nokia-6-2-bootloader/
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Coolboy996 said:
I unlocked bootloader now how to root this phone they didn't released kernel source for preparing twrp should i root the phone with magisk patched boot.img??
Click to expand...
Click to collapse
You can use TWRP or patched image to root the 7.2
Can confirm that it is still unlockable. Got 2 of them today from Argos in the UK (Scotland). They are on 00WW_1_130 with security batch from 2019/08/05.
Only thing I had to do was enable internet and reboot to get the option to stop being greyed out.
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Are you sure? Has Horrendously Menacing Dicks actually started blocking people having reasonable control of their 7.2 devices after letting them have it for so long?
allc0re said:
Just got mine today and it forced a system update upon activation. I was unable to unlock the bootloader.
Click to expand...
Click to collapse
Yep. They blocked the ability with the most recent December MR.
singhnsk said:
Yep. They blocked the ability with the most recent December MR.
Click to expand...
Click to collapse
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
CGarz said:
Ah that sucks. Did you try connecting to the internet and rebooting? That enabled the option to enable OEM Unlocking in developer settings for me.
Click to expand...
Click to collapse
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
That really sucks. Now no devs will buy it =(.
allc0re said:
I was able to turn on OEM Unlocking in Developer Options, but running the command in fastboot failed.
Click to expand...
Click to collapse
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
bkttk2 said:
I know they planned to lock it down ; however were you using the most recent fastboot (platform-tools). I know I had issues with not having most current versions.
Click to expand...
Click to collapse
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Lamtanloc512 said:
I also can not unlock the bootloader after update security 05/12/2019...MB no longer unlockable bootloader any more.
Click to expand...
Click to collapse
Think we may be out of luck then, but one last suggestion. I noticed when reading through the thread on user indicated they were using "flash" instead of "flashing" when trying to unlock the bootloader.
I know I personally did the same thing at first. Did anyone confirm that "flashing" was used?
I know the older methods used flash. Just asking.
Folks,
I bought a used Pixel 3, seller said it was only used for testing. Bootloader is unlocked, and the firmware version doesn't match anything listed on the Google site, but it may just be an older version no longer listed. Can anyone help me determine if this is a standard Android build? Build number: blueline-userdebug 10 QP1A.190514.001 5563344 dev-keys
Scooberjake said:
Folks,
I bought a used Pixel 3, seller said it was only used for testing. Bootloader is unlocked, and the firmware version doesn't match anything listed on the Google site, but it may just be an older version no longer listed. Can anyone help me determine if this is a standard Android build? Build number: blueline-userdebug 10 QP1A.190514.001 5563344 dev-keys
Click to expand...
Click to collapse
You can flash any firmware and bring it up to speed wit hthe latest, then relock yur bootloader if you dont want to tinker your Pixel 3
Follow the official instructions in the link below (from Google)
full factory image https://developers.google.com/android/images#blueline
Instructions: Look towards the top of that same page, linked above
BBobby said:
You can flash any firmware and bring it up to speed wit hthe latest, then relock yur bootloader if you dont want to tinker your Pixel 3
Follow the official instructions in the link below (from Google)
full factory image
Instructions: Look towards the top of that same page, linked above
Click to expand...
Click to collapse
Yes, I saw that and thought I might do it. Was a little confused by the fact that for the latest version there are two files with nearly identical names, one ending in Verizon. Is that for phones on the Verizon network or phones purchased from Verizon? Mine was advertised as unlocked, but I don't know how to verify that. If I use the wrong one I guess I will have problems? Should my phone update to the latest automatically if my ROM is stock?
Scooberjake said:
Yes, I saw that and thought I might do it. Was a little confused by the fact that for the latest version there are two files with nearly identical names, one ending in Verizon. Is that for phones on the Verizon network or phones purchased from Verizon? Mine was advertised as unlocked, but I don't know how to verify that. If I use the wrong one I guess I will have problems? Should my phone update to the latest automatically if my ROM is stock?
Click to expand...
Click to collapse
Reboot your phone. If a warning message comes up as your phone reboots that says your bootloader is unlocked, then it is unlocked.
Tulsadiver said:
Reboot your phone. If a warning message comes up as your phone reboots that says your bootloader is unlocked, then it is unlocked.
Click to expand...
Click to collapse
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Scooberjake said:
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Click to expand...
Click to collapse
Use the version that matches your carrier. If on VZ use that image. It will not lock the bootloader, just some modem changes.
You can go back and forth all you want.
Scooberjake said:
Yeah, I know the bootloader is unlocked, just not 100% sure it is network unlocked. Do I use a different factory image if the phone was purchased at Verizon vs through Google?
Click to expand...
Click to collapse
If the bootloader is unlocked, it was not purchased at Verizon. Verizon phones have locked bootloaders. I have a google purchased unlocked phone that works fine with a Verizon SIM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I can use this second one (since I am one Verizon) regardless of where the phone was purchased?
The bootloader is definitely unlocked (got the message on the phone). But I thought all Pixel 3 phones could be unlocked,not just the ones bought directly from Google.
Scooberjake said:
So I can use this second one (since I am one Verizon) regardless of where the phone was purchased?
The bootloader is definitely unlocked (got the message on the phone). But I thought all Pixel 3 phones could be unlocked,not just the ones bought directly from Google.
Click to expand...
Click to collapse
Yes, the VZ one.
No, only phones purchased through Google can be bootloader unlocked. VZ purchased phones can not. Some EU 3s can be bootloader unlocked after the contract is up.
All can be SIM unlocked.
One last question. Can I sideload an OTA rather than flashing the full factory image? I don't understand when to do one and when to do the other.
Scooberjake said:
One last question. Can I sideload an OTA rather than flashing the full factory image? I don't understand when to do one and when to do the other.
Click to expand...
Click to collapse
In your case flash the full factory image, including the wipe, since you're not real sure what firmware the phone is currently on. In the future you can do the ota if you want or the factory image without the wipe.
Hi,
I want to unlock my bootloader to install the Indonesian Rom,
when I unlock I get this message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I relock after flashing the new Rom will the phone be protected again ?
also, has any one else have problems with dark mode ?
Thank you in advance,
Itai.
itais said:
Hi,
I want to unlock my bootloader to install the Indonesian Rom,
when I unlock I get this message
View attachment 5315651
Click to expand...
Click to collapse
Those tips are just a confirmation. If you are worried about what it's telling you, then don't unlock bootloader.
itais said:
If I relock after flashing the new Rom will the phone be protected again ?
Click to expand...
Click to collapse
Only if you flash your own region stock back. Eg. your device is Indian, then you have to flash back to Indian Rom, then you can relock.
If you relock when having different region Rom, there might cause some problem or even brick your phone.
If you are going to use other region Rom, then do not relock the boot loader.
itais said:
also, has any one else have problems with dark mode ?
Click to expand...
Click to collapse
What problem specific?
pl1992aw said:
Those tips are just a confirmation. If you are worried about what it's telling you, then don't unlock bootloader.
Only if you flash your own region stock back. Eg. your device is Indian, then you have to flash back to Indian Rom, then you can relock.
If you relock when having different region Rom, there might cause some problem or even brick your phone.
If you are going to use other region Rom, then do not relock the boot loader.
Click to expand...
Click to collapse
Ok Thanks
pl1992aw said:
What problem specific?
Click to expand...
Click to collapse
Some apps don't work , and for some i found that i can disable dark mode and then they work and there text is visible
Anybody please feel free to correct if I'm wrong, but I think what "may damage your device or cause financial loss" is exactly that custom ROM you're flashing, nothing else.
disacrol said:
Anybody please feel free to correct if I'm wrong, but I think what "may damage your device or cause financial loss" is exactly that custom ROM you're flashing, nothing else.
Click to expand...
Click to collapse
Finger print is not as secure as device with locked bootloader. This is an example of financial loss, eg. loosing the device stolen by strangers. This is what the "find my device" option Google offers for.
Even if you have official MIUI with unlock bootloader, if people steal your device, they can take your personal data with TWRP if they crack the password and finger print.
pl1992aw said:
What problem specific?
Click to expand...
Click to collapse
^ hijacking this.
*** SPOILER: I've found an answer, it's below ***
This is how sorting menu looks like in Youtube Manager Studio for example. Guess it's app-specific but I've encountered couple of them not very happy about dark mode.
(I'm on Xiaomi.eu roms but stock was the same)
Any chance I could tweak it a little somewhere?
EDIT: Found solution! Just enter Settings > Display > More Dark mode options and then just disable dark mode for problematic apps. Ofc it doesn't fix dark mode for them, just removes dark mode from those specific apps, but for me it's okay as a workaround
I've recently unlocked the bootloader on my Xiaomi device and have encountered an issue getting past the 'This device is Locked' screen.
I have access to the Xiaomi account that was linked to the device, and have entered the correct information, several times using a combination of both with WIFI and without (mobile data) using two different sim cards, and my email address to verify the account using the 2fa on the device.
Unfortunately the screen just disappears for a second before re-appearing and I'm stuck trying to enter the prompts again.
Has anyone encountered this? Does anyone know how I can bypass this screen to continue with the setup process?
I'll try attaching a video that shows the process of what Is happening and I apologise for the sound -- it's hard trying to juggle two devices and record at the same time.
Video
doomanix said:
I've recently unlocked the bootloader on my Xiaomi device and have encountered an issue getting past the 'This device is Locked' screen.
I have access to the Xiaomi account that was linked to the device, and have entered the correct information, several times using a combination of both with WIFI and without (mobile data) using two different sim cards, and my email address to verify the account using the 2fa on the device.
Unfortunately the screen just disappears for a second before re-appearing and I'm stuck trying to enter the prompts again.
Has anyone encountered this? Does anyone know how I can bypass this screen to continue with the setup process?
I'll try attaching a video that shows the process of what Is happening and I apologise for the sound -- it's hard trying to juggle two devices and record at the same time.
Video
Click to expand...
Click to collapse
Check here that your device appears and that the phone number matches, otherwise delete the phone from your account and try again.
Or use the reset after deleting the device from the account.
Disregard the i clicked on it wanting to click on the video link.
.
.
NOSS8 said:
Check here that your device appears and that the phone number matches, otherwise delete the phone from your account and try again.
Disregard the i clicked on it wanting to click on the video link.
.
.
Click to expand...
Click to collapse
The device appeared originally and I removed it from the account yesterday in the hopes I could get through this barrier.. I've been two days on this being blocked by the 2fa limit in 24h. Unfortunately removing the device didn't seem to help.
Should I look to do a fastboot reset of the device? Do you think that could help? I could try a flashing the xiaomi.eu rom again.
And no worries. I've found it pretty funny past few days how ridiculous it is.
doomanix said:
The device appeared originally and I removed it from the account yesterday in the hopes I could get through this barrier.. I've been two days on this being blocked by the 2fa limit in 24h. Unfortunately removing the device didn't seem to help.
Should I look to do a fastboot reset of the device? Do you think that could help? I could try a flashing the xiaomi.eu rom again.
And no worries. I've found it pretty funny past few days how ridiculous it is.
Click to expand...
Click to collapse
To summarize you have unlocked the bootloader then install a Xiaomi eu rom from a stock rom, right.
What stock rom?
NOSS8 said:
To summarize you have unlocked the bootloader then install a Xiaomi eu rom from a stock rom, right.
What stock rom?
Click to expand...
Click to collapse
Yes, It was Chinese stock.
I did the steps to unlock the bootloader, unlocked, waited for reboot, encountered this screen.
First night I tried to unlock on stock rom -- encountering the same issue as in the video.
Second night I tried after flashing Xiaomi.eu. After 2fa ran out I tried deleting the device from the account.
Tonight, same issue after deleting the device from the account.
I've also tried to submit my request to unlock the device to Xiaomi, but it says I'm unsuccessful as current region is different from frequent sign-in regions (though my country isn't in the dropdown and only 'other' is available).
doomanix said:
Yes, It was Chinese stock.
I did the steps to unlock the bootloader, unlocked, waited for reboot, encountered this screen.
First night I tried to unlock on stock rom -- encountering the same issue as in the video.
Second night I tried after flashing Xiaomi.eu. After 2fa ran out I tried deleting the device from the account.
Tonight, same issue after deleting the device from the account.
I've also tried to submit my request to unlock the device to Xiaomi, but it says I'm unsuccessful as current region is different from frequent sign-in regions (though my country isn't in the dropdown and only 'other' is available).
Click to expand...
Click to collapse
Flashing a Xiaomi Eu rom on a locked device after unlocking the bootloader is not a good idea.
The account and the sim card must be the same as the one used for unlocking.
try reset
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or flash the same CN rom as the origin with this tool. (do not lock the bootloader)
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
You could try fastboot erase frp command and see if that helps. Thats the command for removing any account locks.
But flashing a new firmware on a locked, or re locked bootloader is generally a big no
Evo400 said:
You could try fastboot erase frp command and see if that helps. Thats the command for removing any account locks.
But flashing a new firmware on a locked, or re locked bootloader is generally a big no
Click to expand...
Click to collapse
For Google account not Xiaomi.
NOSS8 said:
Flashing a Xiaomi Eu rom on a locked device after unlocking the bootloader is not a good idea.
The account and the sim card must be the same as the one used for unlocking.
try reset
View attachment 5721107
or flash the same CN rom as the origin with this tool. (do not lock the bootloader)
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
Thank you for your support. I reflashed the stock Chinese rom using the flash_all.sh script and unfortunately have encountered the same issue as shown before in the video. To be clear, this issue was happening on the stock rom, then I flashed xiaomi.eu and problem still persisted.
I've used the same number as was used in the unlocking process -- same result occurs it just loops at the unlock screen. Is there anything else you could recommend I do?
The device is no longer linked to my account and I still receive this message upon opening it.
EDIT:
Issue was resolved either by Xiaomi, or by going to Xiaomi Cloud and Find device, selecting the device, selecting the erase device option, then the delete device option from the hamburger menu. Device now seems to be unlocked and setup is appearing. I guess after removing the device from the Xiaomi account it persists in other aspects of the Xiaomi ecosystem.