Database Users

[Q] lib files

maybe some one can help with this, when i push some *.so files to the lib folder, and then i reboot the device i stucked at the hero boot logo.
i replaced only some *.so files that already there, only these come from a other froyo sense rom.

What lib files did you push?
Sent from my Nexus One using xda premium

i want to push these:
libcameraservice.so
libcamera_client.so
libcamera.so
i wenn i got it right these files are to get the camera working in a sense froyo rom.
wenn not please correct me then

arnoslag said:
i want to push these:
libcameraservice.so
libcamera_client.so
libcamera.so
i wenn i got it right these files are to get the camera working in a sense froyo rom.
wenn not please correct me then
Click to expand...
Click to collapse
I thought there was _wrapper lib related to the camera but I think I'm thinking of something else. What does logcat say?
Sent from my Nexus One using xda premium

JieeHD said:
I thought there was _wrapper lib related to the camera but I think I'm thinking of something else. What does logcat say?
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Working on this now aswell, Hope to have some result in the next hour

Ok well the logcat is pretty short. It just stops on the SDcard..
Code:
--------- beginning of /dev/log/system
I/Vold ( 83): Vold 2.1 (the revenge) firing up
D/Vold ( 83): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
W/Vold ( 83): Ignoring unknown switch 'usb_configuration'
D/Vold ( 83): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
If you remove the SD card it is even shorter..
Code:
--------- beginning of /dev/log/system
I/Vold ( 83): Vold 2.1 (the revenge) firing up
D/Vold ( 83): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media
)
ow wait XD I did something stupid gonna retry now
---------- Post added at 10:37 AM ---------- Previous post was at 10:24 AM ----------
Ok no change , still same logcat

Well I tried my luck. But didn't get it to work. Got the same as lirasina.
Sent from my Hero using Tapatalk

Sorry but can someone tell me the exact files you're all pushing from what ROM and to which ROM. Slightly confused at the moment.

JieeHD said:
Sorry but can someone tell me the exact files you're all pushing from what ROM and to which ROM. Slightly confused at the moment.
Click to expand...
Click to collapse
These files
arnoslag said:
i want to push these:
libcameraservice.so
libcamera_client.so
libcamera.so
i wenn i got it right these files are to get the camera working in a sense froyo rom.
wenn not please correct me then
Click to expand...
Click to collapse
From HeroLatte 0.9 to ChoclateFroyo Rel 2

we are trying to push some *so files from herolatte froyo to chocolate froyo. To get the camera to work. Both are 2.2 sense roms. But i'm not sure with files that we have to push to get the camera working to in the chocolate rom.

still no luck, hopefuly some one have more luck then me.

Are the 2 roms not from different devices?
Sent from my Nexus One using xda premium

JieeHD said:
Are the 2 roms not from different devices?
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
herolatte 0.9 is running 2.2.1 ported from my touch 3g with a working camera,the chocolate sense rom has 2.2.1 ported from legend if m not mistaken,I don't think simply pushing the lib files would fix camera though ...
Sent from my HTC Hero using XDA App

That would be awsome if some1 could get the camera workin DD

[DEV] Compiling ICS for Cooper

Hello all,
due to the fact, that there are already activities to compile ICS for a lot of other devices, i have taken the liberty to open a thread for all Dev's and those who are interested in getting ICS to work on cooper. Hope that this is ok...
Meanwhile i could 'partly' compile ICS by using koljas configuration files. But i have to say, that i removed some libraries for compilation because i couldn't find solutions to successfully compile them. First 'goal' should be to have an image which boots. So we have a start. Compilation; without the 'error' libraries; completely succeeded here now. But creation of a first otapackage failed. This is my actual response of 'make otapackage'. I alreday tried to google this problem, but couldn't find a solution..
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.1
TARGET_PRODUCT=cooper
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv5te-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=ITL41D
============================================
build/core/main.mk:324: implicitly installing apns-conf_sdk.xml
No private recovery resources for TARGET_DEVICE cooper
Package OTA: out/target/product/cooper/cooper-ota-eng.lagloose.zip
unzipping target target-files...
running: unzip -o -q out/target/product/cooper/obj/PACKAGING/target_files_intermediates/cooper-target_files-eng.lagloose.zip -d /tmp/targetfiles-8iaaXh
Traceback (most recent call last):
File "./build/tools/releasetools/ota_from_target_files", line 839, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/ota_from_target_files", line 791, in main
OPTIONS.info_dict = common.LoadInfoDict(input_zip)
File "/home/lagloose/WORKING_DIRECTORY/build/tools/releasetools/common.py", line 144, in LoadInfoDict
d["fstab"] = LoadRecoveryFSTab(zip)
File "/home/lagloose/WORKING_DIRECTORY/build/tools/releasetools/common.py", line 163, in LoadRecoveryFSTab
raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))
ValueError: malformed recovery.fstab line: "/boot bml boot NULL NULL NULL NULL"
make: *** [out/target/product/cooper/cooper-ota-eng.lagloose.zip] Fehler 1
Any ideas ?
thx, lagloose

