How to: Modify Google's USB driver to work for fastboot - OnePlus 8 Pro Guides, News, & Discussion

So, I have a OnePlus 8 Pro (IN2025) running stock 11.0.4.4.IN11AA, but whenever I booted into the bootloader, Windows 10 device manager said no driver found, even though I had the current Google USB drivers installed. I checked the hardware ID of the fastboot device, and for me it's "USB\VID_18D1&PID_D00D&REV_0100". I looked in the driver INF, and of course that hardware ID is nowhere to be found. Here's what I did to modify Google's driver to work with my phone instead of trusting random shady downloads from the internet:
1.) Download current Google USB driver and unzip into a folder. currently: https://dl.google.com/android/repository/usb_driver_r13-windows.zip
2.) Disable driver verification. Run the following commands in an elevated command prompt and reboot Windows:
bcdedit /set testsigning on
bcdedit /set nointegritychecks on
bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS
3.) Open android_winusb.inf (from the USB driver folder) in your favorite text editor, like Notepad++. Look for a section labeled "[Google.NTamd64]". Scroll to the bottom of that section, you'll see hardware IDs for ";Project Tango (generic)". After those entries add this section:
;OnePlus 8 Pro
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
Save the modified INF file. Right-click and install it. Now you have a working fastboot driver. These instructions are for x64, for x86 do the same thing in the appropriate section. Cheers.
P.S. OEM unlocking from developer menu doesn't actually do anything in this OS build. You have to "fastboot oem unlock" to actually unlock the bootloader. This will also wipe your phone, so be prepared.
After you're finished it's probably best to turn driver verification back on. Run the following commands in an elevated command prompt and reboot Windows:
bcdedit /deletevalue loadoptions
bcdedit /set testsigning off
bcdedit /set nointegritychecks off

Even with a clean installation of windows I've always been able to plug and play with my phone's, including the 8 pro.
I know this issue happens so Windows 7 so if it helps with that then that's great.
So many seem to have issues though.. Hope this helps them

Right now my only source of internet connectivity is thru my OP8 Pro, so while in fastboot I didn't have internet. There may very well be a Windows Update driver that's downloaded and installed for USB\VID_18D1&PID_D00D for people with normal internet =)
Ideally Google would just add the hardware ID to their INF and re-sign it.

xenoglyph said:
Right now my only source of internet connectivity is thru my OP8 Pro, so while in fastboot I didn't have internet. There may very well be a Windows Update driver that's downloaded and installed for USB\VID_18D1&PID_D00D for people with normal internet =)
Ideally Google would just add the hardware ID to their INF and re-sign it.
Click to expand...
Click to collapse
Connect to a neighbours WiFi?
what about the drivers that are offered from the OnePlus phone when it's connected? Not sure if it does that anymore..

I'm a voluntaryist out in the middle of nowhere in the high desert of southern cali.... off-grid, self-designed 48v 15kw solar system, well, garden, chickens, goats, ducks, etc. I don't have neighbors with wifi, but i've got an almost decent Verizon signal. I'll get around to StarLink after higher priority projects are done.
And....regarding the driver option which I think typically showed up as a CD drive or another device....I don't recall seeing that option for any of the OS builds since I've had mine. Because obviously if I did, I probably wouldn't have created this thread =)

OP a much simpler method would be to create a bootable usb with the latest Ubuntu and install adb through apt (making sure you set up a persistent filesystem to retain adb) and just use Ubuntu for your Fastboot and adb needs. Linux is much more reliable when it comes to flashing in fastboot compared to windows

xenoglyph said:
I'm a voluntaryist out in the middle of nowhere in the high desert of southern cali.... off-grid, self-designed 48v 15kw solar system, well, garden, chickens, goats, ducks, etc. I don't have neighbors with wifi, but i've got an almost decent Verizon signal. I'll get around to StarLink after higher priority projects are done.
And....regarding the driver option which I think typically showed up as a CD drive or another device....I don't recall seeing that option for any of the OS builds since I've had mine. Because obviously if I did, I probably wouldn't have created this thread =)
Click to expand...
Click to collapse
Sounds lovely, I'd love to take some shots in the desert on my Telescope.
Can't remember if my phone gave the driver install option on the 8 pro as I never needed it.
I think in your situation I'd probably have downloaded the driver on my phone first then copied it over to windows directly.
Defo check our starlink, your situation is essentially what it was designed for..
Id be interested to see how well it works.

superchilpil said:
OP a much simpler method would be to create a bootable usb with the latest Ubuntu and install adb through apt (making sure you set up a persistent filesystem to retain adb) and just use Ubuntu for your Fastboot and adb needs. Linux is much more reliable when it comes to flashing in fastboot compared to windows
Click to expand...
Click to collapse
yah, i actually just cleared out a spare 2tb portable HD last night and stuck Kali on it. I'm so used to developing on Windows that sometimes I forget about Linux. The embarrassing thing is I actually admin a dedicated Linux server on an unmetered gigabit connection, lol

