Showing posts with label adb. Show all posts
Showing posts with label adb. Show all posts

Wednesday, August 1, 2012

Mac OSX Mountain Lion kills fastboot : « ERROR: Unable to create a plug-in (e00002be) »

After upgrading to Mac OSX Mountain Lion (10.8), the fastboot command does not work anymore, making it impossible to flash custom roms from OSX Mountain Lion.

Here is an extract of what happens when trying to use the fastboot command from OSX Mountain Lion command shell :

droid $ fastboot erase cache
ERROR: Unable to create a plug-in (e00002be)
< waiting for device >
ERROR: Unable to create a plug-in (e00002be)
ERROR: Unable to create a plug-in (e00002be)
ERROR: Unable to create a plug-in (e00002be)
ERROR: Unable to create a plug-in (e00002be)
ERROR: Unable to create a plug-in (e00002be)
ERROR: Unable to create a plug-in (e00002be)

^C
droid $
The workaround I've found so far is using the fastboot command from previous versions of Mac OSX : Lion (10.7.x) or Snow Leopard (10.6.x).

Friday, May 18, 2012

HTC One X (GSM - Tegra 3) : detailed instructions to flash "[18-05] [ROM] CyanogenMod 9 - Endeavor Unleashed | 008" step by step

Time to give my HTC One X (HOX) a "true" AOSP-based Android experience, so I decided to install the TripNDroid custom stock ROM [18-05] [ROM] CyanogenMod 9 - Endeavor Unleashed | 008 (look for the most up to date version on HTC One X with Tegra 3 - OneX.MoDaCo.com).

As usual, use it at your own risks as you may brick your device.



IMPORTANT : if something goes wrong ...
Head to the When something goes wrong section at the end of the F - Finalize the CyanogenMod flashing section



Prerequisites

This ROM is suitable only for the international HTC One X model (GSM - Tegra 3).

The [18-05] [ROM] CyanogenMod 9 - Endeavor Unleashed | 008 is still in alpha, not even in beta, so be sure you accept that some functions don't work properly !!!

You also have to unlock the bootloader and install a custom recovery. (small lexicon)

Head to HTC One X (GSM) : detailed instructions to unlock bootloader, install custom recovery and root for detailed, step by step, instructions and follow the instructions for A - Unlock the bootloader and B - Install a custom recovery.


A - Preparation

1) Download the file cm_endeavoru-ota-eng.noeri_008.zip on your computer from [18-05] [ROM] CyanogenMod 9 - Endeavor Unleashed | 008 (the link is near the end of the post #1, between "Download" and "Donations"). Put the downloaded file in the folder droid/ along with the fastboot command.

2) Unzip the file cm_endeavoru-ota-eng.noeri_008.zip in the folder cm_endeavoru-ota-eng.noeri_008/ and move the file boot.img in the same folder as the cm_endeavoru-ota-eng.noeri_008.zip. (Why should I manually flash the boot image ?)

3) Download the latest Google apps's file (gapps-ics-20120429-signed.zip) on your computer from gapps-ics-20120429-signed.zip. Put it in the folder droid/ along with the fastboot command.

4) Check the MD5 checksum for the Google Apps file gapps-ics-20120429-signed.zip by opening a command shell and entering the command

droid $ md5 gapps-ics-20120429-signed.zip
MD5 (gapps-ics-20120429-signed.zip) =
7c524e1e078164f681e0aa6753180b2c
droid $
Check the red part with the one provided in gapps-ics-20120429-signed.zip download page (MD5sum: 7c524e1e078164f681e0aa6753180b2c).

5) Plug the HTC One X on the USB cable.

6) Push the CM9 ROM cm_endeavoru-ota-eng.noeri_008.zip file at the root of the SDcard (/mnt/sdcard/).
You can do it by mounting the HTC One X as a USB device, and use your computer's file manager (Windows Manager or Finder) to copy the .zip file to the HTC One X
OR
you can use the adb push command from the command shell :

droid $ adb push cm_endeavoru-ota-eng.noeri_008.zip /mnt/sdcard/
730 KB/s (150106390 bytes in 200.604s)
droid $

7) Push the Google apps gapps-ics-20120429-signed.zip file at the root of the SDcard (/mnt/sdcard/) like you did it in 6).

8) Wait for 30 seconds then power off the HTC One X


B - Make a backup of your existing ROM using the custom recovery

9) Unplug the HTC One X from the USB cable.

10) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure your phone has at least 50% battery !!

11) Choose the RECOVERY item (the 2nd one) using Volume-Down button. Then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

12) Touch the "backup and restore" item.
The "Nandroid" screen appears.
The "backup" item is highlighted in blue.

13) Touch the "backup" item
The screen changes and the backup begins : boot image, recovery image, system, data, .android-secure, cache, sd-ext.
A md5 sum is automatically generated.
A "backup complete" message appears and the menu reappears.

14) Touch the "reboot system now" item to reboot your HTC One X.


C - Flash the boot.img

15) Power off the HTC One X. Ensure the HTC One X is not plug on the USB cable.

16) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.

17) Select the FASTBOOT item (highlight using Volume-Up / Volume-Down button) then press the Power button.
FASTBOOT should now be highlighted in red.

18) Plug the HTC One X on the USB cable.
FASTBOOT should become FASTBOOT USB still highlighted in red.

19) Flash the boot.img (Why should I manually flash the boot image ?) from the command prompt used in step 4), by entering the command

droid $ fastboot flash boot boot.img
sending 'boot' (4286 KB)...
OKAY [ 0.666s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.495s]
finished. total time: 1.161s
droid $

20) Power off the HTC One X using the Volume-Down button 3 times to select POWER DOWN. Then press the Power button.


D - Flash the CyanogenMod ROM

21) Unplug the USB cable from the HTC One X

22) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure the battery is fully charged !!

23) Select RECOVERY using the Volume-Down button, then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

24) Do some cleanup by touching the "wipe data/factory reset" item — which formats /data, /cache, /sd-ext, /sdcard/.android_secure .

OPTIONALLY : The "wipe data/factory reset" should be enough but if you want to be absolutely sure there's nothing left, you can continue the clean-up by touching the "wipe cache partition" item — which formats /cache — then touching the "mounts and storage". A new menu "Mounts and Storage Menu" appears. Touch the "format /data" item — which formats /data then go back to the "ClockworkMod Recovery v5.8.3.1" screen.

