Restoretools.pkg Download
Results 1 - 10 of 21 - Find RestoreTools.com software downloads at CNET Download.com, the most comprehensive source for safe, trusted, and spyware-free. Feb 13, 2018 - Windows restore Fix - Download the (Recommendation) How to Fix. New version of PurpleRestore RestoreTools.pkg,. Purple restore,.
About This File
PurpleRestore is a tool made by Apple and is used for flashing iDevices. It provides far more customization than iTunes, and it is usually used to flash internal firmware to prototypes.
This tool can (and is meant to) handle multiple restores. When performing restores PurpleRestore color coordinates the device in the table and when the device is about to receive the AppleLogo it will turn the background color of the screen to the color assigned to the device. Like iTunes, PurpleRestore communicates with iDevices using a usbmux connection.
'PurpleFAT' is an Apple Factory Activation tool, assumed to be used in factories for UUT's (units under test). If the unactivated device is plugged into a computer and the software is run, it searches for the device and would activate it (Seems not to work and just plays a sound saying 'Oh nooh!') PurpleFAT needs an activation sever. https://albert.apple.com/WebObjects/ALUnbrick.woa/wa/deviceActivation does not work.
Application can be locked for some security reasons, and requires a passcode when unlocking the interface (This passcode is stored in a string, when dissasembled can be found at __text:00003089).
PurpleSNIFF is a tool made by Apple to read identification and diagnostic information from the device. The tool is used by Apple engineers as well as factory workers at Foxconn/Pegatron. It's included in the RestoreTools package.
Like iTunes, PurpleSNIFF communicates with iDevices using a usbmux connection.
PurpleBuildSanitizer is an Apple internal Mac application for stripping internal builds for internal use. When creating a stripped bundle, it names the folder like so, N92-INTERNAL-INSTALL-iPhone3,3_4.2.6_8E200_Restore.
About OpenChange
The OpenChange Project aims to provide a portable Open Sourceimplementation of Microsoft Exchange Server and Exchangeprotocols. Exchange is a groupware server designed to work withMicrosoft Outlook, and providing features such as a messaging server,shared calendars, contact databases, public folders, notes and tasks.
The OpenChange project has three goals:
To provide a library for interoperability with Exchange protocols, andto assist implementers to use this to create groupware thatinteroperates with both Exchange and other OpenChange-based software.
To provide an alternative to Microsoft Exchange Server which usesnative Exchange protocols and provides exactly equivalentfunctionality when viewed from Microsoft Outlook clients.
To develop a body of knowledge about the most popular groupwareprotocols in use commercially today in order to promote development ofa documented and unencumbered standard, with all the benefits thatstandards bring.
Documentation
There are two sources of documentation - text files in the doc/directory, and API documentation generated from the source files usingdoxygen. You can create the API documentation yourself (using 'makedoxygen' at the top level) or you can refer to the copy on theOpenChange web site athttp://apidocs.openchange.org/overview/index.html
doc/howto.txt contains instructions on how to install and set upclient libraries, client utilities and the server / proxy parts ofOpenChange.doc/man/ contains man(1) pages for several OpenChange utilities. Notethat man pages for programming (i.e. the parts that would appear inman3) are generated by doxygen, and will be found in apidocs/ if yougenerate the documentation yourself.doc/doxygen/ provides static content used as part of the doxygen APIdocumentation generation process.doc/examples/ provides programming examples for libmapi.
Structure
Pkg File Extractor
bin/ This directory is created during the build process. Itcontains the binaries (executable programs) that are compiled duringthe 'make' step. The source for most of these is in the utils/directory, described below.
doc/ This directory contains documentation - see description above(in DOCUMENTATION) for the various contents of this directory.
gen_ndr/ This directory contains routines for handling the NetworkData Representation (NDR) for various Exchange RPC calls. The contentsof this directory are generated (using Samba's pidl IDL compiler) atbuild time. The main input file is exchange.idl (see top leveldirectory).
libexchange2ical This directory provides functionality forconverting between Exchange calendar appointments and ICalendar (RFC2445 /RFC5545) format. Exchange -> ICalendar is fairly mature, ICalendar toExchange is in work.
libmapi/ This directory contains the main client-side library,called libmapi. libmapi closely reflects the underlying protocoloperations (Exchange RPC) being performed between the client and theserver. For more information, consult the API documentation (eitherbuild yourself, or online athttp://apidocs.openchange.org/libmapi/index.html)
libmapi++/ This directory contains C++ bindings for libmapi. It isnot a replacement for libmapi, but is intended to provide easieraccess to many libmapi functions for C++ programmers. For moreinformation, consult the API documentation (either build yourself, oronline at http://apidocs.openchange.org/libmapi++/index.html)
libmapiadmin/ This directory contains client-side library functionsfor administering OpenChange or Exchange servers. For moreinformation, consult the API documentation (either build yourself, oronline at http://apidocs.openchange.org/libmapiadmin/index.html). Ifyou are looking for a program you can run, instead of libraryfunctions to write your own program, 'openchangepfadmin' might be ofinterest.
libocpf/ This directory contains library functions for theOpenChange Property Files (OCPF). This allows building of mailmessages, address book entries, appointments and similar objects fromtext files. For more information, consult the API documentation(either build yourself, or online athttp://apidocs.openchange.org/libocpf/index.html)
mapiproxy/ This directory provides an Exchange RPC proxy. You canuse this to provide transparent proxying, or to change / monitorconnections between the client and server. For more information,consult the API documentation (either build yourself, or online athttp://apidocs.openchange.org/mapiproxy/index.html)
python/ This directory contains python scripts used to set up('provision') the server side. They are not required for the clientside.
qt/ This directory contains Qt4 bindings (lib/ subdirectory) anda sample application (demo/ subdirectory). The sample applicationis intended for research and development use, not as a completeend-user application.
samba4/ This directory will be created during the build process ifyou call 'make samba' or execute the ./script/installsamba4.shscript. It is used to build samba4, if required.
script/ This directory contains a range of scripts useful fordevelopment or use of OpenChange. [TODO: document the scripts -perhaps write script/README?]
setup/ This directory contains data for setting up ('provisioning')the server.
testprogs/ This directory contains developer test tools
utils/ This directory contains the source code for a range ofapplications / utilities that can be used to interact with an exchangeserver. They include:
utils/backup/ backup and restore tools
utils/exchange2ical converts Exchange calendar into an ICal file
utils/exchange2mbox two way conversion between Exchange mail and mbox
utils/mapiprofile set up client side profiles (login information)
utils/mapitest/ test tools for libmapi functionality
utils/mapitrace/ test tool for tracing MAPI calls
utils/openchangeclient command line client for Exchange RPC
utils/openchangepfadmin Public Folders admin tools andadministration of Exchange users (add/del)
utils/schemaIDGUIDFor more information on these tools, refer to the man(1) pages in doc/man/man1