I've downloaded the motorola driver installation tool and run it, and it acts like everything worked, but windows still says that the drivers are not installed for the phone.
- Charging works (of course)
- Mass storage works (of course)
- "Phone Mode" works (where the PC sees the phone as a phone or modem - or, for this phone, apparently a CD drive?)
- "ADB Interface" does not work (where you have debugging checked and can do cool stuff with your phone)
I understand that since it doesn't I may have to edit the android_winusb.inf file with the info for my phone, and I know where to get its device ID from. I try to mimic the other entries in that file but there are 4 things I need to enter - single adb, composite adb, and two lines for single bootloader. I guess I don't know exactly what to put there. This is what I tried:
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_42B4&REV_0216&MI_00
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D&REV_0216
%SingleBootLoaderInterface% = USB_Install, USB\VID_22B8&PID_D00D
Someone else must have encountered this before. What did you put in that file to make it work? When I tell windows to find a driver for my "Motorola ADB Interface" in the folder C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver ... it just tells me that it can't find any information about my device.
jeez, all this just to be able to tether using pdanet.
http: //www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
I notice that ADB would never load in recovery, while it would load in regular mode.
The driver was never found in Windows, and it was just called" Transformer."
To fix this you need to do a little driver ini edit to include the hardware IDs in the Google USB driver from the SDK.
Here are the steps that you need to follow in order to enable these drivers:
You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
Open the google-usb_driver folder that you will find inside your Android SDK folder.
Open the android_winusb.inf file in notepad or any text editor to edit it.
Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections.
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
Open a command prompt window and enter this command:
echo 0x955 >> "%USERPROFILE%\.android\adb_usb.ini"
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
Choose to view all devices and click ‘Have Disk…’.
Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
Once the drivers have been installed, you should be able to use ADB with your device.
To confirm that your device is recognized, launch a Command Prompt window and enter these commands:
adb kill-server
adb start-server
adb devices
If you see your device name or a few numbers as the output under the list of devices, your device is now recognized by ADB.
Although these instructions were originally written for Toshiba AC100, they should work for any Nviaid Tegra or Tegra 2 based Android device.
Click to expand...
Click to collapse
The hardware device ID used in regular mode is different than the one in recovery enough to cause a problem.
I found that this is for reg mode
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&MI_01
and this worked in receovery
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F&REV_9999
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4E1F
After the edit and following the instructions I was able to use ABD in recovery
Useful and often overlooked tip, Thanks!
Hi all, i have a problem with my Dicra Tab 307.
It's a tablet based on A13 boxchip 1.2GHz and 512mb DDR3 ram.
I'm trying to use ADB with SDK but Windows 7 didn't recognize my tablet. I have already tried with this guide:
How to find the new VID/PID in Windows 7:
1. Go to the device manager (hit the start button, and type "Device Manager" to find it).
2. Double-click on ADB, under Android Devices and select details.
3. From the combobox select "Hardware Ids" and write down the VID and PID values. For example, in the screenshot below, my PID is 0BB4 and my VID is 0C99.
Changing the VID/PID values in the ADB driver's .inf file:
1. Go to the folder which has the driver (it should be %somewhere%\android-sdk-windows\usb_driver).
2. Make a backup of android_winusb.inf and open the original using a simple text editor (notepad, notepad++, etc).
3. Right at the end of the [Google.NTx86] or the [Google.NTamd64] section (depending on whether you are 32bit or 64bit), paste the following, replacing <YOUR_PID> and <YOUR_VID> with the hex values you wrote down before:
; MY PHONE SETTINGS
%SingleAdbInterface% = USB_Install, USB\VID_<YOUR_VID>&PID_<YOUR_PID>
%CompositeAdbInterface% = USB_Install, USB\VID_<YOUR_VID>&PID_<YOUR_PID>&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_<YOUR_VID>&PID_0FFF
Now, unplug and plug the phone and install the driver normally when it asks you to, by pointing the wizard to the ADB drivers directory.
Click to expand...
Click to collapse
But windows say Can not find the driver for your device, can not install android. Anyone help me please? Thank you!
Help :\
Solved.
THIS IS DRIVER SPOOFING, I DO NOT ASSUME RESPONSIBILITY OF WHAT YOU MAY DO TO YOUR KINDLE, THIS ONLY WORKS WITH KINDLE FIRE'S SUPPORTED BY THE AMAZON DRIVERS, YOU ARE EDITING THEM AND ADDING ID'S, IF YOU DO IT TO A DEVICE NOT SUPPORTED I'M NOT RESPONSIBLE.
First, you obviously need the drivers. You can grab them from here.
Start with a fresh install (uninstall what you have if you do have anything)
Install them, then turn on your ADB on your kindle in your settings>security>Enable adb if your using amazon, or developer options in CM10.1 (click build number 6 times I believe)
Now to Device Manager (Type "Device Manager" in start menu or go to the control panel and find it)
2 Scenarios can happen, You see something that says "Kindle" or something that is an "Unknown device" under the other devices tree
If You see the kindle under "other devices" right click it go to properties, then to details and in the drop down look for "Hardware Ids" In my experience there should be TWO entries, some devices have some more, so if you have "Unknown device" this is a good sign. Like So.
You need to go to "C:\Program files\Amazon.com\Kindle Fire\Drivers\" then open android_usb.inf
(If you have 64 bit windows it'lll be \Program files (x86)\
under the sections "[Amazon.NTx86]" and "[Amazon.NTamd64]"
you need to add new entries for your device something along the lines of
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_6860
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6860&REV_0216&MI_01
Or sometimes
Code:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0216
Make sure all the numbers after "PID_" , "VID_" and "REV_" Match what you see in the Hardware ID's tab. THE ONES IN THE PICTURE ARE FOR A DIFFERENT DEVICE THEREFORE DIFFERENT THEN MY CODE EXAMPLES AND POSSIBLY DIFFERENT FROM YOUR ID'S
After you've added the aforementioned ID's save the file (With admin issues save the file elsewhere and move it over and either overwrite or rename the original)
Now select the device in Device Manager and try to update the drivers from the folder earlier (Amazon.com etc etc) It should work and be recognized.
You may have to do this for the devices different states (Ex. Fastbooot can be different and The stock OS can be different ID's other than the Recovery)
You can always check it with "adb devices" in command prompt
Hopefully this helped, I've had to do it when nothing else worked, kept me from using SoupKit and such and dealing with a whole other mess of problems. Reply If it wasn't clear enough and I'll refine this some more.
Thanks so much for this! I've been banging my head against the wall trying to get adb working again after flashing CM10.1. I did have to update drivers in recovery as well as CM10.1, but NOT fastboot.....just posting my experience.
Well as we all know the Trio products have little to no support on their website. so after alot of searching and digging around i finally found a way to root the stealth G2. now keep in mind this method has worked for me, and it MAY work for you im not sure just post your results here.
Quick reminder: I DID NOT COME UP WITH THESE METHODS, I SIMPLY LOOKED AROUND FOR SOME METHODS AND INCORPORATED IT TO MY DEVICE.
these are the links i got my info from
1.stackoverflow.com/questions/11582410/android-device-not-seen-by-adb-but-accessible-from-windows-xp
2.unlockroot.com/download.html
ALSO if anyone has found any quicker or better methods please feel free to post im only putting what i found worked for me
Step 1 getting the stealth g2 to be recognized as android device
Remember to keep the debug mode checked on your device
The first thing i did was get adb working on it. for me the device never installed properly it would say TrioStealthG2 with an exclamation. what i did was download the adt bundle from developer.android.com,from their once it finished downloading i clicked on it, i clicked on sdk,then clicked on extras,then google, and finally android usb. once in the android usb directory click on android_winusb.inf...from here you want to add some lines under either x86 section or x64 section (youll see under those sections alot of other device names like the nexus with same lines under their name)that will allow your device to be recognized as an android device and not as the G2.Here are the lines
;TrioStealthG2
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_01
We are not done yet though now we want to copy and paste your device id over the line ending in: USB\VID_16D5&PID_8005&MI_01, minimize the page and go to device manager. once their right click TrioStealthG2 or whatever the name is for you and go to properties then go to details and click on hardware id.copy the id it usually looks like the USB\VID_xxxx&PID_xxxx&MI_xx. once you finish copying your id go back to the android_winusb.inf file and now paste your id over those 2 lines i gave you. in the end it should look just like the lines i gave you, the only difference being that YOUR id is now pasted over instead of the one i gave you.it sshould look similar to this: it won't be exactly the same but similar.this is an example. You'll see my lines added in there .(you can try to paste my line and see if it works if not just follow the instructions.)
;
; Android WinUsb driver installation.
;
[Version]
Signature = "$Windows NT$"
Class = AndroidUsbDeviceClass
ClassGuid = {3F966BD9-FA04-4ec5-991C-D326973B5128}
Provider = %ProviderName%
DriverVer = 08/11/2009,2.0.0010.00002
CatalogFile.NTx86 = androidwinusb86.cat
CatalogFile.NTamd64 = androidwinusba64.cat
;
; This section seems to be required for WinUsb driver installation.
; If this section is removed the installer will report an error
; "Required section not found in INF file".
;
[ClassInstall32]
Addreg = AndroidWinUsbClassReg
[AndroidWinUsbClassReg]
HKR,,,0,%ClassName%
HKR,,Icon,,-1
[Manufacturer]
%ProviderName% = Google, NTx86, NTamd64
[Google.NTx86]
;Orange San Francisco
%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;TrioStealthG2
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
[Google.NTamd64]
;Orange San Francisco
%SingleAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_19D2&PID_1354&MI_02
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_D00D
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
[USB_Install]
Include = winusb.inf
Needs = WINUSB.NT
[USB_Install.Services]
Include = winusb.inf
AddService = WinUSB,0x00000002,WinUSB_ServiceInstall
[WinUSB_ServiceInstall]
DisplayName = %WinUSB_SvcDesc%
ServiceType = 1
StartType = 3
ErrorControl = 1
ServiceBinary = %12%\WinUSB.sys
[USB_Install.Wdf]
KmdfService = WINUSB, WinUSB_Install
[WinUSB_Install]
KmdfLibraryVersion = 1.7
[USB_Install.HW]
AddReg = Dev_AddReg
[Dev_AddReg]
HKR,,DeviceInterfaceGUIDs,0x10000,"{F72FE0D4-CBCB-407d-8814-9ED673D0DD6B}"
[USB_Install.CoInstallers]
AddReg = CoInstallers_AddReg
CopyFiles = CoInstallers_CopyFiles
[CoInstallers_AddReg]
HKR,,CoInstallers32,0x00010000,"WdfCoInstaller01007.dll,WdfCoInstaller","WinUSBCoInstaller.dll"
[CoInstallers_CopyFiles]
WinUSBCoInstaller.dll
WdfCoInstaller01007.dll
[DestinationDirs]
CoInstallers_CopyFiles=11
[SourceDisksNames]
1 = %DISK_NAME%,,,\i386
2 = %DISK_NAME%,,,\amd64
[SourceDisksFiles.x86]
WinUSBCoInstaller.dll = 1
WdfCoInstaller01007.dll = 1
[SourceDisksFiles.amd64]
WinUSBCoInstaller.dll = 2
WdfCoInstaller01007.dll = 2
[Strings]
ProviderName = "Google, Inc."
SingleAdbInterface = "Android ADB Interface"
CompositeAdbInterface = "Android Composite ADB Interface"
SingleBootLoaderInterface = "Android Bootloader Interface"
WinUSB_SvcDesc = "Android USB Driver"
DISK_NAME = "Android WinUsb installation disk"
ClassName = "Android Phone"
Save the file and exit now you want to go back to device manager and update the drivers on the trio. click on browse my computer for file and click on the directory the android_winusb.inf you saved is under. for me it was under the android usb folder so i clicked on android usb and thats it. it should update the drivers and tadah now you have an android device.
Step 2: Actually rooting the phone One click method (this is not my method and you can download the program at unlockroot.com/download.html
this is the EASIEST part once you finish getting the computer to recognize your trio as an android device just go to the site i gave and download unlockpro the free download. thats it, yes its free it has the free version and paid version. free version works just as well. once installed just click root, let it do its thing and your set. you may want to download SuperSU from the play store and if it lets you download binary files your good to go. test it and post results ;D
Thank u very much I gave up after that post is there any way to send me the driver files already moded for the tab or post them as downlaods in the thread
I can but I can do it the next day when I get back home I'll copy the drivers off my comp then send it
Sent from my G2 using xda app-developers app
just found another method that should work.
(guide) how to root generic tablets with ics 4.0.4 (a13)
I'm trying this now, will post how it goes..
Hopefully it works xD its much easier thenn this method, afox you have to download android SDK once you got that just grab the android_winusb.inf file that's in it and add the lines I posted above inside that file,save then exit and update driver manually,and go to the folder that has your android_winusb.inf file it should install. I'll try to post an image of how it should look. It should look just like the other lines in that file
Sent from my G2 using xda app-developers app
it works but dont try to change the lcd density below 120 it will just about brick it an can u pls do a adb backup of yours an email me it i did change it an now the launcher wont start now so pls email me a copy of it
nm i got go luancher installed with adb got it fixed lol im try the other root
Oh sorry I didn't reply sooner. But yeah I have my lcd density at 140 atm if you need any more help lemme know
Sent from my G2 using xda app-developers app
warning the android system will become unstable i had busybox an su thats it the thing will open apps then force close them it also is unresponsive am gonna try to put up a debug log an make a adb back up befor it dose so now i need a back up with adb to restore it so can someone do a back up an let me know cause im soft bricked right now
Thanks marreroj32! This totally worked for me. I have a Stealth G2 Hype (4GB ) and since I am new to rooting any android device, I had to do some research to find out what "adb" and other things meant, but it all worked out.
A list of my steps:
1. I actually had to end up copying your driver code into a text file and saving it as "android-winusb-alt.inf" because editing the Google .inf kept giving me errors. Oh and I had 2 Hardware IDs, one that matched yours identically and the other was USB\VID_16D5&PID_8005&REV_0231&MI_01, I used it and it worked fine.
2. My machine kept showing up as "0123456789ABCDEF" in adb devices so I had to actually open up the Dalvick Debug Monitor (command line ddms) and make sure I did in fact have the right device. And it did in fact show up as "mach_speed-g2-0123456789ABCDEF."
3. Once all of that was done, I downloaded UnlockRoot software (watch out for the adware and other goodies it tries to install on the free version) and ran it.
4.) Opened up a terminal on my device (I got Android Terminal Emulator from the PlayStore) typed in "su" and was given Super User access.
5.) This was when I realized "I rooted my device! Now what the hell do I do next?"
Thanks again for the guide
This method installs a ridiculous amount of spyware on your system. Is there another method?
kruuth said:
This method installs a ridiculous amount of spyware on your system. Is there another method?
Click to expand...
Click to collapse
Yes. If you are able to get the drivers working correctly for running ADB commands to the device:
1) Install a program called Cydia Impactor (do a google search)
2) Open program and run the first thing displayed: "# drop SuperSU su to /system/xbin/su" & hit start
3) Install SuperSU from google play store
4) Enjoy
Whole process took 5 minutes after drivers were installed correctly.
Here are the drivers I used Win7-64, I can't remember exactly in xda where I got that them but its the only one that work for me. I already edited android_winusb.inf in this zip.
Mine registered as this below and this is what is in the android_winusb.inf file
;TrioStealthG2
%SingleAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_16D5&PID_8005&MI_00
So please check what your hardware id is before complaining.
By the way, does anyone know of any recovery/ROM that works for the Mach Speed Trio Stealth G2 Hype 4GB?
My trio is bricked
i can't believe that one day, i use my tablet as usual, but i can't turn it on. When i plugs it in my computer, is is charging but when i hold the power button, it doesn't start so i can guess it is bricked. Who can help me with this proble,
Tried using your method for modifying the USB driver and get a hash error.
There were 2 device IDs one being USB\VID_1B8E&PID_C003&REV_0007
And the other without the &REV_0007, tried both, tried them in the 32 and 64, just the 32 and just the 64, all resulted in a message about the hash file not present and corrupt or tampered file...
Friend brought over a bricked device, can only get to splash screen or see Battery charging, the Vol- and PWR gave tones and saw in device mgr like rest of the tutorial.
Just hoped found some method to talk to this device or get it past this logo screen, unknown what had happened to device to find it in this manner.