Hi All,
Does anyone making use of this forum know how to extract .dll''s that are classified as System / ROM/ Read-Only. Using Explorer on XP does not copy / rename or delete these locked files. Using any explorer from within WM2003 has he same result. Also, for those in the know-how: Is the tapres.dll file part of the OS ROM or simply installed to the ROM via a CAB file that contains this .dll? If the latter is true than there is hope yet.
Thank you
http://www.xs4all.nl/~itsme/projects/xda/dumprom.html
.dll file required
Hi,
Mamaich, thank you for the prompt response. However frustrating, I must admit that I simply do not have enough knowledge to work with the program recommended. (It keeps on getting an error and closes on start-up) In an effort to save time, would it be possible for you (or anyone else for that matter) to extract 'tapres.dll' and 'tapres.69.dll from a WM2003SE PE device and post it here? All I need to do is to inspect the stucture of the file and its contents with the view of using a copied version thereof with modified graphics, which will probably then be implemented with registry tweaking.
Your efforts are appreciated.
Device: imate PCCPE (PH10B)
ROM: 2.02.t1WWE (05/17/04)
Radio: 1.18.00
Protocol: 1337.38
Ext ROM: 1.72.126
OS: WM2003SE
if you just want a tapres.dll version: Copy one of the T-Mobile based ExtROM files, search a bit thru the CAB's in it and extract tapres1.dll
This version contains the T-Mobile skin version of the pressed dialer keys.
No need to extract an original tapres.dll from the system rom for this.
Re: .dll file required
Syntax:
dumprom.exe nk.nba -4 -d c:\ROM
this would extract all files from nk.nba to c:\rom directory on your drive. The directory should exist.
Re: .dll file required
forumxda said:
Hi,
Mamaich, thank you for the prompt response. However frustrating, I must admit that I simply do not have enough knowledge to work with the program recommended. (It keeps on getting an error and closes on start-up) In an effort to save time, would it be possible for you (or anyone else for that matter) to extract 'tapres.dll' and 'tapres.69.dll from a WM2003SE PE device and post it here? All I need to do is to inspect the stucture of the file and its contents with the view of using a copied version thereof with modified graphics, which will probably then be implemented with registry tweaking.
Your efforts are appreciated.
Device: imate PCCPE (PH10B)
ROM: 2.02.t1WWE (05/17/04)
Radio: 1.18.00
Protocol: 1337.38
Ext ROM: 1.72.126
OS: WM2003SE
Click to expand...
Click to collapse
i made some littel experimentation instead of extracting the tapres.dll but creating my own tapres.dll base on TapResCandyRed.dll
and manage to create a pressed button skin for .. both portrait and landscape .. but im no artist so its kinda .. messy .. btw heres the files
the skin is base on aladdin's work i already pm him the files but he seems not havent read it yet so .. i will post it here ..
http://forum.xda-developers.com/viewtopic.php?t=19269
PS i also include the cab for aladdin's skin with Pressed Button and with no pressed button
TapResCandyRed.dll
Hi All,
Thanx for all responses.
Toenailed: I'm with you on creating an .dll file based on TapResCandyRed... I have been trying to find the thread on those two .dll's but it is pretty much an exersize in frustration. I presume that you have the link to it, or better yet, please post the TapResCandyRed.dll file for me ;-)
Mamaich: thank you for syntax explination - sadly I still can not get it to work. Reason being that I do not have any actual ROM files to extract (nba files I pressume). I only have ROM update files (nbf)
EdSub: I have searced my entire complement of IntelliDailer CAB's (I have quite a few) for the file tapres.dll. Presumably, this particular .dll file should be contained within one or another IntelliDailer CAB? I do happen to have the T-Mobile versions as such, but they only contain certain common dll's, i.e: intellidailer.dll, iacontacts.dll, DisplayCID.dll, ContactsSDK.dll Also, bear in mind that when hard-resetting the device, followed by a soft reset before auto-installation of Ext ROm files, the pressed button display / contacts display will still be there, in the normal blue /green graphics. It is therefore safe to say that the tapres.dll file is common to the OS ROM and that it is not replaceable with anything from a IntelliDailer.CAB file, as they do not contain anything with respect to the tapres.dll file.
I recall from a post some time ago that someone mentioned two CAB file versions for the phone dailing pad: one for T-Mobile (grey / pink) and the other for the normal blue / green (O2?). As mentioned already, none of the IntelliDailer CAB's i've searced so far contains any tapress.dll. Could it be that it is contained in another CAB file altogether? I would have searced all my Ext ROM's given the time, which unfortunately I do not have.
So, Toenialed, please post the TapResCandyRed.dll thread (or file) if possible, it can only save time and trouble.
Cheers all.
Device: imate PPCPE (PH10B)
ROM: 2.02.t1WWE (05/17/04)
Radio: 1.18.00
Protocol: 1337.38
Ext ROM: 1.72.126
OS: WM2003SE
Pressed Button Display
Thank you Toenailed, I see that you edited your post as I was busy entering my reply. Right, I too have a working pressed botton display for the phone pad (changed to the icon file (.ico) as included in aladdin's .dll file) Thank you Aladdin ;-)
Now that we have the ability to change the pressed button appearance, we can have more 'artistically-inclined' forum users produce various end results. I have not asked permission to include these .ico files from aladdin's .dll, but trust that there will be no issues? Please accept that all credit goes where it is due, without mentioning of particular names. Next on the list, I would imagine, is to change the green button display for the contact list and the blue 'Back / Next' buttons at the bottom of the screen in the contact display. Am I to presumme that we are not looking for bmp's but rather for .ico files to alter the phone pad 'pressed button' and contact list 'blue / green' appearances?? If this is the case, more inspection of the .dll files for IntelliPad is necessary. I have been looking for bmp's all a long.
Let me know your thoughts. Once again, credit goes out to those whom it is due. Thank you EVERYONE who has replied to this post so far - it has indeed been of tremendous assistance.
In the meanwhile, here are the .ico files for artistic revamping (pressed button display for phone pad). They are however included in .jpeg file format - as per limitation of this forum
Cheers.
Device: imate PPCPE (PH10B)
ROM: 2.02.t1WWE (05/17/04)
Radio: 1.18.00
Protocol: 1337.38
Ext ROM: 1.72.126
OS: WM2003SE
Pressed button display
Hi All,
I just thought of something: it probabaly isn't necessary to faciltate the use of .ico files at all.. presumably, Aladdin used it for functional purposes only - to limit the size (and therefore loading speed) I am sure that the .dll file can be altered to use bitmaps instead, if necessary.
Mamaich or EdSub: I need a huge favor! Please use the dumprom faciclity and extract the tapress.dll. tapres.96.dll files from a PPCPE WM2003 device and post them here. It will take me too long to figure out how to use dumprom, I have not been successful yet - even with your syntax guidance (for which I am grateful anyway)
At this stage it is unclear whether or not the tapress.dll file controls just the pressed button display, or addidtionally has something to do with the green button contact list display and blue 'Back / Next' buttons in the same contacts display (bottom of screen). I will only know once I have inspected the actual tapres.dll / tapres.96.dll files.
My guess is that tapres.dll controls only the pressed button display of the phone pad, as altering it in the registry brings about an altered appearance of the pressed button display only. If this is true, we need to find which .dll controls the contacts display button graphics.
Thanx & Cheers.
hi forumxda ..
heres the TapResCandyRed.dll and TapResWoodAndChrome.dll by Tadzio
it only contain the ico of the portrait mode of phone pad since he gets it in wm2003se
you can find it here
http://www.tadzio.com/ppc
and the thread discussion is in here
http://forum.xda-developers.com/viewtopic.php?t=4653
i also attach the extracted tapres.dll and tapres.96.dll of 2.06.00WWE WM2003SE ..
the original skin posted by aladdin1001 found in this
thread
http://forum.xda-developers.com/viewtopic.php?t=19269
he done pretty good job in this .. :wink:
but since the original skin doesnt have a pressed skin button i use the TapResCandyRed.dll by tadzio and replace it with the one that i get from aladdin1001's skin and since the TapResCandyRed.dll contains only an ico for Portrait Mode .. i made some little experimentation and lots of trial and error to make an ico for Landscape Mode ..
i rename the TapResCandyRed.dll to aladdin1001.dll since i get the gif to make the ico of both landscape and portait mode on one of aladdin1001's gif file ..
and put aladdin1001 on credit since the hardwork of creating the skin is all on aladdin1001 and not me .. and because i have a himalaya device not a magician .. i first send to him thru PM the files that i created so he can test it first if its working to his device ..
anyway the Phone Application looks for the icon group of a dll
that was stated in this registry section ..
[HKEY_CURRENT_USER\ControlPanel\Phone]
"IcoFil"="aladdin1001.dll"
"IcoId"=dword:000056BD or 22205 in decimal value
"IcoId_Land"=dword:000056FB or 22267 in decimal value
the IcoFil is the dll file to use on Pressed button skin
the icoid is the Icon Group ID of the Pressed skin for Portrait
the icoid_Land is the Icon Group ID of the Pressed skin for landscape
the other registry value that i dont know exactly for, since im getting an error viewing it in tapres.96.dll .. so i didnt created the icon group for that ..
"IcoId_Sqre"=dword:000056FE or 22270 in decimal value
now the question of why i use the TapResCandyRed.dll instead the Tapres.dll or the Tapres.96.dll (this one really contains the default Pressed Button Skin) because both contains lots of Resources which i think it is not needed since i only want to create a Pressed skin for Phone Application ..
btw keep the Good up Works in exploring our great device .. i will just here to help .. :wink:
Pressed Button Display
Hi Toenailed,
Many, many thanx for all the info, descriptions, files and thread-links Bro.. Now:
1) ;-) I have located those elusive green & blue icon graphics that appear in the contact list from the phone pad.. They are resident in the tapres.96.dll file (amongst many other delicious goodies)
2) :-( I am unable to locate any registry information pertaining to this file, using Resco Registry Explorer anyway. We can alter the extracted tapres.96.dll to include other icons, but it appears that no subsequent registry tweaking can be done to facilitate the altered file. The file shows up in the Windows directory, but needless to say - it is classified as ROM/ System/ Hidden bla, bla, bla.
So... if we make a CAB file that will install this new tapres.96.dll file into the ROM, do you (or anyone else watching this topic) think that we can overcome this small hurdle? It could be that installation problems will result due to the existing ROM file of the same name. We could of course hardcode the installion path in the CAB... To my current knowledge, it is impossible to disable / delete / rename / (do anything really) with the existing tapres.96.dll file located in Windows.
Are we going to try this route? Let me know before I embark on altering the tapres.96.dll file.
For now, here are those pesky green-blue monsters... (some look odd due to .ico / .jpeg format saving: i.e forum limitations)
Again, thank you.
Device: imate PPCPE (PH10B)
ROM: 2.02.t1WWE (05/17/04)
Radio: 1.18.00
Protocol: 1337.38
Ext ROM: 1.72.126
OS: WM2003SE
Re: Pressed Button Display
forumxda said:
Hi Toenailed,
Many, many thanx for all the info, descriptions, files and thread-links Bro.. Now:
1) ;-) I have located those elusive green & blue icon graphics that appear in the contact list from the phone pad.. They are resident in the tapres.96.dll file (amongst many other delicious goodies)
2) :-( I am unable to locate any registry information pertaining to this file, using Resco Registry Explorer anyway. We can alter the extracted tapres.96.dll to include other icons, but it appears that no subsequent registry tweaking can be done to facilitate the altered file. The file shows up in the Windows directory, but needless to say - it is classified as ROM/ System/ Hidden bla, bla, bla.
So... if we make a CAB file that will install this new tapres.96.dll file into the ROM, do you (or anyone else watching this topic) think that we can overcome this small hurdle? It could be that installation problems will result due to the existing ROM file of the same name. We could of course hardcode the installion path in the CAB... To my current knowledge, it is impossible to disable / delete / rename / (do anything really) with the existing tapres.96.dll file located in Windows.
Are we going to try this route? Let me know before I embark on altering the tapres.96.dll file.
For now, here are those pesky green-blue monsters... (some look odd due to .ico / .jpeg format saving: i.e forum limitations)
Again, thank you.
Device: imate PPCPE (PH10B)
ROM: 2.02.t1WWE (05/17/04)
Radio: 1.18.00
Protocol: 1337.38
Ext ROM: 1.72.126
OS: WM2003SE
Click to expand...
Click to collapse
hiya bro ..
ok since youve been asked .. there is a way to altered the tapres.96.dll and tapres.dll and almost all files in the ROM .. ..the exact tools or procedures for me .. is .. still a mystery .. but there is a way
look at my pic .. below .. instead of having "G" if you see a gprs signal .. i change the G to Te in Title Bar .. and T in Signal Notification .. (you have to have a GPRS signal to view it bro)
oki as a gift try to study the cab below .. and try it to install it.. just remember .. you have to have a have a gprs signal to view the Te and T ..
one more thing bro .. it is possible to edit/add/remove/or change the files in ROM .. but still you need a special tool to do it .. i havent seen one .. but this cab .. perform .. to my suprise ..
if you want to ask where did i get the cab .. you will be surprise its from the oem cab of wm2003se to be exact the intellipad.cab ..
and what you only need to change is the _MoveFileList and replace inside with this one
"\Temp\_tapres.96.dll" "\Windows\tapres.96.dll",
"\Temp\_tapres.dll" "\Windows\tapres.dll"
then rename the tapres.dll and tapres.96.dll to _tapres.dll and _tapres.96.dll
then include both to tapres96.cab that i provided .. run it to your xda, perform a softreset and then voila .. heheh just see for yourself bro .. :
Great
a very much great explanation and great work...idol.
:lol: :lol: :lol: :lol:
Lets cook then...
Hey Bud,
Thanx greatly for info and prezzie. I will experiment tonight and post results. This morning I modified the tapres.96.dll file to include altered (way better) icon graphics. Surprizingly though, coping the modified tapres.96.dll file to the device Windows directory was succesfull. I was unexpected, knowing that there is the existing similar-named file in the system ROM. That was followed by a soft-reset to see if it accepted the new tapres.96.dll file. :-( No luck yet... This points back to my last post where I mentioned that there is no mention whatsoever of the tapres.96.dll file in the registry. Only the tapres.dll file. I suspect that the file was not seen due to it not being 'fully' copied to the ROM - checking properties had the ROM attribute clear
By the way Toenailed, where you looking to obtain Borland Workshop??? I have the zip file should you need it ;-)
As with you, the ways and works of extracting the damn ROM still eludes me, everything that I have tried has been rather unsuccessfull... including the likes of Dumprom and XDA Tools (OS Image Tool) even with with explinations from pro's like Mamaich. A programmer I'm not, unfortunately.
Right... btw for me Cheers
Quick Explination request
Hi Budd,
OK, I have to be honest and need to ask you for a quick explination (noobie I am sometimes)
1) Quote1
""and what you only need to change is the _MoveFileList and replace inside with this one
"\Temp\_tapres.96.dll" "\Windows\tapres.96.dll",
"\Temp\_tapres.dll" "\Windows\tapres.dll" ""
(i) Question1
Inspecting you CAB shows the_MoveFileList as you describe it (except with the addition of a couple of spaces i.e: (\Temp\_tapres.96.dll" XTRA SPACES "\Windows\tapres.96.dll). I did not tamper with it much except exporting it, deleting the excess spaces, saving it & importing it back. I trust that there is nothing wrong with that??
2) Quote2
""then rename the tapres.dll and tapres.96.dll to _tapres.dll and _tapres.96.dll""
(ii) Question2
Must the tapres.dll and tapres.96.dll in the ROM be renamed to _tapres.dll & _tapres.96.dll PRIOR to running the CAB?
I modified your CAB to include _tapres.dll (renamed tapres.dll (original received from you - not one in your CAB file today) and _tapres.96.dll (renamed of modified tapres.96.dll by myself ealier today - incl new icon graphics). After running the CAB & soft resetting... no changes affected :-( :-( Scanning the registry afterwards for tapres.96.dll provided two entries: 1x tapres.96.dll & 1x tapres.96.dll1 Remember, I did NOT rename the ROM tapres.dll / tapres.96.dll to _tapres.dll / _tapres.96.dll before running the CAB.. hence the two question asked here.
I'm with you as far as changing the Status Bar - Notification Bar thingies: G - Te, G - T, etc is concerned - tried it succesfully earlier today ;-)
Have you come across any reference to tapres.96.dll in the registry?? I haven't - just tapres.dll
I will get this right with your help sometime, given that both you & I have enough patience that is....
Regardless, THANK YOU for your help so far.
Cheers Bro
Re: Quick Explination request
hiya bro ..
the cab that i post bro .. was just to give you an example that it is possible to manipulate the files in ROM .. and it is possible to modify,add,delete or rename (okih not exactly as delete and renaming since the os will generate the file if you remove or rename the files)
but it is editable and can be copied .. just need some tools like the oem cab .. if the oem cab can make the file in rom .. editable it is possible to create a program that will edit or copy the files that reside in rom ..
forumxda said:
Hi Budd,
OK, I have to be honest and need to ask you for a quick explination (noobie I am sometimes)
1) Quote1
""and what you only need to change is the _MoveFileList and replace inside with this one
"\Temp\_tapres.96.dll" "\Windows\tapres.96.dll",
"\Temp\_tapres.dll" "\Windows\tapres.dll" ""
(i) Question1
Inspecting you CAB shows the_MoveFileList as you describe it (except with the addition of a couple of spaces i.e: (\Temp\_tapres.96.dll" XTRA SPACES "\Windows\tapres.96.dll). I did not tamper with it much except exporting it, deleting the excess spaces, saving it & importing it back. I trust that there is nothing wrong with that??
2) Quote2
""then rename the tapres.dll and tapres.96.dll to _tapres.dll and _tapres.96.dll""
(ii) Question2
Must the tapres.dll and tapres.96.dll in the ROM be renamed to _tapres.dll & _tapres.96.dll PRIOR to running the CAB?
I modified your CAB to include _tapres.dll (renamed tapres.dll (original received from you - not one in your CAB file today) and _tapres.96.dll (renamed of modified tapres.96.dll by myself ealier today - incl new icon graphics). After running the CAB & soft resetting... no changes affected :-( :-( Scanning the registry afterwards for tapres.96.dll provided two entries: 1x tapres.96.dll & 1x tapres.96.dll1 Remember, I did NOT rename the ROM tapres.dll / tapres.96.dll to _tapres.dll / _tapres.96.dll before running the CAB.. hence the two question asked here.
I'm with you as far as changing the Status Bar - Notification Bar thingies: G - Te, G - T, etc is concerned - tried it succesfully earlier today ;-)
Click to expand...
Click to collapse
i already bro .. edited and provided what you needed so you dont need to modify bro the _movefilelist.txt .. :wink:
what you only need bro to do is to rename the tapres.dll and the tapres.96.dll that you created to _tapres.dll and _tapres.96.dll ..
then import it to the cab .. and remember this bro .. the _tapres.96.dll and _tapres.dll should be hardcoded to the TEMP folder .. y? i will explain it here bro .. .
anyway here what really goes as stated in _moveFileList.txt
usually the first statement under " " is the Source of the File and after a very long space the other " " means the destination of the file
"\Temp\_tapres.96.dll" -> Means the location of the file to be move.. so it is very important that the _tapres.96.dll is hardcoded to TEMP folder because it was stated that it came from the TEMP folder
"\Windows\tapres.96.dll", -> the destination of the file to be move.. so the _tapres.96.dll from the TEMP folder will be move to windows directory and will be rename to tapres.96.dll ..
"\Temp\_tapres.dll" -> Means the location of the file to be move.. so it is very important that the _tapres.dll is hardcoded to TEMP folder
"\Windows\tapres.dll" -> the destination of the file to be move.. so the _tapres.dll will be move to windows directory and will rename to tapres.dll
so what really happen in the cab is this bro..
all the file should be extracted to their designated path ..
but the _tapres.dll and the _tapres.96.dll will be extracted in TEMP folder
after extracting the cab will check the _MoveFileList.txt and check all the files listed .. since it is stated like this
"\Temp\_tapres.96.dll" "\Windows\tapres.96.dll",
"\Temp\_tapres.dll" "\Windows\tapres.dll"
the cab will search for the file _tapres.96.dll and _tapres.dll in the TEMP folder and if they found it will move the file to windows directory and rename the file to tapres.96.dll and tapres.dll
now why it move since tapres.dll and tapres.96.dll is both in rom and cannot be moved, copied or modified .. the cab provided all the things need to be able the files to move and replace with the new one ..
forumxda said:
Have you come across any reference to tapres.96.dll in the registry?? I haven't - just tapres.dll
I will get this right with your help sometime, given that both you & I have enough patience that is....
Regardless, THANK YOU for your help so far.
Cheers Bro
Click to expand...
Click to collapse
nope i dont find any thing bro .. and i dont thing you will be needing one ..
OK heres another way bro .. this is much simpler and less complicated and yes very editable ..
1. just rename the tapres.dll bro to
tapres.dll.0409.mui
and the tapres.96.dll to
tapres.96.dll.0409.mui
2. copy tapres.96.dll.0409.mui and tapres.dll.0409.mui to Windows Directory then perform a soft reset ..
then voila you have now the new skin .. :wink:
btw bro i attach a new set of dll .. which i think you will be love to see ..
just the same method bro .. after editing rename the files and add .0409.mui to the filename like shellres.dll.0409.mui etc ..
have fun .. :wink:
ps i attach bro one of the example that i created .. shellres.96.dll.0409.mui
i edited the bluetooth ico .. to look like the buzz bluetooth icon .. like in the picture ..bro
btw bro .. can you post the tapres.dll and tapres.96.dll that you edited bro ..
".dll modification project"
Hey Bro...
As always, thank you much for all your info. I will post my edited tapres.96.dll file for you shortly. Please bear in mind that it is highly experimental and by way of it, I would prefer to test on my device before handing over this Pandora's box. I identified a need for this after seeing that the back-up service that I use, Sprite Backup Premium, could not restore the the original tapres.96.dll file... I had to reflash the device with OS ROM, Ext ROM and Radio...
My knowledge on this stuff increases everyday and with your help we should be able to have a fuss-free way of altering the phone pad display in the near future. I am attaching a few pic's from my device to show what it currently looks like, including the user interface and dailing pad skin.
I will return to this post in the next couple of days or so as I am out of town for business.
Cheers Bro
hiya bro sowee for the late reply .. :wink:
about the tapres.dll and tapres.96.dll bro .. after altering the original tapres.dll and tapres.96.dll you can rename itnow bro .. and no need to flash the os .. it will return an error but it will rename the file and the os will generate the original tapres.dll and tapres.96.dll .. :wink:
about the mui bro ..
MUI means Multilingual User Interface .. its use to change the dll resources without altering the dll itself .. for different language resources it means that instead creating a whole resources for different for different native language you have only to include the diffrent language value describe in wnce.nls
the MUI is stated in this Following registry
[HKEY_LOCAL_MACHINE\MUI]
"Enable"=Dword:0x00000001 ->means enable if 1 and Disable if 0
"SysLang"=Dword:0x00000409 -> language resource uses in the DLL or Exe .. so it is very important to correctly specify the language resources of the bitmap, icon or string for example 409(hexadecimal or 1033(decimal)) means English(USA) to be able to understand by the os the resources .. :wink:
regarding altering of tapres.dll
Hi mates,
A question here, hope you can enlighten me.
Say, I modify my registry's "IcoFil" as mentioned above, to be say, "aladdin1001.dll", eg:
[HKEY_CURRENT_USER\ControlPanel\Phone]
"IcoFil"="aladdin1001.dll"
Since it was originally pointing to "tapres.dll", will there be any components missing? I am not able to see the original tapres.dll, could only take a glimpse of the tapres.dll provided by bros here using RESHACKER. So I'm not sure what the original "tapres.dll" consist of.
And by comparing the "aladdin1001.dll" with "tapres.dll", I notice there are a lot of components in tapres.dll, but aladdin1001.dll have only a few lines.
Any idea what I'm talking about?
Thanks & Regards,
[Charles]
Re: regarding altering of tapres.dll
charleslee said:
Hi mates,
A question here, hope you can enlighten me.
Say, I modify my registry's "IcoFil" as mentioned above, to be say, "aladdin1001.dll", eg:
[HKEY_CURRENT_USER\ControlPanel\Phone]
"IcoFil"="aladdin1001.dll"
Since it was originally pointing to "tapres.dll", will there be any components missing? I am not able to see the original tapres.dll, could only take a glimpse of the tapres.dll provided by bros here using RESHACKER. So I'm not sure what the original "tapres.dll" consist of.
And by comparing the "aladdin1001.dll" with "tapres.dll", I notice there are a lot of components in tapres.dll, but aladdin1001.dll have only a few lines.
Any idea what I'm talking about?
Thanks & Regards,
[Charles]
Click to expand...
Click to collapse
hiya .. charles ..
sowee for the late reply ..
the tapres.dll and tapres.96.dll is the original dll, i extracted from himalaya 2.06.00WWE ROM .. the one that really contain the pressed button skin is the tapres.96.dll ..
and yes theres lots of component that the tapres.dll and that aladdin1001.dll doesnt have.. i didnot include some of the components since the icofil stated in HKCR\ControlPanel\Phone is only looking for three skin ..
the Portrait Pressed Skin -> "IcoId"=dword:000056BD or 22205 in decimal value
the Landscape Pressed Skin ->"IcoId_Land"=dword:000056FB or 22267 in decimal value
and the Square pressed Skin -> "IcoId_Sqre"=dword:000056FE or 22270 in decimal value
i cannot test the Square Pressed skin.. so i didnot creat it either in aladdin1001.dll .. and since what i longing for is the Pressed Skin for both portrait and landscape and not some other stuff that the tapres.dll has to offer .. i only include in aladdin1001.dll the two resources .. aladdin1001(landscape).ico and aladdin1001(portrait).ico ..
I have begged my friend to dump the HK local ROM (from 838pro) for me. I have a Taiwanese CHT9000. After reading the previous articles, it seems that the files in my hand (3 raw files) cannot flash the ROM into my CHT9000. Is that correct? So, what's the purpose of dumping the ROM?
Sorry...I am the beginner here.
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeFAQ
Is it possible extract a ROM from a device and convert it to a flashable ROM? (to have a Backup or to flash it on another device)
Short answer: No, it is not possible.
Long answer: A ROM consists of 7 parts:
1. Extended ROM
2. OS Image
3. IPL (part of bootloader)
4. SPL (part of bootloader)
5. Splash screen
6. HTC Logo (normally uses the same image as the splash screen)
7. GSM radio code
You can dump the original rom, but only the things contained in the FLASH will be dumped, this does not include the IPL, SPL, splash and radio parts, so its unuseful for flashing it back.
Theoretically: if you would have the private keys for one of the 3 certificates stored in the bootloader, used to verify .nbh files, you would be able to create your own .nbh file, and flash it.
Click to expand...
Click to collapse
Hi pof,
Yes. I have read that. So, what's the answer? What does those raw files do? What's the purpose of getting the FLASH dumped? For development?
I used them mainly to see diffs betwen roms / vendors OS bundle and extract files from ROM. You can make a modified OS image out of a dumped OS rom, so when we will be able to flash our own code (see SD-image flashing on the wiki) you can delete unuseful files (help, images...) and add programs directly to the rom... but there's a lot of work to do until we reach that, and very few people can help in the research
Hi
I have another problem. I have dumped my MDA Vario II German ROM and extracted the Part02.raw.
If I try to use the extracted .cab files, the installation fails. Even I can't open the .cabs with Winrar.The files are damaged.
I've tested it with an other Part02.raw from the Developers FTP with the same result.
What's wrong ?
It semms, that the ROM dump ist useless.
Even, you can't use the midi and wave files.Also bmp and jpg files have the same problem.
Couriosity is, that some files work and most not.
I think it's the same problem with other parts of the romdump.
Hey guys
I dumped the black2.5 rom, hoping to make some modifications to the unlock app. Now I have a .raw image, but I am a little unsure as to reading it. I downloaded duttys koch, but I dont think that was the right approach. Im not seeing anything on the wiki, and my searching has brought me here. Can anyone point me in the right direction? Thanks.
@peezy:
Here's how to reconstruct a dumped rom:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoReconstruct
http://wiki.xda-developers.com/index.php?pagename=Trinity_HowtoReconstruct
But in your case, you have the NBH, so no need to dump & reconstruct, you can work with it with tadzio imgfs tools + bepe's packagetool.
pof said:
@peezy:
Here's how to reconstruct a dumped rom:
http://wiki.xda-developers.com/index.php?pagename=Hermes_HowtoReconstruct
http://wiki.xda-developers.com/index.php?pagename=Trinity_HowtoReconstruct
But in your case, you have the NBH, so no need to dump & reconstruct, you can work with it with tadzio imgfs tools + bepe's packagetool.
Click to expand...
Click to collapse
Hopefully a little humor won't get me in trouble, but with dutty's koch, tadzio's tool and bepe's package - you should have everything you need
@pof thanks a bunch!
@todd ahhhh yeeaaahh... <70's pr0n music.wav>
Hi everybody,
I just bought me a TyTN and did the Rom reconstruction procedure, this all worked very well (thx for the great guides), but with this procedure only the Part02 file is transformed into a .nbh file.
Is it possible to fully reconstruct the rom including, splash screen and most import the extrom. I still have all the four Part00 - Part03.raw files but don't know how to convert them to usable .nbh files, I also don't know what the other three PartXX.raw files are.
Cause at the moment when I load the reconstructed rom, I have the extrom from the last rom I had installed which of course is not the extrom of the reconstructed rom.
Any help on this would be great. Thanks.
wwwwwwiiiiiiikkkkkkkkiiiiiiii
Please read exactly what I'm asking for
@peezy: before shouting wiki, you should read my post exactly. I already succeeded in building an OS.nbh from my dumped ROM.
What I'm asking for is a FULL rom reconstruction, especially the extended rom is a problem if missing and I'm quite sure the extended rom and maybe also the boot images are in the other PartXX.raw files but I don't know how to create the missing .nbh files for flash and extended rom. What's not such a big problem is the radio rom. But in case I have to repair the phone I'd like to go back to the OS I had before flashing the WM6 LVSW including boot images and extended rom.
I already found a thread on how to create the boot images, but the problem is I have to pull out the boot images from the dumped ROM and the even bigger problem is the extended rom which I also have to reconstruct from the dump files.
unhide extrom, copy the files and use AnDim ExtROM editor to create your new extrom.nb. See stickies in this forum for more info.
For splash screens see here:
http://forum.xda-developers.com/showthread.php?t=306896
http://forum.xda-developers.com/showthread.php?t=299049
stuck with splash dumps
@pof: Thanks for your help, I was able to create the ExtRom with AnDim ExtRom editor and I tried to extract to splash screens with mtty and usbmonitor.
But I got stuck there because USB Monitor is kind of strange to handle if you don't know what you're doing, so I tried to extract the dumps on my gentoo box. At first with your supplied 'cu' command but that fails for what reason exactly I don't know. So I used ser2net to made my ttyUSB1 accessible with telnet. And then I did a dump of my telnet session with the rbmc command one for each splash screen.
Can you please explain what I have to do in order to get the .bmp's out of the dump files? I assume at first I have to clear out the telnet command lines at top and bottom, but I don't know exactly up to where I have to cut the files and how to convert the resulting file into bmp. Cause I'd like to dump the images from a colleagues phone (which has special boot images and no downloadable rom upgrade).
or maybe you can give me a correct 'cu' command for dumping the stuff directly without having to capture the telnet session.
Thanks for you help
@marcelser: just remove everything before HTCS, and everything after HTCE. Then you have HTCS +262144 byte splash screen + 4byte checksum + HTCE.
So remove HTCS, 4byte checksum and HTCE and you have your splash screen in NB format
It worked
@pof: Thanks for you help. Made a little perl app which grabs only the portion between HTCS and HTCE minus 4 bytes at the end with a little regex and writes that to a new file.
Then used rombaker to make a new splash.nbh file and re-extracted the files in the new RUU_signed.nbh with nbhextract which also converts the extracted .nb splash images to .bmp and the .bmp's looked just fine.
Then I loaded a different wm6 rom which has other splash screens and flashed the RUU_signed.nbh with the created splash screens to the device and had the extracted splash screens back on the device.
I attached the perl file which converts any dump which has the HTCS and HTCE strings in it to splash .nb it should run on any perl version (win32 + linux) although its only tested on linux.
was wondering if someone could tell me where to find the nk.nbf from dcd's 2.2.x roms...want to cook up some custom boot screens, but have NO idea where to find it (or get it from). thanks
You need to extract the nbh from the installer (you can use procmon from sysinternals.exe to find out where the installer extracts it).
After that you need to decompile the NBH using various tools, in which will present you with a 00_OS.nb.
After doing that, you need to extract the splash images from other roms, or create your own, then recompile the NBH.
EDIT: wow first post since 2006, you can tell ive been a leech, glad to give back to the community lol...
I was going to post the contents of the readme file that i'm trying to understand...in order for you to see what i'm being told to do, but I really can't decipher it all that well, so i'm going to attach it. This is what I'm being told to do...
Have you looked in to this: http://forum.ppcgeeks.com/showthread.php?t=16939
Yeah I read through that...
Thing is...with dcd's latest roms, the only file you get when you extract his nbh is 00_OS.nb
I have my splash.nb already made from the image i chose, but I'm not sure what to do with 00_OS.nb and splash.nb
Make an NBH from them.
You can use Dutty's NBH Tool patched for the Titan.
Since I can't find the original thread where I got it (took me forever to find in the first place) I uploaded it to fileshex.
Download here
I don't have to name my splash.nb something specific when creating the new nbh? It will just know that it's the splash?
Edit: nevermind, after opening duttys tool it's clear on how it works...thanks
Ahhh..one more question...
Is it possible to just take my splash.nb and make an nbh out of that. Then put it into the RUU and flash just the splash? Or must it be merged with the entire rom and flashed?
I have no idea.. I never did it. I want the original Verizon splash screen back instead of the static Verizon logo.
Try it and let us know if it works.
Can someone upload VZW_Startup.gif from \Windows somewhere I can download it?
I'd appreciate it very much
Confirmed.
Just took splash.nb and created an nbh just including the splash fields. I then inserted it into the RUU, flashed, and worked like a charm, no need to include any other part of the OS or anything.
Looks badass...for any help let me know...now that I know what I'm doing
P.S. It WILL hard reset the phone though upon flashing...
I put all the necessary files in a zip and I'm working on an easy step by step readme...so if anyone wants to change their bootscreen send me a pm.