Develop Bugs

Deleting files from an unlocked ExtROM

My most new annoying experience...
Everytime I delete some files from ExtROM that I don't want to install in the event of an hardreset, they reappear again after a softreseting the device. :twisted:
Even powering the device down, and waitting more than 10secs, as several times suggested in this forum.
Maybe a silly question, but any ideas to overcome this?

Don't tell me the only way is to coock a new .nbf Extended ROM!?
It is? :?

have you try formatting the extended storage? i used resco file explorer to format it after unlock the extended rom storage.

No I didn't format, as I wanted to delete just some files.
Should I Format?
And then?
- reflash the ExtROM .nbf, and delete unwanted files?
or
- just copy the ones I want to keep?

Also realized that extra files copied into, disappear after softreset :evil:
This thing seems to have own life...
Nothing of these behaviours were happening with previous ExtROM form Qtek (1.13.151 WWE).
Is it a different philosophy between Qtek and i-mate, for ExtROM?
Why these different behaviours?

Conchas said:
No I didn't format, as I wanted to delete just some files.
Should I Format?
And then?
- reflash the ExtROM .nbf, and delete unwanted files?
or
- just copy the ones I want to keep?
Click to expand...
Click to collapse
well... i have no experience in reflashing the ExtROM.nbf, so i prefer the second option, it worked on me , sorry can't much help

see my comments on the following thread..maybe that will help..
http://forum.xda-developers.com/viewtopic.php?p=240962#240962

eagle 1 said:
see my comments on the following thread..maybe that will help..
http://forum.xda-developers.com/viewtopic.php?p=240962#240962
Click to expand...
Click to collapse
Thanks for the hint. It worked!
Finally I think that I got the complete picture.
All difficulties to unlock Ext ROM on this new i-mate ROM, and a comment at another thread, made me think that once unlocked, it wouldn't be needed to repeat it again after further Hardresets. Changing the Reg settings accordingly, would be enough (WRONG!).
Silly conclusion... in fact Ext ROM was visible, but still protected.
The mommentary ability to delete and add files, leaded o a false confirmation that every thing was ok.
Now I can delete and add files to Ext ROM without problems!
Thanks all, the moved me to the rigth track.

Well after a hard reset this time I did not run the un-locker cab again, just changed the registry values. I have deleted a number of cabs, and installed two programs to the space freed by deleting the cabs. I've turned my device off for a couple of hours, and did a soft reset. So far this time my ExtROM is still there, as are my programs.
Granted this is not what I expected to occur.

dah54 said:
Well after a hard reset this time I did not run the un-locker cab again, just changed the registry values. I have deleted a number of cabs, and installed two programs to the space freed by deleting the cabs. I've turned my device off for a couple of hours, and did a soft reset. So far this time my ExtROM is still there, as are my programs.
Granted this is not what I expected to occur.
Click to expand...
Click to collapse
Realy strange...
That were also these comments which caused my confusion before. Now I don't know what to think anymore :?
But will follow only the procedure that works for me.
Unlocking ExtROM on this ROM, turnned to be a really tricky procedure.
For me it only works if I enter the Reg settings manually...
Any attempt to insert them with a Cab file turns into failure to unlock ExtROM. Independent if I run the unlock tool before or after, followed by a softreset :evil:

You have to edit the "Config" file.

Universal Custom ExtROM Issues

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

"Not Enough Memory" troubleshooting thread

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

what causes reboots

just woundering i read lots about reboots and loops here what can cause that
the phone it self or the applications it has?

The SD card inside maybe ?

neggie said:
just woundering i read lots about reboots and loops here what can cause that
the phone it self or the applications it has?
Click to expand...
Click to collapse
or if you have fav 5 on your plan but dont have it on your phone homepage. remove the short cut to fav5 in \windows\startup

A Faulty memory card driver is the culprit of my reboot looping woes.

In the WM6 ROMS (at least the early ones that were causing horrible problems), it was caused by Windows Live Messenger. Basically, when you activate it, it causes notifications to be added to the notification queue. Those build up and eventually cause a reboot loop. If you use SKTools to clear the duplicates from the Notification Queue every 4-5 reboots, it should be fine.
Or you can remove the Windows Live Messenger service manually from the registry, which will disable it and fix the issue, but that's risky if you don't know what you're doing.

I would suggest to re-install and reflash the rom.

ok will try to reisntall wm6 531.4 from tmos site. Also i do have my faves and this usally happens with the default tmobileblue.xml homescreen

I tried all of the fix actions above and the only thing that I could do to stop the looping reboot was to change the name of the dll the card looked for thus disabling access to the card. I even dumped the WM6 ROM for the wing and the T-Mobile WM5 ROM and transferred the dlls over to my device and changed the registry entry to reference the new files. Nothing worked. The card didn't recognize the WM5 or Wing WM6 dll files.

neggie said:
ok will try to reisntall wm6 531.4 from tmos site. Also i do have my faves and this usally happens with the default tmobileblue.xml homescreen
Click to expand...
Click to collapse
Search for the t-mo 531.6 rom. They supposedly fixed a few things.

i found that rom 531.6 but its in a .rar file and the file is a .nbh or somthing how do i convert that any steps >>??

[Q] Updating persistent data before hardreset

I'm currently developing a program that basically receives updates and performs them on mobile devices. These are running Windows Mobile 2003.
The update simply consists in a number of files/directories deletes, creates, attributes changes and overwrites (when modified). It's not clever or optimised in any way. But there is a problem.
If the program finds some files need to be modified, the program performs the modification and then immediately makes a kernel call to hard reset the device, so as to reload the OS which is set to read the persistent directories for further booting instructions (which was just changed).
It appears a small number of devices went through such an update but the old data is still being loaded into the registry for instance. There is no trace of where this could come from and I can guarantee it is not burnt into the OS's ROM. I suspect FAT12 or FAT16 corruption of its tables or perhaps its "Root Level Directory" section... reason is probably that the program makes the hardreset too quickly for all buffers to flush in time. Being a hardreset and not a soft one, I assume the buffers are destroyed and never written on disk, thus some changes are lost and some may have been done partially. This problem leaves what I call ghost files around. These files cannot be found anywhere, but somehow are read by the program in OS ROM that is set to find them in the root level dirs of the persistent partitions.
I've been researching like crazy to find a way to make a good call to FlushFileBuffers() to flush everything (data and metadata) before doing the hardreset. But I haven't found any good documentation that works for win32 ce 3.0. I've had to implement all kinds of silly workaround that are making the whole process take much longer than needed...
I'd like your input on how I could make sure everything is flushed properly on these WM2003 devices before I issue the call to hard reset.
Thanks,
Simon