Database Users

[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]

Hi?
I'm posting this thread for all those who want to root their tablet but need a step by step guide for the same. I have condensed the information from many threads and put it into one. All the credit goes to the respective thread owners who have posted the guides. Let's begin:
NOTE: Im not responsible if you brick your device. You are solely responsible for what happens. If you follow the steps correctly it is unlikely that it will harm your device. If you face any issues you can post it here and I will try to solve them ( or someone else will). All good.
Scary stuff apart, let's begin to root your device ?
1. On your device, Go to Settings, Developer Options, and click on Enable USB Debugging. If there is no Developer Options in Settings, Click on About Phone and click 7 times on Build Number. This will give u the option.
2. Once you have enabled it, connect your device to your computer via USB cable.
3. Install the device drivers from the autoplay options.
4. Right click on My Computer and click on Manage
5. A new window will open called Computer Management, under which u have to click on Device Manager.
6. A list of devices connected to your computer will be shown on the right hand side.
If your device is listed under heading Android, as Android ADB Composite Device, then there is no need to download and install adb/fastboot drivers, and you can go ahead with the rooting process.
But its most likely your device will be listed under Other Devices. Under that it will be as MTP device or by the name of your device itself. This means you have to download and install adb/fastboot drivers on your computer before rooting it.
7. Open your browser and click on http://adbdriver.com/upload/adbdriver.zip which will download the adb installer on your computer. Run through the setup and install it. Run the program, it will automatically detect your device and install the necessary adb/fastboot drivers for it on your computer.
Alternatively, you can click on http://forum.xda-developers.com/showthread.php?p=48915118 through which you can install the same. I did it with the first method for my device.
Download and install it in [C drive].
8. Once the drivers are installed, go to Device Manager again (Step 4 and 5), and check on the list of devices. Your device should be listed under the heading Android, and showing as Android ADB Composite Device.
9. Open up C drive, there should be a folder named 'adb' under it. Open that folder and right click anywhere and open a command prompt.
U can also press 'Win+R' keyboard keys and type in 'cmd.exe' to open up a command prompt and use the cd command to come into the right folder. Once your into the adb folder in the command prompt (it should show as "C://adb>".
Type in command 'adb devices' and press enter (without the colons).
This should show you that your device is connected by the name of your chipset as Baytrail******. If it doesn't show this it means the adb drivers are not installed or ur device is not connected to the computer. Only once after it detects your device you have to go ahead with your rooting process.
10. After you have successfully completed all the above steps you are now ready to root your device.
11. Click on this link forum.xda-developers.com/showpost.php?p=57543871&postcount=1 from where you will have to download 'Intel Fastboot Tethered Temporary Recovery Session Launcher' onto your computer and extract it to some folder.
12. Download the UPDATE SuperSU zip file to your device and store it in your internal memory so you can find it easily later.
13. Now open the folder where you have extracted the Intel Fastboot Tethred Temporary Recovery Session launcher. Double click the launcher.bat file to start and type " ACCEPT " case sensitive without quotes to continue.
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE*
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED "
Please check if your devices is displaying an authorization prompt.
Be sure to check 'Always allow from this computer' and then press ok.
It will ask for the type of recovery u would prefer to run. Options 1-4 will be TWRP recovery and 5 will be CWM. I selected the CWM recovery. So enter number '5' and press enter.
14. It will display the list of triggers to be selected for the rooting process. Select the trigger to launch the Temporary CWM Recovery Session.
The list will be as follows:
T1 oem startftm ( very few devices support this command , but its the original used so )
T2 oem backup_factory ( limited devices support this command )
T3 oem stop_partitioning ( should work on alot of kitkat builds )
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop)
15. Select trigger 'T4' if you have upgraded your tablet to Lollypop Android 5.0.1. After selecting the trigger your device should reboot into fastboot and begin to copy files to your device.
note :*If your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note :*If you see unknown oem command the trigger isn't supported by your device.
16. The temporary cwm recovery session will start at this point on your device.
17. Select install zip from the recovery menu using vol up / vol down to navigate and power to select.
18. Select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
19. Confirm the installation.
20. After install completes reboot your device*through the reboot device option in the recovery menu itself.
21. It's going to take a while for the device to reboot. 'Android is upgrading' window will pop up once the screen gets on. After the boot is complete open all apps to see Super SU installed in it.
Now you have successfully rooted your Yoga Tablet 2. Enjoy ☺
NOTE: Follow all steps carefully and correctly so it becomes highly unlikely that you may brick your device. Make sure there is no powercut to your computer during the rooting process if you are not using a laptop or a UPS for your system. You can post any queries or questions in the thread.
All credit goes to the original thread owners, social-design-concepts, workdowg for helping all yoga tablet users to be able to root their devices.
A lot of work has gone into making this NOOB friendly step by step guide. Hit thanks if this helps you. Much appreciated. Have fun rooting.☺
Posted from my Rooted Lenovo Yoga Tablet 2 (830LC).

