SHAROBALO
JF-Expert Member
- Mar 17, 2011
- 771
- 349
Halow JF
KUANZIA TAREHE 23/JUNE WALE JAMAA WA SYMBIANSIGNED WAMEBADILISHA SITE YAO SO HAWATATOA .cer na .key ANYMOREEEEEE
SO HUTAWEZA KU HACK SIMU TENA..KAMA ULISHAWAHI KUPATA .CER NA .KEY ITUNZE VIZURI KWANI BADO UTAWEZA KUTUMIA...HADI HAPO ITAKAPO EXPIRE BAADA YA MIAKA MITATU...KWA WATAO NUNUA SIMU MPYA....JUA KUWA HUTAWEZA KUCHAKACHUA....REALLY BAD NEWS...NAFIKIRIA NIAHAMIE KWENYE SIMU GANI....
Due to changes to the SymbianSigned website, ALL THE DEVCERTS issued after 23/June can be only used to sign apps which UID belongs to the unprotected-range: 0xE0000000-0xEFFFFFFF
In brief... if you've obtained a DevCert after the 23/June (despite by the website you used to get it) then:
- You can't sign any .sis app (or .sis mod), but only those (few) which UID belongs to the unprotected-range (eg: RP+ Lite Version and HelloOX 2.03)
- You can't hack anymore the phone using HelloOX 2.11 or JustHackIt! (because it contains an embedded .sis which UID is not in the unprotected-range)
- You can still hack it using HelloOX 2.03 (if your phone is supported)
- You can still hack it using a modded UDA (valid for ALL the devices)
The way I prefeer is to create an hacked UDA by adding the *.ldd files only... Then sign (using a DevCert) and install RP+ Lite Version (it can be signed using the new DevCerts too)
Doing in this way, if you don't apply any patches, you can be sure that the phone will behave exactly as the original, because all components are 100% original, no component is permanently replaced...
And when you want to change the behaviour from "vanilla" to "hacked", you just need to apply the included installserver and open4all patches.
You can even put them in "auto" if you need to use the phone as "hacked" for most of time.
POLENI SANA WANA SYMBIAN WENZANGU...NOKIA WAMEAMUA KUTUCHINJIA BAHARINI..
SOURCE::: About new DevCert issued since 23/June
KUANZIA TAREHE 23/JUNE WALE JAMAA WA SYMBIANSIGNED WAMEBADILISHA SITE YAO SO HAWATATOA .cer na .key ANYMOREEEEEE
SO HUTAWEZA KU HACK SIMU TENA..KAMA ULISHAWAHI KUPATA .CER NA .KEY ITUNZE VIZURI KWANI BADO UTAWEZA KUTUMIA...HADI HAPO ITAKAPO EXPIRE BAADA YA MIAKA MITATU...KWA WATAO NUNUA SIMU MPYA....JUA KUWA HUTAWEZA KUCHAKACHUA....REALLY BAD NEWS...NAFIKIRIA NIAHAMIE KWENYE SIMU GANI....
Due to changes to the SymbianSigned website, ALL THE DEVCERTS issued after 23/June can be only used to sign apps which UID belongs to the unprotected-range: 0xE0000000-0xEFFFFFFF
In brief... if you've obtained a DevCert after the 23/June (despite by the website you used to get it) then:
- You can't sign any .sis app (or .sis mod), but only those (few) which UID belongs to the unprotected-range (eg: RP+ Lite Version and HelloOX 2.03)
- You can't hack anymore the phone using HelloOX 2.11 or JustHackIt! (because it contains an embedded .sis which UID is not in the unprotected-range)
- You can still hack it using HelloOX 2.03 (if your phone is supported)
- You can still hack it using a modded UDA (valid for ALL the devices)
The way I prefeer is to create an hacked UDA by adding the *.ldd files only... Then sign (using a DevCert) and install RP+ Lite Version (it can be signed using the new DevCerts too)
Doing in this way, if you don't apply any patches, you can be sure that the phone will behave exactly as the original, because all components are 100% original, no component is permanently replaced...
And when you want to change the behaviour from "vanilla" to "hacked", you just need to apply the included installserver and open4all patches.
You can even put them in "auto" if you need to use the phone as "hacked" for most of time.
POLENI SANA WANA SYMBIAN WENZANGU...NOKIA WAMEAMUA KUTUCHINJIA BAHARINI..
SOURCE::: About new DevCert issued since 23/June
