nazalost za sada kao sto vidim da nece biti svako srecan da moze videti sve faljove u telefonu jer nece moci svako da hackuje Freware

Razbijena je i zastita Signovanje za OS 9.x   

Didn't find on searchin USEFUL INFO SO POSTIN FOR OTHER MEMBERS TOO.

Can anyone check this out and tell us its really true

Here is some breaking news for Nokia S60 mobile users. The very much frustrating Symbian Signed security platform v9.2 has been exposed to hacks. No longer do you need to use tools such as SignSIS & DevCertRequestControl to get a certificate for installing applications. Users can now bypass the Symbian Signed certification check and install any unsigned or self-signed applications or software.

When installing native Symbian OS packages (.SISX files) onto a Nokia S60 mobile device, the code performing the installation (the Software Installer, sometimes referred to as SWI) first reads the settings in a policy file in the ROM (swipolicy.ini) to determine how the installation should proceed. Swipolicy.ini is configured by a device manufacturer prior to device shipping. On a phone, swipolicy.ini is located in z:\system\data\.

This hack involves modifying the swipolicy.ini in the ROM image when you do a firmware upgrade using a HEX Editor and then re-flashing the device with the altered permissions. You can read all about it at the Symbaali blog.

Important Note: This hack is not for the faint hearted and is known to brick a few models that perform a CRC check. Anything that you do following the article below is at your own risk and responsibility.

+ First update your S60 mobile phone using the software update tool.

+ It will download the binary image to C:\Documents and Settings\All Users\Application Data\Nokia\Nokia Service Layer\A\nsl_service_module_00001\http://www.dsut.online.nokia.com.oti...s\P honemodel

+ Open the ROM image in a HEX editor such as WinHex

+ For Java J2ME midlets, look for the following text/string (can be found using search string midp2_rp.xpf near offset 0×2310000):

# midp2_rp.xpf
# Copyright (c) 2004-2005 By Symbian Software Ltd. All rights reserved.
# This file defines one possible interpretation of the MIDP2 Security RP security policy,
# but with a JTWIr1 compliant policy for untrusted MIDlet suites

FormatVersion: 1.0

# MIDlets in untrusted MIDlet suites need user permission before doing anything
DomainBindings: [UNTRUSTED]

FunctionGroupBinding: “Application Auto Invocation”
Permission: User
DefaultMode: Session
MaximumMode: Session
EndFunctionGroupBinding

FunctionGroupBinding: “Landmark”
Permission: User
DefaultMode: Session
MaximumMode: Session
EndFunctionGroupBinding
[…]

+ Change MaximumMode field for each permission you want to add such as Application Auto Invocation, Landmark, Local Connectivity, Messaging, etc to Blanket. If you want, you can also change the DefaultMode to Blanket and save the image.

+ Now run the software update again and it should re-flash the S60 device with your new, unrestricted permissions. You can test if the hack was successful by installing a Java J2ME midlet. You should see more permission options in the application manager (Select the midlet and Click Open).

+ For Nokia S60 SISX files, locate the swipolicy.ini in the ROM image (can be found using search string UserCapabilities, near offset offset 28251550):

AllowUnsigned = false
MandatePolicies = false
MandateCodeSigningExtension = false
Oid = 1.2.3.4.5.6
Oid = 2.3.4.5.6.7
DRMEnabled = true
DRMIntent = 3
OcspMandatory = false
OcspEnabled = true
AllowGrantUserCapabilities = true
AllowOrphanedOverwrite = true
UserCapabilities = NetworkServices LocalServices ReadUserData WriteUserData UserEnvironment
AllowPackagePropagate = true
SISCompatibleIfNoTargetDevices = false
RunWaitTimeoutSeconds = 600
AllowRunOnInstallUninstall = false
DeletePreinstalledFilesOnUnins tall = true
AlternativeCodeSigningOID = 1.3.6.1.4.1.94.1.49.1.2.2.1 1.3.6.1.4.1.94.1.49.1.2.2.5
PhoneTsyName = phonetsy

+ Next you need to download a free dd tool for windows such as one from here

+ Then extract the original text using dd by running the following command:

dd if=phonemodel.C01 of=filename.txt skip=28251550 bs=1 count=648

