I've been thinking: In order to use UrukDroid or Churli's quick-root method, we have to sacrifice using the other, as well as giving up on Angstrom (not a great loss...).
Thinking of the future, is there a way we can insert a bootmenu (something Grub-like) at the beginning of the SDE boot process that could allow us to have multiple OSs on the Archos. This way, for example, we could install Uruk on the SD while still having Angstrom available. We could then potentially install Ubuntu, Honeycomb betas, etc. in additional partitions we create.
I'm hoping to inspire someone...
strongergravity said:
I've been thinking: In order to use UrukDroid or Churli's quick-root method, we have to sacrifice using the other, as well as giving up on Angstrom (not a great loss...).
Thinking of the future, is there a way we can insert a bootmenu (something Grub-like) at the beginning of the SDE boot process that could allow us to have multiple OSs on the Archos. This way, for example, we could install Uruk on the SD while still having Angstrom available. We could then potentially install Ubuntu, Honeycomb betas, etc. in additional partitions we create.
I'm hoping to inspire someone...
Click to expand...
Click to collapse
Yes and no.
The no.
The problem is that the real boot loader (equivalent to grub on a linux box) is still not accessible. That boot loader is what does the choice between the custom, init and recovery images that are place in the /mnt/rawfs.
The Yes
It would be possible to create a zImage and an initramfs.cpio.gz with a special init script that asks what root filesystem to mount and then complete the boot.
The thing is that the kernel will be shared between all the custom boot solutions.
wdl1908 said:
It would be possible to create a zImage and an initramfs.cpio.gz with a special init script that asks what root filesystem to mount and then complete the boot.
Click to expand...
Click to collapse
That is what I was thinking about. I guess it was too early in the morning when I posted...
The thing is that the kernel will be shared between all the custom boot solutions.
Click to expand...
Click to collapse
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
strongergravity said:
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
Click to expand...
Click to collapse
I don't think so. Installing the SDE gives you the possibility to install a secondary kernel and to uninstall the default Android kernel.
So I can give you a No for your first question and a 'Yes, at the current state of development ans research' for your second question.
strongergravity said:
That is what I was thinking about. I guess it was too early in the morning when I posted...
So, did the Angstrom that came in the SDE run on the same kernal as the Android on the Archos? I assume not. If not, this would mean we could only pull this stunt for different Android builds only, right?
Click to expand...
Click to collapse
There can be 3 different kernels.
custom
init
recovery
The custom is the only one that can be replaced when the SDE is flashed to the device, init is the stock android and recovery is just a kernel with some scripts that give you the ability to do stuff like reformat check disk etc.... Also the recovery is the part that is used to flash the custom kernel.
What about kexec, seems to be the perfect choice for this problem.
Unmensch said:
What about kexec, seems to be the perfect choice for this problem.
Click to expand...
Click to collapse
Sounds good to me, someone should definitly do some research and testing. Unfortunately it won't be me as I already have a bunch of project going on
Related
If I undertsand well with the root applied we are sticky on the old kernel. To solve the problem we could is the old kernel to boot a new one as here:
embeddedarm.com/software/arm-linux-bootloader.php
What do you think?
Ciao Angelo
Ok at the end I thinked how to load alternative rom without modifying the bootloader (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
ardf69 said:
Ok at the end I thinked how to load alternative rom without modifying the (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
Click to expand...
Click to collapse
This sounds good. Isn't it similar to HaRET for Windows Mobile?
Theres a ton of potential on the X10 i dont get why so many people don't like it..
anyways I'm working on trying to get apps on the SDcard with CM mod (I'm close)
xxsashixx said:
Theres a ton of potential on the X10 i dont get why so many people don't like it..
anyways I'm working on trying to get apps on the SDcard with CM mod (I'm close)
Click to expand...
Click to collapse
It's only because of the lack of multi-touch.
We'll be able to use froyo anyway, if we can get this bootloader running - whatever SE do. Then nearly all of the features of the X10 can be used.
Just a question concerning Android
If i got it right,
1. Android is running as a virtual java machine on top of the linux kernel
2. SE uses a newer kernel than other donut (1.6) androids
3. Java VM boots AFTER linux kernel and system
4. we have root, so we can modify the init.d (boot) files
5. so wo could let files be launched at boot time
Woldnt it be possible to insert a shell script that after booting linux kernel and before starting the java vm replaces the java vm files so that on top of the SE 2.6.29 kernel Froyo is running?
That way we wouldnt need to modify the bootloader. Only problem (?) ist that we are bound to the linux kernel settings made by SE (as we cannot overwrite the running system).
just an idea to discuss ....
Bax
I'm very very interested in deving for X10, I have extensive knowledge of linux and kernels
but anyways, android is running a Java VM? really?
Baxxx said:
Just a question concerning Android
If i got it right,
1. Android is running as a virtual java machine on top of the linux kernel
2. SE uses a newer kernel than other donut (1.6) androids
3. Java VM boots AFTER linux kernel and system
4. we have root, so we can modify the init.d (boot) files
5. so wo could let files be launched at boot time
Woldnt it be possible to insert a shell script that after booting linux kernel and before starting the java vm replaces the java vm files so that on top of the SE 2.6.29 kernel Froyo is running?
That way we wouldnt need to modify the bootloader. Only problem (?) ist that we are bound to the linux kernel settings made by SE (as we cannot overwrite the running system).
just an idea to discuss ....
Bax
Click to expand...
Click to collapse
Yes it can be done in /init.rc. A better solution (instead of copying files) could be to chroot the envinroment, so you teorically could have more rom (one for each directory in /system). Remain however the problem you cannot run a modified kernel (you need a boot loader like 2nboot-ng as I said before).
Ciao Angelo
xxsashixx said:
I'm very very interested in deving for X10, I have extensive knowledge of linux and kernels
but anyways, android is running a Java VM? really?
Click to expand...
Click to collapse
Hi!
Android is running in a Dalvik VM, similar to Java VM ...
http://en.wikipedia.org/wiki/Dalvik_(software)
Greetings from Vienna,
Bax
ardf69 said:
Yes it can be done in /init.rc. A better solution (instead of copying files) could be to chroot the envinroment, so you teorically could have more rom (one for each directory in /system). Remain however the problem you cannot run a modified kernel (you need a boot loader like 2nboot-ng as I said before).
Ciao Angelo
Click to expand...
Click to collapse
Hi Angelo!
chroot sounds goot, but could be a space/speed problem. On SD there is enough space, but it is slower - so that could be testing ground. Internal Rom is faster, but if original is not overwritten space could be limited.
Concerning modified kernel: Is that modification really necessary for running Android 2.1? If i remember it right N1 uses a similar Kernel for 2.1 as SE for 1.6?
Greetings,
Bax
Lets keep this going and hopefully get a working 2.1 system
Baxxx said:
Hi Angelo!
chroot sounds goot, but could be a space/speed problem. On SD there is enough space, but it is slower - so that could be testing ground. Internal Rom is faster, but if original is not overwritten space could be limited.
Concerning modified kernel: Is that modification really necessary for running Android 2.1? If i remember it right N1 uses a similar Kernel for 2.1 as SE for 1.6?
Greetings,
Bax
Click to expand...
Click to collapse
There are interesting patches to the kernel as overclock for example. I think we can use the original kernel at the start and then we can create a new one kernel from the sources.
Ciao Angelo
That sounds great!
Another limitation i remember is the limited RAM use in 1.6 which is probably also a kernel/driver problem ...
(i think starting from 2.0 or 2.1 the full RAM area is usable)
Bax
We might be able to use the information already tried on the motorola milestone which also has a locked down bootloader.
http://and-developers.com/motorola_milestone
this has information on the kexec option
Also the mot_boot_mode hack looks promising. I don't have any idea of the boot up process of the X10 but hopefully this would work.
"mot_boot_mode hack
A.k.a. the Newton hack. The init.rc script resides in the signed boot CG, so we cannot alter it. But it happens to exec /system/bin/mot_boot_mode, which we CAN change once we run as root, since it's located inside the system CG. By moving mot_boot_mode to mot_boot_mode.bin and creating a shell script as our new mot_boot_mode, we can get the system to run commands of our choice such as mounting partitions, etc. This is the earliest we can tap into the boot process, and it is early enough to let us introduce hacks such as APPS2SD, making better use of /cache, and other useful stuff. We could even branch to load a new kernel using kexec like mechanism."
Yes I know it is not the X10 but hopefully we can learn from work already being done on the motorola milestone.
seems like an interesting idea, I hope some of the devs have time to work on this while dealing with the issues with root. They might be taking a well deserved break which is fine.
ardf69 said:
Ok at the end I thinked how to load alternative rom without modifying the bootloader (e.g. froyo).
1) we need to root the X10
2) we must modify init.rc to load a new kernel or enter in recovery mode
3) we install 2nboot-ng wiki.xvilka.org/index.php?title=2nboot-ng (motorola milestone has the bootloader locked as our X10)
The scripts of the recovery mode must not flash /system but they must copy the files directly onto /system.
Ciao Angelo
Click to expand...
Click to collapse
1 is done
2 working on 2
3.is for omap cpu wont work !!
4.manualy did it and device boots works
jerpelea said:
1 is done
2 working on 2
3.is for omap cpu wont work !!
4.manualy did it and device boots works
Click to expand...
Click to collapse
Great work, jerpelea!.
I'm not sure I understand this, but does this involve loading a another kernel after the flashed one, to boot into another rom?
HunteronX said:
Great work, jerpelea!.
I'm not sure I understand this, but does this involve loading a another kernel after the flashed one, to boot into another rom?
Click to expand...
Click to collapse
I'm curious about that too. Are we talking some kind of chainloading, kexec or even something UML-like?
Yes bu not using motorolas module
Motorola has different cpu
Sent from my X10i using XDA App
jerpelea said:
Yes bu not using motorolas module
Motorola has different cpu
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Ok, thanks.
Is there a module for the QSD8250 snapdragon chipset?
Hi all,
I am a bit confused about the process that i need to follow to gain root access and also convert my filesystem to ext4 and the order i need to do the two.
Could someone form a simple noob guide of how to do the above?
Or should i wait for the 1-click root and custom roms...
There isn't a simple way and I doubt if there will ever be a 1 click root.
The easiest way to learn, IMHO, is to start with SDE.
Download the AOS file from archos - http://www.archos.com/support/support_tech/updates.html?country=us&lang=en
Read the instructions - (boot into recovery, update firmware, plug archos into PC, copy AOS file, ect...)
Install SDE
Once you see the recovery, look into the menus and get comfortable with it, you should try Dogma's perm root and kernel. Then a next step would be to OC with ardat's kernel. Then you can try to learn Linux and $aur0n's method...
...all IMHO of course.
xnatex21 said:
There isn't a simple way and I doubt if there will ever be a 1 click root.
The easiest way to learn, IMHO, is to start with SDE.
Download the AOS file from archos - http://www.archos.com/support/support_tech/updates.html?country=us&lang=en
Read the instructions - (boot into recovery, update firmware, plug archos into PC, copy AOS file, ect...)
Install SDE
Once you see the recovery, look into the menus and get comfortable with it, you should try Dogma's perm root and kernel. Then a next step would be to OC with ardat's kernel. Then you can try to learn Linux and $aur0n's method...
...all IMHO of course.
Click to expand...
Click to collapse
I don't fully agree. There are several Steps in the Process which can be scripted. One would be a Script to partition and preload your sd card for being used in the Archos, including copying rootfs and some Help to move your Data Partition.
Probably SDE is a must for Permanent Root forever, so everyone intending to root his Device has to go through that Process, as well as flashing custom Kernels.
$auron is making good Progress on enhancing his Rom and making it more flexible and customizable. Probably someday there will be a Preferences App to change the Behaviour of the Rom.
Kashban said:
I don't fully agree. There are several Steps in the Process which can be scripted. One would be a Script to partition and preload your sd card for being used in the Archos, including copying rootfs and some Help to move your Data Partition.
Probably SDE is a must for Permanent Root forever, so everyone intending to root his Device has to go through that Process, as well as flashing custom Kernels.
$auron is making good Progress on enhancing his Rom and making it more flexible and customizable. Probably someday there will be a Preferences App to change the Behaviour of the Rom.
Click to expand...
Click to collapse
I am confused also. I've read through just about every post in this forum and the one thing that I can't get a clear answer on is, do I have to have an sdcard to load the UrukDroid stuff? Or can it be done on my internal storage? I've tried going through the instructions and I cannot get the sdcard partitioned and formatted correctly.
And what does "permanent root" mean? Does that just mean you've installed the SDE and a new kernel and removed the default Archos kernel so that it always boots the SDE kernel?
So I am probably asking out of ignorance, but why hasn't this been attempted. It seems like the best way to get rid of SquashFS would be to rewrite the firmware to not use it. I'm sure it would be a huge undertaking if it's even possible.
i think the biggest problem is the .aos file.
That's what I would think. These files surely aren't hack proof.
I would imagine that they used a similar system to the PS3. Signed files etc and without some master key, I think backwards engineering and creating your own aos files will be impossible. Guessing though. I haven't looked into it and wouldn't really know where to begin.
Thanks for the reply!! I suspect you are probably right here.
And you are sure you looked into http://forum.xda-developers.com/forumdisplay.php?f=877
I'm not entirely sure what you are trying to link to fzelle, but as far as I know actually creating an aos update file to flash to the devices (which is what I took this topic to mean), rather than making a custom firmware running in dev mode has not been broached over in the android dev forum.
I absolutely agree that to get full read/write and root on your device the ONLY way to go is UrukDroid. It's great.
You were only talking about reverse engeneering, and that is not needed if you have the full sourcecode and a possibility to install your own making.
This is the first time you are talking about aos.
AOS is just an automatic installation environment on the Archos,
something like MSI on windows.
Everything you get with uruk could than be done with an aos.
BUT ATM Uruk is far away from being usable by the normal "MOD User".
So ( my2cent ) we shouldn't do an AOS until uruk ( or any other rom ) is installable
by those non techies.
And you can install Uruk internaly.
Orly?? Forgive my ignorance.
Does the kernel or initramfs change on the stock OS ever? If it does, is it updated with the aos update file?
I only ask, because if that was the case and we can pack aos files to flash to the archos devices, then what is the need for the SDE at all?
What I took the OP to mean in his original post was, could we edit the aos file to get full read / write access to the stock file system. I don't think we can, but again I am not sure as I have a limited knowledge of the subject.
I probably stopped making sense a couple of posts back (if ever), but I just want to get everything correct in my head.
The Archos Kernel is flashed by the AOS and the SDE flashes another one.
But as the AOS is just an Installer without any knollage of the device, the software inside has to manage the flashing, so yes you might be able to do this but as the internal version are probably signed you would not be successfull.
Thats why the SDE allows to install an unsigned kernel.
So you then have 2 kernels on the device and they can coexist.
It is possible to update the orginal Archos Kernel when having for ex. an Uruk installed.
They can have diff kernels, so everything is possible.
But feel free to browse http://www.openaos.org/ for more infos ;-)
fzelle said:
The Archos Kernel is flashed by the AOS and the SDE flashes another one.
Click to expand...
Click to collapse
Correct the /mnt/rawfs/init is the standard kernel and the /mnt/rawfs/custom is the sde kernel and /mnt/rawfs/recovery is a third one.
fzelle said:
But as the AOS is just an Installer without any knollage of the device, the software inside has to manage the flashing, so yes you might be able to do this but as the internal version are probably signed you would not be successfull.
Click to expand...
Click to collapse
Signed yes, I doubt that it's an installer because of the things i found in the recovery. That kernel and boot filesystem contains everything to flash custom kernels and standard kernels and also can process aos files. There could be some kind of scripting included in the aos to do some specific tasks but the recovery is probably doing all the work.
fzelle said:
Thats why the SDE allows to install an unsigned kernel.
So you then have 2 kernels on the device and they can coexist.
It is possible to update the orginal Archos Kernel when having for ex. an Uruk installed.
They can have diff kernels, so everything is possible.
But feel free to browse http://www.openaos.org/ for more infos ;-)
Click to expand...
Click to collapse
I think the sde enables the flashing through some kind of flag because on the stock system the file /mnt/rawfs/custom exists but is 0 bytes long.
wdl1908 said:
Signed yes, I doubt that it's an installer because of the things i found in the recovery. That kernel and boot filesystem contains everything to flash custom kernels and standard kernels and also can process aos files. There could be some kind of scripting included in the aos to do some specific tasks but the recovery is probably doing all the work.
Click to expand...
Click to collapse
There are a bunch of binaries in initramfs of recovery and init as far as I remember called "abcbox", "cramfschecker" and "aosparser", and THESE are doing the hard work like check whether it's signature is valid or not or even sign it, update the files, etc..
AOS files
If you google around you can find some information.
Without the private key the problem is repacking the AOS file and getting the device to load it.
Some interesting details on the AOS files in this page over at OpenAOS:
http ://dev.openaos.org/wiki/SettingUpMultiRootGen7
Samsung recently announced the new F2FS file system https://lwn.net/Articles/518718/, Im going to get the ball rolling on this, i have compiled a kernel that supports the new file system based off of fauxs source. im only posting the zimage for people who know what they are doing. For this to be usable a new recovery needs to be built to support formatting to F2FS. and possible the bootloader(not currently possible). so the best approach at this point is to build a new recovery and format only system and data to f2fs leaving boot as ext4. Im looking into it but im not very famlier with recovery. modifications need to be made to the android build system but they are trivial. Im ataching a compiled zimage and the patch files to add to any kernel. patches 01 and 16 dont apply so they will need to be done by hand. everything else applies clean.
This looks very intriguing, I haven't heard of it until now and it looks like it could bring some definite speed advantages. I can't wait to give this a whirl on my Android devices and my Arch Linux install which runs off of an SSD.
its going to be a challenge to get it runnig under android, its going to take some collaboration and time
Looks interesting. I may try to help when I get time but I haven't built an n7 kernel. Shouldn't be hard. Also need to add kernel support for the filesystem and at least add the mkfs tool to recovery so it can be formatted via adb shell.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Looks interesting. I may try to help when I get time but I haven't built an n7 kernel. Shouldn't be hard. Also need to add kernel support for the filesystem and at least add the mkfs tool to recovery so it can be formatted via adb shell.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
The largest change that needs to happen right now is recovery, which I'm not very familiar with
Sent from my PG86100 using Tapatalk 2
The bootloader doesn't need to know anything about the filesystem, it loads the kernel directly a preset offset.
That's why you flash a kernel, and not mount the boot partition and unzip it.
So, all that's needed to support a new filesystem is adding the code to the kernel, and enabling it in the defconfig, and then you can use userspace utilities to format partitions to that new filesystem.
F2FS is still immature, they haven't released a fsck tool for it yet, and the mkfs binary they provided is probably x86, so there's no way you can use it on the Nexus 7 now.
Just checked out their sourceforge project, check below post, they have provided source for mkfs.
Also, the recovery needs to be modified only if the default format of the partitions is being changed, and that'll need changes in the fstab as well to mount the filesystem as something other than what it was set to by default.
Nothing will need to be changed in the Android Build System as well, unless you wan't to generate f2fs system images.
f2fs-tools-1.0.0.tar.gz includes source, not binaries.
http://lkml.indiana.edu/hypermail/linux/kernel/1210.2/00005.html 1.5 to 2 times faster, Im going to look into this again it seems very worthwhile
I don't know much about this stuff, more of a user over here, but I sure know when to get excited about something. :victory:
I've read a few things about the new file system and was particularly impressed with the benchmark performance. I really hope to see this becoming a standard feature of android. Please keep up the work. You've found yourself an early adopter.
Thanks again and kudos!
aaronpoweruser said:
http://lkml.indiana.edu/hypermail/linux/kernel/1210.2/00005.html 1.5 to 2 times faster, Im going to look into this again it seems very worthwhile
Click to expand...
Click to collapse
Hi, I also think this seems very worthwhile, maybe even porting it to maguro. This thread was a nice start, I've created a thread on my device's general section, but no replies pushing forward yet.
I looked into it the best option for now would be to format an external SDcard, but that would make it un mountable by a pc. In order to make it work with an internal storage the android build tools will need to be reverted reworked as well as recovery
Sent from my Nexus 7 using Tapatalk HD
aaronpoweruser said:
I looked into it the best option for now would be to format an external SDcard, but that would make it un mountable by a pc. In order to make it work with an internal storage the android build tools will need to be reverted reworked as well as recovery
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks, that's what i thought too, build tools/recovery, a few touches here and there xD
f2fs would be unreadable by a pc... by a Windows pc.
Hello guys,
Is there a possibility to update the "archos 10.1 (gen8)"
from android froyo 2.2 to android 4.4??
And if it is possible would it be worth it to do that ?
Will speed and so increase the tablet?
Greetings Avanox
Absolutely not.
Mavasilisk said:
Absolutely not.
Click to expand...
Click to collapse
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Avanox said:
Hello again, thank you for your reply.
And not possible to install another version that's higher than 2.2 on that tablet?
Greetings Avanox
Click to expand...
Click to collapse
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Ranomez said:
2.3 or 4.0 but that's the highest u can go, did u even have a look in the gen8 android development section?
Click to expand...
Click to collapse
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Avanox said:
Waw great. Thanks for the information.
Yes I did check this section but probably not good enough.
Click to expand...
Click to collapse
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Ranomez said:
Here is the link to ICS (4.0.x): http://forum.xda-developers.com/showthread.php?t=1941377
And here is the link to GB (2.3.x): http://dev.openaos.org/wiki/AndroidInstall_CM7_Gingerbread (there is also a thread on this forum)
Unfortunately the openaos site seems to be down right now (was up in the morning and last night when I answered you) but anyway I did find cm9 (ics) to be more stable and "usable" (less bugs than actually affect usability) than cm7 (gb) although no doubt quite a bit slower than cm7, but again that's me that has at least 300 apps installed on each android device and that goes back to since I had a HTC Touch Pro 2 and turned it from an windows mobile device to an android one and the specs on that were way lower than the ones on the gen8.
Also feel free to ask any questions you may have related to our gen8 tablets, I am one of the "lost souls" still using this tablet and I can say that judging by the fact that I bought this quite soon after it was released (at least in my country) I can say it has served me well since then and I still think it is a decent device (although I do now have a much better and much more powerful tablet device too, my 101it is still a fun thing to play around with).
Click to expand...
Click to collapse
Avanox said:
Hello again I will give it a try now.
Any idea where I can download the kernel ?
Because the download link doesn't work on the link you gave me for android 4.
I just posted for it.
Would you still have it or could you reupload this for me?
Would be awesome.
Greetings Avanox
Click to expand...
Click to collapse
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Ranomez said:
The link that you are talking about that isn't working is the kernel source link (which is actually very unfortunate) and not the kernel itself, the kernel can be downloaded from the attachments of the first post in the thread (a zimage and the initramfs.cpio.gs files)
Click to expand...
Click to collapse
Avanox said:
Hello again ,
I will set it on a row:
1. Cm9 image download (ok)
2. Initramfs.cpio.gz download (ok)
3. Kernel download
(which files are the kernel to download zimage and the initramfs.cpio.gs??)
I can't see a link to the zimage ?? Can you give me the correct link?
4. Data.img.tar.gz download (ok)
Install kernel by SDE menu
(ok I know how to get in the SDE menu but what steps I have to do there?)
Where to configure menu.Ist (is that the one I downloaded in the attachements downstairs?
What about the terminal ? How to enter the terminal to activate Bluetooth?
What is the swap configuration??
Ok and one last question, at the moment my Archos 10.1 gen8 is running on Urukdroid must I remove the sd card for this procedure and reinstall the SDE firmware or not?
Or is this method for cm9 (android4) not like urukdroid method??
Sorry for all my questions but I don’t want to make mistakes.
Greetings Avanox
Click to expand...
Click to collapse
There are a few files starting with zImage, chose one of the 3 of them and rename it to just zImage (no extension and don't extract it although when youu will download it it is an archive, just rename it to zImage and I can't really tell you which one to choose cause I do not know which of the 3 will work best for you, I personally use the 35% one.
To flash it you will use the same procedure as for urukdorid but you will loose access to urukdroid, though you don't need to remove your card and also AFAIR the OpenAOS multi-boot menu does not have the ability to boot at tablet boot (or I am wrong, not sure) so you might have to reboot in recovery and run developer version each time you want to boot it.
You could also use kboot for even more multi-boot and being able to still use urukdroid, I think I posted a mirror for the files on it's thread, or at least I wanted to, if I didn't I will. BUT if you do want this first backup the urukdroid kenrel and initramfs, I can tell you how to do it if you intend to do this, if loosing access to urukdroid is ok for you then I'd say don't bother, uruk isn't that great, you can get the same things on stock after getting root on it, though I could still recommend using it as that's the only way to have rooted stock using the kernels here on the forums or being able to boot also GB and/or debian/bodhi/whatever other linux distro you fancy.
For the OpenAOS boot menu you indeed need to download that menu.lst and put it on the storage, it is already setup for booting CM9 so you don't really need to do much more here.
Swap is already configured so you don't really need to do anything about that or worry about it, it's just info and for the bluetooth I think terminal emulator comes preinstalled so you do the commands in there but I would recommend creating a bash script and downloading SManager from play store and using that to create a homescreen shortcut to your script (I could also share you my script if you would like later after I charge my archos.
Also there is no initramfs.cpio.gs that was a typo, it's actually .gz so you have the right file and the kernel is the zImage.
In the SDE menu just do the steps you did when you flashed urukdroid but only place the initramfs.cpio.gz and zImage without a 3rd file (if I remember correctly the steps for flashing urukdroid), I can't really tell you what steps to do in there as I don't really remember, it's something like go in the repair menu and click flash developer firmware or something along those lines I think.
EDIT: Also if you intend to edit the menu.lst file for whatever reason (if you want to use kboot to add the CM7 kernel and use that to boot CM7 and/or debian for example) don't use windows notepad, instead install notepad++.
Ok this makes some things clear to me
Yeah is also a long time ago urukdroid installing.
I found the guide from it but it seems idd similar to your explanation.
https://code.google.com/archive/p/urukdroid/wikis/Installation.wiki
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Avanox said:
ok I Installed Kernel and initramfs.cpio.gz
But what about installing cm9 image?
1. I did extract "CYANOBIZ_BETA2.6_A101.img" and copyd it to the root.
2. I did uncompressed data.img.tar.gz, I choosed one of the 3 images and renamed it to data_ICS.img
3. I did copy the 2 files to the root.
But what now how to install it? That's not specificly said how you must do it.
Can you help me ?
Greetings
Click to expand...
Click to collapse
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Ranomez said:
You need to also drop the menu.lst file on the internal memory and have the cm9 image named as CYANOBIZ_BETA2.6.img then just got to recovery and boot the developer edition firmware and you will be greeted by a boot menu with just one item, click power and it will boot and that's it.
You don't really install anything, the tablet will boot from the img file and use the data.img file as the data partition, that's all (and if you decide to move any apps to the sd card aka internal memory don't boot in an other android os like stock because the android_secure folder will be wiped, though I am not sure CM9 allows you to, I know CM7 does).
Also I have uploaded kboot and it is on the thread in the development section if you want to use that for more flexible multi-boot (or at least to have the multi-boot menu loaded at every normal boot without needing to enter recovery to boot ics), although now it will be a bit hard to obtain the uruk kernel in case you still want to boot that, it is possible, you just need a linux computer or the ext2fsd driver in windows, I can't really give you the kernel from my installation of it since I understood yours is on the sd card and mine is on the internal memory.
And if you would like I can give you kboot already set up with the stock root kernel and all the 3 ics kernels to make it easier for you.
Click to expand...
Click to collapse
Avanox said:
Ow ok will try tomorrow.
Euhm yeah urukdroid is no more on tablet I think I installed last sde firmware.
The kboot is that for switching between then Linux similar system and android 2.2 and android 4 and maybe urukdroid if I reinstall it (not necessary for the Moment?)
Yeah I will try out that kboot you may send it to me if you want. Maybe it's cool feature
Thanks in advance
Greetings
Click to expand...
Click to collapse
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Hello first of all I wanted to say I just got into android 4.4.
But when I start it up I get a lot of messages that are saying.
This application doesn't work anymore.
Any idea what this could be?
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
R
anomez;65030979 said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Avanox said:
Hmm after looking I restarted it and now it works better the android 4.4
But how do you put something on the internal memory if I connect them with usb to laptop I can't acces the root with all my files.
Greetings
Click to expand...
Click to collapse
It is clearly stated that you can't access the internal memory via msc on the ics thread, only the sd card, and that is also true for any firmware that boots from an img file since the img is on the internal memory and that would mean cutting the system's access to itself=crash.
Ranomez said:
If urukdroid was on the internal memory and you just installed the sde firmware it was not removed and I can send you my uruk kernel, if you first went to recovery and did a full format and then installed the full firmware and then the sde then it is no more on the tablet.
If it was on the sd card then nothing affected it unless you put the card in the pc and used something like minitool partition wizard to delete all partitions and I can not give you the kernel.
Yes, kboot is a chroot based multi-boot menu (think GRUB but unable to boot non-linux kernels, I think) and it allows booting android 2.2, 2.3, 4.0 and linux distributions as ubuntu (although the ubuntu for archos files are gone but you can still use it to boot the kernel from OpenAOS and boot debian from that bootmenu, which will be the same boot menu you will get from android 4.0 though you can not boot stock or debian from that as the kernel is different, well you might be able to boot it but most things won't work, like wi-fi and the likes).
Ok, I will send you my already set up kboot but first tell me if your urukdroid instalation was on the sd card or internal memory and what you exactly did to the tablet cause then I might be able to throw in my uruk krenel and thus you will also once again have access to that as well.
Click to expand...
Click to collapse
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Avanox said:
Hello again,
Owkey now if I start up my tablet android 2.2.1 startsup
(firmware version: 2.4.83)
I did set the iso file from cyanobiz_BETA2.6.img on my internal memory.
So cm9 boots nice on the tablet but I must go first to the SDE (by pushing volume + ) then a see a white menu -> developer edition -> and chose cyonade and it start good
Urukdroid was installed on my sdcard but that doesn't start anymore as standard at moment. don't know why?
Before I started with cm9 I installed the latest SDE firmware for archos 10.1 gen8. (and the procedure to runb cm9)
Would it work with your kboot file so I can choose between:
android 2.2 (Archos),
Android 4 (CYANOBIZ)
Angstrom (openAOS)
urukdroid 1.6 (not in the menu)
Greeetings Avanox
Click to expand...
Click to collapse
Kboot will make it load at boot so it will go to the boot menu instead of stock 2.2 from where u can choose what to boot or (after a period of time) it will just boot your last selection.
Yes from Kboot you can choose to boot any of those though I really wouldn't recommend Angstrom (I don't even think you can still find a rootfs.img for it, if you still have it on your internal memory please upload) cause it is really limited and also I don't think OpenAOS made a kernel for Angstrom and it'll be quite hard to get the kernel from the SDL aos package (though I do have a kernel that can boot it directly, compiled from the stock 2.2 sources, NOT by me). In theory you can edit the menu.lst to launch Angstrom for it but remember you must edit it with Notepad++ and not any other windows text editor (notepad, word, etc) and you will need to know the format for booting a linux image file (I can tell you what that is) and just add the OpenAOS CM7 (gingerbread) kernel also and use that to boot Angstrom, never boot ANYTHING ELSE when loading the boot menu with the ICS kernel, you will have the same options but you must always remember you CAN'T launch anything else than ICS when launching the OpenAOS boot menu with the ICS kernel. But if you are actually interested in running linux I'd say just go the debianlxde way (download from OpenAOS site) as it is so way much better than Angstrom.
To boot UrukDroid you will need to either have linux installed on your PC/laptop or boot a live cd, put the MicroSD Card in a card reader and connect it and then search the uruk partitions to find the zImage and initramfs.cpio.gz (they might have some slightly different names) and put those in a new folder in the kboot os folder, of if you want I could probably unpack the UrukDroid install and update packages to find the right kernel for you but as I can't really remember what tools I need for doing that you will have to wait about 2-3 weeks (I have exams and also bought myself a Nintendo New 3DS XL that I plan to hard mod after I finish with the exams and do a nand dump and try to edit the firmware and flash it back to see what I can obtain so that's gonna take me about 1-5 days as I am not the best with soldering things on motherboards). You will also have to wait that exact same amount of time if you want me to tell you from where on the UD partitions to find the kernel files as I do not know myself and will have to search for them.