Diamond FileAttribute.exe - JAMin, XDA Neo, S200 ROM Development

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.

Related

Creating Own .cab files for settings etc...

Ive been messing about with my TyTN lately and just find it a right royal pain to put my settings back in etc...
...what im asking is is there any way to make a .cab installer that will let me reinstate all my GPRS/MMS/EMAIL settings etc... and copy a few files to the windows folders etc...(ringtones and sounds)???
Just in the event of needing to do a hard reset away from the PC a .cab installer on my SD card would be a godsend!
anyone?
yes, WINCAB CE is a 15 use free application that lets you create and view .cab files. If you search the forums there a numerus threads that contain registry keys for your setings etc
If you download the .cab files for your network provider again from the threads on this forum you can then import them into your own custom cab file using this software.
attached is a file that i use to set name, brightness levels, pIE homepage, and a couple of other tweaks, just edit this one and/or add your own. this should work on all WM2005 devices as it uses the same program language. hope this helps....
I spent the first 3 days after having my tytn making a cab of all my programs and settings cos I hard reset quite a lot, I made a big cab file with everything i like to install on internal storage and with all the settings of the programs I keep in the storage card. I think it is worth to spend the time initially.
What i found most useful was RegDiff to generate .reg files out of two exported registry dumps, registry workshop to browse / export the registry on the PocketPC from the computer and compare current regitry settings on PocketPC with a previously dumped registry file and WinCE Cab Manager to combine the cabs of all the programs I install, set the registry settings, and put shorcuts to all applications into the right places.
Forgive me for digging up an old thread, but this is exactly what I need, a tool that can make a backup of my MMS, GPRS and Email settings. I just got my X01HT yesterday and I've been playing around with different WM6 ROMs and it seriously is a pain to manually enter all my MMS, GPRS, and email settings for every ROM install I do. I also plan on doing the keyboard layout registry fix for the slide out keyboard, and I would but a lot easier to have that registry fix backed up.
pof posted how to do it with three seperate programs, I'm just wondering if there is a program that can do it all in one? I know it's been over six months since this thread was started and I'm just hoping that a simpler way has been made to do this. Any input and help on this matter is appreciated, thanks
Does anybody have the Wincab ce program that they can upload, it seems that the download site is having problems, I am unable to download from them and I can't seem to find it anywhere else, googled and it brings up very little.
Thanks
Lurch3559 said:
Does anybody have the Wincab ce program that they can upload, it seems that the download site is having problems, I am unable to download from them and I can't seem to find it anywhere else, googled and it brings up very little.
Thanks
Click to expand...
Click to collapse
Here is this great app at Megaupload
http://www.megaupload.com/?d=FHNS3KUA
Thank you for the site.
Thanks for posting it.
Can anybody direct me to a thread or WIKI to get more on this. I tried searching but returned nothing helpful. I just want to create a simple cab file with my operator settings.
Thanks
Lurch3559 said:
Does anybody have the Wincab ce program that they can upload, it seems that the download site is having problems, I am unable to download from them and I can't seem to find it anywhere else, googled and it brings up very little.
Thanks
Click to expand...
Click to collapse
Another alternative here:
http://teksoftco.com/index.php?section=airwizard
Sniper258 said:
Can anybody direct me to a thread or WIKI to get more on this. I tried searching but returned nothing helpful. I just want to create a simple cab file with my operator settings.
Thanks
Click to expand...
Click to collapse
I have posted this under http://forum.xda-developers.com/showthread.php?t=299023&page=14
I found this one usefull too: http://forum.xda-developers.com/showthread.php?t=295889
good luck!
what i did is google for wap-provisioningdoc gprs and got this
http://msdn2.microsoft.com/en-us/library/aa456052.aspx and around that area.
Further searches in the forum got me to look&browse in the other files already made; helped a lot in doing mine! credits to wpbear who lend me a hand!
It should get you to a xml file that can be tranformed into a cab.
A bit of warning: is a lot of trial&error and frustrations - took me about two weeks to make it from scratch. I am not specialist so a bit of luck is needed also. It is best to try on a fresh OS install or after a HR.
Hope it helps.
cheers,
dan
__________________
Thanks Dan for the info.
I'll look through it and repotr back.
Has anyone tried the airinstaller?
I saw this a while ago and dl the trial. You can only make one file in the trial and have not done it.
I will try it and post but just curious if anyone already has.
Hey Mr. Pof:
I used Registry Workshop 2.61 to export the following keys (for T-mobile US/Rogers Canada settings):
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Comm\RasBook\ROGERS GPRS] (and subkeys)
[HKEY_CURRENT_USER\Comm\RasBook\ROGERS MMS] (and subkeys)
[HKEY_CURRENT_USER\Comm\RasBook\T-mobile GPRS] (and subkeys)
[HKEY_LOCAL_MACHINE\Comm\ConnMgr\Destinations] (and subkeys)
[HKEY_LOCAL_MACHINE\Comm\ConnMgr\Planner] (and subkeys)
[HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections] (and subkeys, since below this had the 3 names of GPRS/MMS/GPRS as listed above).
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\MMSCSetting] (and subkeys)
Are there other registry keys that need to be exported via Registry Workshop regarding the settings for my 2 providers?
Assuming I have all the settings I need from the registry so that when I import them into a new ROM, the configuation is correct. How do I convert the .REG file from Registry Workshop 2.61 into some form that is or leads to a CAB?
Thanks.
pof said:
I spent the first 3 days after having my tytn making a cab of all my programs and settings cos I hard reset quite a lot, I made a big cab file with everything i like to install on internal storage and with all the settings of the programs I keep in the storage card. I think it is worth to spend the time initially.
What i found most useful was RegDiff to generate .reg files out of two exported registry dumps, registry workshop to browse / export the registry on the PocketPC from the computer and compare current regitry settings on PocketPC with a previously dumped registry file and WinCE Cab Manager to combine the cabs of all the programs I install, set the registry settings, and put shorcuts to all applications into the right places.
Click to expand...
Click to collapse
i found this tool was awesome .................................
crazyut said:
How do I convert the .REG file from Registry Workshop 2.61 into some form that is or leads to a CAB?
Click to expand...
Click to collapse
use wince cab manager.
pof said:
use wince cab manager.
Click to expand...
Click to collapse
this program does not run using vista period i tried
every setting i could such as run as admin and also run as XP nothing seemed to work. does anyone know a cab maker that will run with Vista?
Hi POF
When I click on File, Import, Import from REG, it says 'The Data Is Invalid' then 'The .REG file could not be imported'
I tried it with the Windows Registry Editor Version 5.00 line at the top of the .REG file and also without. Same results. I believe the files are saved in UTF-8 format.
The files contain numerous settings as one file instead of many separate files.
Any ideas, suggestions?
pof said:
use wince cab manager.
Click to expand...
Click to collapse
Okay, I was able to add other .CAB files and my registry edits. Do I need to fill out anything regarding provisioning in order to run the .CAB file on a new ROM?
I don't quite understand what provisioning is for (Pre XML/Post XML).
Thanks again.
pof said:
use wince cab manager.
Click to expand...
Click to collapse
This is how to create a CAB for your WIFI settings
Okay, so after fiddling about all day with various sample xml codes from MSDN, I was finally able to create a CAB to configure my WIFI connection to my home router (including WPA passkey), so that I can just run the CAB every time I flash / hard-reset.
STEP 1. Open Notepad and copy the code below to it
Code:
<wap-provisioningdoc>
<characteristic type="CM_WiFiEntries">
<characteristic type="[B]SSID: REPLACE_WITH_YOUR_SSID[/B]">
<parm name="DestID" value="[B]Destination GUID: SEE NOTE 1 BELOW[/B]"/>
</characteristic>
</characteristic>
<characteristic type="Wi-Fi">
<characteristic type="[B]CONNECTION TYPE: SEE NOTE 2 BELOW[/B]">
<characteristic type="[B]SSID: REPLACE_WITH_YOUR_SSID[/B]">
<parm name="DestId" value="[B]GUID: SEE NOTE 1 BELOW[/B]"/>
<parm name="Encryption" value="[B]SEE NOTE 3 BELOW[/B]"/>
<parm name="Authentication" value="[B]SEE NOTE 4 BELOW[/B]"/>
<parm name="NetworkKey" value="[B]REPLACE WITH YOUR NETWORK KEY, SEE NOTE 5[/B]"/>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
STEP 2. Replace the parameters in the sample code depending on the connection you want to configure:
SSID: Self-explanatory
Note 1
Destination GUID
For a connection to "The Internet", use this GUID
{436EF144-B4FB-4863-A041-8F905A62C572}
For a connection to "Work", use this GUID
{A1182988-0D73-439e-87AD-2A5B369F808B}
Note 2
Connection Type
"access-point" for infrastructure connection
"ad-hoc" for computer-to-computer
Note 3
Encryption
0 = WEP
1 = No encryption
4 = TKIP
Note 4
Authentication
0 = Open authentication mode
1 = Shared authentication mode
3 = Specifies Wi-Fi Protected Access (WPA) authentication
4 = Specifies WPA-PSK authentication
5 = Specifies WPA-NONE
Note 5
Network Key
Put your WPA or WEP network key here, just as you would enter in the settings screen. However, make sure that the key does not contain either the ",< or > characters, since this will screw up the XML code.
STEP 3. Save the Notepad file as .provxml.xml
Choose "ALL FILES" in the "SAVE AS TYPE" box and "UNICODE" in the "ENCODING" dialog box
STEP 4. Open a command-line window, go to the folder where you saved the xml file and type:
makecab /D COMPRESS=OFF .provxml.xml wifi.cab
STEP 5. Copy the CAB file to your device and run it. You should now see your Wifi connection under the settings Wi-Fi control Panel
You will have to manually check the "Hidden Network" box if your router is hiding the SSID (I have not figured out the parameter to do this automatically yet)
Voilá!
Note: If you use WEP, you need some additional lines of code to specify things like the KeyIndex. See these pages for more info:
http://msdn2.microsoft.com/en-us/library/aa455986.aspx
http://msdn2.microsoft.com/en-us/library/aa456208.aspx
By way of example, below is a sample code for an access-point connection connection to the internet, using WPA-PSK authentication.
Code:
<wap-provisioningdoc>
<characteristic type="CM_WiFiEntries">
<characteristic type="My_SSID">
<parm name="DestID" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>
</characteristic>
</characteristic>
<characteristic type="Wi-Fi">
<characteristic type="access-point">
<characteristic type="My_SSID">
<parm name="DestId" value="{436EF144-B4FB-4863-A041-8F905A62C572}"/>
<parm name="Encryption" value="4"/>
<parm name="Authentication" value="4"/>
<parm name="NetworkKey" value="My_Network_Key"/>
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>
I hope this works for you. Let me know if you have any problems / questions.

