Codename: Cletus YAR!
Some bug fixes for 0.27.
- Market works as intended from 0.27
- Fixed init.sh again.. left off a let statement.
- Fixed format.sh script in boot.img and recovery.img, new busybox doesn't have mkfs.vfat, using mkdosfs instead.
- Includes mount.apk in system folder.
Codename: SamJr YAR!
- Made /system/fonts read write
- Fixed init.sh in boot.img, should help with flashing from one firmware to another.
- Minimalist Market.apk, just market this time.
- 0.27 fixed bug in init.sh, replaced if with case, make fonts read write, added /.android/lib to the lib path, /.android/sbin is already there, you can override a binary or library by putting one with the same name in the path in front of it.
Codename: SamIam YAR!
- Ported YAR to new Archos base.
- Includes system modules for extra functionality. cifs, yaffs, lowmemorykiller, and aufs, thanks to X.
- Partition offsets and sizes are the same as stock, except for another partition for system2 taken from the user partition. I believe there are bad blocks in the A7HT or at least my tablet set from the factory, so when you move partitions around these badblocks are no longer accounted for by the system, leading to instability. Keeping things as similar as possible should help with this.
- System is still read write, but only partially writeable, bin and some system folders are left as read only, both for extra security and because I could only fit some much in the system2 partition. I am reusing the old userdata partition for system2, and moving userdata after system2 as a new partition. I considered adding more partitions but there would be disadvantages for 2M tablets and I had to hack vold as it is to get it off of mtdblock8, which is hard coded into it.
- Simpler implementation, just one boot partition.
- 0.16 First run with just Archos and root, updated with new logos, included X's kernel modules
- 0.17 Put insmod aufs bits in init.rk28board.rc and set up /data/sysaufs for an overlay means of having system read write. Same partition setup as stock.
- 0.18 Fixed Market.apk code, removed pagecache out to /pagecache instead of /data/data, updated recovery scripts.
- 0.19 Used an initboot.img to format everything then boot into recovery to flash another boot partition. Userdata set to larger size than usual. Seemed stable.
- 0.20 Set partition offsets to KD0.21 offsets. Problems occured. Aufs was not working well. Tried to make system a regular ext3 partition again. Make the system partition overlap the backup partition to get more space and updated package-file to have backup contain nothing. Problems occurred, all partitions before cache are behind a wall, as you can see in dmesg output when you boot, you can't format them. Tried dd and flash_image to get around it, realised problem with factory set bad blocks or even new bad blocks can't be accounted for by flashing an ext3 image.
- 0.21 Tried to keep cramfs for system and tried splitting up system into the original offsets and sizes, using the backup partition for half of system. Idea was to have one referenced as cramfs to start and then mounted over with a ext3 partition. Didn't work.
- 0.22 Tried using [email protected] in init.rk28board.rc for lib, bin, app, etc, a bunch of img files to be mounted onto system points. You can create a bunch of loop devices but busybox seems to have a bug with releasing them, not a stable solution.
- 0.23 Thought I had something working with part of system being read write, and the rest cramfs, left half of system be rw and mounted the rest as ext3 within it using internal symbolic links, android decided to make system read only on it's own, with seemingly rw mounted bits underneath. Kinda useless.
- 0.24 Pointed the links outside of the cramfs partition to another mount point instead of trying to mount everything under /system. Working finally but with partition instabilities because I had the original userdata resized and it wasn't mapping correctly onto it's bad block list.
- 0.25 Moved system2 down the list one to replace userdata, moved userdata up one and made it's size such that the user partition would match what folks are using with KD0.21. Partition issues went away.
- 0.26 Experimented with various busybox implementations, decided to keep the Archos one they compiled for the firmware, cleaned up some duplication in sbin vs /system/bin, tested against Archos firmware for installation. Eliminated initboot.img since it was giving me grief with the cache partition due to recovery's size, and all it was doing for some formatting. Decided to release what I have.
* contains the Archos System folder with their pack in applications, a version of Market.apk for this release and update.img
Codename: Skeeter YAR!
- Added an extra partition for a read/write /system folder.
- Increased /data to 180MB.
- Separated Archos Apps out to the internal memory in folder Apps.
- wifi config file now referenced in /flash/wifi.
- Recovery image is more developed.
- Clock widget moved to initial screen.
- Wallpaper moves now.
This firmware takes longer to flash, it formats all the partitions including /flash if it's needed, copies all the system files over to a new system2 partition.
You will first see Archos's logo then a red smoking gears logo, repeated again, just faster, followed by a grey smoking gears logo with system2 in the corner, then the normal smoking gears logo. This can take several minutes.
ADB logcat can be run at any time to see the progress being made as it boots. Since I am using a script instead of a binary I don't have a screen full of text to show on the tablet itself.
If you want to switch between the regular cramfs system and the ext3 system use setrecovery --system --reboot or --system2.
To remount /system read write just use mount -t ext3 -r -w -o remount /dev/block/mtdblock8.
test.sh in recovery is a front end for badblocks, just use test.sh cache to clear the partition to zero and check for bad blocks.
Similarly, mount.sh cache /cache, format.sh userdata, e2ck.sh userdata -y all look up the correct mtdblock partition.
Download it here.
- 0.05 Moved clock and made wallpaper move, changed recovery logo to be shades of red
- 0.06 Added extra partition, tried various tricks with mount -o move to select new system partition.
- 0.07 Fixed issue with sdcard not being properly remounted after connecting with computer.
- 0.08 if /flash can't be mounted then format it and mount it, saves reflashing after formatting step.
- 0.09 Added --system2 and --system options to setrecovery functionality
- 0.10 updated recovery with device look up scripts for various functions.
- 0.11 updated init.sh to use new scripts to avoid hard coded refs to /dev/block/mtdblockX
- 0.12 Tested new offsets to match up with SirDom's 0.21.
- 0.13 Mkdir /flash/wifi /flash/wifi/sockets, edited server config path option, creates init config file if it doesn't exist.
- 0.14 Set up /flash/Apps and moved apk files. Created WakeLog.apk.
- 0.15 fixed issue with flashing from other roms due to recovery.img not being flashed immediately.
I just did up a firmware update for myself, that I thought I'd pass along, it's still a work in progress, but I like it. Basically, I had a look at Sir Dom's firmware and tried to figure out what it was doing, and did my own from scratch as far as I could follow along, with a minimalist approach to getting something functioning. The whole point for me was to have something done up that I understood the workings of so if something goes wrong when I am playing around, I have an idea of what it could be. :)
Codename: Fred YAR!
- Superuser mode enabled in boot.img and recovery.img, su binaries included. (aka MountNFS works so I can watch video's via NFS, I can enter recovery mode and do things like format a newly added partition, etc.)
- New boot images, all except the very first one, don't know if that can be changed.
- Latest versions of Appslib and Aldiko already included.
- Deezer, daily paper, global time and ebuddy removed.
- Location in browser now works for me, it didn't before.
- Recovery mode works. boot.img now goes into recovery mode on errors and stops instead of formatting and rebooting in a loop.
- File ownership sanity checks done for superuser/root.
Download it here.
- 0.01 boot images in boot.img and system.img working and made pretty.
- 0.02 adb su working but not in android apps. All ownership set to root.root, lots of chown and chmod testing.
- 0.03 adb su working, su working in apps, permissions for sh set the same as su, but settings not being saved properly for wifi or calibration. All ownership set to user.user instead of root.root. browser location feature working suddenly.
- 0.04 only bin folders and make directories set to root.root, rc scripts as well. the rest set to user.user. su working. stable.
Titanium, andexplorer and shootme are not preinstalled.
If you wish to donate a few bucks , click here.