no consigo instalar los driver

**blerfont** · #21 17/05/10, 17:13:22

uhmm.. haz un "adb logcat" y dime lo que te pone

jesulinsaxo · #22 17/05/10, 17:14:52

waiting for device...

**blerfont** · #23 17/05/10, 17:22:23

http://rapidshare.com/files/36014964...re-v1.6.2G.img

Prueba con ese recovery...

jesulinsaxo · #24 17/05/10, 17:26:04

nada... la misma pantalla negra con htc magic... pruebo con el comando flash o no?

**blerfont** · #25 17/05/10, 17:28:01

Prueba, no pierdes nada

Si intentas entrar en el recovery, es decir, boton power+casita, te aparece un triangulo?

jesulinsaxo · #26 17/05/10, 17:30:16

sale el mismo error de FAILED.... y no, no sale el triangulo al pulsar esos botones

**blerfont** · #27 17/05/10, 17:31:08

Que sale? Nada? Pantalla en negro simplemente?

jesulinsaxo · #28 17/05/10, 17:32:02

No no, al hacer el comando de flash en el ordenador sale lo FAILED pero el movil se queda en la pantalla de fastboot tal cual...

**blerfont** · #29 17/05/10, 17:35:00

Ok, de todas formas, entra en esta pagina:

http://developer.htc.com/google-io-device.html

Ve a la seccion "Download the Image Packages"

Descargate el paquete "signed-google_ion-ota-14721.zip"

Y dentro del paquete deben venir varios archivos img, uno de ellos debe ser un recovery.img, intenta hacer el flash de ese archivo

jesulinsaxo · #30 17/05/10, 17:38:19

me bajo el de 1.6 aunque en la rom esa que tenia ahora pusiera 1.5?

**blerfont** · #31 17/05/10, 17:39:37

Perdon, los pasos son estos:

Copy the Recovery Image Package to the Device

For the recovery-image method only, after you've successfully updated the radio firmware, the next (and final) step is using the adb tool to copy the recovery image package to the device SD card. (If you are using the fastboot method, you do not need to copy a recovery image to the device - see Flash the System Image Package to the Device instead.)

To copy the recovery image to the device SD card, follow these steps:

Ensure that the SD card containing the updated radio image is inserted in the device
Boot the device normally
Connect the device to your development machine over USB.
At a command line, ensure that adb recognizes your device by issuing this command:

$ adb devices

You should see your device in the console output generated by the command

Use the adb sync command to copy the contents of the radio image package to the update.zip archive on the device's SD card:

$ adb push <recovery-image-package>.zip /sdcard/update.zip

The command prints the number of bytes copied and the elapsed time, then completes. However, note that the files are still being copied in the background, so wait a minute or two before continuing. If you continue too soon and terminate the operation before it is complete, you will get a "bad update.zip" error later, when you try to install the update.

To ensure that the entire recovery image package is copied before you continue, use this command:

$ adb shell sync

When sync returns, all of the data has been copied to the device.

Reboot the device into recovery mode by holding down the HOME key during reboot. When the device enters recovery mode, it displays a "!" icon.
Press the HOME+END key combination to display the recovery console.
Next, use the trackball to select the "apply sdcard:update.zip" option and press the trackball to begin the installation. An "Install from sdcard" status message is displayed — when the progress bar completes, the installation is finished. After writing the radio image, the device shows an "updating firmware" icon for a few seconds and then automatically reboots in normal mode.
After the device reboots normally, the operation is complete.

**blerfont** · #32 17/05/10, 17:39:57

Si, de la 1.6, no pasa nada

jesulinsaxo · #33 17/05/10, 17:55:48

pero yo no puedo encender la magic normalmente como creo que pone ahi (si no entiendo mal...)

jesulinsaxo · #34 17/05/10, 18:01:40

asi si puedo hacerlo no?

Flash the System Image Package to the Device

For the fastboot method only, after you've successfully updated the radio firmware, the next (and final) step is using the fastboot tool to flash the system image package to the device. Note that you should always update the radio image whenever you update the Android system image on your device. (If you are using the recovery-image method, you do not need to flash the system image package to the device - see Copy the Recovery Image Package to the Device instead.)

Follow the steps below to flash a system image package to your device:

Boot the device in fastboot mode.
To enter fastboot mode, power up the device (or reboot it) while holding down the BACK key. Hold the BACK key down until the bootloader screen is visible and shows "FASTBOOT". The device is now in fastboot mode and is ready to receive fastboot commands. If you want to exit fastboot mode at this point, you can hold down the keys MENU+SEND+END (on the Google I/O Device, SEND is the "Call" key and END is the "End call" key).

Note that the bootloader screen may vary across devices. For Google I/O Device devices, the bootloader screen shows an image of skateboarding robots. Other devices may show a different image or color pattern. In all cases, the bootloader screen shows the text "FASTBOOT" when in fastboot mode. The bootloader also shows the radio version.

Connect the device to your development machine over USB, if it isn't currently connected.
You may want erase the contents of the userdata partition, by using this fastboot command:

$ fastboot erase userdata

This will remove all of the installed applications and their data, but it is a useful step when debugging because it ensures a clean execution environment for the application. Erasing the user data may also be necessary when you are flashing a lower (downgrade) platform version to your device. However, it is not strictly necessary to erase the userdata partition when upgrading to a higher (upgrade) platform version, which is the typical use-case in consumer devices.

You may also want to erase the cache partition, using this fastboot command:

$ fastboot erase cache

Note that, rather than using separate fastboot commands to erase the userdata and cache partitions, as described in the previous steps, you can simply supply the -w option when flashing the system image, which has the same result.

Next, use this fastboot command to flash the contents of the image package to the device:

$ fastboot update <imagepackage>.zip [-w]

With this command, fastboot copies all of the images in <system-image-package>.zip to the appropriate partitions on the device. During the process, it prints status messages to the command shell. Depending on your bootloader version, fastboot may also print status messages to the bootloader screen.

When all image are copied to the device successfully, fastboot displays a success message. If you encounter a problem, refer to the Troubleshooting section.

For information about other fastboot commands, use

$ fastboot

Reboot the device. In most cases, fastboot should reboot the device automatically after copying the image files.
If necessary, you can reboot the device manually using these fastboot commands:

$ fastboot reboot

or

$ fastboot reboot-bootloader

You can also reboot from the device by holding down the key combination MENU+SEND+END.

After rebooting, the device should start normally. If the device does not start normally, you can try flashing it again. If you did not erase the userdata partition and the device hangs during boot, try erasing the userdata partition and then reboot.

For discussions and support about updating your Google I/O Device, please head over to the io-device group.

**blerfont** · #35 17/05/10, 20:07:20

Del modo que yo te digo, tendrias que poner el zip en la microsd, sacando la tarjeta del telefono.

De tu modo instalas el sistema, pero no se si el recovery...

Prueba cualquiera de los dos metodos y cuentanos

Un saludo, suerte!

jesulinsaxo · #36 18/05/10, 00:01:24

el metodo que me dices ahora mismo no puedo hacerlo pues no tengo lector de tarjetas, y el otro metodo cuando lo empiezo ha hacer me da un error de que no le vale el bootloader, pero si miras al final de esa pagina, si entiendo bien, viene que hacer ese caso, total que descomprimo como dice ahi y le doy para que lo envie y tambien me sale el erro de FAILED (remote: signature verify fail)

**blerfont** · #37 18/05/10, 09:41:40

Por casualidad no tendrás por ahi ningun nandroid hecho de tu telefono como estaba inicialmente, verdad?

Ya que en los nandroid se hacen imagenes de sistema, del recovery, etc... y podrías probar a flashear alguna de esas imagenes de tu sistema original.

Si no tienes ningun nandroid... no se, podría pasarte yo algun recovery.img de alguno mio, pero no se si funcionaría o estariamos en las mismas que con cualquier recovery que te bajes de Amon_RA

Todo esto estoy hablandode flashearlo desde fastboot

Un saludo

jesulinsaxo · #38 18/05/10, 09:45:57

pues no... se ve que soy un desastre XD. Aunque puede que un recovery de una imagen tuya valiera no? porque seria uno digamos "original" o me estoy liando?XD

**blerfont** · #39 18/05/10, 09:55:32

Prueba a bajar e intentar arrancar/flashear este recovery:

http://www.droidaftermarket.com/kous...k-sapphire.img

ya sabes:
fastboot boot recovery-clockwork-sapphire.img
fastboot flash recovery recovery-clockwork-sapphire.img

Un saludo

jesulinsaxo · #40 18/05/10, 09:55:42

es que es muy raro... porque lo de no arrancar ningun recovery lo hacia aun habiendo conseguido instalarle la rom esa que pone en el metodo goldcard....