Develop Bugs

[Q] Cant access developer options.

Hi,
I have a very strange issue and I am hoping that someone has a solution to this problem.
The tablet SM-T705 came with Build number KOT49H.T705XXU1ANG2 out of the box and it is not upgradeable.
Recently I bought a samsung galaxy tab s t705, The first thing that I wanted to do is root my new toy.
Obviously the first step in the process is to enable USB Debugging but it is a no go !
Here is what I am doing:
Settings > General > About device , Then tap the Build number 7 times.
Once I got the message that the developer mode is now enabled, I go back to the General tab but the "Developer options" are nowhere to be found.
I installed Nova launcher and tried to crate a shortcut for for the "Developer options" but all it does is throw me to the General settings tab in the settings.
I tried to factory reset the device and repeat the process but not luck.
I even tried some apps that are just shortcuts for the Developer options but it didn't help.
Any suggestions ?
I really need root (cant stand all the bloatware).
Thank you for your help !
/
16k

16k said:
Hi,
I have a very strange issue and I am hoping that someone has a solution to this problem.
The tablet SM-T705 came with Build number KOT49H.T705XXU1ANG2 out of the box and it is not upgradeable.
Recently I bought a samsung galaxy tab s t705, The first thing that I wanted to do is root my new toy.
Obviously the first step in the process is to enable USB Debugging but it is a no go !
Here is what I am doing:
Settings > General > About device , Then tap the Build number 7 times.
Once I got the message that the developer mode is now enabled, I go back to the General tab but the "Developer options" are nowhere to be found.
I installed Nova launcher and tried to crate a shortcut for for the "Developer options" but all it does is throw me to the General settings tab in the settings.
I tried to factory reset the device and repeat the process but not luck.
I even tried some apps that are just shortcuts for the Developer options but it didn't help.
Any suggestions ?
I really need root (cant stand all the bloatware).
Thank you for your help !
/
16k
Click to expand...
Click to collapse
Your on an old firmware, so that means you'll need to upgrade. Download mode does not need usb debugging. Simply put your device in download mode, flash newer firmware with odin, then root with cfautoroot. USB debugging is only needed to connect to PC while device is on. Hope this helps!

Thank!
DUHAsianSKILLZ said:
Your on an old firmware, so that means you'll need to upgrade. Download mode does not need usb debugging. Simply put your device in download mode, flash newer firmware with odin, then root with cfautoroot. USB debugging is only needed to connect to PC while device is on. Hope this helps!
Click to expand...
Click to collapse
This is the latest version based on Samsung's website and I really need to get usb debug going (not only for root).
Thanks for the help.

Which region is the device?

Samsung A7 2017 lock pattern cannot be bypassed, newly updated to official firmware

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"
}

USB-Debugging mode

Dear Community,
I am currently unable to activate the USB debugging mode on my unrooted Samsung Galaxy S9.
I have activated the developer mode.
USB debugging has alywasy been enabled in the past.
Since I wanted to use Helium, I double-checked that it is activated . but it is not.
The option is grayed out and there is a message saying "USB-Edugging mode will start as soon as usb is connected (translated from german)".
No matter waht I tried, nothing worked out.
Can you please help me out?
Best regards
Bacardi Man

I've noticed on older Samsung devices that if OEM Unlock is enabled then that will grey out USB debugging. The fix was to disable OEM unlock and reboot. Of course, if you're waiting on the 7 day thing to root that may reset the timer. I'm not sure about that since root will never be an option on my US version.

Thank you for the hint, but OEM unlock isn't activated and has never been as I am using Secure Folder (Knox).
Any other suggestions?

Bacardi Man said:
Thank you for the hint, but OEM unlock isn't activated and has never been as I am using Secure Folder (Knox).
Any other suggestions?
Click to expand...
Click to collapse
Probably won't help but worth a shot clearing CACHE from recovery

*Detection* said:
Probably won't help but worth a shot clearing CACHE from recovery
Click to expand...
Click to collapse
Good idea, but that did not work out either.
Am I really the only person with that problem?

Bacardi Man said:
Good idea, but that did not work out either.
Am I really the only person with that problem?
Click to expand...
Click to collapse
Could it be because of knox secure folder?

Tel864 said:
Could it be because of knox secure folder?
Click to expand...
Click to collapse
Maybe, but wouldn't that be made official somewhere?
I never red about it.

Maybe too simple but in Developer Options>USB configuration do you have MTP selected?

Tel864 said:
Maybe too simple but in Developer Options>USB configuration do you have MTP selected?
Click to expand...
Click to collapse
Yes, MTP Mode is selected.

Bacardi Man said:
Maybe, but wouldn't that be made official somewhere?
I never red about it.
Click to expand...
Click to collapse
Looks like it is probably KNOX causing it
https://seap.samsung.com/content/why-usb-debugging-mode-disabled-knox
https://seap.samsung.com/forum-topic/can-i-use-usb-debugging-mode-device-running-knox
Solution 3: Use USB debugging mode on a device running KNOX (For Samsung )
By default, My KNOX and KNOX Premium (through CellWe EMM) disables USB debugging on a device when it creates a secure container.
IT admins KNOX Premium (through CellWe EMM) can later enable USB debugging mode through the Admin Portal: Simply select Policies > Mobile > Samsung KNOX Device Settings > Restrictions Settings > Permit USB debugging = Yes. On the device, you need to go to Android Settings, enable Developer options, then enable USB debugging. The exact steps vary depending on your Android version, as described in Using Hardware Devices.
If you are using My KNOX, you cannot enable USB debugging mode while the container is installed. Unfortunately, you have to root your device and uninstall 'My KNOX' (enter Knox, chose Knox settings app -> More Information -> unistall Knox.), then you will be able to turn on USB debugging mode.
https://www.syncios.com/android/fix-usb-debugging-grey-out.html

USB debugging mode issue with several apps

Sorry for my English.
There are a few apps where you are not allowed to use USB debugging mode while working with them (Fate/Grand Order, Fortnite, some banking apps, etc).
Two days ago I've run into a problem with Fate/Grand Order. I turned on the debug mode and after that turned it off. However, the app still throws an error about USB debugging. The support team said that I should contact my manufacturer. I've found a theme on Xiaomi forum (can't post a link because of anti-spam) about this problem. Some users with POCO F1 have this problem too.
The only solution is factory reset.
Does anyone have the same problem?

ArianEpsilon said:
Sorry for my English.
There are a few apps where you are not allowed to use USB debugging mode while working with them (Fate/Grand Order, Fortnite, some banking apps, etc).
Two days ago I've run into a problem with Fate/Grand Order. I turned on the debug mode and after that turned it off. However, the app still throws an error about USB debugging. The support team said that I should contact my manufacturer. I've found a theme on Xiaomi forum (can't post a link because of anti-spam) about this problem. Some users with POCO F1 have this problem too.
The only solution is factory reset.
Does anyone have the same problem?
Click to expand...
Click to collapse
clear apps data and reboot ?? plug cable in to pc and toggle the settings??

boe323 said:
clear apps data and reboot ?? plug cable in to pc and toggle the settings??
Click to expand...
Click to collapse
I've tried this but nothing helped. I flashed 10.0.3.0 ROM and now everything works perfectly even after enabling/disabling USB debugging mode.
My friend also has Mi A2 Lite so I asked him to check this bug. He installed the game (he was using ROM 10.0.3.0) and after turning on and off debug mode everything worked fine. Then I asked him to install new 10.0.4.0 firmware and check this bug again. He got USB debug error even after disabling USB debugging.
So new February patch makes unable to play some games (such as Fate/Grand Order, Fortnite and so on) where it's not allowed to use USB debugging.

ArianEpsilon said:
Sorry for my English.
There are a few apps where you are not allowed to use USB debugging mode while working with them (Fate/Grand Order, Fortnite, some banking apps, etc).
Two days ago I've run into a problem with Fate/Grand Order. I turned on the debug mode and after that turned it off. However, the app still throws an error about USB debugging. The support team said that I should contact my manufacturer. I've found a theme on Xiaomi forum (can't post a link because of anti-spam) about this problem. Some users with POCO F1 have this problem too.
The only solution is factory reset.
Does anyone have the same problem?
Click to expand...
Click to collapse
You need to disable developer options for fortnite to work!I'm pretty sure that the other apps also require you to disable developer options

gz26 said:
You need to disable developer options for fortnite to work!I'm pretty sure that the other apps also require you to disable developer options
Click to expand...
Click to collapse
I know, as I said earlier, it doesn't work. If you try to enable and disable USB debug for the first time on 10.0.4.0 you will get an error about USB debug.
On 10.0.3.0 everything works fine. Seems USB debugging in 10.0.4.0 firmware is kinda broken. All applications detect it as turned on.

ArianEpsilon said:
Sorry for my English.
There are a few apps where you are not allowed to use USB debugging mode while working with them (Fate/Grand Order, Fortnite, some banking apps, etc).
Two days ago I've run into a problem with Fate/Grand Order. I turned on the debug mode and after that turned it off. However, the app still throws an error about USB debugging. The support team said that I should contact my manufacturer. I've found a theme on Xiaomi forum (can't post a link because of anti-spam) about this problem. Some users with POCO F1 have this problem too.
The only solution is factory reset.
Does anyone have the same problem?
Click to expand...
Click to collapse
You can unable it in Dev options.
Btw you can't run Fortnite on Mi A2 Lite, check sys requirements for the game.

wynix black said:
You can unable it in Dev options.
Btw you can't run Fortnite on Mi A2 Lite, check sys requirements for the game.
Click to expand...
Click to collapse
If I disable it nothing will change. There is a bug in 10.0.4.0 firmware. USB debugging doesn't turn off completely. I'm sorry, but did you even read my message?

Ok, I know 3 people who have the same problem. Does anyone here have the same problem with 10.0.4.0?

[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?