Can someone help?
I got it working on XP but I also have Linux (Ubuntu) installed on this machine.
I can't seem to get it to work though.
Install the app on your android phone (DONE)
Turn USB debugging on on your phone (DONE)
On your G1 go to the home screen, press MENU > Settings > Applications > Development, then enable USB debugging. (DONE)
Follow the instructions here to install the Android driver (STUCK)
I tried creating the file and it saved ok but when I closed it, I got this error.
Code:
[email protected]:~$ sudo gedit /etc/udev/rules.d/50-android.rules
[sudo] password for lukehluke:
** (gedit:5985): WARNING **: Could not write gedit state file: Failed to create file '/root/.gnome2/gedit-2.6C18MU': No such file or directory
I/O error : No such file or directory
I/O error : No such file or directory
I have Intrepid and not Gusty/Hardy or Dapper.
Download and install the ADB utility from here (DONE)
Plug your phone into your computer (DONE)
Also when I try excuting the ADB file, I get the following error.
Code:
[email protected]:~$ /home/lukehluke/Desktop/adb/adb.exe forward tcp:1080 tcp:1080
run-detectors: unable to find an interpreter for
/home/lukehluke/Desktop/adb/adb.exe
Not sure about the first error. You might want to retry editing the rules file using nano or vim or emacs.
As for the second, you seem to have installed the windows version of the sdk or your path is point to the windows binaries.
Sounds like you don't have a /root directory? I've never seen that error before. If you want to use gedit, create the file in your home directory, then sudo mv it to /etc/udev/rules.d
As for the second, you need to install the android sdk for linux. The code is available from here: http://code.google.com/android/download.html
There may be a deb for ubuntu somewhere if you google. I just compiled it. The SDK contains the adb utility.
Lukehluke said:
Code:
[email protected]:~$ /home/lukehluke/Desktop/adb/adb.exe forward tcp:1080 tcp:1080
run-detectors: unable to find an interpreter for
/home/lukehluke/Desktop/adb/adb.exe
Click to expand...
Click to collapse
WTF? Can adb.exe be executed on Linux??
You'll enjoy a lot more success if you stop trying to run executables compiled for Windows in Linux
Do you need USB 2.0 for the tethering to work, or even just adb & mounting the G1 as a storage device? On my one laptop (w/ USB 2.0) I can adb into it fine, I have Ubuntu 8.10 and I never had to install any drivers (not manually at least), I never tried the tethering because I just do it through wireless using iptables -- if I ever need it.
The problem is with an older Toshiba laptop that has no NIC or wireless, I could get a dongle but I wanted to try changing the system wide proxy to go to the G1 once its plugged in -- make this into like my car PC or something. I only have a basic command line install of Ubuntu 8.10 right now but it won't even allow me to mount it as a drive. I see /dev/sdb get added when I plug it in, but not sdb1 for the actual data so I can't mount it (tried formatting as FAT32 & 16). (Note: I had this working fine with a basic flash drive -- thats how I got adb on there to check for devices - which didn't find anything either. Also I had it working with some belkin wifi usb a few months ago). Now that I think about it I didn't try it with just a regular USB cable to see if at least the mounting works, even though I def need the data cable for the tethering. So does it have to be USB 2.0? Also do I need the drivers just to adb or mount it (I'm pretty sure the driver is just for the actual tethering though)?
Thanks in advance for any help.
cl0s said:
Do you need USB 2.0 for the tethering to work, or even just adb & mounting the G1 as a storage device? On my one laptop (w/ USB 2.0) I can adb into it fine, I have Ubuntu 8.10 and I never had to install any drivers (not manually at least), I never tried the tethering because I just do it through wireless using iptables -- if I ever need it.
The problem is with an older Toshiba laptop that has no NIC or wireless, I could get a dongle but I wanted to try changing the system wide proxy to go to the G1 once its plugged in -- make this into like my car PC or something. I only have a basic command line install of Ubuntu 8.10 right now but it won't even allow me to mount it as a drive. I see /dev/sdb get added when I plug it in, but not sdb1 for the actual data so I can't mount it (tried formatting as FAT32 & 16). (Note: I had this working fine with a basic flash drive -- thats how I got adb on there to check for devices - which didn't find anything either. Also I had it working with some belkin wifi usb a few months ago). Now that I think about it I didn't try it with just a regular USB cable to see if at least the mounting works, even though I def need the data cable for the tethering. So does it have to be USB 2.0? Also do I need the drivers just to adb or mount it (I'm pretty sure the driver is just for the actual tethering though)?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try mounting /dev/sdb? It sounds like your sdcard has a raw fat filesystem, instead of having a partition formatted with fat. Also, you have to click "mount" in the usb notification thing that comes up on your phone after you plug it in.
JesusFreke said:
Did you try mounting /dev/sdb? It sounds like your sdcard has a raw fat filesystem, instead of having a partition formatted with fat. Also, you have to click "mount" in the usb notification thing that comes up on your phone after you plug it in.
Click to expand...
Click to collapse
I did mount it on the actual device. Also I tried formatting it twice with gParted, both times with the full disk as the partition, once as fat32 and second time fat16. When I tried to mount /dev/sdb all that came up was something about couldn't find the partitions and it echo'd out the error a couple of times before it stopped, I forget the exact error but I'll check when I get home. I tried to mount it both as dos and vfat, no luck on the Toshiba, doing it on my Vaio though it was fine, both command line and just letting Gnome pick it up.
Also on the Vaio as soon as I plug it in I get /dev/sdb and /dev/sdb1, but not on the Toshiba. The Vaio has Ubuntu Desktop Edition while the Toshiba has minimum command line install, but I believe it shouldn't need anything special to mount the fat16 drive.
I'll try with a regular USB cable and making sure I have whatever dependencies to read Windows partitions when I get home later on and see if that does anything different. Thanks anyway.
I'm not sure why you would even try to format the USB drive. Not useful.
When you plug in the device, you should see a device appear but that is not the sdcard. That will not be visible until you select the notification which appears on the device and choose to mount the drive. At this point, the sdcard will appear in dmesg and can be mounted from Linux.
For adb purposes (which is for tethering), you first need to get adb working right. The absolute first step there is to get the window version of adb away, away, away- GONE!- and make sure you have the linux verison installed. Next you need to create the udev rules. If you use any text editor, create a file in /tmp called 50-android.rules containing one line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and save it. The sudo mv that file to /etc/udev/rules.d, you should be good to go. I would restart udevd just for grins (sudo /etc/init.d/udev restart), then plug in your phone again and see what adb devices gives you, taking great care to use the linux version of adb.
DebauchedSloth said:
I'm not sure why you would even try to format the USB drive. Not useful.
When you plug in the device, you should see a device appear but that is not the sdcard. That will not be visible until you select the notification which appears on the device and choose to mount the drive. At this point, the sdcard will appear in dmesg and can be mounted from Linux.
For adb purposes (which is for tethering), you first need to get adb working right. The absolute first step there is to get the window version of adb away, away, away- GONE!- and make sure you have the linux verison installed. Next you need to create the udev rules. If you use any text editor, create a file in /tmp called 50-android.rules containing one line:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
and save it. The sudo mv that file to /etc/udev/rules.d, you should be good to go. I would restart udevd just for grins (sudo /etc/init.d/udev restart), then plug in your phone again and see what adb devices gives you, taking great care to use the linux version of adb.
Click to expand...
Click to collapse
Haha, trust me I have no Windows anything on any of my machines. I was planning on putting fluxbox or icewm on this so I can have rhythmbox, totem, browser, pyroute - some big icons with the windows set to open full screen so i can use in my car and script it to mount the drive for the music or movies and start tethering and possibly create something to pass over the gps info for navigation when plugged in. If I get it to work with this older/slower laptop I can then def recreate it or something later on with like a mini-itx/atom based pc and a small touchscreen or something (even though in that case I might be better off just putting Android on it). Really just to **** around ya know..
I was formatting just trying to get mounting to work, I def made sure to enable the mounting on the G1 before I tried it but it just wouldn't mount, "adb devices" wouldn't find anything, but you're right about dmesg echoing stuff, but it was errors, as soon as I clicked mount on the G1. I'll try creating that file like suggested and a few other things.
I'll return with more specifics on the errors when I try this out. Thanks for all the help though.
cl0s said:
Haha, trust me I have no Windows anything on any of my machines. I was planning on putting fluxbox or icewm on this so I can have rhythmbox, totem, browser, pyroute - some big icons with the windows set to open full screen so i can use in my car and script it to mount the drive for the music or movies and start tethering and possibly create something to pass over the gps info for navigation when plugged in. If I get it to work with this older/slower laptop I can then def recreate it or something later on with like a mini-itx/atom based pc and a small touchscreen or something (even though in that case I might be better off just putting Android on it). Really just to **** around ya know..
I was formatting just trying to get mounting to work, I def made sure to enable the mounting on the G1 before I tried it but it just wouldn't mount, "adb devices" wouldn't find anything, but you're right about dmesg echoing stuff, but it was errors, as soon as I clicked mount on the G1. I'll try creating that file like suggested and a few other things.
I'll return with more specifics on the errors when I try this out. Thanks for all the help though.
Click to expand...
Click to collapse
I just set this up on my vmplayer running ubuntu, I can use adb shell so the tetherbot app should work..
Related
Trying to do some push/pull and do the new lag fix to no avail. After adb devices, the phone shows up as attached, but after adb remount I get "remount failed: No such file or directory" I'm not able to execute a push or pull command, and therefore I'm not able to run the lag fix.
I have USB Debugging selected, and I was able to delete the bloatware via adb shell, but none of the other commands go through for me...
Which version of Windows are you running?
Windows 7 64 bit
Still haven't found a fix to this, so I'll post up what I'm inputting and what I'm getting in return.
Here is the code I use to get into ADB and then attempt a remount:
Code:
cd C:\android-sdk-windows
cd tools
adb remount
remount failed: No such file or directory
When I try to push and/or pull, I get this:
Code:
adb push ./smoothcalendar.apk /system/app
failed to copy './smoothcalendar.apk' to '/system/app/smoothcalendar.apk': Permission denied
I've tried adb kill-server, then adb remount with the same issues.
currently experiencing the same problem...
Do you have BusyBox Installer installed on your phone? I believe you have to have it installed in order to use Android SDK.
I've got Busybox 1.17.1 on mine.
I'm wondering, is this a problem at the computer level or at the phone level? I know the Vibrant had some issues with push/pull, but I see some stuff here in the dev thread (lagfixes, sideloader stuff) that if I run from my computer attempt push/pull commands that fail and therefore the thing I'm running (lagfix most recently) doesn't actually work and I'm stuck with a slower phone.
If its a phone issues, I can just exchange it under warranty, since I'm out of my 30 days. But I'm hoping it's not as I'd like to keep this one that other than this has worked great for me.
When I first starting using ADB, I was connecting my phone like when I was using Windows Explorer to muck around on it. I had mounted the usb connection in the notification window. I kept getting errors when I tried to push/pull. I reconnected once and forgot to mount the usb connection and everything worked perfectly. Make sure the usb debugging is check marked in Applications in settings. Try to do the push/pull without using remount command and don't click on the USB connected notification option when you plug it in. I'm really new at this linux stuff so I could be wrong. I'm just trying to share my experience in hopes that maybe you're doing the same things I was doing before I stumbled onto the right way to do it.
Hmm, odd, I've tried that very method many times before, to no avail.
I try it just now, and having no problems with push or pull. Works for me! Thanks!
Anybody have one of these? I recently got my hand on one, and the estation c1650 printer also, and wondering if there is anybody else with on, would like root, and or wipe the device and get ride of the stupid hp touchsmart UI. it would be a dream to run a galaxy tab rom or something. I though i saw a galaxy tab floating around? a system dump maybe? But any help would be appreciated.
HP Zeen
OK, I managed to use the latest Android (2.3) SDK usb drivers to get the windows to recognize the device. I could copy files to/from the SD card.
USB\VID_03F0&PID_9F11&REV_0223&MI_01
USB\VID_03F0&PID_9F11&MI_01
To get it to work, I had to edit the inf file at location:
"[SDK PATH]\google-usb_driver\android_winusb.inf" and add the following information:
;FOR ZEEN
%SingleAdbInterface% = USB_Install, USB\VID_03F0&PID_9F11&REV_0223&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_03F0&PID_9F11&MI_01
ADB currently will not recognize the device. I'm not sure what's messed up. Calling HP now to see about proper USB drivers.
Zeen
OK, HP says the USB drivers for the zeen come with the printer and even though I plugged in the first time it didn't work, the second time it did and Win 7 recognized it as a HP zeen. Ran the disk install in between.
That said ADB still has no idea. Fresh eclipse SDK install. Any thoughts on how to get ADB to recognize it?
Let's keep this thread alive. I got the drivers installed with your help. Can't get adb to see mine either. There has to be something we are missing. I think this device is similar to the pandigital novel so I have been reading over there. I will keep working.
Apparently, some firmwares seem to disable "adb" service...
Nice to hear someone else is out there trying. I found the following in a different post about the galaxy s, tried it with the Z4root, and while the command seems to take, it didn't work to get ADB. I tried it on a couple of different machines, let me know if it works for you. Also, when I called HP about the drivers they (at least the support techs) didn't know squat about android. Not helpful.
"Apparently, some firmwares seem to disable "adb" service on the Galaxy S.
So in case you run into this problem (adb unable to see the device) what you will need is to modify /default.prop on the SGS.
Here is what I had originally:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.debuggable=0
persist.service.adb.enable=0
To enable ADB on SGS
1. Run on the device: setprop persist.service.adb.enable 1 to temporarily switch it on.
2. pull /default.props with adb and modify the "ro.secure=0" and "persist.service.adb.enable=1"
2. mount -o remount,rw rootfs /
3. push modified default.props back to /
In more detail:
1. Root your device (see FAQ sticky post)
2. Install shell emulator on the device
3. In shell emulator, enable ADB (not sure if you need to run "su" before that):
setprop persist.service.adb.enable 1
4. Now, you should be able to connect to the device with ADB (temporarily). If not, make sure your udev rules (for Linux: /etc/udev/rules.d/51-android.rules) are smth like:
SUBSYSTEM=="usb|usb_device", ATTRS{idVendor}=="04e8", MODE="0666"
5. To make the change permanent:
adb pull /default.props .
(this will copy default props to local directory)
6. Modify the two properties as follows:
ro.secure=0
persist.service.adb.enable=1
7. Re-mount the root filesystem on the device in read-write mode (requires "su" before that):
mount -o remount,rw rootfs /
8. Now overwrite the /default.props on the device with modified one:
adb push default.props /default.props"
Okay, z4root did give me root access. I installed root explorer and terminal emulator. I am trying to find adb wireless so I can see if we can adb into the device using that. I think if I can i can install the market on the zeen
RootExplorer
Got a link to the RootExplorer APK? When temporarily rooted, I tried to install the market APK and got the finger. Did you perma-root or just do temporary?
I don't know anything about wireless ADB. What's the story with that? (admittedly, I'm a developer but getting up to speed on hacking the thing open).
I dont think I am aloud to post the root explorer apk. Wireless adb is just supposed to let you use adb without plugging anything in. Unfortunately, it says my device isnt rooted when trying to run it. Im gonna keep playing around with it.
Hey can you try to run adb over wifi. Just hook up your zeen to wifi and your pc and run adb like normal, but when you first run it type "adb connect xxx.xxx.xxx:5554
replace xxx with your zeen ip address. See if it lets you connect like that.
all the zeen but the adb drivers are in the zeen itself your just useing and uncapatable cable so it wont install usb driver and masstorage ones with out the proper cable, the adb drivers you will only get when useing sdk tool and has to be in debuging mode and pluse it has to have the correct cords like useing a samsung usb with a motorolla usb and sry i faild english and hate typeing so to lazy to do spell check like any one else will u get my giff the adb driver will install same time sdk will just its kinda tricky getting access to them and makething them work, a good way to test is plug in your w.e droid and go to your cpu cmd window, and type adb shell if it finds you droid then your golden but if not then bad cable or not in debuggin mode and have to have sdk installed and packages installed that come with it....
untile you can take the h p block of the android makret it wil never install or wont install properly more or less a complete rom will come out in like 3-5 months with the market on it and idk if the printing app will still be there but trust me you wont get it but there are 3 other alterative markets out there and 4shared.com has not let no one down............
if you want the android market on the hp tablet for the zeen or any other tablet that people are haveing a problem get anything and don't like yam or black market or any of that b.s g0od t0 4shared.kom and download a apk file with the name applanet and you should install the version 2.7.3 and i tried all the other version some will install and some wont but so far this one install and has 92 percent of the real adroid market and looks just like the market i found everything from root explorer to romanger and every app i seen in my droid i found on there and updates trust me if you want a g0od makret, well i just gave you the answer, n0w s0me one make 2.2 work on this thing, i have one to donate, [email protected] for some work to be done
Thanks for the tip on the Android Market! I installed it on mine and it works
How did you install market?
Sent from my Desire HD using XDA App
Anyone still working on the some development for this device? Thanks in advance!
There are various threads around xda with people trying bits and pieces. Slow progress though!
Okay thanks.
anthonbob said:
Anyone still working on the some development for this device? Thanks in advance!
Click to expand...
Click to collapse
Yes I will continue development after my exam will open in August an development thread to collect the knowledge of developers and not to sit weeks trying to get some information about the device and try to get adb working on Linux like I did
Gesendet von meinem Skate mit Tapatalk 4 Beta
Ok I think im going crazy, I cant find anything about this.
Im trying to access my tab via ADB in OSX. My Evo works just fine, but I just cant find the gtablet. I see in Windows driver's ini has to be modded to include tegra device ID and vendor ID, but I dont see anything for osx and my device is not getting recognized!
Thanks for your help!
Click to expand...
Click to collapse
Ok so after some time, I just found the solution, I dont know why I need it, and some people didnt but anyway, for whoever is having the same problem as I did, this is the solution!
This steps are assuming you have ADB ready and installed!
First, open terminal (/Applications/Utilities/Terminal.app)
Run the command:
Code:
android update adb
Then you will get a adb_usb.ini file in your $HOME/.android directory. Open that file and you will have the following..
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
Add in the 4rth line the following (Device vendor code, this case NVIDIA 0x0955):
Code:
0x0955
Save the file and exit.
On terminal window type
Code:
adb kill-server
and then
Code:
adb start-server
Adb devices should now show up your device!, if by any reason you get "device offline" a re-plug fixed it!
thanks!
damn! bumping this thread, really nothing? I just want to know if anyone can ADB with osx??? Its just me? or what?! thanks
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Linuxslate said:
Works fine for me.
OSX is the only OS I've used (so far) to connect to my G-Tablet via ADB.
Make sure USB Debugging is on on the 'pad, and it's Plug and Play. No udev stuff like on Linux, no USB driver issues like on Winhose.
I have had troubles in the past connecting through USB hubs. I'm currently using the front connectors on a Mac Pro.
Just another trivia note on the subject:
adb remount
Works for me on ZPad, it does not on TnT Lite.
Click to expand...
Click to collapse
Thanks for your reply, so...TnT Lite doesnt work for you?..mh that may be. I have not tried Zpad!
Will keep trying!
roebeet said:
I have a hackintosh netbook, but I don't really use it in this space. Nor Windows. Sorry about that.
Click to expand...
Click to collapse
no worries! Thanks for the reply man!
Fix posted on OP!
UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/
well I see you fixed it. did you get adb going?
Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.
Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone
I have a B90 TF101 and I am able to get into recovery mode. I have no ROM on my internal SD card and have wiped and formatted everything. I have read that it is possible to push a file using ADB while in recovery.
However I am not able to see my device when I use the adb devices command. I noticed that the drivers for the transformer are not installed. So I tried to install them and it tells me that windows can't install. I am pointing the installer to the MTP devices driver folder.
How do I get the drivers to work so I can use ADB or can I set up ADB in Linux and not have to worry about the drivers?
edit: I forgot to mention I am running windows vista.
Hi! Search in transformer's support page, you can find the drivers there
Are you saying that the drivers in the MTP folder are not the right ones? I got them right from Asus' website. Which drivers should I be using?
Ageesaman, did you ever get the drivers working? I had the exact same problem (got adb working as far as listing devices, but then it returned with a blank line after "adb devices" in cmd window). I downloaded the ASUS site's USB drivers download as well as every other utility from that site; I also tried external sources; finally, I tried manually updating by pointing to the unzipped MTP folder - nothing worked. I used both 64 and 32 bit Windows 7 machines. I am stuck in the cwm recovery loop so I can't do much troubleshooting. I tried searching dozens of sites for several hours but came up short.
Thanks in advance for any help offered.
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Ageesaman,
Unfortunately I know nothing about Linux, but what finally got it working for me was starting the installation of PDANet for Android. I saw it look for and install the driver, then I got a ADB confirmation. I then canceled the PDANet install. If you decide to go this route and get error messages in the cmd window, retry "adb devices" up to 3 times. In the meantime, I hope you get your Linux answer. Good luck.
I will give that a try. Is PDAnet something from Asus? I will do a search and see if I can find it.
ageesaman said:
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Click to expand...
Click to collapse
Yes, I can confirm the TF101 works with ADB without drivers on Ubuntu linux [I am on 11.04]. The current [stable, with 12.04 betas] Ubuntu version is 11.10, and you can download it to a live CD and run it off the CD without installing it.
I just got my tf101 the other day and I tried using adb [and older version], and it did not show up. Then I downloaded the tf101 root.zip file, and tried the adb within that folder, and it worked.
I've uploaded it to mediafire:
adb-1.0.29 http://www.mediafire.com/?hqwxbljs2gbpfxe
md5 64c4afbab6d2f769ddbb229f0247cf8a
update: newest adb is 1.0.31 http://www.mediafire.com/download.php?vcvc4dxkdd57695
md5 ed5c8f9a221cae0cb24d6cdc8b76d396
download, and run
chmod +x ./adb-1.0.29
to make it executable
That worked! I can now connect to my device with ADB. Thanks for that pdanet advice.
Now I just need to figure out how to push the file. Can't seem to get it to work. Here is what I am typing in the cmd line.
adb push rom.zip /sdcard
The rom I am trying to push is in the Platform tools folder that I am using to access adb. Does anybody know what I am doing wrong? Any help would be awesome.
is the rom.zip in the same directory as you are in (cd <path>)?
What does it say when you try to transfer it?
You can also try to push it to the full path (/mnt/sdcard/)
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
ageesaman said:
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
Click to expand...
Click to collapse
It's probably because /sdcard is a soft link to /mnt/sdcard/
if you did /sdcard/, I think it should probably work.
You sir are the man! Thanks for your time.
To get the process all in the same place for anyone else who may need this here you go. Just to make it clear.... This is what I did on my device and it worked. It may or may not work for you but maybe it's worth a try.
1. Downloaded SDK and Java JDK.
2. Used PDAnet to force windows to install the correct ADB device drivers.
3. When the drivers where installed and ADB was working I used this command to push the .zip file to the internal sd card.
adb push rom.zip /sdcard/
Just a few notes for this.
ADB was not working well at first because I had Asus sync running in the background. Make sure this is off.
Also make sure you put the file you are trying to push in the same directory you are using for ADB. For instance I used C:/android-sdk/platform-tools/ to access ADB so the file had to be in that folder in windows explorer.
To make it easier to type (I had to do this a lot while troubleshooting) I changed the name of the rom I was trying to push to rom.zip. This made typos less of an issue.
Make sure that you put the file extension (.zip in my case) in the ADB command even if it doesn't say it when you look at the file in windows explorer.
I think that is it in a nutshell. I hope this helps anyone else who needs to push a rom.
Good Luck
This method in this post didn't work for me, but this one did: http://forum.xda-developers.com/showthread.php?t=1689193
I set Windows to look for driver in c:. After a while one was installed and worked.
What I did on windows 7
Go to Device manager
Find transformer , right click on faulty marked unit.
Select properties
go to tab driver
update driver
Select browse
select path to the subfolder ANDROID ( containing usb drivers from asus )
include subfolders
Windows will find to alternatives , choose xxxx ADB
Windows will complain, ignore
done
/Claes R
W