SERV v1.1 and EzWAP 2.5 - MDA, XDA, 1010 Software Upgrading

how do i remove programs which i dont want on my device, but came with jeff's version?

You don't need to: they're not in RAM, so they do not affect the amount of free RAM. In fact, when you use the Special Edition ROM that comes with all this extra software, you end up using something like 3MB less RAM than when you use the O2 ROM, mainly because we left out the 'Action Engine' framework, and because EzWAP is in ROM. (They are both copied to RAM on the O2 ROMs, duh!)
It's slightly more technically challenging, but you could use the mkrom kit to make your own ROM, in which case you could use the space taken up by programs you do not need for programs you'd prefer to have instead.

so how do i replace ezwap 2 with ezwap 2.5? because i need mms as well.

Easy solution: just install EzWAP 2.5, should install in it's own directory and not be bothered by the installed 2.1. (Although we never tried).
Hard solution: get access to a unix, download 'mkrom', insert EzWAP 2.5 in the files2 directory, create the appropriate registry entries in default.reg in the cfg directory, run 'mkrom' and flash the resulting file into your device.

i guess i'll stay with the easy solution thanks

Related

Own ROM with integrated TomTom2

Maybe this is a question especially to the developers, but I'm sure there are some other guys, that can advise me or give some hints.
I'm going to create my own rom with the mkrom-tool and I want to add some special programs. I also want to integrate my tomtom software to the rom. Therefore Ii don't have to reactivate every time, when Ii install the xda.
Now my question: Is this possible? Is there enough space to add this program?
What will i have to do?
Thanks...
Stefan
1) Create a snapshot file using 'ssnap' in your SE ROM
2) Install TomTom to the \Windows directory by moving the .cab to the device and double-clicking it. The CabInst program in the SE ROM will offer the option of installing to an alternative location.
3) Set everything up the way you want it. (i.e.: Twiddle all the settings, and install POIwarner and recent camera database also.)
4) create another snapshot.
5) Copy the two snapshot files to the PC, and compare them using a compare tool. (UltraEdit comes with one).
6) Filter the differences for things you do not need, such as 'last used' items in the file explorer and such...
7) Set up 'mkrom', adding the 3.17.03 ROM image, and test that it works by creating a ROM using the config that's in there.
8) Select what you want to lose, because 1.2 is full. Add the files the snapshot difference tells you are new into the 'files1' or 'files2' subdir, making sure the total file sizes for each doesn't grow.
9) Add the changed and new registery keys to default.reg
10) Run 'mkrom'
11) Presto.
I never found TomTom in ROM to be really useful, because it's big meaning you lose almost everything else, if it even fits. And for it to be useful, you always need the maps on SD-card anyway. Why not create an SD-card backup of the entire setup of your machine the way you like it on an old 16 or 32 MB SD-card? Then you can just put that onto your SE ROM device right after cold-boot, and you're in business.

Remove files from ROM

How can I remove from the original ROM some files like T-Mobile, AIM ... etc. ?
I cooked up a 4.00.10 T-Mobile with GPRS monitor and batterypack but i want some more addons.
Can someone tell me what steps are required to remove from the ROM some files ?
Thanks,
Decebal
ROM = Read Only Memory.
But, i've we're able to add Programs to the ROM in the ROMkitchen, i think we're also able to remove programs.
Regards
Stefan
cruisin-thru said:
ROM = Read Only Memory.
Click to expand...
Click to collapse
obviously i do not deserve that
i was talking about the ROM image and since i've already succeded in putting into the ROM two apps i want to try something else.
so if anyone know how to remove at least T-mobile and AIM files from the image i'll be happy.
thanks,
Decebal
I believe they are in an area not able to be modified.
I was just quoting from that site, it does state that it cannot be erased, modified etc, no offence meant here. :roll:
The mkrom tools will allow you to 'unpack' a rom, i.e. extract all the files that are in it.
A rom, to the best of my understanding, has a 'native' or stock part to it, and then a series of XIP chains -- programs that are added into the free spaces of the rom.
I dont know what happens if you try to remove files from a rom that are part of the standard build...
Maybe the TMobile stuff is in a 'removeable' section of the ROM... there is also the 'operator' section... I am assuming that is a location that will give the 'operator' or creator of the rom space to put specialized programs, such as TMobiles phone apps, etc.
So, it seems that your best bet is to get the mkrom tools and read about how to extract/remove files/rebuild a rom.
Hey, it may even work!
J
You can rebuild a rom image from extracted files and leave some files out but Mkrom does not use compression and therefore the rom you end up with will probably be bigger than the rom you started with.
Richard
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.
XDA developer Itsme said:
If I am correct, an eeprom is something else than a flash-rom.
so the article at least states it incorrectly.
if it is flash, you should be able to modify it.
Click to expand...
Click to collapse
Now, I do think that the real question is "How do we unlock the 'ROM' so that it can be modified being that it is an eeprom?"
Misterdollymaker
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
this is quite interesting...can you elaborate further?? I wish to learn more...
cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
Yes, please! I wish to learn more too! I am looking to remove the standard sounds and replace them with my own (using same names) as well as the boot image and desktop.
yea, no kiddin, i'd like to know how too!
im sure its not impossible, 'they' did it the first time arround.
why not hacking it? and since its all at no charge (no profit) are we realy breaking any patents?
I wanted to know if there is an easy :wink: way around, to put our own programs in the rom. xda-developers certainly can't put ezwap2.5, and the total commander appears to be older version, while new version is much better. There are some more freeware application I'd love to put in there
xda-developers already posted some tools to do job, such as MKROM ...
cgigate said:
you need backup the ROM to *.nb1 or *.nbf file, than using tools to add/delete file to *.nb1 , write the new file back to XDA ROM. it is fun to add/delete file to your personized ROM!
Click to expand...
Click to collapse
I'm interested too
How can i add/delete file from nb1 file?
Thanks
Fabio
I've used mkrom suite to do this (even for Smartphone2002). This are great tools.
Unfortunately it's not as easy as you might think. It's nearly impossible to build a ZERO-KNOWLEDGE ROM file explorer which can add or delete files "on the fly".
You will still have to look for valid gap's in the original rom where you can add a new XIP block.
All .exe and .dll files are "fixed up" that means they MUST run at THE fixed ROM position where they have been initially placed (execute in place). If you dump an exe or dll file you can't use it for other than disassembly to see how things work.
Removing files is a very hard task (they are splitted over the whole rom). And the resulting gap's are mostly not more than 10-16 kB. All you can do is to "hide" files (simply patch the directory entry).
So you see compression is not the real problem (see programers corner for a .bib file which can be used with romimage.exe - a Microsoft Tool to build XIP blocks, this tool supports compression)
John Smith
only the kernel actually runs in the virtual memory area mapped to rom,
all the other XIP stuff runs from a virtual memory area mapped somewhere
in the top of each processes memory space.
( look at the 'real=' values in the output of dumprom )
so for all the other modules it should be possible to move them around
in rom a bit, I think you only need to keep the pagealignment the same.
Hi,
The virtual memory address is also fixed in the module. (That's why I've to rebuild all the stuff I want to copy from other roms).
Since all relocation info is gone the module can't run from another memory position. So the only thing you can do is to move it in it's own XIP section...
John

ROM editing questions; delete, versions, files dir

