FORUMS
Remove All Ads from XDA

[KITCHEN] Raphael Kitchen (From JugglerLKR and JCEspi2005)

2,375 posts
Thanks Meter: 190
 
By jcespi2005, Senior Member on 25th July 2008, 10:39 AM
Post Reply Email Thread
9th November 2008, 10:42 PM |#101  
mrvanx's Avatar
Retired Moderator
Flag York
Thanks Meter: 59
 
More
Its a mismatch issue with the XIP and SYS you are running probably. What build versions are you using?

EDIT:: to elaborate on that gwes.exe has had some problems before that results in the apps behaving rather odd (only using the QVGA portion of the screen, large menus etc...) certain ones have this issue, the majority dont.
 
 
9th November 2008, 10:47 PM |#102  
jcespi2005's Avatar
OP Senior Member
Flag Madrid
Thanks Meter: 190
 
Donate to Me
More
Quote:
Originally Posted by karloe

A qvga program on a vga screen, my guess

Quote:
Originally Posted by AssassinsLament

Ok, for some odd reason, I am now getting the 1/4th Screen Bug too. I had been fine the past few days using your 62 kitchen, but then tonight for some odd reason, I started getting the 1/4h screen bug. I was afraid it was my device but flashing a different custom rom was fine. Also seeing that someone else had already described the bug, eased my mind. Any ideas?

Quote:
Originally Posted by mrvanx

Its a mismatch issue with the XIP and SYS you are running probably. What build versions are you using?

EDIT:: to elaborate on that gwes.exe has had some problems before that results in the apps behaving rather odd (only using the QVGA portion of the screen, large menus etc...) certain ones have this issue, the majority dont.

You are right, mrvanx... remember read something about this issue on this thread http://forum.xda-developers.com/showthread.php?t=438676

Special in this part

Quote:

IMP: There may be chances that although the XIP is working fine, but the windows are seen as QVGA versions. The solution to that is either of the below
XIP & SYS of the same builds or
XIP and the OS\Gwes.exe and \Base_Lang_0XXX\Gwes.exe.0xxx.mui files from same build

Cheers
10th November 2008, 08:29 AM |#103  
Inactive Recognized Developer
Flag Twin Cities
Thanks Meter: 631
 
Donate to Me
More
Ok thanks mrvanx and jcespi2005, that makes sense.
10th November 2008, 10:24 AM |#104  
Member
Thanks Meter: 0
 
More
Can anybody confirm this?

(think I) finally understand...

- Extract the .raw files from my device.
- Use "Raphael_ROM_Kitchen_v0.62" to extract a shipped RUU_Signed.NBH.
- Mess with the OEM part of the shipped ROM to add or remove auto-installed programs etc.
- Use "Raphael_ROM_Kitchen_v0.62" to cook the adjusted extracted RUU_Signed.NBH OEM file AND my original Part01.raw and Part02.raw into a new .NBH file.
- Replace the original RUU_Signed.NBH from the shipped ROM with my new .NBH file.
- Flash my device.
10th November 2008, 09:33 PM |#105  
Senior Member
Flag The Hague
Thanks Meter: 6
 
More
A little help with the Kitchen, I'm still trying to port the BlackStone XIP which I think I did right, but still not booting It displays the radio information but doesn't go from there (first one I did didn't even show the radio so I know I'm making progress ) Can anybody confirm my observations?

- Kichen deletes files on SYS:

del OEM\OEMXIPKernel\*.* /q /s
del OEM\Langdb\*.* /q /s
del SYS\MSXIPKernel\*.* /q /s
del SYS\MSXIPKernelLTK\*.* /q /s
del SYS\WinCENLS_WWE\*.* /q /s

which are actually files from the XIP. So, that means files from XIP (packed in OS.NB in ROM directory) are being used. So:

- to actually port a ROM to another device, you need to port the XIP and SYS from the same build (?)


Also, what's the actual basic workflow on porting? I'm thinking:

