Develop Bugs

[Q] USB Debugging mode blocked by Server?

Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!

I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging

jac10000 said:
I have same problem when the G3 ìs plug on the pc , is it the case for you here ? If yes unplug your G3 and then you can activate debugging
Click to expand...
Click to collapse
It does not show up ever, unplugged or plugged in.

Jacobsen Chief said:
It does not show up ever, unplugged or plugged in.
Click to expand...
Click to collapse
Ok try this :
Solution 1 : Have you switche the activate button ?
{
"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"
}
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode

jac10000 said:
Ok try this :
Solution 1 : Have you switche the activate button ?
Solution 2 : go to menu and select default parameters and try another
Solution 3 : Test the differents options (PTP, MTP, ONLY CHARGE) and each time try to activate Debugging mode when you plug to pc
Solution 4 : Go to this menu and select program install then try to activate debugging mode
Solution 5 : Revoke the authorizations and try to activate the debugging mode
Click to expand...
Click to collapse
None of those things worked... Ive never seen this before. Here is a screenshot

I think it's a bug with lollipop and it seem that the solution is the factory reset

jac10000 said:
I think it's a bug with lollipop and it seem that the solution is the factory reset
Click to expand...
Click to collapse
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?

And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1

jac10000 said:
And by flashing kdz firmware ? Il seems thant the update by OTA to 5 which is the cause of your problem.
Can be that by installing KDZ firmware you have this function ...
When you are on KitKat can you activate debugging ?
Type here your imei to have the lastest version of kdz : http://www.lg-phone-firmware.com/index.php?firmware=1
Click to expand...
Click to collapse
I tried installing the KDZ though TWRP, but when it failed I decided to go ahead and just update it with the LG Software. I had read other articles on rooting the G3 with Lollipop, so I didn't really worry about re-rooting it until I ran into this problem.
For installing with the KDZ, I extracted Modem, Boot, and System.imgs, but the System.img failed. And yes with KitKat, I could use debugging.

facing the same problem myself, did you ever find a solution? because this is getting really frustrating

Dragontype191 said:
facing the same problem myself, did you ever find a solution? because this is getting really frustrating
Click to expand...
Click to collapse
Update, I made a post over on the US Cellular forums and if anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!