Bypass Welcome Screen with DCD 2.3.1 Kitchen?

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?

[QUESTION] Cooking some 'non-functioning' ingredients....

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 )

.RGU skipped during compilation (PkgToolsBuildOs 6.x-5.3)

I know most chefs have moved on to the Visual Kitchen, but I would greatly appreciate some insight on a problem I'm having with the old'style kitchen.
I moved the GSensorCalibrator & GSensor SDK from the OEM folder to the PACKAGES folder. I added a supporting OPTION.XML (Unicode, like the others) and collapsed the contents of 0409 folder to the respective package folder, removed the 0409 folders, and then renamed the packages as follows:
.\Packages\02_PACKAGE_Raphael_GSensorCalibrator_1_0_18192126_0
.\Packages\02_PACKAGE_Raphael_SensorSDK_3_3_18182326_1
The ROM loads up fine from the BuilOS tab of PkgToolsBuildOs 6.x-5.3 and the output of the log pertaining to the package above shows the following:
Code:
Processing: Packages\02_PACKAGE_Raphael_GSensorCalibrator_1_0_18192126_0
Processing: Packages\02_PACKAGE_Raphael_GSensorCalibrator_1_0_18192126_0... Searching for dsm file
Dsm = Packages\02_PACKAGE_Raphael_GSensorCalibrator_1_0_18192126_0\9f517713-bb2d-4e77-8de8-e0638bf94c40.dsm
Processing: Packages\02_PACKAGE_Raphael_SensorSDK_3_3_18182326_1
Processing: Packages\02_PACKAGE_Raphael_SensorSDK_3_3_18182326_1... Searching for dsm file
Dsm = Packages\02_PACKAGE_Raphael_SensorSDK_3_3_18182326_1\c7a71384-f73c-47ac-bd20-610e0dfb3b11.dsm
The Cabinet Tool section of the log shows this:
Code:
-- adding packages\9f517713-bb2d-4e77-8de8-e0638bf94c40.rgu
-- adding packages\c7a71384-f73c-47ac-bd20-610e0dfb3b11.dsm
-- adding packages\c7a71384-f73c-47ac-bd20-610e0dfb3b11.rgu
Notice that the .DSM for the GSensorCalibrator is missing - not sure why. I've even tried recreating the file and using BUILDDSM.
The RGU Comp section of the log shows this:
Code:
package "02_PACKAGE_Raphael_GSensorCalibrator_1_0_18192126_0" does not contain .rgu file "8f517713-bb2d-4e77-8de8-e0638bf94c40.rgu"
importing registry file ".\Registry\c7a71384-f73c-47ac-bd20-610e0dfb3b11.rgu"...
I checked the usual stuff: .RGU file format (Unicode, like others), .PROVXML format (same like others, although irrelevant at this point), duplicate .DSM/.RGU, multiple .RGU/.DSM in the package folder.
I'm completely stumped; I'm sure it's something I'm overlooking but for the life of me, I can't figure out why PkgToolsBuildOs 6.x-5.3 is not "picking" up the GSensorCalibrator .RGU file.
* UPDATE *
Deleting the .DSM files and creating blank empty ones seem to solve the problem ... which still has me confused as I started off with empty .DSM to begin with.
As I suspected, if the Cabinet Tool section does not show a .DSM for an .RGU expect problem with the package in question.
Need to use BuildDSM.exe to add the rgu to the package for the old kitchen.
Also make sure the rgu is read only.
That's how I assumed it was supposed to function - the .DSM essentially provided a folder contents list of sorts.
That said, it appears that the version of PkgToolsBuildOs I'm using will search for the .RGU file in the folder ... when the .DSM file is empty (0 byte).
Cheers,
GSLEON3 said:
Need to use BuildDSM.exe to add the rgu to the package for the old kitchen.
Also make sure the rgu is read only.
Click to expand...
Click to collapse
The RGU does NOT need to be read only...
Is that the extent of YOUR helpful commentary?

