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.
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?
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
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
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.
Hello,
THBK1-10 is a cheap dual system (Android 4.2.2 /Windows 8.1) tablet based on Bay Trail (Intel Atom Z3740D). More details http://www.thomsoncomputing.eu/dualboot.html
I'm trying to hack it, and especially get root and use non-signed zip in recovery. Basically i'm stuck at theses points, and i'm requesting directions to continue the work.
I have posted in W8 section, but obviously, this is no longer the place
General
------------
* i can use a work-around to write system (/system, /data) partitions
* i can flash signed updates via recovery
* google apps are working flawesly. Only thing is to keep original files (stock keyboard and layout)
-> i would like to flash non-signed zip via recovery, but i guess i have to build a custom recovery, or can i exploit something else ?
Root:
-------
* no auto root is working (z4root, towelRoot). Regarding towelRoot, i tryed each 8 common parameters, and i don't really know how to do others. I have also heard this is only working in 4.4.2+
* pushing su is not working. When i'm launching it, let's say from terminal, i have a code 255 return (-1). Tested with both arm and x86 version (i'm still wondering why arm su is also returning -1, i would have expect a non valid binary. Or perhaps my x86 version is bad ?
-> i'm still trying to dig this issue, and idea on how i could do ? i believe running SU was enough... but it seems not. Any idea ?
Many thanks !
Bump. the way it is booting is based on ramdisk images (one for normal android boot, one for android recovery).
I have acces to theses img, and i can, with hexedit (perhaps mounting them directly at a filesystem), view the whole init sequence.
My question is : what triggers the root invalidation ? AFAIK, everything is done as root (mounting FS, updating permissions, etc....). Basically i can't really figure how it is handled.
Thank you !
Solved !
Graveen said:
Solved !
Click to expand...
Click to collapse
Woaw ! I'm very happy to see that somebody tried and succeed to root the THBK1 ! Please can you share your method in a tutorial when you'll have time ? :laugh:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Yes ! I confirm ! Graveen has installed GAPPS on Thomoson THBK1 / Danew Dualboot tablet with sucess ! I'm not familiarised with linux environnement and realize it, but it requires some knowledges of linux command (coLinux especially)
Graveen is the only one users identified that it can put GAPPS on android environnement concerning this tablet.
Big thanks to him !
Graveen said:
Hello, yes !
I'm actually writing a GAPPS tuto, which is intensively tested by Zeksaine. Root will be added, as this is only a simple step inside the whole process.
This is a bit technical (read boring), but it worths the try. My TODO list is here: http://forum.xda-developers.com/showthread.php?t=2799404 , and while i'll take a little break, i hope soon to have custom recovery allowing you to directly flash gapps or supersu.
Click to expand...
Click to collapse
7600
I own a Cube U100GT and it's one of the many Chinese brothers of your THBK1-10. But mine came only with W 8.1.
I just start looking for a dual boot solution and I'm happy to know that it's is possible.
I don't need root for while, just play some games and apps.
So the original Android "ROM" of the tablet can do the job.
My version have 64Gb SSD and I've already resize the Win partition to make room for a new system.
Where can I look for a dual boot tuto and find this Android version?
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: http://www.danew.com/support-pilotes-manuels.php?type=218&produit=219 but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Graveen said:
Heya, can you post your partition list ?
What is the bios of your tablet ? Can you wire an USB keyboard to see this at boot ?
Basically, they effectively seems identical.
For partial update, you can find one here: but it relies on existing android partitions i still have not dumped.
Android-x86 could worth a try also, although i doubt you will have all drivers (touch, gyro, etc..)
Click to expand...
Click to collapse
The partition list is the standard for a windows installation (but no windows image on the end):
1: 300 Mb (Windows RE)
2: 100 Mb (System)
3: The rest (Windows). My SSD is 64Gb.
My tablet already comes with a dedicated keyboard cover, so I have full access to to UEFI Bios.
There's a lot of numbers:
Aptio Setup Utility Version 2.16.1242
Vendor - AMI
Core Version - 5.008
Project Version - 3BAGR 0.03
EC FW Version - 201401101A
Intel GOP driver - 7.0.1029
Sec RC Version - 00.05.00.00
TXE FW Version - 01.00.02.1060
I found the drivers pack for windows 8 and so I could install my PT-BR edition of W81. And reserve 20Gb at the end for another OS.
It's my first UEFI machine and I'm completely lost. There's a lot of options and I can't understand a quarter of that.
On the Tabletrepublic forum someone said that my bios recuse everything except a Windows pendrive. If is true, there's no way to put Android but changing/patching the UEFI.
Android x86 is for desktops right? And the Intel site, can I find Android images there?
Thank you. What i'll do is to check if my bios is identical to yours, because there are effectively numerous options. Then, i could finsh to dump my android partitions and let you play with them.
Honestly, the trick is the OS selection system, which is bring by the EFI bootloader (and certainly a dedicated partition). Once selection is done, another EFI bootloader (windows only) is called.
let's continue here: http://forum.xda-developers.com/showthread.php?t=2799404