Much appreciated for this noob guide.

Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help

Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk

anilkumar247 said:
Thanks for the tutorial.
I did all the steps as you said. I am at step 15 and selected t4 and then the command prompt showed waiting for device and then my tab rebooted itself and then came to a fastboot mode.
Now n TAB its showing error that "E: No valid installer medium found"
now when i press the volume keys, the boot option changes and then the error message changes to
"could not open /sys/devices/virtual/backlight"
Please help
Click to expand...
Click to collapse
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?

AndroMAN said:
Did u check that ADB/fastboot drivers installed correctly? Try to reinstall those drivers and check again. Did u select the UPDATE SuperSU zip file and install it?
Click to expand...
Click to collapse
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.

@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk

anilkumar247 said:
How can i make sure they are installed correctly ?
I have reinstalled them and tried again, but still getting the same error.
I am not getting the update Super SU option, or any options to get it installed.
Click to expand...
Click to collapse
Step 8 and 9. Check under command prompt. It should show the name Baytrail***** when you type in the command "adb devices". Only then u can go ahead.

sajsaj7829 said:
@AndroMAN any idea why my 64gb sdcard is not recognized.
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Have you rooted your tablet? Was it detecting it earlier?

AndroMAN said:
Have you rooted your tablet? Was it detecting it earlier?
Click to expand...
Click to collapse
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk

Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID

sajsaj7829 said:
Thanks........ successfully rooted yt2 1050L
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?

sajsaj7829 said:
Hv rooted...Yes 32gb was working perfect but 64gb it says blank sdcard
Sent from my YOGA Tablet 2-1050L using Tapatalk
Click to expand...
Click to collapse
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.

anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.

AndroMAN said:
Good? All the best and enjoy your rooted device. Have you installed Xposed Framework on it yet?
Click to expand...
Click to collapse
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
AndroMAN said:
Try formatting the new sd card via the tablet, even I have put a 64GB card and I had to format it before it could detect.
Click to expand...
Click to collapse
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.

anilkumar247 said:
Hi
yes, its showing the device ID
prntscr.com/948uzk
prntscr.com/948ybk
I have blackened the device ID
Click to expand...
Click to collapse
AndroMAN said:
Sorry to hear your facing issues. There are already people saying they have successfully rooted their device using this guide. So there must be some step u might have missed or done incorrectly.
Send me the details of your device, model of tablet, which Android version.
Click to expand...
Click to collapse
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:

1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
That might just work :fingers-crossed:

