Question for HD2 Chefs... - Windows Mobile

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

Related

dutty's good NBHTool v1.1 (updated)

{
"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?

Change Loading Screen?

On TyTN it is possible to change loading screen e.g. like this:
{
"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"
}
Does somebody know address to flash the same via MTTY to Artemis as well?
Im also very intrested into changing my startup screen.
its a great Idea to put your address there because it doesn't go away after a hardreset and most people wont know how to get rid of it.
planning to put a nice bluefish over there, you figured it out yet?
itarix said:
Im also very intrested into changing my startup screen.
its a great Idea to put your address there because it doesn't go away after a hardreset and most people wont know how to get rid of it.
Click to expand...
Click to collapse
it tries with this:
http://www.4shared.com/file/19395089/5971579/Upgrade_HTC_First_Splash.html
clodia72 said:
it tries with this:
http://www.4shared.com/file/19395089/5971579/Upgrade_HTC_First_Splash.html
Click to expand...
Click to collapse
still seeing a htc logo at boot...? did it just change again, from a htc logo to a htc logo, or did nothing happen?
thanks for helping though!
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=20&Itemid=27
clodia72 said:
http://www.mrvanx.org/cms/index.php?option=com_content&task=view&id=20&Itemid=27
Click to expand...
Click to collapse
can anyone confirm that it works?
itarix said:
can anyone confirm that it works?
Click to expand...
Click to collapse
I think so.
Dutty's is ok for artemis
clodia72 said:
I think so.
Dutty's is ok for artemis
Click to expand...
Click to collapse
Dutty's IS not OK FOR ARTEMIS You have to use an othe tool. i will upload it tonight i don't have it here at my work. DUTTY's is for the hermes not the artemis
pvdhelm said:
Dutty's IS not OK FOR ARTEMIS You have to use an othe tool. i will upload it tonight i don't have it here at my work. DUTTY's is for the hermes not the artemis
Click to expand...
Click to collapse
Could you upload all of the files needed to change boot screen?
pvdhelm said:
Dutty's IS not OK FOR ARTEMIS You have to use an othe tool. i will upload it tonight i don't have it here at my work. DUTTY's is for the hermes not the artemis
Click to expand...
Click to collapse
Here is a link for the HTC ROM Tool form Dark Simpson to use with Artemis (don´t use Dutty´s tool for artemis)
http://forum.xda-developers.com/showthread.php?t=311909&highlight=htcrt.exe
Tnx Uliba this is the tool i was talking about.
I have assembled the ROM for my MDA Compact3
I have assembled the ROM for my MDA Compact3 with Dutty's and all correctly works!!!
I have change the OS from German to Italian, without canghe the files IPL and SPL
The ROM is possible to see here her ---> http://forum.xda-developers.com/showthread.php?t=316159
Has been only fortune !!
Or with Dutty it is possible to also assemble ROM for Artemis.
Always failed for me with duty's tools...
clodia72 said:
I have assembled the ROM for my MDA Compact3 with Dutty's and all correctly works!!!
I have change the OS from German to Italian, without canghe the files IPL and SPL
The ROM is possible to see here her ---> http://forum.xda-developers.com/showthread.php?t=316159
Has been only fortune !!
Or with Dutty it is possible to also assemble ROM for Artemis.
Click to expand...
Click to collapse
If you are successfull, it will work - i personally had some problems, but may be this was with a former version. Since that i build my roms with HTC Tool.
The next rom that I cook, will try to use HTC Tool.
Is never finished learning, thanks!!
clodia72 said:
The next rom that I cook, will try to use HTC Tool.
Is never finished learning, thanks!!
Click to expand...
Click to collapse
Hi friend - we all are always learning.
For info - i use Dutty´s tool for extracting - for example if i need an special radio rom.
uliba said:
Hi friend - we all are always learning.
For info - i use Dutty´s tool for extracting - for example if i need an special radio rom.
Click to expand...
Click to collapse
YES, I use for extracting the files * .nbh, and it is very simpler and comfortable than NBHextract.
didn't work
it didn't work followed the instructions to make the nb file then converted it to nbh with the htc tool.
after that I renamed the file to TOM_B.B_v3.7_WWE.nbh and used its flash program RUU
it goes to 100% in a split second, and then it says on the pc screen error 228? (not sure about the number) wrong file size, invalid or corrupt file.
the phone simply reboots and I the old bootscreen.
but at the bright side... my phone still works
anything im doing wrong?
did it work with the dutty tool?
btw the htc tool only allows you to select one bootscreen no sub bootscreen. did the people that got it to work with dutty select 2 bootscreens?
itarix said:
it didn't work followed the instructions to make the nb file then converted it to nbh with the htc tool.
after that I renamed the file to TOM_B.B_v3.7_WWE.nbh and used its flash program RUU
it goes to 100% in a split second, and then it says on the pc screen error 228? (not sure about the number) wrong file size, invalid or corrupt file.
the phone simply reboots and I the old bootscreen.
but at the bright side... my phone still works
anything im doing wrong?
did it work with the dutty tool?
btw the htc tool only allows you to select one bootscreen no sub bootscreen. did the people that got it to work with dutty select 2 bootscreens?
Click to expand...
Click to collapse
Here is a new link: Screentool, which is easy to use!!!
http://forum.xda-developers.com/showthread.php?t=317726

[SOLVED] Tool for converting .abi to .nbh?

Hihi, I was wondering if there was a tool that would convert ROMs in the ASUS .abi format into to HTC's .nbh format? (The HTC bit is correct right?)
If you're wondering why, it's so us folks with ASUS device's can use that good Ol' OSKitchen!
Although obviously, if you know of another method to use this kitchen with ASUS ROMs, by all means, let me know!
Any help would be apprepciated, so shoot!
Thanks!
I'm not familiar with the Asus formats, but I assume during cooking you turn the ABI in to an OS.NB? If that's the case, you should be able to use the OS.NB in OSKitchen, and then convert it back to an ABI later.
Ahhhhh, I've been silly haven't I!
I have to split the .abi into os.nb0 and extrom.img with p835abisplit2.exe when I use my normal kitchen!
Thanks for making me realise my mistake!!
I'm considering this solved, so the mods can close it if needs be.
jonnymint said:
Ahhhhh, I've been silly haven't I!
I have to split the .abi into os.nb0 and extrom.img with p835abisplit2.exe when I use my normal kitchen!
Thanks for making me realise my mistake!!
I'm considering this closed, so the mods can close it if needs be.
Click to expand...
Click to collapse
I can easily add nb0 support to oskitchen but will that device work or does it have one of the native kernels that cause platformrebuilder to crash?
I've imported the os.nb0 from my Xda Zest (Asus P565) stock rom into oskitchen, and everything worked fine!
oskitchen built the rom fine, platformrebuilder didn't show any errors or anything and the rom booted, so I'd say it doesn't have one of the native kernels that cause it to crash.
airxtreme said:
I can easily add nb0 support to oskitchen
Click to expand...
Click to collapse
As for adding support, is it not already there?
I used the import wizard that pops up, and it imported fine.
It did say this,
{
"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"
}
But that's not anything to do with the image being imported, It's the name of the device right?
jonnymint said:
I've imported the os.nb0 from my Xda Zest (Asus P565) stock rom into oskitchen, and everything worked fine!
oskitchen built the rom fine, platformrebuilder didn't show any errors or anything and the rom booted, so I'd say it doesn't have one of the native kernels that cause it to crash.
As for adding support, is it not already there?
Click to expand...
Click to collapse
There are lot of different NB0/BIN files but the one that the tool you used extracted seems to be a NB0 with all the extra data removed, usually those have to be converted to nb with osnbtool -sp to clean the exta data.
jonnymint said:
I used the import wizard that pops up, and it imported fine.
It did say this,
But that's not anything to do with the image being imported, It's the name of the device right?
Click to expand...
Click to collapse
Yes the device name currently has nothing associated with it, you can use whatever name you want.
airxtreme said:
There are lot of different NB0/BIN files but the one that the tool you used extracted seems to be a NB0 with all the extra data removed, usually those have to be converted to nb with osnbtool -sp to clean the exta data.
Click to expand...
Click to collapse
I think I see what you mean,
You're saying you might add support for NB0s with all the extra data removed?
And while you're here,
My EXT Packages tab is empty in oskitchen, is it supposed to be?
jonnymint said:
I think I see what you mean,
You're saying you might add support for NB0s with all the extra data removed?
And while you're here,
My EXT Packages tab is empty in oskitchen, is it supposed to be?
Click to expand...
Click to collapse
No I meant I had to add support to rebuilding the NB0 with extra data, your one doesn't need the extra data so it works fine.
Yes the EXT packages are empty because other manufacturers cram everything inside the OEMMisc package. With non-HTC phones you have to sort things up by yourself and it takes a lot.
Ah, I get you now!
What is the extra data though by the way?
Yeaah, my OEMMISC folder is such a mess!
Some things are in there like MMS and EziPhoto and other Asus apps, and there are loads of other things in the extrom.img.
It's all rather confusing.
jonnymint said:
Ah, I get you now!
What is the extra data though by the way?
Click to expand...
Click to collapse
It's data the tools don't understand so it's usually stripped and put back in form of padding.
jonnymint said:
Yeaah, my OEMMISC folder is such a mess!
Some things are in there like MMS and EziPhoto and other Asus apps, and there are loads of other things in the extrom.img.
It's all rather confusing.
Click to expand...
Click to collapse
Well at least part of the stuff is removable directly by emptying the extended rom, phones like the omnia where tons of applications are crammed in oemmisc are a mess to handle.
airxtreme said:
Well at least part of the stuff is removable directly by emptying the extended rom, phones like the omnia where tons of applications are crammed in oemmisc are a mess to handle.
Click to expand...
Click to collapse
That's a good point actually.
I emptied my extended rom using winimage, very easy indeed!
What happens if I just delete the OEMMISC folder?
Would that leave me with, if I build it, a 'blank' (as in no oem customisations) rom?
Or would it not boot?
jonnymint said:
That's a good point actually.
I emptied my extended rom using winimage, very easy indeed!
What happens if I just delete the OEMMISC folder?
Would that leave me with, if I build it, a 'blank' (as in no oem customisations) rom?
Or would it not boot?
Click to expand...
Click to collapse
If the camera and other applications aren't store there probably you would get a clean working ROM.
Haha, yeah the cameras in there.
I took everything else out and it all worked fine so my OEMMisc folder is now tidy, so to speak!
And I can add in all the cabs I need using the package converter in oskitchen.
I've now cooked my first customised(ish) rom! Yaay.
I wouldn't have been able to do it without your help.
Thanks so much!!
jonnymint said:
Haha, yeah the cameras in there.
I took everything else out and it all worked fine so my OEMMisc folder is now tidy, so to speak!
And I can add in all the cabs I need using the package converter in oskitchen.
I've now cooked my first customised(ish) rom! Yaay.
I wouldn't have been able to do it without your help.
Thanks so much!!
Click to expand...
Click to collapse
You're welcome

[ROM][WM6.5.X] Very light 23563 + Kitchen

I've been working on tweaking the hell out of my base ROM, and have now got it to benchmark incredibly well (it also feels very snappy).
This is a WM6.5.X ROM, based on the 3.04 and 2.14 OEM ROMs and 23563 XIP/SYS from Da_G
All it has got is the bare minimum OEMDrivers, plus a fully featured SYS (some of the SYS applications have been tweaked: removed extra screen layouts for LockScreen, removed SampleMusic etc, UPXed a few things).
The XIP has been tweaked quite heavily to get the best performance, and you should be able to add whatever you like to this ROM and it should remain stable.
{
"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"
}
New build (10062801)
Code:
[#] Tweaked XIP
[#] Some files from Oboe and Huashan
[#] Lots of bug fixes
Download:
[url=http://rapidshare.com/files/403536145/WM6550-23563-Leo-GSM-Kitchen.7z.html]Kitchen[/url]
[url=http://rapidshare.com/files/403530741/RUU_Leo_l3v5y_10062801_L_WWE_5.2.23563.5.5.0_3.04.exe.html]RUU[/url]
[url=http://rapidshare.com/files/403536148/ruu_signed_LEO_10062801.7z.html]NBH[/url]
New build (10062701)
Code:
XIP/SYS 23563/23563
OEM 3.04/2.14
[url=http://rapidshare.com/files/403375733/RUU_Leo_l3v5y_10052701_L_WWE_5.2.23563.5.5.0_3.04.exe.html]RUU[/url]
Thanks to Paul at MoDaCo, there's now hosting for my ROMs without the horrible wait time of RapidShare!
You will need to visit here to get the ROMs.
Cool - thanks this sounds and looks great.
I guess this would be an ideal base for SpbMS??
Home sweet home !!!!!!!!!!!!!
good luck with your build mate, always found your build and kitchen to be one of the best starting points for anyone
quick question, looking at your screen shots you've not enabled the 576mb hack? curious as to why.
regards and good luck
chris
chrisd1a1 said:
good luck with your build mate, always found your build and kitchen to be one of the best starting points for anyone
quick question, looking at your screen shots you've not enabled the 576mb hack? curious as to why.
regards and good luck
chris
Click to expand...
Click to collapse
I have enabled 576MB, but the total memory is only 459MB (that's still more than the 448MB you should have though).
ROMRaid is currently down, so uploading to RapidShare instead, unless anyone has any better ideas?
how many megs is the zip file?
gonna hafta give this ROM a shot!
mikentucson said:
how many megs is the zip file?
Click to expand...
Click to collapse
RUU is ~70mb, kitchen is ~50mb
Greetings:
Thank you for all the time you put in to this Rom.
I was just wondering if this is safe for Leo1024(Timous)?!
Cheers
samteeee said:
Greetings:
Thank you for all the time you put in to this Rom.
I was just wondering if this is safe for Leo1024(Timous)?!
Cheers
Click to expand...
Click to collapse
To be honest, I don't know, I don't have a US Leo available for testing...
It's got the XIP from 2.14 which is the Leo1.5, which is the same as the US Leo, so it should work, but that's not guaranteed.
RUU now in first post!
Recommended radio is 2.10.50.26
l3v5y said:
RUU now in first post!
Recommended radio is 2.10.50.26
Click to expand...
Click to collapse
Here is a fast mirror thanks to Sanjeev @ VBNFiles
http://www.vbnfiles.com/xda/birkoffsjunk/RUU_Leo_l3v5y_10052701_L_WWE_5.2.23563.5.5.0_3.04.exe
I am going to wait for the full version, glad to see you back in the game
on my tmo hd2 it has 355mb free program memory but only 195mb free storage memory.. is it just because its not a tmobile rom that i have only 195mb free? with all the lite roms that ive tried, i usually have over 800mb free.
May be I stupid, but cannot find link for a kitchen. From descrition, this kitchen will be very good start point for custom light ROM's... Thanks!
Igoran said:
May be I stupid, but cannot find link for a kitchen. From descrition, this kitchen will be very good start point for custom light ROM's... Thanks!
Click to expand...
Click to collapse
Hadn't uploaded the kitchen yet, found a few bugs which I'm fixing before uploading.
Found lots of lovely bugs related to the XIP I'd used, which I'm fixing and optimising now...
Waiting waiting....
l3v5y said:
Found lots of lovely bugs related to the XIP I'd used, which I'm fixing and optimising now...
Click to expand...
Click to collapse
I would like to ask, bugs are only in kitchen or also in rom? I would really like to try your rom so I don`t know if to wait or download it right now. Thanks for clarification.

[WM Kitchen] OSKitchen v1.34 Alpha2 (21 October 2010) (TESTING ONLY)

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

Categories

Resources