There has been a few times I've ran into issues with drivers not being compatible with Windows 7 x64 so I am going to show you a way to get them working by running a virtual machine with windows xp x32 installed.
#1. Here you can download a free Virtual machine.
http://hotfile.com/dl/45019228/154c711/VMware-player-3.1.0-261024.exe.html
here is the same download link from their website, which will require registration and verification.
https://www.vmware.com/tryvmware/?p=player&cmp=EMC-PlayerEvalActivation&li=license
#2. You will need to either have an ISO of Windows XP or an installation disk for this to work.
#3. Install VMWare Player and follow the instructions, it is very simple.
#4. Once your virtual machine is open, it should install VMWare tools. This will give you access to dragging and dropping, copying and pasting, and various other functions from your host computer to the virtual. You now should copy all necessary files and apllications you will need to complete whatever modification it is you are going to do.
#5. Install HTC Sync on the virtual machine. Link: http://member.america.htc.com/download/Driver/HTC EVO (Sprint)/HTC_Sync_2.0.40.exe
#6. You can easily switch your device from syncing to your host computer to your virtual by right clicking the icon that shows your phone. These icons are located on the bottom right corner of the virtual machine. Picture 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"
}
One of the issues I have encountered so far is when trying to run CDMA Workshop on the virtual machine it will not open. It will give you the error "Sorry, this application cannot run under a virtual machine".
I have found a workaround for this.
Go to the folder on your host computer:
C:\Users\YOURUSERNAME\Documents\Virtual Machines\Windows XP Professional
Open your Windows XP Professional.vmx in notepad. This is the VMware virtual machine configuration file. Go to the bottom of the file on a new line each add these lines of code
Code:
monitor_control.restrict_backdoor = "TRUE"
disable_acceleration = "TRUE"
This will stop CDMA Workshop from thinking it's being run on a virtual machine and should work for other programs as well.
May I ask you what exactly you are having trouble with with W7x64? I was able to get ADB up and running, root my phone, and check my MSL with CDMA workshop within W7x64. Just had to find the right drivers online, but it didn't take too long.
Same here, Win7x64, no problems
DSwarP said:
May I ask you what exactly you are having trouble with with W7x64? I was able to get ADB up and running, root my phone, and check my MSL with CDMA workshop within W7x64. Just had to find the right drivers online, but it didn't take too long.
Click to expand...
Click to collapse
Albaholic said:
Same here, Win7x64, no problems
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=708419&page=6
it's a response from this thread. i, along with several other 64b win7 users cannot get it to work. go to the device mgr and click on the suspect, update driver and point to where the dl'ed drivers are and it does not recognize the drivers.
it seems to work fine on my the xp here at work. which drivers are you both using? i know it's not that technical. i can't develop for hack it any electronics but i can follow instructions and have hacked the psp, unlocked the tp2 and this phone among many, but i cannot understand how some were saying they've been successful and i'm in the same boat with many others who can't seem to get it to work on a 64b win7.
skoobz said:
it's a response from this thread. i, along with several other 64b win7 users cannot get it to work. go to the device mgr and click on the suspect, update driver and point to where the dl'ed drivers are and it does not recognize the drivers.
Click to expand...
Click to collapse
I'll pull my own quote from that thread:
"The 64 bit drivers will not be recognized or installed by the Windows 7 automatically. You must force the installation of the drivers by choosing the "Browse" option then "Let Me Pick" option then the "Have Disk" option."
skoobz said:
http://forum.xda-developers.com/showthread.php?t=708419&page=6
it's a response from this thread. i, along with several other 64b win7 users cannot get it to work. go to the device mgr and click on the suspect, update driver and point to where the dl'ed drivers are and it does not recognize the drivers.
it seems to work fine on my the xp here at work. which drivers are you both using? i know it's not that technical. i can't develop for hack it any electronics but i can follow instructions and have hacked the psp, unlocked the tp2 and this phone among many, but i cannot understand how some were saying they've been successful and i'm in the same boat with many others who can't seem to get it to work on a 64b win7.
Click to expand...
Click to collapse
Weird. I run Win 7 Pro x64 at home, and got the copy of HTC Sync that was on my Evo's SD card to install on it with no issues. Run the version of adb-windows from toast's evo recovery zip file from it too.
crackerstyle said:
Weird. I run Win 7 Pro x64 at home, and got the copy of HTC Sync that was on my Evo's SD card to install on it with no issues. Run the version of adb-windows from toast's evo recovery zip file from it too.
Click to expand...
Click to collapse
Its not the adb drivers that are a problem. Its the diag drivers that won't install automatically.
Berner said:
Its not the adb drivers that are a problem. Its the diag drivers that won't install automatically.
Click to expand...
Click to collapse
My bad, I saw him talking about installing HTC Sync on the virtual XP.
For HTC Diag Drivers see my article in my sig. I have changed the Sprint banner with QPST with no problems using my diag drivers on Win7 x64. I also included 32 bit drivers.
I also outlined a guide on how to manually install them.
thanks for the guide!
Thanks, worked perfect. I was wondering why CDMA workshop wouldn't work right with VMware a few days ago.
Works fine for me on windows7 x64 as well... You just have to point windows to the exact .inf driver file and force it to install. No need to install an entire virtual machine..
Sent from my PC36100 using Tapatalk
The evo always worked fine for me on win7 x64 but its terribly inconsistent with recognizing android phones and installing drivers (moment and vogue were a nightmare) even pointing to them directly. For whatever reason solutions for some definitely dont work for everyone
For some reason Win7 64 is picky about how the drivers get installed. When I followed this guide everything worked fine.
http://forum.xda-developers.com/showthread.php?t=697487
After following the instructions and running CDMA WS 3.6 in VMWare (WinXP Pro) I'm being told my current license key for CDMA WS is locked to a different machine or machine configuration, which I guess isn't terribly surprising.
I am not going to buy another license... so is there any way to set up the VMWare host machine to make CDMA WS think it's running on the same machine to which it's been locked (which is my host machine)?
The only other thing that would solve my problem would be 64-bit diag drivers for a Treo Pro and a Palm Centro.
KJThaDon said:
There has been a few times I've ran into issues with drivers not being compatible with Windows 7 x64 so I am going to show you a way to get them working by running a virtual machine with windows xp x32 installed.
#1. Here you can download a free Virtual machine.
http://hotfile.com/dl/45019228/154c711/VMware-player-3.1.0-261024.exe.html
here is the same download link from their website, which will require registration and verification.
https://www.vmware.com/tryvmware/?p=player&cmp=EMC-PlayerEvalActivation&li=license
#2. You will need to either have an ISO of Windows XP or an installation disk for this to work.
#3. Install VMWare Player and follow the instructions, it is very simple.
#4. Once your virtual machine is open, it should install VMWare tools. This will give you access to dragging and dropping, copying and pasting, and various other functions from your host computer to the virtual. You now should copy all necessary files and apllications you will need to complete whatever modification it is you are going to do.
#5. Install HTC Sync on the virtual machine. Link: http://member.america.htc.com/download/Driver/HTC EVO (Sprint)/HTC_Sync_2.0.40.exe
#6. You can easily switch your device from syncing to your host computer to your virtual by right clicking the icon that shows your phone. These icons are located on the bottom right corner of the virtual machine. Picture below.
One of the issues I have encountered so far is when trying to run CDMA Workshop on the virtual machine it will not open. It will give you the error "Sorry, this application cannot run under a virtual machine".
I have found a workaround for this.
Go to the folder on your host computer:
C:\Users\YOURUSERNAME\Documents\Virtual Machines\Windows XP Professional
Open your Windows XP Professional.vmx in notepad. This is the VMware virtual machine configuration file. Go to the bottom of the file on a new line each add these lines of code
Code:
monitor_control.restrict_backdoor = "TRUE"
disable_acceleration = "TRUE"
This will stop CDMA Workshop from thinking it's being run on a virtual machine and should work for other programs as well.
Click to expand...
Click to collapse
Did everything you mentioned and after i add those two lines and the end of the file and try to open CDMA Workshop in the Windows XP on the virtual machine it keeps closing out just like before. I been trying to get this to work for a couple days. Anyone who can point me in the right directions is appreciated.
bump
Thank you!
Thank you for the knowledge, may you have many happy blessings in your future! :good:
Related
[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.
I am having a devil of a time trying to find nexus 7 drivers that will install on windows 8. I have tried a all that i have found and have came to the conclusion, that i am an idiot.
What i am trying to do is mount /sdcard.
A related question, under ubuntu x64, I have adb working great. But I still have issues mounting /sdcard. So i figured i am doing something wrong.
Help? And yes I searched the site and found several for the galaxy nexus, but not for the nexus 7.
Thanks... And if i just missed the info, please point me in the right direction.
drx69 said:
I am having a devil of a time trying to find nexus 7 drivers that will install on windows 8. I have tried a all that i have found and have came to the conclusion, that i am an idiot.
What i am trying to do is mount /sdcard.
A related question, under ubuntu x64, I have adb working great. But I still have issues mounting /sdcard. So i figured i am doing something wrong.
Help? And yes I searched the site and found several for the galaxy nexus, but not for the nexus 7.
Thanks... And if i just missed the info, please point me in the right direction.
Click to expand...
Click to collapse
I have the windows drivers I will post them later today. For Linux since the nexus 7 uses mtp, you need ro install "gmtp", this will mount sd card for you
Sent from my Nexus 7 using Tapatalk 2
As with all Google devices, USB drivers are downloaded with the Android SDK Manager.
Sent from my Nexus 7 using Tapatalk 2
aaronpoweruser said:
I have the windows drivers I will post them later today. For Linux since the nexus 7 uses mtp, you need ro install "gmtp", this will mount sd card for you
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You are a gentleman and a scholar. Thanks! the gmtp worked. Waiting on the drivers.
tikiral said:
As with all Google devices, USB drivers are downloaded with the Android SDK Manager.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Unfortunately... this is incorrect. They work for win7 x64 but not for windows 8. I already tried that. It worked for the wife's Nexus but not for the nexus 7. That is why i posted. I would keep getting hash was corrupt error with those drivers.
ok... i found drivers for adb and usb... but i doubt fastboot would work. Noone seems to have that working with win8 yet.
Thanks for all the help
I have the same problem since I am running windows 8
Where did you find the drivers?
Pitty87 said:
I have the same problem since I am running windows 8
Where did you find the drivers?
Click to expand...
Click to collapse
A more interesting question is: where did you get a legit copy of Windows 8?
Sent from my Nexus 7 using Tapatalk 2
MSDN and Technet will get the release code on 8/15, GA is in October...
So, if it's NOT the release preview, then they torrented the nice, pirated version....
If you are using the N version of Windows 8, you will not be able to use the MTP device. Only solutions to that for now seems to be reinstalling a non-N version of Windows 8, transfer files using Android Commander (over ADB), or push files with ADB if you know what your doing.
The other non-MTP devices for ADB and Fastboot can be installed by using Google's USB Driver in the Android SDK. (ASUS also has drivers on their site, but they're unsigned I believe and will require you to disable driver signature enforcement; these are the same drivers from Google also, so this maybe pointless)
I can confirm that MTP, ADB, and Fastboot all work fine under Windows 8 Enterprise x64, and ADB and Fastbook work fine under Windows 8 Enterprise N x64.
virtual machine
I too couldn't get my nexus to work with windows 8 so i installed VMWare and installed windows 7 there and used that to access my nexus, I used this to backup and root my nexus using the root toolkit
I got my Nexus 7 to work with Windows 8 but its a pain.
You basically have to do an advanced restart and disable driver checking.
Then force the Windows 7 driver. Then root.
Once you restart the PC again, you won't be able to connect anymore unless you disable the driver check again.
Windows 8 is the biggest turd. I tried for months. I've since put Windows 7 back on and never been happier. I do have Win8 on my laptop and its OK but I have lots of issues with legacy apps. Thing is just a turd. I'm skipping 8
Sent from my Nexus 7 using xda premium
player911 said:
I got my Nexus 7 to work with Windows 8 but its a pain.
You basically have to do an advanced restart and disable driver checking.
Then force the Windows 7 driver. Then root.
Once you restart the PC again, you won't be able to connect anymore unless you disable the driver check again.
Windows 8 is the biggest turd. I tried for months. I've since put Windows 7 back on and never been happier. I do have Win8 on my laptop and its OK but I have lots of issues with legacy apps. Thing is just a turd. I'm skipping 8
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If your using Google's driver for ADB, there is no need for any of that.
{
"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"
}
Oh yea I remember drivers officially coming out after I spent all night screwing with it. Figures.
Sent from my Nexus 7 using xda premium
porticus) salenges
espionage724 said:
If your using Google's driver for ADB, there is no need for any of that.
From where did you download the driver? i have windows 8 x64 as well
Click to expand...
Click to collapse
Geniusguy said:
espionage724 said:
If your using Google's driver for ADB, there is no need for any of that.
From where did you download the driver? i have windows 8 x64 as well
Click to expand...
Click to collapse
Yes please. Bump.
Click to expand...
Click to collapse
yea! i cant get it either!
I use Windows 8 64bits too (90 day evaluation). I can't even install Android SDK (it can't detect Java JDK, installed !). I can't do anything. Can someone help me ?
zepretender said:
I use Windows 8 64bits too (90 day evaluation). I can't even install Android SDK (it can't detect Java JDK, installed !). I can't do anything. Can someone help me ?
Click to expand...
Click to collapse
Set a system variable called JAVA HOME to the jdk, instructions are online. Then install SDK by the zip method. Add SDK to environment variables.
By the way, I don't see why people gripe about 8. I'm on RP build, and it's great. Plugged in nexus, had mtp in 30 seconds. For adb and fast boot I just had to go device manager, update drivers, and manually chose my adb and fstboot.
I was having trouble with the drivers I used for my N7 in Win8 until I uses WugFresh's Root Toolkit to uninstall the old ones and reinstall new ones. He takes you step-by-step, so it's really a no-brainer.
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.
I have seen many questions asking how to install universal naked drivers. Last week I received (loan) a windows computer and had the same issues. I decided to provide the info to help others.
Note: These drivers do work properly for the TF300T even though they may not state that exactly. Also if your tablet identifies as a TF201 it will still work properly.
Note: If you are on windows 8 and having problems please see the bottom of this post #1 for help! This info was provided by prototype7 please give him a thanks.
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process if we are to succeed.
Here are the choices I had to use to change my drivers and a link to the drivers.
windows-start - in search type device manager and return
{
"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"
}
right click on the entry you wish to change the driver for
Update Driver Software
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says drivers not signed; install anyway
Windows 8
Note: The following info was kindly provided by prototype7. Please give him a thanks.
Originally Posted by prototype7
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
Re: How to install Universal Naked Drivers
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
And this thread is now stickied
MD
philos64 said:
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
Click to expand...
Click to collapse
Thanks for the kind words. I have wanted to post this for sometime but didn't have windows to prove the method.
Moscow Desire said:
And this thread is now stickied
MD
Click to expand...
Click to collapse
Thank you!
I just hope it can help some others getting their drivers installed and working.
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Manox7 said:
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Click to expand...
Click to collapse
Thanks!
I don't know why some tablets require the tablet designation and others don't. For that reason we suggest everyone use them. It is a code assigned by google that designates the manufacture of the unit. On linux we have to declare them to avoid a permissions error but we don't have to add drivers.
I'm glad you got everything sorted.
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
prototype7 said:
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
tobdaryl said:
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
Click to expand...
Click to collapse
Go ahead, it would make it easier to see. Glad I could help.
prototype7 said:
Go ahead, it would make it easier to see. Glad I could help.
Click to expand...
Click to collapse
Thanks again, I'll put in the first post for others.
Windows for x64
tobdaryl said:
Thanks again, I'll put in the first post for others.
Click to expand...
Click to collapse
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
nathanielhall929 said:
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
Click to expand...
Click to collapse
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
file selected still not working
tobdaryl said:
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
Click to expand...
Click to collapse
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
nathanielhall929 said:
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
Click to expand...
Click to collapse
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Still nothing
tobdaryl said:
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Click to expand...
Click to collapse
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
nathanielhall929 said:
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
Click to expand...
Click to collapse
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
how do I start ADB?
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
nathanielhall929 said:
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
Click to expand...
Click to collapse
Check the thread you wished me to help with as I think I have already posted the resolution there.
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
Thanks for ur great job
I have tf300t with replaced logicboard. -it was bricked
My os win8 64bit
I tried universal naked driver ..but no way
is their any reasons with the last bricked in this case...??
Sorry for the poor english