Develop Bugs

Has the XDA2i Extended Rom Been Exposed Yet?

Has any one managed to expose the extended rom on the XDA2i for custom instalation on boot.
Also Vodafone Instalation cab works fine on XDA2i with all functions working.

I'm trying to do the same thing - has anyone managed to expose the extended rom on the XDA2i?

It was dumped a long time ago. The 3900 build of Bluetooth drivers comes from there.

Qtek 2020i problem
hi mamaich
I have bought Qtek 2020i before 2 days, can you please direct me how to unlock my extended rom? I will be very thankful to you if you help me in this issue
note: I tried the extended rom unlocker that was prepared for Himalaya and the one for Blueangel too and didn't show even my extended rom folder after soft reseting.

Re: Qtek 2020i problem
I don' have 2020i, so I cannot help with extrom unlocking.

Is there an Extended Rom Unlock Utility for the 2i?
We are desparately in need of a way to unlock the extended ROM of the XDA2i. The reason for this is that our application--for whatever reason--is not compatible with the 3900 bluetooth build, but IS compatible with earlier builds such as that found on the XDA2s.
If it is true that the ROM has been unlocked to gain the 3900 bluetooth build--then can someone please post a link to the way in which this was done and any utilities or software used to do it?!

Re: Is there an Extended Rom Unlock Utility for the 2i?
You can manually edit extended ROM image (NBF file) with extended ROM editor tool (I'don't remember its exact name, look into WiKi), delete CAB file and reflash. But I don't think that downgrading to build 3501 would help. You'd better fix your app.

I've tried this, used ER2003Edit_1_4_26. I have the nbf but it is telling me I can't open them because the password is incorrect. I have looked around quite a bit for a solution but have found none.
Is there a password which will allow one to gain entry to (ie edit and repackage) such that I can truly update the extended ROM of an XDA2i?

ERROR, ERROR ERROR
Sorry for my english
Since April i search a way to edit ExtRom on Qtek 2020i, but it seems that is to complicate for developers.
Status at this day
1) You can see extrom and by this way copy and save cab on other place. To do that you must reset just after steep 1 of hard reset and use your explorer. Other way, with your explorer, go to windows folder and simply run LoadVDisk.exe
2) You can't write into ExtRom
3) You can't edit rom with actuals tools (ER Edit, Dump ....). Passwords is unknow and i think memory adresses are differents
4) Also If you can't write in your Storage, because looked after used differents tools proposed by many peoples who know, to unlock your Extrom, flashing rom do not return Storage in normal status. It's my case and somebody with apparent good intention, but totaly incompetent, can you push to make an fatal error, thank's to all.
I'm am ungry when i read some absurbity (exemple in this forum). When we don't know, we must no speak

so is it impossible now to get the Srorage folder as before, I have this problem now in my 2020i, I cannot write into Storage HELPPPPPPPPP

It's exactly tha i said
DON'T USE FOR MOMENT ANY EXISTANT TOOLS TO UNLOK QTEK 2020I

Any progress in unlocking the extended ROM on XDA 2i anyone?

if somebody can povide me with valid source code I may try converting it for xdaIIi, I have one source now but missing some header files which I couldnt find like Pwinuser.h
I have free time these days, and I am sure that we have many good people here but maybe we need more effort, so let us share our experience on what we found so far, and try to solve this problem ASAP, what makes me more angrey these days is the Storage which also cannot be unlocked back...
so common guys, let's rock it out!

Hi
About storage i have unlocked mine. This lock Storage was appear after trying to unlock Extrom. Pls read this
http://forum.xda-developers.com/viewtopic.php?t=23154&highlight=
For me Storage locked is finish with this simple action.
For Extrom what header do you need ?
I put here registry and files extract from 2020i about Extrom that is nammed VDISK and use VDISK.dll. We can see ExtRom without reset to run LoadVdisk.lnk or .exe directly
I have also original installation of French ROM 1.11.02, Extended 1.11.115 and Radio 1.02 FRE.
Thank's for your support