Hi! I think that at the moment trying to make aosp from android 4 source waste of time! More wisely to try to build android 4 from sorce code with the changes cyanogenmod9)
I changed a few config files for cm9.
And build a lot of libs to lipng and dalvic
Can you help me with config files?
P.S. add armv6-vfp.mk from gingerbread to android_build/core/combo/arch/arm
P.P.S. configs will be on my github's account tomorrow

Axel2033 said:
Hi! I think that at the moment trying to make aosp from android 4 source waste of time! More wisely to try to build android 4 from sorce code with the changes cyanogenmod9)
I changed a few config files for cm9.
And build a lot of libs to lipng and dalvic
Can you help me with config files?
P.S. add armv6-vfp.mk from gingerbread to android_build/core/combo/arch/arm
P.P.S. configs will be on my github's account tomorrow
Click to expand...
Click to collapse
Sounds good...
leave a message here when you're files are at github...

Did you install all the required packages ?
Sent from my GT-S5830 using XDA App

EmoBoiix3 said:
Did you install all the required packages ?
Sent from my GT-S5830 using XDA App
Click to expand...
Click to collapse
Yep. I think it is a more a problem with the config files. Anyway, i will follow Axels idea, and give a try to the Cyanogen Sources ...
Sent from my GT-S5830 using Tapatalk

lagloose said:
Yep. I think it is a more a problem with the config files. Anyway, i will follow Axels idea, and give a try to the Cyanogen Sources ...
Sent from my GT-S5830 using Tapatalk
Click to expand...
Click to collapse
To think the AOSP sync is such an ass .
Sent from my GT-S5830 using XDA App

I dont know much about python, but looking at the stacktrace the problem is in main(sys.argv[1:]), of course you know that, mind checking that line "File "./build/tools/releasetools/ota_from_target_files", line 839"
When you set this line TARGET_PRODUCT=cooper, does it try to config the files for it? Just trying to help here.

traduz said:
I dont know much about python, but looking at the stacktrace the problem is in main(sys.argv[1:]), of course you know that, mind checking that line "File "./build/tools/releasetools/ota_from_target_files", line 839"
When you set this line TARGET_PRODUCT=cooper, does it try to config the files for it? Just trying to help here.
Click to expand...
Click to collapse
Thanx for reply....
i already found the problem. The file 'recovery.fstab' was malformed...
Generally it seems to me, that Kolja took the Config from ZTE Blade and changed only the most important things. But as i alreday said, i'll stop now on AOSP and try the Canogenmod Sources. They are almost updated hourly at the moment.
PS: It would be nice, if all people who tried to compile ICS for our device could give a short information on how far they already got...
Greetz, lagloose

Hi.
First of all i would not consider myself noob and i would like to help out, but right now i have no idea where to start. any pointers or howtos to get started? would love to see ICS on ace

What stage of the development are u guys at and what problems are u currently facing?

lagloose said:
Thanx for reply....
i already found the problem. The file 'recovery.fstab' was malformed...
Generally it seems to me, that Kolja took the Config from ZTE Blade and changed only the most important things. But as i alreday said, i'll stop now on AOSP and try the Canogenmod Sources. They are almost updated hourly at the moment.
PS: It would be nice, if all people who tried to compile ICS for our device could give a short information on how far they already got...
Greetz, lagloose
Click to expand...
Click to collapse
You can use my android_device_samsung_cooper
http://github.com/EmoBoiix3/android_device_samsung_cooper
Sent from my GT-S5830 using XDA App

I'm sorry I was very busy(
Today will be config on git)

making a fork... if you have a site to make documentation should be great!

https://github.com/axel2033/device_cooper_cm9

Thanks for sharing... I'm busy this Weekend. So can't do anything before Monday....
Sent from my GT-S5830 using Tapatalk

Updated coolya kernel https://github.com/teamhacksung/android_kernel_samsung_msm/tree/merge

Good luck for the dev's.I will help for testing , debugging and bug reporting.

Axel2033 said:
https://github.com/axel2033/device_cooper_cm9
Click to expand...
Click to collapse
Great, now we have 3 devs working for it

Great to see work in progress, stares at github with confused look
Sent from my GT-S5830 using xda premium

Guys, please stop posting here except you are a developer or know how to help ...
Sent from my GT-S5830 using XDA App

[GUIDE] How to port AOSP ICS roms to your Device

How to port any ICS AOSP based roms to your Device (AOKP, CM9 & many other)
- for best compatibilty
--> use same android versions. (4.0.4 -> 4.0.4 example)
--> use latest base from CM9 (is best choose for port) or any AOSPbased ICS ROM
--> use each brand for port (mean Desire HD -> Desire S or other HTC devices). you also can port other roms, but you will have issues.
PORT:
-> download latest cm9 base and extract it
-> download target rom and extract it
for Camera
use Camera.apk from base rom for camera issues fix.
Click to expand...
Click to collapse
copy
/app
/framework
/media
/fonts folders and replace in cm9 folder.
repack your zip and let it boot.
if it doesn't boot then copy /system/lib/libandroid_runtime.so from target rom and repack your rom.zip and install again.. if you get bootloop anyway, then just type in adb "adb logcat" and share it with us in this thread..
if you dont get success dont cry, just try to port another rom you can not port all roms
for HTC Devices
to fix network auto select,
decompile framework-res.apk
go to \framework-res\res\values\bools.xml change
<bool name="skip_restoring_network_selection">true</bool>
to false.
Click to expand...
Click to collapse
to fix graphichal issues,
decompile framework.jar
change these files with cm9 base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
Click to expand...
Click to collapse
Click to expand...
Click to collapse
enjoy!
if you like this guide, just give 5 stars to thread and click thanks button

hi, there, and i own a huawei u8800, we allready have a aosp ics 4.0.4 aurora room but i would like to have cm9 or aokp into our phone. in this case based is aosp ics aurora and ported will be cm9 or aokp for example? i´m right?
maybe is better port cm9 from desire z to my huawei u8800, since they have the same cpu and gpu.
dont want tou build a rom, just port.
please i need help. thanks anyway.

lol be thankful you have an ICS rom.. Huawei X6 users like me are trying our best to port from u8860's ICS.
I'd like to ask if the method works for a device that does not have official ICS? i.e. porting an ICS rom to official GB?
Kindly advise sir, and thanks again!

I get the same that in miui v4... boot loop and adb says no device

I get AtCmdFwd error.

Could you post the link of latest cm9 base?

im getting stuck in a bootloop...
INFO:
Device-Samsung Infuse
CM9 Base being used to port- http://forum.xda-developers.com/showthread.php?t=1601844
Rom trying to port- http://www.slimroms.com/ (the i9000 version aka galaxy s)
What i did:
1) opened cm9 base with 7zip, deleted app, framework, fonts, media folders
2) replaced deleted folders with app, framework, fonts and media folders from slim ics base 3.6
3) opened up slim ics 3.6 i9000 essentials with 7zip
4)navigated to app folder and moved apks files from ther to the cm9 base - did the same with framework, fonts, and media folders (I did not just copy the folders this time! i only copied the files inside the folders)
5) put zip on sdcard
6) rebooted and started log cat
any help would be apreciated if i dont answer back right away its because i have to pick my sister up from school
Here are the logcats: (All are the same logcat...but two of them are filtered)

I think I kniw what the problem is...gonna attemot a fix after dinner
EDIT i got out of the boot loops and booted into my portes slimics...now to fix the bugs...there is ALOT
thanks for the guide will def give you some credit once i get this stable...may be getting some help from another dev

So as long as the base and ported roms are from the same manufacturer, this will work?
Sent from my LG-E739 using Tapatalk 2

how to port aosp ics to cm9?

good guide
You can add
Copy etc\cron
And etc\init.d files to run RomControl fix

Am stuck at logo screen.
Can't get logcat because ADB can't find my device.
What to do?
Sent from my LG-E739 using Tapatalk 2