Dragontype191 said:
If anyone is having this problem it is the McAfee bundled in with the new lollipop update, just find the McAfee app (you can't uninstall it without root) clear the cache on it and click the manage space button and it'll ask you to put in your pin to deactivate it, after I did that my debugging is back!
Click to expand...
Click to collapse
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.

To Enable USB Debugging mode that is blocked by Server you have to dissable McAfee Mobile SECURITY

Jacobsen Chief said:
Just did a factory reset-Same result. I could understand them blocking this to protect against root (I wonder why LG and US Cellular are so against it), but what if I was actually a developer wanting to use SDK or make an app? It kind of ruins that feature. Any other suggestions?
Click to expand...
Click to collapse
Click on revoke USB debugging authorization. Click ok. Turn off developers option on the verg top. Turn it on again and voila you now have an option to put a check on usb debugging. Hope it works for you...
LG G3 Android 5.0 user

Jacobsen Chief said:
Alright, heres a new one boys. I recently updated my US Cellular G3 to 5.0, and wanted to root. The first and only problem I have is when I go to allow debugging, the tab is grey out and underneath it says, "USB Debugging is disabled by server policy"
What can I do to change this? Any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
PLEASE PLEASE PLEASE READ! This is probably the fix to this problem all because of a stupid built in app that the g3 includes now and it has to do with McAfee Security.
If it worked mark this up for those future people who have issues!!
Okay so i found out what the problem was. I used to own and lg g2 but recently got the g3. Im with sprint fyi...but anyways i was tinkering around with it being 17 and stupid i bricked the phone, so i eventually got it fixed again. Previously my phone was rooted but now it wasnt so then i went back to get developer options activated and usb debugging active as well, however i ran into this problem. This stumped me because i had it rooted before. So then i was thinking what did i give accsess to that i hadnt before that isnt allowing usb debbugging...well it had to be an app since this didnt happen to me before and it had to be an app that i hadnt used before i bricked my phone and then i thought it has to be a built in app since no third party app would have that permission to say something like "disabled by server policy" then i realised okay what does the g3 have that the g2 doesnt have and is built in.....Mcafee security and Lookout! And it made sence because when you check the box for usb debugging you are making your android less secure! So i entered the McAfee app tapped settings ---> and the first option should be "lock down device" TURN THAT OFF! That right there is your culprit now go back to dev options and you can now enable usb debugging again please rate this up so people can see what was going on and how to fix it. No need to reset your phone. Also let me know if this worked. I have got nothing but positive feed back so far.

I am having the same problem and i have an LG Lucky and usb debugging is disabled by server policy and i really dont know what to do but it worked at first then later it got blocked.

help please
PokrTom said:
Wanted to say thanks for posting this information in the General Area.
For those folk who are not as technically proficient I have laid out your instructions.
__________________________
If anyone is having this problem it is due to the McAfee Security App bundled in with the Lollipop update, you can't uninstall it without root but if you clear the cache on it and manage the space you will get debugging back.
Go to "Setting"
Go to "Apps"
Select the "All" Tab
Select the "McAfee Security" App
Click the "Clear cache" button
Click the "Manage space" button
Enter your PIN
Click "OK"
Your debugging option will now be available.
Click to expand...
Click to collapse
My debugging option is not available. Do I need to have my old sim card in place? It was from at&t. I took it out a while back. Is that why I cannot chose the Debug option? Ive tried everything on this forum.

I had the same issue. It was blocked by mcafee. I had to change it from " locked down mode" to unlocked mode, then turn developer options off and right baxk on. Then i was allowed to turn on usb debugging

Solution
Okay, so I was having the same issue. I contacted LG, Google, and finally AT&T after I tried a lot of the suggested solutions on this post. The AT&T tech support rep helped me research this issue. The issue is that an app on your phone is not allowing you to be able to debug, most likely a security app. I suppose that it thinks by allowing your phone to debug could cause harm to the device. The app that was keeping me from debugging was McAfee, which came pre-installed. When you disable this app, or whichever app is keeping you from debugging, you will then notice that the message 'USB debugging is disabled by server policy' goes away. I hope this helps you all, and happy developing!
God is good!!!

sir can you all help me for this problem? i can't update and fix my g3! ugrrrr !!!1

Hotspot issues

Brand new Mi Mix 2 with Global EU Rom, unrooted.
Setting up a hotspot on Mi Mix 2 works fine, my computer connects with the hotspot and appears as connected on the Mi Mix 2.
Ping works fine from the computer but I cannot access any website (tried on FF and Explorer).
Is there a turnaround possible? I don't want to root.

Did you try to manual alter your DNS settings on PC?

Thanks for the suggestion but concretely what should I try to change?

I tried this today and found it would not connect.
Found this on the MI Forum, was not sure if I could do a link. Thanks DepeTT
I had to turn off PC and Phone, deleted connections, reset up now working.
Looks like i found a solution to that.
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
Global, locked

Thank you FSB
After many hours trying to fix this issue it's finally work after following your instructions . Thank you so much.

FSB said:
I tried this today and found it would not connect.
Found this on the MI Forum, was not sure if I could do a link. Thanks DepeTT
I had to turn off PC and Phone, deleted connections, reset up now working.
Looks like i found a solution to that.
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
Global, locked
Click to expand...
Click to collapse
I am having trouble using the hotspot in my Mi MIX 2 (MIUI 8), I tried to do the procedure but it gives an error:
"C:\Program Files\Minimal ADB and Fastboot>adb shell
chiron:/ $ settings get global tether_dun_required
null
chiron:/ $ settings put global tether_dun_required 0
Error while accessing settings provider
java.lang.SecurityException: Permission denial: writing to settings requires:and
roid.permission.WRITE_SECURE_SETTINGS
at android.os.Parcel.readException(Parcel.java:1684)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.call(ContentProviderNative.java:646)
at com.android.commands.settings.SettingsCmd.putForUser(SettingsCmd.java:268)
at com.android.commands.settings.SettingsCmd.run(SettingsCmd.java:160)
at com.android.commands.settings.SettingsCmd.main(SettingsCmd.java:63)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:343)"
Vlw...