1subw00fer1 said:
Hey i think i have the solution for your problem because everytime i am facing the same issue
That means at first adb drivers are shown as installed correctly within the window of the 'Intel Fastboot Tethered Temporary Recovery Session Launcher' tool. But after my tablet reboots into fastboot via method t4 it always says "No valid installer medium found".
Note: I have these adb drivers installed http://forum.xda-developers.com/showthread.php?t=2588979
So here is my solution that works for me: (this is my first post so i cant provide any screenshots.. )
1. let the tablet stay within the fastboot mode
2. in windows: navigate to the device manager --> there you should see the symbol "android phone" with a yellow triangle
3. right click on this symbol and choose the first option "update drivers" (sry i don't know if i translated it correctly xD)
4. choose the option "search on pc .."
5. there you select the second option "choose from a list.."
6. within the list you select 'android device'
7. within the next list you select 'google nexus adb device'
8. after that the drivers are installing and the recovery starts on your tablet :fingers-crossed:
Click to expand...
Click to collapse
Hello
That worked
But instead of google nexus adb device in the list, i got only motorola ADB device, but still it worked .
Thanks to both of you for the help.

sajju73 said:
Thanks.. cld u please link me to ver of xposed working on yt2.
---------- Post added at 11:25 AM ---------- Previous post was at 11:21 AM ----------
@AndroMAN somebody hv made a exfat binary zip to be flashed via teetherd recovery.... any idea how to go into twrp recovery.
Click to expand...
Click to collapse
There is no working mode of Xposed on YT2 as far as I have seen. Still have to look into it.
Go to recovery the same way u did last time, through 'Intel fastboot launcher:

Congratulations @anilkumar247. I hope your device is rooted and working well. And thanks to @1subw00fer1 for helping out and contributing to this thread. Great work guys. All good ☺

[HOW TO]Guideline / Install MTK drivers / How to Root / Flash a Rom / IMEI Restore

In this Thread i will explain how to set up MTK drivers and Flashtools.
Guideline:
Post #1 : Set up MTK drivers in Windows 8 / 8.1 / 10
Post #2 : Use Flashtools for MTK Devices
Post #3 : How to Root Stock Rom
Post #4 : Windows 10 MTK Drivers installation ( just in case post #1 dont work )
Post #5 : Lost IMEI Backup​
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Install MTK drivers in Windows 8 / 8.1 / 10
what we need:
MTK Vcom Preloader Driver 2.0
Download : https://www.androidfilehost.com/?fid=24438995911977169
First thing we need is to Disable the Signed Driver verification on Windows :
To disable driver signature verification, we’re going to need to get into the Troubleshooting options from the boot manager.
The easiest way to bring this screen up is using this secret trick.
Hold down the SHIFT key while you click Restart.
{
"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"
}
Once your computer has rebooted you will be able to choose the Troubleshoot option.
Then head into Advanced options.
Then Startup Settings.
Since we are modifying boot time configuration settings, you will need to restart your Computer one last time.
After restarting your computer a second time,
choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
That’s all there is to it. Your PC will then reboot and you will be able to install unsigned drivers.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Now its Time to open SP_Driver_v2.0.zip and start the DriverInstall.exe
it will open the install prompt . Press okay and dont change the installation path
Code:
C: // program files / Mediatek / Driver Package
during the installation it will start the verification window security.
Click on Install this driver software anyway
There will be an Error Message . - We Ignore it !
-Now Open your Device Manager and leave it open.
-Power Off your Phone and connect it with your Pc.
-you will see Under ports ( COM & LPT ) a Preloader unknown device
right click on there and click on Driver update/installation.
-Choose manually search for drivers
-Browse to C:// program files / Mediatek / Driver Package and apply.
-If all went good you have successfully installed the MTK Vcom Drivers. :good:
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>​

How to Use Flashtools
i use SP_Flash_Tool_Windows_v5.1520.00.000 and never had a problem with it.
Its for most all MTK Phones and for all Elephone Devices
Download Link: https://www.androidfilehost.com/?fid=24438995911977217
- Extract the Flashtool zip folder to your Desktop
- Click flash_tool.exe to open the Tool
- You will see two "folder buttons" Download agent and Scatter-loading
- Into Download agent place the MTK_AllInOne_DA.bin file .
its in your Flashtools folder
- Into Scatter-loading place the Scatter.txt
All Stock Roms / Custom Recoverys have one Scatter.txt in their Zip files.
- Make sure that every partition is checked
-IMPORTANT NOW, Flashing Part-
-Power Off your Device!
-Press on the Download Button!
-Connect your Device with PC and wait until all is flashed
-you will see a Green Mark when all is done
-Disconnect your Device and press Power button to Reboot.
:fingers-crossed::good::fingers-crossed:
------------------------------------------------------------------------------------------------------------------------------------------------​

How to Root Stock Rom
-If you want to Root your prefered Stock Rom
-Place SuperSU into your Sdcard
-Flash a Custom Recovery with Flashtools and its Scatter.txt
-Hold Vol+ and Power to get into Bootloader Menu
-Navigate with Vol+ and apply Recovery with Vol-
-Flash Supersu.zip
-Reboot
Stock Roms:
Stock ROM Elephone P9000_Android 6.0_20160315 Link: http://bbs.elephone.hk/thread-9967-1-1.html#[email protected]
CWM Recovery:
Link : https://www.androidfilehost.com/?fid=24459283995304518
100% bug free Supersu v.2.46.zip
https://download.chainfire.eu/696/SuperSU/​

Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial
To determine the version of Windows 10 that you have (32 bit or 64 bit):
- Right-click on Start then click on System
- In the System window that opens, in System section, you will find your version of Windows next to System type
To disable Windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
- The computer will restart with the Startup Settings screen
- To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
- After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
- After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure
To install the MTK VCOM USB Drivers on 32 & 64 bit Windows 10:
- Download the drivers *.zip archive and extract the folder from inside on to the desktop:
https://www.androidfilehost.com/?fid=24269982087012126
Right-click on Start then click on Device Manager
In the Device Manager Window click on the first item – your computer name
Click on Action then Add legacy hardware
On the Welcome to the Add hardware Wizard window click on Next button
Select Install the hardware that I manually select from a list (Advanced) and then click on Next button
Click on Show All Devices then on Next button
In the Add Hardware window click on Have Disk… button
In the Install From Disk windows click on Browse… button
In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway
This action will add the following drivers in to the operating system:
- MediaTek DA USB VCOM Port
- MediaTek PreLoader USB VCOM Port – for transferring the firmware to your device
- MTK USB DEBUG Port
- MTK USB Modem Port
- MTK USB port – for transfering PreLoader to your device (and recovery in case of bad or corrupt firmware)
Now we need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window we expand Ports (COM & LPT) section
Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box Delete the driver software for this device is empty
- You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalise
Now, when you will connect your turned off MTK device to the Windows 10 computer by USB, the device will be recognized either trough a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware. The SP Flash Tool will be able to transfer the firmware to your device trough this interfaces. Make sure you connect the device after you press the Download button in SP Flash Tool, as the communication interface will only be alive for 2 seconds if no data is being sent.
Download SP Flash Tool v3 & v5 – Latest versions:
http://laurentiumihet.ro/technology/download-sp-flash-tool-v3-v5-latest-versions/
TUT found here : http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
cheers​

Lost IMEI Restore
A common problem many face in their phone is loss of IMEI no. This is results in no network detection by your phone. U can come to know you have lost your IMEI by checking Settings->About phone->Phone information. There under IMEI section you won’t be finding your mobile IMEI numbers displayed.
Don’t worry you can restore your IMEI’s. Just follow this guide and you will be able to restore your IMEI. I will split the tutorial into two parts.
BACKING IMEI :
-First step before performing all these things is that your phone should be rooted.
When your phone is in normal state with everything functioning install Root explorer and navigate to the below location
Code:
>ROOT>DATA>NVRAM>MD>NVRAM>NVD_IMEI>MP0B_001
-Now copy this MP0b_001 file to your SD card or PC whichever place you feel the file we be safer.
-Now download MTK Droid tools .
-Now extract the zip file and open the MTK droid tools exe file.
-Now in your phone turn on USB Debugging by going to Settings->About phone-> Developer options and there turn on USB debugging.
-Now connect your phone and MTK droid tools should be able to detect your phone. U should see a window like this appearing after your
phone has been detected.
-Now press the ROOT button present in lower right corner. When it asks Supersu grant in your mobile click allow. After MTK droid gets
access u should see a green colour box appearing in the lower left corner which means u have correctly granted access to MTK droid.
-Now click on the IMEI/Nvram tab. A window should open and click backup NVRAM and MTK droid tools would take a backup of NVram in
its folder.
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
-Now paste that file and replace the one present there. Set the permissions for that file as RWER-ER-E. Now reboot your phone and you
should be able to get your IMEI back.
If you still haven’t got IMEI open MTK droid tools and connect your phone and press ROOT again and give MTK droid tools root access.
-Now click on IMEI/Nvram tab and select Restore option and restore the NVram backup which you took earlier. Now reboot your phone and
you should be able to get your IMEI.
Extreme method :
-After performing all the above if you haven’t still got IMEI. Now switch off your phone and open SP Tools and connect your phone.
Click on format and format your whole phone. ( This wipes whole of the phone including NVram region ).
-Now flash stock ROM through SP Tools and after it completes start up your phone. ( Don’t be surprised. Your IMEI will still be in lost state
only ). Now root your phone.
-After successful rooting now connect your phone to MTK Droid tools and again press ROOT button and grant root access to MTK Droid
tools. Now click on IMEI/NVram tab.
-Now as you see in the image above you can see two boxes IMEI1 and IMEI 2. Now enter your device IMEI numbers manually in those two
boxes.( You can get your IMEI no’s from your phone box ). Now click replace IMEI. Now reboot your phone and you should be definitely able
to get your IMEI restored.
MTK DROID TOOLS LINK : https://www.androidfilehost.com/?fid=24438995911972546
found: http://www.androiddevs.net/restoring-lost-imei-mtk-phone/​

MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?

I'm having same issue here on Win10 installed the drivers etc... using latest SP Tools plug phone in and try and put recovery as a download nothing happens.
EDIT: Nvm got it working realised I was downloading and plugging in the phone in the wrong order.

Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#

#LOUDmouth# said:
Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#
Click to expand...
Click to collapse
False positive

kopasz93 said:
MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?
Click to expand...
Click to collapse
I have a solution for restoring IMEI:
In the dialer: *#*#3646633#*#*
OR
download "MTK engineering mode" app and start it
it will open engineering mode:
1/ go to "Connectivity" tab
2/ go to "CDS information"
3/ go to "Radio information"
4/ then select "Phone 1"
5/ At the top there is a command line "AT+" in it
6/ type AT+EGMR=1,7,"your imei number" (for example: AT+EGMR=1,7,"012345678901234")
7/ then hit "Send at command" (if you got error try to put space between "AT" and "+")
8/ go to "Phone 2" and type in the command line: AT+EGMR=1,10,"your imei"
9/ hit "send at command"
10/ restart your phone and it should work
You can check if it changed at Settings -> About Phone -> Status -> IMEI information
If your forgot your original IMEI numbers you can find them on the box of the phone

MTK droid tool recognizes my phone, but do not get the green button so root error. Granted permission in supersu.

If anyone is still struggling (like me) with the error: Initializing scatter file failed. Please check the name of the scatter which you load is legal
i solved by using SP Flash Tool 5.1552.00.000 downloaded from
https://mega.nz/#!ixdnhDLK!oOaAsJrcvJI0vH3fTsUOYjtDxQ_HT61E-_iuo6fTuKk
as specified in elephone forum flashing guide
http://bbs.elephone.hk/thread-1037-1-1.html#.VWgkX_RAU-0

Use latest v5.162 version
Gesendet von meinem P9000 mit Tapatalk

Linux way?
Is there a way to root my brand new P9000 in Linux?

I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?

sundawn said:
I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?
Click to expand...
Click to collapse
Why on earth are you using such an old version of SuperSU?
You are probably using TWRP 3.0.0 which does not work on newer ROM versions. Try flashing TWRP 3.0.2-1.

Well i used it because it is said to work in this tutorial
The newer one didnt work either, as you said i think its the TWRP 3.0.0
I would like to download this http://www.needrom.com/download/twrp-3-0-2-1-4/
but i dont get any registration mails, tried to register with 2 different emails half an hour ago...
The version here on XDA is said to be only for P9000 Lite.
Edit: Ok got my login by using the forgot password function - the linked TWRP 3.0.2 and installing SuperSU 2.65 works.
Thanks!

also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?

n1ck75 said:
also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?
Click to expand...
Click to collapse
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk

skeleton1911 said:
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk
Click to expand...
Click to collapse
Thanks for the prompt reply;
Have got to the fastboot oem unlock part, gives option for
Vol Up - Unlock
Vol Down - Cancel
Vol Up doesn't work? Can only Vol Down

[Guide] VoLTE/VoWiFi/ViLTE/EVS HD+ codec [no root] latest OOS 11.0.7.7

To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “qud.win.1.1_installer_10061.1.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
You should see some Chinese characters on display
8) Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6"
9) In CMD:
ADB shell
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
10) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator”, select device with filled "EFS" and "Banner" fields and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps in PDC.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
11) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
12) In ADB:
ADB reboot
13) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
14) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
15) Disable USB Debugging if necessary.
16) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
After update to latest version VoLTE was not working again. I think we should repeats this step after every update, until OnePlus (if) fixed this issue.

