Boot .rgu prloblem - Windows Mobile Development and Hacking General

hi
i have a problem when io build OS, the boot rgu file has this lines wrong:
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome]
"SK1TEXT"="Contatti"
"ExtensibilityXML"="<PluginsOrder=\"CMyPhotos;CMusic;CWelcomeCenter;CPhone;CVoicemail;CClock;CText;CEmail;CAppointments;CHomeFavs;CWindowsLive\"
CPRFileName=\"Titanium\" DisplayStyle=\"Titanium\" />"
"SK1URL"=":MSCONTACTS"
"HomePluginGuid"="{892B90CB-9806-427e-8BED-F45C6A9E576B}"
"DockOperatorBar"=dword:0 "Enabled"=dword:0
Click to expand...
Click to collapse
do some one know how the good sintax?

Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\CHome]
"SK1TEXT"="Contatti"
"ExtensibilityXML"="<PluginsOrder=\"CMyPhotos;CMus ic;CWelcomeCenter;CPhone;CVoicemail;CClock;CText;C Email;CAppointments;CHomeFavs;CWindowsLive\"
CPRFileName=\"Titanium\" DisplayStyle=\"Titanium\" />"
"SK1URL"=":MSCONTACTS"
"HomePluginGuid"="{892B90CB-9806-427e-8BED-F45C6A9E576B}"
[B]"DockOperatorBar"=dword:0
"Enabled"=dword:0[/B]
imho, just enter. and enter at end.

Why do you have CHome registry keys in your boot.rgu? They don't need to be in there-they should be built into the system.hv, not the boot.hv.

nvmd...
,

Farmer Ted said:
Why do you have CHome registry keys in your boot.rgu? They don't need to be in there-they should be built into the system.hv, not the boot.hv.
Click to expand...
Click to collapse
i'm newbe, i exctracted the boot.rgu file with this command:
mkdir ROM
cd ROM
mkdir XIP
cd ./../..
set _FLATRELEASEDIR=.
echo REGEDIT4 > dump/ROM/XIP/boot.ascii
rgucomp.exe -o dump/default.hv -nologo >> dump/ROM/XIP/boot.ascii
stringconverter.exe dump/ROM/XIP/boot.ascii dump/ROM/XIP/boot.rgu /unicode
del dump\ROM\XIP\boot.ascii
isn't good?

I can't answer that, but I can tell you that in any build, the CHome reg keys are in the sys#/shared/common/CHome rgu (8c58193c-f8ab-447a-af67-a5167df96529.rgu). You may have messed up and dumped the whole registry or something, but you probably shouldn't have that reg key in your boot.rgu.

OK thanku for your interesting....
another question, why do my phone tell me chekscum error when i try to fash the rom craeted by me?
I used wmreloc on a dump build with OSbuild.exe and a xip made with xipkitchen
i have an Acere e101 and around i can not find anything about him, i trying to use the evirusVK but i have only flash.bin file... evirusVK want a nbh file....

up up
please someone who can explane me why after i flash the final rom i got always chekskum error?
i used build OS, wmreloc and osnbtool to build the rom...... I saw that the xip file ported with xipkitchen, is smaller than the the original and boot.rgu file i axtracted with the commands wrote up, is bigger then 1000 kb. why?

Dunno, but 1 MB is way too big for the boot.rgu. That sounds like an .rgu dumped from the system.hv. If you get a stock boot.rgu, it's about 32 KB, but if you dump it from a boot.hv, it may only be 10-12 kb (there's some redundant stuff in the original boot.rgu as well as all of the developer comments). I can't tell you what you're doing wrong, but you're definitely doing something wrong. Sorry I can't be more helpful.

Related

DIY your ROM

