Database Users

[HOW TO] Recover HARD BRICKED Nokia X2 : DOESN'T TURN ON, NO VIBRATION, NO LIGHT

So, Guys. Myself thought of writing this thread so that you can prevent yourselves from entering into danger as well as get rid of it even if you enter by mistake.
As you all know that, we are currently facing an issue of SIM offline, myself got into the trouble (as per me, when i insert a sim in sim 1, device recognizes the network provider but there is no signal. sim 2 is fine) and inorder to rectify that issue, i tried all possible ways like deleting IMEI and rewriting it, changing modem etc.
But nothing worked and so thought of using NOKIA CARE SUIT (NCS) >> Product Support Tool For Store 5
& change the firmware to Nokia X2DS RM-1013 059V782 v2.1.0.13 which was the biggest mistake which i ever committed and it resulted in hard brick.
I suggest everyone not to flash 2.1.0.13 version please
In my case, i was not even able to use the volume buttons and power button inorder to get to bootloader or custom recovery. Trust me, i'm not a noob but i do know the situation in which i'm and searched everywhere and took help of lots of guys and finally found the solution to it.
Just follow these steps:
A. Requirements:
1. Nokia Firmware - Thanks to Firmware27
2. QPST_2.7.422
3. QDLoader HS-USB Driver
B. Procedure:
1. Extract Requirement - 1, 2, 3 separately.
2. Now Install requirement - 2 & in Requirement - 3, just install Setup
3. Now connect USB to NOKIA X2 & Laptop/PC
4. Click on the start menu and type QFIL in search box and open it.
5. Under "SELECT PROGRAMMER", click on the browse button and
select "rm1013_2.1.0.13_user_prog_emmc_firehose_8x10. mbn" from the Requirement - 1
6. Under "DOWLOAD", you will find "LOAD XML" and now click on that and a window will appear infront you :silly:
7. Now in the window, type *.xml in the file name so that the xml files will show up.
8. Now select "rm1013_2.1.0.12_059V787_001_rawprogram_unsparse_ui"
9. Soon another window will show up automatically and now type *.xml in the file name so that the xml files will show up.
10. Now select "P12026702dpi600_label_layout"
11. Now Click on the "DOWNLOAD" just button below the Load XML button.
- Make sure your device is connected to the PC/lappy through cable :silly:
Everything is done. Now sit back and Relax.
Your NOKIA X2 will bootup and it looks exactly like device when you purchased except the scratches and all
Note:
I'm not responsible if your device is bricked. Ofcourse if you are doing this, it means that your device might have already been bricked and i guess there is no other way except this to make it right
This works with all the snapdragon chipset devices.

my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working

frnsl3 said:
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
Click to expand...
Click to collapse
The only prob is OS which you are using and Drivers..

Thx, its helped me

Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.

Kuttappan555 said:
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Click to expand...
Click to collapse
if you are saying that you cannot download from the link i provided.....i just checked it. Itz working fine. i saved it in my g-drive and shared the link

Hi, I tried this and everything worked fine but phone didn't boot up. I mean the flashing worked but phone did not reboot. Screenshot attached. Do you know what is missing?

Is this method still working?

Hard Bricked
Still Working??

Can someone re-upload these files or point to the right direction?

Lumia 950XL Prototype

I have a Lumia 950XL prototype I got recently, but it's stuck on version 10586.164
When looking for updates says it is up to date, already tried it (WDRT) even if you messed up the product code
unsuccessfully
Can someone help me? He has the boot unlocked
(WDRT Error) PACKAGE NOT AVAILABLE FOR THIS PHONE With the original product code
Firmware: 01078.00048.16135.36002
Original product code: 059W5J6
PROTO

you tried Interop Unlock and registry change?
https://forum.xda-developers.com/showpost.php?p=71937591&postcount=323
3.Go to the app bar, then choose x50 series unlock. You will receive an error about the acer service not running. That's ok for now. Click step 1 and it will tell you to install the acer system service and copy some files. To install the acer system service, use iutool [rs and newer builds,this version is essential,old versions will probably not work] (can be found here. thanks @Wack0Distractor ).
iutool install https://forum.xda-developers.com/showpost.php?p=68459157&postcount=13
run this command as administrator
iutool -v -p "path to the file acer.service.acersystemservice.spkg"
if you receive error 0x80070490, disconnect your phone from usb, go to control panel on your pc, devices and printers, find your windows phone and remove device. reconnect the usb to your phone,and after it reinstalls the drivers automatically, run iutool command above again.
if you receive error 0x8024a110, your phone should reboot to the gears UI in a minute. if not, run the command again. if it still doesnt auto reboot, manually reboot your phone. It should reboot into the gears UI, then back into the OS. if it still fails and doest show gears, give you phone a rest for 5-10 minutes and retry(usually needed after a new rom flash).
4.When you're back in the phone OS, copy newndtksvc.dll and ndtksvc.dll to your documents folder on your phone through USB
5.Go to the app bar, then choose x50 series unlock. You should no longer receive the error about the acer service. Now click step 2 and follow the rest of the instructions from the app.
6.If you've taken the silent extras/advanced+info update, or updated that app manually, be sure to choose the option "Restore NDTK 950/XL" in the "x50 series unlock" page and reboot to regain access to the elevated features. It basically means if it suddenly stops working, apply this setting.
Click to expand...
Click to collapse
now you only need change registry
older version of Interop Tools for 10586
https://forum.xda-developers.com/showpost.php?p=68982441&postcount=284

