I had to switch to Windows XP x64 from the 32bit version and found out after I did that the necessary USB driver isn't compatible. It took a little googling, but I figured out how to get it to work. I figured I'd post how I did it to save other people the trouble.
I'm not sure if the necessary changes are the same for each type of Galaxy Player (please reply whether or not they are--I think they should be, though), so I'll go through how I got it right for mine.
1) If you don't already know, root your device with SuperOneClick (http://forum.xda-developers.com/showthread.php?t=803682); then install the Java JDK (http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u26-download-400750.html); then install the Android SDK (http://developer.android.com/sdk/index.html) including the Google USB driver, Android SDK Platform Tools, and Android SDK Tools. (Those are the requirements to use adb on any system.)
2) Hit ctrl-r and type in devmgmt.msc and hit enter. We have to locate your device. If you already connected it and it installed successfully (i.e., with drivers that don't work with adb, like the ones that come with Kies), it'll be listed under SAMSUNG Android Phone. If not, it should show up under Unknown Device. Expand it, right click on the indented line/device that shows up, and go to Properties. Click the Details tab and under Property click Hardware Ids. Keep this window open where you can see it.
3) With your text editor of choice (notepad or wordpad work), open C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\android_winusb.inf. Scroll down to the section [Google.NTamd64]. We need to add a section for our device just like you see there already. Use the longer hardware id from the device manager for the SingleAdbInterface and shorter for the CompositeAdbOnterface. Here is mine:
Code:
; Galaxy Player
%SingleAdbInterface% = USB_Install, USB\VID_04e8&PID_685e&Rev_0400&ADB
%CompositeAdbInterface% = USB_Install, USB\VID_04e8&PID_685e&ADB
Add yours and save the file.
4) Now go back to the Device manager, right click the same line as before, but this time choose Update Driver.
--Click "No, not this time" and Next
--"Install from a list or specific location (Advanced)" and Next
--"Don't search. I will choose the driver to install" and Next
--Click the "Have Disk" button and browse to C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver. If you edited the android_winusb.inf correctly, it will work and tell you to reboot once it's done.
5) After rebooting, your device will show up in adb and Android Commander!
Related
Does anyone know how to get the ADB to work? I tried downloading the usb_driver from Android SDK but that didn't help.
ADB works the same way with the eris as with any Android based phone. You may want to tell people what operating system you are using to get things started.
Assuming you meant windows ( usually thats the case ) you first want to download the htc driver. There are two out there, the 32 bit one and the 64 bit one. This is what I meant by what operating system. Once you have picked a driver, you want to go into your device manager and apply that driver to the ADB device where it is listed by clicking the "update" driver button.
You need the HTC Sync software.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
you can get the one in the sdk to work by adding the Vendor and Product ID to the .inf file. i had to do this to get it to work with the leaked 2.1.
esmith972 said:
You need the HTC Sync software.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
Click to expand...
Click to collapse
You don't need that. The USB driver can be downloaded through the Android SDK.
GrdLock:
While you can download it from the SDK, the version made by HTC in the Sync program is alot easier to install as it puts the driver files in the correct places on your windoze machine to auto-install.
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
ihtfp69 said:
In case anyone still needs this
Click to expand...
Click to collapse
Thanks. It took a while to find this post
Before I rooted (when phone was at 1.5), it connected to ADB just fine. Now that it's running 2.1, it won't recognize it. I've re-updated the USB stuff through the SDK too.
ihtfp69 said:
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
Click to expand...
Click to collapse
Big thanks!!!
ihtfp69 said:
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
Click to expand...
Click to collapse
will try this
paOol said:
will try this
Click to expand...
Click to collapse
Worked perfectly. Definitely try it
ihtfp69 said:
In case anyone still needs this, add these lines to the [Google.NTx86] and [Google.NTamd64] sections of the android_winusb.inf file that comes with the SDK. It will allow you to install the driver for your Eris. I recommend not using or installing HTC Sync unless you really want to.
Code:
; HTC Eris
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
Click to expand...
Click to collapse
Thanks! Once I did this I used Device Manager to install a driver for the ADB Device with a yellow exclamation mark. Windows detected the phone and now my "adb devices" command shows the phone.
I don't need HTCSync as I using :MyPhoneExplorer
I don't need the full Android SDK as I'm not a dev but I'm using ADB and fastboot.
So I proceed like this to install HTC driver +ADB/Fastboot without additional files:
HTC Driver:
Double clic on setup_3.0.5579.exe (dwnld from HTC support site)
Choose the language and clic next (stop when it list the things to install: air,...)
Go to c:/user/yourname/AppData/Local/Temp
Order the files by date and choose the last folder created (so the temp folder were the files were extracted for the full package install)
Delete all *.prq except the ones for the drivers (3 files, 2 if you choose between x86 and x64)
Clic next in the HTCSync install box.
All deleted prq will be 'installed' but in fact no
Check... only drivers are installed
nb: do this if you don't have a sense ROM and don't need HTCSync of course.
Hope this will help
ADB:
Download the SDK, open it with 7zip and take the 'tools' you want
nb: 7zip can't open the HTCSync.exe so the driver extraction was not possible for me. If you can access the files in th exe you may get the driver directly. Not good enough in IT (and/or not enough time to search for the right tool).
Hope this will help
truc007 said:
I don't need HTCSync as I using :MyPhoneExplorer
I don't need the full Android SDK as I'm not a dev but I'm using ADB and fastboot.
So I proceed like this to install HTC driver +ADB/Fastboot without additional files:
HTC Driver:
Double clic on setup_3.0.5579.exe (dwnld from HTC support site)
Choose the language and clic next (stop when it list the things to install: air,...)
Go to c:/user/yourname/AppData/Local/Temp
Order the files by date and choose the last folder created (so the temp folder were the files were extracted for the full package install)
Delete all *.prq except the ones for the drivers (3 files, 2 if you choose between x86 and x64)
Click to expand...
Click to collapse
Nice hack truc. Worked for me. Editing the Google USB driver didn't work because it complained the hash on the .inf files was corrupted. I'm on Windows 8.
Hi,
I recently bought my first Android phone, an HTC Hero, from a helpful eBayer here in the UK. When I got the phone, it had already been rooted and had a custom ROM, v4 RC1 of EzHero, installed.
I want to update this custom ROM to v5.1, because there are some problems with the current version that's installed. (For example, the phone doesn't ring because there are no ringtones installed! Also, the camera doesn't work, and the phone crashed and rebooted whilst I was in the middle of a call last night.)
So, after some reading around on these forums, I tried following the instructions on this thread: http://cleanimport.xda/index.php?threads/709220/. The basic first step is to download the SDK from Google and instruct it to download the USB driver. So far so good. (I am using Windows 7 BTW.)
However, I have been unable to get the USB driver installed correctly, such that when I run the command:
Code:
adb devices
I get nothing back. (Not strictly true -- the first time I ran it it said it was starting a daemon, then said something like "devices list", but listed no devices. The second time I ran it, it didn't mention the daemon, but still didn't list my device.)
When I connect the phone to my computer (via USB, and with USB debugging enabled), I basically get a balloon at the bottom right of the screen to say that it is installing drivers, and then it says it had some problems. It lists out several devices, each with a green tick or a red cross against them. Invariably, one of the devices listed is called simply "ADB", and it always has a red cross against it. I am not specifically prompted to point the system towards any drivers for the device.
If I go into Device Manager, I currently see, under "Other devices", three devices:
- ADB
- Multimedia Controller
- Multimedia Video Controller.
The icon for each of these has a little yellow exclamation mark. If I double-click on ADB, I am given the chance to Update driver. Doing this gives me two options, and I choose "Browse my computer for driver software". This prompts me to "search for driver in this location" and I choose "C:\android-sdk-windows\usb_driver". (I have also tried pointing it to the subfolder "i386", but this gives the same result. I am on a 32-bit Intel system.) There is also a checkbox "Include subfolders", again I have tried both options, and both lead to the same outcome.
I then click Next and receive this error message:
Windows was unable to install your ADB
Windows could not find driver software for your device.
[...]
Click to expand...
Click to collapse
If, instead of clicking Next, I click "Let me pick from a list of device drivers on my computer" and then select "Mobile devices" and click Next, I am presented with a blank list and a button reading "Have Disk". Clicking on this lets me browse, this time, for an .inf file. But selecting the android_winusb.inf file gives the following error message:
---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a
driver, make sure it is designed to work with Windows for 32-bit systems.
---------------------------
OK
---------------------------
Click to expand...
Click to collapse
This is about as far as I have got! I have tried experimenting with a couple of things, but with ultimately the same result:
Running (as administrator) USBDEview and uninstalling anything that starts with HTC, or ADB, or Android, or USB Mass Storage device
Editing the .inf file using the modifications described below:
The first modification I tried is described in comment 44 of issue 1039 on the Android Google Code forum (link removed because I don't have permission to post external links!):
Code:
;HTC Hero
%USB\VID_0BB4&PID_0FFE.DeviceDescRelease%=androidusb.Dev, USB\Vid_0bb4&Pid_0ffe&Rev_0100
You can find / adapt those description with your material manager (look in advanced tabs)
To have a nice name of device, add at the end of file something like
USB\VID_0BB4&PID_0FFE.DeviceDescRelease="HTC Hero rev 0100"
The second modification I tried is described in comment 99:
Code:
[Google.NTx86]
; HTC Hero
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C9A&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0C9A
And the third is described in post 2 of a recent Android Developers Google
Groups thread entitled "cannot install USB drivers for HTC Slide, Android 2.1, Windows Vista 32 bit" (link removed because I am not allowed to post external links!). For this one, I consulted the information displayed when I go into Device Manager > ADB > Properties > Details > Hardware Ids, so the actual lines I added to the .inf file are as follows:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&REV_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
I also tried a slight twist on this:
Code:
;HTC Hero 2.1
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
since all the other devices in the .inf file didn't include the &REV_0100&MI_01 parameters for the %SingleAdbInterface% line.
Finally, I also tried various times to uninstall devices from Device Manager, e.g. ADB, the two multimedia controllers with exclamation marks against them, and USB Mass Storage Device (which does indeed have three lines on the Properties > Details > Compatible Ids screen, as advised by a blog post I found on the Android Simplicity blog entitled "How-To #0: How to Install Usb Driver on Your Computer" (link removed because I do not have permission to post external links!).)
I really can't think of much more to try, so would really appreciate any pointers, however small, from the experts!
Another option might be to give up on Windows and try doing the whole process under Ubuntu Linux, which I have installed under dual-boot. However, the instructions for updating ROMs/making backups/recovery/etc. appeared to rely on some Windows executables so I figured that could be a risky approach (especially given I know very little about how to work Linux...!).
Thanks for reading
Michael
Don't need them. Get the latest HTC Sync and install the My HTC driver and adb will work.
Thanks for such a quick reply btdag!
Really? That would certainly make things a lot easier, however dreamersipaq does make a point of reinforcing how important it is not to have HTC Sync installed in his instructions:
At this point, I'm going to ask that you uninstall HTC Sync. Also, please uninstall HTC Driver... (whatever it's called) Nobody likes them (really though, it will mess up a lot of things. You can install them later when all this is done)
Click to expand...
Click to collapse
[...]
HTC Sync does not like to play nice with the reflash tool
Click to expand...
Click to collapse
[...]
Ok, at this point, I'm going to ASSUME that you don't have HTC SYNC installed (or uninstalled it)
Click to expand...
Click to collapse
Does this not matter after all?
To get adb working I just installed the latest HTC Sync and drivers and then added ;C:\Path\To\SDK\Tools to my Windows Environment Variables as described in this guide:
http://www.villainrom.co.uk/viewtopic.php?f=46&t=1735&sid=d1d70142a6264965b8c370bf1afa64d0
no problems with adb since
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Thanks for all the help.
I'm pleased to say I've now managed to install the update, and my phone is now ringing!
In the end I worked out that I did not in fact need ADB at all. Since the phone had already been rooted and had a custom ROM installed, it dawned on me that it must already have the requisite recovery image installed. And indeed it did. So all I had to do was install Titanium Backup, back up my apps and settings, also take a nandroid backup just to be on the safe side, and then factory reset/wipe and install the update. (And then restore apps and settings using Titanium Backup.) Problem solved!
As an aside, I think there is certainly scope for more 'newbie' documentation. (Or would this be on the Wiki, currently down?) I'm certainly very grateful to those who have taken the trouble to set out what they have learnt already, for the benefit of others. For example though, even after spending several hours searching and reading up all the newbie guides I could find, I still had to read between the lines quite a lot to work out what a 'radio' was, what purpose the recovery image serves, how ADB fits into the whole picture, why there are multiple custom ROMs available for the same version of Android and how to choose one, etc. Perhaps one day I will be advanced enough to attempt that myself!
CyberWalrus said:
As an alternative, if you install "droid explorer" it will automatically download and install the right drivers for you. Plus its a great app. Google it!
Click to expand...
Click to collapse
Thank you very much! I was reading this trying to get my G1 to work and it did. Windows 7 x64 won't allow me to install the android_winusb.inf driver but droid explorer did.
Phone nor computer will recognize adb/usb
First of all, my is rooted but somehow the superuser.apk file is missing. When trying to activate wifi tethering it asks if the device is rooted. The answer is, yes! I can boot into recovery mode but I do not have a way to get the superuser to open without adb. Can anyone help me?
Unable to Instal ADB Drivers
I'm having similar issues trying to root my MyTouch 4G. I've been following steps on the cyanogen wiki website for this device, which refers you to their site's instructions for setting up SDK & ADB drivers.
I've downloaded the SDK zip file, extracted to the C drive and made sure file paths are all the same as per the instructions. When following the instructions under Windows, I've added to variable values ;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools (and double checked these folders on C drive to be sure they're accurate).
When trying to manually update device drivers for ADB, I select the file android_winusb.inf and get error: "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
My device has USB debugging enabled and is in mass storage mode (I've read on other forums that this can fix).
Not really sure what else to try? Any way I can change the .inf file to make Windows recognize it? Running Windows Vista 64.
I've tried following various steps in the AIO thread in the developers section and believe I have a similar problem to pjc007. I have tried foloowing his steps in http://forum.xda-developers.com/showpost.php?p=27548839&postcount=1179 but I'm still stuck on getting the drivers installed when the tablet is in recovery mode. Am I right in trying to install the mtp driver from the AIO/files directory?
I have tried running AIO on two win 7 machines and a virtual xp machine and get the same problem on all machines. Please help
Is anybody able to help at all?
Or if anybody has a UK 16GB Wifi ICS Rom ready to run from recovery, that would be very much appreciated
you mean you háve your tablet already updated or rooted?., and the drivers aren't installed for ICS?
could you be more specific "D
---------- Post added at 09:45 PM ---------- Previous post was at 09:39 PM ----------
1. Update your SDK Manager
- In SDK Manager expand Extras then search for Google usb Driver if not already installed then do this,
2. Open the google-usb_driver folder that you will find inside your Android SDK folder.
- Example C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver\
3. Open the android_winusb.inf file in notepad or any text editor to edit it.
- If you can't change this then try to change permissions in that folder
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
;SONY Sony Tablet P
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_04D2&MI_01
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
4. Open a command prompt window and enter this command:
echo 0x054C >> "C:\Users\Cinquk\.android\adb_usb.ini"
5. Make shure you have USB Debugging enabled.
- Menu > Settings > Applications > Development and enable ‘USB Debugging’.
6. Connect your tablet to pc and let the pc install the drivers some will faill but thats okay.
7. Right-click Computer and click Manage and search your device from the list, right-click it and click Update Driver Software.
8. Choose to browse your pc,
- Choose to view all devices.
- Click Have Disk.
- Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
---- It might say that its not compitable but just proceed.
9. Once the drivers have been installed, you should be able to use ADB with your device.
10. to check that,
- Press Windows button + R
- Then type CMD and press enter.
- cd.. back to your Harddiskdrive.
- cd to your Platform-tools folder Example C:\Program Files (x86)\Android\android-sdk\platform-tools
- then type:
adb kill-server
adb start-server
adb devices
- you should see your devices listed ( Serial Number )
and you can comfirm that you have a working adb with you sony tablet s.
Thanks for the above info, my ADB is working fine in normal boot, but not in recovery mode.
I originally had my tablet rooted and updated to the first US ICS rom about a month ago using AIO tool v2.7
All was fine until I started poking around to find out why my titanium backup kept failing and found this was due to the SD card being set to read only. I followed a guide in these forums to enable read/write (before this fix was available in AIO) and somehow managed to wipe my permissions file.
I decided to start from scratch, flash back to hc and start again, but since doing this I have been unable to install an adb driver for when the tablet is in the recovery mode. ADB is working fine in normal operating mode and I could use AIO fine, until the point where it was waiting for a response in recovery mode as no drivers are installed...
I got impatient yesterday and have now updated a stock, non rooted US ICS as I've been going in circles for a couple of weeks trying to make a pre-rooted update file and I've been missing my ICS I would ideally like to be on a proper UK rom, but will live with US version if there's nothing I can do for now.
Alright that means end of this topic
Hello Everyone,
Well like some of you I had a hell of a time trying to see my sdcards in order to flash new JB roms.
I had MechaPanda and Ntnemis that helped me get it going. I stumbled upon a step that finally made it work.
This will show you how to get ADB and Fastboot to work with Windows 7 32 and 64 bit versions.
It is easy and takes about 5 minutes to do.
Step 1 - get the Windows USB drivers from this thread.
http://forum.xda-developers.com/showthread.php?t=1354487
You need USB drivers first:
http://dl.dropbox.com/u/15069134/usbdrivers.zip
Step 2 - get the free Windows app Notepad+
Windows notepad can work also.
Step 3
Now this is where I found the glitch for me. I was on JB .03 I went back to ICS to at least access my memory. I looked at the PID value and found it's different in ICS vs. JB. So you will likely need your ICS PID value to make this work. You can try using your PID values first if you are on JB first before you wipe back to ICS.
Make sure you add them to 32 and 64 bit section to be sure.
Step 4 Connect your tablet turned on booted into the ICS ROM
Open your Win Device Manager:
Look under OTHER DEVICES.
Right click on the NookTablet (has yellow !)
*my screen cap shows bluetooth device, just click your nooktablet
Step 5 Open the android_winusb.inf file from the drivers package with Notepad+
Step 6 Move down the this section in the file.
You are taking your PID values and replacing the ones in the inf file.
***I DID THE SAME FOR THE [Google.NTamd64] ALSO
[Google.NTx86]
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
See photo for info.
Step 7 - Now go and copy your 2 lines (1 at a time) from the Win Device Manager and replace lines 1 and 2. Do the same under the [Google.NTamd64] bit section too.
Step 8 - Save the file
Step 9 - now go back to Windows Device Manager and update driver, point it to the inf location of the file you edited above. Windows will now install your ADB device
Step 10 - open ADB and test or as I did I booted my tablet in Cyanoboot then picked the Fastboot option
Step 11 - Download the new recover03.img posted in the JB ROM thread.
Flash the new recovery.img with fastboot and you are done.
***The above did NOT work for me using the PID values from JB. It ONLY worked for me going back to ICS. I then flashed back JB and all still works.
You know, all you have to do is install the same ADB drivers for fastboot, right?
NookTabletsPower said:
You know, all you have to do is install the same ADB drivers for fastboot, right?
Click to expand...
Click to collapse
You know I posted that does not work for some of us.
This is how I got mine to work.
droiduzr2 said:
You know I posted that does not work for some of us.
This is how I got mine to work.
Click to expand...
Click to collapse
You smart mama jama... worked for me. I was about ready to chuck this tablet out the front door :laugh:
Do we need a 3rd line "%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF"?
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
Mine says NT is offline. I'm running XP, but at least I can mount USB and access them with windows explorer now.
Still can't do adb. I tried 4.2.2 adb as well.
Thanks
lepa71 said:
Do we need a 3rd line "%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF"?
Click to expand...
Click to collapse
No.
Anyhow, I finally got ADB working again on my laptop as the drivers I'd installed there some time ago no longer worked.
This is what I did...
1. Download the USB drivers as per the OP's post and extract to a temporary folder.
2. In Device Manager, right click the Nook Tablet device (with the yellow exclamation).
In the popup dialog select the Details tab and then Hardware Ids from the combo box.
(Note the image below was taken after I'd done the driver update so it's showing Android Composite ADB Interface instead of Nook Tablet.)
3. Copy the second shorter value there. (The first value with the extra REV_XXXX field may have worked too.)
4. Open the file android_winusb.inf (in the usbdrivers folder) in a text editor and into both the [Google.NTx86] and [Google.NTamd64] sections add a Nook Tablet option using the hardware Id info copied in step 3. Abbreviate the Id for the SingleAdbInterface entry by removing the MI_XX value and preceding ampersand. Save the edited android_winusb.inf file.
Code:
;B & N Nook Tablet
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_6868
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_6868&MI_01
5. In Device Manager, right click the broken Nook Tablet device again, select Update Driver Software, click Browse My Computer for driver software and select the usbdrivers folder (found where you extracted it from the zip file in step 1). The drivers should now install.
Hopefully, everything should work ...
Code:
C:\NookTablet\>adb shell
[email protected]:/ #
Code:
C:\NookTablet\>adb devices
List of devices attached
0123456789ABCDEF device
Mine still shows offline.
D:\Downloads\Droid\NookTablet\Tools>adb devices
List of devices attached
201454000857xxxx offline
Almighty! lets get started,
I have a 64 bit computer running Windows 7 professional.
First let me mention I tried to fix this on my own. darn I tried.
Just plugging the tablet into computer shows a windows explorer page named Autoplay that let me view pictures on device on a folder named
Computer\Trio HD Elite 7.85 Tablet
Installed android-studio-bundle-141.1903250-windows in
Error- SDK required.
Downloaded jdk-7u79-windows-x64 (java development kit)-install reboot PC
Open C:\Andriod in windows explorer, open SDK Manager
A command prompt window flashes briefly, then closes.
click start, search for run key in sysdm.cpl go to advanced, environment variables create new path named JAVA_HOME that does directly to the java .exe file
(this was checked by reinstalling the java development kit, then opening Java typing where java it tells me C:\Windows\System 32 even though the path is
C:\Program Files\Java\jdk1.7.0_79
opening ADB works!
Download Extras- Android USB Driver
open CMD key in
cd C:\Andriod\platform-tools
this brings me to the directory where Android ADB is.
abd devices
no devices detected.
Installed Samsung Kiles.
TRIED to install PDAnet.. failure.
tried to open Device manager, where a entry marked Trio HD Elite 7.85 Tablet sits, and update the driver to the C:\Andriod\extras\google\usb_driver
it complains about driver being unsigned. Using This guide I used step Two downloaded Driver Signature Enforcement Overrider (DSEO) and ran it.
went into the C:\Andriod\extras\google\usb_driver folder and manually keyed in every title in the folder.
each time program stated had signed successfully. The computer is now saying test mode in the bottom right hand corner. however trying to update driver gives same error.
I'm amusing the device needs to be in developer mode, which it cant be put into because it's locked.
The Trio Support is useless there steps do not open any settings. Also tried a list of alternate ways to open tablet recovery. and since ADB isn't reconizing the device I can't run adb reboot recovery
So. end result, im here with coffee and no milk,
A generic tablet cobbled together from who knows where,
and a locked screen.
Think you can help?
ANY assistance is appreciated.
So i have a cheap generic tablet that says Trio Stealth G4X 7.85