Related
Trying to run ADB from a Win 7 x64 system to push items to my Xoom 3G. ADB Devices shows nothing yet I'm able to see files and folders on my Xoom. Any help in what driver I need to install in order to be able to take advantage of ADB would be most helpful as I'd like to root my tablet.
Is USB debugging enabled? If not, that's the issue.
Sent from Desire HD or Inspire 4G or whatever this thing is called via premium XDA app.
Already checked that. Not the issue.
Install the Moto Helper from here:
Link
Once installed plug in the device and it should install the required drivers.
If you have already done this then look for a Motorola folder in your START menu. There you should see a "Mobile Drivers" folder and in that folder a "Motorola Driver Installer" Executable.
Run the executable and tell it to "update". If that doesn't work try selecting "reinstall"
Running Update worked. FYI, the current version doesn't have a "reinstall option."
trouble with adb
I am not hay luck running ADB. It worked several months ago but I'm not sure why it doesn't now and I forgot what I did way back when
When I connect the USB to my PC (Win7), the XOOM mounts and I can see the files, etc., but when trying ADB it says "error: device offline."
I know on my EVO, I have to set the phone to charge only; is that the case here as well?
Any suggestions?
Hello,
Firstly, this is a long explanation, so, for the lazy, I have put a TL;DR version at the bottom of the post. Scroll there to get the general idea.
I have attempted to root my Transformer numerous times now. It is a serial number B60.
I am running Windows XP, so I am trying to use Brk's script.
I am using v6.3.1 of the script, because I have the latest OTA update.
This is my 'Build number' in 'About tablet': HTJ85B.US_epad-8.6.5.9-20110816
I have been trying this method since 8.6.5.6 and at the time I used v6.1 of the script (other methods including a VirtualBox run of rebound's One-Click Universal root linux live-CD).
When I run the script, I follow the instructions exactly.
I backup (option 1), then reboot into APK mode again.
Then, I flash unsecure boot.img (option 4) and CWM. I have tried only installing unsecure boot.img and it has made no difference.
Flashing the unsecure boot.img reports success and flashing CWM reports success.
Next, I reboot into regular Android OS.
Development mode is on for the USB. I check to see if ADB is working (option 7).
ADB is not working. The reason? I do not have root. I have installed the Terminal Emulator application. When I run the command 'su', it says 'Permission denied'.
I have also tried the Transformer pure root tw/us/ww/de/jp (8.4.4.5/11/12/8.6.5.6/7/9) and it has the same results. That is, flashing unsecure boot reports success, as does flashing CWM, but I have no root.
Additionally, I tried a VirtualBox run of rebound's One-Click Universal root linux live-CD. That failed, because I couldn't capture the Transformer as a USB device).
TL;DR version
I have tried several different methods of rooting my Transformer. It is serial #: B60 series running HTJ85B.US_epad-8.6.5.9-20110816.
All drivers are set up completely.
All steps are followed
All steps report success
Root is not granted
ADB will not work
???
More details at the top
One last thing
The only thing that I can think may possibly explain this problem is that I do not have an SD card in the tablet. I know some guides specify that you need one and other ones do not say anything.
I do not think that this is the cause, chiefly because everything reports 'success'.
Are these results typical of what happens when someone tries to flash a B70 or B80 model? If so, is it possible that, although I have a B60 series model, the innards are that of the B70/80 series and thus, incompatible?
I hope that posting my results and problems will help solve someone else's problem at the very least.
At this point, even someone just replying and letting me know that I have done everything correctly would be nice.
Have you got the ASUS drivers installed in your pc? i.e. can you connect and sync your device normally?
Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?
Success!
AustinMartin said:
Here's a hint from the BRK thread:
Found the problem. I didn't install the ASUS PC Suite, just the drivers. Found a hint in another post that PC Suite seems to contain something in addition to the driver which is needed for ADB connections. No idea what it is, the device manager entries still look same...
so did you install the ASUS PC Suite as well as the drivers?
Click to expand...
Click to collapse
Wow! I feel like a complete idiot...
I downloaded and installed the "Asus Eee PAD Transformer TF101 USB Driver" which I thought was what the PC Suite was. I was wrong.
Everything is working after installing the PC Suite and then trying ADB.
I definitely wrote way too much...
telekenetix said:
I definitely wrote way too much...
Click to expand...
Click to collapse
But that is how we learn, from seeing what others have done...
did you enable development ? it is for adb
I found that out early on that the PC Sync app is essentially just a front-end for ADB, since the app wouldn't work when I had debugging enabled on the TF.
mashi said:
did you enable development ? it is for adb
Click to expand...
Click to collapse
Yes. The trouble was that the PC Suite wasn't installed. I thought I had it installed, but it turned out that I only installed the drivers. Everything is running smoothly now.
The thing that still seems odd to me is that I tested to see if I had root, using the terminal application. It said "Permission denied". But, after installing the PC suite, adb was able to function and apparently did something magical.
So, I have to ask. What is this black magic?!
http://org.downloadcenter.samsung.c...113815/T-Mobile_T769_Blaze_4G_USB_Drivers.exe
22.8MB file installing slowly?
First off, I apologize for being paranoid. I downloaded this file and started installing it. It's a 22.8 MB .exe file. I started installing, and it *seems* to be working correctly. After clicking install MSS Installation Wizard is installing Samsung USB Driver for Mobile Phones V1.3.2200.0. Slightly after, desktop toolbar icon popped up Installing device driver software, opened it up showing:
USB Composite Device Ready to use
USB Mass Storage Ready to use
CDC Cerial Waiting for user input
Samsung LTE USB Device Ready to use
Samsung LTE Card USB Device Ready to use
It's been like 10-15 minutes and the MSS Installation Wizard is chugging along, at about 50%. Is this file legit? Is it just my slow ass computer that is making this install take forever? Have other successfully installed this for ADB usage?
Looks to just be the link to Samsung, which yes I have installed. It was a bit slow on my netbook.
Sent from my SGH-T769 using Tapatalk 2
Same here. I installed it yesterday while working on my wife's phone (Blaze also). The first time I tried to install it on my desktop it was slow and there was some sort of error. I had to reboot and redo it before I got it properly installed.
I've never needed the drivers, just downloaded kies.
Sent from my SGH-T769 using XDA
Kies I think installs the drivers for you. You can't properly use the device without the drivers and you definitely cannot use some of the tools without them.
No ADB
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Does anyone know how to get this device working with adb on Debian? I can't for the life of me get the device recognized by adb. I have a 51-android.rules set up and all that jazz. udev sees it and rules are applied properly. I just can't get it recognized. It seems references to accessing this device from Linux are very few and far between. What gives?
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
strungoutfan78 said:
Well in case anyone is interested I found the solution while searching elsewhere. It seems it's a permission problem. If I run a:
sudo adb kill-server
Then:
sudo adb start-server
The device is then recognized. Hope maybe this helps someone else.
Sent from a magical unicorn using CM10
Click to expand...
Click to collapse
Can you explain this a bit more, like where to input these commands. Im a bit green and having this issue.
---------- Post added at 01:25 AM ---------- Previous post was at 01:04 AM ----------
theshowman said:
hi guys
I'm trying to getting ADB going on the T-Mobile BLAZE 4G (T769), but I don't seem to be able to have adb recognize the device.
I've installed the Samsung drivers (linked here) and it installs a bunch of devices.
But, adb devices returns nothing.
Any idea whether I've missed anything?
I'm not new to adb or Android (have done it on over 10 devices), but I just can't to get it going on the Blaze.
FYI, as part of unlocking the devices, I had to enter menus via 7284 and 9090 on the keypad and enable a bunch of usb diag/modem stuff. Could this have anything to do with it?
** UPDATE **
I just used *#7284# and changed back the USB->Modem to USB->PDA and now ADB works.
Click to expand...
Click to collapse
I tried the #7284# and #9090# and got "unable to process request"
any other suggestions?
Hey everyone,
I've read through the All-In-One guide about how to root the TF700T, downloaded the driver pack, put it into developer mode and enabled unknown sources. When I plugged the device into my computer it was immediately recognized and automatically installed the drivers and I can see it through Windows Explorer and browse the file system.
Unfortunately the device doesn't show in adb and I read through this quote in the guide, "if not, install the ADB drivers from Windows Device Manager (if you don't know how to do it then you better stay off from rooting your device)" so I went to the Device Driver and and tried to update the driver with the ADB driver, however, it says it's not compatible.
On the Android device I see the USB mode as Media Device (MTP) and that USB Debugging Connected
In Windows Device manager I see under "Portable Devices" the "ASUS Transformer Pad TF700T" is there and installed without error.
There aren't any device drivers that have a yellow icon indicating they aren't configured correctly.
I had purchased the tablet a few days back and it prompted me for a system update which I did.
I've tried rebooting both my computer and the tablet but it didn't appear to assist.
I'm assuming I'm doing something silly and simple but I cannot for the life of me figure it out.
Does anyone have any suggestions on what I may be doing wrong?
Thanks in advance everyone,
Septurious
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Thanks!
Nebucatnetzer said:
Search for universal adb drivers in Google. It should lead you to a thread on XDA in the TF101 section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Glad I could help.
Excuse me that I didn't post the link directly it's a pain on the phone.
I had a similar problem. The TF700 was automatically found, and no ADB drivers were installed. I kept trying to uninstall the driver, but it wouldnt let me. I don't have an option to "delete drivers" on uninstall.
When I tried installing "legacy hardware" to force the drivers, it would come up listed under "Samsung" and not Asus. I think I have my drivers all screwed up from previous phones i've had. I took the driver set, and went to another PC (same os, Win 7 ult x64), and had no problem installing all the drivers and rooting.
Anyone have an idea for me? Not sure if I should start going through my sys32 and manually deleting all driver files associated with my tablet.
Fixed.
I had to do this.
http://www.thewindowsclub.com/how-to-remove-old-unused-device-drivers-in-windows-7
Went through and cleaned up all the old drivers, between the old Samsung Drivers, Motorola Drivers, previous Android ADB drivers. I now plugged in my TF700, and while the ADB shows up as a Samsung device, it shows up on "adb devices", which it didnt before.
Another solution
I tried all listed tips but failed.
ADB driver was installed automaticaly after enabling USB-modem on my TF700.
Now android device chooser showing device
for hours i tried it! no i know why it didnt work!
turn off windows firewall!!! DD maaaaaan
Septurious said:
Thanks for the info! I searched for "universal adb driver xda" in good ol Google and got to this post.
Downloaded the drivers and started to do the install process described in the post but when I did the "uninstall and delete" drivers deal and then replugged in the TF700T I quickly clicked on the "driver install" dialog in windows and told it NOT to search Windows Update which seemed to cause it to grab the adb drivers that I grabbed from the original post and voila it worked.
After running through the debugfs script and running the SuperUser program once I was rooted and finally got smartdimmer and remote management disabled.
Thanks so much for your reply, most appreciated!
Septurious
Click to expand...
Click to collapse
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
GBDias said:
>> I have the same problem and do the same thing, but windows didn't install drivers: its show a message indicating a problem with the hash of catalogue.
Anyone can help?
Click to expand...
Click to collapse
Windows 8?
Try disabling driver signature verification.
Sent from my DROID4 using Tapatalk
Has anyone figured out how to connect to their Note with ADB yet?
I turned on debugging but the darn thing still doesn't show up in the devices list.
For reference, I'm using the cable that came with the Note and I can transfer files successfully
Have you installed proper drivers or the Android SDK? If you get Android SDK for your pc, make sure open up the manager in there. Then download platform tools and tools. It should give you needed drivers and support for ADB & Fastboot(not sure if Samsung uses it).
Or you might be able to use Odin to do whatever you trying to do with ADB. Not sure though. Depends on what you trying to do.
demandarin said:
Have you installed proper drivers or the Android SDK? If you get Android SDK for your pc, make sure open up the manager in there. Then download platform tools and tools. It should give you needed drivers and support for ADB & Fastboot(not sure if Samsung uses it).
Or you might be able to use Odin to do whatever you trying to do with ADB. Not sure though. Depends on what you trying to do.
Click to expand...
Click to collapse
I'm trying to play with some app deving, I like the logcat tools Eclipse provides.
I'm also trying to play with sqlite,
I updated my SDK to have the ICS and JB API's, I didn't think that ADB would have been significantly different than the honeycomb one I was using with my GB phone. I'll give it another try when I get back to my office on Thursday. I figured either I was doing something wrong, or I had something wrong on my Note when my Prevail works.
Thanks for the help
Well, I updated everything, made sure I have the latest ADB executable and dll's and still can't get it to work.
I have no idea what I'm doing wrong.
I can connect to my phone just fine, pull logcats, install test builds of APKs with Eclipse, everything.
My Note just doesn't show in the device list. I've made sure that adbd is a running service on the Note. Should I be using a different cable from the one that came with the system?
In case it matters, the only things I've done are to install CWM recovery and rooted using this method: rootgalaxynote.com/galaxy-note-10-1-root/how-to-root-galaxy-note-10-1-easiest-methodcwmmethod-2/
Well, turns out I'm a complete idiot.
It helps to have the latest samsung drivers installed
I had given up on getting it to work, then installed Kies to do an update.....
once it installed new drivers, my Note suddenly started showing up in ADB's device list.
Here I thought I already had the latest drivers
I feel like such an idiot