Ya intentaste

Primero

Luego

Y finalmente

Acabo de probar el comando ./configure y me da un error en la Terminal que pone "no existe el fichero o el directorio".

Brinda la página entonces de donde bajastes el paquete para no adivinar y ver que tiene el paquete. A propósito ¿Qué modelo es tu máquina? ¿Podrías mostrar de paso tu sources.list?

Me imagino que lo habrás intentado hacer dentro de la carpeta creada una vez se ha descomprimido el archivo.

¿Que dice el README?

Me apuesto un fresisuis a que no tiene instalado el toolchain (compilador, enlazador, make, etc)

en testing
$ apt-cache show usb-modeswitch |grep Version
Version: 1.0.5-1

El sources.list que tengo es este
# deb cdrom:[Debian GNU/Linux 5.0.3 _Lenny_ - Official i386 DVD Binary-1 20090905-08:48]/ lenny contrib main
deb cdrom:[Debian GNU/Linux 5.0.3 _Lenny_ - Official i386 DVD Binary-1 20090905-08:48]/ lenny contrib main
# Line commented out by installer because it failed to verify:
#deb http://security.debian.org/ lenny/updates main contrib
# Line commented out by installer because it failed to verify:
#deb-src http://security.debian.org/ lenny/updates main contrib
# Line commented out by installer because it failed to verify:
#deb http://volatile.debian.org/debian-volatile lenny/volatile main contrib
# Line commented out by installer because it failed to verify:
#deb-src http://volatile.debian.org/debian-volatile lenny/volatile main contrib
La página de donde lo e bajo es esta http://www.draisberghof.de/usb_modeswitch/usb_modeswitch-1.0.5.tar.bz2. Mi equipo es un portatil acer aspire 3000 con un procesador Amd 3000+ a 1.80 Ghz y 644MB de Ram.
El archivo Readme pone esto, yo como no se ingles pues no me entero de lo que dice.
We have already collected a wide range of information on how to switch all sorts of
devices. If you run into a new one that is unknown yet, don't despair: we can find
out what you need!
How to install 1 (semi-automatic use)
===================================
A x86 binary is included (compiled on Pentium M, Ubuntu 8.10).
If you want to compile it for yourself, just delete the binary and run "make".
Or type at the shell (with other options of your choice):
> gcc -l usb -o usb_modeswitch usb_modeswitch.c
That's as easy as it gets ...
For installation run "make install" (you still have to edit the config file);
Or follow these manual steps:
Take the fresh executable "usb_modeswitch" (or the one provided with the
archive) and put it into your path (preferably "/sbin" or "/usr/sbin").
Put "usb_modeswitch.conf" into "/etc" and edit it according to your hardware.
It's heavily commented and should tell you what to do.
Alternatively you can use the command line to tell USB_ModeSwitch the things
it needs to know; try "usb_modeswitch -h" to list the parameters.
This way you can handle multiple configurations. If any command line parameters
except -W and -q are used, the default config file is NOT read.
Important: libusb stuff - like this tool - needs to be run as root!
For details how to automate the process visit the homepage (see above).
How to install 2 (fully automatic use)
===================================
New since version 1.0.3: a fully automatic system integration that will be able
to identify every known device without user interaction.
If you want this, use this line at the shell:
> make integrated_install
This installs a config file folder "/etc/usb_modeswitch.d", two scripts, an "udev"
rules file and a slightly changed binary.
Important: you need "tcl" for this to work; if you enter "tclsh" and you get a "%"
prompt, you are set. The "tcl" package is part of all distributions I know.
Known working hardware
======================
For details and specific setup see the homepage and the config file.
The automatic installation is in alpha stage and requires your participation,
especially if you own a ZTE made device. There is still not enough
information to tell models and model versions apart. See the announcement of
1.0.3 !!
Contribute
==========
USB_ModeSwitch comes quite handy for experimenting with your own hardware if
not supported yet. You could try this approach:
Note the device's Vendor and Product ID from /proc/bus/usb/devices (or from
the output of lsusb); the assigned driver is usually "usb-storage". Then try
spying on the USB communication to the device with the same ID inside M$ Win-
doze. I recommend this tool:
"SniffUSB" (http://benoit.papillault.free.fr/usbsnoop/index.php.en).
Please post any improvements, new device information and/or bug reports to the
forum (see above) or send it to the author (see below)!
Whodunit
========
Copyright 2007, 2008, 2009 Josua Dietze (mail to the name from "usb_modeswitch.c"
at the domain "draisberghof.de"; please do not post the complete address to the
Net !) or write a personal message through the forum to "Josh"
Command line parsing, decent usage/config output and handling, advanced options
and bugfixes:
Joakim Wennergren (jokedst) (gmail.com)
TargetClass parameter implementation to support new Option devices/firmware:
Paul Hardwick (http://www.pharscape.org)
Created with initial help from:
"usbsnoop2libusb.pl" by Timo Lindfors (http://iki.fi/lindi/usb/usbsnoop2libusb.pl)
Config file parsing stuff borrowed from:
Guillaume Dargaud (http://www.gdargaud.net/Hack/SourceCode.html)
Hexstr2bin function borrowed from:
Jouni Malinen (http://hostap.epitest.fi/wpa_supplicant, from "common.c")
Code, fixes and ideas from:
Aki Makkonen
Denis Sutter
Lucas Benedicic
Roman Laube
Luigi Iotti
Vincent Teoh
Tommy Cheng
Daniel Cooper
Andrew Bird
More contributors are listed in the config file.
History
=======
Version 1.0.5, 2009/08/26
More changes and fixes regarding success check; "--version" option;
config "database" updated
Version 1.0.4, 2009/08/23
Success check bugs (and others) fixed
Version 1.0.3, 2009/08/20
Success check improved; experimental system integration (fully automated),
optional; new parameter "TargetProductList" needed for this; other necessary
small adaptations; more devices
Version 1.0.2, 2009/06/10
Output bugs fixed
Version 1.0.1, 2009/06/08
Added output of descriptor strings for further identification
Version 1.0.0, 2009/06/01
Attention: possible incompatibilities for command line control!
On/off flags don't require arguments anymore (-H, -S, -O, -d, -R,
-n, new: -I), meaning "-R 0" does a reset like "-R 1" or "-R";
long option names changed to standard format (e.g. --HuaweiMode to
--huawei-mode); added device inquiry, for future help with device
identification; catch error -19 as possible success; send and response
endpoints now autoselected (consequently NeedResponse is back);
new devices
Version 0.9.7, 2009/04/15
Updated SonyMode, MD 400 now stable; automatic default endpoint
detection from Andrew Bird
Version 0.9.7beta, 2009/03/15
Major code clean up, optional success control (both suggested
by Daniel Cooper), new devices
Version 0.9.6, 2009/01/08
Special modes added for Sierra and Sony Ericsson, new devices
Version 0.9.5, 2008/10/27
New options for USB tuning (jokedst), lots of new devices, clean up
Version 0.9.4, 2008/06/09
Compat fix for libusb on FreeBSD quirks, more devices
Version 0.9.4beta2, 2008/03/19
Successful udev device release fix
Version 0.9.4beta, 2008/03/16
Multiple device support
Version 0.9.3, 2008/03/09
More devices, no changes from beta version
Version 0.9.3beta, 2007/12/30
New TargetClass parameter for recent Option firmware (Paul Hardwick), more devices
Version 0.9.2, 2007/11/02
New Huawei mode (code from Miroslav Bobovsky, added by Denis Sutter), more devices
Version 0.9.1beta, 2007/09/04 (jokedst)
Added command line parsing, cleaned up config stuff, doc updates
Version 0.9beta, 2007/08/15
Name change from "icon_switch", parameter file and generalizing
Version 0.2, 2006/09/25
Code cleaning, more messages
Version 0.1, 2006/09/24
(as "icon_switch") Just very basic functionality ...
Legal
=====
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details:
http://www.gnu.org/licenses/gpl.txt
Or find it as the file COPYING in this folder.
Last revised: 2009-08-26, Josua Dietze
Sobre lo que dice maxmalkav del archivo toolchain pues me parece que tiene razón porque yo no e instalado nada, solo me e bajo el programa y lo e intentado instalar. Me pueden decir que archivos son necesarios antes de instalar programas tar.bz2. Gracias

El toolchain es un conjunto de herramientas que te permiten compilar programas, en nuestro caso gcc, make y unas cuantas más. Instalatelas rápidamente con los siguientes comandos como root:

¿Por qué no lo instalas usando el archivo .deb? Ese paquete está en los repositorios.

Tienes dos opciones:
1.- Configurar repositorios mixtos.
2.- Descargar el paquete de este enlace e instalarlo con

dpkg -i nombre-del-archivo.deb

A primera vista creo que no tiene dependencias con otros paquetes de testing