Related
I've jest received from CE Communication service (O2 and T-Mobile official repair center) my MDAII and it has a new ROM:
ROM-Vers. 1.72.01GER
ROM-Date: 03/16/04
Radio-Vers. 1.17
Prot. vers. 1337.28
ExtROM-Vers. 1.72.170
Only improvement is the new Radio, and no trufax in the ExtRom.
Ciao.
are you sure that 1.72 is your radio version? ( and you didn't mix it up with your os version ? )
latest I've seen is 1.14.
Yes I did mix it up with os version, the new radio v. is 1.17
Thanks to notice me the mistake!
Gibbo said:
I've jest received from CE Communication service (O2 and T-Mobile official repair center) my MDAII and it has a new ROM:
ROM-Vers. 1.72.01GER
ROM-Date: 03/16/04
Radio-Vers. 1.17
Prot. vers. 1337.28
ExtROM-Vers. 1.72.170
Only improvement is the new Radio, and no trufax in the ExtRom.
Ciao.
Click to expand...
Click to collapse
hihi..
will u b kind enough to post the ftp for us to download?
cheers
j0shua
How to do!? that's my problem.
I'm Windows habits and I'm lost with command line!
Ciao.
Hi
Where i can get this new Radio Version?
Tnx Steve
I wrote a description howto make a copy of the radio rom here:
http://wiki.xda-developers.com/wiki/HimalayaHowtoCopyRom
hope you understand it. if not, tell me. I may create a simple tool for you to just copy the rom using only your xda.
Radio 1.17 sdradio.img
Have I done it well ?
My question now is how to do the reverse, how to write it back.
I've tried:
psdwrite -3 0 0x03400000 sdradio.img
also: psdwrite sdradio.img
but without "effects"
It has been a my pleasure!
Ciao.
itsme, you are always very helpful!
Setup radio ver.1.17
Thank Gibbo for uploaded file!
I try to install Radio 1.17 sdradio.img in my XDA II anyway but no success
Any idea?
:?:
Re: Setup radio ver.1.17
I've successfully installed 1.17. I've made a Radio_.nbf file so you can use it in normal upgrade process, it is attached.
Use this file at your own risk, backup your ROM to SD before installing!!!
Re: Setup radio ver.1.17
mamaich said:
I've successfully installed 1.17. I've made a Radio_.nbf file so you can use it in normal upgrade process, it is attached.
Use this file at your own risk, backup your ROM to SD before installing!!!
Click to expand...
Click to collapse
Any comparisons to 1.14.00 stack Bro?
Re: Setup radio ver.1.17
[Krueger said:
Dr.Stein]Any comparisons to 1.14.00 stack Bro?
Click to expand...
Click to collapse
I have not found any differences. It has the same problems with data calls like 1.14
Re: Setup radio ver.1.17
mamaich said:
I have not found any differences. It has the same problems with data calls like 1.14
Click to expand...
Click to collapse
Alrighty Bro thanks for the prompt reply.
Guess I will wait until my Xda II's next hard reset or a newer O2 ROM or WM2003SE - whichever comes first.
thanks gibbo for the rom, andthanks to mamaich for posting the nbf.
for those interested, this is how to convert the sd-image to an nbf:
- extract the raw-image from the sd-image
Code:
perl sdtool.pl -ri sdradio.img -wm bin
this will write a file named bin-60000000.nb
- create an empty file of exactly 1 Mbyte:
Code:
dd if=/dev/null of=1m.bin bs=1M seek=1
- create a file of exactly 64 bytes, containing only dashes, by first typing 64 dashes into a file, and then truncating the CRLF at the end with:
Code:
dd if=/dev/null of=64.bin bs=64 seek=1
- then concatenate all together with:
Code:
copy /b 64.bin + bin-60000000.nb + 1m.bin radio_.nba
- then set the header parameters with:
Code:
xda2nbftool -sd PH10 -so Qtek -sl WWE -sv 1.17.00 radio_.nba
- then encrypt it for the upgrade tool with:
Code:
xda2nbftool -x Radio_.nba Radio_.nbf 0x20040306
- dd can be found in cygwin
- sdtool is part of the xda-developers romtools and can be found here
- xda2nbftool can be found here.
extract the raw-image
itsme you're unsurpassable one!
Good news, a new MDAIII is comming to me, but would it be possible do the same as with XDAII/MDAII (extract the image from the device, etc.)?
My be is a stupid question, inasmuch as we still do not have it!
Extended Rom 1.72.170
Could someone please upload the new extended rom 1.72.170 German, too.
thx a lot!
itsme said:
I wrote a description howto make a copy of the radio rom here:
http://wiki.xda-developers.com/wiki/HimalayaHowtoCopyRom
hope you understand it. if not, tell me. I may create a simple tool for you to just copy the rom using only your xda.
Click to expand...
Click to collapse
Itsme, you are unbelievable!!! :mrgreen:
That tool will be great!
Could you please post the content of ExtROM too?
Thanks.
Thanks Gibbo & mamaich
Radio v.1.17 in my device now
Sorry guys,
I havent it any more, jest overwrite it, but nothing more from previus or less of T-M ROM 1.72ENG_beta.
I have only a sd.img but I'm no shore if I done it well and I havent it with me now.
Tomorow I'll see if it's good and I would post it.
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.
Hey all, this would probably be only interesting to those who are receiving 2kb, 160x120 MMS messages. Using TMO-USA as an example, the X10 received large MMS images with 1.6, but I'm guessing it doesn't recognize the uaprofile of 2.1 and now are getting tiny mms images. This could also help others on other networks that have the same problem.
Cyanogenmod has an option to switch the profile. Someone else on XDA has posted some of the changes, and those can be found here.
I'm thinking that since I don't think we can compile a new mms.apk, maybe it's possible to edit the current mms.apk with the uaprofile from a different phone (probably the t717/equinox for the tmo users)? Hopefully it's not encrypted or anything either...
So off I go into root explorer and I can't find any mms.apk in my x10. hmm, so i adb shell into it and still no mms.apk. I can't get too far if I can't find the mms application, lol.
so does anyone know what SE uses for mms? or if I'm just simply not seeing it?
obviously, i'm new to working with android, i'll pick up more as time goes on thanks for any help!
Bah! Just in case anyone else looks, I think I found it... sigh.
I searched through the /data/data/ folder and found a reference to 'ericssson' (part of what would be the normal uaprofile text) in com.sonyericsson.converstations_preferences.xml... converstations, eh? makes sense... and yes, there's a converstations.apk
so far i've unzipped it and found 'mms_config.xml' that has max file size and dimensions... but i think this might be only for outgoing mms...
I could be wrong, but isn't it conversations.apk
EDIT: nevermind, looks like you already found it lol
Curious
Thanks for trying to work on it. I would love to have a fix to these small picture messages on T-mo US. But is it possible that the small picture sizes have something to do with T-mo's services somehow???
motibbs96 said:
Thanks for trying to work on it. I would love to have a fix to these small picture messages on T-mo US. But is it possible that the small picture sizes have something to do with T-mo's services somehow???
Click to expand...
Click to collapse
It was working fine with 1.6 but when the X10 jumped up to 2.1, mms images were small. So to me, that means that the tmobile no longer recognizes the phone and it goes automatically downsizing all incoming images.
What I'm not sure is if TMO checks the url of the phone's uaprof or if it just looks at the url and just checks it against their own database. I'm thinking the latter.
Another thought might be if TMO just looks at the specs that the phone gives. The reason for this last question is because X10 1.6 had a max size of 640x480 (not sure if this was receiving or sending) at 1 meg (tmo only handles 300k max). with X10 2.1, it states a max size of 1600x1200 and a max size of 1 meg. Maybe it thinks 1600x1200 is too big and it hits some trigger on TMO's side to only send the fallback size (160x120)
I would recommend emailing customer service (and for anyone else having the same issue with their respective provider) and seeing if they can add the uaprof of the x10i (url) to their database. I know this UAprof is from the v24 update. I'm not sure if it's any different for the DT update or the first 2.1 update. It's not a permanent solution but it's all we have for now.
I thought I'd also post an update, in case if anyone has any thoughts on what I might be doing wrong or helpful tips.
I searched the entire system directory for any text within the files that might relate to uaprof or udp or anything like that. Nothing. I think in 'normal' Android builds have a mm_property.conf file where we can change the uaprof info. So for now, I'm concentrating on converstations.apk and that specific file isn't located there (or anywhere). SE has to store this info somewhere so I think it's in a different conf file. But for the hell of it, I did a hex search for anything that might be related to uaprof (just in case a text search missed something). Again, nothing.
SE encrypted converstations.apk. So if it's in there somewhere, we have to decrypt it first. I'm looking into and reading on decrypting and repackaging the apk. Seems easy enough - I just need to learn a little more.
APN Settings
Name: T-Mobile US
APN: epc.tmobile.com
Proxy: 216.155.165.050
Port: 8080
Username: (leave this blank)
Password: (leave this blank)
Server: (leave this blank)
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MMS Proxy: 216.155.165.050
MMS Port: 8080
MMS Protocol: WAP 2.0 (don't know if this is important)
MCC: 310
MNC: 260
APN Type: (leave this blank)
To create APN settings for your Xperia.
1. Go to 'Settings'
2. Select 'Wireless & networks'
3. Browse down to 'Mobile networks'
4. Browse down to 'Access Point Names'
5. Click the Menu (Left) button
6. Select 'New APN'
7. Key in the detail relating to your provider or carrier
8. Then press the radio button to select it
9. Save settings, reboot phone.
To test your network dial the following on your phone dial keypad to get into test mode: *#*#4636#*#*
Thanks for the help, but the issue isn't an APN setting. Just for giggles, I went ahead and changed the default APN settings to this and can confirm that it still receives small images.
So far I've decompiled the apk but haven't found the settings I need to change
Alright. So I've *properly* decompiled the apk (I'm working on the newest X10i build, v435). It references the UXprof url from framework-res.apk. I found where the url is in that file and changed it to the url for the Tmobile G2 (just to see if that change will work). Unfortunately, I need to recompile framework-res.apk and from everything I've read, it's recommended not to do that.
I'll keep on reading to see if I can do it, but has anyone recompiled framework-res.apk for the x10?
totalundone said:
Alright. So I've *properly* decompiled the apk (I'm working on the newest X10i build, v435). It references the UXprof url from framework-res.apk. I found where the url is in that file and changed it to the url for the Tmobile G2 (just to see if that change will work). Unfortunately, I need to recompile framework-res.apk and from everything I've read, it's recommended not to do that.
I'll keep on reading to see if I can do it, but has anyone recompiled framework-res.apk for the x10?
Click to expand...
Click to collapse
I've dealt with framework-res.apk before. It was just to add the Super Circle Battery, but I can tell you what works.
Compiling the APK seems to encrypt the XML files one by one. If you change any of the resources (like adding images), then you also need to compile a new resources.asrc. Fortunately, since it's a system file, you don't need to sign the APK.
Check this thread for lots of good info on modifying framework-res.apk (thanks to _calum_ and MrRusch):
http://forum.xda-developers.com/showthread.php?t=834806
Important points:
- The XML files and resources.asrc need to be compiled.
- The APK doesn't need to be signed.
- You can compile the XML and resources.asrc with APK Manager, then extract them from the "unsigned" APK it creates, and then reinsert them into a copy of the original APK using WinRAR (or your favorite zip tool).
- Compression should be set to "store" (a.k.a. no compression).
Be sure to have a backup copy of your original framework-res.apk. It's best to leave a copy on your SD card somewhere.
Be careful when replacing framework-res.apk. Copying it with Root Explorer isn't a good idea. I think the permissions get screwed up or something, and you don't have time to change it because it reboots right away. It's better to copy it onto your SD card and use the dd command through ADB.
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
Click to expand...
Click to collapse
If you mess up, then you may not be able to boot the phone. Don't panic. ADB is still available even when it hasn't booted yet, so just use dd to replace it with your old one.
wow, i never would've thought the picture sizes had to do with my phone. hope you find a fix for this!
Thanks Grospolina! That info should help me a lot.
I actually tried to use root explorer at first... LOL. Stuck at the SE screen and I thought I bricked the phone but found out that my USB port on the monitor has quit working... Wasted a couple hours there. Sigh, lol.
I was using apktool since it's supposed to be framework-res.apk friendly but it kept on compressing the apk. I tried to adb push the file but it kept on saying I didn't have permissions. So I ended up using xrecovery to 'restore' the file in update.zip. I did a test mms but it was still small so I went ahead an cleared the davlik cache. I checked the file size of the modified framework-res.apk but either clearing the cache brought the original apk back or xrecovery update didn't work because the file size was the same as the original (apktools shrunk it down to nearly half).
anyways, I'll try it with that adb line.
There is one issue though. If I open up the original framework-res.apk file in 7zip, the file I need to edit doesn't appear. I'll try this but am not sure what to do if the xml file I need to replace doesn't appear.
bah, i can't ever get adb to replace a file. it always says that it's not writeable and then when i get su permission set, some other error happens. I'll figure it out... still reading... typical adb newbie issue, haha.
I don't have enough time right now (or in the next day) to keep on working on this but if anyone on tmobile usa with an xperia x10 wants to give it a shot, I've linked the apk below. The only change I've done so far is change a couple lines in style.xml. I'm not sure this is it for sure, but I can't rule it out yet.
sorry not trying to be rude or nething but i think you should say that this post is about the picture size...cuz a lot of times iv noticed that when you flash it erases your apn settings which is what you need to receive mms messeges in in the first place... just a thought
No offense taken!
I edited the title to reflect that it's to fix incoming picture mms size.
I hope you don't take offense, but this ISN'T an APN settings issue. I explained it several times earlier and it's been brought up before. It's a problem that been mitigated with custom roms because they have the ability to change their uaprof to something the network recognizes.
Several networks, one of which includes TMobile USA, default to a MMS picture size of 160x120 if it doesn't recognize the phone. This project's intention is to change the default uaprof in order for Tmobile USA (and eventually any other providers) to a uaprof of a supported handset.
mms - framework-res.apk - custom
I was totally on the wrong track with APN settings. Admit I saw MMS and jumped the gun without searching on anything. Had just been through all the baseband compatibility issues and APN setting seemed related
http://forum.xda-developers.com/showthread.php?t=830102 - theeedy - good job working with the settings on the Semc Camera Application, related in the compression of images taken by the default camera.
http://forum.xda-developers.com/attachment.php?attachmentid=355818&d=1278461264
This is MMS.apk - it's an interesting modification, couldn't find it easily within my phone.. decompiling it broke with Unknown Resources, which of course is referencing - /system/framework/framework-res.apk
I think it's related to someone's custom Framework-res.apk and used the default Android MMS app for ease of modifications. I'd say that could be the way to go about this and using the Android SDK in Eclipse or Netbeans is probably the right track.. not APN settings... sheesh! - Grospolina is on the money
package="com.android.mms"
Here are permission sections - might make sense..
Code:
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.RECEIVE_MMS" />
<uses-permission android:name="android.permission.SEND_SMS" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_SMS" />
<uses-permission android:name="android.permission.WRITE_SMS" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.CHANGE_NETWORK_STATE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_DRM" />
<uses-permission android:name="com.sonyericsson.android.permission.SEMC_BACKUP_SERVICE" />
<uses-permission android:name="com.sonyericsson.android.permission.SEMC_CUSTOM_SETTINGS" />
<uses-permission android:name="android.permission.RECEIVE_WAP_PUSH" />
<uses-permission android:name="com.android.mms.wap.permission.READ_PUSH" />
<uses-permission android:name="com.android.mms.wap.permission.WRITE_PUSH" />
<permission android:name="com.android.mms.wap.permission.READ_PUSH" android:protectionLevel="signatureOrSystem" />
<permission android:name="com.android.mms.wap.permission.WRITE_PUSH" android:protectionLevel="signatureOrSystem" />
Now your creating your own Framework-res, you need to know the parts that your looking for and what to do with them.. roughly..
Code:
<service android:name="MmsService" android:permission="com.sonyericsson.android.permission.SEMC_CUSTOM_SETTINGS">
<intent-filter>
<action android:name="com.android.mms.MMS_CUSTOM" />
<action android:name="com.android.mms.MMS_SERVICE" />
</intent-filter>
</service>
From here you can define the properties that you need in the RES layout.. you need something along the lines of this in a file called - image_attachment_view.xml - which would define the image properties you are discussing.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<com.android.mms.ui.ImageAttachmentView android:gravity="center_vertical" android:orientation="horizontal" android:id="@id/image_attachment_view" android:background="@drawable/attachment_editor_bg" android:paddingRight="5.0dip" android:layout_width="fill_parent" android:layout_height="wrap_content"
xmlns:android="http://schemas.android.com/apk/res/android">
<ImageView android:id="@id/image_content" android:layout_width="fill_parent" android:layout_height="150.0dip" android:layout_weight="1.0" />
<LinearLayout android:orientation="vertical" android:layout_width="wrap_content" android:layout_height="wrap_content">
<Button android:id="@id/view_image_button" android:layout_width="100.0dip" android:layout_height="50.0dip" android:text="@string/view" style="\?android:attr/buttonStyleSmall" />
<Button android:id="@id/replace_image_button" android:layout_width="100.0dip" android:layout_height="50.0dip" android:text="@string/replace" style="\?android:attr/buttonStyleSmall" />
<Button android:id="@id/remove_image_button" android:layout_width="100.0dip" android:layout_height="50.0dip" android:text="@string/remove" style="\?android:attr/buttonStyleSmall" />
</LinearLayout>
</com.android.mms.ui.ImageAttachmentView>
EDIT: There are also some better MMS applications out there.. before reinventing the wheel perhaps a bit of window shopping?
No problem! Thanks for the info MrHassell. I enjoy reading your posts (chop full of interesting info, haha)
I'll definitely look into your tips there! SE mucked around with the messaging and they don't use mms.apk but conversations.apk. After decompiling conversations.apk, it references outside of converstions.apk (I'm 95% sure of that) for the uaprof. This (I think) makes sense in that the system needs to tell the network its uaprof.
Other MMS applications depend on this system uaprof to receive images and they too, receive small images. Custom roms get around this because they allow changing the uaprof. However, since SE changed the location of some of the interesting strings, I haven't been able to use AOSP or anything like that as a template to find the strings specifically.
I could use a custom rom, but I'm waiting until a stable, feature filled one is available without having to download X, Y, and Z to get features to work. I like messing with my phone but don't want to mess around with an entire rom (yet, I already did that with a Samsung i7500, lol).
So far, the interesting lines (2) is in framework-res.apk. /res/values/strings.xml
>> <string name="config_useragentprofile_url">http://wap.sonyericsson.com/UAprof/%R202.xml</string> (something like this) and h ttp://wap.sonyericsson.com/UAprof/%R101.xml
Which I changed to
>> <string name="config_useragentprofile_url">http://www.htcmms.com.tw/Android/TMO/Hero/ua-profile.xml</string>
Which is the uaprof for the Tmobile G2.
And just for background...
How I think this all works (if anyone works for tmobile usa and knows, please correct me!)
Phone connects to the network OR when the phone receives an MMS
Advertises it's uaprof capabilities to the network
Network looks at the url and either:
goes to the url and assigns those capbilities to that registered phone
or
looks at the url and looks for that url in a local database. Network finds info and assigns MMS values OR doesn't find it and assigns default 160x120 values. Doesn't go to the internet to find those values.
The X10 worked under 1.6. Why? It was rumored to come to the USA and 1.6 would have had the uaprof on their database for testing reasons. 2.1 comes and TMobile USA has already decided not to carry it so they don't add the new url to their database.
totalundone said:
bah, i can't ever get adb to replace a file. it always says that it's not writeable and then when i get su permission set, some other error happens. I'll figure it out... still reading... typical adb newbie issue, haha.
Click to expand...
Click to collapse
The /system directory is read-only by default. You need to mount it as read/write:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
Click to expand...
Click to collapse
If that doesn't work, you could try this:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
exit
exit
Click to expand...
Click to collapse
Also, don't forget to check your phone for a "SuperUser" popup and allow it. In the SuperUser app, this shows up as "Unknown".
Thanks again Grospolina!
Evidently I didn't have it approved by superuser. I thought I did... but forgot that I lost it when I had to reflash a few days ago.
I tried the new framework-res.apk. It didn't crash my phone and it was the new size! unfortunately incoming mms photo sizes are still 160x120 max.
Well... I guess I need to get back to searching ...
just want to say thank you for looking into this. i really want to have the mms picture issues worked out.
thanks again
well my policy I share what I learn
Several friends have asked me how to do it to not be sending pm to give the public preferred time for all to their own kitchens roms
Step 1 CHOOSE the item you want to leave the default
I Elected
CRYSTAL CM7 Theme by DaRk_dOg
step 2
apktool use to decompile and know the command line to add in the build.prop
ejmplo
copy the apk where is the apktool
C: \ Crystal.apk
go to cmd type the following command
cd ..
cd ..
apktool if Crystal.apk
apktool d Crystal.apk (decompile)
step 3
see the lines that nesesitamos for build.prop
go to
C: \ Crystal \ AndroidManifest.xml (use notepad + + to see the lines you need)
and find the following lines
PHP:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:hasCode="false" android:versionCode="44" android:versionName="2.5" package="com.darkdog.theme.crystal"
xmlns:android="http://schemas.android.com/apk/res/android" xmlns:pluto="http://www.w3.org/2001/pluto.html">
<application android:label="@string/theme_name" android:icon="@drawable/icon" android:hasCode="false" />
<uses-feature android:name="com.tmobile.software.themes" />
<uses-sdk android:minSdkVersion="9" android:targetSdkVersion="9" />
<theme pluto:themeId="Crystal" pluto:styleId="@style/Crystal" pluto:name="@string/theme_name" pluto:preview="@drawable/preview" pluto:author="@string/author" pluto:copyright="@string/copyright" pluto:wallpaperImage="@drawable/wallpaper" pluto:styleName="@string/style_appearance_name" pluto:ringtoneName="Shocking" pluto:ringtoneFileName="media/audio/ringtones/Shocking.mp3" pluto:notificationRingtoneName="Teleport" pluto:notificationRingtoneFileName="media/audio/notifications/Teleport.mp3">
<meta-data android:name="com.tmobile.theme.redirections" android:resource="@xml/redirections" />
</theme>
</manifest>
PHP:
package="com.darkdog.theme.crystal
pluto:themeId="Crystal""
PHP:
#Theme
persist.sys.themeId=
persist.sys.themePackageName=
and get something like this in bulid.prop
PHP:
#Theme
persist.sys.themeId=Crystal
persist.sys.themePackageName=com.darkdog.theme.crystal
I hope it serves
Bro,
appreciate your work. but i dont understand what you have done in the above.
is it a theme extract from a rom? pls provide little information.
(its ok, even if you know little english just post some info)
Thank you!
Tommylee567 said:
Bro,
appreciate your work. but i dont understand what you have done in the above.
is it a theme extract from a rom? pls provide little information.
(its ok, even if you know little english just post some info)
Thank you!
Click to expand...
Click to collapse
is to use a default theme in the rom without using theme choose
Sent from my U20i using xda premium