Hello.
Does the step 9 has to be done , becouse i cant get a connection with efs explorer. Its just blank. I ask becouse i have volte and vowifi activated but my phone wont turn automatic to vowifi when i get a wifi connection. i have to first turn off volte and reboot that the phone connects to vowifi

zorantoma
Hi. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?

vip77 said:
To be safe, make a backup via TRWP of your EFS partition BEFORE you flash anything! If you're not rooted, do a nandroid backup via fastboot
Steps:
1) Set your stock dialer app as default
2) Download and install “Logkit+v1.0.apk”
3) Open dialer app and enter *#800#
Scroll down to Function Switch and then tick-mark the “VoLTE”, “VoWifi” and “VTSwitch”. Exit from app and reboot phone. Go to Settings->Wi-Fi & Network->Sim & Network->Sim 1 and enable “VoLTE” & “Wi-Fi Calling” options. Repeat step for SIM 2 if necessary. Reboot phone.
4)Download and install to PC “QPST_2.7.496” + “QUD.WIN.1.1+Installer-10037.3+Setup.zip”
5) Enable Developer options and “USB debugging”
6) Download and install “engineeringmode_V1.01.0.171117173719.25c8842-26.apk”
Open dialer app and enter *#801#
Set “Full-port switch” to ON
7) Connect your phone to PC via USB and allow USB debugging on phone
Run ADB as administrator (if you haven’t download and install to your PC)
In CMD:
ADB reboot ftm
ADB shell
setprop sys.usb.config diag,serial_cdev,rmnet,adb
You should see some Chinese characters on display
8) Run “as administrator” PDC from QPST package. Select “Qualcomm HS-USB WWAN Adapter 9091” from list. In some cases PDC can’t connect to your phone. There is a strange solution:
Run EFS explorer from QPST package “as administrator” and connect to your phone. In the moment of connection PDC works as excepted. Listing of EFS explorer takes a lot time, but after successful connection PDC stops working again. Close EFS and repeat step to finish all following steps.
In PDC right click on "Oversea-Commercial_DS" and deactivate “Sub0” and “Sub1”
Click on “Oversea-Commercial_DS” again and click remove.
Select “India-VoLTE-Vodafone”, right click and SetSelectedConfig for both “Sub0” and “Sub1”. Then click Activate button. Close PDC.
9) Download and extract “Audio+codec+EVS+HD+.zip”
Run EFC explorer “as administrator” and connect to your phone if not done earlier.
Backup to PC “overideconfig” and “overideconfig_Subscription01” from “/efsprofiles/” folder.
Replace “overideconfig” and “overideconfig_Subscription01” from “Audio+codec+EVS+HD+.zip” package with “Discard” “Clean-Up Option”. (Right click on file, “copy Data File from PC..”)
10) In ADB:
ADB reboot
11) Install “com.oem.oemlogkit_1.0.200929184727.270d7d2-1.apk” to return stock logkit.
12) Open dialer app and enter *#801#
Set “Full-port switch” to OFF
13) Disable USB Debugging if necessary.
14) Set back your custom dialer if necessary.
That’s all. You have VoLTE/VoWiFi/ViLTE/EVS HD+ codec. Icons in dialer and curtain.
View attachment 5202729View attachment 5202731View attachment 5202727View attachment 5202725
Click to expand...
Click to collapse
hi i have a problem, i can't connect my op8 to efs file explore, it tells me it is not supported

Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot

vip77 said:
Hi,
patonovich
Same question. Do you have "Qualcomm HS-USB WWAN Adapter 9091" in windows device manager after "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command in ADB Shell?
Also, what Build number and Model you have? Attach screenshot
Click to expand...
Click to collapse
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator

this is what i get when i run efs explorer

patonovich said:
Yes Qualcomm appears, I could change the data with pdc, but i can't copying the files, it tells me that the cell phone is not compatible, sorry my English google translator
Click to expand...
Click to collapse
zorantoma said:
this is what i get when i run efs explorer
Click to expand...
Click to collapse
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.

vip77 said:
Ok, folks. I checked again on clean device and latest version OS 11.0.4.4.IN21AA. there are some changes.
It's seems like QPST need COM device to communicate.
Disconnect your phone.
Update Qualcom driver to newer version (download in attachments 1st post section).
Connect your phone.
After "ADB reboot ftm" command BEFORE entering shell and "setprop sys.usb.config diag,serial_cdev,rmnet,adb" (look at updated command) :
Go to Device manager. You should see two "IN2010" devices in "Other devices" section. You need device with PID "MI_00", in my case it's second one. You could check, who is MI_00: Right click on device, properties, Events tab (look at screenshot).
When you find correct device, right click "Update Drivers", "Let me pick from a list...", select "Ports (COM & LPT)", select "Manufacturer -> Qualcomn Incorporated, Model -> Qualcomm HS-USB Diagnostics 90B6". After that, enter to ADB shell and use command "setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb" (edited). You should see your phone in EFS Eplorer and able to connect (select device with filled "EFS" and "Banner" fields. look at screenshot).
After update to latest version VoLTE was not working again. I think we should repeat this steps after every update, until OnePlus (if) fixed this issue.
Click to expand...
Click to collapse
WOW thanks