I need the C header file not the registry information, read my reply to your post about the Storage, I explained there how does these things work out, at least for the 2020i a far as I could find out, if there is anyone on this forum who can add something or correct me, that would be nice, because we want all to work together to solve this problem ASAP.
I am now trying to find out the functions indside the dll file and find out how do they work, then I will try the password that is provided in this forum to unlock the extended rom. what happens to the Storage is that the old program has 2 parts: lock and unlock, when we tried to unlock, nothing happened because the password and device type was wrong, and when we tried to lock, the code didnt check the device name niether the password and directly locked the diskonchip drive which is in our case the Storage folder. I read the source code and this is what I understood, so I am trying to modify it to unlock one of these folders, and since it was not put completely on the FTP (missing header files) I couldnt compile the code!

EMU, i write respons about Storage in http://forum.xda-developers.com/viewtopic.php?t=23154&highlight=
Let me know if it's ok for you
Désolate for header file, i don't have it

I have an XDA2i. Is there any way I can provide the header files you're talking about? If so, please provide detailed instructions for how I would do it.

Hi Guys,
there is already a new version of ER2003Edit (not published yet!!!) which can open .nbf files of Qtek 2020i. The only problem is with checksum calculation. I am using Itsme's Perl script, but it has a problem calculating the checksum and he didn't have time to fix it yet.
Anyone else...?

Hi EMU
What are the status of your trying to unlol Extrom. Can we help you ?

softworkz said:
Hi Guys,
there is already a new version of ER2003Edit (not published yet!!!) which can open .nbf files of Qtek 2020i. The only problem is with checksum calculation. I am using Itsme's Perl script, but it has a problem calculating the checksum and he didn't have time to fix it yet.
Anyone else...?
Click to expand...
Click to collapse
PLs if it has been updated then let us know we are eagerly waiting for it.
thx a lot
jeet

