hello, i am in a bootloop with my oneplus 6. wiped everything.
since then i tried using the msmdownload tool, but it's not recognizing the phone.
in the device manager the phone is currently being recognized under "kedacom usb device" as android bootloader interface. I tried doing an update to the drive and installing a quallcom drive, but always get an error message "The folder you specified doesn't contain a compatible software driver for your device. if the folder contains a driver, make sure it is designed to work with your computer". i downloaded a few windows program to force installation with no success. tried signing the .inf file of quallcom driver - same errorwhen i try again. when i write in cmd 'fastboot oem unlock' - it says that the device is already unlocked. when i try the command 'fastboot twrp.img' or fastboot boot it also fails. i even downloaded tool-all-in-one - doesn't help. when im making an uninstall of the android bootloader interface, after connecting the phone again - it automatically installs this driver again, even though i marked in the settings not to do that. all i get is a bootloader screen, nothing else.
p.s. new here so sorry if the thread is in the wrong place or something.
Related
Under Windows 8, you will likely run into the issue that you can get ADB to work properly, but cannot get Fastboot to work.
The reason is that ADB and Fastboot actually require/use two different drivers for each to work properly under Windows 8. But, only one of those, the driver that ADB will work under, will intall in a signed fashion that Windows 8 requires. You will need to enable Windows 8 to allow unsigned drivers to be installed, the steps are below.
You can install the normal HTC Sync, and the drivers/devices should be installed and work fine for ADB. You can test this by installing the SDK Tools for Windows and HTC Sync, then run "adb devices" from the command prompt, and it will find the device and work fine.
But...when you go into Fastboot mode, for example, to install a new custom recovery, the Fastboot.exe just flashes in the DOS window and nothing works.
Upon looking back into the Device Manager in Windows once in fastboot mode on the phone, it no longer recognizes the driver/device.
After some driver troubleshooting, I found that when the phone reboots into Fastboot mode, it needs another set of Generic Drivers, the typical ones you can find on the Web for HTC devices. The device while in Fastboot mode, under the Device Manager would show up with the Unknown icon instead of the My HTC device icons at the top of the list.
The issue is Windows 8 by default will not allow you to install unsigned drivers without jumping through some hoops.,
So here is what you do. You can download these generic drives, unzip them somewhere on the desktop, and have them ready.
http://androiddrivers.net/htc-android-drivers/download-htc-one-x-64-bit-windows-drivers/
(There are several other versions out there, just google "Windows 8 HTC One X Drivers" and you will find many to download, or the original HTC .exe. I like the zip file, easier to unzip, then update the driver.
Then, put your phone into Bootloader mode.
Go to Device Manager and notice that your phone is showing up as an Unknown Device in the list.
Now, in Windows 8:
1) Settings
2) Change PC Settings
3) Very bottom, Advanced Startup. Select this.
4) It brings you to another screen to select the options you want.
5) Troubleshoot
6) Advanced Options
7) Startup Settings, Select this option. You will see a list of options it gives you, included is "disable Driver signing"
Select this now and the computer will restart and provide another menu.
#7 is the option to boot the computer with driver signing disabled.
8) Once rebooted, your phone is still in bootloader mode, go back to device manager, right click the unknown android device, and update the driver manually, selecting the folder of the drivers you have downloaded previously.
It will then prompt about unsigned drivers, select Yes to install them anyway.
Now, your phone is detected in bootloader mode, and Fastboot will work properly to flash recovery etc.
this is pretty helpful but make sure you post in the right section
So I did what you did, and when i got to the screen to choose option 7, i tried with both F7 and hitting the number 7, then i went back into device management and tried to update the driver, but it didn't prompt me to install unsigned drivers.
Also, once you click settings, you have to click on general to find advanced options.
Any ideas?
---------- Post added at 12:53 PM ---------- Previous post was at 12:37 PM ----------
Ok, I got it workng, but theres a few more steps involved. Upon trying both drivers that you suggested downloading, when I run an adb devices command, it doesn't show anything under the devices attached listing.. Is that normal, or should I see my phone? I suspect this is why I'm having issues inside roms, since the boot.img isn't flashing correctly.
OK so I am trying the new root method and was able to push all files to my device. The device is recognized and can start when booted into the system. However, when I put my device into download mode and checked to see what port the device was on I got an error message: ">reg query HKLM\hardware\devicemap\SERIALCOMM 'reg' is not recognized as an internal or external command, operable program or batch file." I then went to the original command prompt and punched in "adb.exe devices" and had no results. I went to my Device Manager and discovered that I had "Error 10: Device Could Not Start". I uninstalled and re installed the drivers, rebooted my phone into download mode, double checked that USB Debugging was active and that the phone was MTP data transfer. Manually reinstalled drivers and nothing seems to fix the issue.....I appreciate any help that is given
EDIT: I am trying to root 20F (Lollipop)
did you resolve the issue???
Not sure if this will work or not... But I've had some luck with the old LG drivers. Uninstall your current driver and give it a shot... http://www.multiupload.nl/XEY2YR3L0I Not sure if that link works. May have to find. Lg mobile driver 3.8.1. Will upload it myself if I ever get around to it..
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
Sony instructions are awful, I downloaded both the Studio and the SDK tools and things are just... "off" ( f.ex., android_winusb.inf doesn't even exist anywhere in either Studio or SDK tools to be replaced with ).
So I downloaded minimal ADB and fastboot, and I'm having trouble getting the device to be recognized while in fastboot - in device manager, "S1 boot" is unrecognized - I've tried using the drivers I've downloaded from Sony to no avail. Downloaded Xperia software and flashtool, installed drivers from flashtool ( XZ wasn't included in the ****ing thing, of ****ing course it wasn't... ), same thing.
"fastboot devices" simply isn't procuring an answer, and trying to jump ahead and do the unlock, it says that it's pending for devices to show up ( obviously ).
Some help?
Try this guide: https://forum.xda-developers.com/xperia-xz/how-to/how-to-unlock-bl-kernel-twrp-root-t3541648
btw. Sony use custom adb/fastboot driver (link in guide). If I remember correctly, this driver works, however you have to manually point it in device manager (ignore prompt about being incompatible).
You could also try drivers available in Flashtool - in Devices -> Check Driver menu.
http://imgur.com/a/DYGuG
can't get Android WinUSB driver to install. Any help?
edit
when connected while on, it displays this in flashtool : http://imgur.com/a/SqzuB
bump
Did you try to manually select driver for fastboot device? You have to choose from all drivers, not using automated search. Windows will complain it's incompatible, but it should work.
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).