Drivers are installed. Any ideas, please?
Used Multi Tool and worked flawlessly
I had the same issue. As far as I recall all was solved after I installed the USB drivers contained in the Phone itself. When you connect the phone via USB, besides showing up as an MTP device, it also appears as a CD Rom unit. There you have the driver installer.
open command tools and type this:
Code:
bcdedit /set testsigning on
I got 2 errors while this happend. Use the right serial and if nessecarry try command "ADB kill Server". After this try again. Don't forget -i 0x2b4c in the fastboot commands.
rybaryba33 said:
Drivers are installed. Any ideas, please?
Click to expand...
Click to collapse
uninstall zukusb driver and then again install it it will solve the problem if the problem still persists the use the all in one tool:angel:
octaedro7 said:
I had the same issue. As far as I recall all was solved after I installed the USB drivers contained in the Phone itself. When you connect the phone via USB, besides showing up as an MTP device, it also appears as a CD Rom unit. There you have the driver installer.
Click to expand...
Click to collapse
WOW, such a simple solution, but it worked in my case too! None of the other drivers worked... Thanks man!
Related
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
I've searched and searched for a solution to this, nothing is working. Really need help guys.
Phone is on stock ICS rom, PC is Win8 Pro x64. All three files are in the folder, SDK is installed (x64 version), Google USB driver installed, Java for windows installed, and HTC Sync installed but not running.
When in FASTBOOT and USB connected it shows FASTBOOT USB. Device manager shows Android Phone - Android ADB Interface. Is this correct or should it show something else in device manager?
No matter what I've tried when running fastboot oem get_identifier_token in command prompt I get waiting for device. Also running fastboot devices returns nothing.
Don't know what else to try... Seems it doesn't recognize the device but it's in device manager.
Edit: have also tried different usb ports and I know the cable works.
Edite 2: I fixed it. Took me hours to get this working but for any one struggling like I was here is what I did.
Got rid of all the drivers and started back at Android 1.0 in device manager. Manually installed the official SDK google usb driver and selected Android Bootloader Interface for Android 1.0. Also boot the phone and manually install again and select Android ADB Interface.
Here is what really caused me problems. The HTC tutorial I looked at said to take adb.exe, fastboot.exe, and adbWinApi.dll and put them in their own folder. This absolutely does not work for me even now. I used the directory straight from the SDK (sdk\platform-tools) and added fastboot.exe from a previous sdk revision into that folder. Now everything works!!! Finally!
Hi everyone!! I have the same issue as brother bassvoykevlar but the solution here expresed is not all clear to me. Can anyone please give me a hand on this, i am really mad with it . Thanks in advance.
The Best Solution
this problem has also happened with me and i found a solution to this,
this usually happens if your system lacks fastboot drivers.
ADB drivers can only Run ADB shell so that is why you need to have fastboot drivers as well to use fastboot commands.
i think you must have tried this code:
"fastboot oem unlock"
then cmd may have got stuck on "waiting for device"
don't worry install drivers for fastboot then it should work.
google it then get it.
there is 15seconds ADB,fasdtboot installer available try that.
then give it another try.
Sooooooooooo,
I have a Z1 [C6903] that I picked up yesterday. It came with 14.2.A.1.136 Jellybean 4.3.
I wanted to
Unlock bootloader
Install custom recovery
Root
Install any nice AOSP ROM [preferably LP-based]
I installed the Minimal ADB-Fastboot 1.4.
I also installed the Flashtool 0.9.18.2.
I also installed the Z1 device, Fastboot, and Flashmode drivers [version 1.6.2] from the driver folder. It first failed, and then I disabled driver verification then everything went smooth!
Device manager recognized the phone in MTP and Fastboot, and Flashmode modes. Drivers installed correctly I presume.
Then the challenges arrive:
adb devices returned it as "offline"
Android studio couldn't push a project to it because it was offline
fastboot devices identified it, but fastboot -i 0x0fce getvar version returned an error [getvar:version FAILED (command write failed (Unknown error))]
Things I've tried to do to rectify the connectivity issue:
I'm using a SurfacePro 4 so I can't switch USB ports [only have one].
I've tried different cables - they yield the same result.
I've enabled and disabled USB debugging, revoked access, unplugged and replugged, rebooted, etc. Still no change in result.
Since the device had some OTA updates pending, I ran those and now i'm on 4.4.4 with 14.4.A.0.157, with some other updates currently waiting for me to accept so they can download. I've decided to post here for help and won't run those updates unless it increases my profit
PS: Even after the updates, adb and fastboot still are unchanged in their results.
Help please
Update:
It was a freaking USB cable. I had tried two of them. None had worked.
I finally unleashed my Anker USB cable and Boom! We good to go!!!
Thanks all!:highfive::highfive::highfive::highfive:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
tomascus said:
Make sure to enable USB debugging in Developer Options at the bottom of the Settings app
Click to expand...
Click to collapse
Did this and more. Still to no avail.
The phone shows up in the computer, it just doesn't show as online when I run the adb devices command.
That's what I need help with.
Thanks
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
tomascus said:
ahh have you tried using
Code:
adb kill-server
adb start-server
and trying again?
What should happen is the authorisation window pops up on your phone
Click to expand...
Click to collapse
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
boydee said:
Excellent! I did that, too. even manually closed and restarted adb.exe to no avail.
The thing is, my Z1 DOES NOT show me the authorization pop-up! Ever!
I've done this a million times on other phones, and I know the procedure. It's just that this Z1 is not showing the authorization popup
Thoughts?
Click to expand...
Click to collapse
Find a quiet corner and cry
Tried running adb as admin?
tomascus said:
Find a quiet corner and cry
Tried running adb as admin?
Click to expand...
Click to collapse
Tried this, too!
No change, anywhere.
I actually went ahead and tried adb on another PC with minimal adb-fastboot and adb drivers installed, and it returned the same "offline" response
Whoa!:angel:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
DectonX said:
@boydee
this could work with you
i assume that you rooted your phone you will do that:
1. open your favorite file explorer(suggest: ES File Manger)
2.go to /data/misc/adb/
3.delete "adb_keys" file
4.enable usb debugging
5.reinstall your drivers
6.open command and kill adb server(adb kill-server)
7.connect your device and run command (adb devices)
8.look at your device you will find text box telling you a new pc check always trust bla bla and click trust or something like that
9.you will see something like that
http://imgur.com/ReQtofb
Click to expand...
Click to collapse
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
k9rockstar said:
How to upgrade to kitkat 4.4.4 India version of c6903 Sony Xperia Z1 pls help
Click to expand...
Click to collapse
Hey there! Please check here for a firmware file that works for you.
When you've downloaded, use the Flashtool to flash it to your phone.
If you want help flashing it to your phone, check this thread out.
Hope that helps
boydee said:
Hey, thanks for the advice!!
Finally got root [without use of PC] and when I open the /data/misc/adb/, the folder is EMPTY
A little confused there.
I did the same procedure for the PC [deleting from C:/Users/boydee/.android/] but it also was to no avail.
Click to expand...
Click to collapse
This could problem with installing drivers as PC don't detect adb in debugging mode
So disable driver verification again and install drivers from flashtool remember to check
1. Fastboot drivers
2. Flashmode drivers
3. Xperia Z1 drivers
And restart
If the problem not fixed try adb universal drivers just Google it
I was have same problem with win 8.1 but I didn't all that I just installed win 7 and do it
Remember to backup ta before unlock to backup your DRM keys
I have a problem after updating to latest June Security patch for Nokia 8 TA-1004. I had installed driver long time ago when I wanted to obtain root and there I did it. However, after updating to latest patch which also causes to lose root, I couldn't get my phone to detect adb in cmd. I tried reinstalling driver but still not working. USB Debugging is also on. What could this be the problem? I need help. I want to obtain root back. Thank you very much in advance.
Is your adb up to date? I'm using the latest version of Minimal ADB and Fastboot with bundled driver from my TA-1052, works like a charm.
Get that fork of ADB and Fastboot and use it straight out of cmd :
https://developer.android.com/studio/releases/platform-tools
Rakaloah said:
Is your adb up to date? I'm using the latest version of Minimal ADB and Fastboot with bundled driver from my TA-1052, works like a charm.
Click to expand...
Click to collapse
I've got ADB drivers installed and the N8 is correctly detected as a fastboot device when in "Download mode", however I cannot flash anything, most likely because "adb devices" does not show any device (it is correctly shown when fully booted up). So I'm guessing it's a driver problem...and the problem is that I cannot install the bundled drivers, either on my Win10 (the setup.exe doesn't do anything) laptop or my old W7 laptop (error). Can anyone help ? Thanks !
webvan said:
I've got ADB drivers installed and the N8 is correctly detected as a fastboot device when in "Download mode", however I cannot flash anything, most likely because "adb devices" does not show any device (it is correctly shown when fully booted up). So I'm guessing it's a driver problem...and the problem is that I cannot install the bundled drivers, either on my Win10 (the setup.exe doesn't do anything) laptop or my old W7 laptop (error). Can anyone help ? Thanks !
Click to expand...
Click to collapse
Have a look at my post: https://forum.xda-developers.com/showpost.php?p=78074773&postcount=67
Thanks.
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard