Hi,
I would like to return to rom stock but my z2 pro is whitch in custom rom (twrp+mokee 6 releade and of course rooted), is not recognised on ADB.:
When i launch the command "adb devices", the list is empty.
My phone is in developpers mode and it recognize by windows 7.0.
I had no problem to install twrp and custom rom.
Could you help me?
Thanks
Maybe a late answer, but mostly the reason is wrong drivers or more reasonable just restart adb server by this command "adb kill-server"
Related
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.
I want to install officier rom my htc one. but adb sideload is not working well. I typed on cmd then cmd showed me some long strange english.
how to use adb sideload and get my officier rom. my device is 801s(pn07140)
please help me...
Add
The explanation show "serial number device" but mine "serial number host".How to change to device not host??
Hello,
My nexus 6 was rooted and with TWRP. However, while trying to update to 5.0.2 using this ROM (http://forum.xda-developers.com/nexus-6/development/rom-pure-shamu-beta-2-0-t2952604), I ended up with no OS on it. I can boot into TWRP just fine.
So I am trying to sideload the ROM and rest of the files, however, my Win 8.1 shows "device not found". The command "adb devices" show no devices as well.
Win 8.1 device manager shows the phone as "Google Nexus ADB Interface" with driver ClockworkMod 8/27/12 7.0.0.4.
Any ideas?
Reinstalling and selecting from list did the trick, the device is listed as "Android Composite ADB Interface".
However, I must be missing something too obvious that I just cannot see...
I go into TWRP
go into advanced
go into ADB sideload and enable it
on PC, "adb device" will list it "recovery"
on PC, "adb sideload filename.zip" give me "error: Protocol fault (no status)"
then found out I had to stop the process "adb", which I do now.
Now when sideloading the zip I get "error: closed"
Ok, who knows why it was not working, but ended up doing a push instead, then I just installed via TWRP the ROM, gapps and SU.
Command I used: adb push rom.zip /data/media/rom.zip
this thread sounds like what I do when my mom has a question about something. Leave her alone for awhile and she finds the answer her self.
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 wanna connect my samsung a3 2017 8.0 to pc via adb. because i wanna disable peeking notifications. "adb shell settings put global heads_up_notifications_enabled 0"
but when typing "adb devices" in cmd, there is no phone to be seen. ive tried with platform-tools_r28.0.0-windows and adb-setup-1.3.
i have enabled usb debugging in phone settings and its not rooted. ive never done these things before.
i can see my phone in pc to transfer pics and movies but adb is not working. help me please.
edit: its working now. i just installed SAMSUNG_USB_Driver_for_Mobile_Phones