Many thanks to Nightranger73 for his help on the "wipe data/factory reset" issue.

25) Touch the 2nd item "install zip from sdcard"
The screen "Apply update from .zip on SD card" appears with the item "choose zip from sdcard" highlighted in blue.

26) Touch the highlighted item "choose zip from sdcard" (1st item, already highlighted)
The screen "Choose a zip to apply" appears with a list of files and directories.

27) Scroll through the files and directories (with your finger) until you see the file cm_endeavoru-ota-eng.noeri_008.zip (at the end of the list). Then touch it.
A new list appears

28) A new list appears with a lot of "No" and the item "Yes - Install cm_endeavoru-ota-eng.noeri_008.zip" in the middle. Touch the "Yes - Install cm_endeavoru-ota-eng.noeri_008.zip" item.
The installation begins and a log is displayed at the bottom the screen.
When the installation ends, you're back on the screen "Apply update from .zip on SD card".


E - Flash the Google Apps (optional)

29) Touch the highlighted item "choose zip from sdcard" (1st item, already highlighted) like you already did at step 26)
The screen "Choose a zip to apply" appears with a list of files and directories.

30) Scroll through the files and directories (with your finger) until you see the file gapps-ics-20120429-signed.zip (at the end of the list). Then touch it.
A new list appears

31) A new list appears with a lot of "No" and the item "Yes - Install gapps-ics-20120429-signed.zip" in the middle. Touch the "Yes - Install gapps-ics-20120429-signed.zip" item.
The installation begins and a log is displayed at the bottom the screen.
When the installation ends, you're back on the screen "Apply update from .zip on SD card".


F - Finalize CyanogenMod flashing

32) Touch the last item "++++Go Back++++"
You're now back on the screen "ClockworkMod Recovery v5.8.3.1"
The "Reboot system now" item is highlighted in blue.

33) Touch the "Reboot system now" item.
The HTC One X reboots.
The "HTC quietly brilliant" screen appears briefly.
Then the CyanogenMod 9 screen appears.
The update is rather quick, and you'll soon see the ICS screen.
A message box "Android is upgrading ..." may appear with the message "Optimizing application nn of nn"

If you're stuck for more than 5 minutes on the CyanogenMod startup screen, then something is going wrong !!...


When something goes wrong ...
Here are some places to find help :

Parameter Android

As all your data — accounts, parameters, applications, ... — have been wiped during the [18-05] [ROM] CyanogenMod 9 - Endeavor Unleashed | 008 installation process, you'll have to parameter again all the applications, accounts, ...


BUT YOU'VE NOT FINISHED !!



G - Reactivate the custom recovery [IMPORTANT]

34) Unplug the USB cable from the HTC One X

35) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure your phone has at least 50% battery !!

36) Select the FASTBOOT item (highlight using Volume-Up / Volume-Down button) then press the Power button.
FASTBOOT should now be highlighted in red.

37) Plug the HTC One X on the USB cable.
FASTBOOT should become FASTBOOT USB still highlighted in red.

38) Erase the cache from the command prompt used in step 5), by entering the command

droid $ fastboot erase cache
erasing 'cache'...
OKAY [ 0.086s]
finished. total time: 0.086s
droid $

39) Power off the HTC One X using the Volume-Down button 3 times to select POWER DOWN. Then press the Power button.


H - Ensure the custom recovery is reactivated

40) Unplug the USB cable from the HTC One X

41) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure your phone has at least 50% battery !!

42) Select RECOVERY using the Volume-Down button, then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

If the HTC One X does not enter the recovery mode, but briefly displays a black screen then started Android the normal way, you'll have to start again the recovery reactivation process from step 34)

If you want to make a backup recovery of your HOX right now, follow the instructions from steps 12) and 13)

43) Touch the "Reboot system now" item.
The HTC One X reboots.


Enjoy :-)

Wednesday, May 16, 2012

HTC One X : detailed instructions to install the "Ir1 1.29.401.7 - HTC One X (Tegra 3) Stock ROM DUO [Deodexed-Updated-Optimised]" step by step

As the 1.29.401.7 OTA failed due to custom recovery - failed to verify whole-file signature, I decided to install the Modaco custom stock ROM DUO Ir1 1.29.401.7 - HTC One X (Tegra 3) Stock ROM DUO [Deodexed-Updated-Optimised] (direct link on Modaco).

As usual, use it at your own risks as you may brick your device.


Prerequisites

This ROM is suitable only for the international HTC One X model (GSM - Tegra 3).

You also have to unlock the bootloader and install a custom recovery. (small lexicon)

Head to HTC One X (GSM) : detailed instructions to unlock bootloader, install custom recovery and root for detailed, step by step, instructions and follow the instructions for A - Unlock the bootloader and B - Install a custom recovery.


Preparation

1) Download the file Ir1-1.29.401.7-DUO-endeavor.zip on your computer from Ir1 1.29.401.7 - HTC One X (Tegra 3) Stock ROM DUO [Deodexed-Updated-Optimised]. Put the downloaded file in the folder droid/ along with the fastboot command.

2) Check the MD5 checksum of the Ir1-1.29.401.7-DUO-endeavor.zip file you've just downloaded by opening a command shell and entering the command

droid $ md5 Ir1-1.29.401.7-DUO-endeavor.zip
MD5 (Ir1-1.29.401.7-DUO-endeavor.zip) = cf763aedeb6699219f53e8cdbb58109d
droid $
Check the red part with the one provided in Ir1 1.29.401.7 - HTC One X (Tegra 3) Stock ROM DUO [Deodexed-Updated-Optimised] (MD5: cf763aedeb6699219f53e8cdbb58109d) .

3) Unzip the file Ir1-1.29.401.7-DUO-endeavor.zip in the folder Ir1-1.29.401.7-DUO-endeavor/ and move the file boot.img in the same folder as the Ir1-1.29.401.7-DUO-endeavor.zip. (Why should I manually flash the boot image ?)

4) Plug the HTC One X on the USB cable.

5) Push the Ir1-1.29.401.7-DUO-endeavor.zip file at the root of the SDcard (/mnt/sdcard/).
You can do it by mounting the HTC One X as a USB device, and use your computer's file manager to copy the .zip file to the HTC One X
OR
you can use the adb push command from the command shell :

