Hi to all,
I have a question about this three file :
zImage - initramfs.cpio.gz - openaos-gingerbread-XXX.img.gz
I Know that initramfs.cpio.gz it' useful only to set up the environment (set up filesystem and various exucutable) to boot correctly the zImage (Kernel Android).
So when I flash the device and then I choose the boot from Developer Edition , the device use the initramfs.cpio.gz and the zImage used in flash procedure.
But why i need to copy openaos-gingerbread-XXX.img.gz in the root of the directory?
what is this image file? what's' your role?
thanks so muck
It contains the whole OS,so gingerbread is in there.
Or what did you think where GB is coming from!?
It's right... sorry for my stupid question. I don't know why... but I thought that the OS was the same
thanks a lot...
Related
ok so im trying to port for the first time to a i5800.
Now i have Ubuntu and the disxda's kitchen in it.
I've got the boot.img , system.img, data.img, zImage and factoryfs.rfs of my phone with me.
Now my questions are:
1. would a Froyo init.rc work for the ICS?
2. When i try to mount the factoryfs.rfs of my phone, the aplications i tried to use always gave an error stating its not a valid CD image or somethingsimimlar(ive used UltraISO and MagicISO)
3. When i try to extract boot.img using disxda's kitchen, it says Android header not found in boot.img or anywhere in the boot.img and the kernel pagesize is 0.
4. i dont want an Update.zip instead i want it like a flashable rom(are they the same?)
Any help would greatly be appreciated.
I have a working Kernel - http://forum.xda-developers.com/attachment.php?attachmentid=1743802&d=1361298599
but I need prepare a new one - compilation it is no problem, but how to prepare img file for taht?.
I heard that this is a Rockchip kernel image file - so I am a looking for information how to build this kind of kernel?
Procesor is RK3066.
mafamafa said:
I have a working Kernel - http://forum.xda-developers.com/attachment.php?attachmentid=1743802&d=1361298599
but I need prepare a new one - compilation it is no problem, but how to prepare img file for taht?.
I heard that this is a Rockchip kernel image file - so I am a looking for information how to build this kind of kernel?
Procesor is RK3066.
Click to expand...
Click to collapse
If that is a zImage, then you need to pack it into boot.img in order to flash.
There are many boot.img tools out there which can help you. But the thing is you will be needing your device's original boot.img (Which can be extracted from your device depending upon the partition) which contains the Ramdisk in order to be successful.
coolsandie said:
If that is a zImage, then you need to pack it into boot.img in order to flash.
There are many boot.img tools out there which can help you. But the thing is you will be needing your device's original boot.img (Which can be extracted from your device depending upon the partition) which contains the Ramdisk in order to be successful.
Click to expand...
Click to collapse
In fact it is a regular (no gziped) image not a zImage. The file after unpacking from RK3066 format starts with bytes d3 f0 21 (to unpack I'm using rkutils ).
But I don't understand why we need to make boot.img with this file and only after that, upload boot.img to the device. Normally it should be possible just to upload kernel.img to the partition where kernel is stored, no?
After kernel from the link above is uploaded to this partition, the device boots up without problem. But when we compile new kernel and upload it (after converting with rk-tools ) it is not even possible to boot the device.
Any idea what's going on? Is compiling a kernel, then converting to rk3066 format is enough ?
flowher said:
In fact it is a regular (no gziped) image not a zImage. The file after unpacking from RK3066 format starts with bytes d3 f0 21 (to unpack I'm using rkutils ).
But I don't understand why we need to make boot.img with this file and only after that, upload boot.img to the device. Normally it should be possible just to upload kernel.img to the partition where kernel is stored, no?
After kernel from the link above is uploaded to this partition, the device boots up without problem. But when we compile new kernel and upload it (after converting with rk-tools ) it is not even possible to boot the device.
Any idea what's going on? Is compiling a kernel, then converting to rk3066 format is enough ?
Click to expand...
Click to collapse
Ok, I just had a look at your link and yes, it contains the kernel.img file. So it should be the kernel image file which needs to be flashed. What you actually needed to do is, unpack that kernel image using the tools of your choice and you'll get the ramdisk, zImage etc when unpacking. If you have compiled kernel from Sources, then you need to replace the zImage with yours (Found in arch/arm/boot) if your compilation was successful without errors and repack it to form the kernel.img.
But that doesn't mean it should boot compulsorily, it may not boot depending upon various weird reasons. You may have to fix it by yourself. Nearest bet is using your device's config file (Found in /proc/config.gz) and use that to compile your kernel. You can find all infos regarding what I've mentioned in this thread:
http://forum.xda-developers.com/showthread.php?t=1748297
Welcome.
For a long time I get tired of the boot.img file. I do not know what I'm doing wrong but I can not decompile it to the form that let would to edit. He wants to make some changes in files and default.prop init.rc but I can not because the only file which me to unpacks zImage file is empty, or if I use another tool I received an error "android magic not found" (magical first 7 letters of also I added Hexedit but still the same error).
Here you can download the file boot.img of the fight:
boot.img - 7.44 MB
I have tried programs:
- Android-Kitchen-master
- Android Image Kitchen
- bootimg_tools
- unmkbootimg
- kernel-tools-master
- linux_kernelkitchen-0.002
But unfortunately without success
If someone manages to successfully dismantle this file I would really ask for instructions on how to go about it.
Thank you in advance for your help and sorry for my poor english.
I have met some problem with boot.img and need some help if there's somebody know it.
I used unmkbootimg and mkbootimg, I unpacked a boot.img then got zimage and initramfs.cpio.gz, I repacked it without any edit but the new boot.img becames smaller, it changed from 13M to 7.9M, and the phone couldn't boot from new boot.img,
and there is no question if I use a boot.img extracted from an android3.x-version rom, but if the android version changes to 4.x, the unpack-repack process would lose much size...I tested on mi2s' rom......I don't know if there are some files that will be lost in unpack process, or say the process just ignore files other than zimage and initramfs...
does anybody knows why?
binghemoye said:
I have met some problem with boot.img and need some help if there's somebody know it.
I used unmkbootimg and mkbootimg, I unpacked a boot.img then got zimage and initramfs.cpio.gz, I repacked it without any edit but the new boot.img becames smaller, it changed from 13M to 7.9M, and the phone couldn't boot from new boot.img, does anybody knows why?
Click to expand...
Click to collapse
It could be because of incorrect settings for mkbootimg or there more files,than zImage and initramfs, needed for proper work. Hard to say without more information.
Sorry for my bad English.
B.B.N. said:
It could be because of incorrect settings for mkbootimg or there more files,than zImage and initramfs, needed for proper work. Hard to say without more information.
Sorry for my bad English.
Click to expand...
Click to collapse
There is no question if I use a boot.img extracted from an android3.x version rom, but if the android version changes to 4.x, the unpack-repack would lose much size...I tested on mi2s' rom......I don't know if there are some files that will be lost in unpack process, or say the process just ignore files other than zimage and initramfs...
Hy !
i am beginner in rom cooking. I compile with succes Android from Google and ran good in emulator. After that i try to compile Cyanogenmod for my smartphone (jfltexx - Galaxy S4).
Compile with no problems so i try to understand how i can flash my phone and i found Archikitchen.
After somes trys (at the first time i don't understand what is /dev/block/ and where find /boot), finally i have my zip.
Of course, i flash it and it's no working (obviously it would be not funny isn't it ?). My phone start on kernel, display Galaxy S4 logo, after few seconds reboot on recovery mode.
I made a second zip after compile again (make clean, repo sync, source build/envsetup breakfast jfltexx, make -j8) and not working again (compile good but problem with my second zip).
At this point i want to understand how it is works. use Archikitchen is easy but i don't understand process to make a zip. In my folder (~/cyanogen/out/target/product/jfltexx/), i have :
- boot.img
- kernel
- ramdisk.img
-ramdisk-recovery.img
- recovery.img
- system.img
- userdata.img
I don't know exactly how android boots but i know it looks kernel and ramdisk in /boot and after it mounts /system and /data.
I use dd to flash my new recovery from phylz touch to TWRP and i want to do the same thing with my files (system.img to /system, userdata.img /data etc ...) but i think it's not a good idea because i don't know how use boot.img and ramdisk.img to make /boot.
So many questions for a noob, apologize if they are already a thread for all, i didn't found it.
Thx a lot.