I just make the special edition ROM trhought mkrom and I obtain the.nb1 file, but when I flash my xd and make the cold reset, it hangs on the welcome screen, it print the 3 lines in red in the right bottom and after that ..... Nothing....... sniff
Anyone could help me????
I used the .nbf file that comes with the program A of O2.
Thks
that means that the windows kernel, and gsm have initialized.
the system should then proceed to execute the stuff mentioned in registry key HKEY_LOCAL_MACHINE\init.
maybe something went wrong with default.fdf?
I use the default.fdf that comes with the mkrom.zip, I just extract it and copy the nk.nbf file and proceed, I didn´t modify anything.
thks
I try to make another ROM with diferent Default.fdf but it hangs too.
it could be the NK.nbf file???
can you tell me where is a link fot one NK.nbf valid?
I´m going crazy :shock: jeje
thanks
if you use a different source rom, you need to change your default.fdf to
the one from that rom.
thanks for your patience,
I extract the default.fdf from the NK.nbf with dumprom.exe.
and then I use the fdf2reg.pl to create the default.reg and I put this file in the cfg directory, and after that I execute mkrom (sh mkrom.sh NK.nbf)
is that correct???
thanks
I think that the nbf file that I´m using is not a correct verion.
I tried to make a nbf file form jeff´s page but it doesn´t work with the nbf selection.
Do you know where can I find a nbf file that works with mkrom???
Hi ,
Just downloaded the ER2003 EDIT utility to modify the Extended ROM in my XDA2.
Previously I also downloaded some ROM files available from this web site. Like the RUU15283wwe_cdl.exe
What I am missing now is how to create my own Extended ROM.
The question is the ER2003 Edit asks for an NBF file.
What I have is only EXE file that when I install, automatically decompress and they try to install directly on the pocketPC.
Am I missing something?
Is it possible to have the Extended ROM .NBF file of the Imate version?
Thanks and regards,
Claudio.
Claudio,
Just extract the ROM image (the exe file) with Winzip to a new folder.
Then you can open the ms_.nbf file with er2003edit.
Grtz,
Jos
Thanks for your prompt reply.
I unzipped the file and it comes out an EXE file. When I double click on the EXE file it does not decompress into files, but it starts an InstallShield Wizard, and it begin an installation process.
Can I modify this?
Claudio,
Just unzip this file again with Winzip in a new folder.
You should get 6 files:
- HimaClearJumpCode.exe
- HimaGetDeviceData.exe
- HimaUpgradeUt.exe
- ms_.nbf
- NK.nbf
- Radio_.nbf
The extended ROM is contained in the ms_.nbf file.
When you change the ROM, you should also modify the config.txt file in the ROM.
The ROM upgrade of the XDA can be started with HimaUpgradeUt.exe.
Grtz,
Jos
Hi,
alternatively: When the Installshield setup starts, browser to your temp folder and you will find the extracted files in a sub-folder. Just copy the files to another folder and close the Installshield wizard (which will delete the original extracted files)
Password
It asks me for a password so i can open the rom file..... Can someone help?
I'have got the same problem asking me for a password
HELP ANYONE??????????????????????
me too , all passwords not working. Ive got the lastest release ..
someone asked me to specify the type from the Open Dialogue option
i mean choose :
1- File -> Open Rom Image
2- from the opened box change the drop down option from :
[ WM2003 Auto-Detect ROM *.nbf ] ---> to [WM2003 Extended Rom (ms_.nbf) ]
and it should solve the problem ..
I've tried it but it gave me same password error ...
any help
I have been able to extract the EXT ROM and OS ROMs using the NB2NBF and IMGFS tools. I know that by using a custom ROM I can save on storage space by loading in my programs. I'd like to load Pocket Informat, Alarm Today, Phone Alarm , isilo and TCPMP into the OS ROM. How do I do this? I have all their cabs. I will keep reading the forums too.
I know that some like summiter have done this. Anyone able to help me get started or point me in the right direction?
J-Man5
the only device i ever heard supporting that is walaby
dont know if it's possible with other devices
i mean the os part of the rom is well you know full already
yes it is possibel.you need a tool called [typhoonnbfdecode_v5] look for this tool and how to use somehere in the ftp, and here in the wizard forums
you need to make a dump of the os from a nk.nbf image with the above tool
then you need to extract the files from de cabs you want plus the reg settings,
simply copy the extracted files from cab to your rom dump folder
make a cab file with the reg files from the cab files an also the shortcuts to the programs.
repack the rom with the typhoonnbfdecode_v5, convert the nba image with NB2NBF back to nbf and flash,after that install the cab with reg settings plus shortcuts,
you have a long jorney ahead.
i took me several weeks to make my own rom with netcf.2,adobe acrobat e several other programs integrated to the rom.
faria said:
then you need to extract the files from de cabs you want plus the reg settings,
simply copy the extracted files from cab to your rom dump folder
<snipped>
make a cab file with the reg files from the cab files an also the shortcuts to the programs.
Click to expand...
Click to collapse
OK I have gotten the nk.nbf extracted and the EXT ROM opened using winimage and the OS ROM dumped via imgfs.
Where I am running into problems understanding is how to unpack the .cab install files for the programs I am planning on using and how to "move" them to the \Program Files\ directories that they need to be in. For example PocketInformant is loaded into the \Program Files\WebIS directory. Do I put all the files from the .cab file in the dump OS directory? Is there some sort of program that will extract the .cab file and let me look at what registry settings are being set by its installation?
What program is used to create registry settings into a .cab file?
Thanks
J-Man5
BUMP
wincecab manager ,google it.
Hey!
I want to add some apps to the Rom of my Wizard, too.
I have used imgfs tools to great a dump from my OS.
Now i want to Install Total Commander to a Folder "\Programme\Total Commander\".
How can i do this? Or is it only possible to copy the files without any folder?
Sry for my bad english
Hey
I just got my hermes. beatiful phone. I just upgraded from the 8125, i can't even look at it anymore (my old brick).
Anyway, i unlocked it yesterday and upgarded to wm6. I liked the default 3G (wit the flame) boot screen better than the "Bring Back the ROM page" (allthough that was funny).
I want to know,
1. can someone send the origional CINGULAR 3G(FLAME)=*=*=*=> boot screen?
2. After performing a few searches, i coudln't find out how to change the boot screen. Does anyone know how?
imasri29 said:
Hey
I just got my hermes. beatiful phone. I just upgraded from the 8125, i can't even look at it anymore (my old brick).
Anyway, i unlocked it yesterday and upgarded to wm6. I liked the default 3G (wit the flame) boot screen better than the "Bring Back the ROM page" (allthough that was funny).
I want to know,
1. can someone send the origional CINGULAR 3G(FLAME)=*=*=*=> boot screen?
2. After performing a few searches, i coudln't find out how to change the boot screen. Does anyone know how?
Click to expand...
Click to collapse
You cant have searched very well dude
Easy Splashscreen Guide
Sorry I used the wrong keywords, splash screen did not come to mind, I kept using boot screen, boot image, boot*
Any leads to the OEM screen?
imasri29 said:
Sorry I used the wrong keywords, splash screen did not come to mind, I kept using boot screen, boot image, boot*
Any leads to the OEM screen?
Click to expand...
Click to collapse
You can extract them from a commercial rom using NBHextract.exe
perfect ill try it when I get home. im on my mobile right now.
I could not find the nhbextract.exe, but i did open nbhtool.exe...
I have the default rom which i downloaded off HTC.com... how do i extract the nbh file from the exe? i tried to run the setup to see if it would extract files in any temp folder but i could not find it.
Help anyone?
heres the link to nbh extract
open the ROM exe file using WinRAR and get the nbh file.
Run: nbhextract.exe NAMEOFNBHFILE.NBH
and the file will be extracted (nbhextract.exe and the nbh file must be in the same folder)
mrvanx said:
heres the link to nbh extract
open the ROM exe file using WinRAR and get the nbh file.
Run: nbhextract.exe NAMEOFNBHFILE.NBH
and the file will be extracted (nbhextract.exe and the nbh file must be in the same folder)
Click to expand...
Click to collapse
It is possible to use Dutty's good NBH tool for extracting NBs from NBH. I think it is more n00b friendly way as they can use point and click method and thay are not bound to have NBH in the same folder.
KarhU said:
It is possible to use Dutty's good NBH tool for extracting NBs from NBH. I think it is more n00b friendly way as they can use point and click method and thay are not bound to have NBH in the same folder.
Click to expand...
Click to collapse
nbhextract will convert the .nb files directly to bmp in the same process. Duttys tool just extracts the nb files.
Thanks for the help.
Unfortunately, the rom i downloaded from htc, has a .nbf file instead of a .nbh file (which is 73.xx megs). When i use the extractor, i get error :
Error: 'nk.nbf' is not a valid .nbh file
Could not open 'tempfile.dbh'
I also tried to change the extension of the nbf file to nbh but that did not help either as i got the same error. I'm downloading the rom from http://www.america.htc.com/support/docs/ruu_hermes_1.34.502.1_1.16.00.00_wwe_cws_ship.exe
bump .....
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