droid $ adb push Ir1-1.29.401.7-DUO-endeavor.zip /mnt/sdcard/
1280 KB/s (579827689 bytes in 442.067s)
droid $

6) Wait for 15 seconds then power off the HTC One X


Make a backup of your existing ROM using the custom recovery

7) Unplug the HTC One X from the USB cable.

8) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure your phone has at least 50% battery !!

9) Choose the RECOVERY item (the 2nd one) using Volume-Down button. Then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

10) Touch the "backup and restore" item.
The "Nandroid" screen appears.
The "backup" item is highlighted in blue.

11) Touch the "backup" item
The screen changes and the backup begins : boot image, recovery image, system, data, .android-secure, cache, sd-ext.
A md5 sum is automatically generated.
A "backup complete" message appears and the menu reappears.

12) Touch the "reboot system now" item to reboot your HTC One X.


Flash the boot.img

13) Power off the HTC One X

14) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.

15) Select the FASTBOOT item (highlight using Volume-Up / Volume-Down button) then press the Power button.
FASTBOOT should now be highlighted in red.

16) Plug the HTC One X on the USB cable.
FASTBOOT should become FASTBOOT USB still highlighted in red.

17) Flash the boot.img (Why should I manually flash the boot image ?) from the command prompt used in step 5), by entering the command

droid $ fastboot flash boot boot.img
sending 'boot' (4292 KB)...
OKAY [ 0.670s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.497s]
finished. total time: 1.167s
droid $

18) Power off the HTC One X using the Volume-Down button 3 times to select POWER DOWN. Then press the Power button.


Flash the ROM

19) Unplug the USB cable from the HTC One X

20) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.

21) Select RECOVERY using the Volume-Down button, then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

22) Touch the 2nd item "install zip from sdcard"
The screen "Apply update from .zip on SD card" appears with the item "choose zip from sdcard" highlighted in blue.

23) Touch the highlighted item "choose zip from sdcard"
The screen "Choose a zip to apply" appears with a list of files and directories.

24) Scroll through the files and directories (with your finger) until you see the file Ir1-1.29.401.7-DUO-endeavor.zip (at the end of the list). Then touch it.
A new list appears

25) A new list appears with a lot of "No" and the item "Yes - Install Ir1-1.29.401.7-DUO-endeavor.zip" in the middle. Touch the "Yes - Ir1-1.29.401.7-DUO-endeavor.zip" item.
The installation begins and a log is displayed at the bottom the screen.
When the installation ends, you're back on the screen "Apply update from .zip on SD card".

26) Touch the last item "++++Go Back++++"
You're now back on the screen "ClockworkMod Recovery v5.8.3.1"
The "Reboot system now" item is highlighted in blue.

27) Touch the "Reboot system now" item.
The HTC One X reboots.
A dialog box "Android is upgrading ..." appears with the message "Optimizing application nn of nn"

As the Ir1 1.29.401.7 is a stock ROM, it is not needed to parameter again all the applications, accounts, ... Everything is saved.

Enjoy :-)

HTC One X international (GSM - Tegra3) : 1.29.401.7 OTA failed due to custom recovery - failed to verify whole-file signature

My HTC One X is an international model (GSM - Tegra 3) with a 1.28.401.9 ROM (Software Number). The stock recovery has been replaced with the Official Clockworkmod Touch Recovery 5.8.3.1.

The new 1.29.401.7 OTA upgrade (OTA_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.7-1.28.401.9_release) failed with the following error message :
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted

This error message has already been reported on 1.28.401.9 OTA in the thread 1.28.401.9 OTA problem with unlock/root?.

The error diagnosis is in broncogr's post :

You need stock recovery to apply OTA...
You dont flash it yourself from recovery!!!
The update program does that

The instructions to flash stock recovery in order for the upgrade to work were given in the posts by amacrobie and Squidinker, and merged here :
  • 1. Download the OTA using the handset : go to Settings -> About -> Software Updates -> Check now
  • 2. Flash stock recovery
    • Download the stock recovery http://loadbalancing.modaco.com/download.php?file=endeavoru_recovery_signed.img (or download it from the link in the CWM thread iirc)
    • Put the file endeavoru_recovery_signed.img in the same place as the fastboot you used to change the bootloader the first time
    • Reboot the phone into Fastboot by holding down the vol-down and power switch. Keep holding it until you have the boot menu and can select Fastboot.
    • Then connect the phone by usb to your desktop.
    • Open a command shell (or a Command prompt on Windows)
    • Navigate to the folder with fastboot and type the following :
      fastboot flash recovery endeavoru_recovery_signed.img
  • 3. Reboot
  • 4. Go to Settings -> About -> Software Updates -> Check now
    Assuming you already downloaded it, you'll be prompted to install it
  • 5. The OTA update reboots twice

From then you can re-flash the custom recovery, and the re-root : everything is detailed in HTC One X (GSM) : detailed instructions to unlock bootloader, install custom recovery and root

But it didn't work in my case : the OTA upgrade still continues to fail during the install. That's why I decided to flash the Modaco custom stock ROM DUO Ir1 1.29.401.7 - HTC One X (Tegra 3) Stock ROM DUO [Deodexed-Updated-Optimised]

Tuesday, May 8, 2012

HTC One X (GSM) : detailed instructions to unlock bootloader, install custom recovery and root

This only applies to the international (GSM) HTC One X model (the one with a Nvidia Tegra 3 chipset).


A - Unlock the bootloader
First of all, you have to unlock the bootloader as explained in HTC One X : HTCdev provides a process to unlock the bootloader. Although the HTCdev - Unlock Bootloader dedicated site provides very clear instructions, some may rather like to follow the detailed step by step instructions provided by [Tut] Preparing Your One X for Custom Roms (For Dummies).


B - Install a custom recovery

The second step is to install a custom recovery. I followed the detailed step by step instructions from [Tut] Preparing Your One X for Custom Roms (For Dummies)

B.1) Download the recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img from MANDATORY UPDATE 26/4 Official Clockworkmod Touch Recovery 5.8.3.1 Charging Fixed!!!. The link directs to the touch version of the custom recovery. A non-touch version of the custom recovery is available at ROM Manager - ROMs and Recovery Images.

B.2) Put the recovery image you've just downloaded into the same directory as the fastboot executable.