[Kitchen]Nike WM6.5 Kitchen HTC Mega packages

Build is 23016
download and extract to a folder with no space maybe Nike_kitchen
Kitchen part 1 base
Kitchen part2 EXT folder and Extra Tools put inside kitchen folder if named Nike_kitchen just put this inside that folder
open Erviuskitchen.exe
press load ROM and choose nike then scroll down and set the keyboard you need and what languages
press Create ROM now wait
when finished just close Erviuskitchen.exe
now goto RELEASE_Nike folder and use the custom_ruu.exe to flash your new rom
In Extra_tools folder I have added some other apps found on XDA
EXT Package maker
Put you OEM package in the EXT Package maker folder then drag and drop it on the EXT_PAckages_rebuilder.exe and you should have a EXT package ready to put in you kitchen.
note that some oem packages you download are separated into 2 folders exsample PACKAGE_MEGA_Album and PACKAGE_MEGA_Album_0409
just drag the PACKAGE_MEGA_Album_0409 (language pack) onto EXT_PAckages_rebuilder.exe and it will a folder called 0409 inside PACKAGE_MEGA_Album
now just drag and drop PACKAGE_MEGA_Album onto EXT_PAckages_rebuilder.exe and you have a finished EXT package with language files inside.
The package will be named appname then followed by the build number of the app
CAB Converter by Jason8
How to use:
open CAB_Converter.exe brows for you cab
then choose cab -> OEM or cab->EXT wait for dosbox to close and you have a new OEM or EXT ready to use.
althought it a good app some cabs don't work
Have questions go here for suport
cabdump it is actualy Package Converter by Ervius
that is in most of the older kitchens and works with most all cabs
dubble click on cabConverter.CMD and follow the instructions in the dos box
you should now have a OEM in the same location as where the cab was located
some links most of them are from development and hacking
Get the newest wm6.5 build here and many other usefull tips
Get the newest wm6.1 build here
porting the newest XIP/SYS here
Change the name in the bootscreen and build date of the rom
Open Ervius kitchen and coose the XIP you are going to modify
now press Xipporterex & rom tool
press find date/Version on\ROM\XIP\
change rom date and rom version press change for bouth and you have a new name in bootscreen and rom is set to new date
Change rom info in settings/Device information
go to Nike_Kitchen\EXT\SHARED\Mods\my mods\files
open mxipupdate_OEMVERSION_100.provxml with notepad
Code:
<wap-provisioningdoc>
<characteristic type="Registry">
<characteristic type="HKLM\Software\OEM">
<parm name="ROMVersion" value="5.2.23016" datatype="string"/>
</characteristic>
<characteristic type="HKLM\Software\OEM">
<parm name="OperatorVersion" value="gullum" datatype="string"/>
</characteristic>
<characteristic type="HKLM\Software\OEM">
<parm name="ROMDate" value="20/08/09" datatype="string"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
change the info to what you want it to be
taking this one too
Why not just take this also
Here are the links of gullum's kitchen, with permission of gullum. (Thanks gullum)
Part 1
Part 2
Have fun
Cool I think I will try next week when I have some more time. Thanks again Gullum!
Hi Gullum...
thanks for sharing your kitchen... i will compare with mine because i dont know why my device does not boot when adding notifications or dialer with build 23016 or superior. With previous builds it boots perfectly.
Thanks again.
PS - by the way which build is your kitchen based: 23016 or 23017... in the post you have 230176
thyogo said:
Hi Gullum...
thanks for sharing your kitchen... i will compare with mine because i dont know why my device does not boot when adding notifications or dialer with build 23016 or superior. With previous builds it boots perfectly.
Thanks again.
PS - by the way which build is your kitchen based: 23016 or 23017... in the post you have 230176
Click to expand...
Click to collapse
sorry big finger or small keyboard it's 23016
Very good kitchen, thanks.
Last week I 've builded my first rom with it, works really easy and fast. Again great work.
One question though where can I remove the shortcuts (in startmenu) to packages/ windows components (like microsoft marketplace) I remove from the rom. Is that in the OEM folder?
Gr8 kitchen
Gr8 work gullum.congrats & thanks for sharing with us.
just wanted to know where,in which folder,do i keep other pkgs or prgrms made by pkg builder.
and how to change the sys boss?
hope u will respond!
again hats off to u for such nice work
Help
Help please
I can't find how to chnage languages and keyboard.
Can you help me?
Great Work
Thx alot for your great work
WELL DONE
Keep it up
Re do links
Can anyone redo the link on the first page as there no working
so i can downnload and start cooking....PLEASE PLEASE PLEASE and one more PLEASE.
Invalid or deleted file.... could someone reupload the files....
Thanks.
Yeah, same here.
Added links on post 4 with permission of gullum.
Thank you Rataplan, and of course, thanks to Gullum.

Categories

Resources