Hi,
I write some code that can modify the ROMs, it can save your time to add and delete files by hand.
RomMaster V2.0 Beta
Usage: RomMaster [options] imagefile
-d[m] <dfile> - delete file
replace file/module together with -a option
'm' delete module, deleting module isn't suggested
-a[c] <afile> - add file into the rom
'c' means use compress(need CECompressv4.dll)
-o <ofile> - output imagefile name
-v <0~9> - print info, 0 detail, 9 only show errors, default is 5
-w <5> - 5 is 2005, default is 2003&SE
-x - only save XIP(OS) data
-s <0x...> - Fix XIP start address(Hex)
-e <0x...> - Fix XIP end address(Hex)
In replace mode, 'c'&'m' is useless
It is now 2.0 Bata Release.
You can delete file/modules you don’t like from the ROM.
RomMaster –d “filename” –o “newROMname” “ROMname”
You can add files into the ROM.
RomMaster –a “newfilename” –o “newROMname” “ROMname”
You can replace file in the ROM
RomMaster –d “filename” –a “newfilename” –o “newROMname” “ROMname”
“newfile”’s size should be the same or small than the file you want to replace, new file will occupy the same space as the old one.
I test some ROM in my SP; include SDA, Dopod 575 & 585. I only tested one 2005 ROM. Replace module may don’t work, I am still working on it.
Before you burn the image generated by the tool, make sure you finish follow step:
1. RomMaster –o “TestROM” “SrcROM”
2. Do binary compare “SrcROM” with “TestROM”
a) If they are 100% same, I think you can safely use this tool.
b) If they are 99% same, you should be careful, make sure you only burn the OS part. Because some ROM are modified by someone before, there are maybe some useless data in the ROM, only burn the OS part won’t damage your SP.
c) Else, the “SrcROM” may contain some unknown structure or data, the “TestROM” may won’t work, don’t try burning it into you SP. If you want to modify it, tell me where I can find the ROM, if I am free, I can give some help.
3. I only tested one 2005 ROM, its structure isn’t very correct, and I think that ROM is extracted form emulation ROM. So if 2005 ROM isn’t 100% same, don’t try and be careful even they are 100% same.
This is great!!!
Going to try it!
ncruz,
I'll wait for your experience, cause if this is working we can all save space by directly burning upgraded cameras etc into the rom. will save me at least 1MB ram or storage.
The tools sounds great gmap.
There already exists MKROM tool - http://www.xs4all.nl/~itsme/projects/xda/romtools.html
it is 100% working with WM2003/2003SE devices. But it is rather inconvenient.
I'll test your "-w 5" option on a real device. Real WM5 device has one XIP kernel section with only few modules and about 1Mb free space. All other data is kept in IMGFS partition, I'm currently working on a tool that would work with it.
And one question. When you add new files to ROM, do you add them to a new XIP or extend the existing XIP? And when you delete modules, do you reuse the freed space after adding new ones?
mamaich said:
There already exists MKROM tool - http://www.xs4all.nl/~itsme/projects/xda/romtools.html
it is 100% working with WM2003/2003SE devices. But it is rather inconvenient.
I'll test your "-w 5" option on a real device. Real WM5 device has one XIP kernel section with only few modules and about 1Mb free space. All other data is kept in IMGFS partition, I'm currently working on a tool that would work with it.
And one question. When you add new files to ROM, do you add them to a new XIP or extend the existing XIP? And when you delete modules, do you reuse the freed space after adding new ones?
Click to expand...
Click to collapse
That's great if we can modify IMGFS partition I am waiting for it.
I know that tool and i don't know how it works. I made this tool only for interesting.
You can find XIP chain in 2003 ROM, by XIP chain, you can know the address and length of each XIP section. I will scan the hole XIP region before inserting the new file to reduce memory fragment. When a module is deleted, its space will be freed and reused when adding files. I freed about 6M space in my own ROM by deleteing the useless files, and add about 5M files into it, it works OK.
It seems 2005 don't have XIP chain information in the ROM, i only test one 2005 ROM, and i didn't find the XIP chain info. If your 2005 ROM don't have XIP chain info too, you should modify ROMHDR.physlast to a correct value by hand. Because if i can't find the XIP chian info, I use ROMHDR.physlast to decide the end address of XIP. Or, there are almost no space for you to add new file. My 2005 ROM physlast=0x8c253278, and only about 78732 bytes free before 0x8c253278.
I update the the tool V2.2 , fixed a bug when deeling with MDA(818) ROM.
gmap said:
That's great if we can modify IMGFS partition I am waiting for it.
Click to expand...
Click to collapse
I've PMed you a test version. I'll make it available to public later.
... If your 2005 ROM don't have XIP chain info too, you should modify ROMHDR.physlast to a correct value by hand.
Click to expand...
Click to collapse
My ROM has all needed info, I had to extract everything from rom image after 1C0000 address to a separate file and gave it to your tool. It is working perfectly. I've managed to delete and add a new file to ROM. I have not tested "-dm" option. It seems that all modules/files in XIP section of WM5 are uncompressed. I'm using BlueAngel's WM5 ROM. Later I'll try to replace boot.hv file with my own version.
Can you add a switch to your program "-s bytes" so that it woud skip the given number of bytes from file start, so it would be possible to work directly on NBA files with header?
gmap, can you tell me what file i can use this with? Is it for nbk or nba files? Thanks
I'm not able to edit the xip sextion ...
i've tried your tool on 1.60c.07CHS rom for xdaII :
RomMaster.exe -w 5 -x -o test.bin nk.nba
result :
[Info] It is a common ROM.
[Error] File is damaged, end address small than start address.
[Error] File is damaged, end address small than start address.
RomMaster.exe -w 5 -x -o test.bin imgfs_raw_data.bin (created with mamaich's tool)
result :
[Info] It is a common ROM.
[Error] Load nb00 failed.
RomMaster.exe -w 5 -x -o test.bin img.bin (created by nba part 1C0000 to end)
result :
[Info] It is a common ROM.
[Error] File is damaged, end address small than start address.
[Error] File is damaged, end address small than start address.
How to save the XIP section ?
TofClock said:
RomMaster.exe -w 5 -x -o test.bin imgfs_raw_data.bin (created with mamaich's tool)
Click to expand...
Click to collapse
This would not work. My tool works with IMGFS and you need to edit XIP
and ... how to edit XIP ?
mamaich said:
My ROM has all needed info, I had to extract everything from rom image after 1C0000 address to a separate file and gave it to your tool. It is working perfectly. I've managed to delete and add a new file to ROM. I have not tested "-dm" option. It seems that all modules/files in XIP section of WM5 are uncompressed. I'm using BlueAngel's WM5 ROM. Later I'll try to replace boot.hv file with my own version.
Can you add a switch to your program "-s bytes" so that it woud skip the given number of bytes from file start, so it would be possible to work directly on NBA files with header?
Click to expand...
Click to collapse
mamaich, or anyone else, what did you use to extract after 1C0000?
splitrom?
any help would be greatly appreciated.
Russ
Wow , just an hex-editor like winhex or edithexa
i tried that w/xvi32, and it didn't seem to work. I guess I'll try again
Thx gmap for this great tool. 8)
Recently I want to replace the TureFFS.dll at the XIP area of Wizard OS ROM.
ftp://xda:[email protected]/Uploads/HTC_Wizard/Roms/Qtek/Qtek_9100_1_6_7_ENG__OS_ONLY.zip
I type the following command and it says that it cannot replace the file.
Code:
D:\>RomMaster.exe -d TrueFFS.dll -a TrueFFS.dll -w 5 -o new.nba os.nba
[Info] It is a common ROM.
[Warning] o32_rom(0x8c268ef8)'s o32_data at 0x00000000 is zero.
[Warning] Found dif-referenced region [OLD] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00008000
[Warning] Memory Block(0x8c101000,0x8c1510ac) overlap with Block(0x8c10288c,0x8c1028b8).
[Error] You want to get an object whose size is 108, but it is 112. RomOffset=0x8c268e00
[Error] Could not replace 'TrueFFS.dll' with 'TrueFFS.dll'.
However, I can successfully replace the boot.hv file. Do you know why?
ahlok_hk said:
Thx gmap for this great tool. 8)
Recently I want to replace the TureFFS.dll at the XIP area of Wizard OS ROM.
ftp://xda:[email protected]/Uploads/HTC_Wizard/Roms/Qtek/Qtek_9100_1_6_7_ENG__OS_ONLY.zip
I type the following command and it says that it cannot replace the file.
Code:
D:\>RomMaster.exe -d TrueFFS.dll -a TrueFFS.dll -w 5 -o new.nba os.nba
[Info] It is a common ROM.
[Warning] o32_rom(0x8c268ef8)'s o32_data at 0x00000000 is zero.
[Warning] Found dif-referenced region [OLD] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1e1290 Length=0x00000800 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c1fe538 Length=0x00000600 ObjectType=0x00008000
[Warning] Found dif-referenced region [OLD] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00200000
[Warning] Found dif-referenced region [New] Address=0x8c211018 Length=0x00000a00 ObjectType=0x00008000
[Warning] Memory Block(0x8c101000,0x8c1510ac) overlap with Block(0x8c10288c,0x8c1028b8).
[Error] You want to get an object whose size is 108, but it is 112. RomOffset=0x8c268e00
[Error] Could not replace 'TrueFFS.dll' with 'TrueFFS.dll'.
However, I can successfully replace the boot.hv file. Do you know why?
Click to expand...
Click to collapse
In replace mode, new file should not biger than old file. So, you should delete old 'TrueFFS.dll' first, then add the new one(You can delete some file next to 'TrueFFS.dll' to get free space or move it to a big free space, then modify the file size and related infomation of 'TrueFFS.dll' by hand to make it bigger). Replacing module isn't stable, I confused by some of the module data. If you want to replace a module, it may not work. I haven't find a way that can be used to calculate all of the data.
gmap said:
In replace mode, new file should not biger than old file. So, you should delete old 'TrueFFS.dll' first, then add the new one(You can delete some file next to 'TrueFFS.dll' to get free space or move it to a big free space, then modify the file size and related infomation of 'TrueFFS.dll' by hand to make it bigger). Replacing module isn't stable, I confused by some of the module data. If you want to replace a module, it may not work. I haven't find a way that can be used to calculate all of the data.
Click to expand...
Click to collapse
Thx for your explanation. Actually the new file is smaller than the one being replaced. And I just found that I can only delete those non-module files while all modules could not be deleted.
Thx again. Hope to see new version if you have time to find out how to calculate the data. :wink:
How can i extract a kernel file (kbbdrv.dll)?
thanks
dherrero said:
How can i extract a kernel file (kbbdrv.dll)?
thanks
Click to expand...
Click to collapse
dumprom tool
But if you'll extract this or any other XIP DLL and then readd it to the same, or any other ROM it would not work.
Hello,
I have a Apache Rom,
I would like to delete nk.exe are replace it.
iv tryed:
rommaster -w 5 -d nk.exe nk.nba
also
rommaster -w 5 -d nk.exe -a nk.exe nk.nba
keeps telling me i can delete that file.
just to let you know: if i use dumprom i get the boot partition files (containing nk.exe) and if i use imgfs i get all the os files (not containing nk.exe)
Any help would be great thanks
you cannot delete nk.exe, and you should not even need to do that.

