Ay one have idea how we can open (tsw) file? I try to trasnform to (bin) file then open with a lot of diferent tool but all of them says it's not a orijinal bin file you can't open.
if you search a little bit, you'll see that it is a tool developed by cotulla, that transforms the .tsw file into .bin
ady_uaic said:
if you search a little bit, you'll see that it is a tool developed by cotulla, that transforms the .tsw file into .bin
Click to expand...
Click to collapse
And if you try this tool you go to see is not working.
You transform in bin who is not bin file. So that tool from cotula is the big XXX.
Who said that Toshiba's bin files are similar to htc ones ?
It's a bin file that contains whole system part drivers bootloader and other things with crc checks etc... Cotulla made a decrypter for TSW files now someone need to write tool that will be able to decompress all rom parts and then compress them back to bin file in TG01 format
who know the latest news about TG01 unlock?(japanese device T01A)
who know the latest news about TG01 unlock?(japanese device T01A)
I am confused and want the good news.
yes, i agree with you @nico101. the files are .bin, but the "composition" of those files is different than the ones from htc devices, for ex.
in this case, can you tell me (us) if, with this gps gate, you lose or not the signal, for 1-2 seconds when you drive, or when you walk?
Wait, guys, so all we need is a decompresser for the files?
I think yes.
TG01
bojan6 said:
I think yes.
Click to expand...
Click to collapse
I think we you might need to request a programmer who knows how to decompress files on your wmpoweruser home page wen, and sticky on homepage of xda developers to grab peoples attention!!
we need a hacker to figure layout of .bin file as i said before if some one figures out things i would probably be able to write the programs.
the .bin file is not encrypted or compressed but it contains more files, it is analogue to HTC .nbh file
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
00115498 , \Recovered File 03.png
00115530 , \Recovered File 04.png
00115533 , \Recovered File 05.png
00115563 , \Recovered File 06.png
00115791 , \Recovered File 07.cab
00115962 , \Recovered File 08.gz
00116325 , \Recovered File 09.png
00116351 , \Recovered File 10.cab
00116354 , \Recovered File 11.cab
00116385 , \Recovered File 12.cab
00116391 , \Recovered File 13.cab
00116417 , \Recovered File 14.png
00116420 , \Recovered File 15.png
00116421 , \Recovered File 16.gif
That is inside the bin file.
And here is reply from Cotulla:
"Seems you need decrypt TSW image to BIN and then encrypt it back to TSW.
BIN image have complex format with header and many parts.
Obviously we need exclude all stuffs except OS.
The main problem to test this - I am not sure if we put wrong image, it won't brick device...
-Cotulla"
bojan6 said:
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
00115498 , \Recovered File 03.png
00115530 , \Recovered File 04.png
00115533 , \Recovered File 05.png
00115563 , \Recovered File 06.png
00115791 , \Recovered File 07.cab
00115962 , \Recovered File 08.gz
00116325 , \Recovered File 09.png
00116351 , \Recovered File 10.cab
00116354 , \Recovered File 11.cab
00116385 , \Recovered File 12.cab
00116391 , \Recovered File 13.cab
00116417 , \Recovered File 14.png
00116420 , \Recovered File 15.png
00116421 , \Recovered File 16.gif
That is inside the bin file.
Click to expand...
Click to collapse
Got the same result with Isobuster.
I will now extract these files and look if there could be something done with them.
That is the result from Isobuster but no chance to extract them. Try if you can good. The furst one is the OS, there are some photo and I think other from provider to.
Well I get these files out of the .bin extracted.
But...I cannot extract for example the .cab files ...it tells me that they're damaged...all of them.
DunkDream said:
Well I get these files out of the .bin extracted.
But...I cannot extract for example the .cab files ...it tells me that they're damaged...all of them.
Click to expand...
Click to collapse
You try to open them?
I can open some of the archives.
For example I got a file named _setup.xml
That file contains:
- <wap-provisioningdoc>
- <characteristic type="CM_Networks">
<nocharacteristic type="Bouygtel GPRS" />
</characteristic>
- <characteristic type="CM_Networks">
<nocharacteristic type="MMS BOUYGUES" />
</characteristic>
- <characteristic type="CM_GPRSEntries">
<nocharacteristic type="Bouygtel GPRS" />
</characteristic>
- <characteristic type="CM_GPRSEntries">
<nocharacteristic type="Bouygtel GPRS2" />
</characteristic>
- <characteristic type="CM_GPRSEntries">
<nocharacteristic type="MMS BOUYGUES" />
</characteristic>
- <characteristic type="CM_ProxyEntries">
<nocharacteristic type="HTTP" />
</characteristic>
- <characteristic type="CM_ProxyEntries">
<nocharacteristic type="HTTP-{0DAEA92E-2917-4C6C-9E23-F2BCAA13DA07}" />
</characteristic>
- <characteristic type="CM_ProxyEntries">
<nocharacteristic type="null-corp" />
</characteristic>
- <characteristic type="Registry">
<nocharacteristic type="HKLM\SOFTWARE\ArcSoft\ArcSoft MMS UA\Config\mm1\MMSCSetting\SampleMMSC" />
</characteristic>
</wap-provisioningdoc>
I now tried to open the .bin file with an binary editor
You find the screenshot attached.
There is a text written:
Image file with header
C:\M8650\AMSS\products\8650\build\ms\bin\SDCAOPZ\FactoryImageTG01W.bin
msm=Q8650
flash_device = toshiba_tg_01
flash_id=0x9
And so on...Just look at the screenshot!
And that file is huge! I'll look if there are more information I can get.
I think we need just the furst two file.
00003808 , \Recovered File 01.mov
00112925 , \Recovered File 02.gz
The others are about providers..
This two files are the OS. we need to unpack(open, decompress or bla bla..)them.
If you extracted them tell me how you did it?
without much introduction, the fruit of my labor: tgtool.exe
it will dump parts of .tsw or unencrypted .bin files.
you need bepe's xidump to dump xip and imgfs
this is still alpha code
use example:
tgtool TG01WP_5005000167.tsw
xidump -b TG01WP_5005000167.09
xidump -b TG01WP_5005000167.10
Related
Dear all
Where can download ATOM WM6 Kitchen software,thanks!
sanjian said:
Dear all
Where can download ATOM WM6 Kitchen software,thanks!
Click to expand...
Click to collapse
jiggs dont release a kitchen, sorry for my mistake, he have explained to someone about this,.
i'll upload in the sticky thread the kitchen,. (to mediafire)
please wait, thanks,.
kumara
Thanks reply!
I use ATOM LIFE kitchen software,and i changer same command,but problem which default.hv and user.hv file,this file is empty,can you help me,thanks!
Note:
I think this problem which software XIP folder file,but i copy all file from my rom XIP file same problem.please help ,thanks!
Look this picture:
default.hv file only 44Kb,but right is 688Kb
user.hv file only 28Kb,but right is 72Kb
sanjian said:
Look this picture:
default.hv file only 44Kb,but right is 688Kb
user.hv file only 28Kb,but right is 72Kb
Click to expand...
Click to collapse
try to looak at temp folder (inside your kitchen, beside OEM and SYS folder) then read the log.txt
find in below the error, ususally in the last paragraph, thats mean you have an error with one of your rgu,.
default and user hv, can be build by reading the rgu,.
now, which base rom did you use??
This is log.txt :
Completed successfully
Microsoft (R) RGUComp Version 1.0.000
Registry file processor and hive builder.
Copyright (C) 2004 Microsoft Corporation All Rights Reserved.
built: Nov 19 2004 15:17:13
importing registry file ".\boot.rgu"...
package "MSXIPKernelLTK" does not contain .rgu file "d92a4f0a-378a-4482-8fd3-bd127a05e4de.rgu"
package "SMIME" does not contain .rgu file "8cb4ac12-6bc5-4bda-ab45-539988c36a95.rgu"
package "Bth_A2DP" does not contain .rgu file "6b4ed31c-5ced-41b2-b917-2c006f046a5e.rgu"
package "MediaOS" does not contain .rgu file "ae879543-c73e-4888-812b-d8177c404612.rgu"
package "RUNTIMES" does not contain .rgu file "e658c544-26bf-45ac-a458-2044a5d1e698.rgu"
package "FWUPDATE" does not contain .rgu file "23ba5346-78b8-4436-b7d2-f30712c3cef4.rgu"
package "GPSID" does not contain .rgu file "d13b7447-0248-462a-bba4-d868f31642ed.rgu"
package "WWAN" does not contain .rgu file "77f38251-db87-4e5d-96d9-9e8e35b6dc1d.rgu"
importing registry file ".\Registry\723fb954-d931-4348-b672-82a188e587b5.rgu"...
package "SMS_Providers" does not contain .rgu file "582f7a58-3c50-4301-970a-ed5ec8947692.rgu"
package "BaseAppsFiles" does not contain .rgu file "b04e8c7f-f0f6-4201-83c6-4876404128c9.rgu"
package "MediaOSFiles" does not contain .rgu file "da5e9e89-c2c4-4ff9-ae88-c90a50ec09c9.rgu"
package "Bth_HID" does not contain .rgu file "a492bb92-210b-4933-9a65-272cc8ad9a5b.rgu"
package "NetCF" does not contain .rgu file "38f43c9f-bc38-430e-81d1-a2e6c650f225.rgu"
package "Entertainment" does not contain .rgu file "0cfc3dc0-5fbc-4153-9ce9-72df4d8c2922.rgu"
package "SQLCE" does not contain .rgu file "8a1287c3-da0a-4eb8-8ba7-b70019890abb.rgu"
package "BROWSINGCORE" does not contain .rgu file "d81b11e0-3299-4b65-8305-78f1fa03dc07.rgu"
package "Redist" does not contain .rgu file "208f8be6-1362-45b3-ae17-95d4ab426c11.rgu"
package "Metadata" does not contain .rgu file "034e7cf6-8a37-40ad-85bd-6851b921866a.rgu"
package "Entertainment_DPI_96" does not contain .rgu file "6327354b-cf17-4539-92f4-c590558d3b46.rgu"
package "Redist_dpi_96_resh_240_resv_320" does not contain .rgu file "7a3fc055-392b-4846-acc1-55a34a80db5b.rgu"
package "OS" does not contain .rgu file "d0b41563-b345-4444-aa15-986e7c7fff99.rgu"
package "BROWSING" does not contain .rgu file "b183f2a7-06c3-4f27-9679-7baf97e94efa.rgu"
package "Redist_DPI_96" does not contain .rgu file "a15620ee-f541-454c-99d4-ee268d67e74a.rgu"
package "Browsing_DPI_96" does not contain .rgu file "4091ab29-ebdf-4f28-9f58-a3f3e7495372.rgu"
package "Bluetooth" does not contain .rgu file "25c125d4-0a18-487d-a709-9b4242bbf4c3.rgu"
That's mean do you have based rom without rgu inside...
I only have diskimage_Ver.nb0 file,after dumpfiles can get OEM and SYS and DUMP folder,i'm no changer any thing,direct buildOS,is this problem default and user hv file,thanks!
sanjian said:
I only have diskimage_Ver.nb0 file,after dumpfiles can get OEM and SYS and DUMP folder,i'm no changer any thing,direct buildOS,is this problem default and user hv file,thanks!
Click to expand...
Click to collapse
Do u have .rgu file on your SYS and OEM folder? If yes u must download any others rom. Try jiggs rom 0.7.0a
sanjian said:
I only have diskimage_Ver.nb0 file,after dumpfiles can get OEM and SYS and DUMP folder,i'm no changer any thing,direct buildOS,is this problem default and user hv file,thanks!
Click to expand...
Click to collapse
whose diskimage did you use?
you could try my HTC-Atom diskimage as your base ROM, it have a RGU,.
aLL yo've done is right, so try to work with other diskimage_Ver.nb0,.
gud luck,.
Regards
Kumara
Hi
I use " ATOM WM6 0.7a.0 WWE "this rom try,same problem,after update rom to mobile,stop at "driver default factory......",please help,thanks!
sanjian said:
Hi
I use " ATOM WM6 0.7a.0 WWE "this rom try,same problem,after update rom to mobile,stop at "driver default factory......",please help,thanks!
Click to expand...
Click to collapse
did you add something to your kitchen? OEM? new program? .dll files?
if you had, try to perform g'reloc,.
and tell me, what have you done?
and, please move to Atom WM6 ROM cooking tutorial, so, anybody can learn it,.
thanks,.
mods, i think you could close this thread,.
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 )
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.
how to extract a xip.bin file?
I used xipport and it gived me necessary files: S000, S001 and S002
but these were in binary format. so I could modify these only via hexeditor. is there any way to extract or convert these files?
if we can do this, I will try porting rmnet protocol to clk bootloader