Just got my device back from "the shop" with a new MB as it had the stuck in bootloader problem. Unless I'm missing something, with WM2005 there's no extended ROM, or, as it used to be called "storage".
Is it that no one has figured out how to unlock the extended ROM yet, or is there no longer such a space in the physical ROM?
8) 8)
http://forum.xda-developers.com/viewtopic.php?t=33638
You know, the one right at the top of the forum, sticky, can't miss it?
PReDiToR said:
http://forum.xda-developers.com/viewtopic.php?t=33638
You know, the one right at the top of the forum, sticky, can't miss it?
Click to expand...
Click to collapse
Yeah, I know about that thread, which was started months ago back when WM2003 was the ppc OS, which did have a unlockable extended ROM. There are only two posts at the end of the thread about unlocking the extended ROM with WM2005. Neither of them confirms anything.
That's why I made a new thread, because there isn't an unlocker for WM2005 yet PReDiToR and I wanted to find out if anyone was working on it.
cool_case said:
Yeah, I know about that thread, which was started months ago back when WM2003 was the ppc OS
Click to expand...
Click to collapse
The Universal never ran on anything but WM5. It was marketed as the first WM5 device available.
cool_case said:
That's why I made a new thread, because there isn't an unlocker for WM2005 yet PReDiToR and I wanted to find out if anyone was working on it.
Click to expand...
Click to collapse
By "Extended ROM" and "unlocker" do you mean what I think you mean? The 10MB partition that holds operator .CABs that are loaded after a hard reset? And you want to take away the write protect, make it visible and use it as storage?
If we are talking at cross purposes, please let me know.
PReDiToR said:
cool_case said:
Yeah, I know about that thread, which was started months ago back when WM2003 was the ppc OS
Click to expand...
Click to collapse
The Universal never ran on anything but WM5. It was marketed as the first WM5 device available.
cool_case said:
That's why I made a new thread, because there isn't an unlocker for WM2005 yet PReDiToR and I wanted to find out if anyone was working on it.
Click to expand...
Click to collapse
By "Extended ROM" and "unlocker" do you mean what I think you mean? The 10MB partition that holds operator .CABs that are loaded after a hard reset? And you want to take away the write protect, make it visible and use it as storage?
If we are talking at cross purposes, please let me know.
Click to expand...
Click to collapse
My mistake, the Uni always only had WM05. You're right.
Re-read the extended ROM unlocker thread. Got into extended_ROM with Total Commander. Moved all the cab files out of ext_ROM. So, that can still be done in ROM version 1.30.76.
But, I haven't figured out yet how to "see" the extended ROM. In prior versions of the ROM you could see the separate 10MB partition using the memory utility. Haven't been able to do that yet.
You're welcome.
It's a doddle, two files to run, a little registry edit and a reboot.
I called mine "Storage" and after compressing the files I have, this is what it looks like:
Sorry for the mix-up, PReDiToR. The methods in the ext_ROM thread still work for ROM version 1.30.76 to unlock the ext_ROM. (See my edited post above.) I've gotten into the ext_ROM and moved all the cab files out, but I can't "see" this area to use it, though I can see it as empty in Total Commander.
Maybe it's that I need to rename it, but I thought the utility I got from BuzzDev.net renamed it "extended_ROM". Going to fiddle around with it more.
the utility only makes it writable. you still need to edit the registry
The ROM version doesn't have any effect on it. The factory partitions the DOC, we're not altering that setup (yet). If you reflash your device the ExtROM data goes back into the ExtROM and it is all locked up again in the new OS that you installed.
To use this 10MB You need to do three things, and one optional step:
Run Buzz's unlocker.
Make it load in the right boot phase (Reg Edit).
Make it mount as visible (Reg Edit).
Change the name if you want (Reg Edit).
The unlocker is on page 1 of that thread, the registry edits are on page two.
Once you have done those things, do a soft reset (using psShutXP preferably, or wait 5 minutes before pressing the reset pin).
PReDiToR said:
The ROM version doesn't have any effect on it. The factory partitions the DOC, we're not altering that setup (yet). If you reflash your device the ExtROM data goes back into the ExtROM and it is all locked up again in the new OS that you installed.
To use this 10MB You need to do three things, and one optional step:
Run Buzz's unlocker.
Make it load in the right boot phase (Reg Edit).
Make it mount as visible (Reg Edit).
Change the name if you want (Reg Edit).
The unlocker is on page 1 of that thread, the registry edits are on page two.
Once you have done those things, do a soft reset (using psShutXP preferably, or wait 5 minutes before pressing the reset pin).
Click to expand...
Click to collapse
It had been so long since I did this before, didn't remember having to do all of those steps.
Got it up and running now with the extra 10 MB of space in extended_ROM. Had to use this version of the registry key edit:
[HKEY_LOCAL_MACHINESystemStora geManagerAutoLoadTRUEFFS_DOC1]
"Bootphase"=dword:00000002
"Order"=dword:00000001
"LoadFlags"=dword:00000001
"DriverPath"=" Drivers/BuiltIn/TrueFFS1"
Thanks for the help!
If you do the other registry change - MountHidden = 0 - You will see it as another storage card in your file explorer, and changing the name to something else is helpful.
Once you have done these two things the option to install things to the 10MB comes up when you run .CABs.
No problem.
PReDiToR said:
Once you have done these two things the option to install things to the 10MB comes up when you run .CABs.
Click to expand...
Click to collapse
Yeah, uninstalled a few things from program memory and installed them in extended_ROM. Had done that before the JJ went down for repair - glad to get an extra few megs of program mem back and have extended_ROM space to spare.
PReDiToR said:
If you do the other registry change - MountHidden = 0 - You will see it as another storage card in your file explorer, and changing the name to something else is helpful.
Click to expand...
Click to collapse
Had already done the other registry edit below, but am not able to change the name from extended_ROM2. Not a problem, but a little annoying.
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC1]
"MountHidden"=dword:00000000
"Folder"="Extended_ROM"
"PartitionDriver"=""
"Name"=""
"DefaultFileSystem"="FATFS"
Try this, which is straight from my Uni:
Code:
[HKLM\System\StorageManager\Profiles\TRUEFFS_DOC1]
(Default) = (Value not set)
DefaultFileSystem = FATFS
Folder = Storage
MountHidden = 0x0 (0)
Name =
PartitionDriver =
[HKLM\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
(Default) = (Value not set)
BootPhase = 0x2 (2)
DriverPath = Drivers\BuiltIn\TrueFFS1
LoadFlags = 0x1 (1)
Order = 0x1 (1)
This should have it loading at the right time and you can change the name from "Storage" to whatever you want, assuming you haven't changed any of the other DOC settings.
I know when I was playing with the "ShadowROM" (TrueFFS2) I managed to get it in the wrong bootphase and it came up Storage2. I think Buzz posted something about that in another thread.
I wouldn't live with it having the wrong name, I have to get it absolutely right. I spent ages tonight trying to get the WADesktop \Themes folder into \Storage which caused all sorts of problems and registry edits.
My device, my way.
edit: missed a line of code.
PReDiToR said:
Try this, which is straight from my Uni:
Code:
[HKLM\System\StorageManager\Profiles\TRUEFFS_DOC1]
(Default) = (Value not set)
DefaultFileSystem = FATFS
Folder = Storage
MountHidden = 0x0 (0)
Name =
PartitionDriver =
[HKLM\System\StorageManager\AutoLoad]
(Default) = (Value not set)
BootPhase = 0x2 (2)
DriverPath = Drivers\BuiltIn\TrueFFS1
LoadFlags = 0x1 (1)
Order = 0x1 (1)
This should have it loading at the right time and you can change the name from "Storage" to whatever you want, assuming you haven't changed any of the other DOC settings.
I wouldn't live with it having the wrong name, I have to get it absolutely right. I spent ages tonight trying to get the WADesktop \Themes folder into \Storage which caused all sorts of problems and registry edits.
My device, my way.
Click to expand...
Click to collapse
Ok, that registry change got the name of extended_ROM area changed to "storage". Thanks much!!
[Off track, but ... boy, you're right about WADesktop being a pain with which to work. When I changed the name of the extended_ROM to storage, had to change a line in quite a few dock and other files. WAD was much easier to work with when everything you made for your "your way" desktop was contained in the file default.skin. Now, to see or change stuff on your WAD desktop, you have to open up and change a ton of little files. Still, WAD is great stuff. Without it, the desktop is painfully restrictive and way too boring.]
I'm not tackling putting the WAD themes folder into storage. Getting the main WAD files and the WA2 files into storage frees up enough space - as much as my patience can handle.
I'm impressed that you did it, though!
PReDiToR said:
I know when I was playing with the "ShadowROM" (TrueFFS2) I managed to get it in the wrong bootphase and it came up Storage2. I think Buzz posted something about that in another thread.
Click to expand...
Click to collapse
What's in the "ShadowROM"? What can you do with it?
Here there be dragons ;-)
PReDiToR said:
Here there be dragons ;-)
Click to expand...
Click to collapse
How does one sneak into the cave without them noticing?
Back up before you try this, as the thread says, it usually leads to an unavoidable or sudden hard reset.
ShadowROM.
If you venture in, tell us what you find =)
PReDiToR said:
Back up before you try this, as the thread says, it usually leads to an unavoidable or sudden hard reset.
ShadowROM.
If you venture in, tell us what you find =)
Click to expand...
Click to collapse
Hmm ... looks like if you use it, it isn't shadowing the storage memory anymore and on a soft reset it hard resets back to mimic the storage memory. It's kind of like a RAID 1, but not exactly.
Maybe someone will figure out a way to not have it tied to the storage memory any longer and make it usable as an extra storage area.
However, I think it was intended as a backup area. A better hack might be this - finding find a way to use it as a backup for the OS + installed software, with a way to take an image of what's installed on demand. Then, if something gets messed up and you need to restore, you could restore the image you took.
Related
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
Hide/Show Hidden ROM (at least works on my TyTN - German ROM)
SHOWN:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000002
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000000
HIDDEN:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000001
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000001
For me this was the default:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000002
So, I only had to change this from 1 to 0:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000000
Now I can see the extended rom, my device is an HTC TyTN WWE, I will post the ExtROM to FTP in a while.
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
pof said:
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
Click to expand...
Click to collapse
GREAT !
Now we still need 2 very important Registry Hacks (or missing links to get them work):
1. A hack for presenting a differentiation between GPRS/EDGE and UMTS/HSDPA
2. A hack for invoking the EngineeringTest Mode
I've been unable so far to get that working on the Hermes platform. Keep trying.
pof said:
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
Click to expand...
Click to collapse
GREAT !
Now we still need 2 very important Registry Hacks (or missing links to get them work):
1. A hack for presenting a differentiation between GPRS/EDGE and UMTS/HSDPA
2. A hack for invoking the EngineeringTest Mode
I've been unable so far to get that working on the Hermes platform. Keep trying.
pof said:
Now I can see the extended rom, my device is an HTC TyTN WWE, I will post the ExtROM to FTP in a while.
Click to expand...
Click to collapse
Thank you.
I finished uploading my ExtROM, I also created a wiki page with the contents of all the available Extended ROMs on FTP so far:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtendedRoms
If anyone has a different version not listed, please do the following:
1) Unhide it
2) Zip it
3) Upload it
4) Update the wiki page
Thanks!
pof said:
I finished uploading my ExtROM, I also created a wiki page with the contents of all the available Extended ROMs on FTP so far:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtendedRoms
If anyone has a different version not listed, please do the following:
1) Unhide it
2) Zip it
3) Upload it
4) Update the wiki page
Thanks!
Click to expand...
Click to collapse
Heh, youre busy one.
I added a registry tweak to change the titlebar clock to an annalog one, if someone is interested.
Hopefully we can keep the wiki growing and useful.
My default setup was also:
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\EXT_FLASHDRV] "Bootphase"=dword:00000002
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000001
So I just changed to:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\EXT_FLASHDRV] "MountHidden"=dword:00000000
and did a soft reset. The extended rom then appeared but it was still write protected. How do I get rid of the write protection?
LJ
Use the cab file in the wiki, it unlocks and unhides ExtROM.
After using the cab fille and/or making the tweaks myself, and the are the same as described as above, the result is that I can see the ext. rom, but it is still write protected. I can't delete any file or write a file to the ext. rom. I've got a Tytn WWE. What is the problem, or better: what is the solution???
Should be wrtitable using this cab:
ftp://xda:[email protected]/Hermes/Tools_and_Programs/HERMES_MountExtROM.CAB
If it's not, then try to hard reset and then use the cab without messing with registry keys before.
Problem with Extended ROM
I have tried all the methods in the wiki and also all the reg. edit trick but I still can't see my extended ROM. When I run the cab to Mount Extended ROM it crashes my TyTN. Locks it up befor making it to the windows screen. Does anyone have any ideas how to fix this or tell me where to look? I was going to mess around with bootloader but I am not that computer savy.
hard reset and install the unhider&unlcoker cab file. it should work after hard reset.
Have tried to Hard Reset my Taiwanese CHT9000 and only apply the HERMES_MountExtROM.CAB tweak, now can see the Extend ROM, but still cannot "unprotect" the ROM. Cannot make it writable. Any other methods? Like modifying the registry? Thanks a lot in advance!!
ghl10000 said:
pof said:
I also have updated the wiki page with your hack:
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unhide_Extrom
Thanks!
Click to expand...
Click to collapse
GREAT !
Now we still need 2 very important Registry Hacks (or missing links to get them work):
1. A hack for presenting a differentiation between GPRS/EDGE and UMTS/HSDPA
2. A hack for invoking the EngineeringTest Mode
I've been unable so far to get that working on the Hermes platform. Keep trying.
Click to expand...
Click to collapse
On my Vario 2, when I'm using 3G (and therefore, HSDPA) the [3G] icon is shown in the top bar (and when it connects a small connecting icon with the moving arrows and 3G in it is diplayed, next to the square 3G indicator) - when it drops back to GPRS, it just changes to [G].
Does yours not do this?
rcyh said:
Have tried to Hard Reset my Taiwanese CHT9000 and only apply the HERMES_MountExtROM.CAB tweak, now can see the Extend ROM, but still cannot "unprotect" the ROM. Cannot make it writable. Any other methods? Like modifying the registry? Thanks a lot in advance!!
Click to expand...
Click to collapse
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=453&PN=1
Unsure whether it works myself, as I've not tried it yet, but I'd put (a small amount of) money on it that it works
Hi Chris, Thanks for your reply!!
Unfortunately, my device is still un-protectable after following the whole process. And the registry settings I have checked are exactly the same as the described. The Extended_ROM directory is still write-protected. Couldn't add or delete files in it.
Maybe I am the unlucky one that couldn't change the extended ROM at all...
Since the digital signature security autentification for CABs in ExtROM is on by default, putting in any CAB file that is either not digitally signed, or loses its authenticity because it was modified will not be installed during the Customization phase after a hard reset.
Any ideas how to solve this problen on TyTN?
There was the soluton for the Universal devices wiht the Default_Signed_DisabledSecurity.CAB. This CAB has the right signature for Universal, but it dosn’t work on TyTN.
From this MSDN discussion about Windows Mobile 5 code signing,
"Looks like you won't have to sign the cab if wceload.exe isn't used to install it. Although if it is used to install the cab file you will need to sign it."
Click to expand...
Click to collapse
http://blogs.msdn.com/windowsmobile/archive/2005/12/17/security_model_faq.aspx#506035
A possible gap? If someone could come up with a third party CAB installer that could be used during customisation, maybe it could bypass the official CAB installation procedure (and therefore the signed certificate verification) entirely? Just a thought.
For Universal this problem i think was decided here (http://forum.xda-developers.com/viewtopic.php?t=33638&postdays=0&postorder=asc&start=150) with the help of Default_Signed_DisableSecurity.CAB. But this CAB not work on my TyTN. I think it because of wrong digital sign.
Hi there,
I made visible the extended ROM of M600 with registry tweaks seen in this forum. I dont use any of the programs on the extended ROM, coz I dont like my phone to be customised for my service provider. (I soft reseted while it was trying to customize after the hard reset).
Now I have a 10MB of Ext ROM on "My Device". My qustions are;
1) Is this Ext ROM just like another 10MB SD Card?
2) WOuld this space make the my handheld run faster? or can this be made available fot programme memory?
3) Is there any advantage of installing programmes on it compared to on th SD Card?
Currently I have about 3MB of Orange CAB files on it. None of them I use.
How can I use this space efficiently?
Thanks in advance for any comments
ps: Another thing I just remembered is that, after I made this Ext ROM visible, I cant save the camera pics to SD card. The options on the camera settings are to save it on Main Memory or Ext ROM! it doesnt recognise SD card! funny! Any way around?
Anyone please..?
I order:
1) Yes it is exactly like a 10MB SD card, you just can't remove it from the device. If you need to hard reset it will become hidden again but the data will not be lost.
2) No. Program memory is RAM and this is FLASH. You can only use it for storage.
3) It is mounted before the SD, so if you have an app that needs to run on start up, you can put it on the ext ROM but not the SD.
4) I suggest you move the Orange cabs to your PC. Having the i-mate variant I had 9MB filled with stuff out of which all I needed were Skype and Voice speed dial. Then use this space for the basic and most needed apps. Also some apps like TCPMP can be used with content from different SD cards so ext ROM would be a good place for them. I try to keep main memory free for outlook stuff.
5) Yea, the camera app only seems to recognize the first storage card it sees. Don't know about a fix for that.
levenum said:
[...]
5) Yea, the camera app only seems to recognize the first storage card it sees. Don't know about a fix for that.
Click to expand...
Click to collapse
Thank you very much, Levenum!
I finally understood a bunch of things about the ExtROM.
About this 5th point, I would add something.
The same identical problem raises when the \Network path created by Resco Explorer is shown on the main memory root.
The internal camera seems able to access only to the first two objects in the mountpoint list (you can see this list when installing some apps, as the dest options radio button)
So, question comes out: what about hiding ExtROM again after installing startup apps on it ?
I mean: are those apps still runnable, when staying on a hidden mountpoint ?
Thanks for any answer
..._
Sorry to butt in on this topic, but I have also been thinking of doing this.
I would just like to know though once the Extended Rom has been unlocked as described in many past posts, can you lock it again?
I am just asking this because, what happens if I have to return the phone? Surely messing with it would void any warranty?
I would need to restore the CABS back to Extended Rom, and then lock it before returning it.
Thanks
Val3r10 said:
So, question comes out: what about hiding ExtROM again after installing startup apps on it ?
I mean: are those apps still runnable, when staying on a hidden mountpoint ?
Click to expand...
Click to collapse
Interesting, I never tried it. Perhaps if you don't change the MountHidden flag, but only the MountOrder.
NewSPV said:
I would just like to know though once the Extended Rom has been unlocked as described in many past posts, can you lock it again?
Click to expand...
Click to collapse
I don't know about other devices, but in case of the Prophet it's just a matter of changing back the registry values and soft resetting.
Thanks for that.
I have already backed up my Extended Rom, as Total Commander let me copy the CABS without unlocking the Extended Rom.
Orange has only added 1.95 MB which seems such a waste of vital memory.
I have heard that approx 10 MB is set aside for this. Is this set physically in manufacture by HTC? Can the extended Rom be merged into main memory like partitions can be merged on a PC?
Thanks
I read somwhere that removing things from the extended rom gives the device more storage available and shown int he memory part of settings. This however is not true, the extended rom is a seperate partition, full or empty the device will work the same.
I use mine to store the cabs of installs I use when I hard reset. Saves me copying them over each time.
Thanks very much Levenum and others who contributed. That was very informative and I am glad many others have benefited with this thread.
Cheers
One note:
I made a little experiment this Friday, which require a me to restore my Jamin to it's original state. (Hard reset + restore ext ROM).
I didn't check the CAB attributes when I copied them so even though the ext ROM was in it's original state all cabs that were used after first hard rest were deleted and didn't install after second hard reset.
So when restoring your ext ROM make sure you mark all CABs 'read only'.
I unlock ExtRom and put mein cab, edit config.txt.
But after HardReset mein cab didn't installiert.
I think, dieses cab need to signen.
Help me please signen mein cab or any cab theoretically.
you also need the modified autorun.exe, the config file isnt read by the default one.
dannyoneill said:
you also need the modified autorun.exe, the config file isnt read by the default one.
Click to expand...
Click to collapse
dannyoneill, wie kann man das machen? :shock:
..Sorry, how kan das make?
See this thread for more info
http://forum.xda-developers.com/viewtopic.php?t=38957&highlight=autorun
dannyoneill said:
See this thread for more info
http://forum.xda-developers.com/viewtopic.php?t=38957&highlight=autorun
Click to expand...
Click to collapse
I have renamed the file so:
my_file.cab -> Default_my_file.cab
All the same it is not installed!
There it is spoken about Wizard, i have O2 Xda Neo.
Where it is possible to take patched file Autorun.exe?
Can somebody to lay out it if it´s have?
Please, help me.
as the thread says, you cant just rename the file as it needs to be signed and designed for wm5 for it to isntall. To do your own cabs you need to have a special autorun.exe that reads a config file.
I have been using a small utility to SHOWS MY PHONE NUMBER on the today screen AND SWITCH SIMS. The utility has a 15 day trial. This software was "modded" to work in WM5. The official version only works in 2003SE. While it works OK in WM5, there are many bugs. Unfortunately, the company no longer is working on this utility, so no WM5 compatibility.
What I did was install the utility. The 15 days counts down. After 15 days it stops working. Very normal.
Because I need this utility, I want to install and reinstall it. Here is what I tried to do:
1) I installed a clean ROM. Made a registry backup using SKTools right away.
2) Installed utility
3) When 15 days is up, I uninstall
4) Tried restore original registry using SKTools
5) Reinstall utility
Unfortunately, the utility is still expired. How can this be? Normally, a program puts "keys" in the registry to indicate status. If I restore the registry to before the utility was ever installed, all traces of the utility SHOULD BE gone. What else can the utility be reading that is not unstalled? Another registry somewhere? Am I missing something?
Please help because I do use this and would buy it if it was ever made to work with WM5 by the developer. Until then I have to find a work around.
Thanks for any help.
Could the begining date from which the countdown started have been imbedded in the software at the time of the download from the website to your PC?
APK-1 said:
Could the begining date from which the countdown started have been imbedded in the software at the time of the download from the website to your PC?
Click to expand...
Click to collapse
I don't think so, because if I flash a new ROM and install the software, it goes back to 15 days trial. I don't want to reflash my ROM every 15 days. So it must be reading the original install date from somewhere other than the registry. Any ideas where?
any ideas?
which software are you talking about - SIMName?
DoctorT said:
which software are you talking about - SIMName?
Click to expand...
Click to collapse
WiVit Sim Switcher
often some software hides such data crypted in the registry, someone never find it or doesnt know hot to change...
Ricci82 said:
often some software hides such data crypted in the registry, someone never find it or doesnt know hot to change...
Click to expand...
Click to collapse
You only need to make a WinDiff comparison - or, use SKTracker. I've published a complete tutorial on this: http://forum.brighthand.com/showthread.php?t=215073
Nevertheless, it's not only the Registry that can hold such files / info, but als the file system (mostly under \Windows) and the WinCE databases.
Menneisyys said:
Nevertheless, it's not only the Registry that can hold such files / info, but als the file system (mostly under \Windows) and the WinCE databases.
Click to expand...
Click to collapse
if this is the case, there is no way to know where the info is stored then?
anubus12 said:
if this is the case, there is no way to know where the info is stored then?
Click to expand...
Click to collapse
Sure you can - just keep track of what has been changed upon installation / first start. SKTracker is an excellent tool in this respect.
Ok...I have tried several different cab file from every site...PPCGeeks, PDAphone...I have not yet found the file that will unlock and unhide the extended rom for the HTC 6800. Has anyone been able to do this yet. PLEASE HELP !!!!
You can use a RegEditor to unhide the ExtROM... but IIRC no one has unlocked the ExtrROM to edit it...
\\HKLM\System\StorageManager\Profiles\EXT_FLASHDRV\
change MountHidden=0, exit the RegEditor then Soft Reset
thank you to show us how2 do that. ;-)
I did the steps using PHM RegEdit.
Then navigate to the location:
\\HKLM\System\StorageManager\Profiles\EXT_FLASHDRV \
then change the value (default at 1) to 0.
I then did a Soft Reset -- but no joy. I don't see the drive. Thoughts?
I'm a COMPLETE newbie- but i think (from reading so far) you need to wait at least a minute for any reg changes to be committed before you soft reset.
Did you wait that minute?
michaelk said:
I'm a COMPLETE newbie- but i think (from reading so far) you need to wait at least a minute for any reg changes to be committed before you soft reset.
Did you wait that minute?
Click to expand...
Click to collapse
Hmm -- well originally I sure didn't. However, I did the hack again and then waited.
And now we have JOY!! Thanks.
What can this extended ROM offer us?
Nothing until it is unlocked and we are able to write to it. Then it will offer a few more megs of ram to install apps tr you could set up your own apps you use to start like the Sprint customizations do.