Related
Before i get flammed like crazy. I have searched for guides to cooking roms and used all different kinds of kitchens but none seem to work at all. Unless there is something written between the lines that i can't see i just don't think i'm doing anything wrong.
Anyway. When I try an build a rom and create the os-new.nb file imgfsfromdump just crashes and i can't create the file. Sometimes it works but once it fails it doesn't start working for a long time. I'm not sure what i'm doing. I try and dumb a stock rom and rebuild exactly the same but the same thing happens.
If anyone with some xip|sys porting could give me a hand to get past this step i'd appreciate it.
Thanks..
I'm starting to believe it might be a conflict with SP3. Can anyone confirm that they have these kitchens working with SP3?
replace your ImgfsFromDump with the attached version
itje said:
replace your ImgfsFromDump with the attached version
Click to expand...
Click to collapse
Thanks itje. I tried this but it still crashes everytime i try and compile the files. I'm not sure why. Is there something i could be doing wrong? Have you seen this before?
Did ImgfsFromDump ever work for you? (That is, did you try just extract and create the image without modify any content)
For me, I am not following the script in the kitchen completely to create the image. Here is what I execute on the temp directory (w/ dump as sub-directory) and work fine so far. (just make sure you did not remove the imgfs.bin and the payload in extracting the image)
..\TOOLS\ImgfsFromDump imgfs.bin imgfs-new.bin
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb.payload
..\TOOLS\NBMerge -kaiser os-new.nb
Strangly enough it did work a couple of times then i just started getting that error that says "imgfsfromdump needs to close" that basic windows error. I thought it might have been DEP but i made a exception for that program. I'm going to try this and see if i have the same problems.
I'M SUCH AND IDIOT!!! The reason it was crashing is cause i kept building the dump into packages. So i assume it was looking for files in the wrong place which just causes the process to fail. Thanks guys!!!
Can someone help me find this 21109 build to where i can actuallyt port it? I've tried to extract it from various roms and all it does is fail everytime and my phone is stuck at the sony screen.
*******EDIT******
I finally figured out how to get XIP ported but now i'm having a problem with the SYS folder. No matter what SYS folder i use and no matter how many different tutorials i go through i still get the same point. I flash and it sits at the sony ericisson symbol and does nothing. Is there some folders i shouldn't change in the SYS?
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
itje said:
run g'reloc on the stock sys folder from x1, note all the values..
then run g'reloc on your new UNTOUCHED sys, where you change NOTHING...no swapping of files (unless you port from vga or qvga, or change locale, but thats another story) then change the values on the new sys with the values from the stock x1 sys, apply changes, and you have ported the sys.
cheers
Click to expand...
Click to collapse
When i run g reloc i get the same values as i did with the original build. Let me see if i understand the file hierarchy correctly.
1. I run G'reloc where i have my stock ROM's SYS folde. (note those values)
2. then i run G'reloc where my Donor SYS folder with the rest of the crap from the Donor ROM.
3.Then i copy the Donor SYS folder into the location i have my stock ROM SYS folder and overwrite. I run G'reloc again if the information is different from the first time i ran g'reloc i change it and hit do it.
Is this what i should be doing? I do this and i get the same result no matter which ROM i try and port from. I am porting from a touch pro ROM so is there anything i would need to change due to the vga to wvga switch?
swap from the modules marked with red to blue
base_dpi_192_resh_480_resv_640
to
base_dpi_192_resh_480_resv_800
since our device is WVGA you need to have the value set to 800 instead og 640.
So swap the folders with 640 from donor rom to the ones from either blackstone or x1
I can't get anything to work... If i extract the xip from this 21109 build that i have and try an use xipporterex to create the new xip and write it into the os.nb.payload and then merge the files. If i take that os.nb that is created i can build that and it will boot but if i try use the rom build procedure where it makes the os-new.nb file it will never boot. Even if i do nothing but just extract and rebuild the rom will not boot. From this i assume that i'm doing something wrong, 21109 build is corrupted or both. I'm not this inept. This shouldn't be giving me this much trouble with all these tutorials. Can someone please help me out with the exact procedure they use when building an X1 rom with porting over a new build?
I am currently trying to port the sys 21728 of a wm 6.5 rom to my Karmba kitchen. I used 2 diffrent wikis:
http://forum.xda-developers.com/showthread.php?t=389772
http://forum.xda-developers.com/showthread.php?t=437264
Boths ways do not work. After flashing the device does not boot and stops at the radio screen. The WinCENLS_WWE is in the xip folder.
- dnsapi.dll I deleted from the "OS" folder, cause it is also in the "OEMDriver" folder.
- taskmrg.exe I deleted from the "Shell" folder, cause it is also in the "OEM" folder.
The xip is ported to 21728 and seems to work...the device works with the old sys.
Any ideas?
really no idea?
Try the newer ervius kitchen posted here, already updated to 21812
http://forum.xda-developers.com/showthread.php?t=515824
So I am doing my homework and learning how to make my own SYS and ROM folders for the visual kitchen. Got the SYS down. I just have a question about the ROM. I know the shared folder is the OS version specific files so that is where I put the MSXIPKernel and xip.bin from the new build that I download. For the Kovsky folder, do I just copy it from another build version since this is the device specific portion?
Hello everybody,
I need some help with porting Blackstone Stock Rom Europe 1.56 to Leo Stock Rom 1.43.479.2.
I'm using Ervius Visual Kitchen 1.8.1. The problem appears when i'm trying to port the sys folder.
I did the following:
I made 2 kitchens donor and blackstone. I extracted .nbh files in both kitchen using "Dump NBH/NB/Payload" option.
I copyed folder 21864 from donor ext\LEO\21864 to blackstone kitchen in ext\BlackStone\21864 and selected in ervius kitchen this ext version. I build the rom and it boots up ok...
After this I moved the sys folder from donor kitchen sys\21864 to blackstone kitchen sys\21864.
I ported also xip.bin by copying xip.bin from donor kitchen ROM\xip.bin to blackstone Tools\xip.bin_new then i pressed "Xipporterex & ROM". I checked "Is an AKU 5..." unchecked "Execute Cert Patch", "Execute PP Patcher" and "Change PP to 16 Mb". I clicked on Port It, all went ok. Then i clicked "Find first..." then "Write it". No error. Then "Rom Tools" -> Write & Done.
Then i tried to create rom again selecting all system xip and ext vs 21864. All went Ok but the phone doesn't boot.
What i did wrong. Please help.
Hi fiftyz,
Use this "OEMXipKernel.zip" in attachment as replacement for yours, it's changed to handle 6.5.
If you don't use it, you must recmod several files/folders in the SYS folder.
Better you do some search and reading
sparkienl said:
Hi fiftyz,
Use this "OEMXipKernel.zip" in attachment as replacement for yours, it's changed to handle 6.5.
If you don't use it, you must recmod several files/folders in the SYS folder.
Better you do some search and reading
Click to expand...
Click to collapse
Thank you! I'll try this way.
I did a lot of research before posting here... Maybe i didn't see that part... Sorry and thank's again. I tought that option "Is AKU 5..." from ervius kitchen will solve that part because it creates that folder when porting xip.
I'll post if it is working.
Did you have success with the solution provided by sparkienl?
I tried to build a ROM the same way as you but with also with the same result -> no boot.
I tried also to build up a ROM with the fix from sparkienl, but I got an error in the ervius kitchen during the build phase.
Does anyone have other suggestions?
Did you check the option "real WM6.5 AKU" ?
Yes, I did.
At what point does the ROM stop booting?
maybe is Notification_Enhancement ,I change it with Notification_Enhancement 3_0_1919_3829
EpiphanyNL said:
At what point does the ROM stop booting?
Click to expand...
Click to collapse
it stops on the "smart mobility" screen, before the information (radio, rom, ...) in the right lower corner appears.
You didnt port you XIP correctly
I have been trying to cook a rom using
23xxx sys and rhodium/topaz packages but then I compile I get the error that
tahomabd.ttf already exists.
I have tried to remove all the respective OEM packages one at a time but still get the error. Is it possible that the sys build generates the same file twice?
Euroman28 said:
I have been trying to cook a rom using
23xxx sys and rhodium/topaz packages but then I compile I get the error that
tahomabd.ttf already exists.
I have tried to remove all the respective OEM packages one at a time but still get the error. Is it possible that the sys build generates the same file twice?
Click to expand...
Click to collapse
Try to search for tahomabd.ttf in your kitchen directory, and i`m sure u`ll find more than one.
The slution is - delete one of them
The trick is there the file doesn't exists in the SYS only a lot of DSM files.
Does there exists a way to run a logfile of buildOS?
Euroman28 said:
The trick is there the file doesn't exists in the SYS only a lot of DSM files.
Click to expand...
Click to collapse
Check folders
SYS\COMPLEXSCRIPT_FONTS
SYS\SYSTEM_DEFAULT_FONTS
linshius said:
Check folders
SYS\COMPLEXSCRIPT_FONTS
SYS\SYSTEM_DEFAULT_FONTS
Click to expand...
Click to collapse
Is complex scripted fronts a hidden folder?