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
Related
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..
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!
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
joevirus563 said:
Ok,
I'm not new here but Im new with a TF101...
I have 3 rooted devices at home.
Now when I plug the TF that I bought used, it dosent get detected. I mean at all!
Not "!" yellow in windows and nothing it linux, no noise nothing.
I have usb dev checked...
Now, do I need usb 3.0 to just get it detected and root it using xp or linux???
Click to expand...
Click to collapse
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
hapahopi said:
Go to Settings - Storage - USB computer connection - tick Media device (MTP)
Click to expand...
Click to collapse
Its already at MTP...
Any way to root without computer?
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Happydondavid said:
I've been having the exact same problem for a few months now , I reckon i either have a faulty usb cable or the port has been damaged . I hope there's a software fix for this .
Click to expand...
Click to collapse
Ok and whant have you done to fix it?
New usb cable?
I've not managed to fix it yet . When i plug my TF into my pc it seems to think its charging but the pc doesn't register it at all , if i get a new usb cable and it works i'll report back .
Well does anyone know if this is a problem with the cable or not ?
Happydondavid said:
Well does anyone know if this is a problem with the cable or not ?
Click to expand...
Click to collapse
I have the same problem. I sent my tf101 to the Asus service center to have it repaired. When it came back it would connect to the PC. After a few months it would not connect. Same problem. It appears to me to be software related somehow. In my case the cable has nothing to do with it. None of the suggestions on this or other forums work. Asus does not respond. Maybe Jelly Bean will fix it. Or maybe not.
are you able to ./adb connect to the asus via usb? if so then that will tell you that the problem is not the cable, it's not the usb version, it's not the device hardware. its likely a driver install issue in windows. i would boot into android and make sure that android debugging is selected in the developer settings menu. then try an adb connection. im not sure about how to install all the stupid drivers in windows because i do everything in linux and its soooooo much simpler.
f it is in fact the hardware cable or port that is not working properly then you can always move files to and from the device over wlan connection, with either adb tcp connection, or using some file manager such as es file explorer. just remember as long as you can get an
./adb connection to your android then anything is fixable. ADB IS YOUR FRIEND. get to know it well.
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
qandrav said:
same problem here...tried everything except format the pc (running windows 7)
I have a simple question for the people WITHOUT problem connecting tf101: when you connect the tablet (mtp or not) what do you see on the screen of the pc? something related to autoplay? Are you able to copy, move files to and from the tf101 like a usb stick?
Click to expand...
Click to collapse
I dont ever connect my devices as mass storage to he computers at all. i just do everything via ./adb usb or ./adb tcp connections over wifi. or i use es file explorer setup as an ftp server on my devices and move files around that way if i need to. but i went ahead and pulled out my windows asus tf101 drivers and sync app and linked them for you at the bottom. my advice really is to lose windows and stick with doing everything on android with linux. soooo much better.
https://www.box.com/s/q2j8n7h8xi5o3ld2bt5z
thank you for your long reply! and obv for the files, I'll give it a try!
I admit that sometimes I used swiftp (over wifi) but every time I have to disconnect pc & tablet from the modem...Sometimes use bluetooth but it's too too slow!!! thank you again!!!
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
when I rooted moths ago I used "razorclaw" (and my tf101 is a b70). I use adb with other devices and is very cool but I never need to use with the tf101...
joevirus563 said:
I understand but how do you root using adb tcp???
Envoyé depuis mon Transformer TF101 avec Tapatalk
Click to expand...
Click to collapse
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
The Real Question when USB does not connect.
haxin said:
ok so adb over a tcp connection it works pretty much like adb over usb except your connection is done over the network. so lets say your tf101 and your computer are both on the same WLAN. you can enable enable adb over tcp and connect to it with the computer over the network. however to enable adb tcp connections you need to already have root.
Click to expand...
Click to collapse
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
beware of usb cable
Hi,I personnally own a TF101 sb50.
I had some trouble with usb. Tha cable was ok for charging but didn t register correctly under an usb connection ( it showed up and got kicked out in windows didn t register in lsusb on linux)
If you check the diagram for the cable, it s well endowed there 's resistance inside the cable, and multiple connection.
Depending on your version it doesn t use the same pin, even if it's the same cable.
You can buy a cable on ebay for around 10 euro in europe ( i did it s ok) or buy it cheaper from china(no idea about quality).
to sum it up even if your cable work with another TF, it doesn t mean your cable is not faulty ( i have bounce a nano osci on the faulty cable , and it showed no apparent flaw.) and buying a new one was the solution for me.
good luck for rooting (sb50 :: no need to adb)
The ADB thru WiFi solution worked perfectly for me thankfully, and I am one of the many others who have been having major trouble getting Windows and Linux to recognize the Intercept.
Not sure if this is a duplicate post somewhere, but here's my version using Linux:
1. Go to the Play Store and download the 'ADB over Wifi Widget' app.
2. After installed on your device, the app should be on your home screen. Tap it once to toggle on. You should see an IP address and a port #.
Note the IP address, as this is the address of your device.
3. Open a terminal in Linux.
4. CD to the folder that contains your ADB files. (example: cd /androidsdk/platform-tools)
5. Enter the following code:
chmod 755 ./adb
./adb connect <enter IP address here without brackets of course>
6. You should now be connected to your phone.
Hope this helps...
pm124493 said:
I have both Linux and Windows systems. My TF101 does not connect on either machine. My assumption is I have a internal problem. I have tried two different cables and systems. I need to ROOT the TF101 and upgrade to Jelly Bean. From this post I am told to use ./adb commands over tcp and I appreciate that, but I need to have a rooted TF101.
The ultimate question is can I root the TF101 without using the usb connector? I suspect not, but will defer to the expert developers.
I have tried with settings in various selections like MTP "yes" or "no", Developer USB "yes" or "no" or both on or off at the same time. I have loaded and unloaded Windows Asus Sync and USB drivers many times.
The strange thing is if I am attached to the keyboard, I can see any USB thumb drives attached to the keyboard including my USB serial adapter. I would think USB would not work if the cable does not work. Also if anyone has a link to instructions for loading ADB on Linux Mint 13 64bit, I would appreciate the link.
Thank you in advance.
Click to expand...
Click to collapse
ok when you say that the tf101 doesnt connect in either your windows or linux machine, what do you mean exactly? you mean it doesnt show up as a mass storage device or an MTP device? and have you downloaded and installed the android-sdk in linux? and when you connect the tf101 to your linux machine, do yo uhave usb debugging enabled in the developer settings menu, and are you using the "./adb devices" command in the linux terminal from your /android-sdk/platform-tools/ directory?
also you should be able to flash a custom recovery which will enable you to flash custom rom without using the usb cable. theres a couple files that you need to put on your tf101 in the /sdcard/ directory first.
one is the recovery blob and if you want to keep the stock rom and kernel but just root it then youll need the superuser zip i have included both of them at the bottom.
for starters you need to install a terminal emulator app on the tf101 from the play store.
then once you have the recovery blob on your device in /sdcard/ you can continue. (remember /sdcard/ is the internal memory not the micro sd card)
start the terminal emulator on the tf101 and enter these commands.
mv /data/local/tmp /data/local/tmp.bak
exit
(open another terminal window on the tf101 and enter these commands)
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
(now reboot the tf101 when it boots into android start the terminal emulator app again then enter these comands)
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
exit
(now you should have a team rogue recovery flashed to your tf101)
reboot your tf101.
now you can hold the vol -down button while you power on the tf101 you will see a message at the top of the screen that says soomething like "Checking for RCK" when you see that press the vol- up button right away, this should boot you into the team rogue recovery where you can flash custom roms or just flash your superuser.zip to get root.
hopefully this makes sense and hopefully it works for you.
remember you have to extract the recoveryblob from the zip folder before you move it to the /sdcard/ on your asus. the superuser.zip can remain zipped though.
I had the same problem:
windows will not notice my transformer (rooted).
( usb debugging is on, android 4.0.3 with Android Revolution HD 3.5.1.)
i know in the past it works.
adb list ( of devices) ist empty also. Same Problem with the two cables i have.
can you give me a help what i can do?
Sorry for my poor english
kind regards
gandalf
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!
Hi, I've got an old S5 with a broken screen. There's no image going on and there's no indication that the touchscreen is working.
I'm not looking to recover data, I'm looking to play around with it by controlling it from my PC. Last I remember, the phone is running a Cyanogenmod OS (I don't think LineageOS was around at that time) with either TWRP or CWM recovery, but I'd bet on TWRP.
Now: the device reaches the OS properly, I can tell because if I try to turn the ringing sound up it gives me an audio feedback.
If I connect it to a PC from the OS:
- the phone shows up in Windows Explorer as "SM-G900F"
- Device Manager shows me a "SAMSUNG Mobile USB Composite Device" under Universal Serial Bus controllers
However I cannot access any files (Windows Explorer shows the device as empty), and if I attempt to 'adb devices' in the console it shows me an empty devices list.
Now, I suspect that USB debugging might be off. So I also tried connecting it to a PC from recovery and the exact same thing as above can be observed, PLUS:
- Device manager also shows me a "SAMSUNG Android Phone" list which can be expanded to show me one entry called "SAMSUNG Android ADB Interface"
However it's the same as before, no files available and 'adb devices' shows an empty list.
Now I heard that I can theoretically enable USB debugging through ADB, by writing to a config file. That would allow me to enable USB debugging and try something like Vysor in order to control the phone from my PC.
However that's a moot point until I can figure out why the ADB service on my PC isn't seeing the device. Any help would be greatly appreciated, and if you need more info I can provide it.
Extra info:
- I installed Samsung USB drivers at some point while trying to make it work
- Windows Explorer shows a phone icon for this device, and if I recall correctly that's what happens when it's connected through MTP (Mass Storage should show it like a memory card)
_sepiroth said:
Hi, I've got an old S5 with a broken screen..........
Click to expand...
Click to collapse
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Ibuprophen said:
I've never experienced this situation myself but, I've seen that the following thread has worked for many individuals.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Click to expand...
Click to collapse
Thanks a bunch, that pointed me in the right direction with my research! I solved my issue, I can now control my phone from my PC.
By doing this I ran into a couple of problems, I'm going to describe them and their solutions:
Problem 1: couldn't ADB into the device when in Recovery Mode. That is because after a long head scratching session I came to the conclusion that I didn't have TWRP Recovery installed (I had Philz Touch CWM Recovery and LineageOS 14.1 instead).
Solution 1: ADB mode is enabled in TWRP by default. So I flashed the latest TWRP through Odin, ADB instantly started working afterwards in Recovery Mode.
Problem 2: USB Debugging was disabled inside the OS.
Solution 2: from the thread that Ibuprophen posted, you can enable USB debugging in your OS by opening an ADB shell into your device and modify the build.prop like so
Code:
Adb shell
echo "persist.service.adb.enable=1" >>/system/build.prop
echo "persist.service.debuggable=1" >>/system/build.prop
echo "persist.sys.usb.config=mass_storage,adb" >>/system/build.prop
reboot
Problem 3: /system was empty so there was no build.prop. If I attempted to create a build.prop file it wouldn't be saved after a device reboot, so USB debugging still didn't work.
Solution 3: it seems like TWRP doesn't mount /system by default, only /data. You can mount it manually through ADB like this:
Code:
mount -o rw /dev/block/bootdevice/by-name/system /system
I found this out from this stackexchange question: https://android.stackexchange.com/q...data-partitions-in-recovery-mode-in-adb-shell
Problem 4: When an app tries to use USB Debugging you need to allow it to do so from the phone. Since the screen was broken, I couldn't do this.
Solution 4: You'll need to push a public key to your device with ADB. Boot into Recovery Mode and make sure your device is recognized by your PC and type
Code:
adb push <path to adbkey.pub on your PC> /data/misc/adb/adb_keys
This solution is from: https://stackoverflow.com/questions...b-rsa-key-with-broken-touch-screen-on-android
This will make sure that you won't need to confirm debugging permissions for apps coming from your machine.
So for anyone who has a broken phone screen (my screen is dead and touchscreen/touch buttons are kaput too) and wishes to control their phone from their PC but USB debugging is disabled:
1. Boot device in TWRP Recovery (flash it if you don't have it)
2. ADB into the device
3. Make sure /system is mounted (if it's empty it means it's not mounted), else mount it manually like in Solution 3
4. Configure build.prop to have USB Debugging enabled like in Solution 2
5. Push your public key to the device like in Solution 4
6. Restart the phone (into its OS)
7. Download the Chrome extension called Vysor and launch it
8. Connect your phone through a USB cable
9. The device should appear in Vysor, connect to it and have fun controlling it
Note that if you just want to backup your files, steps 1 + 2 are sufficient. After making sure ADB works you can just 'adb pull' all your files which should be located in /sdcard. Google it, it's easy to find.
The same goes for backups, you can do them directly through ADB.
Again, thanks Ibuprophen!
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
aIecxs said:
Vysor does not work on all graphic cards. a good free alternative is scrcpy
btw instead of flashing twrp, you can flash a modified system partition with proper entries in build.prop (for those with no custom recovery available)
Click to expand...
Click to collapse
Very well pointed out, thanks for this.