Related
When I tried to install it, it failed and now when I try again it says
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
you dont install anything. you extract the android sdk into the c:\. then you copy the two files mention in the thread to c:\windows\system32. you then go to start>run>cmd(enter). type adb devices. ADB is ALL COMMAND LINE. THERE IS NO PROGRAM YOU INSTALL
what two files?
blackfire1 said:
what two files?
Click to expand...
Click to collapse
~sigh~ are you sure you read how to do this at all?
adb.exe and AdbWinApi.dll are the two files that need to go to system32
and then install the drivers from your usb_driver folder from the SDK. Use the AMD one if you're using a 64bit OS or the Intel one for 32bit OS.
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
blackfire1 said:
Okay but I get a problem at
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows-1.5_r2\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
I get a problem at this part when I click install drivers from my pc it pops up an error
bad image
C;\windows
system32\wdcoinstaller01005.dll is either not designed to run windows or it contains an error. Try installing the program using the original installation media or contact your system administrator or the software vendor for support
It worked before but I picked the amd one before because I didnt know which one to pick now it messed up my system and I cant do it again and it didnt work.
Click to expand...
Click to collapse
System Restore and try it again.
that has nothing to do with adb. that means your driver installer that is resident in windows is corrupted. unless you can system restore to a point at which it was working, the only real fix is going to be a new windows install. not entirely sure how one breaks the library for installing device drivers, but hey, thats what you've got.
Ok the problem was solved when I used my other computer.
Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.
G1BRICKED said:
Can anybody help me set up ADB, SDK, and Emulator. I've tried all of the guides but I just don;t understand any of it. I really want Emulator too so f anyone can help, that'd be greatly appriciated. Thanks =D
I have a black G1 with Danger SPL and the latest Radio. I use a Windows Vista laptop and have the SDK downloaded in the C:/ folder but it's the zipped file. Should it be extracted in there? I've tried to do the whole SDK Setup process but for some odd reason it always downloads everything except for like, the firmwares like 1.0,1.1,1.5,1.6,2.0,2.0.1,2.1 or anything.
Click to expand...
Click to collapse
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
nephron said:
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
Click to expand...
Click to collapse
Also at what point are you having issues with setting this up?
nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd C:\sdk\tools
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
Ok so I have it setup as C:\android-sdk-windows and then all of the files. When I type in the first command it says
Code:
The system cannot find the path specified.
And I have the Droid Explorer Installed and everything but it doesn't have the Emulator and that's all I really want. That and FastBoot.
nolimit78 said:
Make sure that you have the usb drivers installed as well.
What i've done is exacted it to C:\sdk\ It makes navigating to it in CMD a lot easier. Once you have that done open CMD and type the following
Code:
cd [B]C:\sdk\tools[/B]
adb shell
This will find your device (make sure it's not mounted and USB Debugging is enabled (default in most roms) and put you into an ADB environment.
this is a really good tool too:
Click to expand...
Click to collapse
If you noticed it extracted it to C:\sdk\tools, you did yours to C:\android-sdk-windows. So you'll need to adapt to the changes..
Code:
cd C:\android-sdk-windows\tools
adb shell
Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.
G1BRICKED said:
Now it says,
Code:
Error: device not found
G1 is in Debugging mode and all.
Click to expand...
Click to collapse
A friend of mine had the same problem. Make sure the device is plugged into the back of your computer, reboot the PC and the Phone. See if that helps. And which ROM are you running?
Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging
G1BRICKED said:
Well see I'm on VegaMans Beta Legend Port, and my phone won't show up on my laptop at all not to mount or anything all that appears is the notification in my bar saying;
Code:
USB Debugging Connected
Select to disable USB Debugging
Click to expand...
Click to collapse
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.
nolimit78 said:
I saw that, It could be that USB Debug is broken on the ROM (it is in early beta) Try using a different rom.
Click to expand...
Click to collapse
Well man, I tried it on FastTest and now I have a Custom Splash1 Image and now I'm not afraid of holding the Back button with the Red one. I think I'm going to throw Sense UI off to the side for now until it supports ADB and all. So thanks man, after all these monthes I finally have ADB Access. One more thing though, how can I get Emulator to work?
Now, when I try to go into Emulator through CMD, I se this;
Code:
C:\android-sdk-windows\tools>emulator
emulator: ERROR: You did not specify a virtual device name, and the system
directory could not be found.
If you are an Android SDK user, please use '@<name>' or '-avd <name>'
to start a given virtual device (see -help-avd for details).
Otherwise, follow the instructions in -help-disk-images to start the emulator
Then, I navigate to C:/Windows-SDK-Windows/SDK Setup and I allow it to run. I get two windows, one that says
Code:
Failed to fetch URL https://dl-ssl.google.com/android/repository/repository.xml, reason: HTTPS SSL error. You might want to force download through HTTP in the settings.
I close that window and go to the one that says Choose Package To Install, but the white box on the side is blank. I close that and go to Android SDK And AVD Manager. From there I go to Virtual Devices and it's blank and grey-ed out. I click new and see
Code:
Name - [I]Here I can write[/I]
Target - [I]Here I can't write[/I]
SD Card: Size [I]Here I can write[/I] MiB or KiB
File: [I]Here I can't write[/I] Browse [COLOR="DarkRed"]Dulled out[/COLOR]
Screw skins and Hardware I can do that on my own, but how can I set a Target if it is grey-ed out?
G1BRICKED said:
how can I get Emulator to work?
Click to expand...
Click to collapse
that is something I can't help you with. I am at work and it won't allow me to download what I need for that. But I am glad you got ADB workin!
Lol thanks =D
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.
I hope this post can be of use to someone. My workplace is running Lotus Notes (sigh) and IBM recently released an update to their Traveler server which supports Activesync sychronizaton of mail, contacts, calendar and directory on Android, Iphone, etc.
The only problem is AT&T blocks Sideloading. Yes a simple root can fix the issue but that is not a true solution for every Captivate for our users. I figured out a relatively easy method of getting around this limitation.
First you need the following:
Rooted Captivate (to obtain the .apk files necessary) Only needed once, I would upload the necessary files but IBM won't like that very much.
Computer with Captivate drivers and Android SDK
The Lotus Traveler setup requires two installs which makes the process more tricky than simply doing an adb install lotusinstaller.apk, so we need a few more steps.
1. On your PC download the Lotusinstaller.apk file from your traveler server and copy it to you sdk\tools folder.
2. Plug your rooted Captivate phone into you computer with debugging mode on and use adb to issue the following command "adb install lotusinstaller.apk"
3. Open the installer application on your phone and enter the required server and authentication information for your system and click next. (this will create the server setting on the phone and download the lotustraveler.apk file to your rooted phone.) I can't remember the exact location so simply do an adb shell then "su" to gain super user rights and then do a find -name LotusTraveler.apk (or *.apk and find the lotustraveler.apk)
4. copy this file to your computer. One easy way would be to adb pull LotusTraveler.apk c:\location of sdk\tools\
Now that you have both the lotusinstaller.apk and lotustraveler.apk you will not need the rooted captivate for future phone setups.
5. Now to setup a stock Captivate. Enable usb debugging
6. adb install lotusinstaller.apk
7. launch the installer and enter the appropriate settings on the phone and click next. It will attempt to download the lotustraveler.apk and then give you an error about not being able to install applications that aren't from the market. Ignore that and close the installer.
8. now issues abd install lotustraveler.apk on your pc
You're done. The installer setup the initial server settings and the lotustraveler did the rest.
To setup more phones begin from step 5 from now on
***Disclaimer***
I wrote this up simply from memory so I'm sorry if this is not 100% accurate with the commands etc.
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
thats exactly my first thought.
jetski said:
you could user the The Android Central Sideload Wonder Machine to put .apk's on the device and not need to root.
Just a thought.
Click to expand...
Click to collapse
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Clienterror said:
Or just side load through ADB in a command window in windows. "adb install filename.apk" done.
Sent from my SGH-I897
Click to expand...
Click to collapse
I'll try the wonder machine first. thanks for that tip.
Your suggestion won't work as stated in my walkthrough. The initial apk downloads another apk to your phone somewhere in the system directory. Once you have both apk files it's a simple "adb install lotusinstaller.apk" then "adb install Lotustraveler.apk"
wonder machine causes the issue of not being able to install the second apk file as stated in my last post. It can replace adb install after you have both apk files on your computer.
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Ziuck said:
I need to get the second file to install it on my non-rooted phone.
Does anyone know the location of the download on the phone so it can be pulled via adb?
Click to expand...
Click to collapse
just do
find -name LotusTraveler.apk
it will show you where the apk is located
I'm trying to install CyanogenMod, unless you can advise me a better ROM?
Doing so, I need to unlock my Bootloader, right? However, after I connect my Sony Xperia T with my laptop via USB-cable while holding the 'Volume up' button, and I attempt to type:
Code:
fastboot devices
into Command Prompt, command prompt says:
Code:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
So I Google'd it and bumped into this thread.
I'm glad someone found a solution, however I'm stuck.
I unzipped the ADB drivers and tried to install the USB driver windows says:
Windows 8 said:
This program might not have installed correctly
SAMSUNG USB Driver for Mobile Phones.
SAMSUNG Electronics Co., Ltd.
If this program didn't install correctly, you can try installing the
program using compatibulity settings.
-> Install using compatibility settings
-> This program installed correctly
Click to expand...
Click to collapse
When I choose "-> Install using compatibility settings", nothing happens.
When I choose "-> This program installed correctly", well... Nothing happens...
What am I missing? Do I need a Sony equivalent?
Edit: After posting the thread, my PC started installing the SAMSUNG USB Driver for Mobile Phones software. However there is still no progress when i attempt to type in "fastboot device" in CMD...
Bounkass said:
I'm trying to install CyanogenMod, unless you can advise me a better ROM?
Doing so, I need to unlock my Bootloader, right? However, after I connect my Sony Xperia T with my laptop via USB-cable while holding the 'Volume up' button, and I attempt to type:
Code:
fastboot devices
into Command Prompt, command prompt says:
Code:
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Instead of doing it manually, since it doesn't seem to be your thing, why don't you use Flashtool and let it take care of everything for you.
If you want to do it manually, if you're not in the same folder with the fastboot executable then you'll get that error, either change directory into the folder where you have the fastboot executable or add said folder path to your Windows system environment variables.
Antiga Prime said:
Instead of doing it manually, since it doesn't seem to be your thing, why don't you use Flashtool and let it take care of everything for you.
If you want to do it manually, if you're not in the same folder with the fastboot executable then you'll get that error, either change directory into the folder where you have the fastboot executable or add said folder path to your Windows system environment variables.
Click to expand...
Click to collapse
Oh, I didn't know there was some tool that can do it for me. I just Google'd how to install CyanogenMod on my Xperia T, or something like that and their website said do this. So I did.
Say I would do it manually (I'm not, just asking out of curiosity), what do you mean by "if you're not in the same folder with the fastboot executable then you'll get that error". The folder was open everytime I did it? So I don't understand.
Edit: Next problem, I installed Sony Mobile Flasher by Androxyde, it doesn't recognize my phone so I have to install drivers. This thread instructs me to a certain folder withing the Flashtool directory to install the drivers needed (Xperia TX), however, once again, it's not working. This is what Device Driver Installation Wizard says:
Device Driver Installation Wizard said:
X Sony (WinUSB) sa0105AdbDeviceClass (03/07/2012 2.0.0010.30011) -- Install Failed
X Sony Net (02/29/2012 6.0.6000.16493) ------------------------------------------- Install Failed
Click to expand...
Click to collapse
Bounkass said:
Oh, I didn't know there was some tool that can do it for me. I just Google'd how to install CyanogenMod on my Xperia T, or something like that and their website said do this. So I did.
Say I would do it manually (I'm not, just asking out of curiosity), what do you mean by "if you're not in the same folder with the fastboot executable then you'll get that error". The folder was open everytime I did it? So I don't understand.
Edit: Next problem, I installed Sony Mobile Flasher by Androxyde, it doesn't recognize my phone so I have to install drivers. This thread instructs me to a certain folder withing the Flashtool directory to install the drivers needed (Xperia TX), however, once again, it's not working. This is what Device Driver Installation Wizard says:
Click to expand...
Click to collapse
What I mean is that when you type "fastboot" in the command prompt, it's actually looking for a program named "fastboot.exe/bat/cmd, etc.". If you would have been in the same folder you most likely wouldn't have gotten that error message.
Regarding drivers not installing, I'm assuming you're on Windows 8, and you're following a guide for a Samsung phone, which it seems it even directed you to install drivers for a Samsung phone in your first post.
First of all, you need to disable Windows Driver Signature Enforcement before it allows you to install the drivers. You have to do that first, then install drivers, then use Flashtool/or do it manually, by opening the command prompt and changing directories to the folder where the fastboot executable is.
Not trying to sound harsh, but if I were you I'd be a bit careful when following guides and/or dabbling with unlocking your phone, etc.; I think you should either read up very carefully before doing anything, ask questions, or leave it for later when you're a bit more knowledgeable on these types of things, because if you're having problems running a program from a command prompt or are even installing drivers for a different phone and expecting things to work smoothly, chances are you'll mess up while tinkering with your phone, especially considering you're following the CM guide and installing a CM ROM when chances are most people with custom Roms and a T would probably be using a different ROM found here on XDA, though I could be wrong.
Antiga Prime said:
What I mean is that when you type "fastboot" in the command prompt, it's actually looking for a program named "fastboot.exe/bat/cmd, etc.". If you would have been in the same folder you most likely wouldn't have gotten that error message.
Regarding drivers not installing, I'm assuming you're on Windows 8, and you're following a guide for a Samsung phone, which it seems it even directed you to install drivers for a Samsung phone in your first post.
First of all, you need to disable Windows Driver Signature Enforcement before it allows you to install the drivers. You have to do that first, then install drivers, then use Flashtool/or do it manually, by opening the command prompt and changing directories to the folder where the fastboot executable is.
Not trying to sound harsh, but if I were you I'd be a bit careful when following guides and/or dabbling with unlocking your phone, etc.; I think you should either read up very carefully before doing anything, ask questions, or leave it for later when you're a bit more knowledgeable on these types of things, because if you're having problems running a program from a command prompt or are even installing drivers for a different phone and expecting things to work smoothly, chances are you'll mess up while tinkering with your phone, especially considering you're following the CM guide and installing a CM ROM when chances are most people with custom Roms and a T would probably be using a different ROM found here on XDA, though I could be wrong.
Click to expand...
Click to collapse
Thanks for your reply.
I decided to re-install Windows 7. I was planning that anyway.
Now I'm going to start from scratch and see what happens.