- port XIP, boot and test
- if working, port SYS, boot and test
- if working, delete OEM packages, boot and test
- if working, do the special tweaks, boot and test
11th November 2008, 02:42 AM |#106  
Retired Moderator
Flag Aiur
Thanks Meter: 2
 
More
Quote:
Originally Posted by jcespi2005

Read the TXT file inside to get the pass.

Waiting your feedback, guys.... thanks...

Cheers.


jcespi2000... umm i don't know bro if i'm missing it but how can i read the txt file without unraring the rar?? as soon as i start to extract the rar it asks me for the password and i'm sorry if i am acting blind but i didn't see it in the first or 2nd post.

thanks for help.
11th November 2008, 06:41 AM |#107  
Senior Member
Flag The Hague
Thanks Meter: 6
 
More
Quote:
Originally Posted by thesire

jcespi2000... umm i don't know bro if i'm missing it but how can i read the txt file without unraring the rar?? as soon as i start to extract the rar it asks me for the password and i'm sorry if i am acting blind but i didn't see it in the first or 2nd post.

thanks for help.

txt file doesn't need the pass, you can double-click it and it will extrract Not the Kitchen though
11th November 2008, 12:16 PM |#108  
Retired Moderator
Flag Aiur
Thanks Meter: 2
 
More
Quote:
Originally Posted by pfcsabre

txt file doesn't need the pass, you can double-click it and it will extrract Not the Kitchen though

thats my problem... winrar won't even extract the txt file as soon as it encounters the password protected kitchen executable. it just creates a empty folder.
11th November 2008, 12:34 PM |#109  
jcespi2005's Avatar
OP Senior Member
Flag Madrid
Thanks Meter: 190
 
Donate to Me
More
Quote:
Originally Posted by pfcsabre

A little help with the Kitchen, I'm still trying to port the BlackStone XIP which I think I did right, but still not booting It displays the radio information but doesn't go from there (first one I did didn't even show the radio so I know I'm making progress ) Can anybody confirm my observations?

- Kichen deletes files on SYS:

del OEM\OEMXIPKernel\*.* /q /s
del OEM\Langdb\*.* /q /s
del SYS\MSXIPKernel\*.* /q /s
del SYS\MSXIPKernelLTK\*.* /q /s
del SYS\WinCENLS_WWE\*.* /q /s

which are actually files from the XIP. So, that means files from XIP (packed in OS.NB in ROM directory) are being used. So:

- to actually port a ROM to another device, you need to port the XIP and SYS from the same build (?)

Also, what's the actual basic workflow on porting? I'm thinking:

- port XIP, boot and test
- if working, port SYS, boot and test
- if working, delete OEM packages, boot and test
- if working, do the special tweaks, boot and test

For porting the XIP (and relationship with SYS) take a look to this thread http://forum.xda-developers.com/showthread.php?t=438676

Great tutorial by ababrekar and other great guys helping in XIP porting....

Cheers
11th November 2008, 02:35 PM |#110  
Senior Member
Flag The Hague
Thanks Meter: 6
 
More
Quote:
Originally Posted by jcespi2005

For porting the XIP (and relationship with SYS) take a look to this thread http://forum.xda-developers.com/showthread.php?t=438676

Great tutorial by ababrekar and other great guys helping in XIP porting....

Cheers

LOL I'm actually following that one But for the workflow..?
11th November 2008, 04:38 PM |#111  
jcespi2005's Avatar
OP Senior Member
Flag Madrid
Thanks Meter: 190
 
Donate to Me
More
Quote:
Originally Posted by pfcsabre

LOL I'm actually following that one But for the workflow..?

mmmm

- port XIP, boot and test
- if working, port SYS, boot and test
- if working, delete OEM packages, boot and test
- if working, do the special tweaks, boot and test

I beleave you can't port only the XIP, cause XIP/SYS are related, and at least you need some files from SYS be ported with the XIP...

Quote:

IMP: There may be chances that although the XIP is working fine, but the windows are seen as QVGA versions. The solution to that is either of the below
XIP & SYS of the same builds or
XIP and the OS\Gwes.exe and \Base_Lang_0XXX\Gwes.exe.0xxx.mui files from same build

Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes