Related
i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
chchia said:
i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
Click to expand...
Click to collapse
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
You can send the "update-script" to me,then let me give a look.
My email addrress:[email protected]
Or just paste it here so that it can help everyone.
dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Well.Take it onder in the web,let me try to download it.
So,I can take a look.
dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Maybe it is this:"write_raw_image tmp/boot.img boot"
zeaxion said:
Maybe it is this:"write_raw_image tmp/boot.img boot"
Click to expand...
Click to collapse
No .... that is wrong syntax. Won't even work in an update-script. For the Incredible S you need an updater-script (not update-script). Commands are followed by parentheses, with each parameter followed by a comma, and then a semi-colon at the very end. Run the kitchen on your ROM to get the proper syntax.
Anyways, nothing can be done at this point unless the original poster provides more detail, like at least posting his updater-script.
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Mattix724 said:
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Click to expand...
Click to collapse
That's correct syntax, but it doesn't work on newer htc devices because of the new filesystem formats. Boot.img has to be copied to /tmp folder before it can be flashed to device. You have to use updater-script to accomplish that.
dsixda said:
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
Click to expand...
Click to collapse
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
I never had any issues using
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
in my updater-script for Incredible S.
lars.oakland said:
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
Click to expand...
Click to collapse
Status 7 usually means you are using the wrong update-binary.
dsixda said:
Status 7 usually means you are using the wrong update-binary.
Click to expand...
Click to collapse
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
chchia said:
assert failed: write_raw_image("tmp/boot.img","boot")
Click to expand...
Click to collapse
Should tmp/boot.img be /tmp/boot.img?
Mioze7Ae said:
Should tmp/boot.img be /tmp/boot.img?
Click to expand...
Click to collapse
Good catch!
rsxtypes72 said:
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
Click to expand...
Click to collapse
Update-binary is not the update-script.
The update-binary file is supposed to be included with the updater-script and contains all the command implementations that are used in the script... however there are three main types of update-binary and you have to know which one to include. They are mostly differentiated by the number of parameters supported for the 'mount' command for your updater-script.
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
rsxtypes72 said:
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On your G2 you should have only an update-script in the ROM, or else the two other files (updater-script and update-binary), not both at the same time. The updater-script is a more advanced script than the update-script yet very similar.
The new versions of ClockworkMod only support the updater-script + update-binary however.
dsixda said:
The new versions of ClockworkMod only support the updater-script + update-binary however.
Click to expand...
Click to collapse
This is why the roms have both. I have not come across a single htc vision rom that only has an update-binary in it. They all have both
Sent from my T-Mobile G2 using XDA App
Update.
I just wanted to add that I have tried countless times to make a rom. I check that update script has no error and still I get the same error.
The weird thing is if I use a custom rom from one of the devs that does boot and I use the kitchen to go from edify to amend and then try to
convert it back later after I have made changes using the kitchen it wont boot and results in same write error.
Has anyone been able to make a bootable vision rom using the kitchen? If you have can you tell me where I can look or can you give me some answers. Yes I have checked google. No luck. Thanks
Im almost ready to give up.
I did make one rom that booted up and worked fine. Except when i went thru the steps to make the zip I removed the updater-script and update-binary created by the kitchen and replaced them with the udpater-script and update binary from one of the dev roms I use. This is the only way I have gotten a rom to flash and boot.
Just a thought. I know you said the htc vision is supported but would adding an edify_def for it help solve the problem?
Sent from my T-Mobile G2 using XDA App
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?
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
Hi guys,
I'm trying to set up Aroma Installer for my own Custom ROM. When I try to flash the ROM, it shows all but when i had nearly finished it let me choose Installation Demo and other options. This will flash the ROM or it will show me what will happen without flashing it?
If it is only a demostration, what I have to do to flash the ROM definetly?
Thank you!!!
TenKoX said:
Hi guys,
I'm trying to set up Aroma Installer for my own Custom ROM. When I try to flash the ROM, it shows all but when i had nearly finished it let me choose Installation Demo and other options. This will flash the ROM or it will show me what will happen without flashing it?
If it is only a demostration, what I have to do to flash the ROM definetly?
Thank you!!!
Click to expand...
Click to collapse
By the looks of it, it's just a demo
To flash a ROM, go to its thread, download it(it won't be 5 mb, it would be probably bigger than 100 mb or around it) and follow the instructions on how to flash it.
Sent from my GT-S5830i using xda app-developers app
How about posting your meta-inf folder here so someone can see where you went wrong as in its hard to give you an answer without more detail
Sent from my Nexus 4 using xda premium
demkantor said:
How about posting your meta-inf folder here so someone can see where you went wrong as in its hard to give you an answer without more detail
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I don't think that there is a problem in my meta-inf folder. I just ask what I have to do to skip the demo and flash the ROM.
Thank you for answering!
iamareebjamal said:
By the looks of it, it's just a demo
To flash a ROM, go to its thread, download it(it won't be 5 mb, it would be probably bigger than 100 mb or around it) and follow the instructions on how to flash it.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
I don't want to flash other's ROM. I want to install Aroma for MY ROM so when someone try to flash my rom, he'll be able to choose what he want to install or not.
Thank you for answering!!
TenKoX said:
I don't want to flash other's ROM. I want to install Aroma for MY ROM so when someone try to flash my rom, he'll be able to choose what he want to install or not.
Thank you for answering!!
Click to expand...
Click to collapse
Then you need to modify Aroma-Config (Uses C as language) and updater-script to make the package behave as you want.
If you don't want options in Aroma, just a simple installer of ROM
Then, follow this guide
http://forum.xda-developers.com/showthread.php?t=2223368
iamareebjamal said:
Then you need to modify Aroma-Config (Uses C as language) and updater-script to make the package behave as you want.
If you don't want options in Aroma, just a simple installer of ROM
Then, follow this guide
http://forum.xda-developers.com/showthread.php?t=2223368
Click to expand...
Click to collapse
I have done all of this before but it continues taking me to the demo.
Here is my aroma-config and udapter-script files.
The reason the demo keeps playing is because you haven't set things up right, that's why I'm asking for your meta-inf folder and all its contents, if you would like to have aroma flash your ROM and not play a demo that is.... Choice is yours
Sent from my Nexus 4 using xda premium
demkantor said:
The reason the demo keeps playing is because you haven't set things up right, that's why I'm asking for your meta-inf folder and all its contents, if you would like to have aroma flash your ROM and not play a demo that is.... Choice is yours
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Here is my meta-inf folder
Sorry, my phone is being a **** and won't let me extract .rar, can you either upload it as a .zip or you could use pastebin to post your updater-script and aroma-binary otherwise it will have to wait until I can get near a PC (few more hours)
Sent from my Nexus 4 using xda premium
demkantor said:
Sorry, my phone is being a **** and won't let me extract .rar, can you either upload it as a .zip or you could use pastebin to post your updater-script and aroma-binary otherwise it will have to wait until I can get near a PC (few more hours)
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Here is the meta-inf as .zip.
Thank you for helping me!!
TenKoX said:
Here is the meta-inf as .zip.
Thank you for helping me!!
Click to expand...
Click to collapse
No problem, just busy right now so sorry if it takes a bit to answer.
Right now all you did was swap updater scripts, you need to edit your aroma-config to have it select what you want.
If you need some help with it I'll be home in maybe 5hours and can lend a hand then, in the meantime take a look at some of my (or others) aroma packaged and see how they matched aromaconfigs to updater scripts
Sent from my Nexus 4 using xda premium
ok this is just a quick sloppy job but should get you what your after, feel free to ask any more questions on how to pretty it up for your installers
View attachment META-INF.zip
demkantor said:
ok this is just a quick sloppy job but should get you what your after, feel free to ask any more questions on how to pretty it up for your installers
View attachment 2099972
Click to expand...
Click to collapse
Thank you!!! It works!!!
Can you tell me how you did it?
Now, how I can put different options? For example, if someone installs my ROM I would like them to choose what kernel or app they want to install or not. How can I do that and where I must place the .apk files (for the apps) or the .zip files (for the kernels)?
Thank you again!!!
I'm seeing that the installer does not install the ROM, how I can do that?
@demkantor
Dear mate!
Could you plz help me to correct my rom aroma installer, i configured aroma-config and updater script but during flash process it show (Status 1) error on line 187 col 4 or something like this.
TenKoX said:
I'm seeing that the installer does not install the ROM, how I can do that?
Click to expand...
Click to collapse
all i did was fix aroma, you need to put the files in the proper place, as in open root folder, there should be two inside (more if needed for other purposes) meta-inf and system, put all rom info organized properly in system and then flash
you can always save aroma logs if you have questions
and yes i can help you add kernel choices and such but i need to know what all options you need or want
ab-samy said:
@demkantor
Dear mate!
Could you plz help me to correct my rom aroma installer, i configured aroma-config and updater script but during flash process it show (Status 1) error on line 187 col 4 or something like this.
Click to expand...
Click to collapse
change
"Touchwiz Launcher","It's the Default (Stock) Launcher of the Samsung Galaxy S2 with some cool Features and transitions",0, #--selected.1 = 3
Click to expand...
Click to collapse
to
"Touchwiz Launcher","It's the Default (Stock) Launcher of the Samsung Galaxy S2 with some cool Features and transitions",0 #--selected.1 = 3
Click to expand...
Click to collapse
no comma after the 0
I have added the system and meta-inf folders and packed all of this as a .zip before. Do i have to modify any other aroma files?
Sorry for being so noob...
Sent from my GT-I9001 using xda app-developers app
No need to apologize, we all learn new thongs every day!
You shouldn't have to edit any script, just take your system folder and meta-inf (and anything else needed) zip them up and sign, when you flash in aroma be sure to save logs so you can check it later for errors
Sent from my Nexus 4 using xda premium
demkantor said:
No need to apologize, we all learn new thongs every day!
You shouldn't have to edit any script, just take your system folder and meta-inf (and anything else needed) zip them up and sign, when you flash in aroma be sure to save logs so you can check it later for errors
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I have signed it with ROM kitchen and packed all as zip. When i try to start Aroma with the recovery, it says:
Code:
E:Can't copy META-INF/com/google/android/update-binary
Installation aborted.
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.