Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.
KodRoute said:
Hello. As the title says I get that error. I need to run adb shell to use some commands. When I type "adb devices" I don't get any device listed (the long name).
My OS is Windows 8.1 64bit.
Thanks.
Click to expand...
Click to collapse
Whats your device?
LS.xD said:
Whats your device?
Click to expand...
Click to collapse
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.
KodRoute said:
Nexus 5. In SDK Manager it says that Google USB Drivers are installed. I don't get it. When I use the phone to flash images in fastboot it works perfectly but ADB doesn't work.
Click to expand...
Click to collapse
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders
LS.xD said:
Try to disable/enable USB debugging again and check if the adb device is listed in your device manager.
You can also try this ADB/fastboot bundle (Includes the google drivers) and work on all folders
Click to expand...
Click to collapse
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
May you press "thanks" for my posts if i helped you ?!
KodRoute said:
Yeah after a while I wanted to check if usb debugging was checked and it wasn't. Turns out now works.
Click to expand...
Click to collapse
Doh! I hate when that happens. It's always the little things.
Related
ATTENTION: PUBLIC SERVICE ANNOUNCEMENT
It has come to my attention that under certain circumstances when the Kindle HD's get stuck in a bootloader bootloop the information on the "boot0" block of the internal storage can be ERASED and RESET.
This partition is special and contains ALL of your device's hardware specific information:
- Wifi MAC address + Encoded Secret for registering w/ Amazon services
- BT MAC address
- Serial #
etc
FOR BACKING UP THIS PARTITION:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb pull /sdcard/boot0block.img
Place the "boot0block.img" file with the other files that you backed up in the original instructions for safe keeping.
FOR RESTORING THIS PARTITION:
(do not do this unless you are absolutely SURE that your boot0 block got wiped out -- hopefully you never need to)
This is done via adb from your PC while the device is in TWRP recovery or in the Android OS (not fastboot):
Code:
cd <your safekeeping files>
adb push boot0block /sdcard/boot0block.img
adb shell "echo 0 > /sys/block/mmcblk0boot0/force_ro; dd if=/sdcard/boot0block.img of=/dev/block/mmcblk0boot0;"
THIS FILE IS UNIQUE TO YOUR DEVICE AND CANNOT BE REPLACED OR REBUILT FROM ANOTHER DEVICE. DO NOT SHARE IT WITH ANYONE AS IT CONTAINS INFORMATION ABOUT YOUR DEVICE USED BY AMAZON DURING REGISTRATION.
very interesting Hashcode,thanks for the information :good:
Odd, I can't seem to find the file after I pulled it with ADB.
EDIT: I didn't even assign the command an output location to begin with. LOL.
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
esox_hu said:
Thanks for the info.
How can I access KFHD via ADB if CM10.1 installed.
I can't see my device in device manager only as a media storage or sth like that.
Should I remove KFHD adb driver and install the google driver?
Or just using the hidden trick in cm10.1?
"Enable Developer options in your phone (Settings > About phone and tap Build Number until you are a developer (about 7 times)
Set root access for APPS and ADB in: Settings > Developer Options > Root Access
Enable Android debugging at the same page (Developer Options). Enable ADB over network if you need.
Check if your Settings > Security > Unknown Sources is checked. you will need it to install over ADB."
Yeah...it helped
Click to expand...
Click to collapse
Just turn on ADB debugging on the tablet, and plug it into the computer. On the computer, open command prompt, use the command "adb devices" to see if your ADB is working.
Other than that, I don't know what happened in your post.
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
AmrBanawan said:
Ok i really can't figure this one out, I used adb many times while testing KFFAide tool so I am 100% sure my adb drivers are installed correctly, But since i switched to cm10.1 (Thanks hashcode) ADB cannot recognize my device anymore, I have enabled ADB on my KFHD and when i connect it to my pc a small notification appears "Android debugging enabled" but when i use "adb devices" command nothing shows up!
Can anyone help me with this i'm completely lost here!
Click to expand...
Click to collapse
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
seokhun said:
Leave the device plugged in, go to Developer Setting and uncheck ADB debugging, then check it again. You should see a prompt, select OK for both.
Click to expand...
Click to collapse
Ok thanks i tried but to no avail
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Yeah I actually have the same problem too now
Thanks for the heads up hash, got it on a usb stick now
---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
I had to manually check android debugging and usb debugging notify and it worked just fine.... make sure adb over network is not checked
Protomartyr said:
Yeah I actually have the same problem too now
Click to expand...
Click to collapse
AmrBanawan said:
Ok thanks i tried but to no avail
Click to expand...
Click to collapse
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
seokhun said:
Why don't you guys try this, go into CMD while connected with the device (ADB debugging on), and type "adb devices" to start the daemon, then try the commands. Other than that, I don't know what else to do.
Click to expand...
Click to collapse
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Protomartyr said:
Nope. Just get "List of Devices Attached" but no serial number. Checked device manager and it's showing up as a portable device. Probably will reinstall them and see if that solves it.
On a side note:
if we ran these commands in terminal emulator on the device, would that be sufficient?
Click to expand...
Click to collapse
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
AmrBanawan said:
Yes
run the first command then pull it manually
But we need to know what's going on, i will need adb sometime soon when prokennexusa releases the next version of KFFAide
Click to expand...
Click to collapse
you can always open up your device manager and manually apply the adb drivers to your kindle
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
had same probs on cm10 getting the files no matter what i tried.in windows 7 and xp it wouldnt install normal driver so i could see kindle as a drive so flashed an amazon zip and pc recognizes it without any problems and now have the files needed
dugoy13 said:
How do we know the boot0 partition is erased?
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Normally you would notice WiFi doesn't work under any circumstances same for BT. And when on Amazon's software it won't let you register.
Sent from my Amazon Kindle Fire HD using Tapatalk 2
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
PaulJCW said:
I can't get ADB to find it either, think i'll revert back to stock to get the file then go back to CM - I notice though on CM turning USB Debugging on doesn't change anything in device manager, it still stays connected as a media device or camera, depending on which you have ticked in storage setting *shrugs*
Thank you Hashcode
Click to expand...
Click to collapse
No don't, just type the command hashcode provided in terminal emulator and you'll find the backup in your sdcard, just copy it to your pc like normal!
You can do it from the terminal without typing ADB. that may be why people are confused. Start with hashcodes command but start with "su -c" in the terminal.
Sent from my Nexus S 4G using xda app-developers app
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
simms22 said:
thats because you cant use adb in recovery at all. you can use adb when in the bootloader.
Click to expand...
Click to collapse
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
I'm using TWRP. My problems with drivers keeps increasing it seems :\
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
you can go to device manager and update the driver, choose Browse my computer, Let me pick from a list of device drivers, and choose one that says adb.
rootSU said:
Sorry, think you got mixed up there.
You can only use fastboot in the bootloader. You can only use adb in recovery or android... Although not sure if adb can be used in stock recovery.
Click to expand...
Click to collapse
GUGUITOMTG4 said:
Revise it, I can use adb push/ pull etc...
you explained that to someone long ago
Click to expand...
Click to collapse
right.
was concentrating on work. i messed up
simms22 said:
right.
was concentrating on work. i messed up
Click to expand...
Click to collapse
We all do it
Lxve said:
Hey!
I followed the steps in this thread: http://forum.xda-developers.com/showthread.php?t=2514396
My problem is that I can't use adb in recovery. In device manager, it shows "AOSP on hammerhead". I saw someone that had a solution for this
problem in that thread but it wasn't clear enaugh for me (using windows 7). Can anybody help me out?
Thanks!
Click to expand...
Click to collapse
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
To make adb works in recovery you need the naked usb drivers
Tapatalk-kal küldve az én Nexus 5-el
You don't need the naked USB drivers at all.
I use the Google USB drivers and they work fine in recovery.
The problem he is having is that windows has automatically installed a different driver than what is needed for adb to work.
Manually updating the driver to the Google adb driver as shown in my previous post will get the op running without having to download anything extra
Sent from my Nexus 5 using xda app-developers app
Alex240188 said:
OK as you said you have followed the steps in the linked post. I will assume you have already downloaded and extracted the latest_usb_driver_windows.zip.
I Use windows 8 but the procedure should be the same for Vista / 7 / 8
Here is what to do.
1. Put your phone in recovery.
2. Plug into PC
3. Go To Device Manager
4. Right click "AOSP on hammerhead".
5. Choose "Update Driver Software..."
6. Click "Browse my computer for driver software"
7. Click "Let me pick from a list of device drivers on my computer"
8. Click "Have Disk..."
9. Click "Browse..."
10. Navigate to the extracted Driver you downloaded. (in my case V:\Downloads\latest_usb_driver_windows\usb_driver\)
11. Double click on android_winusb.inf
12. Click "OK"
13. Click "Android Composite ADB Interface" and press Next. (If it is not in the list, untick the "Show compatible hardware button at the top)
Your driver will now install and you should be able to use ADB normally in recovery
Click to expand...
Click to collapse
Can you check if you can use adb remount when the phone is fully booted? I'm using naked drivers and everything works except this command. Adb root doesn't work also.
This has nothing to do with the drivers. The kernel you use has to be built with the ro.secure=0 flag for remount to work
Sent from my Nexus 5 using xda app-developers app
Hello, Today i have installed Cyanogenmod 11. But after rebooting i connected my mobile to PC and in command prompt
i gave a command " adb devices" and the list is empty. :crying: This happened after flashing CM11. HELP !!!!!
I can access internal memory as a media device.
Did you enable the ADB?
cyrus_ae said:
Did you enable the ADB?
Click to expand...
Click to collapse
As above.
You'll need ADB active on the phone.
And a new / updated version of the ADB drivers / tools on your desktop.
Also, you will get a dialog prompt on the phone to confirm a security encrypted key (to allow ADB between your desktop and your phone)
This is something Google introduced on 4.1 (I think) which, if is not set, will end in a "devices not found" when trying to use ADB
dubidu said:
As above.
You'll need ADB active on the phone.
And a new / updated version of the ADB drivers / tools on your desktop.
Also, you will get a dialog prompt on the phone to confirm a security encrypted key (to allow ADB between your desktop and your phone)
This is something Google introduced on 4.1 (I think) which, if is not set, will end in a "devices not found" when trying to use ADB
Click to expand...
Click to collapse
Thanks for replay
Actually it worked till I flash CM11 using CWM Recovery. Problem came after flashing .
srujan21 said:
Thanks for replay
Actually it worked till I flash CM11 using CWM Recovery. Problem came after flashing .
Click to expand...
Click to collapse
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
deej_roamer said:
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
Click to expand...
Click to collapse
Its working, Thanks
ADB Device not found
deej_roamer said:
Revoke all USB authorisation.
Try reconnecting.
And authorize when prompted!
If it doesnt work!
Also Please post Does your device show up in device manager? IF yes by what name? Is there an ADB Interface?
Click to expand...
Click to collapse
i had same problem, plz help me
vardhanram said:
i had same problem, plz help me
Click to expand...
Click to collapse
The thing you are quoting is solution my friend. It also has a question if solution doesn't work. Please answer that
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
dxlevel81 said:
Hi Guys, I just want to ask if there will be a possible solution on how I will be able to use my phone again. I accidentally deleted the OS and the backup of my OS. When I tried to connect my phone to a pc, the pc wont read my phone. Any possible solution on how will I connect it or any solutions for my problem. I also dont have the custom rom zip on my sdcard anymore.
Click to expand...
Click to collapse
Can you boot into fastboot or recovery?
Mr.Ak said:
Can you boot into fastboot or recovery?
Click to expand...
Click to collapse
yes I can boot into TWRP, but can't connect to pc.
dxlevel81 said:
yes I can boot into TWRP, but can't connect to pc.
Click to expand...
Click to collapse
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Mr.Ak said:
Ahh..
Just boot into Twrp,connect your device to Pc and transfer any ROM and flash it.Gee,twrp supports mtp,which means you can transfer stuff.Alternatively,if mtp is not working for any reason,you can use usb otg as well.
Click to expand...
Click to collapse
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
dxlevel81 said:
The pc wont read my phone anymore, I installed adb drivers already. But I'll try to use an otg usb.
Click to expand...
Click to collapse
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Mr.Ak said:
I forgot to mention you can use adb sideload as well.
Since you've adb drivers installed,boot into twrp,go to advanced and enable adb sideload,connect to PC.Copy the ROM zip in your adb folder(where adb files are situated),press shift and simultaneously hit right button on your mouse,select open cmd here.Now write command "adb devices"(obviously without quotes), if all goes well,you'll see your device Id there,proceed and write command "adb sideload ROM name.zip" (where ROM name= exact name of file you're trying to flash).The flashing progress should start now.
Click to expand...
Click to collapse
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
dxlevel81 said:
Do you have links on working adb drivers? That is my problem now. My pc is unable to read my oneplus
Click to expand...
Click to collapse
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Mr.Ak said:
Device doesn't get detected even after enabling adb sideload in Twrp? What does it shows in Device Manager?
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
It does'nt show in the device manager.
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.)