Database Users

Can't get SDK to recognize Xoom on Mac - help!!

I've already posted this in the development area of the forum, but honestly I'm just sitting here hoping someone will reply and I don't think enough people will see my post there. But at any rate, I've been sitting here for the last few hours hoping someone will help me out; I am trying to complete the unlock procedure for my Xoom on my Mac, and for some reason I cannot get the SDK to recognize my Xoom ("adb devices" shows nothing). I'm really hoping someone can give me a tip as to how I can get this otherwise simple procedure to work.

Dumb question, but do you have USB debugging turned on?
Settings -> Applications -> Development
Oh I guess you're trying to do fastboot... nevermind

Bauxite said:
Dumb question, but do you have USB debugging turned on?
Settings -> Applications -> Development
Click to expand...
Click to collapse
Maybe not a dumb question, as I do not have it turned on...but thats only because none of the published instructions for unlock mention this. I just went straight to the power down, followed but the power-button-and-down-volume combination to go into the fastboot protocol support.

This is incredibly frustrating, I have no idea what to do. I guess this is what happens when you get your xoom several days after everyone else did.

joeski27 said:
This is incredibly frustrating, I have no idea what to do. I guess this is what happens when you get your xoom several days after everyone else did.
Click to expand...
Click to collapse
Are you running adb as root? Try 'sudo adb devices'
I have to do this on linux.

Bauxite said:
Are you running adb as root? Try 'sudo adb devices'
I have to do this on linux.
Click to expand...
Click to collapse
Nope, still nothing showing up. This is ridiculous.

I found something while at work today. You need to go to android.com/filetransfer and download the file transfer application as the Xoom can't be recognized without it. Hope this helps I have used it since launch and it works well.

