I installed ClockworkMod universal ADB drivers. Can't seem to recognize the Wileyfox 2X in command line. Device state is already unlocked.
The thing doesn't have any OS installed either, I want to be using this as my daily driver since my Oneplus X died on me.
Anyone have any suggestions? I'm desperate, already tried pretty much everything.
I just want to flash TWRP so I can install a ROM on it but I've no clue.
What does "adb devices" produce?
Related
Hi all!
I'd like to unlock my bootloader, but fastboot just saying "waiting for any device". ADB works fine and i use "adb reboot bootloader" command to enter fastboot mode.
I think that i have installed all drivers. I tried three different computers and usb 3.0 and 2.0... nothing. ADB works with every machine, fastboot doesn't.
What can i do? Is there any other way to get Device-ID? Need help. Stock ROM is awful
sorry for the wrong section, can you move this to Q&A
My phone has exatly the same issue...The key is the usb driver...With the stock LG drivers the fastboot did not work to me either.
1, uninstall any lg drivers from your os
2, install PdaNet universal usb drivers
3, enjoy!
When i finish with the fastboot, i installed back the LG drivers for the correct MTP communications, but it's not neccesary!
Give it a try, good luck!
Use Ubuntu Linux on USB Stick
no driver issues just works
I have tried everything including installing drivers and updating the Android SDK on Windows 10 but I cannot recognize my Nexus 5x 16GB. When I inspect devices on chrome nothing shows up.
This comes after getting the 5X back from LG after the infamous bootloop issue. They claimed they fixed the flash memory but didn't bother ensuring the phone booted up properly with an OS. I can get to the bootloader and I can get to stock recovery but ADB and Fastboot cannot communicate with the phone.
Any thoughts from the experts, I'm pulling my hair out. If I dont respond right away its because tonight my wife's father in-law is visiting. But I'll do my best.
Finally got Fastboot back. I had to uninstall everything again, not just drivers but apps listed. I then used the tool from this post: http://forum.xda-developers.com/showthread.php?t=2588979 and installed everything, basically hit Y for it all. I also had to run this admin.
Then once the phone was plugged in while in the bootloader I had to update the driver to composite. This shows up when you uncheck compatible drivers. Finally it worked. Now to unbrick my phone!
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.
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 have searched the net high and low for a answer to this question but nothing I have tried works.
I have used every adb and fastboot installer i could find, but nothing i do get fastboot working on my 5t. ADB is recognised and i can reboot to the bootloader from a command shell. But as soon as i type "fastboot devices" it shows nothing.
I have been into device manager and it shows issues with the fastboot driver, i have tried everything i can think of to fix this issue.
I would really love to root my 5t and and have never encountered this many issues on any of my previous devices.
Running a 64gb OP5T and Windows 10
Thank you for your help
I have now re-installed windows 10, re-installed all drivers and ADB and fastboot. ADB is still working but nothing from fastboot. It's recognised properly in device manager but nothing shows up when I type fastboot devices or fastboot OEM unlock. Any tips would be great.
http://www.codeshuffle.in/2016/12/kenzo-fastboot-adb-connection-fix.html
check this link specially driver signature enforcement disable part, it may help
When you say "nothing shows up", what exactly is the response?
How are you getting into the bootloader? Use this from recovery or system:
Code:
adb reboot bootloader
Then proceed.
ADB is working fine. But as soon as I reboot to fastboot mode the phone doesn't respond. I can't work it out have tried everything.
djmcnz said:
When you say "nothing shows up", what exactly is the response?
Click to expand...
Click to collapse
^^
It just says waiting for device or says nothing and brings up a new line. I'm guessing the fastboot driver is the problem. I have installed the Oneplus drives included with the phone. I've installed the universal ones, still nothing.
Is there an individual fastboot driver I could manually install through device manager?
Appreciate the help.
The issue is finally fixed! I went into device manager and changed the driver from a list of drivers on my pc to WINUSB and now its working
Same problem here pal, how did you change driver to winusb, seems I've got all the gear just no idea... By gear I mean files/drivers lol. Rooted so many devices I thought this would be easy, looking forward to getting it sorted. I love a custom rom