Im rocking the OP3 With Oxygen 3.2.7 Im just got the phone 3 days ago and i have been trying to root via the Toolkit : http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
I have done as https://www.youtube.com/watch?v=BQOJR5sUto0&ab_channel=OnePlusExclusive
But when i check the bootloader status or tried to unlock it is reboots into fastboot but just says in cmd "Waiting for anydevice" I have install the drivers via the drive on the PC when you plug in the OP3 and remove and tried again via the Toolkit. All I can find is that it is a problem with the drivers on the PC, but I can't figure this one out
Help a friend in need please!
!!!Fixed!!!
Had to start PC without "driver signature enforcement"
Related
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
get this: [Toolkit] Wug's Nexus Root Toolkit v2.02
It has a guide for the folder you have, under: Initial Setup > Full Driver Installation Guide... > Step 3 > Driver Solution # > Manual Configuration.
coolncool said:
its connecting fine normally as mtp
want to flash another rom as phone has gotten very slow like some chinese crap cell, trying to root it
but whenever i enable debug mode it shows drivers not installed successfully, i have installed every possible samsung driver that i could find online
a guide has given link for the drivers but that folder shows only this so what do i do with it?
i am unable to get past this simple step, n there r so many steps left, root, unlock bootloader, install cwm, flash rom
in device manager it shows this
i have wasted more than 1hr but still nothing
kindly some1 help me
Click to expand...
Click to collapse
...
You should be asking these questions on a Windows forum.
You need to right click Android 1.0 device... Update Driver (basically, tell Windows Device Manager that the driver for the "Android 1.0" device is in that folder you got there)... it will install it, and that part is done. Then reboot the device to fastboot mode and manually update the driver again (it will come up as a different, yet again unknown device, you just feed it the same driver again)
Also... for the operations you're mentioning... "root, unlock bootloader, install cwm, flash rom".... you probably won't even need ADB, just fastboot. As in, you don't need to root before all that. You root in the end. And most custom roms are already rooted too.
This is assuming there's an exploit out there that still allows for root to be achieved without unlocking the bootloader.
Hello,
Ever since the latest oxygen os update, my device got wiped from it's root and twrp. And for the past week when I have been trying to reroot it (w/ the bootloader unlocked) it won't even bother to detect the devices. I have tried reinstalling the drivers, using and different port, fasboot.exe, rebooting my pc, etc but nothing is working. Also, it detects it as an ADB device.
I really need this to be fixed asap as I will be sending my device for a screen repair and will loose all my data if I don't root my device and use titanium backup.
~ ronaldonater.
I have the same issue and am curious how this is fixed. I have Windows 10 and the oneplus three. ADB recognizes device and "adb reboot bootloader" reboots the phone into bootloader. Then "fastboot devices" just says searching for devices. I am tired of having to use my widows 7 laptop each time. Any help would be greatly appreciated.
My phone not recognised on pc. Not even on twrp. I reinstaled drivers, adb..., nothing. Then i tryied on pc at work. Booom! it works. When I arrived home i've reinstaled windows on my laptop. 100% works.
had the very same issue. the phone would detect properly on my work laptop running Win 7 but wouldn't recognise on my home PC running Win10. Tried every ADB tool and driver available out there. But nothing seemed to work.
Problem is with driver conflicts.
Then tried the age old method of factory reseting my PC, installed Minimal ADB tool and voila!!!
everything started like a charm.
First of all go into Windows drivrs and select hidden drivers and delete your entire driver history for that machine and reboot, then connect your phone whilst it's booted up so it can install.
Connect phone in fastboot and let it install. After this you need to manually update the driver for the phone unless it's already showing "android bootloader interface" in device manager. Finally check over android SDK so it's up to date and you'll be good to go.
Greetings every one ..
I have a half dead Oneplus 3 Unlocked + Rooted
here is my problem
there is no OS in it and i flash TWRP many times via ADB and wont boot to it
and i tried to flash the stock recovery V2.0 and done successfully
the sideload mode Recognize my OP3 but when i try to flash the Oxygen Rom it Gives me cannot read
also i tried the Unbrick Tool when the device is connect it showing me Qualcomm hs-usb qdloader 9008
but when i power up the tool as administrator it showing me (no device)
see here : https://www.youtube.com/watch?v=BIbagVAXJJk
Thanks .
on the unbrick guide try method 2 but completley power off the device and count to 10 when holding the vol up button THEN plug the device in. i had that issue also. if you get errors or for some reason it dosnt show up again try on a diffrent pc it will work
Try method 2. BTW "cannot read" error has to do with faulty ADB drivers, get the platform ones
I did instal the right ADB drivers in fact
still no luck
The ones from platform tools? Since that "cannot read" error has nothing to do with your device. Have you tried renaming it? Rebooting your PC? Last one did wonders for me for some stupid reason.
Hi,
I also had this message of "can not read" in sideload mode, this problem often happens with Windows 10, so I used Windows 7 on another pc and it was OK.
I tried Windows 10 & 8.1 & 7 & XP
still The same problem
What if you flash Twrp and boot into it? Then u can adb push the filemm
I tried via fastboot and its done right
but when i reboot into the new TWRP recovery its stuck in the boot oneplus as same like the Video shown up
book an appointment with oneplus live chat so a service tec can fix it and if they ask if it was rooted say no
Hi,
If you access TWRP, install the Official Oneplus Recovery 4.0.2
In TWRP click "intaller" then choose "install image" and select the file you will have to copy to the phone in recovery mode.
Then restart in recovery mode, choose english, then "adb sideload mode"
From there you should be able to flash your phone with an official Nougat zip.
Do the under windows 7.
It is necessary to install the Oneplus USB drivers and ADB tool on your PC before any manipulation.
Finally I solved the problem
like i said B4 my phone wont boot into TWRP by any chance
i traid all the Officials TWRP one and they stuck on the boot image or power the phone off
i flashed a modified twrp (blu_spark 3.0.3-x) thanks for this beautiful smart man eng.stk if im not wrong
and thank you all for the help
i had similar issue...with several phones.. download Malwarebytes trial version and run it...i had a few stealth root tool kit viruses.causing my system to have a hiccup....
I updated my OP3 to OxygenOS 4.1.3 two days ago and obviously lost my root and custom recovery.
After the update, I used the OnePlus 3/3T unified Toolkit because it worked just fine for the past year.
However, upon checking the status of the device, it detected 0 devices connected.
Using the command prompt also gave me the same answer; no devices.
I already have USB debugging allowed/OEM unlocked and developer options enabled, and bootloader is already unlocked, so I don't know what's the problem with this.
Try to reinstall the drivers trough the toolkit. If that ain't worked try to install manually the driver in device controll in windows and select the driver that you can install when download sdk.
For a weird reason my windows, sometimes, lost the driver for adb devices and then i can, just like you, not see my adb or fastboot devices.
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Try these steps:
-uninstall previous version of SDK tools from PC
-download latest SDK Tools from HERE
-have a USB 2.0 cable available
-follow these steps to verify connectivity
see if these things help
Unless there is a specific reason you're still on Sept 8.0, I'd take this chance and upgrade to lasts 8.1 factory image.
evanxalmighty said:
I am getting a Unknown usb device (device descriptor request failed) It keep telling me usb device not recognized while being plugged it. I have tried several things
1. another windows 10 computer worked the first time then same error as a laptop.
2. unintalled the driver and rebooted.
3. also used multiple usb ports
cant find anything after searching
pixel 2 xl 8.0 September update
rooted lastest magisk 15.3
latest twrp installed
stock kernel
recently a fresh install a few days ago because i got it to work somehow but not anymore what do i do?
adb, fastboot, and storage cannot be accessed
Click to expand...
Click to collapse
I'm just spitballing here but....
With phone plugged in, on your pc, under device manage. When you open it up do you see unknown android device? That driver may need to be updated. Also, USB debugging is on, and the option to transfer files? Is your SDK platform-tools up to date?
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
I haven't seen it with this phone yet, but try changing the USB mode on your phone from the notification; I've had a few phones that refuse to work in specific modes.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
Have you tried a different USB-C-A cable just for the heck of it. May have to factory reset and see if that solves it.
evanxalmighty said:
I forgot to mention downloaded the platform tool for both computers. I never updated because i had root and nothing new was that interested enough to start all over. I followed the steps and nothing usb debugging is on. In device manager its says Unknown usb device (device descriptor request failed). I cant transfer files or anything. I tried updating to the google driver but it said it wasnt compatible.
Click to expand...
Click to collapse
So your driver is messed up. Did you use the driver below?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Sent from my taimen using XDA Labs
It won't let me install the driver I get some kind of error when selecting it. I was able to get it to work after plugging it in and out. Now that I updated to 8.1 everything was fine untill I got home. Now it's doing it again. I tried 2 different cables restarted my computer and laptop and can't figure out why it was working fine before without doing anything different.
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
JimSmith94 said:
Try this:
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
Click to expand...
Click to collapse
This definitely worked for me -- Thanks for posting!
I am having sort of the same problem. I was on Android 11 on my 2xl, rooted with fast boot boot twrp.Img and installed magisk and super super, all latest. I could not get gaps so I used Android flash tool to attempt to go back stock and it downloaded and flashed it but it is now stuck in loop, I reboot to recovery and it’s stock now and it will not be recognized by adb or fast boot,!0plesase help