Registry changes

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.

Visual Kitchen and registry...

Does Visual Kitchen use *.hv files to build the registry or are boot.hv , use.hv , default.hv ignored?
In what order are *.hv, rgu, *.reg processed?
And which folders are processed first? ROM>SYS>OEM>EXT
I know that *.provxml are processed after first boot and *.xml have to be invoked during customization.
It seems that EVK uses the rgus to make the hives thats why you dont need to play with them anymore.... then it tooks the XIP hv's and add them too
First XIP then OEM then SYS then EXT and EXT are arranged alphabetically so if you want a reg to be changed at the end of the cooking process you need to rename the EXT pkg with ZZZZ_blablabla
OK. Thank you. I will try and delete *.hvs then and see what happens...
delete them?
I didnt say you can delete them, even worst idea is to delete the OEM or and XIP ones...
I just said you dont need to touch them anymore
Haha..
@Diagrafeas
.hv files are rebuilded during cooking process they contain all registry.
It depends which kitchen you use but the packages have a file with a extension *.reg or *.rgu
You can open them with a tekst editor but if you edit them you need to save them in UTF8 and first
line must be 'REGEDIT4' (without the quotes) and a empty last line.
Make only small edits and test because registry files are very sensitive, if you forget one ' your whole kitchen won't work.
If you edited succesvol and it works as it should be I recommend to make a backup of your kitchen before you edit the next one, this way your always save.
+ Que PPC said:
delete them?
I didnt say you can delete them, even worst idea is to delete the OEM or and XIP ones...
I just said you dont need to touch them anymore
Click to expand...
Click to collapse
OK I will not delete then, but i have another question.
Inside OEMXipKernel there is a boot.hv and a boot.rgu.
The original ones had the same keys.
But now i have made some changes inside boot.rgu.
Which keys will be used boot.hv or boot.hv ones?
EVK recompiles the boot.hv from the boot.rgu, so if you tweak the boot.rgu, you're good to go. You don't need to rebuild the boot.hv yourself.
OK. Thank you all.

