Related
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
Hi friends,
this is my first post here and thanks a lot to whom paying time to answer my questions.
I am having trouble with Samsung A7 2017. My wife always uses fingerprint for unlocking her phone. 2 or 3 days ago (~20.01.2018) she has started an official regular update and it finished normally. But after a restart, the phone gave a message that at least once the phone should be opened with the unlock pattern. Both i and my wife does not know or at least could not enter the correct pattern. So, i talked to a samsung call center person, and she asked me if we have any samsung account working on that phone but unfortunately we do not have one. She told me that more probably the data on the phone would have to be erased in samsung authorized technical service.
Until then, i did not have any experience about android technically, but i am now trying to understand what booting, TWRP, CWM, odin is meaning in terms of android running phone. Actually i am an electronics engineer, i even develop some basic applications on android but this kind of informations are completely different and new to me.
The only important point is that I REALLY DO NOT WANT ANY DATA LOSS, since i have many memories, pictures, videos on that phone. Please do not get angry with me for not backing up earlier, because i am already very sorry on that and angry with myself.
Anyway, i tried following but could not have success.
1. The phone's "developer options" menu is not activated, thus "USB debug" option is also unchecked. We do not have any chance for changing this because we are unable to bypass the pattern lock screen. So as i guess ADB commands are of no use. If this information is not true please explain me how i can proceed since i do not have much information.
2. I restarted the phone, by pressing "VolumeDown + Home + Power" buttons and Downloading mode appeared on the screen. I ran the Odin (latest versions - do not know exactly since i tried many) software on my PC and tried to download TWRP on the phone but failed each time. Phone gave the massage telling about "... FRP lock". I guess this is due to a lock under developer options (something like ... OEM lock). So i could not install TWRP.
Again if my knowledge is false please tell me the true way or right information.
3. I had an idea on creating a bootable SD card so that it will boot from it and thus giving me the opportunity for installing TWRP. But i could not find much information on that.
Please help me find a suitable solution. I am actually not interested in rooting the device or installing TWRP and in fact i do not want my device warranty voided. But my first priority is extracting safely my data from the phone. So if i need to root the phone to get them it is not a problem even if the varranty vanishes. Being able to bypass the lock screen is a sufficient solution for me now but i do not know how. So please direct me in a best and simplest way and i, as a newbie, will try to understand and search what you advice with my greatest effort.
Thank you all in advance & best wishes
Tankut (Elect. Eng.)
Unfortunately I don't think that there is any way to hack your phone with these conditions... The only think I can tell you is that you can factory reset your phone without paying anyone just from the downloading mode
Didn't Google photos automatically backup your pics and videos?
Thanks for your replies.
I actually do not know if google automatically backup all these content but i guess we did not setup such a back up task. But i will search for it. By the way, there was a google account set on the phone and google's "find my moile" app can reach the phone by locking it or ring the phone. Unfortunately it can not unlock the phone. I am just writing these to give additional info which can direct you all of some useful approach.
Another point is "VolumeUP + HOME + Power" menu has some options. These are:
"Reboot system now" , "Reboot to bootloader" , "Apply update from ADB" , "Apply update from SD card" , "Wipe data / factory reset" , "Wipe cache partition" , "Mount /system" , "View recovery logs" , "Run graphcs test" , "Power off"
Are none of these options, especially "Apply update from ADB" or "Apply update from SD card" , of no use? Can something be done with these? For example when i select "Apply update from ADB" the phone gives the message "Now send the package you want to apply to the device with "adb sideload <filename>" ... and waits for some time. Later "Timed out waiting for package" appears on the screen.
In addition to my previous post, i searched for possible backup of photos and videos on google account and found some, it is a nice news. But my wife was usully using CandyCam application on the phone and unfortunately i could not find any photos or videos bakup taken by CandyCam. I could not find a way for adding the CandyCam photo or video folders in the google backup task via google account remotely(that is outside the phone)(If only i had done it before on the phone itself while everything is fine). Do you think it is possible? Thanks.
hayat_bilgisi said:
Thanks for your replies.
I actually do not know if google automatically backup all these content but i guess we did not setup such a back up task. But i will search for it. By the way, there was a google account set on the phone and google's "find my moile" app can reach the phone by locking it or ring the phone. Unfortunately it can not unlock the phone. I am just writing these to give additional info which can direct you all of some useful approach.
Another point is "VolumeUP + HOME + Power" menu has some options. These are:
"Reboot system now" , "Reboot to bootloader" , "Apply update from ADB" , "Apply update from SD card" , "Wipe data / factory reset" , "Wipe cache partition" , "Mount /system" , "View recovery logs" , "Run graphcs test" , "Power off"
Are none of these options, especially "Apply update from ADB" or "Apply update from SD card" , of no use? Can something be done with these? For example when i select "Apply update from ADB" the phone gives the message "Now send the package you want to apply to the device with "adb sideload <filename>" ... and waits for some time. Later "Timed out waiting for package" appears on the screen.
Click to expand...
Click to collapse
Stock recovery is of no use unless you are prepared to wipe/reset the device.
Are you sure you can't use Google's find my mobile?
As far as I'm aware you can reset the lock to a password which you then use on the device. You may have to wait a while for this to happen and reboot.
Also if there is a Samsung account on the device you can unlock with that.
Have you tried entering the wrong pin around 15 times (I think)?
This used to allow you to use Forgot password and enter your Google log in details instead.
Lastly there is a possible way with ADB.
When i firstly used google's find my mobile, i really entered a pin number(temporary password) which i hoped that i would enter it on the phone and the lock would just disappear. But the phone just continued opening with the pattern lock which we already could not pass. During our tries "find my mobile" was able to lock the device, on the screen we entered a symbolic "lost phone" message, we are also able to ring the phone via this application - All of these worked, but pattern lock is still there. After that first attempt, google's password asking or password entering screen(in PC) has not appeared again. So, totally i did not see any kind of password entrance screen on the phone after that samsung's official update.
We did not count but tried many patterns but each time the phone just messaged us to retry after 4 min, 10 min , 30 min and so on... So nothing changed. I agree that after some retries, it should give the user a chance for forgetting the password and trying another method for unlocking the phone but it never show any other than the pattern lock. I wonder why it does not trust fingerprint as my wife was always using. Thanks anyway for sharing your opinions.
I really wonder if this phone's memory should really be wiped out and there is no other way for unlocking it!! Warranty void is not a problem, i just want to see the photos back again. They all belong to my 1-year old son and his birth approximately. So i really do not want to lose anything. I hope you understand my feelings. To tell you the truth, i was just planning a complete backup of all the memories in one place. But actually, i would not guess such a disaster would happen to me. So please do not get angry with me just try to understand me. Thanks again for spending your valuable time on my problem.
hayat_bilgisi said:
When i firstly used google's find my mobile, i really entered a pin number(temporary password) which i hoped that i would enter it on the phone and the lock would just disappear. But the phone just continued opening with the pattern lock which we already could not pass. During our tries "find my mobile" was able to lock the device, on the screen we entered a symbolic "lost phone" message, we are also able to ring the phone via this application - All of these worked, but pattern lock is still there. After that first attempt, google's password asking or password entering screen(in PC) has not appeared again. So, totally i did not see any kind of password entrance screen on the phone after that samsung's official update.
We did not count but tried many patterns but each time the phone just messaged us to retry after 4 min, 10 min , 30 min and so on... So nothing changed. I agree that after some retries, it should give the user a chance for forgetting the password and trying another method for unlocking the phone but it never show any other than the pattern lock. I wonder why it does not trust fingerprint as my wife was always using. Thanks anyway for sharing your opinions.
I really wonder if this phone's memory should really be wiped out and there is no other way for unlocking it!! Warranty void is not a problem, i just want to see the photos back again. They all belong to my 1-year old son and his birth approximately. So i really do not want to lose anything. I hope you understand my feelings. To tell you the truth, i was just planning a complete backup of all the memories in one place. But actually, i would not guess such a disaster would happen to me. So please do not get angry with me just try to understand me. Thanks again for spending your valuable time on my problem.
Click to expand...
Click to collapse
I fully understand your predicament. I would be the same.
I take it there is no Samsung account on the device?
I have helped someone remove the pattern lock once before, but this was using a custom recovery which you cannot use.
There is a possibie way with ADB. . However it depends on the firmware you are currently running.
Have you simply tried just reverting the firmware?
ashyx said:
I fully understand your predicament. I would be the same.
I take it there is no Samsung account on the device?
I have helped someone remove the pattern lock once before, but this was using a custom recovery which you cannot use.
There is a possibie way with ADB. . However it depends on the firmware you are currently running.
Have you simply tried just reverting the firmware?
Click to expand...
Click to collapse
Dear ashyx,
Thanks for your reply,
Yes, unfortunately there is no samsung account on the device.
At this moment i think the device has the latest official firmware(by saying firmware, i think you mean what we install or upgrade as the operating system) which samsung published, because my wife accepted the install just a few days ago(about 20.01.2018). I do not know what this upgrade consists of or what version it is. But is it possible to revert back to previous or former releases of firmware in my situation? Can you explain me shortly how i can do this briefly? And of course, if this works - e.i. if i reverted back to a previous firmware, do you think is it going to be useful in my situation?
How should i proceed? Thanks
By the way, i should say that i already downloaded "Android-Multi-Tools-v1.02b.rar" on my PC and in CMD window i ran the software. I connected the phone to the PC and selected "Apply update from ADB" on the phone in recovery mode. As soon as i select "Apply update from ADB" on the phone, my Windows 10 x64 PC gives a sound like "a new device connected or found". You know, it installs the drivers for the device in device manager on PC. I did not install any more driver and left it as it is. Anyway, on android multi tools software, "ADB devices" command did not show me any device connected. I think it is due to developer options not being activated on the phone. All of the tutorials i watched on youtube say that developer options should be activated before using adb commands.
I just wanted to tell about my experiences. But i did not tried "sideload" download. Maybe it is different than what i mentioned above.
What about fastboot mode? One of the tutorial was saying, in order to use adb, i should activate developer options or set the phone to fastboot mode. I could not find any info on how to set fastboot mode?
What about "Apply update from SD card" option on the phone? Can this also be used and be useful for me? Actually this seems more and more possible to me. But i do not know which way to take, which software to install first, second etc..
I know too much questions, many apologizes on this.
hayat_bilgisi said:
By the way, i should say that i already downloaded "Android-Multi-Tools-v1.02b.rar" on my PC and in CMD window i ran the software. I connected the phone to the PC and selected "Apply update from ADB" on the phone in recovery mode. As soon as i select "Apply update from ADB" on the phone, my Windows 10 x64 PC gives a sound like "a new device connected or found". You know, it installs the drivers for the device in device manager on PC. I did not install any more driver and left it as it is. Anyway, on android multi tools software, "ADB devices" command did not show me any device connected. I think it is due to developer options not being activated on the phone. All of the tutorials i watched on youtube say that developer options should be activated before using adb commands.
I just wanted to tell about my experiences. But i did not tried "sideload" download. Maybe it is different than what i mentioned above.
What about fastboot mode? One of the tutorial was saying, in order to use adb, i should activate developer options or set the phone to fastboot mode. I could not find any info on how to set fastboot mode?
What about "Apply update from SD card" option on the phone? Can this also be used and be useful for me? Actually this seems more and more possible to me. But i do not know which way to take, which software to install first, second etc..
I know too much questions, many apologizes on this.
Click to expand...
Click to collapse
Forget about recovery its useless for anything other than official updates or resetting the device.
What build number does it state in recovery?
ashyx said:
Forget about recovery its useless for anything other than official updates or resetting the device.
What build number does it state in recovery?
Click to expand...
Click to collapse
Here is the recovery screen of my A7 2017
{
"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"
}
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
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?
Hi there,
I normally don't make threads, post comments, etc. I've been into modding devices and changing things for some time now, however. I was annoyed that AT&T decided that they're either not going to release Android 12 or they're being slow and lazy, so I did what I used to do and manually updated. Here's how I did it. Sorry in advance if this is poorly formatted.
This guide is aimed towards people who are new in this field and/or just want to update already. Tested on AT&T variant of the S20 FE.
Note: I only have a Windows machine. This guide REQUIRES the use of a computer at the least, and this is written from the perspective of Windows users. I cannot help you if you are on MacOS or Linux.
1. Prep work
Download Frija 1.4.4. In the model text field, enter SM-G781U. In the CSC field, enter a carrier code which supports your carriers network. For example, AT&T uses GSM, so does T-Mobile. AT&T hasn't released Android 12 yet but T-Mobile has, so I used T-Mobile. Here's a few major carrier CSC codes.
VZW - Verizon Wireless
ATT - AT&T
TMB - T-Mobile
Once you've done the above, leave the "Auto" setting ticked and click on "Check Update". Frija should auto-fill ther Version, Size, OS, and Filename fields when it sees the update from the other carrier. Click Download.
Frija is now downloading Android 12 via the other carrier. This will take some time to complete.
While Frija downloads Android 12, head over to this thread and download Odin V3.14.1.zip. I wouldn't recommend the patched version, just use the normal one. Unzip this to somewhere you'll remember and in its own folder for organization purposes. You'll need it later.
Next, unlock your phone, remove your Pin, Fingerprints, Google account(s), and Samsung account, as they could hinder your ability to unlock your phone until the process is complete later on, as I learned.
If you have the Secure Folder enabled and use it, back up all data in it now. Do the same for anything you care about on internal storage. It will likely be lost otherwise.
2. Installation
I will reiterate once more, back up any data on Internal Storage and Secure Folder that you care about or it may be lost. I am not responsible for lost data. I will not help you if you didn't read and lost your data.
With that in mind, we'll begin with the installation process of Android 12. We'll do this as simply as I know how, and how I've done installs like this for years. You'll need a USB-C cable that's capable of Data transport. The one that came in the box should work fine, but so should most other cables. Basically, if your computer can see your phone, you're good.
Unlock your device, head down to About Phone -> Software Information and tap the build number until Developer Mode is enabled. It may ask for your pin/passcode/pattern if you haven't removed those yet.
If you don't know how to use ADB, you can enter Download mode via hardware keys. Please Google this.
Go back to the main settings screen, scroll down past what you thought was the end, and tap Developer Options. Enable USB Debugging and close settings. Connect your device to your computer, and allow the USB Debugging prompt making sure to tick Always Allow. Open a Command Prompt with ADB access and type "adb reboot download". This will immediately reboot your device to Odin Download Mode.
From here, open Odin, which you downloaded above. Unzip the file Frija downloaded to the same folder as Odin for organization. You'll end up with 6 files, each beginning with an abbreviation. You will only need 4 of these, they are as follows:
AP_
BL_
CP_
CSC_OYN_
You will not need the files beginning with HOME or USERDATA.
Within Odin, click the BL button. Select the file beginning with BL_. Then click the AP button, and select the file beginning with AP_, and so on. Odin will "verify" these files as you select them, and may appear unresponsive for some, in particular the AP_ file may take some time to verify. If you receive a not responding prompt from Windows, click wait.
Once all 4 files are selected, your phone is in Download mode, and Odin sees your phone (shown in the ID:COM field), press Start. This will now flash Android 12 to your device. This will take some time. Do not unplug your device until this process is complete! Doing so could result in a soft (or possibly hard) brick! When Odin completes the flash, you'll first see it say "RESET" then "PASS!". At the end, Odin should look something 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"
}
At this point, your device will now reboot. It should reboot straight into recovery, where it is now advised to Wipe Cache Partition, then Wipe Data/Factory Reset. You can use the volume keys to navigate the menu, and the power button to select. If you haven't backed up your data yet, this will be your last chance to do so, and you can reboot to Android by selecting the Reboot option at the top.
Failing to Wipe Cache and Factory Reset will most likely result in broken features, including but not limited to the ability to recieve Calls, Texts, use Mobile Data, or change your passcode/fingerprints.
Once you've finished Wiping Cache and Factory Resetting, you can reboot your device. Android will take some time to boot, and when it does you'll be prompted with your carriers boot screen, followed by the initial setup wizard for Android 12.
At this time, you've completed the process. Android 12 is installed and all functionality should be there. You can now restore your data from the backups you made and continue about your day with Android 12.
Hope this helped.
This is great. Did you lose any functionality like wifi calling or tethering?