Database Users

Asus Zenfone 3 ZE520KL - connect to QPST

Hello,
I would like to unlock Band 20 on my Tw Phone to be used in Europe.
THe Phone is successfully rooted and Superuser installed.
I have tried to connect my ZE520KL to PC with QPST and QXDM, because I would like to unlock the Band 20.
I have tried:
Device is rooted (follow this forum)
adb Shell / SU / setprop sys.usb.config diag,adb -> and confirmed the status is diag mode
Install Qualcomm USB driver (shown in Windows 10 Device Manager)
-> but QPST do not find any Phone or other USB device
Before this, I have also tried Signal Guru, which display Band 20, and I can lock it,
but the phone do not connect to any LTE band.
May I ask for any recommendations?
Is there any alternative way to unlock Band 20?
Thank you.

Take a look at this thread to start with.
I'm interested in this as well but haven't had any luck. From what I've read, it looks like its more than just nv values in 6828/6829 that block it from working, possibly hardware along with some other encrypted values that once you change seem to break all signal for the phone.

Hello, thankyou for the link.
I have tried it before without success.
Diag mode through adb works, but when i run the script to connect via the Qualcomm driver,
Adb closes (back to promt), but Qpst is still not finding any device.
Regarding Signal Guru: after root etc. I have installed signal guru, and the added Band 20, as it was not shown in original list. Now, when i lock phone to band 20 or lte only, the app tries to test but without any signal and then always immedeately switches to GSM back.
Any othe way i can try?

