Related
I have read a few threads where people claimed to have made a connection with Sony Ericsson Xperia Play via CDMA Workshop and QPST. I have visited the official site from Sony and downloaded the drivers. Still no luck picking up the device on QPST or CDMA. I have installed Gordan's Gate's drivers and still no luck. Can someone point me in the right direction to getting the play detected? I have the R800X version already unlocked and rooted...
Note: I can successfully flash my device to CM7, and the other custom stuff. Thank so much to Ash, Mills, Doom and everyone else with so much helpful information....
solitaire4eva said:
I have read a few threads where people claimed to have made a connection with Sony Ericsson Xperia Play via CDMA Workshop and QPST. I have visited the official site from Sony and downloaded the drivers. Still no luck picking up the device on QPST or CDMA. I have installed Gordan's Gate's drivers and still no luck. Can someone point me in the right direction to getting the play detected? I have the R800X version already unlocked and rooted...
Note: I can successfully flash my device to CM7, and the other custom stuff. Thank so much to Ash, Mills, Doom and everyone else with so much helpful information....
Click to expand...
Click to collapse
simple buddy all you gotta do is open your phone dialer like if your gonna make a call and hit ##3424 and ht call itll take u back to your home screen its normal if it does attempt a call u did it wrong
after that if your using win 7 itll auto download the drivers this is to make a DIAG port if using diff os not sure look for the drivers on google
after that go into your device manager on your computer and look for what port number it gave you and go back to cdma and connect read and write spc is 000000 no extra steps are needed for the spc code
ps try to do it running stock rom because some users remove DIAG on customs roms why alot of people have trouble
Oh no! I have to install windows 7 because I am currently on windows XP (don't tell nobody!). I have been to the sony site and downloaded the PC companion and all 4 driver sets hoping it would be enough to get QPST to recognize my device. Still nothing, I can however connect with fastboot, flashtool, adb, but no luck with QPST detecting the phone no matter what I do.
If anyone out there have XP drivers for QPST that will detect the Xperia Play please share!
solitaire4eva said:
Oh no! I have to install windows 7 because I am currently on windows XP (don't tell nobody!). I have been to the sony site and downloaded the PC companion and all 4 driver sets hoping it would be enough to get QPST to recognize my device. Still nothing, I can however connect with fastboot, flashtool, adb, but no luck with QPST detecting the phone no matter what I do.
If anyone out there have XP drivers for QPST that will detect the Xperia Play please share!
Click to expand...
Click to collapse
try these out make sure you got usb debugging on and hit ##3424 and hit the call button itll take you back to the home screen and when it tells you to locate drivers unzip my rar file and put them like on the desktop or something and try it out
qpst has nothing to do with it for the most prt you need drivers for the DIAG diagnostics mode only then will qpst will detect the phone
edokassiah said:
try these out make sure you got usb debugging on and hit ##3424 and hit the call button itll take you back to the home screen and when it tells you to locate drivers unzip my rar file and put them like on the desktop or something and try it out
qpst has nothing to do with it for the most prt you need drivers for the DIAG diagnostics mode only then will qpst will detect the phone
Click to expand...
Click to collapse
Your drivers are missing .inf file and ##3424 isn't working for SE phones.
http://forum.xda-developers.com/showthread.php?t=1060184
hydrosity said:
Simply go to (via adb shell/terminal emulator) /sys/devices/virtual/usb_composite/diag and run (1 for on and 0 for off, respectively)
Code:
echo 1 > enable
echo 0 > enable
Click to expand...
Click to collapse
LIKE I SAID GRAB THE DRIVERS AND HIT ##3424
if it connects perfect to cdma workshop so will qpst
want more proof?
Okay it looks as if you both are right lol. I just realize my laptop don't have a Com Port and that may make a difference. I will install the drivers and ADB on my desktop tomorrow. Since I am running CM7 I will use the shell command to get to the enable file.
Thanks for the pictures! I noticed that I had the same stuff you had Edo except the Com port device. Oh and in stock I was able to do the 3424 code, but in CM7 it made a phone call lol.
Thanks Blag when I did the echo enable command on my laptop it booted me out of adb but I didn't have a com port lol.
Thank you guys for so much help!
edokassiah said:
LIKE I SAID GRAB THE DRIVERS AND HIT ##3424
if it connects perfect to cdma workshop so will qpst
want more proof?
Click to expand...
Click to collapse
I have GSM version, R800i.
First, ##3424 and call button initiates call.
Second, your drivers don't have inf file.
Blagus said:
I have GSM version, R800i.
First, ##3424 and call button initiates call.
Second, your drivers don't have inf file.
Click to expand...
Click to collapse
aha i have the cdma version not gsm which i think he does to since hes trying to connect to cdma and qpst to flashing purposes right?
okay yes i might of not packaged the zip right with the complete drivers but google is your friend as i dont have win xp i have win 7
and flashing custom roms theres a good chance they took out the diag mode for whatever reason why i suggested him to do it on a stock rom
when i hit ##3424 i dont get the phone call i get kicked back into the home screen and the computer initiates the diag port
there ya go
http://youtu.be/XyeROYQ5ULM
edokassiah said:
aha i have the cdma version not gsm which i think he does to since hes trying to connect to cdma and qpst to flashing purposes right?
okay yes i might of not packaged the zip right with the complete drivers but google is your friend as i dont have win xp i have win 7
and flashing custom roms theres a good chance they took out the diag mode for whatever reason why i suggested him to do it on a stock rom
when i hit ##3424 i dont get the phone call i get kicked back into the home screen and the computer initiates the diag port
there ya go
http://youtu.be/XyeROYQ5ULM
Click to expand...
Click to collapse
I have Win 7 too - do you have full driver package for Windows 7 or was it recognized automatically for you?
I activate diag mode via ADB shell and I get new HSUSB device but I need drivers for it.
Blagus said:
I have Win 7 too - do you have full driver package for Windows 7 or was it recognized automatically for you?
I activate diag mode via ADB shell and I get new HSUSB device but I need drivers for it.
Click to expand...
Click to collapse
try these try xperia driver if that doesnt work try xperia drivers 2
edokassiah said:
try these try xperia driver if that doesnt work try xperia drivers 2
Click to expand...
Click to collapse
You know, guess I'll have to quit it.
My phone's USB PID is E15D and it's not listed anywhere in inf files and I can't even start instalation via device manager. When I manually edit PID in inf to E15D, instalation fails with message install class is not present or valid.
EDIT: OK, after more editing I successfully installed it, but QPST still can't detect it (it's GSM R800i).
EDIT 2: Got it working in the end thanks for your drivers
huh those werent pulled from my computer they were downloaded from website thats how i was able to install the drivers there not attached to my phone in any way
uninstall what u got and retry
edokassiah said:
huh those werent pulled from my computer they were downloaded from website thats how i was able to install the drivers there not attached to my phone in any way
uninstall what u got and retry
Click to expand...
Click to collapse
Got it working in the end
I am the only unlucky person in the world! I think it is because I am still on windows XP. I will no longer put off installing Windows 7. Them drivers are not working for me at all. I just get the sony ericsson device with adb drivers showing up in my device manager. The other devices there are SEC HUSUB and they always have that problem symbol, the one with the yellow question mark. I try to install the drivers from their location and I get the message they don't have any information pertaining to the hardware.
Thanks though!
you have to manually edit inf files.
solitaire4eva said:
I am the only unlucky person in the world! I think it is because I am still on windows XP. I will no longer put off installing Windows 7. Them drivers are not working for me at all. I just get the sony ericsson device with adb drivers showing up in my device manager. The other devices there are SEC HUSUB and they always have that problem symbol, the one with the yellow question mark. I try to install the drivers from their location and I get the message they don't have any information pertaining to the hardware.
Thanks though!
Click to expand...
Click to collapse
Send frm my Play with coustum kernals
Okay so here is the issue I'm facing today. I bought a Sprint Galaxy S5, and I managed to unlock it for domestic use (AT&T). I cannot get an LTE connection because my Qualcomm processor does not have the appropriate bands to use ATT LTE's network.
I read on here that you can write your NV memory to write the firmware and enable these other bands using QPST and QXDM. The issue I'm having though is getting my computer to install the diagnostic driver for COM port. It reads the Modem under modem tab in device manager. Since the computer doesn't think there is a diagnostic port, QPST configuration cannot open a diag port which is what I need. I've been able to successfully put my phone in rndis + DM + modem by using this in emulator,
su
setprop sys.usb.confing_rndis,diag,diag_mdm
Do not type the first _ as it's meant as a space bar, but USE diag_mdm
But there is no indication that any driver has installed, and does not appear in device manager (even with hidden devices shown).
I'm running 6.0.1 CM13 w/twrp recovery with SELINUX set to permissive.
On windows 8
I also noticed that the guide to add frequency bands was written in 2014, I also know that in Lollipop, you needed to enable CP Logging to get it show up.
What I'm wondering is if there is a missing step to properly installing the diag driver, or if Qualcomm/Samsung found other means to activate it.
I noticed that when using EFSPro I can set it to Diagnostic + Modem + adb but I can only read not read/write NV memory
Also I observed when I send the SPC to read the phone with EFSPro, it says
"SPC was accepted by the phone!"
Then followed by.. "SPC was not found".
Then after I close that popup it reads my NV memory, but I can't write.
Is there a method to enable CP logging on CM13 MM and install the diag com port for QPST use? I don't have a stock recovery to enable CP logging through usual means in as I'm using TWRP.
Link to GUIDE
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Thanks in advance.
Sent from my SM-G900P using XDA-Developers mobile app
xHolomovementx said:
Okay so here is the issue I'm facing today. I bought a Sprint Galaxy S5, and I managed to unlock it for domestic use (AT&T). I cannot get an LTE connection because my Qualcomm processor does not have the appropriate bands to use ATT LTE's network.
I read on here that you can write your NV memory to write the firmware and enable these other bands using QPST and QXDM. The issue I'm having though is getting my computer to install the diagnostic driver for COM port. It reads the Modem under modem tab in device manager. Since the computer doesn't think there is a diagnostic port, QPST configuration cannot open a diag port which is what I need. I've been able to successfully put my phone in rndis + DM + modem by using this in emulator,
su
setprop sys.usb.confing_rndis,diag,diag_mdm
Do not type the first _ as it's meant as a space bar, but USE diag_mdm
But there is no indication that any driver has installed, and does not appear in device manager (even with hidden devices shown).
I'm running 6.0.1 CM13 w/twrp recovery with SELINUX set to permissive.
On windows 8
I also noticed that the guide to add frequency bands was written in 2014, I also know that in Lollipop, you needed to enable CP Logging to get it show up.
What I'm wondering is if there is a missing step to properly installing the diag driver, or if Qualcomm/Samsung found other means to activate it.
I noticed that when using EFSPro I can set it to Diagnostic + Modem + adb but I can only read not read/write NV memory
Also I observed when I send the SPC to read the phone with EFSPro, it says
"SPC was accepted by the phone!"
Then followed by.. "SPC was not found".
Then after I close that popup it reads my NV memory, but I can't write.
Is there a method to enable CP logging on CM13 MM and install the diag com port for QPST use? I don't have a stock recovery to enable CP logging through usual means in as I'm using TWRP.
Link to GUIDE
http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
Thanks in advance.
Sent from my SM-G900P using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you ever solve this? I plan on following the same guide and I too am having this same problem.
Hi all,
I have been having some trouble following a guide on how to add GSM+LTE bands to this device. Specifically, I am struggling to connect to this device in Diagnostic Mode.
I am running Windows 7 x64. I have installed Samsung USB Driver v1.5.45.00. I have tried an updated driver but I seem to have had less issues with this version. I have also tried using Qualcomm USB Drivers For Windows (QD Loader) but when I select this folder to search for an alternative driver instead of the one Windows assignes I have to manually select an *.inf file and the options (HD-USB QDLoader 9XXX) does not make any sense to me which driver is required for my device.
I can run ##DIAG# in the Phone app and bring up PhoneUtil which brings up a menu to select CDMA MODEM / PDA and I have used both with no success. This menu allows me to access RNDIS+DM+MODEM. If I try to use other applications to switch to CP from AP in other USB settings or PDA to MODEM the phone disappears in device manager.
In QPST Configuration I have to untick "Show Serial and USB/QC Diagnostic ports only" to show the port and select the device. If I continue and use Software Download to back up the xQCN (NV memory) file it gets stuck at 12% and gives me an error "Could not Communicate in Diagnostic Mode"
If I use CDMA Workshop to do a backup the files hex just shows 00's and EFS Professionals backup is the same.
I have tried using stock Lollipop 5.0 firmware an enabling CP logging, rooted 5.0, a custom ROM including CM and I am currently running rooted 6.0.1 firmware.
I used Idoneapps paid service to find the SPC for my device but I don't believe there is any equivalent service to enable or disable the bands on my device.
All I can consider is wrong is the possibility of not having the right drivers but I have no idea where to find the right ones. I am at a bit of a dead end, any help would be appreciated.
Thanks.
tai1z said:
Hi all,
I have been having some trouble following a guide on how to add GSM+LTE bands to this device. Specifically, I am struggling to connect to this device in Diagnostic Mode.
I am running Windows 7 x64. I have installed Samsung USB Driver v1.5.45.00. I have tried an updated driver but I seem to have had less issues with this version. I have also tried using Qualcomm USB Drivers For Windows (QD Loader) but when I select this folder to search for an alternative driver instead of the one Windows assignes I have to manually select an *.inf file and the options (HD-USB QDLoader 9XXX) does not make any sense to me which driver is required for my device.
I can run ##DIAG# in the Phone app and bring up PhoneUtil which brings up a menu to select CDMA MODEM / PDA and I have used both with no success. This menu allows me to access RNDIS+DM+MODEM. If I try to use other applications to switch to CP from AP in other USB settings or PDA to MODEM the phone disappears in device manager.
In QPST Configuration I have to untick "Show Serial and USB/QC Diagnostic ports only" to show the port and select the device. If I continue and use Software Download to back up the xQCN (NV memory) file it gets stuck at 12% and gives me an error "Could not Communicate in Diagnostic Mode"
If I use CDMA Workshop to do a backup the files hex just shows 00's and EFS Professionals backup is the same.
I have tried using stock Lollipop 5.0 firmware an enabling CP logging, rooted 5.0, a custom ROM including CM and I am currently running rooted 6.0.1 firmware.
I used Idoneapps paid service to find the SPC for my device but I don't believe there is any equivalent service to enable or disable the bands on my device.
All I can consider is wrong is the possibility of not having the right drivers but I have no idea where to find the right ones. I am at a bit of a dead end, any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
man, if anyone can shed some light on this, itll breathe some new life into my phone. I looked for the very same thing a while back as i switched to H2O wireless using AT&T towers and its working, but just on HSPA+ and thats because all of the LTE bands arent unlocked on my phone. QXDM and QPST are the tools we need, but the driver issues are whats stopping me too. Anyone with insight would be greatly appreciated
bump
I was having trouble with connecting to B5 ( 850) LTE as I was consonantly connected to 1800... So i searched and searched and managed to unlock bands and now getting B5 850 as the first preference ...Below guide can literally break your phone if you do not follow correctly ...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will run.
*/
1. Make sure your phone is rooted and you have SuperSU installed, ADB drivers installed
2. Download "Setup DFS Studio" from http://cdmatool.com or the DFS Studio 16.05.31.0 (an older version) from here https://mega.nz/#!h1ImHJyK!gBcp2j6wI...YSoIjPkY_hJJVY ( use this - demo will work and do not update / will prompt with mandatory update you can drag that aside)
3. Connect the phone to the computer via USB
4. Select MTP and USB debugging
5. Open command prompt from Start => Run and type "cmd.exe". Once opened, type "adb shell". It should show "[email protected]_x2:/ $"
6. Open the SuperSU app on the phone
7. Type in cmd.exe "su" and grant access of ADB shell in SuperSU, you will see "[email protected]_x2:/ #"
8. Type in cmd.exe "setprop sys.usb.config diag,adb" and your phone will enter into Diagnotics Mode - this means that the MTP connection will be lost (you won't find any portable device in My Computer).
9. The drivers should be installed for the Diag Mode and you can see in Device Manager at Ports - Qualcomm HS-USB Android DIAG 901D (COMxx). ( mine did not come up so i had to plug in to USB 3 port and refresh port list on to very right DFS )
10. At this stage, if all should be well, you can start the "Qualcomm Tool" from DFS Studio folder. You can close the login window and it will run in demo mode (enough for what we need)
11. In the "Main" tab, double click on "Qualcomm HS-USB Android DIAG 901D (COMxx)" to select it - in the DFS log you will see "Qualcomm HS-USB Android DIAG 901D (COMxx) device in diagnostic mode"
12. In DFS Tool select tab "Band"
13. In tab "CDMA/GSM/HSPDA" select "RF BC Config" and then "Read"
14. Select the bands you need and then press "Write"
15. In the same tab, select "Bands Preffered" and do the same as above (read-write)
16. Select "LTE" tab which is aside "CDMA/GSM/HSPDA" and do the same as above. I changed values only in "LTE BC Config #6828" as the "LTE BC Config DIV #6829" didn't work for me when I pressed Read (there was nothing selected, all blank).
17. After operation had been completed, close Qualcomm Tool, unplug the phone and restart it.
Notes:
You must back up Rom( stock or modified stock Turbo alike and the EFS partition( in TWRP) as my first reboot said no sim... With EFS back up phone was back from dead
Credits for this goes to chatmonchy and valy_cta
This works to use x720 on US network?
It seems it would work on 720 as well, given that it opened bands that are officially open on 720 but not on 727 (such as band 20).
Abdiel1224 said:
This works to use x720 on US network?
Click to expand...
Click to collapse
Should as I was able to write all available bands, for instance I am using Vodafone which has duplex 1800 but x720 out of box support only one after changes I get both
... Please do not forget to back up ROM (stock or modified stock like Turbo) and EFS partition.
I got my phone into diag mode and but had trouble getting windows 7 to recognize the device. I found an upload of the qualcomm drivers and that fixed it and windows recognized the diag mode correctly as you had said in your post as "Qualcomm HS-USB Android DIAG 901D (COMxx)" I tried DFS but couldn't get it to recognize any com ports or my device. It just has blank lists there. I tried changing the com port on the qualcomm DIAG to com2 just in case but that didn't seem to help. Anyone else having trouble getting the com port recognized by DFS?
vw_diesel said:
I got my phone into diag mode and but had trouble getting windows 7 to recognize the device. I found an upload of the qualcomm drivers and that fixed it and windows recognized the diag mode correctly as you had said in your post as "Qualcomm HS-USB Android DIAG 901D (COMxx)" I tried DFS but couldn't get it to recognize any com ports or my device. It just has blank lists there. I tried changing the com port on the qualcomm DIAG to com2 just in case but that didn't seem to help. Anyone else having trouble getting the com port recognized by DFS?
Click to expand...
Click to collapse
I've mentioned bro,
mine did not come up so i had to plug in to USB 3 port and refresh port list on to very right DFS. i have also installed QPST ( QPST configuration)
you can find here,
https://drive.google.com/file/d/0B4NOhMSMyPxuZURyZldIbGtXYWs/view
*#*#76937#*#* diag port enable
saraprobe said:
I've mentioned bro,
mine did not come up so i had to plug in to USB 3 port and refresh port list on to very right DFS. i have also installed QPST ( QPST configuration)
you can find here,
https://drive.google.com/file/d/0B4NOhMSMyPxuZURyZldIbGtXYWs/view
Click to expand...
Click to collapse
Hmm something seemed to be messed up as I didn't have the refresh port dialog box with the version of DFS i had downloaded. I only had "reset" which didn't seem to do anything. I think i ended up downloading the older version and that one worked.
termomen said:
*#*#76937#*#* diag port enable
Click to expand...
Click to collapse
This didn't do anything for me, however i'm also on Lineage OS so I don't know if those codes are ROM specific.
I can however confirm this message works fine for the x720! I was able to unlock LTE bands 17 and 12 confirmed with network signal guru. Thanks for the write up! :laugh:
vw_diesel said:
Hmm something seemed to be messed up as I didn't have the refresh port dialog box with the version of DFS i had downloaded. I only had "reset" which didn't seem to do anything. I think i ended up downloading the older version and that one worked.
This didn't do anything for me, however i'm also on Lineage OS so I don't know if those codes are ROM specific.
I can however confirm this message works fine for the x720! I was able to unlock LTE bands 17 and 12 confirmed with network signal guru. Thanks for the write up! :laugh:
Click to expand...
Click to collapse
Glad to contribute...mine could have been windows 10 related and only recognised with Stock ROM with super SU
Any follow up on this? Have you went out into the wild and actually confirmed that the unlocked bands are truly being used and not just -reporting- unlocked? I'm still waiting to hear from someone saying the unlocked bands were actually proven to be in live action usage after being "unlocked".
Mine is working... Try it ur self
Driver for Qualcomm HS-USB Android DIAG 901D
vw_diesel said:
I got my phone into diag mode and but had trouble getting windows 7 to recognize the device. I found an upload of the qualcomm drivers and that fixed it and windows recognized the diag mode correctly as you had said in your post as "Qualcomm HS-USB Android DIAG 901D (COMxx)" I tried DFS but couldn't get it to recognize any com ports or my device. It just has blank lists there. I tried changing the com port on the qualcomm DIAG to com2 just in case but that didn't seem to help. Anyone else having trouble getting the com port recognized by DFS?
Click to expand...
Click to collapse
Can you please advise where you download the windows 7 driver for Qualcomm HS-USB Android DIAG 901D? Thank you in advance!
When restarting, the value returns to original.
The wcdma band returns to default.
Omg...
Please change the post title which is confusing, you unlocked nothing .... B5 is already unlocked in the phone, all you did, is choose b5 over the other signals as the preferenced one thts it , dont say you unlock stuff when they already are !.... Right now we know that this phone have this hardware for the le x720(i dont know if its same for le x727 but apparently it is) :
SKY77643-21
Hardware allows u to :
WCDMA Bands I, II, III, IV, V, VIII, IX
TD-SCDMA Bands 34, 39
FDD LTE Bands 1, 2, 3, 4, 5, 7, 8, 9, 12, 13, 17, 20, 28, 30
TDD LTE Bands 38, 39, 40, 41
The x720 band are : B1/2/3/4/5/7/8/20/38/39/40/41
The x727 band are : B1/2/3/4/5/7/8/12/17/29/30/38
So maybe try to unlock b28 (hardware compatible) for example or b12 for the le x720 since only the x727 have it and then u can confirm tht u unlock something cause your post and the title are not saying the same.
As with le max 2, modem firms 15S and beyond have restrictions. Even if you change the band, you return to the original.
Japanese guy are making temporary connection possible situations, but it seems to return to the original after restarting.
http://gadget.hrksv.com/2017/05/23/post-4812
@saraprobe which is the decryption code for mega ?
marios199546 said:
@saraprobe which is the decryption code for mega ?
Click to expand...
Click to collapse
Download from cdmatool.com
Because the update is now mandatory and you need to register in order to work now
zaiem93 said:
Please change the post title which is confusing, you unlocked nothing .... B5 is already unlocked in the phone, all you did, is choose b5 over the other signals as the preferenced one thts it , dont say you unlock stuff when they already are !.... Right now we know that this phone have this hardware for the le x720(i dont know if its same for le x727 but apparently it is) :
SKY77643-21
Hardware allows u to :
WCDMA Bands I, II, III, IV, V, VIII, IX
TD-SCDMA Bands 34, 39
FDD LTE Bands 1, 2, 3, 4, 5, 7, 8, 9, 12, 13, 17, 20, 28, 30
TDD LTE Bands 38, 39, 40, 41
The x720 band are : B1/2/3/4/5/7/8/20/38/39/40/41
The x727 band are : B1/2/3/4/5/7/8/12/17/29/30/38
So maybe try to unlock b28 (hardware compatible) for example or b12 for the le x720 since only the x727 have it and then u can confirm tht u unlock something cause your post and the title are not saying the same.
Click to expand...
Click to collapse
Do it yourself and report instead of making assumptions
saraprobe said:
Do it yourself and report instead of making assumptions
Click to expand...
Click to collapse
Assumption ?? Just saying u didnt " manage to unlock " something like u said in ur first post since b5 is already unlocked by default anyway good luck and naa i already knw its not gonna work since values goes back to default People on other post with other phone's had to change nvram values too in order to make it work anyway gl if i have time to unlock b28 ill see
zaiem93 said:
Assumption ?? Just saying u didnt " manage to unlock " something like u said in ur first post since b5 is already unlocked by default anyway good luck and naa i already knw its not gonna work since values goes back to default People on other post with other phone's had to change nvram values too in order to make it work anyway gl if i have time to unlock b28 ill see
Click to expand...
Click to collapse
I did and travelled OS
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.