Monday, 18 March 2013
00:22
Sunday, 17 March 2013
02:07
World's Fastest SL3 LBF "MARKOV" EDITION
oclHashcat-lite v0.10 by atom !!!
Welcome to oclHashcat-lite v0.10.
Download it here: http://hashcat.net/oclhashcat-lite/
Code: This release is a big step forward. We have added both, many major and many minor features.
Per-position markov-chains, aka markov-attack/incremental-attack/charset-files
The markov-attack is a statistically based brute-force like attack, but instead of specifying a charset or a mask, we specify a file. This file is once generated by ourself in a previous step. It contains statistical informations which are made out an automated analysis of a given dictionary.
It can fully replace Brute-Force since it covers the full keyspace.
In Brute-Force Attack (or in Mask Attack) we can limit the keyspace by setting a smaller charset in order to reduce the attack-time. In Markov Attack we have something similar, the "threshold". All you do is to specify a number. The higher the number, the higher the threshold to add a new link between two characters on the two-level table on which the markov-attack bases on.
This background is not so important, just remember that the lower the value, the smaller the keyspace and thus the faster the attack is.
Check these threads for more details
http://hashcat.net/forum/thread-1265.html
http://hashcat.net/forum/thread-1285.html
http://hashcat.net/forum/thread-1291.html
Use .ptx ad .llvmir intermediate kernels
The kernels are distributed in an "intermediate" format (aka IL). It cant be reversed to original C code but still its not a binary format that can be used for execution.
The JIT (just-in-time) compilers from both OpenCL and CUDA, which ship with the driver, compile the final byte-code out of the IL. This takes a few seconds per kernel but once its done the byte-code is cached (CUDA does it automatically, OpenCL not but we add a function to do the same as CUDA does).
This has some nice advantages:
Not 32/64 bit specific
Less HDD space
Smaller .7z
Less problems with driver specific problems as we often see with Catalyst
There is no more need to release a new oclHashcat-* in case a new driver optimization has been added. oclHashcat-* caches driver specific. If it recognizes a driver change it will rebuild thge byte-code from the IL, but using the new JIT from the new driver resulting in driver specific optimized byte-code.
Retaining GPU temperature
When I started with oclHashcat-* Hardware mangement support, some people asked me for add support for fan-speed. For a long time I was not interessted in adding fan-speed code to oclHashcat-* since this is the job for the driver or some specialized controling software.
I did not change my mind completly on this, but still we have added some fan-speed controlling code. The new parameters are:
Code:
--gpu-temp-disable Disable temperature and fanspeed readings and triggers
--gpu-temp-abort=NUM Abort session if GPU temperature reaches NUM degrees celsius
--gpu-temp-retain=NUM Try to retain GPU temperature at NUM degrees celsius (AMD only)
So what this thing is doing is: If the temperature configured with the new --gpu-temp-retain parameter is reached, it starts to increase the fan-speed by 1 percent each second. Thats all.
If you imagine a scenario what this means you will come to the conclusion that this feature also enables you to enfore your GPU running always to a very specific temperature.
Some notes:
--gpu-temp-disable you can completly disable all the temperature stuff.
--gpu-temp-retain currently only works for AMD.
--gpu-temp-abort parameter is just the renamed version of the old --gpu-watchdog.
Both parameters accept the 0 value which disables only this specific feature. This means you can step back to the old behavior by specifying --gpu-temp-retain 0.
The default for --gpu-temp-abort is still 90c.
The default for --gpu-temp-retain is 80c.
Built-in benchmarking mode
Code:
* Benchmark:
-b, --benchmark Run benchmark
--benchmark-mode Benchmark-mode, see references below
Nothing much to explain here I think, but some notes to the benchmark mode:
As long as you do not set the --benchmark-mode you can modify all the configuration parameters you always use. Something like -d, -n, --gpu-accel or --runtime.
With --runtime you can specify the duration how long each test lasts.
If you add -m you can limit to a specific hash-type. If you do not set it, it will iterate through all hash-types.
All unneccessary parallel threads like hardware monitor, restore-support and outfile-watch are disabled. Also the quiet mode is enabled.
On NVidia, the hashes based on SHA256, SHA512 and DES are limited to -n 32, otherwise the driver throws the error cuStreamSynchronize() 702.
New Algorithms supported
SHA512
Oracle 7-10g, DES(Oracle)
md4($pass.$salt)
sha256($pass.$salt)
sha512($pass.$salt)
Full Change Log:
Code: type: feature
file: kernels
desc: added -m 0910 = md4($pass.$salt)
type: feature
file: kernels
desc: added -m 1410 = sha256($pass.$salt)
type: feature
file: kernels
desc: added -m 1700 = SHA512
type: feature
file: kernels
desc: added -m 1710 = sha512($pass.$salt)
type: feature
file: kernels
desc: added -m 3100 = Oracle 7-10g, DES(Oracle)
type: feature
file: kernels
desc: on AMD, switched from .kernel to .llvmir to reduce diskspace
type: feature
file: kernels
desc: on NV, switched from .cubin to .ptx to reduce diskspace
type: feature
file: kernels
desc: added kernel cache to avoid unnecessary recompilation
cred: m4tr1x
type: driver
file: kernels
desc: added support for NVidia CUDA 4.2
type: driver
file: kernels
desc: added support for NVidia sm_30 gpu-architecture [ Kepler ]
type: driver
file: host programs
desc: added support for NVAPI R300
type: driver
file: host programs
desc: added support for NVidia NVML library and got rid of nvidia-smi command
type: driver
file: host programs
desc: added support for AMD ADL v4.0 library
type: feature
file: host programs
desc: splitted --gpu-watchdog to --gpu-temp-disable and --gpu-temp-abort
type: feature
file: kernels
desc: added benchmarking mode
cred: m4tr1x
type: feature
file: host programs
desc: added --gpu-temp-retain to try retain temperature at NUM degrees celsius
cred: m4tr1x
type: feature
file: host programs
desc: workarounded AMD bug in clGetDeviceInfo() CL_DEVICE_MAX_CLOCK_FREQUENCY
cred: m4tr1x
type: feature
file: kernels
desc: added early check for zero-length password hashes
cred: m4tr1x
type: feature
file: host programs
desc: show LM-half as soon as it is cracked
type: feature
file: host programs
desc: added support for charset files and some example charset files
type: feature
file: host programs
desc: added support to read hashes from file
type: feature
file: host programs
desc: implemented base64 parser that would allow for dynamic salt lengths in nsldaps
type: feature
file: host programs
desc: added fan-speeds to status display
type: feature
file: host programs
desc: removed --pw-skip-plain and --pw-limit-plain as they are incompatible to markov
type: bug
file: host programs
desc: fixed bug in status display if ETA calculated > 60 years
cred: arex
type: bug
file: host programs
desc: fixed bug in Oracle 11g hash parsing function, salt length increased to 10 byte
cred: flipit
type: bug
file: host programs
desc: fixed bug in salt-length parser for MyBB1.2 hashes
cred: code841
type: change
file: host programs
desc: changed default charset to the one which passpal outputs running on rockyou.txt
cred: arex
Welcome to oclHashcat-lite v0.9.
Message from Atom (Hashcat-Lite Developer + Bruteforce Guru)
Code: Hello Hashcat-Users,
I am proud to announce version 0.09 of the oclHashcat-lite series.
Download it here: http://hashcat.net/oclhashcat-lite/
The highlights of this release are:
Support for AMD GCN cards (hd7xxx series)
I already wrote some more detailed informations about the integration here: http://hashcat.net/forum/thread-817.html
This card is a true DES killer. I wrote some more detailed informations about this topic here: http://hashcat.net/forum/thread-846.html
Added the LM Algorithm
After so many people requested this algorithm in the feature request section I decided to add it even I had not interesst in it.
However, it turned out it was a good investment of time. I realized how many pentester still have need for it.
See here for discussion: http://hashcat.net/forum/thread-167.html
Vectorized datatype kernels for sm_21 NVidia architecture
This a massive improvement for low- and mid-ranged NVidia GPUs.
The gtx560Ti @ MD5, for example, increased by 23% (1252 Mhash/s -> 1660 Mhash/s).
This improvement can be seen on nearly all algorithms for this architecture.
MD4 based algorithm tuning
To make it short: I found a way to reverse another step in MD4.
Especially the NTLM and DCC algorithm benefit from this code change.
The hd6990 @ NTLM broke the 20000 Mhash/s mark on stock clocks. Average increase is around + 9% (19100 Mhash/s -> 20864 Mhash/s).
Updated EULA
This goes back to a discussion we had HD Moore from Rapid7.
The updated EULA is a lot more relaxed for professional pentesters than before.
See changelog for more details.
Fixed some major issues
On thing that many user complained about in oclHashcat-lite 0.08 was its "instability" and problems with session restore.
This popped in because of a default-settings change in oclHashcat-lite v0.07. It has been set back to oclHashcat-lite v0.06 default.
Discussion can be found here: http://hashcat.net/forum/thread-681.html
Harmonization with oclHashcat-plus
The --help page, the --outfile-format and the -m parameter values, in case of an overlap, are now equal to oclHashcat-plus v0.08.
It will help to avoid confusion, thats why I am planning to do the same change on CPU hashcat in the next version.
Official Download Link:
http://hashcat.net/oclhashcat-lite/
Official Hashcat Forum:
http://hashcat.net/forum/
Official SL3 BF Cracking Guide
http://hashcat.net/wiki/cracking_sl3/
oclHashcat now have a special SL3 Kernel with 12.24% Speed Increase on ALL SL3 LBF Tasks!!!
Download here: (yes it's 100% free)
Download oclHashcat-lite-0.06.7z - hashcat, advanced password recovery
Changelogs from v0.05 to v0.06
Code: * changes v0.05 -> v0.06:
type: performance increase
file: kernels
desc: MD5: AMD 1,07%, NVidia 0,62%
desc: md5($pass.$salt): AMD 1,37%, NVidia 8,10%
desc: md5(md5($pass)): AMD 0,94%, NVidia 0%
desc: vBulletin < v3.8.5: AMD 0,30%, NVidia 0%
desc: SHA1: AMD 11,14%, NVidia 13,62%
desc: sha1($pass.$salt): AMD 16,96%, NVidia 39,10%
desc: MySQL > v4.1: AMD 1,99%, NVidia 7,15%
desc: MD4: AMD 13,46%, NVidia 3,34%
desc: NTLM: AMD 13,16%, NVidia 2,57%
desc: DCC: AMD 34,20%, NVidia 0,89%
desc: MSSQL: AMD 11,23%, NVidia 17,89%
desc: SL3: AMD 12,24%, NVidia 13,48%
desc: Oracle 11G: AMD 16,93%, NVidia 13,53%
type: password length increase
file: kernels
desc: MD5: from 15 to 55
desc: md5($pass.$salt): from 15 to 55
desc: md5(md5($pass)): from 15 to 55
desc: vBulletin < v3.8.5: from 15 to 55
desc: SHA1: from 15 to 55
desc: sha1($pass.$salt): from 15 to 55
desc: MySQL > v4.1: from 15 to 55
desc: MD4: from 15 to 55
desc: NTLM: from 15 to 27
desc: DCC: from 15 to 27
desc: MSSQL: from 15 to 25
desc: SHA256: from 15 to 55
desc: Oracle 11G: from 15 to 45
type: feature
file: kernels
desc: added -m 15 = vBulletin > v3.8.5
cred: chick0n
type: feature
file: kernels
desc: increased salt length for DCC from 7 to 19
cred: Rabbitz
type: feature
file: host programs
desc: hardcoded cpu affinity mask to one (cpu #0) to save energy
cred: randyberger
type: feature
file: host programs
desc: added --pw-skip and --pw-limit parameters for distributed computing
cred: d3ad0ne
type: feature
file: host programs
desc: added status codes on exit, see status_codes.txt for listing
cred: hermix
type: bug
file: host programs
desc: rewritten restore function check from scratch
cred: anonymous
type: bug
file: host programs
desc: fixed multiple instances check
cred: FractalizeR
type: bug
file: host programs
desc: fixed 8 bit characters from russian alphabet
cred: Rolf
8,8xx Million Hash Per Second!
HW Specs: 4 x 5870 @ 980 Mhz
New and Faster SL3 LBF Kernel UPDATE for oclHashcat-lite v0.05 by atom
Official Download Link:
Download oclHashcat-lite-0.05.7z - hashcat, advanced password recovery
Official oclHashcat-lite Homepage:
oclHashcat-lite - advanced password recovery
Official Discussion Forum and Discussion Thread:
hashcat Forum
Featuring:
1. Ultra Fast and Stable SL3 Kernel
2. Upto 4% Faster HASH Speeds on 5xxx and 6xxx Cards
3. 100% Free Software !!!
4. Fixed --restore for Resuming BF Tasks
5. Easier Command Line
IMPORTANT CHANGES FOR COMMANDLINE INPUT
1. Change -m 101 into -m 1900
2. Change --output-file into --outfile
3. No need to use --pw-min and --pw-max
4. No need to use --hex-charset --hex-salt
EXAMPLE:
ORIGINAL COMMANDLINE for v0.03:
oclHashcat-lite64 3D5D9E11835243015407B7BA327E30CCB70F4DB0:003519730379149500 -1 00010203040506070809 -m 101 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 --pw-min=15 --pw-max=15 -n 160 --hex-charset --hex-salt --output-format=1 --output-file=351973037914952.txt
NEW COMMANDLINE for v0.05:
oclHashcat-lite64 3D5D9E11835243015407B7BA327E30CCB70F4DB0:003519730379149500 -1 00010203040506070809 -m 1900 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 -n 160 --outfile-format=1 --outfile=351973037914952.txt
REAL SPEED with 2 x HD 6990 @ 950 Mhz, 7,6xx MILLION HASH per Second !!!
REAL SPEED with 2 x HD 5970 @ 950 Mhz, 7,8xx MILLION HASH per Second !!!
Fastest SL3 LBF Free and UPDATED!! OlcHashcat-lite v0.03 by atom!! (HD6xxx Supported).
Thanks to atom for providing us with 100% Free and 100% fast SL3 LBF Software.
Also 100% support for new ATI 6xxx cards (6970, 6990 etc)...
BR
Thomas
BUGFIXES in v0.03
type: bug
file: cudaHashcat-lite, oclHashcat-lite
desc: fixed a bug in security causing hash was not found randomly
cred: RaNdy
type: bug
file: cudaHashcat-lite, oclHashcat-lite
desc: fixed a bug in --restore if command-line contains --pw-skip
cred: Ciukut
type: bug
file: cudaHashcat-lite, oclHashcat-lite
desc: fixed a bug in --restore if command-line contains --pw-min
cred: hermix
information taken from:
oclHashcat-lite v0.03
official download area:
oclHashcat-lite - advanced password recovery
GPU Driver and SDK Requirements:
NV users require ForceWare v260.x+
AMD users require Catalyst v11.3+ with APP SDK2.4+ or integrated OpenCL driverFeatures
Worlds fastest MD4, MD5, SHA1 and SHA256 cracker
Free
Multi-GPU (up to 16 gpus)
Multi-OS (Linux & Windows native binaries)
Multi-Platform (OpenCL & CUDA support)
Multi-Algo (see below)
Low resource utilization, you can still watch movies or play games while cracking
Supports password masks
Supports distributed cracking
Supports pause / resume while cracking
Supports sessions
Supports restore
Supports hex-salt
Supports hex-charset
Integrated thermal watchdog
... and much moreAlgorithms
MD5
md5($pass.$salt)
md5(md5($pass))
vBulletin < v3.8.5
SHA1
sha1($pass.$salt)
MySQL > v4.1
MD4
NTLM
Domain Cached Credentials
SHA256Tested OS's
All Windows and Linux versions should work on both 32 and 64 bitTested GPU's
All CUDA and Stream enabled cards should work==================================================
==================================================
For more information about how to setup Windows or Ubuntu with
oclHashcat-lite, you can visit atom's official forum or you can also
post your inquiries in ATF Section on this thread:
Fastest LBF Free Download!! OlcHashcat-lite v0.2!! HD6xxx Supported!
You can now build yourself the fastest LBF "Monster PC" by using:
Motherboard: MSI Big Bang Marshal
Video Card: 8 pieces ATI 6970
This will give you 14,170 Million HASH/s on STOCK CLOCKS...
Overclock with give you more than 15,xxx HASH/s and the video cards
will still be less than 80 degrees celcius with the stock cooling system.
==================================================
==================================================
Here is OFFICIAL and UPDATED "HOWTO" for hashcat-lite v0.02
oclHashcat-lite SL3 cracking howto
Check out Post # 6 Where atom discusses about MULTIPLE PC Setups to attack a single phone.
atom's forum is 100% open for discussion about his work...
Welcome to oclHashcat-lite v0.10.
Download it here: http://hashcat.net/oclhashcat-lite/
Code: This release is a big step forward. We have added both, many major and many minor features.
Per-position markov-chains, aka markov-attack/incremental-attack/charset-files
The markov-attack is a statistically based brute-force like attack, but instead of specifying a charset or a mask, we specify a file. This file is once generated by ourself in a previous step. It contains statistical informations which are made out an automated analysis of a given dictionary.
It can fully replace Brute-Force since it covers the full keyspace.
In Brute-Force Attack (or in Mask Attack) we can limit the keyspace by setting a smaller charset in order to reduce the attack-time. In Markov Attack we have something similar, the "threshold". All you do is to specify a number. The higher the number, the higher the threshold to add a new link between two characters on the two-level table on which the markov-attack bases on.
This background is not so important, just remember that the lower the value, the smaller the keyspace and thus the faster the attack is.
Check these threads for more details
http://hashcat.net/forum/thread-1265.html
http://hashcat.net/forum/thread-1285.html
http://hashcat.net/forum/thread-1291.html
Use .ptx ad .llvmir intermediate kernels
The kernels are distributed in an "intermediate" format (aka IL). It cant be reversed to original C code but still its not a binary format that can be used for execution.
The JIT (just-in-time) compilers from both OpenCL and CUDA, which ship with the driver, compile the final byte-code out of the IL. This takes a few seconds per kernel but once its done the byte-code is cached (CUDA does it automatically, OpenCL not but we add a function to do the same as CUDA does).
This has some nice advantages:
Not 32/64 bit specific
Less HDD space
Smaller .7z
Less problems with driver specific problems as we often see with Catalyst
There is no more need to release a new oclHashcat-* in case a new driver optimization has been added. oclHashcat-* caches driver specific. If it recognizes a driver change it will rebuild thge byte-code from the IL, but using the new JIT from the new driver resulting in driver specific optimized byte-code.
Retaining GPU temperature
When I started with oclHashcat-* Hardware mangement support, some people asked me for add support for fan-speed. For a long time I was not interessted in adding fan-speed code to oclHashcat-* since this is the job for the driver or some specialized controling software.
I did not change my mind completly on this, but still we have added some fan-speed controlling code. The new parameters are:
Code:
--gpu-temp-disable Disable temperature and fanspeed readings and triggers
--gpu-temp-abort=NUM Abort session if GPU temperature reaches NUM degrees celsius
--gpu-temp-retain=NUM Try to retain GPU temperature at NUM degrees celsius (AMD only)
So what this thing is doing is: If the temperature configured with the new --gpu-temp-retain parameter is reached, it starts to increase the fan-speed by 1 percent each second. Thats all.
If you imagine a scenario what this means you will come to the conclusion that this feature also enables you to enfore your GPU running always to a very specific temperature.
Some notes:
--gpu-temp-disable you can completly disable all the temperature stuff.
--gpu-temp-retain currently only works for AMD.
--gpu-temp-abort parameter is just the renamed version of the old --gpu-watchdog.
Both parameters accept the 0 value which disables only this specific feature. This means you can step back to the old behavior by specifying --gpu-temp-retain 0.
The default for --gpu-temp-abort is still 90c.
The default for --gpu-temp-retain is 80c.
Built-in benchmarking mode
Code:
* Benchmark:
-b, --benchmark Run benchmark
--benchmark-mode Benchmark-mode, see references below
Nothing much to explain here I think, but some notes to the benchmark mode:
As long as you do not set the --benchmark-mode you can modify all the configuration parameters you always use. Something like -d, -n, --gpu-accel or --runtime.
With --runtime you can specify the duration how long each test lasts.
If you add -m you can limit to a specific hash-type. If you do not set it, it will iterate through all hash-types.
All unneccessary parallel threads like hardware monitor, restore-support and outfile-watch are disabled. Also the quiet mode is enabled.
On NVidia, the hashes based on SHA256, SHA512 and DES are limited to -n 32, otherwise the driver throws the error cuStreamSynchronize() 702.
New Algorithms supported
SHA512
Oracle 7-10g, DES(Oracle)
md4($pass.$salt)
sha256($pass.$salt)
sha512($pass.$salt)
Full Change Log:
Code: type: feature
file: kernels
desc: added -m 0910 = md4($pass.$salt)
type: feature
file: kernels
desc: added -m 1410 = sha256($pass.$salt)
type: feature
file: kernels
desc: added -m 1700 = SHA512
type: feature
file: kernels
desc: added -m 1710 = sha512($pass.$salt)
type: feature
file: kernels
desc: added -m 3100 = Oracle 7-10g, DES(Oracle)
type: feature
file: kernels
desc: on AMD, switched from .kernel to .llvmir to reduce diskspace
type: feature
file: kernels
desc: on NV, switched from .cubin to .ptx to reduce diskspace
type: feature
file: kernels
desc: added kernel cache to avoid unnecessary recompilation
cred: m4tr1x
type: driver
file: kernels
desc: added support for NVidia CUDA 4.2
type: driver
file: kernels
desc: added support for NVidia sm_30 gpu-architecture [ Kepler ]
type: driver
file: host programs
desc: added support for NVAPI R300
type: driver
file: host programs
desc: added support for NVidia NVML library and got rid of nvidia-smi command
type: driver
file: host programs
desc: added support for AMD ADL v4.0 library
type: feature
file: host programs
desc: splitted --gpu-watchdog to --gpu-temp-disable and --gpu-temp-abort
type: feature
file: kernels
desc: added benchmarking mode
cred: m4tr1x
type: feature
file: host programs
desc: added --gpu-temp-retain to try retain temperature at NUM degrees celsius
cred: m4tr1x
type: feature
file: host programs
desc: workarounded AMD bug in clGetDeviceInfo() CL_DEVICE_MAX_CLOCK_FREQUENCY
cred: m4tr1x
type: feature
file: kernels
desc: added early check for zero-length password hashes
cred: m4tr1x
type: feature
file: host programs
desc: show LM-half as soon as it is cracked
type: feature
file: host programs
desc: added support for charset files and some example charset files
type: feature
file: host programs
desc: added support to read hashes from file
type: feature
file: host programs
desc: implemented base64 parser that would allow for dynamic salt lengths in nsldaps
type: feature
file: host programs
desc: added fan-speeds to status display
type: feature
file: host programs
desc: removed --pw-skip-plain and --pw-limit-plain as they are incompatible to markov
type: bug
file: host programs
desc: fixed bug in status display if ETA calculated > 60 years
cred: arex
type: bug
file: host programs
desc: fixed bug in Oracle 11g hash parsing function, salt length increased to 10 byte
cred: flipit
type: bug
file: host programs
desc: fixed bug in salt-length parser for MyBB1.2 hashes
cred: code841
type: change
file: host programs
desc: changed default charset to the one which passpal outputs running on rockyou.txt
cred: arex
Welcome to oclHashcat-lite v0.9.
Message from Atom (Hashcat-Lite Developer + Bruteforce Guru)
Code: Hello Hashcat-Users,
I am proud to announce version 0.09 of the oclHashcat-lite series.
Download it here: http://hashcat.net/oclhashcat-lite/
The highlights of this release are:
Support for AMD GCN cards (hd7xxx series)
I already wrote some more detailed informations about the integration here: http://hashcat.net/forum/thread-817.html
This card is a true DES killer. I wrote some more detailed informations about this topic here: http://hashcat.net/forum/thread-846.html
Added the LM Algorithm
After so many people requested this algorithm in the feature request section I decided to add it even I had not interesst in it.
However, it turned out it was a good investment of time. I realized how many pentester still have need for it.
See here for discussion: http://hashcat.net/forum/thread-167.html
Vectorized datatype kernels for sm_21 NVidia architecture
This a massive improvement for low- and mid-ranged NVidia GPUs.
The gtx560Ti @ MD5, for example, increased by 23% (1252 Mhash/s -> 1660 Mhash/s).
This improvement can be seen on nearly all algorithms for this architecture.
MD4 based algorithm tuning
To make it short: I found a way to reverse another step in MD4.
Especially the NTLM and DCC algorithm benefit from this code change.
The hd6990 @ NTLM broke the 20000 Mhash/s mark on stock clocks. Average increase is around + 9% (19100 Mhash/s -> 20864 Mhash/s).
Updated EULA
This goes back to a discussion we had HD Moore from Rapid7.
The updated EULA is a lot more relaxed for professional pentesters than before.
See changelog for more details.
Fixed some major issues
On thing that many user complained about in oclHashcat-lite 0.08 was its "instability" and problems with session restore.
This popped in because of a default-settings change in oclHashcat-lite v0.07. It has been set back to oclHashcat-lite v0.06 default.
Discussion can be found here: http://hashcat.net/forum/thread-681.html
Harmonization with oclHashcat-plus
The --help page, the --outfile-format and the -m parameter values, in case of an overlap, are now equal to oclHashcat-plus v0.08.
It will help to avoid confusion, thats why I am planning to do the same change on CPU hashcat in the next version.
Official Download Link:
http://hashcat.net/oclhashcat-lite/
Official Hashcat Forum:
http://hashcat.net/forum/
Official SL3 BF Cracking Guide
http://hashcat.net/wiki/cracking_sl3/
oclHashcat now have a special SL3 Kernel with 12.24% Speed Increase on ALL SL3 LBF Tasks!!!
Download here: (yes it's 100% free)
Download oclHashcat-lite-0.06.7z - hashcat, advanced password recovery
Changelogs from v0.05 to v0.06
Code: * changes v0.05 -> v0.06:
type: performance increase
file: kernels
desc: MD5: AMD 1,07%, NVidia 0,62%
desc: md5($pass.$salt): AMD 1,37%, NVidia 8,10%
desc: md5(md5($pass)): AMD 0,94%, NVidia 0%
desc: vBulletin < v3.8.5: AMD 0,30%, NVidia 0%
desc: SHA1: AMD 11,14%, NVidia 13,62%
desc: sha1($pass.$salt): AMD 16,96%, NVidia 39,10%
desc: MySQL > v4.1: AMD 1,99%, NVidia 7,15%
desc: MD4: AMD 13,46%, NVidia 3,34%
desc: NTLM: AMD 13,16%, NVidia 2,57%
desc: DCC: AMD 34,20%, NVidia 0,89%
desc: MSSQL: AMD 11,23%, NVidia 17,89%
desc: SL3: AMD 12,24%, NVidia 13,48%
desc: Oracle 11G: AMD 16,93%, NVidia 13,53%
type: password length increase
file: kernels
desc: MD5: from 15 to 55
desc: md5($pass.$salt): from 15 to 55
desc: md5(md5($pass)): from 15 to 55
desc: vBulletin < v3.8.5: from 15 to 55
desc: SHA1: from 15 to 55
desc: sha1($pass.$salt): from 15 to 55
desc: MySQL > v4.1: from 15 to 55
desc: MD4: from 15 to 55
desc: NTLM: from 15 to 27
desc: DCC: from 15 to 27
desc: MSSQL: from 15 to 25
desc: SHA256: from 15 to 55
desc: Oracle 11G: from 15 to 45
type: feature
file: kernels
desc: added -m 15 = vBulletin > v3.8.5
cred: chick0n
type: feature
file: kernels
desc: increased salt length for DCC from 7 to 19
cred: Rabbitz
type: feature
file: host programs
desc: hardcoded cpu affinity mask to one (cpu #0) to save energy
cred: randyberger
type: feature
file: host programs
desc: added --pw-skip and --pw-limit parameters for distributed computing
cred: d3ad0ne
type: feature
file: host programs
desc: added status codes on exit, see status_codes.txt for listing
cred: hermix
type: bug
file: host programs
desc: rewritten restore function check from scratch
cred: anonymous
type: bug
file: host programs
desc: fixed multiple instances check
cred: FractalizeR
type: bug
file: host programs
desc: fixed 8 bit characters from russian alphabet
cred: Rolf
8,8xx Million Hash Per Second!
HW Specs: 4 x 5870 @ 980 Mhz
New and Faster SL3 LBF Kernel UPDATE for oclHashcat-lite v0.05 by atom
Official Download Link:
Download oclHashcat-lite-0.05.7z - hashcat, advanced password recovery
Official oclHashcat-lite Homepage:
oclHashcat-lite - advanced password recovery
Official Discussion Forum and Discussion Thread:
hashcat Forum
Featuring:
1. Ultra Fast and Stable SL3 Kernel
2. Upto 4% Faster HASH Speeds on 5xxx and 6xxx Cards
3. 100% Free Software !!!
4. Fixed --restore for Resuming BF Tasks
5. Easier Command Line
IMPORTANT CHANGES FOR COMMANDLINE INPUT
1. Change -m 101 into -m 1900
2. Change --output-file into --outfile
3. No need to use --pw-min and --pw-max
4. No need to use --hex-charset --hex-salt
EXAMPLE:
ORIGINAL COMMANDLINE for v0.03:
oclHashcat-lite64 3D5D9E11835243015407B7BA327E30CCB70F4DB0:003519730379149500 -1 00010203040506070809 -m 101 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 --pw-min=15 --pw-max=15 -n 160 --hex-charset --hex-salt --output-format=1 --output-file=351973037914952.txt
NEW COMMANDLINE for v0.05:
oclHashcat-lite64 3D5D9E11835243015407B7BA327E30CCB70F4DB0:003519730379149500 -1 00010203040506070809 -m 1900 ?1?1?1?1?1?1?1?1?1?1?1?1?1?1?1 -n 160 --outfile-format=1 --outfile=351973037914952.txt
REAL SPEED with 2 x HD 6990 @ 950 Mhz, 7,6xx MILLION HASH per Second !!!
REAL SPEED with 2 x HD 5970 @ 950 Mhz, 7,8xx MILLION HASH per Second !!!
Fastest SL3 LBF Free and UPDATED!! OlcHashcat-lite v0.03 by atom!! (HD6xxx Supported).
Thanks to atom for providing us with 100% Free and 100% fast SL3 LBF Software.
Also 100% support for new ATI 6xxx cards (6970, 6990 etc)...
BR
Thomas
BUGFIXES in v0.03
type: bug
file: cudaHashcat-lite, oclHashcat-lite
desc: fixed a bug in security causing hash was not found randomly
cred: RaNdy
type: bug
file: cudaHashcat-lite, oclHashcat-lite
desc: fixed a bug in --restore if command-line contains --pw-skip
cred: Ciukut
type: bug
file: cudaHashcat-lite, oclHashcat-lite
desc: fixed a bug in --restore if command-line contains --pw-min
cred: hermix
information taken from:
oclHashcat-lite v0.03
official download area:
oclHashcat-lite - advanced password recovery
GPU Driver and SDK Requirements:
NV users require ForceWare v260.x+
AMD users require Catalyst v11.3+ with APP SDK2.4+ or integrated OpenCL driverFeatures
Worlds fastest MD4, MD5, SHA1 and SHA256 cracker
Free
Multi-GPU (up to 16 gpus)
Multi-OS (Linux & Windows native binaries)
Multi-Platform (OpenCL & CUDA support)
Multi-Algo (see below)
Low resource utilization, you can still watch movies or play games while cracking
Supports password masks
Supports distributed cracking
Supports pause / resume while cracking
Supports sessions
Supports restore
Supports hex-salt
Supports hex-charset
Integrated thermal watchdog
... and much moreAlgorithms
MD5
md5($pass.$salt)
md5(md5($pass))
vBulletin < v3.8.5
SHA1
sha1($pass.$salt)
MySQL > v4.1
MD4
NTLM
Domain Cached Credentials
SHA256Tested OS's
All Windows and Linux versions should work on both 32 and 64 bitTested GPU's
All CUDA and Stream enabled cards should work==================================================
==================================================
For more information about how to setup Windows or Ubuntu with
oclHashcat-lite, you can visit atom's official forum or you can also
post your inquiries in ATF Section on this thread:
Fastest LBF Free Download!! OlcHashcat-lite v0.2!! HD6xxx Supported!
You can now build yourself the fastest LBF "Monster PC" by using:
Motherboard: MSI Big Bang Marshal
Video Card: 8 pieces ATI 6970
This will give you 14,170 Million HASH/s on STOCK CLOCKS...
Overclock with give you more than 15,xxx HASH/s and the video cards
will still be less than 80 degrees celcius with the stock cooling system.
==================================================
==================================================
Here is OFFICIAL and UPDATED "HOWTO" for hashcat-lite v0.02
oclHashcat-lite SL3 cracking howto
Check out Post # 6 Where atom discusses about MULTIPLE PC Setups to attack a single phone.
atom's forum is 100% open for discussion about his work...
01:53
Unlock Lumia 710 via USB Only in 4 Simple Steps
Unlock Lumia 710 via USB Only in 4 Simple Steps
If you have Qualcomm OSBL, go directly to STEP 3.
If you don't know what Qualcomm OSBL is, start from STEP 1.
STEP 1.
- Update your ATF exe to 9.30 and also UPDATE IMPORTANT FILES.
- After doing this, you should be able to see this File in your Hard Disk:
C:\AdvanceBox Turbo Flasher\Nokia\Lumia\RM803_OSBL_QUALCOMM.esco
---If you cannot see this file inside your Hard Disk, go back to Step 1---
STEP 2.
- Flash this 1 File to your Phone using the +MCU Button on the ATF
software and manually Locating the File in the correct Directory:
C:\AdvanceBox Turbo Flasher\Nokia\Lumia\
Screenshot Helper:
STEP 3.
- Click SP Unlock Button...
STEP 4.
If you have Qualcomm OSBL, go directly to STEP 3.
If you don't know what Qualcomm OSBL is, start from STEP 1.
STEP 1.
- Update your ATF exe to 9.30 and also UPDATE IMPORTANT FILES.
- After doing this, you should be able to see this File in your Hard Disk:
C:\AdvanceBox Turbo Flasher\Nokia\Lumia\RM803_OSBL_QUALCOMM.esco
---If you cannot see this file inside your Hard Disk, go back to Step 1---
STEP 2.
- Flash this 1 File to your Phone using the +MCU Button on the ATF
software and manually Locating the File in the correct Directory:
C:\AdvanceBox Turbo Flasher\Nokia\Lumia\
Screenshot Helper:
STEP 3.
- Click SP Unlock Button...
STEP 4.
01:35
ATF First In The World Lumia 620 WinPhone 8 Full Flashing
Also check out other Lumia WinPhone 8 Phones Flashed by ATF:
ATF First In The World Lumia 920 WinPhone 8 Full Flashing!
ATF First In The World Lumia 810 WinPhone 8 Full Flashing!
ATF First In The World Lumia 820 WinPhone 8 Full Flashing!
ATF First In The World Lumia 822 WinPhone 8 Full Flashing!
ATF First In The World Lumia 620 WinPhone 8 Full Flashing!
Another Lumia WinPhone 8 Flashed Successfully with ATF...
Here is the Screenshot:
Here is the Flashing Logs:
Code:
Windows Phone 8 Flashing Started
Loading Flash Files Please Wait...
======================================================
Windows Phone 8 Lumia Flasher
======================================================
If the Phone is ALIVE
1. Power On the Phone and Connect it to the USB Port
If the Phone is DEAD
1. Connect Phone to the USB Port
2. Press and Hold the VOLUME DOWN and POWER Buttons
3. Wait until the Phone Vibrates Shortly...
4. Stop Pressing the Buttons...
======================================================
================================================
Basic Phone Information
================================================
SW Version : 1030.5603.1250.0001
IMEI Plain : 354636051430307
HW Version : 5000
Phone Type : RM-846
Product Code : 059R3F2
Module Code : 0205404
PSN Number : CKQ578571
Manufacturer ID : RM-846_apac_prc_225
Operator Name : 000-CN
Phone Version : BuildDate : Dec 6 2012 , BuildType : Release , HelloString : NCSd for WP8 , Version : 1.22
Security Mode : Restricted
Variant Information: PRC CV China BLACK V1 Default
================================================
Extended Phone Information
================================================
Public ID : 0385A1440771590576B5303CD247A5EF1CC526FA
Wireless Lan 0 ID: A8:44:81:32:F4:C8
Wireless Lan 1 ID: A8:44:81:32:F4:C9
Wireless Lan 2 ID: A8:44:81:32:F4:CA
Wireless Lan 3 ID: A8:44:81:32:F4:CB
Bluetooth ID : A8:44:81:32:71:2E
================================================
Simlock Information
================================================
SIMLOCK STATE : Not Locked
Booting Flash Mode Initiated...
Please wait upto 15 Seconds for HW Reset
Boot Flash Mode Successful...
Phone Info Query Start...
Blocks Returned: 0x07 Blocks
Block ID 0x01 : 00241000
Block ID 0x02 : 00240000
Block ID 0x03 : 00E74000
Block ID 0x05 : Nokia.MSM8227.P5122.1.2
Block ID 0x0D : 0001
Block ID 0x0F : 0301010100000101FF
Block ID 0x10 : 0100030000
Checking SD Card Size...
Card Size: 0x00000000
Checking Platform Security Status...
Platform Secure Boot Status: Active
Secure FFU EFUSE Status: Active
Debug Status: Active
RDC Status: Not Active
Authentication Status: Not Active
UEFI Secure Boot Status: Active
Checking Secure FFU Mode...
Secure FFU Mode : SYNC + ASYNC
Query Flash App Information...
Flash App Information: 020109011000
UEFI App: FLASH APP
Flash App Protocol Version: 1.9
Flash App Implementation Version: 1.16
Query ROOT KEY HASH...
ROOT_KEY_HASH: 67131691EEDD1F38568C7FFAE284FB2621680FEAC833314467E31DAA963D1467
Erasing Data Partition...
Data Partition Erased Successfully
Sending Image Signatures...
Image Signatures Accepted!
Preparing Buffers for DATA LOOP...
Allocating System RAM OK!
Start Sending DATA BLOCKS...
Finished Sending all DATA BLOCKS!
Exiting FLASH Mode via REBOOT...
Exit FLASH Mode Successful!
Flashing Done!
Total Flashing Time : 00:04:01
FLASHING The Phone...
TEST MODE aka MMOS..
Trust ATF...
01:32
ATF First In The World Asha 206 / 2060 USB Full Flashing
ATF First In The World Asha 206 / 2060 USB Full Flashing!
Here is the Screenshot:
sha 206
Here Is Pinout
ATF First In The World Asha 206 / 2060 USB Full Flashing!
(RM-872, RM-873)
Here is the Flashing Logs:
Code:
Here is My A
Here is the Screenshot:
sha 206
Here Is Pinout
ATF First In The World Asha 206 / 2060 USB Full Flashing!(RM-872, RM-873)
Here is the Flashing Logs:
Code:
Number of Image Files: 3
Processing Image File :
rm872__03.58.mcusw
Processing Image File :
rm872__03.58.ppm_m4
Processing Image File :
rm872__03.58.image_m4_059Q4M1
[]: Found 0 active devices.
[]: Not Found!
Rebooting Phone...
AUTO SELECTED DEAD USB FLASHING...
If Phone Booting does not Start in 5 Seconds,
Then Perform Steps 1, 2, 3 and 4...
1. Remove USB and Battery...
2. Insert USB.
3. Insert Battery. (Some phones boot automatically)
4. Please Power on phone shortly...
Infineon USB Boot: F00A1FB300020303010100FF
Sending PBL...
PBL Successfully Sent...
Sending SBL...
SBL Successfully Sent...
Setting Transmission Speed Done...
Flash Chip Manufacturer: Intel Electronics Corp.
Flash Boot Successful...
Unique Data: 12401407AD102819
Original Product Code: 059Q4M1
Reading : CCC... OK!
Reading : HWC... OK!
Reading : NPC... OK!
RPL Backup was Successful...
Plain RPL saved to:
C:\AdvanceBox Turbo Flasher\Nokia\Backup\354125050970489\354125050970489_013803.rpl
Data Sections : 04
Current File : rm872__03.58.mcusw
Compile Name: rm872__03.58.mcusw_ebl_psi.fls
Image Type : Main Firmware
Data Size : 26480008 Bytes
Sending Certificate Block
FIRMWARE Certificate Block Sent Successfully...
Processing Section 01
FIRMWARE Erase Block: 0x40000000~0x4001FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 131072 bytes
Data Checksum: AFC6
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 02
FIRMWARE Erase Block: 0x40040000~0x4005FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 131072 bytes
Data Checksum: 7A66
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 03
FIRMWARE Erase Block: 0x40060000~0x4015FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 1048576 bytes
Data Checksum: 5169
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 04
FIRMWARE Erase Block: 0x40280000~0x41A7FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 25165824 bytes
Data Checksum: 3E66
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 05
FIRMWARE Erase Block: 0x43E20000~0x43E5FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Data Verification Successful...
Data Sections : 01
Current File : rm872__03.58.ppm_m4
Compile Name: package_m4.ppm_ebl_psi.fls
Image Type : PPM Image
Data Size : 5714012 Bytes
Sending Certificate Block
PPM Certificate Block Sent Successfully...
Processing Section 01
PPM Erase Block: 0x41A80000~0x420FFFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 5710668 bytes
Data Checksum: B665
Uploading Data Blocks to phone...
Block Write Successful...
PPM Data Blocks uploaded to phone...
Data Verification Successful...
Data Sections : 01
Current File : rm872__03.58.image_m4_059Q4M1
Compile Name: package_m4_059Q4M1.image.fls
Image Type : CONTENT Package
Data Size : 15731984 Bytes
Sending Certificate Block
CONTENT Certificate Block Sent Successfully...
Processing Section 01
CONTENT Erase Block: 0x42100000~0x43E1FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 15728640 bytes
Data Checksum: E29A
Uploading Data Blocks to phone...
Block Write Successful...
CONTENT Data Blocks uploaded to phone...
Processing Section 02
CONTENT Erase Block: 0x43E60000~0x43F3FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Data Verification Successful...
Total Flashing Time (Erase + Flashing) : 00:06:40
(Booting time is NOT Included)
Waiting for Phone to Start-Up..(Max 150 seconds)
Scanning USB Ports...
================================================
Basic Phone Information
================================================
MCU Version: V 03.58 05-12-12 RM-872 (c) Nokia
IMEI Plain : 354125050970489
IMEI Spare : A354125050970480
IMEI SV : 33541250509704805F
IMEI (2nd) : 354125050970497
IMEI Spare : A354125050970490
IMEI SV : 33541250509704905F
Phone Model: K 206
Category : Entry
Phone Type : RM-872
================================================
Extended Phone Information
================================================
Product Serial Number: 831BC53BI
Product Code : 059Q4M1
Module Code : 0205283
Basic Production Code: 059P6H4
Long Production SN : 0
PPM SW Version : V 03.58 05-12-12 RM-872 (c) Nokia M4
BT MCM Version : 19b5-22012
MCU SW Version : V 03.58 05-12-12 RM-872 (c) Nokia
HW Version : 2300
RFIC Version : 68
LCD Version : TPO
FWID Version : jV 03.58 05-12-12 RM-872 (c) Nokia V 03.58 05-12-12 RM-872 (c) Nokia M4 059Q4M1 001
Content Pack Version : Content: m4_059Q4M1 V 03.58 05-12-12 RM-872 (c) Nokia
Bluetooth ID : 54:79:75:83:95:A0
CS Type : GSM900, GSM1800
********** SIMLOCK INFO **********
CONFIG_DATA : 0010100000000000
PROFILE_BITS : 800000000004000B
ASIC : 11
PROVIDER : Default Test Operator
LOCK COUNTERS: KEYPRESS 0/3, FBUS 0/10
Block [1] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [2] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [3] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [4] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [5] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [6] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [7] 1:Open 2:Open 3:Open 4:Open 5:Open
SIMLOCK_TYPE : PA_SIMLOC30 (20-digit NCK)
SIMLOCK_TEST : PASSED
SECURITY_TEST : PASSED
SECURITY_CODE : 12345
PHONE_MODE : TEST
================================================
Dynamic Camera Configuration
================================================
DCC ID : 01029704
DCC Ver: 008013
Status : OK
======================================================
Selected VPL File:
RM872_059Q4M1_03.58_016.vpl
======================================================
Variant Details : RM-872 MEA_M4_WHITE_ARABIC_BH
Software Version : 03.58
Product Type : RM-872
Product Code : 059Q4M1
Variant Version : 016
FACTORY SET TO : Full Factory Set
OK
FACTORY SET TO : User Data
OK
FACTORY SET TO : Leave Factory
OK
FACTORY SET TO : Service Center
OK
FACTORY SET TO : Software Upgrade
OK
FACTORY SET TO : Production Tune
OK
Life timer data is not yet used...
Life timer: ----:--
Here is My A
01:15
ATF First In The World Asha 205 / 2050 USB Full Flashing!
ATF First In The World Asha 205 / 2050 USB Full Flashing!
ATF First In The World Asha 205 / 2050 USB Full Flashing!
(RM-862, RM-863 and RM-864)
Here is the Screenshot:
Here is the Flashing Logs:
Code:
Here is the Test Phone:
Soldered Wires (I had no time to make cable)
Here are the USB Pinouts
Trust ATF...
ATF First In The World Asha 205 / 2050 USB Full Flashing!
(RM-862, RM-863 and RM-864)
Here is the Screenshot:
Here is the Flashing Logs:
Code:
Number of Image Files: 3
Processing Image File :
rm862__03.18.mcusw
Processing Image File :
rm862__03.18.ppm_t
Processing Image File :
rm862__03.18.image_t_059Q080
[]: Found 1 active devices.
[Nokia Asha 200 USB Phonet]: Opening Connection
[Nokia Asha 200 USB Phonet]: Port opened OK!
SW: V 03.18 02-12-12 RM-862 (c) Nokia
IMEI: 355488051006524
START FULL PM BACKUP
Please Wait...
Reading : PM 0~400... OK!
FULL PM Backup Saved to:
C:\AdvanceBox Turbo Flasher\Nokia\Backup\355488051006524\USB_FULL_BACKUP_V 03.18 02-12-12 RM-862 (c) Nokia_355488051006524__44149.pm
Reading Battery Value : 3805 mV
Rebooting Phone...
AUTO SELECTED DEAD USB FLASHING...
If Phone Booting does not Start in 5 Seconds,
Then Perform Steps 1, 2, 3 and 4...
1. Remove USB and Battery...
2. Insert USB.
3. Insert Battery. (Some phones boot automatically)
4. Please Power on phone shortly...
Infineon USB Boot: F00A1FB300020303010100FF
Sending PBL...
PBL Successfully Sent...
Sending SBL...
SBL Successfully Sent...
Setting Transmission Speed Done...
Flash Chip Manufacturer: Intel Electronics Corp.
Flash Boot Successful...
Unique Data: 0210140112072813
Original Product Code: 059R563
Reading : CCC... OK!
Reading : HWC... OK!
Reading : NPC... OK!
RPL Backup was Successful...
Plain RPL saved to:
C:\AdvanceBox Turbo Flasher\Nokia\Backup\355488051006524\355488051006524_44158.rpl
Data Sections : 04
Current File : rm862__03.18.mcusw
Compile Name: rm862__03.18.mcusw_ebl_psi.fls
Image Type : Main Firmware
Data Size : 26217864 Bytes
Sending Certificate Block
FIRMWARE Certificate Block Sent Successfully...
Processing Section 01
FIRMWARE Erase Block: 0x40000000~0x4001FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 131072 bytes
Data Checksum: B10A
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 02
FIRMWARE Erase Block: 0x40040000~0x4005FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 131072 bytes
Data Checksum: 7A56
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 03
FIRMWARE Erase Block: 0x40060000~0x4015FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 1048576 bytes
Data Checksum: CC33
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 04
FIRMWARE Erase Block: 0x40280000~0x41A3FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 24903680 bytes
Data Checksum: 787F
Uploading Data Blocks to phone...
Block Write Successful...
FIRMWARE Data Blocks uploaded to phone...
Processing Section 05
FIRMWARE Erase Block: 0x43E20000~0x43E5FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Data Verification Successful...
Data Sections : 01
Current File : rm862__03.18.ppm_t
Compile Name: package_t.ppm_ebl_psi.fls
Image Type : PPM Image
Data Size : 5655192 Bytes
Sending Certificate Block
PPM Certificate Block Sent Successfully...
Processing Section 01
PPM Erase Block: 0x41A40000~0x4207FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 5651848 bytes
Data Checksum: EFA3
Uploading Data Blocks to phone...
Block Write Successful...
PPM Data Blocks uploaded to phone...
Data Verification Successful...
Data Sections : 01
Current File : rm862__03.18.image_t_059Q080
Compile Name: package_t_059Q080.image.fls
Image Type : CONTENT Package
Data Size : 16518416 Bytes
Sending Certificate Block
CONTENT Certificate Block Sent Successfully...
Processing Section 01
CONTENT Erase Block: 0x42080000~0x43E1FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Preparing Data Blocks...
Data Size: 16515072 bytes
Data Checksum: A69A
Uploading Data Blocks to phone...
Block Write Successful...
CONTENT Data Blocks uploaded to phone...
Processing Section 02
CONTENT Erase Block: 0x43E60000~0x43F3FFFE
Start Erasing...
Erasing Please Wait...
Block Erase Done...
Data Verification Successful...
Total Flashing Time (Erase + Flashing) : 00:06:24
(Booting time is NOT Included)
Waiting for Phone to Start-Up..(Max 150 seconds)
Scanning USB Ports...
================================================
Basic Phone Information
================================================
MCU Version: V 03.18 02-12-12 RM-862 (c) Nokia
IMEI Plain : 355488051006524
IMEI Spare : A355488051006520
IMEI SV : 33554880510065205F
IMEI (2nd) : 355488051006532
IMEI Spare : A355488051006530
IMEI SV : 33554880510065305F
Phone Model: Nokia 2050
Category : Phone
Phone Type : RM-862
================================================
Extended Phone Information
================================================
Product Serial Number: DF6CFE3AH
Product Code : 059R563
Module Code : 0205222
Basic Production Code: 059N267
Long Production SN : 0
PPM SW Version : V 03.18 02-12-12 RM-862 (c) Nokia T
BT MCM Version : 19b5-22012
MCU SW Version : V 03.18 02-12-12 RM-862 (c) Nokia
HW Version : 1000
RFIC Version : 68
LCD Version : TPO
FWID Version : iV 03.18 02-12-12 RM-862 (c) Nokia V 03.18 02-12-12 RM-862 (c) Nokia T 059R563 001
Content Pack Version : Content: t_059Q080 V 03.18 02-12-12 RM-862 (c) Nokia
Bluetooth ID : 54:79:75:05:D5:0E
CS Type : GSM900, GSM1800
********** SIMLOCK INFO **********
CONFIG_DATA : 0010100000000000
PROFILE_BITS : 800000000004000B
ASIC : 11
PROVIDER : Default Test Operator
LOCK COUNTERS: KEYPRESS 0/3, FBUS 0/10
Block [1] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [2] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [3] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [4] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [5] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [6] 1:Open 2:Open 3:Open 4:Open 5:Open
Block [7] 1:Open 2:Open 3:Open 4:Open 5:Open
SIMLOCK_TYPE : PA_SIMLOC30 (20-digit NCK)
SIMLOCK_TEST : PASSED
SECURITY_TEST : PASSED
SECURITY_CODE : 12345
PHONE_MODE : TEST
================================================
Dynamic Camera Configuration
================================================
DCC ID : NI00CS00000401022F03
DCC Ver: 010009
Status : OK
======================================================
Selected VPL File:
RM862_059Q080_03.18_021.vpl
======================================================
Variant Details : RM-862 APAC_T_CYAND_COM_PH
Software Version : 03.18
Product Type : RM-862
Product Code : 059Q080
Variant Version : 021
FACTORY SET TO : Full Factory Set
OK
FACTORY SET TO : User Data
OK
FACTORY SET TO : Leave Factory
OK
FACTORY SET TO : Service Center
OK
FACTORY SET TO : Software Upgrade
OK
FACTORY SET TO : Production Tune
OK
Life timer data is not yet used...
Life timer: ----:--
Here is the Test Phone:
Soldered Wires (I had no time to make cable)
Here are the USB Pinouts
Trust ATF...
Subscribe to:
Posts (Atom)
