Fun ( or not do much ) with ADB. Help! - Eee Pad Transformer General

I have been trying to get my Tf101 to connect to ADB for a good 6+ hours now. I have installed the asus software and drivers, I have installed the drivers that I found here for the APX, ADB, ext stuff and I still cannot connect. No matter how many times I kill and start the ADB server or try to use the ADB exe from the SDK or use the one from viper mod it's just says
List of devices attached
Nothing else is displayed.
got device manager to now have an android device tab with the asus transformer adb interface under it. still no luck.
BTW, window 7 pro x64.
Solved, apparently the tablet needs to be in USb camera mode.

Related

Rooted KF not started This device cannot start. (Code 10).

Hi,
Could REALLY do with some help here ... starting to pull my hair out. Rooted my KF with the steps from http://forum.xda-developers.com/showthread.php?t=1410766. Got through the root and the process hung on the recovery install.
Now my KF just shows the Kindlefire booting screen. I've tried loads of edits to the drivers re-installed many times, etc ..
In device manager, I see the device as Android Phone / Android Composite ADB Interface. The problem is that the device status always stays at: This device cannot start. (Code 10).
adb returns nothing. It's like I can't connect to the device at all.
Can ayone please help?
i think its stuck in fast boot??
http://forum.xda-developers.com/showpost.php?p=20729347&postcount=5
Tried the various restarts as suggested in the thread. No luck.
Device Manager still has a problem with the device. KFU can't connect or see the device.
I've tried re-installing the drivers several times, but always get the same result. Searched the threads for a similiar problem and it seems most issues are when people get to the the Yellow Triangle page. I'm not getting that far.
Seems to me to be a driver problem, but I can't trick Windows into figured it out.
follow and join this thread:
http://forum.xda-developers.com/showthread.php?t=1413495
i don't want to write everything twice
Still not working. tried that link and everything in it. Been struggling woudl this for a few days now, so any help would be appreciated.
When kf is pluged in right click my computer then click manage then device manager there should be a yellow ! Next to a device. What device does it show next to it
Edit; sorry answers in the question. Lol
Keep it plugged in. Hold down power for 30 secs turn back on
What does your pc say
Sent from my Kindle Fire using xda premium
NewKindleUser said:
Still not working. tried that link and everything in it. Been struggling woudl this for a few days now, so any help would be appreciated.
Click to expand...
Click to collapse
some more information would be helpful
os/bit of computer ?
have you tried to remove the old drivers ?
http://support.microsoft.com/kb/315539/en-us
which drivers have you used ?
in the meantime there is a new kfu available 0.9.2 which has a new driver installer.
http://forum.xda-developers.com/showthread.php?t=1399889
would download it, extract to c:\ and rename to "kfu" cause it don't likes spaces in the pathname - sometimes. run install_drivers.bat
then run the utility with run.bat and try to set bootmode to normal (option 1)
the 3 status messages from kfu may also be helpful for us
this post from vashypooh might also be helpful:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
Thanks for direction and feedback.
I had previously installed the drivers with kfu 0.8 and 0.9.1.
I'm using Win7 x64 running in a VM (I have a MAC) as well as WinXP 32.
I've downloaded and installed the drivers from the latest KFU. When I connect the KF, it appears under the USB Controllers Group in Device Manager with a Yellow Warning Triangle. KFU cannot connect:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown
NewKindleUser said:
Thanks for direction and feedback.
I had previously installed the drivers with kfu 0.8 and 0.9.1.
I'm using Win7 x64 running in a VM (I have a MAC) as well as WinXP 32.
I've downloaded and installed the drivers from the latest KFU. When I connect the KF, it appears under the USB Controllers Group in Device Manager with a Yellow Warning Triangle. KFU cannot connect:
ADB Status: Offline
ADB Rooted: No
Boot Status: Unknown
Click to expand...
Click to collapse
are both win systems running on the mac ?
that will not function - someone ported kfu to mac - will try to find it for you
here it is:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
The WinXp isn't on the MAC. But the Win7 one is.
I'll try the MAC port as well.
NewKindleUser said:
The WinXp isn't on the MAC. But the Win7 one is.
I'll try the MAC port as well.
Click to expand...
Click to collapse
then you have 2 options:
1. try the mac port
2. use winxp machine and be prepared for a little hassle with the drivers
good luck !
I've seen it show up as unknown USB device before. You can't install the drivers when it's in this state. Usually doing a hard reset on the device (hold power for ~20 seconds to turn off then turn it back on) fixes the device and it will show up as either Amazon Kindle with a yellow exclamation (without drivers) or as ADB Device or some such if you do have the drivers. If it shows up as Amazon Kindle without drivers, install them (right click, update drivers, browse your pc, point it to the drivers folder inside KFU). You should then be able to run KFU option 1 and select Bootmode Normal.
If you can't get that to work, download the android SDK on your Mac, use the SDK manager to download the Android platform-tools, open up a Terminal, cd to that platform-tools directory, and run
./fastboot -i 0x1949 oem idme bootmode normal
Which should get you back in normal mode.
I registered just to say that I thought I had bricked my KF (it was just stuck in fast-boot). I tried all of the driver fix stuff but the Kindle Fire Utility still said that no Kindle could be found. I tried your suggestion, skourg3, and it worked perfectly. (slight addendum for the uninitiated: the command is fastboot -i 0x1949 oem idme bootmode normal).

ADB on TF101

Yeah, its another 'ADB not working on device xxx' thread.. but this one really has me stumped.
Device in question is a TF101, PC in question runs Windows 7 64-bit.
PC has been used successfully to develop android apps. for a Samsung S Plus, with the entire toolchain working.
Same PC, running VMWare, virtualizing XP (32-bit), has also been used to develop/debug with the TF101.
Now the problem. Natively (without VMWare), I have been completely unsuccessful getting the TF101 to be recognized by ADB.
What has been tried:
- TF101 USB drivers from Asus
- TF201 USB drivers from Asus (which also include the TF101 drivers from the look of the .inf files)
- Hand-edited .inf file from the standard android ADB driver
- Adding the VID (0x0b05) to adb_usb.inf
- Uninstalling (and deleting the driver) for anything related to android devices (Samsung, and Asus)
So what happens is that the device does appear in device manager, with 'USB Debugging' checked on the Android device.
With one of the driver combinations I end up with 'Android Composite ADB Interface' in Device Manager, but for some reason its under a 'Samsung Android Phone' Folder, this may well be part of the problem.
No matter what I try, 'adb kill-devices/adb usb' always shows 'error: device not found'
I am two solid days into this now, after reading just about every TF101/ADB thread that google knows about.
Anyone else experienced this?, and might know how to resolve it?
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
baseballfanz said:
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
FWIW, I had the same issue. I installed the USB drivers from Asus and could never seem to get ADB to "see" the TF101.
So I ripped them out and installed the full ASUS desktop PC suite from their website. ADB now sees my TF101 just fine. I uninstalled the suite after I had the connection working and ADB still connects to my TF101 without issue. The Transformer PC suite is on the same download page as the stand alone driver.
If you can't find it, PM me and I'll get back to you with a link.
Col.Kernel said:
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
Click to expand...
Click to collapse
I too was using ADB already on my N1 but couldn't make it work with the TF.
After reading and following directions on that thread I got it working.
He might not need instructions to set up ADB from scratch but there's good infos about the Asus PC Suite.
Step 7
Basically same as what you just posted and same as what I did to get it working.
I can confirm that too that installing ASUS SUIT works better than just installing drivers, I don't know why but it does. It's the same with my phone. Sometimes installing usb drivers do not work but when I install Samsung kies then somehow that works better even though it includes the same drivers I am installing as stand alone which do not with properly.
Sent from samsung vibrant
Same thing happened to me had to buy a new cord.... does the computer recognize it at all
Sent from my Transformer TF101 using Tapatalk
im not sure if it would help but everyonce in a while ill have a hard time with my adb connection and ill start up wireless adb and can conect fine from that. i dont know why i think in wireless you use ip address on wifi so it might recognize and connect different.. of course this depends on if you want to use it and is alos hardware dependant mainly wifi.

Not able to ADB my STR

Hello folks,
I had a WinXP computer, and I installed android SDK, and I was able to connect to my nook via ADB. As it was aging and having fan problem, I bought a new Dell (i5, win7, 4Gb RAM, 500 Gb HD). I installed android SDK, but never tried to ADB my nook. Yesterday I tried it, and whenever I try to connect via IP, or use adb devices, nothing shows up. I tried messing with the firewall, but it was not working at all.
Does anybody have any idea to help me? And also on how to get my firewall back (removed Norton, which I believe is a bloating spyware, and installed avast antivirus, but firewall was not released either, and it gives a 0x80070424 error).
Try this
Attach the usb cable to the NST and see if it is visible in device manager. Ideally if no driver is installed, you would just see it there with an exclamation mark.
Then follow ros87's instructions here. If adb_usb.ini doesnt exist create it.
Then from device manager, update device drivers for the unrecognized nook and point it to the i386/amd folder within the android drivers folder.
once that is done, restart adb, run "adb usb", then try "adb devices". If it worked it should show you the device.
ADB wifi was easier. In fact, it was such a long time since I last used it (before 1.1.1), that I forgot to add the adbwireless button to turn it on.
But thanks anyway. I've never dared to use USB due to inner messiness of the process.

[Q] Adb sideload nexus 10 not recognized

