Guys, Have been searching the site for a couple of weeks now and cant find a solution to my problem.
I work for a company that deals with alot of XDA2 units, so far I have managed to develop a custom extended rom that works fine, but have not been able to find a way to remove links from the start menu and the program menu. seen several threat on the site but no solution. The links have to be removed if a hard reset occurs. At present It has to be done by cloning an image onto the unit (1600 in total)
Any help would be appreciated.
popeye
I would love a program which based on a txt file would "delete","rename"... files and/or registry.
Something that could be executed from config.txt
there was a thread about a .bat interpreter but i don't think they got it working.
M4io said:
I would love a program which based on a txt file would "delete","rename"... files and/or registry.
Something that could be executed from config.txt
there was a thread about a .bat interpreter but i don't think they got it working.
Click to expand...
Click to collapse
I'm using Restorator utility (search through the forum) to do the aforementioned things and much more. Works flawlessly with new Second Edition rom
thx, I completely forgot about that utility. I will defenitely give it a try
http://forum.xda-developers.com/viewtopic.php?t=9333&highlight=restorator
I finally found a method for backing up and modifying the Extended ROM on an XDA2i device.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=373&PN=1
Unfortunately, although this method is able to do most of what I want, some of the cab files do not self-extract successfully during the reset process.
Graham. -- Issue resolved. No spaces allowed in Cab file name --
Before you ask, yes the cab files do self-extract successfully if tried manually (i.e. outside of the reset process).
If anyone has any ideas why some cab files work and others do not, please let me know.
I played with the information in the article yesterday.. Some information in the article is incorrect. They state the ext. rom is 24 MB but when following the steps on the website this is incorrect !
Sure, extra drive reports a 24 MB drive but the what's backuped to the SD card doesn't include the whole 24 MB the ext. rom supposedly has !
What I'm typing below is more guess work than knowledge.
"d2s 80000000 3BF0000" probably means "dump to SD card" for a total length of 80000000 hex starting at 3BF0000 hex.
80000000 hex is 2147483648 in decimal. These aren't the amount in bytes that are copied.. I to honest it I have no real idea in what it are but when dividing it by 1024^2/100 you get 20,48. The / 100 is something I made up since that gives me about the amount in MBs I can put in the ext. ROM without having corrupted files. I don't want to experiment with larger values since I haven't studied the tools that are used in the article enough yet.
In short, be sure not to put more than say 20 MB in the ext. ROM and most likely your problems are solved. I personally put an executable sprite backup file in the ext ROM, packaged it in a way it will be copied to storage and run from there. It's the most effective way I could think of to fill an extended ROM. Simply with a fully installed but clean backup of the pocket pc.
Anyhow, that's it for now.
I considered it being a problem with size and reduced the amount of data in the Extended ROM by a huge amount (deleted several of the cab files that I did not need).
This reduced it down to around 13Mb for what it's worth.
All of the files installed to the ROM ok, but when the process which reads the Config.txt file reached the parts regarding two of the cabs I wanted to install, the files failed to self-extract without giving any feedback.
Several other cab files I wanted to install worked fine.
What all this means is that the problem (probably) lies somewhere other than the size of the Extended ROM.
Thanks for the post sparcle and if you find out anything more please let me know.
If anyone else can help here, please feel free to contribute.
Graham.
As above guide:
CE Rom size is 2700000 (hex)
Total backup size is 3BF0000 (hex)
So extended rom size is 3BF0000-2700000 = 14F0000 (hex) or 21,954,560 (dec)
So extended rom size shall not be over than 21,954,560 in total space.
-----------------------
But itsme's document
http://wiki.xda-developers.com/index.php?pagename=AlpineRomStructure
82700000-83f00000 extended rom
So backup range shall be 3F00000. (size = 66060288 (dec) which you can not use 64mb card, you have to use 128mb card to backup)
So sorry, I'll ask my friend ruchonburi to recheck again.
Just a quick note on the sizes you gave above:
83,f00,000 - 82,700,000 = 1,800,000 (hex)
= 25,165,824 (dec) (24Mb) for the extended rom.
83,f00,000 - 80,000,000
= 3,f00,000 (hex) = 63Mb for the whole rom
The document given at the site uses:
80,000,000 to 83,bf0,000 which may miss some of the extended ROM, which may explain my problem.
I will try using the numbers from wiki and see if it works.
Cheers,
Graham.
I tried using d2s 80000000 3f00000 to create the SD Card backup initially and I still had the same problem with some CAB files extracting successfully and some not.
Graham.
Looks like the issue may lie with spaces in the CAB filenames.
If it is I will kick myself for not realising it sooner and then post here to let you know.
Graham.
Ouch, ouch, ouch....
I've finished kicking myself.
The problem was indeed the space in the cab filename.
On the plus side it means that the process works fine.
Graham.
i just want to ask......by cooking Ext Rom....how much free space that can be use after that???? does it effect any upgrade in the future????
The Extended ROM is an area that you cannot normally write to and is not considered part of the memory (as far as I am aware) under Settings/Memory.
By cooking the ROM you can alter what applications get installed when the device is hard reset. The installed applications will take up their normal memory allocation so in that respect it will reduce the amount of memory available to further applications.
It is possible to increase the amount of memory available by cooking the ROM as there may be elements of the Extended ROM that came with the device that you do not actually want installed. This is done either by removing the relevant cab file completely or by removing the relevant entry from the Config.txt file (both should be done, but one or the other will have the same effect).
Hope this helps,
Graham.
gbird, thanks very much for that information. im sorry because asking question just about benefit, not about how and why. thanks again!
Hi fellow alpine owners
I'm keen to follow your tips and do some work in the kitchen.
I have downloaded all the relevant articles from the link provided so thankyou for that.
However i'm reluctant to take the first step with the thought of a unrecoverable disaster on my hands. MY NEW XDA2i!! So before i get started i thought i would consult the experts for any tips and traps for young players.
I've bought myself a large enough quality SD card to dump to.
I guess the aim of the exercise is to a remove unwanted programs and install some of the cool features of Special Edition ROM 1.2 including that really excellent anti theft tool.
Any assistance would be greatly appreciated, with what to remove/ install and how thanks in advance.
Miket
ROM version 1.11.00
ROM date 01/27/05
Radio version 1.03.00
Protocol Version 1337.42
ExtROM version 1.11.162 WWE
First tip, use the process to back up the ROM of the device and keep it very safe.
Since all you will be playing with is the Extended ROM (and not messing with the OS Rom or Radio Rom) the good news is that if you removed all of the files from the Extended Rom you would still be able to boot the device. This gives you an opportunity to remove files to see what they install. If it goes really wrong, you can restore the Extended Rom from the SD card backup.
The XDA2i device does have a lot of room on it for additional items so you can add in extra Cab files or Exe files if you wish. You need to modify the Config.txt file to make the Extended Rom run these extras.
As for which files do what, there is a lot of info available around this site and others and I am afraid I do not have time to go into it at the moment.
I will see if I get some time over the next few days, but work is a little hectic at the moment.
Hope you have fun,
Graham.
Thanks for the speedy reply Graham
Will endevour to make backup this evening and start chopping up extended ROM.
Any thoughts on the instructions provided by this web site.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=373&PN=1
Obviously a highly regarded PDA hacker.
I will be working through these. It's a bumber that XDA2i is so arkward.
Thanks for now
Miket
The page is pretty good (that's why I pointed at it)
RomUpdate
The only bit that is a bit short on description is the stuff regarding using the romupdate tool at the top.
If you need a more complete description of this tool then I would take a look at:
http://en.pdamobiz.com/en/forum/PDAforum_posts.asp?TID=62&PN=1&TPN=2
Be aware that the addresses for the d2s command are different for the XDA2 and XDA2i
Rom Structure
The memory address information for the Alpine (XDA2i) is available at this site:
http://wiki.xda-developers.com/index.php?pagename=AlpineRomStructure
RomUpdate Commands
There is also a page describing some of the commands available in the romupdate tool:
http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderCommands
XDA2 Cab Files
This site has a description of some of the XDA2 cab files which may interest you (though the XDA2i uses different cab files, some of which have similar names):
http://forum.xda-developers.com/viewtopic.php?t=6470
Soft Reset in the Config.txt File
The last bit I'm going to mention here is that the last item in the Config.txt file soft resets the device. If you remove this item for some reason then adding the line "RST: Reset" on the end of the Config.txt file will soft reset the device automatically for you.
Hope these are of use to you, I know they were all of use to me,
Graham.
Absolutely excellent thanks Graham
Have got as far as using the split tool.
Xp is throwing a 16bit error my way, so i will have to resolve that before i can go any further.
Are you suggesting that when i re-build extended ROM to include "RST:Reset" on the last line in config.txt?
Anyway it's time for bed.
Thanks for the great links, will read through these tomorrow.
Miket
With regards to the RST: Reset command, it is sometimes useful to soft reset the device at the end of the configuration.
This is because some of the Cab files will probably modify the registry and most of these changes will not be picked up until the device is soft reset (the device is still usable, just not using the changes).
Most of the builds that you may come across already do this as a last step in one of their Executables so they do not always include the reset line in the config file. Adding this line to the end will ensure that a soft reset always happens so that registry changes will be used.
Be warned, soft resetting the device will halt the configuration build at that point, so anything after the reset command will never happen.
I hope this makes some sense
Graham.
Hi again Graham
Finally sorted 16 bit issues with the PC. Have loaded SPLIT ROM and created the 3 components. Particularly ext.img
I have also created the virtual drive "X" with "ext.img"
File\properties tells me this is a 24MB file. All good until i wish to open. PC asks if i wish to format disk, i'm not able to read contents any ideas.
TA
Mike
I thought i would try downloading the cooked rom off en.pdamobiz.com as a test. The extended rom opened up perfectly in virtual drive creator. Mine however is an exact match size wise but wont open.
HMMM
I guess the next step is work out what i need and dont need in extended ROM. Assuming i can get past this stage.
Any guidance here would be appreciated.
Miket
Hello guys!
I'd like to modify my german extROM too but I have a little problem: when I'm starting the ntrw.exe (it lay in the basement of my HDD, in C:\) it closes itself!
So I mean, I can't use the ntrw.exe from the PDA-Miz guide to write the ROM-image to my HDD!
What can I do?
Thanks in advance
animelover from germany
At me sometimes the device starts to stammer at playing music and in a root directory there are files dbgtostorage*.* which constantly grow.
At me one such problem?
In an Internet has found only it:
It is necessary to create directories radically:
DbgToStorageLog0.txt
DbgToStorageLog1.txt
DbgToStorageLog2.txt
DbgToStorageLog3.txt
DbgToStorageLog4.txt
And that for debugging and what for she in a working device with an official insertion I and have not understood it.
Tried in the register of a branch to correct or demolish dll a debugger, my animal there and then was ill, began to brake terribly at each operation. I.e. it not an output.
And has created directories, files сertainly have ceased to be created, but also the device has come to life, even began subjectively faster, and that the most important has ceased to stammer.
In general it certainly not the order with this debugger what feature of it activated also the most important who?
Which ROM version do you have? These files usually mean a debug (test) version of ROM.
ROM 1.8.411.3 Rus official.
It appears that the xpanel logger was turned on somehow.
Try doing a hard-reset or find an R2 (5.4.xxxx) ROM for your Herald - it is out already.
It is a hardware mistake!
Did all that is possible and 5.4 too has not helped. Has exchanged the device in shop, in new all is normal!
Hardware itself does not create files, this is an OS feature.
It disagree. I put different ROM, have not helped.
I think memory beaten, therefore and works a debugger.
Rather, radio works in some kind of engineering mode, and system just logs the info. There's a similar problem with P3300. I suppose this has something to do with production quality.
Did both (vvv121,ASerg) of you have solution for this kind of problem i have same problem in my xda orbit now and i haven't found any solution even googled it
please tell me what to do?
In Registry explorer (SKTools) search for key: DebugLog (HKLM\Drivers\BuiltIn\DebugLog\), rename Htc_Lib.dll (delete simbol "_"), change index from 2 to 0. Save and exit SKTools. Soft Reset.
After soft reset - delete all DbgToStorageLog.txt.
In some cooked roms this key is missing. Sorry for English poorly.
I've got a slight problem with this device, probably also with all other WM5.0 devices.
There's this application which I have developed to operate as a shell around Windows Mobile, so users have limited functionality. This is to relieve the people at the helpdesk, since users can't mess up settings and install virusses anymore (at least not that easy).
The way I installed the software on Windows Mobile 2003 (SE) was to install my Autorun.exe in the \Storage\2577\ directory and my cab-files, which needed to be installed, in the \Storage\Main\ directory.
I also used the folders \Storage\Downloads\ and \Storage\Installed\, but to keep things simple I won't mention further anymore.
This solution worked like a charm. After every hard-reset/cold-boot my application was installed again and users could happily operate their devices once more.
Now, as the WM2K3 devices aren't available anymore, I need to port the application to WM5.0. After some minor modifications the software now finally works on WM5.0, except for the installation.
It appears that there isn't an Internal Storage folder anymore. This is probably because of the fact that WM5.0 has the so called 'persistant memory'.
The problem is, the memory is completely erased when doing a hard-reset/cold-boot. I do this by pressing the 3 buttons on the side and pressing the [reset]-button also. After a while the device will perform the hard reset (as usually).
Now, I've read in the Google groups that the root-directory of WM5.0 devices operates as the internal storage, but it appears that this information is faulty. The root folder is also emptied after a hard-reset.
Also my contacts and appointments dissapear after the hard-reset, which is normal WM2003 behaviour, but I thought they were persisted on WM5.0. Perhaps they only meant they are persisted when the battery is drained.
Well, in short:
Where can I put files on a WM5.0 device, specifically the Qtek 9100, so they aren't deleted after a hard-reset?
Is it even possible on a WM5.0 device, if so which device(s)?
Quick solution would be to use a SD-card and let my Autorun work with the OnCardInsert function, but that doesn't really float my boat....
WM5 uses its Extended ROM (Ext-ROM) to install customized software, which survive a hardreset.
Even though the answer isn't exactly what I was looking/hoping for, it did help a little.
First I was looking for the search-string 'persistant memory' or 'persistant storage' which gave numerous results, but none of them with answers to my problem.
Now I used Extended ROM as a search-string and that did help a bit better. Didn't even think about using this before, oh well, it appears posting a question does help indeed.
One of the answers I found was this:
[HKEY_LOCAL_MACHINESystem StorageManager ProfilesTRUEFFS_DOC1]
"MountHidden"=dword:00000000
"Folder"="ExtendedROM"
"PartitionDriver"=""
"Name"=""
"DefaultFileSystem"="FATFS"
[HKEY_LOCAL_MACHINESystemStorageManagerAutoLoadTRUEFFS_DOC1]
"Bootphase"=dword:00000002
"Order"=dword:00000001
"LoadFlags"=dword:00000001
"DriverPath"=" DriversBuiltInTrueFFS1"
The bold registry values need to be edited. This way you should be able to see the Extended ROM in the file explorer.
Well, it doesn't. You still can't see it. It is however possible to access the extended rom and write files to it by making files in \\Extended_ROM\\.
Still trying to figure out how to copy/move CAB-files to this directory, but that should only be a matter of time. Otherwise, the work-around is already in my head
total commander would do the trick, just type "\extended_rom" and copy up to 9.5mb of cab's
This is my first shot at doing anything with a Device's ROM so forgive me if I mention something stupid.
Basically what I'm trying to do is add one program to the install process, so when a Device is hard reset it goes back to factory + this one other program that I want to install.
I currently have it as a .cab package and the company I work for has given me an I-Mate K-Jam to learn how to do this, and then adapt it for newer devices. (which I'm sure will be a fun task).
I'm using the guide for creating a new ROM found here: (which is fantastic)
http://forum.xda-developers.com/showthread.php?t=303406/
The only problem is that I have no idea how to tell the package where to put files. The cab I have wants to put files in these directories.
[DestinationDirs]
CopyFiles1=0,"%CE2%"
CopyFiles2=0,"%CE4%"
CopyFiles3=0,"\Temp
If someone could explain this to me, or if there is an easier way to go about doing what I'm doing any help would be greatly appreciated.