B.3) Check the MD5 checksum of the recovery image you've just downloaded. Open a command prompt and enter the command :

droid $ md5 recovery-clockwork-touch-5.8.3.1-endeavoru.img
MD5 (recovery-clockwork-touch-5.8.3.1-endeavoru.img) = 6adc7248475c61cc5eb2ec951d3d0df0
droid $


Check the red part with the one provided with the recovery image.

B.4) Power off the HTC One X

B.5) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure your phone has at least 50% battery !!

B.6) Select the FASTBOOT item (highlight using Volume-Up / Volume-Down button) the press the Power button.
FASTBOOT should now be highlighted in red.

B.7) Plug the HTC One X on the USB cable.
FASTBOOT should become FASTBOOT USB still highlighted in red.

B.8) From the command prompt you used in step B.3), enter the command

droid $ fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
sending 'recovery' (5732 KB)...
OKAY [ 0.885s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [ 0.556s]
finished. total time: 1.441s
droid $


B.9) Power off the HTC One X using the Volume-Down button 3 times to select POWER DOWN. Then press the Power button.

B.10) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
The FASTBOOT item should be highlighted in blue.

B.11) Choose the RECOVERY item (the 2nd one) using Volume-Down button. Then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

B.12) Touch the "backup and restore" item.
The "Nandroid" screen appears.
The "backup" item is highlighted in blue.

B.13) Touch the "backup" item
The screen changes and the backup begins : boot image, recovery image, system, data, .android-secure, cache, sd-ext.
A md5 sum is automatically generated.
A "backup complete" message appears and the menu reappears.

B.14) Touch the "reboot system now" item to reboot your HTC One X.

The custom recovery is installed and you now have a backup from which you can recover if things goes wrong later.


C - Root the HTC One X

The third step is to root the HTC One X.
I followed the instructions from Installing a custom recovery which also explains how to install the [07.05.2012] SuperSU v0.89.

C.1) Download the SuperSU application (file CWM-SuperSU-v0.89.zip) which is attached in the [07.05.2012] SuperSU v0.89.

C.2) Put the SuperSU application (file CWM-SuperSU-v0.89.zip) at the root of your HTC One X sdcard (into the folder /sdcard). There are different ways to do it. I rather like to use the adb push command

droid $ adb push CWM-SuperSU-v0.89.zip /sdcard/CWM-SuperSU-v0.89.zip
786 KB/s (569873 bytes in 0.707s)
droid $ adb shell
shell@android:/ $ ls -l /sdcard/CW*
----rwxr-x system sdcard_rw 569873 2012-05-08 20:58 CWM-SuperSU-v0.89.zip
shell@android:/ $ exit
droid $


C.3) Unplug the USB cable from the HTC One X

C.4) Power off the HTC One X

C.5) Power on the HTC One X in bootloader mode by holding Volume-Down button while pressing the Power button.
FASTBOOT should be highlighted in blue.
Before doing this, you should ensure your phone has at least 50% battery !!

C.6) Select RECOVERY using the Volume-Down button, then press the Power button.
The "quietly brilliant" white HTC screen appears briefly.
Then the "ClockworkMod Recovery v5.8.3.1" black screen appears.
The "Reboot system now" item is highlighted in blue.

C.7) Touch the 2nd item "install zip from sdcard"
The screen "Apply update from .zip on SD card" appears with the item "choose zip from sdcard" highlighted in blue.

C.8) Touch the highlighted item "choose zip from sdcard"
The screen "Choose a zip to apply" appears with a list of files and directories.
Scroll through the files and directories (with your finger) and touch the file CWM-SuperSU-v0.89.zip.
The screen "Confirm install ?" appears.

C.9) Touch the item "Yes - Install CWM-SuperSU-v0.89.zip"
The installation begins and a log is displayed on the screen.
Then you're back on the screen "Apply update from .zip on SD card".

C.10) Touch the last item "++++Go Back++++"
You're now back on the screen "ClockworkMod Recovery v5.8.3.1"
The "Reboot system now" item is highlighted in blue.

C.11) Touch the "Reboot system now" item.
The HTC One X reboots.

C.12) The SuperSU application appears among the other applications on your HTC One X.
Touch the SuperSU application.

If you like SuperSU and want to support it, maybe would you want to upgrade to the SuperSU Pro.


Important note about the SuperSU rooting application

The following quote comes from SuperSU - Chainfire

The discussion and support thread can be found on XDA-Developers here:
http://forum.xda-developers.com/showthread.php?t=1538053

SUPERUSER
This is meant to replace Superuser (if installed), you use either one or the other. You cannot combine them. Statements that this breaks Superuser are therefore completely nonsensical.

NOTICE: A SPECIAL PROCEDURE IS NEEDED FOR UNINSTALLATION. IF YOU DO NOT LIKE THE APP, DO *NOT* JUST UNINSTALL IT, YOU *WILL* LOSE ROOT.
Superuser access management runs through a so called "su binary". There can be only one of these at a time. So if you install SuperSU, your previous superuser access management solution will no longer operate. So if you want to switch back: (1) Open that application, and search for an option for it to install/update/replace the "su binary". (2) Confirm root-using apps are using the superuser solution you want. (3) Uninstall SuperSU.

Android rooting and custom ROM : small lexicon before rooting HTC One X

