Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
edit:
The driver that was install for my device is from microsoft. (see pictures below)
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
GalosSide said:
Two days ago I tried to use Easy Root ToolV11 to root my device that's running 14.1.1.A.0.402 Model D6503, it said "waiting for device".
I looked something up a bit and tried to install ADB driver, but nothing shown up in my detected ANDROID device list even though it was already plugged in to my PC.
I also tried to set up ADB PATH by following a tutorial in this thread http://forum.xda-developers.com/showthread.php?t=2559009 but it didn't work.
In my device manager my device is under "portable devices" instead "android devices"
I also tried towelroot on my phone. It said that my phone is rooted, but root checker said "This device does not have proper root access"
Ps. usb debugging mode and unknown sources are enabled
Click to expand...
Click to collapse
Are you using Windows 8?
cpumaster said:
Are you using Windows 8?
Click to expand...
Click to collapse
im using windows 7 sp1
also I just realize that i cannot use Sony PC Companion to do anything with my device it said that internet connection is required, but I am already connected.
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
hush66 said:
Not sure but perhaps the drivers were not correctly installed. Try this?
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
I'm still getting the same problem with the driver install.
I think i know what the problem is right now. The driver that was install for my device is from microsoft. (see pictures below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I uninstalled the driver and it was reinstall again every time i plugged my device in. I tried to update the driver, but it said that my driver is already up to date.
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
hush66 said:
Well, I just plugged in my Z2 to my PC and checked the driver details and it's exactly the same as yours. So it might not be an issue with the driver after all.
You mentioned that you have already done the ADB setup but it didn't work. When you said "it didn't work", do you mean the ADB couldn't be setup, or did you mean you still got the "waiting for device" message? To check if your ADB has been setup properly, go into the command prompt and type adb devices. You should see a serial number (of your phone) as the response.
And you should also have had the fastboot drivers installed. Use this tool to install fastboot drivers: http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
GalosSide said:
Finally it work!!!!
I'm rooting right now and it's stuck at cleaning up......what do i do now
Click to expand...
Click to collapse
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Frantiic87a said:
restart the install.bat file.. happens from time to time that it get stuck on cleaning up.
Check the official thread about Easy Root and you'll see loads of people had the same problem.
Just re-run the program and it will work.
Click to expand...
Click to collapse
I did and it said "insmod: init_module '/data/local/tmp/wp_mod.ko' failed (File exists)"
edit:
I restart my phone and root again. It's finally rooted.
Thank you every one for helping me.
Thank you!
sorry we facing the same problem so please tell me if found a solution
ADB FASTBOOT Drivers
Nothing worked for me accept this one.
I went there downloaded this driver installed it and it did its magic.
https://www.driveridentifier.com/sc...14379&scanid=92D42FEE7DDD4826835F8C3C3611A400
Related
I've tried everything. IT WILL NOT recognize my phone.
When trying to install the drivers it says the Authenticode does not have permission. I got the damn drivers directly from Android.com but it still doesn't think its authentic. Because of this, o cannot get the computer to recognize it as an adb device to root the phone.
I'm going nuts now. 2 days with literally 8 to 10 hours of trying with no success.
Can someone please please PLEASE help me?
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
rk0 said:
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
Click to expand...
Click to collapse
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
uoY_redruM said:
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
Click to expand...
Click to collapse
http://www.junefabrics.com/android/driver.php
Tried USBDeview, doesn't seem to let me uninstall anything even though it says you can.
Nothing appears to work.
This is what I keep getting, no matter what I do:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and what makes no sense is when trying to manually install new hardware, it SHOWS there are authenticodes for those drivers:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
I had the same issue, turned out it was a hardware bug.
I sent it to the repair center at HTC in United Kingdom and i had it returned 5-6 days after, working and with locked bootloader
britoso said:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
Click to expand...
Click to collapse
Vista.
I've tried a few of those suggestions and non of worked. Most involved the bcedit trick but its disabled or doesn't exist in the newer security updates.
Vista 32 bits or Vista 64bits ?
in hardware management console what do you see ? yellow question mark ?
Sometimes you need to go in it and find your device to check the HID number and copy it manually in the driver *..inf files to be detect by your OS.
I remembered doing this for my G1 long time ago (years).
If you can, get your hands on another n1 or android device to see if its a hardware problem with the phone, which i doubt. Also try a diff OS.
uoY_redruM said:
I've tried everything. IT WILL NOT recognize my phone.
Click to expand...
Click to collapse
This is for windows 7 64bits : http://tinyurl.com/2548qh4
take a look @ post #4
Hope you solve your problem !
In case you have Windows 7 you can try the following.
http://www.killertechtips.com/2009/...gning-in-windows-7-using-group-policy-editor/
Are you installing the usb drivers using the utility in ADB? If not, delete the drivers in hardware manager, and try installing them with the utility.
I had no problems doing this on Vista, but I prefer to use ADB on Linux.
Sent from my Nexus One using XDA App
hey .
maybe i´ve got something for you.
download my file here
install the binaries and then reboot (i said you don't have to, but i think in your case it would be better)
EDIT: is the debug function enabled in your device?
OK, after a few hours and still no success with Vista, I went to storage and pulled out my personal PC I built that hasn't run in a few years thanks to corrupt hard drives.
I spent 4 hours repairing and fixing the hard drives and SUCCESS, I got it to detect it on my Windows XP PC.
NOW! Still not working! In the command prompt, it shows adb devices as one connected but still when I do an adb push nothing happens. Just recycles the adb menu....
Any suggestions?
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Try using a Linux distribution. Saves a lot of time and headache.
or just reinstall your windows. win7 would be better than vista.
malevolent000 said:
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The PC I'm using now IS working. It recognizes adb device but wont push the flash images or anything.
It connects fine with HTC sync, but I can't find my phone in "my computer". What am I doing wrong? I'm running Vista 32bit, btw.
now sync can't even find my phone. I tried all the usb ports on my tower, it's a fresh install of Vista that is up to date, tried reinstalling the sync program, installed some mtp drivers I found on the Microsoft site. USB debugging on and off, nothing works! and it's the stock Rom, just with some mods. ATT phone btw. any suggestions? mtp stinks btw...... I wanna flash some roms darn it!
May I suggest something to you? Uninstall all your current drivers and also remove HTC Sync, then try to follow this step-to-step guide : HERE or a more complete one HERE. If you need help or precision I will be glad to assist you.
Well i fallowed your walk through and still no luck. Im sure its not the chord i tried 3 different ones, including the the one that came wit the phone. :crying: Im completely at a loss....
NoobDude said:
Well i fallowed your walk through and still no luck. Im sure its not the chord i tried 3 different ones, including the the one that came wit the phone. :crying: Im completely at a loss....
Click to expand...
Click to collapse
you might have to connect directly from usb like the ports in the back of the pc rather then the ones in the front. also try using a different computer and see if it works or not.
well I just about given up. the issue isn't solely with my computer, as it connects just fine with every other usb device in my house, iphone, gs3, digital camera, etc. so up its an issue primarily with my phone or both my pc and phone. I haven't had a chance to try my phone on another computer yet, can't get mtp working on ubuntu. or maybe it does work, and my phones just messed up. maybe something I did, I need to stop messing with system files :laugh:. BUT I had an epiphany, ADB over WiFi, I found a bunch of apps, they all mention running apps and debugging, but can they be used as a replacement for adb via usb? can I use adb Wi-Fi to push a kernel and or recovery?
Well I made some headway! I FINALLY got my computer to at least recognize my phone. I did this control panel>add hardware and manually installing the drivers that way. SO now in device manager Android phone (sdk drivers) and HTC MTP device, finally show up. I get a code 10 on both those deives, BUT when I scan for hardware the drivers from the phone begin to install, how ever they fail to install. MY brain is beat from this, can some help give me the next little push to finally ending this debacle!?
May I ask if you have administrator privileges on your computer? On Vista this a prerogative, you MUST be an administrator otherwise the installation will fail.
Click on Start -> Control Panel -> Control Panel window opens click on the Uninstall a program (If you are using the Classic View of the Control Panel, then you would double-click on the Programs and Features icon instead.) -> The screen contains a list of the programs installed on your computer, locate everything starting with HTC and uninstall all of them.
Make sure your phone is not plugged in. Reboot your computer.
Download this file containing the Vista 32bit drivers. Put this file on your Desktop.
Plug your phone. Use Device Manager to install the driver.
Click Start, right-click Computer, and then click Properties.
In the Tasks pane, click Device Manager.
If you are prompted for an administrator password or confirmation, type your password or click Continue.
In Device Manager, locate the Android USB or MTP Device for which we want to install the driver.
Right-click the device, and then click Update Driver Software.
Click Browse my computer for driver software, click Let me pick from a list of device drivers on my computer, and then click Have Disk.
In the Install From Disk dialog box, click Browse, locate in the file you just downloaded an androidusb.inf and then click Open.
Follow the steps in the Update Driver Software Device Name dialog box to update the driver.
Reboot your computer.
Lets see the results.
NoobDude i may be beating a dead horse here but Ubuntu 13.04(even in the beta which i use as a daily os) has mtp out of the box maybe try that and install sdk, java , adb fastboot.
if lucky thirteens suggestion doesn't work, I'll try that next. cheers gents!
Lucky thirteens post didn't work at all, when i tried to update the drives I would get an error. Either that the driver wasn't compatible or the the current driver was up to date. I haven't tried updating to Ubuntu 13.4 yet. BUT, I kinda made some headway again. After several reboots and trying different things I get this, what you see in the first picture. SUCCESS!, Oh wai....(refer to second picture)..... When i plug my phone in via a USB (on the back of the computer), i get NOTHING. Sooo. One X+ FOR SALE! :laugh: :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you try one those drivers?
HTC USB Driver_x32_1.0.5375
Universal Naked Driver 0.72.zip
Intel® Android* USB Driver
Media Transfer Protocol Porting Kit
Also make sure your computer BIOS is up to date, try an online scan for your computer Dell PC Diagnostic
I'll give em a try fist chance I get!
NoobDude said:
I'll give em a try fist chance I get!
Click to expand...
Click to collapse
There is a universal driver from Koushik Dutta (dev of CWM). This worked on my Win8 x64 PC (nothing else would).
At least it shows my device when I type adb devices.
See if that works.
Google for it. I am not sure if I am allowed to attach the file here - hence not attaching. I also have forgotton / not saved the link. It was in his google+ post...
See if that helps
Okk the link was first when I googled .
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I have a ZEKI 10" TBQC1063B tablet. It apparently an updated version in that it now comes with Google Play Store app installed from the factory. It has Android 4.1.1.
I started to try to Root the device, but was unsuccessful.
In my quest to debug Rooting, I started trying playing with ADB directly. I quickly discovered I could not get to 'first base' with ADB.
Yes, I have USB DEBUGGING enabled, and when my tablet is plugged into my PC, the tablet shows that icon of the Android face in the status line in the lower right screen.
I started to try different drivers (reading that such might be the cause of ADB not working), even though all of the appear to be working OK when I check in Device Manager. One of the attempts I made at drivers led me to those offered as part of PDAnet. While using PDAnet's drivers didn't seem to help, I did stumble upon a CLUE. The CLUE is that while installing the PDAnet drivers, PDAnet did successfully install its own app onto my tablet. I think that such requires ADB to work, no? Could someone confirm such (or not)?
I tried a PC program called AdbDriverInstaller. When I first tried it, it reported a Device Status error of "Driver Incorrectly". So, I uninstalled that driver (I belive at that point it was the PDAnet one), and installed a new driver from a collection called UniversalAdbDriverSetup6. Now, that looked better. AdbDriverInstaller now shows:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looking better?
My problem is that ADB DEVICES still shows no devices:
Does anyone know of anything else to try? This is about the limit of my expertise.
Try!
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Kunal.Kene.1797 said:
You can try using different port...i suggest you clean up all the Drivers and then install them correctly!:silly:
Click to expand...
Click to collapse
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
WaltA said:
Thanks, but I am not sure what you mean,
After trying each driver, I uninstalled and delete it. Is there something else I should be doing to "clean up" ?
How do you install them correctly, other than simply installed them? Device Manager seems to think the ADB device is working correctly.,
Click to expand...
Click to collapse
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Also, this is a good tool..makes adb system wide as well HERE
Also, not sure when Android implemented this, you might see a box up asking for you to grant the PC permission to use ADB, grant it
WaltA said:
Click to expand...
Click to collapse
lacoursiere18 said:
Unplug your tablet then reconnect it.
Type in cmd prompt:
Code:
adb kill-server (Hit ENTER)
adb start-server (Hit ENTER)
You should see your device..
Click to expand...
Click to collapse
I unplugged and plugged my tablet in a few times (over a course of several days while I tried to debug this on my own). Both my PC and my tablet have been powered on/off and rebooted over that time too.
I believe I showed I ready tried those commands, with no success.
TBQC1063B Zeki tablet
Zeki TBQC1063B
Any roms available? This one seems to be stuck. I can get to the boot list, but haven't found a new rom for it. Or even the factory rom.
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.
So I just got my phone today and I was trying to root it (with magisk boot patch) but after using the unlock app and enabling USB debugging fastboot still wasn't showing the device.
There was no option in the developer settings for OEM unlock..
I don't know if it is a bug or am I just missing something, is there anyone who can help me ?
Did you connect to wifi or mobile networks?, you need to be online
NisseGurra said:
Did you connect to wifi or mobile networks?, you need to be online
Click to expand...
Click to collapse
Yes of course otherwise the app won't unlock
*Is it ok for there to be no OEM unlcok option in the developers settings ?
danielbr14 said:
Yes of course otherwise the app won't unlock
Click to expand...
Click to collapse
Unlocked, rebooted, full wiped and add network again?
NisseGurra said:
Unlocked, rebooted, full wiped and add network again?
Click to expand...
Click to collapse
Yes, when I boot it clearly states that the bootloader is unlocked yet I don't have the OEM unlock option in the developers settings..
But if the bootloader are unlocked why you need the oem toggle?, Did you try to flash magic?
NisseGurra said:
But if the bootloader are unlocked why you need the oem toggle?, Did you try to flash magic?
Click to expand...
Click to collapse
Because the device still doesn't show up on fastboot (it does on ADB)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Did you try "fastboot devices"?
windows driver correct?
NisseGurra said:
Did you try "fastboot devices"?
windows driver correct?
Click to expand...
Click to collapse
No I tried to install everything that this guide says to, but the phone still shows up with an incorrect driver
Try the google drivers
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
NisseGurra said:
Try the google drivers
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Click to expand...
Click to collapse
I tried it but When I point it to the driver it says it can't find a driver for my device
danielbr14 said:
I tried it but When I point it to the driver it says it can't find a driver for my device View attachment 5681607
Click to expand...
Click to collapse
And if you try to install it from device manager?
NisseGurra said:
And if you try to install it from device manager?
Click to expand...
Click to collapse
That's what I did, is there a way to install it without the device manager?
danielbr14 said:
That's what I did, is there a way to install it without the device manager?
Click to expand...
Click to collapse
I would delete all installed drivers for Zenfone 9, reboot, change usb-port and install googles drivers.
But as this more an windows issue its difficult to assist remote
NisseGurra said:
I would delete all installed drivers for Zenfone 9, reboot, change usb-port and install googles drivers.
But as this more an windows issue its difficult to assist remote
Click to expand...
Click to collapse
I already tried it, and to be honest I don't think it is something that I am doing. adb detects the phone is both when it isbooted and when it is in the bootloader. Its only during fastboot that windows shows a missing driver the device...
The OEM Unlock toggle is usually unavailable (grayed out) when the bootloader is unlocked. It's possible this is the reason why it doesn't show up.
As for being unable to issue fastboot commands, it sounds to me like a driver issue, like others have stated.
OK, Finally managed to track down the correct driver thanks to this post and download this driver
FYI for anyone who encounters the same issue just open device manager and right click on your unrecgonized device (needs to be already in fastboot mode) the click update and select the driver from the zip file you just downloaded according to your PC then just finish installing it and everything should work.
danielbr14 said:
View attachment 5681497
No I tried to install everything that this guide says to, but the phone still shows up with an incorrect driver
Click to expand...
Click to collapse
Check windows update then optional update. There will be an Asus ADB driver to install.
danielbr14 said:
OK, Finally managed to track down the correct driver thanks to this post and download this driver
FYI for anyone who encounters the same issue just open device manager and right click on your unrecgonized device (needs to be already in fastboot mode) the click update and select the driver from the zip file you just downloaded according to your PC then just finish installing it and everything should work.
Click to expand...
Click to collapse
Just the answer I was looking for. Thank you for sharing!
Quite counter-intuitive that the trcick is to install Win8 drivers for Win10, but presumably they are the same but should have been downloaded automatically in Win10.
mickey36736 said:
Check windows update then optional update. There will be an Asus ADB driver to install.
Click to expand...
Click to collapse
Hopefully this is an option for most people, but, for the record, this did not work for me.
Windows 10 had a bunch of suggestions there but none of them were from Asus.
Perhaps it's glitched and they are in an invisible overflow - my optional driver section has exactly 10 entries. no more and no less, which I find a little suspicious.