Advertisement
SCrid2000

BlackBerry CFP 3.9.0.165 Commands

Aug 5th, 2012
2,392
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.00 KB | None | 0 0
  1. Microsoft Windows [Version 6.1.7601]
  2. Copyright (c) 2009 Microsoft Corporation. All rights reserved.
  3.  
  4.  
  5. C:\Users\User\Desktop>cfp
  6. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  7. Copyright 2010 Research In Motion Limited
  8.  
  9. Usage: CFP [-u<port>] [-g<GUID>|-ig] [-w<password>|-np]
  10. [-v<verbosity>]
  11. [-t<max connect timeout>]
  12. [-c<max command timeout>] <command>
  13. <command> is one of
  14. HELP [<command>]
  15. INFO
  16. FLASHINFO
  17. FILEINFO <filename>
  18. LOAD <filename1> [filename2] [-v] [-p]
  19. WIPE [-F|-I]
  20. SAVEFS [-X] <filename>
  21. CSAVEFS <filename>
  22. NUKE [-A]
  23. FRESH
  24. ERASE <range>
  25. READ <range> [-A] <filename>
  26. CREAD <range> [-A] <filename>
  27. WRITE <range> <filename> [<offset>] [-v]
  28. WRITE <start address> <filename> [<offset>] [-v]
  29. HIS
  30. HOS
  31. GETHISMODE
  32. SETHISMODE
  33. HASHBOOTROM [<bootromfile> [<hwvfile>]]
  34. USBMS [-i<INFO> | -s<ENABLE> | -c<DISABLE>]
  35. PATRIOT [-o] <subcommand> [<arguments>]
  36. GETLOG [filename]
  37.  
  38. <range> is one of
  39. <start address>-<end address> (start address < end address)
  40. <start address>,<length> (length > 0)
  41. All addresses, lengths, and offsets are expressed in HEX. Also,
  42. <end address> is the address of the last byte in the range (e.g.
  43. <length> = <end address> - <start address> + 1)
  44.  
  45. Verbosity Level:
  46. -vd Display nothing at all (output disabled)
  47. -v0 Display nothing other than progress
  48. -v1 Display errors
  49. -v2 Display errors and warnings (default)
  50. -v3 Display procedural steps
  51. -v4 Display protocol commands
  52. -v5 Display everything. Lots of chatter!
  53.  
  54. USB Ports: to use this feature, configuration with USBPortMapper.exe
  55. is required. Please see 'USBPortMapper.exe HELP' for more information.
  56.  
  57.  
  58. C:\Users\User\Desktop>cfp help
  59. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  60. Copyright 2010 Research In Motion Limited
  61.  
  62. CFP Usage
  63. =========
  64. CFP [-u<port>] [-g<GUID>] [-IG] [-W<password>] [-NP] [-FS] [-V<verbosity>] [
  65. -T <max connect timeout>] [-C <max command timeout>] <command>
  66.  
  67. -U<port> specifies the USB port (e.g. -U4 specifies USB port 4). Configuration with USBPortMapper.exe is required.
  68. -G<GUID> specifies the device GUID. Cannot be combined with -U
  69. -IG specifies that cfp will ignore the device GUID when connecting to a device. Cannot be used with -U or -G options.
  70. -W<password> specifies the device password. If a password is required, but not provided, the user will be prompted to enter the password.
  71. -NP specifies that the operation should only procede if there is NO password. The operation will abort if a password is set.
  72. -FS specifies that only a full speed RAMImage may be uploaded.
  73. -V<verbosity> specifies the level of information chatter. If ,<filename> is specified, all output other than the progress will be sent to the specified file.
  74. -T<max connect timeout> specifies a maximum conection timeout in ms.
  75. -C<max command timeout> specifies a maximum command timeout in ms.
  76.  
  77. All of the above are optional.
  78.  
  79. <command> is one of HELP, INFO, FLASHINFO, FILEINFO, LOAD, SAVEFS, CSAVEFS WIPE, ERASE, READ, CREAD, WRITE, HIS, HOS, USBMS, NUKE, FRESH, HASHBOOTROM, PATRIOT, GETLOG.
  80.  
  81.  
  82.  
  83. Where:
  84. ------
  85. The CFP command is used to load firmware and assist RIM internal developers.
  86.  
  87. Use CFP HELP <command> for more information.
  88.  
  89.  
  90. C:\Users\User\Desktop>cfp help info
  91. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  92. Copyright 2010 Research In Motion Limited
  93.  
  94. INFO Usage
  95. ==========
  96. INFO
  97.  
  98.  
  99.  
  100. Description:
  101. ------------
  102. The INFO command extracts and then displays a wealth of information about the device.
  103.  
  104.  
  105.  
  106. Examples:
  107. ---------
  108. The following command will display all known information about a device:
  109. CFP INFO
  110.  
  111.  
  112. C:\Users\User\Desktop>cfp help flashinfo
  113. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  114. Copyright 2010 Research In Motion Limited
  115.  
  116. FLASHINFO Usage
  117. ===============
  118. FLASHINFO
  119.  
  120.  
  121.  
  122. Description:
  123. ------------
  124. The FLASHINFO command extracts and then displays information about the flash
  125.  
  126.  
  127.  
  128. Examples:
  129. ---------
  130. The following command will display all known information about a device:
  131. CFP FLASHINFO
  132.  
  133.  
  134. C:\Users\User\Desktop>cfp help fileinfo
  135. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  136. Copyright 2010 Research In Motion Limited
  137.  
  138. FILEINFO Usage
  139. ==============
  140. FILEINFO <filename>
  141.  
  142.  
  143.  
  144. Where:
  145. ------
  146. <filename> is a list of one or more space separated filenames
  147.  
  148.  
  149.  
  150. Description:
  151. ------------
  152. The FILEINFO command extracts and then displays a wealth of information about the specified files.
  153. NOTE: specifying a verbosity level >= 3 will cause extra info to be displayed.
  154.  
  155.  
  156.  
  157. Examples:
  158. ---------
  159. The following command will display all known information about pcs1900.bin:
  160. CFP FILEINFO pcs1900.bin
  161.  
  162.  
  163. C:\Users\User\Desktop>cfp help load
  164. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  165. Copyright 2010 Research In Motion Limited
  166.  
  167. LOAD Usage
  168. ==========
  169. LOAD [-P] <file1> [file2]
  170.  
  171.  
  172.  
  173. Where:
  174. ------
  175. -P specifies that existing UMP files on the device should be preserved when loading additional UMP files. However, if a file being loaded has the same name as an existing file, then it will still replace the existing file.
  176.  
  177. <file1> is a valid, supported binary or an SFI file
  178.  
  179.  
  180.  
  181. Description:
  182. ------------
  183. The LOAD command loads the specified file(s) onto a device.
  184. 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.
  185. If loading a new FS image any old data on the device is lost.
  186. There must be a valid OS on the device.
  187.  
  188.  
  189.  
  190. Examples:
  191. ---------
  192. The following command will load the firmware onto a device:
  193. CFP LOAD gsm.bin
  194.  
  195.  
  196. C:\Users\User\Desktop>cfp help wipe
  197. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  198. Copyright 2010 Research In Motion Limited
  199.  
  200. WIPE Usage
  201. ==========
  202. WIPE [-F|-I]
  203.  
  204.  
  205.  
  206. Where:
  207. ------
  208. -F specifies that only the filesystem should be wiped.
  209. -I specifies that only the installer partition should be removed.
  210. If no option is specified, both the filesystem and OS are wiped.
  211.  
  212.  
  213.  
  214. Description:
  215. ------------
  216. The WIPE command allows the filesystem
  217. or all the filesystem and OS regions of flash to be irreversibly erased.
  218.  
  219. This command should be used when initially upgrading to the new loader to ensure that old (unrecognized) versions of applications are destroyed.
  220.  
  221.  
  222. C:\Users\User\Desktop>cfp help savefs
  223. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  224. Copyright 2010 Research In Motion Limited
  225.  
  226. SAVEFS Usage
  227. ============
  228. SAVEFS [-X] <filename>
  229.  
  230.  
  231.  
  232. Where:
  233. ------
  234. -X implies that a compressed save is done.
  235. Only valid file system segments are output.
  236.  
  237.  
  238.  
  239. Description:
  240. ------------
  241. 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.
  242.  
  243.  
  244.  
  245. Examples:
  246. ---------
  247. The following command will save the file system data from a device to the file filesys.dmp:
  248. CFP SAVEFS filesys.dmp
  249.  
  250.  
  251. C:\Users\User\Desktop>cfp help csavefs
  252. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  253. Copyright 2010 Research In Motion Limited
  254.  
  255. CSAVEFS Usage
  256. =============
  257. Save an encrypted filesystem dump. See SAVEFS for usage details
  258.  
  259.  
  260. C:\Users\User\Desktop>cfp help nuke
  261. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  262. Copyright 2010 Research In Motion Limited
  263.  
  264. NUKE Usage
  265. ==========
  266. NUKE [-A]
  267.  
  268.  
  269.  
  270. Where:
  271. ------
  272. -A specifies that the OS should be erased as well (requires password).
  273.  
  274.  
  275.  
  276. Description:
  277. ------------
  278. 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.
  279. CFP NUKE
  280.  
  281.  
  282. C:\Users\User\Desktop>cfp help fresh
  283. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  284. Copyright 2010 Research In Motion Limited
  285.  
  286. FRESH Usage
  287. ===========
  288. FRESH
  289.  
  290.  
  291.  
  292. Description:
  293. ------------
  294. The FRESH command puts the device into freshness seal.
  295. Namely, after sending this command, the battery will be turned off
  296. and a manual reset will be required to turn the device back on.
  297.  
  298.  
  299.  
  300. Examples:
  301. ---------
  302. CFP FRESH
  303.  
  304.  
  305. C:\Users\User\Desktop>cfp help erase
  306. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  307. Copyright 2010 Research In Motion Limited
  308.  
  309. ERASE Usage
  310. ===========
  311. ERASE <range>
  312.  
  313.  
  314.  
  315. Where:
  316. ------
  317. <range> specifies the flash region to be erased.
  318. Please type CFP alone for the definition of <range>.
  319.  
  320.  
  321.  
  322. Description:
  323. ------------
  324. 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.
  325. Please BE CAREFUL! If you don't know exactly what you are doing, use WIPE.
  326. This command is not fully functional on secure devices
  327.  
  328.  
  329.  
  330. Examples:
  331. ---------
  332. The following command will erase the OS & filesystem (depends on flash size:
  333. CFP ERASE 0x01010000-0x13FFFFF
  334. So will:
  335. CFP ERASE 0x01010000,0x3F0000
  336.  
  337.  
  338. C:\Users\User\Desktop>cfp help read
  339. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  340. Copyright 2010 Research In Motion Limited
  341.  
  342. READ Usage
  343. ==========
  344. READ <range> [-A] <filename>
  345.  
  346.  
  347.  
  348. Where:
  349. ------
  350. <range> specifies the flash region to be read.
  351. -A specifies that the data should be appended to file <filename>.
  352.  
  353. Please type CFP alone for the definition of <range>.
  354.  
  355.  
  356.  
  357. Description:
  358. ------------
  359. 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.
  360.  
  361.  
  362.  
  363. Examples:
  364. ---------
  365. The following command will read a sector of the filesystem:
  366. CFP READ 0x013F0000-0x013FFFFF dump.bin
  367.  
  368.  
  369. C:\Users\User\Desktop>cfp help cread
  370. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  371. Copyright 2010 Research In Motion Limited
  372.  
  373. CREAD Usage
  374. ===========
  375. Save an encrypted image of memory. See READ for usage details
  376.  
  377.  
  378. C:\Users\User\Desktop>cfp help write
  379. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  380. Copyright 2010 Research In Motion Limited
  381.  
  382. WRITE Usage
  383. ===========
  384. WRITE <range> <filename> [<offset>]
  385. WRITE <start address> <filename> [<offset>]
  386.  
  387.  
  388.  
  389. Where:
  390. ------
  391. <range> specifies the flash region to be erased.
  392. 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>.
  393.  
  394.  
  395.  
  396. Description:
  397. ------------
  398. The WRITE command writes data from a file to flash on a device.
  399. 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.
  400. Please BE CAREFUL!
  401. This command is not fully functional on secure devices
  402.  
  403.  
  404.  
  405. Examples:
  406. ---------
  407. The following command will load data.bin, starting at first sector of the OS:
  408. CFP WRITE 0x01010000 data.bin
  409. Assuming that data.bin is 145 bytes in length, so will:
  410. CFP WRITE 0x01010000,0x91 data.bin
  411. And so will:
  412. CFP WRITE 0x01010000-0x0x01010090 data.bin
  413.  
  414. The following command will load 1024 bytes to flash (address 0x01023424), starting 200 bytes into data.bin:
  415. CFP WRITE 0x01023424,0x400 data.bin 0xC8
  416.  
  417.  
  418.  
  419.  
  420. C:\Users\User\Desktop>cfp help his
  421. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  422. Copyright 2010 Research In Motion Limited
  423.  
  424. HIS Usage
  425. =========
  426. HIS
  427.  
  428.  
  429.  
  430. Description:
  431. ------------
  432. 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.
  433.  
  434.  
  435.  
  436. Examples:
  437. ---------
  438. CFP HIS
  439.  
  440.  
  441. C:\Users\User\Desktop>cfp help hos
  442. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  443. Copyright 2010 Research In Motion Limited
  444.  
  445. HOS Usage
  446. =========
  447. HOS
  448.  
  449.  
  450.  
  451. Description:
  452. ------------
  453. 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.
  454.  
  455.  
  456.  
  457. Examples:
  458. ---------
  459. CFP HOS
  460.  
  461.  
  462. C:\Users\User\Desktop>cfp help gethismode
  463. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  464. Copyright 2010 Research In Motion Limited
  465.  
  466. GETHISMODE Usage
  467. ================
  468. GETHISMODE
  469.  
  470.  
  471.  
  472. Description:
  473. ------------
  474. The GETHISMODE gets the Head in Sand mode of the device. The modes are developer, user and default. In developer mode, the device will NOT reset on a catastrophic error and will display an error code. In user mode, the device will reset on a catastrophic error. In default mode, the HIS mode is dependent on the security of the device and the OS loaded on it. On insecure devices, the default mode is developer mode. On secure devices, the default mode is user mode if a SFI is loaded and developer mode if a MFI is loaded.
  475.  
  476.  
  477.  
  478. Examples:
  479. ---------
  480. CFP GETHISMODE
  481.  
  482.  
  483. C:\Users\User\Desktop>cfp help sethismode
  484. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  485. Copyright 2010 Research In Motion Limited
  486.  
  487. SETHISMODE Usage
  488. ================
  489. SETHISMODE
  490.  
  491.  
  492.  
  493. Description:
  494. ------------
  495. The SETHISMODE sets the Head in Sand mode of the device. The modes are developer, user and default. In developer mode, the device will NOT reset on a catastrophic error and will display an error code. In user mode, the device will reset on a catastrophic error. In default mode, the HIS mode is dependent on the security of the device and the OS loaded on it. On insecure devices, the default mode is developer mode. On secure devices, the default mode is user mode if a SFI is loaded and developer mode if a MFI is loaded.
  496.  
  497.  
  498.  
  499. Examples:
  500. ---------
  501. CFP SETHISMODE HIS
  502. CFP SETHISMODE HOS
  503.  
  504.  
  505. C:\Users\User\Desktop>cfp help hashbootrom
  506. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  507. Copyright 2010 Research In Motion Limited
  508.  
  509. HASHBOOTROM Usage
  510. =================
  511. HASHBOOTROM [<filename1> [<filename2>]]
  512.  
  513.  
  514.  
  515. Description:
  516. ------------
  517. The HASHBOOTROM command connects to a device and calculates a SHA-1 hash signature of the bootrom. Optionally it can hash a specified bootrom file against the HWV on the device or against a provided HWV file. The provided bootrom file may be a BIN file or a valid bootrom contained in a SFI
  518.  
  519.  
  520.  
  521. Examples:
  522. ---------
  523. The following command will hash the file using the HWV from the connected device
  524.  
  525. CFP HASHBOOTROM bootromfile.bin
  526. The following command will hash the file using the specified HWV file
  527. CFP HASHBOOTROM bootromfile.bin hwvfile.hwv
  528.  
  529.  
  530. C:\Users\User\Desktop>cfp help usbms
  531. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  532. Copyright 2010 Research In Motion Limited
  533.  
  534. USBMS Usage
  535. ===========
  536. USBMS [-i | -s | -c]
  537.  
  538.  
  539.  
  540. Where:
  541. ------
  542. -i: Returns current USBMS mode
  543. -s: Enables USBMS mode
  544. -c: Disables USBMS mode
  545.  
  546.  
  547.  
  548. Description:
  549. ------------
  550. The USBMS command can be used to check or change USB Mass Storage mode on USBMS-capable devices
  551.  
  552.  
  553.  
  554. Examples:
  555. ---------
  556. The following command will return the current USBMS mode
  557. CFP USBMS -i
  558. The following command will enable USBMS mode on USBMS-capable devices
  559. CFP USBMS -s
  560. The following command will disable USBMS mode on USBMS-capable devices
  561. CFP USBMS -c
  562.  
  563.  
  564. C:\Users\User\Desktop>cfp help patriot
  565. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  566. Copyright 2010 Research In Motion Limited
  567.  
  568. PATRIOT Usage
  569. =============
  570. PATRIOT [-o] <subcommand> [<arguments>]
  571.  
  572.  
  573.  
  574. Where:
  575. ------
  576. -o specifies use of old-style Patriot communication (through the OS).
  577.  
  578. <subcommand> is one of the following Patriot commands:
  579. INFO
  580. LOAD [-f] <patriot binary file>
  581. BERBUG <Berbug script file>
  582. ERASE <range>
  583. WRITE <range> <filename>
  584. WRITE <start address> <filename>
  585. READ <range> <filename>
  586. LOCKSTATUS
  587. RESETLOG
  588. MEMTEST [<string>]
  589. WIPE
  590.  
  591.  
  592.  
  593. Description:
  594. ------------
  595. 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.
  596. If the string is not specified then MEMTEST enters interactive mode.
  597. WIPE erases all erasable sections of Patriot.
  598.  
  599. Use CFP HELP PATRIOT <subcommand> for help with specific subcommands.
  600.  
  601.  
  602.  
  603. Examples:
  604. ---------
  605. The following command will load a Patriot binary
  606. CFP PATRIOT LOAD patriotbinary.bin
  607.  
  608.  
  609. C:\Users\User\Desktop>cfp help getlog
  610. RIM Wireless Device Command-Line Programmer Version 3.9.0.165
  611. Copyright 2010 Research In Motion Limited
  612.  
  613. GETLOG Usage
  614. ============
  615. GETLOG [filename]
  616.  
  617.  
  618.  
  619. Where:
  620. ------
  621. [filename] specifies that the bugdisp log should be written to file [filename].
  622. If not specified then c:\log.bug is assumed.
  623.  
  624.  
  625.  
  626.  
  627. Description:
  628. ------------
  629. The GETLOG command reads the bugdisp log for debug RAMImages.
  630.  
  631.  
  632.  
  633. Examples:
  634. ---------
  635. The following command will read the bugdisp log to file bug.bug:
  636. CFP GETLOG bug.log
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement