Hello all I tried to cook a rom with Kitchen program but I have a problem while checking the file Boot.img the program reports the following errors
Code:
Checking boot.img
Working Folder Found
Android 'magic' header not found at start of boot.img
Checking if it exists elsewhere...
Warning Android Header not found in boot.img ( unsupported format)
Kernel found at offset775040367 in boot.img
Making folder BOOT-EXTRACTED...
Extracted kernel
Error. Zimage is Emply!
Extracting ramdisk...
Error: No Ramdisk folder found!
Warning: init.rc not found in boot.img
I have tried flash the phone but the installation is aborted
Related
Greetings, oh mighty people on XDA!
I am trying to change the FreeXperia screen (.rle file) on the CM 9.1.0 Rom for Xperia S (Nozomi) and i have run into a brick-wall
Whenever i'm trying to extract my boot.img using Dsixda's kitchen(cygwin - i'm a windows user) i get this:
Code:
Android 'magic' header not found at start of boot.img
Checking if it exists elsewhere ...
Warning: Android header not found in boot.img (unsupported format)
Error: kernel offset (page size) is 0
Press Enter to continue
Also found out that Xperia S is not on the kitchen's supported devices list, so here is the question:
how can i unpack and pack my boot.img using windows 7 (64-bit)?
You can extract it with 7-zip, the boot.img is an ELF file. Repacking will be difficult from there without a complete POSIX toolchain.
can't extract it with 7zip, it's said that file was not supported ...
use ultra iso or winrar ... just a wild
guess
Sent from my Xperia U using Tapatalk 2
Hi
I want to add to my custom ROM a new group id, which I have defined in the file "android_filesystem_config.h".
In general, this file will be included by the android source code, unfortunately my custom ROM has it also built in it sources and I don't have access to this header file.
Then I saw, that android kitchen has in its folder tools/mkboot the file "android_filesystem_config.h". How is this config file used by the kitchen, has it any influence on building the boot.img in the tool or not?
I tried to build a boot.img by running
Code:
mkbootimg --kernel zImage --initrd.gz -o boot.img
, but the modified android_filesystem_config.h did not have any influence. What is the tool mkbootfs for?
Is it even possible to patch a boot.img whit new gid information or do I have to rebuild a whole ASOP?
Thanks and regards
cloooned
hello
i want to create custom boot image.i am using cygwin bash shell and android kitchen.
i extract boot.img with Android Kitchen 0.194 Tools for boot images <unpack/re-pack/etc.>
it show like this
Working folder found
Kernal found at offset 2048 in boot.img
Making folder BOOT-EXTRACTED ....
Extracting kernal ...
Extracting ramdisk ...
Error : NO ramdisk folder found!
Press Enter to counting
How i solve Error:NO ramdisk folder found.
Are you have trouble extracting from the phone or extracting the .img file into something editable? I see at the top of the first page here that there is an update to the Kitchen. Maybe the newer version supports your phone better?
A very warm Hi! to the XDA community
My phone, the Sony Xperia E4, does not have a recovery - so I am slowly learning how to develop one. It has an MT6582 chip.
In the process I have obtained the stock boot.img (via boot.sin) from the phone's stock .ftf firmaware file.
I wish to use MTK droid tools to create the recovery, however it first gave me the error that the boot.img file is not split. After some research I came to learn that such boot.img files need to be split into the kernal (Zimage i believe) and ramdisk.
After some further research I came across this seemingly helpful guide and tool on how to split the boot.img file on Windows (unfortunately I do not have Linux at my disposal atm).
Now to my issue: (referring to the aforementioned guide & tool) When running the command
Code:
bootimg.exe --unpack-bootimg boot.img
I get this error:
Code:
AssertionError: invald bootimg
Which leads me to believe the boot.img file I have extracted may be corrupt or extracted from the wrong .sin file.
If you are still with me, how can i confirm that the boot.img file from the stock rom is indeed "working" and contains ramdisk and kernal?
Some extra information:
This is the guide I used to initially extract the boot.img file from my phones stock firmware. They highlight that boot.img is extracted from the kernal.sin file. My firmware has no such file. Later in the comments it mentions that newer Sony phones have the boot.img file in the appropriately named "boot.sin" file. This is the file i used to extract my boot.img. Thus from here I cannot see why the boot.img file cannot be split.
The full command line and response is:
Code:
C:\Users\\Downloads\Cofface>bootimg.exe --unpack-bootimg boot.img
arguments: [bootimg file]
bootimg file: boot.img
output: kernel[.gz] ramdisk[.gz] second[.gz]
Traceback (most recent call last):
File "<string>", line 2213, in <module>
File "<string>", line 1424, in unpack_bootimg
File "<string>", line 151, in parse_bootimg
AssertionError: invald bootimg
Thanks very much in advance!
Hi everyone
When I try to make a 233-based boot image with Rootkernel, I get this error.
----------------------------------------------------
>rootkernel.cmd kernel.elf boot.img
Rootkernel V5.23
- Unpacking kernel
. /booting:line 1 :syntax error :unexpected "<"
. /booting:line 1 :syntax error :unexpected ">"
Unknown boot image format
Aborting
----------------------------------------------------
Kernel.elf folder inside
I made a mistake.
EDIT...........................
Problem in operating system. Windows Xp did not work, but Windows 10 also worked.
Sorry bad English for Google translate
endelo46 said:
Hi everyone
When I try to make a 233-based boot image with Rootkernel, I get this error.
----------------------------------------------------
>rootkernel.cmd kernel.elf boot.img
Rootkernel V5.23
- Unpacking kernel
. /booting:line 1 :syntax error :unexpected "<"
. /booting:line 1 :syntax error :unexpected ">"
Unknown boot image format
Aborting
----------------------------------------------------
Kernel.elf folder inside
I made a mistake.
Sorry bad English for Google translate
Click to expand...
Click to collapse
are you trying to patch and add TWRP? If so,
there should only be one version of rootkernel 5.23 that will work with nougat, and it will be the one I halfbaked edited for 32.3.A.0.372 TWRP for temporary data only restore. rootkernel will work so long as you get the right 5.23 and only use it to patch boot.img for nougat, anything else was limited to marshmallow...
if you have the proper 5.23, make sure you're not using the fotakernel.sin to get kernel.elf