wang1chung said:
Take a look at this thread to start with.
I'm interested in this as well but haven't had any luck. From what I've read, it looks like its more than just nv values in 6828/6829 that block it from working, possibly hardware along with some other encrypted values that once you change seem to break all signal for the phone.
Click to expand...
Click to collapse
Hi Wang1Chung (Nihau
Did you try to install other custom rom, e.g. for Nougat (I am still using Marshmellow),
if this can help to solve to unlock Band 20?
I am still trying to connect my phone to QPST, one question here:
in the past, my Win10 Laptop detected the Zenfone3 as "other Device" and "USB Controller",
and today I installed one other driver (from Xiaomi Mi5) for Qualcomm, now the device manager
shows the phone at "Modems".
Does this mean, my Laptop sees the phone, and the driver works?
In this case I consider maybe by diag mode is not ok. -> How can I check diag mode is running?
I use ADB Shell with setprop, and in properties it shows "sys.usb.config diag,adb", therefore it should be in diag mode, right?
Is there any code I can put phone to diag mode (Just to verify it is not this issue)?
Thank you!

@Ser71MB1
I didn't try any other roms as there weren't many options when I tried.
I think Windows 10 is your issue. Try running Windows 7 32bit and force windows to use the driver that QPST can find that I mentioned in the previous thread. I think remember reading people had issues with getting QPST to work in windows 10.
From what I remember, with my phone plugged in to my computer, when I successfully enabled diag mode, my phone disconnected and then reconnected with a difference driver....is yours doing that?

Activate USB Debugging

Hello Everyone!
Can somebody inform me on how to activate USB debugging when the screen is locked with a pin and the phone has stock software? Samsung phone with Nougat SW.

...
I have gotten this far with my windows 10 laptop which has adb tools installed:
Boot the phone the phone into Recovery Mode.
Select System Mount
Connect to PC and open CMD and change folder path where adb tools is located.
type adb devices in terminal
Now, the issue is that I see is a number followed by "unauthorized". I am trying to use commands such as adb shell, but seems like I am not allowed? I'm assuming it's because the phone is not USB Debug Enabled. I have a different phone which has USB Debug Enabled and adb shell commands are working perfectly. Any way to use shell commands or work arounds? Thanks in advance!

It is not possible to activate Debugging Mode with a locked screen. AFAIK it never was and it never will. And this is good as it is.
RossTeagan said:
3. Boot your phone into ClockworkMod Recovery, by pressing and holding the Power Button + Home Button + Volume Up or Down, depending on your phone
[/url]
Click to expand...
Click to collapse
Why or even HOW should he have ClockworkMod installed? your guide also is for making a Backup out of cwm when the touch is broken and not for activating debug mode

jaannnis said:
It is not possible to activate Debugging Mode with a locked screen. AFAIK it never was and it never will. And this is good as it is.
Why or even HOW should he have ClockworkMod installed? your guide also is for making a Backup out of cwm when the touch is broken and not for activating debug mode
Click to expand...
Click to collapse
Sorry, I thought it would help you...

Windows 10 won't Recognize my Phone in Fastboot Mode but ADB Is working

Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk

There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.

madbat99 said:
There's no trick, it just works. I have Windows 10 64 bit as well and no issues. Maybe you need to update your platform tools (adb and fastboot). Using old ones can be a problem.
What command are you issuing? Just fastboot devices ?
Make sure you're not using a USB 3.0 port on your computer.
Click to expand...
Click to collapse
Few other thoughts:
- try a different cable; a cable that works for charging and adb communication may not work with fastboot
- avoid external hubs if possible
- be sure to reboot both devices after switching drivers if communication isn't immediately established

Marc_Xperia said:
Hey Guys,
i tried to Root my Moto E4 but Unfortunally i cant get Fastboot to work under Windows 10 Home 64 Bit on Both my Notebook and my PC. I installed The Motorola Device Manager (Since it comes with drivers) and installed ADB and Fastboot but once i Reboot into Fastboot Mode it wont Recognize it for flashing. The CMD Just Says Waiting for Device. I have expierience with Rooting other Phones but i never had this much Trouble getting Fastboot to work properly. Would be awesome if u could show me a Solution to this since i really want a Custom Rom.
Gesendet von meinem SM-A300FU mit Tapatalk
Click to expand...
Click to collapse
When you say you booted to fastboot what do you mean ?
Did use adb and your phone was recognized and then you issued adb command or what method are you using ....
You need to ensure you establish USB debugging connection first & grant authorization ...once link with authorization has been established run adb ...from adb check if recognized run command to boot to fastboot
So start from the top && go down
ARE YOU CERTAIN YOU USED CORRECT METHOD TO TURN OFF DRIVER VERIFICATION ON WINDOWS 10 && YOUR DRIVER ACTUALLY INSTALLED
Last noteworthy point ... when unlocking my motoE4 I had to boot to bootloader ONLY to use fastboot NOT "FASTBOOT"
Hold power + volume button

Excellent troubleshooting from our community. OP has not come back yet to confirm, ask another question, or simply a thanks. (Maybe he got it) Hopefully he gets it sorted.
Maybe the junior members underestimate just how quick and helpful our little community can be.

@Marc_Xperia Do not forget to install AndroidBootloaderInterface Driver Software. *android_winusb.inf*

Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.

Marc_Xperia said:
Thats what my Problem is. I installed the Latest Android Studio, i have gone to SDK Manager. Installed the Android 7.1 Files and USB Drivers and this happens everytime i want to unlock my BL. And yes i disabled Driver Signing on Windows 10. I call it Fastboot Mode since im Used to Xperias so im Sorry i confused anyone.
Click to expand...
Click to collapse
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works

KevMetal said:
When you authorize your adb connection do you tick or select always allow connections from this device ...the fact that your device is listed as *unauthorised* is a clear indication in your previous attempts you didn't authorize to "allways allow connections" from this device
#result _when you reboot authorization is revoked
Enter bootloader mode the old skool way using your buttons..
# MAKE SURE TO SELECT "ALLOW OEM UNLOCK OPTION IN DEVELOPS settings
1.AUTHORIZE TO "ALWAYS ALLOW CONNECTIONS FROM THIS DEVICE"
2.enter bootloader using hardware keys
3.plug in usb
4.run fastboot devices to force fastboot to start deamon ...
5.once fastboot can see your device run oem unlock
6.DO NOT USE USB 3 port so try different USB ports on pc
7. Alternatively use a live USB of Ubuntu minimal to do the job
--- doesn't seem like driver problem if adb can see your device
See if that works
Click to expand...
Click to collapse
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.

Marc_Xperia said:
I did all of that. Next Problem when i boot the device with Vol Down + Power and select meta mode. I will get only the Motorola Logo or a Normal Reboot into System. I set everything up in Developer Settings. Enabled Debugging and Allow Bootloader Unlock.
Click to expand...
Click to collapse
Why select meta mode ? When you are in bootloader you use your volume keys to navigate between meta, recovery& factory reset & meta and you use your power key to select different modes ...what do you want to do in meta mode ?
When you are in bootloader you are essentially in fastboot mode too so it isn't necessary to choose any of the other options unless you are trying to get into recovery which is pointless if you haven't flashed custom recovery yet ..

I Succeded. I Booted into Bootloader with ADB and took a look at Device Manager to install the Driver Properly.
i followed this guide https://forum.xda-developers.com/moto-e4/how-to/guide-unlock-moto-e4-bootloader-unique-t3654275.
Thank you for all of your Replys.

Moto e4 magisk manger trying to instal magisk hide props config says install failed

happymedium22026 said:
Moto e4 magisk manger trying to instal magisk hide props config says install failed
Click to expand...
Click to collapse
Download manually and flash inside recovery yourself

Safety net says the response is invalid does that affect ny device being rooted

happymedium22026 said:
Safety net says the response is invalid does that affect ny device being rooted
Click to expand...
Click to collapse
No it doesn't. That's an error in magisk manager when you hide the manager app itself. Just use a different safetynet checker app if you want to check safetynet.
Why are you posting this stuff in this thread?

XT1687 - Device refuses to switch into DIAG mode.

Hello friends.
I have spent 2 days reading the forums and finally decided to post after not being able to get my XT1687 to switch into DIAG mod so that I can use QPST.
The device is boot loader unlocked, flashed with TWRP, running Arrow OS Pie.
No trick such as using setprop sys.usb.DM or Diag, or anything seems to work. Also, no dialer codes seems to work.
All I can manage to do with Shell is reset the USB connection.
No combination of Vol + UP or 3 finger "saluting"... while in bootloader on BP Tools, QCOM, Tools Mode (Switch to Enable) seems to work. I have tried with every setting of USB Configuration combined with debugging on, or debugging off. Nothing will prompt my Windows 10 machine to call for several of the version of the Qualcomm driver's that I have installed - and the only remotely close to a COM Port is when I set it to USB Tether and sets up as a network adapter but I have not been able to manually update that or any other driver so that it establishes a COM port.
Like, am I just stupid and this doesn't have Qualcomm hardware in it or something?
Very much appreciate any guidance.

Question Nothing Phone 1 hard bricked (Edl Mode)

Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?

pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Try holding power+volup+voldown with the phone unplugged from a computer.
If it doesn't work, let me know.

how to boot to edl mode ??

Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl " or "fastboot oem edl" or "fastboot reboot-edl" or "fastboot reboot edl"

muppetz said:
Try this :
Install ADB and Minimal Fastboot drivers through which Windows will recognize your Device.
Enable USB Debugging on your Android Device. You can do this simply by following the given direction:
Settings > About Phone > tap 7 times on the Build Number. This will enable Developer options on it.
Now, again go back to the main Settings > Developer options > USB Debugging and Enable it.
Connect your smartphone with your PC via a USB cable.
Open Command Window by the press and hold Shift Key + right-click of your Mouse.
Choose Open Command Window here.
Type the following command and press the Enter button to check whether the device is connected or not.
" adb devices "
You will see a device serial code on the screen. That means it is successfully connected. Then follow the next step.
Type the command from below and hit enter to Boot into Download Mode (EDL Mode):
" adb reboot edl "
Click to expand...
Click to collapse
my phone is bricked while flashing stock rom via fastboot
so unable to boot to recovery or bootloader

To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if Qualcomm USB Driver have been installed on Windows .

muppetz said:
To begin with, power off your device. If you can’t do so, then you will have to wait until the battery completely drains out.
Now connect one end of the USB cable to your PC, but don’t attach the other end to the device.
Press and hold the Volume Up and Volume Down buttons together for a few seconds.
Now connect the other end of the device to the USB cable.
Your device will now be recognized as Qualcomm HS-USB QDLoader 9008. You may now flash the device-specific firmware to unbrick it.
Even you have a black screen , PC does recognize your phone . Use only a USB 2.0 port . Verify if drivers have been installed on Windows .
Click to expand...
Click to collapse
tried these steps but phone goes in 900E mode

OK , look then at this :

muppetz said:
OK , look then at this :
Click to expand...
Click to collapse
it does not work as he just changed the drivers from diagnostic mode to qdloader mode

pogradecari said:
Hello there members.
i have a Nothing Phone 1 in Edl Mode. Tried to restart it but still connected on Edl. i have searched around for this problem but sill unlucky to find a solution.
Client pretend to have played with roms and flashed the wrong one.
Any help suggestion?
Click to expand...
Click to collapse
Maybe it's too late already but you can unbrick the phone with this tool
Unbrick / Flash Stock Rom (1.1.7 global) QDLoader 9008 fix | EDL Mode fix
Hi everyone, If your phone (1) does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it without Disassembly. ‼️ Do this at your own risk, I am not responsible for any damage that may occur to...
forum.xda-developers.com

none of these will work

pogradecari said:
none of these will work
Click to expand...
Click to collapse
Why? Have you tried?