Editing MUI files - error in phone :(

When I edit some MUI files (from SPV C550), for example "tshres.dll.04XX.mui" it looks ok... but not in phone.... it shows sometimes some mistakes like the one on the attachment I have uploaded.
Maybe someone knows how to fix it? It hapens only on few files but they are necessary to finish a langpack I create
I am looking forward for your help and thank you very much in advance!

Are you editing on your computer and then uploading it to the PDA (the normal way of developing apps)? If so then it has to do with your font & language pack. Your computer has probably got your languages of choice installed, and you also probably have the appropriate fonts on it as well - but are they on your PDA? If not, then that would explain the box that appears once you port it to the PDA (which basically just indicates that the font that is installed on the PDA does not have that particular character for that language). I don't know how you could overcome this, except to take your computer font and convert it/import it to the PDA. Hope that helps!
Black-wolf

The phone supports all Polish characters... this is not because of this....
It happens even when I open the original english mui file and just save it in ResHacker (or any other program).

ROM COOK WANTED: SecureROM!

Hi Cooks! I need some help from you :-D
I want to know my data secure and possible stolen hardware findable/trackable. And all this WITHOUT changing daily workflows!
My idea is a special "SecureROM" which should contain additional to normal ROMS:
o callFirewall (with Autostart)
o remoteProtect (ATTENTION: individual CAB!!)
The idea is to put remoteProtect (i think its much better than UTA V3 and friends) directly into the ROM. So a thief cant simply hardreset the device (and cancel Ext-Rom installations) and we have the first real secure PDAphone:
o PIN Code for logon activated (5mins idle)
o Storage Card encryption on
o remoteProtect installed
o Bonus: Callfirewall for blocking anonymous phone calls
When the device is lost / stolen - the thief (finder) has the possibility to give it back: Your name / 2nd phonenumber is on the PIN-Loginscreen AND on the remoteProtect lock-screen.
If he DOESNT want to give it back - you can remotely lock, wipe and kill the device.
If you dont know where the device is - you can get information about inserted SIM, IMEI, IMSI (police-tracking) and battery status.
If the thief chances Ownername or SIM - you will be notified and can react.
The thief cant bypass the PIN to get into WM6. He cant pull out the storagecard and get it into a cardreader... because all files there are encrypted with AES. If he softresets - he is still locked. A hardreset will make all informations gone - even those on storagecard - and with remoteProtect in the ROM he will STILL be trackable!!
SO: With this configuration you can feel your data on your device pretty protected... and even your hardware keeps trackable with one exception: When the thiefs flashes an own ROM.
So if you like this idea dear Chefs - could you give it a try and find out how to implement remoteProtect into your ROMS?
PROBLEM: For this issue, you would have to add the possibility to add an individual cab (which is configured and built by the remoteProtect installer BEFORE COOKING) right before flashing. (here is remoteProtect for testing purposes: http://www.scpsoft.com/remoteprotect.htm [Attention MODs: This is NOT a WAREZlink!])
HINT: If using UTA (second best solution) instead of remoteProtect you will have to insert two configfiles (1 XML and 1 txt - File) individually before flashing.

licht77 said:
Hi Cooks! I need some help from you :-D
I want to know my data secure and possible stolen hardware findable/trackable. And all this WITHOUT changing daily workflows!
My idea is a special "SecureROM" which should contain additional to normal ROMS:
o callFirewall (with Autostart)
o remoteProtect (ATTENTION: individual CAB!!)
The idea is to put remoteProtect (i think its much better than UTA V3 and friends) directly into the ROM. So a thief cant simply hardreset the device (and cancel Ext-Rom installations) and we have the first real secure PDAphone:
o PIN Code for logon activated (5mins idle)
o Storage Card encryption on
o remoteProtect installed
o Bonus: Callfirewall for blocking anonymous phone calls
When the device is lost / stolen - the thief (finder) has the possibility to give it back: Your name / 2nd phonenumber is on the PIN-Loginscreen AND on the remoteProtect lock-screen.
If he DOESNT want to give it back - you can remotely lock, wipe and kill the device.
If you dont know where the device is - you can get information about inserted SIM, IMEI, IMSI (police-tracking) and battery status.
If the thief chances Ownername or SIM - you will be notified and can react.
The thief cant bypass the PIN to get into WM6. He cant pull out the storagecard and get it into a cardreader... because all files there are encrypted with AES. If he softresets - he is still locked. A hardreset will make all informations gone - even those on storagecard - and with remoteProtect in the ROM he will STILL be trackable!!
SO: With this configuration you can feel your data on your device pretty protected... and even your hardware keeps trackable with one exception: When the thiefs flashes an own ROM.
So if you like this idea dear Chefs - could you give it a try and find out how to implement remoteProtect into your ROMS?
PROBLEM: For this issue, you would have to add the possibility to add an individual cab (which is configured and built by the remoteProtect installer BEFORE COOKING) right before flashing. (here is remoteProtect for testing purposes: LINK REMOVED
HINT: If using UTA (second best solution) instead of remoteProtect you will have to insert two configfiles (1 XML and 1 txt - File) individually before flashing.
Click to expand...
Click to collapse
Paranoid much ?

Probably an IMO for the US Govt somewhere. They are worse than Nazis. That is why I ditched my issued blackberry for my Hermes.

Well, I think that this is not much paranoid.
I spent for my PDA over 700 euros, so if it is stolen it isn't very good!!! ;-)
For this reason, I bought a legal copy of UTA (Ultimate Theft Alert v.3) and I updated my Schap's 3.30c ROM with all necessary files from the original "UTA v3.CAB" (no Config, only program, dll, and configuration and license files...).
It seems to run very well!!!
Today, after reading this thread, I tried remoteProtect, but I don't like it so much, because if I send a SMS to my PDA, then the theft will see it and can go to flight mode.
If you want to do the ROM upgrade, you must choose your preferred ROM. After, I suggest the "CorePRO_HermKitchen.exe", that contains all the tools you need, with a tutorial about dumping and cooking your ROM.
If you need help, I'm here!
Bye Bye.

I think it's a good idea - I used to work in the Netherlands and on an emergency trip home one weekend, my phone was stolen by someone after my luggage was checked in at Schipol (it was the first HTC Canary smartphone, actually ) Anyway, I didn't notice that it was missing until I got back to NL 4 days later as I thought I'd just missed it in my rushed packing, but in that time, the thieving toerag had run up a £650 phone bill (it was stolen in NL and I got stiffed for roaming charges too
So anyway, I'd be interested too
Smiffy.

@NRGZ28: Yes - I am really paranoid... - this comes with the job
But as Mobilez6600 states correctly - its a question of hardware value too...
@Mobilez6600: Ill have a look into CorePRO_HermKitchen.exe - all I played around so far was Bepes Kitchen... there was no howto and i just cooked a german ROM - i think i was just lucky
Ill give it a try - but if there is a tutorial anywhere i would be glad!
greetz, licht
PS: On my installation the thief cant see the incoming sms... ?

Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez!

JasenR said:
Speaking of thiefs...the link in the OP is to a known warez site. XDA Developers does not tolerate warez![/QUOTE
Dont get your panties in a bunch...
Click to expand...
Click to collapse

NRGZ28 said:
Dont get your panties in a bunch...
Click to expand...
Click to collapse
Thanks NRGZ28, I guess, for your concern about my comfort, everything is fine in that department.
Even more thanks to the mods for their continuous efforts in keeping this site warez free.

@Mobilez6600: Thx for your informations!
I read into Core Kitchen, dumped my preferred rum (Schaps 3.30c german) and created a package out of the desired cab according to theese snippets from the forum:
I don't know if the new Office will work on other builds....
Sorry i can't be more specific...but i didn't tried it so far. So i can't tell you what files to copy or if it will work.
Just try and if you get it working...then you could share that with us too.
I am in the middle of something now and can't try this now....Hope you understand.
Regarding on How to make a package....
* Take a CAB
* Open it with CabAnaliser ...in Extra folder
* Select the XML tab...there save the registry settings in an unicode txt file.
* Extract all files
* Place all files in an folder , and add there an .dsm and rename the previous txt file in .rgu ....assign both the .dsm and the .rgu an UUID (both same UUID)
* Run the initflashfile generator...in Extra folder. Follow instructions...
* Place the generated "initflashfiles.txt" in the same folder you placed previous files
* Give a friendly name to your folder , move it into the OEM folder and pray it will work.
That's it. If you read previous posts you'll know what an .dsm is and how to make one and what is an UUID and where to get it from.
- TIP : If that doesn't work, open the initflashfiles.txt and replace all the "squares" with an tap on ENTER button....It's easy to check the initflashfiles.txt than to create it without that program, trust me.
to create a .dsm
* Create a new empty .txt document
* Go here http://www.famkruithof.net/uuid/uuidgen/ and create a "RANDOM" UUID (example of UUID :2981dd18-0f2c-11dc-8314-0800200c9a66)
* Rename the *.txt into 2981dd18-0f2c-11dc-8314-0800200c9a66.dsm (the UUID is only for example, create your own)
* If you have registry settings, use THE SAME UUID ...so for example rename the *.reg file into : 2981dd18-0f2c-11dc-8314-0800200c9a66.rgu
Click to expand...
Click to collapse
So far - so good. Additionally, a single txt file needs to be copied into rootfolder of the device before installing my custom cab... i put it into rootfolder of the cab for testing.
Unfortunately i get an error during build_os: "Could not find file d:\core\kitchen\temp\dump\Program Files\imageinfo.bin" when build_os is processing my created folder in OEM.
Any advice is highly appreciated...

There is a .DOC tutorial about dumping and re-creating ROM in CorePro_HermKitchen. I used it and I only inserted my files in a folder. After, I modified "initflashfiles.dat", to copy a link in \Windows\StartUp directory, so UTA could run automatically on soft-reset (and hard-reset ;-).
I don't know if it is right way, but it runs, and I'm happy!

Sorry for my late answer, i was - ehm unavaliable - some days.
You are talking about initflashfile.txt and not .dat right?
I still get this error, but i will keep working on it

Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:
PAPPL said:
See this great theft protection Peter Poelman made here at xda-devs!
THIS WOULD BE GREAT!
IIWPO WIKI
IIWPO Thread
Click to expand...
Click to collapse
I tested that tool and found it great too - but it has no SIM detection. Another con is that its in extended ROM which can be easily bypassed by canceling the installation after a hardreset.
After excessive tests with all those tools i have this personal ranking:
1. remoteProtect (commercial, Trial avaliable) pro: a lot of useful commands executeable via SMS, device completely killable, recognizes SIM card change (supports 2 SIMs) as well as owner name changes. Needs 1 txt file as config in the rootfolder during installation when included into a ROM.
2. UTA v3 (commercial Trial avaliable) Recognizes SIM change (supports several SIMs), sends SMS. No SMS commands possible. Optionally (commerical plugin) sends contactlist too. Needs 2 individual files included in ROM.
3. IIWPO (free, xda-dev)
Recognizes change of owner name. Needs 1 individual file included in ROM. No SMS commands possible, no recognation of SIM change.

What prevents a reflash with different rom?

nothing i am afraid... as there is no lockable bootloader
But i think its much easier for a thief to hardreset than to flash... the "flashers" are rather an exception i hope.
If you have any idea to lock the device with the bootloader - tell me

licht77 said:
nothing i am afraid... as there is no lockable bootloader
But i think its much easier for a thief to hardreset than to flash... the "flashers" are rather an exception i hope.
If you have any idea to lock the device with the bootloader - tell me
Click to expand...
Click to collapse
im sure if you had a quick talk to Olipro about the bootloader... he might be able to help you out with a BL that wont allow you to flash without a special CID...

licht77 said:
Quoting from http://forum.xda-developers.com/showthread.php?p=1373052#post1373052 to keep that thread on topic:
I tested that tool and found it great too - but it has no SIM detection. Another con is that its in extended ROM which can be easily bypassed by canceling the installation after a hardreset.
After excessive tests with all those tools i have this personal ranking:
1. remoteProtect (commercial, Trial avaliable) pro: a lot of useful commands executeable via SMS, device completely killable, recognizes SIM card change (supports 2 SIMs) as well as owner name changes. Needs 1 txt file as config in the rootfolder during installation when included into a ROM.
.....
Click to expand...
Click to collapse
@licht77: remotePROTECT is great. But how to install the 1txt file in root folder? Will this survive a hardreset?

Hi Pappl!
Yes, it should survive a hardreset... thats why i dont want to put it into extRom (because the installation of all the extRom - stuff can be cancelled too easy by a hardreset followed by a softreset after screen calibration) but in ROM itself.
This way you have a) your data pretty secure and b) may track down a possible thief. The only thing a (skilled) thief could do is to completely reflash the device (but if he is curious before and tries to access your data with his SIM or so... hehe then u got him)
Like walshieau proposed, it should be possible even to block a complete reflash of the device by a custom booloader - but i dont want to nag olipro before the other tasks are finnished. In that case a stolen hermes is really useless for the thief... and thats a nice idea if this could prevent theft

remotePROTECT can be installed without that text file to the root folder, you just need to set it up first, and extract the setupE.txt file from it's running folder then rebuild it into that folder from the cab file.
I however would like to do this without the cab, cab's can be prevented from running by simply softresetting during that phase of the setup. I have built all the files into one of my roms and put in all the registry entries however the application does not work this way! Setup.dll seems to do some important things and I'm not sure what.
Anyone have any ideas? I'm gonna email the author asking.

You are right... didnt see that encrypted "setupE" file...
Which kitchen are u using? What were the steps u did until now? I am sure we can solve this!

How to fake TRIN100 name for PPC software

Guys,
maybe here someone will help me.
I have company software for my HTC3600 that checks for device name.
The one that is shown as TRIN100 for Trinity for my WM6 ROM.
Maybe you are familiar with the soft that can accept request for this info and give to a program fake name like ABCXYZ?
In other words can you advise something that will allow the attempt to run software designed PARTICULARY for another WM platform?
Thanks for any advise!

First check what have you got in Start->Settings->System->About. There is Device ID Tab.

sorry for misleading
I meant
Start - Settings - Device Information - Identity - Model No.

sand2006 said:
sorry for misleading
I meant
Start - Settings - Device Information - Identity - Model No.
Click to expand...
Click to collapse
I think only try to find "TRIN100" in nbh file with hex editor and change it in some else and then flash on a device, I only in nbh file found the string... no in registry, and in provxml files!!

ervius said:
I think only try to find "TRIN100" in nbh file with hex editor and change it in some else and then flash on a device, I only in nbh file found the string... no in registry, and in provxml files!!
Click to expand...
Click to collapse
yes
that is the straight way
two possible objections
1. if name TRIN100 is used for some low level functional device will not be useful at all )
2. reflashing of this may give nothing only because TRIN100 is hardware name (i am still guessing)
so, the last option is clear for hacked nbh file
but maybe someone has seen software that catches request for this info and substitutes it with any string for calling software?

Asus P525 NB0 Kitchen by Anper

russian version can be found on:
http://asusmobile.ru/board/viewtopic.php?t=7816
version 080302_1843
This is english translated version of tool for editing of P525 ROM made by Anper.
Sorry for not so quite good english.
Additionally attached utilities for preparing of GIF "AsusP525GIFConverterByMrToto.zip"
About util KitchenNB0.exe:
Warranty: not any, only can say, that not especially include any harmful code to that utility. And before new version posting was firmware changes in mine PPC that made by that util.
don't known if that util works on other models (don't have it), it's tested only on my own ASUS P525. Flashing was made only thru USBloader.exe (don't knew how - read asusmobile.ru or anywhere in other places).
On mine device installed unchanged bootloader from WM6 official.
On WM5 was tested process completion on pc, but without real tests on pocket.
That Utility allow process images ROMGalaxy.NB0 and Galaxy.NB0
(Advised to use ROMGalaxy.NB0 (withiut bootloader), as more safe variant for Your device).
That images can be got by decoding of Galaxy.cap (decode can be done from that util).
First part of tool allow split to parts, and correcterrors in CHS, cut off bootloader, unpack galaxy.cap to ROMGalaxy.nb0 (used data from tool made by Ingvarr).
Second part allow you process IMGFS partition (partition that contain main
software). In that part partition IMGFS can be extracted to file. Get from that DUMP (in future You can do anything you want with that). After that combine DUMP to IMGFS and at the end combine and recalculate checksum of NB0.
splitting and combining functions of IMGFS to DUMP and back executed by Tadzio made utilities. But so they is made for HTC devices, so I'm correct that accordely to ASUS specific. That functions is called from mine tool (execute bat files is not necessary). Correction may be done by pressing button CORRECTION. ROM size is REALLY CHANGED WITH DECREASING OF nb0 image and accordely to size User storage INCREASED - checked (by recompressing of misar firmwares and by other firmwares corrections).
Checksum calculating made is done by tool, but algorhitm is taken from Ingvarr tools (slightly modified to this tool, that does not create all of file image in memory, but recalculate by chunks).
Process ROMs can in different directories, for no all in one place files garbage.
To flash ready file I'm advise thru bootloader and exactly ROMGalaxy.NB0 (without bootloader). Existence of bootloader you can check in first part of tool.
In that complect persist other tools, needed for coocing your rom.
But accordely to them - you must teach it yourself. I'm don't made that.
Also added in third part possibility to change any of parameters in XIP part of ROM (for correct processing parameters must be changed in order: firstly unpacking, changing, packing, and combining NB0).
Work examples:
1. Open NB0, if that not persist - make it from galaxy.nb0 (by cutting off of bootloader) or from galaxy.cap.
2. If that is homemade firmware, possible will be CHS error in MBR. Correct that by pressing button CORRECT MBR. (Why error persist? - Possible our firmware makers ignore that, or firmware was combined by utilities from Tadzio or other that was not adopted for ASUS (also possible CHS not so sensitive)).
Also may appear message about file size differences with sum of sizes of all partitions - it's not harmful - in most cases simple ignore that.
3. Next is Operations with IMGFS tab. In that part can simple do next processes in shown order. Get IMGFS, Create DUMP, edit DUMP as you wish, from DUMP create IMGFS, combine NB0 new and it's all, can flash. For checking you may open newly created NB0 in first part of tool.
4. Flashing may be done by USBLoader.exe.
Another example - correction and optimization of firmware size:
Shortly about compression:
I'm has provided an opportunity to combine IMGFS.new from DUMP with LZX compression (greatest, but slower starting) and XPR.
Choose by pressing needed button. At once want to warn you about not all firmwares have library with compression LZX, accordely to that after flashing, it will not run further to blue screen.
If you have not broke bootloader, this all is reperable (Many peoples through it passed).
Well, like everything, write at a forum.
And a long life for yoursdevices.
P.S. if you found translation errors - please PM to me.
20080303
Translation fixes, exe packed in own archieve as mainly only it changed
1. unpack kitchen ASUS_P525_NB0_Kitchen.zip
2. place ASUS_P525_NB0_Kitchen.exe from exe.zip to directory from 1.

