CrackBerry Abuser
|   Originally Posted by kretch  WHAT DO ALL OF THESE COMMANDS DO?? AND THESE [-F|-I][-X][-A][-v]
FLASHINFO
FILEINFO
WIPE [-F|-I]
SAVEFS [-X]
CSAVEFS
NUKE [-A]
FRESH
ERASE
CREAD [-A]
WRITE [] [-v]
WRITE [] [-v]
HIS
HOS -------------------------------------------------------------------------------
Usage: CFP [-p<port>|-u<port>] [-b<max BPS>] [-w<password>|-np]
[-v<verbosity>]
[-t<max connect timeout>]
[-c<max command timeout>] <command>
<command> is one of
HELP [<command>]
INFO
FILEINFO <filename>
LOAD <filename1> [filename2] [-v]
WIPE [-F|-I]
SAVEFS <filename>
CSAVEFS <filename>
NUKE [-A]
FRESH
ERASE <range>
READ <range> [-A] <filename>
CREAD <range> [-A] <filename>
WRITE <range> <filename> [<offset>] [-v]
WRITE <start address> <filename> [<offset>] [-v]
HIS
HOS
HASHBOOTROM [<bootromfile> [<hwvfile>]]
USBMS [-i<INFO> | -s<ENABLE> | -c<DISABLE>]
PATRIOT [-o] <subcommand> [<arguments>]
GETLOG [filename]
<range> is one of
<start address>-<end address> (start address < end address)
<start address>,<length> (length > 0)
All addresses, lengths, and offsets are expressed in HEX. Also,
<end address> is the address of the last byte in the range (e.g.
<length> = <end address> - <start address> + 1)
Verbosity Level:
-vd Display nothing at all (output disabled)
-v0 Display nothing other than progress
-v1 Display errors
-v2 Display errors and warnings (default)
-v3 Display procedural steps
-v4 Display protocol commands
-v5 Display everything. Lots of chatter!
Supported serial rates: 1382400, 691200, 460800, 345600, 230400, 153600,
115200, 76800, 57600, 38400, 28800, 19200, 14400
and 9600.
USB Ports: to use this feature, configuration with USBPortMapper.exe
is required. Please see 'USBPortMapper.exe HELP' for more information.
-------------------------------------------------------------------------------
INFO Usage
==========
INFO
Description:
------------
The INFO command extracts and then displays a wealth of information
about the device.
Examples:
---------
The following command will display all known information about a device:
CFP INFO
-------------------------------------------------------------------------------
FILEINFO Usage
==============
FILEINFO <filename>
Where:
------
<filename> is a list of one or more space separated filenames
Description:
------------
The FILEINFO command extracts and then displays a wealth of information
about the specified files.
NOTE: specifying a verbosity level >= 3 will cause extra info to be displayed.
Examples:
---------
The following command will display all known information about pcs1900.bin:
CFP FILEINFO pcs1900.bin
-------------------------------------------------------------------------------
LOAD Usage
==========
LOAD <file1> [file2]
Where:
------
<file1> is a valid OS binary, SFI file, of FS image.
Description:
------------
The LOAD command loads the specified file(s) onto a device.
If the new OS is larger than the the OS currently on a device, the entire
device will be erased and the contents of the file system will be lost.
If loading a new FS image any old data on the device is lost.
There must be a valid OS on the device.
Examples:
---------
The following command will load the firmware onto a device:
CFP LOAD gsm.bin
-------------------------------------------------------------------------------
WIPE Usage
==========
WIPE [-F|-I]
Where:
------
-F specifies that only the filesystem should be wiped.
-I specifies that only the installer partition should be removed.
If no option is specified, both the filesystem and OS are wiped.
Description:
------------
The WIPE command allows the filesystem
or all the filesystem and OS regions of flash to be irreversibly erased.
This command should be used when initially upgrading to the new loader
to ensure that old (unrecognized) versions of applications are destroyed.
-------------------------------------------------------------------------------
SAVEFS Usage
============
SAVEFS <filename>
Description:
------------
The SAVEFS command saves the file system data from a device to
the specified file. There must be a valid OS on the device. Since this saves a
plaintext copy of the data, it is only supported on insecure devices. For secure
devices, use the CSAVEFS variant which will save an encrypted file.
Examples:
---------
The following command will save the file system data from a device to the file
filesys.dmp:
CFP SAVEFS filesys.dmp
-------------------------------------------------------------------------------
CSAVEFS Usage
=============
Save an encrypted filesystem dump. See SAVEFS for usage details
-------------------------------------------------------------------------------
NUKE Usage
==========
NUKE [-A]
Where:
------
-A specifies that the OS should be erased as well (requires password).
Description:
------------
The NUKE command erases all of the user's data off the device
including the filesystem and the password. This command is useful if a
password is lost and one would like to make the device usable again at the
expense of lost data.
CFP NUKE
-------------------------------------------------------------------------------
FRESH Usage
===========
FRESH
Description:
------------
The FRESH command puts the device into freshness seal.
Namely, after sending this command, the battery will be turned off
and a manual reset will be required to turn the device back on.
Examples:
---------
CFP FRESH
-------------------------------------------------------------------------------
ERASE Usage
===========
ERASE <range>
Where:
------
<range> specifies the flash region to be erased.
Please type CFP alone for the definition of <range>.
Description:
------------
The ERASE command erases flash sectors on a device.
The INFO will provide all of the address information required to use this
command. Note that address ranges must be sector size aligned.
Please BE CAREFUL! If you don't know exactly what you are doing, use WIPE
This command is not fully functional on secure devices
Examples:
---------
The following command will erase the OS & filesystem (depends on flash size:
CFP ERASE 0x01010000-0x13FFFFF
So will:
CFP ERASE 0x01010000,0x3F0000
-------------------------------------------------------------------------------
READ Usage
==========
READ <range> [-A] <filename>
Where:
------
<range> specifies the flash region to be read.
-A specifies that the data should be appended to file <filename>.
Please type CFP alone for the definition of <range>.
Description:
------------
The READ command reads data from flash on a device and writes
it to a file. The INFO should provide all of the address
information required to use this command. If not, you shouldn't be using
this command. Since this saves a plaintext copy of the data, it is only
supported on insecure devices. For secure devices, use the CREAD
variant which will save an encrypted file. This command is not fully
functional on secure devices.
Examples:
---------
The following command will read a sector of the filesystem:
CFP READ 0x013F0000-0x013FFFFF dump.bin
-------------------------------------------------------------------------------
CREAD Usage
===========
Save an encrypted image of memory. See READ for usage details
-------------------------------------------------------------------------------
WRITE Usage
===========
WRITE <range> <filename> [<offset>]
WRITE <start address> <filename> [<offset>]
Where:
------
<range> specifies the flash region to be erased.
If <start address> is specified, the length of file <filename> will be used.
<offset> specifies the data location offset from the start of file <filename>
Please type CFP alone for the definition of <range>.
Description:
------------
The WRITE command writes data from a file to flash on a device.
The start address must be the start of a sector and the length must be a
multiple of 4 (for now). Each sector written will first be erased -- this
means that writing to the first byte of a sector will cause the sector to be
empty aside from the first byte.
Please BE CAREFUL!
This command is not fully functional on secure devices
Examples:
---------
The following command will load data.bin, starting at first sector of the
OS:
CFP WRITE 0x01010000 data.bin
Assuming that data.bin is 145 bytes in length, so will:
CFP WRITE 0x01010000,0x91 data.bin
And so will:
CFP WRITE 0x01010000-0x0x01010090 data.bin
The following command will load 1024 bytes to flash (address 0x01023424),
starting 200 bytes into data.bin:
CFP WRITE 0x01023424,0x400 data.bin 0xC8
-------------------------------------------------------------------------------
WRITE Usage
===========
WRITE <range> <filename> [<offset>]
WRITE <start address> <filename> [<offset>]
Where:
------
<range> specifies the flash region to be erased.
If <start address> is specified, the length of file <filename> will be used.
<offset> specifies the data location offset from the start of file <filename>
Please type CFP alone for the definition of <range>.
Description:
------------
The WRITE command writes data from a file to flash on a device.
The start address must be the start of a sector and the length must be a
multiple of 4 (for now). Each sector written will first be erased -- this
means that writing to the first byte of a sector will cause the sector to be
empty aside from the first byte.
Please BE CAREFUL!
This command is not fully functional on secure devices
Examples:
---------
The following command will load data.bin, starting at first sector of the
OS:
CFP WRITE 0x01010000 data.bin
Assuming that data.bin is 145 bytes in length, so will:
CFP WRITE 0x01010000,0x91 data.bin
And so will:
CFP WRITE 0x01010000-0x0x01010090 data.bin
The following command will load 1024 bytes to flash (address 0x01023424),
starting 200 bytes into data.bin:
CFP WRITE 0x01023424,0x400 data.bin 0xC8
-------------------------------------------------------------------------------
HIS Usage
=========
HIS
Description:
------------
The HIS puts the device into Head in Sand mode. Namely, after sending
this command, the device will reset on a catastrophic error instead of
displaying an error code.
Examples:
---------
CFP HIS
-------------------------------------------------------------------------------
HOS Usage
=========
HOS
Description:
------------
The HOS takes the device out of Head in Sand mode. Namely, after sending
this command, the device will NOT reset on a catastrophic error and will display an error code.
Examples:
---------
CFP HOS
-------------------------------------------------------------------------------
HASHBOOTROM Usage
=================
HASHBOOTROM [<filename1> [<filename2>]]
Description:
------------
The HASHBOOTROM command connects to a device and calculates a SHA-1 hash
signature of the bootrom. Optionally it can hash a specified file.
Examples:
---------
The following command will hash the file using the HWV from the connected device
CFP HASHBOOTROM bootromfile.bin
The following command will hash the file using the specified HWV file
CFP HASHBOOTROM bootromfile.bin hwvfile.hwv
-------------------------------------------------------------------------------
USBMS Usage
===========
USBMS [-i | -s | -c]
Where:
------
-i: Returns current USBMS mode
-s: Enables USBMS mode
-c: Disables USBMS mode
Description:
------------
The USBMS command can be used to check or change USB Mass
Storage mode on USBMS-capable devices
Examples:
---------
The following command will return the current USBMS mode
CFP USBMS -i
The following command will enable USBMS mode on USBMS-capable devices
CFP USBMS -s
The following command will disable USBMS mode on USBMS-capable devices
CFP USBMS -c
-------------------------------------------------------------------------------
PATRIOT Usage
=============
PATRIOT [-o] <subcommand> [<arguments>]
Where:
------
-o specifies use of old-style Patriot communication (through the OS).
<subcommand> is one of the following Patriot commands:
INFO
LOAD [-f] <patriot binary file>
BERBUG <Berbug script file>
ERASE <range>
WRITE <range> <filename>
WRITE <start address> <filename>
READ <range> <filename>
LOCKSTATUS
RESETLOG
MEMTEST [<string>]
Description:
------------
The PATRIOT command accesses a set of sub-commands for Patriot
operations. LOAD, ERASE, WRITE and READ behave similarly to
the standard CFP commands.
BERBUG accepts a text file of line-delimited Berbug command/response pairs.
LOCKSTATUS checks the status of Patriot's flash lock state for Baryon devices only.
INFO command reports info on the loaded Patriot binary.
RESETLOG command dumps the Patriot reset log.
MEMTEST command loads the memory test kernel and sends out each character in the string and prints the response.
If the string is not specified then MEMTEST enters interactive mode.
Use CFP HELP PATRIOT <subcommand> for help with specific subcommands.
Examples:
---------
The following command will load a Patriot binary
CFP PATRIOT LOAD patriotbinary.bin
-------------------------------------------------------------------------------
GETLOG Usage
============
GETLOG [filename]
Where:
------
[filename] specifies that the bugdisp log should be written to file [filename].
If not specified then c:\log.bug is assumed.
Description:
------------
The GETLOG command reads the bugdisp log for debug RAMImages.
Examples:
---------
The following command will read the bugdisp log to file bug.bug:
CFP GETLOG bug.log
| |
|
Clarifications
folks,
Topics 
Reply
