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

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"

Related

Using the RUU Issues

Hero had a hardware fault w/ the SD slot(good thing too! I dropped it last week and had a bit of rub on the top left that was bothering the hell out of me)
Was going to go get it replaced tonight, but for some damn reason the RUU won't work.
I have the latest RUU(1.56?)
Tried with phone w/ and without USB debugging
Went into fastboot mode(which made W7 install drivers for Android 1.0?) yet the RUU still won't recognize the phone.
I'm not computer illiterate, I'm just having problems with this damn RUU.
Halp?
What's the error you're getting?
The RUU basically says like
"Finding your Android Device" for about 30 seconds then says it cannot find it.
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
thedudejdog said:
error 170...
ahh we meet again
i've helped a few people through this but i don't want to spoil the fun..
read this
all the way through it has the steps needed to get you up and going.
what os are you running?
just read windows 7..
try right clicking and "run as administrator"
Click to expand...
Click to collapse
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
intx said:
I've read this before, I got it from geekfor.me
My windows 7 has the real administrator account enabled, running as administrator won't do anything.
Click to expand...
Click to collapse
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
thedudejdog said:
ok.
basically my next question is do you want my help or not?
i know how to make it work for you, at least three other people have gotten it to run by following my directions.
Click to expand...
Click to collapse
Why wouldn't I want help?
ok try this.
type "adb devices"
if that sees your phone type reboot into fastboot then type "fastboot devices"
if that sees your phone then run the ruu
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
intx said:
adb devices sees it.
boot into fastboot, fastboot devices sees it.
run the RUU, error 170 still >_<
Click to expand...
Click to collapse
have you tried this?
realmrealm said:
For some of the people running into problems with Windows 7 you may want to try:
1. Right-click on the executable file "ARUWizard.exe" and then go to "properties"
2. I believe there is a tab called "Compatibility" or something, click on it.
3. there should be a place for you to click next to a "run this program in compatibility mode" put a check there
4. below that there should be a drop down box, try choosing "Windows XP SP3" (or something similar to that)
5. near the bottom should be a place to check "run as administrator" check that.
6. click "ok" and then try running the program again.
I'm in front of a windows xp computer right now, not windows 7, so excuse me if i don't remember the options correctly, but I should be pretty close.
I also don't even know if this will work, but it's definitely worth a shot.
-AndyS-
Click to expand...
Click to collapse
or this?
10 char...
flipzmode said:
Possible resolutions would be:
1) Putting it in to fast boot and trying it again. Check your error log if it fails and seeing if it identified your phone this time.
2) Open a command prompt and "cd" to the folder where your \sdk\tools\ folder and type in "adb devices" and hit enter and see if it sees your phone. If not then that's your problem. If it DOES see your phone then enter the following command
3) adb shell reboot oem-78 -- that will reboot your phone in to RUU-ready fastboot. If you had the RUU still open then close it. Then open it and try running again.
Click to expand...
Click to collapse
or this?
crunchybutternut said:
Just had a thought.. after updating my HTC Sync software the adb included with my RUU might be out of date. I copied adb.exe, AdbWinApi.dll and fastboot.exe from C:\AndroidSDK\Tools and overwrote the files in the RUU folder. Then I ran it without a hitch.. weird, eh?
Click to expand...
Click to collapse
Tried the first two things, neither helped
I figured out part of the problem though. I had to dig up some 64 bit drivers.
I got the RUU to recognize my phone and it sends it to the bootloader and gets stuck on Waiting for bootloader then errors 170 out.
I'll try copying the files over now.
Replacing those 3 files did the trick!
Thanks
intx said:
Replacing those 3 files did the trick!
Thanks
Click to expand...
Click to collapse
no problem, when i did it i tried all of those steps at once, so i wasn't sure which one fixed it for me. so now (in theory) it should work for you on that machine every time.
wont run and get "ARUGlobal.dll can not be found" even tho im looking right at it....

If anyone knows how to get adb working with the Iconia-

