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
Previously, I was on TRON 1.2 and had no issues with ADB and/or USB tethering.
Since updating to TRON 2.0, I have not been able to tether my usb connection via adb (ive tried clockworkmodtether, pdanet, klink).
USB debugging is enabled. I tried disabling, rebooting, and enabling again, but I have had no success.
When I run "adb devices", it tells me my device is offline.
BTW, I am on windows 7 64 bit.
Thanks!
trud9340 said:
Previously, I was on TRON 1.2 and had no issues with ADB and/or USB tethering.
Since updating to TRON 2.0, I have not been able to tether my usb connection via adb (ive tried clockworkmodtether, pdanet, klink).
USB debugging is enabled. I tried disabling, rebooting, and enabling again, but I have had no success.
When I run "adb devices", it tells me my device is offline.
BTW, I am on windows 7 64 bit.
Thanks!
Click to expand...
Click to collapse
To use adb in 4.2.2, you need the most recent version of Android platform-tools from the SDK. Open the SDK Downloader like you did when initially installing adb and update the platform-tools package. (Make sure you kill any instances of the current adb process/daemon running on your computer.) It should be able to connect after that, although you'll be asked to authenticate it on your phone the first time you try.
El Schisne said:
To use adb in 4.2.2, you need the most recent version of Android platform-tools from the SDK. Open the SDK Downloader like you did when initially installing adb and update the platform-tools package. (Make sure you kill any instances of the current adb process/daemon running on your computer.) It should be able to connect after that, although you'll be asked to authenticate it on your phone the first time you try.
Click to expand...
Click to collapse
Thank you, I updated my sdk and its working like a charm!
Hi guys i have a galaxy s3 xxella and running CM 10.1 custom rom developer options enabled and usb debugging too. and root access open for apps and adb. oh and phone is fully rooted and using custom recovery. everything is normal like you see but when i trying to reach adb my device status is offline it shows and i cant do anything.
CM10.1 is based on Jelly Bean 4.2.2. In order to be able to communicate in adb mode with a 4.2 device, you need to update your SDK. In your Android SDK folder, just go to adt-bundle-windows-x86_64\sdkmanager.exe, and install the new API version and SDK platform for 4.2.2.
Also, if you set up the Environment Variable to reach adb easily, know that in the new SDK package it has moved from the "tools" directory to "platform-tools", so change the variables accordingly.
When connecting to your device in adb, you should now see a popup window on your phone asking you to confirm key exchange between computer and device (that's also new in 4.2.2)
Finally, if you are using a Windows App called SnapPea, uninstall it as it replaces adb with a crappy dysfunctional exe.
th3m1773n said:
CM10.1 is based on Jelly Bean 4.2.2. In order to be able to communicate in adb mode with a 4.2 device, you need to update your SDK. In your Android SDK folder, just go to adt-bundle-windows-x86_64\sdkmanager.exe, and install the new API version and SDK platform for 4.2.2.
Also, if you set up the Environment Variable to reach adb easily, know that in the new SDK package it has moved from the "tools" directory to "platform-tools", so change the variables accordingly.
When connecting to your device in adb, you should now see a popup window on your phone asking you to confirm key exchange between computer and device (that's also new in 4.2.2)
Finally, if you are using a Windows App called SnapPea, uninstall it as it replaces adb with a crappy dysfunctional exe.
Click to expand...
Click to collapse
i will try now thanks for all
Edit: yes dude its all working good now thank you.
Hi guys, I've been tearing my hair out for the past 24hrs trying to get ADB to communicate with my devices (Amazon Fire tablet + Nexus 5x).
I've installed ADB and drivers for my devices. They currently show up as Android Device > Google Nexus ADB Interface (ClockworkMod driver installed) and Android Device > Android Composite ADB Interface (Amazon.com driver installed).
I have enabled ADB on my Amazon Fire tablet (5th Gen - 5.1.3) and USB debugging on my Nexus 5x.
When I run ADB, all it sees is my Fire tablet but says "unauthorized" next to it.
On both devices, when plugged into the computer via USB, I get no message about enabling the computer to access the device etc. They just sit there, charging with "USB Debugging Connected" on both devices.
Could someone point me in the right direction to get ADB communicating properly with both devices? I originally wanted to use it to root my Fire Tablet to load a different OS on to it, so I used my Nexus 5x to see if that could communicate with ADB but it appears that neither do.... properly anyway.
Another flag that I'm wondering is that in Device Manager, I do have an exclamation mark next to a USB controller - I've found drivers for it (Renesas USB 3.0 Host Controller) - but it came up with an error saying the device cannot start (code 10) - I don't think this is anything to do with my issue as the drivers are installed correctly it appears for the Android devices.
Thanks a lot in advance.
I've done it! I had to delete adbkey from .android folder on my PC - god knows why! all fixed though. yay.
I have a jp5s tablet running android 4.2.2. It is a prison issued tablet. USB debugging is not enabled, and you can't enable devlopers options. Bluetooth works but app installation is blocked for security purposes. And the ability to allow unknown sources is disabled. Recovery mode only has reboot now. There is no fastboot so adb on windows will not connect. My only idea is maybe a picture or video file that runs a script to allow USB debugging, or installs an apk(a file manager). Also I'll pay for one that will set my devices year back to 2011 or so. Please any help or advice. Maybe a windows program that will force connect adb somehow.
Yeah you can go to settings but its very limited, pressing build number only brings up a list of installed apps.
Nothing google at all its a prison tablet that's the issue I want to install apps
inameasone said:
I have a jp5s tablet running android 4.2.2. It is a prison issued tablet. USB debugging is not enabled, and you can't enable devlopers options. Bluetooth works but app installation is blocked for security purposes. And the ability to allow unknown sources is disabled. Recovery mode only has reboot now. There is no fastboot so adb on windows will not connect. My only idea is maybe a picture or video file that runs a script to allow USB debugging, or installs an apk(a file manager). Also I'll pay for one that will set my devices year back to 2011 or so. Please any help or advice. Maybe a windows program that will force connect adb somehow.
Click to expand...
Click to collapse
Hi , can you post video on YT in order to see what is actually happening your device.
Yes I do, I need to install a 3rd party app