Posts Tagged ‘menu’

How to update the Archos Android firmware to 1.9.x under Ångström

Thursday, June 3rd, 2010

UPDATE:

This guide is outdated, please do not use it anymore! There is a new and updated procedure that is easy to follow and also shows you how to update the Archos firmware. The files linked to in this guide will be no longer available.


As you can’t just install the update the regular way (if it would work it would kill at least the boot menu) here are some steps how to update manually. This is only valid for firmware up to the 1.9.x series.

Currently it does NOT work with the 2.0.x firmware because that seems to have a modified Kernel to support the EGL SGX driver. Also if Archos releases an major update to a different Android version (like Eclair) there will be additional steps necessary!

  1. Unpack the Archos update file. Use archutil or aos-unpack (from aos-tools) or abcbox. Sorry for legal reasons we can not provide unpacked firmware.
  2. Boot into Android and via USB copy the previously unpacked androidroot.cramfs.secure and bitmapfs.cramfs.secure and all lang_*.alz files into the main directory of your device. Also copy the contents of the System directory into the System directory on your device. (If you want to use the script in step 7 then copy it too!)
  3. Unmount the device safely. (Else you might damage the files!)
  4. Reboot your A5IT.
  5. The Boot menu should now appear. Select Ångström or just wait 10s.
  6. Once in Ångström press Other then Root shell – a root terminal appears
  7. Now execute the following commands (this should be easy if you have some previous shell experience). Be very careful while typing on the on-screen keyboard. If you have one attach an USB-keyboard.
    • chattr -c /mnt_data/androidroot.cramfs.secure
    • chattr -c /mnt_data/bitmapfs.cramfs.secure
    • mount -t ubifs -o rw ubi0:system /mnt/ubi
    • cp /mnt_data/androidroot.cramfs.secure /mnt/ubi/
    • cp /mnt_data/bitmapfs.cramfs.secure /mnt/ubi/
    • cp /mnt_data/lang*.alz /media/sda2/

    Or use the small script mentioned in step 2:

    • to make it executable just run chmod 755 /mnt_data/update-script
    • and then execute it /mnt_data/update-script
  8. Congratulations you should now have an working 1.9.x firmware!

As already mentioned the openAOS boot-menu currently does not support the EGL SGX firmware 2.0.x . We will start working on adding support for it as soon as we receive updated Linux Kernel sources from Archos.

If you want to switch to the 2.0.x firmware for now – instead of being able to dual-boot – you can just install that firmware from the recovery menu. It will be easy to restore this functionality later. For now installing the SDE is NOT POSSIBLE after installing 1.9.x or 2.0.x as regular firmware updates. So beware, Archos seems to have promised an updated SDE but that might take a bit.

UPDATE: Archos have published an upgraded SDE meanwhile. So going back and forth between SDE, openAOS boot-menu and regular firmware is now again possible.

Cheers,

Thomas, your friendly ArchDruid

PS: I’m sorry, but I’m very busy right now so 2.0.x support might take a while to surface.

PPS: Merci mille fois à Enjolras pour la traduction française!

How to replace an broken harddrive in an gen6 unit with original firmware

Wednesday, April 21st, 2010

I’ve seen several cases where people report in to Archos related forums with an broken hard-drive. In most cases the firmware is Archos original, so it won’t accept a new hard-drive. You can install the firmware but it will refuse to boot…
Archos will replace the hard-drive on most of their units for a fee. There are some constraints though. As far as I know they will only replace it with identical capacity drives and it takes time to send the device in.

Today Archosfans user peterq finally confirmed unwittingly what I was suspecting all along:
If your original hard-drive failed you can swap the hard-drive yourself and get an working unit also with AVOS by then installing the SDE and subsequently flashing our Boot-Menu!
This comes also with some drawback: if your device is still covered by an Archos granted warranty then this is void. There is no way to hack the boot-loader to enable full write to flash – but besides for an custom boot logo, what would you need that for?

Also you will need to create the hidden partition yourself and populate it with the contents of an Archos firmware upgrade file. But that sure should still beat not having your Archos for a month, right?

To sum up. Good news for all Archos5 and Archos7 owners if their hard-drive ever dies!

If you have some time on your hands to play around: Please send in your guide how to create an hidden partition from scratch on an gen6 device. I might prepare another post on how to create the hidden partition from scratch myself, but that is very low on my priority list unless someone wants to motivate me buy “buying me a beer or two”. ;)

UPDATE: Problem solved! See peterq’s answer to my suggestion. All you need to do is to install an regular firmware first (don’t worry that it doesn’t boot!) and then proceed with the regular guide to installing the boot menu.

PS: I suspect this will also work on gen7, Archos5IT units but don’t have it confirmed.

openAOS Boot-Menu for gen7 Archos devices is here! Get the beta version now!

Monday, April 19th, 2010

UPDATE:

This guide is outdated, please do not use it anymore! There is a new and updated procedure that is easy to follow. The files linked to in this guide will be no longer available.