What is :
  • hboot : It's the bootloader. It's what decides to boot into recovery or android. (http://androidforums.com/desire-all-things-root/436495-hboot.html#post3386080). HBOOT is the bootloader, the first thing that runs when you boot up your phone. Like your regular Linux bootloader, it lets you boot off of different partitions. (Can someone explain these Android ROM hacking terms: HBOOT/bootloader, radio, recovery image, update.zip, NAND unlocking, RUU?)
  • recovery : In Android, recovery refers to the dedicated, bootable partition that has the recovery console installed. (What is recovery? [Android A to Z])
  • S-OFF & S-ON : In a nutshell, S-OFF means that the NAND portion of the device is unlocked and can be written to. The default setting for HTC’s devices is S-ON, which means that neither can you access certain areas of the system nor can you guarantee a permanent root. Furthermore, signature check for firmware images is also ensured by the S-ON flag. (What Is S-OFF & How To Gain It On HTC Android Phones With unrevoked forever and another one What is S-OFF? Why would I want to do it?)
  • NAND : The phone's internal memory (not the SD card) is solid-state (flash) memory, AKA NAND. It can be partitioned much like a normal hard drive can be partitioned. The bootloader exists in its own partition. Recovery is another partition; radio, system, cache, etc are all partitions.
    [...]
    During the rooting process, a critical piece of the process is disabling a security system built into the bootloader that protects these partitions from accidental (or intentional) modification. This is what's referred to as "unlocking NAND." The security system can be set to active or inactive. S-ON means the security is in place (NAND locked). S-OFF means the security is off (NAND unlocked). When S-OFF, you have the ability to modify all partitions. With S-ON, you only have write access to /cache and /data. Everything else is read-only.(Android partitions, kernels explained)
  • NANDroid & NAND backup : It's a backup and restore tool that allows you to take a full image of all the phone's internal NAND memory (hence the name) and store it on your SD Card. Should something go wrong with the phone's software, you can use the previously saved backup to restore the phone to a working state. (What is the relation between ROM Manager, ClockworkMod and Nandroid? Which one(s) do I need?)
    A Nandroid backup is a backup of your phone that is an exact image of the state of your phone. So you could make an exact copy of your current phone, then do major changes to it, and then restore to your previous backup by flashing the backup back to the phone. Flashing means to copy or to install.... you are essentially wiping the device and restoring a previous state (a backup) or you are flashing a new ROM (which is a custom version of Android). (What do “NAND”, “ROM” and “to flash” mean? [closed])
  • Odexed : In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution. (What does odexed and deodexed mean ?)
  • DeOdexed : Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
    In summary, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity." (What does odexed and deodexed mean ?)

Here are some resources for a more complete introduction :
And what rooting is useful for :

Saturday, December 10, 2011

Google Galaxy Nexus : How to unlock bootloader & root GSM Nexus - how to restore official factory image

Google Galaxy Nexus resources can be found on XDA Developers forum.

There are detailed instructions on [HOW TO] Unlock Bootloader & Root GSM Nexus. Take care that this is for the i9250 model (the european model with the i9250XXKK1 baseband version and the ITL41F build number)

There are also instructions on how to restore the [ROM] Official Factory Image ITL41F.

Thursday, November 11, 2010

obfuscation : how to use the obfuscation in the android app development cycle

This post deals with how the new obfuscation step modifies the app development cycle.

I use Eclipse to develop my app (Track Site). After some upgrade, when the app is ready to go live, I usually do the following tasks in order to publish it on the Android Market :
  1. adjust the version number
  2. export an unsigned version of the app from Eclipse
  3. sign it using the standard jarsigner tool
  4. align it using the standard zipalign tool

Obfuscation, as explained in Proguard, Android, and the Licensing Server, involves additional steps that replace the former 2) to 4) steps :
  1. adjust the version number the same way you've done it before
  2. obfuscation is performed using ant (not Eclipse) by issuing a command on the terminal

    mac:TrackSites $ ant release
    Buildfile: ~/workspace/TrackSites/build.xml

    As indicated in the Proguard, Android, and the Licensing Server post, the local.properties file has been modified to perform the signing step [3)] automatically (it still asks you for the passwords though), as well as the alignment one [4)].

    You end up with a signed, aligned and obfuscated app file in the bin/ sub-directory : the app is named SiteListActivity-release.apk. Exporting the unsigned app from Eclipse generates an app file named TrackSite.apk.

    It's interesting to note that the obfuscation process is done in another hierarchy (bin/classes) than the one used by Eclipse (bin/).

  3. as the obfuscation may have broken things, there is another quality assurance phase of the obfuscated app (SiteListActivity-release.apk), not of the non-obfuscated app that has already been tested from Eclipse (TrackSite.apk)

    This should be done :
    a) on the emulator :
    • start the emulator in the background with an AVD as a parameter
      mac:TrackSites $ emulator -avd a8w480 -wipe-data &
      [1] 536
      2010-11-11 10:14:15.172 emulator[491:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.


      The -wipe-data option in the command line allows to « Reset the current user-data disk image (that is, the file specified by -datadir and -data, or the default file). The emulator deletes all data from the user data image file, then copies the contents of the file at -inidata data to the image file before starting. ».

      Here is the emulator state when it is started without the -wipe-data option
      And it's state with the -wipe-data option

      The list of devices + emulators connected to the computer is obtained with
      mac:~ $ adb devices
      List of devices attached
      HTxxxxxxxxxx device <----- the real device emulator-5554 device <----- the emulator

    • install the obfuscated app (SiteListActivity-release.apk) on the emulator using adb command line tool
      mac:TrackSites $ cd bin
      mac:bin $ ls Site*
      SiteListActivity-release.apk SiteListActivity-unsigned.apk
      SiteListActivity-unaligned.apk SiteListActivity.ap_
      mac:bin $ adb -e install SiteListActivity-release.apk
      1340 KB/s (94595 bytes in 0.068s)
      pkg: /data/local/tmp/SiteListActivity-release.apk
      Success
      mac:bin $

      The -e option in the command line « direct an adb command to the only running emulator instance. ».

      The app is now installed in the emulator where it can be tested :

    b) on a real device : it's pretty much the same process as above but on a real device instead of an emulator.

    When installing the app on the device, you may encounter an error if a previous version of the app has been installed from the market :
    mac:bin $ adb -d install SiteListActivity-release.apk
    821 KB/s (94595 bytes in 0.112s)
    pkg: /data/local/tmp/SiteListActivity-release.apk
    Failure [INSTALL_FAILED_ALREADY_EXISTS]
    mac:bin $

    By the way, please take note of the -d option in the command line « direct an adb command to the only attached USB device. ».

    The solution here is to remove the app on the device : Menu -> Settings -> Applications -> Manage applications then select the application to uninstall, click on the "Uninstall" button, confim ... it works ! But there's a better solution using adb :
    mac:bin $ adb -d uninstall fr.androidtobe
    Success
    mac:bin $


    You can now try to install just like before :
    mac:bin $ adb -d install SiteListActivity-release.apk
    839 KB/s (94595 bytes in 0.110s)
    pkg: /data/local/tmp/SiteListActivity-release.apk
    Success
    mac:bin $

  4. Ensure everything works and that the obfuscation has not broke anything. Then publish the obfuscated app (SiteListActivity-release.apk).

    If something has been broken during the obfuscation step, look for clues in the « But Wait, My App is Crashing Now » part of the Proguard, Android, and the Licensing Server post

