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!
Related
Hello,
Been trying to get droid explorer and adb to reconize my tilt2. Here is run down of what i have done.
on an up to date windows xp box
installed latest pdanet for android
installed latest droid explorer
connected my tilt2, it installed the adb driver but wont install the 2 cdc asm drivers
run droid explorer and it doesn't reconize the phone. i have the phone in debug mode and notification does come up.
on the android side i am running
frx 5
wistilt2 test kernel
highlandsun ril driver
btw, tried to run the busybox installer and it says it cant gain root access.. i thought all these builds have it by default or am i missing a step or two. I have superuser installed.
portreeve
All you need is the XDA device to install. The other two, CDC etc are not needed.
Is the adb service running? See if adb.exe is in task manager. You only need pda.net for the drivers, the software will mess with adb itself. So make sure their software is not running.
What do you mean busybox installer? For Titanium Backup or...?
You don't need SuperUser, that is an app that is more for security - if something asks for SU, it'll let you allow it thru the app. Yes, all our HaRET builds are rooted.
portreeve said:
Hello,
Been trying to get droid explorer and adb to reconize my tilt2. Here is run down of what i have done.
on an up to date windows xp box
installed latest pdanet for android
installed latest droid explorer
connected my tilt2, it installed the adb driver but wont install the 2 cdc asm drivers
run droid explorer and it doesn't reconize the phone. i have the phone in debug mode and notification does come up.
on the android side i am running
frx 5
wistilt2 test kernel
highlandsun ril driver
btw, tried to run the busybox installer and it says it cant gain root access.. i thought all these builds have it by default or am i missing a step or two. I have superuser installed.
portreeve
Click to expand...
Click to collapse
I didn't have a problem, My drivers installed automatically for me, but I'm using Win7.
You don't have to have pdanet or superuser for DroidExplorer to work.
Goto your device manager and see what device is listed under ADB interface. My Rhod300 shows up as a HTC DREAM.
arrrghhh said:
All you need is the XDA device to install. The other two, CDC etc are not needed.
Is the adb service running? See if adb.exe is in task manager. You only need pda.net for the drivers, the software will mess with adb itself. So make sure their software is not running.
What do you mean busybox installer? For Titanium Backup or...?
You don't need SuperUser, that is an app that is more for security - if something asks for SU, it'll let you allow it thru the app. Yes, all our HaRET builds are rooted.
Click to expand...
Click to collapse
Sorry arrrghhh, I had the window sitting open, and thought I had hit submit... lol
i was able to install on a windows 7 box and it picked up the drivers but when opening up droid explorer it still shows no devices found. any other advice?
portreeve said:
i was able to install on a windows 7 box and it picked up the drivers but when opening up droid explorer it still shows no devices found. any other advice?
Click to expand...
Click to collapse
Did you try mine? Remove pda.net, once you have the drivers no software is required from them.
Plus, you might also try the good ole reboot, and ensure that adb.exe is running in the task list.
All things I suggested previously...
yes, i've done the suggestion. It shows its connected. Under device manager there is an android phone, under that there is android adb interface but nothing under that. I don't know what else to do. Is there something i am missing on the android side?
and adb is running in taskmanager.
portreeve said:
and adb is running in taskmanager.
Click to expand...
Click to collapse
portreeve said:
yes, i've done the suggestion. It shows its connected. Under device manager there is an android phone, under that there is android adb interface but nothing under that. I don't know what else to do. Is there something i am missing on the android side?
Click to expand...
Click to collapse
and you've rebooted?
I'm out of ideas, I've installed adb on tons of computers, win7 xp etc and all work flawlessly. It is a pretty advanced debugging tool, it's not very easy to install or use...
yes and i have rebooted twice now. still the same thing.
Boot android on phone.
Plug phone in.
Run Windows update.
Check device manager to make sure everything has drivers installed.
Run DroidExplorer
phone will show up as 00000000 in DroidExplorer
Reinstall DroidExplorer if problem persists.
Oh and there should be a device or driver in device manager called XDA, if memory serves me correctly.
Had the same problem about a month ago... downloaded PdaNet from the Marketplace here and it established the connection so I could use the USB to my phone. I didn't have to run it or buy it though .. just install it.
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
Has anyone been able to access their touchpad via ADB on with CM7 Alpha?
If so, what's the trick. I'm running Win7 Pro 32bit, Android SDK is installed with the latest Java 1.7 and USB debugging is on and displayed in notification.
FYI - I'm used to using ADB with my droid eris on GSB so I've tried most of the known stuff. Are there ADB drivers for the TouchPad around?
Thanks in advance.
All ADB drivers are in essence the same, you should be able to use the official ones Google releases with any device.
To get ADB running with my TouchPad(Windows 7 x64) I had a USB Mass Storage Device with the hardware id(USB\VID_0BB4&PID_0C02&REV_0227) I had to go an change the device driver to a USB Composite Device, once I did that the ADB interface showed up and I was able to install the driver.
The mass storage device I changed was this one (USB\VID_0BB4&PID_0C02&REV_0227) and not this one (USB\VID_0BB4&PID_0C02&REV_0227&MI_00).
Here is a link to the Official ADB Google driver http://api.ge.tt/0/8FtSNo8/0/blob/download you may need to force the driver to install.
Worked perfect. Thanks!
adbWireless ftw. No need for cables/drivers.
https://market.android.com/details?id=siir.es.adbWireless&feature=search_result
This worked for me. No modded .ini file or driver needed.
It detected and installed the"USB Composite Device" automatically.
http://rootzwiki.com/topic/6622-cm7-adb-driver/
win7 x64
Hi,
i have the latest android sdk installed on my pc. If i try to connect my new Yuandao N101 tablet it is not recognized by adb.exe devices. adb.exe is version 1.0.29.
If i kill the adb service and start adb 1.0.26 from SuperOnClick rooter it recognizes the device and rooting works without problems.
As device driver for adb i am using the one included in PDAnet.
I tried to exchange the adb.exe in the android sdk with the 1.0.26 version. After this eclipse/adb recognize the device and are able to install apk files and start them. But after this the connection breaks. Seems that current sdk is unable to work with adb 1.0.26.
Any idea how i can make it for adb 1.0.29 to work with my tablet?
Best regards, Udo
Hi,
no one an idea? I tried a lot today but still am unable to get the yuandao n101 to work with adb 1.0.29. It just did not recognize the tablet.
With adb 1.0.26 everything seems fine - but i have to use the current android sdk. Someon an alternative driver out there?
BTW: I am using Windows Vista x64
Ciao, Udo
Thanks so much for posting this.
likal said:
Thanks so much for posting this.
Click to expand...
Click to collapse
I have the exact same problem with a YuanDao N90FHD in win7 x86. it gets detected in adb 1.0.26 but not in 1.0.29. any solutions? (also tried instaling htc sync but no luck)
After upgrading to 4.2.2, some N10 will not be seen by any computer via USB and the only way to remedy it is to shut off USB debugging. On other devices, the computer will see the N10 even if USB debugging is enabled, but running "adb devices" will show the device as offline. This is a problem with the Nexus 7 as well.
UPDATE: Looks like this is a security feature. You will need to update to the latest version of adb if you want to keep using it with 4.2.2.
Sent from my Nexus 7 using Tapatalk HD
Re: Warning: 4.2.2 Breaks ADB and USB Debugging
adb works fine for me.
Actually, at first it did show up as "offline" but still worked fine. Then I toggled the adb setting, now it shows up as "device", and still works fine.
I had just finished sideloading, then I see this post - you had me going for a second there..
Sent from my Nexus 10 using xda app-developers app
I only had an issue with WugFresh's Toolkit because of it being "offline". With mskip's Toolkit I had no issues though it did state it was offline.
noname580 said:
I only had an issue with WugFresh's Toolkit because of it being "offline". With mskip's Toolkit I had no issues though it did state it was offline.
Click to expand...
Click to collapse
ADB works fine for me with 4.2.2 installed, and I can browse my GNex (toro) from my PC, drag/drop files, etc. All working just fine.
Just update your PC Android SDK to API Level 16 or latest
Android 4.2.2 brought up this limitation owing to security breach by ADB-Savy
To enable ADB on your PC, Update your Android SDK-r16 or LATEST, Update the system path for Platform tools --> Execute ADB cdevices command --> check the Device --> Tap Allow on Pop-up. Thats it!
Android Dev site comments :
"When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer. This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog. This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher."