Database Users

Jeff's Exe

OK, I'll start by saying sorry for my stupidness and thankyou for listening to my plea.
I downloaded Jeff's XDA special edition .exe file and unzipped it to a Dir seeing all the files needed to upload a new ROM to my XDA.
I (in all my wisdom) decided to run the osimagetool with the --register and proceeded to right click on the nbf 30mb rom image and selected burn...thinking this was the way to do it (not even trying to run the original exe)
The "programme a" program started and started updating my xda. It started off updating and after a few seconds i heard the "BLIMP" of the activesync telling me it has disconnected, then another blimp telling me it had restarted and re-connected to active sync, but the loader on the screen quickly zipped to 100% done and told me to remove and reboot the xda. The xda however was telling me "upgrading... It will take about 5 minutes". Urk
Now im left with an XDA that sit's on this upgrading screen even after reboot of it.
OK... ive done wrong.. im silly... would any one step up and help me out here (BIG PLEASE AND TY also). Ive got an XDA serial cable sitting here next to me as well as the usb cradle (which im sure wont help now the xda cant run active sync)....
Ideas? Can i run the original rom uploader (xredit?) rather than osimagetool with the serial cable to upload either the new rom i have or the rom i backed up of my old device before doing all this (yes i did back it up to my harddrive first - phew?).
Thanks for reading, and i hope someone can point me to a place in the forum where all people like me end up, or even better send me an email pointing me in the right direction.
Thank you! (email Tony at [email protected])
Note: my original version was 3.17.03 and the "programme a" upgrade program said it was upgrading to 3.16.

can you tell me what splitrom says about the nk.nbf that is now in the 'english' subdirectory of the path
pointed to by the registry key "Software\\XDA Developers\\OsImageWriter", "Programme A Path" ( in current-user )

thanks for coming back to me.
unfortionately, i dont have perl installed on my windows xp machine so the batch file you linked to do doesnt work. If you have a link for a perl install anywhere I'll be happy to install and run it.
In the key you mentioned, here is the value: D:\XDAtools-Jeff\binaries
The directory i unzipped Jeff's version of your tools to.
Im not sure if you perl script does other things, so in the meantime, i'll go and try and find perl (im sure ive installed it on a work machine i had years ago - seem to remember adding local path variables for it)... i'll check my cd archive for it.
Thanks for the help, much appriciated
Tony.

perl can be obtained from either http://www.cygwin.com/setup.exe or http://www.activestate.com/Products/Download/Download.plex?id=ActivePerl

cheers, i'll dl then run the script....
n1 guv

C:\Documents and Settings\tkett.ADPLATES>D:\splitrom.bat
Can't locate List/Util.pm in @INC (@INC contains: C:/Perl/lib C:/Perl/site/lib .
) at D:\splitrom.bat line 86.
BEGIN failed--compilation aborted at D:\splitrom.bat line 86.
^^
Thats the error message i get when running that perl script.
Ive searched the hdd for Util.pm and its sitting in my c:\perl\lib\sgi dir
Things just arent going right for me at the mo.

this module is standard with perl 5.8, with perl 5.6 you have to install
it manually.
as a quick fix, you may also just add a 'min' function manually
Code:
sub min {
my $min;
for (@_) {
$min= $_ if (!defined $min || $_ < $min);
}
return $min;
}
and uncomment the line
Code:
#use List::Util qw(min);

C:\Documents and Settings\tkett.ADPLATES>D:\splitrom.bat
Usage: splitrom <romimage(s)> [options]
-wx xipchain where to write xipchain
-wo osrom where to write output image
-wb bitmap where to write bitmap
-wl bootloader where to write bootloader
-rl bootloader which bootloader to use for NBF
-n nbfinfotext what NBF header to use [ex: PW10A1-EN
-ri nbfinfofile or where to read NBF header info from
-wi nbfinfofile where to save NBF header info
-rx xipchain where to get xipchain from
-rb bitmap where to get bitmap from
-rm [email protected] insert new romsection.
-ob offset where to find the bootup image
-oe offset the end of the desired os image ( def
0000 )
-t NBF | B000FF | NB? | IMG type of result image (default is NB1)
^^^^ Ive put your routine in replacement of that line and am given the options above when running splitrom now. What parameter would you like me to run ?
As always.... a big thanks for the help.
Tony

Itsme, thanks for your interest in my problem. And im very glad people like you are around to help
I have however and thankfully repaired the fault.
Here, (for other newb's like me that get stuck) is how i done it:
I had already backed up my ROM using the osimagetool program to a nb1 file on my pc called "oldrom.nb1". Now because my XDA wasnt booting into Pocket PC windows, i couldnt use active sync to sent the rom image I backed up, back to the XDA...so I had to go and buy a cheap SD reader from my local Dixons store and run osimagetool again. This time writing the rom i had backed up to the SD card in the new SD reader.
Then I rebooted the XDA into the bootloader (hold down the top power button and do a soft reset) and selected to reflash the XDA using the SD card.
If you havent already backed up your rom from your xda to file, then I presume, you have to find another person with an XDA so you can download thers to your SD card (once your in the bootloader menu, press the contacts button to get the options to dump their rom to your card). OR find an NB1 file on the internet that matches your phone version.
These may be simple instructions for most of you, but i've seen a few posts that directly relate to the problem i had, and saw people crying for help, just like i did...hopefully this will help those few.
I did also have a serial cable, and im sure there is a way to upload roms you have on your pc to the XDA via that (using the xda developers old rom tool), but im afriad i didnt read into that after finding out this method. (this way may be better for the skint people who dont want to buy an SD reader, but can get hold of a serial cable for cheap)
REMEMBER FOLKS
It was silly of me to try and flash the device in the first place without reading loads and loads of entries on these forums and really finding out what is going on instead of just flashing blindly in the hope that it would work first time.... please dont follow my lead. :shock:
Thanks again for your help Itsme...and one last question... do you think that with that registry entry as it was above, that i can try again with the .exe jeff made (possibly downloading it again in case of corruption)
(yes i am a glutten for punishment)
Tony

still I'd like to know what went wrong in your case.
can you type 'splitrom nk.nbf' ( in the 'english' subdirectory )

sure:
D:\XDAtools-Jeff\binaries\English>splitrom.bat nk.nbf
this rom seems to be 3.17.03 ENG 2003-05-15 o2euro
this bootloader seems to be V5.15 2002-06-06 20:29:17
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 81401484 -- xip chain 8 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81940000 - 81d2d2b5 -- operator rom 81 files
Tony.

ahhh... haNG ON.... the one i used was in the .exe's folder.. not jeffs tools folder:
D:\XDA-developers-SER-v12\English>splitrom.bat nk.nbf
this rom seems to be 3.16.52 ENG 2003-03-10 XDASER-12
this bootloader seems to be V5.22 2003-05-15 17:46:55
no bitmap found
80000000 - 80040000 -- bootloader 0 files 1 modules
80040000 - 8026a804 -- kernel 13 files 11 modules
802c2000 - 8057d330 9 OS 15 files 32 modules
80580000 - 8075a69c 8 SHELL 79 files 27 modules
80780000 - 80a13b04 7 BROWSING 9 files 14 modules
80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules
80dc0000 - 80ebd150 5 SYNC 12 files 22 modules
80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules
81080000 - 81348248 3 24MCONSUMER 69 files 1 modules
81400000 - 814019a4 -- xip chain 10 xip entries
81440000 - 817f6f14 1 MISC 209 files 40 modules
81800000 - 818e0c14 10 XDA_DEVELOPERS1 13 files 0 modules
81940000 - 8198b6e5 -- operator rom 20 files
819c0000 - 81ee9a58 11 XDA_DEVELOPERS2 202 files 0 modules
hence the 3.16 now.

Hi Ajkett,
Thanks for sharing your knowledge of how to resolve your problem with us. I have however used a new 64 mb sd card to flash my old rom (3.16) to it before trying out the Jeff rom kitchen exe and thank god things are fine for me. Now I have bought a cheap 6 in 1 card reader/writer and would like to keep the old rom in a safe place in my hard disk hence freeing my sd card so that I could use it. I have read those threads in the rom tool section many times and still can't work out how to use the osimagetool. When I clicked on it, it gives me the interactive screen but always do not read my sd card. Even with the card reader, it seems to "think" that the sd card is unformatted and ask to format the card for me. Now the question is whether the rom is inside or not? How can I use the rom tools to read the sd card and copy the rom to the hard disk? What does a rom file appear as? Is it like the nk.nb1 file created in Jeff's rom kitchen?
Cheers
Vic

ahhh your trying to read the rom from the sd card after dumping it to the sd card from the xda?
the way i got it onto my harddrive was without an sd card. Just run the osimage tool and select the xda current memory as the source and then type c:\oldrom.nb1 as the destination.... it will use activesync to read the rom straight from the device.... you dont need the sd card to back it up.
Then when i ****ed my xda up, i run the osimage tool again and wrote from source - oldrom.nb1 to the sd card reader to a formatted sd card.
When it writes it, it gets rid of all the formatting so you wont be able to see whats on it on your pc....the only thing its good for then is to use on the xda to overwrite the rom, until you format it again that is.
Its not like a file on the sd card... its like a bootdisk with the rom written in a way that the xda will understand that its a bootdisk and will boot from it to overwrite itself... like the file is in raw format... not a nb1 file or anything (looks like lots of gobbledigoop) and the pc will not read it.

Thanks Ajkett,
Thanks for your kind reply anyway.
Got it done. The osimagetool could read but I did not write the path correctly; it has to be rom.nb1 apparently for it to work. I even used the card reader and managed to write the rom again the same way to my hard disk. I hope this is the correct way of doing it and it seems that the rom.nb1 file on my harddisk is about 30.5 mb which is probably about right for the old 3.16 rom I had dumped onto it by the XDA.
What puzzles me is that if it can read as source rom.nb1 file when you say you rewrite it to the sdcard, it becomes mumbo jumbo again but it should flash ok within bootloader mode via the XDA. Is this correct?
Cheers
Vic

yep your correct... even thogh it doesnt write a nice 30mb rom.nb1 file to your sdcard, the xda still reads it to boot from.... it must need it a raw info.

Deleting cab files in windows folder???

After installing a program f.ex. Pocket Informant - there is a 1 MB cab file in the windows folder. Can that be deleted - and then saving the storage space?

jenslilholt said:
After installing a program f.ex. Pocket Informant - there is a 1 MB cab file in the windows folder. Can that be deleted - and then saving the storage space?
Click to expand...
Click to collapse
yes. you might want to leave a copy on your computer for ease of reinstallation.
--M

I don't mean on my PC..... but on my PPC. When I install a progtram on my PPC - is the cap file in the windows folder needed?
The reason is, that I discovered, that after installing - and then deinstalling some programs - the cap file where still in the windows folder of the PPC.
My question is therefore: is the cap file used for the running program? And if so, I guess the deinstalling have been poor. Probably common known - I just have no idea...

You can delete the cab file. You can also move it to a storage card in the event that you need to reinstall the program later. But you do not have to keep it on your device.

disable file protection of windows folder

Hi, is there already any solution to disable write protection of the windows folder (ext rom) of the Touch 3g? I'd like to delete some stuff (cabs and sound/movie files) to get more space.
Till now I only found reg-mods or cabs for other phones which most likely wouldn't work on the 3G...

I thought the cab / sound / movie files can be easily deleted using file explorer or Total Commander or Resco

No Total Comander says "couldn't delete". Property of each file says "write protected", but when I uncheck write protection and close the properties dialogue, it's still the same: I can't delete and when I open properties once more, "write protection" is enabled again.

Can you post a few file examples. I'll see what's it like on mine. so we can compare.

thanks for your answers, azahidi! Here are two cabs.
When you look at the properties in Total Comander the box "in Rom" is checked, but it can't be changed, because it's greyed out.
What I noticed is that when I copy a file from the windows folder to my memory card, I can uncheck the "Read only" box in properties and when I copy it back to the windows folder, I can rename it. I can even cut it out from the windows folder and paste it to the memory card again, but when I look into the windows folder, it's back again, with "Read only" and "in Rom" enabled.
It seems to be like the system system file protection in Windows, where the system files are being replaced, when deleted...
So my next step was to create a 0 byte text file, rename it e.g. to "GoogleMaps-ms-htc_compressed.CAB" and overwrite the original cab in the windows folder. But the strange thing is that when you open "Start -> Settings -> System -> Memory" the data storage has not changed a bit...
What's actually strange, too, are the figures, in "Start -> Settings -> System -> Memory" under data storage (in German Datenspeicher, so I hope it's data storage in English)
Alltogether: 98.68 MB
Ocupied: 70.27 MB
Free: 28.41 MB
But:
Total Comander shows following figures for my internal storage:
Alltogether ocupied: 206.0 MB
Only windows folder: 180.9 MB
Files in windows\ without subfolders: 169.0 MB
So I think that part of the windows folder is in fact the ext rom, am I right? But there must be also a hidden part of the ext rom, where the protected files are stored... (compare wiki "extended rom".
So is there someone, who could give some explanation / links or knows someone who knows how to unhide and unlock the ext rom...

Chealuxx,
I understand your predicament. Now it seems that your problem has gone way beyond my expertise level.
Anyway, try this - http://forum.xda-developers.com/showthread.php?p=1571715
I remember using the ROMExtractor.exe once some time ago to modify something but I cannot remember exactly now. Hope this will help.

How to delete from /Windows/ ?

I am trying to save storage memory on my diamond. I want to delete the /Windows/ files Album Sample 01.jpg thru Album Sample 13.jpg which will free up several meg.
tried unsuccessfully with Total Commander...
any one help?
thanks

This means that they're in ROM and cannot be deleted

What you could do is make a image thats very small in data and rename to file names and overwrite with Total Commander.
You can do the same with music thats in ROM too zero length .mp3's
Hope that helps.

stylez said:
What you could do is make a image thats very small in data and rename to file names and overwrite with Total Commander.
You can do the same with music thats in ROM too zero length .mp3's
Hope that helps.
Click to expand...
Click to collapse
thats smart solution

dody said:
thats smart solution
Click to expand...
Click to collapse
smart but useless, since in this way you don't save anything: overwriting ROM files with smaller ones doesn't reduce disk usage but, vice-versa, increases it (since you'll still have the ROM files AND the new ones) also if only of some bytes

bbonzz said:
smart but useless, since in this way you don't save anything: overwriting ROM files with smaller ones doesn't reduce disk usage but, vice-versa, increases it (since you'll still have the ROM files AND the new ones) also if only of some bytes
Click to expand...
Click to collapse
Ah i get you as the files have to still be there for the ROM to be able to rewite the file, know what mean
Good idea though

I don't get you, stylez. "Overwriting" ROM files is only a verbal expression, since you don't really overwrite anything. When you copy to \windows a file that has the same name of a ROM file, simply the system reads the one on disk instead of the ROM one, that (simply for being in ROM) is still there and cannot be changed/edited/deleted.
So, if you "overwrite", for example, the abc.bmp ROM file with a 0 byte abc.bmp, the original one is still in ROM but the system don't read it anymore: instad it reads the 0 byte abc.bmp. And being a 0 byte file, you don't waste disk space, but as the same time you don't gain new space: you can try and see the free space before and after an overwrite with a 0 byte file

bbonzz said:
I don't get you, stylez. "Overwriting" ROM files is only a verbal expression, since you don't really overwrite anything. When you copy to \windows a file that has the same name of a ROM file, simply the system reads the one on disk instead of the ROM one, that (simply for being in ROM) is still there and cannot be changed/edited/deleted.
So, if you "overwrite", for example, the abc.bmp ROM file with a 0 byte abc.bmp, the original one is still in ROM but the system don't read it anymore: instad it reads the 0 byte abc.bmp. And being a 0 byte file, you don't waste disk space, but as the same time you don't gain new space: you can try and see the free space before and after an overwrite with a 0 byte file
Click to expand...
Click to collapse
You misread me as i agreed with you "not in the right terminology"
Thanks for expanation
Sorry for a quick idea that doesn't work and if had of thought about it logically would have known "spending too many hours editing .dll & .cprs"

stylez said:
i agreed with you "not in the right terminology"
Click to expand...
Click to collapse
lol

Desactivation of the booting ring?+Endless notifications

Hi,
i have just upgraded my topaz to the win6.53 latest htc Rom,
and i find the booting ring (first seconds when switching it on)
rather annoying (too loud) ; So how to make the boot silent?
Another worrying bug :
when device is locked , a "1" (missed call/new sms) appears
even if i'm cleanning the notifications.
And the ring choosen for new vocal mail rings after each softreset
even after cleaning the notification
thanks

For the first problem, try this:
- Create a empty .txt file in your pc
- Rename the .txt file to "HTC-QuietlyBrilliantBoot.wav" (no quotes)
- Copy the file to your phone's memory card.
- Use Resco Explorer or Total Commander and copy the file to Windows folder in the main memory, overwriting the old one.
While you're at it, do this too for the "opera9.exe" file (I use opera 10) and "copilot.wm6ppc.cab" (I don't use it) and save about 16 mb of space.

joooe said:
For the first problem, try this:
- Create a empty .txt file in your pc
- Rename the .txt file to "HTC-QuietlyBrilliantBoot.wav" (no quotes)
- Copy the file to your phone's memory card.
- Use Resco Explorer or Total Commander and copy the file to Windows folder in the main memory, overwriting the old one.
While you're at it, do this too for the "opera9.exe" file (I use opera 10) and "copilot.wm6ppc.cab" (I don't use it) and save about 16 mb of space.
Click to expand...
Click to collapse
Hi Joooe ,
many thanks that's quietly brilliant
good idea about copilot, i use zorro instead