Allexsander said:
I am having trouble using the hotspot in my Mi MIX 2 (MIUI 8), I tried to do the procedure but it gives an error:
"C:\Program Files\Minimal ADB and Fastboot>adb shell
chiron:/ $ settings get global tether_dun_required
null
chiron:/ $ settings put global tether_dun_required 0
Error while accessing settings provider
java.lang.SecurityException: Permission denial: writing to settings requires:and
roid.permission.WRITE_SECURE_SETTINGS
at android.os.Parcel.readException(Parcel.java:1684)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:183)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.call(ContentProviderNative.java:646)
at com.android.commands.settings.SettingsCmd.putForUser(SettingsCmd.java:268)
at com.android.commands.settings.SettingsCmd.run(SettingsCmd.java:160)
at com.android.commands.settings.SettingsCmd.main(SettingsCmd.java:63)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:343)"
Vlw...
Click to expand...
Click to collapse
Check if tethering is working.
Google "Error while accessing settings provider, " some say it works

Dear Sirs,
I also have Mi Mix 2 global ROM fully upgraded to MIUI 9.1 not rooted and I faced the same problem. I noticed that my other Android phones can browse Internet using mix2 personal hotspot but my Windows 7 64bit computer, although can be connected to the personal hotspot, it is not possible to get internet connection...
Well after some testing I found that, if I specify manual DNS entries at my computer ( I used Google's public DNS servers ) then my internet connections was fine. In conclusion, in mix2 personal hotspot, there is bug regarding DNS...
Please try it and let me know.
Of course, suggested we better solution if possible.
Thanks and Best Regards,
Mike Kranidis

I cannot set the USB debugging security option (it was restricted).
Is it possible to enable wifi hotspot with buildprop edit ?

For those using predefined APN's, make sure APN protocol shows IPv4 or IPv4/IPv6. If APN protocol is on IPv6 only, you must reboot Windows 10 to get connected to internet (after connecting to any IPv4 hotspot). If there's not an APN profile with IPv4, you can create your own. I did not have to do anything else to get Personal hotspot working. On MIUI Global 9.1.2.0.

Redmi Note 4 Global - Fixed
FSB said:
I tried this today and found it would not connect.
Found this on the MI Forum, was not sure if I could do a link. Thanks DepeTT
I had to turn off PC and Phone, deleted connections, reset up now working.
Looks like i found a solution to that.
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
Global, locked
Click to expand...
Click to collapse
Hey, after trying multiple things and eventually contemplating going back to Apple, I tried your suggestion and it works fine now. The only difference was that I had to enable "USB debugging (Security settings)" as well as the standard "USB Debugging" on my version (Redmi Note 4 Global, Android 6, MIUI Global 9.5 Stable). Just make sure you disable it when you've rebooted the phone so it's secure.
Thanks again

Had issues today, tried an alternate fix from the web.
Settings -> Install Apps -> System Launcher -> Scroll Down - Clear Data / Reset All -- Reboot and it fixed it afterwards.

Logged in to thank you
FSB said:
I tried this today and found it would not connect.
Found this on the MI Forum, was not sure if I could do a link. Thanks DepeTT
I had to turn off PC and Phone, deleted connections, reset up now working.
Looks like i found a solution to that.
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
Global, locked
Click to expand...
Click to collapse

FSB said:
I tried this today and found it would not connect.
Found this on the MI Forum, was not sure if I could do a link. Thanks DepeTT
I had to turn off PC and Phone, deleted connections, reset up now working.
Looks like i found a solution to that.
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
Global, locked
Click to expand...
Click to collapse
Had the issue on my Redmi Note 5 CN....! Luckily I have seen this topic which helped me to fix the issue....! But the settings are not sticking when changing the rom....!

abadidea said:
Had issues today, tried an alternate fix from the web.
Settings -> Install Apps -> System Launcher -> Scroll Down - Clear Data / Reset All -- Reboot and it fixed it afterwards.
Click to expand...
Click to collapse
Mi mix 2s with miui 10 global, unrooted.
This solution worked perfectly. Thanks a lot.

Riparato tethering su MI8
FSB said:
I tried this today and found it would not connect.
Found this on the MI Forum, was not sure if I could do a link. Thanks DepeTT
I had to turn off PC and Phone, deleted connections, reset up now working.
Looks like i found a solution to that.
- I used ADB
- I enabled developer options on the phone and enabled both usb debugging and the (security settings) options
- I typed:
adb shell
- The prompt should change into the phone model
- I typed
settings get global tether_dun_required
- If the result is null or 1 tethering will not work (mine was null)
- I typed
settings put global tether_dun_required 0
- I typed exit two times to go out of the shell
- Rebooted the phone
After that the tethering was working fine, both usb and wifi.
Global, locked
Click to expand...
Click to collapse
Ringrazio FSB per la soluzione.
Provata su MI8 con stesso problema : per qualche tempo ha funzionato il tethering e, poi all'occorenza, non funzionava più.
Fatto : 1. download sul PC di "minimal_adb_fastboot_1.4.3_portable" e aver
2. abilitato "opzioni sviluppatore" e poi "debug usb" e "debug usb (impostazioni di sicurezza)" sul telefono
3. collegato il telefono e dal prompt di adb seguito le istruzioni di FSB (GET per verificare il valore e PUT per impostarlo)
4. riavviato il telefono il tethering ha ricominciato a funzionare.
Grazie.

I tried the solution provided by FSB. It did worked for me but partially. I could use the hotspot for connecting my other Android device but the hotspot failed to provide connectivity to my laptop ( windows 8.1 pro).
Then, i tried changing the network setting on my laptop. I did the following.....
Go to NETWORK AND SHARING CENTRE then go to Change adapter settings then select wifi then right click then select properties then DOUBLE CLICK on Internet protocol version 4 and finally SELECT Obtain an IP address automatically . And do the same for internet protocol version 6.
Doing this helped me restore the connection on my laptop.
Hope this helps.

hi
i've done the same (settings put global tether_dun_required 0) and now works (on xioami mi 8 lite)
but i'm asking, this setting could create problem with future global miui rom updates??
many thanks

This device is locked

Hi, I'm having some problems with flashing back to MIUI Rom.
Here is my situation:
I flashed a while ago to Xiaomi.EU rom.
Everything was working pretty well but I missed the "google-way" so I decided to try the PixelExperience Rom.
I did a full wipe for installing this rom. Was pretty satisfied but suddenly the wifi stopped working.
Also the performance in games was not that good.
Next i have done a full wipe again & installed the xiaomi.eu rom.
But when I enter the installation screens of the rom Miui will notify that my device is locked.
I need to enter my mi account password but it cannot verify it because I have no internet connection on my sim (I can't enter pin-code).
I can search for wifi networks, but the screen doens't give me a keyboard to enter the wifi password.
The screens says that I can unlock my device with i.mi.com (Mi cloud).
I tried a lot of things, deleting my 'phone', turned off find device but nothing is helping.
Next i'll tried the official global dev rom. Same problems!
Is there any way to get it unlocked by a god damn webinterface?!
I'm now back at PixelExperience with a few bugs.
Not my picture but this is simular, I also get a button to connect with WIFI but can't enter password...
{
"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"
}

You can try older Xiaomi eu rom, wait for awhile for the keyboard to pop up.
JeffreyM said:
Hi, I'm having some problems with flashing back to MIUI Rom.
Here is my situation:
I flashed a while ago to Xiaomi.EU rom.
Everything was working pretty well but I missed the "google-way" so I decided to try the PixelExperience Rom.
I did a full wipe for installing this rom. Was pretty satisfied but suddenly the wifi stopped working.
Also the performance in games was not that good.
Next i have done a full wipe again & installed the xiaomi.eu rom.
But when I enter the installation screens of the rom Miui will notify that my device is locked.
I need to enter my mi account password but it cannot verify it because I have no internet connection on my sim (I can't enter pin-code).
I can search for wifi networks, but the screen doens't give me a keyboard to enter the wifi password.
The screens says that I can unlock my device with i.mi.com (Mi cloud).
I tried a lot of things, deleting my 'phone', turned off find device but nothing is helping.
Next i'll tried the official global dev rom. Same problems!
Is there any way to get it unlocked by a god damn webinterface?!
I'm now back at PixelExperience with a few bugs.
Not my picture but this is simular, I also get a button to connect with WIFI but can't enter password...
Click to expand...
Click to collapse

I fixed this problem...
I downloaded the Official China Stable fastboot version of my phone (Mi 6).
I flashed this with MiFlash.
First boot... No device is locked!
I installed the phone quickly because it was a chinese bloatware rom.
Next I flashed twrp in fastboot mode.
Booted in TWRP, Format data & copy the Xiaomi.EU version to internal storage.
After installing this rom in TWRP it booted with "Device is locked..." FUUUUUUUUUUUU
But now I was able to fill in the wifi password!
With a wifi connection you just have to type your password of your Mi account and all problems are gone!

Simple solution
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected

Something similar happened to me, from one moment to another the Wi-Fi worked, I did a full reset and when I turned it on again the device gave me it was blocked, the button opened the button and told me to enter my password I did, but it turns out that never validate apparently still with the problem of wifi, suggestion?

Enter wifi routers admin page (192.168.0.1) or similar like this. Delete wifi's password and bum ! You can connect wifi without buttons.

Thanks Bud
Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
I was having the same problem, your sugession solved it. you are a damn genius buddy :laugh::laugh:

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
This is the easiest way to solve the problem. They should fix that problem soon. It has no sense.

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
f**** genious

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
This was just amazing...
Thanks!

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
fu*king genius! You saved my life!
But still I'm curious why I had this situation. I tried to install twrp, after success fastboot flashing I rebooted my phone a Mi-recovery 3.0 appeared. So no install any kind of zip. So reboot again and this "device is locked" showed up!
Any opinions?

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
genius! thank you

i once flashed from global dev from to china dev rom.. it asked me to sign in my MI account. i typed the correct password but it still would not accept.. so i sign in micloud on PC does not work too so i decided to change the password to try again~ no luck. flashed back to miui global dev it asked to sign in too.. and then it says INVALID USER ID.. well done xiaomi~ now im locked out forever until i can provide proof of purchase to them to unlock my phone from the server. anyone has ever fix this pls help me i need to flash to stock rom and sell the phone LMAO

Hi ppl. I have similar problem with my Redmi 5 Plus phone. I used the phone one day, I activated Mi account, I made transfer data from my old Mi 3, I unlocked bootloader succesiful, and then I installed MIUI 10 (developer version). After phone is booted I got screen with Device is locked. I have full access to my Mi account via web, but when I try to unlock device it says Invalid username! There is my conversation with Xiaomi global support. Then wasn't useful for me I am using custom RR rom, but I want to back to MIUI. What I need to do?
Conversation with Xiaomi support (screenshoots from gmail):
https://www.dropbox.com/sh/utsmwszsenrhld5/AAAMEAUC4sVjR0h_csqDZHPOa?dl=0

Thank you so much, worked well. Tryed to downgrade to miui 9 from miui 10 and got phone lock. Your solution was the best

If you brick your device on the way as it happened to me... check: https://forum.xda-developers.com/showpost.php?p=77755947&postcount=11
These guys helped me unbricking my mi8 using EDL (Test Point) and Mi-flash!

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
Beauty in simplicity. Excellent mind there

THE maaaaannnnn!!!
genius...

Best solution on mi MI8. Thanks!!

Myst3t said:
I had the same tonight, first time i change my rom on my mi mix2 and found a simple solution:
Go to activate this device, and click on the "eye" to see the password you will type.
Type your wifi password here and copy it (long touch on it)
Then go to the wifi section and paste your password !
It's OK you're connected
Click to expand...
Click to collapse
you save my life,thank you so much kisses *x

[Guide] Enabling DIAG for QPST (updated)

Hi everyone, I have finally figured out how to get proper diag support on our device. This will allow us to use QPST and such.
It will be a pretty short guide as it's quite simple, but it does enable us to do a whole lot of things we couldn't do before.
Downloads
* QPST
* AsusVoLTE app
Prerequsities
* Both methods require root, at least initially. There are several threads on how to do that, so look those up if you need help.
USB method
Downloads
* Qualcomm USB drivers
Step 1
Install the drivers and QPST from above. If you've already done this from my VoLTE/VoWiFi guide there's no need to reinstall them.
Step 2
When you've done that, install the AsusVoLTE app and connect the phone to the computer and open up it up. Press the Enable DIAG button, and you should hear/see a new device attaching. This should hopefully be enough, but if not, try rebooting the phone. If that still doesn't work try the Remote method below.
Remote method
Prerequsities
* Both your computer and phone have to be connected to the same network. You may also need to allow port 2500 in your firewall.
Step 1
Start by downloading and installing QPST from the link above, no drivers or such required. If you've already done this from following my VoLTE/VoWiFi guide you can safely skip this step.
Step 2
Now run QPSTConfig.exe from the bin folder of the QPST install and wait for it to open up. Head to the IP Server tab and tick the Accept client connections box - we need to do this as we will be connecting to QPST remotely. Take a note of the Server IP Address (this should simply be the ip address of your computer), and potentially the Server Port below if you have changed it from the default value of 2500.
Step 3
Open up the AsusVoLTE app on the phone, and enter the IP address from the Server IP Address in the field, and optionally, change the port number.
After this you can simply press the Start button.
Now that you have done this, you should, momentarily, see a new port appear in QPST Configuration under the Ports tab with a Port number like COM30001 and the Phone column should hopefully say SDM855 (0). If you do see this you are good to go! You can now start exploring EFS and such.
Troubleshooting
Some people have had issues connecting to the diag port, with EfsTools from the VoLTE guide returning BadCmd and QPST not working either. If you have this problem, try restoring modem settings by running this in bootloader (adb reboot bootloader, or press volume up while rebooting):
Warning: This may cause issues with no service for some, do not run this without a full backup of all of the partitions (in particular, modemst1, modemst2, fsg and fsc) on the device!
Code:
REDACTED because people still run these commands without taking a backup
Do note that this will reset any changes you may have done (like enabling VoLTE through PDC).
Thanks to @xbamaris1` for troubleshooting this with me, and for confirming this worked!
Let me know if this has worked for you, and if you have any questions!

I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.

dennis96411 said:
I'm getting this:
Code:
ASUS_I001_1:/ # diag_socket_log -a 10.30.1.10 -p 2500
diag_socket_log: Diag_LSM_Init succeeded.
diag: In diag_register_socket_cb, registered socket callback function
diag_socket_log: Translating address: 10.30.1.10
diag_socket_log: Trying to connect to address: 10.30.1.10, port: 2500
diag_socket_log: Error calling connect: Operation already in progress, errno: 114
I'll try to restart my computer and phone. Maybe there were some remnants of tools running still.
Click to expand...
Click to collapse
I had this problem to until I realized that its network based and your phone should be connected to your WIFI (at least thats what fixed it for me).
However, Despite this, i am still not getting data from it. COM30001 from an IP of 192.168.1.211 (which is my phone) and it is still not able to browse data from QPST

Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
{
"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"
}
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.

dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update 2: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.

xbamaris1` said:
I really hope we can get QPST fully working. I'm in the same boat as you, was able to get SDM855(0) but nothing after that with QPST. Glad you got it to work though!
I really want to try enabling some LTE bands (just want two as a start, 12 / 17. And MAYBE 66.
Click to expand...
Click to collapse
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.

dennis96411 said:
Does your phone not show up as a USB device like mine? I wonder how I got it to show up. It would be nice to find out so it would be easier to use QPST.
Click to expand...
Click to collapse
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.

xbamaris1` said:
Yeah it shows up as a USB device with SDM855(0) as the device. I actually had a different diagnostic driver that was the ANDROID Diag mode at some point, not sure if that was useful at all, but still no QPST data. Not sure how I managed to get the Qualcomm ANDROID Diag to show up (The exact interface / driver that showed up was: Qualcomm HS-USB Android DIAG 901D) it just magically appeared after trying to change the sys.usb.config at some point. Haven't been able to recreate it and not sure of the significance of it. But I believe QPST still registered it.
Click to expand...
Click to collapse
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":

dennis96411 said:
Try these drivers: https://androidfilehost.com/?fid=11410963190603864074
This is what mine shows up as after running "setprop sys.usb.diag2 1":
Click to expand...
Click to collapse
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.

xbamaris1` said:
Thats what I have now, and usually do have when I enable it. I just thought it was strange when I suddenly got that other interface to connect. Again, not sure the significance of what I had since QPST still didn't work. But just was something I came across while trying to tinker.
Click to expand...
Click to collapse
Which version of QPST Configuration do you have? This is mine.

dennis96411 said:
Wait, I think I got it. I had to use the USB tethering feature of my phone to bypass whatever my router's doing. I also had to run ipconfig to grab the IP address that was assigned to my computer, and manually set that in the "Use specified IP address" box.
Is this IP-based method necessary? I can already see my phone in normal USB mode.
Update: It turns out I didn't need the IP-based method as my phone's already seen through USB. I'm not sure how I managed that.
Click to expand...
Click to collapse
It's not necessary, no - if you get it to show up in usb you won't need to do any of this. I could, however, never get the phone to connect in usb mode - it just shows as No phone.
I will try those drivers you posted and update the guide.

I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2

HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
Oh did those drivers make a difference for you?

HomerSp said:
I've updated the guide in the first post - it now has both the usb method and remote method. I managed to get diag working through USB, but it seems to be a bit fiddly and sometimes required that I reboot the phone before it started working.
If you don't want to use the app to enable diag you can simply run this in a root shell:
setprop sys.usb.diag 2
Click to expand...
Click to collapse
How to change imei with EFS

QPST via remote using your guide worked for me. I am able to use EFS Explorer. Thank you @HomerSp!

Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.

XavierBK said:
Will doing this, to eventually turn on VoLTE and VoWiFi, lock me out of Google Pay and similar services?
Sorry if it's a stupid question, I've not toyed around with rooting since it began disabling pay and bank features that I have enjoyed using.
Click to expand...
Click to collapse
Magisk (the root method) hides itself from bank apps and such, but you can do a SafetyNet check in the magisk manager app, and if that passes so you should be good to go.
Only thing you won't be able to get with the bootloader unlocked is HD video in Netflix and Amazon video.

This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?

ChronoReverse said:
This is very interesting. I read in another thread that with nvram access you can try to enable bands (but it may not work). Is this to the point where that can be tried?
Click to expand...
Click to collapse
Yes indeed, but we have yet to find a way to enable additional bands. We are working on it though, so hopefully we'll have something soon.

Hi, can we use QPST to unlock LTE band on 8G/128G version?

How To Guide Enable VoLTE and VoWifi on OOS 13 without root

Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet. (Edit 27/06/2023: new updated apk available here)
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings

Not works for me... I have the italian operator PosteMobile

Doesn't work for me... I tried to use a custom ROM so I could have VoWiFi, but I felt something was off. I got back to OOS13 on my OnePlus 8 Pro (IN2023) with AT&T and tried this method but no success...

omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh. You should see somewhat like "Shizuku is running" at your phone.
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Thank you! It worked on a LE2121 with Android 13!

Update:
I just updated to 13.1 and lost VoLTE. Re-did the steps and got it back.

Added an edit to step 5 in OP, as with 13.1 I had to uncheck "Disable permission monitoring" in developer settings).

It's not work. Oneplus 10 pro. Oxygen os 13.1

yasador said:
It's not work. Oneplus 10 pro. Oxygen os 13.1
Click to expand...
Click to collapse
Need to be more specific.....

Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please

momiloco said:
Hi,
When I put in the command
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.
on my PC, I get the following error:
sh: /sdcard/Android/data/moe.shizuku.privileged.api/start.sh.: No such file or directory
I tried toggling disable permission monitoring but still getting the same result
Help please
Click to expand...
Click to collapse
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.

omar302 said:
If you are using Windows PowerShell, you might need to .\ Infront of the command. it would be like this:
.\adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Another suggestion, I think the command should be without the period "." at the end. I just edited the original post to remove it.
Click to expand...
Click to collapse
Thanks bro.
I tried like what you suggested but still the same error.
Managed to do it using wireless USB debugging. Much easier.
Thanks

omar302 said:
Thanks to @caracciola for posting this on the OnePlus 7 Pro forum (link to original guide), the same guide worked on my OnePlus 9 Pro (EU - LE2123 - F75 update, also on 13.1) to enable VoWifi (wifi Calling).
I am just rewording the steps here to make them clearer for me:
Note 1: If you have 2 sims, disable the second sim and proceed. After finishing with the first sim, enable the second sim and disable the first sim then repeat the steps from step 3.
Note 2: Make sure to disable permission monitoring in Developer settings.
Install Shizuku app from playstore: Shizuku - Apps on Google Play
Download "pixel ims" from the attachments of original post to your phone (direct link). Exctract the APK and install it, but do not open it yet.
Open the Start shizuku app on your phone.
Connect your phone to you PC with USB DEBUGGING enabled.
Run the ADB command on your PC: adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
You should see something like "Shizuku is running" at your phone. (Edit: might need to uncheck "Disable permission monitoring" in developer settings).
While the shizuku app is running now open the pixel ims app.
Tap "Allow all the time" when seeing prompt asking for Shizuku permission.
Press the button "Enable VoLTE" to enable VoLTE in Pixel IMS
Reboot your phone... Voilà now you have the switches for VoLTE & VoWifi on the settings
Click to expand...
Click to collapse
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?

kmahesh said:
Does the above step exclusively for Pixel phone? I recently bought Oneplus 11r 5g from India and living in US. My phone isn't working. Tmobile is telling me that VoLTE option should be enabled. Question is can I apply the above steps on my phone without bricking it?
Click to expand...
Click to collapse
I think you missed reading the first paragraph. It worked for me on my OnePlus 9 Pro on OOS 13 & 13.1. I am using a Tello (US) line which is basically T-Mobile and got VoWifi to work using these steps.

Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP

kmahesh said:
Actually I read that and I thought 11r might be different from 9Pro. Nevertheless, I gave a shot at this. I got to the place where I need to enable volte but it is greyed out and none of the other options are responding on that screen. See the screenshot. Am I missing something?
Interestingly you seem have owned same sets of phones I owned in the past too - HTC, 7 Pro etc
UPDATE - I downloaded the latest version of Pixel IMS app v1.2.6 - but has no effect on Oneplus 11r & Tmobile.
PLEASE HELP
Click to expand...
Click to collapse
It seems that it doesn't work for all SIM cards. I also tried the same with a 1+ 7 Pro using another SIM and it did not work. Maybe I'll try with the Tello SIM on the 7 Pro just to test if it's an issue with the phone or SIM.

Thanks Omar for trying. All I am trying to find out (1) Is my phone the culprit (or) my T-Mobile is the culprit (2) Is there a solution (with or without rooting) to make this work for USA carriers?
Any help would be appreciated.
Thanks
Mahesh

Hello everybody. I have Oneplus 9R OOS 13.0 Android 13. I did everything according to the instructions using wifi debugging. The volte switch slider has become active. However, when making a call, the phone still falls into the H+, H or 3G network. I have 2 SIM cards installed, before starting the algorithm, I did not deactivate the second one. Could this be a problem? If so, what would you recommend to do in this case?
I tested SIM card 1 used for calls and the Internet in another device, Volte works on it.

Updated to LE2123_13.1.0.580(EX01) and off course lost VoWifi, however, repeating the steps re-enabled it.
Also found an updated Pixel IMS apk (link to download) that has more options when enabling VoLTE or VoWifi.