Setool Support

[Kenya Ahyet]

UnlockBox for service SonyEricsson mobile phones with support for SEMC models from A1, A2, ODM, PNX or PDA platforms. Optionally you can also activate the LGtool license for the multibrand Unlock NCK Codes Calculator by IMEI for LG, HTC, Alcatel, Motorola, BlackBerry, Huawei, ZTE, Micromax, Doro, SonyEricsson, Pantech, Avvio, etc...

This item is shipped with the following FULLY FREE material:

Disc entirely developed by our technical department, you will not find in other stores!!

We supply ALL software, drivers and updates needed for the use and installation of the product.

Manuals in PDF format also 100% in Spanish including real screenshots with all steps for the installation.

Videos in Executable format ready for Windows with real processes of use, unlocking, etc...

Some REAL Samples of the Manuals included into our CD/DVD Disks:

Information about dongles, boxes, activationes, licenses, etc...

Generally, the devices connected to a computer, as boxes and dongles, and its licenses, calculators, activations and software, may need permanent and stable internet connection during the usage of processes and functions available on each device.

This is because the protection mechanisms and algorithms are residing on internet servers owned by the device manufacturer and software developer. These mechanisms are necessary to carry out these above mentioned processes and functions.

Our company strives to select products, for our online sales catalog, that are renowned worldwide, with frequent and regular udates, and in many cases, free and at no charge. However, our company is not responsible for the decisions of each particular manufacturer or developer, including without prior advice, such as, the possibility of a not continuity of updates of any of the products, changes in the policy of renewal of licenses, calculators, activations, credits, logs, server status at anytime (online / offline), as well as future functions, upgrades to new versions, etc ... since these aspects are only depending on the manufacturers of mentioned devices and not in our company.

Before You start, it is recommended to install the phone USB drivers. Download it from setool support area, turn on phone without SIM card, and connect phone to computer using DCU-60 (or compatible) USB data cable. Computer will ask for the phone drivers and install the needed communication ports.

4. Now press "Identify" button, then connect the turned-off phone while pressing "c" button. Computer may ask for some USB flashing drivers, then read the phone information. You shold see "Flash CID: 0049", "Network LOCKED" and "RESTORATION FILE PRESENT FOR DETECTED FIRMWARE". (If restoration file not present, download it from support area, then copy it to "rest" folder in the main folder of setool.) Now remove phone from cable, remove then insert battery. Then press "Unlock / Repair" button to start the unlock procedure of the phone.

8. Now setool software will finish the unlock procedure and resets back the user code to "0000". If You see "ACTIVATION COMPLETED..." and "Elapsed... secs." then the unlock procedure finished, the phone unlocked and phone code reseted.

9. Now disconnect phone, remove then insert battery. Check the phone lock status in secret menu, or press "Identify" in setool, then connect phone on USB cable while pressing "c". If "Simlocks: Not detected" appears, that means the phone is unlocked!

It has been presented at large-scale conferences including Blackhat, DerbyCon, Defcon, and ShmooCon. With over two million downloads, it is the standard for social-engineering penetration tests and supported heavily within the security community.

A punching machine works much like a hole punch for paper. With a paper punch, the punch presses the paper against the support of the hole punch and finally into a round opening and the scrap from the punching is collected in the hole punch container.

Machine punching works in the same way. The sheet is positioned between the punch and the die. The punch moves downward and plunges into the die. The edges of the punch and the die move past each other in parallel, cutting the sheet. Observed in detail, the punching process proceeds in four phases.

When the punch moves upward it can pull the sheet with it. In that case, the stripper releases the sheet from the punch. The higher the fraction of cut on the sheet edge, the better the edge quality. For precise fits, for example, preliminary holes are punched and then the final diameter is punched out with a slightly larger tool. The fraction of cut along such an edge is then as high as 100%.

This directory contains the core Android SELinux policy configuration. It defines the domains and types for the AOSP services and apps common to all devices. Device-specific policy should be placed under a separate device///sepolicy subdirectory and linked into the policy build as described below.

Additional, per device, policy files can be added into the policy build. These files should have each line including the final line terminated by a newline character (0x0A). This will allow files to be concatenated and processed whenever the m4(1) macro processor is called by the build process. Adding the newline will also make the intermediate text files easier to read when debugging build failures. The sets of file, service and property contexts files will automatically have a newline inserted between each file as these are common failure points.

BOARD_VENDOR_SEPOLICY_DIRS contains a list of directories to search for additional policy files. Order matters in this list. For example, if you have 2 instances of widget.te files in the BOARD_VENDOR_SEPOLICY_DIRS search path, then the first one found (at the first search dir containing the file) will be concatenated first. Reviewing out/target/product//obj/ETC/vendor_sepolicy.conf_intermediates/vendor_sepolicy.conf will help sort out ordering issues.

Additionally, OEMs can specify BOARD_SEPOLICY_M4DEFS to pass arbitrary m4 definitions during the build. A definition consists of a string in the form of macro-name=value. Spaces must NOT be present. This is useful for building modular policies, policy generation, conditional file paths, etc. It is supported in the following file types:

The mac_permissions.xml file is used for controlling the mmac solutions as well as mapping a public base16 signing key with an arbitrary seinfo string. Details of the files contents can be found in a comment at the top of that file. The seinfo string, previously mentioned, is the same string that is referenced in seapp_contexts.

It is important to note the final processed version of this file is stripped of comments and whitespace. This is to preserve space on the system.img. If one wishes to view it in a more human friendly format, the tidy or xmllint command will assist you.

Is a helper script for mapping arbitrary tags in the signature stanzas of mac_permissions.xml to public keys found in pem files. This script takes a mac_permissions.xml file(s) and configuration file in order to operate. Details of the configuration file (keys.conf) can be found in the subsection keys.conf. This tool is also responsible for stripping the comments and whitespace during processing.

Often times, one will need to integrate an application that was signed by a separate organization and may need to extract the pem file for the insertkeys/keys.conf tools. Extraction of the public key in the pem format is possible via openssl. First you need to unzip the apk, once it is unzipped, cd into the META_INF directory and then execute

On some occasions CERT.RSA has a different name, and you will need to adjust for that. After extracting the pem, you can rename it, and configure keys.conf and mac_permissions.xml to pick up the change. You MUST open the generated pem file in a text editor and strip out anything outside the opening and closing scissor lines. Failure to do so WILL cause a compile time issue thrown by insertkeys.py

3a8082e126