Gen4 GPL Source code: it's there!
Gen4 GPL Source code: it's there!
check here
all software sucks equally, but some software is more equal than other software
-
- Archos User
- Posts: 79
- Joined: Tue Dec 05, 2006 1:56 am
-
- Archos Guru
- Posts: 957
- Joined: Sat Dec 16, 2006 2:28 pm
-
- Archos Novice
- Posts: 22
- Joined: Tue Jan 23, 2007 6:48 pm
- Location: Ohio
- Contact:
If it really is the whole OS source, does that necessarily mean one could add apps of their own, repackage it and run a "new" OS? I mean after all those things Archos did, is it really that simple? Maybe the Flash-chip only accepts some sort of encrypted key before it allows the installation of the firmware...Edit: Just to clarify the above statement... it seems to be a complete distribution of the Linux OS source used on the series 4 units.

you need a healthy dose of optimism.martinjay wrote:If it really is the whole OS source, does that necessarily mean one could add apps of their own, repackage it and run a "new" OS? I mean after all those things Archos did, is it really that simple? Maybe the Flash-chip only accepts some sort of encrypted key before it allows the installation of the firmware...Edit: Just to clarify the above statement... it seems to be a complete distribution of the Linux OS source used on the series 4 units.
if there's a will, there's a cow........wait a sec.
If you're a WIndows person, you can use this freeware to unpack a bz2 file the .iso file contains http://www.iceows.com/Download.htm
You can then use Windows to unzip the zip file.
I could post all 20,166 files on 604wifi.com (I think) if there is great interest....
You can then use Windows to unzip the zip file.
I could post all 20,166 files on 604wifi.com (I think) if there is great interest....
-
- Archos Expert
- Posts: 191
- Joined: Mon Oct 09, 2006 8:30 pm
Well, good news and bad news.
Good news first. This is a good release. Run "make menuconfig" to create some support stuff, then copy in the config from the cofigs directory that matches the archos x04 you want to build for (the 504 in my case) and run make. About twenty minutes (I think) or so later, on my Athlon XP running gentoo, I had two files and a bunch of directories.
The two files? rootfs.arm_nofpu.cramfs and optfs.arm_nofpu.cramfs. There are, more or less, the exact same files we had from ripping the hidden section at the end of the drive. Some things are missing (like /usr/bin/avos) but these things are not GPL; they're internally developed at Archos without relying on linking statically to GPL parts.
Bad news next. The files are signature-less. The rootfs.arm_nofpu.cramfs file doesn't have the leading 256 bytes at all, and the optfs.arm_nofpu.cramfs has them, but they're all zeros. Now, there's a addrootfs.sh script in the arch/compressed directory of the kernel, but it has a different name (root_fs_arm_nofpu.cramfs) so I'm wondering if it is an example from montavista linux or something, or a previous iteration of development, but that script isn't in the kernel distribution from my gentoo box, so I don't think it's in the normal tree. Of course, I could be totally wrong about all this.
My guess is that this development environment is run through a couple more non-GPL tools that do the signing and bundle into the .aos files we download as firmware.
So, it's useful, but unless we can figure out what those signatures are, and how they're used, I don't think this gets us on the box.
Good news first. This is a good release. Run "make menuconfig" to create some support stuff, then copy in the config from the cofigs directory that matches the archos x04 you want to build for (the 504 in my case) and run make. About twenty minutes (I think) or so later, on my Athlon XP running gentoo, I had two files and a bunch of directories.
The two files? rootfs.arm_nofpu.cramfs and optfs.arm_nofpu.cramfs. There are, more or less, the exact same files we had from ripping the hidden section at the end of the drive. Some things are missing (like /usr/bin/avos) but these things are not GPL; they're internally developed at Archos without relying on linking statically to GPL parts.
Bad news next. The files are signature-less. The rootfs.arm_nofpu.cramfs file doesn't have the leading 256 bytes at all, and the optfs.arm_nofpu.cramfs has them, but they're all zeros. Now, there's a addrootfs.sh script in the arch/compressed directory of the kernel, but it has a different name (root_fs_arm_nofpu.cramfs) so I'm wondering if it is an example from montavista linux or something, or a previous iteration of development, but that script isn't in the kernel distribution from my gentoo box, so I don't think it's in the normal tree. Of course, I could be totally wrong about all this.
My guess is that this development environment is run through a couple more non-GPL tools that do the signing and bundle into the .aos files we download as firmware.
So, it's useful, but unless we can figure out what those signatures are, and how they're used, I don't think this gets us on the box.
Damn, I was hoping the avos code would be available which would allow us to quickly exploit any bugs/weaknesses..... So basically they released what we already grabbed from the extracted directories, but in c++ form...
Ahh well... it did sound too good to be true... back to looking for an exploit...
Greg
p.s. which compiler did you use to compile it with fro the DaVinci chip?
Ahh well... it did sound too good to be true... back to looking for an exploit...
Greg
p.s. which compiler did you use to compile it with fro the DaVinci chip?
Couldn't you just use 7zip?kitty wrote:If you're a WIndows person, you can use this freeware to unpack a bz2 file the .iso file contains http://www.iceows.com/Download.htm