patonovich said:
WOW thanks
Click to expand...
Click to collapse
Please report if everything went well. Good luck.

del

Thank you, it worked.
BR

Working great on OP8T,
Before this guide the Volte profile was change to the default oversea profile.
Thanl you.
UPDATE -
for some reason the OVERSEA profile is active , and volte is lost.
after that i change overideconfig files to Read only after
i copy the file to efsprofiles ,
its work for now for two days in row ,
before that the phone change to ovesea profile in half day.

not working :/
i tried exactly this and not working op8t

Grigiac said:
not working :/
i tried exactly this and not working op8t
Click to expand...
Click to collapse
What exactly "not working" which step?

vip77 said:
What exactly "not working" which step?
Click to expand...
Click to collapse
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t

Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.

vip77 said:
Do you have VOLTE supported and activated by carrier? Be sure using Sim slot 1 also.
Click to expand...
Click to collapse
yes, i did it with pdc on my last device op6 with other guide and work great
but now i have new device and tried with this guide..
and im using slot 1
i have no idea why its not working :/

Grigiac said:
I performed all the steps without error
At the end when I restart the device via ADB, I just do not have a volte symbol..
i tried to return to PDC to see if its still active on india sub 0 +1 and its active
but still dont have VOLTE
my device kb2000 opt8t
Click to expand...
Click to collapse
On which country are you?