Thanks DaLiV.
Thanks anper.
Great tools.
Wait for Eng version for a long time.
vivi

thanks anper & Daliv
great tools, Great work!

updated translation.

thanks!
Thanks DaLiV, anper!!
Have been looking for the English version!!
gabz

nice. looks interesting.
will give it a try.
but will it work using wm6/wm6.1 as base ROMs?
cheers!

ericjm said:
nice. looks interesting.
will give it a try.
but will it work using wm6/wm6.1 as base ROMs?
cheers!
Click to expand...
Click to collapse
tool work with WM5, WM6, WM6.1 only for ASUS P525.

anper said:
tool work with WM5, WM6, WM6.1 only for ASUS P525.
Click to expand...
Click to collapse
sweeeeet!
thanks for this one anper (and DaLiV for the english translation!)
can't wait!

How
How can we add additional OEM packages into our rom using this kitchen?

as in all other roms ... split by packages by other tools, if you want, but to that tool return ready dump directory

sorry
DaLiV said:
as in all other roms ... split by packages by other tools, if you want, but to that tool return ready dump directory
Click to expand...
Click to collapse
Sorry, But I cannot understand what you mean. Could you please elaborate?

search forum for tool like "buildos+packagetools" or "dmp2pkg" - then edit packages and after that make conversion back packages to dump

Sweet kitchen
Just letting everyone know that this kitchen can also be used for Dell Axim X51's - I have
For X51 users, make sure you don't click "Repair CHS" - it's for ASUS PDAs only and will result in a bricked ROM
btw You can also use recookstruct as well to sort the dump into packages, you may have to get rid of some entries in "HKEY_LOCAL_MACHINE\System\Inbox\Settings\WelcomeEmail\Templates\ServiceTemplates" because recookstruct can't parse the "®" symbol sometimes found in the key
(Only works with IMGFS, not XIP)