+ Remember to replace if, skip and count variables with the values of your own ROM image. The count variable is the size of the swipolicy.ini in your flash ROM image starting from AllowUnsigned till phonetsy.

+ Open the filename.txt and edit the UserCapabilities with

AllFiles DiskAdmin NetworkServices LocalServices ReadUserData WriteUserData ReadDeviceData WriteDeviceData UserEnvironment PowerMgmt MultimediaDD TrustedUI ProtServ NetworkControl SwEvent Location SurroundingsDD CommDD

As per one of the comments, you can also set UserCapabilities = All to include the full capability-set.

Ensure that the swipolicy.ini fragment matches the original byte count size that you had earlier. If it is more in size, you may have to remove some non-important attribute such as Oid = 1.2.3.4.5.6 at your own risk to ensure that the byte count matches. Hint: check the size of filename.txt in Windows explorer before importing.

+ Import the filename.txt back into the ROM image by running the following command:

dd if=filename.txt of=phonemodel.C01 seek=28251550 bs=1 count=648

Again remember to replace the of, seek and count variables for your ROM.

+ Now re-flash your mobile phone with NSU as you did earlier. You will find more functionalities that you don’t even get with a developer certificate.

After your phone is unlocked, you can add the AllFiles capability to Y-Browser that enables you to browse and view system and private files on your smartphone’s mobile file system.

Dok mi neko ne potvrdi da radi i ne da graficki prikaz korak po korak, ja ne diram nista 

Ti mozes Prvi da ovo uradis jer si upucen u programiranju ,,tako da ovo bice lako za tebe da ovo uradis ,,ali nije problem da sacekas sa slikovite prikaze

Pa nije bas toliko upucen u programiranju jer za ovo mu treba "graficki prikaz korak po korak" 

Cela fora u ovo razbijanje je u firmware Verzija  to ti je reprogramiranje pre flesanje (ubacivanje firmware verzija) Rasturis firmware i sa ove sifre,slova i brojeve promenis i se oslobodis od svu zastitu na Telefonu ,a za ovakvo nesto Programere najvise znaju X3mE se razume oko programiranje ,e sada kad bi imao neki slikovit Tutorijal korak po korak ja bi prvi ovo isprobao na moju N95

Mislis firmware, a ne "freware"?
Treba da znas da koristis HEX editor, uradis update softa i trazis u datom folderu ROM image kojeg editujes sa HEX editorom i dd tool-om (kod kojeg si propustio link kada si uradio copy/paste u tom uputsvu).
Treba da se skine zastita za java midlete i za  SISX fajlove.
I ponovo da se fleshuje telefon sa modifikovanim firmware-om.
Ja mislim da ce uskoro ljudi objaviti hackovane verzije firmware-a za vecina modela, koje cete skinuti i samo uraditi replace postojeceg fajla od normanog update koji kazu da se nalazi ovde:
C:\Documents and Settings\All Users\Application Data\Nokia\Nokia Service Layer\A\nsl_service_module_00001\http://www.dsut.online.nokia.com.oti...s\P honemodel
To bi bilo najsigurniji nacin.

normalno das sam mislio na firmware malo sam brzao oko pisanje pa sam ispustio ,,,tacno je da ce imati gotove firmware ali ces morati da flesujes sa Boksom ili sa Phoenix  opciju to sto kazu da je u C:\Documents and Settings\All Users\Application Data\Nokia\Nokia Service Layer\A\nsl_service_module_00001\http://www.dsut.online.nokia.com.oti...s\P honemodel to se desava kada radis Update jer prvin fajl ide tu a onda na telefon

U principu koliko sam ja shvatio ovaj tutorial sto si ti postovao ne treba ti Boks ili  Phoenix jer NSU cuva fajlove u taj folder i znam iz licnog iskustva da NSU kada jednom skine update i flashujes fon, drugi put ako hoces ponovo da fleshujes telefon, NSU proverava preko interneta da li postoji novija verzija firmwarea od one sto je vec skinuo i ako nema ne skida je ponovo sa interneta nego koristi onu sto je vec skinuo i sacuvao u onom folderu.
Tu caku koriste za ovaj hack, pa zato kazu da uradis prvo update firmwarea.

Ok ,ako si ti dobro svatio caku mogao i da isprobas