My tablet is in developer mode, USB data bugging is clicked on. In storage, MTP is clicked on. Using the latest Android SDK along with the latest Google Win USB drivers (also different cables, different ports, uninstalled and reinstalled all drivers and software, turned on and off debug, debug authorization.. Just about everything I can think of.) Also, no, not rooted, fully stock. Been searching for a few days for this problem that occurs while trying to upgrade to Kit Kat 4.4 from JWR66Y 4.3 on my nexus 10.
Plug in my n10 normally and WIN7 will see it in the device manager as Android Device, Android Composite ADB Interface, Hardware Ids =
USB\VID_18D1&PID_4EE2&REV_0226&MI_01
USB\VID_18D1&PID_4EE2&MI_01
Boot the n10 into recovery and the adb sideload, the n10 shows everything correctly and waits for the adb sideload file. CONNECT THE USB cable and Win7 does not recognize the device. Tries to find a driver for 'other devices, nexus 10' but eventually returns with no driver found. Tried installing from specific directories (new google usb driver download), letting it search windows update evewn search my entire hd. It cannot locate a driver. Device manager shows an entirely different Hardware Id for 'other devices, Nexus 10' =
HARDWARE IDS (OTHER DEVICES, NEXUS 10)
USB\VID_18D1&PID_D001&REV_0226
USB\VID_18D1&PID_D001
I did a search with this information and found others had this ID/problem with their Nexus 7 during the Jelley Bean upgrade!
http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
There is no Nexus 10 in this file, but the second line of 'google nexus (generic)' list the ID that I have when booting normally.
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
I assume that if I replace this number with the ID I see in adb sideload mode (USB\VID_18D1&PID_D001) I should be able to install the correct USB and ADB drivers as others did on their n7 (shown in that link)?
My problem is identical to tbe description on that link, but I am guessing at the fix for the n10. This sounds like the solution to me, but I am also worried if it could be a sign of a bigger broblem or might brick my nexus. So any help would be appreciated!
Thanks all!
Ed
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Duplicate deleted
KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Wow, I hope someone finds this thread and it saves them the headaches and searches I have been through. Worked just like you said, installed this adb usb driver and it picked it right up. I wonder why google couldn't get the google driver to read their own nexus 10 tablet!
Now running Kitkat 4.4 with no data loss, thanks to you Kira!
Thank you!
Ed
KiraYahiroz said:
I tried changing the ID initially as well but then adb throws errors about the ini file not being verified. In the end I installed these to get the adb drivers properly installed: http://koush.com/post/universal-adb-driver
After that Windows finally properly recognised my N10 (and the command adb devices also showed it could see the device) and I was able to sideload kitkat.
Click to expand...
Click to collapse
Thank you, been banging my head around to try and find a fix, worked like a charm for sideloading KitKat.
cheers
Oh my god, pushing this thread because I almost needed 6 hours to root my Nexus 10 with other ADB drivers but this one worked!

Error 10 : ADB Drivers

I tried a hell lot to install ASUS Zenphone adb drivers on my PC( on Windows 7, 8 and 10).
I got the same error everywhere. Error 10. Driver not installed properly.
I searched the Internet for hours without success.
I hope XDA community has some answers.
i got the same problem as you , my zenfone 5 detected as unknown device , i solved with adjusting usb when plug in to laptop like slowly inserting the usb to laptop port and keep adjusting untill its detected. weird dont know why its happen like that , all other phones that i've connect to my laptop detected with easy except for that zenfone 5.
Did you already download from Asus Official Website ? @ceomaverick
Try use this one.
Step:
1. Download and Extract the file from .ZIP
Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
2. Go to Device Manager, right click ' Asus Android ADB Interface '.
3. Update Driver Software, then choose ' Browse from My Computer for Driver Software'
4. Select Folder where you extract the .Zip file, check 'Include Subfolder' then klik 'Next'
5. Wait while system searching and installing the driver.
6. Finsih
Hope it will help you.
Thanks
OK, some progress here.
Find the Asus 8.0.0.2 drivers or the 8.0.0.3 ones.
Do the Add Legacy Hardware thing for the ADB Composite Interface -- it will install as "Code 10" not started.
Highlight that device and select update device...ask it to search windows online for the update.
In Win7 this will take a long time, in Win10 it will take just a second BUT be nicely hidden. Click View Optional Updates and then click Driver Updates and then select the ADB Composite interface.
In Win7 it completes quickly w/o reboot. In Win10 you have to reboot.
But with that, the ADB Composite Interface will function.
Now do the Add Legacy hardware thing for the Bootloader -- again, installs as Code 10
Put your phone into fastboot
Select the Bootloader device and do the update-from-windows thing.
Win7 does it directly, Win10 you have to navigate through the Update wizard as before
Now the fastboot interface is presented as working...

Categories

Resources