Tuesday, November 9, 2010

HTC Desire HD - the permanent root with [DEV] PERMROOT & eMMC write [INSTRUCTIONS]

A permanent root solution has been found for the HTC Desire HD. Detailled instruction are in the XDA-Developers post [DEV] PERMROOT & eMMC write [INSTRUCTIONS].

Nexus One : how to prepare for Gingerbread

The next release of Android, Gingerbread, is rumored to be OTA released in the coming days. Android Central, working with XDA-Developers wiki comes with a welcomed [How-to] Prep Nexus One for Gingerbread

« If you're like us, and have your Nexus One hacked nine ways to Sunday, you'll need to get ready if you don't feel like waiting for someone to rip it apart and whip up a version for the rooted and ROM'd crowd. »

Saturday, November 6, 2010

Nexus One - installing [ROM] Enomther's TheOfficial Nexus1 - v2.13.2 - 10/11/2010

I've decided to give a try to [ROM] Enomther's TheOfficial Nexus1 - v2.13.2 - 10/11/2010.

The Nexus state before installing Enomther's TheOfficial ROM :


Here are the detailled steps to install it on a rooted Nexus One.
  1. connect the Nexus to your computer using the USB cable
  2. download the resources and check the md5
  3. copy the files to the SD card.
    You can either mount your phone in USB storage mode (recommended) or use adb tool
    The files to be copied to the root of the SD card are :
    • RADIO TheOfficial_Nexus1_Radio_Update_4.06.00.12_7.zip
    • ROM : TheOfficial_Nexus1_v2.13.2_update.zip
    • MUSIC : origmusic_2.12.1.zip
    • CAM : origcam_2.12.3_kernel_audiomod.zip
    • TORCH : CMMod_Torch_2.11.3.apk.apk
    The RADIO TheOfficial_Nexus1_Radio_Update_4.06.00.12_7.zip will be flashed.
  4. make a Nand backup
    • Reboot the Nexus One in bootloader mode : hold down the trackball while you press the power button. Ensure to maintain the trackball hold down until the screens turns to a white screen with 3 green android skating at the bottom of the screen. Ensure that the Nexus One stay connected to the computer via the USB cable.
    • on the screen, the BOOTLOADER should be highlighted with blue. press power button
      on the new screen, scroll down with the Volume down button to highlight the RECOVERY option. Press the power button.
    • the Nexus One reboots and after a few seconds, the screen title with "Android system recovery" appears, with the "Build : RA-nexus-v1.7.0" at the bottom of the screen. The screen should be in cyan instead of green if the Nexus One has already been rooted
    • scroll down with the trackball to the "Backup/Restore" menu and press the trackball
    • on the new screen "Choose backup/restore item" choose the option "Nand Backup" (the first one) by scrolling down the trackball and press the trackball to select it. The question "Create Nandroid backup?" appears at the bottom of the screen, so press the trackball to confirm as it is stated
    • The backup starts, it takes a few seconds to complete. At the end of the backup, the cyan screen is restored. Press Volume down button to return to the previous screen "Android system recovery".
  5. flash the RADIO
    • back to the Android system recovery screen, scroll down to the Flash zip from sdcard item using the trackball. Press the trackball to select
    • on the new screen Choose update ZIP file, use the trackball to select the right ZIP file to flash. Start with the RADIO TheOfficial_Nexus1_Radio_Update_4.06.00.12_7.zip. then press the trackball to start the flashing. Press the trackball again to confirm flashing on the question "Install : TheOfficial_Nexus1_Radio_Update_4.06.00.12_7.zip ?" that appears at the bottom of the screen. The ROM flashing starts and many messages appears on the screen.
    • after some time, the message "Install from sdcard complete" appears and you're asked to reboot the phone to write the image on the phone. Press the trackball to proceed
    • after some time, you're back to the Android system recovery screen
  6. WIPE
    • from the Android system recovery screen, select the WIPE item using the trackball and press it
    • from the new screen "Choose wipe item", highlight the "wipe data/factory reset" item (the first one) and press the trackball once to select it, then press the trackball another time to confirm to proceed as it is asked at the bottom of the screen
    • then redo the same steps for the "Wipe cache", "Wipe Dalvik-cache", "Wipe battery stats", "Wipe rotate settings" but don't wipe the "SD:ext partition"
    • press VOL-DOWN to return to the Android system recovery screen
  7. flash the ROM
    • highlight the "Flash zip from sdcard" item using the trackball and press the trackball to select the item
    • from the "Choose update ZIP file" screen, highlight the "TheOfficial_Nexus1_v2.13.2_update.zip" item and press the trackball to select it. Press the trackball another time to confirm as you're asked to at the bottom of the screen. The flashing starts. At the end of the process, you're back to the Android system recovery screen.
    • follow the same steps to flash the MUSIC origmusic_2.12.1.zip
      and CAM origcam_2.12.3_kernel_audiomod.zip files. The nexus reboots automatically after fashing each of those files.

After flashing the Enomther's TheOfficial Nexus ROM :

Thursday, October 28, 2010

Nexus One - how to upgrade to CyanogenMod-6.1 V6.1.0-RC1 (10/27/2010) - instructions

I have just installed the CyanogenMod-6.1 first release candidate V6.1.0-N1-RC1 - 10/27/2010 (CyanogenMod-6.1 for Nexus One: Holy crap, it's full of AWESOME! V6.1.0-RC1 (10/27/2010)). Just keep in mind it is the 1st Release Candidate and as such, there are still some issues.

As the required radio image is still radio-4.06.00.12_7.img (Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, 4.06 OR HIGHER REQUIRED!)), I just have to upgrade to the new CyanogenMod-6.1 6.1.0-RC1.

