Anyone else having these issues? I know there are people having issues mounting it as a storage drive but any to get around this annoying issue?
Sent from my Transformer TF101 using Tapatalk
I had to update my platform tools yesterday for the TF to work on my mac, after the update everything went fine.
jc.extreme said:
I had to update my platform tools yesterday for the TF to work on my mac, after the update everything went fine.
Click to expand...
Click to collapse
Updating the platform tools worked perfectly, now adb sees my transformer.
Thank you!
gigdesigns said:
Updating the platform tools worked perfectly, now adb sees my transformer.
Thank you!
Click to expand...
Click to collapse
Couple of questions:
1). How do you update the ADB Platform Tools? In my Mac, I have an ADB folder that I used for my Thunderbolt, but I have no idea how to update it.
2). So with the updated ADB Platform tools, I can connect my TF to my Mac and my Mac will see it as a "USB" drive? No any other tool required?
Related
Hi,
I am having problems rooting my Transformer that I just purchased this morning.
My windows XP instance is running in VMWare as I have OSX.
I have the USB drivers installed and the APX driver. If I ADB the device in normal mode I can see the device ID, but when I connect in APX mode VMWare gives a warning about not being to connected to it's ideal controller. I am guessing this is because it's not installed to a USB 2.0 port.
When I run root.bat, my usb host controller interface blue screens and windows restarts.
Has anyone else had this problem? I not a noob as I have managed to root my desire and s-off it. I wondering if it's related to the VMWare USB message.
Thanks,
Jon
You can root the transformer in OSX, I rooted mine through terminal.
Sent from my Transformer TF101 using XDA Premium App
What method did you use? Did you try the nvflash method or using BLOB?
Jon
I've rooted and flashed Prime now but i'd be interested to hear how you did it on OSX. I created a linux VM in the end and used the method in this thread http://forum.xda-developers.com/showthread.php?t=1123429
Jon
They did it the old way in terminal.
Sent from my Transformer TF101 using XDA Premium App
Just use this guide
Didn't need to install any extra drivers like Windows users do get adb from the link provided at the beginning of the guide and the followed each of the steps including downloading the rooting tools. The commands are the same but are entered slightly differently in OSX.
Example
In OSX
Code:
./adb devices
instead of Windows
Code:
adb devices
If you've used OSX terminal before you should be fine.
Back when I did it it was primordial 3.1 but this guide has been updated for Prime v1.4 and the overclocking kernal and sloarnz customized CWM, the latter two i don't use myself.
Edit - I see I'm a bit too late replying, but yes just used terminal adb etc. Was very easy to do and satisfying.
Thanks for the replies, I'll have a read through, if anything just to improve my knowledge.
Thanks again.
Sent from my HTC Desire using XDA Premium App
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
Yeah, its another 'ADB not working on device xxx' thread.. but this one really has me stumped.
Device in question is a TF101, PC in question runs Windows 7 64-bit.
PC has been used successfully to develop android apps. for a Samsung S Plus, with the entire toolchain working.
Same PC, running VMWare, virtualizing XP (32-bit), has also been used to develop/debug with the TF101.
Now the problem. Natively (without VMWare), I have been completely unsuccessful getting the TF101 to be recognized by ADB.
What has been tried:
- TF101 USB drivers from Asus
- TF201 USB drivers from Asus (which also include the TF101 drivers from the look of the .inf files)
- Hand-edited .inf file from the standard android ADB driver
- Adding the VID (0x0b05) to adb_usb.inf
- Uninstalling (and deleting the driver) for anything related to android devices (Samsung, and Asus)
So what happens is that the device does appear in device manager, with 'USB Debugging' checked on the Android device.
With one of the driver combinations I end up with 'Android Composite ADB Interface' in Device Manager, but for some reason its under a 'Samsung Android Phone' Folder, this may well be part of the problem.
No matter what I try, 'adb kill-devices/adb usb' always shows 'error: device not found'
I am two solid days into this now, after reading just about every TF101/ADB thread that google knows about.
Anyone else experienced this?, and might know how to resolve it?
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
baseballfanz said:
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
FWIW, I had the same issue. I installed the USB drivers from Asus and could never seem to get ADB to "see" the TF101.
So I ripped them out and installed the full ASUS desktop PC suite from their website. ADB now sees my TF101 just fine. I uninstalled the suite after I had the connection working and ADB still connects to my TF101 without issue. The Transformer PC suite is on the same download page as the stand alone driver.
If you can't find it, PM me and I'll get back to you with a link.
Col.Kernel said:
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
Click to expand...
Click to collapse
I too was using ADB already on my N1 but couldn't make it work with the TF.
After reading and following directions on that thread I got it working.
He might not need instructions to set up ADB from scratch but there's good infos about the Asus PC Suite.
Step 7
Basically same as what you just posted and same as what I did to get it working.
I can confirm that too that installing ASUS SUIT works better than just installing drivers, I don't know why but it does. It's the same with my phone. Sometimes installing usb drivers do not work but when I install Samsung kies then somehow that works better even though it includes the same drivers I am installing as stand alone which do not with properly.
Sent from samsung vibrant
Same thing happened to me had to buy a new cord.... does the computer recognize it at all
Sent from my Transformer TF101 using Tapatalk
im not sure if it would help but everyonce in a while ill have a hard time with my adb connection and ill start up wireless adb and can conect fine from that. i dont know why i think in wireless you use ip address on wifi so it might recognize and connect different.. of course this depends on if you want to use it and is alos hardware dependant mainly wifi.
Here's a funky issue. I've been using ADB without any problems on 4.2.1 and 4.2.2 on this device (Stock Android and some CM10-based ROMs). When I flashed a CM10.2-based rom (JellyBro, I believe?) a few months ago, I was never able to get ADB to work, so I restored a nandroid of my previous setup. After a while, I decided to flash the stock 4.3 image (today) and see if I still have the problem. I do.
Here are the details in a format that I hope is both entertaining and helpful for troubleshooting
Okay fine, what's the problem now?
- I cannot use ADB with my N4 on 4.3.
- I cannot authorize my device.
Seriously? Simple ADB problems? Shut up and search the forums.
- I did. I tried many things.
Well what did you try, then?
I just tried to use the default feature. The phone should prompt to authorize my computer, but I never get a prompt.
I checked /data/misc/adb/ and the directory was empty.
Even so, I decided to click the "Revoke USB debugging authorizations" option in Developer options.
I copied ~/.android/adbkey.pub from my Linux box and put its contents in a new file named /data/misc/adb/adb_key on my device.
When that didn't work, I rebooted the device.
When that didn't work, I disabled/enabled ADB on the device.
When that didn't work, I killed adb on my computer, then restarted it.
When 3a-3c didn't work, I did them all sequentially before trying again, which also didn't work.
Exactly the same as above, but put it in /data/misc/adb/adb_keys intead of adb_key (because XDA and other sites cite both filenames).
Clicked the "Revoke USB debugging authorizations" button again. Rebooted the phone, killed ADB on my computer. Still no prompts to authorize.
It only removed /data/misc/adb/adb_keys, not adb_key. So I'm pretty sure adb_key is the wrong filename (despite being cited at a frequency on par with the correct name).
Update my platform-tools package. No dice.
Can't actually update; I have the most recent version (18.0.1)
Remove and reinstall platform-tools. No dice.
By the way, my permissions for the adb_keys file are 300. Owner is root. Group is root. Or in other terms:
Code:
#: ls -l adb_keys
-rw------- root root
Are you sure this is only happening to you on 4.3?
Yes. I have no problems after installing any 4.2 rom with recovery, or the 4.2.2 factory image with fastboot.
And it's exactly the same issue with factory 4.3 or a 4.3-based ROM?
Yes. Although I've only tried two or three roms, plus the factory image. There may be a magical rom out there somewhere that does work though.
Any other devices?
I tested adb with my girlfriend's 2012 Nexus 7 running 4.3. It had no issues at all.
Any other computers?
Unfortunately no. I only have my Linux Mint 15 box.
-------
Okay, so that's basically the gist of it. Does anyone else have any clever ideas? (Or does anyone see where I was an idiot and made a mistake?)
Check adb version. You need 1.0.31.
vkn said:
Check adb version. You need 1.0.31.
Click to expand...
Click to collapse
I had the same issue several weeks ago and the update to 1.0.31 fixed it here as well.
pjc123 said:
I had the same issue several weeks ago and the update to 1.0.31 fixed it here as well.
Click to expand...
Click to collapse
I did mention in the post that I already tried that. (EDIT: Well, I mentioned platform-tools, not adb specifically. Points to you.)
Code:
$ adb version
Android Debug Bridge version 1.0.31
Any other suggestions? =(
dotvezz said:
I did mention in the post that I already tried that. (EDIT: Well, I mentioned platform-tools, not adb specifically. Points to you.)
Code:
$ adb version
Android Debug Bridge version 1.0.31
Any other suggestions? =(
Click to expand...
Click to collapse
Oops, I didn't notice that. As I am using Windows when I communicate with the Nexus 4 on 4.3, I can't speak for anything related to Linux, although I do have several Linux computers.
pjc123 said:
Oops, I didn't notice that. As I am using Windows when I communicate with the Nexus 4 on 4.3, I can't speak for anything related to Linux, although I do have several Linux computers.
Click to expand...
Click to collapse
Ah, I gotcha. Thanks for trying though! =). Until I get an working solution, I'm just running 4.2 (Because really, 4.3 isn't THAT big of a deal for me).
i have the exact same problem!
i realy realy need ur help, my phone is dead without it.. i need that adb to work so i can fix this,
please help me im desprete
I had similar issues before w/ my N4 and basically did a full re-install of SDK. Have you tried that yet, might work.
So running into a problem. I have downloaded and installed ADB but the version installed is 1.0.32. And my computer doesn't find any devices when I type adb devices.
Is this because I need a later version of ADB and if so any clue how to install it on Ubuntu? I have searched the WEB and can't find it.
Cheers!
swehes said:
So running into a problem. I have downloaded and installed ADB but the version installed is 1.0.32. And my computer doesn't find any devices when I type adb devices.
Is this because I need a later version of ADB and if so any clue how to install it on Ubuntu? I have searched the WEB and can't find it.
Cheers!
Click to expand...
Click to collapse
i am not a Ubuntu user (using Win10 for now), but i found this
https://www.howtoinstall.co/en/ubuntu/xenial/adb
hope that helps
DrakenFX said:
i am not a Ubuntu user (using Win10 for now), but i found this
https://www.howtoinstall.co/en/ubuntu/xenial/adb
hope that helps
Click to expand...
Click to collapse
Thanks DrakenFX for trying. I had already looked at that one. I looked some more and I guess Ubuntu has been having some problems with MTP. The answer for the problem is found at HERE if anyone is running into the same issue.
I use linux as well, but instead of installing the whole Android development kit, I went for the leaner, no-install-required platform-tools, which is the linux equivalent of "Minimal ADB and Fastboot". You can download it directly from Google here: https://dl-ssl.google.com/android/repository/platform-tools_r23.0.1-linux.zip
Unzip it, open up a terminal in the folder, and type " ./adb devices "
swehes said:
Thanks DrakenFX for trying. I had already looked at that one. I looked some more and I guess Ubuntu has been having some problems with MTP. The answer for the problem is found at HERE if anyone is running into the same issue.
Click to expand...
Click to collapse
man this was driving me nuts , LoL :silly::silly:
just did Step 1 and 2 and my issue got fix ,
just got back with dual boot Ubuntu 16.04.1 + Windows 10 and even installing the drivers couldn't get adb to detect my axon 7...till came across your thread and post reply to the other thread....thanks man
DrakenFX said:
man this was driving me nuts , LoL :silly::silly:
just did Step 1 and 2 and my issue got fix ,
just got back with dual boot Ubuntu 16.04.1 + Windows 10 and even installing the drivers couldn't get adb to detect my axon 7...till came across your thread and post reply to the other thread....thanks man
Click to expand...
Click to collapse
Glad I could help.
adb devices on ubuntu 16.04
swehes said:
Glad I could help.
Click to expand...
Click to collapse
Just to document this in case it would benefit someone else: I have been trying everything I could find on the net to get my A7 recognized by adb devices. The list always came up empty. Yet, on my windows 10, adb devices for my A7 worked. And my htc m7 on ubuntu was also recognized. Finally, I removed the famous 51-android.rules (which had a line for my A7 but not for my m7; on /etc/udev/rules.d) and then adb devices showed the A7.
EDIT:
The day after having written this, I lost the device again: adb devices no longer showed the A7. Again tried everything with no success. Then I downloaded the Android SDK, which comes with version 1.0.39 of adb. Ran that and it worked. Go figure. So I still cannot really put my finger on what made the difference.