I have a little question im trying to get the answer to.
Im pretty familiar with xipport tools and all that, I have ported xip for my old device many times (Herald)
But what I just cant get the hang of is how to use it in kitchens available for polaris.
Im currently working on a little project of making my own kitchen, but I need to learn more on how to build the ported xip into the rom in polaris.
There are many great tutorials on xip porting, but most of them lacks the info I need to make it work for our device (polaris), well maybe I didnt find the correct one...
I have used swtos's kitchen witch can port certain builds (thx for that info swtos) but I need to know why it can only port certain builds, and how to use it (or make my own) to port xip from any builds.
Help here would be greatly appreciated
cheers
Extract XIP.bin from any rom you like.
PUT MSXIPKERNEL files and modules into \sys folder.
Put WINCENLS folder into \sys
Put os.nb from source rom into your ROM directory ,
make a cook ,
You 're ready
or you can remake xip.out file and port it directly into os.nb.payload, but
port address may vary ...
Hello,
when I put os.nb from kaiser ROM, I have a black screen just after splash.
any idea?
M-Amine said:
Hello,
when I put os.nb from kaiser ROM, I have a black screen just after splash.
any idea?
Click to expand...
Click to collapse
yeah thats the problem im encountering too
but u need to put os.nb.payload
swtos said:
Extract XIP.bin from any rom you like.
PUT MSXIPKERNEL files and modules into \sys folder.
Put WINCENLS folder into \sys
Put os.nb from source rom into your ROM directory ,
make a cook ,
You 're ready
or you can remake xip.out file and port it directly into os.nb.payload, but
port address may vary ...
Click to expand...
Click to collapse
can u not use m'relloc to take care of adress?
You MUST use mreloc !! and greloc for other sys files ....
Ok but how to use it ? that's THE question !
Use an other rom that works fine with your ppc. Check every file with mreloc
and put addresses from this file to the new one. Repeat this procedure for
all files into msxipkernel.
For nk.exe use mreloc for nk . With this one , i don't know any guide.
Just try and repeat....
You don't need to port a XIP.
You don't need to port a XIP.
Just copy .ROM map from a working TC ROM and I copy metadata map too.
This is it!
allright
another question then
when i dump the xip with xipport
i get out folder
i do same with the new xip
i compare the folders in modules
in the new xip, i get more modules then I have in the original dumped
This is dumped old xip:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is dumped new xip:
do I not include those?
use another rom, not original, (e.g. any swtos roms)
and yes use those two files
NikMel said:
You don't need to port a XIP.
Just copy .ROM map from a working TC ROM and I copy metadata map too.
This is it!
Click to expand...
Click to collapse
Interesting.
Could you explain what those maps are ?
swtos said:
use another rom, not original, (e.g. any swtos roms)
and yes use those two files
Click to expand...
Click to collapse
what u mean by use another rom?
for os.nb.payload?
or do u mean i should port the new xip to a xip that comes from an unofficial rom, in.ex a xip u have in the kitchen?
Just take a look.
This is the original Diamond ROM on our TC.
I don't need to port any XIP just copy SYS\.ROM, SYS\.VM (not realy needed but you never know?!?!) map and SYS\Metadata from a working TC rom.
swtos said:
Interesting.
Could you explain what those maps are ?
Click to expand...
Click to collapse
use a xip from a not original rom . split os.nb, rommaster os.nb.payload, analyse xip. Use mreloc addresses from this xip.
NikMel said:
Just take a look.
This is the original Diamond ROM on our TC.
I don't need to port any XIP just copy SYS\.ROM, SYS\.VM (not realy needed but you never know?!?!) map and SYS\Metadata from a working TC rom.
Click to expand...
Click to collapse
Right !
swtos said:
use a xip from a not original rom . split os.nb, rommaster os.nb.payload, analyse xip. Use mreloc addresses from this xip.
Click to expand...
Click to collapse
allright, I will try that too.
But I used from original rom, and I used m'relloc and changed adresses, then put the new files in mxip folders in sys. And I used os.nb.payload from another build.
and it worked
swtos said:
Right !
Click to expand...
Click to collapse
Just try it and see how impressed you will be!
No problem. There are many ways to port xip , as you're already know
Good Night Guys !
swtos said:
No problem. There are many ways to port xip , as you're already know
Good Night Guys !
Click to expand...
Click to collapse
thx man for your help in this
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yet again a tool that makes something as easy and comfortable as it can be...this time it's:
NBH packing and unpacking
had some fun rev'ing the NBH fileformat.. code is completly new and app is totally standalone, i.e. this does not depend on anything other executable or batchfile...
as you can guess i have written this to implement it into my kitchen...
you can unpack *any* NBH file no matter what device its been made for, and you can repack NBH files for artemis/athena/trinity and hermes..
enjoy!
download: filemirror by www.thegamebooks.com (thanks)
edit: please install .net framework v2 if you havent already
update 23.03.2007: variable signature sizes supported! sorry for the delay guys...
Edit:
Mirror downloads
http://www.filefactory.com/file/8687...reskillzzz_rar
http://www.sendspace.com/file/3p3p6t
http://www.mediafire.com/?yktqm8c2g0t
as always i'm not responsible for and damaged or broken devices
i have tested it a couple of times and it worked, other people tested it too and it worked as it should.
as always, great job!
well done dutty.... another great tool..... are you using Studio 2003 or 2005?
Very nice and thank you. Is the source available?
Very nice.
this looks good i pray that it works with artemis, i have to try
great, it works~~~~~
Hi,
I can´t start the app in XP. it gives error Failed to start correct initiation (0xc0000135). I know this is not due to the app, but due to something missing at my XP. Any idea of what is it?
Nevermind... fixed.
Unfortunately doesnt work with Artemis' Roms. Dutty is there any possibility to make some patch? Please
phsnake said:
Unfortunately doesnt work with Artemis' Roms. Dutty is there any possibility to make some patch? Please
Click to expand...
Click to collapse
oh! great, nothing but great!
phsnake said:
Unfortunately doesnt work with Artemis' Roms. Dutty is there any possibility to make some patch? Please
Click to expand...
Click to collapse
tell me where to grab a artemis rom and the problem you have
Great work @Dutty.
Br
i think the signature size you're using is always 64 bytes... that is ok for hermes & trinity, but for artemis and probably other devices it should be 1024.
Drug_Store said:
Nevermind... fixed.
Click to expand...
Click to collapse
Noob question but how did u fixed it..I hv the same problem...
Artemis
dutty said:
yet again a tool that makes something as easy and comfortable as it can be...this time it's:
NBH packing and unpacking
had some fun rev'ing the NBH fileformat.. code is completly new and app is totally standalone, i.e. this does not depend on anything other executable or batchfile...
as you can guess i have written this to implement it into my kitchen...
you can unpack *any* NBH file no matter what device its been made for, and you can repack NBH files for artemis/athena/trinity and hermes..
enjoy!
download: attached
Click to expand...
Click to collapse
Tried on Artemis..Orbit ..don't work..even after removing Device ID..
Everytime..I get error..Rom is corrupt.I guess u need to incorporate POF's suggestion of 1024 kb..signature ..It wud b gr8 if this happens ..I can make alive my Orbit.
Atemis ROM
dutty said:
tell me where to grab a artemis rom and the problem you have
Click to expand...
Click to collapse
Here is link to Artemis RUS ROM
http://rapidshare.com/files/17066642/ART_HTCRUS_11241101_026790_RUS_Ship.zip.html
which has nbh file in there ( looks like Dopod's Rom has nba file ???)
so I have tried to unpack nbh from RUS ROM and here is what i have:
Windows.nb
Radio.nb
SPL.nb
PrimarySplash.nb
G3IPL.nb
G4IPL.nb
ExtendedRom.nb
And now there is a couple of questions:
how to assamble nbh back if in tools there are no ACTIVE strings for SPL and IPL(if u choose Artemis)??? Extracted two IPL files but in tools only one string to input IPL.nb, how to bypass this issue??
And the last: how to edit nb files and in which nb is a software sitting???
Thanks if anyone can help.
olch said:
Here is link to Artemis RUS ROM
http://rapidshare.com/files/17066642/ART_HTCRUS_11241101_026790_RUS_Ship.zip.html
which has nbh file in there ( looks like Dopod's Rom has nba file ???)
so I have tried to unpack nbh from RUS ROM and here is what i have:
Windows.nb
Radio.nb
SPL.nb
PrimarySplash.nb
G3IPL.nb
G4IPL.nb
ExtendedRom.nb
And now there is a couple of questions:
how to assamble nbh back if in tools there are no ACTIVE strings for SPL and IPL(if u choose Artemis)??? Extracted two IPL files but in tools only one string to input IPL.nb, how to bypass this issue??
And the last: how to edit nb files and in which nb is a software sitting???
Thanks if anyone can help.
Click to expand...
Click to collapse
Hi
pls read my post above
Does anybody know whether this tool could be used for Excalibur .nbh-files?
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
Mirror 01 - Mediafire
Mirror 02 - FileSavr
How to Get Started:
Download the Opal Kitchen
Extract it to the C: Drive on your computer
Set your Base ROM by running RunMe.bat and choosing e, a
Put your Packages in the Packages folder
Cook it up!
Useful links:
Opal Base ROM (extract .nbh from .exe and place in BaseROM)
Thank you:
Creators of KaiserKitchen
Bepe
Ervius
misar for G'Reloc
Dark Simpson for his HTC ROM Tool
tadzio for ImgFS Tools
udK for Opal Custom RUU
Great job mbarvian
Thread stickied.
kidnamedAlbert said:
Great job mbarvian
Thread stickied.
Click to expand...
Click to collapse
thanks man
and CONGRATS on the moderator status
Yess finally it's here, been waiting so much for this! thanks!
Hey man , can u Share at anyother please? i can not open that link!
terry888_1978 said:
Hey man , can u Share at anyother please? i can not open that link!
Click to expand...
Click to collapse
uploaded at FileSavr!
mbarvian said:
uploaded at FileSavr!
Click to expand...
Click to collapse
thanks a lot !! i got it now! and i going to try ! report later !
i've try that kitchen tools, i got a problem , when i extract a nbh file , i could get "ROM OEM SYS" this 3 folders, but when i choose extract nbh and 2 raw files , i only got "ROM SYS" 2 folders , i try many times, close virus firewall and many ways, it's the same. can someone tell me why?
terry888_1978 said:
i've try that kitchen tools, i got a problem , when i extract a nbh file , i could get "ROM OEM SYS" this 3 folders, but when i choose extract nbh and 2 raw files , i only got "ROM SYS" 2 folders , i try many times, close virus firewall and many ways, it's the same. can someone tell me why?
Click to expand...
Click to collapse
did you have RUU_signed.nbh (shipped Opal ROM), Part01.raw, and Part02.raw in the BaseROM folder?
mbarvian said:
did you have RUU_signed.nbh (shipped Opal ROM), Part01.raw, and Part02.raw in the BaseROM folder?
Click to expand...
Click to collapse
yes , sure !! i've tried CHT's RUU_signed.nbh and WWE's RUU_signed.nbh ! still the same !
mbarvian said:
Screenshot:
Download:
Mirror 01 - Mediafire
Mirror 02 - FileSavr
How to Get Started:
Download the Opal Kitchen
Extract it to the C: Drive on your computer
Set your Base ROM by running RunMe.bat and choosing e, a
Put your Packages in the Packages folder
Cook it up!
Useful links:
Opal Base ROM (extract .nbh from .exe and place in BaseROM)
Thank you:
Creators of KaiserKitchen
Bepe
Ervius
misar for G'Reloc
Dark Simpson for his HTC ROM Tool
tadzio for ImgFS Tools
udK for Opal Custom RUU
Click to expand...
Click to collapse
at last ,when try RUU ruu_signed.nbf,%1 Get a error270,image file corrupted!!!
ps:CID has already unlocked!
mbarvian said:
Screenshot:
Download:
Mirror 01 - Mediafire
Mirror 02 - FileSavr
How to Get Started:
Download the Opal Kitchen
Extract it to the C: Drive on your computer
Set your Base ROM by running RunMe.bat and choosing e, a
Put your Packages in the Packages folder
Cook it up!
Useful links:
Opal Base ROM (extract .nbh from .exe and place in BaseROM)
Thank you:
Creators of KaiserKitchen
Bepe
Ervius
misar for G'Reloc
Dark Simpson for his HTC ROM Tool
tadzio for ImgFS Tools
udK for Opal Custom RUU
Click to expand...
Click to collapse
May I ask how to get a .nbh from the origianal shipped rom?
Why does the ROM that I create untied again to have no the XIP
1, untie the official ROM
2, the creation ROM
3, then untie the oneself's ROM of the creation
The XIP throws to lose
Execuse me, my English is bad.
FYfans said:
May I ask how to get a .nbh from the origianal shipped rom?
Click to expand...
Click to collapse
If it's an exe, open it up with WinRAR and you'll see the RUU along with the .nbh. Simply drag and drop to the place you need it to be in.
Great work mbarvian. Was this through experimenting or did you get an Opal?
%1 Get a error270,image file corrupted!!!
htcrt.ini
[Opal]
ModelId=OPAL100**
SignMaxChunkSize=1024
SPL=$200
SPLN=SPL
Splash1=$600
Splash1N=Splash
Radio=$300
RadioN=Radio
System=$400
SystemN=System
htc room tool
Model ID = OPAL100**
Country ID = 11111111
RUU ruu_signed.nbf,%1 Get a error270,image file corrupted!!!
htc room tool
Model ID = OPAL10000
Country ID = SuperCID
RUU ruu_signed.nbf OK
Download this file.
View attachment OpalChefFix.zip
=========================================================
XIP throws to lose
RunMe.cmd change
line 332
..\TOOLS\ImgfsFromNb OS.nb imgfs.bin ==> REM ..\TOOLS\NBSplit -kaiser OS.nb
line 336
..\TOOLS\ImgfsToNb imgfs-new.bin os.nb.payload os-new.nb ==> ..\TOOLS\ImgfsToNb imgfs-new.bin os.nb os-new.nb
Hi
Somebody, can create a new ROM for russian Viva??
i need Base Rom de Viva But in Spanish sombody get?
thanks I want to know if this can be used in making a wm6.5 rom?
I dumped a Rom now. How can I rebuild it?
Sombody Can Help me?
Please I need help with this, try to cook a rom but before completing the installation of said error write flash
I have used the TMOUS 2.10.1 ROM base to cook my latest ROMs to make them TMOUS compatible.
I have had someone test the ROM and it works fine, but only 512 ROM is recognised.
In EVK, I used the entire OEM > COMMON folder as a base, so that means everything including OEMDrivers and OEMDriversHigh is from the 2.10.1
I even used the OEMXIPKernel from the 2.10.1 ROM dump (even though it appears identical to the 2.10 version).
Is there anything else I have missed that is required to enable the full 1024MB ROM?
Thanks
Good question, I'm using the same stuff but also in my rom thread users reported about the memory.
* OEMXipkernel
* Oemdrivers
* Oemdrivershigh
* Oemversion
* Radio
good question..
My opinion:
It can only be the SPL. Ether they did not use HSPL2.08 or HSPL2.08 is not 1024MB compatible...
I have included in the attached radioconf.nb and radiocust.nb try adding these into the build process, i have also added in the attached my htcrt i use to add these in.. I have not had this issue on my tmobile HD2 rom.
joshkoss said:
I have included in the attached radioconf.nb and radiocust.nb try adding these into the build process, i have also added in the attached my htcrt i use to add these in.. I have not had this issue on my tmobile HD2 rom.
Click to expand...
Click to collapse
Thanks,
but what exactly are these files and what do we do with them? I know you said cook them in, but where?
Thanks
the_scotsman said:
Thanks,
but what exactly are these files and what do we do with them? I know you said cook them in, but where?
Thanks
Click to expand...
Click to collapse
yea my fix probably would not fix you're issue or everyone would have this problem.. i think i'm the only chef that cook's in the radioconf.nb and radiocust.nb into the rom also... just ignore my suggestion.. i would question the users what spl they are using like the above suggestion and be sure you're rom base is 2.10...
joshkoss said:
yea my fix probably would not fix you're issue or everyone would have this problem.. i think i'm the only chef that cook's in the radioconf.nb and radiocust.nb into the rom also... just ignore my suggestion.. i would question the users what spl they are using like the above suggestion and be sure you're rom base is 2.10...
Click to expand...
Click to collapse
Ah ok thanks, I'll see what they are using...
I read through Laurentius26 TMOUS ROM thread...one of the users said
"I flash an other ROM (elegance) just to see the difference and there I have 724 free storage"
So this indicates it's not HSPL related...it has to be something related to the ROM..but what
i would like to understand this also, the htc device info shows 1024 flash and 576 ram but the os info only shows total storage of 227mb and 452 total program.
this should be 1024 storage no?
have you tried just rebuilding the stock 2.10 rom with your EVK and having someone test it to see what ram/storage it has? if so and its not working then i think you should have josh upload his EVK and tools folder and try rebuilding with it and see if it works for you since he said he doesnt have this problem.
make sure dont delete any files that are in the OEM folder,and keep the OEMXipKernel,i think you will get the 1024 rom enble
weixiong said:
make sure dont delete any files that are in the OEM folder,and keep the OEMXipKernel,i think you will get the 1024 rom enble
Click to expand...
Click to collapse
Already tried this...
I'm using Extendir, next rom for T-Mob USA HD2 I will do without this feature and leave XIP what it's, maybe that will solve it who knows.
For now it's just quesing and hoping it works as I don't have a T-Mob US.
twopumpchump said:
have you tried just rebuilding the stock 2.10 rom with your EVK and having someone test it to see what ram/storage it has? if so and its not working then i think you should have josh upload his EVK and tools folder and try rebuilding with it and see if it works for you since he said he doesnt have this problem.
Click to expand...
Click to collapse
Did anyone try this already?
Because my wild guess would be that you need one ore more of the following files from the 2.10:
Code:
\ROM\LEO\os.nb.payload
\ROM\LEO\romhdr.bin
\ROM\LEO\xip.bin
I'm not in a position to test this, but you probably only need the payload.
If I remember correct, storage sizes are in the payload.
Enjoy!
ShaDrac
ShaDrac said:
Did anyone try this already?
Because my wild guess would be that you need one ore more of the following files from the 2.10:
Code:
\ROM\LEO\os.nb.payload
\ROM\LEO\romhdr.bin
\ROM\LEO\xip.bin
I'm not in a position to test this, but you probably only need the payload.
If I remember correct, storage sizes are in the payload.
Enjoy!
ShaDrac
Click to expand...
Click to collapse
Thanks for the tip, will give it a try!
Thanks ShaDrac,
I did a quick compair between HD2 HTC 1.72 rom and T-Mob 2.10.
The IMGFS offset is different.
IMGFS offset of TMob starts earlier as HTC, so that means more space at the end of payload so more mem or am I totally wrong?
1.72:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.10:
ShaDrac said:
Did anyone try this already?
Because my wild guess would be that you need one ore more of the following files from the 2.10:
Code:
\ROM\LEO\os.nb.payload
\ROM\LEO\romhdr.bin
\ROM\LEO\xip.bin
I'm not in a position to test this, but you probably only need the payload.
If I remember correct, storage sizes are in the payload.
Enjoy!
ShaDrac
Click to expand...
Click to collapse
Laurentius26 said:
Thanks ShaDrac,
I did a quick compair between HD2 HTC 1.72 rom and T-Mob 2.10.
The IMGFS offset is different.
IMGFS offset of TMob starts earlier as HTC, so that means more space at the end of payload so more mem or am I totally wrong?
1.72:
2.10:
Click to expand...
Click to collapse
Sounds logical man!
Well I'm trying to figure out using a little I know from my Uni cookings...
I'm just a CooknOOb hehe.. LoL, ShaDrac is the DeverDev so I hope he has an answer.
joshkoss said:
Sounds logical man!
Click to expand...
Click to collapse
Laurentius26 said:
Well I'm trying to figure out using a little I know from my Uni cookings...
I'm just a CooknOOb hehe.. LoL, ShaDrac is the DeverDev so I hope he has an answer.
Click to expand...
Click to collapse
well it makes sense.. it's dumping the imgfs at different start places becuse the tmobile build xip and imgfs structure adressing is different because it allocates the extra ram. The HTC dump and imgfs and xip adressing is allocated for that phone..
This is my htcrt.ini
[Leo]
Experimental=1
ModelId=PB8110000
SignMaxChunkSize=64
RomSections=7, "0x100,IPL,0,TRUE", "0x200,SPL,524288,TRUE", "0x600,Splash,786432,FALSE", "0x601,Subsplash,0,FALSE", "0x301,Radio,20840448,TRUE", "0x700,""Ext. ROM"",0,FALSE", "0x400,OS,0,FALSE"
Could that be the cause, wrong settings?
joshkoss said:
well it makes sense.. it's dumping the imgfs at different start places becuse the tmobile build xip and imgfs structure adressing is different because it allocates the extra ram. The HTC dump and imgfs and xip adressing is allocated for that phone..
Click to expand...
Click to collapse
Hi guys,
Need some help on this one. I recently moved to OS Kitchen. Must say pretty impressive. Still exploring it but i faced an issue. i did not change the sys and simple imported my EVK packs and sys(i hope so). When i build using evk, everything is fine, but when i cook using OS Kitchen i face some issues:
1. The resolution on text and some popup displays is small as in below pics.
2. The softkey font is in bold. earlier it used to be normal.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If anyone knows a specific reason or a workarnd then do help. thanx
Same thing happened to me with the small text, but I haven't had time to figure it out. I just added some oboe stuff and 23132, but left most things the same as a build in oskitchen without those issues. Will keep an eye on this thread .
Mr. Makk said:
Hi guys,
Need some help on this one. I recently moved to OS Kitchen. Must say pretty impressive. Still exploring it but i faced an issue. i did not change the sys and simple imported my EVK packs and sys(i hope so). When i build using evk, everything is fine, but when i cook using OS Kitchen i face some issues:
1. The resolution on text and some popup displays is small as in below pics.
2. The softkey font is in bold. earlier it used to be normal.
If anyone knows a specific reason or a workarnd then do help. thanx
Click to expand...
Click to collapse
Small fonts - this issue is related to the folder structure required for OS Kitchen. In "0409" you will find some packages which are not "0409". Transfer it to "Common" and, no more small fonts.
Bold fonts - This issue is related to the latest WM releases, and, it is on purpose (not a bad idea). The only remedy I know - integrate some files from older COM5 releases. IMHO it is a questionable solution that risks instability by mixing different branches. Better become use to bold.
Hope it helps.
Mr. Makk said:
Hi guys,
Need some help on this one. I recently moved to OS Kitchen. Must say pretty impressive. Still exploring it but i faced an issue. i did not change the sys and simple imported my EVK packs and sys(i hope so). When i build using evk, everything is fine, but when i cook using OS Kitchen i face some issues:
1. The resolution on text and some popup displays is small as in below pics.
2. The softkey font is in bold. earlier it used to be normal.
If anyone knows a specific reason or a workarnd then do help. thanx
Click to expand...
Click to collapse
Hi mate..
this appened because when you rebuild your rom with Ervius kitchen
all dsm in all pack in sys are eliminated,
if you have import sys build from EVk to Os,there will be no dsm
required to Os Kitchen
giorgina351 said:
Small fonts - this issue is related to the folder structure required for OS Kitchen. In "0409" you will find some packages which are not "0409". Transfer it to "Common" and, no more small fonts.
Bold fonts - This issue is related to the latest WM releases, and, it is on purpose (not a bad idea). The only remedy I know - integrate some files from older COM5 releases. IMHO it is a questionable solution that risks instability by mixing different branches. Better become use to bold.
Hope it helps.
Click to expand...
Click to collapse
Everything in the sys seems perfect.
alesscam said:
Hi mate..
this appened because when you rebuild your rom with Ervius kitchen
all dsm in all pack in sys are eliminated,
if you have import sys build from EVk to Os,there will be no dsm
required to Os Kitchen
Click to expand...
Click to collapse
the sys packs in evk have dsm files. so this time i imported sys from the evk folder using oskitchen. but still same issue.
I had this issue with OSB one time, and willysp said he had the issue too.
We basically altered "packages.sof" to rearrange the SYS folders, the order in which they are processed.
Once untouched it was just fine. But it just dont like that SYS order to be messed with.
Mr. Makk said:
Everything in the sys seems perfect.
the sys packs in evk have dsm files. so this time i imported sys from the evk folder using oskitchen. but still same issue.
Click to expand...
Click to collapse
mate
i use build 23132 without this problem
i have downloaded build from link Alexx
try to unzipp another time
and import with oskitchen from desktop
Hi im having this same problem, the problem appear after i order the package.sog and cif. and i dont know how to fixes. im using osbuilder. i have rhodiumw gsm-cdma
EDMYJOSE said:
Hi im having this same problem, the problem appear after i order the package.sog and cif. and i dont know how to fixes. im using osbuilder. i have rhodiumw gsm-cdma
Click to expand...
Click to collapse
Dont mess with SYS order, and it should be just fine.
This link might help: http://www.mobileunderground.info/showthread.php?t=23024
NOTE: This version is for testing only, make a backup of your older kitchen folder before trying the new version.
Changelog v1.34alpha2
Fixed ImgfsFromDump returning an error when the ramdrive cleanup mode setting was enabled
Fixed ImgfsFromDump not returning errors correctly
Fixed os.nb file deletion issue for devices with no sectorinfo
Fixed delete shadow order entries not being saved
Improved file copy and file deleting speed
Implemented detection of registry values that are found without a preceding registry key specifier
Fixed add2 files merging issue
Changelog v1.34alpha1
Moved the project to .NET Framework 4.0
Implemented internal manifest management to reduce disk overhead during package scanning
The kitchen now automatically strips all attributes from all packages files and when generating the ROM uses the ones declared in the DSM file when present or the previous internal default list
Implemented new hybrid build engine to shorten ROM generation time and take care of all overlapping files/modules
Release Notes
Manila management doesn't work
The kitchen prints a list the package and subpackage order while building to allow verifying if it's correct
Placeholder 2
Placeholder 3
could this use for cooked snap/mapl ROM? if not could u add it
Wow, great! I'll be waiting for the beta release
@ airxtreme:
hi , are you planing to put in tools for dumping stock wp7 rom's (the tools that are available at this time ) and only the parts that we can dump at this moment ?
that would be real nice , than we can explore it more simple .
ceesheim said:
@ airxtreme:
hi , are you planing to put in tools for dumping stock wp7 rom's (the tools that are available at this time ) and only the parts that we can dump at this moment ?
that would be real nice , than we can explore it more simple .
Click to expand...
Click to collapse
Until a proper tool for the D000FF files is released I can't produce proper dumps of the roms.
Thanks for this new creature Airxtreme.
It seems more fast then before but unfortunately i got this error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This happen with and without IMPLANTxip.
EDIT : i only dumped and rebuilded Leo signed 1.66 ITA, no Manila patch .
OSKitchen v1.34 Alpha1
Test on ELL ROM ver ALL OK
until now...
got the same error as af974 (dumped fresh Leo s 3.14 ship rom and change any options, non implant xip method)
however what a dramatic increase in build process..
took 3 minutes to reach to the imgfs from dump part while it usually takes 10-20 mins on this busted up laptop..
Cool...i thought i was the only one with this problem
Now it would be interesting know how come that Sternas did get the error.
jjblaster3 said:
got the same error as af974 (dumped fresh Leo s 3.14 ship rom and change any options, non implant xip method)
however what a dramatic increase in build process..
took 3 minutes to reach to the imgfs from dump part while it usually takes 10-20 mins on this busted up laptop..
Click to expand...
Click to collapse
af974 said:
Cool...i thought i was the only one with this problem
Now it would be interesting know how come that Sternas did get the error.
Click to expand...
Click to collapse
Magic Sir, Black Cooking Magic...
Hahahah LOL thats funny ...Sternas did you try to dump and cook or did you copy the new files over the old kitchen?
sternas said:
Magic Sir, Black Cooking Magic...
Click to expand...
Click to collapse
af974 said:
Hahahah LOL thats funny ...Sternas did you try to dump and cook or did you copy the new files over the old kitchen?
Click to expand...
Click to collapse
NO Sir
this is NOT my problem
My Cooking "LAVA" exists ...
I use this tool to build ROMs
extract Stock ROMs is an other subject...
for me the split of "initflashfiles.dat"
is NOT good idea....
Ok it seems to be a trees problem.
I had my Kitchen in D:\XXXXX\OsKitchen
I changed in D:\OsKitchen and i was able to run the kitchen without errors.
af974 said:
Ok it seems to be a trees problem.
I had my Kitchen in D:\XXXXX\OsKitchen
I changed in D:\OsKitchen and i was able to run the kitchen without errors.
Click to expand...
Click to collapse
Oh, that is good....
have fun...
af974 said:
Ok it seems to be a trees problem.
I had my Kitchen in D:\XXXXX\OsKitchen
I changed in D:\OsKitchen and i was able to run the kitchen without errors.
Click to expand...
Click to collapse
Did XXXXX have spaces?
Can somebody please try this imgfsfromdump to see if it solves the crash?
Nope....the exact name is D:\Downloads\osKitchen Next v1.34alpha1
RoryB said:
Did XXXXX have spaces?
Click to expand...
Click to collapse
Same error with it and osKitchen in subfolder.
airxtreme said:
Can somebody please try this imgfsfromdump to see if it solves the crash?
Click to expand...
Click to collapse