ok i have followed the link to download drivers from this site and the install of adb went well. even uninstalling the nook worked fine. driver install worked fine. now the problem i am having is that when i run adb devices command it is not bringing back the serial number. I am not sure where to go from here. any help would be greatly appreciated!!!
also the comp is not recognizing my nook at all.
p.s im pretty much a n00b
HELP!!
Related
Ok am I doing something wrong? I've been using adb on my phone for awhile but when I connect my wife's phone and type adb devices, her doesn't show up. USB Debugging is clicked on and we're both on Cyanogen v4.0.4
Please advice
For some reason I had the same problem with my wifes Magic. I had to install the drivers for her phone, then they both worked perfect for me. Not sure if it'll work for you but that's how I had to do it.
Clinton
Thanks for the reply man I had to uninstall the both android and usb mass storage drivers and reinstalled them and it worked!
I'm trying to root a Kindle Fire and I don't know why but I'm having alot of trouble getting ADB and drivers set up right on my laptop. I'm not sure which packages I need to install in SDK manager. When I try to use the adb command at a command prompt it says command not recognized and I'm thinking it's because I don't have the right packages installed or installed right.I didn't have to go through this when rooting a couple other phones I've done.
http://forum.xda-developers.com/showthread.php?t=1399889
Thanks so much for the link. I ran it and I'm having a hard time getting it to recognize the device. It said it installed the correct drivers but when I attempt the temp root it will not recognize the device, make sure device is plugged in and turned on.
With kindle unplugged Go into ur comps device manager and remove the kindle fire...then install drivers. Then plug it back in. I had same problem. Windows auto installed some generic driver when I first plugged it in before installing correct driver. If still not working try a diff usb port on computer. Hope that helps
I finally got it. Thanks very much. I finally had to switch computers for some reason to get it to work.
I was able to use the AOSP Stock without any issues, however I am not able to figure out how to root to install the CWM. The ADB command is not working from my computer. Any help is appreciated.
Thanks
If it's khanning88's ROM, try running the terminal commands as noted on the 1st post of this thread http://forum.xda-developers.com/showthread.php?t=1808017 and it should work.
I also had problems running adb because after enabling USB debugging, windows didn't recognize the adb connection. i uninstalled drivers, put my device into debugging mode and reconnected. All problems were solved.
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
vipergrm said:
Hi folks,
I really hope someone can help me here. My TF300T is currently rooted and unlocked with the lates CM 10 (4.2.2) build. I am having some issues with reboots since upgrading to 4.2.2 and I would like to change the ROM. I am also trying to flash the upgraded TWRP recovery but unfortunately I am unable to do this. When I boot the TF300 into the menu where you have to select the USB icon normally this would load the ADB driver but my PC comes up as 'USB device not recognized'. I've tried this from two different PCs' with the same outcome. I won't be able to flash recovery or ROM unless I get this sorted. I should note that when I connect the TF300 while it is booted the PC recognizes it no problem. It also works in USB debugging mode so I'm very confused as to why it won't work from the boot menu. I've tried manually installing the drivers, installing Asus PC Sync and also re-installing SDK tools; all to no avail. Any ideas on how to fix this would be greatly appreciated. Thank you!
Click to expand...
Click to collapse
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
jgaf said:
When you get the USB device not recognized, go into device manager locate the device on the list right click and then click on update driver. When it asks you selecte that you want to find the driver files on the computer, then select the option to look at the list of drivers. Once in the list there should be a driver for ADB try installing it and see if it works. That's how I got my adb to work while on recovery.
Click to expand...
Click to collapse
Thanks but that still didn't work for me. What exact driver did you use? Thanks!
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
jgaf said:
Don't remember the name exactly, but from what I can see right now on device manager these are the details on the driver:
ASUS Android ADB Interface
Driver Provider: ASUSTek Computer INC.
Driver Date: 7/17/2012
Driver Version: 4.0.0.5
Digital Signer: Microsoft Windows Hardware Compatibility Publisher
Also, have you tried removing all previous ASUS drivers and trying to install them again?
Click to expand...
Click to collapse
Thanks again. I will give this another go later and see what happens...
Any luck?
jgaf said:
Any luck?
Click to expand...
Click to collapse
I haven't had the opportunity to try it again just yet. I plan to do this tomorrow night on my nightshift in work. I'll let you know then. Thanks for asking
Tried tonight again and still no luck. I know the driver installed on this machine definitely works because its the same one that worked last week when I tried it. Oddly, the ADB driver picks up ok when I'm in the OS with debugging on but I don't think i would be able to flash whilst logged on to the OS. This is concerning because the CM10 ROM 4.2.2 which I have installed a the moment is firing up random reboots. I know it's still in experimental stage and I'm not complaining but it would be nice to change my ROM when needed. Below is a couple of screenshots of the problem I am having.
I had a similar problem my adb worked flawlessly when the OS was running, but it wouldn't get recognized when in recovery (fastboot worked too). So, what I wrote earlier solve my problem. Sucks it didn't work for you. Anyways do you have a recovery installed? If you do why can't you use that one? Also, I'm pretty sure you can install recovery when the OS is running, even from android terminal emulator in the pad.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Thanks again. I did do a backup thankfully and currently it is restoring. I will try to see after restoring the backup if it works. Another method I have found to repair the bootloader is the NVFLASH method, although this does scare me a little! I would be very interested in trying those drivers you have as mine are older but so far I have been unable to find anything newer, despite extensive searching. :crying:
Thanks for your help thus far! :good:
Looks like I'm finally getting somewhere. I decided that I would try connecting directly to the TF300 instead of through the keyboard dock and oddly this worked. The driver is now loading correctly and I am able to flash again! Now to choose a JB ROM... :good:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
I am not familiar with adb when device is off or fastboot. So if you are desperate follow one of the guides on un-bricking the g2 (which will bring it back to stock and wipe data) but then you'll be up and running and you would just have to re-root and unlock it
djohnson308 said:
Okay guys, I've exhausted all my own resources and would really appreciate your help.
Long story short- I have TWRP installed with NO backup files or roms on the device. I made a TWRP backup and put it on my PC pre brick...
When I turn the G2 on and plug it into my PC i get an unknown deivce which has the hardware id: USB\VID_18D1&PID_D001&REV_0232
I attempted to use the TWRP sideload with no benefit- if i can use ADB i know how to push my image but i CANNOT get adb to see the device..
any help will be greatly appreciated!!!
-THank you
Dana
Click to expand...
Click to collapse
Assuming that you can boot into TWRP, then you probably just need to install the right drivers. Search around the forums.
Stock lg drivers don't seem to recognize phone in recovery mode install pdanet and then connect phone to pc while in recovery mode and open pdanet app in pc and follow instructions to install lg drivers and then pc will find ur device it worked for me when l had the same problem.
Sent from my LG-D800 using xda app-developers app
So i cannot seem to get my computer to install pdanet. i searched for a unbrick thread and found one.. i waited an hour for it to download a 2gig file, the lg program said it was pushing to phone which took 15 seconds (no way it pushed 2gigs that fast) then it said reboot the phone then do a hard reset... i went to do that and the phone just pushed me to TWRP. ahhhh losing my mind
What's the message when installing pdanet
Sent from my LG-D800 using xda app-developers app
access denied followed by x64 issues... Im the domain admin, and the website says its good for x64...
well lets see here are you on windows 8 or 7 ?
this is what i did
I put the phone into fastboot mode then connected it to the computer, well now the customer doesn't recognize it and you should have the drivers installed then what you want to do is search for device manager, look under the Universal Serial Bus Controllers and you will see USB connect with an "!" what you need to do is right click on it then go to update drivers, from there you need to select browse my computer for the drivers not the automatic one then select "let me from a list of devices. next you want to unchecked show compatible hardware now look for Lg in the manufacture list and there should be one that says something about "adb interface" and select it.
Now try using a cmd windows and adb. what i did was i download a fastboot.zip it has adb interface in that zip file then i opened a cmd prompt in that folder by holding shift and right clicking. now once it was open i typed adb list and it recognized my phone
then i went into twrp and adb sideload and I side loaded a stock zip now you be fine and back to square one.