I installed Ubuntu touch on my nexus 7 and want to enable ssh-server. I cannot get adb to see the device on both windows and ubuntu
Plz help
Using Ubuntu, open Terminal and enter the following:
sudo adb kill-server
Then enter:
sudo adb start-server
This worked for me and I could then flash my Nexus 4 with no issues.
I have tried that. And this is after I have already flashed the device.
Try booting into recovery and using ADB from there to set it up.
Sent from my Galaxy Nexus using Tapatalk 2
SchwassKIN said:
I installed Ubuntu touch on my nexus 7 and want to enable ssh-server. I cannot get adb to see the device on both windows and ubuntu
Plz help
Click to expand...
Click to collapse
try a different USB cable, some cable are power only, that was what happened to me.
I am having the same issue, however I can communicate over ADB in recovery, so my cable is fine, and the stop/start server doesn't work. I'm trying to get SSH set up but can't because I can't get into it with adb. On a previous build I was able to, did they remove ADB in the RTM?
Thanks,
ScrewedByExisten
@screwedbyexisten Have you enabled developer mode in Settings > About Phone > Developer Mode?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
nikwen said:
@screwedbyexisten Have you enabled developer mode in Settings > About Phone > Developer Mode?
Sent from my awesome Ubuntu Touch device using the Forum Browser app
Click to expand...
Click to collapse
Yes - Interestingly enough after rebooting the tablet it started working in Ubuntu, but still doesn't work inside of Windows. I just get "error: device not found".
ScrewedByExisten
Thnx buddy it worked for me..
Related
Name of topic is clear, does anyone have drivers for this working in ubuntu? tried to search htc sync for linuks, but not succeded.
(also I am pretty noobish in linux, my roommate is giving adviced whenever he can, but he has samsung smartphone and another linux using friends have nexus devices...)
myusernamewastoken said:
Name of topic is clear, does anyone have drivers for this working in ubuntu? tried to search htc sync for linuks, but not succeded.
(also I am pretty noobish in linux, my roommate is giving adviced whenever he can, but he has samsung smartphone and another linux using friends have nexus devices...)
Click to expand...
Click to collapse
You don't need HTC sync in Ubuntu. Download the Linux version of adb and fastboot and you're good to go.
Regards,
navmad
why fastboot devices inst working then?
myusernamewastoken said:
why fastboot devices inst working then?
Click to expand...
Click to collapse
Working fine for me.
Regards,
navmad
Install android-tools-adb and android-tools-fastboot via a package manager.
To use ADB and Fastboot, you have to start and run them as root, to have hardwareaccess.
To do so, just use:
Code:
sudo adb kill-server
sudo adb start-server
sudo adb [command]
also
Code:
sudo fastboot [command]
have a nice day
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Do you have usb debugging enabled?
Sent from my HTC One X+ using Tapatalk 4 Beta
Roodenburgertje said:
adb can't seem to find my device while fastboot does..
I installed the HTCDriver_4.0.1.001 for usb drivers
I can see my device in devicemanagement under Android usb devices > My HTC
this are the cmd results:
C:\Android\fastboot>fastboot devices
FA2AVW103684 fastboot
C:\Android\fastboot>adb devices
List of devices attached
C:\Android\fastboot>
can anyone help me out?
Click to expand...
Click to collapse
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
reaper90 said:
Are you trying to get adb acces to your phone when booted up or in recovery? As already said, in the first case you need to enable USB Debugging in developer options. If your phone is in recovery it may take some minutes for your computer to detect it after starting ADB server.
Click to expand...
Click to collapse
Yes im trying to adb acces from recovery without succes
is it win 8 or 8.1 ?
Win 8.
And i have a international hox+
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
wrong wrong wrong, shut up, NasaGeek
Roodenburgertje said:
Yes im trying to adb acces from recovery without succes
Click to expand...
Click to collapse
Works for me without problems on Windows 8. I don't know what driver version i have, i think i installed the driver with htc sync from my phone and uninstalled htc sync later.
Try the following:
1. Connect your phone to your computer and reboot in recovery.
2. Open command line and navigate to the folder where your adb/fastboot files are.
3. Type "adb start-server" and wait some minutes (as i said it may take some minutes to recognize the phone in recovery)
4. Type "adb devices" and now your device should be listed there as in recovery. If not, wait some more time and try again. Shouldn't take longer than 10 minutes. Otherwise there's probably something wrong with your driver and/or adb/fastboot files.
NasaGeek said:
You can only access adb sideload from your recovery. Every other function of adb is only accessible after your device boots into Android.
Click to expand...
Click to collapse
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
AndroHero said:
You should have full adb access in recovery .....
Sent from my HTC One X+ using Tapatalk 4 Beta
Click to expand...
Click to collapse
You are quite correct. I don't know what I was thinking. I'll edit my post.
The driver that comes with htc sync works just fine...
Alternate is Koush's universal ADB driver...
Hello all, been scouring the web with no avail, so I must come here for your help.
I used some of the guides on this forum in order to root, install CWR, and Cyanogenmod a few months back, but I'm back again today after an OTA update got me stuck in CWR/bootloader.
I can use both of these, and both of these only. I cannot boot into the ROM.
When looking, I've realized the only way to fix this would be to do a full reset and install the ROM again. I've wiped the device with CWR, but I'm not able to flash another ROM onto the device. (I'm looking to flash the GPE ROM this time).
My computer is detecting that something is connected, but even with the ADB drivers and everything, ADB still isn't detecting the device. Any pointers?
Also when looking around, I also noticed that many guides tell me I need to turn S-ON off, and I've tried doing that with rumrunner, but that didn't work since ADB wasn't either.
TLDR; I'm stuck in bootloader/recovery, am not able to flash/sideload due to my PC not detecting the device.
Anyway, THANKS LOADS IN ADVANCE. I've spent all afternoon searching today, and this is my last resort.
-GoldenTatertot
TWRP 2.6.3.3+ and adb sideload will be your friend. Try that and post back results
sent from my mobile device
SaHiLzZ said:
TWRP 2.6.3.3+ and adb sideload will be your friend. Try that and post back results
sent from my mobile device
Click to expand...
Click to collapse
I'm not able to sideload though. My PC isn't detecting the device.
GoldenTatertot said:
I'm not able to sideload though. My PC isn't detecting the device.
Click to expand...
Click to collapse
You need to install HTC sync to ensure the proper drivers are installed.
Download HTC sync manager
Install it,
Remove HTC sync manager but leave drivers
place HTC one on boot loader then fastboot option, connect device to computer wait until android 1.0 installs
Disconnect device and boot to recovery, reconnect device and let drivers install.
Run from computer CMD and get to the place where adb and fastboot exes are located.
Type command adb devices
the if successful prompt to do a adb sideload
Sent from my HTC One using xda app-developers app
TopoX84 said:
Download HTC sync manager
Install it,
Remove HTC sync manager but leave drivers
place HTC one on boot loader then fastboot option, connect device to computer wait until android 1.0 installs
Disconnect device and boot to recovery, reconnect device and let drivers install.
Run from computer CMD and get to the place where adb and fastboot exes are located.
Type command adb devices
the if successful prompt to do a adb sideload
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Alright, I installed and uninstalled HTC sync manager, only uninstalled from PC's native uninstallation process, and not sure if the drivers got uninstalled- didn't ask me about it.
After that, I recall a popup telling me it's installing Android 1.0, which only was active for a moment. I disconnected and booted to recovery, reconnected to computer, and 'adb devices' returned no devices.
Thanks again. Today was the first day at school without my phone this year, and it was dreadful. I'm a total addict.
Do you have a linux distro available which you can try? Preferably Ubuntu. Everytime Windows screwed up, I was able to do adb/fastboot perfectly with Linux.
Install:
sudo apt-get install android-tools-adb android-tools-fastboot
Define rules:
sudo gedit /etc/udev/rules.d/51.android.rules
Write this in that file: SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="Ubuntu"
Save and exit, then do sudo adb / fastboot devices.
svemprala said:
Do you have a linux distro available which you can try? Preferably Ubuntu. Everytime Windows screwed up, I was able to do adb/fastboot perfectly with Linux.
Install:
sudo apt-get install android-tools-adb android-tools-fastboot
Define rules:
sudo gedit /etc/udev/rules.d/51.android.rules
Write this in that file: SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="Ubuntu"
Save and exit, then do sudo adb / fastboot devices.
Click to expand...
Click to collapse
Do you think you could write or link me to a more detailed guide about that? Don't have much knowledge about that kind of stuff. Especially since I don't know what I need to look for.
Ahh, was finally able to get ADB to work on my computer. All good now.
GoldenTatertot said:
Ahh, was finally able to get ADB to work on my computer. All good now.
Click to expand...
Click to collapse
Do you mind telling us the steps? For other people looking for a solution?
Sent from my HTC One using xda app-developers app
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
/thread
Fixed my own issue by plugging the usb cable in the back of my computer. yup, seriously. Thanks to everyone trying to help. Also, thanks for not pointing out what a noob I am.
yepimjosh said:
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
Click to expand...
Click to collapse
I am not familiar with Linux but on Windows waiting for device comes up when the driver for that phone is installed. May be you can look into it for a solution.
Install the drivers and then give it a try.
yepimjosh said:
I'm trying to root my phone on linux, but once i do adb reboot bootloader, my device is nowhere to be found. anyone have a fix? I've searched everywhere.
Click to expand...
Click to collapse
You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
after you reboot to the bootloader you use fastboot commands ,not adb
clsA said:
You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
after you reboot to the bootloader you use fastboot commands ,not adb
Click to expand...
Click to collapse
I have adb. I'm trying to say, when I'm in recovery mode, my phone is no longer found on my computer. Not just adb, the whole computer
yepimjosh said:
I have adb. I'm trying to say, when I'm in recovery mode, my phone is no longer found on my computer. Not just adb, the whole computer
Click to expand...
Click to collapse
What recovery ? Stock recovery does not support adb
clsA said:
What recovery ? Stock recovery does not support adb
Click to expand...
Click to collapse
Sorry, I'm messing up what I'm trying to say. I have adb and fastboot installed, running on ubuntu 16.04. I plug my phone in, open Terminal, and run adb devies. My device pops up, it's there. So I run adb reboot bootloader, my phone goes on the white screen with the android fellow, and all is good. Now, I i try adb devices again, nothing. I put in lsusb (lists all usb devices connected to computer), and nothing. So, naturally, when i try fastboot oem unlock and my code, I'm stuck on <waiting for device>
yepimjosh said:
Sorry, I'm messing up what I'm trying to say. I have adb and fastboot installed, running on ubuntu 16.04. I plug my phone in, open Terminal, and run adb devies. My device pops up, it's there. So I run adb reboot bootloader, my phone goes on the white screen with the android fellow, and all is good. Now, I i try adb devices again, nothing. I put in lsusb (lists all usb devices connected to computer), and nothing. So, naturally, when i try fastboot oem unlock and my code, I'm stuck on <waiting for device>
Click to expand...
Click to collapse
adb does not work in the bootloader
After reboot bootloader it's fastboot devices
If you get no response try a different usb port
Or different usb cord
Sent from my SM-N920T using Tapatalk
clsA said:
If you get no response try a different usb port
Or different usb cord
Click to expand...
Click to collapse
used the rear usb port and magically decided to work, edited the original post. Thank you for your help and I apologize for the much noobiness you had to encounter.
I had installed Kali Nethunter 3 on my Nexus 9 with TWRP, then it started to bug out, so I 'factory reset' it to stock Marshmallow, but when I look in the 'About Tablet' it is still showing [email protected] #2 in the kernal version. I would like to flash stock Nougat, but I cant get my ADB to authorize. I cant get the RSA key authorization dialogue to come up on my device. I do have USB debugging enabled.
If I plug it in while the adb server is started, it does generate adbkey files inside the .Android folder on the Windows machine. I was thinking that I could put these adbkey files into whatever folder they are supposed to be in, on the nexus 9 (data/something...? my data folder looks empty).
Alternatively, could I just put the nougat image onto my nexus 9 and flash it back to stock using TWRP? Ideally making my kali root kernal go away forever? I am not concerned about losing any data.
Not really sure what I am doing here, I just want stock unrooted Nougat and I want my ADB to work again (so I can use it to debug my Android Studio apps)! Thanks.
Can you get a fastboot connection?
Sent from my Nexus 5X using Tapatalk
ritchea said:
Can you get a fastboot connection?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
with my cmd prompt in the platform-tools, if i type 'fastboot.exe devices' nothing happens, it just goes to the next line.
Type fastboot devices
Sent from my Nexus 9 using Tapatalk
junkomatic said:
with my cmd prompt in the platform-tools, if i type 'fastboot.exe devices' nothing happens, it just goes to the next line.
Click to expand...
Click to collapse
and when i type 'fastboot start-server' it says: "< waiting for any device >".
ADB at least can see the device - just says its unauthorized.
I'm not familiar with either of the commands you mentioned as I've never used them. If 'fastboot devices' doesn't return your device, try updating all PC device drivers related to android while connected to fastboot. You don't need adb to install google images, but you need your PC to recognize device (as you know).
EDIT: Is your tab rooted? If so, you can use FlashFire to run the installation without a computer.
If no joy so far, disconnect tab, remove all drivers and let PC redo them when you reconnect. You should get the authorization prompt again.
Sent from my Nexus 9 using Tapatalk
ritchea said:
I'm not familiar with either of the commands you mentioned as I've never used them. If 'fastboot devices' doesn't return your device, try updating all PC device drivers related to android while connected to fastboot. You don't need adb to install google images, but you need your PC to recognize device (as you know).
Click to expand...
Click to collapse
It shows up in my windows devices as Nexus 9, and inside the android studio device manager it is showing the device as unauthorized. I suppse i will try updating all the drivers again.
ritchea said:
I'm not familiar with either of the commands you mentioned as I've never used them. If 'fastboot devices' doesn't return your device, try updating all PC device drivers related to android while connected to fastboot. You don't need adb to install google images, but you need your PC to recognize device (as you know).
EDIT: Is your tab rooted? If so, you can use FlashFire to run the installation without a computer.
If no joy so far, disconnect tab, remove all drivers and let PC redo them when you reconnect. You should get the authorization prompt again.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
yeah it was rooted for kali nethunter. i will check out flashfire, thanks.
FlashFire works great.
Sent from my Nexus 9 using Tapatalk
junkomatic said:
yeah it was rooted for kali nethunter. i will check out flashfire, thanks.
Click to expand...
Click to collapse
so actually it was unrooted during my last factory reset. i finally figured out how to use fastboot to update to nougat, and all the remnants of kali in the kernal is gone. my ADB is working fine now, and i can test on my nex9 from android studio. i used this guide: http://wccftech.com/flash-nbd91k-android-7/
life is good. thanks guys.