mg2195 said:
I think I kniw what the problem is...gonna attemot a fix after dinner
EDIT i got out of the boot loops and booted into my portes slimics...now to fix the bugs...there is ALOT
thanks for the guide will def give you some credit once i get this stable...may be getting some help from another dev
Click to expand...
Click to collapse
Can you please tell what was the problem and how did you fixed? Thanks.

medicjunKie said:
So as long as the base and ported roms are from the same manufacturer, this will work?
Sent from my LG-E739 using Tapatalk 2
Click to expand...
Click to collapse
It would be sane screen res e.g HDPI to HDPI
And also the same processor type too helps
Sent from my LT15i using xda premium

see i hve a question...., what does base mean? does it mean the ics rom which i hve for my device already ported or any ics rom available for my device's manufacturer?
like my phone is samsung galaxy 3....so shud the base be the rom which is available for my g3 or it can be any ics rom like say ics rom for samsung galax s?
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
i m seriously cponfused with that part..... m not gettin g what the base and the rom to be ported shud be?

My logcat ...?? what can i do? http://www.embedupload.com/?d=4HKCKXGIK2

I'm trying to port slimICS and it gets stuck at boot. Here's my logcat if it helps.
http://logcat.miui.us/893012

Zorua said:
I'm trying to port slimICS and it gets stuck at boot. Here's my logcat if it helps.
http://logcat.miui.us/893012
Click to expand...
Click to collapse
see here
Code:
169: E/dalvikvm( 1190): ERROR: couldn't find native method
170:
171: E/dalvikvm( 1190): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimation:(I)V
172:
173: E/JNIHelp ( 1190): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
baksmali classes.dex of services.jar
find PowerManagerService.smali file in the path com/android/server
add line
Code:
.method private native nativeStartSurfaceFlingerOffAnimation(I)V
.end method

tathanhlam66 said:
see here
Code:
169: E/dalvikvm( 1190): ERROR: couldn't find native method
170:
171: E/dalvikvm( 1190): Requested: Lcom/android/server/PowerManagerService;.nativeStartSurfaceFlingerOffAnimation:(I)V
172:
173: E/JNIHelp ( 1190): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
baksmali classes.dex of services.jar
find PowerManagerService.smali file in the path com/android/server
add line
Code:
.method private native nativeStartSurfaceFlingerOffAnimation(I)V
.end method
Click to expand...
Click to collapse
I don't have the folder com/android/server/. What am I doing wrong?
EDIT: Wow, I sound so stupid. Nvm, I did that edit. I had to look up smali and baksmali guides. I'll flash it and see if it boots.
Okay, still refusing to boot.
New logcat: http://logcat.miui.us/894002
EDIT 2: Booted but storage isn't working.
Logcat: http://logcat.miui.us/889025

Zorua said:
EDIT 2: Booted but storage isn't working.
Logcat: http://logcat.miui.us/889025
Click to expand...
Click to collapse
Try decompiling the framework-res.apk and change the storage-list.xml in the xml folder.

Porting of custom rom.

anyone know how to port a rom to another custom rom.?
ex. MiUi based on GDX or MiniCM7 and etc
LeWaOS based on GDX or MiniCM7 and etc
JoyOS based on GDX or MiniCM7 etc
Click to expand...
Click to collapse
i tried to port JoyOS to GDX but it didnt success, it stuck at bootlogo
but when i try to port JoyOS to Cm7 rom by FXP. i got luck and it works
but i think Cm7 rom by FXP have a lots of bugs and its laggy.
i want to try porting in GDX or MiniCM7 or in other rom.
i hope someone can teach me how to do it

Well you can give up on GDX cuz I doubt Team DX will allow you to base their work for your own ports...as for MiniCM7, I think you may have better luck...

The same way you ported it to fxp's cm7 you can port it to miniCM.they are the same base roms.GDX is based on hero gingerbread,so porting other roms to it is a little bit harder and complicated.

RohinZaraki said:
Well you can give up on GDX cuz I doubt Team DX will allow you to base their work for your own ports...as for MiniCM7, I think you may have better luck...
Click to expand...
Click to collapse
really? in MiniCM7 it works? well i will try it now.
and its MiniCM7? so i will use nAa kernel? right?

Yeah, nAa and alfs cm7 version will be ok

D3HuM4NiZ3D said:
The same way you ported it to fxp's cm7 you can port it to miniCM.they are the same base roms.GDX is based on hero gingerbread,so porting other roms to it is a little bit harder and complicated.
Click to expand...
Click to collapse
i see, thanks for the information. i will give feedback if i got seuccess porting with MiniCm7
EDIT: after a few minutes, i didnt got luck. stuck at bootlogo and darker lcd

Take a logcat

RohinZaraki said:
Take a logcat
Click to expand...
Click to collapse
how?

Turn off the phone, open command prompt and type
adb logcat > logcat.txt
on your phone and attach the usb cable and save the .txt file
OR​
http://www.mediafire.com/?p98pd2i9d1c3d71
Download that, connect your phone via USB, on the phone, hit the refresh button for the program like crazy till it reads your phone, go to the logcat section and observe the processes, especially when it bootloops...there should be commands written in RED....save the logcat and post it here

RohinZaraki said:
Turn off the phone, open command prompt and type
adb logcat > logcat.txt
on your phone and attach the usb cable and save the .txt file
OR​
http://www.mediafire.com/?p98pd2i9d1c3d71
Download that, connect your phone via USB, on the phone, hit the refresh button for the program like crazy till it reads your phone, go to the logcat section and observe the processes, especially when it bootloops...there should be commands written in RED....save the logcat and post it here
Click to expand...
Click to collapse
is this the logcat? i dont have any idea

from what i've read, this line seems to be the prob
18:20:03.368 Error Zygote 1752 Error preloading android.media.AmrInputStream.
18:20:03.368 Error Zygote 1752 java.lang.ExceptionInInitializerError
18:20:03.368 Error Zygote 1752 at java.lang.Class.classForName(Native Method)
18:20:03.368 Error Zygote 1752 at java.lang.Class.forName(Class.java:234)
18:20:03.368 Error Zygote 1752 at java.lang.Class.forName(Class.java:181)
18:20:03.368 Error Zygote 1752 at com.android.internal.os.ZygoteInit.preloadClasses(ZygoteInit.java:315)
18:20:03.368 Error Zygote 1752 at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:589)
18:20:03.368 Error Zygote 1752 at dalvik.system.NativeStart.main(Native Method)
18:20:03.368 Error Zygote 1752 Caused by: java.lang.UnsatisfiedLinkError: unknown failure
18:20:03.368 Error Zygote 1752 at java.lang.Runtime.loadLibrary(Runtime.java:455)
18:20:03.368 Error Zygote 1752 at java.lang.System.loadLibrary(System.java:554)
18:20:03.368 Error Zygote 1752 at android.media.AmrInputStream.<clinit>(AmrInputStream.java:33)
18:20:03.368 Error Zygote 1752 ... 6 more
i have honestly no idea what it means...best person to ask is pilu1987

how about this one sir?

zygote is not running.....well zygote is the thing that kinda speeds up your system....it is the main diff between running a rom on emulator and android hardware....zygote is the basic thing which should be running for successful port...u have done some serious error...like messed up init* files.....zygote is the main diff between an android and ios...its the only reason why android is faster than ios(technically)
in short zygote is boot...
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
check whats written in under 1752....repair it....then should be fine...
1752 is the process that is causing bugs...

Rahat34 said:
zygote is not running.....well zygote is the thing that kinda speeds up your system....it the main diff between running a rom at terminal emulator and android hardware....zygote is the basic thing which should be up and running for successful port...u have done some serious error...like messed up init* files.....zygote is the main diff between an android and ios...its the only reason why android is faster than ios(technically)
in short zygote is boot...
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
check whats written in under 1752....repair it....then should be fine...
1752 is the process that is causing bugs...
Click to expand...
Click to collapse
What is the best thing that i can do to fix it and boot properly?
Anyway thanks sir rahat for your response
Sent from my E15i using xda premium

any one who know how to fix the ff
headset
video recorder
sound recorder
thanks in advance.

karlo0321 said:
any one who know how to fix the ff
headset
video recorder
sound recorder
thanks in advance.
Click to expand...
Click to collapse
Of what ROM?
LewaOS, JoyOS, or MIUI?
Sent From My W8 Using Tapatalk

Haha, you think porting is that easy?
Sent from my X8 using XDA

lucastan96 said:
Of what ROM?
LewaOS, JoyOS, or MIUI?
Sent From My W8 Using Tapatalk
Click to expand...
Click to collapse
JoyOS sir lucastan.