dladz said:
Sounds lovely, I'd love to take some shots in the desert on my Telescope.
Can't remember if my phone gave the driver install option on the 8 pro as I never needed it.
I think in your situation I'd probably have downloaded the driver on my phone first then copied it over to windows directly.
Defo check our starlink, your situation is essentially what it was designed for..
Id be interested to see how well it works.
Click to expand...
Click to collapse
the thing is, I couldn't find a driver on the internet for "USB\VID_18D1&PID_D00D" which I actually trusted. Not one from OnePlus, not one from Google. A couple shady looking ones that I wouldn't personally touch. That's why I modified the Google one (after downloading it via my USB tethered phone). Like superchilpil said tho, Linux is probably the sanest option of all.
Considering the fact that OnePlus now forces you to factory reset your device upon bootloader unlock....I'm guessing they're not exactly enthusiastic about supporting fastboot...Also, the big scary warning message on every cold boot regarding the unlocked bootloader lends further credence to the idea they're not too keen on the whole fastboot thing.
edit:
I mean, i did see listings for supposedly compatible drivers on various driver download sites...and I could have taken the time to verify the security certificates on said drivers....but I just have a pretty strict policy of avoiding those sites like the plague

haha !
that worked perfectly on windows 11
many thanks bro

Wish I would have seen this before I wiped and went back to Win10...
Thanks!

THANK YOU!!! This is exactly what I needed.

I've attached the signed drivers to the post. This driver can be installed and used for different Oneplus devices. You can directly install the INF file without modifying it. Also, since this driver is signed, there is no need to use bcdedit commands.

falcont said:
I've attached the signed drivers to the post. This driver can be installed and used for different Oneplus devices. You can directly install the INF file without modifying it. Also, since this driver is signed, there is no need to use bcdedit commands.
Click to expand...
Click to collapse
THANKS, dude!
Your driver is working well on Win10x64 for Xiaomi devices (Mi Max 3, Mi 11) as well.

Related

How to use SDK to root the phone?

Hi all,
I have just switched from the HD2 to the MT3G Slide and want to root the phone.
I knew how to do all the stuff on the HD2 from reading but cannot find any information here. The sticky placed on the top isn't much help because I know you need to use the Android SDK tool but I do not know how to set that up. & when I try to use the command line I cannot type in it. Please can someone give me some help on how to do this so I can get started on rooting my phone.
Thanks for reading!
you claim you read the sticky but yet if you had you would have seen the link on the first page i believe that tells you to get sdk from [link] and then on that page there is a link that says setting up SDK on your [OS] computer. then just follow the steps in there(which is really more like download file and double click setup) after that you can open up a terminal/console/cmd and type in cd \path to sdk\tools
if you are on mac or linux(unlikely since you can't read or search) you would type in
cd /path/to/sdk/tools notice how the slash between directories(folders) is the other way around
then follow the directions in the root thread(incredibly difficult i know but you should still try to do this part on your own)
tubaking182 said:
you claim you read the sticky but yet if you had you would have seen the link on the first page i believe that tells you to get sdk from [link] and then on that page there is a link that says setting up SDK on your [OS] computer. then just follow the steps in there(which is really more like download file and double click setup) after that you can open up a terminal/console/cmd and type in cd \path to sdk\tools
if you are on mac or linux(unlikely since you can't read or search) you would type in
cd /path/to/sdk/tools notice how the slash between directories(folders) is the other way around
then follow the directions in the root thread(incredibly difficult i know but you should still try to do this part on your own)
Click to expand...
Click to collapse
Okay I have downloaded all of the Android SDK already. I have read it but my issue is when I try to type in the command it will not let me type. I also read that Anroid SDK is for xp & vista only and that windows 7 was not listed, so it this my issue? The command line you speak of is the one with the SDK tools and not the acutal windows CMD line?
I have followed everything to the line but still cannot seem to get this to work.
and to be clear I did read and there is nothing on there that states you need to have SDK to root the MT3GS. It says to download the slide_root
what operating system are you doing this on? that would be more helpful so i could tell you how to set this up correctly
tubaking182 said:
what operating system are you doing this on? that would be more helpful so i could tell you how to set this up correctly
Click to expand...
Click to collapse
windows 7. I have android SDK and I have downloaded the 2.1 Android pack.
if you are using windows 7 x64(very likely) then you cannot use that computer and you should try using ubuntu(same as using mac for 99% of the steps and there is a thread in q and a talking about this right now) or setting up a virtual machine and installing xp and using that to hack your phone. virtual machines are easy to setup and use if you can use virtualbox
tubaking182 said:
if you are using windows 7 x64(very likely) then you cannot use that computer and you should try using ubuntu(same as using mac for 99% of the steps and there is a thread in q and a talking about this right now) or setting up a virtual machine and installing xp and using that to hack your phone. virtual machines are easy to setup and use if you can use virtualbox
Click to expand...
Click to collapse
download virtual box right now. will that come with xp installed on it or would I need to download that onto it?
thanks for all of your help.
you will need to get an xp install cd or iso to install xp on it. if you have any friends with xp install disks or you can find one online and use it as a trial(no key=no activation=30 day trial) then you can use it for a day and root with that.
disclaimer: i suggest totally legal versions of windows xp, any install disk you download or get illegally is your fault when the FBI/Bill Gates comes to the door
tubaking182 said:
you will need to get an xp install cd or iso to install xp on it. if you have any friends with xp install disks or you can find one online and use it as a trial(no key=no activation=30 day trial) then you can use it for a day and root with that.
disclaimer: i suggest totally legal versions of windows xp, any install disk you download or get illegally is your fault when the FBI/Bill Gates comes to the door
Click to expand...
Click to collapse
Instead of suggesting that he commits a felony why don't you tell him to use Ubuntu in the virtual machine? It'll take a little longer but it's less likely he'll be fined.
i didn't say commit a felony, and if you are going to use ubuntu then you don't need a virtual box(dumbass) you can use a live cd. i have been told by microsoft on MANY occasions that if you have a friend with XP install disks then you may use those, as well as the fact that installing it for one day in a virtual box is not illegal if you are not using a cracked key/re-used key, you can choose not to use a key and it is a temporary install for yourself to use either until you get a key, or the 30 days is up. much like you can buy vista/7 and install a different version if you like, but you will have to uninstall it and reinstall using the version i bought a key for once the trial has expired. read up and do your homework before you jump down someone's throat, it makes you look like an ass when i have to come back in here and teach you what a computer is
I set up and rooted two phones with windows 7.. I installed the sdk and pdanet drivers and thats it..
using 64-bit? last i knew there was no 64-bit adb driver so i didn't even try with my win7 x64 machine, i used my vista x32 box to root my phone.
http://forum.xda-developers.com/showthread.php?t=532719 this exact guide and links
tubaking182 said:
using 64-bit? last i knew there was no 64-bit adb driver so i didn't even try with my win7 x64 machine, i used my vista x32 box to root my phone.
Click to expand...
Click to collapse
I'm using Windows 7 x64 Bit Ultimate Edition..
The Guide was written from using Windows Machine Yes, it works just fine
eugene373 said:
I'm using Windows 7 x64 Bit Ultimate Edition..
The Guide was written from using Windows Machine Yes, it works just fine
Click to expand...
Click to collapse
Is there anyway that you could give me a little help on getting this to work. When ever I try to type in the command line when i pull up the SDK it doesn't do anything. and when I try to pull up abd it just pops up a CMD for a quick two seconds.
look at link I posted
turboyo said:
look at link I posted
Click to expand...
Click to collapse
thanks. didn't see it. saw the last post was posted by eugene and scrolled down as fast as i could lol.
So the Command line is the CMD program through windows? I don't understand why someone wouldn't set me straight on that since I was saying the command line in SDK wasn't letting me type anything
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
When I do this part it doesn't find the ABD driver but it does not have anywhere to install drivers from my pc at all on my windows 7
edit: found where to go to add the usb drivers but when I select the folder all I get is "windows cannot find driver software on your pc"
edit 2: Found out what driver I needed, thanks for the guide source going to try to root this thing finally
tubaking182 said:
using 64-bit? last i knew there was no 64-bit adb driver so i didn't even try with my win7 x64 machine, i used my vista x32 box to root my phone.
Click to expand...
Click to collapse
Lol seems to me another dumb ass MAC user with nothing more to than make fun of people for not buying a. Crappy MAC. Unless you edit video for a movie company. Don't buy mac. Steve Jobs is a jobber. Plus macs. Suck. Win 7 rocks. Hate vista. Stfu mactard....
Sent from my T-Mobile myTouch 3G Slide using XDA App
Ps not everyone should have a rooted phone. If after about a million tries. Just quit. There are plenty of how toos in the forums. They work read slowly and then read slowly again.
Sent from my T-Mobile myTouch 3G Slide using XDA App

[GUIDE] Crash Course in ADB/Unlocking on WINDOWS

Just wanted to try and put together something helpful for those who are unlocking their devices who might be doing this for the first time or just are having issues.
THIS GUIDE ONLY WORKS FOR WINDOWS FOLK, SORRY! IF YOU HAPPEN TO BREAK YOUR DEVICE OR DO ANYTHING TO IT THAT PREVENTS YOU FROM USING, I AM NOT RESPONSIBLE, CAVETE LIBERUM OPUS.
ADB
Download ADB from here: http://developer.android.com/sdk/index.html
Make sure you install it where ever you are comfortable with, I tend to keep mine in my main installation (C: )
HTC Sync
Download HTC Sync here - http://www.htc.com/www/software/htc-sync-manager/
Why download HTC Sync? For the drivers. After the installation is complete you can remove HTC Sync, just not the drivers.
Appropriate Drivers
In your Program Files (x86) folder, there should be an HTC Folder, with the drivers in it.
What you are going to need to do is make sure that your device has the HTC drivers installed.
You'll need to open Control Panel ----> Hardware and Sound ----> Device Manager
Your HTC One should be under portable device or android phone, or something similar to that. If it is telling you the current drivers are up to date, you may need to disable driver signature enforcement, and that method is different between Windows 7 and 8.
You'll want to update the driver software by right clicking ----> Update Driver Software ----> Browse my computer for driver software ----> Browse...; then select the HTC Driver folder from within the HTC folder (you'll have to navigate to it)
If you need to disable driver signature:
Windows 7 - http://bit.ly/1bE0jZT
Windows 8 - http://bit.ly/1bE0mF7
Trouble Shooting ADB and Rumrunner
I am, in no way, saying that I am an expert in running rumrunner. If you can use irc and contact beaups please do. However, just in general, here are tips I think might work -
Go to "System and Security" from Control Panel and click "Allow an app through Windows Firewall." Click "Change Settings" at the top and then click "Allow another app...". Navigate to your extracted rumrunner file and select the soju.exe to be allowed through. Why do this? Because I personally rather not take down my entire firewall to allow this program to run. No offense to beaups, just doesn't seem terribly practical to me.
In your ADB installation folder, go into SDK -----> platform tools ----> Hold down left shift and right click -----> Open command window here
type in adb devices; if you are not seeing
List of devices attached
XXXXXXXXXXXXXXXXXX device (read the X's as a string of numbers which are your device)
then it isn't ready to be use rumrunner. You'll have to go into Settings -----> About Phone -----> Software Information -----> Then click 7 times on Build Number to unlock developer options. Go into "Developer Options" and enable USB Debugging.
As mentioned in Rumrunner, please run soju.exe AS ADMINISTRATOR, to avoid permission issues on computer-side.
OEM Cables are also ideal in this situation. Also make sure you downloaded the right file (.8 version versus .10)
Last but not least, IT TAKES A WHILE FOR SOJU TO RUN. BE PATIENT Your phone will reboot A LOT during the entire process. It'll take awhile, but if you run into the (.........) problems or an error because your drivers aren't installed correctly be patient.
The guide isn't perfect, but hopefully it helps. I'll add advice if it comes in.
Great guide!
Make sure to remember to do a fastboot devices check too. that is my problem adb works great fastboot is another story
Sent from my HTC6500LVW using xda app-developers app
It also hates USB3
It also hates USB 3.0, had to use my fiances laptop todo it, but very straightforward.

TP-LINK Android Phone / ADB Device

Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either
MKD73 said:
Ok so i'm pulling whats left of my hair out as I cannot seem to be able to remove this pest of a driver , windows 8.1 Pro is insisting my Nexus 5X is a TP-Link Android Phone and keeps over writing my google adb drivers so my fastboot / adb no longer works , has / is anybody having this problem? wugfresh install wont overwrite the TP-Link either all universal adb installers wont work either
Click to expand...
Click to collapse
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?
Alcolawl said:
Kind of surprised you're still running Windows 8.1. Windows 10 is free for you and better in just about every way, regardless of the UI changes. Just a recommendation, though I doubt it'd fix your issue.
There's an easy way to tackle this but it depends on how the driver is being installed. If you're connecting your phone to your computer and Windows is insisting on downloading and installing this "TP-Link" driver from Windows Update, there is a way to disable this in a few easy steps. If you're connecting your phone to your computer and Windows just assumes that it's a "TP-Link Android Phone" and applies the wrong pre-loaded driver (usually gives you a notification near the clock) then we're gonna have to get a bit crafty.
EDIT: Silly question. You don't have USB tethering or any wacky app that would be causing this issue, right?
Click to expand...
Click to collapse
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.
MKD73 said:
Yeah we will have to get a bit crafty, i hid the TP-Link update in windows update god knows how it got installed but its in and i removed it but its still insisting its a TP-Link Android Phone , man its bugging me out . No tether app or other apps no, thats why im lost as to why its started this BS , windows i know can be tricky WIN10 was not for me plus the free upgrade has past now (29July) anyway.
Click to expand...
Click to collapse
Would you mind doing something for me before performing the steps I'm going to list below? Go into Device Manager with the phone plugged in and installed as the stupid "TP-Link" BS and find it in the list of devices. Should probably be under Portable Devices or something. Right click it and click Properties, go to the Driver tab and click "Driver Details". All of the drivers should be located in the 'system32/DRIVERS' folder. Mind giving me the names of those drivers listed? Naming convention is typically driverName.sys.
Additionally, we're going to try a Group Policy change. Hit Windows Key + R and type 'gpedit.msc' and hit enter. A window labeled "Local Group Policy Editor" should come up. Then do the following:
Expand Computer Configuration (Left hand side, the navigation panel)
Expand Administrative Templates
Expand System
Expand Device Installation
Click Device Installation Restrictions
On the right hand side, now, there should be a list of restrictions. Somewhere in that list there should be an item "Prevent installation of devices not described by other policy settings". Double-click that and another window named the same thing should pop up. In the top left, set it to enabled and click Apply, then OK.
Unplug your phone and get rid of that ****ty driver if you haven't already and then restart and try connecting the phone again to see if the same incorrect driver install occurs.
@MKD73 You ever get this sorted out?
Sorry been away on holiday for the weekend , I'll be taking a look in the morning :victory:
Please give update
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838
kalikotpepot said:
Have you resolved this issue? My laptop is acting the same. Device manager sees my phone as "TP-Link Android Phone" with sub category of "Android Bootloader Interface." I can't use ADB with it, not recognized.
I tried doing what Alcolawl said but nothing happens. When I right click the "TP Link--- it just says general properties, no 'drivers' etc. I saw the 'driver' option in the "Andoid bootloader Interface" . It says the driver is: winusb.sys, wdfCoInstaller01009.dll and WinUSBInstaller2.dll. When I tried to edit the group, it says "Windows can not find gpedit.msc
Hope you can help me. My phone is stuck in fastboost mode- LG D838
Click to expand...
Click to collapse
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?
loeage said:
Hi Kalikotpepot,
Got the same issue here., Nexus 5x keeps on rebooting, no way to get to recovery and shows as TP Link on my computer. Did you manage to sort it out somehow?
Click to expand...
Click to collapse
I did it. Execute :
Code:
rundll32.exe newdev.dll,DeviceInternetSettingUi 2
and prevent driver from being installed.
Help me please!
Did you guys manage to fix it? I tried everything you people said but it didn't work. I have a Blu Vivo Xi+ and my PC only recognizes it as TP-LINK Android Phone. I dumbly deleted it's OS and all it's data when trying to update it. I only have access to TWRP and fastboot, is there a way to fix it? I would love if someone could assist me ?.

Question Can't find the Virtual CD with the USB Drivers

Hiya folks.
I am feeling like kind of an idiot here but I can't find this magical virtual CD that allegedley contains the USB Drivers I need to allow ADB to play nicely with my phone.
The phone is connected, I can see and browse the internal storage on the "OnePlus 9 Pro 5G" folder - But there's no virtual CD showing up at all. I have tried with and without developer mode in all of the connection options (Charge only, Files, Photos).
I wouldn't mind except I want to unlock the bootloader, and I can't find any USB drivers that will work. There are a lot of dodgy looking sites, but none of them seem legit at all.
I am using Windows 11, and it's an unlocked North American T-Mobile phone.
[Update, tried on Windows 10 as well but that didn't have it either]
Lorry said:
Hiya folks.
I am feeling like kind of an idiot here but I can't find this magical virtual CD that allegedley contains the USB Drivers I need to allow ADB to play nicely with my phone.
The phone is connected, I can see and browse the internal storage on the "OnePlus 9 Pro 5G" folder - But there's no virtual CD showing up at all. I have tried with and without developer mode in all of the connection options (Charge only, Files, Photos).
I wouldn't mind except I want to unlock the bootloader, and I can't find any USB drivers that will work. There are a lot of dodgy looking sites, but none of them seem legit at all.
I am using Windows 11, and it's an unlocked North American T-Mobile phone.
[Update, tried on Windows 10 as well but that didn't have it either]
Click to expand...
Click to collapse
Are you talking about USB drivers for the OnePlus phone?
TheGhost1951 said:
Are you talking about USB drivers for the OnePlus phone?
Click to expand...
Click to collapse
Yes... I have managed to install it using somebody else's suggestion of installing "Driver Booster" which found and corrected it for me - But I'd still like a proper install package for it and I have no idea where that magical Virtual-CD is!
(Also I just noticed that my signature is about a decade or more out of date )
Lorry said:
Yes... I have managed to install it using somebody else's suggestion of installing "Driver Booster" which found and corrected it for me - But I'd still like a proper install package for it and I have no idea where that magical Virtual-CD is!
(Also I just noticed that my signature is about a decade or more out of date )
Click to expand...
Click to collapse
Just do a Google search for latest OnePlus USB drivers and you will find them very easy. Make sure to disable driver signature verification on PC and reboot before installing drivers and reboot after installing. Done!
Here are the drivers provided by support along side the MSM tool:
https://mega.nz/file/2cACiDgS#9U1K2-2WAu7lqp9ErX4C3eSdWJG0VnKIqbVRrLFxbWU
Give a man a fish and you feed him for the day! Teach a man to fish and you feed him for life!

ZenFone 2 Z00A(d) ZE551ML - can't boot - black/white screen, no bootloader, want Windows (KVM kernel/OS)

I recently bought Asus Zenfone, because here in Ukraine is war, so I want small device with Windows (electricity often is off here because rockets fall on our electrric infrastructure etc).
So I've bought Asus Zenfone 2 used (it costed 16,25$). It came without accumulator, and 1/3 screen working. So I went to radio-market to buy new battery, it costed + ~10.25$ + 2,5$ to install battery. Then I've bought new touchscreen for it for ~22,5$, plus payed ~6,25$ to install it. Then around 7,5$ to restore battery connectors (on device and accumulator). So finally it worked, and wanted to see how to install Windows on Zenfone. Sure, if I had possibility to buy anywhere Zenfone better, new, not used, - I'ld do it, but it is not that easily available, just like any other Intel smartphone.
So, I started reading - how to make my device rooted. I don't understand how to get root. I found on wikipedia, that rooting is different from unlocking bootloader, and realized - yes. I need to unlock bootloader, and to boot from external flash-disk and install windows, or at least - new kernel with KVM support. I used pn my Android (non intel) Limbo x86 emulator, it can run some old windows 98 etc, maybe even xp, never win 2000, and if it runs win-7 or win-8 - it is so terribly slow. So I decided to buy Asus Zenfone. As in KVM mode I can send commands to CPU directly, and hope this Windows works much faster than in emulator. I hope just at least to run Windows XP on it, I need to code some C# code, so that Andorid phone is not only for mp3-playing, internet on the go and make calls, but to learn, study and to work. I don't know why Microsot, Intel and other companies don't like Intel CPUs in mobiles. They could do it if they wanted. I like WIndows because most programs are for Windows. And I want desktop x86 windows also on every mobile, intead of all Androids.
Anyway, What I tried to with my Zenfone. I found one amazing experience - that our hero and inspirer (ley God blesses him, maybe he will work in Intel/AMD/Asus/Microsoft etc to make more newer KVM kernels for future x86 phones with windows) - so Ycavan made KVM for Asus Zenfone 2. Great, I've read his thread - https://forum.xda-developers.com/t/...0-with-kvm-bridge-compiled-need-help.3145055/ - completely, with pen and paper writing down important information, downloaded all the files, and decided to start flashing.
I copied them to root of my Zenfone, unpacked tars and converted them into ZIPs. I also unpacked .img files to root of phone (I mean its folder which is visible if I connect it thorught USB, I know it is not "/" root of file system of Andoird, but anyway it is visible even inside CWM... sorry, was visible)...
So, I made some mistakes. I downloaded the kernel, tried to flash it using commands like :
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150710.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150714.img
fastboot flash boot boot_fhd_2.19_kvm_bridge_20150717.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
fastboot flash boot boot_2.19_kvm_bridge.img
fastboot flash boot boot_fhd_2.20_kvm_bridge_20150820.img
but non of them produced bootable Zenfone. So I had to revert to previous bootloader using the CWM tool.
In fact I liked this CWM most. I found this thread - https://forum.xda-developers.com/t/...root-ze500-ze550-ze551-temporary-cwm.3114063/
or similar here on forum, and it worked amazingly. I attached Zen-phone to USB, turned it off, then on while pressing, keeping pressed volume-up key, and after Asus logo appeared and some "zzz" vibration, again it blinked and I saw bootloader with Android robot, and possibility to scroll through menu using volume up-down, to choose normal boot, or reboot/power off, or to run restore etc.
For some reason, Restore there not worked. So anyway, I understood that I can use tool like ADB (Android debug bridge) and fastboot to copy new firmwares/kernels/bootloaders etc to it, so I guessed I can do it myself, and was ready for risks... And this what bad can happen - it happened.
So, I runned in CWM - file cai_dat_CWM.bat - which asked to type ACCEPT and then T4, and phone started to go into amazing mode, some "clouds" started appearing on phone, and it loaded into special secret menu, from which I could select what to do next. To me it looked like default boot manager which I wanted to see like in Dos/Windows machines - so I can choose to run into safe mode windows, or set some settings before booting, or even use "reanimator dvd" etc to load Windows and other tools to do partitioning, passwrods recovery etc. So it looked like on desktops, and very nice. I went inside the menu, and found good option to make backup. I did it all. Then in same CWM tool (I think it is called SuperSU for Android), I finally choose to restore bootloader/kernel/boot (custom recovery), and this saved my from bricking the first time after I followed the manual from Ycavan. Well, I know I can read a lot more threads how to do this and that, but there is always risk that something wrong can happen. So I tried to read as much as I could, and follow manuals as precisely as I could understand. But my phone is kind of "bricked".
Now it shows some scfreen like TV which can't catch any tv program. So it is some random colors - see attached picture. It is good that it shows at least this. But in worse situation - it doesn't show anything. So let me tell how I achieved this, and if you can tell me how to avoid this mistake and to recover it. I hope to get help from anyone here who installed KVM kernel(s) and acheieved running Windows on their zenfone 2 (or maybe anyone who has XPerience with other x86 phones may help, or if it is general issue how to unbrick - then also non x86 users please help).
So, CWM made backup, I became more non-scared to make more experiments with firmware. But main problem is that I don't know which firmware to use. I ideally suggested that when I change kernel to KVM-supported from Ycavan - that it will work with my Andorid 5.0 (it was installed when I bought it). So, but unfortunately, after installing any of KVM kernels of Ycavan - I was unable to understand which OS to install, which version. So even I tried to try to flash whole 1GB+ image (I have downloaded UL-Z00A-WW-2.20.40.59-user.zip from official asus.com - https://www.asus.com/ua-ua/supportonly/asus zenfone 2 (ze551ml)/helpdesk_bios/ - but. I was unable to upload it to zenfone (flash it), as it said it is older than installed version.
Anyway, now it doesn't matter as I cannot run into ANdroid at all. Worse - I cannot even get Bootloader working in Android, as I see after turning phone on - only "white screen" with non-working TV-like image (see attached picture of my Zenfone 2).
So, to make this happen, I did this: I found some information about TWRP. I tried to install as recovery tool. Even though it was flashed into mobile, and I installed it from apk from Google-Play, still, I was unable to run it... So then I found even cooler tool - which was too risky to install. I was good, but Andorid stopped running at all.
This tool is called - preroot601. I runned in it preroot.bat, and then it did something similar to CWM, but several times it restartd the phone _ i have added screenshots of how it looked like on PC / Windows. So after several restarts, it did a lot of changes - Android didn't start after it. Phone always was able to start into recovery mode - into TWRP (I downloaded its .img and flased it as recovery for phone). But in TWRP I think I did something wrong. I made backup of all files (syste,, bootloader, everything). I saw it is cool - to see there terminal, ability so set attributes for files, mount partitions ... even USB -hey, can I run from flash-disk? or from external DVD/Bluray which I have in this mode? I have USB-hub, and can connect to it keyboard, mouse, flash-usb, ssd/hdd - all through Microusb-usb adapter and to usb-hub. So what I wanted to do is to try to see flash-disk, mount it on my android zenfone. And then after restart - I had black screen or this 'non-working analog-TV screen when no program/channel/wave is caught for signal"...
So, I don't even understand what I did, and why this all happened, and why I have to do to restore bootloader at least.
My aim is to have KVM enabled in the kernel. I don't mind if it is old Windows like XP working on this Zenfone, but I like windows to be my main OS on every phone which I may use in future (and hope they all be x86-64 and not ARM). So as I don't have Steamdect now (it has also AMD x86 CPU, like Zenfone), I want to do this, achieve it - having Windows on mobile - Zenfone.
I can carry it in pocket everywhere, so why not people like having desktop Windows x86-64 in each and every mobile? Even Lenovo are collaborating with IBM - then why not make also IBM-Mobile / IBM-smartphone, which will also be as good as PC - to unassemble it, change any part like on desktop, why not do it? I think everyone will enjoy it, and it will boost everything to better hights, levels.
So, please. If anyone here has similar experience of going to same screen like I have (see screenshot), or like that - black screen - indeed my device also may not even show any thing - even no ASUS logo, no bootloader (even if I press Volume-UP after powering and after flash it usually showed bootloader with robot - no... not now)...
So I don't see anything on screen of Android Zenfone now. no text, no bootloader, no recovery even - no TWRP menu. I think I am ready to format whole zenfone, and install there maybe some partition manager (like you know there is Partition magic on PCs, when I can split HDD/SSD nto two parts, one for Windows, and say other for Unix - Ubuntu or Android x 86 - all on same physical drive)... So I want some re-partitioning for intern SD memory, and be able to install there some ISOs, say with DOS, Win3.11, win 95, 98, 2000, xp, 7, 8,1 and maybe even 10. But guess last will be slow. I think Windows XP would be ideal OS for my Zenfone, if it can run fast. Win 7/8 maybe will be slow. But for some sceintific aims - like I just write some algorythm in Visual studio, and can do it even in WinXP, so why don't do it on my Zenfone? I don't like many Andorids, as they are not for work much - they are used by many people to play games, watch videos on phones, surf social networks, but not for real work. Real work is usually on WIndows, and no laptop can replace "Windows x86 in pocket" (on mobile). And I wonder why Microsoft develops "Windows for ARM" instead of investing millions into efforts like which Ycavan did - to make Windows run in KVM mode fast on x86 smartphones.
Ok, So, any ideas? What should I do now? I need some special tool to fix my phone first. Fix its loader. I think I need to bypass fastboot.exe restriction, which shows "waiting for device". Command in cmd like this: ADB.exe devices -L --- shows device from time to time - it shows:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
So, I cannot even flash some recovery device in this way. In devices manager I see "ADB interface" in "USB devices" category in devices treeview. And sometimes Moorefield appears, but with exclaimation mark - I have no idea how to make it disappear. I found here some info that I can install tool - xFSTK_Downloader_v1.7.0.zip - I downloaded it, installe,d but it doesn't run (I have win10 x64bit). hm... And driver required - iSOC_USB_Driver_Setup_v1.2.0.zip - I installed - but nothing.
So, what to do? How to make bootloader appear again? And how to write there prob=per bootloader with KVM kernel, and which firmware to flash so I can use KVM fast there with fast Windows...? Is it possible at all to make it run WIndows natively on Zenfone? or it will always be only in virtual machine inside some ArchLinux or in Limbo x86 on Android?
I read that Ycavan used this ArchLinux, but I don't understand why. Is he installing it over Android? Then also which version he uses? I need to know each and every version whcih he uses to make everything works. I 'ld require all the firmwares which he uses to make it work also - to make some Windows iso run on my Zenfone 2.
Did anyone achieved this successfully, except for Ycavan - to run Windows on Zenfone? Or except for him noone was able to install KVM kernel, and it was similar to mine situation? And maybe this is the reason why manufacturers of phons don't like x86 phones? I don't know. Any ideas?
See screenshots. What to do in this state?
IF anyone can please upload to somewhere whole pack of files ("WIndows on Zenfone starter kit") to make anyone able to just follow instaructions which will work in all cases to install WIndows there like Ycavan has - it would be great. There is lack of more detailed information - which .img files, .zips, firmwares etc, which OSes are supported by Ycavan's KVM kernels?
I have no idea. if anyone passed this path, and achieved Windows on Zenfone, please share your experiences, Ireally need it. Here in Ukraine when electricity disappears almost daily, we need devices like x86 phones almost for everyone. And mo matter if Windows is a bit old. KVM mode I guess must be much faster, almost native speed, so (like on tablet PCs), so please help...
Thank you all in advance, whoever will answer me.
indubhushan said:
c:\adb>adb devices -l
List of devices attached
0123456789ABCDEF device
c:\adb>fastboot flash boot boot_2.19_kvm_bridge.img
< waiting for device >
Click to expand...
Click to collapse
wrong mode. adb is only working in
- normal/boot mode
- recovery mode
fastboot is only working in
- bootloader mode
- fastboot mode
You can see 0123456789ABCDEF device in adb devices, therefore you are either in TWRP or in Android (Win?)
type adb shell and check the prompt is either $ (shell) or # (root shell)
in root shell you can flash partitions from cmd line. you can also reboot into bootloader/fastboot mode from cmd line.
Code:
adb reboot bootloader
I had success in restoring my bootloader (logo with android robot) - I intalled xFSTK, so somehow I had success to make it run, and I added threee files (1, 2, and 4th) and tried to flash it. Phone was visible as Moorefield. Then I tried to use Asus flash tool to flash big RAW image, but for some reason I don't know why - I had even whole day left it to flash, it didn't do the task - Android stopped booting - no logo showing at all - have to use xFSTK to recover. Maybe I use wrong RAW image (from official site it is .zip, so have no idea where to get those raw files).
When try to flash using flashboot - I get error: - flash cmd error.
As for devices list. My device rarely appear there. It may appear for some seconds, and then xfstk can have success to flash it, and maybe even make it runnable into Android robot scren (bootloader).
I am thinking that I need to install maybe ArchLinux, which Ycavan is using, but have no idea where to get RAW file for it, and how to flash it. Maybe some problem with my USB port on old laptop, or maybe even with USB cable (though have few good almost new cables, even new 4Amperes one). So maybe even problem in port of Zenfone itself (to change it). No idea. Because even when I tried to flash it (that huge 1GB file), phone disconnected, or showed "ready for commands", instead of showing process of ownloading RAW image/Android into phone's memory.
Flashboot/adb almost unusable. Well, I'll try, maybe it'll work.
My hope is try to go into CWM, run from it into "secret menu" on phone, and from it - to access internal memory of phone, and restore phone from backup. But when I tried to load into it once - it hanged on "clouds". I don't know...
And I don't think I'm ready now to format internal memory of phone or to repartition. At least I don't have backup on some external card (sd-card) etc.
as for adb. maybe it can't see my device, even if it is "recovery mode" (when see in devices manager in Windows - Moorefield). Now I'm stuck on xFSTK and can't go anywhere further like adding TWRP into phone, or foing into backup/restore menu on phone, and of course there is no Android. Even when I see Android robot (boot menu) - I feel happy, that at least phone shows anything, so at least bootloader workds. Maybe difference is in drivers - when I have Moorefield driver, then maybe it contradicts with Zenfone driver, and I have to reinstall them? Or use other OS? I have dual-boot (two Windowses on my laptop), so maybe I need to use one Windows - to work with Moorefield (xfstk) - when phone is in "worst" situation when no logo shows / no bootloader. And the other Windows I have to run on laptop - with Zenfone driver installed (I think it shows something like Asus device in device manager). But they seem to use contradicting drivers, I am not sure. And maybe it's some problem with my usb ports, but hope no. They seem to be ok... Maybe I'll have to go some day to give phone for diagnostics to repairing center again ;-(

Categories

Resources