Related
This is not a thread to say ‘thanks’ to developers. Only post here if you have some input in this development progress, by either fixing bugs, or coming up with ideas (and ideally, try your idea and report what happens).
Having that said, let’s move on to where we are at the moment. Currently, we have a build which is based upon Ice Cold Sandwich 6.2 Test Edition for the HTC Desire HD. This build boots up by flashing my custom kernel on it, based on Flyer HC Original Kernel Source, with some patches:
-Quota2 Support
-Genlock Support
-Updated KGSL driver by applying Lord Clockans patches from his kernel
The ZIP we are working on now, can be downloaded here:http://w728685.open.ge.tt/1/files/9iI3CbF/0/blob?download
This ZIP contains a build which is mainly Lord Clockans ICS, with essential changes in the ROM to get it booting (we used LeeDroid’s Flyer HC as the donor ROM). This ROM is made for a HoneyComb HBOOT!
After you have flashed that ZIP, this is the kernel you need: http://ge.tt/9iI3CbF/v/1
You MUST flash this kernel to get it up and running, or it’ll just loop in the logcat complaining about unsupported stuff.
This set should do the following:
-Boot up (bootanimation resets after some time, it’s ok, it will boot within 5 minutes).
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!) Also, the ntrig.c file in /drivers/input/touchscreen/ is modified in the kernel, don’t know if it helped though.
-Full Hardware Accceleration
-Screen is bugged at certain moments (seems to happen especially during things concering wallpapers. Rendering a wallpaper, showing a heavy LWP, etc.). The build.prop file contains some lines such as:
ro.fb.mode=1
debug.composition.type=gpu/mdp
debug.fb.rgb565=0
Perhaps we have to change these lines to get it running without issues (strange thing is, logcat doesn’t seem to make an issue about this). We can also try a recompile of the kernel using the entire driver folder from Lord Clockans kernel (it’s in /drivers/gpu/msm/ in his kernel, and /drivers/video/msm/gpu/kgsl_adreno205_hc in ours, moving the folder to where it should be causes issues, so we keep it like this for the time being).
-Sound is working
-Backcamera seems to be working fine, haven’t tested frontcamera.
-Hardware buttons under the screen aren’t working, and this should be a low
priority for now. It isn’t ideal to use them in ICS anyway (different button functions in comparison with the softbuttons), and I think we shouldn’t focus on this for now.
-GPS switch can be enabled, haven’t tested whether it works.
-Bluetooth switch can be enabled, but turns off automatically after about ten seconds.
-WiFi switch can’t be changed, logcat tells us that it can’t connect with /dev/rfkill, applying this patch in the ramdisk could fix it:
https://github.com/OpenSensation/an...mmit/da09360d70888a7e126871ab2ae5b218514cad18
-Power button and Volume buttons work fine.
-Pen works after we send the event_google command mentioned before.
If the ROM immediately reboots within 10 seconds and it seems like it’s looping, and you can’t even logcat, hold down Power and Volume Down until you get to HBOOT, select FASTBOOT, and enter ‘fastboot erase cache’ in the CMD/Terminal, and reboot, and it should work.
And that’s about it for the current things we know I think. If you manage to fix something, please write down and report what you did to fix it, so we can keep a list. I will work on a vendor folder using the known information, so we can compile a ROM from source, made for our device.
And last, but not least: don’t post here asking for release dates. We will do our utmost best to bring ICS experience to the Flyer, but do not bug us. Thanks.
Now let’s get this up and running guys! I will keep a log of what is fixed and what is not, so we can keep the thread organized. Else we’ll have 50 ZIPs around, not knowing which one is the right one et cetera.
Source code of kernel: http://github.com/Chaosz-X
Ramdisk will be uploaded tomorrow.
Donations are much appreciated, as I'm developing and building atm on a 1.67GHz Dual core...
Donations can me made to [email protected] using Paypal.
i suggest creating two repos... one for ROM and one for kernel... that way single file changes can be tracked even on ROM front, not just kernel...
willing devs can fork those repo and send pull requests to main repo when they get stuff working
I'm not a developer, and I have nothing but love for all the great devs that worked so hard to bring ICS to the Flyer.
Might I suggest, however, that instead of pursuing CM9 builds, the next effort be centered around porting the Android Open Kang Project (AOKP) ROM? In terms of features and customizations, it's considerably ahead of CM9, with numerous supported devices to boot.
I think this ROM, versus CM9, would give users the most flexible and dynamic ICS experience for their Flyer.
Chaosz-X said:
-Touchscreen works after you did this: open ADB Shell (by entering ‘adb shell’ on your pc,), and send the command “echo ‘1’> /sys/android_touch/event_google”. Now touchscreen should be working. (For some reason the file 90flyerhacks in /system/etc/init.d doesn’t do its job. If anyone has a clue > say so!)
Click to expand...
Click to collapse
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
nickiberli said:
Does it work if you add
write /sys/android_touch/event_google 1
to the init.rc file?
Could you post the init.rc file where you trigger the init.d scripts?
Click to expand...
Click to collapse
yes that should work correctly
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Chaosz-X said:
No, I didn't add that. I'll try it tomorrow (or one of you, if you have a Linux machine ready. Laptop with Ubuntu is having some issues atm, can fix it tomorrow).
So, assuming that's working, let's get to the display. We know that it causes issues, but how?
-Logcat doesn't error (except for HtcEbdLog, saying something about rotation, which seems to happen when glitches occur. Perhaps we need to swap the files?)
-At the very beginning, it does tell that initOverlay failed. This overlay-thing is baked in the ROM, and can be disabled in the ROM itself by setting an option to 'false' in the vendor setup. We don't know if it fixes the issue, but since the attempts to add this functionality to the kernel failed, it could be a better idea to fix it in the ROM to get rid of the error.
Any other suggestions?
Edit: and before I forget, tomorrow I'll check the ZIP for what is changed in comparison with the ROM it is based upon, so we know what we have to add in to a new build too.
Click to expand...
Click to collapse
u want me to add stuff to that ramdisk?
start a github repo for the ramdisk and ROM too... trust me... its VERY helpful...
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Chaosz-X said:
I'll start installing Ubuntu within 30 minutes, and will add everything to a GitHub by tonight within about 3 hours I think.
Click to expand...
Click to collapse
thats great... it should make keeping track of changes much easier and other interested devs can contribute if they want...
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Thracks said:
Hello, all.
Attempting to help by working on the build.prop settings. I'm S-OFF with revolutionary and have my device fully configured with the Honeycomb HBOOT/radio/bootloader/etc.
After flashing the ROM and the kernel, the device would immediately reboot upon attempting to return to the main recovery menu. I had to fastboot oem rebootRUU and reflash Globatron's PG41IMG-WIFI-light-B10 zip to get recovery back.
The device never proceeded to the boot animation.
Click to expand...
Click to collapse
I can confirm this happened to me also. The only difference is that I was using the kernel for a port of mine, and it did the same thing.
Yes, it is known that for some reason, Go Back already reboots the device. It's no problem though, it works fine anyway. If it is really looping the bootanimation every ten seconds, keep Vol Down and Power pressed, until you get to HBOOT. Select FASTBOOT, and enter 'fastboot erase cache' in the terminal. Then reboot on the device, and it should boot up fine.
Also, kernel won't work on Honeycomb, haven't checked why it doesn't though (and I won't btw, our goal is not to make a new kernel for Honeycomb, but for ICS, where it does its job fine).
Kernel source is uploaded to my Github: http://github.com/Chaosz-X
Edit the CROSS_COMPILE for your toolchain, and it should compile fine (it does here).
Will add the link to the OP within 5 minutes, ramdisk will be uploaded tomorrow.
If chaos has a device tree set up for the Flyer/View, no build prop editing should be necessary, can just submit requests - but I don't notice it on the git.
Thanks for uploading, I'll have a look and see what has changed so far. It's a little difficult to keep track of the changes since there are no commits that document the patches applied over time, but I'll try to make do with what you've got.
Is this straight from flyer HC kernel source?
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Cimer said:
I may be doing this wrong, but the touch screen commands do not seem to be working for me
Click to expand...
Click to collapse
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
lawguy said:
You have to type it in manually. Copying and pasting does not work, at least it did not for me. I think the issue is with the '
Click to expand...
Click to collapse
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Cimer said:
It may just be me, I tried manual too. I had to use http://forum.xda-developers.com/showthread.php?t=1379875 since I'm stuck on Windows 8..maybe something is up with that. I guess I will just need to sit and wait =/
Click to expand...
Click to collapse
Hang tight for now. Wifi Does not work and the screen freaks out. I'm sure that these things will be fixed soon.
Going to upload ramdisk source within an hour, and try to apply a fix for WiFi, and try to fix the touchscreen by using the command in init.rc mentioned here earlier.
The new modem arrived, I have Internet again, so we have remote access to our Linux machine and can start compiling etc again
Indeed, we're grabbing AOKP source code now. Within about 2 hours we think, we'll start compiling the ROM for the HTC Flyer. Don't know if it will work out, but we have to start somewhere
I'm building CM10 from sources for encore. The build completes ok, and I can flash the image to sd card. After flashing, I get the boot loader working correctly, but the OS does not boot - black screen with screen backlight turned on. From the original fat-tire manifest.
The only suspicions thing during the build are the packaging scripts warnings about /sbin/modprobe not being found. This is normal since I'm on OS X and there is no modprobe, and even if it was it would be useless to try inserting arm modules on x64 kernel. On the other hand, if during the build process there is some chrooting going on, this might mean that a modprobe for the android did not get build/saved properly and it could easily explain why the device does not load the OS. I tried looking trough the make files, but cant find which one produces these. (I've already fixed some unportable use of sed in these files)
Any suggestions will be appreciated. Thanks.
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.
ive been trying to find tutorials and tools needed to squashfs and mksquashfs the system the right way without breaking it.
any ideas?
ive made a bootanimation.zip and unsquashed the system. then replaced the boot animation and mksquashed the img again. but for some reason it locks up right after the animation i added plays. i think it might be because of some permissions got changed.
ill repack a usb debugging and rooted version and try it again so i might have a lil logcat to help.
but i stillhave a feeling about the issue.
im attempting this with a wear 2.0 with a custom kernel and stock recovery
by the way im using both a windows 10 64bit rig and a ubuntu 16 64bit rig
thanx and cheers!
Hello XDA developers,
First of all my motivation to write here is to create a commandline GNU/Linux-like UI (and maybe add desktop GUI later) on the Asus Zenwatch 2, so I could see the kernel messages at bootup and use Midnight Commander without starting the entire main system (for example, get a text-mode shell and stop after every devices got initialized, firmwares got loaded, but before loading any Surfaceflinger and Dalvik stuff). I did similar thing on an Android tablet before by writing my own keyboard and touchscreen handlers based on Yaft. But that didn't help with boot-time kernel messages and the built-in framebuffer console in the kernel is probably much better. It's not enabled in the stock kernel, so I tried to recompile the Sparrow kernel from source (I didn't modify the default configs yet). After some tweaks to the kernel-source (which doesn't compile without them) I could build the Momentum-kernel and the stock Sparrow-kernel too using the provided .config files (e.g: make sparrow_defconfig). I used Android NDK's r13b gcc on Lubuntu 18.04, because an earlier attempt with NDK r18b wanted to use clang and compilation stopped early with errors.
My problem is that despite the kernel finally got compiled it doesn't seem to start at all. (I had similar experience with the Android-kernel in the past, but more success with Raspberry PI)...
I used mkbootimg to repack the generated zImage-dtb and the previously decompressed initrd into a boot.img, and ran fastboot boot on it, but booting simply stucked at fastboot screen, the animated ASUS logo never came in.
Can anyone point me into the right direction how I could troubleshoot further why the kernel doesn't work?
(I assume the 4.9 gcc isn't the issue here, though I got a zImage with slightly different filesize. I've read somewhere the earlier 14.04 Ubuntu and 4.8 gcc is advised for Sparrow kernel compilation but do these versions matter here? Should I replace the modules too on the system partition with their newly built versions, as the zImage changed?)
I know others managed to build a working kernel, for example TWRP has its own custom kernel and it works fine on the Sparrow watch... Is there any step I might have missed? Is there a debug-tool or logging which helps me to find out why the kernel doesn't boot? Something to troubleshoot the kernel-loading and booting? (A simulator for example? Or how do the experts do it in practice?)
I hope I declared every aspects to get some help. If for some reason I don't succeed I might try to make more linux-like AsteroidOS or PostmarketOS to get my complete Linux console on the smartwatch. The thing is that these don't support all hardware on the watch, that's why I'm trying with Android in the first place.
I guess if I'll be able to compile and then run the stock original kernel somehow the rest will be easy. (To enable framebuffer-console, set governors, remove unnecessary drivers, etc.)
Thanks in advance for the help, XDA gurus...