Related
During my quest to get rid of german software and get normal english, i have flashed my system like a million times,
then i got an 02 boot image
then a I-mate
then t-mobile
so its possible to change this image to your willing i guess
anyonen figured out what cab file in extended rom holds this image
maybe we can raw hack it
update
if you got an imate
its
Default_Imate.CAB
there are 2 files
0Splash1.005
0Splash2.004
if you run this cab, it will only edit the boot screens, so it turns into i-mate
i dont know how to edit these 2 files yet
they arent any format i know
hexedit read doesnt discover anything
any help here?
*** update
its a raw format
trying a picture in a bit
got a strange picture now
but he its working great
no hard reset needed or anything
still need to get the format right!
then we can all change our boot screen
When it extracts, it creates a files with a .nb extension i believe. I ran the CAB just for fun and cancelled it halfway through. Upon soft reboot, the top part of the "i-mate" logo was missing (as if just cut horizontally). Re-ran the cab, this time it worked fine.
Are these similar to the screens on the original XDA?
ladies and gentleman
You can now change your bootimages to your liking
*** link has been removed, the file is on page 2 ***
This prehistoric way will change
the boot pictures of your xda2
But it works
boot sequence has 2 pictures
1 will be at startup
and the next wil follow after 2 seconds
so you can make something nice
I included 2 working images, so you can test it you like.
Its supposed to be jennifer lopez and second image is matrix revolutions
step by step
------------
1. open a drawing program and maken 2 pictures
make sure they are saved in 320 height and 240
width. save them as normal BMP or JPG as you like
name them Splash1 and Splash2
2. acdsee 6.0 is required and easiest for this
open it and convert the pictures to
RSB RED STORM FILE FORMAT
setting for me where : use a specific resolution 64 megapixel
anti aliashing off
3. when its done rename the extensions to .NB
4.copy the cab file on your phone
and copy the Splash1.nb and Splash2.nb
in your windows folder
5.now run the CAB file
done
you can delete the 2 files Splash1.nc and Splash2.nc from your
windows map
basic
but works
**sometimes the image doesnt fit properly, i think the width must be adjusted.
will look into that later
Akira
akira, you are the man!
-arebelspy
Maybe you could have the cab file (at the end of its running) delete Splash1.nc and Splash2.nc for us?
-arebelspy
You can use WinCE CAB Manager (http://www.ocpsoftware.com/) to edit the CAB file to include the nb files.
Bam, I got matrix code as my bootup image.
-arebelspy
i was very tired yesterday and it was getting late, so i finished it quickly so other could try.
that cab thing is good, ill try this weekend to make something more handy
the file displacement is maybe because the file has to be exactly as big as the original. try that this weekend to..
IMO, keep the cab how it is. If you make the .nb files inside the cab, you'd have to download a new cab file every time you wanted to change the image, etc. It'd be a lot harder for people to change the startup images, how it is now works good, if it would just delete the two files for us.
-arebelspy
is your picture on the right place or displaced?
displaced.. that's why i replaced it with matrix code, so you couldn't tell
then again maybe it was how you saved the images that made it displaced? i just hit save and did it as that filetype, didnt bother to check about the 64 megapixel anti aliasing off thing.
-arebelspy
Hello,
I have tryed the method but it didn't work for me.
I builded a rom on yorch.net with pocketpc 2003 en get de xd developer startup screen, when i do what you tell above and i restart my XDA the developerscreen is still there nothing has changed.
Can you help me with this problem i really want to change the startup picture
platte said:
Hello,
I have tryed the method but it didn't work for me.
I builded a rom on yorch.net with pocketpc 2003 en get de xd developer startup screen, when i do what you tell above and i restart my XDA the developerscreen is still there nothing has changed.
Can you help me with this problem i really want to change the startup picture
Click to expand...
Click to collapse
I think this program works only on XDA II
xda2 only
So it is not possible to change the startuppic of my xda1
correct
I have the same displacement problem. I'll look into it on the weekend
very nice app so far, thx
my images are also slightly displaced though, maybe 10 pixels to the right
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 ..
NOTE
This is my first cooking, feel free to try it out.
Eventhough I've been testing it and the results are good, conditions still apply: Use this at your own risk :!:
Explanation
This version of ROM is basically a Sin.Merged.v2.0 ROM cooked with xda2jojo/toenailed's extended_rom compression method.
And the result is a fully automatic ROM upgrade which can be done within your XDA II, no PC needed (except when flashing).
The Difference
Sin.Merged.v2.0 :
- Manual ROM merging using ActiveSync (you need to use your PC).
- Extended_rom installed manually using either Sprite BackUp or run it one by one.
Xda2.HERY.mod :
- Automatic ROM merging (no PC needed) continued with automatic extended_rom installation.
- All done automatically following the hard reset after flashing.
Ingredients
ROM = Sin.Merged.v2.0.
Cab files = collected from Sin.Merged.v2.0's collection.
Extended_rom = compressed by xda2jojo/toenailed (using CrunchIt).
Methods
There are 3 ways to take you there.
No matter which method you choose, the end result will be the same.
Method A/B/C How To:
Download the Xda2.HERY.mod.A/B/C.exe
Flash your XDA II by running the downloaded file.
You'll be asked to perform a hard reset after that.
Soon xBackup will automatically start after a while.
Tap "Restore" tab, tick "All Data", open Storage (not Storage Card) and tap Start.
Then wait until it finished, and tap "YES" when it ask for a restart.
Then it will start installing automatically.
Don't bother with the debug pop-up window.
At the end, you'll be asked to choose your provider.
At this point, you HAVE TO choose one then tap "X".
Coz if you don't, it won't restart, and it will ruin the whole process.
If you don't, even another hard reset won't help since the config files in extended_rom has been changed.
Method A/B/C CAUTION :
Whatever you do, DO NOT tap or do anything during the whole process.
You are only allowed to tap "YES" or "OK" everytime.
During the process, NEVER tap anything unless you're asked to (including tapping the Start button).
Changes are made inside the extended_rom during the process.
After everything finish, I've created a file to reverse those changes back to its previous state (before the hard reset).
Therefore when you need to do another hard reset, the files inside extended_rom will be exactly the same as before.
So it is VERY IMPORTANT for you NOT TO interrupt the process except tapping "YES" or "OK" when it asked.
I have tested this method and the result is flawless, but always bear in mind: "Do this at your own risk".
Method A:
Xda2.HERY.mod.A.exe
Method A README.txt
ADVANTAGE :
The benefit of this method is you'll have plenty space in your extended_rom.
The free space can be used to put the cab files that you always reinstall after every hard reset.
DISADVANTAGE :
The downfall of this method is you won't be able to see the compressed cab files.
They will be automatically deleted after the process.
FUTURE MODIFICATION :
Just in case in the future you want to put more cab files into the extended_rom, you have to do the following:
- Unhide & Unlock the extended_rom using the Extended ROM Tools.
- Some cab file is self delete after install, so just to be safe, don't forget to change the cab file's properties to
read-only.
- Copy the cab file(s) into the extended_rom.
- Open config2.txt.
- Add the name of you cab file(s) in the FIRST line, I repeat, ... FIRST line.
- Example, if you want to add a file named "sample.cab", then insert this in the first line, CAB: \Extended_ROM\sample.cab
- Save and close the config2.txt.
- And for security, don't forget to always keep you extended_rom Locked (and Hidden if necessary).
Just in case if you want to see the compressed cab files, just run the ExtROM.exe file in your extended_rom and choose a
folder to extract (if your extended_rom is hidden, Unhide it first).
You don't have to run Unlock the extended_rom to run the ExtROM.exe, just keep it in locked state.
Method B:
Xda2.HERY.mod.B.exe
Method B README.txt
There will be a short delay before xBackup showed up.
Just be patient because a quite large CompactFlashBackUpNew file is being extracted and copied to the Storage folder.
ADVANTAGE :
The benefit of this method is you'll have plenty space in your extended_rom.
The free space can be used to put the cab files that you always reinstall after every hard reset.
DISADVANTAGE :
The downfall of this method is you won't be able to see the compressed cab files.
Because everything has been backed up in a backup file (CompactFlashBackUpNew), which will be automatically deleted after
the process.
Eventhough there's plenty of free space to put extra cab files, with this method, you have to install the added cab files
manually from inside extended_rom.
FUTURE MODIFICATION :
Just in case in the future you want to put more cab files into the extended_rom, you have to do the following:
- Unhide & Unlock the extended_rom using the Extended ROM Tools.
- Some cab file is self delete after install, so just to be safe, don't forget to change the cab file's properties to
read-only.
- Copy the cab file(s) into the extended_rom.
- Run it.
- And for security, don't forget to always keep you extended_rom Locked (and Hidden if necessary).
Method C:
Xda2.HERY.mod.C.exe
Method C README.txt
ADVANTAGE :
The benefit of this method is you'll be abe to see all the installed cab files.
DISADVANTAGE :
The downfall of this method is you won't have much free space left in your extended_rom.
FUTURE MODIFICATION :
Just in case in the future you want to put more cab files into the extended_rom, you have to do the following:
- Unhide & Unlock the extended_rom using the Extended ROM Tools.
- Some cab file is self delete after install, so just to be safe, don't forget to change the cab file's properties to
read-only.
- Copy the cab file(s) into the extended_rom.
- Open config2.txt.
- Add the name of you cab file(s) in the line.
- Example, if you want to add a file named "sample.cab", then insert this line, CAB: \Extended_ROM\sample.cab
- Save and close the config2.txt.
- And for security, don't forget to always keep you extended_rom Locked (and Hidden if necessary).
Just in case if you want to see the compressed cab files, just run the ExtROM.exe file in your extended_rom and choose a
folder to extract (if your extended_rom is hidden, Unhide it first).
You don't have to run Unlock the extended_rom to run the ExtROM.exe, just keep it in locked state.
Millions of Thanks to :
Sin for:
- the Backup.stg file of ROM 2.02.t1WWE.
- all the cab files.
- the genius discovery of merging between ROMs.
xda2ojo & toenailed for:
- the XdA2JoJo[1].v3.0.1t.cab file.
- the CrunchIt.exe file.
- the brilliant idea of compressing extended_rom files.
In conclusion, you guys are simply THE BEST !!!
using the xbackup... :lol:
xda2jojo said:
using the xbackup... :lol:
Click to expand...
Click to collapse
Yes, Jojo, all three methods using xBackup.
But I believe you refer to method B.
For method B, the tricky part is, to make it all run in one step.
As we know, after a ROM flash, all will be back to standard.
I've already put the CompactFlashBackupNew file in the extended rom, which will be auto copied to the Storage folder, ready to be xBackup-ed.
After xBackup complete, you'll be asked to do a reset.
Then, where's the auto config part?
After the xBackup reset, you're suppose to MANUALLY go to Start, Programs, Communication, AutoConfig.
And to clear things up, you have to MANUALLY delete the CompactFlashBackupNew file in the Storage folder.
Plus for safety reason, just in case you accidentally change files in the extended rom, you have to Lock and Hide it, ... once again, ... MANUALLY.
Here's the tricky part, you don't have to do all those things manually.
Everything will be automatic following the hard reset after ROM flashing.
After the xBackup reset, you'll be brought automatically to the AutoConfig, which will bring you to another final reset.
After that, ... voila, you're done.
And the CompactFlashBackupNew file in the Storage folder will be automatically gone, plus your extended rom will also be automatically locked and hidden (you can always unlock or unhide it with the pre-installed Extended ROM Tools).
So no need for you to do step 2, 3, etc.
Only 1 step, and it'll take you to straight to the finish line.
So does the other methods, all in 1 step.
Can anybody tell me the passwords for these files? I want to use them on a german t-mobile device.
Thanks
Password?
What do you mean?
I didn't put any password.
Is it the password to open/run the file or to download the file?
The Password to change the country ID. I need a password if I want to change it in ER2003 Edit.
Or are there any other ways to do it?
Thanks Herry
For ur rom!!!
VIVA O2XDAID !!!
bravo hery go go go hihihi
Hopefully it works, Phreak.
Mengesankan herry.
Halo kepada teman saya di Bali.
Bagaimana membicarakannya benang merah ini menggunakan indo bahasa?
:wink:
Hey, I didn't know that you can speak Indonesian, Jojo.
If you find it hard to say it in indonesian, then just do it in english.
Surely most of indonesian gadgeters speaks english.
hch_111 said:
Hey, I didn't know that you can speak Indonesian, Jojo.
If you find it hard to say it in indonesian, then just do it in english.
Surely most of indonesian gadgeters speaks english.
Click to expand...
Click to collapse
hahaha...
How about this...
''If you find it hard to say in ENGLISH, then just do it in INDON.
Surely SOME(hehehe...some of my friend) of indonesian gadgeters HARDLY speaks in english''.
Yo! my friend.... :wink:
is it Indonesian EXT-Rom only?
It's nice to know our gadgeter (indonesian) can improve the extended room for XDA. i hope we can make better one in next day.
but i've some question for u herry.
1. This rom is only for indonesian user?
2. wht's content in this rom? is it same like the xda2jojo's rom?
3. Any freatures are good in urs rom?
Just inform to you, i'm also cooking my extended room for indonesian only. but i'm not a programer. so it'll take long time.. he he.. i hope we can combine with the others.
btw.. where do u life? tinggal dimana pak?
for XDA2Jojo, i think i must learn from u so much more, buddy. would u teach me about cooking? ya... maybe about some philipine's cooking? ok, thank's b4..
Salut!
Iya donk, gadgeteer Indo jgn kalah...
Tapi kayaknya cara kamu ribet deh. Pake XBackup lagi... PELAAAAN nya ga tahan. Bisa mandi dulu, makan dulu & blm selesai juga. :x
Gue sendiri pake Sin Merged tapi ext romnya gue ganti dgn file2 sendiri kecuali Sin Merged v2.0.cab. Khususnya carrier files hanya gue tinggalin yg gue pake aja. Lagi tunggu Win2K5 nih... kayaknya the great Buzz baru saja release full 128 RAM.
Anyway, keep contributing! 8) 8)
Re: is it Indonesian EXT-Rom only?
moeya said:
It's nice to know our gadgeter (indonesian) can improve the extended room for XDA. i hope we can make better one in next day.
but i've some question for u herry.
1. This rom is only for indonesian user?
2. wht's content in this rom? is it same like the xda2jojo's rom?
3. Any freatures are good in urs rom?
Just inform to you, i'm also cooking my extended room for indonesian only. but i'm not a programer. so it'll take long time.. he he.. i hope we can combine with the others.
btw.. where do u life? tinggal dimana pak?
for XDA2Jojo, i think i must learn from u so much more, buddy. would u teach me about cooking? ya... maybe about some philipine's cooking? ok, thank's b4..
Click to expand...
Click to collapse
Sorry for the late reply.
Allow me to answer the Q's:
1. Actually the only thing that make this one feels like Indonesian ROM is the AutoConfig cab files, which consist 3 Indonesian provider.
For other countries have to search or find the suitable cab file(s).
The rest (other than AutoConfig stuff) are all universal use.
2. Nope, the same thing about JoJo's version is the cooking method (using the compressed ext_rom). It's more alike to Sin.Merged.v2.0's version.
3. The good feature in this ROM is the ability to do it all automatically.
Thank you, hope it explains.
See ya again, friend.
MMS setting for mentari subscriber
can anyone with working mms setting using mentari card, plase post their setting in here.
i tried to set mine but still won't connect to the server / mms won't send.
already went to mentari shop, but still won't work. the step by step they used is for 1.60 rom, i think not for the 2003se version.
so, once again anyone with working mms setting for mentari, please help me.
tks.
Hi there, flashed the rom on my XDA II using method C, was wondering if I got it correct. Whenever I soft reseted my PDA, there will be a prompt from PHM reset for me to reset the phone shortly after load up, as you can see it will be an endless loop if I did not choose "NO" when prompt to reset the phone on startup. Will like to know if this is normal ir did I do something wrong during the process.
Thanks in advance
naoki1980 said:
Hi there, flashed the rom on my XDA II using method C, was wondering if I got it correct. Whenever I soft reseted my PDA, there will be a prompt from PHM reset for me to reset the phone shortly after load up, as you can see it will be an endless loop if I did not choose "NO" when prompt to reset the phone on startup. Will like to know if this is normal ir did I do something wrong during the process.
Thanks in advance
Click to expand...
Click to collapse
Can you tell me what files you have in \Windows\StartUp?
Hery
What is the content of the file 'CompactFlashBackUpNew'?
Is it important
Did you actually notice a difference between merged and non-merged performance (with exactly same extended-rom)?
:!: :?: :roll:
llbasha said:
Hery
What is the content of the file 'CompactFlashBackUpNew'?
Is it important
Did you actually notice a difference between merged and non-merged performance (with exactly same extended-rom)?
:!: :?: :roll:
Click to expand...
Click to collapse
Yes, it is very important.
It contains all the extended ROM that listed in the other methods.
Like I said, all three methods ended up with same results.
Nope, I didn't try to put the extended ROM in merged and non-merged.
Since this already concluded by Mr. Sin that merged one is better than non-merged one, therefore I just use the merged one instead of the non-merged one.
Thanks.
For Atom / Atom Pure / Atom Exec: Use WinImage Version 8.1 or similar program to edit IMG file. There are many programs that can do it.
Do not touch folders found in this image file. Programs that depend on these folders are: FM Radio, AutoConfig, WirelessManager, Camera, Equalizer, Album (life), ImageEditor (life)
The version of the Extended Rom is taken from the text file:
061020_AL1ARCWWE_EX0604.txt
The name is picked up versionCPAapplet.cpl (found in Settings->System Info)
So far, I did not encounter any problems changing the version numbers
The default folder name for this partition on your device is \_QHiddenPartition\ However, when we unlock this hidden partition at device runtime, we can not use the same folder name to install programs and lock it afterwards.
Normally, I used this partition to place the cabs I want to install at hard reset. This is no longer a problem with the cooked ATOM/ATOM EXEC ROMs we made because, serialzs introduced MortScript to do the automatic installation of cabs found in \_QHiddenPartition\ and \cabs\ folder found in storage card.
It is not necessary, however, to unlock the hidden partition just to edit the contents at device runtime. You can always use Total Commander to browse this partion by keying \_QHiddenPartition\ on the location bar.
For ATOM LIFE users, you can simply remove the 12-byte header of IMG file, and WinImage 8.1 can be used to edit the file. You need to restore the 12-byte header prior to flashing your device again.
tj your are very kind ^^;
Last time i ask.you say search.
i use search but still confuse cause alot of topic.
but now you posted this info.
THANKS YOU
thank you,i'm trying to cook and release WM 7.0 tonight. j/k
How to remove or add programs being install in order??? I found that del *.cab to remove the programs and copy *.cab to auto install the programs from extended rom. But i don't know the file where listed the programs is able install in the extended rom at hard reset. In the past,when i cooked BA rom, i remember that i can edit the file include the paths of the cabs I want to auto install at flash rom or hard reset.
jiggs said:
For Atom / Atom Pure / Atom Exec: Use WinImage Version 8.1 or similar program to edit IMG file. There are many programs that can do it.
Do not touch folders found in this image file. Programs that depend on these folders are: FM Radio, AutoConfig, WirelessManager, Camera, Equalizer, Album (life), ImageEditor (life)
The version of the Extended Rom is taken from the text file:
061020_AL1ARCWWE_EX0604.txt
The name is picked up versionCPAapplet.cpl (found in Settings->System Info)
So far, I did not encounter any problems changing the version numbers
The default folder name for this partition on your device is \_QHiddenPartition\ However, when we unlock this hidden partition at device runtime, we can not use the same folder name to install programs and lock it afterwards.
Normally, I used this partition to place the cabs I want to install at hard reset. This is no longer a problem with the cooked ATOM/ATOM EXEC ROMs we made because, serialzs introduced MortScript to do the automatic installation of cabs found in \_QHiddenPartition\ and \cabs\ folder found in storage card.
It is not necessary, however, to unlock the hidden partition just to edit the contents at device runtime. You can always use Total Commander to browse this partion by keying \_QHiddenPartition\ on the location bar.
For ATOM LIFE users, you can simply remove the 12-byte header of IMG file, and WinImage 8.1 can be used to edit the file. You need to restore the 12-byte header prior to flashing your device again.
Click to expand...
Click to collapse
cdmavn said:
How to remove or add programs being install in order??? I found that del *.cab to remove the programs and copy *.cab to auto install the programs from extended rom. But i don't know the file where listed the programs is able install in the extended rom at hard reset. In the past,when i cooked BA rom, i remember that i can edit the file include the paths of the cabs I want to auto install at flash rom or hard reset.
Click to expand...
Click to collapse
The script runs through all cabs present in the the two locations stated above. You don't have to edit any list like you do for AutoRun in BA. Also, AutoRun does not work with cab installation that require user interaction. Now, as for your question regarding the order they go - it's alphabetical.
Hi jiggs!!
You awesome! I have added my operator in autoconfig list, all work fine, now I have all settings for my operator!
THANKS A LOT!!
interesting in rom cooking, thats what i.m always thinking about,.
but i'm afraid to do this, i'm afraid i'll bring my atom unusable,.
thanks anyway jiggs,.
ex.image said:
Hi jiggs!!
You awesome! I have added my operator in autoconfig list, all work fine, now I have all settings for my operator!
THANKS A LOT!!
Click to expand...
Click to collapse
Pls post your settings for others, too. Thanks.
jiggs said:
For ATOM LIFE users, you can simply remove the 12-byte header of IMG file, and WinImage 8.1 can be used to edit the file. You need to restore the 12-byte header prior to flashing your device again.
Click to expand...
Click to collapse
how do you remove 12-byte header?
ichanz said:
how do you remove 12-byte header?
Click to expand...
Click to collapse
Open the file with an HEX-editor, cut the first 12 bytes and save the file. That's all.
You can use "XVI32". This Hex-editor is included in the original Scooter-ROMkitchen.
Hi all,
I use remotePROTECT as a security measure on my Atom - I find the program great.
It will be even better if I place it in extROM (hidden partition) so that it will install again upon hard reset.
I've followed the instructions that come with the software - they require me to place the program's CAB file in the extROM along with the setupE file.
I tried that - did a hard reset and nothing happened - didn't install.
I have an O2 Atom with an official ROM release installed.
Is there anything else I need to do? I note there is an Autoinst.dat file in the hidden partition, but it's encrypted or gibberish so I can't do much with it.
If I've overlooked anything can someone please suggest what I can do to make this do what I want - install itself again after hard reset.
Thanks in advance.
Avocado said:
Hi all,
I use remotePROTECT as a security measure on my Atom - I find the program great.
It will be even better if I place it in extROM (hidden partition) so that it will install again upon hard reset.
I've followed the instructions that come with the software - they require me to place the program's CAB file in the extROM along with the setupE file.
I tried that - did a hard reset and nothing happened - didn't install.
I have an O2 Atom with an official ROM release installed.
Is there anything else I need to do? I note there is an Autoinst.dat file in the hidden partition, but it's encrypted or gibberish so I can't do much with it.
If I've overlooked anything can someone please suggest what I can do to make this do what I want - install itself again after hard reset.
Thanks in advance.
Click to expand...
Click to collapse
If you have read the first post carefully, then you will understand that this won't work because the built-in AutoInstall of the official ROM restricts to signed CABs only as defined by list with no known format as of this date. That's why we have cooked ROMs to bypass this and created another AutoInstall script. There are work arounds for your purpose but definitely this solution is not for you. You have to do some research on this forum.
Anyone knows how to change or create new network settings. I found xml files in network folder and asked if there is a way to have my personal network settings like auto sms delivery or auto configure vms numbers or ...
vocian said:
Anyone knows how to change or create new network settings. I found xml files in network folder and asked if there is a way to have my personal network settings like auto sms delivery or auto configure vms numbers or ...
Click to expand...
Click to collapse
you need to secure this from your operator.
although you can edit the xml files with notepad, I don't know if the GUID found there is important. you can also generate your own GUID to have a unique value.
select the existing xml that best fit your requirements and edit it. you can't edit the cabs found in the networks because they are signed. you need to provision your own cabs. it's more like provisioning certificates using cabs.
jiggs said:
you need to secure this from your operator.
although you can edit the xml files with notepad, I don't know if the GUID found there is important. you can also generate your own GUID to have a unique value.
select the existing xml that best fit your requirements and edit it. you can't edit the cabs found in the networks because they are signed. you need to provision your own cabs. it's more like provisioning certificates using cabs.
Click to expand...
Click to collapse
thank you very much indeed. I found xml files for defualt operator and also txt file wich list this operators. Gussed that first input my operator to that list and then create new xml. but i figured if any guide for what all of this xml comands mean and the whole format.
and another question : how to edit or change cabs? I have a background of programming with c++ and visual basic.net. Is it possible for me to create my own cab without too much effort? and with which compiler ?
tnx
jiggs said:
It is not necessary, however, to unlock the hidden partition just to edit the contents at device runtime. You can always use Total Commander to browse this partion by keying \_QHiddenPartition\ on the location bar.
Click to expand...
Click to collapse
Jiggs,
I am using an atom life, I fould that I could not browse the extended rom with Total Commander. In my memory, I should be able to use TC to browse the extended rom on my ATOM EXEC. Do you know what I am doing wrong?
By the way, is it possible to unhide the extended rom?
vocian said:
thank you very much indeed. I found xml files for defualt operator and also txt file wich list this operators. Gussed that first input my operator to that list and then create new xml. but i figured if any guide for what all of this xml comands mean and the whole format.
and another question : how to edit or change cabs? I have a background of programming with c++ and visual basic.net. Is it possible for me to create my own cab without too much effort? and with which compiler ?
tnx
Click to expand...
Click to collapse
use PocketPC Installation Creator to create cabs.
hh93220 said:
Jiggs,
I am using an atom life, I fould that I could not browse the extended rom with Total Commander. In my memory, I should be able to use TC to browse the extended rom on my ATOM EXEC. Do you know what I am doing wrong?
Click to expand...
Click to collapse
You must simply type \_QHiddenPartition in Total Commander to switch to Extended ROM.
Btw: It's described in the Atom Wiki. You should read it.
By the way, is it possible to unhide the extended rom?
Click to expand...
Click to collapse
Yes:
hit me
scorpio16v said:
Open the file with an HEX-editor, cut the first 12 bytes and save the file. That's all.
You can use "XVI32". This Hex-editor is included in the original Scooter-ROMkitchen.
Click to expand...
Click to collapse
Thanks!! The problem resolve after I remove the first 12 bytes.
For AtomLife ExtRom.img.
Anyone was successful to flash editted ExtRom.img of AtomLife with DSUU? If possible, could you please show me few experience to Update ExtRom via DSUU.
Ex: Remove 12bytes header/edit(add or remove anything can do)/restore 12bytes header. Then replace new ExtRom.img in \Window\temp\ExtRom.img and delete \Window\temp\FLASH.DIO while completed extract of DSUU running. Then imitate DSUU instruction. Is it right? This way, I cuccessed to new Flash.dio for AtomLife.
Okay trying to cook my first ROM, but I have some apps that I always seem to need to install after I change my ROM. How can I add these to my ROM?
The programs are Remote Desktop (Finster's CAB file), BackGammon (exe taken from another PDA), Logmein (CAB file), Advanced Config 3.3 (and NetFrame 3.5), plus some other games I have gathered over the years.
Can anyone assist? I have looked at the OEM directories from OEM 5.5, but there are no CAB files and the other files I can't see how to create.
Anyway - any assistance for a total noob would be appreciated.
DT
From the Nike kitchen, tools>package creator. Copy your cab there, and then run package creator and select the cab. A full package will be created for you to add to your OEM folder.
THanks for that, what about the exe files that just need to be placed in a folder and a shortcut created - eg the backgammon game from the other PDA?
Also - just checking - I open the can and then extract it to create the package?
Thanks
DT
d_train said:
THanks for that, what about the exe files that just need to be placed in a folder and a shortcut created - eg the backgammon game from the other PDA?
Click to expand...
Click to collapse
Probably easier to do one manually or modify another package to suit. If you look in a package:
1) option.xml gives the tickbox for you to include or exclude in cooked ROM.
2) ****.dsm is a 'time stamp' of order of processing of the package.
3) ****.rgu are registry entries that you can change to configure the program.
4) initflash.txt gives the location for files to be copied to - directories, links, folders etc.
5) ****.provxml is an alternative to using .dsm and .rgu.
Also - just checking - I open the can and then extract it to create the package?
Click to expand...
Click to collapse
Just click on open cab, select the cab, and wait for the okay. The package is ready for use.
Thanks for the info - tried the manual way copying some of the info from other packages. I get an error - "Error building default.hv and user.hv!" when I try the first step in creating the ROM. Without the backgammon program selected this step goes fine.
Here is the info I used...
<?xml version="1.0" encoding="UTF-16" standalone="yes"?>
<Items>
<Item name="Backgammon" group="Programs" checked="true">
<Tip></Tip>
<Guid type="p">f70211a0-0b0a-11de-8c30-0800200c9a66</Guid>
</Item>
</Items>
and...
;-------------------------------------------------------------------------------------------
;Package: BackGammon
Directory("\Program Files\"):-Directory("Games")
Directory("\Program Files\Games"):-Directory("Backgammon")
Directory("\Program Files\Games\Backgammon"):-File("pGammon.exe","\Windows\pGammon.exe")
Directory("\Windows\Start Menu\Games"):-File("Backgammon.lnk","\Windows\Backgammon.lnk")
;END Package: BackGammon
;-------------------------------------------------------------------------------------------
I have two files - f70211a0-0b0a-11de-8c30-0800200c9a66.dsm and f70211a0-0b0a-11de-8c30-0800200c9a66.rgu which are empty. then I have the shortcut and exe file.
I also tried adding REGEDIT4 to the f70211a0-0b0a-11de-8c30-0800200c9a66.rgu file
Am I missing something?
Thanks
DT
Okay removed the rgu file for that app and have successfully built my first ROM - yippee!!!
The only things I noticed and am not sure if it what I have done or a bug, but the phone doesn't switch off. Hold the button and it pops up asking yes or no (as usual) click yes and the phone goes blank. but switching it on again instantly brings you back to the page you were on, it doesn't start from scratch.
Also the Manilla 2D is great, but the email widget doesn't recognise my Exchange email - it wants to create an imap or pop3 account, but says "No Accounts" in the display (even though it shows the unread amount on the icon) - did I do something wrong?
Thanks
D
Sorry double post
Thanks
D
d_train said:
Okay removed the rgu file for that app and have successfully built my first ROM - yippee!!!
Click to expand...
Click to collapse
Congratulations.
The only things I noticed and am not sure if it what I have done or a bug, but the phone doesn't switch off. Hold the button and it pops up asking yes or no (as usual) click yes and the phone goes blank. but switching it on again instantly brings you back to the page you were on, it doesn't start from scratch.
Click to expand...
Click to collapse
Sounds like bug. Which XIP/SYS/OEM combination did you use? Left any packages out? Have a look at others who have built a similar ROM using the combination and check the thread out for bug reports.
thanks will do
The XIP/SYS/ROM I used is - not sure the XIP but I downloaded SYS and ROM version 21109 and used OEM 5.5
How can I extract OEM and SYS from an nbh file?
I have an original ROM installation file that I want to extract some apps for my ROM.
Thanks for your help.
D
I use an old Kaiser kitchen (the first we had, by NetrunnerAT if I remember...) which had tools that can extract automatically NBHs.
But with the newest cooked ROMs, you won't have any "real" OEM or SYS packages since they are protected deleting some files you need to make different folders. You can get the XIP and maybe some individual files but nothing really interesting...