TPEnable.exe question.. - PDA2, XDA IIi, 2020i Software Upgrading

I'm trying to cook the latest 1.11.171 Extended ROM from O2 by removing all the O2 stuff...
I can sucessfully update the ms_.nbf file by using the alpine_ext_rom_tool.
The updated ROM downloads ok to the XDA IIi but towards the end of setup I get the following error message 'The file \Extended_ROM\TPEnable.exe is not a valid Windows CE Setup File'.
Clicking on 'ok' the message goes away and the touchpad is enabled??
Any ideas on how to fix this error message?

The best bet is to delete TPDisable.exe and TPEnable.exe files from the ROM and references from the Config.txt file. This will leave more room for other, useful programs. They're not needed.

Related

Need help in installing the V1.2

File was downloaded from Jeff Summer site. I click on the downloaded file and it would start unzipping and the adaptROM program would run itself. The Programme A shows up and and displays STEP 1, Welcome to ROM upgrade utility.
Go next. Release note is empty. Next again I will get the Error 007 message saying that NO ROM IMAGE FILE.
I am using AT&T SX56 and running Window 98, and had no problem upgrading before from Siemens site.What can I possibly do wrong?
Thanks.
try this.
unzip the 'jeff summers' file to a new folder on your desk-top for convenience.
check that you have
adaptrom.exe
programme A.exe
readme.rtf
start.bat
English (folder)
CLoader_serial.nb
CLoader_usb.nb
GetConnectionType.dll
Nk.nbf
remote_flash.exe
SetSystemTime.dll
if all files are present, connect your XDA and run start.bat.
if any files are missing, although they shouldn't be, download the .zip file again.
ian

PPC 2003 and mkrom

Any brave soul try using mkrom in conjucntion with the 2003 ROM? I think I might give it a shot here in a bit but wanted to know if anybody had tried it yet...
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
sheran_g,
i didn't know u could use mkrom with 2003 rom image. can u please post how u did it? i created a special version based on SE 1.1 rom but would like to put the same programs into the new rom. any help is appreciated.
thanks
alex
sheran_g said:
I've managed to build a 2003 ROM. It's extremely tricky though. I'm working on customizing a ROM similar to the XDA Developers SER - as soon as I get some free time
I'd like to acknowledge all the help given to me by Developer Itsme in this endeavor.
Let me know any suggestions you may have for the new ROM.
Click to expand...
Click to collapse
What's tricky about it...?
The modified registry file you make does not get picked up at the device startup. You need to manually inject the memory address of the modified registry file into the ROM in order for it to get picked up.
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
sheran_g,
can u post the steps that u take to buid it? i'm trying right now and its not working. i'm having little problems. can u post ur default.reg and initobj.txt? any other help is apreciated.
thanks
alex
Ok. Here they are in a nutshell:
Get the latest romtools.
Make the following dirs: romfiles, cfg, tmp, out, files, files1, files2
Split the ROM into Bootloader, bootimage, OS image, xipchain into the 'cfg' dir.
Dump the files in the OS image into a 'romfiles' dir.
Get the default registry file, initobj & initdb files into your 'cfg' dir.
Make changes to your default.reg and initobj.txt
Place any files you want loaded in the ROM into the 'files' dir.
Run 'mkrom.sh'
You should then have your new ROM. I'm sorry if it's extremely brief; you'll have to make do with this and the README file in the romtools archive file for now. You'll find my default.reg and initobj.txt files on my site: www.zensay.com/qtek/mkrom
sheran_g,
Have you created a decent working custom WM2003 ROM?
If so what Apps have you added?
How much ROM space does it use?
I've not added any apps to my ROM. I have only added a carrier logo file and made some changes to the registry. So I cannot comment on ROM space yet. The ROM works fine.
sheran_g,
what command did u use to extract rom files? did u do it under windows or unix?
I'm having problems trying to dump the rom image. I don't know if its too much to ask, but can u zip ur directory and post it somewhere so i can download it? or if u can post commands that u ran to dump the 2003 rom?
thanks
alex
Hi,
could you include "O2 home zune" to the 2003 image, like in the 2002 3.19 GER. Its for Germany interested only!
AR :?:
home zone depends on specific 3.19 rilgsm features. which are not in 4.*
okay, used dumprom -4 -d files -q nk.nbf and extracted all files. Got could not find pointer for ofs 00000000 ERROR but all the files seem to be there. Trying to figure this out. Saw the above abreviated directions but am fumbling around. Anyone have concise directions?
Val
Anyone? Just give me a good hint then please.
Hi all!
When i overwrite the rilgsm.dll file in the t-mobile 4.0.10 image with the rilgsm.dll from the O2 GER 3.19 image, i could use the "O2 home zone" option with the hz.exe in Starup directory? rilgsm.dll from german image hes 'at+creg=2' string in it. probably the RIL_GetCellTowerInfo call is now implemented. When it can work, how could i write the german rilgsm.dll to the image? I haven't linux, could somebody cook the image for me?
here is the germen rilgsm.dll and the hz.exe for the "home zone" funktion! http://www.nokiaprog.de/XDA/home_zone.zip
THX
PS: Sorry, my english! ;-)
AR
the homezone enabled rilgsm.dll depends on other dll's and exe's.
probably ril.dll, stk.exe, cell*.dll and maybe more, I have not tried
replacing all.
you don't need to build a new rom in order to experiment with this, you
can just copy the desired files to \windows, to override the rom versions.
And I don't think it works with the RIL_GetCellTowerInfo call,
but adds some notification events.
to change the CREG setting you need to call RIL_DevSpecific with parameter 25 ( to turn it on ) or 26 ( to turn it off )
even though that does not seem to be how hz.exe does it.
Hi,
I opened the image file in the Hex editor and renamed the file there rilgsm.dll. Then I flashed the image, which was phone probably deactivated, because rilgsm.dll was missing. Then I copied over ActiveSync the German rilgsm.dll into the Windows directory, XDA reset and he not accept the file. I assume because the file was not in the EPROM memory! Therefore I wanted to have rilgsm.dll first times in the image!
AR
XDA developer Itsme said:
my latest romtools can be found at romtools
now it calls dumprom to find and fix the filedata offsets.
I think they should now build 2003 roms.
Click to expand...
Click to collapse
Is there any other way i can access this site or I can download this files, the sites are block here in my country, Please Help
Ronnie

