Posts Tagged ‘boot-menu’

new openAOS boot menu version for gen6

Wednesday, July 28th, 2010

The plans for this have been quite long in our pipeline but we finally got around to making it happen. As users seem to like to go hence and forth between different Archos firmware versions we were often asked to make this easier. (You have to mount the hidden partition, copy the files, etc. – quite a hassle, especially if you don’t have an Linux PC at hand at the time)

So what we have done now is that before we display the boot menu we also check if the directory ‘openaos/update exists on the FAT32 partition (this is X:\openaos\update for you Windows people). If this is the case then we take everything¹ that is in that directory and copy it over to the hidden partition! Presto! Your Gen6 device just changed its firmware!

This way you can easily switch between e.g. firmware 1.6.54 and 1.7.11 . Some people told us that they do this because of certain features working better on the respective firmware.

All you have to do is install this initramfs together with an regular openAOS zImage like e.g. this from kevin’s r199. You can do this from the SDE menu in Recovery mode.

enjoy!

Thomas, your friendly neighborhood ArchDruid

PS: This comes also handy if you just installed SDE and flashed those two; as during the update procedure it will create the menu.lst correctly and add an AVOS entry if necessary!

¹ Everything in this context means the *cramfs.secure files, the lang* files and the upselling directory of an unpacked firmware. While only the cramfs files are really important in our opinion. – For unpacking firmwares look for ‘aos-tools’.

Debugging Archos devices just got a lot easier.

Monday, July 12th, 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 integrates g_serial debugging. The files linked to in this guide will be no longer available.


I’ve been talking about this idea for a while now, but today I finally had the right mood to work on it and I think I’ve found a sufficiently flexible solution for now.

I’m loading the kernel modules (musb_hdrc and g_serial) in the initramfs. Fortunately there was enough space left for that.

I’ve created 3 separate serial interfaces using g_serial.

  1. /dev/ttyGS0 – unused (root shell on Archos Android firmware)
  2. /dev/ttyGS1 – unused
  3. /dev/ttyGS2 – kernel messages. this is simply ‘cat /proc/kmsg’

You can now attach terminals or logs to this in your images. Usually by editing /etc/inittab and adding a line like:

s2:235:respawn:/sbin/mingetty --autologin root ttyGS0

If you need to disable this you can just kill the ‘cat’ process and if running stop the getty’s. After doing that you can remove the g_serial and then the musb_hdrc module. You can then e.g. reload musb_hdrc to have it act as a host controller again.

The important changes are in the initramfs. The zImage is only needed if you want the root shell for Android. Get the files here.

Enjoy your easy debugging! No need for serial dongles anymore!

Cheers

Thomas, your friendly neighborhood ArchDruid
PS: As a bonus this zImage will boot Archos 2.0.x firmwares. There will be some problems with transparencies though. We’re going to fix that in the long run though.

PPS: If there is demand I can generate a set for gen6 too.

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!

Just for fun: openAOS boots Maemo/Mer oh and Meego too, ’cause we can!

Friday, May 7th, 2010

This is more of an “oh-look-shiny” thing right now.

I’d like to EMPHASIZE this: Currently we do not support Mer on Archos hardware! This is just an proof of concept!

Gaap asked me on IRC today how to try Maemo/Mer on his A5IT. – Turns out it was very easy.

  1. You take: Mer build for SmartQ5 (Touchbook might work even better I guess)
  2. Throw that into an 500M+ ext3 image.
  3. For good measure throw in some parts of the original Archos SDE images.
  4. Modify menu.lst (the image needs /sbin/init)
  5. profit!

Here are two short videos by Ian58 and spz0:

To get this far you need to go through the first boot assistant. Notice that the screen calibration will be totally off and you need to aim a bit to the side. When you manage to hit an input field the virtual keyboard will show up.

Update: If you like watching paint dry you’ll also like this one: Meego code drop 20100331 repackaged for Archos

Please note, that this is just an proof of concept and nowhere near seriously usable. It just happens to work (a bit). But if someone wants to step up and properly port that or later Meego to Archos hardware. We’re very much open to it. Just contact us for hints and some help!

Pour notre communauté d’utilisateurs français!

Saturday, April 24th, 2010

http://www.openaos.org/wp-upload/menu-beta/fr/initramfs.cpio.gz

DualBoot : La Recette  (Archoslounge)