I slightly depart from Cyanogen's instructions to upgrade :
  1. Do a Nandroid Backup !
    --->> steps 1) to 11) from Nexus One - how to upgrade to CyanogenMod-5 [stable 5.0.6 version of 04/15/2010] - detailled instructions
  2. Wipe : I add this step as it prevents problems with Google Apps ; just remember to save everything before (don't forget to backup your Track Site's data).
    The wipe has to be done while in recovery mode just after the Nandroid backup (the previous step).
    Here are the detailled steps :
    • from the "Android system recovery" screen you are just after the step 11), scroll down to the "Wipe" item using the trackball, press on the trackball to select the item
    • On the "Choose wipe item" screen, choose the "Wipe cache" item (the 2nd one) using the trackball. The "Wipe cache" seems to be enough and does not need to reinstall all applications. Press the trackball a 2nd time to confirm on the question that appears on the back of the screen.
    • The wipe starts and takes a few seconds to complete. At the end of the wipe, the cyan screen is restored. Press Volume down button to return to the previous screen "Android system recovery".
    • follow on with step 14) of the upgrade procedure
  3. Install the CyanogenMod-6.1 6.1.0-N1-RC1 - 10/27/2010 ROM (your Google apps will be backed up automatically)
    --->> steps 14) to 16) from Nexus One - how to upgrade to CyanogenMod-5 [stable 5.0.6 version of 04/15/2010] - detailled instructions. Don't reboot at this time and continue with the step below
  4. There's a 4th step to Cyanogen's instructions to install the most up to date version of Google apps : HDPI-20101025 (UPDATE 11/03 : Google Apps have been made available in a dedicated place : http://goo-inside.me/google-apps/ ; a wiki dedicated to Google Apps have been made available )
    --->> steps 15) and 18) from Nexus One - how to upgrade to CyanogenMod-5 [stable 5.0.6 version of 04/15/2010] - detailled instructions. At the end, just reboot (or power-down by selecting the right option with the trackball in step 17)).

The detailed instructions to follow are pretty much the same as for Nexus One - how to upgrade to CyanogenMod-6 V6.0.0-RC1 (07/11/2010) - instructions to get the 6.1.0-N1-RC1 - 10/27/2010 ROM update-cm-6.1.0-RC1-N1-signed.zip installed.

Wednesday, July 14, 2010

Nexus One - how to upgrade to CyanogenMod-6 V6.0.0-RC1 (07/11/2010) - instructions

I have just installed the CyanogenMod-6 first release candidate V6.0.0-RC1 (07/11/2010) ([ROM] CyanogenMod-6 for Nexus One: Holy crap,full of AWESOME! V6.0.0-RC1 (07/11/2010) on XDA-developers) — the one that brings Froyo (Android 2.2) to my Nexus One.

As I had already installed the radio image radio-4.06.00.12_7.img when I had installed the CyanogenMod-5 5.0.8-N1, this time, I just have to upgrade to the new CyanogenMod-6 6.0.0-RC1.


So Cyanogen's instructions to upgrade are :

- Upgrading?
1. Do a Nandroid Backup!
2. Install the CyanogenMod-6 V6.0.0-N1-RC1 - 07/11/2010 ROM (your Google apps will be backed up automatically)

I add a 3rd step to Cyanogen's instructions to install the most up to date version of Google apps :
3. Optionally install the FRF91-HDPI Google Addon as CyanongenMod 5.0.8 installs EPF30+ Google Addon

The detailed instructions to follow are the same as for Nexus One - how to upgrade to CyanogenMod-5 [stable 5.0.6 version of 04/15/2010] - detailled instructions to get the CyanogenMod-6 V6.0.0-N1-RC1 ROM update-cm-6.0.0-N1-RC1-signed.zip installed, skipping the WIPE steps 12) and 13) as it is not a first install and as Cyanogen doesn't require a WIPE in it's instructions.

Then I do again step 15) to install the FRF91-HDPI Google Addon gapps-hdpi-FRF91-signed.zip and I finish by a power down on step 17) instead of a reboot.

On step 18) everything started as usual, but the boot time was longer.


First surprise, the screen looks like my personalized screen instead of the new Froyo screen. Then my Gmail account was unavailable, and it was impossible to register a new one, making any synchronization impossible.

I then have to perform a factory reset to solve the problem. Everything works well now. But it suggests Cyanogen's instructions need another step to perform some kind of wipe.


The new CyanogenMod-6 comes with new wallpapers.

Sunday, April 18, 2010

Nexus One - how to upgrade to CyanogenMod-5 [stable 5.0.6 version of 04/15/2010] - detailled instructions

I just upgraded my Nexus One to CyanogenMod-5: Kang Central Station (STABLE) [04/15/2010 / 5.0.6].

As it is just a CyanogenMod-5 upgrade from 5.0.5.3-N1 to 5.0.6-N1, only the following steps are required :
  1. download the Cyanogen 5.0.6-N1 (the latest stable CyanogenMod for the Nexus One) from Cyanogenmod For Nexus One V5.0.6 (04/15/2010) : update-cm-5.0.6-N1-signed.zip
  2. check the MD5 sum :
    md5 update-cm-5.0.6-N1-signed.zip
    and check the checksum
    MD5 (update-cm-5.0.6-N1-signed.zip) = 43835d679958294befa16af78bf7311b
    against the one of the forum MD5Sum: 43835d679958294befa16af78bf7311b
  3. connect the Nexus One to the computer and mount the Nexus One in the Mac
  4. copy the Cyanogen 5.0.6-N1 (the update-cm-5.0.6-N1-signed.zip) file to the root of the Nexus One SD-card. Wait a few seconds in order to be sure everything is copied to the SDcard. Unmount the Nexus One on your computer.
  5. Reboot the Nexus One in bootloader mode : hold down the trackball while you press the power button. Ensure to maintain the trackball hold down until the screens turns to a white screen with 3 green android skating at the bottom of the screen. Ensure that the Nexus One stay connected to the computer via the USB cable.
  6. on the screen, the BOOTLOADER should be highlighted with blue. press power button
  7. on the new screen, scroll down with the Volume down button to highlight the RECOVERY option. Press the power button.
  8. the Nexus One reboots and after a few seconds, the screen title with "Android system recovery" appears, with the "Build : RA-nexus-v1.7.0" at the bottom of the screen. The screen should be in cyan instead of green if the Nexus One has already been rooted
  9. scroll down with the trackball to the "Backup/Restore" menu and press the trackball
  10. on the new screen "Choose backup/restore item" choose the option "Nand Backup" (the first one) by scrolling down the trackball and press the trackball to select it. The question "Create Nandroid backup?" appears at the bottom of the screen, so press the trackball to confirm as it is stated
  11. The backup starts, it takes a few seconds to complete. At the end of the backup, the cyan screen is restored. Press Volume down button to return to the previous screen "Android system recovery".
  12. FIRST INSTALL ONLY : scroll down to the "Wipe" item using the trackball and press the trackball to select the option
  13. FIRST INSTALL ONLY : in the new screen "Choose wipe item", using the trackball, select every wipe item one after the other and perform the wipe pressing the trackball. When every wipe has been performed, return the the previous screen using Volume Down button.
  14. back to the Android system recovery screen, scroll down to the Flash zip from sdcard item using the trackball. Press the trackball to select
  15. on the new screen "Choose update ZIP file", use the trackball to select the right ZIP file to flash. Here, there should be only one zip file available to flash : update-cm-5.0.6-N1-signed.zip. then press the trackball to start the flashing. Press the trackball again to confirm flashing on the question "Install : update-cm-5.0.6-N1-signed.zip ?" that appears at the bottom of the screen. The ROM flashing starts and many messages appears on the screen.
  16. after some time, the message "Install from sdcard complete" appears and you're back to the cyan screen "Android system recovery" with the item "Reboot system now" selected by default
  17. just select the default option by pressing the trackball down. The Nexus One reboots.
  18. after the Nexus One has boot the normal way, just to be sure, check the "Mod version" value in the "Setting" then "About Phone" : the value should be "CyanogenMod-5.0.6-N1"