Let me guess, you used LewaOS porting guide for porting JoyOS, right?
Sent From My W8 Using Tapatalk

lucastan96 said:
Let me guess, you used LewaOS porting guide for porting JoyOS, right?
Sent From My W8 Using Tapatalk
Click to expand...
Click to collapse
yes i used it, any problem by using that sir?
can you help me to figure out this problems?

[Q] I337M kitchen troubles..

Hello good people of XDA I just cant seem to make a ROM
using @dsixda 's Android Kitchen for my I337M!
I had the kitchen working for my S3,
Tried with S4 and it wouldn't boot up.
Restored my entire computer, fresh
installed the kitchen / cygwin.
Tried again, same results.. No booty.
Used another 'updater-script'.. No booty.
I have searched and searched, tried everything
I can, but nothing works, none of my ROMs boot.
Was hoping someone here might have an idea of
what I am doing wrong?

Bump for some help..

I second that
Adizzzle said:
Bump for some help..
Click to expand...
Click to collapse
wheres the i337m love

The French Tickl3r said:
wheres the i337m love
Click to expand...
Click to collapse
I have no idea I guess I'll try using VB on my windows comp and try to install Ubuntu inside of windows.
Im eager to start building ROMs!
Does the Android kitchen work for you by chance?

I finally got cygwin and the kitchen running ( got a missing "clear" error, ended up downloading literally evry available package, took like 5 hours)
So then I got myself a copy of the stock rom on 4.4.2 , tried importing it into the kitchen and got some sort of error saying missing zip..
My goal is to cook a pre rooted, knox free stock version of the rom.
Sent from my SGH-I337M using xda app-developers app

The French Tickl3r said:
I finally got cygwin and the kitchen running ( got a missing "clear" error, ended up downloading literally evry available package, took like 5 hours)
So then I got myself a copy of the stock rom on 4.4.2 , tried importing it into the kitchen and got some sort of error saying missing zip..
My goal is to cook a pre rooted, knox free stock version of the rom.
Sent from my SGH-I337M using xda app-developers app
Click to expand...
Click to collapse
Thats odd, I get no errors when building / setting up working folder
just when I flash the ROM it ALWAYS bootloops on me..
Dang, the other S4 variants work just fine. :crying:

So thanks to @The Sickness I have found out that the kitchen
leaves needless commands in the updater-script, and in order
for me to get the ROM booting I had to remove those commands
and flash a kernel with my ROM. It finally booted!!!
However after flashing my ROM - VLUFNC1 + KT kernel
I loose Mobile Data and Wifi is inaccessible which I am
assuming is due to the kernel.
Finally making progress..

I too have got the kitchen up and running for the i337m. I posted my progress here but i havent went ahead and actually tried to flash it.. reason being im not sure I actually want to up grade to 442.. so comfortably numb with 422 (debloated and with wanam xposed framework)
one thing i noticed and I was not expecting is the absurd storage space cooking roms takes from my computer..
in any case, thanks for posting your progress, Ive been stalking this thread bc he was supposed to cook a Samsung I337M - STOCK VLUFNC1, with 4 way reboot, modded systemUI, rooted, deodexed and free of that insidious knox, but It seems the project might have been abandoned, as the thread is now closed..

Just wondering what you had to remove in updater script because i was having the same issue ? thanks
Adizzzle said:
So thanks to @The Sickness I have found out that the kitchen
leaves needless commands in the updater-script, and in order
for me to get the ROM booting I had to remove those commands
and flash a kernel with my ROM. It finally booted!!!
However after flashing my ROM - VLUFNC1 + KT kernel
I loose Mobile Data and Wifi is inaccessible which I am
assuming is due to the kernel.
Finally making progress..
Click to expand...
Click to collapse

radeonddr said:
Just wondering what you had to remove in updater script because i was having the same issue ? thanks
Click to expand...
Click to collapse
I had to delete the following and switch the boot.img:
package_extract_file("flash_image", "/tmp/flash_image");
set_perm(0, 0, 0777, "/tmp/flash_image");
assert(package_extract_file("modem.bin", "/tmp/modem.bin"),
run_program("/tmp/flash_image", "/dev/block/mmcblk0p2", "/tmp/modem.bin"),
delete("/tmp/modem.bin"));
delete("/tmp/flash_image");;
Click to expand...
Click to collapse