XDA tools nearly there but can't understand, any help plse

I have installed jeff summers version of xda tools. And though I think I understand what I am doing I am not totally convinced. Before I embark on cooking roms and upgrading etc I would like to be able to do the following:
1: Dump my current rom from my device to my PC I can do this using XDAtools OSImage but can only Can this only be NB1(windows CE(*.nb1) type files if I try to call this NBF I get the following error:
error opening C:\program files\xdatools\bootloader_v5_15.nb0ea for reading. the system cannot find the file specified.
error opening source bootloader from C:\program files\xdatools\bootloader_v5_15.nb0ea. error opening target device.
Can I dump my device memory into a file called ‘xxxx.NBF’?
2: When I try to upgrade my ROM by:
Start OSImage tool and select source as:
‘C:\PROGRAM FILES\XDATOOLS\BINARIES\ATT160204.NB1’
Select destination as ‘device memory (via programmeA) ‘
When attempting to load an ‘NB1’ ROM from my PC to my device memory (via programmeA) I always get the following message:
ProgrammeA not found - run with --register error opening target device.
I originally ran the programmeA with --register when first installed.
I have tried searching for a solution but to no avail. Any help appreciated.
Thanks John.
If you're trying to burn your original ROM back to the device that shouldn't be a problem. Use the [...] button to locate your .nb1 ROM for the source, and select Device Memory (via Programme A) as your destination.
Have you installed ProgrammeA.exe into the binaries folder of XDATools? That's the only thing I can think of.
Thanks I have tried this but believe the problem is the ProgrammeA file but it is definetly in the binaries folder. I am running win98SE but don't think this should be a problem. When you run jeffs tools it extracts itself out under program files and places all the required files in the right directories. Would appreciate it if any one out there can supply some help ?
Thanks John
I think I know what the problem is...
I have the same problem. If you look at the dos box that pops up you see that programmeA.exe looks in to the \\Binaries\English\ folder for a *.nbf file. It looks like you will have to provide it a *.nbf file in stead of a *.nb1

wrong NDF while uodating ROM

Hi,
I own a qtek 9100
While I was updating the ROM 2.17.17.02(that I downloaded from this website) I got an error " WRONG NDF"
Anyone knows what could be the problem?
FP
I suggest that you swap over to the "Wizard Upgrading etc" forum and start doing some basic research. The .nbf file contains a number of fies (OS, RAdio, Splash screens etc) all of which have a .nb extention. The .nbf file more than likely is packaged in some executable which is used to deploy it on your 9100. If you are getting a message saying wrong file then you are likely not using the correct ROM for your device or the file may be corruped.
Thank you for th esuggestion.
I went over the Wizard upgrade forum. It'a bit mixed up!
I donwloaded the 2.17.17..... ROM version.
when I install it, it stops at 85% and gives me a error message 326!
Any Idea?

Windows file attribute problems

Hi All,
I need your advise regarding copying files from and to Windows directory on my Hermes. Before I flashed the unit with DOPOD, I-Mate and new WM6 Vanilla Roms I was able to replace any file within my windows directory - like the one phcanOcerbmp.dll to get 3G icon instead of U. After i finished flashing and finally decided which ROM I'll stick with - latest HTC - I can no longer replace any files. Every attempt of doing so ends up with a message - cannot copy - access denied etc. If I check the individual file's attribute it is marked as "read only" and "system". Is there any way on earth to change the attribute and go back to where I was before flashing??? Was there somethin in one of those ROM's that caused it?
Thanks for all your comments.

Categories

Resources