How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!
I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.
Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?
Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!
I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.
ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.
sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.
+1 for sticky
sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.
Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App
bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.
sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.
bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse
Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App
Related
OK, posted this in the Q&A section with several responses but no real answers. Figured I'd post it here before another section where it might get locked or moved.
Anyway, ADB was working fine until a few days ago. Now it says "error: device not found." Fastboot still works just fine. I've tried everything I can think of to get it working again. I've uninstalled and reinstalled the usb drivers, removed the Android SDK from my PC and reinstalled, wiped and reflashed my device, made sure Debugging is on, and tried getting ADB to work on all 4 of my PC's. All running either Windows XP or Windows 7. No dice. Can anyone help? Thanks in advance.
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
UnderCoverLover said:
The other day it took me about an hour to remember to just turn on usb-debugging and plug it in to the usb drive. I kept going to the fastboot screen instead. Maybe that's your problem too?
Click to expand...
Click to collapse
Thanks for the reply. If you read my OP you'll see that I've made sure debugging is on. In fact, debugging is also enabled by default after a wipe and clean flash. Unfortunately my problem isn't as simple as enabling usb debugging.
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Thanks for the response. I'll give this a shot when I get home. FYI, I didn't change devices. Same Nexus One I've had for the past month. Just one question: When you say,
"In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices"
I don't know what this means. Where can I access this? Thanks!
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
markouk said:
Just a thought but are you remembering to boot up the phone as normal?
As in not into fastboot, etc.
This stumped me for a few hours.
I kept trying to "adb" while the phone was in fastboot or recovery.
Sorry if I'm teaching you to suck eggs.
Click to expand...
Click to collapse
Yeah, I've had the phone booted up normally. Thanks though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MaximReapage said:
Click to expand...
Click to collapse
Thanks a lot.
deprecate said:
Have you gone from one phone to another? When I made the switch from a tmo->att n1 I had to remove ALL drivers before installing them again in order for my phone to work.
Perhaps try removing ALL drivers and starting fresh?
In Envrionmental Variables, create a System variable:
variable name: devmgr_show_nonpresent_devices
variable value: devmgr_show_nonpresent_devices
With your phone not plugged into your pc, go to device manager and under the View menu, select "show hidden devices".
Remove everything under ADB. Remove anything in unknown devices that says Nexus1 or Android, or Google. Remove the Composite Devices under USB (they will be added back upon reboot if the system uses them) as well as the Mass Storage Devices.
Reboot your system. Plug your phone in and update/install your drivers for your phone.
I used both the drivers from the sdk and from http://forum.xda-developers.com/showthread.php?t=613217 to have fastboot and adb functional.
Good luck!
Click to expand...
Click to collapse
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Part Four said:
Followed all of these directions, reinstalled the driver, and I still can't connect via adb. Still getting "error: device not found." Help!
Click to expand...
Click to collapse
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
myn1 said:
Try to download the latest Android SDK and have it installed again. Also download the USB drivers within that package...
Click to expand...
Click to collapse
Done and done, days ago. Still no dice. This is ridiculous.
Still having problems. Tried everything I can think of, and everything suggested to me by the XDA community. I don't know if this will help any of you guys help me, but when I type "adb devices" into a command prompt, it returns:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
And then shows nothing. So effing frustrating! EVERY computer I have (I actually have tried it on 6 different laptops and PCs) returns the same error and cannot find my Nexus One. WTF happened!? HELP!
Part Four said:
WTF happened!? HELP!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=613217
pvillasuso said:
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
I'm sure you're trying to be helpful but, if you've read through this thread, you'd know that I've already done all of that. OBVIOUSLY, I've done all of that because, like I said, ADB STOPPED working. In order for it to stop, it must have, at some point, worked just fine. And it did. It worked perfectly until recently. So, yes, I've installed all the damn drivers I need. But, no, it's still not working. It's infuriating.
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
temperbad said:
debugging mode os on? did you open adb, delete all htc drivers then reinstall them from the sdk. not just install them but delete and then reinstall.
Click to expand...
Click to collapse
Yes. *Sigh*
Do you see this device ( pic ) @ device manager :
If you do , there is no reason for adb commands under DOS prompt for not workig well ... really weird
temperbad said:
also once in bootloader your good, some instructions say go into hboot, not for me, just right in bootloader, not hboot.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
What do you mean, I'm "good?"
[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.
Ill add this to the FAQ
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.
Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info
RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.
n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.
Very simple and easy to follow. Thanks OP.
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.
I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...
Introduction
This is an Open Beta of the Heimdall One-Click flashing utility.
I began the Heimdall One-Click project at the start of June. Heimdall One-Click is based on Heimdall by XDA Senior Member Benjamin Dobell. The goal is to reduce the number of problems we've seen in flashing packages. Once "Connected" is working on all platforms The beta test is complete.
There has already been some serious beta testing done to date. All that is left is cross-platform compatibility
Beta Test
You don't have to flash to test. Just verify "connected" appears.
1. Ensure you have the latest version of Java installed on your computer: http://www.java.com/en/download/installed.jsp?detect=jre&try=1
2. Download and run this: http://oneclick.adamoutler.com/files/Modem-KC1-One-Click.jar
3. Put your phone into Download mode, and connect to the computer. Verify you see "Connected" displayed. see image here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. reply to this post with the OS you use, result and any problems!
5. optionally click flash to upgrade to the KC1 modem.
Platforms requiring test
Linux Ubuntu/Debian 64
Linux Ubuntu/Debian 32
Windows 7 -on hold
Windows Vista -on hold
Windows XP -on hold
Mac OS-X Lion
Mac OS-X Snow Leopard
Mac OS-X Leopard
Please note: the final version will be roughly 10 megs, this beta contains alot of extra fat to be trimmed.
Beta7 31July2011 Fixed installation of VCC redistributable on each start of program for windows. No changes for Linux or Mac.
no known issues.
Beta6 31July2011 No fixes. Added live PIT View to show what has been flashed and keep an up-to-date log of what's going on in the background.
noted problem with Windows installation of Visual C++ on every run.
Beta5 31July2011 Revised windows installation. No longer installing heimdall.exe to program files. It is now created in temp folder on each start of the application. Visual C++ redistributable is installed when required. Drivers are installed on first click of "flash" button if connection to device is not possible. No changes for Linux or Mac.
Beta 4 30July2011 Fixed installation order for Windows so no reboot/restart is required. Added log into Details window. Each instance gets its own unique and randomized folder. Added logging for flash operations. Fixed unused imports. Fixed links for windows. Reduced memory usage. No changes for Linux or Mac.
Installation of drivers is still a problem on some systems. Use of "Program Files" is not acceptable as a "repository" for binaries, must have an uninstaller or create a binary instance installation.
Beta 3 29July2011 Fixed installer for Windows and Mac. No changes for Linux.
Windows installer is demonstrating problems with order of verifications... VCC redistributable should be installed before heimdall is verified. This leads to having to close the application out and retry. Windows not reporting heimdall installed after installation without reboot. All windows hyperlinks are inoperative.
Beta 2 29July2011: Initial Release.
problem with windows platform installer renders platform unusable. Problem with mac platform does not install newest version of Heimdall.
why not just flash modems thru CWM?
Thegodfather156 said:
why not just flash modems thru CWM?
Click to expand...
Click to collapse
Because he choose something "safe" to flash for the screen shot. Cuz some ppl will want to toy with this, but for the very first time will not actually flash unless they see it exactly the screen shot Adam posted.
it is an EXAMPLE
Also, he is showing just what this "one-click" can do.
Nice job sofar keep it up
Sent from my SAMSUNG-SGH-I897 using XDA App
The hits just keep coming. (;~)
Sent from my SGH-I897
DaNaRkI said:
Because he choose something "safe" to flash for the screen shot. Cuz some ppl will want to toy with this, but for the very first time will not actually flash unless they see it exactly the screen shot Adam posted.
it is an EXAMPLE
Also, he is showing just what this "one-click" can do.
Click to expand...
Click to collapse
he seems to be pretty nifty when it comes to Heimdall. i like it, i was just curious what the advantages of this method in comparison to flashing modems thru CWM
you dont have to bold your words, i wasnt trying to be a ****.
Thegodfather156 said:
why not just flash modems thru CWM?
Click to expand...
Click to collapse
As was stated, this is a beta test. I'm not going to release a full package with kernel, factoryFS, Cache and bootloaders for a beta. However, this method makes it much simpler to flash a modem then any other method.
The simplest method for flashing a modem with CWM
1. download package with phone via barcode or transfer to /sdcard/Download
2. Start phone in recovery mode
3. Select install zip from SDCard
4. select Choose zip from sdcard
5. select "download" and then select "modem.zip"
6. scroll down to "yes" and select it
7. select reboot
One-Click:
1. connect phone in download mode
2. download/run this package
3. click flash.
Also, I'll be providing one-click packaging... simply select the Heimdall 1.3 tar.gz file and it will make a one-click out of it.
I've got the mac problems worked out. I'm currently working on windows. A beta 3 will be up shortly.
AdamOutler said:
As was stated, this is a beta test. I'm not going to release a full package with kernel, factoryFS, Cache and bootloaders for a beta. However, this method makes it much simpler to flash a modem then any other method.
The simplest method for flashing a modem with CWM
1. download package with phone via barcode or transfer to /sdcard/Download
2. Start phone in recovery mode
3. Select install zip from SDCard
4. select Choose zip from sdcard
5. select "download" and then select "modem.zip"
6. scroll down to "yes" and select it
7. select reboot
One-Click:
1. connect phone in download mode
2. download/run this package
3. click flash.
Also, I'll be providing one-click packaging... simply select the Heimdall 1.3 tar.gz file and it will make a one-click out of it.
I've got the mac problems worked out. I'm currently working on windows. A beta 3 will be up shortly.
Click to expand...
Click to collapse
you are on another level when it comes to developing dude. keep up the good work.
Works fine on Ubuntu 32bit (I already have udev rules configured from a heimdall source build)
-.-;
@Adam - so.. does this thread mean your hijacking and near constant post in the official Heimdall thread will cool? You were making that thread a lil hard to keep up with. Granted seeing such an interested dev at work was pouring out tons of really neat info
@godfather - Just putting it up there as a preventive incase someone else might consider jumping on your question and going off all "I can flash most of that thru CWM, and have never had a problem with ODIN" crap. I've seen some ppl here post things like how Heimdall is bad cuz it was reverse engineered by some guy, and that they would rather stick with such a poorly written program just cuz it came from samsung... Cuz clearly we all love the stock cappy
Tried to run it under windows 7 64Bit. Says I must run as administrator. Although I am logged in as administrator, I atttempted to use the runas command from a command window. Looks like your command line just come back with a syntax error for me. Maybe I did something wrong since I've never used that command before. In any case...problematic to get it installed here.
kb9nvh said:
Tried to run it under windows 7 64Bit. Says I must run as administrator. Although I am logged in as administrator, I atttempted to use the runas command from a command window. Looks like your command line just come back with a syntax error for me. Maybe I did something wrong since I've never used that command before. In any case...problematic to get it installed here.
Click to expand...
Click to collapse
I'm uploading a new version which corrects that problem now. I didn't realize the changes in 1.3 would ripple the installation across all the platforms.
I've finished uploading commits and a new version of the KC1 beta. Please give feedback on Windows and Mac. Linux has been tested working.
working as connected here!!! After a few installs of drivers and C++ redistributable...then it said I had to install heimdall manually..clicked OK and they I saw the connected message. Looks like no joy on the KC1 upload...I'm perpetually "handshaking with loke" Phone has yellow digger guy on it and it says downloading on the front..??
Adam, this looks nice, I finally figured out how to install the drivers and find my device. I downloaded the Heimdall suite 1.3.0 and when I click on drivers, it sees the device. Question: if I install the drivers, will it effect the drivers I have intalled for Odin? Also, if I want to use the Heimdall suite for flashing custom ROMs does it work the same as Odin as far as the files and where to put them?
Rhiannon224 said:
Adam, this looks nice, I finally figured out how to install the drivers and find my device. I downloaded the Heimdall suite 1.3.0 and when I click on drivers, it sees the device. Question: if I install the drivers, will it effect the drivers I have intalled for Odin? Also, if I want to use the Heimdall suite for flashing custom ROMs does it work the same as Odin as far as the files and where to put them?
Click to expand...
Click to collapse
Yes. Heimdall uses the well known and understood Open-Source LibUSB drivers. Odin uses closed source proprietary drivers.
kb9nvh said:
working as connected here!!! After a few installs of drivers and C++ redistributable...then it said I had to install heimdall manually..clicked OK and they I saw the connected message. Looks like no joy on the KC1 upload...I'm perpetually "handshaking with loke" Phone has yellow digger guy on it and it says downloading on the front..??
Click to expand...
Click to collapse
Which version of windows is that?
Win 7, professional, 64bit
Win7 ultimate x64 issue
Everything seemed to work fine at first, showed device connected then after a few seconds it would disconnect and reconnect over and over and over. I tried to recreate the issue but could not. I tried a few more times and it only disconnected and reconnected once after 30 seconds and it wouldn't do it again. Anyone else see anything like this. I attached a screen shot.
Android x86
there are several developers working on this project there is a source for what they have so far, that said ill link in a sec. this is a tutoral of how ive managed to get this far in android x86 ive got most of root working on various builds let me state that i am using a acer aspire one 532h 2588! i am currently running RC2.1 by314
For root you must be on ext3 to get it working although it will still run in ntfs and you will be able to read windows usb drives ext3 you cant the con to ext3.
http://www.youtube.com/watch?v=JfWb_h96_-Q&feature=youtu.be
YouTube how to
-Dev Links-
http://source.android.com/
http://code.google.com/p/android-x86/
http://tabletsx86.org/
http://www.android-x86.org/
http://android-x86.sceners.org/en/
http://www.android-x86.info/
http://www.ceh-photo.de/blog/the ones here work for more computers, just saying! http://www.ceh-photo.de/blog/?p=562 BETA 4
-Needed-
2g min usb for installation of iso
i used a external hdd, you can use a usb drive 4g min i would say, or you can install on os hdd but do not format it!
lili usb creator - http://www.linuxliveusb.com/en/home
minitool partion wizard - www.partitionwizard.com
-steps for live testing-
1) use lili usb creator to install the iso onto a 2g min usb
a) select the RIGHT usb drive lol
b) then select the iso that your going to test
c) i personally only have format the usb selected but you can install the other crap but i dont lol
d) click the lighting bolt to start click the oks lol
2) insert the usb with iso on it, to your laptop with it off
3) start the laptop into the boot options (f12 for me) select the usb with iso
4) click run live...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TEST EVERYTHING YOU CAN, root hardly works here and no data is saved...
-steps for installation-
1) format your usb or hhd partion with minitool partion wizard to either ext3 (most root availible) or ntfs (for use with usb drive ?music?)
2) use lili usb creator to install the iso onto a 2g min usb
a) select the RIGHT usb drive lol
b) then select the iso that your going to use after tested for the best one
c) i personally only have format the usb selected but you can install the other crap but i dont lol
d) click the lighting bolt to start click the oks lol
3) turn your laptop insert the usb with the iso and the usb or external or even the internal if you want to do something crazy but you will format your windows or stock os! i use a external hdd as in my vid..
4) start your laptop enter your boot options (f12 for me) select the usb with the iso
5) select to install
a) select the partion that you set up earlier (if you dont see it detect devices ext3 = linux)
b) choose to format (i format to the format i set it for you dont have to...)
c) yes install grub (if installing to external you dont have to install grub but i do for debugging and to get to windows without unpluging)
d) yes install windows if your installing on a windows hdd
e) reboot (as soon as you see your bios you can remove your usb if your dont you will get error 17)
And now your running android ics on your laptop/netbook/pc
I didnt develop any of this! just trying to get it out there for others
thanks button is nice but not nessary
Acer Aspire One 532h Android x86 ICS RC2.1...
Nice tutorial, thanks!
MEHH lol i thought there wasnt a comment yet lol oh well i need to modify it
Acer Aspire One 532h Android x86 ICS RC2.1...
http://forum.xda-developers.com/showthread.php?t=1973492
Android x86 tut
LOL awesome
XML
Nice man
Sent from my SCH-I500 using Tapatalk 2
Awesome
Sent from my PG86100 using xda app-developers app
You should probably mention that the android x86 builds are generally limited in their hardware support.
lambstone said:
You should probably mention that the android x86 builds are generally limited in their hardware support.
Click to expand...
Click to collapse
Thanks that's why I say test before you install it. The link with green next to it is Chris's blog his runs on more than the rest
Fascinating AOKP Jelly Bean Milestone 1 Devil 1.8.1...
I am confused.
I'm trying to download LiLi. I click on the download link here but it takes me here. Clicking the "Download LinuxLive USB Creator" in the second link takes me back to the first.
Am I not clicking the correct link?
Will this be Mac capable? Also, I am running Intel Centrino2, no support for us?
I am writing this from Andorid on my laptop.
Very cool.
sebouh00 said:
I am confused.
I'm trying to download LiLi. I click on the download link here but it takes me here. Clicking the "Download LinuxLive USB Creator" in the second link takes me back to the first.
Am I not clicking the correct link?
Click to expand...
Click to collapse
Yes you are
BlueEditionE6 said:
Will this be Mac capable? Also, I am running Intel Centrino2, no support for us?
Click to expand...
Click to collapse
On that I have no idea I'm trying to get as many developers as I can to help out I'm about to try to compile a newer version if I can get my PC you repo everything it lost net last night and can't get it to restart or catch up idk what to do
Try beta 4 its your best bet
Sent from my SCH-I500 using Xparent Cyan Tapatalk 2
Thank you so much for this guide and these links, i have installed android on my dell laptop and its working perfect, haven't tested everything but everything i have tested so far seems to work great.
Nice job! Got it running on my laptop just fine. I wonder if it will work on my desktop?
shelby04861 said:
Nice job! Got it running on my laptop just fine. I wonder if it will work on my desktop?
Click to expand...
Click to collapse
Beta 4 runs on my amd Asus machine but my wifi adapter doesnt. can anyone help me compile a recovery for computers
Sent from my SCH-I500 using Xparent Cyan Tapatalk 2
The WiFi is kinda weird but I haven't really looked into it too deep. It will not connect to my home WiFi network but it will to my neighbors and my cell phone. Go figure. I have been trying out different iso images from the many downloads but I can't fins one yet that will boot on my old dell dimensions 2400 desktop. One of the error messages that pops up is for the computer model check and of course it fails, among other things. If anyone knows of a download for an iso that will work on at least dell desktop computers, let me know.
If it's broken...beat it into submission until it works!
Kaptinkrunk said:
Android x86
there are several developers working on this project there is a source for what they have so far, that said ill link in a sec. this is a tutoral of how ive managed to get this far in android x86 ive got most of root working on various builds let me state that i am using a acer aspire one 532h 2588! i am currently running RC2.1 by314
Click to expand...
Click to collapse
NEED HELP
I installed in the 5gb ext3 partition i created for the ICS, installed grub. But when I try to run it after installation, i end up with a static screen,
ok, linking youtube video doesnt work for me as well, so heres the link http://www.youtube.com/watch?v=dfH2zDcX0kA
anyone can help?
Also, it screwed up my Win7, wont allow me to boot, when i try to recover the Win7, the reboot process kept getting interrupted by GRUB, anyone can help me with that? Now I am without a computer.
Blue
Thanks for sharing Android x86 tutorial for every android developers for better solution. I appreciate your way.
BlueEditionE6 said:
NEED HELP
I installed in the 5gb ext3 partition i created for the ICS, installed grub. But when I try to run it after installation, i end up with a static screen,
ok, linking youtube video doesnt work for me as well, so heres the link http://www.youtube.com/watch?v=dfH2zDcX0kA
anyone can help?
Also, it screwed up my Win7, wont allow me to boot, when i try to recover the Win7, the reboot process kept getting interrupted by GRUB, anyone can help me with that? Now I am without a computer.
Blue
Click to expand...
Click to collapse
Try booting a Win7 Setup DVD, then hit repair and proceed with following what shows your on screen.
white-energy said:
Try booting a Win7 Setup DVD, then hit repair and proceed with following what shows your on screen.
Click to expand...
Click to collapse
It wont let me repair, since repair requires reboot, but then GRUB kicks in everytime i reboot, therefore stuck. I popped in the cd and reinstalled Windows.... but lost every program,
this is a bit off topic, but how can i restore everything from my old win7 to my new win7? I tried using the comand prompt in the recovery page, but the programs are still missing, tried just copy and pasting from windows.old folder to current windows folder, no luck.
Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?
C'mon... Somebody..:? Anybody?
Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium
do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.
androidkid311 said:
Try this. Plug it in via USB as you would. Then unlock your nexus 7 and it should up, works for me lol.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I've tried that. Doesn't work. Nothing makes it register.
Billchen0014 said:
do you have a factory original usb line? sometimes other ones just wont work. also try changing roms.
Click to expand...
Click to collapse
Tried this too. I've been using the new factory cable and it doesn't work. I've tried five different cables and different usb ports. Also tried factory resetting and different roms as well.
Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck
Wilks3y said:
Couple of things to try:
1 - Go through Device manager (Start -> Right Click My Computer -> Manage) - And remove anything and everything to do with Android, or Nexus etc.
2 - Plug in device, if nothing happens right click The top of "Device Manager" - Which should be your computer name - And click "Scan for hardware changes"
If this doesn't work, try to download WugFresh ToolKit, and install the drivers through his ToolKit, I had issues like this when I first got my Nexus, trying all different things and random drivers, my only way to fix it was going through WugFresh toolkit and downloading his drivers. CLICK HERE FOR THE TOOLKIT
Good luck
Click to expand...
Click to collapse
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.
Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Username invalid said:
Here is the latest Android Composite ADB Interface Driver straight from SDK instead of toolkit.
http://d-h.st/kDu
If you are worried about ROM failing, installing MultiRom is highly recommended. Not indifferent to partitioning a hard drive and installing multiple operating systems on a PC, MultiRom is indispensable when experimenting. If one ROM doesn't boot, simply boot from another or to your stock rooted.
Example -
Click to expand...
Click to collapse
Is tha driver different from the drivers I downloaded from the SDK manager?
nicholi2789 said:
Is tha driver different from the drivers I downloaded from the SDK manager?
Click to expand...
Click to collapse
It is version 7.0.0.1.
nicholi2789 said:
Thanks alot man. I do have Wigfreshes toolkit, i just haven't really done much with it. I will try all this when I get home though. Sounds like a good method to try. The device came pre-rooted and unlocked, all I had to do was flash recovery through goo. I'm running Vanilla root box night lies and they are great. I'm just really worried about getting in a bootloop or softbricked since there is no battery to pull, and i can't connect to my computer to unbrick. If it happens I'll be waaaay up the creek with no hope for a paddle.
Thanks alot.
Click to expand...
Click to collapse
No worries mate best of luck !!
Let us know if not and I'll try find another way
I found this while searching. http://dlcdnet.asus.com/pub/ASUS/EeePAD/Nexus7/usb_driver_r06_windows.zip . USB drivers for win 8 problems-
Sent from my Nexus 7 using Tapatalk 4 Beta
best and quick solution. Open "settings"
nicholi2789 said:
Okay, So I bought this new Nexus 7 about a week ago. It was used but the person I bought it from was trustworthy. It came pre-rooted and unlocked. Anyways, my Windows 8 laptop WILL NOT recognize it no matter what I do.
Let me start off by saying, I am no novice to Android. My main device is a Verizon Galaxy s4, and it was the S3 before that. Both phones I did lots of modding and theming on them, and always running a custom rom. I have adb installed and working on my computer as well.
Now the problem. When I plug in my Nexus into my laptop, nothing happens. It doesn't make the usual windows device plugged in sound or anything, and it doesn't show up as a drive in Windows explorer. Even if I open up the device manager and then plug in my Nexus nothing shows up. Not even the "device not recognized" thing. Nor do I get a notification in the Nexus statusbar saying it's plugged in as a media device.. Though the battery DOES charge.
I have tried enabling usb debugging and toggling back and forth from MTP to PTP and still nothing. Tried it w/out USB debugging as well. Nothing.
Tried plugging it in while in fastboot.. Nothing.
I even downloaded the Google drivers through the Android SDK manager and since it doesn't show up as any device in device manager I can't uninstall them and update with the new drivers. This is soo soo sooo frustrating. Obviously it was able to connect to a computer at some point because they rooted and unlocked it, but now I get nothing. I've tried 4 or 5 different computers, Windows 7 AND Windows 8. And even more USB cables.
Can somebody please please shed some light on this?
It's soo frustrating not being able to use ADB with my new device or even do simple file transfers. Right now I'm using Airdroid to move files around but it's agonizingly slow and worthless for moving big files like Roms and whatnot.
And before you say it.. YES I have searched and found no definitive answers even though I KNOW other people have had this problem.
Someone help please?
Click to expand...
Click to collapse
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC
iralamanoj said:
Open "settings" on your nexus 7 2013, click on "storage", click on options(3 verticle dots on top right corner), check allow MTP... Thats it you can now open your nexus drive on your PC
Click to expand...
Click to collapse
Haha, thanks for the help, but I wish it were that simple. It was a first Gen Nexus7 by the way too.
I'm no novice to the ways of Android, and i tried everything under the sun to get it to work. Nothing Would make it show up on the computer.
Anyways, it just ended up turning off one day (with a fully charged battery too) and wouldn't turn back on. I ended up calling Asus and they repaired it for me. It had a burnt out USB port. They fixed it and it's up and running fine now.
Long story short, be careful what you buy on eBay one, and two, Asus has EXCELLENT customer support. From the day I called them to the time I got it back fully repaired only took 7 days exactly. And I didnt have to pay for shipping. If you ever have a problem with an Asus product don't hesitate to call them.
I just solved my problem. The Nexus 7 was not showing up in the device manager and windows explorer. Once usb plugged it would charge but do nothing.. In device manager I found "ACER Composite ADB Interface". I googled it and this is the problem. apparently Windows update install this thing but it doesn't work with the Nexus 7. You have to uninstall it (don't forget to check the delete from computer box or else it will reinstall itself). Then look for this : ASUS Android Composite ADB Interface Driver 8.0.0.1 for Windows 7 64-bit and download it.(sorry I can't post links)
Now with your Nexus 7 plugged in update your driver by selecting the browse my computer option and locate the file you just downloaded and there you go it should work. After months of searching it's finally working. :victory: