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.
Related
So I used ECLIPS3's master app to root my phone (worked great by the way, thanks ECLIPS3 ) But now whenever I plug my phone back in with USB debugging on, it won't find the drivers. Even when I have it look in the USB drivers folder I installed with the Android SDK. I tried removing it with device manager and reinstalling, but still didn't work. I guess it's not that big a deal since I have root now and can just flash the roms from sd card. But I'd still like to know if there's a way to fix this just in case. Never know when you might need it
I didn't use the master app but I did have the same problem with my last rom update. My quick solution was to update the android_winusb.inf file in the usb_driver section of the sdk (there are a couple of ways to correct this problem- this was just the easiest at the time).
I added this line to the [Google.NTx86] section:
; HTC Eris After 2.1
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C98&MI_01
You may have to check the DeviceInstance Id in your device manager to see what ID to use if this line doesnt work.
Thanks for the help! But I already found a work around. I read that if you downloaded htc sync it would put the drivers where it needs to be and install automatically, which it did. But thanks anyway
A tutorial for how to get ADB and DroidExplorer up and running for your Rhodium in Windows Vista.
All this information exists in bits and pieces of posts throughout this (and other) forums, though I felt it would be helpful to compile it in one place.
If you’re running a different version of windows, the differences should generally be fairly minor. Please let me know if there’s any mistakes or modifications I should make here.
ADB refers to the Android Debug Bridge, a tool put out by google, which lets you access your android device via the USB connection for the purposes of debugging it. One particularly useful component is the ability to access your phone from your PC via a terminal window (similar to a command prompt). While not necessarily intended for this purpose, it may be used for a rudimentary level of USB access to transfer files to and from your device. It will NOT let you have any of the advanced functions that a native driver would.
Optional First Step: Download ADB from Google:
You may choose to install the SDK yourself, but this will be incorporated in your installation of DroidExplorer in step 4 if you don't already have the SDK installed.
ADB is part of the Android SDK (Software Development Kit), which you can download from:
http://developer.android.com/sdk/index.htmlInstall the most recent version for windows. For simplicity sake, I suggest you extract/install it to the root, so for example, to
C:\android-sdk-windows\
Optional:
To make your life easier, it’s a good idea to add the folder containing adb to your system environment path, so you can use adb from anywhere on your drive.
To do this, right click on My Computer, click ‘Advanced System Settings’, and then click on ‘Environment Variables’.
Choose one of the PATH variables (either for your user, or the system wide one), and add the path containing the adb.exe file. For example, if you extracted the sdk to the root of C drive as I had suggested, the path would be:
[blah blah, preceding path values] ;C:\android-sdk-windows\platform-tools\
Make sure you remember to have a semicolon preceding the path you’re adding, so windows knows it is separate from the previous entry.
Second Step: Remove previous drivers:
If you have tried to connect your phone (in android mode) to your PC, you may need to go to the device manager and remove the incorrectly-installed drivers.
Third Step: Install Drivers:
The key obstacle here is that there is no driver made by HTC (or others) specifically to connect the Rhodium in Android mode to a PC. While there may eventually one day be such a driver, we need to resort to a work-around.
Drivers Option #1:
A product called PDANet installs software on your android phone and your windows PC that then functions as a PC and device driver set. (The application has other intended uses, as you can read on their website, but these are secondary to our purpose).
Download and install the latest version of PDANet, on both your android Rhodium (via marketplace) and your PC (via the below link):
http://www.junefabrics.com/android/index.php
You will then need to follow the prompts to connect your phone, select the manufacturer (HTC), and the HTX XDA Driver will be installed. Windows security may require you to approve the installation, as the driver is unsigned. After installing, you will need to restart your computer before the drivers will work.
As part of the install, you will be asked to connect your RHOD phone to your computer via the USB cable. The new hardware wizard should pop up, and you should choose to install the driver automatically (given that you’ve previously placed the driver onto your system with PDANet – if you’ve managed to locate the specific driver file as I’ve heard rumors of, then browse to that file).
USB Debugging needs to be enabled on your device, which it is in the stock builds provided here (Settings->Applications->Development->USB debugging).
Drivers Option #2:
Install the HTC Sync Drivers - this has been described for Windows 7, although there are mixed reports as to the success. Information is in the below links:
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
Optional:
To check that your phone is working, type ‘adb devices’ into your command prompt. If you see your device, you’re good to go. (if you didn’t set the environment path to include the location of adb.exe, you’ll have to either cd to the directory first, or type
C:\android-sdk-windows\platform-tools\adb devices(if you installed the sdk elsewhere, then modify the expression appropriately
What can you do now? To see a list of commands you can use, simply type adb from the command prompt.
To use adb to send a file ‘picture.jpg’ to your sd card, in your command prompt, go to the location of the picture, and then type :
adb push picture.jpg /sdcard/to see the contents of /sdcard , type:
adb shell ls /sdcard/Read more about ADB here: http://developer.android.com/guide/developing/tools/adb.html
And for more details on setting up and using ADB, see this (the source for this workaround):
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
--
Fourth Step: Install Droid Explorer
Now that this is working, you may appreciate an application called DroidExplorer, which gives you a GUI that lets you navigate your device in a manner similar to windows explorer. From here, you can copy, move and delete files, as well as install and uninstall applications.
Download and install DroidExplorer from here:
http://de.codeplex.com/
Startup DroidExplorer, and you’re finished. Do read up on ADB and DroidExplorer on their respective pages so that you know both what you can do as well as what you might inadvertently break by blindly playing with options.
As has been said frequently on this website, if you want safe, stick to the default ‘stable’ XDAndroid install for the Rhodium, and keep your windows mobile running as a backup. If you want more, know that you’ll have lots of learning to do, and potentially may loose all the data on your phone and need to spend hours learning and fixing it. You may even brick your phone (make it unusable and unsalvageable – make it about as valuable as a brick).
Helpful Links:
The wiki for ADB on XDAndroid:
http://xdandroid.com/wiki/FAQ#What_is_ADB_.2F_How-To_ADB
Original xda thread on getting USB to work on the rhodium:
http://forum.xda-developers.com/showthread.php?t=849718
If you have any additional comments/changes to suggest, please let me know, and I’ll modify this initial post.
Heh, I always meant to turn that "original XDA thread" into an ADB tutorial for Windows users... but I just never got around to it.
Thanks for putting this together - do you mind if I reference it in the FAQ?
Just skimmed over the how-to - perhaps you should mention that in lieu of the Android SDK, you can simply download Droid Explorer. It usually takes care of the nitty gritty stuff, but pdanet seems to fill in the gaps with driver issues...
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
AkumaX said:
I actually found the drivers we needed (XDA in Device Manager)
http://forum.xda-developers.com/showpost.php?p=12705726&postcount=7
Click to expand...
Click to collapse
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
arrrghhh said:
Droid Explorer took care of all the drivers for me on Windows the first time. The second time, PDA.net took care of them for me. I had issues with a ton of different drivers the second time around; even tried wiping them from the system, etc... PDA.net was the only solution that worked for me, as you can see in the linked thread I started.
Click to expand...
Click to collapse
I installed Droid Explorer and was left w/ 3 (!) Drivers missing, CDC abstract control model ACM x 2, and XDA. After I installed the HTC Sync drivers, it found the driver for XDA and then that gave the ability to let Droid Explorer install the other two *shrugs*
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
slycker said:
AkumaX, which version of windows did you get the drivers working with? Had you previously tried to install other versions of drivers, or was this 'fresh'? I haven't tried this route (being happy with my PDANet drivers working) - would you say the instructions are good on: http://www.mydigitallife.info/workaround-for-htc-hero-sync-problem-in-windows-7/
arrrghhh, please go ahead and link to this post. I had included the SDK portion because I had mis-read the droidexplorer main page, where the author stated his intent to stop updating the SDK and default to the pre-installed SDK. I see now that he intends to link to the SDK, and thus facilitate its installation for the user. I'll update that in the first post.
Click to expand...
Click to collapse
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
AkumaX said:
I'm using Win7-64 bit, so I used those drivers. It was a fresh install, and I never even thought to use PDANet, my own searching stumbled upon that thread for the HTC Sync Drivers. It could be better that you install the HTC Sync Drivers before Droid Explorer, but I'd have to find another 'clean' system to try on
Click to expand...
Click to collapse
That's what VirtualBox is for! lol.
yes i can install usb drivers thank you !
I am new to the Android platform so please excuse any silliness on my part…
Below are the steps I took to successfully allow my Vizio Tablet (VTAB108) to connect via USB using the generic Google ADB driver as Vizio does not include ADB access for the tablet.
History:
I am trying to Root my tablet and from what I read throughout the forum, the easiest steps to root a tablet is using the SuperOneClick method.
Since SuperOneClick requires ADB access and the Vizio does not include the ADB driver (and the generic Google) do not work out of the box I was at a loss to how I would run SuperOne Click.
This article are the steps I took to get ADB access working with Windows 7 x64 and the Vizio Tablet.
I am hoping my steps here can further lead to root access for this tablet.
As an FYI, I was still unsuccessful in getting SuperOneclick to completely run after following these steps, but maybe someone has an alternate method of rooting now that ADB access is available? /me crosses fingers
It would stop at Step #6 at which time I would disconnect and reconnect the tablet. It would contine to step #8 but then finally fail. If anyone has an alternative to SuperOneClick, I would gladly try it.
IMPORTANT:
The instructions below assume you have already put your Tablet into USB debugging mode.
The instructions below assume you are running Windows 7 x64. If you are running x32 versions of your OS, modify the below settings as apporopriate for your OS[/B].
1. Download and install the Google Android SDK.
(Being this is my first post, I cannot post a URL so google the following topic exactly and click the first link):
what-is-adb-and-how-to-install-it-android
2. When you get to the USB driver install you will have to manually modify your android_winusb.inf settings file to allow Windows to recognize your Vizio Tablet using the generic Google ADB-USB driver.
3. Find the "usb_driver" folder in your sdk directory. (Mine was: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver).
4. Right-click "android_winusb.inf" and open it with notepad or your favorite text editor.
Under the [Google.NTamd64] section, paste the following:
Code:
;Vizio Tablet
%SingleAdbInterface% = USB_Install, USB\VID_0489&PID_E040&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0489&PID_E040&REV_0227&MI_01
then, open a command prompt and type the following:
Code:
echo 0x489 >> "%USERPROFILE%\.android\adb_usb.ini"
5. Right-Click the unknown device in Windows Device Manager (Under Other devices) and manually install the driver for your Tablet.
NOTE: Originally my tablet connected to the computer and installed the regular Windows 7 Mass Storage driver. I had to remove this driver before I could see the device listed under "Other Devices". Follow these instructions if you need to remove your generic Mass Storage driver:
Code:
A. Unplug all removable devices (USB drives, Thumb Drives, SD Cards, Etc...) but leave the Android phone plugged in.
B. Open Windows Device Manager.
C. Select "Universal Serial Bus Controllers"
D. Select USB Mass Storage Device.
IMPORTANT: Click on the details tab and select "Compatible Ids" under the Property drop-down. You should see three items listed under Value. If not, you are looking at the wrong Mass Storage Controller.
E. Select Uninstall Driver
F. Close the window.
G. Right-Click your computer name at the top of device manager and select "Scan for Hardware Changes".
H. Your new "Android Phone USB device" with a Yellow Exlamation mark! will appear under Other Devices.
I. Click on the "Android Phone USB device"
J. Select "Update driver software"
J. Select "Browse my computer for driver doftware"
K. Browse for the location that you have unzipped the android_usb_windows ( Mine is: C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver )
6. Now test to make sure you can access your device in USB Debug mode:
Type the following from a command prompt:
adb kill-server
adb devices
You should see your device serial number at the command prompt and in Windows Device Manager if everything worked.
drivers
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
USB Drivers Not Installing
[email protected] said:
USB Drivers have been posted on the vizio support website for Intel and for AMD. Are they crucial to what you want to do about rooting?
Click to expand...
Click to collapse
I grabbed those drivers a couple of days ago and could not get Win7 or WinXP to install them with the vtab1008.
I can use adb to interface with the vtab008 (using Linux and Win7), but GingerBreak and SimpleOneClick (which uses GingerBreak) are unable to root the vtab1008.
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Agreed
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
This is my thinking EXACTLY!
[email protected] said:
I've been pestering Vizio about the downsides of the tablet. Coming from a rooted Nook, there are some things about the vizio i really like. It's a nice build at an attractive cost. If I can get netflix and hbo go working, a better remote app and a more logical system of using the sd card, I would keep it. Otherwise it goes back to Costco on the 89th day after purchase.
Click to expand...
Click to collapse
Yes, I agree. If there's no root, the tablet is not worth it.
The drivers worked for me.
I downloaded the drivers from the Vizio site and when I plugged the VTAB into my computer I manually installed the driver. I just used adb to grab a bunch of screenshots.
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
You can get to recovery mode by holding down both volume buttons and the power button. Details
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Mark0266 said:
I cant even get the drivers to install. I've did a right click on the .inf file and it will not install. Any Ideas?
Thanks
Mark
Click to expand...
Click to collapse
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
marvin02 said:
DL the drivers from the Vizio site. Turn on USB debugging on the VTAB. Plug the VTAB into your computer. When the install driver prompt comes up follow the steps to install a driver from a specific location and point it to the driver you downloaded. The steps will vary depending on the version of windows you are running.
Click to expand...
Click to collapse
Thats the problem the prompt never comes up. Running Windows 7
Well I got the driver for adb to install but it still will not show up when I do adb devices
Bootloader?
the.joeba said:
OP worked for me (without the mass storage issue)
Code:
adb reboot bootloader
just did a true reboot
Code:
adb reboot recovery
got me the exclamation mark and the "Home" button brought me to a recovery screen where it would let me flash signed updates or cache/full wipe the device.
Click to expand...
Click to collapse
Did you actually get into the bootloader? adb reboot bootloader simply reboots the device for me.
So whats with gingerbreak? No love with it? I thought this thing was rooted already prior to shipping? Hmmm. My bro just ordered one for me and I am curious about getting it rooted. Lets get this thing rooted and overclocked and get it some love. Also, whats the word on honeycomb on this beast? anything?....
Mark0266 said:
Well I got the driver for adb to install but it still will not show up when I do adb devices
Click to expand...
Click to collapse
Same here.
Rooting help
I have some coding knowledge, but have never worked on rooting a device. I did not pay for mine, so if anyone has references to some info I can look at about obtaining root then I will work on mine without fear of bricking it.
I have been at this for weeks, to no avail.. tried changing params in Gingerbreak, tried running it under every condition possible, and the only thing I haven't tried is changing how GingerBreak is using the /sdcard/ mount point, as that's where the internal memory is mounted to.. It's a pretty odd move to make, and I don't like having my true sdcard in /sdcard/external. what a crock :/
This tablet has to have a way to be rooted, I tried an older version of gingerbreak 1.1 just kept running, never failed, but didn't root the tablet just kept running, like it was gonna root the tablet, kinda weird, I do know that the bootloader is not locked down, my wife works for vizio, the company gave there employees a tablet for free
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!
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment Rockusb.rar
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
Thanks for the info. Will be giving it a go later today
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
when in doubt go back to the forums. I can not get the inf in the rockusb to install. "Installation for this file type not permited" . So I'm stuck, the program will not complete. I'm on windows 7 so maybe the driver is for another system. If you can provide futher help, Thanks in advance.
New approach
Ok I cannot get the drivers to install on my computer. Window 7 seems to default to its own driver and will not let me install the rockusb drivers.
With that said, I have the system Update.img and was wandering if the img itself can be rooted and then updated to the tablet. If this is possible and anyone with the knowledge is willing I will upload it. Or if someone is really patient and would like to walk me through the process and I will attempt to do this myself
No Help
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
Can't tell your level of PC knowledge so if you already know this don't get offended. The .inf is editable and there are areas in there that allow manufacturers to prevent installation on some OS's to prevent conflicts. Make a system restore point or better yet a backup and then post the contents of the INF somewhere and point the folks here to it and they may be able to help you edit it to install. Regardless, you'll have to use the "have disk" option instead of letting windows search for a driver even if you get the edits right. And the usual disclaimers about me not being responsible for any issues with your equipment as a result of this are in effect.
tannerjames said:
So with no help I assume this is dead. I have a usb driver package with an .inf file a .sys file and a .cat file but this will not install on my computer thus leaving without a clue and no help. Have seached for a way to force install this driver command line install right click and install the inf. Nothing works so if someone wants to throw me a bone, thanks, if not I guess this thread is dead.
Click to expand...
Click to collapse
I was able to root using the instructions above although i don't think you need the rockusb drivers. You just need the usb drivers that come with the android sdk. I am on Win 7. Thanks for the above info for rooting.
I was able to install ROM manager and now proceeding to backup ROM and upgrade using this guide: cant post link as forum is preventing, but search for rom flash guide on androidpolice com.
Hope this helps.
Big thanks to this thread to get me going...!!!
?
could someone please, Barney style, Explain how I am supposed to select the android_winusb.inf because my steps are as follows. Right click on device p771a in device manager, browse my computer, let me pick from a list of device drivers, have disk, point to the google usb driver (C:/Android/android-sdk/extras/google/usb_driver) select the android_winusb.inf open. Hit ok, (The folder you specified doesn't contain a compatible software driver for you device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems). Hope this helps explain my troubles. Glad that my thread is helping others to root this device but it does not work for me.
Could it really be that simple?
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
tannerjames said:
Found in another forum about the nexus 7 when connected to the pc there is a presistent notification that allows you to change the connection type from mpt to camera which will give you adb access and the tool from this thread works great. Thanks for the help guys, got my root on
Click to expand...
Click to collapse
Glad you could figure it out...
I was not able to use the ROM Manager to backup the ROM since the device is not supported on this tool, but see below for how you can obtain the stock image.
I've tried to flash multiple different ROMs using RKAndroid to the tablet, spending days on this, with no success. The tool itself works great and I am able to flash the ROMs since it supports the RK29 chipset which I believe this tablet has. The stock ROM for this device is available from the manufacturers web site (the link is available when you go to Settings => About Device => System Update, hkcdigital dot com slash update slash update.img), if anyone would like to take the stock rom and upgrade it to Android 4.2/JB.
I was able to unpack/repack the stock image using the wendal image tools and modify / cook the ROM using Android kitchen method described elsewhere in this forum. Rockchip Batch Tool is another great utility to flash custom ROMs to this device. Also, If you put the ROM as update.zip or update.img file on the microSD card, the tablet will take it and flash the image as long as it is in the right format. Ofcourse you can put the tablet into recovery and restore from there as well. I've found that the stock image (update.img) has the following file/folder format when unpacked: /RK29xxLoader(L)_V2.27.bin, /package-file, /parameter, /recover-script, /update-script, /Image/boot.img, /Image/system.img, /Image/recovery.img and /Image/misc.img.
Is it possible to upgrade this tablet to Android 4.2 or atleast Jelly Bean? Would be very helpful if someone is able to do this. The most success I've had so far is with the custom ROM Oma_Odys_Loox_JB_4.1.1_v1.2.2a flashed using RKAndroid. It flashed the tablet fine, updated the boot etc. On tablet boot I am able to see the new logo, but then the it doesn't go anywhere from there. I think customizing this ROM or the stock ROM we should be able to get the new OS on to the HKC tablet. I've given up for now since I don't have the time to spend on this anymore. If someone is able to do this, please post the instructions or upload the custom ROM, as I am sure it will benefit a lot of people and will be much appreciated. Happy cooking!
Thanks!
jawadshaik- rom manager
If you have successfully flashed rom manager on this device could you post the steps you took to do so. What version? Manual flash? The program itself says there is no recovery for this device.
Sorry jumped the gun on that last post. Thanks for the info
What's the secret to keeping the battery from draining so quickly while it's idle? I just got this and see it drained about 40% in about 2 hours I think and I wasn't using it.
tannerjames said:
I have used many different methods to root phones even a few tablets for friends. But I have bought a HKC 7 inch tab from walmart. Great starter tablet by the way. I have found no information what so ever on any forum about this model. It has decent processor power and runs rather smooth. Alas there is no way to root this thing to reach its full potential. I checked around on the net and found nothing, none of the one click apps work on this model. Adb does not recognize the tablet either. I've put in the tablet ID into the adb_usb.ini still no device found. I'm not looking for anyone to just hand me the root process on a silver plater, though that would be nice, but any help moving me in the right direction would be appreciated.
Click to expand...
Click to collapse
@jawadshaik
Just out of curiosity, when you were flashing that Rom that brought up the boot screen, did you do a wipe/factory reset from recovery mode before flashing? I have no idea if that would help or not, but most if not all roms require a data wipe before flashing... Just curious if you had tried this as I have heard of this happening on other devices because a data wipe wasn't done first. Might be worth a shot if you haven't tried it already, just a thought
Sent from my Huawei u8651s using xda app-developers app
Krytical said:
I rooted one of these for a friend at work,
sourceforge.net/projects/androidroot/ is the root that I got to work.
and I've attached the driver that the manufacturer provided me when I requested a driver for development purposes.View attachment 1468367
Here is how I got it rooted
1. Installed Java JDK and Android SDK.
2. downloaded and extracted Manufacturer driver from Rockusb.rar and right clicked on the .inf file and selected install.
3. Opened Android SDK manager, installed Android SDK for version of tablet, and SDK tools, and Google usb driver from extras.
4. Enabled usb debugging mode on the tablet, and enabled unsigned apps to be installed.
5. Connected the tablet via USB
6. when the tablet shows up in the device manager as P771A I selected to update the driver manually, and selected the google USB driver from the android SDK.
7. Downloaded and extracted the android root I listed above.
8. Run android root and when it says "press any key to continue" it is waiting until the device connects to the computer again, as it could be rebooting, and one time when the tablet reboots, there is no text, just a black screen, but it does eventually connect and you can continue.
Also. I extracted the root to my desktop. when I ran as admin, it did not work, because the files were not on the administrators desktop, only mine, so it might be a good idea to extract the root to C:\ drive, so if you need to use admin, it won't fail
hope this helps
-Brandon
Click to expand...
Click to collapse
So after doing working on this a while, I've finally figured it out. Here are some caveats:
1. You can't do this on a Mac or Linux box. Don't ask me why, you just cant.
2. You have to turn on USB debugging, change the Security to allow Unknown sources and MOST IMPORTANT: when you plug it in, you have to change it to "Connected as a Camera". Putting it in storage mode doesn't work!
HOW TO INSTALL THE PROPER DRIVER & ROOT THE DEVICE:
1. Follow the steps quoted above and download the Google Android SDK, and the Java JDK (from oracle.com/java).
2. When you first plug it in (use the USB plug labeled USB not the HOST one), it complains and will discover a P771A device. When it does, right click on your computer, choose Manage my computer, go to the device manager and then right click on the P771A device. Click "Update Device Driver". Choose "Browse my computer for Driver software". Then choose, "Let me pick from a list of drivers on my computer". Browse to the \adt-bundle-windows-x86_64\sdk\extras\google\usb_driver folder which you would have if you had downloaded and installed the Google Android SDK. A list of 3 drivers will appear when you click OK. CHOOSE THE "ANDROID BOOTLOADER INTERFACE" as the driver. None of the others work.
3. Run the root script batch file mentioned above which can be found here at: sourceforge.net/projects/androidroot
4. The root script isn't really great at explaining so I'll try. When you first run it, make sure your device is unlocked and on the home screen.
5. The first thing it will do is reboot your machine. Don't press enter until your machine comes back up.
6. After your machine boots unlock it and then press Enter again. Your machine will reboot. This time it won't seem to come up but the backlight will remain on.
7. Wait about 30-45 seconds then press enter again. You should get: uid=0(root) gid=0(root) in the command prompt window.
8. Press Enter. You should get:
remount succeeded
727 KB/s (22364 bytes in 0.030s)
Removing changes except ROOT...
Installing superuser...
2288 KB/s (843503 bytes in 0.360s)
9. After about 30-60 seconds, your device should reboot. You'll see a box briefly saying "Android is Upgrading" and you'll arrive at the lock screen. Press Enter to exit the command prompt.
Your device is now rooted and you should see "SuperUser" installed. I promptly installed "root uninstaller" to get rid of Facebook, Skype, and Youtube which my little kids don't need access to. This device doesn't have a bootloader or recovery mode so rooting it doesn't get you much besides the ability to uninstall the system software. Have fun.
This may help someone but on step 2 of the guide on the second page, after you right click your device and go to "Let me pick from a list of drivers on my computer". You then click "Show All Devices" then "Have Disk..." Direct it to the root of the adt-bundle folder you downloaded then you can select from the three drivers. I'm on windows 7 32bit and the drivers didn't show up for me like how it was suppose to..
I also could NOT get any of the drivers in the "manufacturer USB" packet to install... I WAS able to install the google drivers, but that also would not allow ADB to see the device... So still stuck with everyone else...
P771A possible problem
I'm having a similar problem where the USB driver downloaded through Android SDK's -> Extras -> Google USB Driver, tells me that the file contains no information about my device. I noticed in the Sources of SDK, there wasn't an API for 4.0.4, only 4.0.3 then 4.1, so i downloaded 4.0.3 repo.
============================================
my devices is on 4.0.4, and my Kernal is as follows:
3.0.8+
[email protected] #8
Wed Aug 29 09:59:19 PDT 2012
Build Number:
P771A-user 4.0.4 IMM76D user.v402.007 release-keys
============================================
I've also made sure weather Unknown Sources is on, as well as USB debugging.
Might the Kernal be the problem? Also, does it matter weather its MTP or CTP?
Now HKC is telling me that they don't support the ability to jail break their devices
Sent from my P771A using xda app-developers app