Hello. I want to root my phone but I have some problems.
First I install ADB on Windows 10 and pair with phone (get the prompt to allow connections to that device). After that I run command "abd devices" and I see my device in list.
Second I run command "fastboot flashing unlock" and it says "waiting for device" and nothing happens (in "developer options" "usb debugging", "usb debugging(Security settings)", "OEM unlocking" are turned on and I also run "adb reboot bootloader" command)
I found some information that problem can be in drivers but there is new problem came out
When I want to update driver it says "Windows found driver software for your device but encountered an error while attempting to install it".
I tried disable driver signing enforcement and it doesn't help. I use this drivers: Google USB Driver and https://web.vip.miui.com/page/info/mio/mio/detail?postId=18464849&app_version=dev.20051.
Google's ADB & Fastboot drivers are meanrt to be used with Goggle devices.
Download and install the suitable Redmi Note Android USB drivers:
https://c.mi.com/thread-3960523-1-0.html
xXx yYy said:
Google's ADB & Fastboot drivers are meanrt to be used with Goggle devices.
Download and install the suitable Redmi Note Android USB drivers:
https://c.mi.com/thread-3960523-1-0.html
Click to expand...
Click to collapse
This pages redirect to Google USB Driver and I tried to install it and it didn't work. Its the same problem
Related
I have installed adb drivers. But when I enter the command "adb devices", my phone doesn't get detected. I have Xperia ZL and adb detects it and not my OnePlus One. Yes, I have enabled Android Debugging in developer options. Tried updating driver software too. It says "windows couldn't find driver software for your device". I use windows 7.
EDIT: Solved. Installed drivers from here
anagramgenius said:
I have installed adb drivers. But when I enter the command "adb devices", my phone doesn't get detected. I have Xperia ZL and adb detects it and not my OnePlus One. Yes, I have enabled Android Debugging in developer options. Tried updating driver software too. It says "windows couldn't find driver software for your device". I use windows 7.
Click to expand...
Click to collapse
This problem is solved here is the link.
http://forum.xda-developers.com/showthread.php?t=2782721
If I helped you. Please click thanks
Sent from my YU Yureka using XDA Free mobile app
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..).
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.
The Windows Device Manager shows that the ADB interface is loaded and fastboot works fine, but ADB not so much.
"ADB devices" can't see the attached phone (Moto G9+), though fastboot sees it ok. Fastboot flashes & gets information all ok.
"ADB reboot" responds "error: device '(null)' not found"
What goes?
Thanks.
Remove the driver from Windows OS. Instead install the "Android USB Driver" provided by OEM what fits your phone.
jwoegerbauer said:
Remove the driver from Windows OS. Instead install the "Android USB Driver" provided by OEM what fits your phone.
Click to expand...
Click to collapse
I'm using the latest 64-bit device drivers supplied the phone's manufacturer (Motorola - G9+).
doktorspin said:
I'm using the latest 64-bit device drivers supplied the phone's manufacturer (Motorola - G9+).
Click to expand...
Click to collapse
Have you ever enabled "USB Debugging" in Android's Develeoper options?
jwoegerbauer said:
Have you ever enabled "USB Debugging" in Android's Develeoper options?
Click to expand...
Click to collapse
I've rooted the phone, so yes.
(It's just that It installed another recovery over my TWRP & when I reflashed TRWP & Magisk, I couldn't get root back. I'm now trying to figure things out, one of which is the ADB problem, but the problem is also seen on my earlier phone of the same make -- Motorola G.)
I have LE2110. In Settings I've enabled "OEM Unlocking" and also "USB Debugging".
I also instsalled the proper USB drivers but think they are unecessary regardless.
I boot into Fastboot & connect to laptop withofficial USB cable.
From the folder where I installed Android SDK Platform Tools I open command prompt.
Type in fastboot oem unlock and it says 'waiting for devices'.
I've rebooted everything, tried a few times over several days but always same result.
Phone works perfect, no issues otherwise.
Any tips what to try next or possibly what I'm doing wrong?
Thank you
I have a global unlocked 9. I had to use this to unlock bl. Open your command window from this after it installs,make sure to add shortcut to desktop when installing. Then run unlock command. Worked for me back in April when I bought device.
"minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities" https://androidfilehost.com?fid=746010030569952951
For me, I installed every driver while being in testsigning on ("bcdedit /set testsigning on" in cmd as administrator then reboot) and then I rebooted, turned testsigning off, rebooted again then it worked.
100 percent driver issue. Just reinstall the correct drivers and you'll be good to go.
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
dotuletz said:
Can you try to install this app on your computer and then try? pdanet this installs also the drivers for your phone. Otherwise try searching on the forum for the correct drivers.
Before any command you should try and see if your device is connected by doing in command prompt: fastboot devices
Click to expand...
Click to collapse
Plus you can reboot edl through adb.