I have tried several different roms to see if any difference is made. The only rom i have found that correctly receives these files is the TMO wing original ROM. Is there a setting I'm missing? I'm currently using the gullumTF2D_II_Herald rom.
thanks for any help
Related
ive installed the weatherfix on my kaiser. everything worked fine but ive lost the other functions like buddys and sounds. so i unistall the patch and got my old home plugin back. trough this process i got another problem:
i cant get any weather-data.
does anybody know how i can fix this problem?
thanks for your help
im really a newbie and searched all the forum. ive read over 200 posts in this forum: http://forum.xda-developers.com/showthread.php?t=319187 because i thought it would be the right forum and used the search function over 7 hours. but i dont get the answer to my question. if somebody just would send me the link it would be great. ive downloaded a lot of stuff to fix this problem in this forum, but my problem is that i dont know whats excacly the answer to the problem and i dont want to crash my tilt. its my first windows mobile device.
I'm going through something similar, if I understand you correctly.
You installed N2A's fix to be able to get weather data on custom locations? When you say that you can't get any weather data do you mean just for the new location you created or is it the same for any other location in the default list?
I also have the same problem. anyone know how to get local weather on the HTC home working?
Me Too
I would like the local weather too.
i got the same problem with my wizard, i just done a hard reset.. x)..
I've managed to get this working perfectly thanks to this thread:
http://forum.xda-developers.com/showthread.php?t=319187&highlight=weather+htc+xml
I'd followed the guide before to install the patched version of HTC Home provided, but as has happened to other people my icons got messed up. It also stopped the backlight changing shortcut in HTC Home from working (I tried a few of the patched versions and none seemed to like the backlight).
In the end I found it much better just to patch the htchome.dll file on the version already installed on my Kaiser, following the guide at the bottom of http://weather.not2advanced.com/files/ linked from the first post in the above mentioned thread. That way I got to keep things exactly how they were and how I like them with the added advantage of working weather info.
I then set the attributes of my patched dll to System and Read Only and removed Archive to match the attributes of my original htchome.dll in my Windows folder. I was able to replace the file using Resco Explorer - it asked if I wanted to overwrite the existing file and then warned me that the file was in the ROM and replacing the file could break my device. I confirmed the overwrite and told it I was sure I wanted to write the patched dll to ROM and it all worked out very nicely.
I'm using Dutty's 2k8 ROM (v3 final) and my htchome.dll file shows version 2.0.814.722. Here's a copy of my patched dll for anyone that wants to use it - I strongly suggest only using it if you're using the same ROM as me and the version number is the same. I've no idea what would happen if you tried to replace a different version and I won't be held responsible for anyone trying it .
se0siris said:
I've managed to get this working perfectly thanks to this thread:
http://forum.xda-developers.com/showthread.php?t=319187&highlight=weather+htc+xml
I'd followed the guide before to install the patched version of HTC Home provided, but as has happened to other people my icons got messed up. It also stopped the backlight changing shortcut in HTC Home from working (I tried a few of the patched versions and none seemed to like the backlight).
In the end I found it much better just to patch the htchome.dll file on the version already installed on my Kaiser, following the guide at the bottom of http://weather.not2advanced.com/files/ linked from the first post in the above mentioned thread. That way I got to keep things exactly how they were and how I like them with the added advantage of working weather info.
I then set the attributes of my patched dll to System and Read Only and removed Archive to match the attributes of my original htchome.dll in my Windows folder. I was able to replace the file using Resco Explorer - it asked if I wanted to overwrite the existing file and then warned me that the file was in the ROM and replacing the file could break my device. I confirmed the overwrite and told it I was sure I wanted to write the patched dll to ROM and it all worked out very nicely.
I'm using Dutty's 2k8 ROM (v3 final) and my htchome.dll file shows version 2.0.814.722. Here's a copy of my patched dll for anyone that wants to use it - I strongly suggest only using it if you're using the same ROM as me and the version number is the same. I've no idea what would happen if you tried to replace a different version and I won't be held responsible for anyone trying it .
Click to expand...
Click to collapse
Works perfectly thanks a million. I always wanted the weather to wok
So i would do my research and properly learn how to extract all the files out of the rom but i'm on a time limit and have to ask!
I'm sending my AT&T Tilt to my dad in saudi arabia noon tomorrow. (the tytn II is $850 over there and the tilt is $400, same thing just no front camera) so he needs arabic on it and i'm loading the HTC arabic rom on it now and sure its gonna run like crap. SO i want to cook arabic onto sleuths 6.1 rom.
I got the kaiser kitchen, put the .nbh into base rom, ran !begin.exe and it extracted the rom for me.
I went through the files, i found ARA_IN4_Arabic.cab and ARASIPSetting.exe
I installed the cab and seems to put arabic on the device but the SIP isn't working, i tried to ruch the ARASIPSetting.exe on the device but nothing would happen, i put it in the windows folder but still can't use the arabic SIP or edit its options in the Input settings... any help would be great... as i said i'm trying to figure this out tonight hence i ask for help rather then read all the rom cooking and dumping readmes (although i've already read a couple, i still can't figure out how to trace which files are needed)
Thanks in advance.. heres to hoping. x
fone_fanatic said:
So i would do my research and properly learn how to extract all the files out of the rom but i'm on a time limit and have to ask!
I'm sending my AT&T Tilt to my dad in saudi arabia noon tomorrow. (the tytn II is $850 over there and the tilt is $400, same thing just no front camera) so he needs arabic on it and i'm loading the HTC arabic rom on it now and sure its gonna run like crap. SO i want to cook arabic onto sleuths 6.1 rom.
I got the kaiser kitchen, put the .nbh into base rom, ran !begin.exe and it extracted the rom for me.
I went through the files, i found ARA_IN4_Arabic.cab and ARASIPSetting.exe
I installed the cab and seems to put arabic on the device but the SIP isn't working, i tried to ruch the ARASIPSetting.exe on the device but nothing would happen, i put it in the windows folder but still can't use the arabic SIP or edit its options in the Input settings... any help would be great... as i said i'm trying to figure this out tonight hence i ask for help rather then read all the rom cooking and dumping readmes (although i've already read a couple, i still can't figure out how to trace which files are needed)
Thanks in advance.. heres to hoping. x
Click to expand...
Click to collapse
The best thing to do is flash with 1.2Sleuth ROM. It is a 1.60 ROM and works great. use also 1.27.12.17 Radio. After unzipping the attached In4Mobility Package, copy the exe file onto your SD card, and open from there. Install all three files on your DEVICE MEMORY... NOT THE SD CARD. After that do a soft reset. Go to In4mobility in the settings folder and enable Arabic. Then enable Arabic Language and enter location.. etc..in the other in4mobility folders in the 'Programs".
Good Luck.
Sorry I am not able to load the In4Mobility File. PM me your email address and I can email it to you.
Hi all,
I need some advice on doing something that was fairly easy to do in WM6.0 ROMs, which is changing the default keyboard skin by replacing the msim.96.dll.0409.mui file.
I've tried a number of WM6.1 ROMs and this does not work. The only way I have been able to get the .mui file working was to re-cook the ROM and using an OEM package. Even after I re-cook with a new keyboard skin and try to replace the .mui file it does not work. Very strange.
Any of the cooks out there have any ideas why this is? I did a reg. dump of a ROM with and without the keyboard OEM package but did not find anything specific that would show why this does not work.
Appreciate any feedback. I know this works without any issues in WM6.0 ROMs.
Thank you.
Don't know what your doing wrong buddy but most of the time you need to cook the new .mui file in like I always do and i have no issue with the WM6.1 roms ever using the grey keyboard that I always use in my roms. To get this straight your dumping the rom and then copying the new .mui file right over the old file if there is one at all then rebuilding the rom? that is the only way it will work you can't copy over it once you have rebuilt the rom it needs to be cooked in.
austinsnyc,
Thanks for the response.
If I cook the .mui file in a ROM it works fine. The problem is not being able to replace the file (even though the file is overwritten). I was able to do this in WM6.0 ROMs but it doesn't seem this is possible in WM6.1 ROMs and I just wanted to confirm it.
So if I dump, change file, re-cook, works fine. I guess I'll have to do that with any of the new WM6.1 ROMs I end up running.
Thanks again.
ecltech said:
Hi all,
I need some advice on doing something that was fairly easy to do in WM6.0 ROMs, which is changing the default keyboard skin by replacing the msim.96.dll.0409.mui file.
I've tried a number of WM6.1 ROMs and this does not work. The only way I have been able to get the .mui file working was to re-cook the ROM and using an OEM package. Even after I re-cook with a new keyboard skin and try to replace the .mui file it does not work. Very strange.
Any of the cooks out there have any ideas why this is? I did a reg. dump of a ROM with and without the keyboard OEM package but did not find anything specific that would show why this does not work.
Appreciate any feedback. I know this works without any issues in WM6.0 ROMs.
Thank you.
Click to expand...
Click to collapse
austinsnyc said:
Don't know what your doing wrong buddy but most of the time you need to cook the new .mui file in like I always do and i have no issue with the WM6.1 roms ever using the grey keyboard that I always use in my roms. To get this straight your dumping the rom and then copying the new .mui file right over the old file if there is one at all then rebuilding the rom? that is the only way it will work you can't copy over it once you have rebuilt the rom it needs to be cooked in.
Click to expand...
Click to collapse
Actually you can change it easily via cab install but you need to sign it first. You can try the attached cab, and here: http://forum.xda-developers.com/showpost.php?p=1610615&postcount=3 for other skin.
Try this. First import the attached Keyboard Cert registry file (use dotfred's task manager which does registry editing, or resco registry editor). Once you do that, you should be able to use the various keyboard cabs. I've attached one that has like 20 keyboard styles you can choose from (uses mortscript to do this). Choose the one you want, soft reset, and presto...
sakajati said:
Actually you can change it easily via cab install but you need to sign it first. You can try the attached cab, and here: http://forum.xda-developers.com/showpost.php?p=1610615&postcount=3 for other skin.
Click to expand...
Click to collapse
sakajati,
Works fine now. Thanks for the links.
mfrazz,
Thanks for the info also! Appreciate it.
Ok I have taken the official windows mobile 6.1 rom from att and used the kitchen to extract RUU_signed.nbh which was successful in unpacking. I added one Package to oem folder and used kitchen buildos option. Rom was built successfully however when flashed to device it never even boots. More interesting than that is the New RUU_signed.nbh files is actually smaller than the original Ruu_signed.nbh file that was in the Cingular Official 6.1. Anyone with any ideas. Keep in mind that I have successfully built several roms based on the latest official cingular 6.0 rom with out any problems. Has something changed? Do I need a special WM6.1 Kitchen? Please Help me.
first, which kitchen are you using?
the (!!!readmefirst!!!.txt) says kitchen 0.3.
Pampered4Life said:
the (!!!readmefirst!!!.txt) says kitchen 0.3.
Click to expand...
Click to collapse
kaiserkitchen?
I would try updating to the latest version just to make sure, then we'll continue
Same situation. Kitchen RAR FIles says KaiserKitchen 1-20-08.rar extract and build succeeds however same scenario as decribed in original post. Strangely enough can use the same kitchen but using the att official wm6.0 rom and works flawlessly. If you would like I am willing to send an invitation for remote assistance via email to you for help?
I doubt it...
but, just out of curiousity, can you attach your one package that you are adding?
Fixed. Forgot I disabled a .net assembly in the configuration. Thanks anyways man.
Hi, never extracted a radio before, and I am totally blind so I can't use windows 6.5 yet, so just want the radio from the 6.5 rom, I extracted the .nb files from the spl.nbh and the ru_signed.nbh and they both have a 22.1 mb file which I asume is the radio, however two things, I don't know which is the correct one and even tried both but get an error that invalid model id when using the ru, do I need to sign the nb before converting it back to an nbh or please give me some guidence in this process.
gigawatt said:
Hi, never extracted a radio before, and I am totally blind so I can't use windows 6.5 yet, so just want the radio from the 6.5 rom, I extracted the .nb files from the spl.nbh and the ru_signed.nbh and they both have a 22.1 mb file which I asume is the radio, however two things, I don't know which is the correct one and even tried both but get an error that invalid model id when using the ru, do I need to sign the nb before converting it back to an nbh or please give me some guidence in this process.
Click to expand...
Click to collapse
Take a look at this post, I alreaday did it.
http://forum.xda-developers.com/showthread.php?t=550863
the radio you did was the one from the t-mobile 6.5 windows mobile and is it the thrd post with radio 3.47.25.29 because I thought the radio was higher then that, and if I wanted to do it myself how could I?
Dash 3G, Snap ROM V 122209 can used in C720W?