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.
Related
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
mdky said:
Hello,everyone.I've got a Sprint optik(zte v55) 7" pad coming with HC 3.2.
After I flash a modified kernel, Its usb debugging mode can't work properly and my pc can't recgonize it.
Before I flash the kernel, when I switched to usb debugging mode and connect to my pc(runing win7), v55 will display a icon in taskbar showing it's connected with pc, my pc will show a new driver that showing the dirs and files in v55's internal storage, and when I run command "adb devices", it will show v55 is connected.
now, all the above is not happening anymore.
Can anybody know what should I do now ? My intention is to root and flash CM10 to v55,and can be recongize by my pc again.
The kernel I flashed into is in http://forum.xda-developers.com/showthread.php?t=1473555,kernel #60 for v55.
Click to expand...
Click to collapse
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
For more info, you should check Android's page on ADB if you would like. http://developer.android.com/tools/help/adb.html
I'm not sure if any of this is actually directly related to your issue, but it is nice to start with the basics.
wildstang83 said:
Hi, here are some things to keep in mind when using adb.
Be sure of the command you are issuing
Insure you are in fact cd'd to wherever on your pc the adb binary is located
Insure your jdk is included in your path on your pc
To make things easier you can always also add the tools and platform-tools folder of the android sdk to your path
Lets make sure you are properly set up first before you start flashing things randomly.
Click to expand...
Click to collapse
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
mdky said:
Thank you for reply.
The adb command I use is install by v55's driver.Everytime I use adb, I always go into the driver's dir (C:\Program Files\ZTE Tablet V55 USB Driver) which adb.exe is in.
And this dir is in my path.
The thing is : I use 'adb reboot bootloader' and 'fastboot boot CWMrecovery.img' to flash the kernel in, which means the adb.exe and fastboot.exe can work before I flahsed the kernel, and now they can't work.So I think maybe it's the kernel cause v55's usb can't work ?
Forgot to metion: now, when boot into android system or recovery mode, I can't use 'adb devices' to discover the device;when I boot in ftm mode(which I don't know what it is),sometimes 'adb devices' print 'xxxxx offline' , sometimes print 'xxxx recovery'.
when print 'xxx recovery', I use 'adb reboot bootloader' , v55 enter black screen with back light which seems in bootloader mode, but 'fastboot devices' and 'fastboot boot CWMrecovery.img' are not working.Very strange.
Click to expand...
Click to collapse
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
wildstang83 said:
Ooook now we're getting somewhere, I think
Make sure when you send your fastboot flash command you send it like so:
Code:
fastboot flash recovery recovery.img
Replace 'recovery.img' with the actual name of the img, whatever it is.
Also if you are getting the device offline error try killing server:
Code:
adb kill-server
and then restart it
Code:
adb start-server
See if that helps.
Click to expand...
Click to collapse
I will try these command when I get home, thank u!:good:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
mdky said:
"adb kill-server" and "adb start-server" works fine.They turn v55's "adb devices" from "offline" to "recovery".
And I run command "adb reboot-bootloader", it seems that v55 is in bootload mode.
But after that,I run command "fastboot flash recovery CWMrecovery.img",it returns '<waiting for device>' and stuck there.
Before I flash the kernel #60, I can run "fastboot boot CWMrecovery.img" to boot to cwm,so I think it's not likely be the driver's problem,am I right?
Click to expand...
Click to collapse
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
wildstang83 said:
Sorry to take so long to reply. I think it is not a driver issue. Do you know if debugging/adb is even enabled in the ramdisk? This generally would have to be done by the dev who created the kernel. Speaking of that, have you tried to contact that dev for further support? For sure they would know more than me since I don't own the device myself. I just know enough to be slightly dangerous, lol
Click to expand...
Click to collapse
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
mdky said:
It's very nice of you to keep help me here ,thanks again:good:!
After keep trying in past two days, I found that in ftm mode adb is enabled, and 'adb reboot bootloader' truly made the device into bootloader mode.
On my win7 pc, It can't be recognized.I switch to my old xp pc,and install the driver come from other zte user,and then...fastboot works.
Now I have the v55 running CM10,Awesome!Thanks to all contributors.
Still, my win7 pc and xp pc can't recognize my v55 through usb.But it's not big deal now.I can use tf and wifi and other ways to transfer file to v55.
Click to expand...
Click to collapse
Oh wow, that is quite the ordeal, but atleast its something huh, lol
I wonder if you could run adb and fastboot commands in xp mode on your win7 pc?
I know there is a way to run programs in XP mode, its just been awhile since I've done it.
And its no problem to keep trying to help, even if I don't know the device and all that. Maybe I can learn to while we are at it, and maybe make a new friend along the way
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Thermaltake868 said:
Hi I am trying to flash elitekernel from bootloader fastboot but adb is keep saying that "device not found" when I tried to enter adb devices but he said "list of devices attached", I tried adb kill-server and adb start-server I tried disconnect and connect my device from USB, but nothing helped. Can someone help me what am I doing wrong ?
Click to expand...
Click to collapse
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
[email protected] said:
The device never gets recognized so easily on "adb" whereas in fastboot u would not have any issues.....
since u r going to flash the kernel try "fastboot devices" u ll be able to see ur device
The adb issue will be solved by restarting the PC or by trying to re-install the HTC drivers
Click to expand...
Click to collapse
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Thermaltake868 said:
I tried fastboot devices and enter but it's just blank nothing
I tried restart PC didn't help, I tried to restart the phone too, and reinstalling drivers nothing.
Even WinDroid HTC One X+ Toolkit won't recognized him when he is in fastboot, but when he is in windows he said Online on status. I really have no idea where did I go wrong I usually always get him into fastboot flash normal.
Click to expand...
Click to collapse
I always had the device shown as BLANK on "adb" when using windows
whereas on fastboot I never had that issue.....
can u try this
In windows install this MInimal ADB and Fastboot give a try on"fastboot devices" using this
if not working re install the drivers and try the MInimal ADB and Fastboot again
I am suggesting this because it had worked flawlessly for me with proper drivers and MInimal ADB and Fastboot.......
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Thermaltake868 said:
I never had to install drivers I just installed some adb universal drivers from WinDroid HTC One X+ Toolkit 3.0 it always worked without installing any other drivers, but all of the sudden it's not. I tried now using that MInimal ADB still blank, I will try now to reinstall or uninstall completely that adb universal drivers, and try again.
Click to expand...
Click to collapse
Dude try this USB drivers if nothing works
[email protected] said:
Dude try this USB drivers if nothing works
Click to expand...
Click to collapse
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
EDIT:
I manage to get device ID on adb devices in windows, but when I enter bootloader in fastboot he can't recognized him on command "fastboot devices" he said "device not found", and I can't flash kernel becouse he needs to be in fastboot.
Thermaltake868 said:
Installation won't start on this one that you gave me. I run it but nothing happends.
P.S
I download AdbDriverInstaller he said that I already have installed adb drivers, don't know how when I uninstall it all.
Click to expand...
Click to collapse
Weird I just installed this and Minimal ADB on my PC and checked....
all good here can see the Device on the adb and fastboot..
try again as administrator or something...might help not sure
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Thermaltake868 said:
I was thinking all the time that I'm doing something wrong, but every time I did it before it went well, but now I have no idea whats happening, why he won't recognized phone in fastboot, it said fastboot usb, and when I connect him he is always "waiting for device" or "device not found"
Click to expand...
Click to collapse
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
[email protected] said:
thats sad......but it happens
can u confirm using which u r trying to get the phone on fastboot....android sdk kit or Minimal ADB
and can u see these files in the fastboot folder
ADBWinApi.dll ADB link library for Windows
ADBWinUsbApi.dll ADB link library for Windows
please confirm this....
Click to expand...
Click to collapse
I am using minimal adb that you gave me, and yes both files are in the folder.
Thermaltake868 said:
I am using minimal adb that you gave me, and yes both files are in the folder.
Click to expand...
Click to collapse
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
[email protected] said:
are u still not able to install this driver I gave the link for....
I would try by uninstalling all the installed drivers and install only the above mentioned driver.....Give a try :good:
Click to expand...
Click to collapse
I did that too now, and in windows I get adb devices he show me number of my device, my friend told me now that I can flash kernel when I am in OS that I don't have to be in fastboot he will enter fastboot on his own, and I try that too, and as I told he manage to find device via adb, but when he enter bootloader in fastboot he is waiting for device in kernel cmd windows he can't find him.
Make sure your using a USB port that connects directly to your mobo. adb/fastboot is dodgy with USB hubs. Try a port at the back of your PC.
Sent from my HTC One X+ using Tapatalk
I fixed it I had old drivers for USB I installed new from intel chipset did the setup.exe -overall in cmd after that I uninstall htc drivers that I installed before remove them completly restart PC after that install latest HTC Sync connect the phone run the .bat from kernel, and it went successfully.
Thanks for all the help guys
Adb is showing list of devices attached..what is the solution for this..if any one knows how to solve this problem can u help me??
@Vinay23
On the device I'm using, this was under "Default USB Configuration" - advice from others appears to be that selecting PTP is the way to go.
For me, it works =).
Hope that might help out.
I found it here:
“adb devices” returns empty “List of devices attached” on Ubuntu
Based on react native documentation (https://facebook.github.io/react-native/docs/running-on-device) I wanted to connect to ADB in my ubuntu vm (Ubuntu 18.04.2 LTS) but my problem is that i keep ge...
stackoverflow.com
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
In Windows I cannot find it at all, running adb devices gives me an error.
In ubuntu it shows up as ??????????? but i have no permissions for some reason, so I cannot do the steps to Bump
Anyone have a way to fix this so I can Bump and finally get on to flashing the Modem, then custom roms finally!
You can also install it from Terminal Emulator, right on the phone, rather than adb. In TE, skip the "adb shell" line, input the 2nd - 4th lines, starting from "su".
chewyTree said:
In Windows I cannot find it at all, running adb devices gives me an error.
In ubuntu it shows up as ??????????? but i have no permissions for some reason, so I cannot do the steps to Bump
Anyone have a way to fix this so I can Bump and finally get on to flashing the Modem, then custom roms finally!
Click to expand...
Click to collapse
You can also use Flashify to flash the bump'd TWRP recovery - that's what I did, worked beautifully. You can find Flashify in the Play Store.
For Linux, you must run sudo adb devices... Then the rsa key will pop up on the phones screen, then your good to go. You must run the sudo command first, or you'll need to run the adb kill-server command, then start again with elevated permissions. If your on 11c, you must be in ptp mode, for 10b ethernet mode.
For Windows, well who cares, use Linux...
annoyingduck said:
For Linux, you must run sudo adb devices... Then the rsa key will pop up on the phones screen, then your good to go. You must run the sudo command first, or you'll need to run the adb kill-server command, then start again with elevated permissions. If your on 11c, you must be in ptp mode, for 10b ethernet mode.
For Windows, well who cares, use Linux...
Click to expand...
Click to collapse
Thank you all. Those adb kill commands were it. Everything worked out fine.. but now when i do the rest of the steps i boot into system recovery (not twrp) but like the phone system recovery, and it seems like thats not what i should be booting into.
annoyingduck said:
For Linux, you must run sudo adb devices... Then the rsa key will pop up on the phones screen, then your good to go. You must run the sudo command first, or you'll need to run the adb kill-server command, then start again with elevated permissions. If your on 11c, you must be in ptp mode, for 10b ethernet mode.
For Windows, well who cares, use Linux...
Click to expand...
Click to collapse
Yeah but those things are spendie and my 3 kids devour any dollars I get lol
WHATSAMATTA U ALUMNI
Sup. I'm a new member of XDA and would like to be a part of the community. I've heard great things.
I'm trying to install ADB and fastboot on my computer running the latest version of Ubuntu. Here's what I have done:
1. Enabled Developer options
2. Verified that USB debugging and OEM unlocking are on
3. Ran the command:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Click to expand...
Click to collapse
However, unfortunately I receive this response:
adb reboot bootloader
daemon not running. starting it now on port 5037
daemon started successfully
error: device not found
Click to expand...
Click to collapse
Unfortunately it does not recognize my device. I tried Googling it and looking on the CM Wiki, but I wasn't able to figure out why my device isn't recognized by my computer. Any ideas?
Thanks :]
after the two commands try apt get update command. and reboot the system.
Now it may work.
try it in Windows which is way easier than the linux.
"adb devices" command will list the working device and state.
sundhar88 said:
after the two commands try apt get update command. and reboot the system.
Now it may work.
try it in Windows which is way easier than the linux.
"adb devices" command will list the working device and state.
Click to expand...
Click to collapse
I tried typing in "apt get update" but it didn't recognize the command. Tried adb devices but it didn't input any results. I will move over to Windows to see if I have better luck.