Hey,
somehow the Ramdisk is mounted on my TyTn (on the latest Custel Rom).
So i can access is like a normal SD-Card. The problem is TomTom can't find it's Maps anymore. I'v read that this can happen when more than 1 or 1+virtual SD-Cards are installed.
I don't no know whicht programm mounted the disk. I didn't unlock the extrem or something like that. Softreset doesn't help, it starts up with the Ramdisk accessable from fileexplorer.
Any Hints?
yuo have unlocked the extended Rom on your device.
Hide it again using whatever software you used to unhide it....
AFAIK Custel was cooking HTCustom in his rom. Start it and uncheck "show extrom". Then you have to softreset and you problem should be solved.
I found a shortcut in the List of installed Programms. It's german for "unmount Ramdisk" and that works.
The strange thing is that i've never unlocked my Extrom. And the fact that the Shortcut is german tells me that some other program must have done it.
This is really strange. Which programs did you install?
What exactly is written in German - "entferne Ramdisk"?
I'm not aware of any program that calls the extrom ramdisk.
Related
Hi. Are there actually any ported ROMs for the Uni that allows a super-clean (i.e. purely Microsoft) WM5? Thanks.
This is exactly what i am here at the Forum for please someone step up?
Cause i foudn one in general by name one time but im not sure if they are shapped for the Universal
I guess to clarify ...
A Clean version of WM5 shapped for the Uni if possible
I want to amke sure i do not lose any features
Please help thanks
rightnow im on the newest qtek but is actign weird so im going back to my orignal imate
don't install the extended ROM...
Can you explain SIMPLY which file is the extended ROM?
philby said:
Can you explain SIMPLY which file is the extended ROM?
Click to expand...
Click to collapse
What "ady" meant was:
1st: Install Buzz's Ext ROM Unlocker and unlock your Ext ROM.
2nd: Cut and paste them to your SD Card and save a copy on your computer for backup.
3rd: Perform a hard reset. Since you already took off the Ext ROM, you now have a pure Microsoft OS running on your device.
To answer your question, the Ext ROM is what you see being installed when you perform a hard reset. It is indicated by a progress bar during installation after a hard reset. The Ext ROM contains the customizations provided by the "Brand" name of your device.
The simpliest way to avoid the installation of the Ext ROM, if you don't want to unlock it is:
1st: Perform a hard reset.
2nd: "IMMEDIATELY" perform a soft reset by pressing the reset pin as soon as you see the "Microsoft Today Screen". By doing this, the installation of the Ext ROM is by-passed.
If you are going to ask me where to find the Unlocker. Just do a search. Hope this cleared it up.
Thanks for the excellent reply. Can you tell me what exactly would be excluded by not installing the Extended ROM contents? I am guessing this would be like selecting a corporate install on the O2 XDA EXEC?? Thanks again for any reply.
philby said:
Can you tell me what exactly would be excluded by not installing the Extended ROM contents?
Click to expand...
Click to collapse
Any customisations your operator has made. It's hard to say what exactly as that changes per ExtROM (and each new version of Windows Mobile by each operator has a new ExtROM so...)
If you don't install the ExtRom you have plain Windows Mobile, if you install the Extended ROM (which it will be default) it adds patches, customisations (backgrounds, sounds, GPRS settings etc), button configurations, home page settings, add icons, remove icons, custom programs etc.
My advise is to read the wiki (link in top left) open up your ExtendedROM as the poster above advised and then customise it how you want, or just by pass it completely each time and add in what you want manually.
philby said:
Thanks for the excellent reply. Can you tell me what exactly would be excluded by not installing the Extended ROM contents? I am guessing this would be like selecting a corporate install on the O2 XDA EXEC?? Thanks again for any reply.
Click to expand...
Click to collapse
xanth is absolutely right. The Ext ROM changes with each "Brand". I am attacching a link for the O2 Ext ROM explanation: http://forum.xda-developers.com/viewtopic.php?t=32527
Some applications in the Ext ROM, you can deduce what it is made for like "default_Backgamon etc...(which installs the game backgamon in Imate Ext ROM) and some are similar to O2's, so let it be your guide.
why
you don't want a "clean version" it would not contain any drivers, camera software or bluetooth software that make life easy. your jasjar is not clean by bypassing the ext-rom. to prove this look at your programs the zip program and voicedial do not come with a clean wm5 image.
Re: why
sandrobber said:
you don't want a "clean version" it would not contain any drivers, camera software or bluetooth software that make life easy. your jasjar is not clean by bypassing the ext-rom. to prove this look at your programs the zip program and voicedial do not come with a clean wm5 image.
Click to expand...
Click to collapse
Actually ALL WORKS FINE with a clean install, as mentioned above, the only thing you might have to add is the settings for MMS, and video call capabilities. But ALL SOFTWARES INSTALLED WORKS. From BT to WiFi, camera app, voice dial, etc... I know because I already tried it.
Re: why
sandrobber said:
you don't want a "clean version" it would not contain any drivers, camera software or bluetooth software that make life easy. your jasjar is not clean by bypassing the ext-rom. to prove this look at your programs the zip program and voicedial do not come with a clean wm5 image.
Click to expand...
Click to collapse
Well that depends on the base Windows Mobile ROM. Some will have some features, while some won't (won't fit possibly?) and would require the ExtROM to install them.
I appreciate this is a Universal thread, but one example is the BlueAngel. The SX66 doesn't come with a camera so it's ROM doesn't contain camera software and if you used that on a regular BlueAngel (XDA IIs for example) you'd need to install the camera software seperately.
Hope this actually makes sense.
what about a real clean ROM...
i mean a ROM that does not contain any of those "dog barking" junks media files and themes (there is around 8MB of these), as well as unnecessary EXTROM files. YET sparing drivers for camera, bluetooth , and other crucial drivers.
thanx
go it
then you are correct to hard reset then soft reset before your device wants to load the ext-rom
unnecessary media files are not in the ext rom
they come with the winows folder and the my doc. they r more than 8mb , and they serving for NOTHING... so stopping the erom wont save you from them
Hi everyone,
I made [a while back now] an ExtROM for the Alipine device. I am trying to convert this to the XDA Exec [Universal] device and have got as far as getting my custom software onto the rom and flashed to the device, it appears to run the Autorun.exe, read my config.txt and actually looks like it is installing. Problem is, nothing actually gets installed!!!
I am very confused right now
If I run the updates manually, they work but prompt me for an install location [memory card or device], could this be why nothing is happening?!? Is there something extra i need to do to the cab files maybe?
Any help would be appreciated
Do you also get the prompt about un-signed programs when installing manually?
Sadley no i do not, and the really really odd thing that i should of mentioned is that we wrote 2 .exe files that basicly cull parts of the registry and certain files which work as standalone apps and in the XDAIIi ExtROM but as a part of the Universals ExtROM does nothing...it really does look like i am missing something here, but what
I did have the same sort of problem in the ExtROM I just completed.
Only I am using my ExtROM as space for installs so dont know how to resolve problem
I unhid the ext_rom using:
[HKLM\System\StorageManager\AutoLoad\TRUEFFS_DOC1]
Bootphase=dword:2
[HKLM\System\StorageManager\Profiles\TRUEFFS_DOC1]
MountHidden=dword:0
At first I saw ext_rom folder with a few files on it ... I tried to copy them to my micro sd card but recieved an error message saying they are write protected... I tried copying those files again to my computer but my artemis hanged... now I soft reset... i can still see the ext_folder with the files on it... then i soft reset again after that, no more files in the ext_rom folder... I decided to do a hard reset but after that Tomtom did not install...
I know I did not unlock the ext_rom prior to unhiding it...
I managed to unhide ext_rom folder again and clicked on properties.. it shows Total space=14.91Mb, Used=6.24Mb, Free=8.67Mb... I still dont see the files in it...
I guess its still there and it just doesnt auto install after hard reset... how do I activate it again???
Pleas help!
Prior to the program disapearing did you update the TomTom software to vesion 6,030 - Since doing this my Artemis refuses to auto install from the ROM following a hard reset, to install I either locate the Autorun file on the memory card, or connect up via the TomTom Home application which should find the device and offer the update/ installation - Mike
mikealder said:
Prior to the program disapearing did you update the TomTom software to vesion 6,030 - Since doing this my Artemis refuses to auto install from the ROM following a hard reset, to install I either locate the Autorun file on the memory card, or connect up via the TomTom Home application which should find the device and offer the update/ installation - Mike
Click to expand...
Click to collapse
Yes I did... the original installation was 6.020... so i updated to 6.030... have you tried Unhiding your ext_rom?
What else is in the ext_rom anyway? is there any important file in there?
No I have not messed around with the external ROM (yet) - as you have TT 6,030 is there a file on your memory card to install the application? - if not simply fire up TomTom Home on the PC with the Artemis connected and it will install what you need - Mike
mikealder said:
No I have not messed around with the external ROM (yet) - as you have TT 6,030 is there a file on your memory card to install the application? - if not simply fire up TomTom Home on the PC with the Artemis connected and it will install what you need - Mike
Click to expand...
Click to collapse
NO I have deleted everything from the mem card...
Yes I did use tt home to reinstall tt navigator back to my Artemis...
So far my artemis works perfect... but still Im not happy with the ext_rom not showing the files...
Does anyone know how to re-enable the ext_rom to install after hard reset???
So, some of you have this error, some dont. So lets try and figure it out. Heres what we know.
The problem affects ALL Artemis WM6 ROMS.
Remember, the issue doesnt appear when just using it normally. Its only under certain circumstances. Heres how you re-create the problem.
Run Tomtom, this causes the error90% of the time.
Create a new word document and try to save anywhere.
Heres my setup and what ive tried to fix it.
Device: MDA Compact III
SD Card: 1gb
Ive tried font cache size, system cache, removing the memory card.
Please dont post "I dont get the error" if you havnt tried running tomtom or saving a word document.
Thanks
To add to the problem re-creation, I was trying to copy a directory with around 15 files in it from the internal memory to the storage card, the message just kept popping up for all the duration of the copy process, I stoppped clicking ok eventually. I looked at the free program mempry available then and it was pretty good at around 22mb.
Device: Orbit XDA
SD Card: 1gb
I too have noticed that looking at the free storage space seems to fix it for tomtom (but not word). There is something else wrong with Excel in that the "Save As" is in the wrong place, infact where it is isnt actually save as.
You're right, I haven't noticed this before with excel. I can't remember if it was like this before, was it? It won't be easy figuring this little memory issue out. I hope someone has a trick up their sleeves.
I have the WM6 emulator running on my pc and the excel thing isnt there. Comparing the registry settings on the emulator with my device. I would love to hear if anyone does actually have Word working without issue.
BREAKTHROUGH!
OK. I installed the original Orbit rom and... IT WORKS!!!! So the question is what did bepe and the guys do when they de-branded it? The orbit rom has an Ext-Rom with a load of branded stuff PLUS! some patches. I bet one of these patches fixes the issue!
These custom roms have NO Ext-Rom at all, hence the increased storage space. however in the process of removing the ext rom they have managed to cause these memory errors.
So guys, any chance of a rom close to the Orbit rom but with the English language and Ext rom left in tack?
Great work mate, it is the removal/merging of the extended rom that's causing the problem then. Maybe it's not even a patch in the extended rom, maybe it's the way the extended rom was merged that's causing it. This surely deserves more looking into.
Great breakthrough
Word FIX!
Thanks to pvdhelm for the tip on this one. Attached is a patch to fix the memory issue with word (and only word). To fix it for other apps you need to view the memory in the control panel and click on "Storage Card". The word fix is pernament but the other memory issue it only until you reset your phone.
Absolutely brilliant, so it looks like missing registry entries!! We need to find out what was in the original extended rom then to find out if we're missing anything else. Looks like only me and you here, you should post this fix in the main threads mate.
Cheers and well done.
I have a copy of the rom, tried isntalling it all but to no avail. It looks like on boot up the system thinks it has a different ammount of ram due to the ext rom being merged. By displaying the ammount of storage it realises it has a different ammount and fixes it. Until the next reboot. So if anyone knows what changes when you view the storage that may be fixing it I would love to know.
Or if somone can make a rom with the ext rom still in place.
EDIT: Heres one just for the MDA Compact III without WiFi users. It applys the Word memory errror fix but also fixes the Comm Manager issue and does so just for the MDA as it removes WiFi from the list.
Maybe this is a clue for you all. I have never had these errors, ands I use Tomtom daily and have tested word for you again with no fault.
The difference? Well I upgraded to WM6.0 the original way before USPL patch and flashed the OS only. I'm assuming you with problems used the ROM installer method. Am I right with my assumption? If so that should narrow down the culprit.
I used Bepes original WM6 WWE OS only upgrade, therefore the Ext ROM on my device is still the old T-Mobile WM5 one and was simply not allowed to run. So it can't be right to assume there is something missing from an EXT ROM patch.
It's most certainly the extended rom being merged then, there's nothing else to it.
gajet, can you give me the exact steps you took. I went from the T-Mobile rom to Black and blue then to the others. I uses USPL first though.
Can you give me a quick set of steps you took i.e Original T-Mobile rom, then ran USPL, then updated to Bepes.
Also, if you used bepe's can you also tell me which rom update util you used? as the one ive tried has errors at the end.
Thanks
dannyoneill said:
I have a copy of the rom, tried isntalling it all but to no avail. It looks like on boot up the system thinks it has a different ammount of ram due to the ext rom being merged. By displaying the ammount of storage it realises it has a different ammount and fixes it. Until the next reboot. So if anyone knows what changes when you view the storage that may be fixing it I would love to know.
Or if somone can make a rom with the ext rom still in place.
EDIT: Heres one just for the MDA Compact III without WiFi users. It applys the Word memory errror fix but also fixes the Comm Manager issue and does so just for the MDA as it removes WiFi from the list.
Click to expand...
Click to collapse
VERY interesting reading!
If you move this thread, please drop a link on here for us, thanks. The first one to crack this problem will be worshipped from afar I am sure!!
I think it could be an order of upgrade issue, heres the latest.
1. Downgraded to T-Mobile WM5 rom
2. Ran USPL
3. Upgraded to Bepe WM6 using the EXE version
The word issue is no longer there but the out of memory in Tomtom is. Also no ext rom.
It would be good to know from others and gajet what steps they took and which files they uses to do it. Especially as gajet still has his extended rom.
I've tried:
official t-mobile wm5 to german wm6 to bepe uspl &
official t-mobile wm5 to bepe uspl
Both times I have had the error with tomtom but no problems with word.
Both times temp fix (looking at storage) worked (sorry about font cache red herring - thought I was onto something there).
Just tied chi-tai extended battery plugin with the storage showing on the homepage (as a way to force system to get correct memory) but no joy.
I have htc touch com manager and phone skin but not the home plugin.
Cheers
Matt
I think Ive cracked it. Just doing some final testing but watch out for a new "How to" thread.
go Danny go.
Look forward to seeing it.
Will test and report back once you've posted.
Cheers
Matt
Sadly the original thread was edited to reflect the OS update was repackaged but eddie2k still goes on the reexplain the process in this thread.
eddie2k said:
then use winrar to unpack the (bepe) wm6 wwe rom in this page (written in red). flashed using bootloader method.
after u get german rom installed , run ARTE os flash utility from xda ftp (log in properly) link don't work if not logon properly..
ftp://ftp.xda-developers.com/Uploads/Artemis/arte.zip unpack
copy os.nb from first folder (bepe) wwe rom to arte folder and rename os.nb to windows.nb then run UpgradeRom.bat
hard reset, soft reset done.
Click to expand...
Click to collapse
Now I didn't bother installing the german O2 release as my MDACIII was CID locked, so I just used ARTE package with Bepes WM6 .nb renamed and flashed the OS only, then after hard resetting, at the point of about to load EXT ROM soft reset.
This thread was also the guide although you could skip the process of extracting the .os from a ROM package as Bepe originally provided us with the raw windows.nb file.
Thanks gajet, Ive just posted the steps. Your post was deffinatly the key. Once I saw you still had your ext rom I knew we could do it.
Answer is here
http://forum.xda-developers.com/showthread.php?t=313486
Hi,
Could anybody provide help for me? My P3300 doesn't seem to be able to install any programs / games anymore?!? What to do, has anybody had the same experience?
Once I install a program from my desktop PC to the P3300 or when I copy the CAB-file straight to the P3300, I get the standard installation screen: "choose a location.....Device, Storage Card or Bluetooth...blablabla"
But when I tap either one, let's say Storage Card, the thing is loading and a 2 seconds later I get the same screen, but with the message: "pocketxpdf.sf.net pocketxpdf cannot be installed. To try installing again to a different location, choose a location: Device, Storagecard or Bluetooth."
How is this possible all of a sudden? Never had problems...there is enough storage space, I've never updated the ROM, just a soft-reset doesn't work either. I don't want to do a hard-reset yet until I know a way to export my Contacts so I don't have to bring them in manually again after a possible hard-reset. (since i cannot install the program EasyHelper anymore...)
Anyone have any clue, what could be wrong?
My Specs:
HTC P3300 UK
Original ROM version
WM5
Installed programs:
Windows Vista Skin
Battery Status
Pocket Mechanic
SBSH Clock
Resco Explorer
PSshutXP
Pocket Painter
Wisbar Advantage 2
TomTom WE full
Games:
Battleship
Chess
Worms
Many thanks if you could help me out!
Greetz
Pallemans
Had you checked the Artemis Wiki pages you could have found a possible answer. There has been an official patch released by HTC for SD cards getting corrupted. http://wiki.xda-developers.com/index.php?pagename=Artemis_Problems
FIXED!
Sorry mate, but my problem had nothing to do with SD-Card bugs.
I already fixed my problem, see:
http://forum.xda-developers.com/showthread.php?t=339063
But thanks for your reply.
Greetz