Related
I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?
Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim
Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?
More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!
Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.
Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device
I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.
I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.
One thing I forgot. Do not unplug your device between uninstall and hardware scanning.
AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim
Hi XDA
I am new to the Android scene but not new to hacking and moding in general. I have an Asus Transformer that I've been trying to root for over a day now with out success.
I've been following this guide since I don't want to remove the information from my tablet as I actually want to gain root to back up some applications before I continue further down the CWM and mod's path.
http://forum.xda-developers.com/showthread.php?t=1125714
I have adb setup and can access the device in apx mode, when running the batch script for root, the terminal shows that it's copying data, and I see output successful written twice on the tablet it's self, If i further continue the CWM batch script I get a 3rd successful message appear on the tablet.
I reboot the transformer and enter normal mode, and ensure debugging is actively set, and a little bumblebee icon is in the bottom status bar, I then proceed to run the root_app batch which should open up su for me.
However even though I don't receive any error messages and only successful ones, it just wont root! I've tried replacing the boot.img and recovery.img from another post on rooting, to see if this would give any success alas non was given.
I am now completely lost on what I can do next, I don't understand why this wont work for me, whilst it seems to work correctly for everyone else.
The details of the transformer as current:
Android 3.1
Kernel 2.6.36.3-00001-gf377a2b
Build hmj37.ww-epad-8.4.4.5-201105271
Dock EP101-0209
I am using windows 7 64 with drivers installed and asus sync installed.
Nvidia USB Boot-recovery driver for mobile devices
Date 31/01/2011
Version 1.1.1.0
Please can I get some direction from the XDA community on this issue since I've got over 20 tabs open in my browser looking information up and yet nothing seems to help, as stated I don't want to loose my data just yet since I really want to back up a couple of apps of importance to me, hence I am having to use this rooting method for now.
I would of posted in the above linked thread but XDA wont let me since I am a new member.
Please can someone shed some light on this for me? I am willing to rip out the boot.img from the transformer my self, and mod it given the commands and little help since I can't see what else I can do.
Bump
Can someone please move this to applicable transformer area? This thread is being viewed but not answered, and I think I need a dev to look at it
Is there anyone here who can confirm the drivers I am using for apx are ok? I did pull them from the package which is part of the guide I linked and was following.
More info
Well i've ensured that JDK and SDK are installed that all parts are updated and installed according to the adb guide, and yet still nothing...
.
Here is a sample output on the transformer after running root.bat
imageshack.us/photo/my-images/204/20110622112439.jpg
Restricting new users is actually pretty S**T i can't post in correct threads, I can't add links to images to show my outputs what a way to welcome new people!!
With regards to running the root_app.bat which gives the superuser permissions, I have debugging enabled, and I see my tablet in windows I can explore the file system and I see it listed as Transformer TF101 under portable devices.
Driver Provider Microsoft
Driver date: 21/06/2006
Driver Version 6.1.7600.16385
Could it be a problem with this driver?
Stop looking and start answering I am getting really F*** off here, I've had no sleep and i am still no further forward, 2days of hell for something that people are reporting as the fastest and easiest root ever!
What driver version do you have listed in windows when you have the tablet connected under debug mode? please at least someone help me with that answer so I can continue this dam search for a fix.
Anyone?
If you could please just confirm if your using the same drivers when having the tablet on in normal mode, and connected with debug option active.
Going to spam this now so I can link into the original guides tread.
Spam to unlock my account 1.
Spam to unlock my account 2.
Spam to unlock my account 3.
Spam to unlock my account 4. Should be unlocked so i can post in dev section.
FIXED!
Ok so i finally got pissed off with this and having a strong suspicion it was a driver level issue only I ripped all the drivers out for normal mode, with and with out debugging.
I re-installed the device and the drivers fresh from ASUS website (again) and low and behold it's working.
I believe the reason for my issue was a corrupt MTP driver, I recently did the asus sync update and that caused a number of sporadic errors! (Adobe AIR completely disappeared out my system!)
Anyway, thanks to the XDA community NOT (69 views not a single confirmation of driver version I was asking for!) I WILL help others and since I've spammed this thread enough to unlock the dev threads it's now being posted and linked there for the benefit of others!
3hours sleep 2 days of messing = pissed off but finally relived user of transformer!
Big shout to the dev's who have made the tools in the first place you're doing a great job, and I hope to assist, with guides, testing and maybe a mod or two.
Hi All,
I just tried to connect my TF101 to an old WinXP box and got the error above when installing the driver from the Asus site, the solution after looking here was to install the Microsoft User Mode Driver Framework for WinXP here. I think this fix applies to all android devices but I figured it was worth a post if it saves some TF users from a long search.
Thank you for this, helped me fix it after searching around for 2 hours!
thanks heaps
You are a legend. Samsung should put this on their site. I couldnt get my Samsung Galaxy S II to connect, installing the Framework and then uninstall and driver and plug phoneback in then worked.
WORKED LIKE A CHARM!!!
POST THIS IN SAMSUNG WEBSITE
This driver package solves the Error code 28
for MTP device as samgung, then it works in Kies.
Hey thanks for the info +1
Thanks it works
equal or better file already installed on this computer
I get the same INF error when I try to hook up my video camera. I tried to download the file but received a message stating that I already have an equal or better one already. Obviously that is not correct because it is not working.
I am lost and can no longer put my videos from Panasonic Mini DV on my computer.
Any chance anyone knows how I can fix this..thanks!!
Gigsee, what operating system are you experiencing this on?
The help above is specifically for WinXP, it *may* be applicable to Vista also but will certainly not apply for a Win7 box because the usb driver stack is totally different there.
You'll have to help me out by giving step by step instructions of what your clicking and what your seeing at the time to pinpoint your problem and please be very specific with the wording of any errors your seeing.
Reply with something like;
1- click start> settings > control panel > system.
2 - open device manager tab.
George
Hi George - Thank you for taking the time to try to help me. I have an HP that is running on Vista Home.
I have tried to add the video camera several ways. One way is to open Movie Maker and add video camera. I also just hook the video camera up to the computer. I've tried a USB cord and HP told me I needed an IEEE 1394 cord, but that made no difference. I've tried going through the control panel to cameras and adding a camera. No matter how I try, it always does the same thing:
1) I plug in the USB cord. I instantly get this message: USB Device Not Recognized.
2) Control Panel; Scanners & Cameras; Add Device
3) I am sent to the Welcome to the Scanner and Camera Installation Wizard
4) Next; I have the box asking me if I want to select the manufacturer from the list (only my old printer is on the list) or to select that I have the manufacturer's disk
5) Have Disk
6) Message says to the Insert manufactures installation disk, which I do. It asks me to copy manufacture's files from:
7) I hit browse and change drive to E (since that is my disk drive).
8) A list of 6 files come up. Acrobat Reader, DV Studio3, USBDriver, ArcSoft, G726, AUTORUN
9) The acrobat, dv studio, arc soft all upload correctly. When I hit the USB Driver, it takes me to another screen that says DRIVERS. At this point, the file name gets automatically filled in as "AUTORUN.INF" When I click "OPEN" I get AUTORUN.INF File not found. Check the file name and try again.
note: It used to be that when I hooked up the camera to the computer, It would automatically detect it and try to connect with it. It was then that I got the error above about "A Service Installation section in this INF is invalid." Now, it doesn't even let me get that far.
I hope I was descriptive enough..thanks so much for trying to help me!!
Patti
I had the same issue with ASUS Transformer Prime TF201 connecting to WinXPSP2. Solution worked immediately. Thanks to original poster.
confirmed fixed issue with samsung vibrant! thank you
Hi !
I've got a Samsung Galaxy S2 SGH i777. I've been trying to connect it to my laptop ( now xp sp3 ) for a few weeks now.
I've tried almost everything :
-updated sp2 to sp3
-uninstall and reinstall drivers manually
-tried suggestions from android and xp forums : tried every connection mode, every usb port, code error 28 suggestions, .Net framework update , updated windows media player "mode", and some others ... even trying this Microsoft User Mode Driver Framework.
But no success. I've always had this annoying " A service installation section in this INF is invalid " message.
Until yesterday when I found this site and followed divadrummer 5 steps :
fixya.com/support/t221754-service_installation_section_in_inf
( as a knew member I cannot post outside links for a while - so you need to supplement the above line with the usual "stuff" like "www"
I've found the "inf" file in the windows hidden system.
Hope I could help .
Thank you very much!
Galaxy SII - MTP INF Issues
This is the EXACT issue I've been having. I'm thrilled to see it on XDA since I know there's so many competent people out there just brimming with eagerness to help me figure this out. (Or at least you're borderline willing)
Device: Samsung Galaxy SII Sprint SPH-D710 (i think)
OS: ICS
Computer: Dell Latitude d610
OS: XP SP3
As you know I connect my phone to the computer, it recognizes new hardware and attempts to install it. The only way to get the computer to recognize the phone in My Computer is by connecting as a digital camera and even then the VAST majority of my files are unavailable.
1. I installed the link provided by the original poster.
2. I uninstalled my phone by the device manager and in fact by removing the samsung phone drivers that I had earlier installed.
3. I then plugged my phone back into the computer.
4. I installed the Samsung drivers again
5. I allowed the "found new hardware to run its course.
6. I receive the attached screen shot with the error stating "An error occurred during the installation of your device. The required section was not found in the INF.
I have tried to follow the instructions above and I think the User Mode stuff sounds promising.
Next I attempted another fix at the link below:
fixya.com/support/t221754-service_installation_section_in_inf
The link had the following instructions: (Thanks Divadrummer)
"If the player is showing up in your Windows' Device Manager under "portable devices" with a yellow "!":
1.) Right-click the yellow "!" and choose "update driver".
2.) When given the option to connect to Windows Update, choose "no, not this time" and click next.
3.) Choose "Install from a specific location (advanced)" and click next.
4.) Choose "Don't search. I will choose the driver to install" and click next.
5.) Click the "Have Disk" button. Browse to C:\Windows\inf and choose the file marked "wpdmtp.inf"
I can't believe the generic players have such crappy support when so many people have this problem! I think the Windows file problem might be caused by "compressing old files" when you do a disk cleanup."
After doing as advised I found no wpdmtp.inf file. SO... I did what any amateur computer guy would do. I googled the file and downloaded it directly. I placed in in my INF directory and then tried to do step 5. I still experience the same error.
Suggestions and inquiries are welcome and encouraged.
Thank you in advance.
thanks
bstdnator said:
Hi All,
I just tried to connect my TF101 to an old WinXP box and got the error above when installing the driver from the Asus site, the solution after looking here was to install the Microsoft User Mode Driver Framework for WinXP here. I think this fix applies to all android devices but I figured it was worth a post if it saves some TF users from a long search.
Click to expand...
Click to collapse
I wasted an entire day scouring for a solution and yours was it!! I owe you alot!! I registered just to thank YOU!!:good:
I had XP w/ Gnex JB 4.1.1 and all I was doing was hitting walls. I tried more crap than you can imagine! Installed every driver scheme ever mentioned, installed WMP11, Installed SDK Manager.................
What a freakin' nightmare.:crying: And then, your suggestion with the MS framework. Worked instantly!! THANKS A MILLION!!
All day I screwed with this when I had not a second to waste on something like this. Why oh Why do I dig my heels in!!?? At least it worked!!
Absolute legend!
I've spent 3 days mucking around trying to connect my Galaxy S3 to connect to my Windows XP pc to no avail. 5 phonecalls to Samsung which did nothing. Read your post installed the driver you linked to and bam it's working.
Thank you Thank you Thank you. You have saved my sanity!
bstdnator said:
Hi All,
I just tried to connect my TF101 to an old WinXP box and got the error above when installing the driver from the Asus site, the solution after looking here was to install the Microsoft User Mode Driver Framework for WinXP here. I think this fix applies to all android devices but I figured it was worth a post if it saves some TF users from a long search.
Click to expand...
Click to collapse
this was an awesome cure. Helped me install my new Motorola Electrify M XT901. Keep up the good work!
I experienced same problem. but whe n updating new UMDF it says " an equivalent or newer version of UMDF is already installed on this system".
I tried to uninstall this old UMDF but I can't find it in the directory.
Please I need help.
not working for my xp system
and s3
Work on my htc one s Thx Bro :good:
Hi,
As a brand new owner of TF700T (9.4.5.22), I'd like to root it. I've thus read many posts on this site (and elsewhere, which most often direct to this forum..), in particular one describing the use of debugfs.
One pint that I've still not understood is how to install debugfs: post states to unzip the debugfs files and then to install its drivers. But when I connect my TF700T to PC (with debug tckied and asus sync unchecked), my Win7 64 deos not recongizes the device (unknown device). If I go to device manager, I see a "unknown device" and if I "update its driver", I select the directory of drivers/android from debugfs 1.9, but then I get a message that there's no need to update driver, but still I see "no driver" has been installed for the device, and it remains "unknown".
What do I do wrong ? Or do I need to install Asus Sync on PC, and then simply "exit" it to run adb/debugfs ? ("exit" and not "uninstall") ?
I also tried to check various websites, such as the transformerprimeroot site and its tutorials, but it doesn't help me. I also found another website suggesting to install java sdk+Google SDK, etc., but I've the feeling it's not required for rooting... or is it ?
Thanks in advance for your help,
Ricorico94
Try using the USB driver from the Android SDK. Although that might be the same one that's included in the debugfs root tool.
If the tablet shows up as a ADB composite device or something (don't have the tablet nearby to check, sorry) in the device manager you should be good to go.
If you can run "adb shell" and get anything but an error message, you're good to go. Type "exit" to get out of the shell.
Do not install the Asus Sync software, it can only end in tears
Einride said:
Try using the USB driver from the Android SDK. Although that might be the same one that's included in the debugfs root tool.
Click to expand...
Click to collapse
I'm not sure where to look: on Android SDK pages, it states that to connect devices, you need to go to OEM pages, and when I go follow their link to Asus I get the support page which lists firwraes and Asus Sync, but not drivers separately. Does it mean I need to install first Asus Sync, then remove it ?
I could progress :
- first, it coud interest others to see that despite Asus does not propose USB drivers for TF700T, it still does for TF201. I could download such USB drivers, thoug I did not use them..
- as I had to put my laptop on hibernation, when I switched it on again, I unzipped the USB drivers (nothing more, so probably no effect), I plugged in my TF700T and then it was recognised. I assume the download of the USB drivers did not have any effect, but it's probably linked to laptop exiting hibernation (update of some Win7 processes, I guess?)
- in device Manager, under Portable Devices, it states "ASUS Transformer Pad TF700T" and not "composite ADB" as I could read sometimes..
I'm now starting the debugfs.bat, and it's looking ok so far...so I cross my fingers !
It worked ! My device is now rooted. Thanks a lot to all of you !
I'm having the same problem, but unfortunately without Windows suddenly finding drivers.
In Device Manager, the tablet shows up as ASUS Android Composite ADB Interface, but with no driver installed (and the familiar little yellow warning triangle). Windows can't find drivers automatically, and telling it to find them in DebugfsRoot_v1.8/Drivers/Android doesn't work.
As far as I can tell, the ASUS TF700T page currently has no drivers. (I'm not allowed to link 'cause I'm a new user.) The TF201 page does have drivers, listed under 'USB', but diff tells me they're the same as the ones packaged with the debugfs root tool.
I just wanted to check: am I doing something wrong? It seems like rico also saw no drivers at the ASUS page, but then Windows suddenly recognized his tablet anyway.
I haven't installed the Android SDK because I'd rather not install Java, and from what I can tell it won't make a difference here (and rico didn't need it). But I'm a noob, so please let me know if that's what I have to do!
pyrthas said:
I'm having the same problem, but unfortunately without Windows suddenly finding drivers.
In Device Manager, the tablet shows up as ASUS Android Composite ADB Interface, but with no driver installed (and the familiar little yellow warning triangle). Windows can't find drivers automatically, and telling it to find them in DebugfsRoot_v1.8/Drivers/Android doesn't work.
As far as I can tell, the ASUS TF700T page currently has no drivers. (I'm not allowed to link 'cause I'm a new user.) The TF201 page does have drivers, listed under 'USB', but diff tells me they're the same as the ones packaged with the debugfs root tool.
I just wanted to check: am I doing something wrong? It seems like rico also saw no drivers at the ASUS page, but then Windows suddenly recognized his tablet anyway.
I haven't installed the Android SDK because I'd rather not install Java, and from what I can tell it won't make a difference here (and rico didn't need it). But I'm a noob, so please let me know if that's what I have to do!
Click to expand...
Click to collapse
Here is what I did
get ASUS Sync from the Asus Website
install it
Then uninstall asus sync (it screws things up) but keep the drivers or whatever the other thing it installs is
run debugfs.
GrimSage said:
get ASUS Sync from the Asus Website
Click to expand...
Click to collapse
Aw, I was hoping to avoid that. I'll give it a shot, though. Thanks!
Edit: Looks like it worked fine. For anyone else coming to this, just in case it's not clear, installing ASUS Sync installs three additional things: Adobe Air, MSXML, and USB drivers. Obviously the drivers are the important part. I never plugged the TF700T in while Sync was installed; I immediately uninstalled it (and Air and MSXML, but those shouldn't matter). Then I plugged my tablet in and it was detected just fine (as ASUS Transformer Pad TF700T, rather than ASUS Android Composite ADB Interface, so that matches rico's report).
Thanks again, GrimSage!
Edit again: I was worried that I'd screwed something up, but apparently I just had to actually run the Superuser app before su would work. Yay, I'm rooted and can install Arch Linux.
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
d14b0ll0s said:
The text is fine, but it should go from there smoothly. Do you have ASUS sync installed and running? If so, kill it and kill it with a heavy stab.
Does your PC recognise the Infinity when you plug in the USB cable?
Click to expand...
Click to collapse
ASUS sync is not installed on my computer and it's disabled on the tablet. My computer recognizes it when it's connected.
Sounds like a classic "it should work" situation.
Try it on a different PC perhaps. You may have some third-party software installed that's interacting with the adb. Hard to tell without looking into it really. When you try to use custom commands in adb, not the .bat file, does anything work? What does waiting for device report?
^^^ this
I know this from experience, that not all Windows PC's are created equal. I had an issue rooting my tablet on 2 Windows XP machines and one Windows 7. The final Windows 7 machine I tried magically worked. All had admin access and no restrictions.
qnfauf said:
I tried searching everywhere and was not able to find a solution.
When I run it, the following texts appear and then hangs indefinitely.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
From what I've found after searching, people have solved it by reinstalling driver, but it does not work for me.
I set both the security setting and USB debug setting, and driver is correctly installed.
I also tried following this video tutorial (http://forum.xda-developers.com/showthread.php?t=1798586), but that is pretty much what I did in the first place and that Debugfs hangs at the same spot.
I am new to an Android device. I own an iPhone which I jailbroke, but I am moving away from Apple. All I am trying to do right now is trying to change the dock keyboard layout, which apparently requires rooting.
Any help would be appreciated.
Click to expand...
Click to collapse
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Thanks for all the help. I don't really have another computer I can use right now.
newellj79 said:
If you have adb setup properly you should be able to type "adb devices" from a command prompt. If all is well you will see your tablets serial number listed. If adb isn't setup properly, well you won't see anything.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
When I type "adb devices", it says
"List of devices attached" and two blank lines. I guess adb does not see my device. Am I doing something wrong?
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Forcepath said:
I am having the *exact* same issue. I'm not sure what the deal is - I recently used ADB to root my SGS3 so it definitely boggles my mind as to why it's not working on my tablet.
Just wanted you to know you weren't the only one. I'm going to try reinstalling ADB drivers later tonight to see if maybe something is wrong on that front...
---------- Post added at 09:26 PM ---------- Previous post was at 09:15 PM ----------
Okay, let me explain how I got this to work.
First of all, the xda post you referenced has a link to a bad set of drivers. (Don't worry, it got me too at first, shame on that XDA poster for stealing credit in the first place...)
So, go here (http://forum.xda-developers.com/showthread.php?t=1706588) and download the ASUS Android Drivers USB.zip as well as as the rootdebugfs that is there.
Next, open your device manager - the reason I keyed into this is because there was a driver that said "ASUS Android Composite ADB Interface" that did not install properly. Unzip the ASUS Android Drivers and then right click on "ASUS Android Composite ADB Interface" and update the drivers, manually point to the folder that contains all of the ASUS Android Drivers and click ok, it should update your drivers CORRECTLY (You'll get a successfully updated drivers window). After that try using the rootdebugfs bat again, worked like a charm for me after that!
If you're still having issues, please let me know, and post a screenshot of your device manager if you don't mind, it could be the key to your issues as well.
Sorry for the long post, hope I made sense
Click to expand...
Click to collapse
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
mtp to ptp
qnfauf said:
Thank you, that worked!
In the process of trying to get it to work, I definitely saw "ASUS Android Composite ADB Interface" a few times in device manager. After reading your post, I could not get it to show. I tried uninstalling the driver, searching for new hardware, etc. to no avail. However, switching the USB connection type from MTP to PTP while the device manager was running (I'm not sure why it had to be running) made it show up. Then I used the correct driver files to install the driver and the root worked. That guy who put up the video tutorial apparently put wrong drivers.
Click to expand...
Click to collapse
switching from mtp to ptp fixed it for me. it caused the device manager see an new device, which then had a yellow triangle. i just right clicked on it and hit refresh, and it installed the driver. g2g after that.
I had same problem but its solved now n its just drivers problem
just google "phones_brand_name usb drivers"
download and install them
n you are done