I have unlocked the ExtROM and am using it, I have no need for the Orange customisations.
In the registry this is called HKLM\System\StorageManager\Profiles\TRUEFFS_DOC1 and can be unlocked, renamed, written to and even (by Buzz) erased and the space added to ... Main storage or \.
What about TRUEFFS_DOC and TRUEFFS_DOC2?
Which parts of the system are they?
DOC is typed as imgfs, which I imagine is the 128MB ROM that contains the OS, flashed in working state during a ROM upgrade.
DOC2 is FAT and could be the \ partition?
If we could make the DOC partition read/write (yes, very dangerous), even temporarily, could we overwrite the OS installed files with our own instead of taking up space in the \ memory?
Overwriting stuff in the 128MB partition seems more sensible than keeping the original file and using the valuable 64MB that HTC skimped on.
I know that you can cook a ROM to do this, but that is a long and involved process that isn't for the faint hearted. I'm tearing my hair out at the registry creation part, going through the posts here trying to make sense of them before asking another question in an already long thread. Renaming a few files and putting them in the expected places seems like a quick fix solution that if done properly shouldn't be too dangerous.
Universal DOC2 visible
In search for a find today, I'll post here how to make the DOC2 partition visible.
This registry adjustment allows you to see a new partition called 'ShadowROM' (saw it in the registry somewhere > the name I've given it last format). It contains all data, *.vol databases etc.. THE Windows basic replication folder. All your new/user data, as of the last install.
First things first: BACK UP YOUR DEVICE.
What you do with this is for your own purpose. Incorrect use and you loose all your data!
Open Notepad and copy/paste the following into a reg file which you can simply open on your device.
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\TRUEFFS_DOC2]
"Bootphase"=dword:00000001
change this to:
"Bootphase"=dword:00000002
to make the partition active in normal operation, being bootphase 2.
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC2]
"Folder"="ShadowROM"
To give the little beast a name.
Notice the extra screenshots I posted for oddities!
This is interesting... What are the pro & cons of keeping files and apps here vs external storage?
Is it just saving space for the apps that must be installed internally?
Are there performance or ram gains for the universal?
Thanks.
leaving the registry this way, I can delete files within that partition, or copy a (several megabyte in size even)file. Consequence of such an operation: next soft reset = hard reset. No 'buts'. Straight to 'OUT'.
I've been fiddling with other registry keys in the neighbourhood which seem to have some effect.
The use however... finding that there are several directories "Windows" and "Program Files" and so on... these events take up processing time, i/o operations, some of which have caused and probably will cause performance issues.
This looks more like a mess then 'user friendlyness'. If for instance backup or dataloss purposes are reasons for these... leave the device without charging for a couple of days.....
epicus, thanks for the sharing... Looks like I'd still need to wait a little bit before I venture into this.
I dumped tapres.dll to my PC, modified some of the phone dialogues using Resource Builder 2, now how do I replace tapres.dll on my HTC Apache?
I can't copy it into the PPC's windows directory where the original is, because the original is locked.
Any help with this?
Try total commander. It worked for me in a similar situation.
Can i ask you what you have changed?
Copy the file to the windows directory using total commander, it will overwrite. It still doesnt seam to let you delete the "system" file, but you can overwrite (at least it worked for me)
Later; Lew
Hey Lew,
TC seemed to do it for me first time, wrote over the system file. Decided I needed more work on my edited version, did so...second time around, it wouldn't overwrite my updated tapres.dll on the device.
So, decided to restore the original backed up copy. It let me rename my updated version which DID work, though visually unappealing (Ugly). Copied the original over, reset, no phone. Ugh.
Renamed the ugly version back, and was able to overwrite it with the original backed up tapres.dll. Reset..and again no phone. I have a nice PDA now, without the use of the phone. Grrrr.
Brick anyone?
I am from a generation where everything was command-line driven, and installing was copying some files into a directory.
Okay, windows doesnt work that way, no problem.
But I took a peek into the \windows directory and since space is tight in these little mainframes, I was shocked by the number of bullsh*t filenames:
(I have got an ENglish Tytn)
- 1st file doesnt have a name and type (1-5-06, 88B)
- 2nd is called ___cusTSKTEMP
- 2 files called 0 (different type, but type is hidden)
- also the same for files called 1 (2 pieces)
- loads of files called something like 034e7cf6- ...........
Who knows if these files can be deleted?
One other ? I cant run TCPMP well, is there any other experience around?
Hi everyone,
a couple of weeks ago, I just got myself my first HTC (Topaz). After some reading I decided to update my ROMs. So I backed up my data (at least I thought so), dumped my original ROMs with "Dump my phone", flashed Hard-SPL for Topaz, updated the Radio ROM and flashed a cooked ROM. Everything went smoothly and I was happy. Until I discoverd, that all my pictures were not on my SD-Card and hence I did not back them up.
After looking around for some time, I believe that Part03.raw from my dump should contain my pictures, etc. My question now is, is it possible - and if it is, how - to extract my pictures from Part03.raw?
I tried mounting Part03.raw with Daemon Tools, it seemed to work, but the "My Documents" folder is empty (but I see a bunch of other files scattered around the other folders). When I open Part03.raw with a hex editor, at least I can find the file names of the pictures.
Any help is greatly appreciated. Best regards, Dash.
You dumped the ROM, Read Only Memory. That's not the file and folder structure of the phone that you can see in the file explorer. That structure is created from the ROM. Your files are really lost.
That is what I thought. Thanks for the answer anyway.
Best regards, Dash.
Hi guys,
Recently i have noticed tha my t9 words are not working
I found this on xda
Directory("\Windows"):-Directory("ET9IMEDB")
Directory("\Windows\ET9IMEDB"):-File("eT9AsDb.Adb","\Windows\eT9AsDb.Adb")
Directory("\Windows\ET9IMEDB"):-File("eT9Rudb.Rdb","\Windows\eT9Rudb.Rdb")
but when i added it to initflashfiles.txt, all the files look like on the screenshoot
when i simply change a name of \Windows\ET9IMEDB to \Windows\ET9IMEDB_t, and change it back again to ET9IMEDB, files are normal, but after soft reset its the same story
so i did a mort script
Rename ("\Windows\ET9IMEDB\", "\Windows\ET9_temp\")
Rename ("\Windows\ET9_temp\", "\Windows\ET9IMEDB\")
and added it to StartUP folder, it works, but i want to know what is causing it
thanks for help in advance
Billy
ps. I am using leo3.02 IME packages on Topaz Rom
Wow, I'm glad I clicked this. I've run into the same crap many times. My temp fix is the same as yours. I don't use et9, but this has happened to me w/ several apps that I've relocated to windows, like ucweb. My only fix is to get corruptable files/folders oit of windows.
yeah, but you can't get this folder out of windows, cause it must be located there
Have you looked in the .reg file in the package? There may be a key in there that sets the path.
The files would get corrupted every time I would soft reset.
I'll add that for me, I've run into several apps that would give me corrupted files. Usually, it was apps that I'd relocated from \program files into \windows (to save storage space). For instance, Bing would do this to me. The rom files were fine, but the sub-folders would become corrupted after every soft reset if they were in the \windows folder. In particular, the XAML folder would go wonky. The fix was to rename it, then name it back. I'm sure you figured this out the same way I did: you couldn't delete the corrupted files/folders, or copy them, or anything, unless you first renamed them (lucky that worked). When I'd rename the folders, I'd notice that the files inside were no longer wonky. I made an EXT for FpseCE that was relocated to \windows, and all six sub-folders would become corrupted after a soft reset. It was a royal pain to rename them, so that was basically when I decided it wasn't worth the saved storage space to have the apps located in rom, so I moved FpseCE, Bing, and UCWEB (the CDDATA folder would go bad) to program files. The other app that would mess up on me was Weather2go (a today plugin). The Weather.dat file (located in \windows) would go bad for maybe the first 4 or 5 soft resets after a flash, but then it would mysteriously become stable. It was annoying as crap, because the plugin would go blank and not show the weather forecast after a reset. I don't know why, but now it works fine. Perhaps it's because I took the other 3 apps or so out of \windows. The really weird file that would screw up on me was an ID txt file for SK Today Commander. SK software puts an ID text file in windows for all it's paid-for apps. I have maybe 5 of their apps, and the files were fine for all of them except today commander. It would become corrupted at each reset. Now, it doesn't happen any more to me.
I wish I knew why it happens, but I don't. Now, if I'm making a package for a new app, I will test it before flashing, and do several soft resets to make sure that none of the files that might be created by the app are not corrupted after a soft reset. It's been a couple of months since I had the problem.
I looked at the xt9 package I have, and it looks like you can relocate the entire thing to another directory. It will be a pain in the butt, but if you really need it it might be worth a try. There's an installdir key that needs to be changed (from \windows), plus many keys for the path to all the dll's. I don't see a path for the databases, but they will probably move to the new location (assuming you change all the paths).
now i had finished all correctiong all errors for my rom (new packages from Oobe and Huashan) and new manila, i was using topaz ext before, but is it time to change it for a fresh apps
so i will have time to find solution for this, it may be to many files in rom, first i will try to remove some apps, my nhb file has 230mb, so it could cause problems in filesystem, we will see
I doubt it's that, but you never know. My rom is pretty light (only ~2500 files). I tried Task 29, and that didn't do jack squat. Moving things out of \windows was the only thing that worked. I guess maybe moving to osbuilder could help; maybe the module allocation in EVK is causing issues. I've never had S.O.D. before, but I have had this plenty. It's pretty clear that something hinky is going on during boot-up, though.
well i am using osKitchen v1.31beta10, so it's not EVK problem
OsKitchen and EVK are pretty much the same, though, aren't they? They both run platformrebuilder; I'm not sure if they handle modules the same way, but I suspect that they do. Osbuilder is supposed to do a better job of it, but the thought of converting all my packages over makes me want to hurl.
I figured out what is going on with this (sort of). I don't know why you get the corrupted files/directories in \windows, but I know how to avoid it. Files/folders become corrupted after a soft reset when their names are all capital letters. For instance, if I have a folder named \CDDATA in \Windows (or \XAML or \BIOS-those are from Bing or fpsece), then any file inside that folder will become corrupted after a soft reset (except for .lnk files, go figure). So, the key is to just rename the folder with lower case letters. In the case of UCWEB, which used the CDDATA folder, it works just as well with a folder named cddata, except that I can soft reset the device w/o issues. I'm assuming that Bing would work with an \xaml folder, and fpsece would work with all 6 of its sub-folders being named in lower case.
The same thing happens with files: if their name is all capital letters (inc. the extension), then they become corrupted after a soft reset. Renaming them fixes it (same with the folders). Anyway, this is why the OP's files go wonky in the \ET9IMEDB folder.
Like I said, I don't know why it happens. I get it with EVK roms and OSBuilder roms.
Farmer Ted good find, thanks