I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
officetally said:
I can't get adb to work with my iconia to save my life... I've tried every driver out there to try to get the device recognized but I can't even get it connected to my computer. I have the mini usb cable and all, and I can copy/paste files into the tablet memory, but whenever I start adb it won't recognize it. How did you guys get yours set up? And I've connected my incredible via adb so I know my sdk kit is legit. Just let me know, thanks-
Oh, and: Iconia is rooted. Also, I've tried to start the device manager (i'm on win7 btw), locate the missing device driver, update driver, and navigate to where I got the acer driver from their website, but to no avail. Could it be my rom? I have a hc 3.1 on there atm. Well, that's about it haha
The ultimate goal is to install native ubuntu on the a500, but I need access to adb first.
Click to expand...
Click to collapse
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
kjy2010 said:
This may sound silly, but have you gone into settings, applications, development, and checked "USB debugging" to on?
Click to expand...
Click to collapse
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
looking335 said:
Hmm ... did you install the USB drivers from Acer's support site?
http://support.acer.com/product/default.aspx?modelId=3851
Another option with ADB is to do so via IP. Search the Market for 'adb' and there should be a few apps that will allow you to use ADB over TCP/IP. From your computer, with ADB installed, you'd connect with something like:
adb connect <Tablet's IP address>:<port>
I seem to think port 5555 is the default.
If, after trying this method, you still cannot access/see your tablet (assuming you started ADB services), then you may want to check your SDK.
Best of luck.
Click to expand...
Click to collapse
And please my op... of course I tried the drivers from acer's site, both of them. And my sdk kit works, just like I said. But thanks!
officetally said:
DUDE! Haha, why didn't I think of this?? Thanks a lot man, it worked!
Click to expand...
Click to collapse
Glad it was something simple!
Sometimes we always overlook the simple things.
But I would not have told on myself.to many other things could blame it on.giggles

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??

[Q] Having trouble getting Mac OS X to see N4 with adb and fastboot

Hello,
My N4 is soft-bricked. Well, hopefully that's all it is.
I want to sideload a ROM onto it, via Mac OS X 10.9.3
I have found plenty of instructions on how to do that with a Mac.
But I can't get ADB or fastboot to see the device.
When I go to the system information on this Mac and looked at the USB devices, I see the Nexus there... along with its serial number, etc. But in Terminal I get a device not found error in ADB and nothing at all in fastboot.
It is my understanding I don't need to install any special drivers on Mac for it to detect the device. Is that correct?
If not, does any one have any suggestions on how I might get this device connected properly?
Thank you...
With further research, I have made some progress. I found this: http://stackoverflow.com/a/7169048
It says:
Also, if that does not work, check to see if the device shows up under USB in the System Profiler (included in OS X). If it is showing up there, but not in ADB, try adding the USB Vendor ID of the phone to ~/.android/adb_usb.ini
This file can be created if it does not already exist. The Vendor ID of the Nexus S is 0x18d1. Please make sure the last line of the file is a Vendor ID, do not leave a blank line at the end.
Click to expand...
Click to collapse
After doing that, I can now see my N4 listed. Well, at least it does when I am in recovery mode.
Now I shall see if I can make some progress with pushing a ROM to this thing (I am new to all this, so I'll see how this goes...)
Can you get to the bootloader screen? Only there fastboot will work.
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
coolqf said:
Way easier if you just set up a virtual machine and run Odin from Windows.
Sent from my SM-T320 using Tapatalk
Click to expand...
Click to collapse
Thanks. I have a VM on this Mac... so i'll try doing this through that.
AndroidWelcome said:
Thanks. I have a VM on this Mac... so i'll try doing this through that.
Click to expand...
Click to collapse
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Thanks
coolqf said:
Let me know if you run into any problems. It's how I change ROMs on my Tab Pro. I use OS X 10.9.3
Click to expand...
Click to collapse
Sorry I never replied. Thank you. I got it sorted. Nice to have my N4 up and running again.

Categories

Resources