Related
I'm looking for the registry entries for the microsoft bluetooth stack on a ppc2003se device and maybe the bt dlls in the windows directory. I downloaded a imate jam rom, but I can't figure out how to extract the information I need from it If someone could provide me with a copy of their registry entries (i think all the important ones are stored at HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\), I would greatly appreciate it. Thank you for your time!
Jason
P.S. In case you are wondering, I'm trying to restore full bluetooth functionality to my crippled samsung i730 verizon phone (mostly I want the DUN profile). It uses the ms stack and the main (only?) problem appears to be that some of the registry entries have been removed. If I can compare my registry entries to working entries, I'm hoping I can find the solution!
you can extract all files from ROM with dumprom tool, then convert default.fdf to defailt.reg with fdf2reg.pl script.
The BT DLLs from jam's rom would be useless for you - they are XIP.
Thanks for the info on the dlls, i didnt know what arcitecture the jam used. As for the dumprom tool, I tried it multiples times in different configurations to no success (nk.nbf, nk.nba, different passwords). The rom I grabbed was 1.12 from the "How to upgrade with the latest I-mate Jam ROM --GUIDE--" thread. any suggestions for one that will work?
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
CRCinAU said:
Hi all,
I've managed to find a dump of build 19900, however I haven't managed to make a working ROM out of it as yet. I'm hoping to find a way to get it working with bepe's kitchen tools - therefore removing the reliance on a custom chinese binary to build these ROMs.
I believe this ROM is big storage, so I'd like to make available a non big storage version as well for everyone to benefit.
Any takers to help out?
Download URL: http://rapidshare.com/files/113432995/Hermes_RomKitchen_19900.rar
Click to expand...
Click to collapse
Will take a look at it dude, aint got a load of time at the mo though. Might have a quick PM session and see if theres a WWE version we cna use.
Have you guys tried PM'ing Dvha79_ddt? I'm not much help on cooking but i'll try and suggest anything
Good luck guys.
Need testers let me know.
I've managed to get the ROM to build using Bepes kitchen, however it doesn't boot. It sits there at a black screen on power on...
This leads me to believe it's part of the XIP that is just wrong.
I've attached what I've extracted from the included os.nb by doing:
nbsplit -hermes os.nb
RomMaster -w 5 os.nb.payload -x -o xip.bin
Run xipport, choose Dump xip.bin
I then deleted os.nb & os.nb.extra.
Then put the XIP dump together as it should be (i think) for bepe's kitchens.
Not 100% sure where to go from here...
edit: Oh, I've attached the TOOLS directory too - just in case you don't have a copy of Bepes great work.
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
dan1967 said:
This is a non big storage modded 19900 xip that works.
I haven't used in a kitchen just yet.
I will have a look at the dump later on.
Click to expand...
Click to collapse
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
CRCinAU said:
Hmmm - I've used your XIP - it boots, but same as using the default ROM kitchen tools, it hangs after displaying splash2. I replaced the OEM_FLASHDRV.DLL in OEMDrivers with a non-BS version, in case that was an issue, but still no go...
Click to expand...
Click to collapse
For now you can try to merge that XIP with the payload from the ROM (without kitchen) and it should boot&work.
Will try to get the romhdr.bin and in fact to rebuild the whole ROM folder and let u know whats happening.
Using Dvha79_ddt 900
I know it's not what you are looking for, but I am using Dvha79_ddt ROM and it is working as well as his 701 which was very fast and rock solid. Would like to help in any way I can as I loved your ROM's apart from the issues. As a noobie where do you find these ROM's in the first place?
A lot of it is hit and miss finding things here and there - like this kitchen that seems to be almost complete, but just doesn't work. A bit of hacking around and it can probably be made to work.
As WM6.1 doesn't exist for the hermes devices, it is always ported from something else - which can lead to weirdness.
Most of it is pot luck, and a lot of knowledge (and I'm missing some in getting this kitchen working )
just a working trick
what I am sure is working (tried it before) is replace the whole ROM folder from new kitchen with your working one and then just slip in the xip.bin into the new payload in a few steps.
Still can't get this working....
I've changed the BuildNB.bat to show the following:
Code:
echo.
CD ROM
..\TOOLS\buildxip.exe -b
if not "%errorlevel%"=="0" goto error
del out.bin
copy xip_out.bin out.bin
CD..
This should use your XIP in the ROM, which shows as 3.62.07.Dan - however I still can't get past splash2... Eventually, the backlight goes out, but it doesn't seem to display anything past splash2... Eventually, the screen goes off (power setting). Turning it back on via the power button just gives me a white screen... I'm at a loss to figure out what's happening here.
The OS.nb.payload is the same (non-BS) that I was using from my 10.1 release of my ROM, and the XIP folder contains the same XIP as 10.1 release (Build 19209) - however the XIP version shouldn't matter, as we delete it and merge yours into the OS-new.nb instead...
About the same happened to me and after a re-flash of a good nbh I got some very strange things happening. I could not install any cab. Very weird.
I had to format everything.
Anyway the xip is working if slipped into old rom, but that's not much of a news...
I looked into S00 of FLASHDRV.DLL module in order to convert it, but it does not look like usually.
Maybe that dump is not from a hermes device.
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
CRCinAU said:
Hrrrm - that is possible, however the site said that it was for Hermes devices... Are you looking at it in the OEMDrivers directory or the XIP?
Can we swap out the FLASHDRV.DLL from a working ROM? I'm pretty sure that isn't tied to a certain build?
Click to expand...
Click to collapse
I can try to make it work with the XIP from the 19900 version existing on this thread. (actually from there was the xip I uploaded). Could it work? There will be maybe a 409 & 804 conflict?? I have no clue really. Can only try.
I don't believe the XIP is localised, nor are the OEMDrivers. I may be wrong here though. 409 vs 804 should in theory only become an issue when applications that use localisation is involved..
It is definitely not a hermes rom as the kitchen does not accept a hermes payload while other kitchens accept older (different) payloads. Kitchen halts at ImgfsFromNb.
I can not think of something else. I give up on this one.
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
The XIP definatly isnt localised at all,
What sort of sizes are you guys getting for the os.nb filesize?
CRCinAU said:
Hrrrmmm...
What about this:
ftp://user:[email protected]:333/Aikon/Build19900RKXiaoQiao.7z
It weighs in at 145Mb, but it is supposed to be another Hermes 19900 kitchen that I haven't managed to get going either...
Click to expand...
Click to collapse
The download speed is obscene. It will finish maybe tomorrow.
being tired of seeing too many protected roms floating around, i decided to make japanese wm6.1 cooking base files myself. it took me awhile, but i finally figured it out. i would like to share my experience of making a japanese wm6.1 rom for hermes here.
actually, it is not that difficult, and all i did was just assembling pieces from different official roms. so, i would NEVER call it my OWN rom or anything because every part of the original roms was developed by MS and HTC. (sorry, but i really think it's too funny many people, who know slightly better than others, put their names in the ver info, apply procection or whatever to their roms, and say "this is my own rom!" for something made out of other roms originally built by MS and HTC.... is this place for dev info sharing for similar-minded guys? donations?? c'mon!)
i will explain about the details step by step later. here's a rough tutorial.
things you need:
[tools]
Pandora Kitchen (thanks to mattk_r) for cooking and burning
http://forum.xda-developers.com/showpost.php?p=1364931&postcount=1
or
i prefer bepe's Extended Hermes Kitchen for WM6.1
http://rapidshare.com/files/88850555/HERMES_DEV_v2.1_Build_19199.rar
G'Reloc.exe as usual
http://forum.xda-developers.com/showpost.php?p=1524413&postcount=1
[roms]
bepe's kitchen (thanks to him!) for simple and working oem folder and xip (OEMXIPKernel only)
http://forum.xda-developers.com/showpost.php?p=1177762&postcount=1
x04ht (japanese softbank diamond) rom for most of the sys part
http://forum.xda-developers.com/showpost.php?p=2998164&postcount=1
htc hermes official wm6.0 rom simply for os.nb as a template
http://rapidshare.com/files/46467733/HTC_TyTN_WWE_3.54.255.3_6275_1.48.00.10_108.exe
htc kaiser (or opal) official wm6.1 rom for dpi_96 files
http://rapidshare.com/files/157469239/Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.rar
http://forum.xda-developers.com/showthread.php?t=441689
s11ht (japanese emobile kaiser) official rom for 0411_dpi_96
ftp://htc-jp.com/EM/S11HT_firm_V2_6_881_0_JPN.exe
[basic strategy]
[oem]
1) bepe's oem folder is very simple and clean for cooking (some modifications are necessary in *.rgu files, tho)
2) replace OEM.cer by the one from x04ht rom
[rom]
1) basically, you can take OEMXIPKernel from bepe's xip or from htc hermes official wm6.0 rom
2) MSXIPKernel and MSXIPKernelLTK are from x04ht rom or whatever you want
3) use os.nb from htc hermes official wm6.0 rom just as a template
[sys] (tricky)
1) the base is opal sys. but remove all the language specific (0409) folders.
2) take the language specific but non-vga folders from x04ht, x05ht or whatever wm6.1 japanese rom (0411 folders not including dpi_192)
3) take language specific qvga folders (the 0411_DPI_96 folders) from s11ht
4) take .vm folder, packages.* in metadata folder, and service.exe in os folder, shell32.exe and shellres.dll in shell folder from hermes official or bepe's sys. (irda is not included in opal rom. take them from bepe's rom if you wanna use irda.)
[points]
1) don't forget to copy WinCENLS_Lang_0411 into your sys. otherwise, the device does not boot since WinCENLS_Lang_0411 is not included in xip.
2) if you take sys from any newer versions, taskmgr does not work since it is not signed by softbank. remove mxipupdate_taskmgr_shell_1.provxml in base_lang_0411. it's useless, anyway.
3) this method does not create shotcuts in windows\appbuttons. you need create those shortcuts with japanese names yourself to make the buttons work properly. (does anyone know how these shortcuts are automatically created?)
4) os ver info is stored in the original files. (read here for details: http://forum.xda-developers.com/showpost.php?p=1172925&postcount=1) you can change the ver info as you want, but i REALLY hate to see ver info with someone's name or some personally customized splash screeens. so, the ver info does not reflect the actual ver you take all the files from.
5) i don't think this works only with hermes but with any other qvga devices (you have to change xip part.) hope many other qvga device users can make (assemple?) their own japanese wm6.1 roms freely.
question:
i made a shortcut file with 14 japanese (2 byte) letters and put it in the windows directory, but the hermes did not boot. i changed the name to 13 japanese letters, and then it booted... are there any filename restrictions for east asian language files??
reserved for step-by-step guide
here is the japanese wm6.1 cooking base files for hermes
sys: 21014
xip: 21014
oem: basically based on htc oem
http://www.mediafire.com/?3almqggzvgy (OS.NB.payload is not included. place one in rom folder.)
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://www.mediafire.com/?2gfymtframj
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning. (.VM is not included. take it from another hermes rom to cook it!!)
happy new year, and happy cooking!
Congrats and welcome to hermes cooking sir. if you need a copy of a unprotected rom of mine, just let me know, PM or post
Peace sir,
Joshua
Very big thank for you...
qtotter said:
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://www.mediafire.com/?2gfymtframj
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning.
happy new year, and happy cooking!
Click to expand...
Click to collapse
I'm Andy. Thank you very much, qtotter-san.
Lately I've been thinkin about changing my handheld (I'm using BA and MPx200 at this moment). But, despite my condition as a Japanese language student, I would love to have a Handheld powered by Japanese Windows OS. To buy Japan's handheld seems to expensive for me, so I decided to search for Japanese ROM first, then decide which one shall I buy.
I've been searching all the time for Japanese ROM (not 日本語化 ROM but 日本語版 ROM FILES), n finally, look what I found here, not only Japanese ROM, but Hermes WM6.1 Japanese cooking base (very big thanks ^o^). I've tried to search in xda-developers, and some other forum, but still unable to find Japanese ROM. I'd also sent private messages to Japanese developers here, but still I have no idea where to find Japanese ROM.
And now, I found this thread. This really helps me.
心から感謝を申し上げます。(kokoro kara kansha wo moushiagemasu)
Once again thank You very much, qtotter-san. I really appreciate your hardwork.
qtotter said:
sys: 20931
xip: 20931
oem: basically based on bepe's oem
others: commmanager and calc replaced for the touch looks
note: i did not modified the ver info in shellres.dll.0411.mui, and the ver info shown in control panel does not reflect the real os ver.
note2: this file is just for cookers. i will not provide the rom tuned up for my own use. i will not response to "please send me your rom" requests. (sorry)
link
http://rapidshare.com/files/178421014/hermes_jpn_wm6.1_cooking_base.zip.html
you can use these files FREELY since i simply assembled them from the other roms. they don't belong to be from the beginning.
happy new year, and happy cooking!
Click to expand...
Click to collapse
can't download not....can you release again? I want to cook JP 6.1 too...thanks a lot!!
could anyone tell me how to build OEM MMSLite?
antony34 said:
can't download not....can you release again? I want to cook JP 6.1 too...thanks a lot!!
Click to expand...
Click to collapse
it seems like it's been downloaded 10 times, already... the link has been updated.
qt
qtotter said:
it seems like it's been downloaded 10 times, already... the link has been updated.
qt
Click to expand...
Click to collapse
Thanks a lot!!!
I hope the explanation of WM6.5,please!
Opal/Diamond Dialpad
if you use opal dialpad with japanese wm6.1 rom, smart dialing stops working. i happened to find a solution while playing with my diamond. just delete the following reg key to make smart dialing work.
[HKEY_LOCAL_MACHINE\Security\Phone\PhoneKeyMatch]
"SmartFilterFlags"=dword:00000002
This entry is in the *.rgu of Base_Lang_0411.
Download won't start
Is anything wrong with the server?
Woops!
Problem solved by deleting temporary internet files
updated japanese wm6.1 base to 21014
i will update msg #3 shortly.
Thanks qtotter sann!
but BT seem have problem, once flash it. it show have not BT device...
antony34 said:
Thanks qtotter sann!
but BT seem have problem, once flash it. it show have not BT device...
Click to expand...
Click to collapse
no bt applications are included. (drivers are included.) please use any bt apps from your favorite roms.
qtotter said:
no bt applications are included. (drivers are included.) please use any bt apps from your favorite roms.
Click to expand...
Click to collapse
But I can't avaliable BT at comm manager...
antony34 said:
But I can't avaliable BT at comm manager...
Click to expand...
Click to collapse
confirmed. i will check what causes this later.
May I ask some one to upload a COOKED Japanese rom?
I am far from to play with Hermes, have switched to Raphael.
qtotter said:
confirmed. i will check what causes this later.
Click to expand...
Click to collapse
qtotter sann,
Wifi & Camera seem also have problem.
Wifi & Camera sometime got error when avaliable.
I will keep report if still have problem or bug.
Thanks!
I have been working on this new ROM Kitchen project over the last months.
Public beta can be found here:
http://www.darkforcesteam.com/showthread.php?p=3560
Downloading this minute. Is it also for old devices? (Blue Angel?)
Sounds great, thanks for this kitchen
motisu said:
Downloading this minute. Is it also for old devices? (Blue Angel?)
Click to expand...
Click to collapse
Should theoretically work for all HTC devices.
Only have an HTC Diamond to try it myself, but others tested it on Universal, HD, Raphael, ...
Nice to see you back Bepe!, Happy New Year
OMFG
bepe, you've completely outdone yourself this time!!! Checked out the videos, looks amazing!! Congratulations.
Downloaded, will check it out and post results. Thanks!!!
Hmm.it will work on all htc devices.
maybe some older dev cant use,need to test by yourself
really nice Rom Kitchen.
Great jod!!!
Cheers
Monkeybape
i second the post with the video tutorial !! great work and even me is able to build a rom now *lol*
Is removal of unneeded files from XIP supported, bepe??
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
chavonbravo said:
Is removal of unneeded files from XIP supported, bepe??
Click to expand...
Click to collapse
yes, it possible to add/remove all files/modules you want. It works the same way as in IMGFS... just delete the file/module from the XIP package or add a new one to an existing or new package.
the Kitchen will not include files that are not needed like boot.rgu, *.rgu, *.dsm to the XIP section, so there is no need to remove them after the XIP partition is build.
mbarvian said:
this look fantastic bepe, as usual
even though I have tested it, I noticed two things:
1. Wouldn't replacing WINCE_NLS in the XIP from a different device, let's say, cause the phone not to boot?
2. What if the device you are porting from has a different resolution, wouldn't you have to change the files in the SYS manually?
other than that, it looks GREAT!
thanks again
Click to expand...
Click to collapse
1. replacing WINCE_NLS is not really a problem, but the size of the .nls file might be.
example:
- you are using a WWE Kitchen with a WWE nls size: 267 KB
- you want to change lang to CHT, the nls size would be 1500 KB
--> this means the size of the xip section would grow very much
--> ROM\os.nb.payload is WWE and would not have enough space for the bigger CHT XIP
--> ImplantXIP.exe should give you an error I think... never tried it...
solution: use the CHT os.nb.payload (just replace the WWE .\ROM\os.nb.payload by the CHS one)
The CHS roms would have more space for XIP, so all would be working fine
2. Using another resolution is not a good idea... most SYS packages are compatible, but there are packages like this:
- Base_DPI_192 - this is for 192 DPI like Diamond, Raphael, HD
- Base_DPI_96 - only for QVGA devices
- base_dpi_192_resh_480_resv_640 - this package tells you the exact resolution it was made for
You could mix two builds, like using only new packages without *_DPI_192 or *_dpi_192_resh_480_resv_640 in the name...
... but not really a good idea, even that many ppl are making that. Consider that there might be resources that might be changed
Would take a look at it, but the forum requires compulsory registration to view.
Please fix your forum.
It tells me I'm missing msvcr71.dll when I try and dump. I noticed that file is other kitchens so I tried to copy it over and it starts the dump but then RecMod.exe stops responding and it asks to close.
I keep getting this error when it comes to running platformbuilder
Code:
This aplication has requested the runtime to terminate it in an unusal way
boo, I wanted to watch the tutorial on your forum again, getting an initflashfiles .dat not where it's supposed to be error. but your forum seems to be down, or under too high traphic right now, is there any way you would think of putting together a short text based info set on everything we need to know to dump and rebuild? if not, no biggie, I am sure I will figure it out, like any great new tool, there is always a learning curve Thanks much for sharing your work with all of us though
Good to see you back bepe!!! I will give this a shot later on today...
outstanding bepe!! I thought your tutorials were excellent too!
thanks bepe
tested your kitchen on my Elfin and it worked well except for implantxip, because i've reduced the size of my XIP partition in template payload, so implantxip gave me error like "no xip section found". i replaced implantxip with msflshtool and it worked fine. no other issues faced in ROM building and porting newer build for my Elfin . although i had to make some adjustments to Dump_200.bat for dumping the ROM.
also, we used buildxip for xip porting before and it had some specific switches like -g, -k and -f useful for enabling different kernel modes, changing fsrampercent etc. i was wondering if same is possible while xip porting with new kitchen or is the best setting chosen automatically?
and, do check your paypal for Transaction ID: 45A49499TS934251W
All,
I own an MwG (formerly ubiquio) 501 and eventually started looking for software updates for it. The device is mostly ditto to the imate JAQ3, so I proceeded as follows:
1- get a WM6.1 ROM for JAQ3 (as linked in a thread of this very forum)
2- try to flash it (fail)
3- disassemble the ROM with tools from chinese website (osnbtool.exe)
4- port XIP merging with the ROM of my own device (thanks to the wonderful manual full xip porting thread!)
5- insert my original IMGFS of SYS and OEM
6- success!
the current situation is (settings -> about)
CE OS 5.2.20269 (Build 17936.0.3.0)
The performance boost obtained by upgrading the XIP is significant (keyboard is usable and video playback is ~ 15fps @ full screen), but I would like to perform more optimizations (e.g. switch to .NET CF 3.5) but as soon as I start to work with the dumped SYS and OEM I have troubles, it seems that every kitchen is expecting to work on the XIP (or on .nb and .nb.payload) but such files are not compatible with the one I get from osbntool.exe (but the dump folder is).
Do someone have advice on how to proceed? I would like to either
1-find a kitchen that works with my device
2-go for manual cooking
For 2 I achieved to split the dumped folder to packages and removed some of them, then - as far as I understood - I would need Greloc (got it) and bepe's buildos.exe (nowere to be found )
Is someone willing to help me? Thanks a lot.
Rest assured I am going to share the obtained ROM (I am already willing to share the current one, of course, just drop me a line!)
Best,
DAniele