1 Is it possible to delete files (.dll is what I'm after) out of wallaby ROM? I thought I read that it was, but now I can't find that info, mkrom, splitrom, etc info that I see all tells me that you can only add or change..
2 BTW, what's with all the versions of romtools & tools with the same name (but different versions?) in the demokitchen? I assume its good to have the latest and greatest, but I am beginning to rethink my assumption there. When I say versions, I am looking at the dates of said files in either /~itsme/cvs-xdadevtools/romtools or /Wallaby/Tools/CustomROMToolset or /Wallaby/Tools/MKromxxx.zip or http://wiki.xda-developers.com/uploads/mkrom.zip as well as a bunch of different versions of dumprom.exe (win32).
Any particular set that is most functional? I've noticed that a .pl file or two wanted to run dumprom (ELF version) which !work on cygwin, and another wanted .. unicode whatever.. yeah.. In one place or another I had to edit the .pl file & run it under cmd prompt instead of cygwin. Worked swell.
3 So in a set (I think it's the wiki's customrom instructions) of cook-you-own-rom instructions, it says to add neccesary files to files directory. files directory you just dumpromed to. Ok. My neccesary files are MMS files & whatnot. Later in the directions it tells you to run some xipchains stuff, with files1 and files2 directories as arguments. Well, there's nothing in there, since I put them all in files. The ROM builds, but I end up with basically the same rom I started with. if I dumprom it back out, I can't see any of the file additions I did in the new rom.
So I'm gonna assume again, that I should stick my files in files2 for the most part, so the scripts that build xipchains & calc free space etc can do their job & one of those scripts will get my files where I want them. (in the rom!)
TIA
BTW, if anyone is interested in the Arcsoft MMS Composer software not working in LumpiStephans kitchen, you need to grab & install Camera_WWE.sa.cab from someplace, which will install the requisite .dlls to make the MMS software work. Yeah, it's big, and there is no camera on the wallaby, I know. But the EzOS wap browsers MMS software really sucks (for me), and looses parts of the messages from certain people. I dunno if it's their email client, or what.. don't care.
if anyone is interested, I can tell you what DLLs it needs, I sat there for a while checking out the dependencies, and that way you don't have to install as much extra crap, but I don't have it handy right now. lemme know.
squib308 said:
1 Is it possible to delete files (.dll is what I'm after) out of wallaby ROM? I thought I read that it was, but now I can't find that info, mkrom, splitrom, etc info that I see all tells me that you can only add or change..
Click to expand...
Click to collapse
No, it is not possible to delete files out of a ROM.....
squib308 said:
3 So in a set (I think it's the wiki's customrom instructions) of cook-you-own-rom instructions, it says to add neccesary files to files directory. files directory you just dumpromed to. Ok. My neccesary files are MMS files & whatnot. Later in the directions it tells you to run some xipchains stuff, with files1 and files2 directories as arguments. Well, there's nothing in there, since I put them all in files. The ROM builds, but I end up with basically the same rom I started with. if I dumprom it back out, I can't see any of the file additions I did in the new rom.
Click to expand...
Click to collapse
The 14. command (Run "perl makefiles.pl ./files ./files1 0x$size1 ./files2 0x$size2" ) should split the files with best fittings to the corresponding directories....
So perl makefiles.pl ./files ./files1 0x00050000 ./files2 0x00380000
would copy up to 320 KB to files1 and up to 3584 KB to files2......
squib308 said:
BTW, if anyone is interested in the Arcsoft MMS Composer software not working in LumpiStephans kitchen, you need to grab & install Camera_WWE.sa.cab from someplace, which will install the requisite .dlls to make the MMS software work. Yeah, it's big, and there is no camera on the wallaby, I know. But the EzOS wap browsers MMS software really sucks (for me), and looses parts of the messages from certain people. I dunno if it's their email client, or what.. don't care.
if anyone is interested, I can tell you what DLLs it needs, I sat there for a while checking out the dependencies, and that way you don't have to install as much extra crap, but I don't have it handy right now. lemme know.
Click to expand...
Click to collapse
You can tell it me, and send me the dll, than i will include it to the Arcsoft MMS-Composer....
Stefan

write enable/disable extended rom

This simple little proggie simply sets write enable/disable of the extended rom and can also hide/unhide it thus allowing for customising config.txt for example.
The alternative: create an ms.nbf file with WM2003 rom editor then dump the whole thing with HimaUpgradeUt.exe, a method that requires time, a pc, and patience (yawn).
Works on my standard WM2003 Himalaya (SPV M1000) but probably works on anything with an extended rom (try at your own risk and report back).
NOTE: shortcuts are based upon files being located in the root of storage, so unrar to storage folder or amend them as necessary.

My very first fully-working cooked ROM for Sprint Mogul!

This is only OS + ExtROM, does not include radio nor splashes nor SPL.
This is basically the same OS+ExtROM as found on Sprint's latest official ROM 3.56, MINUS all that Sprint bloatware (OnDemand, AudibleAir, Sprint Music, etc.) occupying both OS and ExtROM space. I also removed Sprint Navigation and Sprint TV from the ROM and ExtROM (respectively) because I want more control on how Sprint programs are installed (into the device vs into SD card); I have the separate CAB installers for Sprint Navigation (TeleNav) and Sprint TV so I can install them the way I want. I also removed the ringtones from the ROM because I don't like Windows Mobile's approach to copying ringtones from ROM (\Windows) to internal memory (\Windows\Rings) which effectively results in unnecessary file duplication within device memory, but I have stored the removed ringtones into an SD card so I can later add them either to \Windows\Rings (with no wasted copies in ROM) or to \Storage Card\Windows\Rings.
The amount of memory I gained this way was used to (1) update the core fonts (Courier New, Tahoma) to the latest versions found on Windows Vista (the versions found on the original ROM date way back to 1999, even in WM6.1! plus WM only includes regular-face Courier New, I had to add bold/italic/bold-italic versions), (2) add smartphone fonts Nina and Segoe Condensed, (3) add the Windows Vista version of Japanese font TTC MS Gothic/MS PGothic/MS UI Gothic (the AC3 compressed version is still outdated, version goes back to 1999 ), (4) replace the USA wince.nls with the Japanese wince.nls (which includes all charsets found on USA wince.nls + adds Shift-JIS, JIS, and EUC-JP), (5) add the WM6 Japanese IME files, (6) update the SymbolPad's config file to allow inputting almost all the Pan-Euro characters found in Vista's Tahoma and all math symbols included in MS Gothic, (7) add PQzII with some customized bitmaps so you can map CTRL, ALT, and IME to any buttons you want, (8) add PHM RegEdit, Notepad and a few other PPC PowerToys (I also added MADE because it is more powerful than Notepad), (9) add KT_Capt (print screen!), and (10) add FontOnStorage (yes, a very old program that dates back to WinCE 3.0, but still works on WM6.1 as long as the fonts in your SD card don't conflict with those already in internal memory). I preserved Adobe Reader LE, the Camera app, and IA Zip.
I modified the registry entries to (1) enable ClearType and menu animations (but disabled HTC's EnlargeMenu because it doesn't play nice with menu animation), (2) set internet cache/cookies/history to load onto SD card, (3) display both date and time (and AM/PM) in title bar, (4) enable font linking so Tahoma can work together with MS UI Gothic to display full Latin/Greek/Cyrillic/Japanese, (5) enable and configure the Japanese IMEs, and (6) set the new black Vista-like HTC theme as the default rather than WM6.1's solid-green default theme or Sprint's annoyingly-bright orange theme (although both themes are still included if you want to use them).
I used NBHExtract on the original stock ROM to extract the NB files, then NBSplit/ImgfsFromNB/ImgfsToDump to dump the OS, then PKGTool to convert dump to packages, then the usual ROM-kitchen procedures (remove unwanted files, add wanted files/packages with some help from CAB Extractor and InitFlashFiles Generator, modify RGU entries, regenerate DSM files with BuildDSM, modify packages.sof with XVI32, and dump XIP with RomMaster), then BuildOS to "bring packages to a boil" into new dump, then ImgfsFromDump/ImgfsToNB/NBMerge to "simmer" new OS.nb, then HTC Extended ROM Editor to remove the Sprint bloatware from ExtROM.nb, then finally NBHGen to "bake" both OS.nb and ExtROM.nb into the new ROM.
As I said above, the radio and splash image NBs are not included in this 82.2-MB ROM; adding the radio and splashes, the ROM grows to 94.1 MB, which is still 2.5 MB smaller than the stock ROM (even after adding that big, uncompressed Japanese font MS Gothic which is about 8 MB, but that's because the font itself is smaller than the whole combination of OnDemand/AudibleAir/SprintMusic/TeleNav/ringtones).
I thank pof/TheBlasphemer, mamaich/Tadzio, bepe, AnDim, and bot for all the executables they made that made my ROM cooking possible.
For those Sprint Mogul owners who don't want outdated fonts, annoying bloatware, or duplicated-in-device ringtones, my ROM can be downloaded via RapidShare:
http://rapidshare.com/files/144942116/Sprint_Mogul_3.56_OS_ExtROM_only_by_Unicode787Plus.exe.html
congrats! I just cooked my first couple roms a few nights ago, and one for my girlfriends titan too. its fun and addictive!
Sprint Navigation (TeleNav) and Sprint TV installer CABs
For those who download and flash my Sprint Mogul ROM and still want TeleNav and Sprint TV in their Moguls, they're attached to this message. Just copy them to an SD card and install them, easy! (You can install them either into internal memory or into SD, makes no difference!)
Will later post the ringtones I removed from my ROM.
Sprint Mogul ringtones
Ringtones removed from my ROM are attached to this message. For some reason I had to split them into two different ZIP files because xda-developers constantly refused my single 2.18-MB ZIP (even after using Legacy ZIP 2.0 compression method)
MMS
There is no way to add MMS (PIC/VIDEO)? I'm not using the 8525, i have a new MOGUL (SPRINT)
Sorry, I don't use MMS at all (and VERY VERY RARELY use SMS), so I don't know how to add MMS support to Mogul. For that you'll have to ask either mamaich or bepe in either this forum or ppcgeeks.
If I flash your cooked rom.. and I dont like it ... can I flash back the original rom.
mrfordwrench
What is up with the battery icon on the upper right. It looks like it is broken. Is it supposed to be that way. Otherwise everything works great.
What exactly is the PQzII for?
Mrfordwrench
mrfordwrench said:
If I flash your cooked rom.. and I dont like it ... can I flash back the original rom.
mrfordwrench
Click to expand...
Click to collapse
Yes you can flash back the original ROM - by redownloading it from the HTC website. Same procedure if you try any other custom ROM - like mamaich's or NoChem's kitchens...
Battery icon
mrfordwrench said:
What is up with the battery icon on the upper right. It looks like it is broken. Is it supposed to be that way. Otherwise everything works great.
What exactly is the PQzII for?
Mrfordwrench
Click to expand...
Click to collapse
Read my private message - that explains the purpose of PQzII.
As for the battery icon, I don't know. If you disable date/clock display on the title bar (either by doing so from Settings or by messing up with the Registry), then you'll see a useless battery icon instead of the clock. HTC's own custom battery indicator (shows only on Today screen) is a bit more accurate, but not as accurate as Palm Treo's own custom title-bar battery icon. If I could somehow copy Palm's battery-icon code (cannot do so directly from the phone - it seems to be copy-protected, and I don't have access to a Treo WinMo kitchen) and transplant it into my next Mogul ROM, then I would be happy.
Hi Dear,
I was looking for the same thing you done. I just wanted to remove some of the programs (like office mobile, pdf, audible air, sprint navigation etc) and not to added anything else to that original rom. The process you described over here is quite short and not elaborative. I tried and reached upto the step of generating "imgfs.bin" but thereafter i was hanged and i could not do any more i.e. dumping, packaging and the reverse process. Can you do me a favour and give some detailed steps or if possible can you give me the link providing details on this as well as all the required softwares (I done all these steps on command propmpt, is there any better way like grapical interfece)
Very eagrly waiting for your reply.
Regards
Tarun Kabra
Cooking ROM
tarun_kabra said:
Hi Dear,
I was looking for the same thing you done. I just wanted to remove some of the programs (like office mobile, pdf, audible air, sprint navigation etc) and not to added anything else to that original rom. The process you described over here is quite short and not elaborative. I tried and reached upto the step of generating "imgfs.bin" but thereafter i was hanged and i could not do any more i.e. dumping, packaging and the reverse process. Can you do me a favour and give some detailed steps or if possible can you give me the link providing details on this as well as all the required softwares (I done all these steps on command propmpt, is there any better way like grapical interfece)
Very eagrly waiting for your reply.
Regards
Tarun Kabra
Click to expand...
Click to collapse
Once you have generated imgfs.bin, you must dump it with a tool named ImgfsToDump.exe. It will create a folder containing the whole dumped image. Then you must use another tool, PKGTool.exe, to unpackage the dump folder into its constituent package subfolders (called packages). Now it's just a matter of removing unneeded files (be careful here, you don't want to remove files that are needed by WinMo itself) and updating outdated fonts (Courier New and Tahoma) with newer versions (you will first need to find on which pacakges they are located, then copy the new versions onto those same package folders) and, optionally, adding new fonts, input methods, or other programs onto the Custom subfolder. You will also need to edit some RGU registry entries (each package may have one) in order to activate some features or input methods. Then you will need to run another tool, BuildDSM.exe, to reprocess the edited packages. Then it's time to build a new dump from the new and edited packages: you will need to download BuildOS for this. BuildOS has a tool called BuildOS.exe, but running such a tool is tricky since you can't just double-click on it (it will crash), you must run it from some batch file located just outside the folder containing the tool; BuildOS.exe will convert the packages back into a new dump. Then it's just the matter of reconverting the dump into a new Imgfs.bin (with ImgfsFromDump.exe), inserting Imgfs.bin into a new NB file (the ROM itself) with ImgfsToNb.exe, then repackaging the NB file into the final NBH ROM with NBMerge.exe.
This is roughly all I can remember. You can optionally seek help from other fellow users, since I learned my technique from one or several of them: mamaich, no2chem, maybe Asukal...

Categories

Resources