[SOLVED] Errorlevel: -1073741819

Hello everyone I have a small issue here hope someone knows how to fix it or if someone had this error before what did you do to fix it??
Well Im Using Ervius kitchen and it was working fine, I'm able to cook with SYS 21901 but if I want to do an upgrade and use something else like 23563, 24611 or others it gives me this error: -1073741819
This error usually comes up when I hit the create rom button, but at first everything looks fine but in the middle of the process it tells me that RomKitchenExecutable and Imgfsfromdump.exe are not responding and it just shut down.
Thanks to everyone in advance
hi,
check this reply from twopumpchump: from this thread
twopumpchump said:
michal_banszel said:
Actually I always got error:
ERROR! (errorlevel: -1073741819)
ERROR executing: kitchen_build_rom.bat
ERROR!!!
What is more... some files in my kitchen f.g. erviuskitchen.exe is now... hidden It has changed itself. And I'm not able to change it all exe files in my main folder (PagePool Changer 2.21.exe and nueSpinLockPatcher.exe) and S00x files in my ROM folder changed into hidden. With no reason. It happend first time to me and don't know why??
Click to expand...
Click to collapse
have you edited your kitchen_build_rom.bat? the files didnt change attribute by themselves i dont think, im guessing you may have edited your bat file to give hidden attribute to your dump and possibly didnt do it right. having the attributes changed to hidden in some files will cause platformrebuilder to crash. maybe try using ervius's bat unedited and unhiding all the files you said you werent able to change the hidden attribute, but you can with the unhide.bat i posted a few pages back. again im just guessing, maybe it will help.
Click to expand...
Click to collapse
lion75y said:
Hello everyone I have a small issue here hope someone knows how to fix it or if someone had this error before what did you do to fix it??
Well Im Using Ervius kitchen and it was working fine, I'm able to cook with SYS 21901 but if I want to do an upgrade and use something else like 23563, 24611 or others it gives me this error: -1073741819
This error usually comes up when I hit the create rom button, but at first everything looks fine but in the middle of the process it tells me that RomKitchenExecutable and Imgfsfromdump.exe are not responding and it just shut down.
Thanks to everyone in advance
Click to expand...
Click to collapse
regards,
mike
This solution didn't help, I did edit the .bat file but only to change the device name, and add REM to the line specified and still it gives me that those programs from the kitchen have stop working or not responding and it stops the process.
where did you get your new SYS???
is from PPCkitchen format?
download another pkg diferente source...
post your build log
+ Que PPC said:
where did you get your new SYS???
is from PPCkitchen format?
download another pkg diferente source...
post your build log
Click to expand...
Click to collapse
the new SYS I have been obtaining them from these page
http://forum.ppcgeeks.com/showpost.php?p=1710334&postcount=55
also the SYS from our friend NRGZ28 doesnt work for me it gives me the same error and keeps telling me that those applications from the kitchen are not responding ( or Crash) but its weird because I can cook with 21901 but I cannt add or if I select another SYS it gives me the error.
http://forum.xda-developers.com/showthread.php?t=650783
P.S. On the build lod it shows that is missing alot of modules and files and thats because at that moment is when it gives me the warning that the romkitchenexecutable.exe and imgfsfromdump.exe are not respnding
mmmm
weird did you check that modules are fine?
i suggest you to use the PPC kitchen file attribs.. i will post them at night to edit the bat.. so the kitchen will be ready to accept PPCkitchen attribs SYS
Ok Thanks I will be waiting bud. I will keep messing with it, and reading to see if I can find the answer to this issue now.
Insert the following as third line into the kitchen_build_rom.bat:
Code:
attrib -a -r -h -s /s
so the kitchen_build_rom.bat reads like this:
Code:
@echo off
cd..
attrib -a -r -h -s /s
REM........................
set IMGSTART=0
set ULDR=ULDR
.
.
.
Do not fiddle around with attributes anywhere else ...
cheers
Cool thanks i forgot this totally
vogonj said:
Insert the following as third line into the kitchen_build_rom.bat:
Code:
attrib -a -r -h -s /s
so the kitchen_build_rom.bat reads like this:
Code:
@echo off
cd..
attrib -a -r -h -s /s
REM........................
set IMGSTART=0
set ULDR=ULDR
.
.
.
Do not fiddle around with attributes anywhere else ...
cheers
Click to expand...
Click to collapse
Thanks, Am testing right now to see if this solves the issue.
Found the answer to my problem, I just needed to add the EXT packages for 6.5 and 6.5x . I was using the same ones that the kitchen created when I dump the rom. I found this out by doing alot of tests between a good kitchen already set up and mine ...
Can someone provide me the link to obtain a clean set of EXT packages for Rhodium and that are 6.5 and 6.5x plz
That my friend is hard... so hard... and the PKGS hunt is a task that we must to do by ourselves you know.... if you search as "Tachi phone canvas EXT PKG" you will find something interesting like a thread with the cab.. so you need to convert it... then maybe in the same or another post or thread there is the OEM and you need to transform it to EXT there arent all full of EXT PKGS repository you know... thats the Cooking world bud search for ressolution too
Thanks
Just to let everyone know I also found out that on my dumped EXT files from my stock rom the GlobalSmartDialing makes the Ervius Kitchen to crash if you erase them or make them NOT to be inlcuded in the rom will solve the issue.

[Q]How to cook with extendir

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

Categories

Resources