Hi,
unfortunately I am not able to implement a new *provxml to a new ROM.
I know http://forum.xda-developers.com/showthread.php?t=398025
and some other threads, but all my entries (Mailaccounts, WiFi informations - which I got with rapiconfig) are not in my new ROM.
I am doing somewhere a mistake. It does not work:
I have done the following:
1. created an acconts.provxml
2. renamed to _setup.xml
3. Created an OEM package with Ervius Package Creator.
Have now 5 files in the OEM folder: _setup.xml, *.rgu, *.dsm (size 0k), option.xml and initflashfiles.txt
4. Moved option.xml out of the OEM folder
5. Drag and drop OEM folder over BuildDSM.exe. This creates a new *dsm (size 1k)
6. place back option.xml in OEM folder
7. copy OEM folder under \Packages - i have tested also the OEM folder
8. cooked and burned ROM
Does someone has a OEM package with a *.provxml (including email2 and wi-fi infos). All imported emai-addresses and wifi info van be deleted of course. ?
If I use "rapiconfig.exe /p _setup.xml" all my infos are ok.
Any help is welcome.
Regards
kuzco1
this is what works for me...
you have to name it:
mxipupdate_zz_oemoperators_100_PPC+All_filename.provxml
you can replace 'filename' with whatever you wish.
(there should be no space in provxml, this editor isn't working right for some reason)
let us know if this works for you...
joemanb said:
this is what works for me...
you have to name it:
mxipupdate_zz_oemoperators_100_PPC+All_filename.provxml
you can replace 'filename' with whatever you wish.
(there should be no space in provxml, this editor isn't working right for some reason)
let us know if this works for you...
Click to expand...
Click to collapse
Hello,
what do you really mean ?
I have renamed my _setup.xml to mxipupdate_zz_oemoperators_100_PPC+All_filename.provxml and put this file \OEM\OperatorPKG. After cooking and burning my Kaiser does not boot any longer - I have to reverted to my old ROM.
Regards
kuzco
have you tried creating a cab file with your _setup.xml?
see if that works, maybe your xml has errors.
as far as creating a dsm, all I did was drop the file into another oem folder that already had some provxml files.
the fact that your phone won't boot now would indicate to me that after the filename change the file is indeed being processed, but the xml has errors.
download the 'tmobileforromcooks.zip' file in the following post and compare the provxml files with yours.
http://forum.xda-developers.com/showpost.php?p=2237367&postcount=1
good luck
joemanb said:
have you tried creating a cab file with your _setup.xml?
see if that works, maybe your xml has errors.
as far as creating a dsm, all I did was drop the file into another oem folder that already had some provxml files.
the fact that your phone won't boot now would indicate to me that after the filename change the file is indeed being processed, but the xml has errors.
download the 'tmobileforromcooks.zip' file in the following post and compare the provxml files with yours.
http://forum.xda-developers.com/showpost.php?p=2237367&postcount=1
good luck
Click to expand...
Click to collapse
Thanks, but this zip does not work either. I will play more ....
kuzco1
hint hint: Try adding these settings to an already existing prov.
as i read somwhere you cannot add any provxml file in a dumped rom! but u can change and add reg edits in an existing provxml file. and theres another thing i think you should know: provxml files are the last reg based files that will get written in the cooked rom SO they have the ability to change and overwrite rgu files that you created if they both have the same reg path but diff values.
I finally found a way to overcome space issue that cause BuildIMGFS throw error when you put too many files in the ROM using captaintrip's kitchen
The repack used imgfsfromdump instead of buildimgfs which avoid the size issue and in additon can reduce the final size of flash.dio
The usage are the same with captaintrip's kitchen, I only rename the bat to "iPAQ61x_91x flex kitchen" since this works for both 61x and 91x
You will need to rename flash.dio to TEMPLATE.ROM and put it under ROM folder, when you run iPAQ61x_91x flex kitchen.bat it will also prompt you,follow instruction
keep in mind if you use flex kitchen to build your rom won't be able to extract it properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
use iPAQ614c Rom Kitchen.bat if you want to build your rom in old way
Updated July 7th: attached new cecompr_nt.dll that fixed memory leak, necessary for LZX compression, replace the one under TOOLS folder
Download (v0.3):
mediafire
Updated: Dec 9th ,09
v4 Beta:
-improve ability to decompose ROM, however the packages in SYS and OEM portion is usually mix up so you have to manually move them to correct folder after extraction
Download:
21501 kitchen
21215 kitchen
Rom folder for w version for 21215 (Rename it to ROM if you want to build w version)
21232 kitchen
21234 kitchen
21725 kitchen - removed due to too many issue, use 21728 kitchen instead
21728 WWE Kitchen
21728 ITA Kitchen
21728 GER Kitchen
21728 FRA Kitchen
21812 WWE Kitchen
21815 WWE Kitchen
23001 WWE Kitchen
23001 CHT Kitchen
23004 WWE Kitchen
21921 WWE Kitchen
23009 Hybrid WWE Kitchen
23016 18.1 WWE Kitchen
21854 WWE Kitchen
23047 WWE Kitchen
23052 WWE Kitchen
21867 WWE Manila 24M2 Kitchen
21869 WWE Kitchen
21869 WWE Manila 25M Kitchen
23088 WWE Kitchen
28002 WWE Kitchen
28011 WWE Kitchen Beta 29
28011 WWE Beta 29_2 Kitchen - kitchen of Beta 29.2
note: you can replace WinCENLS_Lang_0404 with WinNLS_WWE (from other rom kitchen) to save ROM space
-arcsoft streaming player & codec can be removed if you don't need them
23515 xip (use with 23518 SYS)
23518 CHT Kitchen (LZX)
23518 WWE kitchen
21888 WWE Kitchen
23529 WWE Kitchen
28230 WWE Kitchen
23544 WWE Kitchen
23563 WWE Kitchen
91x 28011 WWE Kitchen -not tested since i don't own 91x device so use as your own risk, use dnw in the worst case
91x 23518(23515)/21888 untested xip
Official WM 6.5 Tookit/SDK/Emulator: here
FCC Information for 610c
FCC information for 910c
----------------------------------
Structure Overview
XIP is the kernel, this is also what you see those 2xxxx build mean, the whole term is called "Execute in Place", i.e execute files in rom directly without copying to ram, this is for boot process, anything wrong mean you will stuck in clean boot
OEM is for device/manufacturer specific program/drivers
SYS is for Windows Mobile system files
A package is a folder with at least a dsm file,all other files are extra
-rgu file is just reg file which you can use notepad to edit
-default all files goto Windows directory (obviously exclude rgu file)
-initflashfiles.dat/txt is a text file with instruction to move files to different directory
Files vs Modules
Modules are folder with ".dll" in their names. Inside the folder there is imageinfo.bin, S00X where x is a digit. When they are cooked into ROM they will become dll with proper relocation (done by WMReloc/G'Reloc). Supposedly being modules would make them load faster(because no need to relocate at runtime?) and some dlls must be in modules or else some program will not work properly. However there are also cases that modules must be converted to files.
Technically you can put everything in SYS since at the end buildOS will merge everything together but it is easier to manage if you follow the OEM/SYS structure
Common Issues TroubleShooting
hang on 1st boot screen (HP Logo)
-XIP porting issue, .rom , .vm file not correct .etc
hang on 2nd boot screen (WM splash screen)
-module did not relocate properly (did you run WMReloc or GReloc?)
-XIP (lower possibility, i don't think it affect..just in case you should keep in mind)
hang/crash on today screen
-software conflict/missing .etc , check your SYS/OEM files
Endless HP update/customization engine
-happens because of different model uses different customization engine, using one from other model/region will cause it to rerun every boot time, the only solution seem to prevent it to run from start by removing it from initflashfiles.dat. Convert all the fix into packages and integrate to the rom instead
installed SIP(virtual keyboard) cannot be switched
-use recmod (under tools folder) to convert all modules into files in browsingie folder
cannot compose new sms/email .etc
-replace redist_lang_[lang_code] folder with one that worked before
wifi cannot turn off after boot
-set HKLM/Comm/SDIO86861/Wireless to 1
XIP
To insert ported xip, run this command: osnbtool -c TEMPLATE.ROM 1 xip_out.bin
where xip_out.bin is your new XIP file
xip porting tutorial can be found all over the place in xda/ppcgeek .etc
Also make sure in ROM folder, the boot.rgu is from your device xip (the kitchen I provided only contains 61x xip so to cook for 91x you need to put 91x boot.rgu instead)
Phone Radio
rilgsm.dll is needed but usually it is in OEM folder
PagePool
Overview: xda wiki
edit using pagepool_by_wlodixon under flash folder, copy your flash.dio and run the appropriate cmd
The only exception is if the rom set pagepool to 0 (Dynamic PagePool), it won't able to recognize and you have to hex edit
hex edit the xip.bin at 0x000A75E4, change all 4 bytes to your desired value (all 0 for dynamic pagepool)
Convert cab to OEM
get package creator here
use it to open cab, then wince cab analyzer opened, choose extract folder icon, after close wince cab analyzer, you will be present with shortcut screen, do you things and hit done, finally hit complete package unless you want to change some option
Create simple cab for file/reg changes
get QuickCab
Xt9
corresponding lang files in OEMApp/OEMLang_#### where #### is the 4 digits lang ID
-[2letter langs code]hpd.ldb
-[2letter langs code]lbUN_xt9s/lsUn/.etc].kdb
-et9.SQR.[Language].bmp [Optional, some language like Polish/Portuguese just point to english bmp in registry]
-[a bunch of number/digit known as GUID].rgu (if you open it up you will find there is registry on xt9)
also under OEM\OEM_Lang_[Lang number]
-initflashfiles.dat (actually you can use notepad to open it and seacrh for ldb/kbd/bmp to see which lang files )
cooking different language
-you will need your language OEM folders from original HP rom
-your language wince.nls
-replace all language mui (e.g 0409=English) with your language mui
-some languages may added extra folders, be sure to copy them into SYS too
-sometime the hp customization/update will end up endless run in every start, in this case you will need to prevent it from running and integrate all updates into the ROM
OptionXML Addon
I have written this small .Net 3.5 App to generate option.xml for SYS packages which will allow you to select the common package and different language more easily without moving folders all the time, just unzip the zip to kitchen which will overwrite the existing batch file and put the exe under TOOLS folder.
To select/UnSelect a category in BuildOS, you can click on the Category group (e.g click on 0409 will select all 0409 packages in SYS), then click on one of the packages will select/unselect the whole group
Reserved for extra space in case
-------------Step by Step guide for xip porting-----------------------
Make sure you read this tutorial first
1. copy(either get it from kitchen or dump it using osnbtool) the existing xip_out.bin and rename it to xip.bin, open xipport, click dump xip.bin and you will get a OUT folder
2. choose write map then make packages , now rename this out folder to some other name
3. dump the new xip(from other device) using osnbtool, rename it to xip.bin & do the same as step 2 with xipport
4. now copy MSXIPKernel & MSXIPKernelLTK under Modules and Files folders from OUT folder(from step3) and overwrite to corresponding 61x OUT folder(from step1)
4.5 as said in the xda tutorial, remove hd.dll, osaxst0.dll folders and their corresponding text files under modules to avoid physical address overlap
5. use xipport to undo and then realloc and write maps. Then you check map files to make sure there is no !!!(memory address overlap) I recommend using XIP address tools to check for overlap, sometime you will get error when you realloc (key already exist .etc), use xip address tool and set work folder to OUT then you will see error on first dll addr which you have to fix all highlighted red cell(overlapped address). Note that to fix first dll addr address you have to highlight the cell, enter the new start address on the V address cell in bottom, click modify, then use mouse to highlight the 1A cell above, and change the D address cell to the same as V then click modify button(on the right of V cell). You should see the change in table then. For virtual base overlap you only need to modify V cell only
Note: first dll addr overlap will result error when you click realloc in xipport.
The goal is have no overlap as shown in MAP.txt. When there is no more overlap, use xipport to build xip_out.bin and then insert the xip into the dio file using osnbtool
Commands:
extract xip: osnbtool -d flash.dio 1 xip.bin
insert xip: osnbtool -c flash.dio 1 xip.bin
also make sure your ROM\boot.rgu is from your device xip
-----------------------------------
IPAQ 91x boot keys:
Clean bOOt - Voice Commander + OK + Reset
Download Image - Volume Down + OK + Reset
Calc Checksum - Volume Up + OK + Reset - disconnected, SD card out
RUU - Volume Up + OK + Reset - UsbConnected, SDcard out
SDloader - Volume Up + OK + Reset - USB disconnected,SDcard in SDloader
Modem_CAL - Voice COmmander + Volume Up + Reset
Diagnostics - Voice Commander + Volume Down + Reset
-------------------------------------
LZX Compression:
The default compression algorithm for ROM is XPR, if you must include lots of files that causes your resulting rom >80mb under XPR(81920kb - ROM Size limit for 61x, bigger than this the device won't boot), you need to use LZX compression. It reduces rom size by ~13% but with ~1-3% performance hit(from other post I read, I never verify the performance hit).
To use LZX compression, you need to replace the cecompr.dll folder in XIP Modules with the one attached in this post. Re-port the xip (realloc + write map + build xip_out.bin) and then use osnbtool to inject the xip inot TEMPLATE.ROM.
Then hex edit the imgfs_raw_data.bin in the rom kitchen, replace the first string "XPR" without quote you found with "LZX" without quote.
Make sure you have replace the cecompr_nt.dll under tools folder of the kitchen with the one I attached in 1st post to avoid memory leak
Now just build normally, you will notice the time to inject file will take much longer because of the compression
Is there any ROM kitchen tools for hp iPAQ h6365 WM2003?
Wow great kitchen. Thanks for sharing.
here, here! keyx you da man
One thing though - when you say this:
Phone Radio
if you are using SYS from other device, make sure you replace ril.dll and phone.dll from a working rom in phoneRedist or you will get a phone radio not installed which disable phone function
rilgsm.dll is also needed but usually it is in OEM folder
Click to expand...
Click to collapse
I'm not sure that is actually correct. I've been using ril.dll and phone.dll from all kinds of donor SYS; these are OS files that should be generic. It is only rilgsm.dll that is manufacturer-specific.
you are right, I corrected the post
I think I do anything wrong...
If I extract your ROM(WM 6.5 Beta 3.81) and put it together to a ROM again, it is 10MB smaller.....After extracting this, its 1MB smaller...
Question is, why?
Greets
chucknican
actually for unknown reason if you use my kitchen to build rom, you won't able to extract it properly...i am not sure why. But currently it is the only solution for me to overcome buildimgfs error
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
chucknican said:
so the solution is that I use captaintrip's kitchen to extract and yours to build it together again?
Click to expand...
Click to collapse
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
benjaminries said:
I can't get this kitchen to build my ROM. The after WMReloc does the modules rebase, I get the following feedback...
Code:
Injecting files ...
Input file imgfs_raw_data.bin cannot be opened. Exiting.
In fact, when I watch the temp folder during this process, I see no imgfs_raw_data.bin at all. In your new script, I can't see where this file would come from anyway.
Help?
Click to expand...
Click to collapse
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
keyx said:
no in fact i will need to upload a kitchen as the result rom using my flex kitchen will not be extracted properly
you have to run "prepare_imgfs flash.dio -nosplit" to get the imgfs_raw_data.bin first, this process is done when you extract a rom before but if you just directly use it to build a rom you need to manually run the command on a flash.dio first
Also keep in mind if you use flex kitchen your rom won't be able to extract properly, anyone want to edit your room will need your kitchen instead. If you don't have buildimgfs issue you may want to stick with the old way of building rom
Click to expand...
Click to collapse
So... these files go in the root folder? That's what works for me anyway. Hmm... I think this could be easily added to the script, if you ever have to release an update to the kitchen. Anyway, thanks.
21501 kitchen added on 1st post
EDITED: kitchen updated to detect missing of imgfs_raw_data.bin and extract it automatically, I also updated some tools versions
ADC and Ipaq Data Connect
Are both of these necessary? When both are installed the ADC seems to run first and configures a "Proxy Internet" Profile in the Connection Manager which lists all 3 possible connections for my data carrier, even though I can only use the internet2.voicestream.com with T-Mobile. Maybe I am not using this correctly, but once I removed the ADC, the ipaq data connection worked fine and I was able to connect to the internet without a problem. Is this all this app does, or is there another usage that I should leave it installed for?
Thank-you
you can remove ADC if you don't want it, i think it just help to setup data connections
Customization
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Where do you test the new roms? In the device or in somekind of emulator?
gkleding said:
Keyz
I have removed some of the OEMs from the kitchen, but am not sure that I modified the initflashfile.dat correctly,will you look at it for me and see (I highlighted what I have removed)? If I remove the entire last 3 lines that contain the Utility file the device does not reboot from sdlauncher when installing. When I leave the last line in it is very speedy to install and reboot, but I have the empty utility Folder in my programs folder! I also had tried to add the BSPropCab.cab to the OEM folder but cannot get it to install correctly. I saw that you had it installed in one of your previous roms along with the other 2 arc cabs. The arc cabs I can get to work, but I really dont want to put them in, just the bsprop. Is this possible?
In OEM I added Coreplayer, PdaNet, SKTools5, Live Search, Google Search and WM5torage1.9. I had to add Google Search in here because I could not get it to work by adding the original files back into the OEM App folder: In Systems I removed ADC, VOIP and One Note, replaced NETCF with NETCF3.5, and added Transcriber back in. I thought about removing WMWidgets, I use all SPB Software, but I dont understand all of its functions, I have Googled it and there really isnt alot out there about it. What I did find though makes me think Microsoft will add more function to it once the official 6.5 is officially released-So I will keep that. For me this is a very good ROM, you have done an excellent job with modifying the kitchen.
Thank-you
Sunday
Click to expand...
Click to collapse
what do you mean by bsprop not installed correctly? if you convert it to OEM folder correctly it should work but if you leave the customization engine run on startup there is no point to preinstall bsprop since it will reinstall again from ipaq file store(unless you did not install the update before).
Also if you modify initflashfiles.dat i believe you should use hex editor to remove the FF FE header added by notepad.
Sometime when you flash a lot the device will act weird & does not reboot from flashing, you can try to clean boot it or reflash. I think you can remove all highlighted entries without issue. You may need to leave a blank line at the end of file though.
wmwidget is a widget engine that can run apps that use pie as a container/interface, for me it looks kinda like a shortcut to a webpage, msn weather/money .etc are the sample widget come with 6.5 for now. You can remove it if you don't use it.
SwimmerBoy said:
Where do you test the new roms? In the device or in somekind of emulator?
Click to expand...
Click to collapse
device only until i figure out the emulator issue
I'm still learning here and have been looking into registry settings. I've tried editing the default.hv, and while rgucomp says it builds fine, this results in the ROM not booting.
If I look at the rgu from the modified default.hv, its in a different order than the original.
Just wondering if I need a different app, or if there is a kitchen that will build a new default.hv with the rgu's from the imgfs dump.
Da Mafia said:
I'm still learning here and have been looking into registry settings. I've tried editing the default.hv, and while rgucomp says it builds fine, this results in the ROM not booting.
If I look at the rgu from the modified default.hv, its in a different order than the original.
Just wondering if I need a different app, or if there is a kitchen that will build a new default.hv with the rgu's from the imgfs dump.
Click to expand...
Click to collapse
You may ask to l3v5y for his kitchen. I'm using it if i need to re-arrange packages. For simple files modify I use my tgtool set.
hello to all will u please anyone can help me to how we cook with extendir...i stuck with this step :
"Modify the order of all other file system filter drivers in your boot.rgu. Personally I change order 0 to 10, 1 to 11, 2 to 12, etc.
Modify your boot_ms.rgu (also in XIP) if you cooked encfilt.dll/mencfilt.dll in your rom.
Rebuild your boot.hv and port the boot.rgu, boot_ms.rgu and boot.hv in to your XIP. "
wil u please anyone can explain about the order of boot.rgu
thanks to all
shafizal said:
hello to all will u please anyone can help me to how we cook with extendir...i stuck with this step :
"Modify the order of all other file system filter drivers in your boot.rgu. Personally I change order 0 to 10, 1 to 11, 2 to 12, etc.
Modify your boot_ms.rgu (also in XIP) if you cooked encfilt.dll/mencfilt.dll in your rom.
Rebuild your boot.hv and port the boot.rgu, boot_ms.rgu and boot.hv in to your XIP. "
wil u please anyone can explain about the order of boot.rgu
thanks to all
Click to expand...
Click to collapse
When you look at the boot.RGU files you'll find some keys in the "HKEY_LOCAL_MACHINE\System\StorageManager\filters\" and "HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\" sections.
Those keys have a value inside whose name is "Order", you have to find all of those keys and if there is any that has the order 0 (usually they all start from 1) you have to move all the values up by 1. (0 becomes 1, 1 becomes 2, etc.), then you can add the ExtenDir entries:
[HKEY_LOCAL_MACHINE\System\StorageManager\filters\Extendir]
"Order"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\Extendir]
"Dll"="Extendir.dll"
"Order"=dword:0
If you have problems understanding this upload the RGU file and I'll do the changes for you.
airxtreme said:
When you look at the boot.RGU files you'll find some keys in the "HKEY_LOCAL_MACHINE\System\StorageManager\filters\" and "HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\" sections.
Those keys have a value inside whose name is "Order", you have to find all of those keys and if there is any that has the order 0 (usually they all start from 1) you have to move all the values up by 1. (0 becomes 1, 1 becomes 2, etc.), then you can add the ExtenDir entries:
[HKEY_LOCAL_MACHINE\System\StorageManager\filters\Extendir]
"Order"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\Extendir]
"Dll"="Extendir.dll"
"Order"=dword:0
If you have problems understanding this upload the RGU file and I'll do the changes for you.
Click to expand...
Click to collapse
thank u very much bro here is my boor.rgu
http://www.sendspace.com/file/5u38dj
shafizal said:
thank u very much bro here is my boor.rgu
http://www.sendspace.com/file/5u38dj
Click to expand...
Click to collapse
I looked and all the orders seem to be fine, you just have to add the two entries at the end
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\filters\Extendir]
"Order"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\Extendir]
"Dll"="Extendir.dll"
"Order"=dword:0
If that doesn't work try the boot.rgu I attached where I added those two entries and also moved all the others entries' order up by 1.
airxtreme said:
I looked and all the orders seem to be fine, you just have to add the two entries at the end
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\filters\Extendir]
"Order"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\Extendir]
"Dll"="Extendir.dll"
"Order"=dword:0
If that doesn't work try the boot.rgu I attached where I added those two entries and also moved all the others entries' order up by 1.
Click to expand...
Click to collapse
thank u very much bro will try this and i will post
How about
airxtreme said:
I looked and all the orders seem to be fine, you just have to add the two entries at the end
Code:
[HKEY_LOCAL_MACHINE\System\StorageManager\filters\Extendir]
"Order"=dword:0
[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS\filters\Extendir]
"Dll"="Extendir.dll"
"Order"=dword:0
If that doesn't work try the boot.rgu I attached where I added those two entries and also moved all the others entries' order up by 1.
Click to expand...
Click to collapse
That is the easier part. How do you add the file extendir.dll to xip?? Thats the problem I am facing and for which there seems to be no answer.
Premananda_laishram said:
That is the easier part. How do you add the file extendir.dll to xip?? Thats the problem I am facing and for which there seems to be no answer.
Click to expand...
Click to collapse
If you're using platformrebuilder or a platformrebuilder-based kitchen it's just a copy&paste of the module inside the OEMXIPKernel folder. I have no idea about others but if they use XIPPort is going to be a mess.
request
airxtreme said:
If you're using platformrebuilder or a platformrebuilder-based kitchen it's just a copy&paste of the module inside the OEMXIPKernel folder. I have no idea about others but if they use XIPPort is going to be a mess.
Click to expand...
Click to collapse
Would you be kind enough to post or pm me an xip with extendir 1.6 already added in msxipkernel. I will just port it to my kitchen from then on.
Premananda_laishram said:
Would you be kind enough to post or pm me an xip with extendir 1.6 already added in msxipkernel. I will just port it to my kitchen from then on.
Click to expand...
Click to collapse
Sure but you have to tell me which cache size you want first.
2 or 4
airxtreme said:
Sure but you have to tell me which cache size you want first.
Click to expand...
Click to collapse
2mb or 4 mb cache 1.06 version. Please cook it with extendir in msxipkernel, because my kitchen does not have the provision to port oemxipkernel.
I forgot to mention, I will be cooking for wm6.1.
Premananda_laishram said:
2mb or 4 mb cache 1.06 version. Please cook it with extendir in msxipkernel, because my kitchen does not have the provision to port oemxipkernel
Click to expand...
Click to collapse
I attached the xip to this post
wm6.1
Can I use this to cook for wm6.1 rom? I edited my post a few minutes back.
And one final request. Could you please upload your whole kitchen(pre-port) to some sites so that I can use it to build xip for future extendir release. Bugging you every now and then would be very annoying to you.
Premananda_laishram said:
Can I use this to cook for wm6.1 rom? I edited my post a few minutes back.
And one final request. Could you please upload your whole kitchen(pre-port) to some sites so that I can use it to build xip for future extendir release. Bugging you every now and then would be very annoying to you.
Click to expand...
Click to collapse
I have no idea if it could work on WM6.1 but I supposed yes.
I used a clean oskitchen install, imported the latest leo rom, added the file to the MSXIPKernel folder and enabled the setting to halt after platformrebuilder runs to get the xip.bin from its folder. No need to upload the whole package just for that because you can take any wm6.1 rom for HTC phones (the first 6.1 rhodium ROMs are fine) and import it.
I cannot use it
I cannot use it. It says the dsm file is missing
Premananda_laishram said:
I cannot use it. It says the dsm file is missing
Click to expand...
Click to collapse
Platformrebuilder strips the DSM informations from the files to make the ROM faster so I can't do much about that. All I can tell you is that you can use xipport to dump another xip, then click build packages, add extenddir.dll+txt from my XIP dumped with xipport in the files\MSXIPKernel folder, click undo, click realloc P, click write maps and rebuild the xip.bin to have one with extenddir that your kitchen will probably accept.
mine
Here is the xip from my kitchen. Will it be possible to use it in your kitchen and then add the extendir dll. That way I can use it directly in my kitchen
Premananda_laishram said:
Here is the xip from my kitchen. Will it be possible to use it in your kitchen and then add the extendir dll. That way I can use it directly in my kitchen
Click to expand...
Click to collapse
I've attached the xip with extenddir in msxipkernel to this post.
BTW No it can't be used without having the full ROM; I had to do the work by hand editing the DSM and removing the debug libraries.
If you can upload an original ROM for your phone plus the kitchen you are using I can look if I can add support to oskitchen: since it's a 6.1 phone it should probably work fine.
you can put it anywhere in the xip, just remember that the module wont work in xip you have to use the .dll file.
Here it is
Here is my kitchen and folders
rom, sys and oem from this
http://asusmobile.ru/files/ROMs_P525/not_official/Alexx~/ASUS.P525.WM6.1.20273.1.3.3.WWE.exe
Kitchen attachment