I wanted to flash twrp recovery on my opo using sdk platform-tools with out android studio for unlocking and flashing oxygen os. I am using windows 10 laptop. Although my mobile device shows under "adb devices" , other commands like "fastboot reboot" doesnt work. cmd stops at "waiting for the device". I tried several drivers, but windows is only taking inbuilt mtp driver for usb. Not one plus or samsung drivers . Or Is this not a driver issue ?
please help. How can i resolve this on windows 10. How to flash custom rom to opo using only platform tools on windows 10.
Related
I keep trying to install the fastboot android drivers on windows 10 but every time I connect my shield tablet original to windows 10 laptop. It's already recognized and is put under the Category "Universal Serial Bus Devices" as the name "Shield Tablet". Then after I try to install the adb drivers, I try the command fastboot reboot, but it stays at "waiting for device". What should I do now? Im just trying to flash the official build version of TWRP on my Shield tablet original WIFI. Thanks for the help!!!!
Grab the Shield drivers from here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
koop1955 said:
Grab the Shield drivers from here: https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
Click to expand...
Click to collapse
That is only compatible with windows 7,8,8.1
RunicGamer said:
That is only compatible with windows 7,8,8.1
Click to expand...
Click to collapse
Did you try installing them? I am running Windows 10 and have those drivers installed.
Here is a guide to installing drivers on Windows 10: http://en.code-bude.net/2015/08/19/how-to-install-unsigned-drivers-in-windows-10/
I had to do the manual install on Win10. Hit browse, show list, pick folder, etc. I think it comes up as Android Device Interface or something to that effect.
There is a problem recognizing the adb driver on Windows 10.
can not recognize the device in the adb state.
In normal mode, the adb device is recognized.
Device recognition in the adb state is recognized as a lemobile android device.
lemobile android device driver is suspicious.
This issue prevents the bootloader unlock code from being recognized.
If you try to install multiple drivers, it will be recognized as a lemobile android device.
Is it a problem with adb driver recognition?
Please see the photo.
So I want to flash stock rom back but when flashing my laptop freeze and I cannot do anything....tried many times and same problem..try run adb command in platform tool and adb device list not showing my pixel..how to fix this problem?
The first time I got my pixel I had to manually install drivers from the official android developers website, after that my PC detected my phone when in ADB and fastboot.
Make sure you also have the latest platform tools (28.0.2), get them from here
My adb detect my pixel in fastboot command..but in adb command cannot detect "adb devices"
TENN3R said:
The first time I got my pixel I had to manually install drivers from the official android developers website, after that my PC detected my phone when in ADB and fastboot.
Make sure you also have the latest platform tools (28.0.2), get them from here
Click to expand...
Click to collapse
The latest is actually 29.0.1. They haven't been updating the changelog. Try to download it now, and you'll see.
:good:
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
herkio1 said:
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
Click to expand...
Click to collapse
Adb use Adb.exe and fastboot fasboot.exe (differente programs)
For Twrp you must use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
download sdk Platform tools https://developer.android.com/studio/releases/platform-tools.
extract platform-tools folder.
Put this twrp https://androidfilehost.com/?fid=17248734326145679747 into platform tools folder
Phone in fastboot mode power and volume - (Obviously the phone must be detected on the pc)
use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
Solved thanks, I used fastboot for fastboot mode and adb for in twrp/booted in system. I must have mistyped because I could flash the twrp.img file but it then gave me an error when trying to boot into it.