Related
I changed from DogGuy to this new DCD kitchen and do really like it, but I have come across a couple of strange things. I was wondering if anyone else is having the same issues, and has figured them out. I can no longer skip the welcome screen and calibration with this new kitchen. I even tried to recreate the script with the newest oemizer, and still no luck. I am using a real high GUID (ffffffff-f493-424e-b7f1-cab5da57bd61) so it should be one of the last updates to the registry. But it still does not work. It did work with the DogGuy kitchen and the 6.1 rom from No2Chem. Has anyone made this work? Here is the code form my oem:
;<<<<<----- First Boot Settings ----->>>>>
;Skip Welcome Screen
;================================================= ============
[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
"Disable"=dword:FFFFFFFF
;Stylus Calibration
;================================================= ============
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="2018,1980 3383,3022 3387,972 649,950 667,3021"
[HKEY_LOCAL_MACHINE\ControlPanel\Stylus]
"Group"=dword:00000001
;--------------------------------------------
Also, I have not been able to successfully change the today screen through an oem either.
;Today Theme
;================================================= ============
[HKEY_CURRENT_USER\Software\Microsoft\Today]
"Skin"="\\Windows\\Lamborghini_Gallardo.tsk"
"UpdateFlag"=dword:00000001
"Restriction"=dword:00000002
Thanks,
Poltergeek.
you need to edit initflashfiles.dat and remove the line that places welcome in startup.
Poltergeek said:
I changed from DogGuy to this new DCD kitchen and do really like it, but I have come across a couple of strange things. I was wondering if anyone else is having the same issues, and has figured them out. I can no longer skip the welcome screen and calibration with this new kitchen. I even tried to recreate the script with the newest oemizer, and still no luck. I am using a real high GUID (ffffffff-f493-424e-b7f1-cab5da57bd61) so it should be one of the last updates to the registry. But it still does not work. It did work with the DogGuy kitchen and the 6.1 rom from No2Chem. Has anyone made this work? Here is the code form my oem:
;<<<<<----- First Boot Settings ----->>>>>
;Skip Welcome Screen
;================================================= ============
[HKEY_LOCAL_MACHINE\Software\Microsoft\Welcome]
"Disable"=dword:FFFFFFFF
;Stylus Calibration
;================================================= ============
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\TOUCH]
"CalibrationData"="2018,1980 3383,3022 3387,972 649,950 667,3021"
[HKEY_LOCAL_MACHINE\ControlPanel\Stylus]
"Group"=dword:00000001
;--------------------------------------------
Also, I have not been able to successfully change the today screen through an oem either.
;Today Theme
;================================================= ============
[HKEY_CURRENT_USER\Software\Microsoft\Today]
"Skin"="\\Windows\\Lamborghini_Gallardo.tsk"
"UpdateFlag"=dword:00000001
"Restriction"=dword:00000002
Thanks,
Poltergeek.
Click to expand...
Click to collapse
place a file named " welcome.not " without quotation marks on the sd card and when you hard rest it will skip the welcome screen including calibration
Thanks DCD that did it. You are the man! I learn something new everyday.
-Poltergeek
dcd1182 said:
you need to edit initflashfiles.dat and remove the line that places welcome in startup.
Click to expand...
Click to collapse
which initflashfiles.dat would this be?
\OEM\OEM_Lang_0409\initflashfiles.dat
Poltergeek
Hey poltergeek - what about the today screen.... have you been able to figure out how to set it to the theme you want in ROM???
Nope, Still working on that. Something in the Kitchen is still overriding my settings in my hacks oem folder. I had trouble with it in the DogGuy kitchen as well. It uploads the Lamborgini tsk file, but I cannot get it to set properly. I just have to manually set it after every flash.... which is often. If I figure it out, I will post the fix.
Poltergeek
same here, poltergeek. i used oemizer to make the oem, and whatever the setting is, its overriding anything i do to change the theme...dcd help!
another problem im having is i edited the initflashfiles.dat to have nobottombar.exe in the startup folder. well, its in the startup folder and it doesnt activate until i go into the windows/startup folder and open it ugh. heres the line i made, its the last one listed:
; Startup Folder
Directory("\Windows\StartUp"):-File("coldinit.lnk","\Windows\coldinit.lnk")
Directory("\Windows\StartUp"):-File("bugtrap.lnk","\Windows\bugtrap.lnk");
Directory("\Windows\StartUp"):-File("poutlook.lnk","\Windows\poutlook.lnk")
Directory("\Windows\StartUp"):-File("CheckAutoRun.lnk","\windows\CheckAutoRun.lnk")
Directory("\Windows\StartUp"):-File("TrayAp.lnk","\windows\TrayAp.lnk")
Directory("\Windows\StartUp"):-File("nobottombar.exe","\Windows\nobottombar.exe")
Poltergeek said:
Nope, Still working on that. Something in the Kitchen is still overriding my settings in my hacks oem folder. I had trouble with it in the DogGuy kitchen as well. It uploads the Lamborgini tsk file, but I cannot get it to set properly. I just have to manually set it after every flash.... which is often. If I figure it out, I will post the fix.
Poltergeek
Click to expand...
Click to collapse
that something is wm6.1. it sets the default wm6.1 theme over anything you set in an oem.
i think you can still use cusTSK.exe and config.txt to set a different theme with autorun.
dcd, what would happen if we delete the windows mobile 6.1 theme?
Skipping the welcome screen. A while back I used OEmizer from Dogguys kitchen to make a simple OEM called preferences. in it I checked off skip welcome screen, Owners name, my IMAP settings for email etc. All of which are automatically implimented when I build the rom. I simply took that OEM and inserted it in the OEM folder of DCD's kitchen and it worked perfect.
On a side note, it allows you to choose your skin, but I never figured out how to make the new skin upload or auto impliment.... any idea?
You cant depend on an OEM for everything. You guys need to check the shell folder and edit this file mxipcold_wpc_2.provxml
Enjoy!
Poltergeek said:
\OEM\OEM_Lang_0409\initflashfiles.dat
Poltergeek
Click to expand...
Click to collapse
thanks.....
UGH! this is so aggrivating! i edited mxipcold_wpc_2.provxml and changed the .tsk to the one i want. i edited the today picture to what i want. now i cant get the right color for the bars! does anyone know a basehue color for black? mine is <parm name="BaseHue" value="16400A4" datatype="integer"/> its supposed to show up black but its showing up blue?!?!? heres my mxipcold_wpc_2.provxml:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKCU\Software\Microsoft\Today">
<parm name="Skin" value="\Windows\vista.tsk" datatype="string"/>
<parm name="UseStartImage" value="1" datatype="integer"/>
</characteristic>
<characteristic type="HKCU\Software\Microsoft\Today\vista.tsk">
<parm name="COLOR_TITLEFLATCENTER" value="1657344" datatype="integer"/>
</characteristic>
<characteristic type="HKLM\Software\Microsoft\Color">
<parm name="SHColor" value="/wAAAAAAAADd3d0A///MAP///wAVvB0AFbwdAMnpywAUpxsA////ABSnGwAUpxsAFKcbABW8HQA0fzgA////AMnpywA30z8AN9M/AP///wAVvB0AFKcbAP///wAVvB0AhITDABW8HQAUpxsA////AP///wAAAAAA////AAAAAAD///8AFbwdAAhKAADe/2MA////AMnpywAUpxsA////ABSnGwA=" datatype="binary"/>
<parm name="BaseHue" value="16400A4" datatype="integer"/>
</characteristic>
<characteristic type="HKLM\System\GWE">
<parm name="SysColor" value="yenLAAAAAAA30z8AjdWRAP///wD///8AAAAAAAx/EgAAAAAA////AAAAmQDAwMAA////ADfTPwD///8AyenLAICAgAC/v78AAAAAAP///wD///8AAAAAAP///wAAAAAA///MAP///wAAAAAAT5r2AMDAwAA=" datatype="binary"/>
</characteristic>
</characteristic>
<characteristic type="FileOperation">
<characteristic type="%CE2%" translation="install">
<characteristic type="stwater.jpg" translation="install">
<characteristic type="Copy">
<parm name="Source" value="%CE2%\stwater_240_320.jpg" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Just delete the file. You will loose the flat bars on 6.1 tsk.
Enjoy
ok if i delete the file, and make an oem to set whatever.tsk as the theme, will it make it the theme?
edit:: ok i deleted the file. made an oem to make a certain .tsk default, and still isnt working. just makes the today screen have a blue background and blue bars.
so... no luck changing the default theme as it boots up?
Change some ROM file attribute on Hard-reset
Here a file that I've found in the Diamond ROM.
AutoAttribute remove read-only file attribute after Hard reset to let users delete somes unecessary files cooked in ROM like image template or anything you want.
Caution : don't change attribute to all file, user can make catastrofic experiences.
For use it, just take the package in your OEM folder and add in your Config.txt :
Code:
EXEC:\Windows\AutoAttribute.exe \Windows\MASD_RemoveReadOnly.txt
Now just take a look in MASD_RemoveReadOnly.txt, you'll understand how it work :
example
Code:
\My Documents\UAContents\Templates\MMSTemplates????.inf
[COLOR=red]Here each "?" is a char[/COLOR]
\My Documents\UAContents\Templates\*.*
[COLOR=red]* is for varchar here it's any files of any extension how are in "My Documents\UAContents\Templates\"[/COLOR]
\Program Files\OrangePhoto\*
[COLOR=red]Here all files and folders how are in "Program Files\OrangePhoto"[/COLOR]
good cooking
xvx45 said:
Change some ROM file attribute on Hard-reset
Here a file that I've found in the Diamond ROM.
AutoAttribute remove read-only file attribute after Hard reset to let users delete somes unecessary files cooked in ROM like image template or anything you want.
Caution : don't change attribute to all file, user can make catastrofic experiences.
For use it, just take the package in your OEM folder and add in your Config.txt :
Code:
EXEC:\Windows\AutoAttribute.exe \Windows\MASD_RemoveReadOnly.txt
Now just take a look in MASD_RemoveReadOnly.txt, you'll understand how it work :
example
Code:
\My Documents\UAContents\Templates\MMSTemplates????.inf
[COLOR=red]Here each "?" is a char[/COLOR]
\My Documents\UAContents\Templates\*.*
[COLOR=red]* is for varchar here it's any files of any extension how are in "My Documents\UAContents\Templates\"[/COLOR]
\Program Files\OrangePhoto\*
[COLOR=red]Here all files and folders how are in "Program Files\OrangePhoto"[/COLOR]
good cooking
Click to expand...
Click to collapse
Good find! I'm currently working on ripping some new apps as well!
l3v5y said:
Good find! I'm currently working on ripping some new apps as well!
Click to expand...
Click to collapse
If you found working please share with coockers
Nope tried it.
If i run it in Autorun as the first EXEC: then Autorun doesn't parse the rest of the Autorun commands.
Now set it to last command in Autorun but it didn't change the atributes i could not delete the files using a mortscript then set in SDAutorun and Autorun and also Manually.
I'll recheck.
Also this file looks familiar to another similar named file i found in an ELF extrom once.
Nope running this in Autorun kills all Commands that come after it also in UC SDAutorun.
Anyone got this working?
The File was
ChgScutAttribute
http://forum.xda-developers.com/attachment.php?attachmentid=52827&d=1191352085
Change Shortcut Attributes
Supposedly should change Shortcut Atributes (duh)
But never found how and which Shortcuts?!
I just looked at it in Reshacker and it appears to have some dialog that indicate this.
Or does it really only change the startmenu shortcuts?
But this is out of my Cupcake reach Maybe someone else can find out how it works..
Also in the Diamond OEM eacht file mentioned in the MASD_RemoveReadOnly Is also accompanied by some Provisioning file operations.
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\SOFTWARE\HTC\AutoShortcut">
<parm name="|%csidl_mypictures%\album sample_*.jpg" value="RemoveReadOnly" datatype="string" translation="install"/>
<parm name="|%csidl_mypictures%\album sample_04.3gp" value="RemoveReadOnly" datatype="string" translation="install"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
Frick it i simply use a mortscript to change the atributes and then deletes itself at startup.
Same effect with Clean up.
I'm cooking a localised ROM (DUTCH) build 20931 (and in the future 20954).
I got ROM up and running quite smotely as i may say BUT....
2 problems I really do not understand:
1) I always used the same package "FInixNOverBattery". I didn't change a thing in the package but somehow it shows the original battery icon again...
2) Kinda the same thing happened with the enlarged system status. Ever since I used the baserom 1.95.502.5 it does not show anymore. I already checked registry and touchflo settings and it should be enabled. But I still get 'normal' popups when I hit volume/reception/etc and not the enlarged one which you have to choose again from
somebody got a sollution?
Thanx in advance....
Greetz Merten3000
merten3000 said:
I'm cooking a localised ROM (DUTCH) build 20931 (and in the future 20954).
I got ROM up and running quite smotely as i may say BUT....
2 problems I really do not understand:
1) I always used the same package "FInixNOverBattery". I didn't change a thing in the package but somehow it shows the original battery icon again...
2) Kinda the same thing happened with the enlarged system status. Ever since I used the baserom 1.95.502.5 it does not show anymore. I already checked registry and touchflo settings and it should be enabled. But I still get 'normal' popups when I hit volume/reception/etc and not the enlarged one which you have to choose again from
somebody got a sollution?
Thanx in advance....
Greetz Merten3000
Click to expand...
Click to collapse
1) FInixNOverBattery needs it's SDKCerts to work. Cook the registry settings and it will work. You may also want to remove the phcanoverbmp in your phone canvas.
2) Do you have the EnlargeStartMenu cooked? You also need one from the Blackstone build.
pfcsabre said:
1) FInixNOverBattery needs it's SDKCerts to work. Cook the registry settings and it will work. You may also want to remove the phcanoverbmp in your phone canvas.
2) Do you have the EnlargeStartMenu cooked? You also need one from the Blackstone build.
Click to expand...
Click to collapse
Thnx!! System Status is working. I had EnlargeStartmenu/EnlargedTitlebar cooked but after I replaced the enlargedTitlebar with another on it worked again!
For the battery icon package:
I got the following in the RGU:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BatteryIconLevels"=dword:00000065
"BatteryIconIdStart"=dword:000003e9
"BaseDll"="phcanOverbmp.dll"
"BaseId"=dword:00000000
And I have a xml which is as follows
Code:
- <characteristic type="CertificateStore">
- <characteristic type="Privileged Execution Trust Authorities">
- <!--
SDK Failsafe Priv Root
-->
- <characteristic type="1c28a327d2dc579d241f2f83e98c1ef8ffbf1e82">
<parm name="EncodedCertificate" value="MIIEfzCCA2ugAwIBAgIQTQC040UA3pJF4GZVmWLkbzAJBgUrDgMCHQUAMIGQMYGNMIGKBgNVBAMegYIAVABFAFMAVAAgAFUAUwBFACAATwBOAEwAWQAgIBMARgBhAGkAbABzAGEAZgBlACAAQwBvAG4AZgBpAGcAdQByAGEAdABpAG8AbgAgAFIAbwBvAHQAIABmAG8AcgAgAFcAaQBuAGQAbwB3AHMAIABNAG8AYgBpAGwAZQAgAFMARABLMB4XDTA0MTEwODIzMDA1M1oXDTA5MTIzMTA4MDAwMFowgZAxgY0wgYoGA1UEAx6BggBUAEUAUwBUACAAVQBTAEUAIABPAE4ATABZACAgEwBGAGEAaQBsAHMAYQBmAGUAIABDAG8AbgBmAGkAZwB1AHIAYQB0AGkAbwBuACAAUgBvAG8AdAAgAGYAbwByACAAVwBpAG4AZABvAHcAcwAgAE0AbwBiAGkAbABlACAAUwBEAEswggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDK+lwE9mOuPjhBCmbgkKTm/bqW8st0EJuYle3wLRfZKQ8jr2oU5dxg1CAZhThXdZZLFFIHwf8KvaQDRsx4OcMEd8CZF1tKAMu+ye3irsEhzwK8qkHaWM2SMSI8YyuuClOZMBzQOAe2Z9niKyuwzNmZ24EjjxLMsAJ3H/rFAVTIVLALxf34vV4855vXczdeBr6pv1MCXi0gWXnBrFt74R8DWEZGtrj80nrFX3EpBlgVm94k8dig61S5C+nWh9+F3pCpSYWE8yc0AVyCAWtowDa7Sg4Q292ZwTC2cMRWk025LAyemegRAOPN3TaqwhW9y14zmOhK0JGpZq7rJIhA88dJAgMBAAGjgdowgdcwDQYDVR0KBAYwBAMCB4AwgcUGA1UdAQSBvTCBuoAQyMFxH213dj3Lcp1n/thJrKGBkzCBkDGBjTCBigYDVQQDHoGCAFQARQBTAFQAIABVAFMARQAgAE8ATgBMAFkAICATAEYAYQBpAGwAcwBhAGYAZQAgAEMAbwBuAGYAaQBnAHUAcgBhAHQAaQBvAG4AIABSAG8AbwB0ACAAZgBvAHIAIABXAGkAbgBkAG8AdwBzACAATQBvAGIAaQBsAGUAIABTAEQAS4IQTQC040UA3pJF4GZVmWLkbzAJBgUrDgMCHQUAA4IBAQCzbN5MZGnx4QR1Mnr0AEI9DYtBtVGserpgj8nK9jVykSz8eIIt9Fc2txieAGh7pZA9X8yoRlzO50AKSrxxHB2Rnd/PbUEMtmHNNFYj0uP2LgdYLXed8NNzW4VV6DjQ6HdDfqLA2Drp7QniYw6TMIxAqttTyETxl0LP5mAwRxk3pAyJ1Bbtim1SlDJSWe1AxkXnOt1nEzju6Z37Cnfba06Xtco1KiaB8Lku0dVUrVeA+RiiKaa/dJZOWjwOmgBjKIHb39qU9F2PumCH4Pd/IVWRUvzgVd4cLb2r8lJ3jXnuGs9dKSFnmoAYoRRcxLmxupOaU5peY5GMa6K/BAJoRt4h" />
</characteristic>
- <!--
SDK Priv App Root
-->
- <characteristic type="d4fb8924cfba6c9c67360e7d6512ffde99d2d283">
<parm name="EncodedCertificate" value="MIIDoDCCAoygAwIBAgIQ8gy25VyTNaxKTY+BkIAXsTAJBgUrDgMCHQUAMEgxRjBEBgNVBAMTPVRFU1QgVVNFIE9OTFkgLSBTYW1wbGUgUHJpdmlsZWdlZCBSb290IGZvciBXaW5kb3dzIE1vYmlsZSBTREswHhcNMDQxMTA1MDAwNjQyWhcNMDkxMjMxMDgwMDAwWjBIMUYwRAYDVQQDEz1URVNUIFVTRSBPTkxZIC0gU2FtcGxlIFByaXZpbGVnZWQgUm9vdCBmb3IgV2luZG93cyBNb2JpbGUgU0RLMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyTRPgw3DBwztRltEsMwPObJRI/NMwcz/7f01HluHpQx+LcqR10dLZvwOX3UGprOZeobSRYk99Oa0xiFuXXVf+XAoEycdb1hjuFO/L7o2e/xfqX6FLBCVtl79ekXUbj+wyEKZZBBfsFUoQfQj0Qg7seSpD+YWjQJ7cLrMLyMNZHrBYEX/J8+qPR5PCT7zO0qlfmOjvyBCdb1x3FxCZZrSVN1TJDdm2+6gUDEf99nZHE/15A1uOwWWRb16+Mn2Bk8gven8lflQ1occ+/AXhTfjKqNxApf8MPESjkcf5+RKZLlnYx0sgTmR7Oz7ZPO4ox7igzaPJ63QfhlufNhMeG2pxQIDAQABo4GNMIGKMA0GA1UdCgQGMAQDAgeAMHkGA1UdAQRyMHCAEFXN9dXzTpRiYNFtrL4y+5ihSjBIMUYwRAYDVQQDEz1URVNUIFVTRSBPTkxZIC0gU2FtcGxlIFByaXZpbGVnZWQgUm9vdCBmb3IgV2luZG93cyBNb2JpbGUgU0RLghDyDLblXJM1rEpNj4GQgBexMAkGBSsOAwIdBQADggEBAC53q9xWAdlbyIQsAJK5OrMqMme1cA3EH+AzYY/E0S7BK8sWc5rRSotOcjIQP+uK7pMTvBzCphopqJuF5N2RJ8ZDm6DkIHH4gWtmCIKYgLYUKIojFeNcHucWCrhsU6qLb/eOjg2/MnGPxaswmvzlrKtsyDtmUecB/P7Fx2Ka9+F8wqjA6YeUnX0/QxZsWyHkrwKmOsO2H/20FS2MzM4fZIyUOr6eMavjg3DX70JWJLg0CkQD8jnHxieShdOF2oeGhbzoBjQ3H4C2st/UgAh/QN13+pWBAeO1dmvd+rzeLgI1v6TPNyam3ndKJftTAP1fxNFfDfNxG6WzmCP7vA0SULE=" />
</characteristic>
</characteristic>
</characteristic>
- <!--
Microsoft Visual Studio Signing Authority
-->
- <characteristic type="CertificateStore">
- <characteristic type="Privileged Execution Trust Authorities">
- <characteristic type="884B8CDDB6FF1A3D2FF4BC09EC45E2AE2CCB244C">
<parm name="EncodedCertificate" value="MIIEjTCCA/agAwIBAgIQuCykvf6s9KVL7HIysc7nszANBgkqhkiG9w0BAQQFADCBuTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCldhc2hpbmd0b24xEDAOBgNVBAcTB1JlZG1vbmQxHjAcBgNVBAoTFU1pY3Jvc29mdCBDb3Jwb3JhdGlvbjEiMCAGA1UECxMZVmlzdWFsIFN0dWRpbyBmb3IgRGV2aWNlczE/MD0GA1UEAxM2TWljcm9zb2Z0IFZpc3VhbCBTdHVkaW8gSW50ZXJtZWRpYXRlIFNpZ25pbmcgQXV0aG9yaXR5MB4XDTA0MTAxMTIyNTIwMFoXDTM5MTIzMTIzNTk1OVowgawxCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpXYXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xIjAgBgNVBAsTGVZpc3VhbCBTdHVkaW8gZm9yIERldmljZXMxMjAwBgNVBAMTKU1pY3Jvc29mdCBWaXN1YWwgU3R1ZGlvIFNpZ25pbmcgQXV0aG9yaXR5MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDjXYPMN5De4mQVThwxT1uNZRsH53LFfgMuJJEUDs3igYwd+hj0O+q+yM6WwC/BEa/eTvN0yXdWBa9/VFYQ3lqbcMTMF/vPTWqBzY/aOhq2hHE5ikqsT3yIUKB42QTpKT8yoprbOOkdJ097bDqJEa6jsikrZlkQfXTYasSFo6gf6QIDAQABo4IBnzCCAZswDQYDVR0KBAYwBAMCBkAwewYDVQQDBHQecgBNAGkAYwByAG8AcwBvAGYAdAAgAFYAaQBzAHUAYQBsACAAUwB0AHUAZABpAG8AIABQAHIAaQB2AGkAbABlAGQAZwBlAGQAIABFAHgAZQBjAHUAdABpAG8AbgAgAEMAZQByAHQAaQBmAGkAYwBhAHQAZTAkBgNVHSUEHTAbBgEBBgEDBgEGBgEBBgEFBgEFBgEHBgEDBgEDMIHmBgNVHQEEgd4wgduAEMTFNerp58rQqJZku7LMpYOhgbQwgbExCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpXYXNoaW5ndG9uMRAwDgYDVQQHEwdSZWRtb25kMR4wHAYDVQQKExVNaWNyb3NvZnQgQ29ycG9yYXRpb24xIjAgBgNVBAsTGVZpc3VhbCBTdHVkaW8gZm9yIERldmljZXMxNzA1BgNVBAMTLk1pY3Jvc29mdCBWaXN1YWwgU3R1ZGlvIFJvb3QgU2lnbmluZyBBdXRob3JpdHmCEGNH1pJnhsmsTfxzVt0hidcwDQYJKoZIhvcNAQEEBQADgYEATRX+ejR5NxLpQpOVHpguVt8xFS/DcbHZ/tptmYdZ3YNydWEsTWP7JI84c87vxzCB02fcQNOMaBwwlIuLQyz8vBITRpLlHVaF4SggjkjQNCnDNskI1iKV3C6tjBmRPblfMhXQWjiIigUzPnyavTc3k0bT3WwdI0l/NNJeyN0VxaQ=" />
</characteristic>
</characteristic>
</characteristic>
- <!--
=================================================================
The above code is not complete because of board limititations but it shows certs are installed I guess...
Any more suggestions? Or do you gave a working package?
Thanks again for your help!!
merten3000 said:
Thnx!! System Status is working. I had EnlargeStartmenu/EnlargedTitlebar cooked but after I replaced the enlargedTitlebar with another on it worked again!
For the battery icon package:
I got the following in the RGU:
Code:
REGEDIT4
[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BatteryIconLevels"=dword:00000065
"BatteryIconIdStart"=dword:000003e9
"BaseDll"="phcanOverbmp.dll"
"BaseId"=dword:00000000
And I have a xml which is as follows
The above code is not complete because of board limititations but it shows certs are installed I guess...
Any more suggestions? Or do you gave a working package?
Thanks again for your help!!
Click to expand...
Click to collapse
Just cook it with the rest. Add the registry to any .rgu file and the xml to any .provxml file. Do not create one as for some reason the .provxml will not be executed. Validate your .provxml file afterwards (open it in IE or FF-- sohuld show a valid xml).
pfcsabre said:
Just cook it with the rest. Add the registry to any .rgu file and the xml to any .provxml file. Do not create one as for some reason the .provxml will not be executed. Validate your .provxml file afterwards (open it in IE or FF-- sohuld show a valid xml).
Click to expand...
Click to collapse
Damn did it all but no luck....still the same old battery indicator
merten3000 said:
Damn did it all but no luck....still the same old battery indicator
Click to expand...
Click to collapse
try putting it in mxipupdate_oemoperators_100.provxml at the very beginning.. not at the end
just an fyi, you dont need certs for stuff that's cooked in, ROM files are automagically trusted.. so look elsewhere for the issue with this loading.
Da_G said:
just an fyi, you dont need certs for stuff that's cooked in, ROM files are automagically trusted.. so look elsewhere for the issue with this loading.
Click to expand...
Click to collapse
I don't know that well he may have duplicate phcanoverbmp and BuildOS is overwritting it Merten, try renaming your battery icon to another dll and point
[HKEY_LOCAL_MACHINE\security\ResOver\Bitmaps]
"BaseDll"="<name of your dll>"
Da_G said:
just an fyi, you dont need certs for stuff that's cooked in, ROM files are automagically trusted.. so look elsewhere for the issue with this loading.
Click to expand...
Click to collapse
You have been a great help....I appreciate it!!
Keep up the good work!
Glad to see You back and testing...
If You are in need of a beta tester, I'll be available once more
(but not before Monday afternoon, can't have the gf unhappy )
for the one's who like it , I made a .cab from the patched files of 7.918.9193 found on ipmart .
just install the cab and you have the Navigator 7.918.9193 (no need to first install an old package).
this version is from a HD2 but runs good on a TP .
DON'T ASK FOR MAP'S AND DON'T ASK HOW TO ACTIVATE MAP'S
Here is the link to ttn7.918.9193_vga_black.cab
Thanks to JaCoL_JcL we also have the ttn7.918.9193_(W)QVGA_black.cab
Here is the link to ttn7.918.9193_(W)QVGA_black.cab
Edit: fixed the link .
You wrote "TomTom Navigator 7.918.9193 (W)VGA" in this tread title, is it really WVGA?
Hassan99 said:
You wrote "TomTom Navigator 7.918.9193 (W)VGA" in this tread title, is it really WVGA?
Click to expand...
Click to collapse
it was a dump from a HD2 so I think so .
on ipmart a lot are using it on a HD2 .
reported as warez link! u must but this application m8! don't share here this kindda files !
JaCoL_JcL said:
reported as warez link! u must but this application m8! don't share here this kindda files !
Click to expand...
Click to collapse
what is wrong with this it is not cracked or someting like that .
and if an admin ask me to remove this link I will do it
JaCoL_JcL said:
reported as warez link! u must but this application m8! don't share here this kindda files !
Click to expand...
Click to collapse
Only the TomTom Maps are considered Warez, the TomTom application isn't.
Dave
DaveShaw said:
Only the TomTom Maps are considered Warez, the TomTom application isn't.
Dave
Click to expand...
Click to collapse
thanks Dave for correcting this .
Gr Cees.
TomTomNavigator 7.918.9193 QVGA/WQVGA
DaveShaw said:
Only the TomTom Maps are considered Warez, the TomTom application isn't.
Dave
Click to expand...
Click to collapse
good to know sry about affair xD
------------------------------------
Here is a (W)QVGA installation cab, color - black:
Code:
http://www.multiupload.com/LDPXH7IEN3
JaCoL_JcL said:
good to know sry about affair xD
------------------------------------
Here is a (W)QVGA installation cab, color - black:
Code:
http://www.multiupload.com/LDPXH7IEN3
Click to expand...
Click to collapse
I will post it on the first post
Can this simply be installed over an existing TomTom installation, or will maps have to be re-authenticated (re-registered, whatever it's called)?
pistou said:
Can this simply be installed over an existing TomTom installation ?
Click to expand...
Click to collapse
yes it can .
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Frank Caarls said:
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Click to expand...
Click to collapse
Hi all
one question !
in the past ,for change the VGA to QVGA version ,the hack are for the TTN7 build 7451.9033 : run in qvga black or blue, or VGA black.
For this , use an hexadecimal editor like Hexedit or Ultraedit, open TomTom Navigator.exe and modify displacement 2A8578h :
. 10h VGA Black
. ODh QVGA Blue
. 12h QVGA Black
but in the new 7.918 there is no "2A8578" in the file tomtom.exe ,how change this, in this version ? in the first post,this is only a VGA version ,not QVGA for me ???
thanks in advance for your reply
Frank Caarls said:
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Click to expand...
Click to collapse
Unzipping via 7zip actually gave me different filenames... renamed according to nearest filesize, gonna try and see. Anyway, thanks for the idea!
Frank Caarls said:
If you have Tom Tom already installed just extract te cab file in this post.....rename the 001-file to "Tom Tom navigator.exe" and the 002-file rename to "data.chk". Copy these 2 files to the navigator map in your phone directory replacing the existing files and you are done. All your settings will remain.
Have this version running since a few days.......no problems!
Click to expand...
Click to collapse
Nice post, but wrong for me. (For the file I downloaded from the OP).
The two files you need will be the two largest ones, with data.chk being the larger of the two. You know you have found the correct tomtom exe because the icon will change to a tomtom logo.
I hope this one solves my keyboard problems, for some reason my keyboard always stopped working properly after a while, though I suspect tomtom home maybe screwing with my phone install or something.
I have tomtom 7 with us and canada maps.
What exactly is this and what does it do?
what does this offer that is not already in 7.916.9189 ??
is it simply that it's WVGA ?
does it actually look any better for being WVGA ? (am I missing the plot ?)
according to GPS undergound, this version will only work on :* ERA MDA Vario IV
* HTC HD 2
* HTC P3470
* HTC Touch 2
* HTC Touch Cruise
* HTC Touch Cruise II
* HTC Touch Diamond 2
* HTC Touch HD
* HTC Touch Pro
* HTC Touch Pro 2
* HTC TyTN II
* O2 XDA Diamond Pro
* O2 XDA Guide
* O2 XDA Orbit 2
* Orange HTC Touch Pro
* Orange P4550
* Samsung i900 Omnia
* SFR HTC Touch HD
* SFR HTC Touch Pro
* Sony Ericsson XPERIA X1
* Swisscom HTC Touch Pro
* Swisscom HTC Touch Pro 2
* Swisscom XPA1615
* T-Mobile MDA Vario III
* T-Mobile MDA Vario IV
* Vodafone HTC Touch Pro
* Vodafone XPA1615
because it's not been cracked for any pda yet ? - is this a cracked version ?
http://www.gpsunderground.com/forums/showthread.php?p=162055#post162055
if you open the .cab with winrar you will find the file setup.xml
if you open the setup.xml you can read what the file name is.
Code:
- <wap-provisioningdoc>
- <characteristic type="Install">
<parm name="InstallPhase" value="install" />
<parm name="SetupDLL" value="1" />
<parm name="ProcessorType" value="2577" />
<parm name="OSVersionMin" value="3.0" />
<parm name="OSVersionMax" value="100.0" />
<parm name="BuildNumberMin" value="0" />
<parm name="BuildNumberMax" value="-536870912" />
<parm name="AppName" value="TomTom Navigator" />
<parm name="InstallDir" value="%CE1%\Navigator" translation="install" />
<parm name="NumDirs" value="4" />
<parm name="NumFiles" value="7" />
<parm name="NumRegKeys" value="0" />
<parm name="NumRegVals" value="0" />
<parm name="NumShortcuts" value="1" />
</characteristic>
- <characteristic type="FileOperation">
- <characteristic type="%CE2%" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="ttn6bt2003.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="TTN6BT~1.001" />
<parm name="OverwriteIfExists" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="BtCoreIf.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="BTCOREIF.002" />
<parm name="OverwriteIfExists" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="BtSdkCE30.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="BTSDKC~1.003" />
<parm name="OverwriteIfExists" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="phone.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="000PHONE.005" />
<parm name="NoOverwrite" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
</characteristic>
- <characteristic type="\TomTom" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="TTToday.dll" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="0TTTODAY.004" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
</characteristic>
- <characteristic type="%InstallDir%" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="[COLOR="Red"][B]TomTom Navigator.exe[/B][/COLOR]" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="[COLOR="Red"][B]0CABB32B.006[/B][/COLOR]" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
- <characteristic type="[COLOR="Blue"][B]data.chk[/B][/COLOR]" translation="install">
- <characteristic type="Extract">
<parm name="Source" value="[COLOR="Blue"][B]0CABE6BA.007[/B][/COLOR]" />
<parm name="WarnIfSkip" />
</characteristic>
</characteristic>
</characteristic>
- <characteristic type="%CE11%" translation="install">
<characteristic type="MakeDir" />
- <characteristic type="TomTom Navigator.lnk" translation="install">
- <characteristic type="Shortcut">
<parm name="Source" value="%InstallDir%\TomTom Navigator.exe" translation="install" />
</characteristic>
</characteristic>
</characteristic>
</characteristic>
<characteristic type="Registry" />
</wap-provisioningdoc>
that mean that 0CABB32B.006=TomTom Navigator.exe and 0CABE6BA.007=data.chk
evilc said:
Nice post, but wrong for me. (For the file I downloaded from the OP).
The two files you need will be the two largest ones, with data.chk being the larger of the two. You know you have found the correct tomtom exe because the icon will change to a tomtom logo.
I hope this one solves my keyboard problems, for some reason my keyboard always stopped working properly after a while, though I suspect tomtom home maybe screwing with my phone install or something.
Click to expand...
Click to collapse
Indeed you are right.....have downloaded this TomTom Navigator from a "different" place......
Sofar had no problems to make map updates with TomTom Home....but for how long.....?
Hello all,
i just registered here to find out if opening a KML file on my SD card with Google maps in offline mode can work.
I am looking for an solution quite a time, but only found this thread on stackover...
To load kml into Google Maps on Android without writing an app, you can create a little html file somewhere with a geo-uri link to the kml file and then click on that link in any Android web browser.
For example: suppose your kml file is located in /sdcard/overlay.kml then you write a geo-uri link like this:
<html>
<head><title>Example KML link page using a geo-uri</title></head>
<body>
overlay.kml
</body>
</html>
Click to expand...
Click to collapse
Clicking on the link will launch Maps and then Maps will attempt to load and your kml.
Be warned however that the Android version of Maps does not appear to handle the same version/range of kml elements as the desktop version (or desktop Google Earth).
Click to expand...
Click to collapse
a other thread is about editing the manifest file to get maps to open local KML files
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="h**p://schemas.android.com/apk/res/android"
package="com.example.lyold"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="15"
android:targetSdkVersion="16" />
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.VIBRATE"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.CAMERA" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="com.example.lyold.LoginActivity"
android:screenOrientation="landscape"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
<activity
android:screenOrientation="landscape"
android:name=".Home" />
<activity android:name="com.google.earth.EarthActivity" android:screenOrientation="landscape"/>
</application>
</manifest>
Click to expand...
Click to collapse
Don't know if this is already outdated solution or not, i just cant get it to work.
Does anybody know a way to open local KML files with google maps in offline mode ?
ThX in advance !
PS: i want to open kml ONLY in google maps, i know there are several apps out there that support kml files....
hello again,
before i start trying to finf out how to edit the manifest file.
I wanted to ask if adding the line
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
Click to expand...
Click to collapse
could help me out here ?
ThX,
SA
Please Help !
Hello world !
Does someone know if editing the manifest file could solve the problem that google maps won't open KML file which are on the phones SD-card.
If not, i can give up to find an option..
ThX,
SA