Dreamelba said:
On which country are you?
Click to expand...
Click to collapse
Israel
tried India & telfonica uk
Nothing work

[GUIDE] VoLTE & VoWIFI on 11.0.5.5 Oneplus 8 PRO

Hi,
I've recently upgraded my phone from version 11.0.4.4 to 11.0.5.5 and after upgrade all my modem configs were reverted to the default ones. I was not able to use VoLTE & VoWIFI as before.
Previous guides to run PDC tool didn't want to work on my unit, but after several hours, I've managed to solve how to do this. I'm sharing my method to all who has similar problems.
All the files for procedure are attached to the thread (use GUIDE ONEPLUS8 PDF) to see the procedure with screenshots. There is also guide how to root phone but it's not mandatory for VoLTE, VoWIFI change.
For POLAND PLAY VoLTE & VoWIFI choose DT_COMMERCIAL instead of PLAY_COMMERCIAL
VOLTE & VOWIFI – ACTIVATION & MODEM CHANGE
1. Enable USB debugging and have adb android shell installed
2. Upload to APK from tools folder to phone directory called Download
com.android.engineeringmode_V1.01.0.171117173719.25c8842-26_minAPI26(nodpi)_apkmirror.com.apk
com.oem.oemlogkit_1.0-1.apk
3. Find the apps and install
4. Type code on your phone *#800#
5. Don’t choose any app, stay in OnePlusLogKit
[GUIDE] Magisk for OxygenOS 11
Instructions - Download the magisk_patched.img - Reboot your device in bootloader-fastboot mode - Flash the patched_boot.img in the boot partition: fastboot flash boot boot.img replace "boot.img" with the magisk_patched.img path However, it...
forum.xda-developers.com
6. Go to Function Switch and enable (each time phone reboots)
a. VoLTE switch
b. VoWifi switch
c. VT switch
7. Go to your SIM Card in Settings and enable VoLTE and VoWIFI
8. Install QUD.WIN and QPST from the tools folder on Windows
9. Open CMD
# cd C:/adb
# adb reboot ftm
(this would turn off phone in development mode)
# adb shell
# setprop sys.usb.config diag,serial_cdev,rmnet,adb
(this enables diagnostic port needed for PDC)
10. Open Device Manager in Windows
11. Look for device IN20AA without driver – in the details find one with identifier MM_00 (there will be 3 same names but different identifiers)
12. Pick driver manually from file qqwan0.inf
13. Choose manually Qualcomm HS-USB WWAN adapter and adapt
14. There is gonna both devices visible in the Device Manager after few refreshes
a. Qualcomm HS-USB WWAN adapter
b. Qualcomm HS-USB WWAN adapter 9091
15. Try PDC with WWAN adapter 9091 if it’s working
16. If not, Unplug & plug the device (don’t write once more setprop, just plug it back)
17. In the Device Manager in Windows, delete Qualcomm HS-USB WWAN adapter but leave Qualcomm HS-USB WWAN adapter 9091
18. Open PDC once again and choose the only left Qualcomm HS-USB WWAN adapter 9091
19. The list of configs will be loaded
20. To change the modem config choose desired config ex. Commercial DT_POLAND (OLD ROW_COMMERCIAL NOT WORKING) – choose name, right click, select SUB0, SUB1 and click ACTIVATE. Check if in the row of your new modem config in SUB0 and SUB1 you have active setting
NOTE# For PLAY PL 260-06: DT Poland Commercial has VoLTE & VoWIFI
21. Close PDC. In cmd type command and reboot phone
# adb shell
Oneplus8$ reboot
NOTE!!! PDC MODEM SETTINGS MAY REVERT ONCE YOU TAKE THE SIM CARD OUT OF TRAY. YOU NEED TO MAKE THE CHANGE AGAIN TO DESIRED MODEM CONFIG.
#############################
CHANGE CARRIER POLICIES (UNLOCK BANDS)
Prerequisite is to have engineer apk installed.
1. Plug the phone into PC and dial *#801#
2. Turn on the Engineer Mode Toogle only
BASED ON: https://mt-tech.fi/en/modify-oneplus-7-pro-5g-8-and-8-pro-nr-lte-a-band-combos/
You have to install diag-driver manually if you have Android 11 installed. Check in Device Manager after enabled Engineer Toggle and connected USB to your computer you see two Unknown device labeled your phone model number. I have IN2013 (OnePlus 8 Europe).
Unknown devices in Device Manager
• Download Qualcomm diag-drivers and extract compressed zip-file.
• Right click the device and select Update driver.
• Select Browse my computer for drivers
• Select Let me pick from a list of available drivers on my computer.
• Select All devices.
• Browse drivers in extracted Qualcomm Drivers zip and find qmdm.inf
• Then find Qualcomm HS-USB MDM Diagnostics 90B6 and click Next to install it. You may get warning because hardware id doesn’t match. This driver still works fine.
• Now install same driver to second unknown devices (IN2013 if you have same model).
3. Now you should have driver installed to both interfaces.
4. Open QPST Configuration, Wait for Phone list in the window
5. Then go to Start Clients > QPST EFS EXPLORER
6. It will list all the QUALCOMM directories. Go to policyman directory
7. Copy the carrier_policy.xml (SIM1), carrier_policy.xml_Subscription01(SIM2) and lte_feature_restrictions
8. Modify files accordingly:
Modify OnePlus 7 Pro 5G, 8 and 8 Pro, 9 and 9 Pro NR/LTE-A band combos - MT-TECH.FI
On this instruction we will modify OnePlus 7 Pro 5G, 8 and 8 Pro band combo profiles with Qualcomm software. OnePlus has limited 5G access and 4G+/LTE+ Carrier Aggregation combinations and this instruction help you to unlock. However this instruction doesn’t unlock hardware defined combinations...
mt-tech.fi
or overwrite in QPST files with the modified files for PLMN 26066 with 5G and DSS enabled from folder on Onedrive called policyman (modified)
9. Reboot the phone
10. Dial in *#*#4636#*#*
11. Choose Phone
12. Choose Band config NR/LTE/TDSCDMA/GSM/WCDMA
Now it should work with all 5G bands regardless of some restrictions for not supported PLMNS

thanks. worked like a charm

thanks but after read the guide i think its to hard for me to do.
anyone have easyer method ?
after flash RadioActive kernel i lost VoLTE. (OOS 11.0.9.9.IN11AA)

I was unable to install any of the log kit provided. error given was ' conflicts with an existing package'. Any help?

momiloco said:
I was unable to install any of the log kit provided. error given was ' conflicts with an existing package'. Any help?
Click to expand...
Click to collapse
This is for OOS 11 Android 11
In A12 not is possible install logkit.

any idea what we can do in A12?

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.