Talking on those lines, i was wondering if anyone has used the latest kernel available from here?<div><a href="http://developer.mips.com/linux/">http://developer.mips.com/linux/</a><div>I was wondering if that can be used :)</div>
<div>This is my output in the tablet i have</div><div><div>$ cat /proc/version </div><div>Linux version 3.0.8+ (shen@compiler) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #1 PREEMPT Sat Mar 3 10:02:16 CST 2012</div>
</div><div><div><br><div class="gmail_quote">2012/4/10 Akash <span dir="ltr"><<a href="mailto:akash87@gmail.com">akash87@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yep i figured it was for GB. <div><br></div><div>I'm guessing you are waiting for a stable kernel to come out and then update your post.</div><div><br></div><div>Nevertheless, for someone like me, who is noob, i did not even know that it was more like the standard build until you just mentioned.</div>
<div><br></div><div>My main aim is to just replace the system.img that i've built from the aosp code. </div><div><br></div><div>Btw, can you tell me if this <a href="http://forum.xda-developers.com/showthread.php?t=1490886&page=9#edit24523131" target="_blank">post</a> will actually work?<div>
<div class="h5"><br>
<br><div class="gmail_quote">On Tue, Apr 10, 2012 at 12:20 PM, Sztupák Sz. Zsolt <span dir="ltr"><<a href="mailto:mail@sztupy.hu" target="_blank">mail@sztupy.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi!<br>
<br>
The tutorial you see is for Gingerbread builds as they are quite proprietary. I haven't updated them yet for ICS, mainly because an ICS build is more like the standard on these devices (kernel+initramfs in one file + system.img is a sparse ext4 in a separate one).<br>
<br>
SztupY<br>
<br>
Akash <<a href="mailto:akash87@gmail.com" target="_blank">akash87@gmail.com</a>> a következőt írta:<br>
<div><div><br>
>On Tue, Apr 10, 2012 at 10:27 AM, Tom Cubie <<a href="mailto:mr.hipboi@gmail.com" target="_blank">mr.hipboi@gmail.com</a>> wrote:<br>
><br>
>><br>
>><br>
>> On Tue, Apr 10, 2012 at 11:56 AM, Akash <<a href="mailto:akash87@gmail.com" target="_blank">akash87@gmail.com</a>> wrote:<br>
>><br>
>>><br>
>>> On Apr 10, 2012 6:29 AM, "Tom Cubie" <<a href="mailto:mr.hipboi@gmail.com" target="_blank">mr.hipboi@gmail.com</a>> wrote:<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > On Mon, Apr 9, 2012 at 10:58 PM, Akash <<a href="mailto:akash87@gmail.com" target="_blank">akash87@gmail.com</a>> wrote:<br>
>>> >><br>
>>> >> Hi,I downloaded allwinner-linux 3.0 branch from amery in github. i<br>
>>> changed the cross compile path to the appropriate location in<br>
>>> sun4i_crane.sh file. Running<br>
>>> >><br>
>>> >> buil.sh -p sun4i_crane gives me an error in the build_standby<br>
>>> function, saying there is no make target for 'all'<br>
>>> (lichee/arch/arm/mach-sun4i/pm/standby inside this folder)<br>
>>> >><br>
>>> >> I tried "making" it manually and it still gave me an error, from the<br>
>>> root of the kernel.<br>
>>> >><br>
>>> >> Jus wanted to find out, did anyone ever try compiling it? And if so,<br>
>>> did it compile successfully? With/without the shell script<br>
>>> >><br>
>>> >> I'm stuck with a small problem and im wondering if anyone might be<br>
>>> able to solve it.<br>
>>> >><br>
>>> >> I've built ics aosp source code with the allwinner device files and<br>
>>> system core provided by sztupy. I managed to build it successfully and now<br>
>>> i have the system.img and the other output files that usual building spits<br>
>>> out. But in order to make it successfully compatible with allwinner a10<br>
>>> board, they say i have to run mkfs.sh script, but this REQUIRES a<br>
>>> kernel/compiled kernel files as you might know.<br>
>>> >> 1. Which of your kernels can i use to compile successfully? ( i would<br>
>>> be greatful if anyone can provide the bImage(compiled kernel) :) )<br>
>>> ><br>
>>> > You can use this kernel if you want to run android.<br>
>>> > <a href="https://github.com/allwinner/linux-2.6.36.git" target="_blank">https://github.com/allwinner/linux-2.6.36.git</a><br>
>>> Does ICS run on this kernel?<br>
>><br>
>> ICS is not running on this kernel in products, but ICS can run on this<br>
>> kernel.<br>
>><br>
>Thank you for this information, i will try it out and let you know!<br>
><br>
>><br>
>>> >><br>
>>> >> 2. The tools provided by sztupy which will help disintegrate the<br>
>>> firmware image, Is it possible to use those files that have been extracted<br>
>>> back into the input for reconstructing it? If so how?<br>
>>> ><br>
>>> > Where is the tool?<br>
>>> The a10 kitchen tools...i can post the link if you want me to<br>
>>><br>
>>> If you can get a kernel from an android ics image, you can use it in your<br>
>>> ics build. In ics, the<br>
>>> > nandb is the boot.img partition, which contains kernel and rootfs.<br>
>>> ooh thanks, and how do i get the recovery.img and root.img?<br>
>><br>
>> recovey.img is not important, but you can get root.img from boot.img, it's<br>
>> an android<br>
>> defined image, you can see the header here:<br>
>><br>
>> <a href="https://github.com/sztupy/allwinner_android_system_core/blob/android-2.3.7_r1/mkbootimg/bootimg.h" target="_blank">https://github.com/sztupy/allwinner_android_system_core/blob/android-2.3.7_r1/mkbootimg/bootimg.h</a><br>
>> You can check this page for more info:<br>
>><br>
>> <a href="http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images" target="_blank">http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images</a><br>
>><br>
>You see i was going along this tutorial<br>
><a href="http://forum.xda-developers.com/showthread.php?t=1490886" target="_blank">http://forum.xda-developers.com/showthread.php?t=1490886</a><br>
>It was over there that i found the a10 flash kitchen tool, which says<br>
>according to<br>
><a href="http://forum.xda-developers.com/showthread.php?t=1490886#post_message_22397975" target="_blank">http://forum.xda-developers.com/showthread.php?t=1490886#post_message_22397975</a><br>
> that<br>
><br>
</div></div>>*B: Create image*<br>
<div><div>><br>
>If you have initialized the kitchen, you have to copy the four files from<br>
>linux (system.img, root.img, recovery.img and bImage) inside the _input<br>
>directory. You will also need to rename the .img files to .fex (so they<br>
>should be system.fex, root.fex, recovery.fex).<br>
><br>
>If you are done with this, then run create_image.bat. It will create an<br>
>output.img file, that can be flashed to the device using LiveSuite.<br>
><br>
>Naturally, from this i was thinking that those 4 files would be needed to<br>
>be able to create the final image.<br>
><br>
>><br>
>>> >><br>
>>> >> 3. Ultimately i want to replace only the system.img in the final<br>
>>> image, is there a straight forward way to do that?<br>
>>> ><br>
>>> > Try fastboot.<br>
>>> Fastboot does not even recognize the damn device :p<br>
>><br>
>> Fastboot needs u-boot running fastboot command and in fastboot state.<br>
>><br>
>(Ok, i think i've to elaborate in this case, i'm using ubuntu 10.04 as per<br>
>the recommended build environment. Plugging in my device and taking it into<br>
>the fastboot state is when "fastboot devices" should list down the device.<br>
>But it is not doing so. I'm guessing i'm going to have to try it in windows<br>
>now)<br>
>Directly related to this, i was wondering, again because of looking at the<br>
>tutorial, it says i'm supposed to run the images through the shell script<br>
>mkfs.sh, which will give out system.img. Am i supposed to flash the img<br>
>given out by the shell script or am i supposed to flash the img that has<br>
>been derived from compiling the aosp code?<br>
><br>
>><br>
>>> >><br>
>>> >> Thanks In advance!<br>
>>> >><br>
>>> >> --<br>
>>> >><br>
>>> >> Adrenaline Junkie<br>
>>> >><br>
>>> >> _______________________________________________<br>
>>> >> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
>>> >> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>>> >> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > --<br>
>>> > Keep simple, stay foolish.<br>
>>> ><br>
>>> ><br>
>>> ><br>
>>> > _______________________________________________<br>
>>> > arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
>>> > <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>>> > Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
>>> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>>> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> Keep simple, stay foolish.<br>
>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
>> <a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>> Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a><br>
>><br>
><br>
><br>
><br>
>--<br>
>Adrenaline Junkie<br>
><br>
>_______________________________________________<br>
>arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
><a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
>Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a><br>
_______________________________________________<br>
arm-netbook mailing list <a href="mailto:arm-netbook@lists.phcomp.co.uk" target="_blank">arm-netbook@lists.phcomp.co.uk</a><br>
<a href="http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook" target="_blank">http://lists.phcomp.co.uk/mailman/listinfo/arm-netbook</a><br>
Send large attachments to <a href="mailto:arm-netbook@files.phcomp.co.uk" target="_blank">arm-netbook@files.phcomp.co.uk</a></div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br>
Adrenaline Junkie<br>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Adrenaline Junkie<br>
</div></div></div>