hi, can you boot in masstoragemode and dump few partitions?
before update, make full dump via win32diskimager

If you can have your phone recognized by PC in any mode, there's a spark of hope, but be warned that I take no responsibility for any damage that may occur (and it may occur since you are installing a software that's made for final products on a prototype):
I strongly recommend you to perform a full ROM backup if possible to be able to get back to this version if things go horribly wrong. If you can't do this, you may consider enrolling in Windows Insider program (which may allow you to get new builds), or perform a software RM Code change - most recommended- (check here: thewincentral.com/get-windows-10-mobile-redstone-on-older-lumias-using-an-app-now-uses-same-mod/)
You might not find a ROM corresponding exactly to that product code (because it's a prototype) on the internet, but you can download any Lumia 950 XL Firmware you'd like (check this: www . lumiafirmware.com/ser/RM-1085).
Once you've downloaded all firmware files, use the following tool to flash the firmware onto your device: androidmtk.com / use-windows-phone-image-designer-tool
(remove spaces from urls)

[SOLV][TWRP instal][Athene XT1642]Many solutions tested but fastboot never load image

Hello forumers first of all I apologize for my approximate english I'm french and I talk about english only in forums so I will do my best you to understand myself.
I'm a new user on Androïd (and smartphone too) and after learning basics functions and many docs about this I decide to root my phone.It's new,not second hand so it was never used previously.With your threads to root it I succeed in unlocking bootloader without problems.Then I wanted to install TWRP by following your tutos and other sources (vidéos.......)and at each time fastboot don't load my image.
So I'm looking for solutions in forums and web and nothing works.Here is what I did after installing a win7 rather than my usualy Linux (install problems too )for this work :
use USB2.0 rather than 3.0 to connect my phone
use 2 different cable (original with my phone box and another)
install adb/fastboot on C:\ rather than Program Files (because permissions problems during install)
use one of your threads to redo it (image from shreps)
rename the image many times and another image version too and redownloaded it too
use complete path
use mfastboot v.2 too
This is a capture from terminal after fastboot :
so I spent hours to attempt many combination and reading posts but I don't know where to look for now.
Maybe can I use another recovery than TWRP to root?Which?
For info I'm not a dev

Hmm, one cause may be that you're missing the file extension from the file name. That TWRP image usually has .img on the end
I'd enable file extensions in Windows (here's a tutorial: https://www.howtohaven.com/system/show-file-extensions-in-windows-explorer.shtml ) and also use the Tab key on the keyboard to auto-complete the full file name. Make sure that the file name you're using has the extension (else Windows may not find it).
Also, when you flash TWRP, you may see 'Image not signed or corrupt', that is a normal message as TWRP is not cryptographically signed by Motorola.
With TWRP, you need to also boot directly to the recovery after flashing - easiest way to do this is to press the Volume keys on your device until you see 'Recovery' then press the Power key to select.

Hello echo92,
in my capture it was an attempt without .img extensions I should have pointed out that when I renamed it I attempt many solutions (even just name twrp.img or twrp-athene.img or twrp or twrp-athene or original name with and without extensions etc....).
Thanks for info for display extensions about windows because I looked for manip and not find
I'm under Linux so I didn't use win for many years but I have another pb with devices recognisation by adb and not to solved for the moment.So I install a win especially for rooting my phone it seems to be easier than Linux (and tuto are under windows)
So I will try again all my manips but in a nvidia forum I saw it was a windows issue and they only recommand to let complete path.
It's the most probant solution I have found until now.
I specify when I connect my phone after start it win recognize it normally so.........
I'm going crazy :silly:

[Guide] Enable Volte on custom rom (Android 10) (Rooted)

Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97

Got stuck at PDC
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.

aperture22 said:
I was successful in installing QPST and the device shows up in the Device Manager as a Qualcomm USB Modem connected to COM9. It even shows up in QPST config. But PDC shows no devices (even when run as Admin). Any help is appreciated . Thanks.
Click to expand...
Click to collapse
Did you install the Qualcomm usb driver which came included in the QPST zip file.
I'm not sure if it is a problem with the qpst version ,I'm using QPST 2.7.480.
And once I run the command in adb shell I get my device to show up as Qualcomm USB Composite Device in device manager under the universal serial bus controllers category.
And if everything is working well , the pdc will not show anything when it opens up but you'll find your device in the drop down menu.

I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.

aperture22 said:
I have installed the same version. My device shows up in two places - under Modems and also under Ports (COM & LPT) as Qualcomm HS-USB Diadnostics 9091 (COM9). It's not showing up under USB controllers but. The PDC device list dropdown is still empty.
Click to expand...
Click to collapse
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg

activate button is disabled even after running as admin

Gauravlonkar said:
activate button is disabled even after running as admin
Click to expand...
Click to collapse
To activate a profile: Right click on it and under setselectedconfig select sub0/sub1/both (try and check what works for you) and then you'll be able to click the activate button.
To deactivate select the sub under deactivate in the right click menu (or) just activate some other profile .
Do check the other xda forum posts related to this which i've provided links under reference, it might be helpful when you're stuck with something related to this .

the command after su doesn't do anything to my custom rom ....

prokiller1199 said:
the command after su doesn't do anything to my custom rom ....
Click to expand...
Click to collapse
I've tested it to work with luisrom,Havocos and some other rom I don't remember which one.
Running the command doesn't bring any popup or open up anything on the phone but you'll be able to see the change in the device manager of your pc.
The change caused by the command only persists till it is connected (ie. if you unplug nd replug the usb cable it will revert to the default state), until you change the state from the option provided in your notification (ie . something like from charging only to file transfer or tethering ect) and restart of the device.
Do also check if you have the correct drivers installed.

*deleted*

Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.

aperture22 said:
Finally got VoLTE on my Airtel SIM. Thanks for the detailed instructions and the necessary files.
Click to expand...
Click to collapse
hello,
why in PDC shows no devices (even when run as Admin)? I have the same problem.

gammerboy said:
Disclaimer: I do not know the underlying working of what this procedure does. Just sharing what's working for me. I do not take responsibility for any problems which might arise from following this guide. Please proceed with caution.
I have tested this on the Oneplus 3t and only for airtel india. Please feel free to experiment and report for other carriers.
References:
https://forum.xda-developers.com/oneplus-5t/how-to/guide-volte-vowifi-german-carriers-t3817542
https://forum.xda-developers.com/on...n-carriers-t3817542/post77874888#post77874888
https://github.com/edgd1er/voenabler
This guide will proceed assuming that Volte is working on OOS 9.0.6 for your carrier and does not work with the custom roms.
prerequisites:
For mobile
Unlocked bootloader, TWRP (Latest)(or some recovery based on twrp like shrp)
For PC
QPST and the requried qualcomm drivers which comes bundled with QPST , Minimal adb and fastboot
Files
OOS 9.0.6 , any android 10 based custom rom for which atleast someone has mentioned volte works on, A root option that you prefer
Make a complete back-up before proceeding.(Some say having a efi partition backup is good idk why I think it has the imei details and stuff)
1 . Flash OOS using twrp then Flash recovery (twrp) zip or img (Flashing OOS generally flashes back the default recovery)
2. Using the inbuild file explorer in twrp navigate to /system/etc/firmware/ and copy over the mbn_ota folder to your internal storage and move it over to your pc.
3. Flash the custom rom, gapps(if needed), root solution of your choice and boot up. Get the initial setup done and check if your network is working.
4. Enable adb and connect your phone to your computer.
5. Open up cmd in your minimal adb folder
and type in (or copy) what's given line by line:
adb shell
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
(Or)
type in
su
setprop sys.usb.config diag,serial_smd,rmnet_ipa,adb
in a terminal within android (download from playstore or install using apk)
This will enable serial over usb needed for use with PDC until you change the state to mtp or tethering or restart
6. Open PDC(as admin if required) from the qpst folder.
7. Select the device. Check the links provided to find out how to enable profiles in PDC. From my experience you do not have to remove any profiles from your device using PDC.
8. If the required profile is not present then use the load option to load in the required .mbn file from what you had copied from oos previously. ( I used mcfg_sw_Airtel-Commercial.mbn for airtel ) and activate the profile.
9. Might not be required - To force enable Volte in your rom add these lines to the build.prop file
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
10. Reboot phone
Credits:
@ToucanSam
@dagoban
@jamal2367
@Drake97
Click to expand...
Click to collapse
Sir can u make a total video tutorials so that we can easly understand because i just confuse what shuld i insta 8n pc and what shuld instal in mobile
---------- Post added at 07:55 AM ---------- Previous post was at 07:52 AM ----------
ronaksworld said:
if still cant find it in dropdown list of PDC then
type in dialpad *#801# and select Full-port switch Turned ON and then reopen PDC as admin,
If you still face the issue try this link it has DRIVER + QPST + APK .zip
https://mega.nz/file/nmpj1KIa#DPbxR_raJu60uDqpch_waGKAM8FR-vdTRkPMuryIHrg
Click to expand...
Click to collapse
Sir in this zip file their two apk file but that not installed in my phone can u tell me which one shuld i instal in pc and phone step by step plz

Tried to enable VoLTE & VoWIFI on my Redme 9 Pro, using the PDC and can actually get the VoWIFI works. However, once the device reboot, it just fall back to the ROW_Commercial profile and have to redo again to get it work.
Can anyone help with this issue?

Thans for your support

I'm also trying to activate VoLTE on my oneplus3t. But stuck in loading a .MBN file in the PDC tool. When I click the load button and select the .MBN file to open nothing happens.

QPST driver install...

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.