Related
Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
So, I've never had a problem with ODIN before, but today, while trying to ODIN back to stock (Obsidian V2 isn't working, so I'm seeing if that's the problem) I got the little Windows Error Message that says "USB Device Not Recognized" and then some other bull****. I know that I installed the Drivers (at least I think they were the right drivers) and I plugged into all 4 of my USB ports and still get the same message.
I had the same issue once. Try uninstalling the drivers you have and download and install a fresh set. That worked for me.
hmmm... I tried that (numerous times) and it still isn't working. All I get is "USB Device Not Recognized: One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." The drivers are installed, reinstalled, and re-reinstalled. I even tried to go in and change it to the right drivers myself, but no dice...
I had this problem, and got it fixed. Download the 64 bit drivers, you can find the link in the vibrant bible, and it should dl as a zip file. Unzip it on your pc, then from your windows device manager, reinstall the drivers for the unrecognized device, and point it at the 64 bit drivers folder you just unzipped. It should load the drivers and be recognized. If other devices also pop up, point them at the same folder. I did this oj a 32 bit win7 system and it worked great. Good luck.
Sent from my Vibrant running Macnut R10
kuhan said:
hmmm... I tried that (numerous times) and it still isn't working. All I get is "USB Device Not Recognized: One of the USB devices attached to this computer has malfunctioned, and Windows does not recognize it." The drivers are installed, reinstalled, and re-reinstalled. I even tried to go in and change it to the right drivers myself, but no dice...
Click to expand...
Click to collapse
try a different computer, i have had this happen to me, google how to uninstall ghost drivers or hidden drivers.
Br1cK'd said:
I had this problem, and got it fixed. Download the 64 bit drivers, you can find the link in the vibrant bible, and it should dl as a zip file. Unzip it on your pc, then from your windows device manager, reinstall the drivers for the unrecognized device, and point it at the 64 bit drivers folder you just unzipped. It should load the drivers and be recognized. If other devices also pop up, point them at the same folder. I did this oj a 32 bit win7 system and it worked great. Good luck.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
Wait, I'm confused... what do you mean point it at the 64-bit drivers? I'm not much of a Windows guy...
djkdawg said:
try a different computer, i have had this happen to me, google how to uninstall ghost drivers or hidden drivers.
Click to expand...
Click to collapse
I've only got the one Windows machine at my house... I can't do anything else until my mom gets back into town this weekend.
Sorry I assumed you were somewhat of an advanced user. If you are using a windows system, download and unzip the 64 bit drivers I mentioned above. Access Windows device manager from the control panel to view the systems devices. The devices that are not loaded properly will be easy to identify. You the right click on the device, choose "reinstall driver", then "have driver file" (or something very similar, i don't have the specific verbage in front of me), and then select the folder where you unzipped the previously mentioned 64 bit drivers. It should then load the drivers and recognize the device. As a note, you should have your phone in dl mode and plugged in so that windows actively sees the phone.
Hope this helps and its not over your head. I work in IT sometimes my explanations can be too technical, but i tried not to do that here. If your near central colorado I'd offer some in person help at this point. Hope you can get it fixed.
Sent from my Vibrant running Macnut R10
Br1cK'd said:
Sorry I assumed you were somewhat of an advanced user. If you are using a windows system, download and unzip the 64 bit drivers I mentioned above. Access Windows device manager from the control panel to view the systems devices. The devices that are not loaded properly will be easy to identify. You the right click on the device, choose "reinstall driver", then "have driver file" (or something very similar, i don't have the specific verbage in front of me), and then select the folder where you unzipped the previously mentioned 64 bit drivers. It should then load the drivers and recognize the device. As a note, you should have your phone in dl mode and plugged in so that windows actively sees the phone.
Hope this helps and its not over your head. I work in IT sometimes my explanations can be too technical, but i tried not to do that here. If your near central colorado I'd offer some in person help at this point. Hope you can get it fixed.
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
ah, thanks... I wouldn't call myself advanced... adept at best. Before I got the Vibrant, I was a HARDCORE Apple fan... Still an Apple fan, but not so hardcore lol
So I tried doing exactly what you said and it keeps saying "Your device drivers are already up-to-date" even though it still shows up as "Unknown Device" and already said "Device Driver Software could not be found"
Did you let it auto detect the driver or did you select have disk and then browse to the unzipped driver folder?
Sent from my Vibrant running Macnut R10
Br1cK'd said:
Did you let it auto detect the driver or did you select have disk and then browse to the unzipped driver folder?
Sent from my Vibrant running Macnut R10
Click to expand...
Click to collapse
I tried both.
At this point, the last advice i have is to completely uninstall all drivers for the galaxy s, from add remove programs, then reboot your pc and try the 64 bit installation again before reinstalling the normal drivers, if that doesnt work, see if you can use a friends pc, install the normal drivers and see if it works on a different computer.
Sent from my Vibrant running Macnut R10
Hey folks,
got a "little" problem with my device. I tried to copy some videos of it and it just won't work.
---
I connect my device to my PC and these things happen ...
Windows 7 x64:
Nothing.
Windows 7 x64 with Kies installed:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Windows 7 x64 with Kies installed and device in mass storage mode:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Ubuntu 11.10 x64:
Nothing.
Ubuntu 11.10 x64 and device in mass storage mode:
I see some files on my device, but when trying to open them, I only get some errors ... the real problem here, when I disconnect the USB cable (or unmount) then there are no files on my device left ... everything has been moved to "lost.dir" and I can´t open them from there, not even from my phone.
---
I tried to connect with USB debugging enabled, but it would work.
Any ideas?
/Edit 1:
The only way to copy stuff over to my computer is by using Kies Air ... and it takes ages for HD videos.
/Edit 2: THE SOLUTIONS LOL :-D
1. I had to connect my device via another USB slot
2. when USB debugging is enabled, it still wouldn't mount; then I installed this app https://market.android.com/details?id=com.jrtstudio.automount and now everything works just fine
freakin.ro said:
Hey folks,
got a "little" problem with my device. I tried to copy some videos of it and it just won't work.
---
I connect my device to my PC and these things happen ...
Windows 7 x64:
Nothing.
Windows 7 x64 with Kies installed:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Windows 7 x64 with Kies installed and device in mass storage mode:
Windows sees that there is a new device, but it won't let me open as a storage ... "Code 10" in the device manager.
Ubuntu 11.10 x64:
Nothing.
Ubuntu 11.10 x64 and device in mass storage mode:
I see some files on my device, but when trying to open them, I only get some errors ... the real problem here, when I disconnect the USB cable (or unmount) then there are no files on my device left ... everything has been moved to "lost.dir" and I can´t open them from there, not even from my phone.
---
I tried to connect with USB debugging enabled, but it would work.
Any ideas?
/Edit 1:
The only way to copy stuff over to my computer is by using Kies Air ... and it takes ages for HD videos.
Click to expand...
Click to collapse
1) Using a Rom? If yes check in thread if it, if this problem is already known.
2) Tried different USB-Slots?
3) Connect phone, search in device manager for the device and uninstall the drivers.
Then un- later replug the phone and wait if all drivers got installed again.
CHEERS ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
Lost DIr is for error files that have been corrupted .
jje
... connected to another USB port and it really works :-D it´s on the same controller ... so now I´m really confused lol.
I´m running Samsung's stock 2.3.4. I´ll try to get ADB working later and if it works i´ll close this, thanks very much
freakin.ro said:
... connected to another USB port and it really works :-D it´s on the same controller ... so now I´m really confused lol.
I´m running Samsung's stock 2.3.4. I´ll try to get ADB working later and if it works i´ll close this, thanks very much
Click to expand...
Click to collapse
You're welcome, mate ;-)
Sent from my Galaxy S2 - I9100 with SensatioN Rom!
JJEgan said:
Lost DIr is for error files that have been corrupted .
jje
Click to expand...
Click to collapse
I know, is there a way to restore this files?
so, just tried another app:
https://market.android.com/details?id=com.jrtstudio.automount
it mounts my device correctly even when USB debugging is enabled :-D
So I have a Samsung Vibrant(just got it recently) and I'm having problems when i connect it to the computer. It gives me an USB device not recognized on my windows 8 computer. I have spent all morning searching and reinstalling drivers and trying my old pc and new cables and i found out that my old windows 7 computer with 4GB of ram and an overloaded hard drive will detect my device the problem there is it not my main computer and i dont want to have to connect all the vga cables boot it up connect mouse and ect to use this computer just to be able to copy files, and do other things from my computer to my phone I dont know why my main computer dell inspiron windows 8 will not work when it was a couple of days ago when i had a problem with conectivity and had to flash back to stock but now it wont connect. could someone help me? Here's a list of things i've tried
installing kies
installing adb again
aoi tool and then drivers
a bunch of diffrent drivers found on the fourms
diffrent usb cable
i would like to be able to do it on my main computer but its not working if someone could help that would be great
also please dont hate on me for having windows 8 jk i dont care :good:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Vono123 said:
I'd have to say that your drivers are all scrambled. Look up "android SDK" here on xda and install that for a bigger variety of drivers. Or just download Google's USB driver and manually install it through device manager which always works for me. Windows 8 is new and very complicated.
Click to expand...
Click to collapse
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
apples723 said:
I will try this when I get home from school this afternoon but i have tried downloading android SDK(adb correct?) and then going into device manager and then going to downloads/adb/sdk/exstras/google/usb drivers and it never finds anything.
Click to expand...
Click to collapse
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Vono123 said:
Android SDK is installed in the main drive right? local disk c?
You have to click the folder (usb_driver) and then click update.
In the android sdk folder there should be and exe file called SDK manager. There you will be able to download all the drivers for your current android version also the latest Google drivers and SDK tools etc.
I was stuck on this process for a long time because it allways works different for everybody. Just keep me posted on what you do I'm more than glad to help.
Click to expand...
Click to collapse
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
apples723 said:
everything is up to date in the sdk manager do i need to reinstall it? also it still wont find the drivers i have atatched some png files take a look the picktures and it will show you the where the drivers are and what im selecting
EDIT****
I forgot to mention i tried it at school on a windows 8 computer and it worked fine its my crappy computer thats only five months old
Click to expand...
Click to collapse
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Vono123 said:
So what exactly happens when you click update? What does it say?
Is your PC up to date? (update wise)
Do you have the the drivers for the phone itself like samsung drivers?
And did you try rebooting your PC after installing your drivers? <-- that is important. You should always reboot after install or uninstalling drivers otherwise you'll end up scrambling them.
From the pictures it shows you have the drivers but I'd also try going deeper than usb_driver, try clicking on i386 or amd64.
Click to expand...
Click to collapse
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
apples723 said:
i have the latest update from microsoft and yes i have the drivers for my phone itself and i rebooted a right after i installed the drivers and then unisntalled and i have gone into i386 and amd64 give me a second and i upload a picture of the error
EDIT
i uploaded the pictue of the error im getting
Click to expand...
Click to collapse
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Vono123 said:
OK make sure there are no HTC drivers on your PC. When you hook up your phone does USB storage work or anything like that?
Check those out and then I want you to go to Google, download pdanet latest version via pc (dont install yet) and go to the play store and install on your phone turn on USB debugging and the install non market apps and hook your phone up to the computer. Then install pdanet via PC and see if that works. HTC drivers get in the way of Samsung's BTW.
Click to expand...
Click to collapse
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
apples723 said:
you want me to install pdanet on my phone too and by the way there is no htc drivers that are on my computer
Click to expand...
Click to collapse
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Vono123 said:
OK good and yes its in the play store for free but I don't think you have to install it but it makes the process more easy for ya.
You do have usb debugging and install non market apps checked right? You need those on.
Click to expand...
Click to collapse
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
apples723 said:
still giving me the error i think its my computer because it works on our family laptop school computer and basment computer how do i totally unistall drivers not from device manager theres a difrent way i think not sure
Click to expand...
Click to collapse
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Vono123 said:
I want you to uninstall all your Samsung drivers(not android SDK) under control panel/uninstall programs. If you see something like Samsung kies definitely uninstall it. Reboot your computer and follow this guide for windows 8:
http://forum.xda-developers.com/showthread.php?t=2038555
After this if it doesn't work I'd recommend pulling out your old computer for android modding lol. I'll still look up some threads for your problem. Let me know what's going on after that. Make sure when you follow that guide your phone can not be plugged in the computer. And when you plug your phone into the computer after everything is done and after you reboot your computer for the second time, USB debugging has to be off and when phone is done unplug and turn back on USB debugging and plug back in and wait for that. Adb should work.
[Edit] you can also try running your drivers in windows 7 compatibility. Sorry I couldn't help much.
Click to expand...
Click to collapse
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
apples723 said:
ive tried so many things i give up it makes me mad that any other computer even ones with windows 8 on them it works fine with out any sepecial installation but on my current computer it doesnt
Click to expand...
Click to collapse
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
binaryfalcon said:
I think I know what the problem is. Make sure you uninstall all the previous drivers, then have the correct drivers ready.
What you have to do is to disable driver signature enforcement.
Step 1. Go to the right bottom corner of the desktop and wait for the side menu to appear. When it's there click on the gear icon with the title "Settings".
Step 2. Now click on the entry "More PC Settings", then click on the entry "General".
Step 3"Restart now" (under "Advanced start up ") and click it.
Step 4. Now click "Troubleshoot", then "Advanced Options" and after that click "Windows Start up Settings".
Step 5. Click on "Restart" and wait, then on the next screen press F7.
You will now reboot, and try now to install the drivers (by manually selecting the folder in device manager).
I'm not sure what is the correct drivers for you.
But try this. It's still worth a shot.
Click to expand...
Click to collapse
didnt make a difrence still getting error i think its something with my system so i guess without a full diagonostic it wont work
I think I've made a huge mistake.
I just wiped my device in TWRP because the last CM Nightly I installed was acting up.
I went into TWRP, wiped and factory reset. I then rebooted and went into TWRP again.
I wanted to install CM 9.1, which I copied onto my 64GB SanDisk Ultra, and I was thinking to just flash it from the external sd.
I read somewhere on xda that I needed to maybe use a smaller SD card and have the format in FAT32, which I did, but TWRP still does not recognize them.
I am currently stuck with TWRP v2.3.1.0, no way to flash a new rom from a blank internal memory or an external memory.
I tried updating SDK and the most updated drivers for the device through the Device Manager and use "adb push" or "adb sideload" but the device is not recognized.
Can someone give me some kind of suggestion to solve this situation.
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
squidlr said:
I’d suggest using a linux install to do the adb stuff if you’re not doing so already, no need for crazy windows drivers to see a connected device.
Sent from my EPAD using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
kgal said:
Thanks for the reply.
Can you elaborate a bit on what a linux install is? My PC has W8 on...
Click to expand...
Click to collapse
Windows 8 is a bugger to get drivers working properly.
Try and use a windows 7 machine or a friends laptop or try the following instructions.
Windows 8 Instructions
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Ubuntu is a linux based Operating System, and can be used to do most things Windows 8 does, sometimes worse, sometimes better. So in this case, it's less trouble to connect an android device to a linux OS such as Ubuntu, as it can recognize a telephone without having to install drivers.
If you want to give it a go, you can install Ubuntu alongside Windows 8.
http://www.makeuseof.com/tag/tired-of-windows-8-how-to-dual-boot-windows-ubuntu/
And then install Fastboot and ADB:
http://putokaz.wordpress.com/2012/08/29/install-adb-and-fastboot-android-tools-in-ubuntu-via-ppa/
But, I'd stick to Windows and follow the advice of Flumpster if you're not too confident installing a second operating system.
I can and have knowledge of installing another OS to run alongside Windows.
I use VirtualBox to run Mac OSX and Android. Can I run Linux on VirtualBox and do the process through that?
I am not quite sure what I should do after disabling Driver Signature Enforcement on Windows 8...
Yes, you can install Linux in a virtual machine - give it a try. If the device is still not recognized via OS running in the virtual machine, you can then always install to your hard disk and try that route.
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
jamesthedisciple said:
The other option is to run Ubuntu as a live cd eg from the disk in memory (not install) and do it that way. I first unlocked and rooted my mobile this way. I can give more info on this if you like.
Click to expand...
Click to collapse
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
kgal said:
I think I'll give a multi-boot option a try. I've been wanting to install a different OS anyway since upgrading to Windows 8. Now I just have incentive.
Click to expand...
Click to collapse
Just a quick thought after re-reading your first post, I'd try a smaller sd card (16 or 32GB). I have heard of the larger faster cards giving some people problems.
Solved!
After trying to install Linux using Ubuntu 13.04 and getting more errors (something with the UEFI vs Legacy Boot installation), I decided to retry and find the original Windows drivers for the TF201.
I found one through Softpedia, downloaded it, used the "Have Disk" option when installing the yielded "Transformer" device in the Device Manager and sideloading the new CM 10.1 Nightly onto it.
Works like a charm!
Thanks everyone for the support!