Related
Hi everyone I have started a new thread for English WWE ROM. If you are like me and own a Chinese Dopod U1000 device, and wish to use it in English, then I have authored a CAB. It is virtually 99% there (I think) I have tested it quite thoroughly, (there is an Uninstall if you wish to go back to Chinese.) The install is based on the Dopod WWE ROM (RUU_Athena_DOPODASIA_WWE_1.24.707.3_104_6275_1.32.00.10_108_Ship)
However as the ROM on the Taiwan device is newer, the CAB only enables the English language. Ok unfortunately you will need to do a hard reset first and then run through the extended ROM setup. Once the vendor automated builds have finished, run my CAB. The install will prompt for a reboot (in chinese, just select the option on the bottom left.) Once rebooted the unit should start up in English; now set your region and install all your apps. Please use this thread for Bug reports etc. Also credit goes to Dutty (And his set of Tools) and also Asukal, and also wu5262 and ahmadfarid for testing.
My congratulation.
I have a Dutch Ameo. Can I use your *.cab to get english system?
Buch070 said:
My congratulation.
I have a Dutch Ameo. Can I use your *.cab to get english system?
Click to expand...
Click to collapse
In Theory yes; however I don't have an Ameo ROM to test with. In theory you can uninstall if you are not happy with the install.
faisal.husain said:
In Theory yes; however I don't have an Ameo ROM to test with. In theory you can uninstall if you are not happy with the install.
Click to expand...
Click to collapse
OK, I will try.
Buch070 said:
OK, I will try.
Click to expand...
Click to collapse
Please keep us posted
It worked for me. If you don't like it, via hard reset you can always return to your original ROM.
I did as follows:
- hard reset
- reset again before loading the ext Dutch ROM
- installed the English Dopod U1000 WWE Language ROM CAB, copied before to a Microdrive
- reset
- got an error; " The file VCDaemon cannot be opened. .... reinstall or restore the file"
- install the WWE extROM, copied before to a Microdrive.
Checking how it works now.
faisal.husain said:
Hi everyone I have started a new thread for English WWE ROM. If you are like me and own a Chinese Dopod U1000 device, and wish to use it in English, then I have authored a CAB. It is virtually 99% there (I think) I have tested it quite thoroughly, (there is an Uninstall if you wish to go back to Chinese.) The install is based on the Dopod WWE ROM (RUU_Athena_DOPODASIA_WWE_1.24.707.3_104_6275_1.32.00.10_108_Ship)
However as the ROM on the Taiwan device is newer, the CAB only enables the English language. Ok unfortunately you will need to do a hard reset first and then run through the extended ROM setup. Once the vendor automated builds have finished, run my CAB. The install will prompt for a reboot (in chinese, just select the option on the bottom left.) Once rebooted the unit should start up in English; now set your region and install all your apps. Please use this thread for Bug reports etc. Also credit goes to Dutty (And his set of Tools) and also Asukal, and also WU3562 and ahmadfarid for testing.
Click to expand...
Click to collapse
Finally it's out btw faisal, you keep getting my name wrong, it's wu5262 not wu3562 not a big deal really, thanks for the hard work
Sorry mate will correct, I suffer from dyslexia
Buch070 said:
It worked for me. If you don't like it, via hard reset you can always return to your original ROM.
I did as follows:
- hard reset
- reset again before loading the ext Dutch ROM
- installed the English Dopod U1000 WWE Language ROM CAB, copied before to a Microdrive
- reset
- got an error; " The file VCDaemon cannot be opened. .... reinstall or restore the file"
- install the WWE extROM, copied before to a Microdrive.
Checking how it works now.
Click to expand...
Click to collapse
Ok guess is that the ameo does not ship with Cybrion Voice commander. You can fix this by navigating to Windows\startup and deleting VCDaemon shortcut....
faisal.husain said:
Ok guess is that the ameo does not ship with Cybrion Voice commander. You can fix this by navigating to Windows\startup and deleting VCDaemon shortcut....
Click to expand...
Click to collapse
Thanks, I did it. Works OK.
Failed to install TrueVGA. I have installed OzVGA, it is working.
Buch070 said:
Thanks, I did it. Works OK.
Failed to install TrueVGA. I have installed OzVGA, it is working.
Click to expand...
Click to collapse
Yes I have tried to install true vga, it is a bit flakky on my dopod with or with out the english. However what i found was after soft booting a couple of times it kinda of worked.
Also have it working with T-Mobile Ameo Dutch with the same issues reported above. I have removed the "non existent" program shortcuts and uninstalled the voice commander application because it is not translated at all to english. Will work on the registry values to correct the positions of the tray icons vrs program links. A few programs need to be renamed and then no-one would know this used to be a Dutch ROM
Thank you guys for this wonderful job.
victoradjei said:
Also have it working with T-Mobile Ameo Dutch with the same issues reported above. I have removed the "non existent" program shortcuts and uninstalled the voice commander application because it is not translated at all to english. Will work on the registry values to correct the positions of the tray icons vrs program links. A few programs need to be renamed and then no-one would know this used to be a Dutch ROM
Thank you guys for this wonderful job.
Click to expand...
Click to collapse
@victoradjei If you send me the reg vals in a txt file I will update the installer to include these.
faisal.husain said:
@victoradjei If you send me the reg vals in a txt file I will update the installer to include these.
Click to expand...
Click to collapse
Ok will do that in a few hours time. Currently out with the kids
victoradjei said:
Ok will do that in a few hours time. Currently out with the kids
Click to expand...
Click to collapse
AT your leisure, I am stuck at work at the moment, I would much rather be with my kids though!
faisal.husain said:
AT your leisure, I am stuck at work at the moment, I would much rather be with my kids though!
Click to expand...
Click to collapse
Seems that most of us is not that young already
ahmadfarid said:
Seems that most of us is not that young already
Click to expand...
Click to collapse
Maybe that is the reason why we can afford such expansive toys.
TrayApplet alignment
Buch070 said:
Maybe that is the reason why we can afford such expansive toys.
Click to expand...
Click to collapse
No comments
Now lets see to unfinished business.
On my ex-Nederlands version, the tray applets are out of alignment. This is how I fixed it. Will find time tomorrow to "unhide" some of the icons.
Go to HKLM\SOFTWARE\HTC\TrayApplet\...........
You will see the keys (folders) named 2 to 9. Re-name them by reducing the numerical values by 1, so 2 becomes 1 3 => 2, 4 => 3 etc. until 9 renamed 8.
Currently SIM Acess Manager is not responding, and the Backlight.exe control icon is hiding. That will be sorted out later in the day by mapping the correct paths.
victoradjei said:
No comments
Now lets see to unfinished business.
On my ex-Nederlands version, the tray applets are out of alignment. This is how I fixed it. Will find time tomorrow to "unhide" some of the icons.
Go to HKLM\SOFTWARE\HTC\TrayApplet\...........
You will see the keys (folders) named 2 to 9. Re-name them by reducing the numerical values by 1, so 2 becomes 1 3 => 2, 4 => 3 etc. until 9 renamed 8.
Currently SIM Acess Manager is not responding, and the Backlight.exe control icon is hiding. That will be sorted out later in the day by mapping the correct paths.
Click to expand...
Click to collapse
do you know how to hide the connection icon in system tray when sync? it waste me one row of space just for this icon....
Dopod has release a new U1000 rom. Just log on to their site and grab your copy.
This is bugging the heck out of me.
On my WM 6.1 roms this fix is implemented but i have yet to see it in the smartphones. Is there a way?
I would like to keep an install cabs directory on my wife's micro sd but i can't seem to find a way to stop it from deleting the cabs after i install them.
(I may just not be wording my searching correctly but any help would be appreciated)
Mine stay put after install. Check your registry key named nDynamicDelete @ HKLM\Software\apps\Microsoft Application Installer\
Mine has a value of 2. You can also use CabInstl instead and have the option to select where to install and when to delete or not.
h4waii said:
Mine stay put after install. Check your registry key named nDynamicDelete @ HKLM\Software\apps\Microsoft Application Installer\
Mine has a value of 2. You can also use CabInstl instead and have the option to select where to install and when to delete or not.
Click to expand...
Click to collapse
Thanks... I'll check tonight on her phone. Mine also do with WM6.1 PRO on my wizard, but hers do not with gnatgosplat's star trek wm6.1 rom.
ROCOAFZ said:
Thanks... I'll check tonight on her phone. Mine also do with WM6.1 PRO on my wizard, but hers do not with gnatgosplat's star trek wm6.1 rom.
Click to expand...
Click to collapse
Let us know how that goes but also you can change
HKCR\cabfiles\shell\Open\Command\(default) = \Windows\wceload.exe "%1"
TO
HKCR\cabfiles\shell\Open\Command\(default) = \Windows\wceload.exe "%1" /nodelete
Thanks!
JZ
ROCOAFZ said:
This is bugging the heck out of me.
On my WM 6.1 roms this fix is implemented but i have yet to see it in the smartphones. Is there a way?
I would like to keep an install cabs directory on my wife's micro sd but i can't seem to find a way to stop it from deleting the cabs after i install them.
(I may just not be wording my searching correctly but any help would be appreciated)
Click to expand...
Click to collapse
Just make your cabs "read only" and then they won't get deleted. No registry edit required.
I did a search for WOW HD in the forums and didn't see anything so I thought I'd ask. I updated the ROM last night and reinstalled the WOW HD and now it comes up as there's no driver loaded and it exits.
Anyone else having issues with this?
Try this:
http://forum.xda-developers.com/showthread.php?t=355913
didn't work on the mogul to enable SRS WOW HD, still comes up as the driver isn't loaded and exits. Yes, after soft reset.
But, thank you.
didn't work on the mogul to enable SRS WOW HD, still comes up as the driver isn't loaded and exits. Yes, after soft reset.
But, thank you.
Click to expand...
Click to collapse
Did you attempt to update the registry as it says?
i reinstalled it on 3.2.0 without a hitch...still works fine
note that there are two SRS WOW HD cabs on xdaforum
are u using it with bluetooth headphones?
SRS WOW HD still doesn't work on new official rom or test rom even with registry change. Any ideas? It also shuts off all volume (not vibrate) on the phone until it is removed. When launched it says that there is no srs driver loaded. Thanks for any help.
dunebuggydude11 said:
SRS WOW HD still doesn't work on new official rom or test rom even with registry change. Any ideas? It also shuts off all volume (not vibrate) on the phone until it is removed. When launched it says that there is no srs driver loaded. Thanks for any help.
Click to expand...
Click to collapse
works fine for me
-install .cab file
-softreset
-edit reg file so instead of what they have for "old driver" change that to wavedev.dll
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev]
"OldDriver"="wavedev.dll"
"Dll"="WOWHD_ARM_WCE_PPC2005_Driver.dll"
"IClass"="{A32942B7-920C-486b-B0E6-92A702A99B35}"
"Bass"=dword:00000000
"Treble"=dword:00000000
"AGC"=dword:00000000
"MicGain"=dword:00000027
"3DEff"=dword:00000000
"GainADC_ReceiverMIC_12h"=dword:00000037
"GainADC_HeadsetMIC_12h"=dword:0000002A
"GainADC_LoudSpkMIC_12h"=dword:00000037
"GainADC_BluetoothMIC_12h"=dword:00000021
"HPVol_PhoneCall_04h"=dword:00000004
"SPKVol_PhoneCall_02h_06h"=dword:00000003
"SPKVol_NotPhoneCall_02h_06h"=dword:00000000
"DACVol_0Ch"=dword:00000007
"Sysintr"=dword:00000019
"Priority256"=dword:0000003E
"Order"=dword:00000001
"Index"=dword:00000001
"Prefix"="WAV"
Click to expand...
Click to collapse
-import reg file
-soft reset
hmmmm
gc14 said:
Did you attempt to update the registry as it says?
Click to expand...
Click to collapse
=
peepeesea said:
-edit reg file so instead of what they have for "old driver" change that to wavedev.dll
Click to expand...
Click to collapse
?
yea if you read the thread its pretty easy to figure out. i think most people are just using the reg file that is provided with out editing it first. the "old driver" that is ref. in that reg file is not the same one on my device, so i did was change it and tuhduh!
still doesn't work. Maybe there is a difference between DCD's 3.2.0 and the Official sprint rom 3.56
The Mogul can't find ANY SRS WOW Driver for some reason. The sound works fine however if the DLL is changed back to wavedev.dll otherwise it is muted always.
dunebuggydude11 said:
still doesn't work. Maybe there is a difference between DCD's 3.2.0 and the Official sprint rom 3.56
Click to expand...
Click to collapse
yeah maybe a different driver... uninstall it, soft reset then see what the driver is that shows up under HKEY_LOCAL_MACHINE\Drivers\BuiltIn\WaveDev, then put that diver in the old driver place in the reg file
nope, still didn't work. it said wavedev.dll and i replaced that once i soft resetted it. Unfortunately it still didn't work. It must be the sprint rom
there must be some other way to make it work because it still says the driver can't be loaded. I would imagine it has something to do with the registry since it supposedly works fine on the DCD 3.2.0 Rom.
If Possible, can someone try to figure out or give any ideas on what would be causing the problem. Thanks. I REALLY want to be able to use SRS WOW HD because it makes the music sound 1000 times better! Thanks.
I'd really like to get this working on my touch again, will try the reg edit
eXplicit815 said:
Try this:
http://forum.xda-developers.com/showthread.php?t=355913
Click to expand...
Click to collapse
read everything in that link, thats all i needed to know and it works for me
yeah, i just switched over to dcds 3.2.0 rom and now it works fine. It has to be something in the "Official" Sprint 3.56 ROM that is causing the problem
SRS WOW
Yea..I am running the newest Sprint ROM (leaked release) and have tried every different version. With it installed I get no sound at all or the file error message.
Hope someone much better at problem solving than me gets a minute to take a peek at it.
The sound is horrible without it.
For my Samsung Omnia SGH-i900
HI guy,
Should I do the same for my Samsung SGH-i900 WM6.1. After I load SRS WOWHD i had the same error, and I did try the steps to install SRS than soft reset than run the Wavedev.reg zip file but still no sound. May be is bcos I don't know hoe to do Reg edit, can someone teach me step by step in the wavedev.dll reg edit part? thank you all.
Just install the Radio Refurbish.cab.. it should be left in your extended rom from the old vzw rom..
look here.. posted by NexVision..
http://forum.ppcgeeks.com/showpost.php?p=282968&postcount=33
thats why i figured to do before doing all this reflash old roms, etc.. thanx
anyone tried this?
Has anyone here tested this?
madsuse said:
Has anyone here tested this?
Click to expand...
Click to collapse
its not new. its been done in the past to fix VZ users who let Sprint customizations run. I think the trick is properly sending the /Refurbish parameter. I once made a cab with a shortcut to launch the .exe with that parameter, but it seemed to only work for about 50% of people who tested it.
still have cab?
dcd1182 said:
its not new. its been done in the past to fix VZ users who let Sprint customizations run. I think the trick is properly sending the /Refurbish parameter. I once made a cab with a shortcut to launch the .exe with that parameter, but it seemed to only work for about 50% of people who tested it.
Click to expand...
Click to collapse
Is it possible you still have the cab, I loaded Vista and haven't gotten all of my tools working yet.
madsuse said:
Is it possible you still have the cab, I loaded Vista and haven't gotten all of my tools working yet.
Click to expand...
Click to collapse
This is the verizon one.
Thanks
I am a little rusty with cabarc.
Guys, if you read the thread on ppcgeeks, you'll see I've already posted there that I've TRIED radiorefurbish WITH the proper /Refurbish parameter and it does not work.
gc14 said:
Guys, if you read the thread on ppcgeeks, you'll see I've already posted there that I've TRIED radiorefurbish WITH the proper /Refurbish parameter and it does not work.
Click to expand...
Click to collapse
Are you 200% sure that whatever you are using to execute the command is correctly sending the parameter? this is all the verizon customizations do. config.txt should say "EXEC: /Windows/RadioRefurbish.exe /Refurbish"
I know I spoke with NexxVision in the past and he had no problems using it outside of verizon customize. I think I also remember reading that /Refurbish is case sensitive.
I got nowhere with /Refurbish... but when I did /refurbish... that worked.
Are you 200% sure that whatever you are using to execute the command is correctly sending the parameter? this is all the verizon customizations do. config.txt should say "EXEC: /Windows/RadioRefurbish.exe /Refurbish"
I know I spoke with NexxVision in the past and he had no problems using it outside of verizon customize. I think I also remember reading that /Refurbish is case sensitive.
Click to expand...
Click to collapse
Yes I'm 200% sure. I've made my own shortcut link with the parameter included as well as tried with Resco Explorer 2008. Both /Refurbish and /refurbish did not work. Nitro, it must have been a fluke, I don't know what to tell you.
gc14 said:
Yes I'm 200% sure. I've made my own shortcut link with the parameter included as well as tried with Resco Explorer 2008. Both /Refurbish and /refurbish did not work. Nitro, it must have been a fluke, I don't know what to tell you.
Click to expand...
Click to collapse
it works on the Stock original verizon rom. I couldn't get it to work on the latest and greatest. I believe it's WM6 specific. Not 6.1
it works on the Stock original verizon rom. I couldn't get it to work on the latest and greatest. I believe it's WM6 specific. Not 6.1
Click to expand...
Click to collapse
LOL...it really doesn't matter if it works on the stock rom. If you have the stock rom flashed, it already ran as part of customizations. The entire point behind the thread on ppcgeeks was rolling back the PRI without having to flash back to stock, which as I've stated, is not possible.
gc14 said:
LOL...it really doesn't matter if it works on the stock rom. If you have the stock rom flashed, it already ran as part of customizations. The entire point behind the thread on ppcgeeks was rolling back the PRI without having to flash back to stock, which as I've stated, is not possible.
Click to expand...
Click to collapse
I agree... But i've screwed up the phone so many times... I ran it anyway. lol
gc14 said:
LOL...it really doesn't matter if it works on the stock rom. If you have the stock rom flashed, it already ran as part of customizations. The entire point behind the thread on ppcgeeks was rolling back the PRI without having to flash back to stock, which as I've stated, is not possible.
Click to expand...
Click to collapse
its absolutely not impossible. there is no ability that the stock rom gives you that any other rom doesnt. it is simply executed by autorun. other people have been able to run radiorefurbish.exe within custom roms. talk to nexxvision. its an issue of correctly passing the parameter, the exe seems to be touchy.
i've personally rolled my PRI back using radiorefurbish in the past when i was messing with it before. i've never had the verizon stock ROM on my device.
i am sure that if the exe is run with the parameter by autorun (config.txt has to be modified) then it will have the same effect in any rom. if anyone wants to test, it would be a quick change to the UC package.
dcd1182 said:
its absolutely not impossible. there is no ability that the stock rom gives you that any other rom doesnt. it is simply executed by autorun. other people have been able to run radiorefurbish.exe within custom roms. talk to nexxvision. its an issue of correctly passing the parameter, the exe seems to be touchy.
i've personally rolled my PRI back using radiorefurbish in the past when i was messing with it before. i've never had the verizon stock ROM on my device.
i am sure that if the exe is run with the parameter by autorun (config.txt has to be modified) then it will have the same effect in any rom. if anyone wants to test, it would be a quick change to the UC package.
Click to expand...
Click to collapse
Only if I actually felt like pulling my XV6800 out. I really want to wipe the PRI off this Sprint Mogal and get it to the Verizon one. This roaming is annoying. LOL
its absolutely not impossible. there is no ability that the stock rom gives you that any other rom doesnt. it is simply executed by autorun. other people have been able to run radiorefurbish.exe within custom roms. talk to nexxvision. its an issue of correctly passing the parameter, the exe seems to be touchy.
i've personally rolled my PRI back using radiorefurbish in the past when i was messing with it before. i've never had the verizon stock ROM on my device.
i am sure that if the exe is run with the parameter by autorun (config.txt has to be modified) then it will have the same effect in any rom. if anyone wants to test, it would be a quick change to the UC package.
Click to expand...
Click to collapse
I'm not doubting that it's never worked before...because I too have had it work a while ago when I had to roll back from the Sprint PRI. Since then, I've tried to use it on several different occasions on several different roms not changing my method that worked the first time whatsoever, and it does nothing. That's all I'm saying. If you can somehow get it to work, more power to you.
i'll give it a try
dcd1182 said:
its absolutely not impossible. there is no ability that the stock rom gives you that any other rom doesnt. it is simply executed by autorun. other people have been able to run radiorefurbish.exe within custom roms. talk to nexxvision. its an issue of correctly passing the parameter, the exe seems to be touchy.
i've personally rolled my PRI back using radiorefurbish in the past when i was messing with it before. i've never had the verizon stock ROM on my device.
i am sure that if the exe is run with the parameter by autorun (config.txt has to be modified) then it will have the same effect in any rom. if anyone wants to test, it would be a quick change to the UC package.
Click to expand...
Click to collapse
I flashed the new verizon rom and had the customizations run before I knew it was a bad thing. I am on the new verizon radio and dcd 3.2.6.
Just need some prompting on how to run it. I usually flash via sd with uc via sdconfig.
madsuse said:
I flashed the new verizon rom and had the customizations run before I knew it was a bad thing. I am on the new verizon radio and dcd 3.2.6.
Just need some prompting on how to run it. I usually flash via sd with uc via sdconfig.
Click to expand...
Click to collapse
if you just want to try... copy the radiorefurbish.exe to the /Windows directory. Then in Resco explorer... highlight the file... then go to Run... type /refurbish in the paramaters part. If that does nothing... try /Refurbish
Resco Explorer
nitro66215 said:
if you just want to try... copy the radiorefurbish.exe to the /Windows directory. Then in Resco explorer... highlight the file... then go to Run... type /refurbish in the paramaters part. If that does nothing... try /Refurbish
Click to expand...
Click to collapse
Guess I need to fine cab for Resco Explorer.
Found it.
Installing now.
ok....
here's the deal:
I've been using an OEM-package in mylast roms for tomtom version 7.915.
This has been working without troubles.
Now I cooked a new ROM based on new 21018 XIP/SYS
The device really flies and everything seems to working flawless....EXCEPT tomtom.
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
I did not change anything to the OEM-package. So I guess it has something to do with the new SYS.
Do more people have this problem and/or does somebody now the fix....
Thnx all in advance for your help!!
Greetz Merten
p.s. I used the search function of course and saw a lot of similar errors but no sollutions.....
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
crazyC said:
I am running TomTom 7.915.9196 (OK via a cab) on 21028.1.6.0 (just installed yesterday)
This is Da_G's simple kitchen plus the updated pack posted in that thread this morning.
Don't know if that helps, but I would be very interested in an OEM for TOMTOM if you can get it working?
Click to expand...
Click to collapse
I got the exact same oem-package working in M-rom v1.71!
So it really beats me why I get the error.
I tried cooking the rom again but still the error....
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
crazyC said:
I am still cooking up my rom and so will reflash tonight - if you can post up your tomtom OEM I will take a look and try and flash it and see if I can get it to work? Maybe a conflict somewhere that might not be on mine as I do chaneg a number of the packages.
Click to expand...
Click to collapse
Ok OEM can be found here in the map: packages
Package looks OK at first glance - hope to be able to try it tonight and will post back tomorrow with results.
If this doesn't work - you could try simply using the cab via UC etc as I do - I have checked and the cab of the same version in your OEM DOES work for me.
In fact, I think I might leave it in my UC, (but will flash tonight anyway with it just to see)
merten3000 said:
When I start Tomtom, in a flash I see the gray bootscreen but then immediately I get the error: 'Unable to start. Not enough memory is available.'
But I have more then 130mb program memory available so that can not be the issue....
Click to expand...
Click to collapse
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
GenghisZ said:
I had the same problem some time ago, and it turned out to be SKtools automated Free-Ram shadow service that was causing this.
You dont happen to have similar software running (something that clears your RAM on the fly)?
Click to expand...
Click to collapse
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
merten3000 said:
I tried new ervius packagetool: 5.3 and saw something about shadow service... will roll back to 4.3b1 and see if tool is the problem...
Thnx for the tip!
Click to expand...
Click to collapse
Nope, did not help...
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
crazyC said:
OK - apart from the shortcut not being copied to programs - I didn't check the initflashfiles first - d'oh - it works.
I went to windows with file explorer and ran it from there - no problems.
Have flashed twice - it must be something else in your rom.
Does the page pool make any difference? or the filecache sizes?
Click to expand...
Click to collapse
I always change my roms pp to 32mb...can that make a difference? I did it in v1.71 and tomtom worked fine...
I don't know - I have been around here long enough to know that your skills far outweigh mine. If it used to work then I see no reason for the change.
All I know is that my rom is based on Da_Gs really clean latest (ie 5.08) from his simple kitchen thread (from his post near the end not the first post) plus Eras2rs package updates.
The only other packages I add are a few utilities and personal tweaks. I import an advanced config xml as part of the UC process but that just ensures the various settings in Advanced Config are set to advised etc.
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Harikoss said:
Hi,
I don't know if this can help but I got this same error message when the map isn't correctly activated.
Regards,
___________
TP - RomeOS 1.70
Click to expand...
Click to collapse
Maps work(ed) fine..
btw I bypassed the error by removing the OEM-package and made it a cab which is installed during system configuration. It takes more system space but this way it is uninstallable....but it remains a mistery to me why the OEM does not work in this SYS and does in 21014 SYS...