I adapted the instructions from Step by Step Guide on How to Install Cyanogen Mod ROM on your Nexus One! to perform the upgrade.

Thursday, April 15, 2010

Nexus One - CyanogenMod For Nexus One V5.0.5.3 (03/23/2010)

I have just installed CyanogenMod For Nexus One V5.0.5.3 (03/23/2010). It takes me quite some time because I missed some important points, the most important one being to root my Nexus using superboot.

Cyanogen's advise is to download everything that will be necessary and to check the md5 checksum.

Then, the first step is to unlock the bootloader using fastboot. fastboot can't be found in the android sdk but it can be found in the superboot archive contents.

During the whole process, I've found useful instructions in those locations :
Everything seems to work well. More feedback soon.

Saturday, January 30, 2010

Nexus One - activate ADB connection mode

By default, the Nexus One is not visible from ADB while executing the adb devices command from the terminal.

$ adb devices
List of devices attached
emulator-5554 device


Instead, it can be is mounted like a USB key.

To access the Nexus One using ADB commands, the USB debugging mode has to be checked in the Android global setting (Menu button, then Settings item, then Applications item, then Development item, then check USB debugging mode).

$ adb devices
List of devices attached
emulator-5554 device
xxxxxxxxxxxx device

Wednesday, December 16, 2009

Archos's solution to ADB connection bug with Mac OSX since 1.4.xx firmwares

Archos support proposes a solution to the bug on ADB connection mode with Mac OSX 10.6.2 with firmwares updates since 1.4.07 to the latest 1.4.16 :

You actually need to modify or create the adb_usb.ini file

In terminal, you need to type :
echo "0x0e79" >~/.android/adb_usb.ini
Then
./adb kill-server
and
./adb start-server


I just modify the first command in order to preserve the original contents of the ~/.android/adb_usb.ini file by issuing the following command
echo "0x0e79" >> ~/.android/adb_usb.ini


Here is the result :

$ adb devices
List of devices attached

$ adb devices
List of devices attached

$ more ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
$ echo "0x0e79" >> ~/.android/adb_usb.ini
$ more ~/.android/adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79
$ adb kill-server
$ adb start-server
$ adb devices
List of devices attached
A5S-xxxx0004-xxxx0000-0403xxxx-1500xxxx device


All works perfectly.

Monday, December 14, 2009

Archos 5 IT - firmware 1.4.16 - bug on ADB with MacOSX still exists - driver ExtFS for Mac OSX

Le nouveau firmware 1.4.16 ne corrige toujours pas le bug dans la connexion en mode ADB sur Mac OSX 10.6.2

« adb devices » ne trouve pas l’A5IT

Bug déjà signalé sur la 1.4.08 (http://www.jbmm.fr/2009/11/26/2-firmwares-sinon-rien/) et la 1.4.09 (http://www.jbmm.fr/2009/11/28/et-hop-un-firmware-archos-5it/)

Avant de décider si je repasse à nouveau en 1.3.07, je vais tester le driver Paragon ExtFS for Mac OS X signalé par ArchosLounge.net dans son article Archos 5IT et le Mac : LA solution !


---------------------- English version -----------------------

The new firmware 1.4.16 still doesn't solve the bug in the ADB connection mode with Mac OSX 10.6.2

« adb devices » doesn't discover the A5IT device

Bug has been signaled on 1.4.08 (http://www.jbmm.fr/2009/11/26/2-firmwares-sinon-rien/) and 1.4.09 (http://www.jbmm.fr/2009/11/28/et-hop-un-firmware-archos-5it/) firmware versions

Before deciding to reinstall the 1.3.07 firmware, I will make a try with the driver Paragon ExtFS for Mac OS X which has been reported by ArchosLounge.net in Archos 5IT et le Mac : LA solution !

Sunday, December 13, 2009

Archos 5 IT and Mac OSX - when it comes to connecting in ADB mode

The filesystem used by the Archos 5 IT is ext3 as stated in the FAQ



As MacOSX does not support anymore, one way to connect the Archos 5IT to the Mac is by using ADB - Android Debug Bridge. Here are the Archos 5IT support instructions.


As stated, everything works directly with MacOSX, nothing to install.
To make a check :
  • connect the Archos 5IT to the Mac using the USB cable
  • open a Terminal (you'll find it in /Application/Utilities)
  • go to the directory where the Android SDK has been installed, and from here, go to the tools sub-directory (you better add the Android SDK's path to your PATH)
  • just do an « adb devices » command
  • the answer should be something like

    List of devices attached
    0123456789ABCDEF device

    where the device is the Archos 5IT

Instructions to use ADB can be found on Android's Developers site and on Android wiki. In short, exec a « push » to put a file on the device and a « pull » to get a file from the device.

Using ADB, you can even access the full Archos 5IT filesystem.


ADB support bug in the Archos 5IT latests firmwares

The 1.4.09 and 1.4.08 Archos 5 IT firmwares both have a bug in the ADB support that makes the device not be found and ADB mode not working at all.
You have to stay back on Archos 5IT 1.3.07 firmware in order to use ADB connection mode on Mac OSX.