After spending most of the weekend reimplementing the init-script and cutting out everything that needed Archos binaries I spent this whole monday adapting the bitbake recipes and fixing minor bugs.

Ladies and Gentlemen! I present the public beta version of the openAOS Boot Menu for generation 7 hardware!

The openAOS Boot Menu now runs on 7th generation Archos devices!

The openAOS Boot Menu now runs on 7th generation Archos devices!

As this is just a beta version  (in the true meaning of this word!) some functionality around it is still missing. For now you have to set up most things yourself. For today just a short introduction (prerequisite is an Linux PC and an unpacked Archos Android firmware):

  1. Install the gen7 SDE on your device. Make sure Ångström boots.
  2. Reboot your device while holding down the [VOL -] button.
    • Press the [VOL -] button 5 times to reach the “Developer Edition Menu”. Then Press [Power]
    • Press the [VOL -] button 2 times to reach the “Flash Kernel and Initramfs” entry. Then Press [Power] ONCE. Wait 2 seconds.
    • The screen now should say “connect your device…” – Please do so and mount the device on your desktop PC.
  3. Download those four prepared files into the main directory of your device.
  4. Copy the previously unpacked androidroot.cramfs.secure and bitmapfs.cramfs.secure into the main directory of your device.
  5. Unmount the device safely. (Else you might damage the files!)
  6. Press the [Power] button – The screen will flash briefly and say “Kernel and initramfs updated”.
  7. Press the [Power] button – The device will now reboot.
  8. The Boot menu should now appear. Select Ångström or just wait 10s.
  9. Press Other then Root shell – a root terminal appears
  10. Now execute the following commands (this should be easy if you have some previous shell experience). Be very careful while typing on the on-screen keyboard. If you have one attach an USB-keyboard or see update at the bottom! ;)
    • tar -xvzf /mnt_data/ubitools.tar.gz
    • chattr -c /mnt_data/androidroot.cramfs.secure
    • chattr -c /mnt_data/bitmapfs.cramfs.secure
    • ./ubidetach /dev/ubi_ctrl -m 5
    • ./ubiformat /dev/mtd5 -y
    • ./ubiattach /dev/ubi_ctrl -m 5 -d 0 -O 2048 Make sure you get that right: …-d [ZERO] -[CAPITAL-O]
    • ./ubimkvol /dev/ubi0 -N system -m
    • mkdir /mnt/ubi
    • mount -t ubifs -o rw ubi0:system /mnt/ubi
    • cp /mnt_data/androidroot.cramfs.secure /mnt/ubi/
    • cp /mnt_data/bitmapfs.cramfs.secure /mnt/ubi/
  11. Now reboot the unit and go back into recovery (see step 2, this time select “Access HDD using a PC“)
  12. Connect it to your Linux PC and fire up a partition manager
  13. Make sure you are editing the right drive!
  14. Create an new ext3 partition in the empty space at the end of the drive. Make sure it is created as type primary and is the second partition (e.g. /dev/sdc2)! The unit will not boot Android if the partition is e.g. sdc3 or sdc5!
  15. Now mount that partition and copy some of the remaining contents of the firmware onto it (lang*.alz and the upselling directory)
  16. Unmount the drive and reboot your Archos device.
  17. Congratulations you should now have an dual-booting gen7 device!

The final version will hopefully automate 99% of the above process. If you know some shell scripting and want to help. Please let me know. I won’t have much time over the next few weeks myself.

PS: I should have mentioned that you can of course also generate an script put it onto your device together with the other four files in step 3 and then run it instead of step 10. /bin/sh  script
PPS: I’m working on an clean commit of the sources used to build the files. Please allow me a day or two as I currently have other priority tasks.

Sneak peak

Monday, March 29th, 2010

I’m posting this to give you an idea what we are currently working on.

And also so nobody thinks we’re a bunch of lazy people that don’t do anything.

The boot menu as you can see it is still a work in progress, e.g. the init script is currently more a proof of concept and will need some loving also currently I still have problems to mount the ubifs to boot into Android.

update: OK was just that I didn’t expect that Archos deleted the “system” but left “data” ubifs intact. PEBKAC detected …

update2: see finally running – Ångström & Android

Oh and before anybody asks, no we don’t have UAE running — yet! (So don’t ask for it, it’s actually rather at the bottom of the ToDo list…)

a work in progress shot of the boot manager for gen7 devices

a work in progress shot of the boot manager for gen7 devices

MultiBoot openAOS

Monday, January 25th, 2010

Yesterday I took the time to try out the improved boot menu by Kevin – our currently most active member. It’s really cool. You can even put AVOS (The original Archos® UI) in there!

The menu sports a nice C64-like low-res bitmap font look. I’ll try to post a photo later.
But the most impressive part: It comes with touchscreen support! Take that C64! ;-)
You just tap an boot menu entry twice and off you go!

openAOS boot menu

openAOS boot menu

I’ll try to post an small HowTo ASAP so it will be easier to join in on the fun.