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
There is nobody who can help me I have to give me a reference
Aleaba said:
There is nobody who can help me I have to give me a reference
Click to expand...
Click to collapse
if im not mistaked the kitchen was built primarily for HTC devices
thank you
If you have any ideas for how I can cook a rom for lg P920 I would be grateful for the help
Aleaba said:
thank you
If you have any ideas for how I can cook a rom for lg P920 I would be grateful for the help
Click to expand...
Click to collapse
What exactly are you trying to do?
Sent from my PC36100 using Xparent Red Tapatalk 2
Go to the LG optimus 3d or thrill 4g Dec section and look for acid hazard kitchen Tom that's what I'm running on my 3d and its awesome
xstokerx said:
Go to the LG optimus 3d or thrill 4g Dec section and look for acid hazard kitchen Tom that's what I'm running on my 3d and its awesome
Click to expand...
Click to collapse
Ok I'll try to give them a look, thanks
jboyer0000 said:
What exactly are you trying to do?
Click to expand...
Click to collapse
I'm trying to cook a rom, as I wrote above does not work with Kitchen, thanks for the help
I tried but it does not work on my phone refuses to flash the rom with AcidHazardROM KITCHEN, attached you can see all the folders of my rom files and scripts
Aleaba said:
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
Click to expand...
Click to collapse
Its only the kernel that's not compatible with the kitchen. You can still mess with the rom itself in the kitchen. You may need to copy the updater script from your original rom though. Also I would recommend just zipping the rom up manually and not using the kit hen for that. The kit hen is good for adding root or deodexing, things like that.
If you want to mess with the boot.img for the p920/925 you will need specific tools which can be found in the development section of the Thrill/p925 forum.
Sent from my SAMSUNG-SGH-I777 using XDA
http://forum.xda-developers.com/showthread.php?t=633246
I made a rom for LGP970
Related
I have been cooking a customized ICS ROM using dsixda's kitchen and all I done was deodex the ROM and add some other stuff like bash, nano etc. I then built and signed it. When I attempt to flash it tells me there is an error in the .zip file and displays (status 0). I am guessing I have done something wrong when building the ROM in dsixda's kitchen.
Does anyone know what a status 0 error means in CWM and how I can fix it?
Wrong update-binary
私のEVO 3Dから送信される。
Ahh right thank you!
Sent from my Nexus S using xda premium
dastin1015 said:
Wrong update-binary
私のEVO 3Dから送信される。
Click to expand...
Click to collapse
what shoukd it be update or updater
Sent from my GT-S5670 using xda premium
Mr.Oug said:
what shoukd it be update or updater
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
update-binary, update-script and updater-script are three different things.
私のEVO 3Dから送信される。
I had faced the same problem what should i do ....?
I have the same problem!
how can i solve this problem?
same here, my galaxy note is bricked
I have the same problem.. on LG 2x
find out if your device takes update-script(Amend)or updater-script(Edify)
Sent from my HTC VLE_U using Tapatalk 2
ourcumnt THIRD
How to find out if your device takes update-script(Amend)or updater-script(Edify)?? :good:
Pranjal Joshi said:
How to find out if your device takes update-script(Amend)or updater-script(Edify)?? :good:
Click to expand...
Click to collapse
Look in the Meta-inf then com>Google > android then you will see the script one the binary and the update or updater script
If you got update-script then amend
Updater-script you got edify
Sent from my PG86100 using Tapatalk 2
try to find an update-binary from another custom rom and use that one
globula_neagra said:
try to find an update-binary from another custom rom and use that one
Click to expand...
Click to collapse
please don't try that, i just used JMP xtreme's update binary file on my custom rom, and i just CEMENTED my Micromax canvas 2.
i'm also stuck at the status 0 error.
SOMEONE HELP US !!!!!!
FirmShark said:
I have been cooking a customized ICS ROM using dsixda's kitchen and all I done was deodex the ROM and add some other stuff like bash, nano etc. I then built and signed it. When I attempt to flash it tells me there is an error in the .zip file and displays (status 0). I am guessing I have done something wrong when building the ROM in dsixda's kitchen.
Does anyone know what a status 0 error means in CWM and how I can fix it?
Click to expand...
Click to collapse
Status 0 means that you have a wrong script.Put a correct script in "/META-INF/com/google/android" floder in your rom.
quadratic_function said:
Status 0 means that you have a wrong script.Put a correct script in "/META-INF/com/google/android" floder in your rom.
Click to expand...
Click to collapse
I use dsxda and when i build the rom i use updater script, the ROM was coocked by 0, from system folder and boot.img, any solutions?
The update-binary for mtd type phones from dsixda kitchen no longer run on some new mtd phones. You may try to replace the update binary with other update binary and modify the scripts to mount using busybox and the format partition command should be removed and do the format from cwmr menu.
I´ve got update-binary, update-binary.orig, updater-script, updater-script.orig and update-script
What should i do to fix the status 0 error?
thanks for help
sgt_R04CH said:
please don't try that, i just used JMP xtreme's update binary file on my custom rom, and i just CEMENTED my Micromax canvas 2.
i'm also stuck at the status 0 error.
SOMEONE HELP US !!!!!!
Click to expand...
Click to collapse
Ofc, you have to use one, from the same phone, eg: OTA UPDATE
Instalation aborted
how to solve this problem?
Hi everyone,
I'm noob here. I'm using Xperia S. And now learning mote about android.
However I have a question, how can I make boot.img from my ftf file?
Sure, I extracted the ftf, decrypt the kernel.sin into kernel.elf.
From kernel.elf, I decrypt it again and get 4 files, one image (I suppose it is kernel zImage), one ramdisk.gz, one file forgotten and another is elf.4.
Okay, now the problem comes.
The main purpose of me is to change the bootlogo of my Xperia S.
I searched for a day to change the bootlogo, most need to add the rle file into boot.img file (ramdisk).
For sure I read through the site how to unpack, edit and repack the boot image.
The kernel and ramdisk of mine are extracted from ftf but not existing custom Rom,
1. Can I directly use the mkbootimg program to create boot.img? Will it work out?
2. Do I need to aware of any parameters or setting for Xperia S? Since I worried that different devices have diff setting.
3. Is it better to make it on linux? I found mkbootimg.c in c language file but not precompiled program as tutorial, the link given is broken. Can work also?
Sorry, I'm really quite new and very noob, I tried searching and many other things, but still can't figure it out.
Hope that pros here can help me...
Sent from my LT26i using xda app-developers app
Trevor Chuah said:
Hi everyone,
I'm noob here. I'm using Xperia S. And now learning mote about android.
However I have a question, how can I make boot.img from my ftf file?
Sure, I extracted the ftf, decrypt the kernel.sin into kernel.elf.
From kernel.elf, I decrypt it again and get 4 files, one image (I suppose it is kernel zImage), one ramdisk.gz, one file forgotten and another is elf.4.
Okay, now the problem comes.
The main purpose of me is to change the bootlogo of my Xperia S.
I searched for a day to change the bootlogo, most need to add the rle file into boot.img file (ramdisk).
For sure I read through the site how to unpack, edit and repack the boot image.
The kernel and ramdisk of mine are extracted from ftf but not existing custom Rom,
1. Can I directly use the mkbootimg program to create boot.img? Will it work out?
2. Do I need to aware of any parameters or setting for Xperia S? Since I worried that different devices have diff setting.
3. Is it better to make it on linux? I found mkbootimg.c in c language file but not precompiled program as tutorial, the link given is broken. Can work also?
Sorry, I'm really quite new and very noob, I tried searching and many other things, but still can't figure it out.
Hope that pros here can help me...
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
how did you decrypt kernel.sin ? can you explain step by step ? Im also a noob
ShivangDave said:
how did you decrypt kernel.sin ? can you explain step by step ? Im also a noob
Click to expand...
Click to collapse
For how to decrypt the kernel.sin, you can use Flashtool (not Sony official one)
Under Tools (perhaps I remember correctly), there is a option about decrypt SIN, and then you can choose the kernel.sin you want to decrypt.
Have to tried kernel kitchen?
neectron said:
Have to tried kernel kitchen?
Click to expand...
Click to collapse
Yes, I tried Kernel Kitchen by champion at that time after I asked this question since nobody answer this thread.
I use command way to perform this boot.img creation also. It work that time. now forgot some part dy.
Trevor Chuah said:
Yes, I tried Kernel Kitchen by champion at that time after I asked this question since nobody answer this thread.
I use command way to perform this boot.img creation also. It work that time. now forgot some part dy.
Click to expand...
Click to collapse
Oh,now I see question is so old
neectron said:
Oh,now I see question is so old
Click to expand...
Click to collapse
yeah, very old. haha
Anyway, thank you for your kindly reply.
Moving my way toward developer (super noob developer). haha
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
kagouro said:
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
explain more
Help Building a CUSTOM(from STOCK ROM)
Newbie here---
- I have downloaded the HTC stock RUU for my device.
- I used Android Kitchen cygwin to extract the files, setup the working folder.
- Added root permissions,BusyBox
- Built the rom from working folder.
Wanted to test whether this works or not... But Phone Got stuck on HTC logo .. Not even BOOTANIMATION.
What did i miss or DO wrong here??
Where in these steps worked flawlessly when i took a custom rom? What else should be done here?? Help would be Appreciated!!!
Learn More About Kitchen. Add Root, Busybox, Put apk files in System/aps etc. What do you want to do?
cheqolada said:
Learn More About Kitchen. Add Root, Busybox, Put apk files in System/aps etc. What do you want to do?
Click to expand...
Click to collapse
I'm Sorry, The ROM i built from the working folder did not boot. My question was what went wrong?
kagouro said:
Hello,
I want to make a custom ROM based on a stock i9001 ROM. However when I extracted the tar file there were IMG and ext4 files. I know how to make a rom via cygwin when i have: 1) system folder
2) META-INF folder
And 3) boot.img
I don't know what to do to the stock ROM
(.tar) to be like this
*** sorry for my bad english
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Maybe this is what you search:
http://forum.xda-developers.com/showthread.php?t=1976412
yashwantpiduru said:
I'm Sorry, The ROM i built from the working folder did not boot. My question was what went wrong?
Click to expand...
Click to collapse
My Answer is for kagouro - Becouse i Don't see your post when I write.
If Your Phone is dedected in adb you can use logcat (adb logcat in windows cmd) if phone don't dedected in adb - flash recovery via fastboot, join in recovery , instal working rom and found bad files in rom (try add modyfication singly - first root, second busybox etc - in this metod you can see whad mod don't work - probably stupid method but work :cyclops
yashwantpiduru said:
Newbie here---
- I have downloaded the HTC stock RUU for my device.
- I used Android Kitchen cygwin to extract the files, setup the working folder.
- Added root permissions,BusyBox
- Built the rom from working folder.
Wanted to test whether this works or not... But Phone Got stuck on HTC logo .. Not even BOOTANIMATION.
What did i miss or DO wrong here??
Where in these steps worked flawlessly when i took a custom rom? What else should be done here?? Help would be Appreciated!!!
Click to expand...
Click to collapse
Kitchen will replace certain necessary parts of your ROM if it isn't compatible with the kitchen, it puts them back when you compile. When you compiled your ROM did you take the guided option? Also, and probably the first thing I should have asked, is your phone compatible with kitchen?
Sent from my SPH-D710 using xda premium
Stryke_the_Orc said:
Kitchen will replace certain necessary parts of your ROM if it isn't compatible with the kitchen, it puts them back when you compile. When you compiled your ROM did you take the guided option? Also, and probably the first thing I should have asked, is your phone compatible with kitchen?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
My phone is compatible with the kitchen.
Yeah I took the guided step! Still no luck
sent from my oc'd incS
yashwantpiduru said:
My phone is compatible with the kitchen.
Yeah I took the guided step! Still no luck
sent from my oc'd incS
Click to expand...
Click to collapse
OK, just for giggles try this, take the meta-inf folder from a rom you know works and using 7zip replace the one in your rom. Let me know if that helped at all:beer:
Sent from my SPH-D710 using xda premium
Stryke_the_Orc said:
OK, just for giggles try this, take the meta-inf folder from a rom you know works and using 7zip replace the one in your rom. Let me know if that helped at all:beer:
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Sure! its late! I will try and let you know asap!
P.S: actually I tried this as well adding aroma installer to the rom! That had some ext3 error ! Dont have a clue what's that?
sent from my oc'd incS
yashwantpiduru said:
Sure! its late! I will try and let you know asap!
P.S: actually I tried this as well adding aroma installer to the rom! That had some ext3 error ! Dont have a clue what's that?
sent from my oc'd incS
Click to expand...
Click to collapse
Ext3 is a mount point, I'm not sure what it would be specific to your device, but it tells me there's an error in your updater script
Sent from my SPH-D710 using xda premium
Stryke_the_Orc said:
Ext3 is a mount point, I'm not sure what it would be specific to your device, but it tells me there's an error in your updater script
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks for the heads up... I am gonna check the updater script.
sent from my oc'd incS
How do I extract boot.img from Xperia U
I already got many images but while unpacking they all say android magic header not found stopping using many tools
I used android kitchen and all
one more thing
i made rom using android kitchen and then when i boot
wifi,bluetooth and phone aint working
Help Me
:crying:
jatinrungta said:
How do I extract boot.img from Xperia U
I already got many images but while unpacking they all say android magic header not found stopping using many tools
I used android kitchen and all
one more thing
i made rom using android kitchen and then when i boot
wifi,bluetooth and phone aint working
Help Me
:crying:
Click to expand...
Click to collapse
Have you tried this link? I find it helpful for the single core A8 Cortex (Polaroid) tablets when I have to access the boot.img. Look about halfway down for the "Boot partition" section.
Hope this helps.
https://www.miniand.com/wiki/Allwinner/Unpacking+and+building+LiveSuit+images
jatinrungta said:
How do I extract boot.img from Xperia U
I already got many images but while unpacking they all say android magic header not found stopping using many tools
I used android kitchen and all
one more thing
i made rom using android kitchen and then when i boot
wifi,bluetooth and phone aint working
Help Me
:crying:
Click to expand...
Click to collapse
Use championswimmer tool http://forum.xda-developers.com/showthread.php?p=26229528
Sent from my GT-I9100 using xda app-developers app
rename it to kernel.elf and it can be extract either via flashtool or kitchen (kernel tools etc)
hi i know this seems like a over asked question but my case is different at least i could find a solution .. i did look for it
so i need to unpack a boot.img and i did try with dsixda's kitchen and championswimmers kitchen but no hope .. they both say android magic header not found and doesn't unpack it.. i need to edit the bootclasspath of the kernel but there isnt a way i can without unpacking yeah ? i even tried re-naming to .elf and extracting with flashtool but that dosent give me an output either ..
does anyone know how i can do this ? or atleast a workaround ?
androidous said:
hi i know this seems like a over asked question but my case is different at least i could find a solution .. i did look for it
so i need to unpack a boot.img and i did try with dsixda's kitchen and championswimmers kitchen but no hope .. they both say android magic header not found and doesn't unpack it.. i need to edit the bootclasspath of the kernel but there isnt a way i can without unpacking yeah ? i even tried re-naming to .elf and extracting with flashtool but that dosent give me an output either ..
does anyone know how i can do this ? or atleast a workaround ?
Click to expand...
Click to collapse
Try using this tool found here http://forum.xda-developers.com/showthread.php?t=2073775
it has worked very well for me. If this doesn't work for you then I can suggest some Linux alternatives.
Sent from my SCH-I535 using XDA Premium 4 mobile app
shimp208 said:
Try using this tool found here http://forum.xda-developers.com/showthread.php?t=2073775
it has worked very well for me. If this doesn't work for you then I can suggest some Linux alternatives.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey thanks but ive tried that kitchen before and no luck
i figure the problem is
caused because the boot.img 's are not of standard type and do not have the standard ANDROID header therefore that kitchen wouldnt work
Okay, unpackbootimg crashes trying to unpack the boot.img from FXP204-cm-9-20130126-UNOFFICIAL-kumquat because it has the wrong "magic" at the top. trevd pointed this out as a definite incompatibility for some devices a couple pages back. Trying trevd's split_img from the first page, it actually reports the "Wrong magic" error and shows that the file has an ELF header not an ANDROID!. Opening in HxD shows that there is no ANDROID! header later on as with some HTC devices, so ELF is the only header, and we're basically dealing with a different, unsupported filetype here. On the upside, there is no real gap in the data, so there might not be a ramdisk packed with it anyway.
Click to expand...
Click to collapse
enlighten me on the linux alternatives please
androidous said:
Hey thanks but ive tried that kitchen before and no luck
i figure the problem is
caused because the boot.img 's are not of standard type and do not have the standard ANDROID header therefore that kitchen wouldnt work
enlighten me on the linux alternatives please
Click to expand...
Click to collapse
These are the linux alternatives they may or may not work based on what you said but might as well give them a try.