angermeans said:
I found something while at work today. You need to go to android.com/filetransfer and download the file transfer application as the Xoom can't be recognized without it. Hope this helps I have used it since launch and it works well.
Click to expand...
Click to collapse
This is not true at all. The file transfer tool is for transferring files to the Xoom, not interacting with it via adb and fastboot. The Mac should just recognize the device (mine does, and I don't have the file transfer tool installed).
I just realized this is related to the post you made in the Root (or unlocking?) thread. Make sure if you want to see the device in "adb devices" that you have the Xoom booted normally.
If you have it in fastboot mode it should show up in "fastboot devices"

TWRP for mac???

EDIT: Please delete thread, problem solved.
Does anyone have any information on installing twrp from a mac? I have adb installed, but I haven't read anywhere about how to install it using a mac.

I installed TWRP using my Mac with the official Android SDK and platform-tools for Android 2.3 and Android 4.0 installed.
Basically just followed the instructions on the RootzWiki, as recommended by one of the devs: http://rootzwiki.com/topic/12343-how-to-install-twrp-20-linux/

did you install usb drivers (even though they aren't supported by mac osx)? and did you do anything differently because you were using a mac?
thanks for the link.

adbirdie said:
did you install usb drivers (even though they aren't supported by mac osx)? and did you do anything differently because you were using a mac?
thanks for the link.
Click to expand...
Click to collapse
Sorry man, I don't remember whether or not I installed any USB drivers. If they're not supported, I imagine that I didn't.
But, I don't want to give you misleading info -- so, if you're not sure, I'd say hold off until someone who really knows what they're talking about chimes in. I'm pretty reckless when it comes to this stuff, and I'd hate for you to do something you regret on account of my mouth, ha!

sorry, another question, did the kindle automatically show up in adb with no tinkering, hate to pester you, im just planning everything before i give it a go.
also, did you plug it in while it was on with usb storage enabled?

adbirdie said:
sorry, another question, did the kindle automatically show up in adb with no tinkering, hate to pester you, im just planning everything before i give it a go.
also, did you plug it in while it was on with usb storage enabled?
Click to expand...
Click to collapse
You don't need any drivers. Adb and fastboot should both work just fine. You might need to edit the ini file though.

Did you have to edit the usb_ini file? if so, how would i go about doing it?

adbirdie said:
Did you have to edit the usb_ini file? if so, how would i go about doing it?
Click to expand...
Click to collapse
Same as on linux... I changed it, but i'm not sure i needed to.

ok, one final thing ( i promise) http://rootzwiki.com/topic/12343-how-to-install-twrp-20-linux/ is that similar to what you did?

Edit: I've ****ed up and now i'm stuck in fastboot. do you have any ideas how to fix that?

VS980 root troubles

Hey guys ive been pretty stoked to root and rom my g2 now that im bored of LG's UI haha i have been trying to use the IOroot method but something about the drivers is giving me such a hard time! i installed them but every time i open a command window and type in "adb devices" nothing is coming up so obviously its not being able to read my device which isnt alowing me to root my phone any help would be greatly appriciated! thanks in advance

I was having trouble, finally went to LG site to download drivers
Sent from my VS980 4G using XDA Premium 4 mobile app

adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978

djraimondi said:
adb is a special android thing. You need to install it to just use it anywhere. Do this:
1. Create a folder on your desktop (you can call it root or whatever you want).
2. Extract IORoot into folder created in step one.
3. SHIFT RIGHT CLICK and do "open command window here" (This is the most important).
4. type
Code:
adb devices
5. if you devices shows run the root.bat file to root your device.
Look at this for a little more help.
http://forum.xda-developers.com/showthread.php?t=2515978
Click to expand...
Click to collapse
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past

Cyko.Tech67 said:
IVe done this so many times haha... the problem is when i type that into the command window nothing comes up under listed devices and ive downloaded and installed the drivers from several different locations including the LG website... could it be the ethernet thing that im missing? because thats the only thing i dont believe ive done cause this is a hastle xD ive had no problems rooting in the past
Click to expand...
Click to collapse
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???

hd-renegade said:
Do you have the phone listed correctly for what mode to be in when you plug in the USB cord???
Click to expand...
Click to collapse
i have tried both with Charge only mode and MTP

Cyko.Tech67 said:
i have tried both with Charge only mode and MTP
Click to expand...
Click to collapse
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.

hd-renegade said:
This is just a thought, but maybe, power the phone off, power the PC off. Turn them both back on, re-read the instructions on how to root the phone. It sort of sounds like you could be missing just a little thing on the instructions. You may also try a different USB port on your PC too. I rooted mine back on iRoot 6 so I would have to think that iRoot 10 should be better then what I used.
Click to expand...
Click to collapse
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...

Cyko.Tech67 said:
I just dont think im installing the drivers right because ive tried everyone and their mothers usb ports and ive tired it on 4-5 computers there has to be something im missing with the drivers because the process just wont start Daemon will succsesfully start running than nothing...
Click to expand...
Click to collapse
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.

hd-renegade said:
It has been a while sense I rooted mine, but I think the fix for me was getting the drivers from the LG Site and using the LG Flash tool.
Click to expand...
Click to collapse
whats the flash tool for?

I think I ended up flashing back to LG stock. Sorry it has been a while sense I played with that stuff.
Sent from my VS980 4G using Tapatalk HD

I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.

dp917 said:
I had the same issue. I installed these lg drivers, not sure if they had anything to do with it because it still didn't work. What finally worked was when I turned off debug and may have been in mtp connection. Obviously after you have to put back in debug and ethernet connection to follow the ioroot method.
Click to expand...
Click to collapse
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?

Cyko.Tech67 said:
alright one more question and thanks for the fast replies guys! i appriciate it but im not to nifty with computer tech as i am Smartphone xD laptops still have an ethernet mode correct? and if so where do i go to enable it?
Click to expand...
Click to collapse
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."

dp917 said:
Ethernet mode is in enabled in your phone. Settings > scroll to bottom "pc connection."
Click to expand...
Click to collapse
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went

Cyko.Tech67 said:
awesome thanks so much guys a thanks to both of you ill try it when i get home and let ya know how it went
Click to expand...
Click to collapse
Let the folks here know how you make out.

hd-renegade said:
Let the folks here know how you make out.
Click to expand...
Click to collapse
unfortunatly with ethernet on i am still getting the same results... its just not recognizing my device? at least now in the notification bar i get the notification that USB debugging is on so i guess im making progress? uggh this is getting pretty annoying any thoughts guys?

Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.

Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.

Steamer86 said:
Run it directly from local drive root. IE C:/ Windows 7? Control alt delete. End the stale adb process, you should see two, one not performing sitting around 2000 kb ram and the other using ram. End that and it should force adb to kick in. I had to do this on win 7 multiple times with dif phones. It's like it locks up when finding the com port or whatever the hell it's doing. I take no blame if you screw up your device this way. I have resorted to a virtual xp for all my phone needs as not everything works in Linux.
Click to expand...
Click to collapse
simon_lefisch said:
Here's how rooted my phone with IORoot:
Unzipped IORoot to root of my hard drive
Plugged in phone with usb (make sure debug mode is enabled). When prompted to choose connection, choose modem. You should see debug icon appear in status bar. If not, choose Ethernet.
Opened IORoot folder. Hold down shift and right click an empty area and choose 'open command window'
Type adb devices. If device shows up, proceed. With normal root procedure.
Click to expand...
Click to collapse
Not sure if it matters but I am running 64 bit Windows 8
- In the instructions didn't you have to change a setting for the Com Port to get it to see the phone??
- Did you ever get the prompt on your phone to accept the Connection. I can not remember what it was, but it only comes up once, and I am not referring to the USB connection IE Ethernet??
- Are you sure you have Developer Options turned on?? The step where you keep tapping on the Developer thing and then the phone finally gives you the Developer Options??

Oneplus 5 ADB

Can someone guide me how to get ADB working on OnePlus 5?

stalvekio said:
Can someone guide me how to get ADB working on OnePlus 5?
Click to expand...
Click to collapse
i'm using 'block this!'

What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options

colin.pohle said:
What's the problem about it?
download android platform tools or minimal adb and fastboot, make sure drivers are installed and activate ADB Debugging in Developer Options
Click to expand...
Click to collapse
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers

stalvekio said:
I have tried all of those. All i get is emty list. It cant detect my phone.
Probably i havent found the right drivers
Click to expand...
Click to collapse
Try these.

I had driver issue for side loading even after Installing OnePlus drivers windows wanted to use standard ADB drivers

Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!

What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.

ddaharu said:
What exactly do you want to accomplish. Because I just flashed everything on my phone. When the phone was running normal ADB was not recognized in my phone. However when I was in bootloader mode I got to unlock my bootloader and flash TWRP.
Click to expand...
Click to collapse
Adb still somehow has to work... The drivers are there (although all my win 10 devices installed the correct ones automatically) and it doesn't even really matter which adb he is using

shadowstep said:
Try these.
Click to expand...
Click to collapse
I tried. Device manager still shows adb interface yellow.
d0nsman said:
Download the Android SDK kit first. Then plug in your OP5 to your PC and you should see something called "CD Drive (F: ) OnePlus Drivers". Click on it and it will install the OP5 drivers. Then enable developer options on your phone, by hitting the build number 7 times. Then go into developer settings and enable USD debugging. After that, go to the Android SDK folder and go to tools/platform tools, then hold shift and right click and open a command/powershell window and type adb devices. After that you should receive a fingerprint notification on your phone so just say yes to it. Ten type in adb devices again in the command/powershell window and it should be able to detect your device. I said everything from scratch so I hope it sort of helps!
Click to expand...
Click to collapse
I did that. ADB devices gives me empty list.

stalvekio said:
I tried. Device manager still shows adb interface yellow.
Click to expand...
Click to collapse
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.

shadowstep said:
Do you have Windows? If yes, what version? With 10, I know they work a 100% for sure. With 7, after installing these, there is still a yellow exclamation mark in Device Manager. To resolve that, right click on the device in Device Manager, uninstall the driver. Then, reconnect the device after enabling USB Debugging, and then let windows download the required drivers from Windows Update. It should be ~8.5 MB. Once it's downloaded and installed automatically, you should be good to go.
Click to expand...
Click to collapse
win 8.1.
Did as you sugsested but no change .... adb interface is yellow

stalvekio said:
win 8.1. Did as you sugsested but no change .... adb interface is yellow
Click to expand...
Click to collapse
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:

shadowstep said:
Stop using the worst windows ever! Jokes apart, try using the these or these. I had them installed before, and they worked fine, in Windows 7 & 10 at least. Good luck! :good:
Click to expand...
Click to collapse
Nope. No help.
I think it´s something very easy i have missed

Finaly - got it working.
This guide helped:
http://www.asunsoft.com/android/how-to-manually-install-usb-driver-for-android-phone.html

Anyone get ADB working?

Anyone get ADB working? I'm getting a no permissions (udev rules) on my linux machine. I'm guessing we need to add the device into udev
EDIT: Solution for Ubuntu/Linux here: https://forum.xda-developers.com/showpost.php?p=73619079&postcount=20
hmm it works on my Mac though..

did you use Sudo?

stewa2jm said:
did you use Sudo?
Click to expand...
Click to collapse
Yeah, it's not working.. I tried adding the dev in my android.rules file and still nothing. I'm going to play with it more now
Sent from my PH-1 using Tapatalk

Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.

stewa2jm said:
Do you need to update your ADB version on your Linux box? I had this issue at one point. With a different phone a couple years ago. Wouldn't recognize the device.
Click to expand...
Click to collapse
I'm always on the latest version since I do a lot of Android development. I don't get why it's not working.. I've had to add devices in udev so many times, never did it give me an issue before. I'll see if I can figure it out though
Sent from my PH-1 using Tapatalk

ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.

whatever you figure out, please let us know! Good luck, and congrats on getting your device!

IM0001 said:
ADB Debugging is on in Dev Options right? lol
I know its super basic, but got to check anyway.
Click to expand...
Click to collapse
Really? Lol I did mention it works on my Mac, so yeah.. It's turned on.. I've even tried turning it off and then on again. [emoji1] [emoji1] [emoji1] [emoji1]
stewa2jm said:
whatever you figure out, please let us know! Good luck, and congrats on getting your device!
Click to expand...
Click to collapse
Will do!
Sent from my PH-1 using Tapatalk

any idea whats causing adb to not work?

drocny87 said:
I found a work-a-round to transfer your files from one phone to the Essential.
create a folder on your desktop and copy and paste all files you want transferred to the PH1. Once you have completed that just copy and paste those files from that folder to the phone.
Click to expand...
Click to collapse
wow, an extremely obvious solution to a problem no one asked about and has nothing to do with this thread!!

I've got ADB to connect somewhat. Instead of cd\sdk\platform-tools just run cd\sdk. ADB devices shows my phone, but once I ADB reboot bootloader, it will boot into the bootloader, but that's it.

I can't get it to work at all windows 10
Sent from my PH-1 using Tapatalk

I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device

skw5115 said:
I'm on Windows 10 as well. ADB works as long as the phone is booted into the OS. Once I enter the bootloader ADB nor fastboot can see the device
Click to expand...
Click to collapse
What is your usb setting? Charging, file transfer?

bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
I tried on both already
Sent from my PH-1 using Tapatalk

I got ADB working on linux. You need to add this to your 51-android.rules
#Essential
SUBSYSTEM=="usb",ATTR{idVendor}=="2e17", ATTR{idProduct}=="c032", MODE="0666", GROUP="plugdev"
I still can't get fastboot to work yet though. To get it to work I need to run: sudo $(which fastboot) devices
I'm going to play around with it more to see if I can get it to work just using fastboot devices

ADB is working on Windows 10, but as mentioned above, fastboot isn't recognized. Can't unlock the effing bootloader without that dammit.
---------- Post added at 08:20 PM ---------- Previous post was at 08:14 PM ----------
bricky23 said:
What is your usb setting? Charging, file transfer?
Click to expand...
Click to collapse
File transfer

Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked

skw5115 said:
Okay so to get it my PC to recognize the device in fastboot, I had to open Computer Management < Device Manager and find the device listed as Mata while booted into the bootloader. Windows didn't know what driver to use so I manually selected the Android Bootloader driver. You have to list all installed drivers on your machine and it should show up for windows 10 users. Device is now unlocked
Click to expand...
Click to collapse
Same here, just manually installed Google USB Driver and installed it as "Fastboot Interface" and it worked.

Ok I got adb and fastboot both working on Ubuntu/Linux now. Instead of adding the line I posted in my previous post just run this:
sudo sh -c "echo 'SUBSYSTEM=="usb", ATTR{idVendor}=="2e17", MODE="0666", GROUP="plugdev"' >> /etc/udev/rules.d/51-android.rules"
Then
sudo service udev restart
Then ubplug your device if it's plugged in via USB and then plug it back in. adb works as well as fastboot